
From hannes.tschofenig@nsn.com  Wed Feb  1 04:34:13 2012
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7B021F86C7 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 04:34:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.421
X-Spam-Level: 
X-Spam-Status: No, score=-106.421 tagged_above=-999 required=5 tests=[AWL=0.177, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BekzDMMHfeBy for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 04:34:12 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFDC21F86C4 for <ietf@ietf.org>; Wed,  1 Feb 2012 04:34:10 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q11CY3VQ005541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 1 Feb 2012 13:34:03 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q11CXuV3027822; Wed, 1 Feb 2012 13:34:03 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 1 Feb 2012 13:34:00 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCE0DD.C5400047"
Subject: RE: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard
Date: Wed, 1 Feb 2012 14:33:58 +0200
Message-ID: <999913AB42CC9341B05A99BBF358718D010E445C@FIESEXC035.nsn-intra.net>
In-Reply-To: <1328072000.47240.YahooMailNeo@web125501.mail.ne1.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard
thread-index: AczgnXn6BKCcm8DASLO05SnFWWZoWwAHXCyg
References: <1328072000.47240.YahooMailNeo@web125501.mail.ne1.yahoo.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "Francisco Corella" <fcorella@pomcor.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 01 Feb 2012 12:34:00.0248 (UTC) FILETIME=[C613C380:01CCE0DD]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:34:13 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCE0DD.C5400047
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Francisco,=20

=20

if a token is created for access to server S1 and S2 then any party that
gets access to the token can obviously access both servers. This should
not be super surprising.=20

=20

So, if you have a deployment where you want to grant access to resources
at multiple servers and the attack you describe is a concern then you
need to create multiple tokens.=20

=20

The content of the token defines what the token can be used for.=20

=20

The bearer token specification does not define the content of the token
and therefore it is difficult to say more about it beyond what it
already says.=20

=20

If you think it is worth to specify highlight this type of attack then
the appropriate place to describe it is the threats document.=20

=20

Ciao
Hannes

=20

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Francisco Corella
Sent: Wednesday, February 01, 2012 6:53 AM
To: ietf@ietf.org
Subject: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The
OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard

=20

The bearer token protocol described in the document referenced in the
subject line is vulnerable to the following attack by a malicious
resource server.

There are two resource servers S1 and S2, S1 hosting a resource R1,
and S2 hosting a resource R2.  Servers are not entitled to access
resources that they do not host.  S1 is malicious.  The client obtains
a broadly scoped access token that allows access to both resources.
The client uses the access token to obtain resource R1 from server S1.
Malicious server S1 then presents the access token received from the
client to server S2 and gains access to resource R2, which it is not
entitled to access.

Including the identity of the intended recipients in the token, as
recommended in Section 4.2, does not help, since the intended
recipients of the broadly scoped token include both R1 and R2.

Francisco


------_=_NextPart_001_01CCE0DD.C5400047
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1856651489;
	mso-list-type:hybrid;
	mso-list-template-ids:1564776464 119044392 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;
	mso-fareast-font-family:SimSun;
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Francisco, <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>if a token is created for access to server S1 and S2 then any party =
that gets access to the token can obviously access both servers. This =
should not be super surprising. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>So, if you have a deployment where you want to grant access to =
resources at multiple servers and the attack you describe is a concern =
then you need to create multiple tokens. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The content of the token defines what the token can be used for. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The bearer token specification does not define the content of the =
token and therefore it is difficult to say more about it beyond what it =
already says. <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If you think it is worth to specify highlight this type of attack =
then the appropriate place to describe it is the threats document. =
<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Ciao<br>Hannes<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></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=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>ext Francisco Corella<br><b>Sent:</b> Wednesday, February 01, 2012 =
6:53 AM<br><b>To:</b> ietf@ietf.org<br><b>Subject:</b> REVISED Last =
Call: &lt;draft-ietf-oauth-v2-bearer-15.txt&gt; (The OAuth =
2.0Authorization Protocol: Bearer Tokens) to Proposed =
Standard<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt;background:white'><span =
style=3D'color:black'>The bearer token protocol described in the =
document referenced in the<br>subject line is vulnerable to the =
following attack by a malicious<br>resource server.<br><br>There are two =
resource servers S1 and S2, S1 hosting a resource R1,<br>and S2 hosting =
a resource R2.&nbsp; Servers are not entitled to access<br>resources =
that they do not host.&nbsp; S1 is malicious.&nbsp; The client =
obtains<br>a broadly scoped access token that allows access to both =
resources.<br>The client uses the access token to obtain resource R1 =
from server S1.<br>Malicious server S1 then presents the access token =
received from the<br>client to server S2 and gains access to resource =
R2, which it is not<br>entitled to access.<br><br>Including the identity =
of the intended recipients in the token, as<br>recommended in Section =
4.2, does not help, since the intended<br>recipients of the broadly =
scoped token include both R1 and =
R2.<br><br>Francisco<o:p></o:p></span></p></div></div></div></body></html=
>
------_=_NextPart_001_01CCE0DD.C5400047--

From Jinesh.Doshi@Colorado.EDU  Wed Feb  1 08:49:59 2012
Return-Path: <Jinesh.Doshi@Colorado.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 449E221F87F2 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 08:49:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPBwUnK0qAjz for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 08:49:58 -0800 (PST)
Received: from ipmx3.colorado.edu (ipmx3.colorado.edu [128.138.128.233]) by ietfa.amsl.com (Postfix) with ESMTP id 42E8821F86E0 for <ietf@ietf.org>; Wed,  1 Feb 2012 08:49:58 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEAEhsKU/AqBGb/2dsb2JhbABDsAOBbQFFGQV3hkOCK69UiQWLMgEFAgIJBQwGBAEEAUABAQECAQMBgnECAQsCHgIEbCshgxwEiEGMX5J1
X-IronPort-AV: E=Sophos;i="4.71,602,1320649200"; d="scan'208";a="490764513"
Received: from omr-raz-2-priv.int.colorado.edu ([192.168.17.155]) by ipmx3-priv.int.colorado.edu with ESMTP; 01 Feb 2012 09:49:57 -0700
Received: from superman.int.Colorado.EDU (EHLO superman.int.colorado.edu) ([172.20.56.167]) by omr-raz-2-priv.int.colorado.edu (MOS 4.1.10-GA FastPath queued) with ESMTP id CXY31639; Wed, 01 Feb 2012 09:49:57 -0700 (MST)
Received: (from superman.int.colorado.edu [172.20.56.142]) by superman.int.colorado.edu (MOS 3.10.10a-GA) with HTTPS/1.1 id APY49592 (AUTH jido6357); Wed,  1 Feb 2012 09:49:57 -0700 (MST)
From: Jinesh Doshi <Jinesh.Doshi@Colorado.EDU>
Subject: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
To: ietf@ietf.org
X-Mailer: Mirapoint Webmail Direct 3.10.10a-GA
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20120201094957.APY49592@superman.int.colorado.edu>
Date: Wed,  1 Feb 2012 09:49:57 -0700 (MST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:55:22 -0000

I support the updates to this draft.

Jinesh

From fcorella@pomcor.com  Wed Feb  1 12:31:23 2012
Return-Path: <fcorella@pomcor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2780811E8094 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 12:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.691
X-Spam-Level: 
X-Spam-Status: No, score=-0.691 tagged_above=-999 required=5 tests=[AWL=0.418,  BAYES_05=-1.11, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jaldjOlyVcBV for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 12:31:22 -0800 (PST)
Received: from nm5-vm1.bullet.mail.ne1.yahoo.com (nm5-vm1.bullet.mail.ne1.yahoo.com [98.138.91.32]) by ietfa.amsl.com (Postfix) with SMTP id D69EA11E8085 for <ietf@ietf.org>; Wed,  1 Feb 2012 12:31:21 -0800 (PST)
Received: from [98.138.90.48] by nm5.bullet.mail.ne1.yahoo.com with NNFMP; 01 Feb 2012 20:31:16 -0000
Received: from [98.138.89.252] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 01 Feb 2012 20:31:16 -0000
Received: from [127.0.0.1] by omp1044.mail.ne1.yahoo.com with NNFMP; 01 Feb 2012 20:31:16 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 850107.76920.bm@omp1044.mail.ne1.yahoo.com
Received: (qmail 30482 invoked by uid 60001); 1 Feb 2012 20:31:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1328128276; bh=rhzbh/6YkEnyQQbLwjf4/lzStymlqkpmCJlKw1jdRMw=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=KngpNNsizH8dAbNRDYVbFjdS6pnEEximU9P+0L6v+XwEXNM3iyxuNhJYYB9ZqIW6OpxR7hHaJecAeDGqRb+JGxS0xj8nxnblxO7ullI5MaB5rVCngOfODSlc3UQc7d5B9795Z9yBGICRuOR92yWMZnxvxYocFTuzR2+vn+JOtuw=
X-YMail-OSG: __d7i64VM1mHIdP98G8UoZORyCn0Ddh2K4y1kLqcDdixBek _TQuIKoObSbXfQJCHD2nDSZIbuq13MinaZH8KL9W_i9_3c88AG1pzPw4WuNt 3VwUOs5mFO1FZ8xJHJkw._t48y1moimIlPLC9H8Q5D8f9wKP4AzRJmLKKBFp zEItmtS18SNtz07pOtRZPv5qFNxKkK7GwKgTO_Rjcsg2_c.7zXlRocZrzHqH VG5JajL9yGyfIN_Et7.WHq3PYdLPnjq.gUjeafABX3W2bYiLiH.kRl3vHZdV P73xmR38mwSMlv7_wF6EpqIeJPg_q35DUFzuXPuQNS7kf0h7ry2obVP74w9m r5le.UkGv._yryIIgV4sDyvkTYomapcRXtWplvCizCdoQ0ZfVO0nCEIyRPvt EGgHOsohKPtlBVj97L7QaSRISRzLF9llr8CAQ2C6EfBSllbkAgNjrXCLtuAZ 0dYc7JG6GWB_0Q8HhbpCX8MMwI20H
Received: from [174.65.117.33] by web125501.mail.ne1.yahoo.com via HTTP; Wed, 01 Feb 2012 12:31:16 PST
X-RocketYMMF: francisco_corella
X-Mailer: YahooMailWebService/0.8.116.331537
References: <1328072000.47240.YahooMailNeo@web125501.mail.ne1.yahoo.com> <999913AB42CC9341B05A99BBF358718D010E445C@FIESEXC035.nsn-intra.net>
Message-ID: <1328128276.30174.YahooMailNeo@web125501.mail.ne1.yahoo.com>
Date: Wed, 1 Feb 2012 12:31:16 -0800 (PST)
From: Francisco Corella <fcorella@pomcor.com>
Subject: Re: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard
To: "Tschofenig, Hannes \(NSN - FI/Espoo\)" <hannes.tschofenig@nsn.com>, "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D010E445C@FIESEXC035.nsn-intra.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="329289550-1412768873-1328128276=:30174"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Francisco Corella <fcorella@pomcor.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:31:23 -0000

--329289550-1412768873-1328128276=:30174
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Hannes,=0A=0A> if a token is created for access to server S1 and S2 then=
 any party=0A> that gets access to the token can obviously access both serv=
ers. This=0A> should not be super surprising.=0A> =0A> So, if you have a de=
ployment where you want to grant access to=0A> resources at multiple server=
s and the attack you describe is a concern=0A> then you need to create mult=
iple tokens.=0A> =0A> The content of the token defines what the token can b=
e used for.=0A> =0A> The bearer token specification does not define the con=
tent of the=0A> token and therefore it is difficult to say more about it be=
yond what=0A> it already says.=0A> =0A> If you think it is worth to specify=
 highlight this type of attack then=0A> the appropriate place to describe i=
t is the threats document.=0A=0AWhy shouldn't this attack be discussed in t=
he security considerations=0Asection of the protocol spec?=A0 The security =
considerations section=0Aalready addresses two closely related attacks: "to=
ken redirect" and=0A"token replay".=A0 It could use the following language =
to address=0Atogether this attack and the "token redirect" attack:=0A=0A* I=
f there are multiple resource servers, and different resource=0A* servers p=
rovide client access to different resources, and resource=0A* servers are n=
ot entitled to access resources others than those that=0A* they provide cli=
ent access to, then care must be taken to prevent a=0A* malicious resource =
server from using an access token presented by a=0A* client to access, thro=
ugh another resource server, a resource that=0A* that the malicious server =
does not provide client access to.=A0 This=0A* can be accomplished in two d=
ifferent ways:=0A* =0A*=A0=A0 1. By including in the access token a specifi=
cation of the set of=0A*=A0=A0 resources that can be accessed by the token.=
=A0 The set must satisfy=0A*=A0=A0 the following condition: every resource =
server that provides=0A*=A0=A0 client access to a resource in the set must =
provide client access=0A*=A0=A0 to all the resources in the set.=A0 Or,=0A*=
=0A*=A0=A0 2. By including in the access token a specification of the set o=
f=0A*=A0=A0 servers that the token can be presented to.=A0 A resource serve=
r=0A*=A0=A0 must verify that it is a member of the set when presented with =
the=0A*=A0=A0 token.=A0 The set must satisfy the following condition: all t=
he=0A*=A0=A0 resource servers in the set must provide client access to the =
same=0A*=A0=A0 set of resources.=0A=0ABest,=0A=0AFrancisco=0A=0A=0A=0A=0A=
=0A>________________________________=0A> From: "Tschofenig, Hannes (NSN - F=
I/Espoo)" <hannes.tschofenig@nsn.com>=0A>To: Francisco Corella <fcorella@po=
mcor.com>; ietf@ietf.org =0A>Sent: Wednesday, February 1, 2012 4:33 AM=0A>S=
ubject: RE: REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAu=
th 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard=0A> =0A>=
=0A>Hi Francisco, =0A>=A0=0A>if a token is created for access to server S1 =
and S2 then any party that gets access to the token can obviously access bo=
th servers. This should not be super surprising. =0A>=A0=0A>So, if you have=
 a deployment where you want to grant access to resources at multiple serve=
rs and the attack you describe is a concern then you need to create multipl=
e tokens. =0A>=A0=0A>The content of the token defines what the token can be=
 used for. =0A>=A0=0A>The bearer token specification does not define the co=
ntent of the token and therefore it is difficult to say more about it beyon=
d what it already says. =0A>=A0=0A>If you think it is worth to specify high=
light this type of attack then the appropriate place to describe it is the =
threats document. =0A>=A0=0A>Ciao=0A>Hannes=0A>=A0=0A>From:ietf-bounces@iet=
f.org [mailto:ietf-bounces@ietf.org] On Behalf Of ext Francisco Corella=0A>=
Sent: Wednesday, February 01, 2012 6:53 AM=0A>To: ietf@ietf.org=0A>Subject:=
 REVISED Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0Autho=
rization Protocol: Bearer Tokens) to Proposed Standard=0A>=A0=0A>The bearer=
 token protocol described in the document referenced in the=0A>subject line=
 is vulnerable to the following attack by a malicious=0A>resource server.=
=0A>=0A>There are two resource servers S1 and S2, S1 hosting a resource R1,=
=0A>and S2 hosting a resource R2.=A0 Servers are not entitled to access=0A>=
resources that they do not host.=A0 S1 is malicious.=A0 The client obtains=
=0A>a broadly scoped access token that allows access to both resources.=0A>=
The client uses the access token to obtain resource R1 from server S1.=0A>M=
alicious server S1 then presents the access token received from the=0A>clie=
nt to server S2 and gains access to resource R2, which it is not=0A>entitle=
d to access.=0A>=0A>Including the identity of the intended recipients in th=
e token, as=0A>recommended in Section 4.2, does not help, since the intende=
d=0A>recipients of the broadly scoped token include both R1 and R2.=0A>=0A>=
Francisco=0A>=0A>
--329289550-1412768873-1328128276=:30174
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:12pt">Hi Hannes,<br><br>&gt=
; if a token is created for access to server S1 and S2 then any party<br>&g=
t; that gets access to the token can obviously access both servers. This<br=
>&gt; should not be super surprising.<br>&gt; <br>&gt; So, if you have a de=
ployment where you want to grant access to<br>&gt; resources at multiple se=
rvers and the attack you describe is a concern<br>&gt; then you need to cre=
ate multiple tokens.<br>&gt; <br>&gt; The content of the token defines what=
 the token can be used for.<br>&gt; <br>&gt; The bearer token specification=
 does not define the content of the<br>&gt; token and therefore it is diffi=
cult to say more about it beyond what<br>&gt; it already says.<br>&gt; <br>=
&gt; If you think it is worth to specify highlight this type of attack then=
<br>&gt; the appropriate place to describe it is the threats
 document.<br><br>Why shouldn't this attack be discussed in the security co=
nsiderations<br>section of the protocol spec?&nbsp; The security considerat=
ions section<br>already addresses two closely related attacks: "token redir=
ect" and<br>"token replay".&nbsp; It could use the following language to ad=
dress<br>together this attack and the "token redirect" attack:<br><br>* If =
there are multiple resource servers, and different resource<br>* servers pr=
ovide client access to different resources, and resource<br>* servers are n=
ot entitled to access resources others than those that<br>* they provide cl=
ient access to, then care must be taken to prevent a<br>* malicious resourc=
e server from using an access token presented by a<br>* client to access, t=
hrough another resource server, a resource that<br>* that the malicious ser=
ver does not provide client access to.&nbsp; This<br>* can be accomplished =
in two different ways:<br>* <br>*&nbsp;&nbsp; 1. By including in the
 access token a specification of the set of<br>*&nbsp;&nbsp; resources that=
 can be accessed by the token.&nbsp; The set must satisfy<br>*&nbsp;&nbsp; =
the following condition: every resource server that provides<br>*&nbsp;&nbs=
p; client access to a resource in the set must provide client access<br>*&n=
bsp;&nbsp; to all the resources in the set.&nbsp; Or,<br>*<br>*&nbsp;&nbsp;=
 2. By including in the access token a specification of the set of<br>*&nbs=
p;&nbsp; servers that the token can be presented to.&nbsp; A resource serve=
r<br>*&nbsp;&nbsp; must verify that it is a member of the set when presente=
d with the<br>*&nbsp;&nbsp; token.&nbsp; The set must satisfy the following=
 condition: all the<br>*&nbsp;&nbsp; resource servers in the set must provi=
de client access to the same<br>*&nbsp;&nbsp; set of resources.<br><br>Best=
,<br><br>Francisco<br><br><div><br><blockquote style=3D"border-left: 2px so=
lid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left:
 5px;">  <div style=3D"font-family: times new roman, new york, times, serif=
; font-size: 12pt;"> <div style=3D"font-family: times new roman, new york, =
times, serif; font-size: 12pt;"> <div dir=3D"ltr"> <font face=3D"Arial" siz=
e=3D"2"> <hr size=3D"1">  <b><span style=3D"font-weight:bold;">From:</span>=
</b> "Tschofenig, Hannes (NSN - FI/Espoo)" &lt;hannes.tschofenig@nsn.com&gt=
;<br> <b><span style=3D"font-weight: bold;">To:</span></b> Francisco Corell=
a &lt;fcorella@pomcor.com&gt;; ietf@ietf.org <br> <b><span style=3D"font-we=
ight: bold;">Sent:</span></b> Wednesday, February 1, 2012 4:33 AM<br> <b><s=
pan style=3D"font-weight: bold;">Subject:</span></b> RE: REVISED Last Call:=
 &lt;draft-ietf-oauth-v2-bearer-15.txt&gt; (The OAuth 2.0Authorization Prot=
ocol: Bearer Tokens) to Proposed Standard<br> </font> </div> <br>=0A<div id=
=3D"yiv1006253131"><style><!--=0A#yiv1006253131  =0A _filtered #yiv10062531=
31 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;}=0A _filtered #yiv1=
006253131 {font-family:SimSun;panose-1:2 1 6 0 3 1 1 1 1 1;}=0A _filtered #=
yiv1006253131 {font-family:"Cambria Math";panose-1:2 4 5 3 5 4 6 3 2 4;}=0A=
 _filtered #yiv1006253131 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 =
4;}=0A _filtered #yiv1006253131 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4=
 4 2 4;}=0A _filtered #yiv1006253131 {panose-1:2 1 6 0 3 1 1 1 1 1;}=0A#yiv=
1006253131  =0A#yiv1006253131 p.yiv1006253131MsoNormal, #yiv1006253131 li.y=
iv1006253131MsoNormal, #yiv1006253131 div.yiv1006253131MsoNormal=0A=09{marg=
in:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}=0A#yiv1=
006253131 a:link, #yiv1006253131 span.yiv1006253131MsoHyperlink=0A=09{color=
:blue;text-decoration:underline;}=0A#yiv1006253131 a:visited, #yiv100625313=
1 span.yiv1006253131MsoHyperlinkFollowed=0A=09{color:purple;text-decoration=
:underline;}=0A#yiv1006253131 p.yiv1006253131MsoListParagraph, #yiv10062531=
31 li.yiv1006253131MsoListParagraph, #yiv1006253131 div.yiv1006253131MsoLis=
tParagraph=0A=09{margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-l=
eft:36.0pt;margin-bottom:.0001pt;font-size:12.0pt;font-family:"serif";}=0A#=
yiv1006253131 span.yiv1006253131EmailStyle17=0A=09{font-family:"sans-serif"=
;color:#1F497D;}=0A#yiv1006253131 .yiv1006253131MsoChpDefault=0A=09{font-si=
ze:10.0pt;}=0A _filtered #yiv1006253131 {margin:72.0pt 72.0pt 72.0pt 72.0pt=
;}=0A#yiv1006253131 div.yiv1006253131WordSection1=0A=09{}=0A#yiv1006253131 =
 =0A _filtered #yiv1006253131 {}=0A _filtered #yiv1006253131 {font-family:S=
ymbol;}=0A#yiv1006253131 ol=0A=09{margin-bottom:0cm;}=0A#yiv1006253131 ul=
=0A=09{margin-bottom:0cm;}=0A--></style><div><div class=3D"yiv1006253131Wor=
dSection1"><div class=3D"yiv1006253131MsoNormal"><span style=3D"font-size:1=
1.0pt;font-family:&quot;sans-serif&quot;;color:#1F497D;">Hi Francisco, </sp=
an></div><div class=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.=
0pt;font-family:&quot;sans-serif&quot;;color:#1F497D;"> &nbsp;</span></div>=
<div class=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.0pt;font-=
family:&quot;sans-serif&quot;;color:#1F497D;">if a token is created for acc=
ess to server S1 and S2 then any party that gets access to the token can ob=
viously access both servers. This should not be super surprising. </span></=
div><div class=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.0pt;f=
ont-family:&quot;sans-serif&quot;;color:#1F497D;"> &nbsp;</span></div><div =
class=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.0pt;font-famil=
y:&quot;sans-serif&quot;;color:#1F497D;">So, if you have a deployment where=
 you want to grant access to resources at
 multiple servers and the attack you describe is a concern then you need to=
 create multiple tokens. </span></div><div class=3D"yiv1006253131MsoNormal"=
><span style=3D"font-size:11.0pt;font-family:&quot;sans-serif&quot;;color:#=
1F497D;"> &nbsp;</span></div><div class=3D"yiv1006253131MsoNormal"><span st=
yle=3D"font-size:11.0pt;font-family:&quot;sans-serif&quot;;color:#1F497D;">=
The content of the token defines what the token can be used for. </span></d=
iv><div class=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.0pt;fo=
nt-family:&quot;sans-serif&quot;;color:#1F497D;"> &nbsp;</span></div><div c=
lass=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.0pt;font-family=
:&quot;sans-serif&quot;;color:#1F497D;">The bearer token specification does=
 not define the content of the token and therefore it is difficult to say m=
ore about it beyond what it already says. </span></div><div class=3D"yiv100=
6253131MsoNormal"><span
 style=3D"font-size:11.0pt;font-family:&quot;sans-serif&quot;;color:#1F497D=
;"> &nbsp;</span></div><div class=3D"yiv1006253131MsoNormal"><span style=3D=
"font-size:11.0pt;font-family:&quot;sans-serif&quot;;color:#1F497D;">If you=
 think it is worth to specify highlight this type of attack then the approp=
riate place to describe it is the threats document. </span></div><div class=
=3D"yiv1006253131MsoNormal"><span style=3D"font-size:11.0pt;font-family:&qu=
ot;sans-serif&quot;;color:#1F497D;"> &nbsp;</span></div><div class=3D"yiv10=
06253131MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;sans-s=
erif&quot;;color:#1F497D;">Ciao<br>Hannes</span></div><div class=3D"yiv1006=
253131MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;sans-ser=
if&quot;;color:#1F497D;"> &nbsp;</span></div><div style=3D"border:none;bord=
er-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt;"><div><div style=3D"bor=
der:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm;"><div
 class=3D"yiv1006253131MsoNormal"><b><span style=3D"font-size:10.0pt;font-f=
amily:&quot;sans-serif&quot;;">From:</span></b><span style=3D"font-size:10.=
0pt;font-family:&quot;sans-serif&quot;;"> ietf-bounces@ietf.org [mailto:iet=
f-bounces@ietf.org] <b>On Behalf Of </b>ext Francisco Corella<br><b>Sent:</=
b> Wednesday, February 01, 2012 6:53 AM<br><b>To:</b> ietf@ietf.org<br><b>S=
ubject:</b> REVISED Last Call: &lt;draft-ietf-oauth-v2-bearer-15.txt&gt; (T=
he OAuth 2.0Authorization Protocol: Bearer Tokens) to Proposed Standard</sp=
an></div></div></div><div class=3D"yiv1006253131MsoNormal"> &nbsp;</div><di=
v><div class=3D"yiv1006253131MsoNormal" style=3D"margin-bottom:12.0pt;backg=
round:white;"><span style=3D"color:black;">The bearer token protocol descri=
bed in the document referenced in the<br>subject line is vulnerable to the =
following attack by a malicious<br>resource server.<br><br>There are two re=
source servers S1 and S2, S1 hosting a resource R1,<br>and S2 hosting a res=
ource
 R2.&nbsp; Servers are not entitled to access<br>resources that they do not=
 host.&nbsp; S1 is malicious.&nbsp; The client obtains<br>a broadly scoped =
access token that allows access to both resources.<br>The client uses the a=
ccess token to obtain resource R1 from server S1.<br>Malicious server S1 th=
en presents the access token received from the<br>client to server S2 and g=
ains access to resource R2, which it is not<br>entitled to access.<br><br>I=
ncluding the identity of the intended recipients in the token, as<br>recomm=
ended in Section 4.2, does not help, since the intended<br>recipients of th=
e broadly scoped token include both R1 and R2.<br><br>Francisco</span></div=
></div></div></div></div></div><br><br> </div> </div> </blockquote></div>  =
 </div></body></html>
--329289550-1412768873-1328128276=:30174--

From heard@pobox.com  Wed Feb  1 13:25:38 2012
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 3558511E80BE for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 13:25:38 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kn3u--KB75yC for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 13:25:37 -0800 (PST)
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9528511E809B for <ietf@ietf.org>; Wed,  1 Feb 2012 13:25:36 -0800 (PST)
Received: (qmail 18991 invoked from network); 1 Feb 2012 13:25:34 -0800
Received: from shell4.bayarea.net (209.128.82.1) by shell4.bayarea.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Feb 2012 13:25:33 -0800
Date: Wed, 1 Feb 2012 13:25:33 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-X-Sender: heard@shell4.bayarea.net
To: IETF <ietf@ietf.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <4F28432E.6090209@gmail.com>
Message-ID: <Pine.LNX.4.64.1202011324080.17956@shell4.bayarea.net>
References: <20120131174018.0032318C0DD@mercury.lcs.mit.edu> <DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp.twcable.com> <4F283D7F.2040207@qualcomm.com> <4F28432E.6090209@gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:25:38 -0000

On Wed, 1 Feb 2012, Brian E Carpenter wrote:
> On 2012-02-01 08:14, Pete Resnick wrote:
> > On 1/31/12 11:59 AM, George, Wes wrote:
> >>> From: Noel Chiappa [mailto:jnc@mercury.lcs.mit.edu]
> >>>
> >>> Is that wise? I thought (IIRC, and maybe I'm spacing) the 
> >>> whole reason for allocating this space was that 1918 space 
> >>> _couldn't_ easily be used for CGN because there were too many 
> >>> conflicting usages.
> >>>      
> >> [WEG] yes, but the general sense I got from the ensuing discussion was
> >> that no one expects anyone to actually adhere to that advice (ie MUST
> >> NOT be used as substitute for 1918 space), and as soon as the space is
> >> released, it'll be "cats and dogs living together, mass hysteria..."
> >> because everyone and their cousin will start using it as 1918-bis
> >> anyway, no matter whether the IETF wags their fingers at them or not.
> 
> I have no doubt that this space will be (mis)used as additional
> private ambiguous address space. But IMHO the text should make it
> clear that this is the wrong way to use it and give the reasons
> why - basically the same information as in the new text, but stated
> exactly the other way round. For example
> 
>      Shared Address Space is IPv4 address space designated for Service
>      Provider use with the purpose of facilitating CGN deployment.
>      Shared Address Space is not intended to be used as additional [RFC1918]
>      space, because either or both of the following issues might arise:
> 
>      o  Shared Address Space could also be used on the Service Provider side
>         of the CPE, with overlapping subnet or host addresses.
> 
>      o  Some CPE routers behave incorrectly when using the same address block on
>         both the internal and external interfaces.
> 
> > Speaking as one of the bozos^h^h^h^h^h ADs whose comments (and suggested
> > text) ended the document up here, let me suggest the slightly less
> > pessimistic view from Wes's, and the reason that I think this
> > *shouldn't* specifically update 1918:
> > 
> > This *is* a special use address block that is akin to 1918. It is
> > non-routable address space, just like 1918. But unlike 1918, this block
> > is defined as "might be used by your ISP on your outside interface". So,
> > people using it inside their networks (which, I agree with Wes, will
> > happen, and like everything else on the net, will be done stupidly by
> > some) have been told that this is *not* private use space and that they
> > use it at their own risk and their CGN service might stop working if
> > they use it in a way not described in this document. But I'd hate for us
> > to allocate space to "CGNs only" when it's obvious that this can be used
> > for a whole class of these sorts of things, and can be used by other
> > people who build sane equipment that understands "shared" addresses can
> > appear on two different interfaces. These aren't "private" addresses a
> > la 1918, they're "shared", so it's not an addition to that space. Let's
> > properly document what it is we're doing, giving people fair warnings.
> 
> Exactly, hence my suggested text above.

+1

//cmh

From presnick@qualcomm.com  Wed Feb  1 14:34:13 2012
Return-Path: <presnick@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 0177511E80FD for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 14:34:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.569
X-Spam-Level: 
X-Spam-Status: No, score=-106.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMH0fMPgy+8c for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 14:34:12 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 4C40C11E809F for <ietf@ietf.org>; Wed,  1 Feb 2012 14:34:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1328135652; x=1359671652; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F29BDC7.7060904@qualcomm.com>|Date:=20We d,=201=20Feb=202012=2016:33:43=20-0600|From:=20Pete=20Res nick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Brian=20E=20Carpenter=20<brian .e.carpenter@gmail.com>|CC:=20Noel=20Chiappa=20<jnc@mercu ry.lcs.mit.edu>,=20"ietf@ietf.org"=20<ietf@ietf.org> |Subject:=20Re:=20Last=20Call:=20<draft-weil-shared-trans ition-space-request-14.txt>=0D=0A=20(IANA=20Reserved=20IP v4=20Prefix=20for=20Shared=20Address=20Space)=20to=20BCP |References:=20<20120131174018.0032318C0DD@mercury.lcs.mi t.edu>=09<DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVP EXVS03.corp.twcable.com>=09<4F283D7F.2040207@qualcomm.com >=20<4F28432E.6090209@gmail.com>|In-Reply-To:=20<4F28432E .6090209@gmail.com>|Content-Type:=20text/plain=3B=20chars et=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=ADFLU8FCx0SgxoGM8rQmBVjABWHArHTOOoWBdBOYdDE=; b=Oxlc+pMn+BesAjDkEYSZzvi7HsKmvF02HT0uWQ8vUpL/0E20vKQr5r6I WKVS4Xg5t8uCCY+mCECV6HLIzAlME+t3JhyBv3TPZ166KdHG7hBrcvtI0 U//6qmJHF4h75RJcEEj6GBi4ws4wqSXkcnPFARlCxX5x/JSpKq67AwLkj 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6607"; a="157471165"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 01 Feb 2012 14:34:11 -0800
X-IronPort-AV: E=Sophos;i="4.71,601,1320652800"; d="scan'208";a="193379579"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 01 Feb 2012 14:34:03 -0800
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Wed, 1 Feb 2012 14:34:03 -0800
Message-ID: <4F29BDC7.7060904@qualcomm.com>
Date: Wed, 1 Feb 2012 16:33:43 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120131174018.0032318C0DD@mercury.lcs.mit.edu>	<DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp.twcable.com>	<4F283D7F.2040207@qualcomm.com> <4F28432E.6090209@gmail.com>
In-Reply-To: <4F28432E.6090209@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:34:13 -0000

On 1/31/12 1:38 PM, Brian E Carpenter wrote:
> IMHO the text should make it
> clear that this is the wrong way to use it and give the reasons
> why - basically the same information as in the new text, but stated
> exactly the other way round. For example
>
>       Shared Address Space is IPv4 address space designated for Service
>       Provider use with the purpose of facilitating CGN deployment.
>       Shared Address Space is not intended to be used as additional [RFC1918]
>       space, because either or both of the following issues might arise:
>
>       o  Shared Address Space could also be used on the Service Provider side
>          of the CPE, with overlapping subnet or host addresses.
>
>       o  Some CPE routers behave incorrectly when using the same address block on
>          both the internal and external interfaces.
>    

Ah. I think we're in pretty good agreement. The -14 text uses the words 
"may be used as [RFC1918] private address space", and I agree with you 
that we don't want to use those words. We need to say that though it is 
similar to 1918 space, it has limitations. So I wouldn't object to the 
above text , but I think we do have to give some indication of the flip 
side. I want something that says that Shared Address Space can be used 
for other Service-Provider-type uses and are not limited to CGNs. They 
can be used on any network equipment willing to do address translation 
across interfaces which both use the Shared Address Space, just as CGNs 
do. That is, clarify throughout that this *isn't* just like 1918 space 
(it has limitations and can only be used in particular circumstances), 
but do describe what the conditions are under which it can be used.

In your above, I would even strengthen "is not intended to be used as 
additional [RFC1918] space" to "can not be use as [RFC1918] private 
address space", and then maybe add something about where it can be used. 
In the intro, I would change the second paragraph (and it's sub-bullets) to:

    Shared Address Space is similar to [RFC1918] private address space in
    that it is not global routeable address space and can be used by
    multiple pieces of equipment. However, Shared Address Space has
    limitations in its use that the current [RFC1918] private address
    space does not have. In particular, Shared Address Space can only be
    used on routing equipment that is able to do address translation
    across router interfaces when the addresses are identical on two
    different interfaces.

Or something to that effect. Does that still capture that Shared Address 
Space is similar to 1918 space, it can be used for purposes other than 
CGN, but it can't be used everywhere 1918 addresses are used?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From brian.e.carpenter@gmail.com  Wed Feb  1 17:40:34 2012
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 4D43211E80F8 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 17:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.42
X-Spam-Level: 
X-Spam-Status: No, score=-103.42 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OkyIu+X1I0gl for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2012 17:40:33 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id CF25511E814A for <ietf@ietf.org>; Wed,  1 Feb 2012 17:40:32 -0800 (PST)
Received: by iagf6 with SMTP id f6so2838878iag.31 for <ietf@ietf.org>; Wed, 01 Feb 2012 17:40:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZvUUGwVQN7HDLcj3UluM4zMaQIphoWab9M1939IZMCM=; b=P8MQqEkQ9m9gCsK0V2eiJhCWRYA0gC6JcBcCKPPksFKCLXjdK5unilzLf87VAZP7XY /YwoSXl1svRzYegg0XAgYTdwGGFF+k3f1W0z8b7NU9wRwJ6EHxywdOsWfBm+GfmxRPBl c7cbmzF6WB7PkLE9vUtJo92T2z/8b0OxWSolc=
Received: by 10.42.144.69 with SMTP id a5mr743525icv.45.1328146825584; Wed, 01 Feb 2012 17:40:25 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id f8sm1617627ibl.6.2012.02.01.17.40.22 (version=SSLv3 cipher=OTHER); Wed, 01 Feb 2012 17:40:24 -0800 (PST)
Message-ID: <4F29E98E.7080703@gmail.com>
Date: Thu, 02 Feb 2012 14:40:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120131174018.0032318C0DD@mercury.lcs.mit.edu>	<DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp.twcable.com>	<4F283D7F.2040207@qualcomm.com> <4F28432E.6090209@gmail.com> <4F29BDC7.7060904@qualcomm.com>
In-Reply-To: <4F29BDC7.7060904@qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:40:34 -0000

Pete,

We seem to be agreeing violently.

Regards
   Brian Carpenter

On 2012-02-02 11:33, Pete Resnick wrote:
> On 1/31/12 1:38 PM, Brian E Carpenter wrote:
>> IMHO the text should make it
>> clear that this is the wrong way to use it and give the reasons
>> why - basically the same information as in the new text, but stated
>> exactly the other way round. For example
>>
>>       Shared Address Space is IPv4 address space designated for Service
>>       Provider use with the purpose of facilitating CGN deployment.
>>       Shared Address Space is not intended to be used as additional
>> [RFC1918]
>>       space, because either or both of the following issues might arise:
>>
>>       o  Shared Address Space could also be used on the Service
>> Provider side
>>          of the CPE, with overlapping subnet or host addresses.
>>
>>       o  Some CPE routers behave incorrectly when using the same
>> address block on
>>          both the internal and external interfaces.
>>    
> 
> Ah. I think we're in pretty good agreement. The -14 text uses the words
> "may be used as [RFC1918] private address space", and I agree with you
> that we don't want to use those words. We need to say that though it is
> similar to 1918 space, it has limitations. So I wouldn't object to the
> above text , but I think we do have to give some indication of the flip
> side. I want something that says that Shared Address Space can be used
> for other Service-Provider-type uses and are not limited to CGNs. They
> can be used on any network equipment willing to do address translation
> across interfaces which both use the Shared Address Space, just as CGNs
> do. That is, clarify throughout that this *isn't* just like 1918 space
> (it has limitations and can only be used in particular circumstances),
> but do describe what the conditions are under which it can be used.
> 
> In your above, I would even strengthen "is not intended to be used as
> additional [RFC1918] space" to "can not be use as [RFC1918] private
> address space", and then maybe add something about where it can be used.
> In the intro, I would change the second paragraph (and it's sub-bullets)
> to:
> 
>    Shared Address Space is similar to [RFC1918] private address space in
>    that it is not global routeable address space and can be used by
>    multiple pieces of equipment. However, Shared Address Space has
>    limitations in its use that the current [RFC1918] private address
>    space does not have. In particular, Shared Address Space can only be
>    used on routing equipment that is able to do address translation
>    across router interfaces when the addresses are identical on two
>    different interfaces.
> 
> Or something to that effect. Does that still capture that Shared Address
> Space is similar to 1918 space, it can be used for purposes other than
> CGN, but it can't be used everywhere 1918 addresses are used?
> 
> pr
> 

From wwwrun@ietfa.amsl.com  Wed Feb  1 18:33:14 2012
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id 09B5511E8087; Wed,  1 Feb 2012 18:33:14 -0800 (PST)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: IAB Appointments 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20120202023314.09B5511E8087@ietfa.amsl.com>
Date: Wed,  1 Feb 2012 18:33:14 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:33:14 -0000

Hi all,

The 2011-2012 IETF Nominating committee is pleased to announce
the selection of the IAB members whose two year terms start at
IETF83.

The Nomcom has selected the following persons to serve as members
of the IAB and they have been confirmed by the ISOC Board of
Trustees (in its role as the confirming body):

Bernard Aboba
Jari Arkko
Marc Blanchet
Ross Callon
Spencer Dawkins
Hannes Tschofenig

We would like to express our sincere gratitude to the incumbents
who are not returning for their outstanding service, the many
highly qualified members of the community who offered to serve,
the community for their assistance in this process, and the
individuals named above for agreeing to serve the community on
the IAB.

Suresh Krishnan
Chair, NomCom 2011-2012

From kathleen.moriarty@emc.com  Thu Feb  2 06:15:45 2012
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B4AD21F86B1; Thu,  2 Feb 2012 06:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.814
X-Spam-Level: 
X-Spam-Status: No, score=-9.814 tagged_above=-999 required=5 tests=[AWL=0.785,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zB6DWUk7PwZK; Thu,  2 Feb 2012 06:15:45 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id DFE9721F86A7; Thu,  2 Feb 2012 06:15:44 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q12EFRI2009415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Feb 2012 09:15:41 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 2 Feb 2012 09:15:16 -0500
Received: from mxhub21.corp.emc.com (mxhub21.corp.emc.com [128.222.70.133]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q12EFFj8017899; Thu, 2 Feb 2012 09:15:15 -0500
Received: from mx06a.corp.emc.com ([169.254.1.153]) by mxhub21.corp.emc.com ([128.222.70.133]) with mapi; Thu, 2 Feb 2012 09:15:15 -0500
From: <kathleen.moriarty@emc.com>
To: <draft-kucherawy-authres-spf-erratum.all@tools.ietf.org>, <ietf@ietf.org>,  <gen-art@ietf.org>
Date: Thu, 2 Feb 2012 09:15:11 -0500
Subject: Gen-ART review for draft-kucherawy-authres-spf-erratum-01
Thread-Topic: Gen-ART review for draft-kucherawy-authres-spf-erratum-01
Thread-Index: AczhtRLJBvVGVkBJS/qwO9eQTEqwFQ==
Message-ID: <AE31510960917D478171C79369B660FA0E2C119FCA@MX06A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 02 Feb 2012 08:23:10 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:15:45 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-kucherawy-authres-spf-erratum-01
Reviewer: Kathleen Moriarty
Review Date: 2012-02-02
IETF LC End Date: 2012-02-03
IESG Telechat date: (if known)

Summary:  This draft is ready for publication.
   This memo updates the registry of authentication method results in
   Authentication-Results: message header fields, correcting a
   discontinuity between the original registry creation and the SPF
   specification.


Major issues:

Minor issues:

Nits/editorial comments:
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org<mailto:Gen-art@ietf.org>
https://www.ietf.org/mailman/listinfo/gen-art




From alan.b.johnston@gmail.com  Thu Feb  2 13:55:05 2012
Return-Path: <alan.b.johnston@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 C2A5E21F860B for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 13:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.426
X-Spam-Level: 
X-Spam-Status: No, score=-102.426 tagged_above=-999 required=5 tests=[AWL=-1.427, BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqviNs-Qq6Zg for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 13:55:05 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD3221F8530 for <ietf@ietf.org>; Thu,  2 Feb 2012 13:55:04 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so4070925obb.31 for <ietf@ietf.org>; Thu, 02 Feb 2012 13:55:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=rA4n+KjDPDwgj7AdYTvxIOb0R+wyfdy8AeLl8g9BPHc=; b=gAN0SVnj5ADsNKsfdwCpmo2Va0xSu3cWHuv8fQ0PfOBEyPUk+56T0xEo5Qq71jVODk SVxkdJLt0Q+b0KSagxXoRh9E4aIdL47EEnWSoBn0mpLHcYbsbrkyY3tGp8GLtZZ32mLc 8hUu6OaYuKv2p0JLhqfO4PuzGcBJMmIl/OUbw=
MIME-Version: 1.0
Received: by 10.182.59.41 with SMTP id w9mr4092870obq.70.1328219704716; Thu, 02 Feb 2012 13:55:04 -0800 (PST)
Received: by 10.182.75.136 with HTTP; Thu, 2 Feb 2012 13:55:04 -0800 (PST)
Date: Thu, 2 Feb 2012 15:55:04 -0600
Message-ID: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
Subject: Yet Another Reason?
From: Alan Johnston <alan.b.johnston@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:55:05 -0000

Is this yet another reason not to have IETF meetings in the USA? ;-)

     http://yro.slashdot.org/story/12/02/02/1719221/do-you-like-online-privacy-you-may-be-a-terrorist

The FBI and their would-be tipsters could be flat out trying
investigate everyone who uses encryption, anonymizer and privacy tools
on the Internet, or changes SIM cards in their mobile phone!  At least
"wearing T-shirts with inscrutable slogans" isn't on the list yet or
we'd all be rounded up...

Seriously - who writes this stuff?

- Alan -

From cgrundemann@gmail.com  Thu Feb  2 15:05:58 2012
Return-Path: <cgrundemann@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 4F4D121F85C9 for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 15:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GU3zOsW48vm3 for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 15:05:57 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9F221F85C2 for <ietf@ietf.org>; Thu,  2 Feb 2012 15:05:57 -0800 (PST)
Received: by dakl33 with SMTP id l33so2735040dak.31 for <ietf@ietf.org>; Thu, 02 Feb 2012 15:05:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=cP99qI0ySUOegysKT5vyjuDKji28QtsU9lw9AdDdPnw=; b=rBAI5upvzotLtMLKpJingZPZlMB/QfSjo7bm18k2bLFJq4EL0dL2AaKt3E5VyVWAUC xdXpv2GETQmlfhucyNGfULWMsBRGiYyD2QuogJJ0Lm/YvsEBy5sku+W1L7CD6LhoW0xq Tiv69mTIVDr/7snixURWkX7UHpXbgpNhSvm4s=
MIME-Version: 1.0
Received: by 10.68.74.72 with SMTP id r8mr11743554pbv.8.1328223957236; Thu, 02 Feb 2012 15:05:57 -0800 (PST)
Received: by 10.143.60.13 with HTTP; Thu, 2 Feb 2012 15:05:57 -0800 (PST)
In-Reply-To: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
References: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
Date: Thu, 2 Feb 2012 16:05:57 -0700
Message-ID: <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
Subject: Re: Yet Another Reason?
From: Chris Grundemann <cgrundemann@gmail.com>
To: Alan Johnston <alan.b.johnston@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:05:58 -0000

Hides the screen, nervous, pays cash... Sounds to me like anyone
surfing pr0n at the "Internet Cafe" is now a suspected terrorist.


On Thu, Feb 2, 2012 at 14:55, Alan Johnston <alan.b.johnston@gmail.com> wro=
te:
> Is this yet another reason not to have IETF meetings in the USA? ;-)
>
> =A0 =A0 http://yro.slashdot.org/story/12/02/02/1719221/do-you-like-online=
-privacy-you-may-be-a-terrorist
>
> The FBI and their would-be tipsters could be flat out trying
> investigate everyone who uses encryption, anonymizer and privacy tools
> on the Internet, or changes SIM cards in their mobile phone! =A0At least
> "wearing T-shirts with inscrutable slogans" isn't on the list yet or
> we'd all be rounded up...
>
> Seriously - who writes this stuff?
>
> - Alan -
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



--=20
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.theIPv6experts.net
www.coisoc.org

From nick@inex.ie  Thu Feb  2 15:39:12 2012
Return-Path: <nick@inex.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 490A921F86B3 for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 15:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wm31UNQItmQv for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 15:39:11 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 9F9E121F86A3 for <ietf@ietf.org>; Thu,  2 Feb 2012 15:39:10 -0800 (PST)
X-Envelope-To: <ietf@ietf.org>
Received: from crumpet.foobar.org ([IPv6:2001:4d68:2002:100:2841:5444:ab2a:358b]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q12Ne3wU023151 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 2 Feb 2012 23:40:09 GMT (envelope-from nick@inex.ie)
Message-ID: <4F2B1E95.2090503@inex.ie>
Date: Thu, 02 Feb 2012 23:39:01 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Yet Another Reason?
References: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com> <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
In-Reply-To: <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
X-Enigmail-Version: 1.3.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:39:12 -0000

On 02/02/2012 23:05, Chris Grundemann wrote:
> Hides the screen, nervous, pays cash... Sounds to me like anyone
> surfing pr0n at the "Internet Cafe" is now a suspected terrorist.

"If you have nothing to hide, you have nothing to fear"

(Apologies to Daniel Solove who has written extensively about this
particular asinism).

Nick

From dotis@mail-abuse.org  Thu Feb  2 17:25:03 2012
Return-Path: <dotis@mail-abuse.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 E71C621F8498 for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 17:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.456
X-Spam-Level: 
X-Spam-Status: No, score=-101.456 tagged_above=-999 required=5 tests=[AWL=-0.660, BAYES_00=-2.599, LONGWORDS=1.803, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id otVq3xgsy76z for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 17:25:03 -0800 (PST)
Received: from mailserv.mail-abuse.org (mailserv.mail-abuse.org [150.70.98.118]) by ietfa.amsl.com (Postfix) with ESMTP id 5FAB821F8487 for <ietf@ietf.org>; Thu,  2 Feb 2012 17:25:03 -0800 (PST)
Received: from US-DOUGO-MAC.local (SJDCLUXGATEWAY2.sdi.trendnet.org [10.31.37.9]) by mailserv.mail-abuse.org (Postfix) with ESMTPSA id 4FA3617402DE for <ietf@ietf.org>; Fri,  3 Feb 2012 01:25:03 +0000 (UTC)
Message-ID: <4F2B376E.30605@mail-abuse.org>
Date: Thu, 02 Feb 2012 17:25:02 -0800
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Yet Another Reason?
References: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
In-Reply-To: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:25:04 -0000

On 2/2/12 1:55 PM, Alan Johnston wrote:
> Is this yet another reason not to have IETF meetings in the USA? ;-)
>
>       http://yro.slashdot.org/story/12/02/02/1719221/do-you-like-online-privacy-you-may-be-a-terrorist
>
> The FBI and their would-be tipsters could be flat out trying
> investigate everyone who uses encryption, anonymizer and privacy tools
> on the Internet, or changes SIM cards in their mobile phone!  At least
> "wearing T-shirts with inscrutable slogans" isn't on the list yet or
> we'd all be rounded up...
>
> Seriously - who writes this stuff?
Dear Alan,

I can't help but imagine Jeff Foxworthy saying:

"You might be a redneck if you think someone--
   concerned about privacy
   signing on to Comcast or AOL
   paying using cash
   changing their SIM card
   concealing data in photos (is there an app for that?)
   purchasing chemicals
   reading equipment manuals
   reading revolutionary literature
   writing program code
   watching attack coverage
   looking at stadium seating maps
--might be a terrorist.

Call (888) 705-JRIC and mention "redneck". :^)

Regards,
Douglas Otis

From narten@us.ibm.com  Thu Feb  2 21:53:37 2012
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 B730721F864E for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 21:53:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.074
X-Spam-Level: 
X-Spam-Status: No, score=-109.074 tagged_above=-999 required=5 tests=[AWL=1.525, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8Ql4WngCGNC for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 21:53:37 -0800 (PST)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 0D82F21F864F for <ietf@ietf.org>; Thu,  2 Feb 2012 21:53:10 -0800 (PST)
Received: from /spool/local by e34.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, 2 Feb 2012 22:53:10 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 2 Feb 2012 22:53:07 -0700
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id C782019D8026 for <ietf@ietf.org>; Thu,  2 Feb 2012 22:53:03 -0700 (MST)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q135r4UG129000 for <ietf@ietf.org>; Thu, 2 Feb 2012 22:53:04 -0700
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q135r3oa025790 for <ietf@ietf.org>; Thu, 2 Feb 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q135r3r9025757 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 2 Feb 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q135r2Lj008067 for <ietf@ietf.org>; Fri, 3 Feb 2012 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q135r2iJ008043 for ietf@ietf.org; Fri, 3 Feb 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201202030553.q135r2iJ008043@rotala.raleigh.ibm.com>
Date: Fri, 03 Feb 2012 00:53:02 -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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12020305-1780-0000-0000-000002D5D4C9
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000245; HX=3.00000181; KW=3.00000007; PH=3.00000001; SC=3.00000001; SDB=6.00110473; UDB=6.00027450; UTC=2012-02-03 05:53:08
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 05:53:37 -0000

Total of 72 messages in the last 7 days.
 
script run at: Fri Feb  3 00:53:01 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.33% |    6 |  7.73% |    51134 | tglassey@earthlink.net
  4.17% |    3 |  7.23% |    47849 | fcorella@pomcor.com
  4.17% |    3 |  6.71% |    44414 | michael.jones@microsoft.com
  4.17% |    3 |  5.68% |    37585 | alexey.melnikov@isode.com
  4.17% |    3 |  5.25% |    34752 | bernard_aboba@hotmail.com
  4.17% |    3 |  5.04% |    33318 | stefan.winter@restena.lu
  4.17% |    3 |  3.56% |    23558 | brian.e.carpenter@gmail.com
  4.17% |    3 |  2.97% |    19649 | sm@resistor.net
  4.17% |    3 |  2.02% |    13357 | nomcom-chair@ietf.org
  2.78% |    2 |  3.16% |    20872 | mnot@mnot.net
  2.78% |    2 |  2.87% |    18961 | presnick@qualcomm.com
  2.78% |    2 |  2.75% |    18182 | shanna@juniper.net
  2.78% |    2 |  2.52% |    16649 | wesley.george@twcable.com
  2.78% |    2 |  2.18% |    14444 | cgrundemann@gmail.com
  2.78% |    2 |  1.99% |    13156 | julian.reschke@gmx.de
  1.39% |    1 |  3.25% |    21465 | sra@hactrn.net
  1.39% |    1 |  3.20% |    21185 | terry.manderson@icann.org
  2.78% |    2 |  1.76% |    11672 | hartmans@painless-security.com
  2.78% |    2 |  1.52% |    10056 | jnc@mercury.lcs.mit.edu
  1.39% |    1 |  2.76% |    18280 | danielmaiax@gmail.com
  1.39% |    1 |  2.33% |    15395 | hannes.tschofenig@nsn.com
  1.39% |    1 |  1.92% |    12721 | ron.even.tlv@gmail.com
  1.39% |    1 |  1.48% |     9789 | narten@us.ibm.com
  1.39% |    1 |  1.43% |     9469 | daedulus@btconnect.com
  1.39% |    1 |  1.33% |     8802 | vinayakh@gmail.com
  1.39% |    1 |  1.25% |     8296 | lberger@labn.net
  1.39% |    1 |  1.20% |     7928 | heard@pobox.com
  1.39% |    1 |  1.15% |     7580 | william.polk@nist.gov
  1.39% |    1 |  1.14% |     7533 | randy@qualcomm.com
  1.39% |    1 |  1.10% |     7244 | olaf@nlnetlabs.nl
  1.39% |    1 |  1.03% |     6789 | scott.brim@gmail.com
  1.39% |    1 |  1.01% |     6699 | jean-francois.tremblaying@videotron.com
  1.39% |    1 |  0.94% |     6248 | kathleen.moriarty@emc.com
  1.39% |    1 |  0.93% |     6135 | ogud@ogud.com
  1.39% |    1 |  0.92% |     6073 | marshall.eubanks@gmail.com
  1.39% |    1 |  0.88% |     5835 | dotis@mail-abuse.org
  1.39% |    1 |  0.88% |     5820 | arnt@gulbrandsen.priv.no
  1.39% |    1 |  0.87% |     5764 | dhc@dcrocker.net
  1.39% |    1 |  0.87% |     5761 | chair@ietf.org
  1.39% |    1 |  0.84% |     5581 | nick@inex.ie
  1.39% |    1 |  0.83% |     5471 | alan.b.johnston@gmail.com
  1.39% |    1 |  0.78% |     5192 | jinesh.doshi@colorado.edu
  1.39% |    1 |  0.72% |     4793 | francis.dupont@fdupont.fr
--------+------+--------+----------+------------------------
100.00% |   72 |100.00% |   661456 | Total


From alexey.melnikov@isode.com  Fri Feb  3 05:14:21 2012
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 46D5A21F8625; Fri,  3 Feb 2012 05:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.099
X-Spam-Level: 
X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1wLe8FBT9DWy; Fri,  3 Feb 2012 05:14:20 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6E70E21F856D; Fri,  3 Feb 2012 05:14:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1328274857; d=isode.com; s=selector; i=@isode.com; bh=p040+9qOAPW1BYfPD5JvCq4sWOPy7yNFjhEkpCArW6Q=; 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=Jhds+fq1zgVGtDOykvZX7ojd9Hz51G15ZXla6PpoaXs456uWdvdo/OTl77qxMOrZs/9toH hgo90Dzu26awl06pNURGGIR6C9/wBf1FqRoSGLwSZva5O97JqsEsHTXBpjEYnFe+5FY6zL +izWzbQRGOcjxPG5h1xJy+tsM+jxuTg=;
Received: from [144.254.105.99] (dhcp-guest-bru-peg1-144-254-105-99.cisco.com [144.254.105.99])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <TyvdpwAvKKUJ@rufus.isode.com>; Fri, 3 Feb 2012 13:14:17 +0000
Message-ID: <4F2BDDB1.8030709@isode.com>
Date: Fri, 03 Feb 2012 13:14:25 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Mike Jones <Michael.Jones@microsoft.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [OAUTH-WG] Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com>
In-Reply-To: <4F27C37C.1090008@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: General Area Review Team <gen-art@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:14:21 -0000

On 31/01/2012 10:33, Alexey Melnikov wrote:
> On 30/01/2012 05:20, Mike Jones wrote:
  [...]
>> About your third minor issue on RFC 6125 versus RFC 2818, you'll find 
>> that, per the history entries, a previous reference to RFC 2818 was 
>> changed to RFC 6125 in draft 14 at the request of Security Area 
>> Director Stephen Farrell.
I've quickly chatted with Stephen and he said that he only asked the 
question and didn't necessarily instructed the WG to do the change from 
RFC 2818 to RFC 6125. Keeping this in mind...
>> If you'd like to see this reference reintroduced, I'd request that 
>> you work with Stephen on specific alternative proposed wording that 
>> is acceptable to both of you.
>  Ok, I can work with Stephen and Peter Saint-Andre (RFC 6125 
> co-author) on some text.

So, here are the proposed changes:

4.2.  Threat Mitigation

      To protect against token disclosure, confidentiality protection MUST
      be applied using TLS [RFC5246] with a ciphersuite that provides
      confidentiality and integrity protection.  This requires that the
      communication interaction between the client and the authorization
      server, as well as the interaction between the client and the
      resource server, utilize confidentiality and integrity protection.
      Since TLS is mandatory to implement and to use with this
      specification, it is the preferred approach for preventing token
      disclosure via the communication channel.  For those cases where the
      client is prevented from observing the contents of the token, token
      encryption MUST be applied in addition to the usage of TLS
      protection.  As a further defense against token disclosure, the
      client MUST validate the TLS certificate chain when making requests
      to protected resources.

I suggest inserting "[RFC5280]" at the end of the last sentence above.

      To deal with token capture and replay, the following recommendations
      are made: First, the lifetime of the token MUST be limited; one means
      of achieving this is by putting a validity time field inside the
      protected part of the token.  Note that using short-lived (one hour
      or less) tokens reduces the impact of them being leaked.  Second,
      confidentiality protection of the exchanges between the client and
      the authorization server and between the client and the resource
      server MUST be applied.  As a consequence, no eavesdropper along the
      communication path is able to observe the token exchange.
      Consequently, such an on-path adversary cannot replay the token.
      Furthermore, when presenting the token to a resource server, the
      client MUST verify the identity of that resource server, as per
      Representation and Verification of Domain-Based Application Service
      Identity within Internet Public Key Infrastructure Using X.509 (PKIX)
      Certificates in the Context of Transport Layer Security (TLS)
      [RFC6125].

Please replace the last sentence quoted above with:

      Furthermore, when presenting the token to a resource server, the
      client MUST verify the identity of that resource server, as per
      section 3.1 of [RFC2818].

[Expanded motivation for the change:
I think the reference to RFC 6125 needs to be replaced with the 
reference to section 3.1 of RFC 2818. Firstly, the procedure described 
in RFC 6125 differs slightly from RFC 2818 (matching of IP addresses is 
allowed, wildcards can be used with partial hostnames (e.g. foo* is 
allowed, where RFC 6125 doesn't allow for that). Secondly, if RFC 6125 
is referenced, then the OAuth document needs to say whether 
SRV-ID/URI-IDs are allowed and whether wildcards are allowed.]


From stephen.farrell@cs.tcd.ie  Fri Feb  3 05:17:54 2012
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 53A7721F856A; Fri,  3 Feb 2012 05:17:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hE7aKXORzqe0; Fri,  3 Feb 2012 05:17:53 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 1A12D21F8559; Fri,  3 Feb 2012 05:17:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id DD507171C25; Fri,  3 Feb 2012 13:17:51 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1328275071; bh=rCgo3aUfHyU0P3 j7PcJYxpIPsDcKFJXdpbM26as6Ppw=; b=YJIRE6iyfjwsolXos24jUKGEwv6qRf mVO2dOuqU/1OXTPfZviMP1OxLA7bxFdJLzfLOqh7qKmjawKuSSZfHcwPZABidHnh 6RYTi88X0vHVflGodBqSdZndrK+o2EtAbjGuuV7QNzoS0RwxTuLX8ADFo0/3Ns4B EhMbXl7w3/WamgqGdjH9NqiBxEXPVRniemdh2l3WUv7DztunB23bHp2JPFBBLFZh YajHxpspA5oxVvigPinKf6vqgBlEBCEapMOnNhHzzFUNa/a9pRWtVRzu8AMSeHX5 ffg5kMJhwf6A/QRgMZ+T33J9z/MVfZUMGu14BwerXhH/6/wP85N/QgcQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id 6BKpEOxwmkm1; Fri,  3 Feb 2012 13:17:51 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id C3537171C06; Fri,  3 Feb 2012 13:17:50 +0000 (GMT)
Message-ID: <4F2BDE75.4080405@cs.tcd.ie>
Date: Fri, 03 Feb 2012 13:17:41 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: [OAUTH-WG] Gen-ART review of draft-ietf-oauth-v2-bearer-15.txt
References: <4F2575CE.9040001@isode.com> <4E1F6AAD24975D4BA5B16804296739436638B7AD@TK5EX14MBXC284.redmond.corp.microsoft.com> <4F27C37C.1090008@isode.com> <4F2BDDB1.8030709@isode.com>
In-Reply-To: <4F2BDDB1.8030709@isode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion Discussion <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-oauth-v2-bearer.all@tools.ietf.org" <draft-ietf-oauth-v2-bearer.all@tools.ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:17:54 -0000

That looks fine to me fwiw,
Thanks,
S.

On 02/03/2012 01:14 PM, Alexey Melnikov wrote:
> On 31/01/2012 10:33, Alexey Melnikov wrote:
>> On 30/01/2012 05:20, Mike Jones wrote:
> [...]
>>> About your third minor issue on RFC 6125 versus RFC 2818, you'll find
>>> that, per the history entries, a previous reference to RFC 2818 was
>>> changed to RFC 6125 in draft 14 at the request of Security Area
>>> Director Stephen Farrell.
> I've quickly chatted with Stephen and he said that he only asked the
> question and didn't necessarily instructed the WG to do the change from
> RFC 2818 to RFC 6125. Keeping this in mind...
>>> If you'd like to see this reference reintroduced, I'd request that
>>> you work with Stephen on specific alternative proposed wording that
>>> is acceptable to both of you.
>> Ok, I can work with Stephen and Peter Saint-Andre (RFC 6125 co-author)
>> on some text.
>
> So, here are the proposed changes:
>
> 4.2. Threat Mitigation
>
> To protect against token disclosure, confidentiality protection MUST
> be applied using TLS [RFC5246] with a ciphersuite that provides
> confidentiality and integrity protection. This requires that the
> communication interaction between the client and the authorization
> server, as well as the interaction between the client and the
> resource server, utilize confidentiality and integrity protection.
> Since TLS is mandatory to implement and to use with this
> specification, it is the preferred approach for preventing token
> disclosure via the communication channel. For those cases where the
> client is prevented from observing the contents of the token, token
> encryption MUST be applied in addition to the usage of TLS
> protection. As a further defense against token disclosure, the
> client MUST validate the TLS certificate chain when making requests
> to protected resources.
>
> I suggest inserting "[RFC5280]" at the end of the last sentence above.
>
> To deal with token capture and replay, the following recommendations
> are made: First, the lifetime of the token MUST be limited; one means
> of achieving this is by putting a validity time field inside the
> protected part of the token. Note that using short-lived (one hour
> or less) tokens reduces the impact of them being leaked. Second,
> confidentiality protection of the exchanges between the client and
> the authorization server and between the client and the resource
> server MUST be applied. As a consequence, no eavesdropper along the
> communication path is able to observe the token exchange.
> Consequently, such an on-path adversary cannot replay the token.
> Furthermore, when presenting the token to a resource server, the
> client MUST verify the identity of that resource server, as per
> Representation and Verification of Domain-Based Application Service
> Identity within Internet Public Key Infrastructure Using X.509 (PKIX)
> Certificates in the Context of Transport Layer Security (TLS)
> [RFC6125].
>
> Please replace the last sentence quoted above with:
>
> Furthermore, when presenting the token to a resource server, the
> client MUST verify the identity of that resource server, as per
> section 3.1 of [RFC2818].
>
> [Expanded motivation for the change:
> I think the reference to RFC 6125 needs to be replaced with the
> reference to section 3.1 of RFC 2818. Firstly, the procedure described
> in RFC 6125 differs slightly from RFC 2818 (matching of IP addresses is
> allowed, wildcards can be used with partial hostnames (e.g. foo* is
> allowed, where RFC 6125 doesn't allow for that). Secondly, if RFC 6125
> is referenced, then the OAuth document needs to say whether
> SRV-ID/URI-IDs are allowed and whether wildcards are allowed.]
>
>

From dworley@avaya.com  Fri Feb  3 07:23:37 2012
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2D4621F8552 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2012 07:23:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.446
X-Spam-Level: 
X-Spam-Status: No, score=-102.446 tagged_above=-999 required=5 tests=[AWL=-0.706, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aLQypNvLPHva for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2012 07:23:37 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3273521F8540 for <ietf@ietf.org>; Fri,  3 Feb 2012 07:23:36 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUFAL36K0+HCzI1/2dsb2JhbABDoneMJ4EFgXIBAQEBAgESKD8FCwIBCA0BCh4QIRElAQEEAQ0FCBqHWpxOnA2ID4NHCgkRBQIxAgEFBQYIAwGDEoETH4JWYwSIRJJdhQ+Hbg
X-IronPort-AV: E=Sophos;i="4.73,352,1325480400"; d="scan'208";a="328121545"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 03 Feb 2012 10:23:35 -0500
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Feb 2012 10:09:36 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 3 Feb 2012 10:23:35 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Chris Grundemann <cgrundemann@gmail.com>, Alan Johnston <alan.b.johnston@gmail.com>
Date: Fri, 3 Feb 2012 10:19:34 -0500
Subject: RE: Yet Another Reason?
Thread-Topic: Yet Another Reason?
Thread-Index: Aczh/0OKM6hwqxqgRLm/Zp0P8+ce4QAh/h9q
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B226F573BF8@DC-US1MBEX4.global.avaya.com>
References: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>, <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
In-Reply-To: <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:23:37 -0000

On Thu, Feb 2, 2012 at 14:55, Alan Johnston <alan.b.johnston@gmail.com> wro=
te:
>
> The FBI and their would-be tipsters could be flat out trying
> investigate everyone who [...]

... including "uses a VPN" -- which is ubiquitous among business travelers.

> Seriously - who writes this stuff?

I'd guess it's people who:

1) don't particularly care about citizens' privacy,
2) are tasked with finding people who are very hard to find, and
3) have a nearly unlimited budget for following up on a enormous
   number of leads with a high proportion of false positives

Which matches what I've read about the "homeland security"
bureaucracies of the US government.

Dale

From ek@google.com  Thu Feb  2 18:57:26 2012
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 7694721F8566 for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 18:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuU30QVZL9-G for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 18:57:26 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id EF3D321F855E for <ietf@ietf.org>; Thu,  2 Feb 2012 18:57:25 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so4428898obb.31 for <ietf@ietf.org>; Thu, 02 Feb 2012 18:57:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:x-system-of-record:content-type:content-transfer-encoding; bh=0asXAR0YJ9bNbQ7IYFFtRqiP3MiXdCmmQNZAbeXhRp0=; b=f2zluPHpfYblmRcgNJPkXJCJeBgwERaKHAzW+72SLtg5lWXi2OGf6bs0Kudl79uz77 hsaPlmHPXBUcl1HKx8Z5OpPopDNAzX0lTRyGK9VQxZywQ5I1RTUZtOfiCAYr8M7mp1K0 DcohRfcvD80NpbmQjwFk2io1+rDQRRqK3jFUg=
Received: by 10.182.75.65 with SMTP id a1mr4949920obw.32.1328237845530; Thu, 02 Feb 2012 18:57:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.75.65 with SMTP id a1mr4949861obw.32.1328237844017; Thu, 02 Feb 2012 18:57:24 -0800 (PST)
Received: by 10.182.97.4 with HTTP; Thu, 2 Feb 2012 18:57:23 -0800 (PST)
In-Reply-To: <20120201150911.25955.80172.idtracker@ietfa.amsl.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com>
Date: Fri, 3 Feb 2012 11:57:23 +0900
Message-ID: <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
From: Erik Kline <ek@google.com>
To: ietf@ietf.org
X-System-Of-Record: true
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 03 Feb 2012 08:16:04 -0800
Cc: v6ops@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:57:26 -0000

World IPv6 Launch changes the relevance of this document greatly, I
think.  Since this would be published after the announcement of World
IPv6 Launch, I think the document should be updated to discuss its own
applicability in a post- World IPv6 Launch Internet.

On 2 February 2012 00:09, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Considerations for Transitioning Content to IPv6'
> =C2=A0<draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> as an
> 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 2012-02-15. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
> =C2=A0 This document describes considerations for the transition of end u=
ser
> =C2=A0 content on the Internet to IPv6. =C2=A0While this is tailored to a=
ddress
> =C2=A0 end user content, which is typically web-based, many aspects of th=
is
> =C2=A0 document may be more broadly applicable to the transition to IPv6 =
of
> =C2=A0 other applications and services. =C2=A0This document explores the
> =C2=A0 challenges involved in the transition to IPv6, potential migration
> =C2=A0 tactics, possible migration phases, and other considerations. =C2=
=A0The
> =C2=A0 audience for this document is the Internet community generally,
> =C2=A0 particularly IPv6 implementers.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-imp=
lications/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-imp=
lications/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From fgont@si6networks.com  Thu Feb  2 20:16:06 2012
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 9532921F85D6 for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 20:16:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.863
X-Spam-Level: 
X-Spam-Status: No, score=-1.863 tagged_above=-999 required=5 tests=[AWL=0.736,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9e-J+BxwLVb for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2012 20:16:05 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id A338A21F865D for <ietf@ietf.org>; Thu,  2 Feb 2012 20:16:05 -0800 (PST)
Received: from [190.48.224.59] (helo=[10.42.43.100]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1RtAZ5-0004cM-F9; Fri, 03 Feb 2012 05:16:01 +0100
Message-ID: <4F2B5F75.9060103@si6networks.com>
Date: Fri, 03 Feb 2012 01:15:49 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16
MIME-Version: 1.0
To: Alan Johnston <alan.b.johnston@gmail.com>
Subject: Re: Yet Another Reason?
References: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
In-Reply-To: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 03 Feb 2012 08:16:16 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:16:06 -0000

On 02/02/2012 06:55 PM, Alan Johnston wrote:
> Is this yet another reason not to have IETF meetings in the USA? ;-)
> 
>      http://yro.slashdot.org/story/12/02/02/1719221/do-you-like-online-privacy-you-may-be-a-terrorist
> 
> The FBI and their would-be tipsters could be flat out trying
> investigate everyone who uses encryption, anonymizer and privacy tools
> on the Internet, or changes SIM cards in their mobile phone!  At least
> "wearing T-shirts with inscrutable slogans" isn't on the list yet or
> we'd all be rounded up...

You may also want to check this:
<http://www.schneier.com/blog/archives/2012/01/british_tourist.html>

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




From jeff_downs@partech.com  Thu Feb  2 10:58:38 2012
Return-Path: <jeff_downs@partech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E598F21F8534; Thu,  2 Feb 2012 10:58:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VtyJOYHlMvYs; Thu,  2 Feb 2012 10:58:38 -0800 (PST)
Received: from imail2.partech.com (imail2b.partech.com [192.133.62.26]) by ietfa.amsl.com (Postfix) with ESMTP id D97A121F8508; Thu,  2 Feb 2012 10:58:31 -0800 (PST)
Received: from eclipse.partech.com (eclipse.partech.com [172.16.8.4]) by imail2.partech.com (8.13.1/8.12.11) with ESMTP id q12IwJkN024248; Thu, 2 Feb 2012 13:58:19 -0500
Received: from beasley.parcorp.local (beasley.partech.com [172.16.16.70]) by eclipse.partech.com (8.12.9/8.12.9) with ESMTP id q12IwAbs025706; Thu, 2 Feb 2012 13:58:18 -0500 (EST)
Received: from [192.168.167.155] ([192.168.167.155]) by beasley.parcorp.local with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 2 Feb 2012 13:56:56 -0500
Message-ID: <4F2ADC65.2010700@partech.com>
Date: Thu, 02 Feb 2012 13:56:37 -0500
From: Jeff Downs <jeff_downs@partech.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: Gen-ART review of draft-ietf-payload-rtp-klv-02
References: <84A8BD83-8B84-4049-B9CF-1AB0E36211F9@bbn.com>
In-Reply-To: <84A8BD83-8B84-4049-B9CF-1AB0E36211F9@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Feb 2012 18:56:58.0356 (UTC) FILETIME=[70828B40:01CCE1DC]
X-Mailman-Approved-At: Fri, 03 Feb 2012 08:16:26 -0800
Cc: jimsgti@gmail.com, General Area Review Team <gen-art@ietf.org>, abegen@cisco.com, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:58:39 -0000

Richard and all:

I am one of the co-authors of the above named draft.  Thank you for the 
review and comments on the draft.

After discussion with the document shepherd and the WG co-chair, we 
decided to incorporate some of the suggested changes into a new revision 
(-03) of the draft.  This new revision was uploaded to the IETF 
datatracker yesterday and is available now:
http://tools.ietf.org/html/draft-ietf-payload-rtp-klv-03

Please see below for specifics on how each of the Gen-ART comments were 
addressed.

Again, thank you for the review and comments.

Jeff Downs
PAR Government Systems



On 1/26/2012 4:11 PM, Richard L. Barnes wrote:
 > ===== MINOR =====
 >
 > Section 6.1.: Given that the KLV format can carry a variety of data
 > types, would it be helpful for this type to have one or more
 > parameters to describe what types of KLVs might be in the stream?

The widely varied nature and use cases of this format do not lend very 
well to specific parametrization describing the data. KLV, by its very 
nature, is self-identifying through the use of universally unique keys.
No changes were made to the draft in this regard.

 > Section 8, "appropriate caution and security practices": It could be
 > helpful to note here that it is dangerous for implementations to
 > accept active content from streams that lack authenticity or
 > integrity protection, since this could make them vulnerable to
 > attacks using spoofed packets.

Text has been added to draft revision -03 in Section 8 to describe this 
scenario and to caution implementers.


 > ===== EDITORIAL =====
 >
 > Section 4: It would be helpful to note a little more explicitly that
 > a KLVunit is a sequence of KLVs, without any overall framing (thus
 > the requirement for the marker bit / timestamp to distinguish).

Text has been added to the preface of Section 4 to further clarify this 
in draft revision -03.

 > Section 4.2., last paragraph: It would be helpful to note explicitly
 > what this paragraph implies: A receiver MUST consider a KLV unit to
 > be completed when it receives either a packet with m=1 or a packet
 > with a new timestamp.  In the former case, the packet payload is
 > included in the KLVunit; in the latter case, it is not.

The suggested text has been added to draft revision -03 at the end of 
Section 4.2.

 > Section 4.3.1.1., "are left to each implementation": It could be
 > helpful to point to some ways that KLV recovery is done, as guidance
 > to implementors. (Provided this can be done without IPR concerns.)

In the interest of keeping the draft simple and focused on carriage 
within RTP specifically, I have not added guidance on KLV recovery 
techniques.  Techniques for this are not inherently unique to the 
carriage of KLV data over RTP (that is, such techniques can be applied 
to any KLV data where known damage/loss has occurred), and thus we feel 
this is outside the scope of this document.

 > Section 8, "The main security considerations ... alternatives may
 > exist": This chunk of text doesn't really add anything beyond the
 > normal security considerations for RTP.  Suggest just adding an
 > appropriate reference to standard RTP security practices.

This text comes directly from the template data in 
http://tools.ietf.org/id/draft-ietf-payload-rtp-howto-01.txt
To keep the reviewed draft in line with the template, no edits have been 
made here relevant to this comment.

 > Section 8, "Receivers are encouraged to place limits...": Suggest
 > changing "are encouraged to" to "SHOULD".

This change has been incorporated into revision -03 of the draft.

From Tina.Tsou.Zouting@huawei.com  Thu Feb  2 20:56:36 2012
Return-Path: <Tina.Tsou.Zouting@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 9302D21F85E7; Thu,  2 Feb 2012 20:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.432
X-Spam-Level: 
X-Spam-Status: No, score=-4.432 tagged_above=-999 required=5 tests=[AWL=-1.974, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MANGLED_PERFRM=2.3, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fH8-K8LhqR8g; Thu,  2 Feb 2012 20:56:35 -0800 (PST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 1033021F85DD; Thu,  2 Feb 2012 20:56:35 -0800 (PST)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYS00ATOWE83A@szxga03-in.huawei.com>; Fri, 03 Feb 2012 12:56:32 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LYS00GGTWDY3U@szxga03-in.huawei.com>; Fri, 03 Feb 2012 12:56:32 +0800 (CST)
Received: from szxeml214-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AGU28948; Fri, 03 Feb 2012 12:56:31 +0800
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Fri, 03 Feb 2012 12:55:59 +0800
Received: from SZXEML526-MBS.china.huawei.com ([169.254.7.225]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Fri, 03 Feb 2012 12:56:09 +0800
Date: Fri, 03 Feb 2012 04:56:08 +0000
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
In-reply-to: <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com>
To: Erik Kline <ek@google.com>
Message-id: <7AA10427-E0B6-4441-A59D-54D51084948C@huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_FjKF2JMaMHLx6rDWEfWHxg)"
Content-language: en-US
Accept-Language: en-US, zh-CN
Thread-topic: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Thread-index: AQHM4iCuCXHujMgG4UGZ2dpnBHAge5YqnAg2
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com>
X-Mailman-Approved-At: Fri, 03 Feb 2012 08:17:33 -0800
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:56:36 -0000

--Boundary_(ID_FjKF2JMaMHLx6rDWEfWHxg)
Content-type: text/plain; charset=Windows-1252
Content-transfer-encoding: quoted-printable

I think that although the draft mainly discusses aaaa-whitelisting, it can =
be more specific in section 2 on issues impacting content delivery over ipv=
6.

Perhaps the biggest challenge in the IPv4-to-IPv6 transition is that the tw=
o protocols are not compatible; that is, IPv4-only systems cannot talk dire=
ctly to IPv6-only systems. This means no one can turn off IPv4 support unti=
l every last device they want to reach has acquired IPv6 connectivity. Unfo=
rtunately, many existing devices =97 including PCs running older OSes, as w=
ell as older cable and DSL modems, wireless routers, and other business and=
 consumer electronic devices=97have either limited or no IPv6 support. In o=
ther words, companies will have to support both protocols for years to come=
, in a long and bumpy transition period. During that time, there will effec=
tively be two Internets, an IPv4 one and an IPv6 one, loosely bound togethe=
r into a hybrid Internet by various transition technologies.

Challenges of reaching IPv6 users from IPv4 sites
Many types of Web applications rely on an end-to-end connection, where each=
 device, household, or entity is associated with a single IP address. CGN b=
reaks this assumption =97 as it creates a situa=ADtion where hundreds or th=
ousands of end users =97 related only by their network provider =97 share t=
he same IP address, and each user=92s IP address may change with every new =
connection. Thus, CGN cripples functions like geo-location =97 using the us=
er=92s IP address to determine their location, in order to personalize cont=
ent or to enforce licensing restrictions, for example, and abuse mitiga=ADt=
ion =97 IP blacklisting or whitelisting, in order to block spammers, trolls=
, or other abusive users.
CGN   breaks assumptions that many of today=92s Web applications rely on. I=
n particular it affects applications, such as peer-to-peer and VoIP, which =
rely in some way on a unique end user IP address. Troubleshooting the issue=
s is extremely complex and costly, as it can=92t be done without the NAT op=
erator=92s help.
In order to reach IPv4 sites, IPv6 end users need to go through a NAT64 gat=
eway. Because there may be only one or two such gateways within a network, =
communications may be forced through long, indirect paths. In addition, the=
se gateways quickly become congestion points within the network, as well as=
 easily targeted points of failure, further affecting the perfor=ADmance an=
d reliability.

Challenges of reaching IPv6 users from IPv6 sites
Because the IPv6 Internet is still sparsely connected, native IPv6 communic=
ations may require longer, less direct routes than their IPv4 counterparts,=
 resulting in slower performance and higher packet loss. This is particular=
ly troublesome for high throughput or low latency applications such as onli=
ne gaming or streaming media. In addition, a significant portion of the IPv=
6 Internet currently relies on tunneling traffic over IPv4, creating additi=
onal performance degradation.

So I think that content providers and application providers are no longer p=
ondering when to enable delivery over  IPv6 but are focused on how to manag=
e this transition in a manner that is cost-effective and efficient in the s=
hort term but takes into account long-term needs and opportunities.

Sent from my iPad

On Feb 2, 2012, at 7:05 PM, "Erik Kline" <ek@google.com<mailto:ek@google.co=
m>> wrote:

World IPv6 Launch changes the relevance of this document greatly, I
think.  Since this would be published after the announcement of World
IPv6 Launch, I think the document should be updated to discuss its own
applicability in a post- World IPv6 Launch Internet.

On 2 February 2012 00:09, The IESG <iesg-secretary@ietf.org<mailto:iesg-sec=
retary@ietf.org>> wrote:

The IESG has received a request from the IPv6 Operations WG (v6ops) to
consider the following document:
- 'Considerations for Transitioning Content to IPv6'
 <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> as an
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<mailto:ietf@ietf.org> mailing lists by 2012-02-15. Exceptiona=
lly, 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 document describes considerations for the transition of end user
  content on the Internet to IPv6.  While this is tailored to address
  end user content, which is typically web-based, many aspects of this
  document may be more broadly applicable to the transition to IPv6 of
  other applications and services.  This document explores the
  challenges involved in the transition to IPv6, potential migration
  tactics, possible migration phases, and other considerations.  The
  audience for this document is the Internet community generally,
  particularly IPv6 implementers.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impli=
cations/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impli=
cations/


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


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

--Boundary_(ID_FjKF2JMaMHLx6rDWEfWHxg)
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">
</head>
<body bgcolor=3D"#FFFFFF">
<div>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
I think that although the draft mainly discusses aaaa-whitelisting, it can =
be more specific in section 2 on issues impacting content delivery over ipv=
6.<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5">Perhaps the biggest challenge in the IPv4-to-IPv6 transi=
tion is that the two protocols are not compatible; that is, IPv4-only syste=
ms cannot talk directly to IPv6-only systems. This means no one can turn of=
f IPv4 support until every last device
 they want to reach has acquired IPv6 connectivity. Unfortunately, many exi=
sting devices =97 including PCs running older OSes, as well as older cable =
and DSL modems, wireless routers, and other business and consumer electroni=
c devices=97have either limited or no
 IPv6 support. In other words, companies will have to support both protocol=
s for years to come, in a long and bumpy transition period. During that tim=
e, there will effectively be two Internets, an IPv4 one and an IPv6 one, lo=
osely bound together into a hybrid
 Internet by various transition technologies.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<b><o:p>&nbsp;</o:p></b></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<b>Challenges of reaching IPv6 users from IPv4 sites<o:p></o:p></b></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5">Many types of Web applications rely on an end-to-end con=
nection, where each device, household, or entity is associated with a singl=
e IP address. CGN breaks this assumption =97 as it creates a situa=ADtion w=
here hundreds or thousands of end users
 =97 related only by their network provider =97 share the same IP address, =
and each user=92s IP address may change with every new connection. Thus, CG=
N cripples functions like geo-location =97 using the user=92s IP address to=
 determine their location, in order to personalize
 content or to enforce licensing restrictions, for example, and abuse mitig=
a=ADtion =97 IP blacklisting or whitelisting, in order to block spammers, t=
rolls, or other abusive users.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5">CGN &nbsp;&nbsp;breaks assumptions that many of today=92=
s Web applications rely on. In particular it affects applications, such as =
peer-to-peer and VoIP, which rely in some way on a unique end user IP addre=
ss. Troubleshooting the issues is extremely complex
 and costly, as it can=92t be done without the NAT operator=92s help.<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5">In order to reach IPv4 sites, IPv6 end users need to go =
through a NAT64 gateway. Because there may be only one or two such gateways=
 within a network, communications may be forced through long, indirect path=
s. In addition, these gateways quickly
 become congestion points within the network, as well as easily targeted po=
ints of failure, further affecting the perfor=ADmance and reliability.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<b>Challenges of reaching IPv6 users from IPv6 sites<o:p></o:p></b></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5">Because the IPv6 Internet is still sparsely connected, n=
ative IPv6 communications may require longer, less direct routes than their=
 IPv4 counterparts, resulting in slower performance and higher packet loss.=
 This is particularly troublesome
 for high throughput or low latency applications such as online gaming or s=
treaming media. In addition, a significant portion of the IPv6 Internet cur=
rently relies on tunneling traffic over IPv4, creating additional performan=
ce degradation.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; margin-=
left: 0in; margin-bottom: 0.0001pt; ">
<span class=3D"A5">So I think that&nbsp;</span>content providers and applic=
ation providers are no longer pondering when to enable delivery over &nbsp;=
IPv6 but are focused on how to manage this transition in a manner that is c=
ost-effective and efficient in the short term
 but takes into account long-term needs and opportunities.</p>
<br>
Sent from my iPad</div>
<div><br>
On Feb 2, 2012, at 7:05 PM, &quot;Erik Kline&quot; &lt;<a href=3D"mailto:ek=
@google.com">ek@google.com</a>&gt; wrote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div><span>World IPv6 Launch changes the relevance of this document greatly=
, I</span><br>
<span>think. &nbsp;Since this would be published after the announcement of =
World</span><br>
<span>IPv6 Launch, I think the document should be updated to discuss its ow=
n</span><br>
<span>applicability in a post- World IPv6 Launch Internet.</span><br>
<span></span><br>
<span>On 2 February 2012 00:09, The IESG &lt;<a href=3D"mailto:iesg-secreta=
ry@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:</span><br>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>The IESG has received a request from the IP=
v6 Operations WG (v6ops) to</span><br>
</blockquote>
<blockquote type=3D"cite"><span>consider the following document:</span><br>
</blockquote>
<blockquote type=3D"cite"><span>- 'Considerations for Transitioning Content=
 to IPv6'</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp;&lt;draft-ietf-v6ops-v6-aaaa-whitelis=
ting-implications-08.txt&gt; as an</span><br>
</blockquote>
<blockquote type=3D"cite"><span>Informational RFC</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>The IESG plans to make a decision in the ne=
xt few weeks, and solicits</span><br>
</blockquote>
<blockquote type=3D"cite"><span>final comments on this action. Please send =
substantive comments to the</span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"mailto:ietf@ietf.org">ietf@ietf.=
org</a> mailing lists by 2012-02-15. Exceptionally, comments may be</span><=
br>
</blockquote>
<blockquote type=3D"cite"><span>sent to <a href=3D"mailto:iesg@ietf.org">ie=
sg@ietf.org</a> instead. In either case, please retain the</span><br>
</blockquote>
<blockquote type=3D"cite"><span>beginning of the Subject line to allow auto=
mated sorting.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>Abstract</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; This document describes consideratio=
ns for the transition of end user</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; content on the Internet to IPv6. &nb=
sp;While this is tailored to address</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; end user content, which is typically=
 web-based, many aspects of this</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; document may be more broadly applica=
ble to the transition to IPv6 of</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; other applications and services. &nb=
sp;This document explores the</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; challenges involved in the transitio=
n to IPv6, potential migration</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; tactics, possible migration phases, =
and other considerations. &nbsp;The</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; audience for this document is the In=
ternet community generally,</span><br>
</blockquote>
<blockquote type=3D"cite"><span>&nbsp; particularly IPv6 implementers.</spa=
n><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>The file can be obtained via</span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"http://datatracker.ietf.org/doc/=
draft-ietf-v6ops-v6-aaaa-whitelisting-implications/">http://datatracker.iet=
f.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-implications/</a></span><br=
>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>IESG discussion can be tracked via</span><b=
r>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"http://datatracker.ietf.org/doc/=
draft-ietf-v6ops-v6-aaaa-whitelisting-implications/">http://datatracker.iet=
f.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-implications/</a></span><br=
>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>No IPR declarations have been submitted dir=
ectly on this I-D.</span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>___________________________________________=
____</span><br>
</blockquote>
<blockquote type=3D"cite"><span>v6ops mailing list</span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"mailto:v6ops@ietf.org">v6ops@iet=
f.org</a></span><br>
</blockquote>
<blockquote type=3D"cite"><span><a href=3D"https://www.ietf.org/mailman/lis=
tinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a></span><br>
</blockquote>
<span>_______________________________________________</span><br>
<span>v6ops mailing list</span><br>
<span><a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.i=
etf.org/mailman/listinfo/v6ops</a></span><br>
</div>
</blockquote>
</body>
</html>

--Boundary_(ID_FjKF2JMaMHLx6rDWEfWHxg)--

From fred@cisco.com  Fri Feb  3 08:35:39 2012
Return-Path: <fred@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 00C1E21F84FB; Fri,  3 Feb 2012 08:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.17
X-Spam-Level: 
X-Spam-Status: No, score=-106.17 tagged_above=-999 required=5 tests=[AWL=-0.171, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh3awGi3VWgg; Fri,  3 Feb 2012 08:35:38 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 4991221F84D0; Fri,  3 Feb 2012 08:35:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3592; q=dns/txt; s=iport; t=1328286938; x=1329496538; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=bDbztDUlH0glbqhDJXDUInHLDg+k4cnC6nQNfbYXdyA=; b=ZtrQg40h2qdpcAADaW75Q53aK6hxbw21KpUTa5fXBaYx9+GAhG+2UvNy vxs8Hjx1Mi50g9sY0Q1P4gEQtabYis1zCbiEVYTGkeQ3Qp90xV19Slo4r wzVCkhQ7xjzQW8o58kYxA0TAqJPOusH9M+sdP7k1fIqDJDFfBiM2zXGd1 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAG8MLE+rRDoI/2dsb2JhbABDrx6BBYFyAQEBAwEBAQEPASc0CwULCw4KIwsnMAYTFA6HWgmZXwGeeYtWBwICCQUMBhMBCAUDAwkNgw8FGAILAgVjBRAbBIJWYwSIRIxjhViNIg
X-IronPort-AV: E=Sophos;i="4.73,352,1325462400"; d="scan'208";a="28623756"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 03 Feb 2012 16:35:37 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q13GWoga003616; Fri, 3 Feb 2012 16:35:36 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 03 Feb 2012 08:35:36 -0800
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 03 Feb 2012 08:35:36 -0800
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com>
Date: Fri, 3 Feb 2012 08:35:36 -0800
Message-Id: <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com>
To: Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:35:39 -0000

On Feb 2, 2012, at 6:57 PM, Erik Kline wrote:

> World IPv6 Launch changes the relevance of this document greatly, I
> think.  Since this would be published after the announcement of World
> IPv6 Launch, I think the document should be updated to discuss its own
> applicability in a post- World IPv6 Launch Internet.

With respect...

The document was originally discussed in v6ops, and you chose to not =
comment. It went through last call there in January 2011 and was sent to =
the IESG. IESG review took until April, and an updated draft was posted =
at the end of May 2011. At IETF 81 (Quebec City) we were able to have =
you, the author, and some others discuss it. The IESG again decided it =
needed a revised draft, and that draft - in large part, a rewrite - =
arrived in October. v6ops had a second WGLC, in which you again declined =
to comment, although you may have seen Lorenzo's comments, which were =
picked up in a November version of the draft. Ralph and Jari finally =
cleared their "discuss" ballots a couple of weeks ago, and we are having =
a second IETF last call.

I'd like to understand your objective here. I know that you don't care =
for the draft, and at least at one point took it as a somewhat-personal =
attack. Is your objective to prevent the draft's publication entirely, =
or do you think that there is value in publishing it given a productive =
response to this comment? At what point are you willing to either =
participate in the public dialog or choose to not comment at all?

> On 2 February 2012 00:09, The IESG <iesg-secretary@ietf.org> wrote:
>>=20
>> The IESG has received a request from the IPv6 Operations WG (v6ops) =
to
>> consider the following document:
>> - 'Considerations for Transitioning Content to IPv6'
>>  <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> as an
>> Informational 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 2012-02-15. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>   This document describes considerations for the transition of end =
user
>>   content on the Internet to IPv6.  While this is tailored to address
>>   end user content, which is typically web-based, many aspects of =
this
>>   document may be more broadly applicable to the transition to IPv6 =
of
>>   other applications and services.  This document explores the
>>   challenges involved in the transition to IPv6, potential migration
>>   tactics, possible migration phases, and other considerations.  The
>>   audience for this document is the Internet community generally,
>>   particularly IPv6 implementers.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> =
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impl=
ications/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-aaaa-whitelisting-impl=
ications/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From david.black@emc.com  Fri Feb  3 10:57:18 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2466A21F853D; Fri,  3 Feb 2012 10:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.412
X-Spam-Level: 
X-Spam-Status: No, score=-109.412 tagged_above=-999 required=5 tests=[AWL=1.187, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIQjTD0d3glL; Fri,  3 Feb 2012 10:57:17 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE0C21F8476; Fri,  3 Feb 2012 10:57:16 -0800 (PST)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q13Iv3ln014116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Feb 2012 13:57:06 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 3 Feb 2012 13:56:42 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q13IufHE016263; Fri, 3 Feb 2012 13:56:41 -0500
Received: from mx14a.corp.emc.com ([169.254.1.94]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Fri, 3 Feb 2012 13:56:40 -0500
From: <david.black@emc.com>
To: <ietf@cybernothing.org>, <msk@cloudmark.com>, <gen-art@ietf.org>, <ietf@ietf.org>
Date: Fri, 3 Feb 2012 13:56:39 -0500
Subject: Gen-ART review of draft-ietf-marf-redaction-08
Thread-Topic: Gen-ART review of draft-ietf-marf-redaction-08
Thread-Index: AczQCujbMXhqirD5Sk6EB1sS2KVtOQG/Hm+wAudY0sA=
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AD13B873@MX14A.corp.emc.com>
References: <7C4DFCE962635144B8FAE8CA11D0BF1E05A7B80D63@MX14A.corp.emc.com> <7C4DFCE962635144B8FAE8CA11D0BF1E05A7CF1028@MX14A.corp.emc.com>
In-Reply-To: <7C4DFCE962635144B8FAE8CA11D0BF1E05A7CF1028@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 06 Feb 2012 11:07:13 -0800
Cc: presnick@qualcomm.com, david.black@emc.com, marf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:57:18 -0000

The -08 version is a significant improvement that aligns the draft's
recommendations on mechanisms for redaction and anonymization with the
situation-dependent levels of security that are appropriate for those
purposes.

idnits 2.12.13 didn't find anything.

The -08 version is ready for publication as a Standards Track RFC.

Thanks,
--David


> -----Original Message-----
> From: Black, David
> Sent: Thursday, January 19, 2012 7:10 PM
> To: ietf@cybernothing.org; Murray S. Kucherawy; gen-art@ietf.org; ietf@ie=
tf.org
> Cc: marf@ietf.org; presnick@qualcomm.com; Black, David
> Subject: Gen-ART review of draft-ietf-marf-redaction-05
>=20
> Based on discussion with the authors, the -05 version of this draft resol=
ves the
> issues raised in the Gen-ART review of the -04 version.  An important ele=
ment of
> the approach taken to issue [1] has been to explain why the security requ=
irements
> for redaction are significantly weaker than the strength of the secure ha=
shes
> that are suggested by the draft.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Tuesday, January 10, 2012 9:44 PM
> > To: ietf@cybernothing.org; Murray S. Kucherawy; gen-art@ietf.org; ietf@=
ietf.org
> > Cc: Black, David; marf@ietf.org; presnick@qualcomm.com
> > Subject: Gen-ART review of draft-ietf-marf-redaction-04
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on Ge=
n-ART, please
> > see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
>.
> >
> > Please resolve these comments along with any other Last Call comments y=
ou may receive.
> >
> > Document: draft-ietf-marf-redaction-04
> > Reviewer: David L. Black
> > Review Date: January 10, 2012
> > IETF LC End Date: January 18, 2011
> > IESG Telechat Date: January 19, 2011
> >
> > Summary: This draft is on the right track but has open issues, describe=
d in the review.
> >
> > This draft specifies a method for redacting information from email abus=
e reports
> > (e.g., hiding the local part [user] of an email address), while still a=
llowing
> > correlation of the redacted information across related abuse reports fr=
om the same
> > source. The draft is short, clear, and well written.
> >
> > There are two open issues:
> >
> > [1] The first open issue is the absence of security guidance to ensure =
that this
> > redaction technique effectively hides the redacted information.  The re=
daction
> > technique is to concatenate a secret string (called the "redaction key"=
) to the
> > information to be redacted, apply "any hashing/digest algorithm", conve=
rt the output
> > to base64 and use that base64 string to replace the redacted informatio=
n.
> >
> > There are two important ways in which this technique could fail to effe=
ctively hide
> > the redacted information:
> > 	- The secret string may inject insufficient entropy.
> > 	- The hashing/digest algorithm may be weak.
> >
> > To take an extreme example, if the secret string ("redaction key") cons=
ists of a
> > single ASCII character, and a short email local part is being redacted,=
 then the
> > output is highly vulnerable to dictionary and brute force attacks becau=
se only 6 bits
> > of entropy are added (the result may look secure, but it's not).  Beyon=
d this extreme
> > example, this is a potentially real concern - e.g., applying the rule o=
f thumb that
> > ASCII text contains 4-5 bits of entropy per character, the example in A=
ppendix A
> > uses a "redaction key" of "potatoes" that injects at most 40 bits of en=
tropy -
> > is that sufficient for email redaction purposes?
> >
> > To take a silly example, if a CRC is used as the hash with that sort of=
 short input,
> > the result is not particularly difficult to invert.
> >
> > I suggest a couple of changes:
> > 1) Change "any hashing/digest algorithm" to require use of a secure has=
h, and
> > 	explain what is meant by "secure hash" in the security considerations =
section.
> > 2) Require a minimum length of the "redaction key" string, and strongly=
 suggest
> > 	(SHOULD) that it be randomly generated (e.g., by running sufficient ou=
tput
> > 	of an entropy-rich random number generator through a base64 converter)=
.
> >
> > For the latter change, figure out the amount of entropy that should be =
used
> > for redaction - the recommended string length will be larger because pr=
intable
> > ASCII is not entropy-dense (at best it's good for 6 bits of entropy in =
each
> > 8-bit character, and human-written text such as this message has signif=
icantly
> > less).
> >
> > From a pure security perspective, use of HMAC with specified secure has=
hes
> > (SHA2-family) and an approach of hashing the "redaction key" down to a =
binary
> > key for HMAC would be a stronger approach. I suggest that authors consi=
der
> > approach, but  there may be practical usage concerns that suggest not a=
dopting it.
> >
> > [2] The second open issue is absence of security considerations for the=
 redaction
> > key.  The security considerations section needs to caution that the red=
action key
> > is a secret key that must be managed and protected as a secret key.  Di=
sclosure
> > of a redaction key removes the redaction from all reports that used tha=
t key.
> > As part of this, guidance should be provided on when and how to change =
the
> > redaction key in order to limit the effects of loss of secrecy for a si=
ngle
> > redaction key.
> >
> > Editorial Nit: I believe that "anonymization" is a better description o=
f what
> > this draft is doing (as opposed to "redaction"), particularly as the re=
sult is
> > intended to be correlatable via string match across reports from the sa=
me source.
> >
> > idnits 2.12.13 didn't find any nits.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From ek@google.com  Fri Feb  3 17:43:20 2012
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 502EC11E80E2 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2012 17:43:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A547DWXJHPq9 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2012 17:43:19 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B846211E8096 for <ietf@ietf.org>; Fri,  3 Feb 2012 17:43:19 -0800 (PST)
Received: by qcsg13 with SMTP id g13so2783844qcs.31 for <ietf@ietf.org>; Fri, 03 Feb 2012 17:43:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:x-system-of-record:content-type:content-transfer-encoding; bh=hok4rc7Ei+ic50sRwyzc2soLt/VSXwlK3ZNnxrXuINQ=; b=kUYMR74BiMJqqaVjRY91r4+W+bSxQACMr0x+9hnyK+s4IY2hZHXqG4PFp7vfCW1N1T ZdQO8nzzll/XDRPxBJrXWO7MvuYG6aD8nvyHayhTFLTRp8VMOK1uWJEJoPm4oSAX29w9 WFudfHMr2tl467SekWXR0pChfoftg8X5QAsCw=
Received: by 10.224.177.68 with SMTP id bh4mr11680498qab.2.1328319799181; Fri, 03 Feb 2012 17:43:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.177.68 with SMTP id bh4mr11680489qab.2.1328319799080; Fri, 03 Feb 2012 17:43:19 -0800 (PST)
Received: by 10.229.101.158 with HTTP; Fri, 3 Feb 2012 17:43:19 -0800 (PST)
In-Reply-To: <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
Date: Sat, 4 Feb 2012 10:43:19 +0900
Message-ID: <CAAedzxoGOH3ntQiPJPZSyZE-qWdQj1fW3Q07SK3W72jpHdXvAQ@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
From: Erik Kline <ek@google.com>
To: Fred Baker <fred@cisco.com>
X-System-Of-Record: true
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 06 Feb 2012 11:07:25 -0800
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:43:20 -0000

On 4 February 2012 01:35, Fred Baker <fred@cisco.com> wrote:
>
> On Feb 2, 2012, at 6:57 PM, Erik Kline wrote:
>
>> World IPv6 Launch changes the relevance of this document greatly, I
>> think. =C2=A0Since this would be published after the announcement of Wor=
ld
>> IPv6 Launch, I think the document should be updated to discuss its own
>> applicability in a post- World IPv6 Launch Internet.
>
> With respect...
>
> The document was originally discussed in v6ops, and you chose to not comm=
ent. It went through last call there in January 2011 and was sent to the IE=
SG. IESG review took until April, and an updated draft was posted at the en=
d of May 2011. At IETF 81 (Quebec City) we were able to have you, the autho=
r, and some others discuss it. The IESG again decided it needed a revised d=
raft, and that draft - in large part, a rewrite - arrived in October. v6ops=
 had a second WGLC, in which you again declined to comment, although you ma=
y have seen Lorenzo's comments, which were picked up in a November version =
of the draft. Ralph and Jari finally cleared their "discuss" ballots a coup=
le of weeks ago, and we are having a second IETF last call.
>
> I'd like to understand your objective here. I know that you don't care fo=
r the draft, and at least at one point took it as a somewhat-personal attac=
k. Is your objective to prevent the draft's publication entirely, or do you=
 think that there is value in publishing it given a productive response to =
this comment? At what point are you willing to either participate in the pu=
blic dialog or choose to not comment at all?

With humblest apologies...

Having spent time rereading, I think W6L is clearly an implementation
of  sections 4.5 and 5.7, or 4.4 and 5.6, depending on the
implementer.

Additionally, in retrospect, there's probably no great reason to add a
reference to a future event.  It seems to me that the most meaningful
technical observation that can actually be offered would be its
scheduled calendar date.

There's no excuse for my failing to reread afresh before commenting.
Again, my apologies,
-Erik

From ve7jtb@ve7jtb.com  Mon Feb  6 17:07:13 2012
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B42C21F863C; Mon,  6 Feb 2012 17:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYgjZSNNlfvm; Mon,  6 Feb 2012 17:07:12 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 99D2821F8636; Mon,  6 Feb 2012 17:07:12 -0800 (PST)
Received: by yenm3 with SMTP id m3so3135403yen.31 for <multiple recipients>; Mon, 06 Feb 2012 17:07:12 -0800 (PST)
Received: by 10.236.182.2 with SMTP id n2mr28926322yhm.11.1328576832240; Mon, 06 Feb 2012 17:07:12 -0800 (PST)
Received: from [192.168.1.213] ([190.22.43.24]) by mx.google.com with ESMTPS id k16sm39280147ani.5.2012.02.06.17.07.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 06 Feb 2012 17:07:11 -0800 (PST)
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0	Authorization Protocol: Bearer Tokens) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/signed; boundary="Apple-Mail=_AA4301CA-C6FB-4ADE-A185-D4A8447AAF67"; protocol="application/pkcs7-signature"; micalg=sha1
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723453AAB9682E@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Mon, 6 Feb 2012 22:07:04 -0300
Message-Id: <7D4DB9C9-7194-42A0-A573-4243FE27E512@ve7jtb.com>
References: <20120123154643.16223.44509.idtracker@ietfa.amsl.com> <4F1D8391.3080009@gmx.de> <4F1F3D84.1030300@gmx.de> <90C41DD21FB7C64BB94121FBBC2E723453AAB9682E@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Tue, 07 Feb 2012 09:25:23 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, "oauth@ietf.org" <oauth@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:07:13 -0000

--Apple-Mail=_AA4301CA-C6FB-4ADE-A185-D4A8447AAF67
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

RE new text in Draft 23

http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-10.10

Generated tokens and other credentials not intended for handling by
   end-users MUST be constructed from a cryptographically strong random
   or pseudo-random number sequence ([RFC1750]) generated by the
   authorization server.

Given that many implementations may elect to use signed tokens, such as =
SAML or JWT (JOSE) this should not be a MUST.

Giving people sensible defaults such as the probability of an attacker =
guessing a valid access token for the protected resource should be less =
than 2^(-128).

The probability of generating hash colisions randomly is a odd metric,  =
2^(-128) for a SHA256 as I recall. =20
Many factors play into what is secure, token lifetime etc. =20

I don't mind some reasonable defaults but adding a requirement for =
unstructured tokens is a bit much.

Regards
John B.




--Apple-Mail=_AA4301CA-C6FB-4ADE-A185-D4A8447AAF67
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIO9TCCBwsw
ggXzoAMCAQICAgZDMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0Ew
HhcNMTAwMzE3MTM0NDQ1WhcNMTIwMzE4MTE1NTExWjCBzTEgMB4GA1UEDRMXMTY1NTU1LTJHU3FU
T1ZUbkk4OHhOSW4xCzAJBgNVBAYTAkNMMSIwIAYDVQQIExlNZXRyb3BvbGl0YW5hIGRlIFNhbnRp
YWdvMREwDwYDVQQHEwhWaXRhY3VyYTEtMCsGA1UECxMkU3RhcnRDb20gVmVyaWZpZWQgQ2VydGlm
aWNhdGUgTWVtYmVyMRUwEwYDVQQDEwxKb2huIEJyYWRsZXkxHzAdBgkqhkiG9w0BCQEWEGpicmFk
bGV5QG1hYy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDB7DXf6x80dsJiB9B9
Ds4cBQdA+9bNuZMBeXkUAHrvYH2taw6y8fcadbhgk92FyPiCbsHtB1VTaJThaMqtXuTkS4r5Sfb8
k5kboz3OQVPMmrOJIUpaoDP2heKEhMUSL6ev9CvsuYs+XXe7f9vY3w/A8cVg/NoOXbdqKXbWOMMd
NSdg7uJWSsmpqILFzQsumwqVH24tYX0sqvpJy/r+pc84j6QM+Ew0B9bz3OkEMafjcCeGRfdsQnLB
+rIR8BPDeeKRP6a5e8Lf6slUQ3s/rh33otnkNaz6DMLTJrj0qoAD7FxB7LlLalIjrg08BNZDJUQK
7zTlNxkPqVHVTg3H0OG/AgMBAAGjggMyMIIDLjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFMjJGKHWsNb6VU54Wkktqcu2on3B
MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MFQGA1UdEQRNMEuBEGpicmFkbGV5QG1h
Yy5jb22BEXZlN2p0YkB2ZTdqdGIuY29tgRNqYnJhZGxleUB3aW5nYWEuY29tgQ9qYnJhZGxleUBt
ZS5jb20wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQIBMIIBIDAuBggrBgEFBQcCARYi
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYBBQUHAgIwgaowFBYNU3RhcnRD
b20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNlZSBzZWN0aW9uICpMZWdhbCBMaW1p
dGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBh
dmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBa
MCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jcnR1Mi1jcmwuY3JsMCugKaAnhiVodHRw
Oi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1Mi1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsG
AQUFBzABhi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMi9jbGllbnQvY2EwQgYI
KwYBBQUHMAKGNmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczIuY2xpZW50
LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEF
BQADggEBAHu8WZHdSu+I5GMzGDrkxFVUzZ2JAcwzgSscYNFX2CFJlU8ncC+/E5Y18oiGcIR9o7J3
Hh4fGrjJmxTsq2O3E9/qg0yWSEzlCBhAXl/D+GTyUJA/KfIuCbdsuS5opprSrBZztqMYcGSCQJFz
lE+esdbCXazdyEww5XfiGVgKiRyV2ycXyxNjekowbcDffSsOYplGBjJwPRYpESgfCYDXm+yyDQhy
Xk0pxNEA7ob5fAMellN8FcgLfQtwSRcg8cYl/m8/BeVl6+eZuzCb061PdUN+mDf6erS55tXqgWJ3
toTp3GGaaOwwGs/bA1UnLqYm93RfTyL3kU1OWG8syPFMLoIwggfiMIIFyqADAgECAgEOMA0GCSqG
SIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAyNTRaFw0xMjEwMjIyMTAyNTRaMIGM
MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERp
Z2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmlt
YXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDLKIVFnAEs+xnyq6UzjCqgDcvQVe1dIoFnRsQPCFO+y92k8RK0Pn3MbQ2Gd+mehh9GBZ+36uUQ
A7Xj9AGM6wgPhEE34vKtfpAN5tJ8LcFxveDObCKrL7O5UT9WsnAZHv7OYPYSR68mdmnEnJ83M4wQ
gKO19b+Rt8sPDAz9ptkQsntCn4GeJzg3q2SVc4QJTg/WHo7wF2ah5LMOeh8xJVSKGEmd6uPkSbj1
13yKMm8vmNptRPmM1+YgmVwcdOYJOjCgFtb2sOP79jji8uhWR91xx7TpM1K3hv/wrBZwffrmmEpU
euXHRs07JqCCvFh9coKF4UQZvfEg+x3/69xRCzb1AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/
MAsGA1UdDwQEAwIBpjAdBgNVHQ4EFgQUrlWDb+wxyrn3HfqvazHzyB3jrLswgagGA1UdIwSBoDCB
nYAUTgvvGqRAW6UXaYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEp
MCcGA1UEAxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9
BggrBgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2EtY3Js
LmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYDVR0gBIIB
VDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0
Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5zdGFydGNvbS5vcmcv
aW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQgQ29tbWVyY2lhbCAoU3Rh
cnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCByZWFkIHRoZSBzZWN0aW9uICpM
ZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5
IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYw
EQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIBDQRDFkFTdGFydENvbSBDbGFzcyAyIFByaW1h
cnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVtYWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUF
AAOCAgEAHvcQF/726YR5L5A3Ta7JV1nTu3w9yWqp00945pg7uea+1KVtR/7/yeNFAV7MPQylPE8p
ROEcGU+RwwDFuNn9cePfAMzOBTpy/6VE076+gYkZa4n8uWaL5A2FVo8tRmEyfoT4gRL9B5h5w8Y4
ZySCJBLyfp4jByyxHaTTIWZ8TIkxUQLSBeFnmHKYFwYwMbBA0Sgb8ONCvq9zeJcpMkkDadhJSCfB
9c9gZocbaaVHVqTlSeENRr5/Y31dapzIRQg2Pl9V/A65Cq03KQxMXBpXn8HkLO/g2FCt7KYkJCaT
e6qT2JX8thmB3nb+5RmtWQIITCP+PPNkFQCts6ujOtJx6TlDLWA+tV7QLN2Q+S98p/SwnXito+GW
0N7kXcL8QDBVsF8lCvwCz+JQrvUIcW5xEzpAVk9xSbpePxVIMzNEUQhBobkFojhUqGt+VyU3GH/+
BP2brzl4StOJ1KXuw2EzFs0ai9OMsqCUFRyhykm6MrbnsnSrqhWSnSQPYIu+zpzwWC/8sZFxoJCw
vbbIu+6E+AIGa8tP+pYF+empPn/7pkIoTT4LSkkEIxGKvUvDJTh86VDNL8bIIQE2LHVDwcOq+mcQ
x416FAA9Nw1DBGyrFr6hQe5yTVXrJ4G7vJosNRGCwPnx302gonaFdwi++YyqjPyhPO6q4fRarYvW
yqp5L6UxggNsMIIDaAIBATCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0
ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIGQzAJBgUr
DgMCGgUAoIIBrTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjAy
MDcwMTA3MDVaMCMGCSqGSIb3DQEJBDEWBBQWK/uj8aETvEvLNway5KKCugBzKDCBpAYJKwYBBAGC
NxAEMYGWMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgZDMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsT
IlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENs
YXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIGQzANBgkqhkiG9w0BAQEFAASC
AQBWRTWqwRMsdSi0025K+czNfE1RtshaIMh+absgw4E/WxWc9A7AtOHjqD7or1XR9rfqYT2X9O1E
i331Ps9yumoTgxJ6CfITjjBESR8nNYyT7LaBh1SHUmFuhGGBlBHfWRAWPwaMqQverGYDMUAbCsGl
ATSijKTgntQGHSgrpmSiX6zRZP4RQVVaJWpJffKHIKtx307YS62YK3EHuGe8Eyiks/2qliXxe8un
yNkIbQnCDDbnMZ8G0Yi7EE6YtHmA3oHOjstCIN1a458Qwght5ZZBxbpZnsZt6OqN7otShNb7ihPA
V6aejiV3HlTCLm3MC7VaIYTbhmKr90t8CbmoOMWdAAAAAAAA

--Apple-Mail=_AA4301CA-C6FB-4ADE-A185-D4A8447AAF67--

From sakimura@gmail.com  Mon Feb  6 19:46:08 2012
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 2365611E80D6 for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2012 19:46:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=-0.553, BAYES_00=-2.599, DEAR_SOMETHING=1.605, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQhXra4rsjYm for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2012 19:46:07 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id C1FC711E80BE for <ietf@ietf.org>; Mon,  6 Feb 2012 19:46:06 -0800 (PST)
Received: by lahl5 with SMTP id l5so4295880lah.31 for <ietf@ietf.org>; Mon, 06 Feb 2012 19:46:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=zVt/uWNvqKb2O4epNr/odYhor+TZULT74f/q/PSZ7CM=; b=TxMy5/rRKtauCtwiDPuZT17aOcTwBsyG4voiu3ql34dkAW4fa6LEjvwBjeYP2Mg0v6 /OsOb8YvHH7OLmErp0qEo/b5Hh/iyEKKufJCtceiwSpWYPdt3oz33IjjDJdjqB9uV4bJ PIuehhvrsuRO74dT9QvnmOVtuviqzXRg9R/BM=
MIME-Version: 1.0
Received: by 10.152.112.104 with SMTP id ip8mr11390990lab.15.1328586365798; Mon, 06 Feb 2012 19:46:05 -0800 (PST)
Received: by 10.152.21.133 with HTTP; Mon, 6 Feb 2012 19:46:05 -0800 (PST)
Date: Tue, 7 Feb 2012 12:46:05 +0900
Message-ID: <CABzCy2Cm2e221WOUGR+o1S3uOduHRNoLEabCFAQwg9evwN+k8Q@mail.gmail.com>
Subject: Comments on Section 10.10 of OAuth 2.0
From: Nat Sakimura <sakimura@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 07 Feb 2012 09:25:59 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:46:08 -0000

Dear Sir/Madam:

Attached below, please find the comment in response to the
Last Call: <draft-ietf-oauth-v2-23.txt> (The OAuth 2.0	Authorization
Protocol) to Proposed Standard.

These comments are on the changes between rev.22 and rev.23.

Yours faithfully,

Nat Sakimura


=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
Comment on Section 10.10
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D


Title: "constructed from" vague
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D

Comment
--------

The current text goes as:

=A0 =A0The authorization server MUST prevent attackers from guessing access
=A0 =A0tokens, authorization codes, refresh tokens, resource owner
=A0 =A0passwords, and client credentials.

=A0 =A0Generated tokens and other credentials not intended for handling by
=A0 =A0end-users MUST be constructed from a cryptographically strong random
=A0 =A0or pseudo-random number sequence ([RFC4086]) generated by the
=A0 =A0authorization server.

=A0 =A0(Note: 1750 was modifed to be 4086)

It is unclear from this sentence if it only allows the sequence
that is compliant to Section 6.2 of RFC4086.
It is also unclear whether it could be a string that included
such random string during the generation, or has to be the
prn sequence. I believe the former is the case.
Clarification is desired.




Title: Only allowing the construction from PRN sequence too limiting
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Comment
-------
An alternative measure would be to use digital signatures.
The current text seem to only allow PRN sequence.
Other measures should be allowed as well.


Title: Probability requirement needs refinement
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Comment
--------
The current text goes:

=A0 =A0The probability of any two values being
=A0 =A0identical MUST be less than or equal to 2^(-128) and SHOULD be less
=A0 =A0than or equal to 2^(-160).

This seems to be simply stating the randomness requirement.
What we would like to do to control the credentials guessing attacks
depends on the kind of token in question.


Title: Last para 10.10 is normative yet undefined
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D

Comment
--------
It goes:

=A0 =A0The authorization server MUST utilize other means to protect
=A0 =A0credentials intended for end-user usage.

Since it has a "MUST", it is a normative language.
Yet it only requires "other means", which is undefined.
It also excludes the possibility of using server generated
PRN sequece as the user password.


=3D=3D=3D=3D=3D=3D=3D=3D
Proposal
=3D=3D=3D=3D=3D=3D=3D=3D

10.10. =A0Credentials Guessing Attacks

=A0 =A0The authorization server MUST prevent attackers from guessing access
=A0 =A0tokens, authorization codes, refresh tokens, resource owner
=A0 =A0passwords, and client credentials.

=A0 =A0The appropriate probability of the success of the attack
=A0 =A0during the lifetime of the tokens and credentials depends
=A0 =A0on the risk profile of the application in question.
=A0 =A0The application SHOULD set the policy requiring the probability
=A0 =A0of the success of the attack during the lifetime of each type
=A0 =A0of tokens and credentials and implementations MUST adhere to
=A0 =A0such policy.

=A0 =A0For the generated tokens and other credentials that are not
=A0 =A0intended for handling by end-users, one way to achieve it is
=A0 =A0to construct them including a cryptographically strong random
=A0 =A0or pseudo-random number sequence described in Section 6.2
=A0 =A0of [RFC4086] generated by the authorization server.
=A0 =A0Typically, the probability of any two values being
=A0 =A0identical is set to be less than or equal to 2^(-128) and
=A0 =A0often considered desirable to be less than or equal to 2^(-160).

=A0 =A0Other possible control measures includes:

=A0 =A0- Progressive slow down and token revocation on the failed attempts
=A0 =A0- Pattern analysis of failed token and credential usage

=A0 =A0For the credentials intended for end-user usages,
=A0 =A0typical controls includes:

=A0 =A0- Progressive slow down and other mechanisms such as captcha
=A0 =A0 =A0on the failed attempts to thwart brute force
=A0 =A0- Pattern analysis of failed token and credential usage
=A0 =A0- Enforce the use of strong passwords (e.g., complex, non-dictionary
=A0 =A0 =A0strings that contain mixtures of upper case, lower case,
=A0 =A0 =A0numeric, and special characters)
=A0 =A0- Enforce the use of Multi-Factor authentication and other
=A0 =A0 =A0strong authentication mechanisms


END

From ben@nostrum.com  Mon Feb  6 15:17:25 2012
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 36CEB21F85EA; Mon,  6 Feb 2012 15:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yWtJ+D2eOKg2; Mon,  6 Feb 2012 15:17:24 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 51A8121F8582; Mon,  6 Feb 2012 15:17:24 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q16NHN9L014007 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Feb 2012 17:17:23 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Date: Mon, 6 Feb 2012 17:17:22 -0600
Message-Id: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 07 Feb 2012 09:26:03 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:17:25 -0000

I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments =
you may receive.

Document: draft-ietf-dhc-forcerenew-nonce-03
Reviewer: Ben Campbell
Review Date: 2012-02-06
IETF LC End Date: 2012-02-06

Summary:This draft is not quite ready for publication as a proposed =
standard. There are some potentially significant issues that should be =
addressed first.

[Note: Hopefully this draft has had or will have a SecDir review, since =
it seems ripe for significant security implications.]


*** Major issues:

-- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.=20

I think some additional text in (perhaps in the security considerations) =
is needed to explain either why the vulnerability to eavesdroppers is =
either okay in general, or limits the mechanism's use to environment =
where it is okay. It also seems like that, in the best case, this =
mechanism proves only that a Forcerenew request comes from the same DHCP =
server as in the original transaction, but otherwise does not prove =
anything about the identity of that server. If so, it would be worth =
mentioning it.

-- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)

*** Minor issues:

-- Section 1 "=20
In such environments the mandatory coupling between FORCERENEW and DHCP =
Authentication [RFC3118] can be relaxed."

It's not clear to me what connection that assertion has with this draft. =
Is there an intent that the proposed mechanisms be used only in such =
environments? I don't find any language scoping this proposal to any =
particular environment.

-- section 3:

Does this draft update either 3203 or 3118? If so, please state that =
explicitly in the abstract, introduction, and draft headers. (I think it =
must at least update 3203, since that draft requires the use of 3118, =
and this draft relaxes that.)

-- section 3.1, last paragraph: "...only if the client and server are =
not using any other authentication..."

That seems to conflict with the statement in section 3 that this =
mechanism is only used if RFC3118 is not used. That is, it's not a =
choice between this mechanism or any other mechanism, it's a choice =
between this mechanism or 3118.

-- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."

Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?

-- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the =
Forcerenew message using the Forcerenew nonce =85"

Using it how? Is it the secret key for the HMAC calculation? (If so, why =
aren't we calling it a "key" in the first place?)

-- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew =
nonce Protocol authentication MUST include the DHCP Forcerenew Nonce =
protocol authentication option=85"

Only if the client advertised it, right? Otherwise, this seems to =
conflict with the previous SHOULD NOT.

-- section 3.1.4, 4th paragraph: "=85 =20
the client computes an HMAC-MD5 over the DHCP Forcerenew message, using =
the Forcerenew Nonce =85"

Using it how?

-- section 6:

You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)

*** Nits/editorial comments:

-- Abstract, second sentence:

I have trouble parsing this sentence. Are the propositions correct?

-- Section 3.1.1,4th paragraph: "=85 configured to require =85"

Do you mean configured to "require", or configured to "use"? I would =
normally take "requires" to mean that the server would not work with =
clients that don't advertise support for the mechanism.

-- section 3.1.1, message flow diagram:

It would be helpful if you could avoid widowing the top of the diagram. =
One has to keep flipping back to see the labels.

-- section 3.1.3, 5th paragraph:=20

Please expand "RDM"

-- section 3.1.4, first paragraph: "The client MUST=85"

A client that supports this mechanism MUST=85

-- section 3.1.4, 2nd and third paragraph, 1st sentence of each:

I'm confused by this sentence of each paragraph. Are they intended as =
conditionals for the rest of the respective paragraph?







From ben@nostrum.com  Mon Feb  6 15:27:45 2012
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 9709711E80AE; Mon,  6 Feb 2012 15:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.197
X-Spam-Level: 
X-Spam-Status: No, score=-102.197 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmgCUjlJ+dbI; Mon,  6 Feb 2012 15:27:45 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF27621F84C9; Mon,  6 Feb 2012 15:27:44 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q16NRds6015436 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Feb 2012 17:27:44 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
Date: Mon, 6 Feb 2012 17:27:39 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <7492D649-454D-45CB-8983-4A6C385D13E2@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 07 Feb 2012 09:26:03 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:27:45 -0000

Additionally, the I got a failed delivery notice (User Unknow) for David =
Miles's address.

On Feb 6, 2012, at 5:17 PM, Ben Campbell wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-dhc-forcerenew-nonce-03
> Reviewer: Ben Campbell
> Review Date: 2012-02-06
> IETF LC End Date: 2012-02-06
>=20
> Summary:This draft is not quite ready for publication as a proposed =
standard. There are some potentially significant issues that should be =
addressed first.
>=20
> [Note: Hopefully this draft has had or will have a SecDir review, =
since it seems ripe for significant security implications.]
>=20
>=20
> *** Major issues:
>=20
> -- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.=20
>=20
> I think some additional text in (perhaps in the security =
considerations) is needed to explain either why the vulnerability to =
eavesdroppers is either okay in general, or limits the mechanism's use =
to environment where it is okay. It also seems like that, in the best =
case, this mechanism proves only that a Forcerenew request comes from =
the same DHCP server as in the original transaction, but otherwise does =
not prove anything about the identity of that server. If so, it would be =
worth mentioning it.
>=20
> -- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)
>=20
> *** Minor issues:
>=20
> -- Section 1 "=20
> In such environments the mandatory coupling between FORCERENEW and =
DHCP Authentication [RFC3118] can be relaxed."
>=20
> It's not clear to me what connection that assertion has with this =
draft. Is there an intent that the proposed mechanisms be used only in =
such environments? I don't find any language scoping this proposal to =
any particular environment.
>=20
> -- section 3:
>=20
> Does this draft update either 3203 or 3118? If so, please state that =
explicitly in the abstract, introduction, and draft headers. (I think it =
must at least update 3203, since that draft requires the use of 3118, =
and this draft relaxes that.)
>=20
> -- section 3.1, last paragraph: "...only if the client and server are =
not using any other authentication..."
>=20
> That seems to conflict with the statement in section 3 that this =
mechanism is only used if RFC3118 is not used. That is, it's not a =
choice between this mechanism or any other mechanism, it's a choice =
between this mechanism or 3118.
>=20
> -- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."
>=20
> Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?
>=20
> -- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the =
Forcerenew message using the Forcerenew nonce =85"
>=20
> Using it how? Is it the secret key for the HMAC calculation? (If so, =
why aren't we calling it a "key" in the first place?)
>=20
> -- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew =
nonce Protocol authentication MUST include the DHCP Forcerenew Nonce =
protocol authentication option=85"
>=20
> Only if the client advertised it, right? Otherwise, this seems to =
conflict with the previous SHOULD NOT.
>=20
> -- section 3.1.4, 4th paragraph: "=85 =20
> the client computes an HMAC-MD5 over the DHCP Forcerenew message, =
using the Forcerenew Nonce =85"
>=20
> Using it how?
>=20
> -- section 6:
>=20
> You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)
>=20
> *** Nits/editorial comments:
>=20
> -- Abstract, second sentence:
>=20
> I have trouble parsing this sentence. Are the propositions correct?
>=20
> -- Section 3.1.1,4th paragraph: "=85 configured to require =85"
>=20
> Do you mean configured to "require", or configured to "use"? I would =
normally take "requires" to mean that the server would not work with =
clients that don't advertise support for the mechanism.
>=20
> -- section 3.1.1, message flow diagram:
>=20
> It would be helpful if you could avoid widowing the top of the =
diagram. One has to keep flipping back to see the labels.
>=20
> -- section 3.1.3, 5th paragraph:=20
>=20
> Please expand "RDM"
>=20
> -- section 3.1.4, first paragraph: "The client MUST=85"
>=20
> A client that supports this mechanism MUST=85
>=20
> -- section 3.1.4, 2nd and third paragraph, 1st sentence of each:
>=20
> I'm confused by this sentence of each paragraph. Are they intended as =
conditionals for the rest of the respective paragraph?
>=20
>=20
>=20
>=20
>=20
>=20


From jhw@apple.com  Tue Feb  7 10:45:27 2012
Return-Path: <jhw@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 8237921F8771 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2012 10:45:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.238
X-Spam-Level: 
X-Spam-Status: No, score=-109.238 tagged_above=-999 required=5 tests=[AWL=-0.498, BAYES_20=-0.74, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jnPutHzkE9t for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2012 10:45:27 -0800 (PST)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 083F621F86BE for <ietf@ietf.org>; Tue,  7 Feb 2012 10:45:27 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LZ100CKFDE8QQ30@mail-out.apple.com> for ietf@ietf.org; Tue, 07 Feb 2012 10:45:22 -0800 (PST)
X-AuditID: 1180711d-b7b88ae000004be6-8b-4f317142e022
Received: from kallisti.apple.com (kallisti.apple.com [17.193.13.64]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 02.E0.19430.241713F4; Tue, 07 Feb 2012 10:45:22 -0800 (PST)
Subject: Re: ITC copped out on UTC again
From: james woodyatt <jhw@apple.com>
In-reply-to: <CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com>
Date: Tue, 07 Feb 2012 10:45:22 -0800
Message-id: <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com>
References: <CAMm+LwgtUzw9GB1Mc=zQ3Fr_RPrsfy7d59HH6fstvsgTN=_C+g@mail.gmail.com> <CAJNg7V+56hgjyCptJLNr1YqrZ5d3y3VsJZCD+P999V4u1GourA@mail.gmail.com> <4F1D2DD7.6090103@tana.it> <CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnluLIzCtJLcpLzFFi42IRPMjroOtUaOhvMH2FgcWzjfNZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsXvrAcaCfRwVW2/9YGlgvM3WxcjJISFgIrHuzA9GCFtM4sK9 9UBxLg4hgdlMEl13boIlmAV0JHZuvQPWwCtgKDHzVTsriC0soCGx8dFqJhCbTUBF4tvlu2A2 p0CgxKOf38BsFqD4gYPnWSDmaEssW/iaGWKOjcTcc0fZIZZ9ZZTYvu8fO0hCREBZ4tHU81DX yUrcPrifaQIj3ywkd8xCcscsJHMXMDKvYhQsSs1JrDQ01kssKMhJ1UvOz93ECAqmhkLZHYz7 f/IfYhTgYFTi4T3IbeAvxJpYVlyZe4hRgoNZSYR3aZChvxBvSmJlVWpRfnxRaU5q8SFGaQ4W JXHedbP0/YUE0hNLUrNTUwtSi2CyTBycUg2MplsEAxPm9J9W+rHvY+z110p8XOc8J+hJzYjN shFVrl58c+6NotPbDb9/mvMg08v081keQfcXf78tkOnt/vBTbvf/zpuBmV9t08plbKd2tDdt Srkyp/ln49amL8+blVfz5r3QXb5NSrbZt0/e53vl7L7JRy9venji5qOedRmhvL/qrd6K7qrp VWIpzkg01GIuKk4EAIujn44iAgAA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:45:27 -0000

On Jan 23, 2012, at 10:03 , Marshall Eubanks wrote:
> 
> And, of course, this is also orthogonal to the problem at hand, as UTC, GPS time, TT, all  also experience from the same issues, and it has nothing to do with leap seconds.

A point in favor of deriving the Internet time scale directly from TAI is that it fairly effectively reduces UTC to just another time zone, one that covers the entire surface of the Earth, but a timezone nonetheless.

Just like every other time zone, its future divergence from TAI is unpredictable.  The principle reason is that time zones are under the control of-- and subject to change at any time by-- various sovereign and treaty bodies.  TAI has a fairly stable foundation in non-relativistic physics, which experience has shown to be somewhat resistant to the power of political bodies to modify at will, so it should be good enough for most running code on the Internet.

Shorter james: +1 for switching to TAI.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From fanf2@hermes.cam.ac.uk  Tue Feb  7 11:03:50 2012
Return-Path: <fanf2@hermes.cam.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 9983221F879A for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2012 11:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.356
X-Spam-Level: 
X-Spam-Status: No, score=-6.356 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ig2qP-mwgYZP for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2012 11:03:49 -0800 (PST)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0AB21F8572 for <ietf@ietf.org>; Tue,  7 Feb 2012 11:03:44 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:41197) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1RuqKN-0002kF-ZC (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 07 Feb 2012 19:03:43 +0000
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1RuqKN-00061p-SR (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 07 Feb 2012 19:03:43 +0000
Date: Tue, 7 Feb 2012 19:03:43 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: james woodyatt <jhw@apple.com>
Subject: Re: ITC copped out on UTC again
In-Reply-To: <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com>
Message-ID: <alpine.LSU.2.00.1202071858230.6811@hermes-2.csi.cam.ac.uk>
References: <CAMm+LwgtUzw9GB1Mc=zQ3Fr_RPrsfy7d59HH6fstvsgTN=_C+g@mail.gmail.com> <CAJNg7V+56hgjyCptJLNr1YqrZ5d3y3VsJZCD+P999V4u1GourA@mail.gmail.com> <4F1D2DD7.6090103@tana.it> <CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com> <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:03:50 -0000

james woodyatt <jhw@apple.com> wrote:
>
> TAI has a fairly stable foundation in non-relativistic physics, which
> experience has shown to be somewhat resistant to the power of political
> bodies to modify at will,

Actually TAI depends a lot on relativity as well as quantum physics. For
example, it is supposed to match the rate of the SI second on the geoid
(which is roughly mean sea level). NIST's lab in Colorado is about a mile
high, so they have to apply a general relativistic rate correction to
their atomic clocks because of their gravitational potential.

> so it should be good enough for most running code on the Internet.

Except where that code needs UTC.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Viking, North Utsire: Southerly or southeasterly 5 to 7, occasionally gale 8
in Viking. Moderate or rough, becoming rough or very rough in Viking. Showers.
Good.

From john-ietf@jck.com  Tue Feb  7 11:13:07 2012
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 6EEAE21F888A for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2012 11:13:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7sQM1lTpIlp for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2012 11:13:06 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C0ED721F8887 for <ietf@ietf.org>; Tue,  7 Feb 2012 11:13:06 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1RuqPl-000Mu5-AY; Tue, 07 Feb 2012 14:09:17 -0500
Date: Tue, 07 Feb 2012 14:12:59 -0500
From: John C Klensin <john-ietf@jck.com>
To: james woodyatt <jhw@apple.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: ITC copped out on UTC again
Message-ID: <DAD5F12E89BD32997D8254AE@PST.JCK.COM>
In-Reply-To: <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com>
References: <CAMm+LwgtUzw9GB1Mc=zQ3Fr_RPrsfy7d59HH6fstvsgTN=_C+g@mail.gmail.com> <CAJNg7V+56hgjyCptJLNr1YqrZ5d3y3VsJZCD+P999V4u1GourA@mail.gmail.com> <4F1D2DD7.6090103@tana.it> <CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com> <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:13:07 -0000

--On Tuesday, February 07, 2012 10:45 -0800 james woodyatt
<jhw@apple.com> wrote:

>...
> TAI has a fairly stable foundation in non-relativistic
> physics, which experience has shown to be somewhat resistant
> to the power of political bodies to modify at will, so it
> should be good enough for most running code on the Internet.

You obviously have not been in enough meetings in which
proposals were put forth, by political types with the best of
intentions, for regulations to improve the Internet...
regulations that would work really well if the speed of light
were adjusted upward by 10% or so and/or could be dialed up and
back by a bit to match regulatory convenience. :-(

What was that about a free lunch?

     john




From stephen.farrell@cs.tcd.ie  Tue Feb  7 15:31:04 2012
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 49B4021F87AD; Tue,  7 Feb 2012 15:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YuE2cqYXXE4L; Tue,  7 Feb 2012 15:30:54 -0800 (PST)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 7847621F87A8; Tue,  7 Feb 2012 15:30:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 52420153C7E; Tue,  7 Feb 2012 23:30:52 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1328657451; bh=7dyf/TSB8odIM0 26tiSJ+9MHzypH7NOo9MuWtaskw1E=; b=UxDThKWzaCcKTbPyzZWSVtDj9CTHP7 ar+XJMk5bC7H+BMuCJlaVyyqGijmJ48K3Q+oaNXeEjun+mv/y5fvNP8AKOS0Wf/L 0jB5rmgZc5BiQc/iodOmX+Pk8xI4hbsScS0hmFI2CAhy/lP2PmS5nhEsqF/TmUHt rjU2RXJjbqJowf2mm4L6V7qJgsxVtlem2xsNQcFoZ38Kf5jAu6OoyIZ2KU8wBV6+ 1OgZIzEgf35jPBZmYZ2PrNiInhg2DJ4XkIxUNF7hvFDz5L6G+hH5rR2Z7nge2X7c 3zvTPCe+Uy4T545gvqcQYeOmI0gf3uT7dzhPZ/8hk2I2xF0OY5moeKgw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id zsRL5zciEEGj; Tue,  7 Feb 2012 23:30:51 +0000 (GMT)
Received: from [10.87.48.9] (unknown [86.42.18.155]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id BFB40153C7D; Tue,  7 Feb 2012 23:30:51 +0000 (GMT)
Message-ID: <4F31B427.4090402@cs.tcd.ie>
Date: Tue, 07 Feb 2012 23:30:47 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com>
In-Reply-To: <20120207225848.10346.42650.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg-secretary@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:31:04 -0000

This is pretty good already. Some additional FAQs I'd
suggest below. Feel free to take 'em or leave 'em, I'll
not be upset.

- "Anyone found a cheaper hotel option?" In addition to the
main and backup hotels, the reality is that some IETF attendees
prefer to stay elsewhere. If there are things worth recommending
about that, people will be interested, esp. in cost and flocking
together.

- If there's any crazy hotel booking rules related to the main
or backup hotels, additional explanation is usually useful

3.1: - maybe add "non flight options" sometimes places are
drivable or accessible via train for enough attendees to be
noteworthy

3.1.1.1 - where to find the taxi rank at the airport

3.1.1 - commuting info for those not in main hotels, incl. e.g.
mass transit daily/weekly tickets etc. routes

3.2.1 - places to get a grab'n'go sandwich etc.

3.3 - local etiquette maybe, but I can't think of a good
example that wouldn't insult somebody:-)

Cheers,
S.

On 02/07/2012 10:58 PM, The IESG wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IETF meeting attendees' Frequently Asked (travel) Questions'
>    <draft-george-travel-faq-03.txt>  as an 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 2012-03-06. 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 attempts to provide a list of the common Frequently
>     Asked Questions (FAQs) that IETF meeting attendees often ask
>     regarding travel logistics and local information.  It is intended to
>     assist those who are willing to provide local information, so that if
>     they wish to pre-populate answers to some or all of these questions
>     either in the IETF Wiki or a meeting-specific site, they have a
>     reasonably complete list of ideas to draw from.  It is not meant as a
>     list of required information that the host or secretariat needs to
>     provide, merely as a guideline.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-george-travel-faq/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-george-travel-faq/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>

From daedulus@btconnect.com  Wed Feb  8 01:55:41 2012
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 3ABEF21F8567; Wed,  8 Feb 2012 01:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jYZjAxOODpj2; Wed,  8 Feb 2012 01:55:40 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id 6961621F85D9; Wed,  8 Feb 2012 01:55:38 -0800 (PST)
Received: from host86-163-138-100.range86-163.btcentralplus.com (HELO pc6) ([86.163.138.100]) by c2bthomr10.btconnect.com with SMTP id GFV18413; Wed, 08 Feb 2012 09:55:35 +0000 (GMT)
Message-ID: <003d01cce63f$7041f280$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com> <4F31B427.4090402@cs.tcd.ie>
Subject: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC
Date: Wed, 8 Feb 2012 09:55:39 +0100
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-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4F324697.0070, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.1.30.73017:17:7.586, ip=86.163.138.100, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4F324698.011F,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: The IESG <iesg-secretary@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 09:55:41 -0000

----- Original Message ----- 
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: <ietf@ietf.org>
Cc: "The IESG" <iesg-secretary@ietf.org>
Sent: Wednesday, February 08, 2012 12:30 AM
> 
> This is pretty good already. Some additional FAQs I'd
> suggest below. Feel free to take 'em or leave 'em, I'll
> not be upset.
> 
> - "Anyone found a cheaper hotel option?" In addition to the
> main and backup hotels, the reality is that some IETF attendees
> prefer to stay elsewhere. If there are things worth recommending
> about that, people will be interested, esp. in cost and flocking
> together.
> 
> - If there's any crazy hotel booking rules related to the main
> or backup hotels, additional explanation is usually useful
> 
> 3.1: - maybe add "non flight options" sometimes places are
> drivable or accessible via train for enough attendees to be
> noteworthy
> 
> 3.1.1.1 - where to find the taxi rank at the airport
> 
> 3.1.1 - commuting info for those not in main hotels, incl. e.g.
> mass transit daily/weekly tickets etc. routes
> 
> 3.2.1 - places to get a grab'n'go sandwich etc.
> 
> 3.3 - local etiquette maybe, but I can't think of a good
> example that wouldn't insult somebody:-)

Which motion of the head means yes, and which means no?

Tom Petch

> 
> Cheers,
> S.
> 
> On 02/07/2012 10:58 PM, The IESG wrote:
> >
> > The IESG has received a request from an individual submitter to consider
> > the following document:
> > - 'IETF meeting attendees' Frequently Asked (travel) Questions'
> >    <draft-george-travel-faq-03.txt>  as an 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 2012-03-06. 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 attempts to provide a list of the common Frequently
> >     Asked Questions (FAQs) that IETF meeting attendees often ask
> >     regarding travel logistics and local information.  It is intended to
> >     assist those who are willing to provide local information, so that if
> >     they wish to pre-populate answers to some or all of these questions
> >     either in the IETF Wiki or a meeting-specific site, they have a
> >     reasonably complete list of ideas to draw from.  It is not meant as a
> >     list of required information that the host or secretariat needs to
> >     provide, merely as a guideline.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-george-travel-faq/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-george-travel-faq/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> >
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From joelja@bogus.com  Wed Feb  8 07:37:10 2012
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 1F80B21F8701; Wed,  8 Feb 2012 07:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.849
X-Spam-Level: 
X-Spam-Status: No, score=-101.849 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFwByYVouxow; Wed,  8 Feb 2012 07:37:09 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 95AF021F8700; Wed,  8 Feb 2012 07:37:09 -0800 (PST)
Received: from Joels-MacBook-Pro.local (115.sub-166-250-77.myvzw.com [166.250.77.115]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q18Fb5Ot039504 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 8 Feb 2012 15:37:06 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F329696.6000505@bogus.com>
Date: Wed, 08 Feb 2012 07:36:54 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
In-Reply-To: <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 08 Feb 2012 15:37:07 +0000 (UTC)
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:37:10 -0000

On 2/8/12 05:54 , Lorenzo Colitti wrote:
> On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@cisco.com
> <mailto:fred@cisco.com>> wrote:
> 
>     The IESG again decided it needed a revised draft, and that draft -
>     in large part, a rewrite - arrived in October. v6ops had a second
>     WGLC, in which you again declined to comment, although you may have
>     seen Lorenzo's comments, which were picked up in a November version
>     of the draft. Ralph and Jari finally cleared their "discuss" ballots
>     a couple of weeks ago, and we are having a second IETF last call.
> 
>     I'd like to understand your objective here. I know that you don't
>     care for the draft, and at least at one point took it as a
>     somewhat-personal attack. Is your objective to prevent the draft's
>     publication entirely, or do you think that there is value in
>     publishing it given a productive response to this comment? At what
>     point are you willing to either participate in the public dialog or
>     choose to not comment at all?
> 
> 
> Ok, let me see if I can rephrase Erik's objection.
> 
> The draft needs to take World IPv6 Launch into account, because it's a
> key piece of the puzzle.
> 
> We can't publish an RFC on how to transition content to IPv6 if the RFC
> ignores the event when 5 of the top 10 websites in the world (and
> probably many more) will permanently enable IPv6 for everyone.

Ops is not marketing.

If you're saying some flag day makes the contents of the document no
longer operationally relevant after a given date, I'll take the point
but disagree.

The document in it's present form has a wider audience than the
operators at 5 of the ton 10 websites.

> Cheers,
> Lorenzo
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From fred@cisco.com  Wed Feb  8 08:02:56 2012
Return-Path: <fred@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 2BF2F21F85DF; Wed,  8 Feb 2012 08:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.151
X-Spam-Level: 
X-Spam-Status: No, score=-106.151 tagged_above=-999 required=5 tests=[AWL=-0.153, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFoL6LLlIstJ; Wed,  8 Feb 2012 08:02:55 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 695BB21F85D6; Wed,  8 Feb 2012 08:02:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3757; q=dns/txt; s=iport; t=1328716975; x=1329926575; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=ZaC+ql16a2rAMnYFUS1q0vo8Jzj6hwbyq9/wG5jh1QA=; b=FqA1BYSknvWiVlzglmrQp5h7IWkXg1AyKCtWQya+7UEHrYiKt0/K0ejW OtcwihL460nLWVqVNR9pZlEqx/kEJYqrO2nbt4BU9yum08nVEHl7H3yLs /zyrz4OUdousE0txTcJ0bpvAX4vrmSy5vT4Ke6WL4oUBvkETBa5NeUIfZ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOebMk+rRDoH/2dsb2JhbABDr3CBB4FyAQEBAwESAWYFCwsEFBUOC1cGEyKHWpt6AZcAi1MCDxETAQgFAwMJDYMPBRgCCwIFQSIVGwQRgkZjBIhGjGeFWI0m
X-IronPort-AV: E=Sophos;i="4.73,384,1325462400"; d="scan'208,217";a="29317827"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 08 Feb 2012 16:02:55 +0000
Received: from Freds-Computer.local (sjc-vpn2-244.cisco.com [10.21.112.244]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q18G2Qas004363; Wed, 8 Feb 2012 16:02:54 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 08 Feb 2012 08:02:55 -0800
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 08 Feb 2012 08:02:55 -0800
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
Date: Wed, 8 Feb 2012 08:02:54 -0800
Message-Id: <2381D869-D36C-4817-BE5C-32A65813EB38@cisco.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-16-369940344
Cc: Erik Kline <ek@google.com>, v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:02:56 -0000

--Apple-Mail-16-369940344
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

What specifically would you like changed in the draft? Can you suggest =
text?=20

On Feb 8, 2012, at 5:54 AM, Lorenzo Colitti wrote:

> On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@cisco.com> wrote:
> The IESG again decided it needed a revised draft, and that draft - in =
large part, a rewrite - arrived in October. v6ops had a second WGLC, in =
which you again declined to comment, although you may have seen =
Lorenzo's comments, which were picked up in a November version of the =
draft. Ralph and Jari finally cleared their "discuss" ballots a couple =
of weeks ago, and we are having a second IETF last call.
>=20
> I'd like to understand your objective here. I know that you don't care =
for the draft, and at least at one point took it as a somewhat-personal =
attack. Is your objective to prevent the draft's publication entirely, =
or do you think that there is value in publishing it given a productive =
response to this comment? At what point are you willing to either =
participate in the public dialog or choose to not comment at all?
>=20
> Ok, let me see if I can rephrase Erik's objection.
>=20
> The draft needs to take World IPv6 Launch into account, because it's a =
key piece of the puzzle.
>=20
> We can't publish an RFC on how to transition content to IPv6 if the =
RFC ignores the event when 5 of the top 10 websites in the world (and =
probably many more) will permanently enable IPv6 for everyone.
>=20
> Cheers,
> Lorenzo


--Apple-Mail-16-369940344
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">What specifically would you like changed in the draft? Can you suggest text?&nbsp;<div><br><div><div>On Feb 8, 2012, at 5:54 AM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Sat, Feb 4, 2012 at 01:35, Fred Baker <span dir="ltr">&lt;<a href="mailto:fred@cisco.com">fred@cisco.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 class="im">The IESG again decided it needed a revised draft, and that draft - in large part, a rewrite - arrived in October. v6ops had a second WGLC, in which you again declined to comment, although you may have seen Lorenzo's comments, which were picked up in a November version of the draft. Ralph and Jari finally cleared their "discuss" ballots a couple of weeks ago, and we are having a second IETF last call.</div>


<br>
I'd like to understand your objective here. I know that you don't care for the draft, and at least at one point took it as a somewhat-personal attack. Is your objective to prevent the draft's publication entirely, or do you think that there is value in publishing it given a productive response to this comment? At what point are you willing to either participate in the public dialog or choose to not comment at all?</blockquote>

<div><br></div><div>Ok, let me see if I can rephrase Erik's objection.</div><div><br></div><div>The draft needs to take World IPv6 Launch into account, because it's a key piece of the puzzle.</div><div><br></div>
<div>
We can't publish an RFC on how to transition content to IPv6 if the RFC ignores the event when 5 of the top 10 websites in the world (and probably many more) will permanently enable IPv6 for everyone.</div><div><br></div>

<div>Cheers,</div><div>Lorenzo</div></div>
</blockquote></div><br></div></body></html>
--Apple-Mail-16-369940344--

From lorenzo@google.com  Wed Feb  8 05:54:52 2012
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 33D5221F865D for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 05:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSMOZuPJGHVL for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 05:54:51 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id A03DD21F8659 for <ietf@ietf.org>; Wed,  8 Feb 2012 05:54:51 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so1023544obb.31 for <ietf@ietf.org>; Wed, 08 Feb 2012 05:54:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:x-system-of-record:content-type; bh=ENct9zuBM/KtSoi788U61wDlvFKkk+3auCus6P3AbdA=; b=bm2E4v5g3eYiOW9JD9yTZW7XYWzx9DJSH8no7P65BLiu3+8FAJOky5Hii/LQXZJoTh +3pKmX88U/MGCtwsTwZSAlTbqMKqhHvXzVT3XvLpNc8NW34eceQtgBU5jTjwy+xrB7KY ugCW6TKc9KtWWdfGQvObmQI1cecKPsiUBKtE0=
Received: by 10.182.8.69 with SMTP id p5mr25761758oba.28.1328709291346; Wed, 08 Feb 2012 05:54:51 -0800 (PST)
Received: by 10.182.8.69 with SMTP id p5mr25761741oba.28.1328709291188; Wed, 08 Feb 2012 05:54:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.81.71 with HTTP; Wed, 8 Feb 2012 05:54:31 -0800 (PST)
In-Reply-To: <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 8 Feb 2012 22:54:31 +0900
Message-ID: <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
To: Fred Baker <fred@cisco.com>
X-System-Of-Record: true
Content-Type: multipart/alternative; boundary=f46d0444ec4b4fa32b04b8743d3a
X-Mailman-Approved-At: Wed, 08 Feb 2012 08:10:38 -0800
Cc: Erik Kline <ek@google.com>, v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:54:52 -0000

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

On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@cisco.com> wrote:

> The IESG again decided it needed a revised draft, and that draft - in
> large part, a rewrite - arrived in October. v6ops had a second WGLC, in
> which you again declined to comment, although you may have seen Lorenzo's
> comments, which were picked up in a November version of the draft. Ralph
> and Jari finally cleared their "discuss" ballots a couple of weeks ago, and
> we are having a second IETF last call.
>
> I'd like to understand your objective here. I know that you don't care for
> the draft, and at least at one point took it as a somewhat-personal attack.
> Is your objective to prevent the draft's publication entirely, or do you
> think that there is value in publishing it given a productive response to
> this comment? At what point are you willing to either participate in the
> public dialog or choose to not comment at all?


Ok, let me see if I can rephrase Erik's objection.

The draft needs to take World IPv6 Launch into account, because it's a key
piece of the puzzle.

We can't publish an RFC on how to transition content to IPv6 if the RFC
ignores the event when 5 of the top 10 websites in the world (and probably
many more) will permanently enable IPv6 for everyone.

Cheers,
Lorenzo

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

<div class=3D"gmail_quote">On Sat, Feb 4, 2012 at 01:35, Fred Baker <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:fred@cisco.com">fred@cisco.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 class=3D"im">The IESG again decided it needed a revised draft, and tha=
t draft - in large part, a rewrite - arrived in October. v6ops had a second=
 WGLC, in which you again declined to comment, although you may have seen L=
orenzo&#39;s comments, which were picked up in a November version of the dr=
aft. Ralph and Jari finally cleared their &quot;discuss&quot; ballots a cou=
ple of weeks ago, and we are having a second IETF last call.</div>


<br>
I&#39;d like to understand your objective here. I know that you don&#39;t c=
are for the draft, and at least at one point took it as a somewhat-personal=
 attack. Is your objective to prevent the draft&#39;s publication entirely,=
 or do you think that there is value in publishing it given a productive re=
sponse to this comment? At what point are you willing to either participate=
 in the public dialog or choose to not comment at all?</blockquote>

<div><br></div><div>Ok, let me see if I can rephrase Erik&#39;s objection.<=
/div><div><br></div><div>The draft needs to take World IPv6 Launch into acc=
ount, because it&#39;s a key piece of the puzzle.</div><div><br></div>
<div>
We can&#39;t publish an RFC on how to transition content to IPv6 if the RFC=
 ignores the event when 5 of the top 10 websites in the world (and probably=
 many more) will permanently enable IPv6 for everyone.</div><div><br></div>

<div>Cheers,</div><div>Lorenzo</div></div>

--f46d0444ec4b4fa32b04b8743d3a--

From fgont@si6networks.com  Wed Feb  8 06:24:37 2012
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 A220121F85DD; Wed,  8 Feb 2012 06:24:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qX-EhpNqnj6j; Wed,  8 Feb 2012 06:24:37 -0800 (PST)
Received: from srv01.bbserve.nl (unknown [IPv6:2a02:27f8:1025:18::232]) by ietfa.amsl.com (Postfix) with ESMTP id D6AB721F85F7; Wed,  8 Feb 2012 06:24:36 -0800 (PST)
Received: from [190.48.215.115] (helo=[192.168.123.102]) by srv01.bbserve.nl with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <fgont@si6networks.com>) id 1Rv8Rk-0000d3-5X; Wed, 08 Feb 2012 15:24:32 +0100
Message-ID: <4F31EFFC.5020402@si6networks.com>
Date: Wed, 08 Feb 2012 00:46:04 -0300
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16
MIME-Version: 1.0
To: ietf@ietf.org, igor@yahoo-inc.com, jjaeggli@zynga.com,  Warren Kumari <warren@kumari.net>
Subject: Re: Last Call: <draft-ietf-v6ops-v6nd-problems-04.txt> (Operational Neighbor Discovery Problems) to Informational RFC
References: <20120206150214.5445.40209.idtracker@ietfa.amsl.com>
In-Reply-To: <20120206150214.5445.40209.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 08 Feb 2012 08:10:38 -0800
Cc: v6ops@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:24:37 -0000

Folks,

I've reviewed the aforementioned document.

These are my comments:

** Technical: **

* Section 6.1:

It should be noted that the proposed mitigations makes address scans easier.

Also, the text currently says "and may not interact well with networks
using [RFC4862]". -- I'd argue that "it does not work with networks
using [RFC4862]".


* Section 7:

I believe that probably the most important implementation advice with
respect to the issue being discussed is missing (at least explicitly).
It could be stated as follows:

"NDP implementations should limit the number of Neighbor Cache entries
that are in the INCOMPLETE state. The aforementioned limit should be
much lower than the global limit on the total number of Neighbor Cache
entries. Since the attack discussed in this document is based on
triggering address resolution for non-existing nodes, limiting the
number of entries in the Neighbor Cache that are in the INCOMPLETE state
will mitigate the aforementioned attack, while still allowing ongoing
communications with "known" nodes to continue unnafected".

(feel free to use the text verbatim or modify as necessary)


* Section 7.1, bullet "4":

This paragraph is at least a bit vague. I'm not sure if you're referring
to something similar to what I've mentioned above -- but it doesn't read
like that.

You may want to replace this paragraph with the one I provided above, or
at least clarify it.


* Section 7.2:
   On implementations in which requests to NDP are submitted via a
   single queue, router vendors SHOULD provide operators with means to
   control both the rate of link-layer address resolution requests
   placed into the queue and the size of the queue.

My understanding is that being an "Informational" document, you should
s/SHOULD/should/ -- i.e., remove the RFC2119 language in the recommendation.



** Editorial: **

* Section 3:
      packets.  In higher-end routers, the forwarding plane is typically
      implemented in specialized hardware optimized for performance.
      Steps in the forwarding process include determining the correct
      outgoing interface for a packet, decrementing its Time To Live
      (TTL), verifying and updating the checksum, placing the correct
      link-layer header on the packet, and forwarding it.

Maybe this text should reflect IPv6, rather than IPv4 (i..e, s/TTL/Hop
Limit/, and remove the checksum bit)


** Nits: **

* Abstract:

s/DOS/DoS/, (there are a few instances of this elsewhere) and expand the
acronym the first time you use it.


* Section 1.1:

s/IPV6/IPv6/

* Section 2:

Missing space in "memoryand replaces existing "

* Section 4:

   addresses (and in many cases becomes unable to perform maintenance of
   existing entries in the neighbor cache, and unable to answer Neighbor
   Solicitation).

s/Solicitation/Solicitations/

* Section 7.2:

s/Neighbour/Neighbor/


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




From rcallon@juniper.net  Wed Feb  8 08:23:07 2012
Return-Path: <rcallon@juniper.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 940D021F859F; Wed,  8 Feb 2012 08:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.321
X-Spam-Level: 
X-Spam-Status: No, score=-106.321 tagged_above=-999 required=5 tests=[AWL=-0.322, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XxTPnKEuAZj9; Wed,  8 Feb 2012 08:23:06 -0800 (PST)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE7721F85B1; Wed,  8 Feb 2012 08:23:06 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTzKhZqX/3xO7QY8luEJCnJ+9v2jfy3zS@postini.com; Wed, 08 Feb 2012 08:23:06 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 8 Feb 2012 08:20:26 -0800
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by p-cldfe01-hq.jnpr.net (172.24.192.59) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 8 Feb 2012 08:20:26 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 8 Feb 2012 11:20:25 -0500
From: Ross Callon <rcallon@juniper.net>
To: t.petch <daedulus@btconnect.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 8 Feb 2012 11:20:20 -0500
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to	Informational RFC
Thread-Topic: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to	Informational RFC
Thread-Index: AczmR9W84Vbsn+4dQ6G2sF5h1XTDiwANZfyw
Message-ID: <DF7F294AF4153D498141CBEFADB17704C709741770@EMBX01-WF.jnpr.net>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com> <4F31B427.4090402@cs.tcd.ie> <003d01cce63f$7041f280$4001a8c0@gateway.2wire.net>
In-Reply-To: <003d01cce63f$7041f280$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: e4081efb-6d29-443c-8708-750833aec629
Cc: The IESG <iesg-secretary@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:23:07 -0000

Also useful: What levels of tips are normally expected in what circumstance=
s (in restaurants, taxi's, etc..).=20

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t.p=
etch
Sent: Wednesday, February 08, 2012 3:56 AM
To: Stephen Farrell; ietf@ietf.org
Cc: The IESG
Subject: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingatten=
dees' Frequently Asked (travel) Questions) to Informational RFC

----- Original Message -----=20
From: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
To: <ietf@ietf.org>
Cc: "The IESG" <iesg-secretary@ietf.org>
Sent: Wednesday, February 08, 2012 12:30 AM
>=20
> This is pretty good already. Some additional FAQs I'd
> suggest below. Feel free to take 'em or leave 'em, I'll
> not be upset.
>=20
> - "Anyone found a cheaper hotel option?" In addition to the
> main and backup hotels, the reality is that some IETF attendees
> prefer to stay elsewhere. If there are things worth recommending
> about that, people will be interested, esp. in cost and flocking
> together.
>=20
> - If there's any crazy hotel booking rules related to the main
> or backup hotels, additional explanation is usually useful
>=20
> 3.1: - maybe add "non flight options" sometimes places are
> drivable or accessible via train for enough attendees to be
> noteworthy
>=20
> 3.1.1.1 - where to find the taxi rank at the airport
>=20
> 3.1.1 - commuting info for those not in main hotels, incl. e.g.
> mass transit daily/weekly tickets etc. routes
>=20
> 3.2.1 - places to get a grab'n'go sandwich etc.
>=20
> 3.3 - local etiquette maybe, but I can't think of a good
> example that wouldn't insult somebody:-)

Which motion of the head means yes, and which means no?

Tom Petch

>=20
> Cheers,
> S.
>=20
> On 02/07/2012 10:58 PM, The IESG wrote:
> >
> > The IESG has received a request from an individual submitter to conside=
r
> > the following document:
> > - 'IETF meeting attendees' Frequently Asked (travel) Questions'
> >    <draft-george-travel-faq-03.txt>  as an 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 2012-03-06. 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 attempts to provide a list of the common Frequently
> >     Asked Questions (FAQs) that IETF meeting attendees often ask
> >     regarding travel logistics and local information.  It is intended t=
o
> >     assist those who are willing to provide local information, so that =
if
> >     they wish to pre-populate answers to some or all of these questions
> >     either in the IETF Wiki or a meeting-specific site, they have a
> >     reasonably complete list of ideas to draw from.  It is not meant as=
 a
> >     list of required information that the host or secretariat needs to
> >     provide, merely as a guideline.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-george-travel-faq/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-george-travel-faq/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> >
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From randy@psg.com  Wed Feb  8 10:06:14 2012
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 A5F4821F86AD for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 10:06:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0nD+w1kPmQBO for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 10:06:14 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4797221F8659 for <ietf@ietf.org>; Wed,  8 Feb 2012 10:06:14 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RvBuI-0004Zr-4A for ietf@ietf.org; Wed, 08 Feb 2012 18:06:14 +0000
Date: Wed, 08 Feb 2012 10:06:13 -0800
Message-ID: <m2obt9yzca.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF	meetingattendees' Frequently Asked (travel) Questions) to	Informational	RFC
In-Reply-To: <DF7F294AF4153D498141CBEFADB17704C709741770@EMBX01-WF.jnpr.net>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com> <4F31B427.4090402@cs.tcd.ie> <003d01cce63f$7041f280$4001a8c0@gateway.2wire.net> <DF7F294AF4153D498141CBEFADB17704C709741770@EMBX01-WF.jnpr.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:06:14 -0000

perhaps this document should not attempt to duplicate Rough Guide or
Lonely Planet?

randy

From adrian@olddog.co.uk  Wed Feb  8 12:36:35 2012
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 A745411E809B for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 12:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gu6ybn+03WRf for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 12:36:35 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id E8D6811E80AE for <ietf@ietf.org>; Wed,  8 Feb 2012 12:36:34 -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 q18KaX5X018247;  Wed, 8 Feb 2012 20:36:33 GMT
Received: from 950129200 (cust.static.46-14-88-124.swisscomdata.ch [46.14.88.124]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id q18KaNWR018194 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 8 Feb 2012 20:36:29 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Randy Bush'" <randy@psg.com>
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC
Date: Wed, 8 Feb 2012 20:36:20 -0000
Message-ID: <088401cce6a1$585413d0$08fc3b70$@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: Aczmnkt0d41cb9RjQO6qIlVdlGQk8Q==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:36:35 -0000

I find Fodor far more pleasant for its antiquated interests.

Michelin is OK if you like your culture graded through a French filter.

Hang on! Shouldn't we also have a Trip advisor style points count?

> perhaps this document should not attempt to duplicate Rough Guide or
> Lonely Planet? 
> 
> randy


From marka@isc.org  Wed Feb  8 13:06:05 2012
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 5996D21F851B; Wed,  8 Feb 2012 13:06:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.261
X-Spam-Level: 
X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kfuKXn+CkxGX; Wed,  8 Feb 2012 13:06:04 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id B83C121F8508; Wed,  8 Feb 2012 13:06:04 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 566A6C944A; Wed,  8 Feb 2012 21:05:51 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:3981:7370:f4ed:515c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id EDD4F216C6A; Wed,  8 Feb 2012 21:05:50 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 18A0D1D0458C; Thu,  9 Feb 2012 08:05:48 +1100 (EST)
To: Lorenzo Colitti <lorenzo@google.com>
From: Mark Andrews <marka@isc.org>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
In-reply-to: Your message of "Wed, 08 Feb 2012 22:54:31 +0900." <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>
Date: Thu, 09 Feb 2012 08:05:48 +1100
Message-Id: <20120208210548.18A0D1D0458C@drugs.dv.isc.org>
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:06:05 -0000

In message <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com>,
 Lorenzo Colitti writes:
> On Sat, Feb 4, 2012 at 01:35, Fred Baker <fred@cisco.com> wrote:
> 
> > The IESG again decided it needed a revised draft, and that draft - in
> > large part, a rewrite - arrived in October. v6ops had a second WGLC, in
> > which you again declined to comment, although you may have seen Lorenzo's
> > comments, which were picked up in a November version of the draft. Ralph
> > and Jari finally cleared their "discuss" ballots a couple of weeks ago, and
> > we are having a second IETF last call.
> >
> > I'd like to understand your objective here. I know that you don't care for
> > the draft, and at least at one point took it as a somewhat-personal attack.
> > Is your objective to prevent the draft's publication entirely, or do you
> > think that there is value in publishing it given a productive response to
> > this comment? At what point are you willing to either participate in the
> > public dialog or choose to not comment at all?
> 
> 
> Ok, let me see if I can rephrase Erik's objection.
> 
> The draft needs to take World IPv6 Launch into account, because it's a key
> piece of the puzzle.
> 
> We can't publish an RFC on how to transition content to IPv6 if the RFC
> ignores the event when 5 of the top 10 websites in the world (and probably
> many more) will permanently enable IPv6 for everyone.
> 
> Cheers,
> Lorenzo

World IPv6 day just means Google is at 5.5 now and will go to
5.6/5.7.  It really does not change anything.  The decision to
whitelist is a subjective one, not a objective one.  Similarly the
decision to stop whitelisting is also a subjective one.

While I, and I suspect most of the list, think that whitelisting
should no longer be needed that isn't our call to make.  All we can
do is encourage people to not whitelist by running dual stack
services without using whitelisting.

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

From smb@cs.columbia.edu  Wed Feb  8 13:41:40 2012
Return-Path: <smb@cs.columbia.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 1CF1321F85A7 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 13:41:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.82
X-Spam-Level: 
X-Spam-Status: No, score=-3.82 tagged_above=-999 required=5 tests=[AWL=-1.221,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbDsxeTYXucG for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 13:41:39 -0800 (PST)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id 49EC821F858D for <ietf@ietf.org>; Wed,  8 Feb 2012 13:41:39 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q18LfaGv007402 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 8 Feb 2012 16:41:36 -0500 (EST)
Subject: Re: ITC copped out on UTC again
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <DAD5F12E89BD32997D8254AE@PST.JCK.COM>
Date: Wed, 8 Feb 2012 16:41:35 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <9488D5C3-452C-4E9E-931E-0521CD6CD934@cs.columbia.edu>
References: <CAMm+LwgtUzw9GB1Mc=zQ3Fr_RPrsfy7d59HH6fstvsgTN=_C+g@mail.gmail.com> <CAJNg7V+56hgjyCptJLNr1YqrZ5d3y3VsJZCD+P999V4u1GourA@mail.gmail.com> <4F1D2DD7.6090103@tana.it> <CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com> <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com> <DAD5F12E89BD32997D8254AE@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1251.1)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:41:40 -0000

On Feb 7, 2012, at 2:12 59PM, John C Klensin wrote:

> 
> 
> --On Tuesday, February 07, 2012 10:45 -0800 james woodyatt
> <jhw@apple.com> wrote:
> 
>> ...
>> TAI has a fairly stable foundation in non-relativistic
>> physics, which experience has shown to be somewhat resistant
>> to the power of political bodies to modify at will, so it
>> should be good enough for most running code on the Internet.
> 
> You obviously have not been in enough meetings in which
> proposals were put forth, by political types with the best of
> intentions, for regulations to improve the Internet...
> regulations that would work really well if the speed of light
> were adjusted upward by 10% or so and/or could be dialed up and
> back by a bit to match regulatory convenience. :-(
> 
> What was that about a free lunch?


Yes.  A line I heard recently (from someone else whom I think is
on this list) is that when you tell a politician that something
violates the laws of physics, that statement is taken as a negotiating
position.

		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From brian.e.carpenter@gmail.com  Wed Feb  8 14:47:07 2012
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 3C28111E80AA for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 14:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.501
X-Spam-Level: 
X-Spam-Status: No, score=-103.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G46DDhZ5l9uk for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 14:47:06 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 64DA311E8083 for <ietf@ietf.org>; Wed,  8 Feb 2012 14:47:06 -0800 (PST)
Received: by eaal12 with SMTP id l12so350516eaa.31 for <ietf@ietf.org>; Wed, 08 Feb 2012 14:47:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FQQmPluRqmB4ibQ3a3j3dd/PhMAu15o8HksHMF6WkK4=; b=g+xwqZGYIe9hnw58VmvR/EoObSgjMeieUwZR7+BgFqggiEhOnoyvExMM4JOgf5X/4B GE6q31IQPeXkTLrQkC6hEhfZkGh3HjME69GOgdRAerY/cLImEh0CIdSdmryG4R8oP9B6 Jh8QIxUkUSpELdB1WkltL6ZVyjzQWTMnfhFe4=
Received: by 10.14.127.195 with SMTP id d43mr1077521eei.102.1328741225456; Wed, 08 Feb 2012 14:47:05 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id a58sm2322723eeb.8.2012.02.08.14.47.02 (version=SSLv3 cipher=OTHER); Wed, 08 Feb 2012 14:47:04 -0800 (PST)
Message-ID: <4F32FB5F.4020206@gmail.com>
Date: Thu, 09 Feb 2012 11:46:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: ITC copped out on UTC again
References: <CAMm+LwgtUzw9GB1Mc=zQ3Fr_RPrsfy7d59HH6fstvsgTN=_C+g@mail.gmail.com>	<CAJNg7V+56hgjyCptJLNr1YqrZ5d3y3VsJZCD+P999V4u1GourA@mail.gmail.com>	<4F1D2DD7.6090103@tana.it>	<CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com>	<1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com>	<DAD5F12E89BD32997D8254AE@PST.JCK.COM> <9488D5C3-452C-4E9E-931E-0521CD6CD934@cs.columbia.edu>
In-Reply-To: <9488D5C3-452C-4E9E-931E-0521CD6CD934@cs.columbia.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:47:07 -0000

On 2012-02-09 10:41, Steven Bellovin wrote:
> On Feb 7, 2012, at 2:12 59PM, John C Klensin wrote:
> 
>>
>> --On Tuesday, February 07, 2012 10:45 -0800 james woodyatt
>> <jhw@apple.com> wrote:
>>
>>> ...
>>> TAI has a fairly stable foundation in non-relativistic
>>> physics, which experience has shown to be somewhat resistant
>>> to the power of political bodies to modify at will, so it
>>> should be good enough for most running code on the Internet.
>> You obviously have not been in enough meetings in which
>> proposals were put forth, by political types with the best of
>> intentions, for regulations to improve the Internet...
>> regulations that would work really well if the speed of light
>> were adjusted upward by 10% or so and/or could be dialed up and
>> back by a bit to match regulatory convenience. :-(
>>
>> What was that about a free lunch?
> 
> 
> Yes.  A line I heard recently (from someone else whom I think is
> on this list) is that when you tell a politician that something
> violates the laws of physics, that statement is taken as a negotiating
> position.

I don't see the problem. An experiment in Italy has observed
super-luminal neutrinos, and a somewhat unlikely violation of
the 2nd law of thermodynamics would allow pigs to fly and all
NTP servers to update themselves simultaneously. Clearly these
are matters that any self-respecting politician could use in
negotiation.

I am much more worried about
http://internetsociety.org/events/internet-society-events/world-conference-international-telecommunications
than about UTC.

     Brian

From yaacov.weingarten@nsn.com  Wed Feb  8 23:37:18 2012
Return-Path: <yaacov.weingarten@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3E6E21E800E for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 23:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8zfBwLXTsv66 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2012 23:37:18 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 07D3621F8591 for <ietf@ietf.org>; Wed,  8 Feb 2012 23:37:17 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q197bFU1021450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Thu, 9 Feb 2012 08:37:15 +0100
Received: from DEMUEXC047.nsn-intra.net ([10.159.32.93]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q197bFFd026198 for <ietf@ietf.org>; Thu, 9 Feb 2012 08:37:15 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC047.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 9 Feb 2012 08:37:15 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCE6FD.A4E61116"
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC
Date: Thu, 9 Feb 2012 08:37:14 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C013FEDEE@DEMUEXC013.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meetingattendees' Frequently Asked (travel) Questions) to Informational RFC
Thread-Index: Aczm/aQtfGuicoJnQiG9oekDIA2g2A==
From: "Weingarten, Yaacov (NSN - IL/Hod HaSharon)" <yaacov.weingarten@nsn.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 09 Feb 2012 07:37:15.0189 (UTC) FILETIME=[A4BD5E50:01CCE6FD]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 4202
X-purgate-ID: 151667::1328773035-00007EDF-3839FDEC/0-0/0-0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:37:19 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCE6FD.A4E61116
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

One more question for either Section 3.1 (or Security Considerations
;-))
How much time does Airport check-in take including getting through the
security lines?  How much time before take-off should one plan on
leaving the hotel/site?

Best regards,
Yaacov Weingarten
Nokia Siemens Networks
Industry Environment, PTE
ph#:  +972-9-775 1827
mob#: +972-54-220 0977



------_=_NextPart_001_01CCE6FD.A4E61116
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>RE: Last Call: &lt;draft-george-travel-faq-03.txt&gt; (IETF =
meetingattendees' Frequently Asked (travel) Questions) to Informational =
RFC</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Hi,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">One more =
question for</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">either Section 3.1 (or Security Considerations =
;-))</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">How much =
time does Airport check-in take incl</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">uding getting through the =
security lines?&nbsp; How much time before take-off should one plan on =
leaving the</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"> <FONT SIZE=3D2 =
FACE=3D"Arial">hotel/site?</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Best =
regards,</FONT></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"><B><I></I></B></SPAN><SPAN =
LANG=3D"en-us"><B><I></I></B></SPAN><B><I><SPAN =
LANG=3D"de-de"></SPAN></I></B><B><I><SPAN LANG=3D"de-de"><FONT =
COLOR=3D"#800080" FACE=3D"Lucida Calligraphy">Yaacov =
Weingarten</FONT></SPAN></I></B><SPAN LANG=3D"en-us"><B></B></SPAN><SPAN =
LANG=3D"en-us"><B></B></SPAN><B><SPAN LANG=3D"de-de"></SPAN></B></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Nokia Siemens Networks</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">Industry Environment, PTE</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">ph#:&nbsp;</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS"> +972-9-775 1827</FONT></SPAN><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN><SPAN =
LANG=3D"de-de"><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">mob#: +972-54-220 0977</FONT></SPAN><SPAN =
LANG=3D"en-us"></SPAN><SPAN LANG=3D"de-de"></SPAN></P>

<P DIR=3DLTR><SPAN LANG=3D"en-us"></SPAN></P>

</BODY>
</HTML>
------_=_NextPart_001_01CCE6FD.A4E61116--

From bortzmeyer@nic.fr  Thu Feb  9 05:04:45 2012
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 1967521F86B7; Thu,  9 Feb 2012 05:04:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-mJSEo5svPV; Thu,  9 Feb 2012 05:04:44 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4AB21F864E; Thu,  9 Feb 2012 05:04:44 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 5B6D01C00E1; Thu,  9 Feb 2012 14:04:43 +0100 (CET)
Received: by mx2.nic.fr (Postfix, from userid 500) id 46B751C00F5; Thu,  9 Feb 2012 14:04:43 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [IPv6:2001:67c:2218:9::4:163]) by mx2.nic.fr (Postfix) with ESMTP id 3329E1C00E1; Thu,  9 Feb 2012 14:04:43 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id 16DC8B38370; Thu,  9 Feb 2012 14:04:41 +0100 (CET)
Date: Thu, 9 Feb 2012 14:04:43 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IAB Chair <iab-chair@iab.org>
Subject: Re: IAB statement: "The interpretation of rules in the ICANN gTLD Applicant Guidebook"
Message-ID: <20120209130443.GA28346@nic.fr>
References: <053c01cce6ad$7f29fa90$7d7defb0$@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <053c01cce6ad$7f29fa90$7d7defb0$@iab.org>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.1.0-1-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Bogosity: No, tests=bogofilter, spamicity=0.000001, version=1.1.5
X-PMX-Version: 5.4.6.353000, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2012.2.9.125118
X-PerlMx-Spam: Gauge=IIIIIII, Probability=8%, Report='MULTIPLE_RCPTS 0.1, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, BODY_SIZE_800_899 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __USER_AGENT 0'
Cc: dnsop@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:04:45 -0000

On Wed, Feb 08, 2012 at 02:03:31PM -0800,
 IAB Chair <iab-chair@iab.org> wrote 
 a message of 116 lines which said:

> The IAB has issued a statement entitled "The interpretation of rules
> in the ICANN gTLD Applicant Guidebook".

This is a very bad statement. When work started on document
draft-liman-tld-names, there were no IDN TLD in the root and some
expressed concern that the digits (in their Punycode encoding) could
create a problem. Also, draft-liman-tld-names was disputed because it
created new rules (explicitely forbidding all-digits TLDs) without a
good reason. The document has fallen in disinterest and I'm quite
surprised to see it resurfacing now: we have IDN TLDs in the root for
a long time and the sky has not fallen.

I hope that ICANN will ignore this statement.

From lorenzo@google.com  Thu Feb  9 01:25:23 2012
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 A5F7421F86B3 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 01:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.846
X-Spam-Level: 
X-Spam-Status: No, score=-101.846 tagged_above=-999 required=5 tests=[AWL=-0.830, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DELqdo-cZyZi for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 01:25:22 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id B8DCC21F86B0 for <ietf@ietf.org>; Thu,  9 Feb 2012 01:25:22 -0800 (PST)
Received: by iagf6 with SMTP id f6so2682261iag.31 for <ietf@ietf.org>; Thu, 09 Feb 2012 01:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=foXKHPrx3LuDKdmXGmafHXaI8VY0+nJ/vLf6S5WS5Iw=; b=f/XwLXF71+j2Ed8hg1yybsJwHzNHrGw8eNMV43eVceHDWEpKjDK1SnnKKJ42373H8T Ms1ABfO4tUZ1n0p7i770ln0ro0lMFZ1/CRAHVL3kCQn1WqeyrobpLRAgnOcTMiKuChXU UrmJrn8G10GGCQbgruPkUTukx/LmGN2CirYdc=
Received: by 10.42.177.133 with SMTP id bi5mr1207196icb.40.1328779522307; Thu, 09 Feb 2012 01:25:22 -0800 (PST)
Received: by 10.42.177.133 with SMTP id bi5mr1207186icb.40.1328779522214; Thu, 09 Feb 2012 01:25:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.122.218 with HTTP; Thu, 9 Feb 2012 01:25:02 -0800 (PST)
In-Reply-To: <4F329696.6000505@bogus.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com> <4F329696.6000505@bogus.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Feb 2012 18:25:02 +0900
Message-ID: <CAKD1Yr2FpapZuz4fk1M1uqmG2Xgao_K=Houpnz0Jq2k56ZLMLg@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
To: Joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=90e6ba6e86dc680cfe04b88497ee
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQlrmoRNAu+MEnIJ8nGBfPzxXnO3hSVNe0zceCecXrVBF5XwSggAP5+LTyTyXkQsLH5OwFjhM6jYVhQY4LmtALKCnY2ng17oPzPUOFx4drs1TpO4I9IQM0GY4gRMarSMK8kbwzXb
X-Mailman-Approved-At: Thu, 09 Feb 2012 08:06:43 -0800
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 09:25:23 -0000

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

On Thu, Feb 9, 2012 at 00:36, Joel jaeggli <joelja@bogus.com> wrote:

> Ops is not marketing.
>

And if I were looking for a marketing venue, a standards body that produces
ASCII text documents read by a handful of engineers would not be high on my
list. This is not about marketing.


> If you're saying some flag day makes the contents of the document no
> longer operationally relevant after a given date, I'll take the point
> but disagree.
>

I think you're missing my point.

It seems to me that approximately 30% of the non-biolerplate text in this
draft discusses DNS whitelisting. (And in fact, in its original form the
draft entirely on DNS whitelisting - hence the filename. The rest was added
later.)

Whitelisting is a practice relevant to a few large websites (since nobody
else is using it). It so happens that the websites that employ this
practice are going to stop using it, all together. Given the cost and
implications, I'd say practice is unlikely to be resurrected.

So, you decide to tell the whole story, and talk about whitelisting *and*
World IPv6 Launch. Or you can decide that whitelisting will soon be
irrelevant, and not talk about either whitelisting or World IPv6
Launch. But you can't talk about whitelisting without talking about World
IPv6 Launch, because if you do, your document is missing the key piece "how
do you remove the whitelist", and that's a disservice to its readers.

To be more specific, at least section 5.5 ("it is unclear how implementers
will judge when the network conditions will have changed sufficiently to
justify turning off DNS Resolver Whitelisting and/or what the process and
timing will be for discontinuing this practice") is now incorrect. It *is*
clear, and it's what those implementers are doing as part of World IPv6
Launch.

Does that make more sense?

Cheers,
Lorenzo

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

<div class=3D"gmail_quote">On Thu, Feb 9, 2012 at 00:36, Joel jaeggli <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:joelja@bogus.com">joelja@bogus.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">

<div class=3D"im">Ops is not marketing.</div></blockquote><div><br></div><d=
iv>And if I were looking for a marketing venue, a standards body that produ=
ces ASCII text documents read by a handful of=A0engineers would not be high=
 on my list. This is not about marketing.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">If you&#39;re saying some flag=
 day makes the contents of the document no<br>
longer operationally relevant after a given date, I&#39;ll take the point<b=
r>
but disagree.<br></blockquote><div><br></div><div>I think you&#39;re missin=
g my point.</div><div><br></div><div>It seems to me that approximately 30% =
of the non-biolerplate text in this draft discusses DNS whitelisting. (And =
in fact, in its original form the draft entirely on DNS whitelisting - henc=
e the filename. The rest was added later.)</div>

<div><br></div><div>Whitelisting is a practice relevant to a few large webs=
ites (since nobody else is using it). It so happens that the websites that =
employ this practice are going to stop using it, all together. Given the co=
st and implications, I&#39;d say practice is unlikely to be resurrected.</d=
iv>

<div><br></div><div>So, you decide to tell the whole story, and talk about =
whitelisting *and* World IPv6 Launch. Or=A0you can decide that whitelisting=
 will soon be irrelevant, and not talk about either whitelisting or World I=
Pv6 Launch.=A0But you can&#39;t talk about whitelisting without talking abo=
ut World IPv6 Launch, because if you do, your document is missing the key p=
iece &quot;how do you remove the whitelist&quot;, and that&#39;s a disservi=
ce to its readers.</div>

<div><br></div><div>To be more specific, at least section 5.5 (&quot;it is =
unclear how=A0implementers will judge when the network conditions will have=
 changed=A0sufficiently to justify turning off DNS Resolver Whitelisting an=
d/or=A0what the process and timing will be for discontinuing this practice&=
quot;) is now incorrect. It *is* clear, and it&#39;s what those implementer=
s are doing as part of World IPv6 Launch.</div>

<div><br></div><div>Does that make more sense?</div><div><br></div><div>Che=
ers,</div><div>Lorenzo</div></div>

--90e6ba6e86dc680cfe04b88497ee--

From afarrel@juniper.net  Thu Feb  9 04:18:11 2012
Return-Path: <afarrel@juniper.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 EF7B221F86FE for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 04:18:11 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4RadaesRN1YL for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 04:18:11 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 8461D21F859B for <ietf@ietf.org>; Thu,  9 Feb 2012 04:18:09 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q19CI7r4024136;  Thu, 9 Feb 2012 12:18:07 GMT
Received: from 950129200 (cust.static.46-14-88-124.swisscomdata.ch [46.14.88.124]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q19CI6wA024128 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Feb 2012 12:18:07 GMT
From: "Adrian Farrel" <afarrel@juniper.net>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees Frequently Asked (travel) Questions) to Informational RFC
Date: Thu, 9 Feb 2012 12:18:07 -0000
Message-ID: <0a8c01cce724$e26a2db0$a73e8910$@juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AcznJNJ/pOwhilqxR26WU4qhnr0GIQ==
Content-Language: en-gb
X-Mailman-Approved-At: Thu, 09 Feb 2012 08:06:43 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: afarrel@juniper.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:18:12 -0000

I think that this sort of guidance to IETF local hosts may be helpful, and the
current document is fine for publication.

If the author has time to work on it, I would recommending severe pruning of the
preamble text. On the whole it gets in the way of the list of questions.

As has been pointed out, the list of things to consider can become endless. Up
for consideration are...

IMHO the question of visas is buried and not given enough detail. Of particular
importance to IETF travellers is the amount of time that they will require to
apply for a visa. Of course, this makes an n-squared information grid, and there
can be no substitute for pointers to embassy web pages. But we have examples of
there not being enough time between the announcement of the meeting location and
the meeting itself (viz. three months!)

National holidays have been known to impact IETF meetings and travel.

Add to 3.3.1 availability of social health services and air quality info.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 07 February 2012 22:59
> To: IETF-Announce
> Subject: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees'
> Frequently Asked (travel) Questions) to Informational RFC
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IETF meeting attendees' Frequently Asked (travel) Questions'
>   <draft-george-travel-faq-03.txt> as an 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 2012-03-06. 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 attempts to provide a list of the common Frequently
>    Asked Questions (FAQs) that IETF meeting attendees often ask
>    regarding travel logistics and local information.  It is intended to
>    assist those who are willing to provide local information, so that if
>    they wish to pre-populate answers to some or all of these questions
>    either in the IETF Wiki or a meeting-specific site, they have a
>    reasonably complete list of ideas to draw from.  It is not meant as a
>    list of required information that the host or secretariat needs to
>    provide, merely as a guideline.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-george-travel-faq/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-george-travel-faq/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From sm@resistor.net  Thu Feb  9 08:33:15 2012
Return-Path: <sm@resistor.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 4D84121F848B for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 08:33:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.609
X-Spam-Level: 
X-Spam-Status: No, score=-102.609 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qCn7p2-D++Pi for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 08:33: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 32B2421F847C for <ietf@ietf.org>; Thu,  9 Feb 2012 08:33:11 -0800 (PST)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q19GX6ij026813 for <ietf@ietf.org>; Thu, 9 Feb 2012 08:33:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1328805190; i=@resistor.net; bh=Gx0vihwW2XrrTpOjs7foVUI6GSxbIqVrhJreT96wg1U=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=uQ78tnveQBvVimPZPy84lwnbHFOBS2/DW7S6egnJ3Nw2t+wI7hDkg1zA14KRriFOk KU02A0eShs8gYs/QmDIIq0U5STm+8tTXkGUd8NDh4AyNrvCBRTud/ev81DWGTernRR QkJMPa+n0WZz4ykwfNSz4y+9sgiCK3hFlCs6wriM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1328805190; i=@resistor.net; bh=Gx0vihwW2XrrTpOjs7foVUI6GSxbIqVrhJreT96wg1U=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=rBVEdkRKtiVeNypxmERwZPYxpYf/WD5nxveGKc/+J5hbHxfXh6NH84TRbSjIwmo3J 9xrB6BVNy+cL9kLMF9rqaFJu0JJt/5mfVparVU3gqboPC8BnnjJU7kcolapwPncBug SFhV7NlnD6Nkr00LH95UQYQlkToUoU9Lx8+dn9hI=
Message-Id: <6.2.5.6.2.20120209065941.075b6e08@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Feb 2012 07:44:55 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:33:15 -0000

At 03:03 PM 1/30/2012, The IESG wrote:
>The IESG has received a request from an individual submitter to 
>consider the following document:
>- 'IANA Reserved IPv4 Prefix for Shared CGN Space'
>  <draft-weil-shared-transition-space-request-14.txt> as a BCP
>
>On its December 15, 2011 telechat, the IESG reviewed version 10 of this
>document and requested various changes. These changes are reflected in
>the draft version 14 and the IESG now solicits community input on the
>changed text only. Please send substantive comments to the ietf@ietf.org
>mailing lists by 2012-02-16. Exceptionally, comments may be sent to

Is that a two-weeks Last Call?

Will the determination of consensus be made only on the basis of this 
Last Call?

In Section 3:

   "A Service Provider can number the interfaces in question from
    legitimately assigned globally unique address space.  While this
    solution poses the fewest problems, it is impractical because
    globally unique IPv4 address space is in short supply."

Unique IPv4 address space is not in short supply in some regions.  If 
it is globally in short supply, I gather that several regions have 
already reached their IPv4 Exhaustion phase.  I haven't seen any 
announcements about that.

   "While the Regional Internet Registries (RIR) have enough address
    space to allocate a single /10 to be shared by all Service Providers,
    they do not have enough address space to make a unique assignment to
    each Service Provider."

The above is incorrect as RIRs are still providing unique IPv4 
assignments to service providers that request IPv4 addresses.  On 
reading this draft, I conclude that as IPv4 addresses are nearly 
exhausted, the only option left is to deploy Carrier Grade NAT 
instead of requesting IPv4 addresses from a RIR.

For the determination of consensus, I do not support this proposal.

Regards,
-sm 


From cgrundemann@gmail.com  Thu Feb  9 08:57:58 2012
Return-Path: <cgrundemann@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 1232921E8014 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 08:57:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.499
X-Spam-Level: 
X-Spam-Status: No, score=-4.499 tagged_above=-999 required=5 tests=[AWL=1.100,  BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBChR9JObxm4 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 08:57:56 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id E561A21E8023 for <ietf@ietf.org>; Thu,  9 Feb 2012 08:57:56 -0800 (PST)
Received: by dakl33 with SMTP id l33so1693429dak.31 for <ietf@ietf.org>; Thu, 09 Feb 2012 08:57:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=mKrM7ZzIQ9YkufOYVdDehzyJ1gVmfkA1Bomb8EElhP4=; b=q4ED1+pCms0KLZWBSgLsHf3AKDhr7CI15J3j3oINjiGjxTJOshDq16KzaHM+o2HR6D UI8vJVnls0MXRNLIHW4ge+x6a8JDxK12+pYgq10854YHELAMJSnxhDq7sbDORpYCY9Pu kr1Bz19DQLmD+cZThgyr7LrfPqGFidveL7r7k=
MIME-Version: 1.0
Received: by 10.68.228.101 with SMTP id sh5mr7443306pbc.127.1328806676645; Thu, 09 Feb 2012 08:57:56 -0800 (PST)
Received: by 10.142.105.13 with HTTP; Thu, 9 Feb 2012 08:57:56 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20120209065941.075b6e08@resistor.net>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net>
Date: Thu, 9 Feb 2012 09:57:56 -0700
Message-ID: <CAC1-dtmdA_ApS83=JA1Y3V0yBUFqciJ16X6MZxqkaSViQxenaw@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:57:58 -0000

On Thu, Feb 9, 2012 at 08:44, SM <sm@resistor.net> wrote:

> In Section 3:
>
> =A0"A Service Provider can number the interfaces in question from
> =A0 legitimately assigned globally unique address space. =A0While this
> =A0 solution poses the fewest problems, it is impractical because
> =A0 globally unique IPv4 address space is in short supply."
>
> Unique IPv4 address space is not in short supply in some regions. =A0If i=
t is
> globally in short supply, I gather that several regions have already reac=
hed
> their IPv4 Exhaustion phase. =A0I haven't seen any announcements about th=
at.

http://www.apnic.net/publications/news/2011/final-8
http://www.coisoc.org/index.php/2011/internet-society-statement-on-apnic-ip=
v4-depletion/
http://www.apnic.net/community/ipv4-exhaustion/ipv4-exhaustion-details
http://isoc.org/wp/newsletter/?p=3D3592

> =A0"While the Regional Internet Registries (RIR) have enough address
> =A0 space to allocate a single /10 to be shared by all Service Providers,
> =A0 they do not have enough address space to make a unique assignment to
> =A0 each Service Provider."
>
> The above is incorrect as RIRs are still providing unique IPv4 assignment=
s
> to service providers that request IPv4 addresses. =A0On reading this draf=
t, I
> conclude that as IPv4 addresses are nearly exhausted, the only option lef=
t
> is to deploy Carrier Grade NAT instead of requesting IPv4 addresses from =
a
> RIR.

Are you proposing that every ISP on the planet be given a /10 for
inside CGN use, rather than one single /10 being reserved for this
purpose?

Cheers,
~Chris


> For the determination of consensus, I do not support this proposal.
>
> Regards,
> -sm
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



--=20
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.theIPv6experts.net
www.coisoc.org

From rogerj@gmail.com  Thu Feb  9 10:02:52 2012
Return-Path: <rogerj@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 E91F521F85AA for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 10:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gC5bQC9sBJnz for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 10:02:45 -0800 (PST)
Received: from mail-lpp01m020-f172.google.com (mail-lpp01m020-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8C24B21F8599 for <ietf@ietf.org>; Thu,  9 Feb 2012 10:02:44 -0800 (PST)
Received: by lbbgk8 with SMTP id gk8so1105206lbb.31 for <ietf@ietf.org>; Thu, 09 Feb 2012 10:02:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fBKBV5iSkLLjHJkqXoY/qeMFR3AwgRAqH87j1maEq2I=; b=MEGPXgtBa6SsHXa3azu1vX1fpJ4YJF/KnUa0UbKZT69DEOEQPxE0p0bVtfw4x+/aWg NpUELtxXnB/8R8rYYjpQrpR+oyItrQq37ZOfGnX5qYLW5wKNi66FpLOb1g7h5r65l6aO +OEiiA1Y8tJQEEFgp3np+4wfqM7zSHJggInnA=
MIME-Version: 1.0
Received: by 10.112.100.169 with SMTP id ez9mr946075lbb.82.1328810563526; Thu, 09 Feb 2012 10:02:43 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Thu, 9 Feb 2012 10:02:43 -0800 (PST)
In-Reply-To: <CAKD1Yr2FpapZuz4fk1M1uqmG2Xgao_K=Houpnz0Jq2k56ZLMLg@mail.gmail.com>
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com> <4F329696.6000505@bogus.com> <CAKD1Yr2FpapZuz4fk1M1uqmG2Xgao_K=Houpnz0Jq2k56ZLMLg@mail.gmail.com>
Date: Thu, 9 Feb 2012 19:02:43 +0100
Message-ID: <CAKFn1SF=xzMTQbepGhn1xrthwE2cUwh=CTmzzeveQzg190OYNQ@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:02:52 -0000

On Thu, Feb 9, 2012 at 10:25 AM, Lorenzo Colitti <lorenzo@google.com> wrote=
:
<snip>
> It seems to me that approximately 30% of the non-biolerplate text in this
> draft discusses DNS whitelisting. (And in fact, in its original form the
> draft entirely on DNS whitelisting - hence the filename. The rest was add=
ed
> later.)
>
> Whitelisting is a practice relevant to a few large websites (since nobody
> else is using it). It so happens that the websites that employ this pract=
ice
> are going to stop using it, all together. Given the cost and implications=
,
> I'd say practice is unlikely to be resurrected.
>
> So, you decide to tell the whole story, and talk about whitelisting *and*
> World IPv6 Launch. Or=A0you can decide that whitelisting will soon be
> irrelevant, and not talk about either whitelisting or World IPv6 Launch.=
=A0But
> you can't talk about whitelisting without talking about World IPv6 Launch=
,
> because if you do, your document is missing the key piece "how do you rem=
ove
> the whitelist", and that's a disservice to its readers.
>
> To be more specific, at least section 5.5 ("it is unclear how=A0implement=
ers
> will judge when the network conditions will have changed=A0sufficiently t=
o
> justify turning off DNS Resolver Whitelisting and/or=A0what the process a=
nd
> timing will be for discontinuing this practice") is now incorrect. It *is=
*
> clear, and it's what those implementers are doing as part of World IPv6
> Launch.
>
> Does that make more sense?

Or, the way I read you, you tell us that this entire document isn't
relevant anymore.

It cover something called whitelisting that were in use for a short
periode of time for reason no one in a few year can understand as
relevant?



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From sm@resistor.net  Thu Feb  9 10:14:39 2012
Return-Path: <sm@resistor.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 53C8221F8729 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 10:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xclnJKdMoK6B for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 10:14: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 2C1AA21F8723 for <ietf@ietf.org>; Thu,  9 Feb 2012 10:14:37 -0800 (PST)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q19IEUd6024360; Thu, 9 Feb 2012 10:14:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1328811275; i=@resistor.net; bh=7H6/erGt9aixyLIvdtTjE5+rqIR63Nd9n1K/fcdMIo8=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=meKeEKBgQuskFbUrLRNgvqo2MZtGSBmayqdEma1b+HiqfYDo3RozuuDQok6rAWavc 8+/Yqy7X1jAlHo0HBuOQgB65KcRcsg3YNmigVSQT8E0JgKbi0mJwPGBGjitgEo4Jyb u0AeN5uQ32/ZOhanoxHFuQye1yzXY4g3lwwFKwts=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1328811275; i=@resistor.net; bh=7H6/erGt9aixyLIvdtTjE5+rqIR63Nd9n1K/fcdMIo8=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=F2NLH9r43k64+FEatbFPfqOu+z6F8Yb5KOsFXFOCdU/mkb0VzwL/WaHHnYgA6/ayo AJveSCCSf4JY4IIF+wVHnli9EI00frAcSfbTLV3SEB5MUdZbGSTPtESVB9cmxwMonH vrW+nfvpR5WB5Cy9pChEB6NdFomATRCcjD5aJlw4=
Message-Id: <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Feb 2012 09:59:28 -0800
To: Chris Grundemann <cgrundemann@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <CAC1-dtmdA_ApS83=JA1Y3V0yBUFqciJ16X6MZxqkaSViQxenaw@mail.g mail.com>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <CAC1-dtmdA_ApS83=JA1Y3V0yBUFqciJ16X6MZxqkaSViQxenaw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:14:39 -0000

Hi Chris,
At 08:57 AM 2/9/2012, Chris Grundemann wrote:
>http://www.apnic.net/publications/news/2011/final-8

I am aware of the APNIC announcement.  That's one out of five regions.

>Are you proposing that every ISP on the planet be given a /10 for
>inside CGN use, rather than one single /10 being reserved for this
>purpose?

No.

If I am not mistaken, IPv4 assignments are on a needs basis.  In my 
previous comment, I mentioned that RIRs are still providing unique 
IPv4 assignments to service providers that request IPv4 
addresses.  Even if the IANA pool was not exhausted, it is unlikely 
that an ISP would get a /20 due to the slow-start mechanism.

Regards,
-sm 


From cgrundemann@gmail.com  Thu Feb  9 11:14:15 2012
Return-Path: <cgrundemann@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 30F3621E801C for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 11:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.774
X-Spam-Level: 
X-Spam-Status: No, score=-3.774 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvZAuo4npgGk for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 11:14:14 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2B31A21F8584 for <ietf@ietf.org>; Thu,  9 Feb 2012 11:14:14 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so1871730pbc.31 for <ietf@ietf.org>; Thu, 09 Feb 2012 11:14:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/wJU1ia4pnpYhZ+SukPWH0eUCvigmD+ThwKoWIc1O24=; b=I95UTg/uhnLaPXYxk7Nfb4qubawsHuVYg0qXEEsNB5h9fHND8pU89EU6p+e3QC+zjE RHgpcN15avFE6ZjvrBBsP3riajT23ZCo/pOLe49ub3UVf/Ry78ZdeAumPHqfYKECNKGI ZTvbglhyqoWKpZcmdDMbGFl/hrblFGZWPf9YQ=
MIME-Version: 1.0
Received: by 10.68.132.137 with SMTP id ou9mr8526610pbb.93.1328814851655; Thu, 09 Feb 2012 11:14:11 -0800 (PST)
Received: by 10.142.105.13 with HTTP; Thu, 9 Feb 2012 11:14:11 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <CAC1-dtmdA_ApS83=JA1Y3V0yBUFqciJ16X6MZxqkaSViQxenaw@mail.gmail.com> <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>
Date: Thu, 9 Feb 2012 12:14:11 -0700
Message-ID: <CAC1-dtnbuCYCXBCnLbzAdZX5owfX3E5E8SS1a0aDNrSZTV+_=g@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:14:15 -0000

On Thu, Feb 9, 2012 at 10:59, SM <sm@resistor.net> wrote:
> Hi Chris,
> At 08:57 AM 2/9/2012, Chris Grundemann wrote:
>>
>> http://www.apnic.net/publications/news/2011/final-8
>
> I am aware of the APNIC announcement. =A0That's one out of five regions.

My apologies, when you stated "I haven't seen any announcements about
that." I thought you were not. Hopefully others found the link useful.

>> Are you proposing that every ISP on the planet be given a /10 for
>> inside CGN use, rather than one single /10 being reserved for this
>> purpose?
>
>
> No.
>
> If I am not mistaken, IPv4 assignments are on a needs basis. =A0In my pre=
vious
> comment, I mentioned that RIRs are still providing unique IPv4 assignment=
s
> to service providers that request IPv4 addresses. =A0Even if the IANA poo=
l was
> not exhausted, it is unlikely that an ISP would get a /20 due to the
> slow-start mechanism.

In the ARIN region, slow-start only applies to new-to-ARIN
organizations. Most (if not all) of the ISPs we're discussing here are
established entities and are not subject to slow start.

More to the point: I do not see giving everyone a unique bit of space
for inside CGN use as an efficient solution to the problem. Likewise,
waiting until we are completely out of IPv4 space before reacting to
the problems that IPv4 free pool exhaustion WILL cause seems _very_
unlikely to produce positive results.

Cheers,
~Chris

> Regards,
> -sm



--=20
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.theIPv6experts.net
www.coisoc.org

From rbonica@juniper.net  Thu Feb  9 12:41:54 2012
Return-Path: <rbonica@juniper.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 87F1311E8089 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 12:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.536
X-Spam-Level: 
X-Spam-Status: No, score=-106.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7IJUcb-5VKRY for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 12:41:53 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 8024611E808E for <ietf@ietf.org>; Thu,  9 Feb 2012 12:41:46 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTzQvidYnaMq5DDfdpg8ZceAHyLv4ummh@postini.com; Thu, 09 Feb 2012 12:41:53 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 9 Feb 2012 12:40:13 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Thu, 9 Feb 2012 15:40:13 -0500
From: Ronald Bonica <rbonica@juniper.net>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 9 Feb 2012 15:40:13 -0500
Subject: RE: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA Reserved	IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA Reserved	IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AcznSIneOPq/1bmYTAGEegBO+Bl8OgAIj2TA
Message-ID: <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net>
In-Reply-To: <6.2.5.6.2.20120209065941.075b6e08@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: f8e27f27-03b2-4c3e-9447-119194e72cb6
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:41:54 -0000

SM,

At NANOG 54, ARIN reported that they are down to 5.6 /8s. If just four ISPs=
 ask for a /10 for CGN, we burn one of those /8s.

Is that really a good idea?

                              Ron


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> SM
> Sent: Thursday, February 09, 2012 10:45 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-weil-shared-transition-space-request-
> 14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
>=20
> At 03:03 PM 1/30/2012, The IESG wrote:
> >The IESG has received a request from an individual submitter to
> >consider the following document:
> >- 'IANA Reserved IPv4 Prefix for Shared CGN Space'
> >  <draft-weil-shared-transition-space-request-14.txt> as a BCP
> >
> >On its December 15, 2011 telechat, the IESG reviewed version 10 of
> this
> >document and requested various changes. These changes are reflected in
> >the draft version 14 and the IESG now solicits community input on the
> >changed text only. Please send substantive comments to the
> ietf@ietf.org
> >mailing lists by 2012-02-16. Exceptionally, comments may be sent to
>=20
> Is that a two-weeks Last Call?
>=20
> Will the determination of consensus be made only on the basis of this
> Last Call?
>=20
> In Section 3:
>=20
>    "A Service Provider can number the interfaces in question from
>     legitimately assigned globally unique address space.  While this
>     solution poses the fewest problems, it is impractical because
>     globally unique IPv4 address space is in short supply."
>=20
> Unique IPv4 address space is not in short supply in some regions.  If
> it is globally in short supply, I gather that several regions have
> already reached their IPv4 Exhaustion phase.  I haven't seen any
> announcements about that.
>=20
>    "While the Regional Internet Registries (RIR) have enough address
>     space to allocate a single /10 to be shared by all Service
> Providers,
>     they do not have enough address space to make a unique assignment
> to
>     each Service Provider."
>=20
> The above is incorrect as RIRs are still providing unique IPv4
> assignments to service providers that request IPv4 addresses.  On
> reading this draft, I conclude that as IPv4 addresses are nearly
> exhausted, the only option left is to deploy Carrier Grade NAT
> instead of requesting IPv4 addresses from a RIR.
>=20
> For the determination of consensus, I do not support this proposal.
>=20
> Regards,
> -sm
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From drc@virtualized.org  Thu Feb  9 12:59:17 2012
Return-Path: <drc@virtualized.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 84DF021E8047 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 12:59:17 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-KCyuiHfPkN for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 12:59:16 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id C920A21E8019 for <ietf@ietf.org>; Thu,  9 Feb 2012 12:59:16 -0800 (PST)
Received: from [192.168.2.159] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 5B7051705A; Thu,  9 Feb 2012 20:59:16 +0000 (UTC)
Subject: Re: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA Reserved	IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
Date: Thu, 9 Feb 2012 12:59:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E058265-058E-450F-BE2F-E54F10348A18@virtualized.org>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1257)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:59:17 -0000

Ron,

On Feb 9, 2012, at 12:40 PM, Ronald Bonica wrote:
> At NANOG 54, ARIN reported that they are down to 5.6 /8s. If just four =
ISPs ask for a /10 for CGN, we burn one of those /8s.
>=20
> Is that really a good idea?

Long ago, I once proposed a policy at ARIN to try to extend the IPv4 =
runway.  One of the most common responses I received (including from =
several members of ARIN's AC) was "let it run out naturally", with the =
rationale being either:

a) "it'll force people to move to IPv6"
b) "we spent a lot of money to prepare for IPv6 because we knew it was =
coming soon, we don't want to give our competitors who fiddled the =
summer away more time"

I suspect those people would answer "yes" (well, unless their opinions =
have changed as reality starts biting).

Regards,
-drc
=20=

From rogerj@gmail.com  Thu Feb  9 13:02:52 2012
Return-Path: <rogerj@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 0B67A21F8587 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 13:02:52 -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=[AWL=-0.462, BAYES_00=-2.599, FB_NO_MORE_ADS=1.174, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nqxdz2DPJZwM for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 13:02:48 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC3721F8576 for <ietf@ietf.org>; Thu,  9 Feb 2012 13:02:48 -0800 (PST)
Received: by lahl5 with SMTP id l5so2187001lah.31 for <ietf@ietf.org>; Thu, 09 Feb 2012 13:02:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=p23wTmuhCpqmg841Q4uLg085zkVyqhjTMa+OfuxhD5A=; b=f06yxHsZ4qlroDNJe4HH2MVyUPx9aFKac0VLnandH1jsMDFxlIN7OlDwAVYbmKDnJ3 i5QOFEAbjYxAwyqmpBVI22D/rFExG3xgLO9bu1skrZSW+I1bOpwEjhhaLcld4tbODyYU s/ekTC6hn/CiuZzbLjJESOcPKDbBx0gf0y+Mk=
MIME-Version: 1.0
Received: by 10.112.29.6 with SMTP id f6mr1159720lbh.69.1328821367179; Thu, 09 Feb 2012 13:02:47 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Thu, 9 Feb 2012 13:02:47 -0800 (PST)
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
Date: Thu, 9 Feb 2012 22:02:47 +0100
Message-ID: <CAKFn1SH9_q1mpYMjmUbZ0TntJ0DvvsHbD+Xpj0rcCpucNOK3qw@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Ronald Bonica <rbonica@juniper.net>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:02:52 -0000

On Thu, Feb 9, 2012 at 9:40 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> SM,
>
> At NANOG 54, ARIN reported that they are down to 5.6 /8s. If just four IS=
Ps ask for a /10 for CGN, we burn one of those /8s.
>
> Is that really a good idea?

It's not about good or bad idea, it should be more about; If they can
justify having a /10 each then they should get it. And yes, that will
hurt.



... wish people could use more time to move on instead of trying to
squeeze even more out of the good old, dry and dead dog called IPv4.



With all of that said, giving out this shared address space is a
horrible idea, but it just a little bit less horrible than the
alternates.
And yes it will be abused and be counted as yet another RFC1918 space
anyway. I know of plenty of people that will be trilled for this
space... "woho, no more address collision" while they quiet think "I
hope no one else know about this address space...."

in other word, move on, give out this space, it'll hurt just a little
bit less than the other options.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From cgrundemann@gmail.com  Thu Feb  9 13:17:33 2012
Return-Path: <cgrundemann@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 2704221F856A for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 13:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.739
X-Spam-Level: 
X-Spam-Status: No, score=-3.739 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0cRscVMaX8WO for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 13:17:32 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id D815E21F853B for <ietf@ietf.org>; Thu,  9 Feb 2012 13:17:31 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so1958502pbc.31 for <ietf@ietf.org>; Thu, 09 Feb 2012 13:17:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=ae2spiOQQ8/xfVczbvqK4PXRhN1zwuKyhPYU16OfTTA=; b=fWp2ZQkMJSOEWoP0ehbQtn/DSCD7DDFjmSyAgzNJNGMvV2fFyp1d4Db7M8YKHGsp0S iz6XMKcHJqTm1hMg6Rru6kVYNoK7ESZEZlFGGWnCuTXOBIvLb0kU01mPRBkfQUoXKgJp L9TZpyYMxqzC18zeBn3n0ZVFODgxDVKfnm8nY=
MIME-Version: 1.0
Received: by 10.68.132.137 with SMTP id ou9mr9423872pbb.93.1328822249955; Thu, 09 Feb 2012 13:17:29 -0800 (PST)
Received: by 10.142.105.13 with HTTP; Thu, 9 Feb 2012 13:17:29 -0800 (PST)
In-Reply-To: <8E058265-058E-450F-BE2F-E54F10348A18@virtualized.org>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net> <8E058265-058E-450F-BE2F-E54F10348A18@virtualized.org>
Date: Thu, 9 Feb 2012 14:17:29 -0700
Message-ID: <CAC1-dtko61E+Ohd_vPJCuYXZZwNkoRMmvt9bPx0McdssmOJTsg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:17:33 -0000

On Thu, Feb 9, 2012 at 13:59, David Conrad <drc@virtualized.org> wrote:
> Ron,
>
> On Feb 9, 2012, at 12:40 PM, Ronald Bonica wrote:
>> At NANOG 54, ARIN reported that they are down to 5.6 /8s. If just four I=
SPs ask for a /10 for CGN, we burn one of those /8s.
>>
>> Is that really a good idea?
>
> Long ago, I once proposed a policy at ARIN to try to extend the IPv4 runw=
ay. =A0One of the most common responses I received (including from several =
members of ARIN's AC) was "let it run out naturally", with the rationale be=
ing either:
>
> a) "it'll force people to move to IPv6"
> b) "we spent a lot of money to prepare for IPv6 because we knew it was co=
ming soon, we don't want to give our competitors who fiddled the summer awa=
y more time"
>
> I suspect those people would answer "yes" (well, unless their opinions ha=
ve changed as reality starts biting).

Being one of the people who believe that IPv4 should run out
naturally, I can tell you that my answer is "no." Natural-run-out and
waste are not synonymous.

Cheers,
~Chris

> Regards,
> -drc
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



--=20
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.theIPv6experts.net
www.coisoc.org

From dougb@dougbarton.us  Thu Feb  9 14:30:31 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD21E21E805E for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 14:30:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.411
X-Spam-Level: 
X-Spam-Status: No, score=-3.411 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jnvqfqXc59A for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 14:30:31 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id B61C221E8050 for <ietf@ietf.org>; Thu,  9 Feb 2012 14:30:30 -0800 (PST)
Received: (qmail 15187 invoked by uid 399); 9 Feb 2012 22:30:25 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 9 Feb 2012 22:30:25 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F3448FF.3080803@dougbarton.us>
Date: Thu, 09 Feb 2012 14:30:23 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com> <4F329696.6000505@bogus.com> <CAKD1Yr2FpapZuz4fk1M1uqmG2Xgao_K=Houpnz0Jq2k56ZLMLg@mail.gmail.com> <CAKFn1SF=xzMTQbepGhn1xrthwE2cUwh=CTmzzeveQzg190OYNQ@mail.gmail.com>
In-Reply-To: <CAKFn1SF=xzMTQbepGhn1xrthwE2cUwh=CTmzzeveQzg190OYNQ@mail.gmail.com>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IETF Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:30:31 -0000

On 2/9/2012 10:02 AM, Roger Jørgensen wrote:
> Or, the way I read you, you tell us that this entire document isn't
> relevant anymore.
> 
> It cover something called whitelisting that were in use for a short
> periode of time for reason no one in a few year can understand as
> relevant?

+1


-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From marka@isc.org  Thu Feb  9 14:41:17 2012
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 0721F21E8063 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 14:41:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id REeDq9z5BdFe for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 14:41:16 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id F376921E8036 for <ietf@ietf.org>; Thu,  9 Feb 2012 14:41:15 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 1B5F95F98BF; Thu,  9 Feb 2012 22:40:49 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:28fa:2c1:b003:67a9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 0EF83216C6B; Thu,  9 Feb 2012 22:40:47 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 758501D1BB31; Fri, 10 Feb 2012 09:40:41 +1100 (EST)
To: SM <sm@resistor.net>
From: Mark Andrews <marka@isc.org>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <CAC1-dtmdA_ApS83=JA1Y3V0yBUFqciJ16X6MZxqkaSViQxenaw@mail.gmail.com> <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-reply-to: Your message of "Thu, 09 Feb 2012 09:59:28 -0800." <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>
Date: Fri, 10 Feb 2012 09:40:40 +1100
Message-Id: <20120209224041.758501D1BB31@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:41:17 -0000

In message <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>, SM writes:
> Hi Chris,
> At 08:57 AM 2/9/2012, Chris Grundemann wrote:
> >http://www.apnic.net/publications/news/2011/final-8
> 
> I am aware of the APNIC announcement.  That's one out of five regions.
> 
> >Are you proposing that every ISP on the planet be given a /10 for
> >inside CGN use, rather than one single /10 being reserved for this
> >purpose?
> 
> No.
> 
> If I am not mistaken, IPv4 assignments are on a needs basis.  In my 
> previous comment, I mentioned that RIRs are still providing unique 
> IPv4 assignments to service providers that request IPv4 
> addresses.  Even if the IANA pool was not exhausted, it is unlikely 
> that an ISP would get a /20 due to the slow-start mechanism.
> 
> Regards,
> -sm 

In none of the discussions I've seen has anyone proposed forcing ISP's
to use this space.  It is being provided as a alternative, the same
away RFC 1918 space is offered as a alternative.

Today you get ask "have you considered RFC 1918 space?"  You can
still get space even if RFC 1918 space would have worked.  I suspect
a similar question, will be part of allocation proceedures, for this
space in the future.  You need to know that the applicant is aware
of this space.

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

From sm@resistor.net  Thu Feb  9 14:54:24 2012
Return-Path: <sm@resistor.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 91E4E11E808A for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 14:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTbpv4BkqvKI for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 14:54:22 -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 E6CB811E8073 for <ietf@ietf.org>; Thu,  9 Feb 2012 14:54:21 -0800 (PST)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q19MsF8n025192; Thu, 9 Feb 2012 14:54:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1328828059; i=@resistor.net; bh=4cIxLIZIgNwxPJABPJcWCEDi1SRgpTBBRD3tP172tPk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=AqeFdO9gzNvbLcToD4A5tZQ647MzDHByU7YYXzPx3nISGnpK2/EzyAsWD/Hp9ZMv/ 3KM+ve0MkdiLQHnWU1wp7lC3uaKqeZmTbEEijJRQCNcFUJhL8j4k5E4yqtRL9i2tQf dWBuvMf7TxDi3eht/M5juR/UFiPKHHBbNHwy8Ie8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1328828059; i=@resistor.net; bh=4cIxLIZIgNwxPJABPJcWCEDi1SRgpTBBRD3tP172tPk=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=aKlWNy+KRedW3iKmIybllYCtAD5mRLOR4LCDPBRg2wGwg989tjCQv5IIpkVMi79Q0 PfnmyTeJDgFgHMoTrF7S0T8LtgSFz6YhP19gm0IykwJoki+rcKNisyPzUKvYFTYsPP LB7bdTWt3V1vWrw3sxmKmKh1Of20TdrdFXNPsaR8=
Message-Id: <6.2.5.6.2.20120209140006.0c54d270@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Feb 2012 14:40:18 -0800
To: Ronald Bonica <rbonica@juniper.net>
From: SM <sm@resistor.net>
Subject: RE: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA Reserved	IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr. net>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:54:24 -0000

Hi Ron,
At 12:40 PM 2/9/2012, Ronald Bonica wrote:
>At NANOG 54, ARIN reported that they are down to 5.6 /8s. If just 
>four ISPs ask for a /10 for CGN, we burn one of those /8s.
>
>Is that really a good idea?

The short answer is no.

The long answer is a bit complicated as it would be difficult to 
justify efficient utilization of a /10 within a three-month time 
frame.  There are also specific policies which can be used to get a /10.

 From an IETF perspective, I understand that the IESG is faced with a 
difficult decision and I respect its decision.

I note that Chris Grundemann has been fair when we interacted in a 
non-IETF venue.

Based on the above, I'll keep the -1 for the determination of consensus.

Regards,
-sm 


From jhw@apple.com  Thu Feb  9 15:25:14 2012
Return-Path: <jhw@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 5A90521E805E for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 15:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.113
X-Spam-Level: 
X-Spam-Status: No, score=-110.113 tagged_above=-999 required=5 tests=[AWL=0.486, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWyZFm-an2Kq for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 15:25:13 -0800 (PST)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id DE1AA21E805B for <ietf@ietf.org>; Thu,  9 Feb 2012 15:25:13 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LZ5001XYFNT99M0@mail-out.apple.com> for ietf@ietf.org; Thu, 09 Feb 2012 15:24:50 -0800 (PST)
X-AuditID: 11807134-b7c1cae000003f41-b1-4f3455c2a1cc
Received: from kallisti.apple.com (kallisti.apple.com [17.193.13.64]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 57.5C.16193.2C5543F4; Thu, 09 Feb 2012 15:24:50 -0800 (PST)
Subject: Re: ITC copped out on UTC again
From: james woodyatt <jhw@apple.com>
In-reply-to: <alpine.LSU.2.00.1202071858230.6811@hermes-2.csi.cam.ac.uk>
Date: Thu, 09 Feb 2012 15:24:50 -0800
Message-id: <A0E5A08E-694A-4E0E-8C17-3536F70578D4@apple.com>
References: <CAMm+LwgtUzw9GB1Mc=zQ3Fr_RPrsfy7d59HH6fstvsgTN=_C+g@mail.gmail.com> <CAJNg7V+56hgjyCptJLNr1YqrZ5d3y3VsJZCD+P999V4u1GourA@mail.gmail.com> <4F1D2DD7.6090103@tana.it> <CAJNg7VK1BDu7i7OADsW9SVP_iFXA8esMinHad-j0oUHE0UJVug@mail.gmail.com> <1C430E83-F59A-43AD-997D-E3523AB66AD7@apple.com> <alpine.LSU.2.00.1202071858230.6811@hermes-2.csi.cam.ac.uk>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42IRPMjroHso1MTf4P1DI4tnG+ezODB6LFny kymAMYrLJiU1J7MstUjfLoEro6mpk6XgBnfF0T+aDYzzOLsYOTkkBEwk1t78xQZhi0lcuLce yObiEBKYzSTRduk5E0iCWUBL4sa/l2A2r4ChxMxX7awgtrCAhsTGR6vB4mwCKhLfLt8FszkF PCR23NzI0sXIwcECFP94xhhijLbEsoWvmSHG2Ej8enARatcjJolDxx6ygCREBJQlHk09D3WQ rMTtg/uZJjDyzUJyxiwkZ8xCMncBI/MqRsGi1JzESkMTvcSCgpxUveT83E2MoEBqKDTZwXjw J/8hRgEORiUeXg92E38h1sSy4srcQ4wSHMxKIrzWfEAh3pTEyqrUovz4otKc1OJDjNIcLEri vMXHDP2FBNITS1KzU1MLUotgskwcnFINjKtkhGSWmV23bkjite0+fr+0bHn/aut/D//l60Q1 zF9aHLTEccJrZ9sEX28H5d1uXnKv5e9+Czv/YHdm9z/TO2vWMou6Ll55bOat5L+rLT+3ys4v 3L8+PbT9mvIDczenHSrPDzdsUH3571RrxTKuE1z8uS2TWRZIHk1YkPf4IV9Qr/git3cxL5VY ijMSDbWYi4oTASJhJEcgAgAA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:25:14 -0000

On Feb 7, 2012, at 11:03 , Tony Finch wrote:
> 
> Actually TAI depends a lot on relativity as well as quantum physics. For
> example, it is supposed to match the rate of the SI second on the geoid
> (which is roughly mean sea level). NIST's lab in Colorado is about a mile
> high, so they have to apply a general relativistic rate correction to
> their atomic clocks because of their gravitational potential.

I'm aware of that.  The point I was trying to make so clumsily is that, outside of the physical contexts where relativity and quantum effects are significant, TAI is a comparatively stable and predictable timescale next to the UTC and the NTP timescales.

It would be a perfectly good replacement as The Internet Timescale.

>> so it should be good enough for most running code on the Internet.
> 
> Except where that code needs UTC.

...or awareness any other timezone, for that matter.

On Feb 7, 2012, at 11:12 , John C Klensin wrote:
> 
> You obviously have not been in enough meetings in which proposals were put forth, by political types with the best of intentions, for regulations to improve the Internet...

I said "somewhat resistant" not "impervious" didn't I?  [I'm not going to recount any of the stories I know about various famous technology sector executives and their unhappy encounters with the laws of physics.]


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From john-ietf@jck.com  Thu Feb  9 17:17:45 2012
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 EB34821F85F8 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 17:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKWS-y9vxufd for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 17:17:45 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 51C2321F85F7 for <ietf@ietf.org>; Thu,  9 Feb 2012 17:17:44 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Rvf3d-0001wX-9k; Thu, 09 Feb 2012 20:13:49 -0500
Date: Thu, 09 Feb 2012 20:17:35 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ronald Bonica <rbonica@juniper.net>, SM <sm@resistor.net>, ietf@ietf.org
Subject: RE: Last Call:	<draft-weil-shared-transition-space-request-14.txt>	(IANA Reserved	IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <F009A06F781B2D652606BEC6@PST.JCK.COM>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.net>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120209065941.075b6e08@resistor.net> <13205C286662DE4387D9AF3AC30EF456D7651F2925@EMBX01-WF.jnpr.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:17:46 -0000

--On Thursday, February 09, 2012 15:40 -0500 Ronald Bonica
<rbonica@juniper.net> wrote:

> SM,
> 
> At NANOG 54, ARIN reported that they are down to 5.6 /8s. If
> just four ISPs ask for a /10 for CGN, we burn one of those /8s.
> 
> Is that really a good idea?

Ron,

I've mostly been staying out of this since an earlier round, but
that question/ scenario seems pretty irrelevant to me.    If
four ISPs ask for (and can justify) /10s to serve customers, or
a larger number asks for smaller allocations that add up to the
same thing, we burn a /10 equally quickly.   I think the real
answer to questions like the one you ask is another question:
Suppose there is a strategy that delays, by (say) six months or
a year, the date that ARIN (for example) runs out of
useful-sized blocks to allocate, it is worth doing something
strange or pathological just to gain that extra time?  I think
the answer to that question is "no", regardless of how one
defines "strange or pathological", because a year of traditional
IPv4 allocations from the RIRs one way or the other is quite
unlikely to make a major different to the Internet.

I'm not claiming this proposal is either strange or pathological
(or that it is not).  But I suggest that the decision be made on
the same basis that other allocation decisions are made, not by
trying to save a few months or by deciding that some types of
applications or applicants are inherently more privileged than
others regardless of their actual merits. 

      john


From narten@us.ibm.com  Thu Feb  9 21:53:10 2012
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 A466E21F8517 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 21:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.142
X-Spam-Level: 
X-Spam-Status: No, score=-108.142 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LA8UMMipfeYI for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 21:53:09 -0800 (PST)
Received: from e3.ny.us.ibm.com (e3.ny.us.ibm.com [32.97.182.143]) by ietfa.amsl.com (Postfix) with ESMTP id E3F9A21F84E7 for <ietf@ietf.org>; Thu,  9 Feb 2012 21:53:08 -0800 (PST)
Received: from /spool/local by e3.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 10 Feb 2012 00:53:07 -0500
Received: from d01dlp01.pok.ibm.com (9.56.224.56) by e3.ny.us.ibm.com (192.168.1.103) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 10 Feb 2012 00:53:05 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id BE67438C8026 for <ietf@ietf.org>; Fri, 10 Feb 2012 00:53:04 -0500 (EST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q1A5r44r312184 for <ietf@ietf.org>; Fri, 10 Feb 2012 00:53:04 -0500
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q1A5r4sj014749 for <ietf@ietf.org>; Thu, 9 Feb 2012 22:53:04 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q1A5r3Qo014715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 9 Feb 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q1A5r2jF028603 for <ietf@ietf.org>; Fri, 10 Feb 2012 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q1A5r2AO028559 for ietf@ietf.org; Fri, 10 Feb 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201202100553.q1A5r2AO028559@rotala.raleigh.ibm.com>
Date: Fri, 10 Feb 2012 00:53:02 -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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12021005-8974-0000-0000-0000061B4744
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 05:53:10 -0000

Total of 48 messages in the last 7 days.
 
script run at: Fri Feb 10 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.25% |    3 |  5.36% |    21229 | cgrundemann@gmail.com
  6.25% |    3 |  5.16% |    20447 | sm@resistor.net
  4.17% |    2 |  5.30% |    20983 | ben@nostrum.com
  4.17% |    2 |  5.09% |    20153 | lorenzo@google.com
  4.17% |    2 |  4.92% |    19502 | fred@cisco.com
  4.17% |    2 |  4.58% |    18133 | stephen.farrell@cs.tcd.ie
  4.17% |    2 |  3.93% |    15574 | ek@google.com
  2.08% |    1 |  5.92% |    23447 | tina.tsou.zouting@huawei.com
  4.17% |    2 |  3.66% |    14515 | marka@isc.org
  4.17% |    2 |  3.66% |    14502 | jhw@apple.com
  4.17% |    2 |  3.60% |    14285 | rogerj@gmail.com
  4.17% |    2 |  3.41% |    13525 | fgont@si6networks.com
  4.17% |    2 |  3.03% |    12010 | john-ietf@jck.com
  2.08% |    1 |  3.38% |    13396 | ve7jtb@ve7jtb.com
  2.08% |    1 |  2.95% |    11706 | david.black@emc.com
  2.08% |    1 |  2.58% |    10239 | yaacov.weingarten@nsn.com
  2.08% |    1 |  2.41% |     9545 | rcallon@juniper.net
  2.08% |    1 |  2.37% |     9393 | sakimura@gmail.com
  2.08% |    1 |  2.35% |     9302 | alexey.melnikov@isode.com
  2.08% |    1 |  2.25% |     8913 | daedulus@btconnect.com
  2.08% |    1 |  2.23% |     8836 | narten@us.ibm.com
  2.08% |    1 |  2.22% |     8800 | jeff_downs@partech.com
  2.08% |    1 |  2.04% |     8096 | rbonica@juniper.net
  2.08% |    1 |  1.99% |     7886 | afarrel@juniper.net
  2.08% |    1 |  1.86% |     7359 | brian.e.carpenter@gmail.com
  2.08% |    1 |  1.81% |     7166 | joelja@bogus.com
  2.08% |    1 |  1.66% |     6584 | bortzmeyer@nic.fr
  2.08% |    1 |  1.59% |     6284 | dworley@avaya.com
  2.08% |    1 |  1.57% |     6227 | dot@dotat.at
  2.08% |    1 |  1.57% |     6210 | smb@cs.columbia.edu
  2.08% |    1 |  1.52% |     6039 | dougb@dougbarton.us
  2.08% |    1 |  1.45% |     5761 | drc@virtualized.org
  2.08% |    1 |  1.31% |     5202 | adrian@olddog.co.uk
  2.08% |    1 |  1.27% |     5018 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |   48 |100.00% |   396267 | Total


From dougb@dougbarton.us  Thu Feb  9 22:54:04 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0650721F8772 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 22:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uhc55zTGRiyG for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2012 22:54:03 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 97E9E21F8771 for <ietf@ietf.org>; Thu,  9 Feb 2012 22:54:03 -0800 (PST)
Received: (qmail 1839 invoked by uid 399); 10 Feb 2012 06:47:18 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 10 Feb 2012 06:47:18 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F34BD74.8020807@dougbarton.us>
Date: Thu, 09 Feb 2012 22:47:16 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
In-Reply-To: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:54:04 -0000

On 01/30/2012 15:03, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider the following document:
> - 'IANA Reserved IPv4 Prefix for Shared CGN Space'
>  <draft-weil-shared-transition-space-request-14.txt> as a BCP
> 
> On its December 15, 2011 telechat, the IESG reviewed version 10 of this 
> document and requested various changes. These changes are reflected in 
> the draft version 14 and the IESG now solicits community input on the 
> changed text only.

As I (and many others) remain opposed to this entire concept I think
it's incredibly unfortunate that the IESG has decided to shift the topic
of conversation from "whether" this should happen to "how" it should
happen. But comments more to the point below ....

> Please send substantive comments to the ietf@ietf.org 
> mailing lists by 2012-02-16. 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 requests the allocation of an IPv4 /10 address block to
>   be used as Shared Address Space to accommodate the needs of Carrier
>   Grade Network Address Translation (CGN) devices.  It is anticipated
>   that Service Providers will use this Shared Address Space to number
>   the interfaces that connect CGN devices to Customer Premise Equipment
>   (CPE).
> 
>   Shared Address Space is distinct from RFC1918 private address space
>   because it is intended for use on Service Provider networks.
>   However, it may be used as RFC 1918 private address space in certain
>   circumstances.  Details are provided in the text of this document.
> 
>   As this document proposes the allocation of an additional special-use
>   IPv4 address block, it updates RFC 5735.
> 
> The following text captures the most salient change between version 10 and 14 of this document:
> 
>   Shared Address Space is IPv4 address space designated for Service
>      Provider use with the purpose of facilitating CGN deployment.  Also,
>      Shared Address Space can be used as additional [RFC1918] space

I think it's a feature that we're finally willing to admit that this new
block is going to be used as 1918 space. Given that previous requests
for new 1918 space have been (rightly) denied, I think this document
should describe why this request is better/more important than previous
requests, and what the bar will be for future requests for new 1918 space.

> when
>      at least one of the following conditions is true:
> 
>      o  Shared Address Space is not also used on the Service Provider side
>         of the CPE.
> 
>      o  CPE routers behave correctly when using the same address block on
>         both the internal and external interfaces.

When I previously proposed this as *the* proper solution I was told that
it wasn't in any way practical. Now that we're apparently willing to
discuss it as *a* possible solution one wonders why a new block is
necessary at all.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From roberta.maglione@telecomitalia.it  Fri Feb 10 05:52:53 2012
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8224F21F84B3; Fri, 10 Feb 2012 05:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.57
X-Spam-Level: 
X-Spam-Status: No, score=0.57 tagged_above=-999 required=5 tests=[AWL=1.289, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cfa7siBcV3AJ; Fri, 10 Feb 2012 05:52:51 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id BE57B21F8527; Fri, 10 Feb 2012 05:52:50 -0800 (PST)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 10 Feb 2012 14:52:49 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Fri, 10 Feb 2012 14:52:49 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Ben Campbell' <ben@nostrum.com>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>
Date: Fri, 10 Feb 2012 14:52:48 +0100
Subject: RE: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AczlJZFTFF9sbXZqSKGvHQvAXvqfzQC0stGQ
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
In-Reply-To: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, The IETF <ietf@ietf.org>, "'Henderickx, Wim \(Wim\)'" <wim.henderickx@alcatel-lucent.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:52:53 -0000

Hello Ben,
   Thanks for reviewing this document.
Please see answers inline [RM]

Best regards,
Roberta

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: marted=EC 7 febbraio 2012 0.17
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
Cc: gen-art@ietf.org Review Team; The IETF
Subject: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-dhc-forcerenew-nonce-03
Reviewer: Ben Campbell
Review Date: 2012-02-06
IETF LC End Date: 2012-02-06

Summary:This draft is not quite ready for publication as a proposed standar=
d. There are some potentially significant issues that should be addressed f=
irst.

[Note: Hopefully this draft has had or will have a SecDir review, since it =
seems ripe for significant security implications.]


*** Major issues:

-- I admit to not being a DHCP expert, but If I understand this draft corre=
ctly, it proposes to send what is effectively a secret-key in a DHCPACK req=
uest, then use that key to authenticate a force renew message. It seems lik=
e any eavesdropper could sniff that key, and use it to spoof force renew re=
quests. The introduction mentions that there may be some environments where=
 the use of RFC3118 authentication could be relaxed, and offers an example =
of such an environment. But nowhere does this draft appear to be limited in=
 scope to such environments.

[RM] The intention is to use this method only for environments with native =
security mechanisms, such as the Broadband Access network. You are right it=
 is not clearly said in the document I can add the following sentence at th=
e end of the introduction in order to clarify this point:

"This   mechanism is intended to be use in networks that already have nativ=
e security mechanisms that provide sufficient protection against
spoofing of DHCP traffic."


I think some additional text in (perhaps in the security considerations) is=
 needed to explain either why the vulnerability to eavesdroppers is either =
okay in general, or limits the mechanism's use to environment where it is o=
kay. It also seems like that, in the best case, this mechanism proves only =
that a Forcerenew request comes from the same DHCP server as in the origina=
l transaction, but otherwise does not prove anything about the identity of =
that server. If so, it would be worth mentioning it.

[RM] That's correct this mechanism only proves only that a Forcerenew reque=
st comes from the same DHCP server: let me say this is a trade off between =
the total security provided by RFC 3118 and no security at all. In addition=
 this method relays on the same mechanism already used for DHCPv6 Reconfigu=
re message

-- The mechanism appears to be limited to HMAC-MD5, and there does not appe=
ar to be any way of selecting other algorithms. Is HMAC-MD5 really sufficie=
nt as the only choice? Is there some expectation that stronger mechanisms o=
r algorithm extensibility would be too expensive? (Perhaps the extensibilit=
y method would be to specify another mechanism that's identical except for =
a different HMAC algorithm. But if that's the intent it should be mentioned=
.)
[RM] This is because this mechanism relays on the authentication protocol d=
efined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and there HMAC-MD=
5 is used.

*** Minor issues:

-- Section 1 "
In such environments the mandatory coupling between FORCERENEW and DHCP Aut=
hentication [RFC3118] can be relaxed."

It's not clear to me what connection that assertion has with this draft. Is=
 there an intent that the proposed mechanisms be used only in such environm=
ents? I don't find any language scoping this proposal to any particular env=
ironment.

[RM] The intention is to use this method only in environments with native s=
ecurity mechanisms, I'll try to clarify this point

-- section 3:

Does this draft update either 3203 or 3118? If so, please state that explic=
itly in the abstract, introduction, and draft headers. (I think it must at =
least update 3203, since that draft requires the use of 3118, and this draf=
t relaxes that.)
[RM] Yes that's correct, it updates 3203, I'll add it in the document.

-- section 3.1, last paragraph: "...only if the client and server are not u=
sing any other authentication..."

That seems to conflict with the statement in section 3 that this mechanism =
is only used if RFC3118 is not used. That is, it's not a choice between thi=
s mechanism or any other mechanism, it's a choice between this mechanism or=
 3118.
[RM] I'll clarify the sentence

-- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this option=
 unless the client has indicated its capability in a DHCP Discovery message=
."

Why not; what harm would it do? And on the other hand, if you want to disco=
urage it, why not go all the way to "MUST NOT"?

[RM] For backward compatibility: if the client did not indicate its capabil=
ity for this feature it means it is a legacy client and it does not support=
 it, so the server should not send the nonce to this client

-- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the Forceren=
ew message using the Forcerenew nonce ."

Using it how? Is it the secret key for the HMAC calculation? (If so, why ar=
en't we calling it a "key" in the first place?)
[RM] based on the procedure specified in section 21.5 of RFC 3315

-- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew nonc=
e Protocol authentication MUST include the DHCP Forcerenew Nonce protocol a=
uthentication option."

Only if the client advertised it, right? Otherwise, this seems to conflict =
with the previous SHOULD NOT.
[RM] ok

-- section 3.1.4, 4th paragraph: ".
the client computes an HMAC-MD5 over the DHCP Forcerenew message, using the=
 Forcerenew Nonce ."

Using it how?
[RM] based on the procedure specified in section 21.5 of RFC 3315

-- section 6:

You mention this mechanism is vulnerable to MiTM attacks. Why is this okay?=
 Are there some environments where it is good enough and others where it is=
 not? (Also, do they really need to be MitM attackers? Seems like any eaves=
dropper could learn the nonce.)

*** Nits/editorial comments:
[RM] I'll address the following comments too.

-- Abstract, second sentence:

I have trouble parsing this sentence. Are the propositions correct?

-- Section 3.1.1,4th paragraph: ". configured to require ."

Do you mean configured to "require", or configured to "use"? I would normal=
ly take "requires" to mean that the server would not work with clients that=
 don't advertise support for the mechanism.

-- section 3.1.1, message flow diagram:

It would be helpful if you could avoid widowing the top of the diagram. One=
 has to keep flipping back to see the labels.

-- section 3.1.3, 5th paragraph:

Please expand "RDM"

-- section 3.1.4, first paragraph: "The client MUST."

A client that supports this mechanism MUST.

-- section 3.1.4, 2nd and third paragraph, 1st sentence of each:

I'm confused by this sentence of each paragraph. Are they intended as condi=
tionals for the rest of the respective paragraph?







Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From C.Donley@CableLabs.com  Fri Feb 10 07:47:30 2012
Return-Path: <C.Donley@CableLabs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB2B21F85DD for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 07:47:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaQ5r0maDL4Z for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 07:47:30 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id E5E5A21F85D0 for <ietf@ietf.org>; Fri, 10 Feb 2012 07:47:29 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id q1AFlO4Z006624; Fri, 10 Feb 2012 08:47:28 -0700
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Fri, 10 Feb 2012 08:47:24 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Fri, 10 Feb 2012 08:47:25 -0700
From: Chris Donley <C.Donley@CableLabs.com>
To: Mark Andrews <marka@isc.org>, SM <sm@resistor.net>
Date: Fri, 10 Feb 2012 08:47:23 -0700
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczoC0iNSDYZA1Z9SHS9RcM2ma3LyQ==
Message-ID: <CB5A8851.4048F%c.donley@cablelabs.com>
In-Reply-To: <20120209224041.758501D1BB31@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Approved: ondar
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:47:30 -0000

On 2/9/12 3:40 PM, "Mark Andrews" <marka@isc.org> wrote:

>
>In message <6.2.5.6.2.20120209091221.082cb2f8@resistor.net>, SM writes:
>> Hi Chris,
>> At 08:57 AM 2/9/2012, Chris Grundemann wrote:
>> >http://www.apnic.net/publications/news/2011/final-8
>>=20
>> I am aware of the APNIC announcement.  That's one out of five regions.
>>=20
>> >Are you proposing that every ISP on the planet be given a /10 for
>> >inside CGN use, rather than one single /10 being reserved for this
>> >purpose?
>>=20
>> No.
>>=20
>> If I am not mistaken, IPv4 assignments are on a needs basis.  In my
>> previous comment, I mentioned that RIRs are still providing unique
>> IPv4 assignments to service providers that request IPv4
>> addresses.  Even if the IANA pool was not exhausted, it is unlikely
>> that an ISP would get a /20 due to the slow-start mechanism.
>>=20
>> Regards,
>> -sm=20
>
>In none of the discussions I've seen has anyone proposed forcing ISP's
>to use this space.  It is being provided as a alternative, the same
>away RFC 1918 space is offered as a alternative.
>
>Today you get ask "have you considered RFC 1918 space?"  You can
>still get space even if RFC 1918 space would have worked.  I suspect
>a similar question, will be part of allocation proceedures, for this
>space in the future.  You need to know that the applicant is aware
>of this space.
Please remember that this draft is in support of ARIN Draft Policy 2011-5.
Should this draft become an RFC, and should ARIN pony up the /10, ARIN's
staff is likely to look askance at requests for address space for CGNs.
IMO, an IETF RFC is not the correct place to tell ARIN or other RIRs how
to allocate space; the ARIN/RIR policy processes can be much more targeted
to the needs of the community, and in this case, I think your concern has
already been addressed.

Chris
>
>Mark
>--=20
>Mark Andrews, ISC
>1 Seymour St., Dundas Valley, NSW 2117, Australia
>PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From john-ietf@jck.com  Fri Feb 10 10:16:08 2012
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 C25B621F87E0 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 10:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kEmgcFa1ptr1 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 10:16:08 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 05DA021F87DD for <ietf@ietf.org>; Fri, 10 Feb 2012 10:16:08 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Rvuwr-0003E1-Pc; Fri, 10 Feb 2012 13:11:53 -0500
Date: Fri, 10 Feb 2012 13:15:40 -0500
From: John C Klensin <john-ietf@jck.com>
To: Chris Donley <C.Donley@CableLabs.com>, Mark Andrews <marka@isc.org>, SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>	(IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <077059305C20FC38FD924991@PST.JCK.COM>
In-Reply-To: <CB5A8851.4048F%c.donley@cablelabs.com>
References: <CB5A8851.4048F%c.donley@cablelabs.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:16:08 -0000

--On Friday, February 10, 2012 08:47 -0700 Chris Donley
<C.Donley@CableLabs.com> wrote:

>... 
> Please remember that this draft is in support of ARIN Draft
> Policy 2011-5. Should this draft become an RFC, and should
> ARIN pony up the /10, ARIN's staff is likely to look askance
> at requests for address space for CGNs. IMO, an IETF RFC is
> not the correct place to tell ARIN or other RIRs how to
> allocate space; the ARIN/RIR policy processes can be much more
> targeted to the needs of the community, and in this case, I
> think your concern has already been addressed.

Chris,

To follow up on an earlier comment, the rate at which ARIN (or
other RIRs) are running out of /10s (or /8s) is probably
irrelevant, as are hypotheses about what ARIN staff might do
about requests for allocation for CGN use with or without this
policy/ block.

But, since people want to talk about it in those terms, I'd be
interested in some real data and projections.  In particular,
how many large ISPs have expressed significant interest in this,
where "large" is defined as "big enough that an application for
a /10 would be taken seriously".  Now, if one /10 block is
allocated to this use versus all of those ISPs applying for
separate ones, how much does that change the likely date at
which all of the currently-unallocated /8s are exhausted.   

If that difference is less than years, I, personally, don't
think that particular argument is useful.   Other arguments may
be, but not that one.

     john


From cgrundemann@gmail.com  Fri Feb 10 10:22:32 2012
Return-Path: <cgrundemann@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 E34AE21F8639 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 10:22:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.716
X-Spam-Level: 
X-Spam-Status: No, score=-3.716 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7UnO0RibYBsa for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 10:22:29 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id D227E21F8620 for <ietf@ietf.org>; Fri, 10 Feb 2012 10:22:27 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2761155pbc.31 for <ietf@ietf.org>; Fri, 10 Feb 2012 10:22:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=wZMOFKB8aFJyEif8pgRVczdkYydrFbaT5LQON2m5eNU=; b=c1WEfEeZP2oaY645fVqunMfPQ5Ckp+xAd6yA9cRIuc9wkI9nRehg904YFEhT15Y3h7 EmEYFR0rAx1ZpankDcA7DiMlpuKMdrK3eKAtEnuObgO5h1j/l2cRNAK7fd4dwEcjAP8a Tsi0JXDWyaZwmfBGZGMjgKDARS+euJAmiWH/s=
MIME-Version: 1.0
Received: by 10.68.218.167 with SMTP id ph7mr18343206pbc.110.1328898147677; Fri, 10 Feb 2012 10:22:27 -0800 (PST)
Received: by 10.142.105.13 with HTTP; Fri, 10 Feb 2012 10:22:27 -0800 (PST)
In-Reply-To: <077059305C20FC38FD924991@PST.JCK.COM>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM>
Date: Fri, 10 Feb 2012 11:22:27 -0700
Message-ID: <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:22:32 -0000

On Fri, Feb 10, 2012 at 11:15, John C Klensin <john-ietf@jck.com> wrote:

> To follow up on an earlier comment, the rate at which ARIN (or
> other RIRs) are running out of /10s (or /8s) is probably
> irrelevant, as are hypotheses about what ARIN staff might do
> about requests for allocation for CGN use with or without this
> policy/ block.
>
> But, since people want to talk about it in those terms, I'd be
> interested in some real data and projections. =A0In particular,
> how many large ISPs have expressed significant interest in this,
> where "large" is defined as "big enough that an application for
> a /10 would be taken seriously". =A0Now, if one /10 block is
> allocated to this use versus all of those ISPs applying for
> separate ones, how much does that change the likely date at
> which all of the currently-unallocated /8s are exhausted.

This is not about IPv4 life-support. This is about providing the best
answer to a difficult problem. Run-out date is not nearly as important
as efficient use at this point. It is not efficient for multiple ISPs
to use different space when a shared space will function optimally.

> If that difference is less than years, I, personally, don't
> think that particular argument is useful. =A0 Other arguments may
> be, but not that one.

Please see https://tools.ietf.org/html/draft-bdgks-arin-shared-transition-s=
pace
for a more thorough analysis of the motivations, pros, cons, and
alternatives for this shared CGN space. I think you'll find that those
other arguments are laid out there.

Cheers,
~Chris

> =A0 =A0 john
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



--=20
@ChrisGrundemann
http://chrisgrundemann.com

From adrian@olddog.co.uk  Fri Feb 10 11:08:37 2012
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 E90B521F8741 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 11:08:37 -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=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6MIIlimgv8N for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 11:08:37 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id B01AB21F8737 for <ietf@ietf.org>; Fri, 10 Feb 2012 11:08:31 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AJ8UlW025207 for <ietf@ietf.org>; Fri, 10 Feb 2012 19:08:30 GMT
Received: from 950129200 (cust.static.46-14-88-124.swisscomdata.ch [46.14.88.124]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1AJ8SdO025201 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 10 Feb 2012 19:08:29 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: Furthering discussions about BCP79 sanctions
Date: Fri, 10 Feb 2012 19:08:28 -0000
Message-ID: <01a801cce827$60060e80$20122b80$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-Index: AczoJzul+MIj4ApHRpW9ss/k/s81nw==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:08:38 -0000

There has been some discussion on this list about
draft-farrresnickel-ipr-sanctions-00.  Thanks for the input.

The conversation seems to be partitioned into:
- discussion of sanctions and how to apply them
- discussion of measures that can be taken to 
  help people to adhere to BCP79
- discussion about whether the IETF's IPR policy
  needs further work.

I think it is important to have all three of these discussions, but in this
thread I am focussing only on sanctions.

Within the sanctions conversation I see three broad responses:

1. Sanctions must be applied very flexibly, taking into account all
circumstances and without hard rules.

2. Sanctions must be "algorithmically" and repeatedly/predictably deduced from a
full analysis of the situation. 

3. Detailed rules are not needed, but there must be a clear line that defines
"bad" breakage of BCP79 and a well-defined sanction to use in all such cases.

Furthermore, there is some debate about who should/can be responsible for
applying sanctions.

The authors of the draft are of the opinion that in the case of work produced by
a working group, the disruption caused by breaking BCP79 is directly to "the
smooth running of the WG".  The Chair has the responsibility and the authority
to make decisions, on behalf of the working group, regarding all matters of
working group process and staffing, in conformance with the rules of the IETF.
The AD has the authority and the responsibility to assist in making those
decisions at the request of the Chair or when circumstances warrant such an
intervention.

The authors also believe that all attempts to codify "programmatic" mechanisms
or red lines will always be subject to special cases, interpretation, and
leniency. 

We would like to hear more from you about these points and about anything else
you have found in the I-D.

Thanks Adrian (and Pete)


From john-ietf@jck.com  Fri Feb 10 11:30:03 2012
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 2F73521F8796 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 11:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.704
X-Spam-Level: 
X-Spam-Status: No, score=-102.704 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XaQVWhdjyDu for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 11:30:02 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EF23221F881A for <ietf@ietf.org>; Fri, 10 Feb 2012 11:29:58 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Rvw6D-0003Jf-Ji; Fri, 10 Feb 2012 14:25:37 -0500
Date: Fri, 10 Feb 2012 14:29:24 -0500
From: John C Klensin <john-ietf@jck.com>
To: Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <CA9CD08984777E1019A5A1BF@PST.JCK.COM>
In-Reply-To: <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.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
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:30:03 -0000

--On Friday, February 10, 2012 11:22 -0700 Chris Grundemann
<cgrundemann@gmail.com> wrote:

> On Fri, Feb 10, 2012 at 11:15, John C Klensin
> <john-ietf@jck.com> wrote:
>=20
>> To follow up on an earlier comment, the rate at which ARIN =
(or
>> other RIRs) are running out of /10s (or /8s) is probably
>> irrelevant, as are hypotheses about what ARIN staff might do
>> about requests for allocation for CGN use with or without =
this
>> policy/ block.
>...

> This is not about IPv4 life-support. This is about providing
> the best answer to a difficult problem. Run-out date is not
> nearly as important as efficient use at this point. It is not
> efficient for multiple ISPs to use different space when a
> shared space will function optimally.

Indeed, although I note that it isn't a huge step from the above
to get to "we could really make _much_ more efficient use of
IPv4 space by partitioning the Internet into regions and using
explicit routing or X.75-like gateways to route traffic between
regions, thereby permitting each region to use almost all of the
IPv4 space".  One could even use CGNs to establish that model
with each ISP using almost the entire IPv4 space inside its
castle walls.    Now, I think either of those would be terrible
ideas but, as you and others are probably aware, people who
believe themselves to be serious and competent have proposed
them, almost exactly =20

Anything that moves us closer to those models gives me visions
of slippery steep cliffs and the creeps, so I feel a need to be
careful about efficiency arguments too.   YMMD, either because
you see the efficiency arguments differently, because you have
reason to be less afraid of an ultimate "islands connected by
gateways" outcome, or for other reasons.

>> If that difference is less than years, I, personally, don't
>> think that particular argument is useful. =C2=A0 Other =
arguments
>> may be, but not that one.
>=20
> Please see
> https://tools.ietf.org/html/draft-bdgks-arin-shared-transition
> -space for a more thorough analysis of the motivations, pros,
> cons, and alternatives for this shared CGN space. I think
> you'll find that those other arguments are laid out there.

I have and I agree those arguments are there (their interaction
with my fear of the scenarios above is another matter).  Again,
my main suggestion was that we just stop the discussions based
on allocation strategies or IPv4 exhaustion alone... because
they are distractions rather than helpful.

     john


From dougb@dougbarton.us  Fri Feb 10 14:09:55 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1916F21F84FD for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 14:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwba-a7J48j6 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 14:09:54 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 150C321F84F7 for <ietf@ietf.org>; Fri, 10 Feb 2012 14:09:53 -0800 (PST)
Received: (qmail 26714 invoked by uid 399); 10 Feb 2012 22:09:49 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 10 Feb 2012 22:09:49 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F3595AB.7010209@dougbarton.us>
Date: Fri, 10 Feb 2012 14:09:47 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Chris Donley <C.Donley@CableLabs.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5A8851.4048F%c.donley@cablelabs.com>
In-Reply-To: <CB5A8851.4048F%c.donley@cablelabs.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:09:55 -0000

On 02/10/2012 07:47, Chris Donley wrote:

> Please remember that this draft is in support of ARIN Draft Policy 2011-5.

Partially, sure. But RFCs apply to the whole Internet.

> IMO, an IETF RFC is not the correct place to tell ARIN or other RIRs how
> to allocate space;

I'm not going to parse the nuances of what you wrote, but I think
generally you're wrong.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From wwwrun@ietfa.amsl.com  Fri Feb 10 14:13:46 2012
Return-Path: <wwwrun@ietfa.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 30) id A152011E8072; Fri, 10 Feb 2012 14:13:46 -0800 (PST)
From: NomCom Chair <nomcom-chair@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: Nomcom 2011-2012: Selection Summary and I* Composition 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20120210221346.A152011E8072@ietfa.amsl.com>
Date: Fri, 10 Feb 2012 14:13:46 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:13:46 -0000

Hi all, 
  Several people had asked for a summary of the Nomcom
selections, and the composition of the I* bodies after the
selected persons assume office. Here they are.

IESG Selection Summary and Composition
=======================================

The Nomcom selected the following persons to serve as Area
Directors in the open IESG positions:

APP: Barry Leiba
INT: Brian Haberman
OPS: Benoit Claise
RAI: Gonzalo Camarillo
RTG: Stewart Bryant
SEC: Sean Turner
TSV: Martin Stiemerling

The complete composition of the IESG after these persons
assume their duties will be:

APP: Pete Resnick, Barry Leiba
GEN: Russ Housley
INT: Ralph Droms, Brian Haberman
OPS: Ronald Bonica, Benoit Claise
RAI: Robert Sparks, Gonzalo Camarillo
RTG: Adrian Farrel, Stewart Bryant
SEC: Stephen Farrell, Sean Turner
TSV: Wesley Eddy, Martin Stiemerling

Liaison and Ex-officio Members:

Bernard Aboba - IAB Chair
Joel Halpern - IAB Liaison
Alexa Morris - IETF Executive Director
Michelle Cotton - IANA Liaison
Sandy Ginoza - RFC Editor Liaison


IAB Selection Summary and Composition
======================================

The Nomcom selected the following persons to serve in the
open IAB positions:

Bernard Aboba
Jari Arkko
Marc Blanchet
Ross Callon
Spencer Dawkins
Hannes Tschofenig

The complete composition of the IAB after these persons
assume their duties will be:

Bernard Aboba
Jari Arkko
Marc Blanchet
Ross Callon
Alissa Cooper
Spencer Dawkins
Joel Halpern
Russ Housley
David Kessens
Danny McPherson
Jon Peterson
Dave Thaler
Hannes Tschofenig

Liaison and Ex-officio Members:

Mary Barnes - IAB Executive Director
Lars Eggert - IRTF Chair
Sean Turner - Liaison from the IESG
Heather Flanagan - Liaison from the RFC Editor, RSE
Mat Ford - Liaison from ISOC

IAB Executive Assistant:
Cindy Morgan


IAOC Selection Summary and Composition
=======================================

The Nomcom selected Marshall Eubanks to serve in the open
IAOC position.

The complete composition of the IAOC after he assumes his
duties will be:

Bernard Aboba - IAB Chair (ex officio)
Eric Burger - appointed by the ISOC Board of Trustees
Dave Crocker - appointed by Nomcom
Marshall Eubanks - appointed by Nomcom
Bob Hinden (IAOC Chair) - appointed by the IAB
Russ Housley - IETF Chair (ex officio)
Ole Jacobsen - appointed by the IESG
Ray Pelletier - IETF Administrative Director (non-voting)
Lynn St.Amour - ISOC President/CEO (ex officio)


Suresh Krishnan
Chair, NomCom 2011-2012
nomcom-chair@ietf.org
suresh.krishnan@ericsson.com


From dougb@dougbarton.us  Fri Feb 10 14:13:58 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36AA921F8535 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 14:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H98v4yC5T+Zq for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 14:13:54 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 59B1321F8526 for <ietf@ietf.org>; Fri, 10 Feb 2012 14:13:53 -0800 (PST)
Received: (qmail 29929 invoked by uid 399); 10 Feb 2012 22:13:50 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 10 Feb 2012 22:13:50 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F35969D.2000902@dougbarton.us>
Date: Fri, 10 Feb 2012 14:13:49 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com>
In-Reply-To: <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:13:58 -0000

On 02/10/2012 10:22, Chris Grundemann wrote:
> This is not about IPv4 life-support.

Seriously?

> This is about providing the best answer to a difficult problem.

The best answer is to make sure that CPEs that will be doing CGN can
handle the same 1918 space inside the user network and at the CGN layer.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From brian.e.carpenter@gmail.com  Fri Feb 10 15:32:00 2012
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 C8A3621F85D3 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 15:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.5
X-Spam-Level: 
X-Spam-Status: No, score=-103.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGMvBOZjVvn3 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 15:32:00 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 096F521F855B for <ietf@ietf.org>; Fri, 10 Feb 2012 15:31:59 -0800 (PST)
Received: by eekc41 with SMTP id c41so1119431eek.31 for <ietf@ietf.org>; Fri, 10 Feb 2012 15:31:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NVnUenNYNHWTH82qGzRz0zFv2VcJf82mYeKDdQJVyIg=; b=WFndWVb51kz4LLAwXOMNFL4cBvXS7npN+qijtzcrLxHTzCl5bs+ccRkldzB5PcN13w /LPUiU9nj56VwaTNT1zdEIi2Ehmj7iY1QEee4mDmw8hVG94LONlE0BMTP6p//PQ61sEt 0i5QForTlcjlmTjXUNrpER9SYnga2VoDXAzpQ=
Received: by 10.213.32.5 with SMTP id a5mr512822ebd.51.1328916719156; Fri, 10 Feb 2012 15:31:59 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id v51sm27861502eef.2.2012.02.10.15.31.55 (version=SSLv3 cipher=OTHER); Fri, 10 Feb 2012 15:31:58 -0800 (PST)
Message-ID: <4F35A8E5.40401@gmail.com>
Date: Sat, 11 Feb 2012 12:31:49 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5A8851.4048F%c.donley@cablelabs.com> <4F3595AB.7010209@dougbarton.us>
In-Reply-To: <4F3595AB.7010209@dougbarton.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:32:01 -0000

On 2012-02-11 11:09, Doug Barton wrote:
> On 02/10/2012 07:47, Chris Donley wrote:
> 
>> Please remember that this draft is in support of ARIN Draft Policy 2011-5.
> 
> Partially, sure. But RFCs apply to the whole Internet.

Hear hear.

> 
>> IMO, an IETF RFC is not the correct place to tell ARIN or other RIRs how
>> to allocate space;
> 
> I'm not going to parse the nuances of what you wrote, but I think
> generally you're wrong.

The RIRs get their space from IANA@ICANN, so s/ARIN/ICANN/ and
read clause 4.3 of RFC 2860 carefully.  The IAB decided that
the current issue *is* the IETF's business under that clause.

   Brian

From presnick@qualcomm.com  Fri Feb 10 15:42:35 2012
Return-Path: <presnick@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 4D22021F85C6; Fri, 10 Feb 2012 15:42:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.566
X-Spam-Level: 
X-Spam-Status: No, score=-106.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAnDowjkPCiv; Fri, 10 Feb 2012 15:42:34 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 2B34621F85C4; Fri, 10 Feb 2012 15:42:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1328917354; x=1360453354; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F35AB67.9030206@qualcomm.com>|Date:=20Fr i,=2010=20Feb=202012=2015:42:31=20-0800|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Doug=20Barton=20<dougb@dougbar ton.us>|CC:=20<ietf@ietf.org>,=20The=20IESG=20<iesg-secre tary@ietf.org>,=20IETF-Announce=0D=0A=09<ietf-announce@ie tf.org>|Subject:=20Re:=20Last=20Call:=20<draft-weil-share d-transition-space-request-14.txt>=0D=0A=20(IANA=20Reserv ed=20IPv4=20Prefix=20for=20Shared=20Address=20Space)=20to =20BCP|References:=20<20120130230332.4239.59749.idtracker @ietfa.amsl.com>=20<4F34BD74.8020807@dougbarton.us> |In-Reply-To:=20<4F34BD74.8020807@dougbarton.us> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.48.1]; bh=WgM+TfcULBKCITOGve/JoTe6tTW4uEIhET6P21z8OMk=; b=GXUKyzOv4dARzFsm9pgurcXEHwO40agqp1xljXmiDssuhUId1XBoFU4j +BX6ETF1qkvzX9f/LP7r+R8/tIAANULF53DGh6x+Qi8qSMSEsZBhilzGi e5S3NIMTUevazK/+LOUJM//riZ/DSyI92r3atVsBi398TlBZWsyDSfuuK o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6616"; a="162306794"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 10 Feb 2012 15:42:33 -0800
X-IronPort-AV: E=Sophos;i="4.73,396,1325491200"; d="scan'208";a="253448068"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Feb 2012 15:42:33 -0800
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 10 Feb 2012 15:42:33 -0800
Message-ID: <4F35AB67.9030206@qualcomm.com>
Date: Fri, 10 Feb 2012 15:42:31 -0800
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <4F34BD74.8020807@dougbarton.us>
In-Reply-To: <4F34BD74.8020807@dougbarton.us>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: The IESG <iesg-secretary@ietf.org>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:42:35 -0000

On 2/9/12 10:47 PM, Doug Barton wrote:

> As I (and many others) remain opposed to this entire concept I think
> it's incredibly unfortunate that the IESG has decided to shift the topic
> of conversation from "whether" this should happen to "how" it should
> happen.
>    

As an AD who is now comfortable with going forward with the document, I 
do want to point out that the IESG as a whole has *not* come to 
consensus on this document. There are still not the required number of 
"Yes" or "No objection" ballots for the document to move forward. So I 
don't think it's accurate to say that the IESG is only deciding "how" it 
should happen.

>>    Shared Address Space is IPv4 address space designated for Service
>>       Provider use with the purpose of facilitating CGN deployment.  Also,
>>       Shared Address Space can be used as additional [RFC1918] space
>>      
> I think it's a feature that we're finally willing to admit that this new
> block is going to be used as 1918 space.

I expect there will be clarifications as per the earlier messages in 
this thread: This is *not* to be used as additional 1918 space. (See my 
message of 2/1/12 4:33 PM -0600. ) 1918 space is guaranteed to be 
private, and devices have been built that have made the assumption that 
the space is private and they will not see it on a network that is not 
within its administrative control. This proposed space is most assuredly 
not that. It's shared and therefore has additional constraints on use 
that 1918 space does not. It is certainly *similar* to 1918 space in 
that it is not globally routeable, but it is not 1918 space.

> Given that previous requests
> for new 1918 space have been (rightly) denied, I think this document
> should describe why this request is better/more important than previous
> requests, and what the bar will be for future requests for new 1918 space.
>    

I hope it does, and if it is not sufficient, I expect text will be 
accepted by the authors. In particular, the text suggested in the 
aforementioned message was:

    Shared Address Space is similar to [RFC1918] private address space in
    that it is not global routeable address space and can be used by
    multiple pieces of equipment. However, Shared Address Space has
    limitations in its use that the current [RFC1918] private address
    space does not have. In particular, Shared Address Space can only be
    used on routing equipment that is able to do address translation
    across router interfaces when the addresses are identical on two
    different interfaces.

> When I previously proposed this as *the* proper solution I was told that
> it wasn't in any way practical. Now that we're apparently willing to
> discuss it as *a* possible solution one wonders why a new block is
> necessary at all.
>    

See above paragraph.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From dougb@dougbarton.us  Fri Feb 10 15:57:11 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0320221F84F5 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 15:57:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.563
X-Spam-Level: 
X-Spam-Status: No, score=-3.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQpouGTsE9eA for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 15:57:10 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0469E21F84EA for <ietf@ietf.org>; Fri, 10 Feb 2012 15:57:09 -0800 (PST)
Received: (qmail 15617 invoked by uid 399); 10 Feb 2012 23:57:05 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 10 Feb 2012 23:57:05 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F35AECF.5080106@dougbarton.us>
Date: Fri, 10 Feb 2012 15:57:03 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com> <4F34BD74.8020807@dougbarton.us> <4F35AB67.9030206@qualcomm.com>
In-Reply-To: <4F35AB67.9030206@qualcomm.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:57:11 -0000

On 02/10/2012 15:42, Pete Resnick wrote:
> On 2/9/12 10:47 PM, Doug Barton wrote:
> 
>> As I (and many others) remain opposed to this entire concept I think
>> it's incredibly unfortunate that the IESG has decided to shift the topic
>> of conversation from "whether" this should happen to "how" it should
>> happen.
>>    
> 
> As an AD who is now comfortable with going forward with the document, I
> do want to point out that the IESG as a whole has *not* come to
> consensus on this document. There are still not the required number of
> "Yes" or "No objection" ballots for the document to move forward. So I
> don't think it's accurate to say that the IESG is only deciding "how" it
> should happen.

I suppose that's some small comfort.

>>>    Shared Address Space is IPv4 address space designated for Service
>>>       Provider use with the purpose of facilitating CGN deployment. 
>>> Also,
>>>       Shared Address Space can be used as additional [RFC1918] space
>>>      
>> I think it's a feature that we're finally willing to admit that this new
>> block is going to be used as 1918 space.
> 
> I expect there will be clarifications as per the earlier messages in
> this thread: This is *not* to be used as additional 1918 space.

The following is not meant to be a snark (nor is anything else I've
written on this topic, for that matter), but I think it's a huge problem
that you think *saying* "Don't use this as 1918 space" is going to make
any difference at all.

>> Given that previous requests
>> for new 1918 space have been (rightly) denied, I think this document
>> should describe why this request is better/more important than previous
>> requests, and what the bar will be for future requests for new 1918
>> space.
>>    
> 
> I hope it does,

For my money, it does not.

> and if it is not sufficient, I expect text will be
> accepted by the authors. In particular, the text suggested in the
> aforementioned message was:
> 
>    Shared Address Space is similar to [RFC1918] private address space in
>    that it is not global routeable address space and can be used by
>    multiple pieces of equipment. However, Shared Address Space has
>    limitations in its use that the current [RFC1918] private address
>    space does not have. In particular, Shared Address Space can only be
>    used on routing equipment that is able to do address translation
>    across router interfaces when the addresses are identical on two
>    different interfaces.
> 
>> When I previously proposed this as *the* proper solution I was told that
>> it wasn't in any way practical. Now that we're apparently willing to
>> discuss it as *a* possible solution one wonders why a new block is
>> necessary at all.
>>    
> 
> See above paragraph.

So if we're saying the same thing about CPEs capable of doing CGN
needing to understand the same block(s) on the inside and outside, why
is the new block necessary?


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From cgrundemann@gmail.com  Fri Feb 10 16:12:39 2012
Return-Path: <cgrundemann@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 7D51621F8546 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level: 
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9im6rq+Y4QA for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:12:36 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4EBFB21F8447 for <ietf@ietf.org>; Fri, 10 Feb 2012 16:12:35 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2988094pbc.31 for <ietf@ietf.org>; Fri, 10 Feb 2012 16:12:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=5INEyB9pQ79pa/sOIhqPnK3j7cG7KqvbRZkZsogW83M=; b=u5rI28FeXGqOsuvMsdA0OP7uRrsoIPyKP+Tc/jNCy3ByRytZikVDug/5+I5l+j3N1C fZTiFiMTyTk3gT6cd0KcwZiIlVswLN8KmixWHHp1Bd7viVYJX1U1BXuOzIYJt3Amn56M xbugNvspbD5ccSsKPVm/S9m0bIQDWz3h0ruW4=
MIME-Version: 1.0
Received: by 10.68.242.42 with SMTP id wn10mr21090852pbc.25.1328919151754; Fri, 10 Feb 2012 16:12:31 -0800 (PST)
Received: by 10.142.105.13 with HTTP; Fri, 10 Feb 2012 16:12:31 -0800 (PST)
In-Reply-To: <4F35969D.2000902@dougbarton.us>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us>
Date: Fri, 10 Feb 2012 17:12:31 -0700
Message-ID: <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:12:40 -0000

On Fri, Feb 10, 2012 at 15:13, Doug Barton <dougb@dougbarton.us> wrote:
> On 02/10/2012 10:22, Chris Grundemann wrote:
>> This is not about IPv4 life-support.
>
> Seriously?

Seriously.

The birth of a shared CGN space in no significant way extends the life
of IPv4. It does provide the best possible solution to a necessary
evil (CGN inside addresses).

>> This is about providing the best answer to a difficult problem.
>
> The best answer is to make sure that CPEs that will be doing CGN can
> handle the same 1918 space inside the user network and at the CGN layer.

Are you volunteering to buy everyone on earth a new CPE? If not, who
do you suggest will? My bet is that no one is willing to drop the
billions of dollars required - if they were, we could just sign
everyone up for IPv6 capable CPE and skip the whole debate... ;)

Cheers,
~Chris

> Doug
>
> --
>
> =A0 =A0 =A0 =A0It's always a long day; 86400 doesn't fit into a short.
>
> =A0 =A0 =A0 =A0Breadth of IT experience, and depth of knowledge in the DN=
S.
> =A0 =A0 =A0 =A0Yours for the right price. =A0:) =A0http://SupersetSolutio=
ns.com/
>


--=20
@ChrisGrundemann
http://chrisgrundemann.com

From dougb@dougbarton.us  Fri Feb 10 16:23:51 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D681621F8628 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.565
X-Spam-Level: 
X-Spam-Status: No, score=-3.565 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYSHN-c4wJkp for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:23:51 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D89D221E8015 for <ietf@ietf.org>; Fri, 10 Feb 2012 16:23:50 -0800 (PST)
Received: (qmail 8772 invoked by uid 399); 11 Feb 2012 00:23:49 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 11 Feb 2012 00:23:49 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F35B513.3040900@dougbarton.us>
Date: Fri, 10 Feb 2012 16:23:47 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
In-Reply-To: <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:23:52 -0000

On 02/10/2012 16:12, Chris Grundemann wrote:
> On Fri, Feb 10, 2012 at 15:13, Doug Barton <dougb@dougbarton.us> wrote:
>> On 02/10/2012 10:22, Chris Grundemann wrote:
>>> This is not about IPv4 life-support.
>>
>> Seriously?
> 
> Seriously.
> 
> The birth of a shared CGN space in no significant way extends the life
> of IPv4. It does provide the best possible solution to a necessary
> evil (CGN inside addresses).

Ok, now THIS is a snark:  Dude, don't bogart the good stuff, pass it
around man. </snark>

We were specifically asked not to reopen the debate on the necessity of
CGN to start with, so I won't go there .... feel free to dig through the
archives on all the reasons why this evil isn't actually necessary.

>>> This is about providing the best answer to a difficult problem.
>>
>> The best answer is to make sure that CPEs that will be doing CGN can
>> handle the same 1918 space inside the user network and at the CGN layer.
> 
> Are you volunteering to buy everyone on earth a new CPE? If not, who
> do you suggest will? My bet is that no one is willing to drop the
> billions of dollars required - if they were, we could just sign
> everyone up for IPv6 capable CPE and skip the whole debate... ;)

Everyone doesn't need a new one. In fact, the only end users who need
new ones are those behind ISPs that chose to ignore IPv6, "need" to
deploy CGN, and can't actually get CGN done with existing 1918 space. I
strongly suspect that the latter number will be very small, and what
this allocation request is really about is to make lives easier (read,
cheaper) for those that didn't want to invest in IPv6, and now don't
want to have to think hard about how they do their network design.

It's also in no way clear to me how many extant CPEs would break if CGN
were deployed with 1918, and/or how many of the extant CPEs will have to
be replaced anyway to do CGN in the first place. Repeated requests for
hard data on this (by me and others) have gone unanswered, I suspect
because collecting such data would also be expensive.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From mansaxel@besserwisser.org  Fri Feb 10 16:25:51 2012
Return-Path: <mansaxel@besserwisser.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 1F90621F8699 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Or1DwBIQwwZH for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:25:50 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 862F321F867A for <ietf@ietf.org>; Fri, 10 Feb 2012 16:25:49 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id CFA6C9E96; Sat, 11 Feb 2012 01:25:46 +0100 (CET)
Date: Sat, 11 Feb 2012 01:25:46 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120211002541.GG27669@besserwisser.org>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:25:51 -0000

On Fri, Feb 10, 2012 at 05:12:31PM -0700, Chris Grundemann wrote:
> On Fri, Feb 10, 2012 at 15:13, Doug Barton <dougb@dougbarton.us> wrote:
> > On 02/10/2012 10:22, Chris Grundemann wrote:
> >> This is not about IPv4 life-support.
> >
> > Seriously?
> 
> Seriously.
> 
> The birth of a shared CGN space in no significant way extends the life
> of IPv4. It does provide the best possible solution to a necessary
> evil (CGN inside addresses).

We do not need another reason for people to delay v6 deployment. Just
saying "this isn't about sticking your head in the sand" does not make
it any more so. This _will_be_used_ as an excuse for not rolling out v6. 

> >> This is about providing the best answer to a difficult problem.
> >
> > The best answer is to make sure that CPEs that will be doing CGN can
> > handle the same 1918 space inside the user network and at the CGN layer.
>
> Are you volunteering to buy everyone on earth a new CPE? If not, who
> do you suggest will? My bet is that no one is willing to drop the
> billions of dollars required - if they were, we could just sign
> everyone up for IPv6 capable CPE and skip the whole debate... ;)

There are more than 1 prefix in RFC1918. Tell the customers to use
another one than the one you inflict on them as bad excuse for not
doing v6 quick enough. That there will be increased support load on any
provider not giving customers public space is a suitable punishment for
above mentioned failure to deliver v6.

I still strongly oppose the publication of this draft. In any form except
a complete rewrite telling providers to use RFC1918 and be done with it.

-- 
Måns, sadly enough not surprised by the fact 
      that this bad idea still isn't properly killed. 

From mohta@necom830.hpcl.titech.ac.jp  Fri Feb 10 16:39:23 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 278C021F8592 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:39:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p217KHhYBirD for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:39:22 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 2BFA411E8072 for <ietf@ietf.org>; Fri, 10 Feb 2012 16:39:21 -0800 (PST)
Received: (qmail 7183 invoked from network); 11 Feb 2012 00:52:55 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 11 Feb 2012 00:52:55 -0000
Message-ID: <4F35B869.20106@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Feb 2012 09:38:01 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120131174018.0032318C0DD@mercury.lcs.mit.edu> <DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp.twcable.com> <4F283D7F.2040207@qualcomm.com>
In-Reply-To: <4F283D7F.2040207@qualcomm.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:39:23 -0000

Pete Resnick wrote:

> and can be used by other 
> people who build sane equipment that understands "shared" addresses can 
> appear on two different interfaces.

With so complicated functionality of NAT today, the only
practical approach to build such equipment is to make it
a double NAT as:

                          +-----+   +-----+
	(a private space)-| NAT |---| NAT |-(same private space)
                          +-----+   +-----+

the only problem is that we need another private address
space used only between element NATs within the double NAT.

Can IETF allocate such address?

						Masataka Ohta

From cb.list6@gmail.com  Fri Feb 10 16:47:35 2012
Return-Path: <cb.list6@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 CF86721F8549 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.292
X-Spam-Level: 
X-Spam-Status: No, score=-3.292 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xj4lv79S5vcL for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 16:47:35 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 07EB321F8546 for <ietf@ietf.org>; Fri, 10 Feb 2012 16:47:35 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so3006416pbc.31 for <ietf@ietf.org>; Fri, 10 Feb 2012 16:47:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=K4PSrtUwZEN4PgF2wzCjNbj5Ja4LrfYy9FcUfMuCR90=; b=N8MrH+AdVVC28nPS08H5kfaN17aaoFgkJ6P2z/nvA0rrJCIC2YNu+xvxGrqyoCTsIN Pde6BeToWrsqoEOE++RuAUNyGyThoAVVBRs2ADejzWxOFYojddISUMufwn6/jtnUVM1R Pg32IJ7JNVR4N1A8dZ1i8MfDx3YimgWtcPjEw=
MIME-Version: 1.0
Received: by 10.68.73.105 with SMTP id k9mr20577310pbv.121.1328921253856; Fri, 10 Feb 2012 16:47:33 -0800 (PST)
Received: by 10.143.164.16 with HTTP; Fri, 10 Feb 2012 16:47:33 -0800 (PST)
Received: by 10.143.164.16 with HTTP; Fri, 10 Feb 2012 16:47:33 -0800 (PST)
In-Reply-To: <20120211002541.GG27669@besserwisser.org>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com> <20120211002541.GG27669@besserwisser.org>
Date: Fri, 10 Feb 2012 16:47:33 -0800
Message-ID: <CAD6AjGSMY=XV3a==6vr45RwfPiuvP+HCDWUyjtwPHH1kSVHddQ@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Cameron Byrne <cb.list6@gmail.com>
To: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Content-Type: multipart/alternative; boundary=f46d04190db44544ec04b8a597ea
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:47:35 -0000

--f46d04190db44544ec04b8a597ea
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Feb 10, 2012 4:25 PM, "M=E5ns Nilsson" <mansaxel@besserwisser.org> wrote=
:
>
> On Fri, Feb 10, 2012 at 05:12:31PM -0700, Chris Grundemann wrote:
> > On Fri, Feb 10, 2012 at 15:13, Doug Barton <dougb@dougbarton.us> wrote:
> > > On 02/10/2012 10:22, Chris Grundemann wrote:
> > >> This is not about IPv4 life-support.
> > >
> > > Seriously?
> >
> > Seriously.
> >
> > The birth of a shared CGN space in no significant way extends the life
> > of IPv4. It does provide the best possible solution to a necessary
> > evil (CGN inside addresses).
>
> We do not need another reason for people to delay v6 deployment. Just
> saying "this isn't about sticking your head in the sand" does not make
> it any more so. This _will_be_used_ as an excuse for not rolling out v6.
>

+1. This is all business. Companies have made their choices.

> > >> This is about providing the best answer to a difficult problem.
> > >
> > > The best answer is to make sure that CPEs that will be doing CGN can
> > > handle the same 1918 space inside the user network and at the CGN
layer.
> >
> > Are you volunteering to buy everyone on earth a new CPE? If not, who
> > do you suggest will? My bet is that no one is willing to drop the
> > billions of dollars required - if they were, we could just sign
> > everyone up for IPv6 capable CPE and skip the whole debate... ;)
>
> There are more than 1 prefix in RFC1918. Tell the customers to use
> another one than the one you inflict on them as bad excuse for not
> doing v6 quick enough. That there will be increased support load on any
> provider not giving customers public space is a suitable punishment for
> above mentioned failure to deliver v6.
>
> I still strongly oppose the publication of this draft. In any form except
> a complete rewrite telling providers to use RFC1918 and be done with it.
>

This is the logical path for the cgn minded. They need to deal with the
challenge of renumbering users.

I also oppose this draft.

Cb

> --
> M=E5ns, sadly enough not surprised by the fact
>      that this bad idea still isn't properly killed.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

<p><br>
On Feb 10, 2012 4:25 PM, &quot;M=E5ns Nilsson&quot; &lt;<a href=3D"mailto:m=
ansaxel@besserwisser.org">mansaxel@besserwisser.org</a>&gt; wrote:<br>
&gt;<br>
&gt; On Fri, Feb 10, 2012 at 05:12:31PM -0700, Chris Grundemann wrote:<br>
&gt; &gt; On Fri, Feb 10, 2012 at 15:13, Doug Barton &lt;<a href=3D"mailto:=
dougb@dougbarton.us">dougb@dougbarton.us</a>&gt; wrote:<br>
&gt; &gt; &gt; On 02/10/2012 10:22, Chris Grundemann wrote:<br>
&gt; &gt; &gt;&gt; This is not about IPv4 life-support.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Seriously?<br>
&gt; &gt;<br>
&gt; &gt; Seriously.<br>
&gt; &gt;<br>
&gt; &gt; The birth of a shared CGN space in no significant way extends the=
 life<br>
&gt; &gt; of IPv4. It does provide the best possible solution to a necessar=
y<br>
&gt; &gt; evil (CGN inside addresses).<br>
&gt;<br>
&gt; We do not need another reason for people to delay v6 deployment. Just<=
br>
&gt; saying &quot;this isn&#39;t about sticking your head in the sand&quot;=
 does not make<br>
&gt; it any more so. This _will_be_used_ as an excuse for not rolling out v=
6.<br>
&gt;</p>
<p>+1. This is all business. Companies have made their choices. </p>
<p>&gt; &gt; &gt;&gt; This is about providing the best answer to a difficul=
t problem.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; The best answer is to make sure that CPEs that will be doing=
 CGN can<br>
&gt; &gt; &gt; handle the same 1918 space inside the user network and at th=
e CGN layer.<br>
&gt; &gt;<br>
&gt; &gt; Are you volunteering to buy everyone on earth a new CPE? If not, =
who<br>
&gt; &gt; do you suggest will? My bet is that no one is willing to drop the=
<br>
&gt; &gt; billions of dollars required - if they were, we could just sign<b=
r>
&gt; &gt; everyone up for IPv6 capable CPE and skip the whole debate... ;)<=
br>
&gt;<br>
&gt; There are more than 1 prefix in RFC1918. Tell the customers to use<br>
&gt; another one than the one you inflict on them as bad excuse for not<br>
&gt; doing v6 quick enough. That there will be increased support load on an=
y<br>
&gt; provider not giving customers public space is a suitable punishment fo=
r<br>
&gt; above mentioned failure to deliver v6.<br>
&gt;<br>
&gt; I still strongly oppose the publication of this draft. In any form exc=
ept<br>
&gt; a complete rewrite telling providers to use RFC1918 and be done with i=
t.<br>
&gt;</p>
<p>This is the logical path for the cgn minded. They need to deal with the =
challenge of renumbering users.</p>
<p>I also oppose this draft. </p>
<p>Cb</p>
<p>&gt; --<br>
&gt; M=E5ns, sadly enough not surprised by the fact<br>
&gt; =A0 =A0 =A0that this bad idea still isn&#39;t properly killed.<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.iet=
f.org/mailman/listinfo/ietf</a><br>
</p>

--f46d04190db44544ec04b8a597ea--

From jnc@mercury.lcs.mit.edu  Fri Feb 10 17:25:36 2012
Return-Path: <jnc@mercury.lcs.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 F189921F85D6 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 17:25:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9auZKfGgBu0 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 17:25:36 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 103DD21F85D4 for <ietf@ietf.org>; Fri, 10 Feb 2012 17:25:35 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CBBC318C153; Fri, 10 Feb 2012 20:25:34 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120211012534.CBBC318C153@mercury.lcs.mit.edu>
Date: Fri, 10 Feb 2012 20:25:34 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:25:37 -0000

    > From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>

    > We do not need another reason for people to delay v6 deployment. 

The last time this issue (CGNAT space) was discussed, we were asked not to
open this can of worms. I don't know if that request still holds, but
seriously, nothing good can come of a discussion on this topic. It will
just be a lot of rhetoric, and _zero_ minds will be changed.

	Noel

From randy@psg.com  Fri Feb 10 17:33:26 2012
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 5227D21E801A for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 17:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Cq-Ono9z4+s for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 17:33:25 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF4311E807F for <ietf@ietf.org>; Fri, 10 Feb 2012 17:33:25 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Rw1q7-00096X-SF; Sat, 11 Feb 2012 01:33:24 +0000
Date: Fri, 10 Feb 2012 17:33:22 -0800
Message-ID: <m239ai9msd.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Cameron Byrne <cb.list6@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>	(IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <CAD6AjGSMY=XV3a==6vr45RwfPiuvP+HCDWUyjtwPHH1kSVHddQ@mail.gmail.com>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com> <20120211002541.GG27669@besserwisser.org> <CAD6AjGSMY=XV3a==6vr45RwfPiuvP+HCDWUyjtwPHH1kSVHddQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: image/jpeg
Content-Disposition: inline; filename="life-support.jpg"
Content-Transfer-Encoding: base64
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:33:26 -0000

/9j/4AAQSkZJRgABAQEASABIAAD/4QCMRXhpZgAATU0AKgAAAAgABgEGAAMAAAABAAIAAAESAAMA
AAABAAEAAAEaAAUAAAABAAAAVgEbAAUAAAABAAAAXgEoAAMAAAABAAIAAIdpAAQAAAABAAAAZgAA
AAAAAABIAAAAAQAAAEgAAAABAAKgAgAEAAAAAQAAAdSgAwAEAAAAAQAAATIAAAAA/9sAQwABAQEB
AQEBAQEBAQEBAQIDAgIBAQIDAgICAwQDBAQEAwQEBAUGBQQFBgUEBAUHBQYGBwcHBwQFCAgHBwgG
BwcH/9sAQwEBAQECAQIDAgIDBwQEBAcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcHBwcH
BwcHBwcHBwcHBwcHBwcH/8AAEQgBMgHUAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAAAAAB
AgMEBQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGhCCNC
scEVUtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0
dXZ3eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY
2drh4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkKC//E
ALURAAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy0QoW
JDThJfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm5+jp
6vLz9PX29/j5+v/aAAwDAQACEQMRAD8A/oC+Il3J/wAJHqsbSOQs7HBPHU1w5lZ/m3E57nmuv+Ig
B8UatkA/vj/M1xq9BX87Vna5+qUfgXoP3t60gLJ8zEkN60lKCSjZOfr9axuaC7mLecD+7Xqval3n
Oe3oajX7m3+E9u1LDC7Dkk8dDVO+moDtzbjKT+7foO1G9vWgw3G3aYmCD1HAoWB3YLvOW44puL7g
G9vWje3rVC+vbbRdMuL/AFGRltbQM8kpznAFeDXv7S/gazlCxWWt38rJgJaR4BweTkginDVbjSvo
kfRGZG4QFj6Cmsk/G5WQZ65r5kP7UWmPIy6d4L1mVwOHupggx+C1Wf8Aaf1NywPg6JYx90yTE4Pr
wK0XuLcv2M3sj6mZJI3LM52r1XNORHTckjFmznOexr5Ef9o/XXXzk0DTkHQgu7fnWFffHvx3Lxbp
pdvj5i2C7c9OtJVYp3bLWHm0fbn+eamjSaTIhZ1ZeeoC/qa/P9vjH8Q7nft1sIM8mGFRisq4+IPj
q8DPceJdSPbMRCED04pufM/dZqsDOZ+iTXTRoJLrUbeyiUkYLxpk/Umqdx4q8NW8kT3viLSbbj5k
N0jHjvgE1+Z19e32qJOmp6pqNxGuCBdSkjNYx06zXbm2hYgffZRk04Qvqxf2dfdn6V3HxW+HFliW
bxlpe2DKuqyO+T9ADXOXf7RHwq07hvFMt20BLMtrBIRg9AOK/PxLeCIFY4Y0U9lAq9HCMFlVgXAy
VA59KiaVLVsqOXuP2j7Yv/2svh5EmywsfE9+w4DQ2Lrn3BJ5rnv+GsbGaQx6f4K8UbAM+ZfFFB/W
vkv7FI0bsDJuY5yKa8EYhzdPbQ9/9ImWOlCopbGzwcF8Uj7L+EH7W/g74k+IbrwB4p0zUfhb8RjI
XtdC8TSqbTVIO0lncD5HyOfLYiQc5FfWO9o1y5ZFxlQH3s3+0D6V+KPiq4+Hes2baN4l1fQpYo2W
ZGFwyXcE2eJIXjJZGB5BUg+9e3/C39pbxj8J7PR7fx21z8VPhDLKbX/hYskMq6z4dh42m5CbVuYQ
esmA4A+YtQoqtqtH26fJnDVw3sNU7o/TtLmZmASRmb0LZqWX+0Jo5IlBDOpG5cZHHUe9WtPW01Gz
stU025tLjT7+KKe21CFCFuIpFDK4HVcg9TmvMvjx4g8S+Dvhjr2reFAX8R38sdjZEIrmOSaQRBwG
GCV3ZA9hUUYyrzULat2MHNU1zM+PPj/8Cvhf8WvBV/8AB/4j/EDTPhv4s8N3c2q6N4q1hVubfVYJ
Z/NiZsH9zLGx2MG+8oHNfnj8WdO+KXwY8PR67pXiLTdB8efDHVLbTn+J3wct002XVdHuGCPCQhCM
UwrjLZ4r7p8CfC7VfB2t+Krz4lfDfxV8U7zxfDHDqL+JZ5pSQE+Z4v7oYnG0cDaK9y1n4UfB3xr8
K9S+FNn8EfE/hbRtdRjcjT/MaVW27VdpHzkrngeoFfs9BydCFKslJxSTff5HxEoxjVlOm7XZ8r/D
H4BaP8Q9OTX/AIp6J+0b8XtSupAyyeJ9RiksX3AHkPOI15J6+1esfF74K/Dnw78BfHOpeC/hmPAn
iHwcPNa1uvsstxvXmObfCzDIIzkHtXjWia/47/Y98QaJpei+KNV1zwlHqFrY6jo3itci7tncIsqr
/wAspEBwzDlsDNfYXxy8R6br3gP9ow2Uizw6VpUMbXwypYkEBSOmQO/U1yYPE1Y4pYacIqEotqys
9Lb/AHmmIoqVL2sZNtNbnFfD74lfFjx98NtA8RQ3SmCOxglnkQly7GFckn19fpX038FfEmteJNGm
/tW4luZrRsF5Ow44/Wvgr9m3x9f+Gfgx4V0z7PHcWWp6XEpaTn+CvuD9nZFn0vVkRlkLElrdG2vn
j9K/MMdRVGc4ro2fXYepzwi2fQcls6M7CdjvOQmenFN/fnlmnU+ik4re/s18iVl8soANpJJq9Hax
lAWYhvTpXlKcmk4m5gxxOyxbGmMjf89M7afJYzeavzkbuu0nFdQltamMK7A+zGneVHF8wCsnaneb
7BsczDaXPmGLzHeMnmQn7vtVg6YY5iFmMw963RagglAQsnO0dDTkgnQjEaKD/FijkQbFKC18yPDz
sgTlU7Zq9FAdpLnkfxGrRtc8s8f4YzTkt4wRh3PsSeam0UFyssSKwZZeRT5GlK4V3DHuDV4RRA5E
aA+oAocDaeBQrLoFzNkEwZMtI47hSfzq95MjRhjOQCegPzUAkHI4PrSd89/Wp07ANMLryZnb2agL
jqc/WpVQuTjtT/Jah66DuQrI8Z2oCFbqRxipFuGQ481n3DPXpUqQndz3qy1mEIKxgKeS4FNrmWqC
7ZUWZ3G7ex565oklk3L85+Xp7VZNsinCKzL6gcVZjtNyggEexFTyJ9AM3bJJ85Ykt3NW4RO21TK5
VTkAngVd+wvjPmxKPRhzVhYIFGC43dyppqPkCM6KG5nY75EjwTye9JEtw27Mrn6mtWK1UsTH++JP
R+auC2mHCwICfQU7BcxYoQ4O7zs+tSJDOpAMhCHr1raWzu8gYcKevGKnOnsOXbjvRoF7lC1gjNzA
A+4lhxX6CfDaNk8OWhYnhRx+FfCmn2sC3kDKVJDdMV94/Dsn/hH7cZOAOlfb8CQtiZSXY+Z4k+BH
eUUUV+wHxh+AXxBtpoPFeqmf7z3Mg4OeNxxXFfZyqoPc8/jXq3j7Th/wkeqKTktM2CPqa47+zU7X
BT/Z9K/neU1zNM/VKXuxSOcaA5POPY1bW2wF8k7n7qfWtmOzhMhJLO0Jxn1xV1oUaSMpCvnkfK7c
VHtC3zdTmxbMAYIh9pd+SnTaau/2aegZt3pnvXQxQtATvxvPJ+tIbdASTcAkc7QOahTlHZiUbGUl
luWKMN++QgsSeOvNBthkAzBgZOQP5VsNDB5cYCgt/do8ojB8ojnrUubnqwPL/iXp8KeBfEGzJZbZ
yD17V+ZtpG62qkuSBkY/Gv1P+I8ZfwR4lGD/AMech6ei5r8vDucSxBSY5CsnmDpkrWlOVldnpYDS
5WZUfAc4HrT2ijjfdG2cjGRWlHaEiMhVPOcyDINb2l/DbWPEcUuoJ411DSbMtxp1lp0LH/vpyf5U
3ioHoKLk9DkYw3mKMHB7etMCxtG3mMUfJw7YAHPfNew2Hwg0tUja/wDEPiXUGjOcO0ca/kqjFatx
8IvA1wY3utNl1NR18y8lkCn/AGgMAZ981jUx0Foi/YTfQ+eJtd0OwRjPrukxrAdzIJtrsenQdaLf
XNNm2iw/tTWiei2FvNcnnnHyjHfpX1tpvgjwvpXkLZ6Fodm4HyNDboxx7txz9c108cUMS7IY4kUN
j90OM+3+Fcrrxeur/rsaww0/5kvl+tz45tbXxXqjXEdp4D8WKAARJqUMdih98SkNW2vhL4lXEDG3
8LaVA3GDqF/k9O5SNh+tfVj7Af3isSO9KhVlzHyntUvF66RL+qX3kfL9v8KfiTemSfVdW8L6FFgB
bWytZbyQZ/i3Oqq2K29O+B+pP82tfEzxBeNF92PTbaC1j/Dy1LY+tfQ0NtcPLIwyFbpmtC10DVrt
2Fvp9zIwP3lzz+lS8RUqbW+4j6rTpatt/M8Hs/gn4RQp/aOo+I9cuI3LeVqGoS7Tk+gx+Vblr8J/
hzBGYbfwZozOxyWukkkP1+bNfQlj8PfGFwh/4lc32dhkz3MexF+rEYqy3gPT7GIy654u8O6TKT/q
vtXmN+SGtZKtJaN/IznKhBXsjx6w8LeH7IrDpXh7QrIp/HZ2aDj67a4P9od5tP8Agt8SbhIFCrpU
sYjTABBU8Cvqq28E3usItz4b8IfFb4gW0XyrL4M0CZ7V+2DcEhCPU7BXMfET4FePPiF8PfGPgCb4
V+K/AereKNPNvb6x47vEihg5ID+VsJbGegIralhalDlq1FZXW5y4nMqUouMJLZn0t4A06ceBfAKy
I9ozaJp67Yzgndaoev414x+1Uni9PBGieGPBmiQ6p4m8S6vCkTXs5C2xtlNyXO0E8iIjivqXwvo8
mg+G/DmgT3tndzaHplvZG5RjtdoYFRig7ZI4rl/iJdzaLN8Pddjtw95pPiWyFtKF8zAnfyXBB4OU
kau7JakZ42jGT05rL1PmcXTaotvR2ufn1pX7evi/wgW0n4tfs9/EvUNRjby08SfDOOHV7W6HY7S6
vCeMEEDNd0n7fNjqRis/Df7NH7QF9fXByBqtvpdlGABksd85YkemK/S/X/hV4C16/u573wtppkuD
ne8Pls5ySTkGqWnfCzwN4djl1DTfDlhbXEC/8fCp55UfQ9K/Z/qcH0PjJVZcrPwj+MPjPTfjt8R/
hvJBo2oaXD468R2lmdGu/LM8f2aU+YrGMkfw9jXvPi9Eb4S/tczhEaVbZAJFznJ3EA/RSK+O/D+s
6lqv7SnwfjK2cdpo/jq+jiitVILZu5vmI7V9leMIpovgj+15qTMGjWFEZR6YIz+tfK5TmkMzx0J0
G1FRkte6bT/FHsYzBzwVB06m94v70meGfCqF4fhp4FikA3DS7Zto6cwrX3F+zLaBte1G6y24RFdm
eO3NfHfgPTzb+CvCNvBkxQaRaIOM/wDLIH+tfcH7L9u6apqbvu3fZzjt3FfFY6Tk6kn3f5nv0FdL
0PsuCG4MkqttIY5GaSO0ZZGDgAg545qdnYknyN2P4jQMnkpsz/CK8aN4I3i7q4NbQbjuVc0z7OpB
wvlejNVqCLzZAp4z3apXt1RioPSi7GU8beM7tv8AF605SSQCcj3q+sIIHfinCEZHc+lCVwal0RT2
j0FBRiDtXDdjitr7O/aEKf73NH2WT+KbA7kUWuBkmCcGLd0NStDkEcD3rTWBYyCQZlHWQ9RU48lz
tVMk+tAzJitQYWJXecjgdaBacj9yy+5zW9FbEtxGF46r1qWSy8wAHdgHuKNguZZtAUQADPtTPsfv
/n866AaftVZQSSnGB71NNYInlQhwR980XC5ziWeGFXZbbJUeXvOK6GKCNyZCpLlSAR0p8Ns22MvE
JHiG5X7CmmNe8c7Db7Wxt2f7FTiyM0zKSMHn0FdLJYbyHlYIz87amjtYEwpczOOsR6Ci/UrkOe+x
26Dy2HlOvWQ8596ILabEoUJIufvY610hgTjzYEDH7mDwKctsTkRjEo696kfszDgteT/o5z6rxV42
5P2fzuM/nV+C0cEgq2c5JxVoW3mjcTjb2ptlWMgWzMwUljk4xVnyfI+TyeD1J5raNptjWU/aQX43
ZzTls2Y7RH9p3f8APTj8KBp2M2yVftMRCr164r7Q8A8aHAOnAr5YtLAo6kxiIqR+7HNfV/gqMLo8
LZya+64E1ry9D5LiTWCZ2FFFFfrp8YfiL4+hH/CS38odSYZmwR7muDSFRKwLIB1zmvSvHtqD4i1M
c/NM2PzrjDCjDyjAw2f8tgBzX85V1ed0fqlL4UZrxmJg0YLB+m3nNPK3RXzWg+Q873Wuggt9sUGW
iBgJwG698UxoWdEhaZVEg5B7VmlcsylgUwNKQPOUcrnnHrigWofE3BZ+qjrWt5KKFG8Et8jfQcZq
SCHBUgLk8j3oGY32RnmljEe4ICQeo6VMls7GH93GqqeZMj5fet77MrIJmOXftF0p32GeQbw8Sx90
HUilewk77HP6p4ZTxNp97osssDNqMRgSKd2AkLDAGV5GScZ7da/Ozx/8OdY8B60dF8f/AA+8f/B7
UmyIrnx/AJPD2pEfKvkapbl7ZyQdwSWRGx0GeK/WrwFow1LxTpYBxiVCrL3wa/SS90nR9W0mfQ9W
0e01XTZ4zHLpuoQRy2koZdrKRIDnIJz2+vSvYyrA0cap+1v0t6nJicxrYCUeSzT3P5LtQ8O6tpqR
G7tpJbaVt0WoWB863IwfuMuVI+hr1f4esT4fjjCRlomLMDjcBnqfzr9ovHP7Cfwq1FdSvPhdHcfC
3U7vLP4fsEM3hy4kP8T2x4Q9fniKYyflOePEvDX7KHjzw+mq6XJ8N/B8EFi+5tevdelNncMOTNFC
kBfb/sM27k81ji8hqRdoWaPSwfEVJJuasz4Na0vGnaH7JKJsD5FQkjPQ4rYsPBHia+dvLsL+SAfM
y+U+PbnHFffHwW/Z+8X/ABS8J23jDXfiP4a8HxXdzPCth8M9DEvyRybA/n3zs4bgjHl4GK+iNN/Y
++FEN0l14i1H4lePLuEHE/ifXJ1iOeuYoBHFzxxsxUx4amrc8kaVeKYy0hBs/IqXwfc27n+2b/Q9
HEgz5ep30QkwO+wtu79hV7SPCdheCYWN1qWuSk/JD4T0TU9Sdv8Ad8qFoyc985r9v/C/wX+E3gXF
94a+HnhvR7l/kN/HZwNdH/edhk/ka9Hs2tLbMltaRx7Dgm3ijjU+5+XOfpxWyyClGzk38jzKnEdW
TajGx+Kmg/AH4j6ysbaP8H/ijdAAMJNZFroMRz/EfPmV8+o8uvaLH9kb4q3cPmHwV4N0cyBcy+JN
dkuplOOdy28eOPY1+pwuwckAKD2DZppuw0U6hsNn+lelTynC0EuVX9Tknm2Lmt7I+AtE/Y98Yw8a
z4t8BaQ5GNvhjTTcSxD1DXYwT9RXoelfsgaLbtDLrnxT+I2u2yD5rWzmh0kfgbTa3619YyXgMhwg
bP8AEeM8U03JSN2b5QxwB1rrhTpU1ZQRzyxFepa9Rngdl+y18A4LhprzwIPEMnVdQ8X393q0pb3+
0SMPzWvZNL8D+BPD6CPRPCHhfQjgYubLTYFc+3CZrXS8yoG3p3Jpi3yoZQ7GQw/eH9386TxMeZOK
26I5nh5S3d/maq3L+QIpDIka9ZIvkTFeCfGbwqmp2kOq20YMtuDkDq69fxr1+61a3tdPluri4jht
IY2meeVtiKigszE9gACc1+Wev/8ABTz4b6nL4kk+GnwI/aI+OHw+8LSSRat8T/BGi2sOi2uwkOIm
nkD3WME7kxmqqUZ5zTnSjFya1+ZUKkcFJN2R6N9niJUiOJOR8/0NedeM41u/E/wc0yMRXUGp+KLZ
3tSQd4iWR92O4UjJ9K6TwT498C/GHwfpfxM+Guryar4P8Rh3h8xBDcRMshSS3lTJw6OCrDPBFcx8
YfBUXizwBrEAvrzS7/QR/aVhqmktsubaWI78g+4GCB1Ga+Qy2usJiqc6qd4S1SV+p7VeP1ilJR6r
Q+o50kFxMrwNG4kI2IOFA3ZBrOvWEWl6o7qSBbyMB64Qmvm0fHHx74R07wrpvifwFoXjqW/0m0nT
xl4d1qe2S+hkiDI8iyoSHGcNtOCQawdd+PPivUY5rHS/B3h3w+lzFJE91qdxJqBWMoQdoUDDe5r7
fMvFTh/JqkqeJxkVOm/ej73NeL1VuXftr2POwfBOa5nCMqOHbjJXTurWe2t+2/mfg18Np2vvjB8O
NZtzKssfxBuB8oyTm9mB/KvvTxnZSj4E/tWtvXakcafuzncCSece3NfLfwF+DupN+0j4U8F2epxa
3a/DW5vvFev6nOhhRSZGMMS4zgs7ORnstfX/AItWIfs6ftPXhdQL6aFCq8iNDHgA/p+dcfBNqlWC
X2ozl8pyco/g07bq+ppxInHnW9nBP1SSf4o868KB4fCPhaGGEnytPh/1Qz1iT/Cvsn9meLzNT1Ey
GVCluRt59RXyj4WtjDoWkQxgsIrSFePaMV9jfsyW7S6vrHyOCsRyXBXHI9a+exVVNSbdj0aULRTP
rY2imXchlcgDhgdtWooY5ZSkkQ8yP5sr0qS+vNK0xz/aeq2enKo+ZblwuOOuK8i8Q/tEfBPw20i3
XjJtWeE7Gg0G3uLop65CgA/nXn4bD1MQrU4OXorlSrQhvJI9eltgzbyAgboGGKYLQE4BBPXArwnR
f2sP2fNdlaJPG6aXcDodX0u5th6dWBr17SfiJ8O9cWF9G8e+F7+SZMgJcBGPPTDYxW1TA16KvOm1
6poiOJpy2kvvOht7cBuMMaumHg9Aa1bNrO9hBtZLSUxqN0tvKjj68GrQ0iaTcVLHueCK4uePc6Yx
5jn4bSTyyTKuPc9ae9nGkaSIUZ26ovLflXSwWcPlqikO390c5pyxRK8e2EF3yVxz0659KpPW1x8i
7mOIIPJQxJueTuOTTRayDnyzx13jAro1KFXESRmJf40/vHtUkVtO5bEZw3ILdKFqCjbUx47WR12g
LEeu9Ov6U9bLORJdO3sCa6IWsjxhAY1J5+XqadDaoxKsuGXnd6073LucybCJQhDTMQeitgD61fSF
CqrKkcmOgRefxroDbxTfu/JMfl/8tPWlWyEbZTac9S1K62C5g/Z2PyQIyKeo6VNHYzxZjLjEnOSc
V0T2ZlKMULBe8Pake3jMiEZI/wBr60EuotjCexiTaJ3Ry33R15q3DbRoQroXPd8cfhWn5ETTbXTO
3GGqbqcAYP8AdNRUm4hGZmy6YC6tFCiBvn3sd3P07VZFuy/vSAWbk7BWiFOBwakWKRvuoTVJ3Quc
qeV7CneXbgZMZ4cn/wCvVxLN5PuzKT3HPFTR6ZPIflkVh3pmd30ZmBoS2VHfg1MMMQNy88cmtiGy
KtKr+UI9v3jSJZRAhwVIX2oApWaiKcOvJHp15r6i8IIsWkWsQxkDPHuM187p5eGKoAcYyBivojwo
CbCJhypx8w/3RX3nAHvYiovI+a4k/ho6yiiiv1w+MPxr8bRBvEN2cZPnMP1NcotujxYj5lUnKkV6
l4ytoT4gusAYMzHnr1Nctb2cMbyMSmGPFfzfPd2P1OgrQj6HMJp8jKrFyM9ql/sy4LIREzj+/wAV
1qRrwqxIQOhNTea6fL5GdvGRWck31LUbHNjRyQCYuvuKtw6XtEG5NpQHOfpXQBSwB4GecUvlk8ZH
NKEeXeVyjGjso0t9u0Bhnr1qKNI41YtgADoa2PsUQOdxJFSGFMHK7x/c9abkg0PTPg5pqTeJ42Nt
+6t0B8wc4Oc19pvMxD7Dn58rnjIxXzP8D7JreLU9RChctsKSfT1r3p7qPAkkkdA+TlQcDHr6V7GU
4lUad+rPMxUVUlroa7TSgZP6EVBNdfuJvMBdSpPl7gu7HJXPUcA8ivn3xB+1B+zp4W8SJ4M8QfHP
4ZaR4ukfy18OahrFutyW7AjdgE5wASKtfHnxZqXhn4K/EDxRokeoX09lpck6/wBiRm5uigxvMSrk
u20kjbnPbNd9XGShyrld33OONGE1pK50nwWs49H+H+nwwQ6zYLLcXMjaVrVwl3JATcOflkUsCpBz
jNeqNdoAGk3kHoVzXxX+xV44g8Z/DLxJPo8XiqTwroHiC4tNK1bxTDJBNqFsUjl89VkAbbvkkTp/
BX0/4l8W6F4V0W+8Q+Jdf0nw3oVqhefWNcuEtbaFV6sXkIA+nX0BrnqZhU5nTa1NYUYRW52pmhkU
7o5yijduAZgPw/GqYvGT5XuLdgSPm8xRjPQHnrXwBqH7cXgjxXKdM+A3w4+J/wC0dqWTGms+C7GK
w0BCG5L6hevGmz1KKxrzvxPrX7a3j1rn/hIfi38If2XPC1yVB0z4WRXHjDxUIh/A1xN5NrG2DjCq
wBycmvcwGQ4/MV7tNpd3p/w5w4nMsPhHumfp5e3QsctdOttGOWlnYIijruJPAHueK8I8Vftbfs1e
BpZrXxV+0N8FdBvbVis1hqHibThcRkdQU83cD7Yr4C1X9nv4FeIlQ/Ey/wDjB+0BfQkOL74u+JLi
ezd/732SApEg/wBnBxnqa7bRPCXwj8Jizi8F/Av4N+GUslCpNDoNtJIuO4kKmQnvkk19ThfD3Ezt
KpWtftv+LPMrcSRhtDmPX9T/AOCk/wCx1A5tdF+KV78Rr9zhLD4UaBqXiWZj7fZbeRfxzis1f+Ch
3wtmmU6Z8Ev2vtVhddv2u2+GOuRRyH0G+NBn3wKxovGut2cRt7S5j0uNvvRaVEsURHpjI4+gqs/i
zV3XYdX1CRQdwXzNqA+wxxXsw8OqH/Lyo5f16HBU4lnN6RsdDd/t++D9PMUtz+zp+2Lb2khwGm+H
WpTn6YTJ/MVTH/BS79mm2VI/Gll8bfhM75xP8R/AWvaZAvuZGtmT9awT4m1mOQTLqN0jodwRZSck
nucVYXxt4m8wp/aEk2/7/n4USe2071qa3hvharvGpJBHiOpD7CZ0XiX9tf8AZg+IXwm+Kr/DT4+f
C/xbrlv4Y1N7fwzBrFtDqUhFnIRi3lZZT0/uV4X4Lmv9J/Zd+CXh7z7u3trbwXC8th/qAWkiZ2kK
4wd3Tft7da0PiT8PPhF8ZdGudF+K/wAHPhr4ztZkMZm1TTITcICMbo5VUOmM56k181eHfhX49+CO
q6/4f8I+Lr7xJ+zXeaBcNaeEfHNy1zqvhS+TO2Gyl5822kRiCGwVwODmvT4a4Xlw5ObU+ZS72uvu
uc+aZp/acIqMeVo6j/glr4beb9kDxLrRiaV7r4o+LWtpxIZcQjUWVxk/dTKsAvbPSvvJ9Liuonhl
gEsM6lHjGDuUjBHNfH3/AARvvRf/ALHNzo2d6W/jTxNcHeM5aTWJ8gf419932kyWFzNBGgBDZJbj
A9vWvwHO5ueMr/4n+Z+iZYn7CCbu7I+VbrSrz4caVf6drPhGT4j/AAu00TXFlb2dzHa6r4eBdna3
iZ2USwfNlQxLKc4HSvkj44ePvEmlaz4a+E3wJ+EviMfFz4oIZNJPxMuDa6VaRCPzZLichv3mxOdg
znpiv1Q1LQNP1vTr3R9RgE1hqUTRTRDAYqR29+9flZ+zp40uvix+3r8ePCvxGudR8QeMP2bLJdN8
Pa4kw+xGzuNokZ0PIlChVHtn1pYfLcuzX2mJxmEp1atJKSk4pyette9n+B0SzLGZe40cPXlCE7px
T0+R9K/s0fsvyfA3wRr0fifV7bxr8VviNK134n8dwxjfezbQqwR8Dy4YwcIoA4OTzXzl8W/Ckvhz
9m39peCaOKO4k1mGMN/eiCLj+lfrLHblOAfKSMgCMc+YT3Pp0r4D/bIubS0/Zv8Aj25sTCf7esoz
PHgs25Y16d+SK93gavOtj5zm7vlk/wAvuS2SWx5Ge01ToxiurX3nxD4pl13w14EbXdPsLi4RBbwJ
cIjKsayMqGRWA4YZ4r6e03w3beA1WPQ7zU9ZuWiSKW48RapdN5rhQSxQOEP4rV/4s2Vtp37KVg5h
CfbLyyBm4U4Mq4Bz9a+cf2sBrl9P4E0DSvEGs6Bb3/iSGO4n8NXHlXJiwd2e2MAfWvruA1h54Ovi
K1NP2b3snovU8fiGpWlWpUYStzJaH0jqHiTW5PKnvtEjuW3bVewSF2DY4GOSRx1NYJ8b2dtGwuJd
Y0ZwScNayW8XJ/vR4WnxfsQ/tAPbeHdU+HP7SOqCz1axNz/YvjG0F0UIQEZdWzjBx0/nXN6j8F/2
5fCt2dIj0v4afEiO1gE5h06aeznljyecOpQE88Zr6bBeIeVVfcVTkXZxt+h4tXIcVR3XN8zrrbxv
oty2LfxXay7Y9qwtMXOSen7xj/KtQGzvhDcCy0bVZpB8zPbQTsT74WvH/A9lr3jHUfEejfE/4Rt4
I17w66RMt9IjpKWGcqyferZb4Z+Abu+n0/SdWey1aEkPa6XeHeD3+XINfZ0cTHGU1Ug01La3VHiz
hKleErprc9itbiezMqNpukWMUqfKlvClszAemxVJ/WvO/FHxZ+HujRi31r4sR+Fri0zxpXi+Swki
+qLNnPtivzY/bM8CeJ/ClxoKS+OfFGq+HtQ3hNLe6kt1jPuqEh/qTXwbpthZ2yzGytktwr7Hd48S
lvXcd2a5cZSw9aTUqSfqkzpo1KsUpRm18z9jfEf7V3h7w2s7+FP22Pi/DdxnMel29lD4rtR+NzbS
MR/wIV51ov8AwVe+NXw48VaFceIdX0H48/Dm4uo4NWXUfC0fhbVLCBnAN0jQyIkxAOdvl5PvX5me
WmSxUeYej7QxH48GsS4tFjbVtS1HUHbTzFzYsNyqByWya+dxXC+XYuLUsPFeit+R6eFzTEUGrVG/
U/uF0i7sNf0HSNe0aR59H1+CO8tWmG1vJljDxkg89DWx9lR02twcdjivP/gsqXPwf+Ft3bSrcRT+
HtPcGM5AU2yYr05IGlYIQyg98V/OPwSkpdz9Mpz5opmfHDAPKj2tGy5zIx/SrAC8qkasf73A/nWo
bUhRGqpj17mlSxJba/y/Q1YzJdWH3kC575BoSAzBzvI2DO1clj+A5Nby2Ea5LH5SQNzdMnoK+Q/j
78d4fDmof8K9+GvjDwdpvjy3Il1TVtaV7tdFtjwH8lHTzJGPAG8Y61vgcvqZlXjSoq8pGGIxkMHB
zqOyR9U29hJIpMbu8Z6sMmpf7PEcq8qxIyI2I8xvYL1J9gK/Hy++MWoeKBc6Xqnxy8Z+ItYP7t4d
G1i28PhD02hYgZFX0+djg9a8nufAugRX322fSvE82oZ846vP4l1SS4zn/WLKJfve+AK/QsN4YYyq
r1KsY/e/yR83V4toxtyxbP3hbT5DMCYdgOPlf5SD6EHoatLYKjlpYTGRwfMBB/XrX476D8RvF2ia
c1ppPxF+JNlEhUiV9TTVQgHYi7V2J9cEV6FZftO/GjSIi+leKfBPjKa24bT/AB3os2nyP/vXVvJL
z7+UPpXBjfDnM8NrTUano7P8Ua0eKsPP4k18j9ShawsrONm0HBJ4xVsmCMJHGq78ct2P41+eWgft
rfEFbCSTxv8AAfQtTayXeG+GHilNRlb/AHYr6C1Kn0Ac/WuhsP8Agoj8Fo4/M8a+DPjp8LZI/nlu
PE/hxru0Vf8AaktJJv5GvAr8M5jhNauHkvRX/FX/ACPVo5xhqv2z7wjbdnJihP8AexmoFdEP+kZk
z0ZPWvlzwB+2/wDshfFLUjo/gn9ov4YajrecHRdVvTpN4D6eXeLE2foDX1NCIJoIL1HW60+4G6PU
bMieCT6Mmc141alKhK1ROL89DtjXhU+GSY1TyDjI9PWld9mQIwAeMNwRV9Y18wIhO7swZefcDOT+
VMl8rcrOrTuc4Y8cioUk9iozUthtmBMwjMOAepAr6D8NIE02NV6YFeDWEuJNhUDf3Fe9+HuLGMc8
jqOlfe+H/wDvNT/D+p85xG/3aN+iiiv1w+MPym8XWanXLkufmMzdPqa5UWcPOQ3JPf3rtfFrltcu
iFb5JGYg/U1zJhde27PORX82VLxk0fqdJrlS8iKKOOPscD8amMgycDj3qSO1mkPC9fWp/IK/KyLu
Xg9Kz9TUz+p+tSeUx/HvWmLJyAQkfPPakjQSfdU/jT5RNX6mcInJAAyTUn2K5chQjLk/eIPFai2r
hgdmMHrmtOCB5J4o1dizsAAT15qWrlHtfgG2Nl4f2q7xtcSbmzxxivj/AP4Kj/E74o/B39hD48eN
/hTqq6R4stbaytYtYiZvtFrbXV/Bb3MkRUgpKIZXKNnhsHtX23FPbaPoRuXV1itLcyNtBY8L6V+J
n/BWD9oZPEf7F/xm8M2WkMlpqMuk2zXdw21udXtRwBXo5PHmxNGO65o/mjhx1N+zm12ZrfsTfsrf
sn6x8NNBtPGv7P8A8NfiPrPi61ZtQ8YeP9Lj1XXdQn6tNJcyh59/TlHBzg8Yr68/ZU+J2i/BT9jH
4ZeI/jx8QbXQdO0aO+tLLVtd1IXt1LZxalcx2VshbfLdSJb+UgQZduQQdua8O/YrupP+FaaHFHHC
ptY5hE8g37Plzkg4z0x7Zz1Fcr+yh8MvAvhPwh4G+MvjSSf4ufGq6siNN1jxSQ+neF7RZHSC00+3
IKR7UC75yDJI2STzmv3fiXhl8SeypxlyJb2XS2h+b5ZmrwPPKevRH0vafHf9ov41X7yfA3wNpXwA
+DNuNo+Kvx702RdXumPUadozNGVjXlvMmIyWGFNcDdfAn4V399PrHxY8T/Eb9p7xA0plM3xv1eW9
0GOQHIaPSbXybNV/uo8b7cDJPNekalr2pa/cfaNWvrm/lAxum7AnOFySQPYk/h0rElbyuUQbP7q9
TXq5Pwlhcr1ULtdXqzPE5tWxWrdl2OhPiDU4bGDR7A2vh/QrXi30nw7DHY2kIH8PkwqqbenAA981
hyeY7PI2JnkOS02Nv/AVA+Ue3Pfnmq6yMxVdrHfyOelWN4QASLIpPCkLkMfTPavp4wjFaI827k0N
j+T92WDMPQYFT7fdfxNVA4DuxBBHGOpz6cU9/OLH5JFDJuXgYOOMZ7fjWkE3oCnpoNnt/OypbC/7
PWo0tnRQq5YDuazta8R6H4Y0e/1zxHrWlaRpelQtcXOoXtwghijCk7i2cc4PHXjpXkuhfHLVvH8U
l98FvgD8ffjToEPDeKvCOkR2emufWOS9lh81fR1BB9axq1oUfidilTdTVHtywtk+Zg+3U1GCNowP
3leB+JP2lvCfw1h3fHjwf8TvgDc4LbfiTosxtMdgLq186Ak+m+sBf2tfhNd263+g6V8X/F+lSIsi
614S8Gare2UgJwCsoiCsB3YZAqI4ulNXUkEqEtkj6oyg5dhjvjmvPviWbm2+H3iy4Q5MdpKRzzgo
a8Ntv2z/ANn4atbaJ4h1bxv8PNRvmCW5+J3hrUtCtpmPRfPniEQJ7ZYV6x8WtTtr/wCEfirVdKuL
TVtLu9PcxXWnyiWOUGM/dK5z9RWtOpGurwdyWn1Ri/8ABFdGX9lm6ZimJPFPiE7ieM/2xcdfyr9W
vFVgbhIZXVFmzy9rzxX4h/8ABJH4/fAr4UfsgeHE+IvxJ8LeA317W9c8ux1q53XE0g1u6DMFQEhf
9ogV+5uj6rpHiLTrXV9GvrXVdH1CNZLfVbGVZreeN1ykiOOHUjnI6cZxX8n5xCX1uu2mlzPf1P1z
AVY0qcFfWy/I87i09FnRWllmz2XkV+If/BOZYNX/AG+/+CjeqXkEhvrfXfs0cq8kRLMwAPp0FfvJ
c2UllePFHHuLOGC+vPavwb/4JlTTXX7e3/BSB0hMY/4SKVTE+Mgrcn0rpyaH7nGO/wBhf+lE5hO1
Whp9p/kfuPFYq4jWJH8yF9ziTpj2r4A/bdsr6D9lb4qXT20Eh1HxbpwBU5baZYl5r9HTDMz7XIjL
kSZHcDgivhP9rPTZNa/Z2+JenhpGH/CYWBVW9pomx9eK7uCE/rtR/wByX6HJxBK8IP8AvI89/aG0
aKL9mnwlaXEbMuoalYfJjoPMXAH5V8uftQ6S994o+Fthp11daM134kZX1OzVHcIiOwBBUntX3B+0
raxQ/A34cQFjIBq9gpT23CviP9rXQ9U1rxt8K7HQ72XStRi8SSyC7X5QB5cpGSOW9MAV9PwZ/wAi
XG/P8UeNnWuOw7P0AtfDfxf+GWs/DnxV4Qudb+Jeo+J9AksrnT9VIksbMjyzBMI42VVCnOTjJB56
V12g3v7WGmeO9bOoaR8JfGpitITNJbzyadcuh/hA+ZFI5HHpWZ4D0L9qzQNe0lNJ8VfD3x1pKaZH
IsF5utTb/KoNswALbyCCGIxwc16Ppnj74y+HvGniA+Jfg3Ne+Tp0Ilm8Eara3iABm5CPhjxX5a06
mi5Xp1PpHaL3PlLxtc+KNR8beMpfFHhNfB2siRUNpFdi8gI8oDKNxz9BX573XgP4mv8AFrQptI8A
S6JZ6ZIHvfGUcrsNQUuTvb5sHg4/Cv0q+IXi7TPGPjbxT4ktrDUdMhi2xvF4gtzBNFIIw3I6e1fO
svxj0zTr/wAORa3pjWp8WStFaT2c0U7sA20F0DZXJz+lf07wlC2V4W/8q/Nn5nmj/wBqq27/AKL/
AIJ8J/8ABRAzwar8M47aZlgkS4MkA+4zKM5/WvzfXzMNvJbf8x4xzX6Y/wDBQ6326p8MN2CUiusn
GM/KO1fm6TFyCG9OMV6eIhabsRh6d4lONfNOOgPc8VleIbSN/DuthXWNnt5AHm+6DjvWztO9AuBG
pz71neJY5B4X8QlJFikjs5WEh5521zyTSOiMLNH9rP7P9g9n8DPg7E5iaZPDGmg+V8qN/oqcj1Fe
xIB8jPsVX+uf0r8hvgD8f/iHoPwp+GVmdQGqw22h2QWS8XPAt04x0xxX1Nov7WF4reVrHhhbjcP+
Pi2fYR/wGv5XxeEnGq23/Vz9UoaRXyPtcBGbGDgc7iDiiQxs+I8AAZLMcD9a+cNL/ac8CX6xrfW2
paXI7BS8g8xR+VemaZ8V/AGpRmW28RWYCuFKXEZO/PsaGuU05rFH4zfEix+Efwy8ZeOr94xPodqR
aWs67lubpwBDEB/ExcqMDmvxwl8N2Wk/2hqWsWsep+MfEzjVNe1y/VJru5uJF3tCWYEhIs7FjGAM
V9OftN/Fex+IvxasvA+jss3hT4FGPVdUmhcS29/qsqHyLbHQ7FO8+nFfkz/wUJ/aXh/Zj+AHiTxz
CkWp+NPEJGm6NYNL++uryU5Dcf3Ac59q/b/DrI1gsPLG1V709l2Xc/PeI8e8VNUY6W39T5N/aJ/4
KH/sm/Cv4oap8OvFfw9Hi/xJagNJc+A9OMt1EO26aIrsbvtzniuR8O/8FOP2J5pbaFfFv7TvwuaU
7TPc2+pzWsXsVZpB+lfjH8Cvh7r2sS658Q9aiv8AU9ev7yXUL3VbCe0+3R3LtvZ9twfnUZxtHpX0
b4y8T2Gp+Fpknk0TXdU1UhA2q+HFsNTTHBYTRnYR9B1r79V5PXRHgRpq9j9qPBP7bv7O/ikxxeCP
21Ph7qUkhx/ZfxQjg0+cE/wu0yRH9a+gtP8Aix8Sb6DdoX/Clvihp5HmK/gjXIRKyeoCu6/nX8nl
34R0i9+0QS6TDO8iEeU0cZLEn+IlD6+1W5P2fvCFrJeXum67qfgbXdBgEjajpEFxaN5p+6iT27cE
9ian2reonTvtof1vw/HCPTXDeOPhr8QvDt0ijL2Vm2qWaL/z03wsRj3C1vaf+0b8I97wt8VdM0e6
usg2etzS6c7jOPLZZcDPscV+Vv8AwSBvPiz4j8MfFCf4j+P/ABV438M+D9SistEPiKeS5kdPL3Sx
tI5DPtPGTX6vfFbSfBd18O/GOoeN9F0W40yw064nMuoW8UuzERClTjcGL4Aye9ehTqzqQu0l9/6H
M4qMkr6nN+O/A37N3xOs4rv4ieCvgn41gmwbfWNWsdPuLtDj7y3KKJvfiSvnfVbTwZ8JXvNV/Z5/
aa/aa+EPiGxPmWdj4G8b6lqGiRv/AM8/sOotc2yp7BMV8QfCfTtU0vwVYW+sLbxy77idVRS/lxPI
TGMH0XHAr1eORvKWWNui5ZW5LcV52Jw9LGq1WmpLzSf6HTTrTp6xdj9lP+Cav7f/AMTfid8XPEX7
Lf7TPi3w34u+Idvpba94P8dafpQ0q91mwR9lyl3HFiDzkcqd6AbgeQK/cRCzwxyGORwobLgccnrX
8hf7CdtdJ/wU9/ZwdRL9nfwt4jjfzZC6kFrVzxjgDjA+tf17tLbxqq+bLleNsf3TX8+cYZdSy3Gu
NKKipJOy26n6Jw/iJYiheXclhi2zReYcAnqpr3/w6f8AiXwquCgH3u9fOhuEjkZNwzwQ+eBX0B4S
l8zTIskkkDmvU8P3bEVG+y/Mx4k/ho6qiiiv1w+LPzN8T2THXL6QIPLmZ1VSehz1rnEtZVUB5FQD
gcZzXf8Aii3I1O5lKqUWQ/MWwTzWFFbwMBvYMvYJyVr+ba+s5PzZ+r0k+VNGFDbYn2SLIGC5Lg4G
fSpTE5JIgJ9yea2Y7ZpJmQBiN+fNIwSPpViS1kLvtZgM9BWV2jTlZiCK5AHmOsKn1XOKIrFkj3BQ
w9jXRixmYDfGZBjvSwWMcEbIVaT3JouHIzFjtFb5txBXnBat7SNPZ9UtFxlVYNnnn2pYLSIrxAAx
6ZNdt4bhjN8MxljGuTgc9KG7hNcqudleQ/8AEuv4ypaNrVxu9DsNfzTf8FJoTN+zB8UIHQzNDq2k
7lJwSBrFsa/ppmxJp7RYABV92/hgNp7V/Nd/wU6t/sn7OPxsCFmYahph2KMFT/a1vXp5K7Yql/iX
5nFjHejP0f5H2R+xLOo8ARRSsVliuJo1QHgDYMD9at/s8MZPgj4ILsjy20EkOQMH5J5B+tcx+wlN
9o8KNHNMGaK5DeQeWJKCug/Zxnjn+Dfhp0jP7ua8j8uIgliJ5AFGcDlsD8a/qfCp8yXkfj1WKXMv
M9vtSXQuRtJ/hNTvnhsBlHXJwaEUK0qDeDGxU7wQDg4yM9eQR+FRzpblGluELLCC27cFH054/Piu
1q25LlaN2RqkU0jujyNJCu4wIOWXOPl9SDyewGTmvLviB8X/AAt4A1TR/DCpq/jP4h+I3CaZ8LfB
sR1HWr5mOFIhQ/u0J6yuQu3BzWb4k17x9488WJ8Dv2df7L1f40XEaXGo6vf7jo3gyxJw2o3bgYd2
4jitxlnJJIAUkfqH+zP+yn4D+Amh3V7blfHHxZ8UKJvEfxj1qNf7V1icqNy5OTDChGxIVIVVUDGa
8jMcz+p+7Czb/A3oUPaNuT+R+eXhT9mH9uz4z3k7+KfEHg79kvwtaSArDoNvb+KfFsyE/dEkuILc
kdzG+CMV9M+Hv+CYXwIltG/4WX45+Pfxh1qdw1zrviPxheaasz9x5GnNBCg7bVUD1r9Ary5s9MR5
Lu/tdPtywJknkEaKF78/KKp/8JLYyWc2pW2q2upWNnHJKbi3nSR32jcVAGPoK+cr4+riLc0tTtUV
FaRsfkBpP7Ef7NOuftry+CNJ+Gl1D8N/gPoC61q2j6rr2p39preqXTBLOO4hmndJRGokcBh8x69K
/UqK9isbW10vRbaDR9O0uMQ2+k6VGIYokH3UCKMLx2GBX5WfsaftD3Hxa/aF/ar/AGgdWl0rwj4D
8fwWdho2kSDF35NjM0aXU5xks6sW2gcAjmv00huLbX9LS60e/kjttRRzBqVjIrxMChTcCpPKtk4r
wMTmH1mTjF7afdY+uyzKfZLnqw3ta5xP/CcfDT4sT+N/hhqF54V+JP8Awjj/AGLxB4MvIU1G3tXd
N6xzK4K78EMQDkDn2r88Pix8crL/AIJ+fEnRofAXgD4zXv7POqmI+J/AthpV1qfhvQEdht1PTLk7
zbheRNan904wQqEHPYaFqtx+zOdN/Zy+CHg7WPi78UdeubvXNSvUMVvcajLPcPdSXtw7kouGYL80
mQqgAdq9L+NHjz49QeCvBOmjT7v4feLvFmox2N/YYi1O0j85hHuAj3xlT8w+bK5A55FYQxElZKN0
bYnBUq91opLta/3I+6dR0L4Q/HzwDp0utaB4M+Knw48W2qXllBrFnDqVje2sgBSdAysApVuq4wfS
vhXx/wD8Elv2ZPGVnqNn4E1v4y/AS31QFJ7D4S+Kb2PT3Qg/ItpdNNBGPaNFrqP2evBPhr9k/wCL
g/Z61b9o3xL4vi+LNtc634O+EHi7T444tIEOGvI7W6RdjRElpFtxgxrwBgGv0WiaNDtDiXpkpkAf
jXvRk6XuxdrHx1SKpva6Z+Jvi79l39iD/gl/+yp40vpfCGl61dahZ6hHJ42+JttHq2oalPOZJSjS
SqVhzuIxGqgk9MmtH/gj14N+IXhz9hP4V6v8T9UurjUfiDLfeJdL0fUnJk0bS76fz7KwRSSVVImX
5DyuAK/Qb9r39mvwd+1n8CvHHwe8ZwRPY+J7R445LgF/Kl2fJKMcgg4PHpXxP+x18ctc0KS1/ZK+
Pel2Xgb41fCyBbTSbSTZ9n8VaTAhQXtm6fK0ijZvgHz85wQM18dxvSqVMPHkjzK933R7mRTj7S85
H33eQG5eKTndbkDzl/iGelfgt/wTN0uKH/goJ/wUotpg8E8niBpliJ52NOxzX75RCV3BAAjlO4Km
eASQCe4+h5zxX4bfshqPBX/BXT9uXwlcRSQzeL9GsdVgRxtDA4LEevJr4XJp2o4tdXD8nqfS5g71
KDeyf5o/b0WMG6OZtxwMBevSvjj4h2Uer+AfHemajGrW0/jeNUEhxu2hcAD8K+1UkZMLyMlkyozj
OOf1r42+Ls19pvwv1K7027ilubj4gW8b74gSqeaEb/GvQ4JqL29aS6U5P8FYwz1rlprvJGB+1ZpV
tZ/DHwBasQDFqVnkAcAq2c/qK+BP2oNCfxP8RfhLpVxd3umwzeI5t19pE32a7jGyRQyyfw8nuK+/
/wBtG6TT/g7oOopb5Fld2swAPcugPPavGPF+meE5dSudb8SW2m3UOnyO6yamuVCs3BX0bnj619n4
dYP+08txdCMrczSvva6foeFxLUWFxNCo1dK7t80fQ/hv9lL4i6PqME3w7+PHjzwr4V1iGG9vLq9n
i1O+NzGhUHfMrKY2G3KDHTtW1p+jftT+FvHWvDRvGfw1+K8sVnbMdN8R6cNEuJAWIIWWB9oIHPKn
Oa+XdK8f6T4T019f0Txpf6Jpeky+VJIl+8UEDHACujnbk46DNetaT8c/iLIYNd0Px7p2pafckGSa
9tUuEuFx8qiRMECvOxnhhj6Mb0akKi81Z/5fiKlxJTqy99Nfkcn4xm8W3vijxFefELw7p3hTXrsq
9xp1tc/bbbaEA3hiq7vToK+f7TwH8GNX8XR6nZWOjz+J9MPmxrJPKHjPXcse7HvwK968W6jqvj7U
9b1fXHhW81pBGTZEtBFgDgfxds4Ir5x8PfBq90f4myfEibxv/bq28ItotJhhS38lQCPLyHO9+vGO
a/Xskws8Bg8PQnGzjFJq+z1ufLY2vGrVnNPRs+Nf+Ch7htW+FhwWUw3e6Tt90V+bGxfr71+k/wDw
USx/bnwyQyHCw3WVII3ZVeeeRX5vFMZOenat67aqS5jfCSSiVcr6Y981leMSo8Ma224Kstm+R65G
K0+pHX8K5f4gyeT4T1dJWMX2poo1c/McNKoHA9awqvR+h0v4kfvx8K7P7H8N/AEWQwj0ayUgjGf9
GTmvQD5ePmGxe7Btp/OuS8MXFppHgzw0Lq5gtrew0uAS3d4wiiRVgQ7snv2xXxp8WP27PDmg+In+
HPwM8P6t8bPijJGc6J4StXuY7QnhfMcjy1OecswX3r+bMHl9fNJuNJXtu3ol6vZH6RVxcMJFOb9F
1foup98rASyi2WZTLkhjkggcnJPAriPG3jE+EPDur6toNvca9r1tGDY6Hpriaa4nbhB8pIUA8kno
K/OHT/gF+3p8djHqfxq+OFl8AfDl8d58D+BUj1TVjGeQJJV2wxnHB2M+M1iX37B/hRfGOsaZafFz
42eKbPwTo73WrWFrrES6jqOoS5+zQI7KFiKqC5XnI4zXu5Xw/RxWIjh/rHPN9Iq603u9jzMVm9Wl
SlUVLlXeT1+St+p9aeCfi18GPC15YfBdvih4a1H4uahcHUddtrq633F3qk/zvbySDKb0GEWMMcBf
ev5y/wBv7426v+1N+1rL8MvCq3ur+Bfgm72kOjWKMy3OoNxLIRjLFRwPSvtP4Xfs0fETxP8AEG08
O2kPxQtfBseqx6jf6z8QNPj0waIsMmf3U6tuuJ36eYo6Hrio/jH/AMEpPGel/ELxL8W/2afiNpOr
6r4sumvb/wAGeJ71rOdJm4Lw3allz3wcV+7U4TjGMIR0R+dufPJyluz5G0nwb4b0DR9FsNSOipqV
rCUk0rx3os+lh2zny1niKlvTcTXlXiBl1C7kNtaJZadCSselW9w89vBg9FLEtj8a9g8R/Bn9rrwT
Ler8Rvhf8VYrW1Qwy61bbtZtfLJySkkLOWU9eVBryQatoFuUttRuoLG5Jw1nqMbafJx7Shefxq7+
z3E5J9TP0qyuLWew1caXHeWqTCI/2isq2UzH+BmHUgHOQ3GKvePLG902ODSdDmt57nxOY0TR9GvW
vI7u4ZgsWQckHc3TPA+ldt4V8R6ZpV5ptyniJbGws7gXCRxXEdzErj/pm7bCxFfav7CXwU1n4yfH
i++P3ijSkb4d+DpJJtL1C/t4oI9T1EnasqRp8u2JS3IyCTUfG0kxyvE/Tb9i74GTfs/fAHwX4S1i
LZ4pvIjqWrS5GXuZ/ncHHoMD8K82/bN+ILy6b4d+DlhdtFN4lZNS1ieE7GjtImDJGw5wJJAvfoD6
19v+KvEmi+ENB1nxZ4gu/sGl6HavdTzy/MSqKScAevYd8ivxL1DXtd8b+JfE/wAQfEEjPqPi658+
Ozujv+z2i58mAf7qkcYFd1dunDkRzpcz5up02m7jgRKR5ZCDYdoIx0PtXRorI7eZhFbgLXMWLOyI
28sHcfKBjFdNAXlI85d2D0NcyNdWfRv7CLrH/wAFBv2fdTuDCjR6B4hQGQ4Y5FnwBX9Vk2oM5YqI
tu3d6Gv46/gF44vvAH7b/wCz/wCJNOjjkmtdC15fIl5yGFqD1r+gbS/2v0uJ449Z064iDkI08YBC
jpu4FfhXiFBvMdP5Y/qfofC1nhr+bPvb+0Iy8EbXIWVm4yOvHSvqXwFJ5ui27kZY981+fWk+LbTX
oLO/tLlZ4JWUpcJ0YHnr619+fDhhNoVvODw6D5e1LgWSWImvT8yOI/gR6HRRRX68fGH5/wDiGCKT
UbkSB2HmE4rMhtY1dvIgUFfXk12OvW4W5mRIibrzWyWGRjPFVLezYFpQ8Kyj74bofpX824h3qS9W
frVGScE0YjQS7BK0Y3N1wMc0gtWYBihyfTNdWsPnqCrxlB12/Lj8WwP1p62kZinby2YxlQGXczc+
ygqf++q5JVlDcqVRLXc59bJtqnzJBx0zRHZmQNu3D6VmeK/iF8OPAcc1x428eeCvB9nHhftHinVr
TTlVvQ+e6nP4V4FP+3B+yjv/ALP8OfGHRfHWqxuQ1t8MLW78UzbQP7ljFKB9c1vRp1MQ7Qg36Iip
iIUt5H0vDpe+NzEzAYPJ611ejW6oIpRuR4uC6dSPxr4Wk/bh8NyTzr4U+Af7V/jm3UHbdad4EutK
s3OOglvGi49yAB3NW9P/AGs/jbdWBvtL/ZOPhy3kb5Yfi3450XRrkp/e8q3kuHHb7wFezheG8wxj
Sjh5a90ediM3w9Be9UWh9/zPC4uHw7SyIVG7oOOtfzdf8FVW+yfs8/HEygAHVNKXGccf2xbc1+qy
ftm+K/DF5aN8UvgTqy+FL5N8/jz4GXy+NbHRR0K3kSLHcx7epYRMuOc4r8gv+Cm+pr8ffgl4n0z4
DXlj8T7DxX4t0ZbnUvB06XcdpYRanBPc3NwMhodkcblhjjBGa7sBkuKy/HUoYik4+8tWtHr3Ma2P
o4ihUdOV9H+R9YfsC3Yk0XV1hCl4biERiT7p3RjJz1wPrXyP4+8Wnwh+wlp3im68VeIfC2g+HfGS
NrGr+G7k2t29iNdZJ0WRQSgKj7wxg4JOMivqD9geR47rWrYELa2l3bFkIwAPLK7APwDH2IrxLwD4
Mj+Jf7FvxG8DXVmut2l3qXiC3vdFuVLLc241K63wYHIUxhsn+EAt2r+i3UUtI6XiflrklNt9z6l0
P4d/HTwboCa7+zn4svf2nvBcREl/8Jvi9cpZeM9OyoYNpt9Gnl3cLjPyzpndyHwcBPD/AMQ/jf8A
HLU4fh/8F/gv8RPhx4pmdote8efHXRZdL0jwlbgjzJCHymoSgjEaxuAzBc4XIP46/s2ftJePf2TH
034HfHw/Ef4jeCYbp28L/tB+EdOutVuLCzULjTNUihVrmIxbh5dwdysg5xjn99Phl+0t8brmDQYv
CXirWvGFlfCOaz0+7ja6e4DkEABlJK4xyWOO4FeFTx9fD3hOV/zPYnhI1kpxP0K/Zk/Zk8BfsweD
tQ8O+ERf6xr3iK5N9rnj3xGwm1fVbxh88szchMfwxLhEB4UGvpF4vlijgkkjjJy7ryRnqee5OT+N
Z+i3Gpz6ZZXOrafHpupXcSSXNnHIsoRyOeVwM/hn1rYJhWJ1TOZOuea8y7m+ZnM3ZnmHxI+Eng/4
n6Tf6X4pt9RNtfxmH7fpN5La3EfHDAoQMj3GK+CfFH7F/wAYvhpZ6tf/ALOvxx13WYri2kjPgP4o
hLlJcp0iuo1UxN2AdX7c1+pMMIeFUl3fIemaiZiJjEvyqOPl4PPv1H4UXTjoy4V+m5/Hx+z/AKr4
h+CXxEtPhf8AGnTtc8B654ajvra40nxCJImmMwKpcfKAJYyCoVh3OQCa/Sv9gD44Hwn8R/id+yP4
vu2UaJOvijwXqmo3bTnVNJvZN7JG7H940E6zRuo5CmPPWv0r/a5/ZR8CftT/AA2uvDGvWkNl4x0U
m68PeOo90N3pF4o+X50wzRP91lOVI6iv5pPGv7JPxp8AeK/AFo/7avw3+E/7TnwW14X+jeBfi9pE
mkafd27MPNhtNT3OoguoyELMu0vnIUqDXzVXLZ4Wq6kHeMvw6/mz7bBZzHF0Yxno1/wx+/WixQfC
/wDar1Tx7r9k0nhL4q6P/Zx8V4D22kXUIVxHIwACrIsZTIx8zDOaj1n4ZW3xJ/ab8c+Px48h8QfC
PxL4FtPDj+E9MuZMJfw3887XaSqdsDLHIoDIAc4z90V774PudW8R+DtCl8beHrfSfEEtsi6l4ZuH
S5ht5WQbo0ZR5cy7slXAweCOtY3j8ax4X+Gvjy9+Geh2E3i3T9Mun0/SLOBIhJcLCSke3ADncenf
GK6Y4iSpeyS07lzy6nOp7bW581eI/wBkj4i6p4x+HPjvwz+0/rGv+JPhNdTS6DN8Z/DdprsmnxzW
xjltTc232ad0IYqWZi3U5yad8W/2r/2nv2T/AAjqHxI+PXhL4DfEP4W+Gd0ur6v8Mb7UtG161t1/
1lwltdiaOXYvzFN4yOMjrX46/Hj/AILV+Kv2bPG/gP4KP8I/iV4witNKs9R1v4p+N7eOK4vxcfNc
C1tZFLXMsTiVmtVO8LHgAnAr4p/b7/4KWaP+0Pb/AAl+Fo8Yt4v+C/xK1GNvGlz4Dv0h1rSdEFxE
tzZ/YPlkSeTcqkMEYKjKM120ZVp8rcNH19DzcRhcMoSj7T4enW5/bp4Q8a6F8QPCPhHxz4Xu4NS8
O+OtMttUsLtJNhntriESI6cEElGB68Gvg/8Abz/ZYs/if4Y0f4k+Gbi68N/E34a3C3mneK9CPl3u
nyoRsuAR95RyHQ8OpYEdKq/Ab4ta/wDs9S/Db9n74v79e+H2sW0Gl+A/jnp1sLLS5rdVAstDv4kA
FpdJEEiRm4lOznNfo8I/MiuPNG+OQMNmAQ/GcOv8JXoQeua7WlJd0z5rXD1LSVj81/2NP2l9V+PX
hTxP4W+I9lBo3xu+Ec6WHiGw0391Behk3QanChyzR3EeJSMnYxYZr4u/s9fB3/Bbi2uLiRjH8Svh
o7xNGAqTGBghI9SM0v7XnhXX/wBmD9orQfj98PJLtf8AhCZ1vr/SNGDL/a2kzuGu4cdJCoaRlBzt
PTA4rz39ujxtpPgv9vD/AIJyftHaHqMk/hHxtY32kx63F+7imtbhYZVUseOVLEc+9fnc8l/svHSp
0n7taM0vJ8raX+R9KsWsRRjKW8Wj93FZRLHkyKJmX5foBmvkn4pLE/wvvJIY4HE3jYMxBIxtnz/S
vr23kFx9jf8A1kYQSLIo4IYAgZ79Ca+Ovi7HAvwcm4WJj4ymOUU5JE7c57V5fAkPfxLl0pu5253N
P2H+JHBftlx3ni/4L3/hrw6XfWtG0xdTkBicxIEK7YyVBy7fwgYzg18mWXxT+GHxP0ODw/P4p/s/
XtRtYVn0q6cWt7aXAiTcDHIQcqwPVSOK/SgfF3wl8FUuvEvxLTWU0Txfb2ENreaLp0+p7miVs+Ys
Kswxkfw/jT9X1b9g39pF59G8UXPwL8e30su+bQPEcFnZ6rDI3ILrOEmV+Qema/R/DynQwGDvTfNK
p8Svs1ofO8SzqVa/vrSO3zsfmBP8D/t/hW90nQfG763qtxdm6l1HxDBFqEDvgjDxxlFGM9uag/4S
Pwh+y18LJpfif49sbiK3czCQKIfNYEt5cacYyflC4Pucc12P7ffwF/ZJ/ZK+Ft/8VPDXjjxp8JfE
DjydD8M+EtYuNRXUZycjyrS5kCFAMAlTgZHfAP5z/Cb/AIJqftrftPW3hP8Aaf8AizYaJ4m0S+gF
5ovwb+KupPZalqESn9xc3EDjYkZwJFt2bkEZHNfoaxsIJcsbM+eUVLqUIv8AgoF+0B8Xb/xS/wCz
5+zdceLvB1uHMnifX3e2tLeLbtIa4kaKE+5XOPXvVj9k/wCKHizWvjH4T03SNHsND1fVtOvJvG2g
+E7+TWNIhPnMLaUSSM6pMFzko2DmvurWPE37THwi0pNL+J37Lvi//hG9OwjXvgmxh1HS1ULj7lup
RF9MgY/WuR8KftUfs+adcT2UehR/D+8u3El5YtpsNnJI4OdzmMKWGexqoyhiGvf2Er07+6fOP/BR
IqfE3wzBZ/ltrlueRwqdfzr83rbUbO+haSzuILxRx50DjYx7ge9feH7ePxm+D+uxeCNVtviB4Waa
ISoPPulV2jcDgA/ebgcV8CeF9I8X+Jvstl8NPhD401PTJHJj1u8sho2jgH+MzXWwn1yAc9s1zVqi
dR63OnDxfLsX41YASgKWU4+zPneT9B1qpN4K1zxjq1lpL63ZWOire2s13LPEsUcVvDIJJX3ufQYA
r2Ox/Zd8azSS3/xY+K2jeEfCrR+ZL4V8FylrjHffeHaV/wCAA/WvA9W8OW/xk14fBv4N3V14Z+DP
gh9mv+NdQZrp7o7svbJI5LPIwySVf5Ac1hOUa0Gm7X0OiN21Y+t7v4h/FX9ufxvrnwi+Eeov8Pvg
B4LkFprHxIijDz3KrgeRbl8gyNj7wyE46mv0H+A/7Onwo/Z20CbQPhfoUhkvHzf+KtYd7jV9Umx/
rJrhyWPsowo9K+Tv2UYfCnhv4n+I/CPgY2Ung7StChtlttGZZbS3lRsDLRsR5hHJJ5JJzX6HLcwx
7XkHmJFyQ7lc8+vrX4bxPWlh6zwVLSnG2i2v3fdn3mVUIygq8tZvd/ovIzfFviGz8KeHNb8S3jeV
DpNvJJ9luHwJJQMJHk9CzEDj1ryj4V+FdT8L+FP7S8SyFPHHjS6bV9ZlkYYjZx+7gXI4WNCFwec5
rlfiR4j0vxd8VvA/w/1aSOLwZ4PA8Q61NfSjy7mUMRa2pTILEv8ANyccCvaDcLqgkmV1nichm8l1
lHXoSuccV974a5KsNTnjp/FLRLyW/wB585xVmHtZqinot/U8/wDF+rX15dW3g3Rtc0HTNb1qOSW5
ufEEjGO2tgOSNgzuYZxnivlnTtbkvPE/iTxpeeGIbX4RfB+B7S8fwPqTW51SfH+sJmCl1Uc/KxJJ
60340+JPitoOl/FXT9O+BfiTxpeeKf3Wm+OfDCWWpNawkBRmNmEy7BuPyrmvKodf/Z91Ob4RfCTU
dSuvBvg2xiNx4ln8efbfDa6nNGobyHW52o7NJkgnjiv0OTk2fLRStc9k8NftD6T4b+FviP4gfEnx
Pq/hWa4e5utC8LeIbEq09n/y7IS8e52kPGQ5rsvC+ieEPjh8KtG8cfHD4Q/D9bq9tmu309rRJEjj
xlTkhWViMZBJ5NfNvj2TVf2iv2ifCPwr8J+KLbxV8A/hxHBqupuGguraS4BHkW8d1DlZFQAZUEDP
avuDxVpl74iuofDug6JovijQ/Di+dq+g65frp9lMP+WVo0jYA3EZIJHFaUpNX5tUiKkoq3mfJPjX
9nj9jDwTY6Br/wASP2cPD/hbTPGVxHaWd/bSSSrcSyEBY8JICjDIJx0Ffdvg3w34X8GeH9L8L+Dt
JsNA8PaTCYrXT9Lj2QxxkdAGyTn1OTz1r83PhT4e0X49/tKar40sPAEPgz4b/CS4ewh8Ox35vtMv
NUjc+fexssjxso/1av325xX6U+IvEml+DfDmueLPEN1DYaToVtJdz3NzhEghCkgZ6EjAX3JFGHnz
Jytt1CraMkr7nwf+3B8T7pR4V+DOjTJAviSM6nrbud5azV9iQn+75hXP0Q+tfHtkwRIcKrLGPlDZ
71ymteKdU+JHjTxX8SNTWeC48a3geCzuD89rZxjEKY7DHzcetdTbndEHyCc9RXPKTnJsfKobHU6a
MLG5kjJZ92011cb7RuABOa5PTwvkwfIp57j3NdisaiFW5yTQU9jkfBcqD9rz4IRF1Ekfh7WpSueN
pe1B9+tfp3PqVpA7LiVmfIDRsSP1zX5NeFllP7cfwqtbcSuLLwPqsjgnITfeQ4J+uDX6bTzBdoj5
fuBX41xzK2YS9Efe8NT5cMku7P0b/Zl8Sy6l4abTWnlePTpxtSTBxnvX7V/CZnfwtaltpGByK/nQ
/Zg8RS2Wu3+nyTSpHdgPtZv4s1/Q58E5Xk8I2hZywKjGTmuDg2HLi5eZXEP8NHslFFFfrh8afHWu
Kn9qXBI43nJr8rv2uv2/tY+B3x68E/ss/Crwj4L8TfFrxFoP/CWat4l+JuoSad4d8O6Q11Jawu/k
jzZ55ZkcKu5VCxHqTX60ataIby9WUtu5bC+ueDX8fv8AwVpe90f/AIKffEnWLS8kTZ8FvDO5PN2E
Aa5q3A/HJr8R4Yy6jmeYeyxCvH3nvbbU+8zbFVMLheak7N2P16/4Wj+0v4usfO8Q/tU+CvCsE0gB
0z4FeBEdUBP+qF5f3k2SM43GEZwOBXG614F0vxBJ9s8e/GD9pv4oFZiHt9b8UW+h2a/3U+z6bbxE
/i1fzceAf2kPiV4Xu4dV8J/EHxHod0RiOC7d7nTn55R4JAY2zj7yjPoa/R74Pf8ABQme7iTTfjTo
Kxzvgf8ACXeDo2uLPYOhljLF4j7gEV+4YHh/L8Jq6EU+9r/mfB4nHYqbvz3R+j3/AArP4KwzRmL4
H+AtVnWRZf7Q8Yz3+u3G8ev2mZh9RivU7HxbruiKU8L2/hvwkmc/8UnpVrpzemMxIDj8a8Z8AfE/
4ffFDTv7U8BeNNC8SwOxUrpl5H5inPIaM4dCO5Ix3r0z7LGMtC4GOozmvep4WjQ0jFW8kebKrOfx
NlrUvFPivWRs1XxBq9+rcGO5mYqQexHTFULeJsq88paKI85J4Hp9KkeJBFGwXk9TTggVYsKx3dVX
kn2reUrqyE7TLVtez6fOk+lavd6cFBB+zHbuP94gcMe3PavM/Gvwd+GHxCj1RdX0XUvBWt64S03j
j4UXKaRf3TAcefDtMFwPVCgLevNegsACWBRD2WXh6I2ZjGmcBDkFeD+Y5x7VjVoxrr3lcuFWVP4W
ec/Afwp42/Zu8QaxeS/aPjv4CnMVwmr+ArUReI7Lbn5LywL4kOD9+Fv4funPHoHwI174Vw2fxH0/
4f63b3ml6ff3d62kX/7rVLXzjLLLHLbvtkVsyOhUp0bFXm4fz0Lx3C/ckgADKfb0H0rmvGHgzwb8
SlQ+OfDcN/qbHFv4p8NTvpHiGFQpB23cG2QjnOxyyHAyOBh0oKDTirmc3zp9Lnw/4Y8c6BcftdQe
HLHTY7Wy8V+GdUfTrSUh42liubXdFyMZ2SEgdcKe1ftd+xNqnh2x8f6jpd1ZWUOpanCP7Pv5FBeN
EVlCjsBx0Ffh18T/ANkH4veG/F3gn4ifAnxpa/E2z+HOqJqcfh7xvLb6R4jgjKlLiBJwq210JEIX
a5D5AOfT7P8Ahp+0L4W0X4i+HLi5utQ+GXjVLpZG8F/E+0l0LUQGYM6RicbJkwcK8RcEEHIzXy+Y
wm6nNbc9/CtOny82x/SbAoKsvGzrt9+5p4tolOQDn61zukaymq6bZapaMqwanGtwgQ7xsYcYJ7da
37SR5EYu24g9TXn666bHnNcorzLE2zvVNt7StIuefan3ijzEPdutSgbIJEXAkIyp/nSUbJeporaW
IFM6kHLE5z8w6+309q/Mf/gp1+yAP2lfglqHiDwlpVjc/Fn4dzJqujLcxbotQ8g75NOuBnc8UgG7
ggggEYr9RocPEjfeyOvrSPbQSRyRvErrKGBL8tggggHqODjinJqTcXs0FGp9XmpLc/OL9iPxn/wm
n7OXw+1c6P4v8O3EUZjm0zxhd/b2tJhnzIY5yAzwIciMNl1XaCSRk/W0kUUgzIAyg7sds/3vrX4V
/tAfA/4hfCb49eOdL8H/ABX+LnhD4Ltr9p4qsfhJptxFHoF7OJFunVXMZuEX7QuWRJFVslSCpxX6
KfB79rPwV440iNPGOt6f4Z8R5w8V86x2z8/wt0J/GvCrw9g0pH6Jl+Iji4OS6dDy/wDbZ/4J5fB/
9sDwe2k6xotja+I4na4tdUiZopVfBxMjqQ0bAnO4Hj0r+fr4w/8ABHr4yfs++CPEvjT4a+Hofi/B
4fuIdWu7HxPOtzqN3FAxb7MBHCHJ4ypLZbvX9gtrc2WoafFc2E6ajbyRbRcWJD7hjoMGvzJ0f9nX
9o39pzxV4s+I/wC0T8cfjn8GPClrrNxaeD/gh8DtUt9FtbTToSoh1HVJERpLua4O/wDcOzIqL9wE
GnhsTOkv3c7eV9GZY6jTqtc8Lt/f95037NvxX+Hv7ef7D2n6v4c+16PqN5pR0ya1mZBcaHrNnxvY
sCUlhlVSueQBjtX3F+yF8W9T+NfwG8C+MNU8q08Voh07XEuV+X+0bR/IuS3zDq4JGK/nF8YfGPQ/
+CX/AO2f+0T8OBdPpHwL+NfhaPxxbPcSnybW98h4ru5UgAB2khV3CryZmwOa7j9hO/0H9n79i2X9
oT46QeJIPG/xJ1HWfF2m+HfEOr3hu4rKWczW48qSXy0OxlLDaG5rrrYn6m3JRbi7W+emnofOZrFS
gpT+NNp99Nmfrb+3l4dtryfwtdzxh7HUra5s3jf5Sy8gkKckjJ4Ga/nY+KnxE8VfGH/gmJoPjPUr
RbzxV+wt8Xv+EbuNRiDGWLTY7lrWOQAfdCxuhPb5a9f+Evwn/aI/b28eaV+0j4s/a68Z/C7xbdO2
peGfhrqFxHd+HtA02RR9itfsK4E0rxBZpBJuZfNIyCuB9XeA/wBlzxr+zP8AAD9or4B/Hn4WWfib
4bftIz3+qar8dvg/dz6vZQajcRMBJdWTKLizXOCCiMinGSMVw5liOeNOtGF5Qknby+1+BssFOlBK
eikv+GP19/Z0+JFv8Ufgd8I/HllPFLba/odtK7RnILKnlsf++lavNPirC4+CySsAftPiu5lBI4wL
hsGvhv8A4IkfFw+Mv2Ub34WahqUGr+IfgTrN5okn2cn9/b+a3lzDJyw4JzgfeHFfevxVWWT4H2cR
TMkGvXbLGAQSgmfmvnMkwywWLzGm1ooyt6PVHTi5/WKWGa35kcH8ZWR/AvwyaAoyNgEscvnI6e1c
t8W/2afhJqXhD4m/HXxVqtrosXh+H7dcSXFtHHAVt7VDwwKsCdoH3upqfxxq9vqPgz4WLAwndphG
IETeVORnJHQda/Nz9uT48+LP2pvFCfsB/s8390Iba/k1Lxz4wQgQWWnW6brg7ucooXGP4mKrzmo8
NE3ip9uV/mjp4pvClBX3Z8v/ALOH7Nfxk/b0+LWr/HvR5LqP4E/B3VVXRdF8XzNfjV76MAhIop9y
GFMq8i9MsozxX7oD9oT9s34XhbXxt8IvBnjLQtMiCtLpVld6PdMF4DZDSQr2xtXHtXof7A5+GPgD
9mTwX4K8HaTrPh7wl4ZjeODUtVs5AL1fMIecydZd7Akk5zgV9p6N4x8Ba1c/YNF8UeFNTukyv9jR
XEEUhHoUb5s/hzX7Dh8XRryfLJP5o+GnCVJ+/DTvY+HdA/4KCeDLpI4/iD8LfH3g+WUfP9hWDXLR
Rjkt5QRh/wACU129j4q/YR+PtwlrO/wb8TazertOmeJoYLDVGJ/h8o+U7H6Zr6Y8SfDPwB4qjki8
ReEtGu2l6SG3VbgfiADXyl8X/wBiT4Ha/wCHLu6tfDsem3qFfluUR0wW6gMDXTOEqavZWJi4PVOx
+d37cXgD4A/BzxPo+leFPgN8J0iigaeHxLrtuZXszjP7su5Vfoc1+ZWrfG/SGL22k3F/rsqDBXw1
bme2iX+7uGIx/wB9fhX0T+37+yF4C+EPxE+GcNjdazrEF9exlLTVdRuZ7NIiTlDA7mILjgDbgdsV
+Z/xY+J3iPxf4mHwH+BlpENSvlVNV1zS4x9j0iA8GdnT5FGM4XqTjiuNpzmz0qc1TgtbnK/ED4lf
EP8AaM8STfBr4Z2k3h7RVKnX/El1Puj0+HPO5gMea3RUBHvXsvhX4WaL4B0Hw/4W0H+0Rp+kazBa
SW93IDBqBkYebPIowWdu53V3Hw88KfDD4F+Gbbwfpd/Yia8kEl1fXTrNeX9233p5Am5ixPTcAB7V
0mo2E8994dRAu6+16CaNHwMoDnIPrxXBmdX9xV5eifqbYGnepHmW5+gOm6H4a8KWptPDuiaNokDY
XyNOgWDdgfeOOWP1NTHUWlQBIkmZT88bnaD+PauZlvJWk2MEdRnbvOTn69aoLebHmHmASP1XAIP5
1+CTnKS6n6QjyvRtI0jxP+0h8R4db0mWdT4WsplWV8w7lnI3YHfFejah8KPD7t5mlaz4u8MkNv36
Bd4LE9RhwRXxZ8cf2htI/Zp8S/tC/GTVI4mh8F/DyOeC2mJ2XFx55EUfXnLEV+T/AMJ/BX/BX79p
H4YL+2l4Q/aQ07w5e66JNQ0X4Eq9wLC7tkYlYvKGYssOBk5PqK/oHhKooZfR0u2n+bPy/O4f7XV6
a/oj+iAeFvirpEckWhfEa21bHCweNdPRzjPCmSBlPTvzXN61B8QrwRWXxD+DPgH4iWEXIudNnDIf
+2csZP618i6Z/wAFBLv4Q/sW237RH7X3w78S/Cf4g6Nu068+H11aGC71S/U7V+yo5+ZJDyDnAGa+
UNF/4LKfGPR9DtPij8Yv2Avjr4J+At+Vki+Jek2z3gigb7s8sbEbVxg5GRX0rrRjb3jyfZt6n6qe
D9f+EfwvS7g034c6t8NJL2Tfc28elSeS7k54cNtC/hXHeLPAWmfELxB4l1z4a/tI6r4N1DxXB5F9
oEf2W6sm+QgN5bgMHwcZBre/4bO/Zsuv2ebD9qO7+IGlP8Fr+GOR/FMkTXCwFiB5UsagsrKxwykc
V3Hh3xN8BPix8OoPir4c1XwD4k+H9/AbweNLLyo7NYVBLM0i4KbRnOTxjmtElN2vuTKJd+Bvwj0P
4NeANH8FaRfnUvIB+0avPGI2u5GHzM20nIPX6mvkT9ur4vaVe6LpPwK0XU4rvWvEVyLrVYbSTKpY
wnd5Rx03twfpX0b4M8NfBP4saJc618JPibHrujxTeTJqfgbXlvNPglwPlwjEBuQSPfpX5S/EGw07
Q/iL4x0mx1DTfEGpaHePaXuqW84uL2NgclH3ZZcdcCpq1JQhyxSsHLzO+7MO1T5bbYDGIsJtHGFH
Qfh0rvbfmHI4BPQVwtm4dUZmcb25yMd67u3AChR93jrXKimdNp28xQ+m7+tdeSzReV2Ixx1rk7B2
WCIgkbZdvHpXUozZWXOTn/U9zzTKkuh5X8Mp/wDjOq6LEv8AYPh6mQ55UvetnB7Z2iv0JudVkSYs
qqoIyWznFfnF8LHEv7anxMldHW8sPBGmwqqg7QHuZmbn3GK+8ZLgRkbWwR2PNfinGUva4+b8kfov
Dv7rCxXqe7fBbxXLYeO9OkHz29xhct8uea/qH+Alwt14G0eQtiTb9wem2v5GPDusLBr+nvbuEaCV
XXacADPWv6w/2WLqS9+Fnhi8IQi6tVYuDnJx1quD4WxLfkY8QNuim+59M0UUV+onxp8wa1I66jcA
MQM4/Wv5Kf8AgsfFcXH7eni2c2KrZwfBnw/G17HGPMlf+3taIXPcdPyr+t7WY8X80iIHZlbcGGQO
etfyef8ABZNII/25dSZLy4aS4+DGjXQsj/qyE1/VUJ9/v/rX49wX/wAjT5T/ACZ9pnmmEXyP54vC
vxs0TTvFp+GXjrRf+Edsb5mTSfGF03madqhYcxGQf8e8i/Nw3Hy+9e92+jT2y2V94a1WOS2nVlEb
skkDFewZCcfSvhv+z9X0698YPoGmWfxU+GlxqE39r+Ak8q41DTtSz+8a33fLg4UtDIGHznGCRXTe
ErOKBZrj9nb4iW/hW6Uh7n4SeNQ8kEbDpi1nInhB6BoWCnvmv3S/c+LZ9jab4v1jw5rNvrlvLqvg
/wASabIpg8Q6DOUfOP4sDBH1Ffop8Kf+ChvxL0KW2sPHmg6H8SvDiRBH1rw8xsdX35+8VYmJvoOT
X4zwfHb4lLfR+HPFPwE1yPxBJMsc2oWM0TaK69Gl3s5KjqRnkV77d+F41lW70W9uNJumwSnmFovp
6VUZNbGVWMX8R/R/8K/2pfg38Y4hbeF/FNjY60MJL4c8QMLXULVweVaI9c/3gxr35dxYcu0LdGGG
X/eBHav5LrrVNSsbizPiHTJrySxOYdb0sGOeIZzuWROR65Br7J+EH7avxl+HTWCWHiqy+JPhSKMo
3h7xyfOu4U/uJdKVcemGzXQsRr7zMZ0LfCf0HMqKrbZtxP8AD61Emd4PpyfpXxR8G/27Pgz8Sp7T
QPFt7D8LPHjuqx6F4mJitr0noIJz+7kzz8u7PrX2BP4k8OxQMz65pFswfPlyXEfCEdSc5xjpXVBx
kviMOVxVmjZkO8bznbIcqPSmIsbFElJEagqMHGMnOK831j4w/DTRHCXPiu0ZVGCtmRPg+g4NeV6t
+1F4JtmdNL0u+1iVTwSWRfqelJyjDaQ1TlJbH1DdyW/mxv5i7kGFHb8h1/GqniLw9oPxI0SXwt46
8JWPjzw9OvlyWPiGNm8lTnmKX5TE4zkEOOQODXxFqn7XPi5QToHhvw5pZX/l4nja4c+mQSQPyrzf
xF+0P8ZNfZ47vxfqVhbyjJi0MC1iXPpsxUN82kldFxhKO2h+p3gPxj+0F+y58OdX1j4d/Ey2+IPw
3+HlrLqdz8HvjtMpvV0y3jLywaZqMJMqSqgYqlwjIxx8wIr9oPgj8TtC+NXwl+Hfxf8ACyzL4X+J
ujWmuacLnb5oguYFlVHxwWXcUJ7lc96/jp0nxp4vitviJrY1zW7zVLDwfrksc2oTtOHYadLjduJr
+hb/AIJGfFnwp4q/YM/ZJ8GSaja6b4k0L4f6Ms9uziKS9JskYzKBjO4sSSOpzXy+Z0Y0pXXU7EnV
XmfqJON8pWT5AoyrevtUZmA8ssArr3PpmlZcnbMQFABQhsn6E+tRuuY8uq7gwGcc4xXnCWhLiUf6
ossfZVIxXmHxE+Mvw9+FdnNqPj3xnovhWELhYtVm2zSkdfLj5eQnP8CH614b+2Z+0Zqv7Ovw5stY
8J22m3vj3xhqEOjaJBr526dFO4LS3dySQqwQQrLKxyM7RgnpX89Xgn/gqH+y9pHxJ8VadpEniD9q
/wCOtrcvFr3xU8H6HqHixYLlm+W1intYnhsYVAISJGXIHc5rixmIdBPkjzSNIQdS1le5+qn7SXxV
8J/HbXfCsXw10vx94ntbeF0fU7jw/e6fZlWO4ZnuFjUc4PIr8mPib+zZ+1V+zhrOo+Kfg34T0/4s
/C7xJN9rvfhD4gv2ttR0dzyf7OvArRq78/6NKMNwVZcc/oL4U/4KT/BbULGHVPHth4r+GNkZDHNq
ni3SLzSrOMbsK5a6jURAcZyVHvX3H4O8b+C/iJoFv4s8C+J9B8VeHr+IiDVtAvbe6tbo9wHUvk/j
XzuJzWvW96pTVkdkMZWwElytxZ/PV4D/AOCnfgPwhqJ8I+LfG/xE/Z98R2Kqk/gn4x6XcaN9kkB5
AmO+CXPZkkArtfGf/BYD4ReFtOF9qv7Unhm9bPlQaV4TdtT1eXuES3ttxbJ6HcOT1r3T/go3+0T8
JfA623we8E/DHwB8Yv2ifFaAWnhq9tI7620FJAR9svkA+4Ac7WIHSvgj9nj/AIJ9eGI726+KPxT0
+yk+I2rjMutRWUEM1qp5+zW6qmyCL+6FUE9ya5quPo0IXkmm9l+vkvNn2OUYrFZtG7gkl1Z+b/7S
vxu+JP7Wfxo8F+P9f8MeIfAHgnxLBf6Vo194vQJ4pu4Dal2vZYMsttE7BfKRiSMEt1r77/ZP/ZL+
EvxO8Pvqvxi0P4g/FDTFgVFufGPiG7CF+hCxIAm0jIxkcVj/AB98CeENH/aX+F3gTwda3OrXPh+1
kv8AVVv2MhhjIZpGYD5ceUu7kdGFfqP8GtGi0X4c+Hbe3RVilUy4UAcOMr+HpXLnGc1vZUOV8nMu
bTs3od2XYClWxFZzXPZ2u+6Sv+JyWgfsZ/sfaGkq6X8GdQ8NT/KbfUfCniO8tLqIjoysXwp/CveP
CulfEL4YSyTfBj9qv4q6FaIixw+B/jhYQeMNFCgfdA3QTkf7XmHjsalaONgVZEIPYinAAKqAAKnA
XsK8ahmuJoO6nf1PcnllCatyWOB0Xw58ePhl8Tdb/aB8C+AfBVv8Q9XjH9ty/Am+Eng7xUg5DXmk
XCrdWs55G+CaXk/cNfWXhn9u34BftC+CLjwHd6jB8GPi74NErat8KPH++wnLbWLyQSTBTMpbJB2q
2Oq14dHc3Fk0c1pPJatFwJYWKFfyrlPiZ8N/hp8c9IXQfjT4A8MfEO2txut9Xv4DbavaHGN0F5Ft
njYDpgkHHIr1aHEKcpOrDWceVtb2PCxPDClb2UtndJnzT+0N+3ZbaPa+GPgx8BNOb4n/ABg1e4e1
gi8Mq1xb24kAVeR99gTkuMKgBJzX3J+xN+xTP+yn+zd+0J8TviDra+Nv2gfidbXM/iHXmhRIbCMq
sjadA2SzpGern77biBggV8J/DT9lTVf2V9dvfGP7MUHhX4l6dq8wlvvB/wAVbkW/i2VVOfstrqcp
QSoB0ic9cV+sVr+2b8HfjF8DvFvwxnvbz4R/Gm40ieGX4QfE6CTSdVSXZtfyGkCR36+jWztu98Gv
pOEquHwdf2GFS9m18T1k5XWj7JdD5rP8JXcFUrfEnay2SPSP2ItVWb9lz4XyeYJAsVwVaTrj7TIR
nNe2eKfBXgLxiqf8JD4X02/uQd41K2byLqJh0cMuOR1FeI/s7aOnw6+B3w+8LS3n2g6NZZmvZWSC
Jmdy33X+ZevRua9ZGsiZJpreaG6tplKvLZzRyKRn+8p+XFfkeMxFSniKsqT5WpS1Xqz6iFOM6cU1
0/Q8hsdc+NXwo+Knh/4caT8RBr3hrxPazXluvja3GptZrGM+UHjZXVee4Jr17Uviz4stobi2+Jdl
4F0LSpZbYQ+IdK1FwspMy53QygeWNuc/MTxX56ftkfto/s//ALOPxU+HvjL4iePPDHkaNpFzbNo+
m3Yurt5pE2pEPKY4diANpBP0r8+r2z/bI/4Kla/4eh8S2Wv/ALKn7GOp6xbW9oJrT7F4v8UwtJtM
9t5w863yAR57ooxygPBr9jq5jj442lNSUaLjG/NazdteXq38reZ8XHB4etRnGUW5pvby7kv7dH7Q
h/b/AP2sbD9mz9ja707XPEWiq9tqvxb8QbjoWh+U5Dyq8WTK/BxH1bsB1r0bwf8A8E+/hL+yf8PB
pmu+OvEnxH8b6tI1ze6nJGmnW2oXJP7x3T5nKc/ICele8eJ/hR8Ff2S/2gPhT8LvhH4X0HwJ4C8N
WE8YisW2XVzIIWLXVzOcNPPIR8zMSSSfWqGqvrfxZ8R6zrq3MqaJYxHDyLlVC5wOfSvI4yzvFUMV
9Xpz5Kdk3bT8dz0+HsupSpKrKPMz5yj8EeHb270bw/Z6NY6dDql/FG72saq8gyWxuPPSvIvGejQ2
PxA0PSLOOVLfSdWO03BD4C9BxXunh7UXX4i+DbGSaO6t11QYcYIOA1ctZaZZ+IPjnpumanbXElrf
6pMRDbgh+EPzcckV0ZNJ0crxM9/i9dkPMYqWLpJabHVvdW+1jcTorhyQB161RuNWhgjbyV84/nWn
8T9A0vwp4lj0q2luEaY8C7XPJPfNVZvAfiWGJZbe0iu7dk3lo3AYcZzgGvz3niktdz6Wd2z4Z+Ov
wDtv2rpv2gfgvcXKWF34z+HypaXcg+WO5SfdCW9twAP1r83/AINf8FA/jJ/wTy+A8H7Lvx5/ZP8A
jFrHxa+HiS2Xh3xD4RtDfeH9cjyfJk81eVAOMgAn6V+0fwou5YP2pvFlpKSrXPglTgDjctx1Br69
eyindc2sF08fQ3aLIR9M5xX79wlT5suoyi7PX8z8yzyX+2VU/L8kfzOft9w/tSftW/8ABOD4cfH3
4x/CKz+H3i34d+IIfEWofD3RFnkuX0tJQfOeKT5o228lK+8viD+0b8SPil+yt8LfGf7HnhL4B/HT
wBc6IIfGHgT4kawdOMFuloo8ldhIVwwYFW9OK/WfVNLsNV0+80rWNPttR0zUo2gn0++iWWCaNhhk
dWBDKQcYPFfkh8R/+CJP7GXjPVNY1fwp/wALV+DS+JZDLf6F8KfEU9hpNyScnNswZFBz0AA9q+hl
SlF3WtzzIyR+XfjX42fD/wCM/wDwR0/aSm+H/wAENG+A9j4V8QNY3nhPw7ftf2L3XnjzZoiVUgFs
8c/WvLP2NPij8Qv2OPh58RP2RPjZdpefDr9oz4e3fiLwP4rbdHbrcyWTE2nzHA3Z24HcV+z/AMQ/
+CU3w80L9h34lfsjfs3anqHhZfHNwt/Jr3jm7fUZJ7kMCS7YGAcYwoAriv22v+CbmrfHb9gv4f8A
wx0axttR/aG+BGjW40DWdJdYHuZ4ogklqsjEYWQDAyR9a53RmteqRaktjy//AIN2VeL9l34kyoAo
HjCVdpHBYww4JrlddtUT4w/tD3zOd+q+M792hUbSMNt+U+mK+jv+CI37N/xq/Zo/Z08Z+D/jv4A1
rwD4im8RteRadqbI7zR+REvmAoxBBIPftXjXxDs1tPiT8RfLtpwbjxDeTkyLgjdM2fpnitVdU4Jg
qns5NozbNpBHFGEwyNjnk13luSYgzfez1rhbEBIl2FsZOM9etdxZklUySct3+lSZN8zOq04/u4Iz
95mzz9a6aGBnbzJJ3jkHeucsVBWOb+6xGfxrpbcmSHdOfLbs3vSepZ418JruSL9rX45srxF08N6M
GaT72N0vFfXkmqnz3ZpisbfxdQtfD3w3m+0ftZ/H2bKtnRdGiDxnCrhZP619K+IPGFhoMFvLNa6v
fi7BRYdKt2mIbpvyFPA61+N8Txc8dUsr7fkj9HyRWwsPmeo6NqIj1O2cDzQGA84fKAM9MV/XB+xL
drqHwM8Hz7stHbge/Sv4tR8Q9Os7Tw9rWmyR+ILPWb+3sd27yjDJIxG04xzxX9lP7BEkp+B/h5J0
COse0eU2Y/lwMDtmt+GYThitVujkz5x9irPqfcdFFFfox8efNusf8hCf/df+dfyi/wDBaISw/t06
A0ahFu/gTbneeh8nxNdE/wDo2v6u9akKXE47bW5r+Wr/AILUq3/DZfwpl8ks978GL1NySbGIj8QR
sR/4/X4twbV/4WIx8p/kz7XPtcJ9x/J/p8d/bfGTxBH4c1pfhp8Rpwj2y3w+1eH/ABdbjBH2iNSP
3o7rncCg47V2vi7xH4Kuo4bT9oP4dp4N1QOUt/HnhC1a+0+DP/LQOoFzbsfUqVrmLWOHStT8c6V4
00G78bfDOa++02Os2my9utBuHYF4JIgPMZVcsQQQVyCOldomj+LzpD6t8EvGem/FHwZbkpceAvHT
PqDAY+aIXMhFxA3+y52+1fvifNqfFPcof2DqnhKw8P3mjftKrrfw41C+hWwi1to7+6nBlX/R45WZ
HdD3BTjJHavuMW/yLyTxnjvX5yaQPCK+KNLm0v8AZp8SeFvHM94v2qyvIYhYaeM83MM7gxH1BQBj
35r9G44dpQk846E98U0rmFeN4lUrvkdDtw3GH6Vy2p+EbC/kMtk9zY6gQcXNpjBOOldwB5pDHjnv
UU4+bIGMHt0quUXNKCVuh59KdSg8Dasl8BPe2drcLHcTD50wrYcHqD71+l3h+9u38P6Hb3F5JPMt
nCWmZifM+Qcc/wCeK/PLxXL5HhXXJQPu2z/+g1+ieljbpmmpkYW2Q4/4CtOHx/ISlzXZd757nvQe
evP1oorpGV7uWK3t5bmaeW2igG97iFwnlgAku2eqgA5FfO3hv49XHi26u9W0HwLdz+A/KkuYdaN2
q39xbRsVa6S3x+7jZlYgk5IFe2+MNMuNb8K+JdHtWeO41KwmhWeMAmMsu0Nz2Ga/PX4S/GnUPAcw
8J3fw48Y3fja6to9IudJsbFnWxnhjMPm7iu3yHUhwAeOa560pXSTKjHmufppp2qBvh18XNd02cTL
J4C1u4gjY7hg2Ei4/AMc195/sbz6hon7K/7MY0qd9PuYPAeiBbqIkPn7FGT0xxmvzx07TJdD+CXx
jsFZUm0z4dazu+zvtJY2rBkR/wDgWW+lfQnwttPjF8PPgV+z58Rvhm2r/EzwtB4H0SHW/g4WSa9d
I9PiRrrR5hiSOQKBugYlJCuBtJOfGzPVxud2Cd02fvZ8MP20da8P2UOifEPR5te0u1UIusW0mbgf
8AJ5x65r6m0z9rD4J6lbRXSeILvTppMA22rWrAoffFfhN8LfjF8Nvi9pMtx4F8U2Gq3Gl7Vv9AvE
a21bTGJwyTQSYljdW+Vgw4Ir1P7O0/2hIHMkX/PWT7igerdB2/OvMaOx4aMtX1Ot/wCC63xC8L+O
/wDgnp8bPDvgfxZeT64umNejUvDh8m4tkG0PgsAVG1iOD0LVyH/BIn9ij4C/Cr9kn4aaRpFhYazq
w06I6ldQwKzz3MyiY3EzhRvzuwOuMV4j8X/FfwW0zwprHhP42eM/Beh+HfGcJ0q50XxDqUG++juf
3QjjiBMm5icKQOCc1xX/AATo+Ok37KvxhuP2R/ilrEttpumoJfA3ijX2Mh8UaA+WjMUg4mktSfs8
g5YDyjjiuHGU5Jc66bnrZNGGGqNdXsf0Ban8BvhHq1pc2epfD/wxc2+pAo8VxarIjj0IK4Ir8Xf2
0NX8Nf8ABNPxdbQ/s7/CG80HxV8c/wDQtK0qOUL4L1W7liIkuJQgVbSWHKkjnzd3GMcfvjZajbXG
nW99Z30d3aXaK8dxbP5sThhkFW/iHvXDfGH4RfDX9oT4f6h8L/i/4XsPFvhjUMvA7ZN5ZXCA+XcQ
TdYJIsk+aOucHNeTGhCsnF6c2zPQzWlLERV/eXVdT+eL9nP9mTSPhyLz4leMNeufiJ8WvHG6/wBX
8ZamomjuJ3OTGhOWWNTgRZJyoFfRHxQ8faH8KvA+s+OPFF7KLHRoyym1Xc0j7SREPrivn34qeBP2
h/2AvFtzpPj+C7+JH7Oskw/sj4rwxFYEjY/JbXZTLW1yOhJxHJ2Ck7a+TfE/jSf9tf4nx+EIpNS0
39nT4ZRrf+ILxJRE2p3QO5bJRwWJA6LwI9x/iFfIf2NUnXlPGO0Iq8n+i7vyPclmtKNCEMIrTeiX
X1ZL8B9H1T4harrPxe8SRyxeM/j/AHRFhbSnIsNDWTiUZyQZGD4GceWF4+av1btbKDTLW0sbaMm0
sFW3RRxsYL1/Qj8a8U+DmiRXsN943ks4bQTqljp2nK/y6fYQqI4o1HoQOvevdu+O57dzXnYzFPHV
ZVbWV9F0S6JeSWx6eW4T6lRjDr1831fzCikDBs4IOOuOcUtc53geevP1pwTeNzDcsfODzTaP60PU
CT5o3DlmRJ+N9UPFeheH/HWh3Hhvx/oei+L9ECGJbXUxumt/SWFiC0cgJyrrkg9qt9eDzR3z3Heq
pTlRlzRdmROCqKzPM9B8I2fgGTTrbx94Ck/a3+CmgwsVsfEcoi+IHhqPukTyusGpwKBnywY5ACcZ
ziuV+JFh+xt440e+8aeCfht4v8LfAZ4AmofFH4E+JpdE8U+HJRxKt3pMsYkCI3LhGf5cnB4z75C1
zE6T28xhZD/x8A8x+4+teT/EL4KeCviRNrWuw3es/Db4j6paSWf/AAs3wS4j+2IYyoivLQgw3ynJ
DLKpO3jtX0mB4jbcaeIs0utv6+/8D5vG5BC/PTv6X/r7j8/PDHwh/Zh/YP8AjX4R+NfxMlt/2h/g
14w1BP7K+O/iGNNX1Tw/PcoFtTLDIGQ2zb/9cgUxtjI6kf0O/C74j+C/HfxG+Hdp4N1Oz122vrhL
xL3TG3ptRBjHt3FfzK+LPgr4v+BvwG1H9mj4v+Br7xv8IZI7m1b4s+F1l1DSLm2nleVWkjjy1i0Z
I2qBhQe44qx+xX8GP2bfBy2mufCL9oj4tfCTxbpkaxWt78K/HM8P2YqMLNLa3LS2827qQ0YHYivp
1neElyyxNL2jT0la9u3U+eqZJWqN/V5cqa1i3/wNj9b/ANtPS9b8c/toeFPDGmSLDcCaQu03cC3f
n617nbeFI/Anw41LTlVpZ/s7Fpcjk4Nfn6/gb9srw/8AEa0+NPhj9o/4U/tRavZxsItC+PuhQeG9
SiVvlbyL/TPLt/M2bsu8LZ645r2y8/aY+IM/hzWdE+L/AOzt8SvAGsiEw/214SB8V6DNx977ZYq2
B3/eKpqcdhcs4ln7SdW030Tt+H/BOWisdkkeVU/dXlc8n8FCS/8Aib4QEUYlK6iZHIGMAIc1z1pq
Tad+0H4TliBZJNami+/syCpzzXUfs6+KND1r4kK8ep25e3hmH2WZ3hlUlT/DLg5/CvF/EPiPSvCn
xJm8Qaq99qniDSb6VPD3hO3BM2q6jI22KHgZ2gkFj2GTXorJnhcBUw1OXM5X1fml/kcrzH22IhUq
K1j1T9o34l3j/FzTvAPw4+H/AIl+LvxEitjqsng7wvHCklpYpzI8ss7LGowDiMnLHGOtfRPwp+Kn
gf4w/D2XW/D9nf6fLpW/TdS8O+I7b7FqOmXCrzbyw5IRu4dWIIrwHxhr8v7P3hH7DpuoyH42/E66
j1Lxp43V8XUjghjZwMPuQR5CBR/dJ718feHvjfqkH7f/AIb03QWlj8N/GvwrLHqtnIA32i9tD8l6
W/vbTs9xX5lPARxdqGHXNKPVdWtWl8k/uPs6tWeFh7WrKybWnZM9h+GaQxfte+Jkgkk26j4SuQtq
33YtlwOM19moZIgyMR5oODt5HSvi34Wzzv8AtbeI2UoEl8KXayrxnInGDX2q4BL/AD7CCDn14r9x
4OUqWX04SVmr/mfm3EDU8VJp3Q6W4VgiqzBjxz3p4t4m6E7++KqMhO1jCRsPEvPNPWRkLEkhm719
Rc8W2mg+WHygGXedxwARkMfTI6flUzzxwQxb8l5AQIoG8xgQOhwOPqRWfdxNJFOly80SXUZiaWGR
oX2nrhlIZT7gg1V03T7bS7K3srFZha2q7FaeWSd8f7TuSzH3JJp3DlvrcbLe3Sa3p1pFo2p3CSRC
dteLwi1i5GISN/mOx65CY461+IXxuSSL4peMRLkSfbJt2PVnzX7mRriVZcjjG365r8O/jvG8/wAV
/GbSnNyt1ISeMfernxcbWbe+ptStFnndouyNV67TXcWv+oX61wtjCXjCOQGyHJ9K7y3OVUjkHHNc
y0Qm7s6fTwdluCf9SdxrpoBnNx5LHd2zjP8AhXMaf/y7f7/9a6rrGRzgnpQ9S3sj4Y0zxX4r079q
n47+FvAOhWmp+JdTsdLeTWdXBOnaVEIjuZyCPNb0QYzivZ774W+JAtv4r1X4lfEHxdrdjdxzHRtP
1CPRtPQhgdiRHefK9cnpWR8P2x8af2hZgI/MmvdPTa/fFknB9s1W8d/Eyzm8SHwjo+neLdZNhKqa
l4g8PT/Z9L0Zj2llx+8ccHZn0Ffj+fOdTH1adLS2/wBy/qx+g5SorCwlN3udmul3WgaXoEt1LCt1
qXia1u7i2iOEQs5ARB/EOMl/Wv7fP+CfrZ+BPho5/wBbHnH4mv4cmn1W68LeBLnWHlkvn1ywWS6u
l3OwEr7Tk8jdyfwr+4n/AIJ6Ef8ACh9E57cfnWnDrcsQuZ9ZHPnsEqd0ux95UUUV+iHyR83axzNc
452tk47V/Mr/AMFrIoF/aa+Bt00aSSzfC3XYVY4P/MZsj/Wv6btYGy4dBybtmDL3+Wv5p/8AgtnZ
Rj47fs1aghDNeeAPFcJxzxFqOkt/NzX4pwjJxzmmrfzf+kyPt84SqYKV+lj+WmD4R6oL/UfHPgXx
LJ4Y8QanM8l3prAy2eoSIcfvIxlTuwPmODxXl3jPRdIttUbUviFpOt/CfxZAyi1+KXw08yewJXtO
qAOg77WUqf7wr7V8Gon9jLll3G4dmX0+Yk/ka3r6yhvBNDfWovbaQbDa3AV42H0Ir+gFZ6nwcqqj
oz490rVfiXrcmhrdfEb4c+JvDsdygXxro0S/2rqOSMRzIG2xNzg4Y19kGRJGVEkSSRVLlVIJwOp+
nI/OvEX+AXwuj8X2vjaz8M2VlrmmuHMVuzrbu/ZwgbYSPp61f8SQNdfFPwVbm7ms1k0+83rFJ5UW
R5P3u2R1o6ahUh7W2ux7KMSFSeCeQrdSPWlkYYK5G4/w968t8O+O7PxJfa5ZeHdXt/FMOiN5U0gi
KOdrbWKyrw4DAg4HUV1+i6/ZapcXOmupsdVtFMxsHOZGj3YL4PO3PGaq90Y+zcVdkXjBS/hHXYwQ
GktyBn34r9HrNEitYID8zRwRkSdjlVr84vFkfneHdTj3hPNgUBz7yiv0dgj8mKBd/mfuYxu/7ZrS
pfH8hyldL1JqehwTk/nTKK6ih0wDKDnIBxgc8nt+lYDXWhR6tHp73WkprWA39mtOguMMMg7M55B4
rWubs2FtdXqKjzxxsscbDPmsQSIfbdtPPUbRX58/Amy0Xx1peqePNd1V49V1FbrWNV1tZWS4+3eb
KPLZidqRwiOOJUAH3TnkmsatXkaKS0ufdXj+4ntfgT+0tfWr4eLwHqcYx2LNFGR+TEfjX70/Ar9j
T4rad+zp8D59Ph07UYx4L0JhCtwsUsR/syAqcHgn2r+e7xDe3mr/ALK37QGs6jNsu9R+H9zvu2Gw
k/abcbtvbt+df2/fs/mW2+AfwGt2nN48fg3Qg00ihVIGl25HTr1rxMzd5Jm1Gr7HU/ke1X4MeGE/
4KnePG+KnhVbTxhceBLS98Oa4krWs/2mzvEW8aMxkCQ4kjLA7vXFc54f+D2lf8FA/j/8cJvHvin4
m6/8MPghr8fgvQ/hj4MvbjTdK1K7jtknu7i4aBg1zLvlQfMAoCYzxX9EH7c3/BMTwF+2Zrfhvxiv
xH8e/BT4j+DZpbrSfiH8MZIoNX09pUMcyIXBV4pEZldXBGdhGCK4v4MfCr9mL/gl34H8O/CD4dWH
jb4w/FfUWlv20uxiXVfE2rXc7s11qd4VyIlkfkyuu1e3AAry5TUI3bsd0a0ajUUuZn53/Cj/AIJ7
/Bn4O+JF134d/s621h4wizEmv61aSXuqLk8hZ5tzD6hhj8K+Z/8AgoC+h+IoU+C1z4J1zWfihoMs
Wpx+LtGuFhj8AyA/u7171SWjuGOCtsCC+AGIXNfsr8Rvjv8AHH4r6ZLp19faN+zd4QuFIu9N8ITw
694tuIyPmhF26i204EZVnSNpMHjB5r83Pjr+05+zB8D/AAkvgjVpNBbRLNjKPDEV8moaldTv96a7
lclp5XP8TZPoBivBxmdc37rCR9pUfbb79j3sHllmp4p+zhvvr8upwv7IP/BW3xr+zbP4X+Bn7Zuj
3V14WtZfsOnftN6QC2l35c/J9uhxmwlOcEsfLLdXANfuN4o/bz/ZP8I+AW+IuvfF3w1Z6HGm+O3s
pRNeXAxnMSq3zZ9Qcc1/LjbeHfjB+1bPqEHwk+A6/CX4UauDCvjX4xLcG3uEPeG1YI06H/Z6A8k8
mvKPHv8AwTs1n4daf4amtv2hPDGr+JvB94bnTfhYfC8N34VeQ8lWtjKZXBI7zfgK86hjaOEajjKq
jPrGN5flovQ9b2daun9Wg3HvLT8Hq/wP1Z1X4j/tF/8ABYrxtL8Ofh7a+Jvgb+xjocjyaj41vN6X
+uwrLjy4VAUy7jwD/q1PIZsVxX7V/wCwP8Kvhe1j8P8A9kT4ieLNP+Jmnacb/WPAV1JEfCen2iOu
7U9W1Kd4xpgbax2qskkmw4TjNeDfDr9qr/goj8EofBHwz1D4d+FdE1r426imiaR8QPD1650vSZZI
iTcf2fcoTGkaKz+WJipbAIwaT4lfErwv8fvibpn7G/8Ab3/CK/AzQ/EBk8X6zqt80fiH4yeLLeFJ
bq1muQVaK0tY5Y3a3UkSeYFG0Ic+vGpDM6bk1ekui19bnlSh9UnGFK/tZdXpa5v/AAO8Rfts/Ea/
stJ/Zc0PwX+0v8PfC88NhceMrizfwx4bd1IWZdO1C9Yz3UCPuVZhbhHYHaSK/SK58LftRaBb3X/C
e/smeOrMRbWlvvhtrOmeKERtuT+7WZJeRnGIyfav1L+BHhj4deB/hn4X8MeAbvSjoWnWmPL05Io0
GIwP9Wowu3GFVemATkkmvjz4jeL/ABv8evE2qeG/2b/2lrb9nf4vaIZI0+Gvx28NXDS6qUbCXUAk
uYpZIiPl3Qj+IcivGnlGExErxhZPazf/AAT154+tgrRdW781e/orLQ+UNJ+JXhLVb5tEudQvvC3i
CyYRS+FvHlpcaRqsLH+ForhE69ipIPrXojMCNoViQA2/tg9D+Nfnf+09+29/wUS/Zzt/Hfwh/a3+
A/wG+JniGbT5V0DUW0y4a18QfIcTWcjFvPYEgtEJvMQjBJr8z/2b/wDgon8bfAfxG8KfDb4lzp8R
tI8ZzmI+HtV/0LUNNYKXZrd1HKL90xMDjA54ryq3C8+Wc6Ek+XdPf5HVS4mhTlCFaPxbNLT5n9Hp
UjqCPrSV578PviPoHxFsHvtImdZ4W2NYXDhpYh6H/wDVXoXXOCDjjg18yn3PqVJS2YUUUUxhU6yR
KFMhESRKzySsw2EDJ+b049fSokVpG2ICzccD3PFeO+Porv4j+MvCH7PWiajHpFx8QEmudf1yNS81
ho0HNyFwR5by7TEJD03ZHStaGHlipqETDE4hYWLnI4O4/a9+DNhrUtr9u8ZDw2LsWE3xRg8P3Evh
i1umO1YJb4fINx+UYyM8da97t/A/w1mu7vVH+HfgW7v9bjUya1punRQzXCkZDl1QMQQc5IHWvjD9
uvXtO1f4a337PfhPTLTwp4FutLkih0Tw6hhiiSJN0Xy43GTeFbzSdxOa9O/Yu+I1z8Vf2Wvgz4tv
JvM1O2086RqLu5LNPZSNbMxPX/lmuc9zV1aUIw9rSbVnZ+fb8n+Bx0Ks6tT2dZK9r/18mj2ub4Xe
D47oXvhi41/wdPHwV06QPD/3wSMitvQLPxXpb3AuvElvdxQn9zfWatDcS/7w/wDr1tjIABxn1ByK
XkrvXDAehyK43ZvmfU9GNNQ2R598WvHHh3wz4ae+8c+Grjxw19/o9n4c07Sxf6nqMzceXHjGAT1c
vgdTXyr8HPhJ4e+At/45/aH8Z+Hrbwp448UpnSPhmL5tUtfCcLfwI8n/AC8Sj5n8sFV6bq/QNp71
tMvbm6mt7DQ9EjM9zdzCM/YkxkvlhlQa+NV0U/tB+LTrd091bfDrws5hsrQoyy37A8zE5wyntXZS
x1VUnGLaUt/+B2PPrYWnUqqVSKutj5e8bWnibxJpt78TNX8+OPVrspDBck7AhOd2Twa+EvGvxj8B
fAj9rT9mT4q/E/WR4X8HSwalpk2tXFvLPDBI8YKbxGCQCe+OK/ar9pTRo4vhja2+kWVtbWGiXCq1
vAufkA+8a+D/ABB+zle+MNH8F/EvU/Den+I4vD13/aVlDJCZhCy8bWTowOOhHNdOTY+OX1o1ZLRX
/KyOTNcv+uU3Sjo3b80z2T9lfxd8LPil8aviR8R/BPxV8A+JtL0/QHtraLSdYhlnuHmmyQIiQ4wO
2K+5rjekqgxuRIR29utfnTffCT9iL4yReR8TfgL4O8G+MhICPE/gyN9A1CGXqJ47izMMisDyBuIB
6g16h4V/Z0+IHhGK4h/Z/wD2y/Ht7o0KhovC/wAatPs/G0MZHpdfuboKOmDIxr9Nyvj7CQjy1YuH
nuvwPhsbwfiG+anJS8k7P8T7Sjlzlf4FH3+1Y3iXxBpPhvRdQ17W7trTR9LiM09zGvmkKOwQcsTX
zXqN/wDtx+CtP+1z/Dn4E/HcQZDDwTqt34V1GYY6rHd+chb/AGd2K8MT9q5fjJ4Q+LHw08XfCbx7
8Bfi94PtIZrrwB8RVjaW5tJLlIxdQyqiLNHnjcuetfZYLiLCZlf6vVUnb5/dY+YxeUYjBNe2p2TP
sLT4v2uPF+kxeKfhh+ytFbeC7xTNba38WvFtl4budQiHIlW22yyKjD7pcLnI7VzPwG+PGn/HCx8a
Wf8AwjmqeC/G3w81aTRfEPgfV5IrifT7pc9JovlnRxyrgcivtb9r3xLqnhr4UeErPTbiWz87SNNt
x9mY5VRbIT06Zr8Zf2IbCztv2j/2xP7Oilha6k0yeb7RMzebO6EtIATyxHFddOcrxi3uYOMeV2Wx
+nSxuF8oqwG9fmIwDzX4dfGeQt8TPGkrZDG/lGD1+8a/cyKKYfvWZ3jLAorDnHXFfhX8X5/O+JXj
OZhs3ahLwf8AeNdOMjytIxg7o4XT1DkMxKsT0NdtaqVt1GD+NcXY/NIjDkN0I712VpJIyFHUgDoT
3rhTNE+ZXOr0792Lcrzzzt+tdfGcshxnODiuP04FUQtwCcZNdNAZTJENjHII54BJ7U3qN62PkvTr
+60P4g/tNeI1urOFLG6gcwS8keXZIx57dRU3w00PxbZ+B9Jv7FPDmoJ4gzqc1lqIOyeSd/MLucHB
6YNeR+JNSufEHxV+Pfwu0uzvptU8e65ZR3F3aqxi06yW0iM0hIH8WNgJ719raZpNnpGn6XoliG+y
aTbxwxnsUVcAN7jrX45xBXlhsTUV780vwSR+g5PH21KDXRfjc8k1S68ba7N4cstZ8Myad/ZWr218
2paTILiNlQn5Ng59K/uH/wCCdGpWuq/AvQLy3+0DK42ToY2GQGJwfev4+NA2LqdvkhmjkUhCMk81
/Yv/AME8l2/AnQcFVDxg7NuD0Fa8MS58QlZK19ic/TVK7fU++aKKK/Rz40+b9W3rdySsvyxo+Wzn
aT6+n41/Oh/wW108Q/FP9lS8W2mlN74U8X2xk2EKC0+jsBk8chWP4V+t3xo/a3sfB/7SnhP9lnwB
8PdY+JHxq8YaDL4kZFvI9K0bRtMWdYjdXl0ylh8zLiNPmbPsa/Bj/guh8Std+GPxG/Y78W/FXXPh
zN4J12DxDoE0vhaGWKPRb+dLGSN5rqSRt4ZIXAYqo+UetflfCmTYpY+njZQ/d3eu3Rr5n1WbY6n7
GVJO8tD8PvB0YXTXWPLJ9ouEU+p3k4rsi6uS6nKtyD0rntEWK2tn/s+/t9UtLqQ3Fvebl2GN+Vfc
OCCDwe+a39rJtUrIODy646V+0x0SPjKyvqtyg20s5wuFJyT2wM8+n9a+FPi74s8RfE/4wx/CL4Oa
tpVlrVhpNxa614zvH/caUshjwiJgrLK21lJB+XufX6M+Nnj/AFPwT4Wt7XwzHBeePfGNxFpmi6fM
Mhrid9vmMv8AEsS/vCemBz0rz3wl8ONA+FHjPw1oukShrqXSZ7nVPEV+BJdXtyXDTXEjenPC9qNy
qKdtTzr9n/4UfHD4d3+laLrbXcOjaHeCTU/FdzqUl6L+FSUjjgh27IV2gBhkcnoTX1sP9I+I1zPd
eU1xHowKPjDBWuBtzj12n8q8v+GXxV8ceL9Wkn8QeELGw8B69cSLoPi+wuHJvYI5TCySRHjJdGfd
/tV6Vp7Z+Iuvwy58230i3TI5HM7sOfoKUFyqxpPZnTa1EZ9LkhXkyGFMe/nrxX6KLgBR6BVH4JzX
53a23k6bE5+813bRgj1M6cV+jE4RZyq9DyP8/gaqnpL5GC5XFDKKKK6ig+ZsxhUZZQQwkBIxjt/t
en48186J+zP8NY/E914ym0u0WW5lN9NDbvMIrl+G81oVIVyMgngjOa971fVRomkazqpieYWFnNM0
SH5pFRdxjHoWwPm6jHvXwn8KbO78ea1qfxS1/wAXavD4qTRxqUmox3TR2aLNudIIIf8AVCBEKICQ
WbaxJrkxLV0uoWPsj4u3Nnov7MX7Vk6IqR2PgSZYZ25RWbUrKPJC5AUbuxI45xX7rfBT/gtH+zF4
A+Fvwy8PfE7xv4Wni0Pw9plpLdaU5kIMdjCpHKAcYx17V+AHxhvptS/ZD+OsOsrG8/i/w3p2mPFH
8iySXWsWSZKdCCC3A9Pav0n8Ffsa/steHdD8KSRfAH4V/arDSrNZb06TDNLK/wBlj3MWYZBLZY/W
vLzKcFNKd/kdeFpSqJ2Pr74+f8HBP7GOmfD3xJb/AAH8Zaz4v+K2sWj2ejWdpZf6NHcSkJG7MAxZ
kLbliVSXYDjGSPzls/2r/wBq/VPAUEXwu/ZZ8UaHf+Jd174i+K3xi1e10G78SXkuWN5Oly3nLCM4
RFQ/IFGMYFecf8FENN8J+BPhB8M08J+GfDHheyg8X6bIsGkWkVuY5AzeW3GBkNjoPrXnnjPx9408
beEpbjXfEN1cT22nKiCN2ZV45YIpxmvieJMeockIUlK/81/yTSfoz6vh7Lefnl7Rxt0Wn4tM9V0P
9m39pj9oUJrfxt/ali0zwfcy4ufAPwSaZo7g/wDPJrlhCFUAYyifQ19GeHfg9+yf+zodMn8MfD3R
tV8c2ZKR6zeRPrOvSyd5GuJvMYAnopYAYr5p+Fn7RF54L8BQeEbi3isNDWFZpvFEfMsSj73HcnP6
19zfCLwr4k1zwxY/EjRP2fvij4i0HXPns/F91bpJPer/AM9Y7YgSbD2Jr4yVbHZmnTgnyR+zFcsf
ujZfefUUqeCy9KcmuZ9Zav8AEoyWPxY+KEyTXl/ffD/wnIQqwLPm9ukx/EVx5YPXAPHSvSfCvwy8
IeEQkun6Raz35G6bVLzMlw7egzn+dVdQ+Lfh/Qbl9N8XeG/iX4LjiOGuPF3hu8s7WFh1BkK7QAe/
Siw+M3wk1WY2+nfEvwTdzDrEmoxK4/BiD+leVUwNWjdTg4/I9ehiqNXWE0/maPjr4deGviDZ6Lba
7FL5+hXyahaajEx861lRcB05HP418k/EP9gb4W/EfRdW0nxHJ9uiv719UWaNZLe6ivmx/psUkbBo
p8gEyqwOB1r7ttpI71d9nLDdxnpJbOJFb6EE1KIpSWXy3Ei8mNxtbHrg1nGtKnrGbXo7ajlhKVR3
lFO5+NOlfso/8FEvgtNdR/Bn9tfxPL4Ysw32PSPG2m2+uXFtH2hWaZt7YHTPOepr2XwP+2t8UPhp
ol58N/8Ago18PNW/ab+FaM08Pxn8NaUi6v4elVTulktY1FxbMmdwntWcLtJYAV+lyli4VVkLg8BR
3+p4rntb8KeGPEcF1B4g0Sw1gbiHklQfOSMFcdD6mvaocQ16btN83fTX71bX1OKrlFKpDkg2vK7a
+7ZfLU/OrxN+1z8P/ilbXHwS0/4xeHv2vvgNd2n9s+G/EetX3n+INHimOz7DeMwMkU8DAKJC29lC
55FcnbfsaxfEPRrfR9Y0HSbzw1c25Ww8Wi6D3tiVT5ZY5QfPLduSM/rX3j4f/Zm+APhLVPEOueFv
hV4K0HVvFRH2++0218mW7252lgCMHnPevYNO0jTdDtE0rR7SO302EAIgzx+dZ4zNp1p81GTivXX8
B4fKoQhyVUpfLS3zPxs+Hni/4rfsG+O9P8A/F+G68VfC3xXPHBZfEREDlUycRzjBZHGeOSp9c1+y
2larZ67plhrGkzpfaVqcK3NtcwJjdGwyOBz35z0rg/ix8K/CPxp8Ea34E8b2cl1p2rW7RrdIQJbZ
sfLLG3VWU8ivin9jD4h+KPBfi/xt+y78R7+S51HwHNJHpWuznZNdQAjY3PBDIVJUdDmta845vRlX
5VGrT1lbRSj/ADWWzT+L5M58PCWUVlSbvSn8N9XGXb0a2+4/SD09xmimrJvAyFVlGCo56HrmnZ69
9oycdh6mvET0ue8DPGqEysY4o1Yu47Ac5/DFeHeEPG9h4T8B/GT9oSOyWfU/iJfNpGkzAZnXTbI+
WJIzj5VeYSk9Mgd6j+N3iLVntvD/AMLPCd6bLxp8VXayS4Rd8um2PBuNQK9lVMoCcDc681c+K+k6
H4L+CUvhvS7YJofhnTY9NsI7o7SqIoAZs9XY5Yk9Sxropy+rRbV7z/I4MR/tU0v5fzPgf4qeM38b
eK5PEVv9ojjkijDsxG4sE5P4kYqX/gnr44Phf4j/AB1/Z21e4kthJfR+M/D7S/Kv2S5RVuYIx0ws
yMzHOP3leZo5Nk24lnGMgDml0/4F+MfHHinwZ8Xfh1qfiDw942+Fd3uh1vw6yMZLWQfvrSWNuJY3
xyD0PIrWg4RUoTektvJ9Pl3OerGpJxqQXvJ/ej9hbrxj4TsrqS01HxR4f027Rd5t9TvYYHx9HYZP
sOaoSfFb4bWfkrb67eeOdVU4j8O+AbJtQllb+684CxRj3Z+K+Ov+E5+N1/Mtrrnw+0/xDdR8Rzan
pi+ZGf8AfC8/jX0J8M9I+KMksGpeMrvTdG06VPMj0fS7WOHzT/ddlAJPtXE7QabVzuk5VdL2Rq61
pXjj4v6nph8Z6daeAfhto8nmwfC/TrtrqW8k7SXcyAeZ/uEsB2r1eG1tbCK3022S3tbO1T5LW02r
HGvp2OfwqPUL+00iwuNW1O6g07TbMbpdQvHWKGMDrlmOBXh938fE8T38uh/ATwB43/aL8QuQhi+G
kQbSLQ9P319saNDnqM5FdNPD1sfJQpQu+yJq4mlg481SaXmz26/0yx8Rabc6Tc2EOq6ZdH94gHmR
ufTcMjPtmsWf/hFPh1oH/Ex1fQ/CegWKn95qtxHawqvf/WEVgzfCL4vDTE8SftBftG/D34A6FDEZ
LrwF8MbG31PW4VK58ubUr4tGrY4JSHg5xXz5LefsD2WovrmjeCNa/ag120bYPE3xb8RS67BBJ/s2
ystsB3x5dfWYTgLFV1zVpqmvvf4Hy2J42w9N2oxc3935m5dftF/sz6pq39l+HdUg+I3iLcCumfDX
RrzxBcs2extYXjz7FhXu2j2Xxv1DS01Xwj+yv490vTLkbobn4j6jpPg9pz/z0EcsxmUfWOvIT+2V
4+0e2bSfhf4N+H/wq0sKIls/COjwRHYBweFHQf8A668O1z40/E3xZJ52veMtbui+cxRzNEhz/EFy
cfnX0uF8PsJBfvJufzt93U8Kvxri5/DFR/H9T6q8QeE/2o7qb/TdY/ZS+E1s6bnm13xdc61qMfsf
JswpI9Ax+tfP+t/s7aJrupahrPxa/bD+GOteI7uGKzj1Tw74Yu7t4IUmEvl72ZSy5AFeITajqV2z
td3M9w7Hma4cyMR+Jqu6GSUtmRolHO4L1r3sLwvgcDNVKdO0l1u7/meLic+xeNThVndPyR7l+0J+
0Tqes694f+GviTxV4R8XaXqhji0nxNoMM9sZzHGF8qWJ0+RgoB4JX3zXzT+wAZ7j4u/tiav5yFpN
dsrUIykE+XCcDkdK8p+J4DfEz4G+ciljqM58voTiE85FewfsILInxh/a4htiXsxqmnyAuekrQ8iv
o6SXNHyPJlHki2fpnGQY237pFjOREDycLya/BL4ny+b8Q/FE8MbAyX0xML9QN5r96ZQYzJIp/eqr
AjsPlr8DPHkgk8c+IrpW3PNdzYTHq5rsx3xI54mdZOmYm+6oPPtXZ2/RfwrhbPeY18xQr7uRnNd1
bn5FbsMCuBDjojp9N+SKMZMjGYEj8q69CNylsgZGdvWuQ084MK9Szg8eldfAyySIP4dwzmmNnw/4
R07466h8dv2i7z4X6P4Q8T6Xp2q2gvdI1u+eyumlNmm11ZY2G3bxjd17V6tdeOviR4ajkuPiD8C/
HuiGI/NqXhfytctDjuDG/mD/AL4z7V6l+x/BEfjD+1uIVEV23iGxHmocrt+wJ1Br7pubGMo4fbJg
5yhIBP06V8djcgw2OqTlOPvPr1Pq8FmVbDQilLRdD80fBv7Rnwf1vXLO0k8ZR+HdSlYAaX4wt5dL
mc56Dz1TP4V/br/wTqvbTUvgF4bvdPuYbyzlgXbc27B0bjsRwa/l/wBW+EHwu8W3VsPGXgjwzrsA
IVWv4FQj5s8lQCefev6ff+CfPgTwd4F+Deiaf4N0mLSNPZc/ZLZ5JIl4/h3scfhXJl2R08trc8JN
/IWOx0sZT5ZLY/QKiiivpDxD+Q3/AIKq23if4U/8FJPhx8YbOfUvDeiePvhq+iQeKYlkSznvrW/R
/sUkjfu97Rh2VMhiFzivn3xf4k8FfHjw7J4Q+Oej6P4k0u7XYsmvxC+spcABHPmZCkgth8jjABr+
qz4sfDH4ffF7QNb+HvxS8GaD468F+KontL7w/wCILdZ4ZonyCQfvIwJyGHIxkYODX8Pnxj8IfEf9
l39o79p34dfA611/44/Ab4L65ZaPD4F8W3w/4S3SPtVgl55enysClzapvKrFNhwMDcQK+G4Yz1Ym
LwiVnTvbs1ff8T6TMMD7J+172PGviz/wT3+JHwdh1Xx3+yJ4gn8SeEppmnPwP1i6ebT/ACSSW+xS
sC1u4AG2MkL1HAOa+bfDvxysI9fi8DfErwz4i+EHj6yOZPCvjyMWZlDfdMUjN5c2e2xiT6V+m3wM
/ah8LeO4rqPwFrF1DreljGp/DjxNF9l1TTXBHmLPblicA8bgcHtxVP8AbcuvgX4x/Z0+IXiH4h+B
LTVPFdhbRWuj20UaF5NQuZ1htjAfvo4ZhnD4A7V9tSxnJueLVwyk7o/LLRVg+JX7RGra9bSrdeGf
gnZSaXYzqQ8Z1O4i33BUj+JEcIScbcsO1ct8e/EfiHw7408Jv4Z0ux1fxV4ntZ9GsNMnkPJLL5tx
IADtiQK2X55IHevZrj9h79p79iTwBp+q6RJpfxv8CGBL/VtI0hHj8RWVzKoku3RjlbqMOzL8zBto
9a+cP2dvHWg/Gfx54++L99cWlvPfCPQdE0S7f97plinzyF158uSWRV564B9a9GjXVaN0csqTpNpm
z8Gv2fPiR4C1DSodc+LkXiXwjp05vP7Et4S7l5AGe3DOOI1fO0DHWvovRnZvH3jFNys0NjaJ5gOR
nLnH61039gpEwvtOup7KSRiBZqcrkdTz1HvWboWhXFl4h8Qa7dSwzHWhBEsMGcrszljn1zxW+xg6
ikmmybxU8kWj2jeYo3apYEc9d11EK/SqZNt5crGrMrsWB7gAn+tfml45WGHS9EQq7bdd02JsfxZu
4xxX6X3DFLm44ZYnJCkdfvsf6U6XxfIza91WIt67tmfm/u96dTMYccLz/F3p/QFjwi8s3XA9a6iy
pfQpdWk9pIGZbhSNhwEJwR83fHJ4HWvkvwt+yVpnh7xemqnxt4tPgy1uDNaeA47tms7cZ/1WTy0Y
6iNiQK+vSjv83lyqqgtl1wSPpTySAoKsMKGPGSuemR1rOdNT3FzWZ5F8e7ZW+EUlpaiGGG88W+F7
VLKUn94r61CWjz36E7ewFfumFSDNu0YRSmwFCNq4GMfgOK/GCTwPf/tFeOvhV+zB8OdZt4vil8Q/
FemaslyqG5TRdO0uVrq61GZRwqA+XCCTy0ygetfpr8TI/jv+yj4p/wCEa/aP+H9nrHhTWrpYNM+N
Pw8uTc6LM00wWFJ0k2yW8zb1LLgrluCRXg5mnOopLax6eAmo7nw5/wAFXrSG5/Z6guEVw2g6vp+p
K6Lk5iuo8/oWr5x0jULRvhdaaxezLDHNp6u9ycjqvCjHJLHgAAnJr6m/b3n0/wCKHwS1jQ/D2sae
EuLB5hcaiTGixq8chHGSWKqcD1r6A/4J0/snQ+H/AAB8NP2h/wBoPQpJpIYVu/AXwj1ZOZFUYGt6
hEwxtOxHgiyRj5m5YBflcdk884q0ow011fke/gs2hlcakpddl3Om/Y4/Ynk8H+H/AAp8bP2mvB2m
fa9QjS48K/AvXIxO8UjAtHf6mj9HQYdIOdjEFgCCB+gGqapf6jey6hcyCa9wETy2McUSjjagXhQB
wMUalrdzq2p3Gp6hPJcX967ztO7l1ZnOSFU/dHPQdKzAy5ACbMjOz0r9DyvL4ZRSVOmrfL8z4vMM
dPH1XUnr+XyOhsfFniexUfZPEWtW0SDBt0uHEUg7KQDyPrXPeJ9O8F+M9h8d/Db4Z+OpD0k8X+Hd
Pv3/AO+3j3frS4Owr3p8kRfZggbfWu9r2qd9TlU3FproeM6t+y9+zBqiyvZ/BxfAGoytvGsfCHW9
R8MyQnr8q2sqqfoRj1rnk/ZjstOnEng/9pz9pDw5Eelh4rls/E1sg/u/6UGbFfRp6GoMbuCSM9xx
XmYvJsJinedJO/kdlDM8Rh2uSo18z59m+Fn7Q9gskfhb40/BTx2kHMdv4/02/wDD93IeymS1Vo1+
oXHtVeMftSaOY7bU/wBmWfx2DjN38F/EWnaoh9ZFhuJLeY5GexNfRrgAmB5XZt6qqHkPn9T1rwf4
r/tVXPwM1oeC/h9YeH9U8b3mnvJret3krF9GSRSsFuipgmZiQxBYBVHPJArwcbwRl9aDcY8r8j3s
Nxhjabs583qZng34h2fi3W/E/hufwn8Q/AHivw15TX/gz4o6XJpOowK4O2RFfKzRkgjfGzLnvXoH
vXy7onxL8QfEn9sPWk1jU9Wu5fBvwm0F7xJHDQPcXl9eMMqDwwWJc5zyTzX1BvHzcrsAzuJ5/Kvx
7PcDDK8VOhTd4r/gH6ZkmOnmOGhWmtWSKVU7pNjRH5WRz1z3r8p/2lYrjwH+2b8IvHkCqv8AbUMU
TyxkKJZBJ5ZB9Rsbr7V+qzQC42qjeZkZ+U4x7/hX5M/tT6wPG37Xnwd8B2n7xfDGyaUFdxGAXP6l
R9arJIN1Kr6OEr/NGeeNunBLfnjb5P8A4c/WKLa6CdVVRP8ANgEHsKeAVk80HLDBUHoCDnn1HtVe
zBS2giZeY0A3hcA8Y/p+tSmQAuAGYoM4HcnoPxrxo/CrnuPexz+meD/DGi+Itd8Y6fpUEXiXxKix
X2s3TeZM8YO4Rgt92IMAwRcDPWvkX9oXx+PGOs2Pww8N7r5jMpmmifzDPKTklvYGvq7x7Ldr4avb
C28SaN4Ul1IKBqutMsa7MZLISRnrXBfDL4R+EvCkcfiJNRtvF+qagS8XidCksLMeu0qTjFKNTmd7
3sYyirWR5rP+yvpV94U0yAX/APZ/icASSX0WdjAj7h/H2qf4O/CL4ifDTxJPcPqOnTaBe/JOltKx
YjJ527a+rZLqO0zLdsIEjjLZuSEVu5wTwcDk187WHxv1f4r+Prz4VfsyeBL/AOMnj3TmMd/4oRzZ
+EfD2BkteXnIJA5KIGaurC4WvmE1TpRu2Y4rEUsDHnqStY9613xDoPhTTbrVvE2u6Z4b0WxQySav
rsotYkA7kvjFeS+GPGnxl+OzSr+zf8Mbi68FM5juf2iviwo0vwnDj70lurf6RfY/2Yyp/vYrHvvh
58I/hL4itvG/7T/jS4/al+MGmuZrL4f6bALLwPocp+6Y7YsWu3Q/KJZyemQg7eb/ABd/al8e+PIb
qG51aPwh4Qtoz5ehaa62dtDGvU/LhQAP4Riv0nKOA40rSxkrv+VbfNnwWZ8ZTqNxwysu/U7fxH8O
v2evh7eNq/xz8da9+1z8SLWTcnhi+mktPBOnSA/8s9PjZYmA/wCmisa8a+JX7aPxl8TeJPAf7PH7
PUGn+AL/AOIuow6VpfhT4dWcVjbadE5CyXJWFQCEUlssOwr4A179rLwSdbk8L/DfTPEXxd8Yo+1r
Hwb+/hhPTdLO3ypg9euK+tP+Cd/w5+K3iT45+Nfjx4j1D4f/AA81LwBpRSDVD5uvXumPcsR8oASL
zwmdoJwD1zX2kKuFwCWGoJJ9lufJVVWxSdaq3p1Z9BfE8/skfBr4ofEG6vfCl98Y9B/ZC8PrN438
QeNbm61KHWfEUpVVMsVw5jlVWYvkLsXvivyh+N37UnxA+Lvxt1X43/sy/sbeKH8A6PpMXh3Xbv4G
aZaX+i6hct+/iu/I03crMinY7hCV6Zr9+tVg+HNp4f1jwZ4P8JNJp3iC+e/1zxP4xYX2seJ7x/vz
3mAFCt2jHyqOBxXzB45/aJ+CnwKntfDcurW1v4ouPks/h18OrePUdVuD2SO3jyF5wBkrj1xxXd7K
yT5rHGpc+lrn4Fa78evG3iSe80vx/wDEnxH8NvENoVWT4YeC9FvrTxCWb7sIS4hWfew4zGpHvX2/
+zJpXjrTvAV1eeMvE3iXXrXW7tp9NsfGiSJq+nQdPs84lO8MD2NfZ3gj4Z+MvHH7QN5+1b428B2v
w40m18KSaRb+FfGDxal4ju+S4uLgIoS1Kjoqszc8mvir9lt3vPA/i7XDM0lrr/irVbi2hlkaV4o/
tJGNxPI47g/WvJwcZ1MRNuo5Jfcd9dx9nFKCR9J0m45wDxjJpaUJubqMnjn3r3GcJ4F4/f7X8b/g
vborPFAl3Nt9DsxmvYf+Ceri78T/ALV2pBg9w3i1LZpB1+S3+UfnXi/iEJL+0T8PoG3NNY6LdShV
PP8ArQM161/wThu9Piv/ANqe3N/E17N45ZzA7L5ijyRg4zVUv4ivsOq/cP031AuqXZXlgjH5e2F5
z+VfgFrFwLnVdRvSfMMtxIeOW+8a/fm9ZotP1u4WSNgYpMy54XCEn8q/nqtLlLtEuliuohMWfFwu
AcscHrXTjanM0zjg7xkzatuW285LZ5rtLcYtw2QQT2rjLAGSY5eP5efMB+Qn+6D6+1Q+KfiT4F+H
OnC98c+KNI8PQ5+S3vZVNzMf7kcS5d2/2QK4nKzNKMOeJ69YMFjg3fLJvA+chO/q2BXXWscyOF8l
2YclMgP+Ckhm/wCAg14B8OfGfxf+MZSP4F/ADxzr+mT5VPG/xFceHdCc56ruWSZ+x4QV75Y/sNfH
Pxpafavjt8eJNA8PSAu/w1+Bdn/ZqMP7sl/Pvnf3wq59qh4iKOiNCUzzr9jfzW+L37XGpzaxDDby
+JLWKFYisglkSxjDIMcEjPTPY96+2pbr4h3C3f8AZnh7T7uzgYlbqceTL9QCMZ/Guq+AXwA8D/Cb
wufDXw/8Jf2bpnnPIwDtJcXErMSXmlcM0rEnOTj0r6JX4ceJL+KKP7KULvxkYX8QK83dt9z1Kb5F
Znxzo15bPqdp/wAJemv2l0ZQBHdqfIzn1UkYr+q79iaSyf4PeHRYywPCI+BEfbvX4iaZ8EtYlubc
381ituzAGOVNwHPpjmv3w/Zb8Nx+G/hppFmkkMgUY/dxBO3bms3Saa1JqV1Zo+mKKKK0OQ+cNXE0
d1eNCqgupBl/i4cHg9q/jy/4KIeJZvhb+0z/AMFFPFWjWFncalot74b1yOyuJWhBkbQlj3AoRzhD
1z0r+tfxN47tIdRutN06y1TWNRwf3FjH+7yT/eJr+TP/AIKc2F9qvx2/4KEWV/oc+nX+qaB4VuHt
rh13caZfqOcdwoP4V+T8H4SqsVVqSg1Gz1aa6o+vzTEwlTjCMk3fb5Hx74y+Cfw4+Klrp/jeXTm8
GfELULCO6i+KHgKT+y9egdow64uY8NOhLcxSbkI6rXwn4x8Q/Ey3+Pvhv4d/Ga98QfGL4K/s5yJ4
o1bxn4L0xrrUWurmErYJqVvAQz+XskkIRccqxXgV9veKfi3a/Cn9nDw98RHt5tW1iHQNOh0vRIVB
e+1G4tore0tV55Z5XVjgHCAnk8Vb/Zs+Emv/AAz+H8s/jXVrTWviV421GbX/ABBrFmcP9tlREaKN
sBtiRosaAsQBuOOcV+jo8Fok+L/7VUmnfsqfEHxb8LfHNl4rsPFNidC0qXSbjzFe+vWFrEgBA8uY
O+PmCMCnIzXR6v8AsC/sv/E/4eeFtN8DWsvwZ+MXhnSLazj8d+BpF028vZEiAY3G393dgtlirqR1
xg818M/tO/ArwtqHxw/Z7g+GN3/wr74kfETXTqN20atPod2dOhe4S5urHKpJIskajeCMk5Iz1+lt
E/aK1/wV4htfCH7RHhrT/hxr2ov5dh8TvDUpufCmpSD+AyMEktJT/cZCp6b61p1nBWHKPO7s+TPi
H4G/ab/ZNub2z+Ofhu+8TfDaGXZZ/GvwvbPf6bcQdjdwrue0dR1cJt4zmup8F/EXwd4ysbTUdA1z
TdTtbleJ7SZJIg/UAuCVBPoTu9q/Y3wr8YNQOnRaZriaX4w8PXUIaRbkJckRsOm4ghkI6JyBnnNf
JHxU/wCCb3wT+Kup6p8S/wBnjxhqvwJ+KGolpptI0+NLjw/euedstku0df4kYEdq9GjirPucdXCK
Z8yweEpvGmqeGdIkZEgi1ay1GZkYnckc3mben+yBn3r79k3MzSKsitISriXG3AZiNuCfpX55aR+z
h/wUV+GHjnTNCt/B3wW+ImlW6tnxxFq15pUZRmwNyNDJtIHVcnrX3n4b/ZH/AGlPHEbR/Ef4n+Hv
BFiY9j6L8NbJ45QCOq3Vxncf9oRZ7gjrXT9ajF6as5Xh9lfQqeK/GXg7wPp/9q+MPFOgeF7IKW87
xDfW1mPp+8cEn0UZJ7A14hZ/tNeGvGM11Y/B/wAC/FP4yXaHZDf+DtBuk0iV/wC6b2cRwj67j69q
+3fhn/wTW/Z88C31x4j1rSr/AOIXii6O6TXfiJdPrtyvOf3fnfLF/wABWvtvRPB3hbwyoXT9Ptfl
2iNmiileEDgIMg8dOMUSxU7bWNVRXVn5D+HPhv8Atu/EuSS4Hw98A/A7TWAC3Hie5Gu6qg7nCYhG
R0GW6dK+rPAv7GV8PIuviR8Q/FHiu6ddzxLe/Y7XJ+8BHbhBj2Oa+1tf8XeHvCkM93r2taZowhUH
zb2VEgQck5BKovA6gZr4e+I3/BSX9nfwXa6nH4PuvFfxh1PS45Liay+FunPqyxBVLNlhtUYAyfbP
pXPOq57vU0VKyvY+zfg38PvCvwKu9U1P4X6FY+Ftd1GH7PdeJrK3VrueLcG2NMVLkZUHBOM9a8T/
AG6NQ8V/EH4S+HPh9P428Z6RH8RvFmn2M2uaLf8A+l2sXn+a80RZnMbR7Ny7kxk8DArzHwf8Tv2v
Pj34e0fxd4B8IfDP4K+BvElr9rsfEfxKu5dX1p4WAKv/AGfbKkatgjhrj8DWjYfs861f+JvC/jr4
pfGLx78RdZ8NNJNHpJhh0rQWnZSvmLaqHk+UHjMxrHn6FQhzM+K/hBoPxH+Gnx+0X4eftDeN9A+M
Xw+0XR9R8XaXJdwC11TVRp5hVLfUFjwk2x54mOVG4pyOcV7Pe/8ABUf41HxFqs01/wCAtdgtn2Q6
ZqukzQW9rboxVLdTEyqqqgVAAMcVlfHyCLRP2nvg9fG6EdxrngnxTpslvKAVaJvscmexyTGPWvzd
ntvHa6ro0nhe68PWnh1L+V9Umvy3nsvnH92q7SDx3JHXpXXgl7NXjpqYV6anKzV0ftF4E/4KiaJf
zrZ+OPAD2SyfOdW8LX8VyIcnONkmxsDPQFsV9Oab+3p+zdqMlobnxZrmkJNw13q+kXZiHHUvCki/
mRX8/d1Z2l629tPtJl3s3mXCqzkZPAyDt/Csg+GdP892jmv7J2UYNhOYQpHqF4b6kV3OtNO9rnLL
Dp7H9Q3hX9oL4JeN1tz4V+KvgHVpLpiqWyapBHcZHrE7CUfQpmvZoJ7e6SOa1mS4hk/jgPmD/vpc
r/49X8jhstZWKQwanFehvl8vWLSGZsdOHI3L+BrpvD3xF+LnhDZH4b8T3ttFHznSb+4hH02sWT/x
2tKWJcd4kfVk9mf1gnGUVvMUSdCY3H8xVXd97cY1KHBSbcuR69K/nC0X9u/9pnw9GsR8U6gUtkzv
1TTrfUw2eMH/AFRx9CDX0f4B/wCCo+uQ2Wpf8LWsPDd9Fo8BnfVNAt5bKRIwPnd42dgNvXhjXR9Z
g94kfVpI/Sv4/fHnS/hPoP8AZ+h3MF38V/Ftq0fh/SColktScr/aEyj/AFaRH5stxuUAZzX5ixRR
Ryzz3kj6vcXFxvu9avmM1xf3LnL3ErnlpCc89PmPtTbrVJ/GXiXxB8Sda1nT9e17xo6tb6hpassE
GnKm+2tI85+QId5PG53bgcYtxS7poyyICxAwgwuc9cVw1pupdpW7HZSpKC82canjHxb4Q/am/aD1
jQNTutOe10jwppbfNlZAmlm4Kkem64Jx719YeGv2rNcsRAvi7RbXUIhgNeWMX7w/UV8S6rcrf/tC
/tNzhizRaxokLei7fDVidv4EkV0mJ5h5SMjMBkI/GQOuPfGeK/CeJrTx1Zy6P9EfrGQp0sHSUdrf
qfpppH7R/wAJ7yze/udck0h4UMklvqURVUQD5tp7n2r89f2ZNOn+Of7TPxP+Lkswu9BtLqSG0ubl
snCSZCxn8F/Kvl34w+MbmHT7HwNoJtZ/EviaUW6RAn92WPDHuNo5bjj3rW+B9xrnws1y78NaLqtz
Y3liu5ntnPlXLk5eUDjhmJIHpWkMM8vwUpXtKrsv7q6/N/gvMzqYuONxMU17tPf/ABPp6Jfi/I/o
Gwo2CJjMQig7OAvHTnHpUFzK8EM0+GjMEbNkMA2MZI984xX506f+1H8SdLhSzu4tE1cJws17Edy+
3B5rTk/a98T2FvcX/iLw/pMujafG8rxWce1zhexJ5+lfMckprRH0jqqSvc+pNJ8O/BeD9nvSP2hf
i/8ACrQ/jZ8QfGuqXtvYWPxLV9U0nSreCcwxQ2ts58qDATJYLubPJ6V+fOkftifDv4bfG/4q+EvC
nhabwho15ptjPa/CnwdbMbB9VmkMeyxtkDEPIduUH3j1Ir7MXxJH4n/YB+AOuWCyWdr4j1PU7sWz
Yyoa9k9+Olflr+yR498LfD3/AIKE/Hj4nal4I0jxT428FeHbKDQNT1dWdNNlkZsyhM7Wfngkcdq/
dcTkdLMMFDDtWuovQ/G8Pm1XBYmda/NZs/UvwX+zX8T/AIgwXHxS/wCChfi7VPhF8K4wG0j9mjwv
q5sdT1cdVk1aW1ffGn/TsrjOcN3FafjL9pbTPDfh5PhH+zb4a0D4N/CuxBCaV4F09NOjufWQsoDF
jyS5O5upJr58+IvxO8afFPW5td8YaxLfTuSUtU+W3jBOeFH864Hcx/1kksrHjfIcn+VexgMuoZZD
2dCCivx+88/F42rj5c9STf8AXYp6nqF7OLvU7u4mnvY0eQzSSM5kbPVsnmvx38S/F+18WfGX4saZ
8ZG1jxP4K+HGlQ3Nj4KNxLBpNxK6szebDGQsoOMYNfr5qA/0DUB/0wc1+APxEf7N8Wv2j1kZnePR
LUxjPH3GBz69a5s9m44eSTavb80bZYk6i0T/AOGbP6VP2Ov2GvCniz4T+B/jT8aviT4d+HPw28aW
UWoab8Bv2cIorTUZoH5Rb24Vd8WR1VWB561wPhTx58YNH8S/Gn4ffs1fsg+J7C2t/FEsMeqfEKd9
F8Jw2iRhbe6kuLh/NvHYZYhAee/NfXX7NSy6F+zV8FxOHZLPw5ZMElIbGYF6YA456HNe8GSSS1Ms
mJYpE4e8/ebcDIIzypHsfwrxcPSjgpOVONm+vU9CtKWKtzyv5dPuPkDw1+zb8QvFrQap+0H8fPGn
i27uFzc/Dn4ZXB8MeFoWP/LLbbbLm4A6bnkIbuK968A/B34T/CkXTfDX4d+E/Bk925eXUNGso1vp
26FpbhgZXJ9S+a7uwu41traGB7lwykyPCFeSQk9CWGSPoRUkQllnvX24jt32tIWGwcZ+pPtitasn
Vd5N/eOlSjS6HM+ONSS28FePrpGeE6ZpV473W8sXItnOMdAP19TX44/sq2ttZ/A7wgYgJH1Pz7t7
kg5dpJ2Y1+vfjOxd/h38ToiwcXOl353n7rBrV8Ba/JX9mgsvwO8ARqFEdvbOmB14lbmvQyxWk0jk
zDZHu1IWUfKW2FujelAOce9RShN+Dy+CFPp717V7nkyZ4PceXd/tK6Q7NgWnhx2xKpAG6YA5PvXT
/sQf8Ezbr9rLwJ+0f8bPAvxF+J/wg+KNp46urK18afDjWSlpKka/LHdWMhaKaLOM/u92O9Ycf2j/
AIaIuJ7xM2MXhxBHKFwNwlyQTX63f8ETPixpfhb9mL4gWGg6Zc+KfEHivx1qt6QkQhsrYCUqpdzy
Txnis6kebTY3i7o/NfxL8K/+Cr37Nx1nRfFvwvsf2mfBUKNDH43+EeowWuoiLaVaS4sLp0AYj+51
7V8LR/Dz9qfxOJdP+FX7Lvim21SJMZ+ItzY6FY2eT/HiZpHI9AK/tn8TTal41tri58dawL14ojHH
4a8LRsYhkdGkc5J9QF/E14T8Ivgve+KtU1ezstLtvDOmQuxa6jAF4Vz9wvjJB+tZOnNPTUpcqvc/
mW+Gn/BNX9o7x7DY3nx6+K/jDw5FOQZfAHwJiSzt0U/eiku9rTyDtuR1r9Tvgb/wTD/Zc+Ht3Yav
4f8Ah74Ju/G0OA3ijx2W1PxBnuTPeF5QfXDV+8Phn4X+H/B9t5drHL9sAwbqQ8fkcn8c1R8VfD3w
x4lgdNc0i1lDrgXluBHN/vBgKcMPbWTuP2sYr3VY+NLf9nrRLIIJpbgW6gDZGp8r6FQMEVuXnwf8
IaVp2oNHpkdzPFCCpkTeP/rV68fhVrOgIx8FeMtc0qPtb66wuo+nQdMCuK8Rah8R9Asblde8MaTr
+nohDap4clYTOMdfLZQP/Hq2jSUOgOTZ5b4J8O6VBaTNBpNoqJKwLLGMj3rqm0yFRNlIo42HyfL1
Pb6VV8A+NfCVzbXdpLePoN8HLGz8RR/Zsk9gTwa9Km0+0uoUvLSWFlfrPGwkjb8R0rP6rEi/NueU
QacrXMSmP5gwIPbr6V+rPwOXy/BemxhcDk/Tivzoh0nF0gIUlyMOnINfpT8G4fJ8F2KEfMO9Y16M
acbopHq9FFFcgzyOWOwsrqd4bW3tpWyMBRGrr3wT8oNfxz/8FcviP4L+HP7Tn7dOufEjxLpGhaFe
+HvCEVtc3TqnmF7HVl8qPPMkpIBCKCcAnpX7d6t/wUV+NPxh1bUvB/7GX7DPxs+IurxzOrfFP4/r
B4A8DaeyMU8+VrgyXtyFOGEcNud+PvL1r+cv9sf9lj4s2X7aPxo+KH7bnxC8E/HH45H4f6Lq1h/w
ienTWnhjw1HPc6tElrbW8+43EiCA4ncA/vH4HGOjF1E4rlRnRi1U5up8Hfs3+AfiX8XrX4S/Gb41
AaB4W8JaNZN4M+DjMuyB0tEjh1m5GSGnZC7RrkY3rgZAr9DZU3NJt/dFiOUXYePavJvgVLn4M/CO
5t1a2eTw1YN6lXFsmH5yNw6D0r1NGyUSMYH93JP868f1PVufJ1xYQeJf22dKuv8Aj4t/hP4HkdwT
uEVxqNxIFznoSgAGOxr6V1zRND8S6ZPoviTRdN8R6Lex7LjRtegS9tpR6FJAQT6E9K+avg6v9pft
J/taa4Z1Y6ZqGkaMqL1VYdMhmKk9/mkz+Jr6xMS7XbJy/JJNID5Nb4RfFD4TXB1P9mu4uPEfhmeX
L/s9eLLoy6dGM5YaZcyHNo55/c5KK2MKBXqPwj/aA8NePdVutF0u41rwH8TvDp/4mfw48VpJp+s2
bqcFlVgDNHnIEsW5Txg816xY/ES0+HPir4cXd9od7rX/AAmXiGz0JDYFA0LXEqorsTztXOSB1ANc
l+2T8L/hj4nk8W6148hvtLPgtjdWnjvwmXt9a0hg2DJBJH8568ocg9watRThfqPc/T34W69F4h8H
2uo6hNFJe2+VleYKzKoH3iP4f+BDPeud+JH7S/wR+FdjHN43+IvhTRQi7I7LUtQjWXP+xGWLyE9N
qrnniuY/Yd/4JE2H7QXhzxLN8bv2xf2mPEvgTwjqNrZ2fgjw1dWmgT6hFNptveb7i8gRpmIW4CdU
OF61+6nwT/4JvfsSfsu6Xdt8G/2f/AOl66YW8zxV4ltjrWtTuV5ke6uS7lj1J+terQo1KivaxwVa
0Iysj+fCz/aK+NPxYtRL+y/+y18bPjBZSEBPGV3pFx4Y8OjP8X27UBFGw9l3ZGSBxX0To37CH7c3
xGsLC/8A2ivjp4f/AGcfDOvxhp9I+Aemx65d2yEghWvp1lhaTHVljAB6dK/ZiXTj9sW3eFDFE22K
IKFjiXPRQMBfwr6+0CJF0TSI3jibKhSpUEEYPB7N+Nb0sNrZu5lWr8vTc/lq/bk/4JpfAP4M/sKf
tE/EDw1rvir9ozxjFpUWPG/xw1+bXL+yJuY1821hLrBbMAzAiOMZBGc4r079ir4MfC+D4CfFyFPB
uiWVvH4J1SNY9JtYrdYyunSqJAqKFDjP3+or9BP+CvnhHwtZf8E+/wBpnXbTTLXStTbTLeFZbFCq
uz3sOAQDgdDzivjj9mC5l0f9nD44XdsJfNsvAerSRog+Rm/s+Tg59TkVy4qlGFSNuxrSqOdNtlD4
b+E0s/hx8P7SBrWBLXR7REi28FRAmCO2eTn1rQ1HQbzIW5siqynO7A2t78V9zaL8J/Buo+FvBfhr
TNaPh3xFaaPZRtpPiKEweYwtkyEkPyt9c1594m+C/jHw/JcG90yYW1o2VeAidJR7Fcj/ACK19jKK
12FGbTPwQ/bc0j+yvjr+y9rhliFvdWfiXTTtA3b3sBIg/wDIX86/PXTDK1tJ5gKE3MrlCB/z0P8A
hX6s/wDBSfSm03xr+ylDdW6Wsk+u6xKIyCH2f2Fdqw+oLLX5F3OuWvh7w3qutTRNNBZPO2xmKMX3
MUXofvHj25rTDLRkVbyd0dQQwkAV5I4iemc4/OmMkrzIgZiiNnzOM/SsCHWNRtLeyl8S2VvYi9k+
/by7lhBGVjbjlhkAkdweKb4o8baJ4E8M6l4t8Qi6XQdNdBcXmnxNcNArHAYqPmI7kgcCup6id9LH
Vyux5BL/AOz2oL5gXIAOfvJ8p6+1cnonjXwl4gS3n0PxV4e1WK7w8clrdxv5qnkYXO5TjHUZrsCI
yvllWC4zvhy5z+IA/Wi5CTOa8WJ4ln8PaxbeGbu1i1yeEG0kuXUKjerdOnXFZV3ZXd34H1K08UCy
u7640qWG9eML5TkxnJA9D3rr97Km4oHCAMJI1JMg/vscYA9qx/FOpLaeEPEmqTylks9PuJHDAcBY
zwMCk9S2mz61/ZeuZ5/2dPguZ5zcMvh21TzUJ4CR7FUk8ngA/jXvNmA13ag7jmVMBeSTuHFeIfs3
wPafAD4PQyoUL+HLKQL0ILRK38mr3nRt51jSgkfmsbmMBc4/jHNFtNCk7ang8NzJe/H39rO4S32K
fGdpCFQH/lnoFgpH4HiqPxE+IWj+ANEOpajcxm4f5Es03GQueFCgfMzbiMAdTXiXjH436Z4C/aB/
a18Ow2d7r/jC5+IMqWfh3SAJridjptmMFMjYN3AZiBjqRXTfDz4VeKrzxGPH3xdu7O98UIpaw8GW
b+fa6RvH3pGI2yTYOMrkLz1ODX5Lm+ChhcXVxWJXut3jHrO1tfKK633PvsBjKlfDU8Ph1qlaT6R8
n59jR+E/gu/ku3+J3jy1uD458QHdDpt6oL6Vb5wFI6B5B8zdwODW5Y4t/ilqLJsWBombMZ53Y/Qe
1euW5MbMixlgxC7l5xgY/wA//WrznRdOik8Ya5qEnlSMgwuc5HIr5mtjJY6rUrVOq+S8l2SPZo4S
OFhClH5+b7mxqmtSL4q8N6RCEZbiGW4lkOQ4KkAD0xzWZ4t+2f8ACH+LTdStKitMsc0gGVTHGK5x
9We++L66eFcnSNLGA+ODJJn/ANkrqPiLJ5PgbxGicBIWG89M7e/41FNKnKEe9vxZcXzQnJvuj7x+
GF55n/BOL9luKRv3gkviAe4N5JzX5h/A3zZv2r/2nJjEyRINPhE6KCGATJHP1r9PvBFubT/gnf8A
sqQkr5gtJZMxjHzNcSMf51+Zf7O0r3Hxz/aZvGcnGqwxe3FunX9a/faV+Wn6I/HOZtz9WfacWfLX
PXFPpBkZHTHFLXQKOyM3UY3/ALPv22nJgcCv5+fiRFHN8Xf2hJTK5uDoloixt90hiQW/A1/QnqAk
Gn3n3NrQt9elfz8/EQwL8bfjgVT5v7Cs0cSEADMo5xXlZyuaj81+aPQyzSrr2f5M/rT8D22o6Z+z
l4Gt9NKz6ja+FNPFujY2mUW6YB+tafw18Tv8QfCLanqK3UWsaXI9rqOlXR2fY5U4KkDGAeoz2o8K
26t8IPAdtAZLgHR9Oztby1I8mP1/xrzL4i+H/iN4W1XXPEnwp8M3Op2vxCtBZ6nZtOkJtJgNn2zB
68HnHpXk2PQacNzpbL47aXbeNP7D/sP+zfh9550+L4jSMyWr3w4+zsCcgE8b+me9ed/EW08SfEb4
pWnhXwj4u1TwlL8PEbULjUtLl3W73T/6m2kHKuDjcfavbNI+Fdj/AMK70/wBr17bXWhtZLHJZ20O
5ZJiNzOWPzb9xJzml+DXwt034YaZrFlY32qavfapeGaTVdYCyTEAYVC2Bwo4HH40wTbMvwxrPjLx
X8MvHMHjbw9daD4oW1vLa8DcQ3DCBh58QOcK3Xivyw/ZZy3wW8OxmR3+xT3lsQ3X5LlhX7VyW6mL
W4Jw8puFlMe48AvGykfTmvxE/Zs1WytfBHjnSLi5t9PXwL4n1S0uZbp1jjT/AEgvks5VenuK7sum
ozdzkxydlc+knJjCkBSAecnkDPUDvUi4YytiNh2u9xKIP9oYyM9BzXyyn7Sc3xL8RXfgX9lv4b+K
P2h/Flo5gn1fSSmleFLF+hNxqFwApCnqIlc8Vz/xs/Y/+OFn8L/GHx2/al+O2pavpvgGxl1aD4K/
BwTaf4egdQPLimumIluNrHBIUKcZFerKvGLPPVJyR9HCaJvFOqzxrE89rZ7X3qshRcfdOc89a/b3
/gir8MvB11+xT4a1RDBf3ut65qlxcWBcFFIvHxhR7V/Oz8Abl4fg1c+OdVCwSazpjXLTTOSiJ5Jx
855OOBzzxX65f8EuPFmseCP2XfhbfeHb2WS1u5Lm5dIX3I5e5Ynpj1oq1LOIo+8mk9j+k5dB8Pac
gNppFvA4OCHiXPA+leZ/Da0t/wC0vEzLCo3zMVI4/i6VD8MPi3a+P7AwXdvNDfwDDCUdTjrmtj4d
Rut/rLlQFa4ZeO4ya3unqjllBxUrnd3tgjlWu4VZJxlUA4HtXO3ukxtlbeMyAHiN/uj2r0IbSsis
ocP/AH+dv0qrJbRIoKg5GOa15big7JWPIbrTIZj5kZVHTgpOflz+NcZr+kIbK8WWGJwR0KBh+te5
3dnG8TboEY5POK5jU9FKWt0gPmExZaT74GajlN/a33PmCy8L6ZqdjPDdaPp9/GzkeRdQpJGQO20j
ArgdV+E+mJcST+H77WPCF2OSmhzMtsp/65HKEe2K95fUNF8G6XcXet39rp6JIdsV0w8xwepAGa82
m8Q+LvHU0i+BfDotdHYlV8X69mGMn1SL7zj0PFJOx0bnmV5cfEDwX5c17d+HvEumQfMZbspZ3OPx
IGfwr9LfgZrza54L0m8SylsormPd5NyCrA+x6MPcV8J6Z8Hrax1KPV/El5c+MdZ3ZE+oHMFse+xP
8c1+i3w3t47fw9ZRRRJbrEgHlx8A8f56Vw4pPfoNHodFFFcgz5J1r42WtzcX2n+BvC/inxxfRs3y
6fbvb2sZBwMzSgqADwcV/Nh/wUin8X6x+1X8cNa8YeHrLw1qZ+FnhtBYWN39pYqL/XmU7+hPJzj6
dq/qtu44Ip71RDCkZjICIgGMfSv5h/8AgqDeSan+1D+0tbtayM+j/DzwxbrMuNrZk1qTnHK/e6V1
V4WpKSRlhp3nex+T/wAB9z/BH4RuoWLPhiwbyz1BNuhP869bj8uFvMZgNqMxcngEZ/8AiTXkvwMh
Y/Bf4QBSS58MaeCrcD/j2Titf4q+JF8D/DPxz4qvCka+GtJuLpwG64ikZSPfL4x714lz107s8F/Z
CD694U+KXxSljX7T8W/HWr3yXMY3M9vbTmziP+6YoB/Ovrs+dt4Kj0NeA/ss+G7jwR+zb8HdDvke
PVX0KG7uoJxtxJcK08i8d/3gzX0LvO3k8YoEzyzxxYre+N/2f4TguvxG0RwxJydspJHuK9B/aztW
u7P4hWJneP8Ata9hsh5R5zJfImPyJrkPFNv5/wAQv2e4SD8nxA0px2wNzGtn9rTVJNFlvLj+z9T1
y4Hi3SFGm6NGJrq4LatADHGmQGZlLADI61Ub2uN6n9S3/BPLR7bRPh78XI4FlVbnxbEi5THyxaRZ
RgcDpgYr72v4xJZXalmXMbY5744r8xf+CePx58Paxouv/DvW/D/j7wD4z8Z+JNT1TSvD3j7SJ7CS
+tLeG2icJNhoZHj25ZQwOGFfp+6LcQzwudxI4QfeP4/5NfTYaalC97ngVo2k0j57uNNy6PIwVwxB
bHfPAr3jTFuV0/Skji3LCgLP+FeCeJviV8LPA2u2ukeKPF2kWOsXrl4/DtvI15qEoAOcQWwllxkj
h0Q9Kp3fxo8f6hbCP4cfBHxFJZyRBj47+LN9B4U0aEdDIYnMl4QDg8W/IB6ZqZVVTZdROaij5K/4
LNtcT/8ABN/4/wD2FLxrlm04bLYZyPtidfavin4EQ7v2afi9aQsHfVPCN1ahWJVwZkeMD3PzrXs3
7aXjLx3rPwc8X/Dz4tfGn4XfELT/ABcYy/gz4dadLY6fZLE28fvnYyXDE7QSQn3enNeNfB2+Oi/s
6ePZZruOymurOzhGoGMzRxeZewxodq/M3X8K4MRL2s00dtKm4U3fqf0A6j4L8M6t4d0zTNa8P2Gr
2VnBEpbUgIxEVjCgiQYYHA9fWvnfxXNofgu6uLbwJ8SJPtxGB4IuVHiGKQ9NixgGSP03BsVyeu6/
oGoTBPFfizxR8QGt1z/ZGm7rKz3E4HyrtY9G65q/pl/4+vbVbDwX4SsPDOm3EZcM0Shtg6ueNzkA
jODu6elelTlzLQ5Y+7uz8Gf+CxGueJ9b+If7Es/iX4YnwLewal4jUapEQsV8o0SZgCjcq3y555Ff
hN/Z0PiTwzqmhX7BbbV/PV5wf9UxkbGPcZyD2r9wv+CvPiew1T4rfsq/Dye71PxLrfh3XtZN9rdp
EZdPtphodyhsEuz8j3B372RchFjYE5xX4ZahrSeEvCWveJZ1hePRVvLpoSDtdULfLgf3duc9y1c9
LVy9Te9rHFaV4J8enVYB4x8WadPo+mAGPTbZP31wR913I4B6Zx1rufH0OtHwvqcPhy80HTNelCJb
z+KY45NOucjAhkD/AClXOE45Gc9a8n8L/E3R/s2lazdfESPx3Hrlxb2FzpmkKPJs7uddyxowAyi5
wx5xivS/irBpF14D1qHW/B2oeO9LuVAm8N6JcBLmRQcF7diRuZPvYUg9MGtLiPkKXwTYWd2y+Mf2
boNEklO4618K9RZ443PJZYfkkYZzj5z9TVRvEHg7RZ/s/h/4+fFL4STxnB03xzDKIHPpi7jkQf8A
fdaNlceGNHH2Hwp+0P438IoVAtbD4kpctGhx9xortCox0/1mPet6GT43Bdsb/B748aXeNgCza2sL
4fjH5gI/3ttJ9xlrw54k8YxeMPCdprv7RGg+NNLklLWmh+G0sYX1GQjlZXhY+aB1wAo46V9EfFiR
Yvhj49ZQAf7IuRxx8xjIr5k8FWOox/EPw/HZ/s+2fwtWSdpNT1+9lsmeb0Fv5BJcE467D14r6P8A
jVGo+GHjSIOIvPsZIi/oWXApsibZ+jfwot/sPwr+GFi8IUWfh3TI8jjGLKIH9RXqnh5d3iDRQQnl
NdRAiU8Ebx2HJ+g5NcV4Ms1tfB3hO1G50s9JtInmBO0nyExx19K4D4wfGbR/gv4ak8RyPNd635iw
6foVohmnvrpmAigiUclnYquegzk8CpV4RbepabVij8OfhF8ZvEfjL9p/48eFf2Y/iN8QvCfij4ma
7awfFLwFpkOpXE8do0du0DQoWuIRH5eMlecda1fA/jrwp44sbzUfDl7JctpVy9lfWdzA9rc2d3ES
ssE0T/MrhgQenvX6P/8ABMX4tfG74Mfsr23gjxDNc+H/ABHrOo6r4m1SGNiBHfaldyXMsZYcHyw6
RlhxlCRwRX47/s5TXGuXPx98c6ndRXNz45+I2uXg8g/udwuXRiDnDA9Qa/MeKsopUozxUW+aUlu9
NT7LhvM6jccO7cqR9FC5eFLiZEEgDFi3pXM+H4M3d5eRoP8ATHbcWH48fjit/JkjuLOMOryH73QA
VZjiltre2t7ZUVEbJYDrxXwTdkz7Jx5pRfY8F8OTi7+Ofjq5LF47S3tbdVVRwyo5PP1atz4gzSP4
B8bF5VYpI6r5Z4BwODXLeEfJtfiz42kIfzL27yJWyAMRJx78n9aueNZx/wAIN8R9z+WIdSlXyuOf
3anNexKknVj6RPO5v3bu9byP0u8JTNF+wJ+yxBMn7w6Z5o7clnJr8zf2YAk/xR/aVvP+WbeIgmB7
W8fFfpzoisf2FP2VzEwVY9Hj3B1xgFHPDHg81+XX7Jkstx45/aLuSgiV/FUo2KQ+cQR4Oa/c0rcn
oj8kgrOb8z7kJJZsjHPSigsWJZjkk9aK3YloVbr57bUEYttVGUAHttzX8/8A40t2m+Mv7Rk2xXEG
g27C4m+bBBLD+Vfv5OT5Go89Vbn/ALZ1+EGuRG6+K37TytvfydJt4FbGB/qXOK8XPG40G/Nfmehl
qTqff+R/WH8Irz/hIvgT8M7+IK4uvD2nuue5+zRnr9a9cnVU0+VpSIZxEAAxOBx0r5f/AGMNcbxJ
+yR8DdUuHzK3h6CP90QSTGNmTjvxivo+S7vLhFhtdOlSHy8PcapgK/H8OOa8xtHoxXOrmjZSh7W0
EcWy3EeWbP7sn1JrGs9VgtVuY3uRNcyTnFrbjduXHGP8alsdJluI7db+5muhESBaQYWId+eV4xXz
58W/2xP2WPgNLdaX43+KnhOy16FS6+F/C6za1qx9F8q3RiDnsxUe9DdtbGqs9T6Qsri8u53W60+M
W8Z+QuGZm9iAR+dfiZ8KP2Jvhf8AFb47ftRQ/GPV/G/ifRvDfixZ4/g9BqD6foJjuY/NS5nS3KPP
u5G12K+1cv44/wCCuPir4pfEjwd8HP2ZvAtv4T1/xdqcFlH4j+JJh1HVbhDIN7R6bAXFvlc/NNKu
3uK/ZDwR8FrHwz8R/GXxTGpXEutfEXTrS21nRhCYreS6gXC3CgEqDgkbVJA9a2wrblc48XKLSNv4
f/C/wT4C0Gx8LeBfCPh/wX4UsUEdvoPh21S2tkQdtqj5j7tk+9cZ+1h4O8KeI/2avjPo3irUbvSf
Dtxokn2zV4PMc26KQQdqqzOMgZVe1fUFhauWgEUQSM/LtI71tXGmwtY3LXCIzqpGyRdwYEYIIPBz
XoXVzz22z+NPQv2sfixpPwfufCWm+C/g3feBrW0lsY/HeqeKLWLThAAyrPJCzCUHaAdmN2eK/on/
AOCVY1fUP2PfhNrWp6VrHh2+Xz9trcQPb2N9H5hKXMKOM+W45B7jBrjZv2Df2Px8Qr74iP8As2/D
F/GE92bs6wdPRkaUtkuYj+7znn7vWv1S8LWsVlpFnDBDDBFFFGiQQqFVEVcKoHQADgDtWrbq2SJc
eTU+jfBPxyufBNskN34J03UIivz6hpuIpM464Fep/Cn9pD4XX95f6fd6qdD1K4lLC31RGj2k9QWI
C18gyiSVWYhDubqAAa5PQ7RLmbUVuY4pbdGYN5qZC8n14rSnVcHbcidNVEfs9p2qabqsAu9LvIdV
t5BlZdLkSdPx25Ip80su0L5ErnOWONoUelfiRdeMtJ8GXY/4RLxV4g07xAD8mn+GDLMWbsCqnaOf
WvQvD/7QX7SdxHHF4jjh1Dw+W2vBPNHaaxOvYYVWAPqTXTSxKqOxk6HLsfqH4p8ceFfClq8+t6xb
RMvK2VqRJNL/ALOzlvyrzPUtQ+KHjy0kh8N6NB4F8M3gCnXNWG+6YeyHAz+FeIfDr48fBTw9dCbx
R4Q8R+FPEk+Vn1rxVEdQBPbE3zKo9gBX134d+I3grxlbM/hbxNperCTkJazq0uO428dq2vfZmWsd
keQeFPgd4YsJBe+JHvPGuutIWbUPEDb4Y8dCkf3RXp1zpvkjZHbq8MQ2o9uBHtX0GOMV3llHa+W6
XMSIHyY9qg4/Gobi0ZTuMimM/dUVSiHPLueVNpJkdcBgAR8rHmvo/wAGwi30qGIDHA4NeWNYCa4i
XPlEn/WdxXsHh+BoLWNNyyqOPM6H8q48arROilV59HudFRRRXnmx8SftJ/G3WvhTH4N8M+AvB9l8
Qvi58VtQk0vw74Pvbo2du7JHJNc3l1J/yzt4IY2kZhgk7VByRX4pft4eFPBmk6L43+KXjzxdp/iH
42fFuOz0rxDH8OLaeew063tredbMJayySSMgM02Zo8AkjNe0/tv/ALUMHhH9tOLwNF+6ni+FV9ce
H9YDnbeXTapC13DCo+9IsaIWxztDdq/n6/aY+PN98NvBniX4jXVnL4y8V6ldQ6dpmiCdiL28uJHE
MROQVG8NIcH7o9qeLqyj7q2RrhqVm5HkP7NvxPddG0b4J+P7BvCPxD8F2wsNOivQ6w+JNPg+SG+t
XYKHZ4wCYR8y4bPSqP7Y2pvefDvwj8MtMuBJrHxv8SWegxQIfn+yB2lu5AR95RFHgnphq434NWPx
b/aH/aa+G/7GP7R/hW18Q6prGtWvixvE/gi1uLTT4tFSCU3kzTg7rdopWEaS5AaUxZ6133jL4U+K
fAv7WfjPxJe3/jD44/s+/snWzeHLb4vwW63M2l65qMcU0qak0ZJZreDZE1xHkKZ0EhG41wKnJx5r
HVzpy5UfVNvBBbW1pZWCJFa2EaxQxxjKoiqFAHtgAU3zHTIZiT/tUlvdxXMNveWM1jeWF+hlS+0+
QSxzJngxkdiORU5iLRCSYNGw59zUFM4jXbg/8LD/AGfZZgEQePdLRpCOgJkGf8+ldF+1HY2Wo3d5
qV74jg8L6N4d8Sadq+p+KpLk26abaW2pJNJdbsHbtVQc4rn/ABB+++IH7P8A5beVGPH+lk+ZxjBc
5r6L8WfEnwN8JfH3iL4kfE670Gy8HeHLhri+u9bEL2SIzYRGSQgH6VrT5eVRkwkrI+0fg/8AHL9o
b9pDUP2edW/ZS8Jal8d7f4JX+rWGqftB+IYZPCXgeayvViEcizSruvbhAh8zyF2McZZSa/VDxNre
q+H7OWL4+ftPSX1jJGA3gH4TWdv4XgYngxPdO092+CfvLIucDpmvwn8F/wDBRX9pT9uay1qy/Yz+
FWs+Ivht4TuW0Zvir47mPg/wlbTJGoaC3UE3Nx5YKl9kbK2Vxnt758IP+CV3xc/aIuNQuP2rf2sP
HuqWrQF/+EH+Bpm8M6DEzdIzdOftF6MkBgChYZ+lenRX2aex58+VP3j2/wCJX/BRX9lX9l6a5i8I
+H/hx4Z1mbhvEPiG+/tPXZyR/FJcebcOx44Vh9K+QdV/bJ/4KAftZXQtf2e/2fvin4n8MawRDF8Q
viHbS+EvDUcJP3y1wiz3EXII2A56/T9ffgR+xV8F/wBjTTIrfwf8AfAt3ZXJIfxvpmlxXWuTMvJe
aSVDcN7s7n2r788I+KvBmvQb9Cv7OK4cBfsFxiKVGyM8fpXQqEptORnKsl8K0P5cvip+yl8cvg/o
3g/4jftM/H22uvEXxH1A+HdE+E3gXQRDoBu3iaYs93K7zOQsZAOVHJ4r6X+GmnqPgTrGkX8d0ItT
m0OCVQNnlCTWrZWIPcDkg5r60/4K0w3c8P7HmqotsmnaJ8RpmuppfkVGOkXAiIx1Od2K+WPAlwY/
gn4gCyAqbrQ920cbm1q1JHzfXtXLVj7OdkbRq81M/fDTvhn4L0gTLpuh21w0UjoZbjDvtBBDBjzn
LEV578Q/EOsyX1j8Lfh5bf2d421aJmutes0FyPDVl903TKfleZuRFGTgtyQQMV7lciINc28mz5CW
2oFBIznt71+e/wAVv2v/AAF+zZ8a/Fvg3xHZXMUfiYQasbpIRlt8Kw8t/wBsj+dd1VOMNHY8+jer
fqfkR/wWq8J+Hfh58Q/2Bfh/4Wt5bDSLd/Fd+8zO08t5e/2YFa5mkPMkzB3Bc88mv5nfjJ40h8D/
AAo8W372dvqupak8+l2OkXHzJc3FxKUjjK+zckd6/re/4KLWf7Pn/BQv4WeCX8J/FjXPg78cvg5d
y6l4T8daeIpo7d5YWimhuIX4mt3Q4ZOuQmASK/j4+P37Nf7ZXhr48fAr4QahJ8K/jdqOt6pd+KNM
bwzv0efUE08IXmuRKgjjDCRMDJBK54rlpzjSbjzXO6NKUlexqfCf9mLwj8M9H8NRLqmsaufDsKSr
pV2yi0+1FAJJOBuYhiwG4n2r27xfo+p69pE9honiO68E6rIyyWmv28cUrQuvVRFKNuD3xjNY+uXX
x28Eyi3+IP7K/wAX9OhVQZtW8MR2+u2qEDt5Eu/A6cIeRXJp8e/h/aNLD4gm8TeCZN3/AB5+PdIu
9Ky3qTMgyPqRXRCcX1M0mnqjz3xLpHxlFh9k1vwP8Kvi7bwoRPc6jbHTZ39G3bpIg3TOBjPavFbn
SvCul3Rk139nX4lfDi8UhhqXwp1eaRmPq0cOxmHfkGvt7SfiF4A8Tuj6J428JardzDasOn38D89M
gb67YsDCQnkOrfeFsBID+VU2nsxt2Phf4ba54R8S/E7w9baL40+L3jjUdLlklNr41he2tdFUKQ4l
DRL5j5OFMhJ59ea+p/ifpzal4SvdLDPN/bU0cBUclQTjiu1SxtUa4ngtbaK6chftCoqtwAFBOM4F
cL431rVtFi8L3Om2j6hcXetWMLW0cPnCOHzgJJj7Ad6u1gTufpNqetWHhDwzBcahcQw2+m2UQxI4
TPlxKCW7dq+ff2cPhhrX7VXxct/ip4psbqL4c+BC58NWEyYS8kbIfVWVuoCgiNexIbniqdt4S8Uf
tR/EGHwpp0EqfC/Q7uK31nVpCJFv5I9rNp8YXh88ebJ0AJH0/VfxL4h8HfsufCZdXvtLjv8AVPMt
9N0rwxokCyT6rqMpKW1jbxjBI3Ebm6IoZjgCuGvVlJ8sTaEUtWcV+0H8RNf0OPwv+zd8GIFb4x/F
aE2sGo26l08OWJQC51adM4yse4xo5AZh3r4F+Jf7EHxb/Zd0ODxN+ylqXjn4t+ELOTzNZ+CHiWWO
fVVkYF5r2zum5lctlmhKt97g8V9q/sT/AAr8XQ/HX9qz4ifE7WbbXPiJ4ni0az1i5trh57SwuTDJ
c/2daHp5MEMkEfbcdz4yxr9Cb3w7cGAqPKuE4VQnLqB0/AVwYnAwx8OSexvQxU8LK8NGfzPj9uj4
c6LDDaeOtP1rwL4mtRi70PxlpV/plzE4OCrh1PT+8vymvYvhl+0n4C+K+oGz8La34f1dHDFItEvE
llBx/wA82AYfU9a/cjVdCsL4Ot7bRXEkWFzdoJACOn3q+Mf2lP2G/hl8d9Gvbuz03R/AvxXsx9q0
T4r+FoY7LUbC7UZQyyxqDJEejI5IIPSvl8RwdSafs736dj6GhxLUi489nY+Gdegh0LxvZ65HAkdr
fk+YHBT96QF+b1PA/KuO8Uvcal8MviFdTmLz77U7uOCe3BGdq7Vf68VWtvid4q+FviI/Bf8Aa20W
38HeO9MjX+zvHVxsTw94liQ4+0WlwR5YkxyyNtYZ6EUfEz4s/DTUtAt/C/hTxVoWua/es8sOh6DK
l5cSphnMhjgLFeM5Y4HXNfJfVa+HrRp1IO6sr2urJ9z3vrNDEQc4SWz/ABP1WtpFH7DX7MS2yjMO
jxIsbE7VIRgT/PrX5e/sf7n8SftBzfJ8viu4D+VwufKSv1AvIptO/Yk/ZrgSMpv0JJBkfMN0Jbk9
+tflh+w83m3Pxyu/nJu/Fl1viVsA4Cgsd3A6da/cd+X0Pyim3Jyt3PvRVZQQxyc9TSeXIxJDnB9q
+dvH/wC1F8K/A2rP4a03UNY+KPj1+Y/h18ILVvEGpk5x+88oGOED+87riqsXhn9tP45Wts3h3SPC
H7K/gzUuG1Lx9Mur+MvKPVktIcwwMe2+QkccUSqRh1OiNKUuh618R/iD4D+F/hq71/4geLvD3hDT
TG3+na7ciAOcYwi5JlP+yozX44+D7jTPFPxM/aB1a0d9R0bX1tZLV0jKCe3aA7XBbkcdFr9tvg5+
wx8DvhRqyeLdR0vUPi78Spfnm+JPxab+2dRic8uYVlDR2oLZICAEdBivzP8AirdWWn/ta/tLw6vd
2mm31reWM4stWnjt8WotflmXd0QDp2r53PcS54drzX5nsZThYwrLme6f5H61f8EwvGVnrf7HHhsX
E9lZDwNeXmlXVxeOUW28mYlfNJYKnynPNZn7QH/BUX4E/Cea68P/AA1V/j18Q7AtFc6B4JmMekWT
jp51+yPHnPVFGfev5+PA/wAJ/jn+1Brut/Db9nTR/Gviv4brqMl5e395fT6V8Oortzhri4lXH284
/wCWaBhX6qfAf/gjL4O0+3tr/wDaX+IOofE/V5FGzwN8O5H0Xwzp/fZ5Yw8/uzjBrmo0p1rW09TS
c4wb1+7Y+OPFv7d37dX7aHiC7+GvwF07U7s3TlLvwh8EbR7DT7NScFb7XJd7IB0OxkPXGK+hfgl/
wRk+IHjBU8RftH/GS9+Huo6tP/pPgP4Nwx391IOpE+tXTSSyE/7OCvav3C8I/CrU/hnoVh4d+Hlj
4Vt/CmhxLHaeExEtksUKjopjA3N9etd/p/jMWs0cPibRtV8PTyfKtxcW4kth7h1yAPriu+nQUfi1
OKtWcvhPBPgF+wJ+yb+zTNa3/wAKvhHpMHiyLIm8eeKp5NX1yV+7m4uizsT6pgCvtW10uSYqSzKk
f3V/hHr9KLE2d9YG40y806+h6vcWUwlDH2/u11Wn2zTwxMuQO4Hc12Une0Tma53qVbW0kDxRLCCw
JIkHr61qmzjWxuTcP5jkEYfrmtVlETKqgKyjqvXNZmqTQQWdxJPLbwAKWMt02xPxNbOg07WIi7nz
fJBNHqM8LR/KZecjqM19GaWiwabA7MNhUfvWYKFOOh9q+Zr/AMUR6hqbp4d0rU9eu1JzdQ4SwVge
7969N0/wP4i8SRWsvjjxK1vpUq5Hh3ww7xhh/tuMZ9MVkk5L3Stzc1v4labYvLpOh2914h1wcGz0
mMzBW/2mAwo965nQPDHjzxldy22u6z/widhfSZbQvDY8+6kB52PJnKA9yBXr2l6HpukWX9naNp8N
hDbjCiwXyy+e7EDLH1Jr6y+A3wjuba5PifWUjSMKNiMAXXPvVUqMuZXQnJRTuT/B39mTwPovhqC4
m0r7Le35Ja7lPn3J9zI2Tmuj1f8AZssGL3Gj6hcLPJ/y1kVd2Pr1z719QRoLZVihLokfQdD9aUsx
zkk59a9NUFF3RxqtJnxhP+zLql3+7ubqO7s2O5muAsi59wSRXSeDf2XfC/hi4m1i3u9U07Vo8hbr
QrkwEZ/2clfzFfWQtzvCf8szyUH3TVgNsHBwo5wOlNU7DdWTPHIPD/xK0GJX0jxHH4ogAwNP8UW6
rIo9pocZ/EVCnxH1LTpli8ceEdS0WKP5f7S0/dc23+8cDgfjXs4mTzC64Er8bwDn86RwdkgUhfM6
kgkH6jvV2MzkNI8T+GNbZW0fVrC+kzjyZJPKl/AGvbNLgENvArDbKRkjO7PFeIap4K8L6vKkzaPa
fbhyb2xXyJc567gAa9g8MWdvYafHbW9zJdKnGXk80r7E+tcON+FGtD4jpaKKK846z+ZT/gpf+zAP
2nfhX4tk8HLe2Hx7+G8NzrXw+8a+HJTa6lp+rRJlbQHlZYZ1LJJE4KkNuJG2v5Pvh98RIPE3ijQN
U/aq+N/hLWP+FQXctzafC6XTE0G9g1VQIXm1FHdmkdB8qqoVeSR1r+zz4neJW8E+NribS9WfW9Pv
75jPodtlriLJJKxEfdweDX5Zftc+KPghoutxfEbxL8Ffhvqviy7JFlfajoFlqfii+lHCwWsYQ3Ms
nyjaCCoO455qKkedG1KTjuj4o+DWo/ED4Z6L8aP2/ItFNn4i+JPh1Pg/8F/Adxugn8SX19dxqupB
GBYp5paXaM/Jb5zzmv14/Zu+FPgD9lP9n/SfhF4m8RWXjHxPeNc6n4o8QauBPN4g1W72SXk0gJww
YbVUHOAoHQV8v/s3fsi/Fb41+N/Bf7Xv7WPinX9B1vRrSW18Efsz2iLa2HgW1lVhBdy7PkW+kRn8
2QMWjaVhxX6neGPh74K0DdfWmjQtccKmqaou68f/AGR6VpTpcqtcmrNSdz8fPir+yl4k8P6trPxC
/ZX8E+KL3wGxa61D4KalJuRVPLzaRI6hoyTljbNvUncFKAivn3wx4r0bxnp0mq6ReSyiwk+zXOnT
R+RfabLHxLDNESXikzgYYY61/SENyNIVV0Cr8o6EcCvg/wDah/Yf8MfGeTU/if8ACrUbb4QftFxW
wSPxtptuPsGt5ILWWqQgEXceOQ5BkU854rnqYdSd1oXDFptJn5I+JZp4viJ+z8YVV5JfH2lggjpk
sK2P2lfC+i+PPiL8NfBXiLR4vEHh7x18TNFsdR0OUlVurc3p3xEjnBFed6jN8RtA+MPwH+Hnxa8B
av8AD34ieEPiPpMeo21xC8mnX6Yci7sbnlJ7WRSJBhi0ZbaQMYr1v4kXES/tUfsnWVzB8l78WtNR
FB6gQXc3mf8AjtQo8sUvM6pSumf0AfB/4R/DX4SaV4d+Gvwt8J6R4G8B6dckW+jaerCMNLJ++Zyx
3tKxH3yTxjiv1s8N+GdD0DTorfSrK3tmiwWYkFj9K/Muwe3s9Ttr2NpFgt5o5C6HnAI5FfW2r/tC
6Jp9sRptq892Vx5lwMpnb3r2cG0lc8OvFzsz6cnYJHvMkUaKckSruVvbHvXyb+0nN8O/hb8LfiL8
XEs2s/EvhPTJ9StIdBn8h7m5RSYoSp+Vg8m1SOM5615jrHx/8b6tEBaXP2K1ORst1w3457V8B/t3
+KfEdv8Aso/HbxXDJNrF74O0OXX/AOz7iUqlz9iZboxZzg7vK2n2Jq6mLjJNIcKburnnX7avwM+O
6fBDSvFPxk+N2t/GL9o3wnrlp4l0n4deFU/s3RLbT0tT5tglptPmzjznHmtLyFUAda+DPiL+1x8O
oPgh43+B+p+LdB8CfETx1o8P2AeI9Sis7m2uo2SeAbQd6Sh0jUhQeRXcfHb/AIKY/CL4ifB5/jt4
c+KGg6zBq+nCaG5huN01uREw8kgnKuGOwJ1OGOK/AbU/2d/Dni79n3xN8Y/jXpFtr/xf+K1za6kJ
tRG+azeW5j+x6fFj94hWMxRlU9eeleTWqpWV9T1acVKLR/ox/sq+ONT8c/s9/CXxZ4m1FdQ8Xa7o
cF3qL5EkpkddoADAbgQAcHnqa/LL/goB/wAEzP2m/j38c7z47/s7/HHwHb3Xi7TLXT9V+Fvx1t7q
50mye2VvLfT7i0KSWodSd6yLIMjIPJFbfhfW/i/8EtK0Kfw1IuteGdEsLeA+FptsL2OyFAUiY4aR
UGPlYnlq+rvBH7f/AMPruxttO8VXhg8QOvlG08sreBnBBVUHuOg/rXoJqvCz6HnRpypO8UfyT/EH
xV+0/wDBD4qeOvg/8RfghoXjvXvhzcpaarqn7P3iZru3gkZS6EQXkMbkYXoTn3r5I1D9r7SNP/bH
8AeLvGenfE/4cDwb4JvoGj8WaQ7zRTXV5Hl/3QcCHbEctn17cV/R98TV8J+NP2k/2qfE0/g640mL
X30263axCRd3G6zudsihucdzX5I/s9fsa/ti/tQftVftZeKvgN4j+AfiCX4O6dpWiS6J8RoruyWW
K7NzcRWcE0SOkc4C/OzBRgj615zw6lflWp6Sq8mkj0fwV+298M/GskMegfFL4beI7iZQ39nT3kUd
wzHlhsfDL8xPBr2GXxt4E8V2x/4Sr4deHPENndja21Yrtee43AivF/2mP2Fv2ifg54If4jftVfsJ
+EvFvgmxnt7S58RfDK+0bxfJbTzypDu8oMLoJvZAMKTXxvY/DH9m7QNR0/S9Av8A4sfs3+J77zZY
tChvtZ8ISTqgBdltbpVhlCggsVQqARnrWN5x0kXGpGpsz7K179lL9hXxzdz3usfCPRNE1W45Fxpc
clnsbuf3LrzXEXn/AATi+Ad5i5+HPxi+JvgOa5P/AB66Jq4lSL6xXIcf+PV5nY+GviPcRQyfCj9p
XTvGUaHjTPF9vYaysvHRmtlSU/XaatyeOf2jPCzgeKvg5ofja1t+P7T+FmqIs34wXjJJ+VVSrO75
mE6anui9ffsB/HvRS0ng7462XizSlHFr400aGS6cDsZraSMfjsFeX6r+xv8AtUeI/EWlaDqWreFP
BXh2F1M/iXwks91qU6Z+aKBZQI4yR1cs+3jivaNG/ar8OW1ybbxBcfEH4UX6DbJB450bUNOtIwvU
m6KtbH/v4RX1D8Iv2h9K8Y6zp9n4d+KPgjxjpjupkfS9Xt7h4xnncqthR67hiur63KWiZHsIn0V8
Hfhj4H/Zy+GCahdSWei6L4Ys5L261S7cKYAqFpp5C33mbBLP0BPTFa/wB+Cvjn9o74s6Z+0f8VND
bwn8LtA8K3usfDrwFqMEgv4le4ghTXruN+A9wjSCIchU3HIJxWp8F/hb4h/4KAftIWfw40y0v5v2
Mvg5JFdePvGtrayR2fizVIZd6+GbadxtlgVlU3LRfKy5XJJYV+xvxM1ew07XP2ktQtYLa0t/Avhr
SNIiS0IhjtoWSadYV/upwo2/StHGydzidROXKfmH+xv4b0658M/GTxRPc2dvqfjz4la1bxi5Hl+f
HYiGziIJ9oj+dfV2veCdQ02VYJreS0lQcCEhgw9elcl+xH8Zfgb4U/YW+HreKG0zxj4s8V6jr+tS
eG9Igl1C7WS71y9kRR5QJUlPL5J4re+GfgP9o74oeJNX1zwtbt4C8HW4JttJ8eOk4dW5CqnJHHdu
BTlS0Ti73BS3ueca7Z6fpNvPdaxJZ2lvGcmdjhzXh2qeKW1KdofBeialr5P/AC8QYWIY7ng8V9e+
JPgXp+jaktz8QvDHim+1sks934jTztHPP3ojF+7VfyNbEPgeZrBbnSNHguNLhHyXelLugx/dGPSq
5JRVmUpLofnD4x+BJ+K1kE+MGkeHNX0J8mLQ720W6dCRg/MwyjEcZBFeM3H7Jv7PvwY8C/EbxD8N
/hN4U8HaqNGulbV7SPfe/wCqYkAkkrn2I+lfqjqGgsFZrZGZ25aMjivmn9oqySy+CvxMltLGS21K
TS5rcTxyLEu6ZPLBZiQAvzdTWUqUbNtalKtJNWPE/iTpx0H9kr9n7TBLGy6XoESq0gKgA2uQG9+a
/FD9kz9kq9+MmnfEfxL4w+Nfj7Svh1qPiy/gPw1+G5h0sXZDD/X3hDykE9kC8cZr9hP2xfjB8H/h
t8C/hj4O1L4ofD9tX8Pabb2k+iW+pQPcBktgm75W+bBHGOua+WP+Ca+jX0XwH13V7yKXyfEHivVL
u3Z8lpEaTKOM8/MORXXjXZrldjHL3vc+kfhL+z38KPghbT6T8MfA+ieEY53LT39srz6hd44zJPJl
29yTzXuFvbEbUJB3HLBDkGtmzspZpSJoNyEZyetdBaaV5UvmldttGeUNcOrPSlLlMy3sGzv3mYtz
hOCK8B+MX7Ff7NPx78RWfir4ufDHT9a8SIqRv4mt7iayuJkXpHM8LgyL2wV6V9b29uJm8u2UgSdz
kfzrM8Qf6Gi/acBgeM9/aqlHlMpT52hvgPwH4V8F6DpnhTwd4e0jwr4S0GMQ2ukaFb+RDEnZlTqx
Pdjk16ja6fHb/urXLhj1qPwlbLPYpMfnE+CSOcV6Hb2NtbAMoGZD+VEpcxzy0ZhQadNgBht3HGQM
EV050mMwS2kscc0VwMGOVQ6kfQirltbzgSFAHh7oafq+u+HvDkA/tbVLPTZwA3kXMmHPoAo+Yn0A
FKSsJu557qnwz0O2tJrzQrm+8OXnUf2PNuiz/tKeMeorOt/EHjzwdpP2zW4NM8R6HD1vrGUW1wB/
1zOSx+hputeK/GXiqzvbfwn4fl0vSWBB8TeJU+zK2f4lj6sfTIrT8I/DvTjZ2moeJdSvvFer243L
c6j8lqnPRI+hPvTjU5NhGbp/xfg8TXMWl+FdMmsriYbhd+J826AjrtTq/wCddWPAkepxNqPijV7v
xBczHf8AYYnEVrH9EHOPqTXYXug6LqlolreaVazKfuq/y7f90joawLb4f+JrV8eDNU1QMp/5BuoA
z25HYA84rtlTk1zMNznV062tZClpb28FvnAFsoVT+Ar17w/pN/qbW9np8MkssqAAAEqB/SsLwx8P
viEJVfxl4O1zT7GWQ51XTovPgYZ+9xkr9MV+i/wt8H+A9K023m8PXlnquqbBv2uDPGcfdKnnP4Vt
QV0ZTlyo5H4ZfAW1sVt9X8RqkksgD/ZS5I9utfSlrprW0TR28C29kR5aRr2xzV5DH5aFflnxj5+O
fT61PNvEOHOHX7w9D710KJy8zasxkJDxqTyemTUmB6Cmp8qLu4471TJBLEHIB6irEX6pKTuXJPXn
NW2ZY03SMI1HV5OAK8f8UfGLwzpU8mm6TPceLPEMRI/sTRVMocj+8V4GPc9qly5RqLlsevsF2tlk
Qd3bgCvK/Fnxd8IeGpVsY55tW1W5x5eg6Z+8kkccADvye1cjY+H/AInfEEfavFmry+B/C1ycpoWh
ybL+49nZc44969J8IfD/AMF+Cbd4tD062W9un3HU7pvtN3IT6ueeanm5hq3Vnm9ivxf+IcoXVGb4
Y+HFO5bW3UXOoSqe43D5M9Oc19VeEdGttB0m2021a6kSAfNPePvlkPdm4rlhGN25SWbrwcnGeteh
abLE1pABLGzFegYEnHWuPGRtFGtJ80jRooBB5ByD3FFeedJ/Nj8bPCn7Z8/xV8TaX8FtP/Zj+H/w
5mmeKy+IHjldY8Qa68LDDO1hEYbfzOuC04wcEjtXzv4X/Y7h+GXivUfibq3jXxP8WvjBri+Xd+M/
iBBEltbjOfs9lbwj/Ro+B825m4wSetf0yah8D/DWpTzTyQhDMclaxp/2cfB9yqLJDGQnTcMn+VPR
7q5XNY/JDwRrP2/TYdMv7eS11yBQsulS8Rtjqyk9a9MEMkaqDFMgxwJFINfolqP7Mfge+SNZLRA8
IGy5txsm3Dp8wGcVa0/9n/QoIfs1zbibbwssh3ED6mkZyjzH5wyx3B+727UpjJBDiTaRyUHP4V+m
A/Z88H4G63+bHP1pT+z54N5/0cj3FBLgfi58ZND0zUdJ8PS6roFpqWqaNfR3Fpqeq24kexcsVWRS
OmV25PrX5K2/we1T4s/tLfCI6ffDRNU8CeMLbxLBeXKF0kW2VzJD/s7k8xR7sB3r+we5/Z68FX1t
PaX9jHfWlyADDMg3Hb2zjjPSvLNA/Yb+DfhvxkPGej6LLZ6hsdcNLvA3HJqZx51Y6adRU42Z8RvD
d7Gae3JSUqoki+XaoGDx7mvWPBvwk1LxhZi+k1CztbCU/PvOZF544+tfdB+Avg8c/Zxn16/0pY/g
h4eto3jt3uY1k6hHKj8hXR9YUbX6GEo8x8vD4P8AgXw+p/tzxTJMdvItlVx/u15T8WoPhh4g8Oaz
4FsNFlu9K12zm0+7uboqYHgmiaKQOMHcNrnjvgV9w3nwI0Z9yxoX3872JJz75rjNV/ZV8Na0vl6r
fXpikbLWdplYyPTIGRRPE81pLqKMLdT/AD7/AI1f8Ef/ABR+zX8UbJPhj8Pk/aO+FAle/wBHCa7B
omoabIHDfZ7+zYtDO6Bl8uaNvmQ4ZQymv0I/Z3/Y3/aJ+L/xC8CfEf42eCtL8K+Hfhvdw6tpHwzt
7oSx3l1H/qnvJCoj2Jt3bEOT0zX9iei/sjfCXRFb7H4Ys45WxiS6BuGJz3LZrsF+AHhRV2Koi2/w
RRhUA9uK5XTT1Or2zWh+MbfCvX/EVw0/jTxRf3Mc26RtL8PxvCvzHjDNkD0x7Vpz/BTwPc6P9gbQ
buLaQFvnKm9U54ZXAyrZ74xX7FH4AeFm6gv9eP6UJ8BPC8ZZBG67sNuUZGQfXFayfM7nPr3P5mxo
niDQ/jT+0VpereL73X9LtNL0pIY9bj33lsohuCFLg4IAGM4rjP8Ag38+Nmi2l9/wUW8d6/GILjxt
8V49O0tZZF2TQWFkYQ68/N989K/oO+IH7B/gXxdp3xY+yTXOn+IfivZCxn1mEFZLdRHIgdWxkMFk
bHvivJP2df8AglV+z/8AAb4Y6n8MbXwrb65o2p3ragL++iIuY5Rbxx+aXG2TzXKliw7mmpcklYtx
U46s4r/gpB42utc/ZosvDug2U19H8QPEWjWQunBDRgajFK5A7f6v8hX4/eKrm88N/t6/sS+JLS30
+5l0238UxS2GtxLcRzQ/YLcGNkIIOSQefSv6Sbj9kzRZtD8O+FbzXPEmr+F/D96t3baTrl0+oeSY
87f3kg3t14yenHauQvP2Dvhlf/E3wD8ULqO7bV/h3bajb6cioNqvehUd2BHZEABNOpVVWVyYL2as
fK1t+xp+xx+1zper3XxL/Zx8HaL41fLyeKfh+p0jUVGT8ySxEAE/T14r578Vf8EPfA+nMbj4HftM
fF/wqr/8y18VLez8XWCeysTbz/hvNftz4a+DWm+D3ml8OXU9sbkEESjsfXiusuvC+rTQ+VDerHH6
lPn/ADxVqVKruthPnezP5W/HH/BLX9tDwbrKWWoaj+z18QPhqZXe68Xw6le6Hc2MIhaRrmWxuIrh
H6Y2JMevUV+d3wV/4J3/AAf+Inwa8M/EX4keHPD1x4+uRc38XivSwtkzAyyCNN0WMplM/MQea/sy
+J37NmqfELQ9T0F/EN5Dp/iK2ntrycSOk0SyxshZB64PGK8R0z/gmd+z23g/4WeE/EfgWPxDD8KI
lTTF1O5uUihlClTMREyiXOd21wQCOlc6UVKXKaqpLqz4B/YG+N2o/s+/sh/Br4FeDfh/c654j0CG
+e9u5ZWXT1nuNRuJ97Oq7ThZFGC5atnT9Y+K3ivwp+3D4j8b6ZY6brHjLUtMtLCwtN7Qts0+RBsZ
+DydpNfs5B8B/CsOm6LpFppljY2GkwCGNba3SJQAegVQOf8AaPNF/wDA/wAO3/h658Ovp8Qsrm4+
1kCMKzunC7jjngmtnUbVjNJRd0j8Z/2NfhlYfDr4JfB7wt440M6HdeGdLihu4dMRMeYzsxdnx8+S
xPtmv1+8E654QuNO+z+HJV8lcR+S6hXIx1z6Vrr8AfCqRRJFA0flxquxhlfcYq7b/A/w/ZTCbTxc
WrKMh4pCnP0p0q8aT1IqR59TXk06K4t7i0vEhubKdfntp1Dqw9CDXjN98D9Nsr6TWvB+tXng/Vrg
nNhbRi40x89A0ZwQD3wa+k7Hw2bO3jglmmuWj7uM/rWymj2uAJYywH901u8fF9DBU6iPy3+Kfw+8
Y6JdC517QLRoLlyJNa8LEmKQ9iyn7lfLvxY+F/ij4geBPEWjeE7nRdO1vVoQlvd+JrT7fp784MEs
K4LK4GCwYEA5FfvFd6Bps6bJLYyRH+CRfMBPupyCK5DUfhR4Ov5BdLo1vaXanJe1GxTx1Cjis511
L3ovU3gmkr7n8EPx/wD2D/2q/EPxLC+H/wBmL9jn4RJeNtm+Imi3d/qkW4ADzRZyhW3HGQvmBQSa
+7v2Xf2Zrn9nP4a/8IZf+MNY8e+I7+5k1DVNf1YCCOSZ8bkt4k4hReirk8Dqa/q6139nP4f+Ild7
7S45pOoeRNrZrhv+GQfh9EB5dpGQ5ydy5I/SsG76s0ufhxbaaF3SQhmycAKDk44rYh0q5ljCssiD
d0cEV+20X7Ifw6jYsbGNjH0I4z+laqfss+A9o/0VF/2Sv/1qv2g+ex+Mmm6bBbvmJJLiTurjIzXl
3xRivbWa1/dKMjzFDdz6Cv3zi/Zi8DW5ylqn1VB/hXGeK/2OPAPiQxPPaBjAOCef0qZS5tx09Hc/
J74ZxNN4ahkuBDbrKPmeVtir2JyeldDrHjPw14fW3tZtVi1TUlIKaV4e23dy6noSFJIB9cVz3/BS
f9if4xanonw7sfhV8PvG/wAQfhxcQ3Flq/h34c7ptQsruQp5N+9urKZowqshU5Vd2SK+YtM/Zl/a
y+G/xR8Zt8IPg98T/A+k614btHj8H2cei2j3bQwBBLGHVmaRG6opz6g0+b3XHuKUuZ3PrSCT4meL
k8y00mw8G6JOD5eoz7p7x19dowAfrV3w78OtA0e7j1K7jutd1mRt51PX3EsvHUqMYQfWviy//ZG/
bi8U+MNH8eeKfhr+1Bf61c2vh66vzaatY2lrLNBeS+fGbZXWNCqbCw8vBHJzXXwfDH/gqrqV7cPB
4T/aE0eG28VyMYbn/hHlH9mGMFEDbB5q7hjIPepZO59zazpWpahpd1DZ2dxcG8yFMZGB7ADmuq+H
nwr8Z69pVrFDYLHDbuR5sgZiD/SvjDV/DP8AwVqe1+LOr6N4W+K1o2q3kGk6RpTp4eV4bc3GHu7a
M/6s+UfmlPoaqXvxD/4KV+Hvil4g+FX9n/GjX9S8O+E4Vt9C8IL4fuWW6MYP25njUoZd2cFjg8iq
hK25PKfqZafBTwr4ZgtNU+I/jvw54WsbqTbFLrt9DYxyP/cVpSAx+lfS/hPwd4N02wtpvD0Om61a
zjK6laTx3EbjsVZcg1+OP7TPw7/a8+KX7FnwUtPHnwG+Ifxb+I0sVzb6/pk2naTd+JtNuZJB9nv2
twgi4AIcx5IB5GK8e1T4R/8ABS/4XeEvGWm/A/wR8Vvh897d6fNp+l+CbPQJ4YrVLBA8IDqxDCXO
fQ5Ga7Vi4siVOUnoz+iWGGBFWNYmglgBb7KcYI+h5NeWfEHQfhfaR2ms+JfEeifDe6v5Vhh1+81G
DS98zHKxr5hAdj2XOTX4haLb/wDBYO+vdPGvn9oCxt9B8NXlws02m6BLDqereZ+7hkWJQ6fIQVbp
kGvSP2g/gZ+2v8YP2APhj8H/AIl+DPiJrX7QviHXklvvEem2+na6LGFZC6NeSnd9nVgQN8S7kIwc
AU3i01ZiVCV7n6x6dqHjqw08al4L8Q+Ffi1oNuTH51ldiGY7eCvnp5iSMO4wCKuab8b/AAr5ktn4
sjf4f3Vqpe4TxayWtkmDyTO5CHk8HPevxub9m/8A4KMfBf4d6x4A+Et58XYovDXh3w/bWY8ESeHY
bG5nkZf7XnhRo42+0KA75zlmPfNdfH8Jf22L/wCEH7ddt+0rf/Ezx5o1t4VvLPwnoHjjSNC1ix1J
Et9yX8Num4faAA5ZWOAeQMgUlilHUXsH1P2utPFPhjU4bi50rxHoOpQwIJJJNMvIrry1K7gzBGO0
FfmBPbmvKPEXxesU1M+H/B+iar4w8RMeIrVlS0Xnq7DOB161/NR+xP8Asi/tbv4N+Hfjj4c+DfjL
8OPAvxB8SWD6nd+D73TLJr/S7PRBEJrm2uNzNE92mApABVmyCCK+qvCPhH/grf4M074WWcNn8X76
/uZtS1DxFoEttottb2M6qyQwfabVRHcQH/WJFnk4GOlH1y4vYmP/AMFQP2xf2rf2RfEGiat8SfiR
8H/hv8EvG+jXlx4dtNK8K6hrl/eavFIoXRruf7ZFHEHV0YSqowC/HGa9zj/4KV+B/hn+zX8J9d8D
t+zl8Rf2ivEFpHc6/wDDTwB4rVNN0xIYRLeP5+JLh3CZRFKAPKyjOOa29D/Zq+Of7T/7Enxl8N/t
8WY8P+N9N1eTxH4U8bfE5bPboUlpGstvcmIRFbaJZFw0bjDoX6hq/Nr4n/sYfHf9qjXvh7/wUJ+G
v7OvgjxronwE1Kyh8Efs3aFpFj4XXx9axRGKfWLoYiLq9yFuIUkYAxIDtrmlW5jXkP2w8Q/8FSf2
X/C/hv4s6vrmpa3Zaj8EP7EtvE3htI41mtZdXVGto42JAkK7yr4wflPHFQfG/wD4Ki/sxfs/6hpW
jeOZvGCarrXjLSfBFtptjZ273D3WpQRzQSqpk5tws6KX6ivzi+HH/BCPX/ifrfgn4u/tJ6wuk+MP
ihpOpXfxW8C2F7JeWura1I7nSrgoMw5sY55UTZjBCnBPNe8Qf8EbfEOo/F74z/HH4m654a+J/jHV
fB+jeHfC0OsFvslteWMVqH1J4pE8uKYm2H76MbgCQKIYndIzVBLqfUviX/goh4E0r41fGf8AZ60v
w9eWV78L/CF7rS/F3WZ7ez8JxahbxITpnzP5gkTz4SXJwS5AGRX5Ufs6f8FhPht43/a80HWNKh+M
/wC078SvEHw40XQ5fh7+zrozX2m2mredI95JO9xLFFb7WYZmLY2gdcV7H8If2S9S0r9sj9rf4D/t
O/BL4s/GH4dftH2Tv4X16LSlvfA2kaTLCr3YnvFKGKd7lQAjZbCRnHFfQv7HP7Ldt+y5+0h+zDc+
Gfg//wAKp0TXPhneeFdW0nTdJjtYhe2l80kMs7Rr/rHjy3mO25s9azdRvc1jFRd0fujoFxc3miaV
d3lhd6VdXUCSSaZqDI09uzLkxuUJUsM4OCRkdaK16KgoKKKKACiiigAooooAKKKKACiiigAooooA
KKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKAI3AKLnn
HrVJLW2N4lybeA3CKyi42DeATyAeuKKKANA9DUFFFABMiOylkViO7DPrVb7HaKy3C2tsLhgAZwi7
yAemcZoooAuxgfMcVJRRQAUUUUAFUr2GG4jeK4iinikVlaOZQysCCCCD2I4oooAjtLS1sreG2s7a
3tLeJQFt7ZBGijHQAcCtAdB9KKKAMjU9PsNRimstQsrS+s7mNkktLyNZYpFI5VlYEEexqSysbKxt
LOysrO1tLO1RVitLWNY4owF4CqBgY9qKKALo6j61Oecg8g+tFFAFeOOMLkRoDnGcD1pY44zhjGhZ
GJDEDIPqKKKAJ6KKKAP/2Q==

From presnick@qualcomm.com  Fri Feb 10 19:19:49 2012
Return-Path: <presnick@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 DAAF521F85CF for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 19:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.566
X-Spam-Level: 
X-Spam-Status: No, score=-107.566 tagged_above=-999 required=5 tests=[AWL=1.033, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kNtB1azPSMys for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 19:19:49 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id ED03C21F85CE for <ietf@ietf.org>; Fri, 10 Feb 2012 19:19:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1328930388; x=1360466388; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F35DE46.3070100@qualcomm.com>|Date:=20Fr i,=2010=20Feb=202012=2019:19:34=20-0800|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Doug=20Barton=20<dougb@dougbar ton.us>|CC:=20<ietf@ietf.org>|Subject:=20Re:=20Last=20Cal l:=20<draft-weil-shared-transition-space-request-14.txt> =0D=0A=20(IANA=20Reserved=20IPv4=20Prefix=20for=20Shared =20Address=20Space)=20to=20BCP|References:=20<20120130230 332.4239.59749.idtracker@ietfa.amsl.com>=09<4F34BD74.8020 807@dougbarton.us>=20<4F35AB67.9030206@qualcomm.com>=20<4 F35AECF.5080106@dougbarton.us>|In-Reply-To:=20<4F35AECF.5 080106@dougbarton.us>|Content-Type:=20text/plain=3B=20cha rset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=8BXYGBAN8P3xgKfgmZzVv6nugwID0fx7g196yCVECOc=; b=NEqX2b36GH278Pb7LSJsesiHFNqS1IKejXUT82Q/2PwDLzJAST3uoO7H kPmiaG+qP1e9B4zN7D2vA3VWKwkAtGTkE34v2d7PTHQMzKraD92D+qabf G1ltTAeTDlAZVidLKl4rAyUkAbC+1+NmfY9G9FL4NLHQG+Spf2nIL5Hzz c=;
X-IronPort-AV: E=McAfee;i="5400,1158,6616"; a="160034385"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 10 Feb 2012 19:19:48 -0800
X-IronPort-AV: E=Sophos;i="4.73,396,1325491200"; d="scan'208";a="183905845"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Feb 2012 19:19:48 -0800
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 10 Feb 2012 19:19:46 -0800
Message-ID: <4F35DE46.3070100@qualcomm.com>
Date: Fri, 10 Feb 2012 19:19:34 -0800
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>	<4F34BD74.8020807@dougbarton.us> <4F35AB67.9030206@qualcomm.com> <4F35AECF.5080106@dougbarton.us>
In-Reply-To: <4F35AECF.5080106@dougbarton.us>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:19:50 -0000

On 2/10/12 3:57 PM, Doug Barton wrote:

> On 02/10/2012 15:42, Pete Resnick wrote:
>    
>
>> I expect there will be clarifications as per the earlier messages in
>> this thread: This is *not* to be used as additional 1918 space.
>>      
> The following is not meant to be a snark

Not taken as such.

> ...I think it's a huge problem
> that you think *saying* "Don't use this as 1918 space" is going to make
> any difference at all.
>    

Neither the text of the current draft nor the proposed text that Brian 
and I seem to like says "Don't use this as 1918 space", nor do I think 
saying so would be a good idea or make any difference. I apologize that 
I was not clear when I said that it "is *not* to be used as 1918 space". 
What I meant was that the document should be clear that this so-called 
"Shared Address Space" has limitations and can't be used in 
circumstances where 1918 addresses can be used. Now, I am under no 
delusions that some equipment won't *try* to use this new space in ways 
that will cause problems (any more than I think that people won't use 
port numbers for non-registered uses, or won't use bogus SMTP protocol 
return codes, etc.). But like those situations, folks who want to use 
this new address space *don't care* if other people do stupid things 
with it; they're making their own beds and they can lie in them. 
Remember, the whole purpose of using new address space is that the 1918 
space has specific semantics that folks have already implemented and 
deployed in equipment *in compliance with the spec* in that they don't 
NAT what they consider an "outside" address. If people with current 
equipment call and complain when a CGN uses 1918 space and screws up 
their equipment, they've got a legitimate beef. But if new folks start 
using Shared Address Space without NATing it properly, they've only got 
themselves to blame.

The new and suggested text makes this all clear: You can safely use this 
non-globally-routeable Shared Address Space so long as you NAT it on 
both ends. If you don't, you're going to have routing problems. You want 
routing problems? Have at it. I don't care. Like any good IETF spec, 
we're just telling you what the rest of us intend to do.

If the text is not clear, please help.

>>> Given that previous requests
>>> for new 1918 space have been (rightly) denied, I think this document
>>> should describe why this request is better/more important than previous
>>> requests, and what the bar will be for future requests for new 1918
>>> space.
>>>
>>>        
>> I hope it does,
>>      
> For my money, it does not.
>    

Again, text welcome.

>>     Shared Address Space is similar to [RFC1918] private address space in
>>     that it is not global routeable address space and can be used by
>>     multiple pieces of equipment. However, Shared Address Space has
>>     limitations in its use that the current [RFC1918] private address
>>     space does not have. In particular, Shared Address Space can only be
>>     used on routing equipment that is able to do address translation
>>     across router interfaces when the addresses are identical on two
>>     different interfaces.
>>      
> So if we're saying the same thing about CPEs capable of doing CGN
> needing to understand the same block(s) on the inside and outside, why
> is the new block necessary?
>    

I believe this has been said multiple times before (and is not the 
subject of this Last Call, AFAICT), but: The new block is necessary 
because current equipment, which will be connected to CGNs (or any other 
kinds of devices that use this new space), and which conforms to a 
reasonable interpretation of 1918, is not able to understand the same 
block on the inside and the outside, and therefore will not be able to 
route through CGNs (or other such new equipment) if they used 1918 
space. Again, if the current text is not clear on this point, please 
identify where clarification is needed. (If you disagree with my 
assessment, let's please take that conversation offlist and we can 
figure out where the disagreement is and maybe bring our collective 
wisdom back to the list. And that invitation is to anyone who feels that 
they disagree with the above reasoning. You have my email address.)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From presnick@qualcomm.com  Fri Feb 10 19:37:31 2012
Return-Path: <presnick@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 54E2621F846B for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 19:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CbMHSlrPefA for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 19:37:30 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8A421F8440 for <ietf@ietf.org>; Fri, 10 Feb 2012 19:37:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1328931450; x=1360467450; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F35E26A.1050203@qualcomm.com>|Date:=20Fr i,=2010=20Feb=202012=2021:37:14=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Masataka=20Ohta=20<mohta@necom 830.hpcl.titech.ac.jp>|CC:=20<ietf@ietf.org>|Subject:=20R e:=20Last=20Call:=20<draft-weil-shared-transition-space-r equest-14.txt>=0D=0A=20(IANA=20Reserved=20IPv4=20Prefix =20for=20Shared=20Address=20Space)=20to=20BCP|References: =20<20120131174018.0032318C0DD@mercury.lcs.mit.edu>=09<DC C302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp. twcable.com>=09<4F283D7F.2040207@qualcomm.com>=20<4F35B86 9.20106@necom830.hpcl.titech.ac.jp>|In-Reply-To:=20<4F35B 869.20106@necom830.hpcl.titech.ac.jp>|Content-Type:=20tex t/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=Ul+H4iqg9OxYgMUFn5qv2QDKI5vC+QUi2EnuCrNJY7Q=; b=axR58+a+413gDurUkEelKuFYZsXDq8WNvrCX7vIAlwr8V9FjlZE/OGpo qGYkvVmNUx0ockwrA0krSqWEHqSeCtGIEtEx24aNSOAUkx5uZKcOyZy4n uBtVn9PPtzu2p1tpz0hAev6n/12oJiAOjzhW/3t2Hghuhie3qBqIM7KBS w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6616"; a="162342569"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 10 Feb 2012 19:37:30 -0800
X-IronPort-AV: E=Sophos;i="4.73,399,1325491200"; d="scan'208";a="193878002"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Feb 2012 19:37:30 -0800
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 10 Feb 2012 19:37:28 -0800
Message-ID: <4F35E26A.1050203@qualcomm.com>
Date: Fri, 10 Feb 2012 21:37:14 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120131174018.0032318C0DD@mercury.lcs.mit.edu>	<DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp.twcable.com>	<4F283D7F.2040207@qualcomm.com> <4F35B869.20106@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4F35B869.20106@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:37:31 -0000

On 2/10/12 6:38 PM, Masataka Ohta wrote:
> Pete Resnick wrote:
>
>    
>> and can be used by other
>> people who build sane equipment that understands "shared" addresses can
>> appear on two different interfaces.
>>      
> With so complicated functionality of NAT today, the only
> practical approach to build such equipment is to make it
> a double NAT

Correct. That's what a CGN is, and that is what other equipment of this 
sort would be.

> as:
>
>                            +-----+   +-----+
> 	(a private space)-| NAT |---| NAT |-(same private space)
>                            +-----+   +-----+
>
> the only problem is that we need another private address
> space used only between element NATs within the double NAT.
>
> Can IETF allocate such address?
>    

That's what this document is doing: Allocating address space to go 
between 2 NATs.

Maybe I don't understand your question?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From dougb@dougbarton.us  Fri Feb 10 19:51:44 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7AB21F85A3 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 19:51:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.567
X-Spam-Level: 
X-Spam-Status: No, score=-4.567 tagged_above=-999 required=5 tests=[AWL=1.032,  BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wb6daSJr9Vu4 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 19:51:43 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6715B21F85A1 for <ietf@ietf.org>; Fri, 10 Feb 2012 19:51:42 -0800 (PST)
Received: (qmail 2458 invoked by uid 399); 11 Feb 2012 03:51:35 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 11 Feb 2012 03:51:35 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F35E5C6.20709@dougbarton.us>
Date: Fri, 10 Feb 2012 19:51:34 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>	<4F34BD74.8020807@dougbarton.us> <4F35AB67.9030206@qualcomm.com> <4F35AECF.5080106@dougbarton.us> <4F35DE46.3070100@qualcomm.com>
In-Reply-To: <4F35DE46.3070100@qualcomm.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:51:44 -0000

Thanks for your response, mine is below, with snipping.

On 02/10/2012 19:19, Pete Resnick wrote:
> On 2/10/12 3:57 PM, Doug Barton wrote:
> 
>> On 02/10/2012 15:42, Pete Resnick wrote:
>>   
>>> I expect there will be clarifications as per the earlier messages in
>>> this thread: This is *not* to be used as additional 1918 space.
>>>      
>> The following is not meant to be a snark
> 
> Not taken as such.
> 
>> ...I think it's a huge problem
>> that you think *saying* "Don't use this as 1918 space" is going to make
>> any difference at all.
>>    
> 
> Neither the text of the current draft nor the proposed text that Brian
> and I seem to like says "Don't use this as 1918 space", nor do I think
> saying so would be a good idea or make any difference. I apologize that
> I was not clear when I said that it "is *not* to be used as 1918 space".
> What I meant was that the document should be clear that this so-called
> "Shared Address Space" has limitations and can't be used in
> circumstances where 1918 addresses can be used.

I'm sorry, I was trying to be concise in order to not re-open the debate
on the topic of "should," but your response indicates that you're not
seeing my point.

The premise of this draft is that a new block is necessary because the
same prefixes can't be used in the customer network and the CGN layer.
So, let's allocate a new block to use *only* in the CGN layer. That way
it can never conflict.

My point is that no matter how loudly you say, "Don't use this as 1918
space!" some users will do it anyway. There have already been several
requests for more IPv4 1918 space because a non-zero number of end user
networks have run out. So we know that people *will* use this new block
internally. Therefore we can be fairly certain that at some point there
will be a conflict. That means that there is no reason to allocate this
new block.

> But if new folks start
> using Shared Address Space without NATing it properly, they've only got
> themselves to blame.

That's interesting ... so you're saying that the people who created the
problem should be responsible for dealing with their own mess? :) More
seriously, you seem to be saying that because the draft says "Don't do
it" it's Ok for us to do the allocation because if someone does screw up
it's not our fault because we told them not to do it. My point is that
because we can see the trap, we shouldn't walk right into it with a
smile on our face.

> If the text is not clear, please help.

I don't think any amount of text-twiddling can help, since I feel that
this is a bad idea from the ground up.

> I believe this has been said multiple times before (and is not the
> subject of this Last Call, AFAICT), but: The new block is necessary
> because current equipment, which will be connected to CGNs (or any other
> kinds of devices that use this new space), and which conforms to a
> reasonable interpretation of 1918, is not able to understand the same
> block on the inside and the outside, and therefore will not be able to
> route through CGNs (or other such new equipment) if they used 1918
> space.

Yes, that's been *said* multiple times, but it hasn't been backed up
with solid data. OTOH, numerous people (many of whom are in a much
better position to know than I am) have pointed out that the
overwhelming majority of consumer CPE devices use one of 192.168.[01] as
their internal networks. That number is likely to be in the 80% range,
if not much higher. Therefore it's very likely that most of this problem
is solved already if the ISPs simply stay away from those 2 ranges.

What I, and others, have said repeatedly now is that given how easy most
of this problem is to solve, the people who have a fiduciary interest in
solving the rest of it should do so, without asking the rest of the
Internet to subsidize their (arguably flawed) business model.

Or put more simply, if the problem is that CPEs don't know how to deal
with the same block on the inside and outside, there are (at least) 2
ways for the ISPs to solve that which do not involve allocating a new
block.

> Again, if the current text is not clear on this point, please
> identify where clarification is needed. (If you disagree with my
> assessment, let's please take that conversation offlist and we can
> figure out where the disagreement is and maybe bring our collective
> wisdom back to the list. 

I appreciate the invitation, but I don't know how much more I can bring
to the topic that I haven't already.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From jnc@mercury.lcs.mit.edu  Fri Feb 10 20:04:09 2012
Return-Path: <jnc@mercury.lcs.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 8C4F721F85B5 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 20:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=0.450,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V39kuY6Rsk9f for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 20:04:08 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 450B321F8592 for <ietf@ietf.org>; Fri, 10 Feb 2012 20:04:08 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 852BD18C156; Fri, 10 Feb 2012 23:04:07 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120211040407.852BD18C156@mercury.lcs.mit.edu>
Date: Fri, 10 Feb 2012 23:04:07 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:04:09 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > My point is that no matter how loudly you say, "Don't use this as
    > 1918 space!" some users will do it anyway.

And if they do, any problem that results is _their_ problem.

    > That means that there is no reason to allocate this new block.

No.

If people are using thing X in way A, _which is allowed by the definition of
X_, then it's really rude/unfair for a responsible standards body to turn
around and say 'ooops, now you can't use thing X in way A'.

If, on the other hand, the standards body then says 'here's a new thing Y;
don't use thing Y in way A', and people go ahead and use thing Y in way A,
then the standards body can reasonably sit back and laugh at them and blow
a raspberry at them when they complain.

	Noel

From dougb@dougbarton.us  Fri Feb 10 20:15:16 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828CF21E8025 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 20:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.616
X-Spam-Level: 
X-Spam-Status: No, score=-3.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlnObV7PMM9S for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 20:15:15 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED3B21E8020 for <ietf@ietf.org>; Fri, 10 Feb 2012 20:15:15 -0800 (PST)
Received: (qmail 12703 invoked by uid 399); 11 Feb 2012 04:15:14 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 11 Feb 2012 04:15:14 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F35EB51.2080208@dougbarton.us>
Date: Fri, 10 Feb 2012 20:15:13 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120211040407.852BD18C156@mercury.lcs.mit.edu>
In-Reply-To: <20120211040407.852BD18C156@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:15:16 -0000

On 02/10/2012 20:04, Noel Chiappa wrote:
>     > From: Doug Barton <dougb@dougbarton.us>
> 
>     > My point is that no matter how loudly you say, "Don't use this as
>     > 1918 space!" some users will do it anyway.
> 
> And if they do, any problem that results is _their_ problem.

You snipped the bit of the my post that you're responding to where I
specifically disallowed this as a reasonable argument.

>     > That means that there is no reason to allocate this new block.
> 
> No.

Let me boil it down even more for you. The new block's purpose is to
make collisions impossible. It cannot fulfill that purpose. So it
shouldn't be allocated.

> If people are using thing X in way A, _which is allowed by the definition of
> X_, then it's really rude/unfair for a responsible standards body to turn
> around and say 'ooops, now you can't use thing X in way A'.
> 
> If, on the other hand, the standards body then says 'here's a new thing Y;
> don't use thing Y in way A', and people go ahead and use thing Y in way A,
> then the standards body can reasonably sit back and laugh at them and blow
> a raspberry at them when they complain.

Setting aside the fact that what you're suggesting is a silly and
childish way for any human to act (even taking hyperbole into account),
it's a very irresponsible way for an SDO to conduct themselves. And
that's assuming that this action doesn't have a cost, whereas the truth
is that it has several, both direct and indirect.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From jnc@mercury.lcs.mit.edu  Fri Feb 10 20:44:43 2012
Return-Path: <jnc@mercury.lcs.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 AF2D421F8551 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 20:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.239
X-Spam-Level: 
X-Spam-Status: No, score=-6.239 tagged_above=-999 required=5 tests=[AWL=0.360,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OKPP639mqANr for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 20:44:43 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1126C21F8550 for <ietf@ietf.org>; Fri, 10 Feb 2012 20:44:42 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7779C18C158; Fri, 10 Feb 2012 23:44:42 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120211044442.7779C18C158@mercury.lcs.mit.edu>
Date: Fri, 10 Feb 2012 23:44:42 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:44:43 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > You snipped the bit of the my post that you're responding to where I
    > specifically disallowed this as a reasonable argument.

What an easy way to win a debate: 'I hereby disallow the following
counter-arguments {A, B, C}, and since you have no other
counter-arguments, I win.'

Just because you don't think much of it, doesn't mean the rest of us have
to agree with you on that.


    > The new block's purpose is to make collisions impossible.

Ah, no.

If you were to say 'to make collisions very unlikely if it is used in the
way it is specified', then I could agree with that. But to take a
straw-man absolutist position like "impossible", and then knock it down
with great pomp:

    > It cannot fulfill that purpose.

is not exactly a plausible argument. Outlawing cell-phone use while driving
may make accidents caused by cell-phone usage less likely, but it can't make
them impossible. Only physics (and math) make things _absolutely_ impossible


    > it's a very irresponsible way for an SDO to conduct themselves.

What, to say 'if you use this in a way that we specifically direct it not
be used, any problems are your fault'?

That's odd, because my lawnmower says much the same thing: 'Don't use this
as a hedge-trimmer. If you do, and cut off your arm, don't even bother
thinking of suing us, because we warned you not to.' (OK, so I translated
the legalese into something more amusing, but the basic message is exactly
that.)


    > And that's assuming that this action doesn't have a cost, whereas
    > the truth is that it has several, both direct and indirect.

And that would be...? How exactly does simply allocating a chunk of
address space - something the Internet engineering community does every
day - for a specific purpose "have a cost ... both direct and indirect"?

If you're actually thinking of 'deploying CGNAT' in the text above, this
discussion is not about that. That's going to happen no matter what the
IETF says/does. (Just like all those other NAT boxes the IETF huffed and
puffed until it turned blue in the face about.)

This is only about allocating a chunk of address space.

	Noel

From dougb@dougbarton.us  Fri Feb 10 21:27:24 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBAFD21F84A3 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 21:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.615
X-Spam-Level: 
X-Spam-Status: No, score=-3.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5VdsaoX139K for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 21:27:24 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7B50021F845E for <ietf@ietf.org>; Fri, 10 Feb 2012 21:27:23 -0800 (PST)
Received: (qmail 25821 invoked by uid 399); 11 Feb 2012 05:27:18 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 11 Feb 2012 05:27:18 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F35FC35.4010103@dougbarton.us>
Date: Fri, 10 Feb 2012 21:27:17 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu>
In-Reply-To: <20120211044442.7779C18C158@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 05:27:25 -0000

On 02/10/2012 20:44, Noel Chiappa wrote:
>     > From: Doug Barton <dougb@dougbarton.us>
> 
>     > You snipped the bit of the my post that you're responding to where I
>     > specifically disallowed this as a reasonable argument.
> 
> What an easy way to win a debate: 'I hereby disallow the following
> counter-arguments {A, B, C}, and since you have no other
> counter-arguments, I win.'
> 
> Just because you don't think much of it, doesn't mean the rest of us have
> to agree with you on that.

I understand that. Do you understand that I understand what you're
saying, and I don't agree with you?

> 
>     > The new block's purpose is to make collisions impossible.
> 
> Ah, no.
> 
> If you were to say 'to make collisions very unlikely if it is used in the
> way it is specified', then I could agree with that.

Ok, let's go with that. We already have a way to make collisions "very
unlikely," don't use either of 192.168.[01]. Fortunately this method
doesn't require allocation of a new block.

So now what we're talking about is how much we're willing to pay to make
the collisions how much more unlikely?

> But to take a
> straw-man absolutist position like "impossible", and then knock it down
> with great pomp:
> 
>     > It cannot fulfill that purpose.

I was using shorthand (or argumentum ad absurdum if you prefer) to point
out that given the fact that this new block can't fix the whole problem,
and also given the fact that there are already solutions available that
fix most of the problem for free, allocating the new block is a bad idea.

>     > it's a very irresponsible way for an SDO to conduct themselves.
> 
> What, to say 'if you use this in a way that we specifically direct it not
> be used, any problems are your fault'?

Again, you snipped the bit where I answered this. Go back and re-read my
previous post if you're confused.

>     > And that's assuming that this action doesn't have a cost, whereas
>     > the truth is that it has several, both direct and indirect.
> 
> And that would be...? How exactly does simply allocating a chunk of
> address space - something the Internet engineering community does every
> day - for a specific purpose "have a cost ... both direct and indirect"?

Again, I'm really trying not to dive back into the "should we" question,
but just as an example, there are 4,096 /22s in a /10. That's 4k new
SMBs that cannot get IPv4 space if this block is allocated.

If you want more, go look at the archives.

> If you're actually thinking of 'deploying CGNAT' in the text above, this
> discussion is not about that. That's going to happen no matter what the
> IETF says/does.

Yep, I get that.

> (Just like all those other NAT boxes the IETF huffed and
> puffed until it turned blue in the face about.)

FWIW I always said that the IETF sticking its collective fingers in its
ears and singing "la la la la la" instead of acknowledging the reality
of NAT and trying to figure out how to do it right was a big mistake.

> This is only about allocating a chunk of address space.

I wish that were true. :)


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From mohta@necom830.hpcl.titech.ac.jp  Fri Feb 10 23:35:57 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 025F721F85C5 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 23:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wWusSCU87xD for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2012 23:35:56 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 97EFD21F85A0 for <ietf@ietf.org>; Fri, 10 Feb 2012 23:35:50 -0800 (PST)
Received: (qmail 9977 invoked from network); 11 Feb 2012 07:49:30 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 11 Feb 2012 07:49:30 -0000
Message-ID: <4F361A3D.3080601@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Feb 2012 16:35:25 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120131174018.0032318C0DD@mercury.lcs.mit.edu>	<DCC302FAA9FE5F4BBA4DCAD4656937791738DC11F6@PRVPEXVS03.corp.twcable.com>	<4F283D7F.2040207@qualcomm.com> <4F35B869.20106@necom830.hpcl.titech.ac.jp> <4F35E26A.1050203@qualcomm.com>
In-Reply-To: <4F35E26A.1050203@qualcomm.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:35:57 -0000

Pete Resnick wrote:

>>> and can be used by other
>>> people who build sane equipment that understands "shared" addresses can
>>> appear on two different interfaces.
>> With so complicated functionality of NAT today, the only
>> practical approach to build such equipment is to make it
>> a double NAT
> 
> Correct.

Note that the double NAT, here, is AN equipment.

>> Can IETF allocate such address?
> 
> That's what this document is doing: Allocating address space to go 
> between 2 NATs.
> 
> Maybe I don't understand your question?

My point is that those who are arguing against the proposed
allocation because of the capability of a double NAT
equipment should argue for allocation of another space
to enable development of the double NAT equipment.

						Masataka Ohta

From mansaxel@besserwisser.org  Sat Feb 11 00:16:04 2012
Return-Path: <mansaxel@besserwisser.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 D881221F85C9 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 00:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zG48lPZrWjzf for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 00:16:04 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 7D93121F85C6 for <ietf@ietf.org>; Sat, 11 Feb 2012 00:15:51 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 2FF079E96; Sat, 11 Feb 2012 09:15:48 +0100 (CET)
Date: Sat, 11 Feb 2012 09:15:48 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120211081543.GH27669@besserwisser.org>
References: <20120211031325.EAAC418C146@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120211031325.EAAC418C146@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 08:16:05 -0000

On Fri, Feb 10, 2012 at 10:13:25PM -0500, Noel Chiappa wrote:
>     > I still strongly oppose the publication of this draft. In any form
>     > except a complete rewrite telling providers to use RFC1918 and be done
>     > with it.
> 
> If you have any good technical reasons for finding this a bad idea _other_
> than the supposed negative effects on IPv6 deployment, it would be useful to
> hear them. Are there any?

There is no case for it. Any space so allocated will, by tearing down
the last community restrains on address reuse, become an extension to
RFC1918. There are legitimate uses for unique v4 space as documented in
RIR policy and v4 sunset procedures. Let the /10 go there instead.


-- 
Måns

From mansaxel@besserwisser.org  Sat Feb 11 00:32:06 2012
Return-Path: <mansaxel@besserwisser.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 A8E9C21F85D3 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 00:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hcmm6ttWim-v for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 00:32:06 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 0656921F85C0 for <ietf@ietf.org>; Sat, 11 Feb 2012 00:32:05 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 6F8579E97; Sat, 11 Feb 2012 09:32:04 +0100 (CET)
Date: Sat, 11 Feb 2012 09:32:04 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: ietf@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120211083156.GI27669@besserwisser.org>
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120211044442.7779C18C158@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 08:32:06 -0000

On Fri, Feb 10, 2012 at 11:44:42PM -0500, Noel Chiappa wrote:
 
> This is only about allocating a chunk of address space.

For which there is better use than prolonging bad technical solutions. 

Address translation has set the state of consumer computing back severely.
It might be all nice and proper according to those who desire to keep the
power of owning a TV transmitter, a printing press or a transaction broker
service.

Do keep in mind that the real driver in IP technology is the ability
for end-nodes to communicate in a manner they chose without prior
coordination with some kind of protocol gateway. NAT and more so CGN
explicitly disables this key feature.

And this is not what the IETF should be doing. The IETF should seek
to maximise the technical capabilities of the Internet protocol
suite so that it may continue to enable new uses of the key feature,
ie. end-node reachability.

Allocating CGN-blessing address space is a clear violation of this.

-- 
Måns

From rogerj@gmail.com  Sat Feb 11 03:31:25 2012
Return-Path: <rogerj@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 B525621F8551 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 03:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fU-MqAplPyVx for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 03:31:24 -0800 (PST)
Received: from mail-lpp01m020-f172.google.com (mail-lpp01m020-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3C0DD21F8550 for <ietf@ietf.org>; Sat, 11 Feb 2012 03:31:24 -0800 (PST)
Received: by lbbgk8 with SMTP id gk8so2039935lbb.31 for <ietf@ietf.org>; Sat, 11 Feb 2012 03:31:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Ohvh7WRzPC7lb9g8HoCg9YWFKzzrsSzWVhTPHuLKDww=; b=EPOcpGQ9FS3ciG2WAfUGbwsz421e98dH6QgHr6pWam6M/Zsk+kX3Kn3BT1ox3x6f/a raAGBswIgwS9138K8MSmUjtWGE44fJbLg/YM8rH8rLqkwKpzv4M5uVGNzf/uzdj4Wf/s sMmIkPIPggdtN1Z201Os99DKdLTvdS8lILYVQ=
MIME-Version: 1.0
Received: by 10.112.85.233 with SMTP id k9mr3307573lbz.56.1328959883171; Sat, 11 Feb 2012 03:31:23 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Sat, 11 Feb 2012 03:31:22 -0800 (PST)
In-Reply-To: <20120211083156.GI27669@besserwisser.org>
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <20120211083156.GI27669@besserwisser.org>
Date: Sat, 11 Feb 2012 12:31:22 +0100
Message-ID: <CAKFn1SGmpQ1fjxGr6pcFTAzjshg7q6L81azMxNjK1oub9x0qRw@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 11:31:25 -0000

On Sat, Feb 11, 2012 at 9:32 AM, M=E5ns Nilsson <mansaxel@besserwisser.org>=
 wrote:
> On Fri, Feb 10, 2012 at 11:44:42PM -0500, Noel Chiappa wrote:
>
>> This is only about allocating a chunk of address space.
>
> For which there is better use than prolonging bad technical solutions.
>
> Address translation has set the state of consumer computing back severely=
.
> It might be all nice and proper according to those who desire to keep the
> power of owning a TV transmitter, a printing press or a transaction broke=
r
> service.
>
> Do keep in mind that the real driver in IP technology is the ability
> for end-nodes to communicate in a manner they chose without prior
> coordination with some kind of protocol gateway. NAT and more so CGN
> explicitly disables this key feature.
>
> And this is not what the IETF should be doing. The IETF should seek
> to maximise the technical capabilities of the Internet protocol
> suite so that it may continue to enable new uses of the key feature,
> ie. end-node reachability.
>
> Allocating CGN-blessing address space is a clear violation of this.

Is that true?
And if so, why and how can it be formulated or find support it earlier work=
?
And if it is not true. Why and where do you find support for that view?


I ask because you might touch something quite fundamental there... can
IETF support something that will break/limit reachability on Internet.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From mansaxel@besserwisser.org  Sat Feb 11 06:15:44 2012
Return-Path: <mansaxel@besserwisser.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 88CFD21F8547 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 06:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRVpW-xIQzT8 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 06:15:44 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 5340921F84A2 for <ietf@ietf.org>; Sat, 11 Feb 2012 06:15:41 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 3E9BE9E96; Sat, 11 Feb 2012 15:15:39 +0100 (CET)
Date: Sat, 11 Feb 2012 15:15:39 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: ietf@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120211141535.GJ27669@besserwisser.org>
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <20120211083156.GI27669@besserwisser.org> <CAKFn1SGmpQ1fjxGr6pcFTAzjshg7q6L81azMxNjK1oub9x0qRw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKFn1SGmpQ1fjxGr6pcFTAzjshg7q6L81azMxNjK1oub9x0qRw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:15:44 -0000

On Sat, Feb 11, 2012 at 12:31:22PM +0100, Roger Jørgensen wrote:
> On Sat, Feb 11, 2012 at 9:32 AM, Måns Nilsson <mansaxel@besserwisser.org> wrote:
> > On Fri, Feb 10, 2012 at 11:44:42PM -0500, Noel Chiappa wrote:
> >
> >> This is only about allocating a chunk of address space.
> >
> > For which there is better use than prolonging bad technical solutions.
> >
> > Address translation has set the state of consumer computing back severely.
> > It might be all nice and proper according to those who desire to keep the
> > power of owning a TV transmitter, a printing press or a transaction broker
> > service.
> >
> > Do keep in mind that the real driver in IP technology is the ability
> > for end-nodes to communicate in a manner they chose without prior
> > coordination with some kind of protocol gateway. NAT and more so CGN
> > explicitly disables this key feature.
> >
> > And this is not what the IETF should be doing. The IETF should seek
> > to maximise the technical capabilities of the Internet protocol
> > suite so that it may continue to enable new uses of the key feature,
> > ie. end-node reachability.
> >
> > Allocating CGN-blessing address space is a clear violation of this.
> 
> Is that true?
> And if so, why and how can it be formulated or find support it earlier work?
> And if it is not true. Why and where do you find support for that view?
> 
> I ask because you might touch something quite fundamental there... can
> IETF support something that will break/limit reachability on Internet.

IMNSHO, the answer should only be NO to that question.  Where can I search
support for this view? I believe, for starters, that:

a/ The original IPv4 Internet was designed with a flat reachability
   model, as seen from the host IP-stack. (routers are a different thing,
   but indeed the flatness repeats itself, technically, in the DFZ.)

b/ When the Internet faced an address shortage there were two solutions
   put forward; one being CIDR and the other being IPv6 (nee IPng,
   IIRC). While it is true that there was work codified in RFC 1631 etc that
   makes the IETF one of the culprits behind NAT, it is also written that

   The short-term
   solution is CIDR (Classless InterDomain Routing) [2]. The long-term
   solutions consist of various proposals for new internet protocols
   with larger addresses.

   Until the long-term solutions are ready an easy way to hold down the
   demand for IP addresses is through address reuse. 

	....

   This solution has the disadvantage of taking away the end-to-end
   significance of an IP address, and making up for it with increased
   state in the network.

		(RFC 1631, p1)

   We here clearly see that the authors tasked with describing address
   translation were fully aware that they were breaking E2E, and that
   they saw address translation as an intermediate measure to be retired
   as soon as suitable long-term measures were available.

   Reading further in the sequence of IETF documents describing NAT,
   we discover something of a more defaitist position in 3022. The
   discussion on disadvantages is still there, but there is less talk
   of replacing NAT with v6. Apparently the massive success of broadband
   routers was showing.

So. With this little historical research made, I think that we can see
a couple of  things:

1. The IETF knew the drawbacks. 

2. NAT was only a desperate measure. 

3. NAT was to be retired when IPv6 was ready. 

4. The IETF failed to predict the massive market penetration of broadband
   routers and similar solutions.

The key question then becomes, are  the market lemmings throwing
themselves over the NAT cliff reason enough to give up sound engineering
principles? I think that numbering critical devices in a sunset phase
(where IPv4 is, resource-wise) uniquely is a more prudent use for address
space than giving it away to people who've made bad business decisions
(which doing any network business without v6 firmly on the 1-year roadmap
is, post say 2006). Especially since it will be used to keep running a
system that the IETF has known for 18 years to be severely deficient.

-- 
Måns

From john-ietf@jck.com  Sat Feb 11 07:34:44 2012
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 6395B21F8503 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 07:34:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level: 
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CTL5AXtVjQ3W for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 07:34:43 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9E58B21F84FB for <ietf@ietf.org>; Sat, 11 Feb 2012 07:34:30 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1RwEuH-0005CS-Ju; Sat, 11 Feb 2012 10:30:33 -0500
Date: Sat, 11 Feb 2012 10:34:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Arturo Servin <arturo.servin@gmail.com>, Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <A697AE602B337417D34B37FF@PST.JCK.COM>
In-Reply-To: <CE91A108-BED5-4BBF-AF4E-D341C6D9769B@gmail.com>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com> <CE91A108-BED5-4BBF-AF4E-D341C6D9769B@gmail.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
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:34:44 -0000

--On Saturday, February 11, 2012 11:00 -0200 Arturo Servin
<arturo.servin@gmail.com> wrote:

> 
> On 10 Feb 2012, at 22:12, Chris Grundemann wrote:
> 
>> Are you volunteering to buy everyone on earth a new CPE? If
>> not, who do you suggest will?
> 
> 	I suggest the ISPs, they are charging for the service, right?

One additional observation about this particular line of
argument.

It seems to me that, to the extent to which this allocation idea
is part of a legitimate IPv6 transition strategy, we should be
listening carefully and with sympathy.  We can still debate
whether it is the best strategy, whether there are better ways
to do the same thing, etc., but I hope there is no one who will
argue against having strategies for moving forward other than
hoping that the world ends before the last IPv4 allocation is
given out by the RIRs.

But, as soon as one suggests that the alternative to this space
request is "volunteering to buy everyone on earth a new CPE", we
aren't talking about transition strategies any more.  If we
assume that end system networks will eventually either be
running IPv6 or that the IPv6-IPv4 transition will occur at
those boundaries, then that CPE equipment will need to be
replaced because most of it doesn't support IPv6.   I suppose an
ISP could be stupid enough to buy CPE now that supports "same
address range inside and outside" but does not support IPv6, but
such an ISP would be much too stupid to survive (with or without
help from us).  

So the CPE will need to be upgraded.  There are potentially
interesting economic discussions about capitalization,
amortization, and deployment rates, but let's not pretend that
this allocation for CGN use is the alternate to replacing CPE --
unless it is really a plan for IPv4 Forever based on layers and
layers of address translation (and this is where I incorporate
my snarky comment about X.75 gateways by reference -- a comment,
I'm pleased to report, a few people have responded to with tales
of painful experiences in past lives).

>...
>> if they were, we could just sign
>> everyone up for IPv6 capable CPE and skip the whole debate...
>> ;)

So, Chris, if you expect this allocation will avoid the costs of
signing everyone up for IPv6-capable CPE, what is your
transition plan?  Or are you advocating an IPv4-forever model?
If the latter, can you explain succinctly to the rest of us how
you expect it to work?

best,
  john




From jnc@mercury.lcs.mit.edu  Sat Feb 11 08:02:39 2012
Return-Path: <jnc@mercury.lcs.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 83F2621F845E for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 08:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RvQVw97GQbS for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 08:02:38 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 96E9321F845A for <ietf@ietf.org>; Sat, 11 Feb 2012 08:02:38 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A388C18C170; Sat, 11 Feb 2012 11:02:37 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120211160237.A388C18C170@mercury.lcs.mit.edu>
Date: Sat, 11 Feb 2012 11:02:37 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:02:39 -0000

    > From: Nilsson <mansaxel@besserwisser.org>

    > Address translation has set the state of consumer computing back
    > severely.

We basically all know that. I myself am not happy with NAT either - in
fact, back in 1992 (!!) I myself wrote what was perhaps the first
"problems with NAT document". So?

    > Allocating CGN-blessing address space is a clear violation of this.

You seem to be operating under the illusion that the IETF has the power to
actually do something about NAT, and more particularly, CGNAT. This is not
correct. No action by the IETF will have the slightest affect on the
deployment of CGNAT (and probably the amount of CGNAT deployment).

The notion that 'IETF blessing' will make any _real_ difference at all is
complete wrong. The IETF's blessing (or failure to do so), and an
appropriate amount of local currency, will get you a cup of coffee, as
they say...


In reality, the _only_ choice the IETF has is between:

- Deploy CGNAT with messy ad-hoc assigned addresses (squatting, whatever)
- Deploy CGNAT with an assigned address block

Given those two choices, I pick the second.

	Noel

From rdroms.ietf@gmail.com  Sat Feb 11 10:18:12 2012
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 7025221F84D8 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 10:18:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.25
X-Spam-Level: 
X-Spam-Status: No, score=-103.25 tagged_above=-999 required=5 tests=[AWL=0.305, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g3pPwNIExS3F for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 10:18:11 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 97CB521F84D3 for <ietf@ietf.org>; Sat, 11 Feb 2012 10:17:58 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so3506711pbc.31 for <ietf@ietf.org>; Sat, 11 Feb 2012 10:17:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=m0RExqV+4qD211q5V7jMF7la8wM04iRR/ygid5vD/cc=; b=G8lTlxn9k6FObGwSOxEij4RgsmAiQquk9iFjGidR8n5aya8yKCfkXxIboMffI6h/VI /RID6fOqgfXvw0MwZpvWZgyRPxWApFZE3977fPz41ypEfRPjOAgK3xrfibCP7l/QGeC5 opKSh4Ks+kpnJqom8E5468uvR9MYi3+enIdmI=
Received: by 10.68.212.73 with SMTP id ni9mr6775312pbc.56.1328984278438; Sat, 11 Feb 2012 10:17:58 -0800 (PST)
Received: from sjc-vpn6-303.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id g6sm9885720pbq.6.2012.02.11.10.17.55 (version=SSLv3 cipher=OTHER); Sat, 11 Feb 2012 10:17:57 -0800 (PST)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4F35FC35.4010103@dougbarton.us>
Date: Sat, 11 Feb 2012 07:52:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <4F35FC35.4010103@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1251.1)
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:18:12 -0000

On Feb 11, 2012, at 12:27 AM 2/11/12, Doug Barton wrote:

> On 02/10/2012 20:44, Noel Chiappa wrote:
>>> From: Doug Barton <dougb@dougbarton.us>
>>=20
>>> You snipped the bit of the my post that you're responding to where I
>>> specifically disallowed this as a reasonable argument.
>>=20
>> What an easy way to win a debate: 'I hereby disallow the following
>> counter-arguments {A, B, C}, and since you have no other
>> counter-arguments, I win.'
>>=20
>> Just because you don't think much of it, doesn't mean the rest of us =
have
>> to agree with you on that.
>=20
> I understand that. Do you understand that I understand what you're
> saying, and I don't agree with you?
>=20
>>=20
>>> The new block's purpose is to make collisions impossible.
>>=20
>> Ah, no.
>>=20
>> If you were to say 'to make collisions very unlikely if it is used in =
the
>> way it is specified', then I could agree with that.
>=20
> Ok, let's go with that. We already have a way to make collisions "very
> unlikely," don't use either of 192.168.[01]. Fortunately this method
> doesn't require allocation of a new block.

But, what we've been told by operators in the discussion about this =
draft is that "very unlikely" is not "sufficiently unlikely", and that =
no /10 within the set of RFC 1918 addresses makes the probability of a =
collision sufficiently unlikely.  You may disagree with that claim, but =
I think we have to respect it.

> So now what we're talking about is how much we're willing to pay to =
make
> the collisions how much more unlikely?

I would certainly feel more comfortable with better data, but it seems =
highly unlikely that we can generate it.

- Ralph

>=20
>> But to take a
>> straw-man absolutist position like "impossible", and then knock it =
down
>> with great pomp:
>>=20
>>> It cannot fulfill that purpose.
>=20
> I was using shorthand (or argumentum ad absurdum if you prefer) to =
point
> out that given the fact that this new block can't fix the whole =
problem,
> and also given the fact that there are already solutions available =
that
> fix most of the problem for free, allocating the new block is a bad =
idea.
>=20
>>> it's a very irresponsible way for an SDO to conduct themselves.
>>=20
>> What, to say 'if you use this in a way that we specifically direct it =
not
>> be used, any problems are your fault'?
>=20
> Again, you snipped the bit where I answered this. Go back and re-read =
my
> previous post if you're confused.
>=20
>>> And that's assuming that this action doesn't have a cost, whereas
>>> the truth is that it has several, both direct and indirect.
>>=20
>> And that would be...? How exactly does simply allocating a chunk of
>> address space - something the Internet engineering community does =
every
>> day - for a specific purpose "have a cost ... both direct and =
indirect"?
>=20
> Again, I'm really trying not to dive back into the "should we" =
question,
> but just as an example, there are 4,096 /22s in a /10. That's 4k new
> SMBs that cannot get IPv4 space if this block is allocated.
>=20
> If you want more, go look at the archives.
>=20
>> If you're actually thinking of 'deploying CGNAT' in the text above, =
this
>> discussion is not about that. That's going to happen no matter what =
the
>> IETF says/does.
>=20
> Yep, I get that.
>=20
>> (Just like all those other NAT boxes the IETF huffed and
>> puffed until it turned blue in the face about.)
>=20
> FWIW I always said that the IETF sticking its collective fingers in =
its
> ears and singing "la la la la la" instead of acknowledging the reality
> of NAT and trying to figure out how to do it right was a big mistake.
>=20
>> This is only about allocating a chunk of address space.
>=20
> I wish that were true. :)
>=20
>=20
> Doug
>=20
> --=20
>=20
> 	It's always a long day; 86400 doesn't fit into a short.
>=20
> 	Breadth of IT experience, and depth of knowledge in the DNS.
> 	Yours for the right price.  :)  http://SupersetSolutions.com/
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From cgrundemann@gmail.com  Sat Feb 11 11:38:14 2012
Return-Path: <cgrundemann@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 3AD0021F8550 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 11:38:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.687
X-Spam-Level: 
X-Spam-Status: No, score=-3.687 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCKpMvkfe2Fx for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 11:38:13 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1660721F84DE for <ietf@ietf.org>; Sat, 11 Feb 2012 11:38:13 -0800 (PST)
Received: by dakl33 with SMTP id l33so3486988dak.31 for <ietf@ietf.org>; Sat, 11 Feb 2012 11:38:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=d8S5CeWVtR9KOvDu2wQ9ebSC1ti1OPE4pYb7yl7IeQc=; b=Yd26fPT60OwWMtuspx6f+EliM0U9+SPSdoxRbgfcExHGGt9CREStwyNjvfLCHk85F1 X6n6+G0y4b9XHUnSE31599HK1bjlK+GSAQpCJuUSPFH77BfXv3CxewMcc2P9GbNKuDci oXixAo/NWsaLunWAw+7C7GiymVFsQyp8PDNEs=
MIME-Version: 1.0
Received: by 10.68.241.170 with SMTP id wj10mr29670810pbc.42.1328989092439; Sat, 11 Feb 2012 11:38:12 -0800 (PST)
Received: by 10.142.105.13 with HTTP; Sat, 11 Feb 2012 11:38:12 -0800 (PST)
In-Reply-To: <A697AE602B337417D34B37FF@PST.JCK.COM>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com> <CE91A108-BED5-4BBF-AF4E-D341C6D9769B@gmail.com> <A697AE602B337417D34B37FF@PST.JCK.COM>
Date: Sat, 11 Feb 2012 12:38:12 -0700
Message-ID: <CAC1-dt=m6mF6qpa+ShOZh_wUNBP-qgBepsHP2aASZG+1FdkNrg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.net>, Arturo Servin <arturo.servin@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:38:14 -0000

On Sat, Feb 11, 2012 at 08:34, John C Klensin <john-ietf@jck.com> wrote:

> So, Chris, if you expect this allocation will avoid the costs of
> signing everyone up for IPv6-capable CPE, what is your
> transition plan? =A0Or are you advocating an IPv4-forever model?
> If the latter, can you explain succinctly to the rest of us how
> you expect it to work?

You snipped the comment I was replying too, and thus the context of my
statement.

What I was replying to was a statement that we should just give
everyone a CPE that could handle the same space inside and outside. My
response was that if we are to replace CPE it should be with IPv6
capable CPE, _not_ CGN tolerant CPE.

What I did not say was anything about prolonging the life of IPv4. In
fact I have argued against that several times, a few in this very
thread.

Hopefully that clears up your confusion.

Cheers,
~Chris

> best,
> =A0john
>
>
>



--=20
@ChrisGrundemann
http://chrisgrundemann.com

From mohta@necom830.hpcl.titech.ac.jp  Sat Feb 11 15:52:14 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED5821F858F for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 15:52:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.06
X-Spam-Level: 
X-Spam-Status: No, score=0.06 tagged_above=-999 required=5 tests=[AWL=-0.150,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iS+cv8tpVhcL for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 15:52:13 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 62B4521F8572 for <ietf@ietf.org>; Sat, 11 Feb 2012 15:52:12 -0800 (PST)
Received: (qmail 17112 invoked from network); 12 Feb 2012 00:06:14 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 12 Feb 2012 00:06:14 -0000
Message-ID: <4F36FF19.2070000@necom830.hpcl.titech.ac.jp>
Date: Sun, 12 Feb 2012 08:51:53 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org, =?UTF-8?B?TcOlbnMgTmlsc3Nvbg==?= <mansaxel@besserwisser.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <20120211083156.GI27669@besserwisser.org>
In-Reply-To: <20120211083156.GI27669@besserwisser.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:52:14 -0000

Nilsson wrote:

> For which there is better use than prolonging bad technical solutions.

A problem is that IPv6 is a bad technical solution.

For examples, its bloated address space is bad, ND with full
of bloated useless features is bad and multicast PMTUD only
to cause ICMP implosions is bad.

> Address translation has set the state of consumer computing back severely.

No, not at all.

> Do keep in mind that the real driver in IP technology is the ability
> for end-nodes to communicate in a manner they chose without prior
> coordination with some kind of protocol gateway. NAT and more so CGN
> explicitly disables this key feature.

Wrong. Nat can be end to end transparent, if hosts recognize
existence of NAT and cooperate with NAT gateways to reverse
address (and port) translation.

See RFC3102 and draft-ohta-e2e-nat-00.txt. I have confirmed
that PORT command of unmodified ftp client just work.

Though my draft assumes special NAT gateway, I recently
noticed that similar thing is possible with UPnP capable
existing NAT gateways.

> And this is not what the IETF should be doing. The IETF should seek
> to maximise the technical capabilities of the Internet protocol
> suite so that it may continue to enable new uses of the key feature,
> ie. end-node reachability.

Yes. So, let's abandon IPv6, a bad technical solution, and
deploy NAT with UPnP or PCP (if designed properly) capabilities.

					Masataka Ohta

From dougb@dougbarton.us  Sat Feb 11 16:10:42 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF51F21F8597 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 16:10:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.994
X-Spam-Level: 
X-Spam-Status: No, score=-2.994 tagged_above=-999 required=5 tests=[AWL=-0.635, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oi-2qJhTzSw2 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 16:10:37 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9595A21F857D for <ietf@ietf.org>; Sat, 11 Feb 2012 16:10:35 -0800 (PST)
Received: (qmail 18692 invoked by uid 399); 12 Feb 2012 00:10:29 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 12 Feb 2012 00:10:29 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F370374.5030409@dougbarton.us>
Date: Sat, 11 Feb 2012 16:10:28 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <4F35FC35.4010103@dougbarton.us> <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
In-Reply-To: <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:10:42 -0000

On 02/11/2012 04:52, Ralph Droms wrote:
> 
> On Feb 11, 2012, at 12:27 AM 2/11/12, Doug Barton wrote:

>> Ok, let's go with that. We already have a way to make collisions
>> "very unlikely," don't use either of 192.168.[01]. Fortunately this
>> method doesn't require allocation of a new block.
> 
> But, what we've been told by operators in the discussion about this
> draft is that "very unlikely" is not "sufficiently unlikely", and
> that no /10 within the set of RFC 1918 addresses makes the
> probability of a collision sufficiently unlikely.  You may disagree
> with that claim, but I think we have to respect it.

Why do we have to respect it? Completely aside from the issue of
trusting the fox to report on the security conditions of the henhouse,
we haven't been provided any data to support the claim. What they're
saying is, "We don't have data for this, and we won't generate it. But
we want you to trust us anyway that doing this thing that overwhelmingly
benefits us is the right thing to do."

Now on its face that's a bad deal no matter how you look at it. Now add
in the fact that this issue has been created by the same foxes refusing
to invest in IPv6, AND the assertion from people who know better than I
that most of the problem can be dealt with by avoiding 2 1918 /24s, it
just keeps getting worse.

Make no mistake, I understand what they are asking for, and I'm very
confident that I understand why they're asking for it. It makes their
job infinitely easier if they can be given a /10 that, at least in the
short term, they can be close to 100% certain will not be used inside a
customer network. That way they don't have to think hard about their
network design (and don't have to take as many customer service calls),
and they will have N more years to diddle away until customers start
using that block internally. And then the whole thing goes pear-shaped
again.

So no, I don't have to respect what they're telling us.

>> So now what we're talking about is how much we're willing to pay to
>> make the collisions how much more unlikely?
> 
> I would certainly feel more comfortable with better data, but it
> seems highly unlikely that we can generate it.

Generating the data on what CPEs use what blocks by default and how
prevalent each of them are in the market is simply a matter of time and
money. These types of surveys have already been done for DNSSEC, so we
know exactly what it takes to do them. The fact that the same people who
want us to spend valuable public IPv4 addresses so that they can save
time and money with their CGN deployments are also refusing to spend the
time and money necessary to back up their claims should, really, be
making more people angry than it seems already are.

And while I'm at it, John Klensin's post today about the "get everyone a
new CPE" topic was a much more thorough treatment than I'm capable of,
so I'll just add a +1.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From randy@psg.com  Sat Feb 11 16:25:16 2012
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 97EF121F8596 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 16:25:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.527
X-Spam-Level: 
X-Spam-Status: No, score=-2.527 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LhRcquQFhchA for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 16:25:16 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2192821F8593 for <ietf@ietf.org>; Sat, 11 Feb 2012 16:25:16 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RwNFi-000Ert-4D; Sun, 12 Feb 2012 00:25:14 +0000
Date: Sat, 11 Feb 2012 16:25:14 -0800
Message-ID: <m2mx8oq4np.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>	(IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <4F35FC35.4010103@dougbarton.us> <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:25:16 -0000

> But, what we've been told by operators in the discussion about this
                              ^ some
> draft is that "very unlikely" is not "sufficiently unlikely", and that
> no /10 within the set of RFC 1918 addresses makes the probability of a
> collision sufficiently unlikely.  You may disagree with that claim,
> but I think we have to respect it.

aside from inter-operator acquisitions, this space will be used as 1918
and will soon have the same collision properties.

but we have had this discussion many times.  no one is changing anyone's
minds.  the iesg is simply trying to justify a bad position, where no
position is particularly good.  how much email do we all have to read to
paper over the iesg's lack of guts?

randy

From jnc@mercury.lcs.mit.edu  Sat Feb 11 17:39:04 2012
Return-Path: <jnc@mercury.lcs.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 E767721F85A4 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 17:39:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.722
X-Spam-Level: 
X-Spam-Status: No, score=-5.722 tagged_above=-999 required=5 tests=[AWL=-0.363, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diDQ0FNy7oAV for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 17:39:04 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6246521F85A2 for <ietf@ietf.org>; Sat, 11 Feb 2012 17:39:04 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 955FC18C18A; Sat, 11 Feb 2012 20:39:03 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120212013903.955FC18C18A@mercury.lcs.mit.edu>
Date: Sat, 11 Feb 2012 20:39:03 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:39:05 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > We already have a way to make collisions "very unlikely," don't use
    > either of 192.168.[01]. 

I gather that that's not desirable, because otherwise people wouldn't be
asking for another block. Of course it could probably be made to work
somehow - with enough thrust, etc, etc. But that's not the point - engineering
is (or ought to be) all about balancing costs and benefits.

If the people involved were asking for something incredibly
painful/expensive in order to make their lives easier, the answer would
rightly be 'no'. The cost would far outweigh the benefit. But they're not.
All they're asking for is a modest chunk of address space, and the cost of
doing that is not significant - we allocate chunks of space _all the time_.

    >> This is only about allocating a chunk of address space.

    > I wish that were true. :)

But it is. As I said before, the IETF has precisely two choices:

- See CGN deployed using various hacks (e.g. squatting on space)
- See CGN deployed using a block of space allocated for that purpose

Allocate, or don't allocate. That's the only choice.


    > It makes their job infinitely easier if they can be given a /10
    > that, at least in the short term, they can be close to 100% certain
    > will not be used inside a customer network. That way they don't have
    > to think hard about their network design (and don't have to take as
    > many customer service calls)

So, I gather that given the choice above, your choice would be 'I prefer
the ugly solution' - because you want to make their life as miserable as
you can, to punish them for the high crime of deigning to defy your sense
of what's best for the network.

Talk about "a very irresponsible way for an SDO to conduct themselves", to use
your own very apt phrase.

	Noel

From joelja@bogus.com  Sat Feb 11 23:11:44 2012
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 1737821F85D3 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 23:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I-ZcsEjWqFhj for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 23:11:43 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8F2ED21F85D5 for <ietf@ietf.org>; Sat, 11 Feb 2012 23:11:43 -0800 (PST)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q1C7Bcvi037856 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 12 Feb 2012 07:11:39 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F37662A.5020405@bogus.com>
Date: Sat, 11 Feb 2012 23:11:38 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120211044442.7779C18C158@mercury.lcs.mit.edu> <4F35FC35.4010103@dougbarton.us> <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
In-Reply-To: <62FF590A-BC92-46C1-8006-1BAC5F05E7D9@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 12 Feb 2012 07:11:40 +0000 (UTC)
Cc: IETF Discussion <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:11:44 -0000

On 2/11/12 04:52 , Ralph Droms wrote:

> But, what we've been told by operators in the discussion about this
> draft is that "very unlikely" is not "sufficiently unlikely", and
> that no /10 within the set of RFC 1918 addresses makes the
> probability of a collision sufficiently unlikely.  You may disagree
> with that claim, but I think we have to respect it.
> 

Given a provisioning system with two pools  of address for a given set
of customers, it can likely be demonstrated that no deployed consumer
cpe is internally numbered in both of them.

Managing breakage due to an address collision with existing cpe is one
kind of support cost. Managing breakage due to a new formerly
non-private scope address range now being employed is another support cost.

It's entirely possible that reasonable people with experience operating
consumer facing networks can disagree on which cost is more onerous.


From sm@resistor.net  Sun Feb 12 09:25:50 2012
Return-Path: <sm@resistor.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 7C8DF21F877A for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 09:25:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PjBFrqCFpea for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 09:25:48 -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 5255B21F8775 for <ietf@ietf.org>; Sun, 12 Feb 2012 09:25:47 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1CHPa1B001722; Sun, 12 Feb 2012 09:25:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329067545; i=@resistor.net; bh=J7VijTB2RadhiDF9t2Q/8bY42TWLhlyDnO7B0ftUggs=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=s8qkmhTYbcpkBdqN6E74vOIGKIBOkkTJH9+l345+UvRShVS832gPWIjnyHfkoGTrb 1z/21+kokZowbuIZ/BKZLXuXRBWNsvxwPk1sxsvsz/p/t4Bs/LWEhk3AG4GCNi4GoU g0T8KLol/60qr4e5YO9qaL4SvpcvdlBHLfuZFiRg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329067545; i=@resistor.net; bh=J7VijTB2RadhiDF9t2Q/8bY42TWLhlyDnO7B0ftUggs=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=c5vSAiTErYcG6WiiQs0rMLmizc9bBKoqGtzPI/nmOK8E+/uh0yV4CzRSbrNRyj9Hc 3VlP2R7oedmrbWcwJLVvQBu+V8I5IH/iZT90tbFrCkgOa9iW+niFT3fLs9OLJzygQL Mp+01rGKXawAnoT3j99njlyH3pq86zlwWPdNx2tQ=
Message-Id: <6.2.5.6.2.20120212011537.05c62e20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 12 Feb 2012 08:06:46 -0800
To: adrian@olddog.co.uk, <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Furthering discussions about BCP79 sanctions
In-Reply-To: <01a801cce827$60060e80$20122b80$@olddog.co.uk>
References: <01a801cce827$60060e80$20122b80$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:25:50 -0000

At 11:08 10-02-2012, Adrian Farrel wrote:
>There has been some discussion on this list about
>draft-farrresnickel-ipr-sanctions-00.  Thanks for the input.
>
>The conversation seems to be partitioned into:
>- discussion of sanctions and how to apply them
>- discussion of measures that can be taken to
>   help people to adhere to BCP79

The following messages are about the "help people":

http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html
http://www.ietf.org/mail-archive/web/marf/current/msg02081.html

>Furthermore, there is some debate about who should/can be responsible for
>applying sanctions.
>
>The authors of the draft are of the opinion that in the case of work 
>produced by
>a working group, the disruption caused by breaking BCP79 is directly to "the
>smooth running of the WG".  The Chair has the responsibility and the authority
>to make decisions, on behalf of the working group, regarding all matters of
>working group process and staffing, in conformance with the rules of the IETF.
>The AD has the authority and the responsibility to assist in making those
>decisions at the request of the Chair or when circumstances warrant such an
>intervention.

Ok.

In Appendix A:

  "-  Does the large number of patents that the individual has authored
      provide any level of excuse for failing to notice that one of
      their patents covered the IETF work?"

That should be "the individual has invented".

I suggest removing the above as prolific inventors should pay more 
attention to BCP 79.  There is the following excuse:

     "Is there a reason for the individual forgetting the existence of
      the IPR (for example, it was filed many years previous to the work
      in the IETF)?"

which can be used.

Section 6.1.2 of BCP 79 is about an IETF Participant's IPR in 
Contributions by others.   Should sanctions be considered if the 
individual participates and does not disclose?

Regards,
-sm 


From adrian@olddog.co.uk  Sun Feb 12 10:12:53 2012
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 4CB8621F865F for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 10:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.607
X-Spam-Level: 
X-Spam-Status: No, score=-2.607 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sTO3cEgPUk-G for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 10:12:52 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 08C1421F866E for <ietf@ietf.org>; Sun, 12 Feb 2012 10:12:49 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1CICl4F016892;  Sun, 12 Feb 2012 18:12:48 GMT
Received: from 950129200 (cust.static.46-14-88-128.swisscomdata.ch [46.14.88.128]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1CICiiA016849 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 12 Feb 2012 18:12:46 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'SM'" <sm@resistor.net>
References: <01a801cce827$60060e80$20122b80$@olddog.co.uk> <6.2.5.6.2.20120212011537.05c62e20@resistor.net>
In-Reply-To: <6.2.5.6.2.20120212011537.05c62e20@resistor.net>
Subject: RE: Furthering discussions about BCP79 sanctions
Date: Sun, 12 Feb 2012 18:12:39 -0000
Message-ID: <03e501cce9b1$ed0f2e20$c72d8a60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-language: en-gb
Thread-Index: AQGDJ+LkHplH6a9DlbHfpzKg2UOqLgICudWklrz3UfA=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:12:53 -0000

Hi SM,

> >There has been some discussion on this list about
> >draft-farrresnickel-ipr-sanctions-00.  Thanks for the input.
> >
> >The conversation seems to be partitioned into:
> >- discussion of sanctions and how to apply them
> >- discussion of measures that can be taken to
> >   help people to adhere to BCP79
> 
> The following messages are about the "help people":
> 
> http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html
> http://www.ietf.org/mail-archive/web/marf/current/msg02081.html

Yes. I've been watching those threads, and I think that some other WGs are
thinking of following similar procedures.

> >Furthermore, there is some debate about who should/can be responsible for
> >applying sanctions.

[snip]

> In Appendix A:
> 
>   "-  Does the large number of patents that the individual has authored
>       provide any level of excuse for failing to notice that one of
>       their patents covered the IETF work?"
> 
> That should be "the individual has invented".

Yes.

> I suggest removing the above as prolific inventors should pay more
> attention to BCP 79.  

I'm inclined to agree with you.

Others feel that there may be some mitigation in this case.

By listing the point, we are giving the WG chairs the opportunity to consider
it. They may deduce that it provides an excuse, no excuse, or exacerbates the
case.

> Section 6.1.2 of BCP 79 is about an IETF Participant's IPR in
> Contributions by others.   Should sanctions be considered if the
> individual participates and does not disclose?

Yes. That is certainly my intention in this document. All violations of BCP 79
are cause to consider sanctions. The severity of the case may be judged by many
factors, and I suppose that the level of "participation" may be one of these
factors. I am hoping that Section 2.1 makes the first point clear, and Appendix
A the second point.

Cheers,
Adrian






From sm@resistor.net  Sun Feb 12 11:47:39 2012
Return-Path: <sm@resistor.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 DACC321F8683 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 11:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKuPxUN-lCGg for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 11:47:36 -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 A698221F8669 for <ietf@ietf.org>; Sun, 12 Feb 2012 11:47:35 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1CJlUDS018708 for <ietf@ietf.org>; Sun, 12 Feb 2012 11:47:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329076055; i=@resistor.net; bh=glYOIrRljN2VX0m1QpfZi82Sq+zODmYSAAZ3zc4s2GY=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=G4KHawB310qy5CXbY4kr0qY8Qidl2XzJxtvm7qXykGvNZFk2ArOGVgh4sDkL616KL 9obmusKAvwiUvS/u6HOdyj41iQr7F1LyqnpKse7y2D0tY+y5+/v0Ms8hQg1Fz18v9r /4HeCow8X/xKzcSTirs9U8HyHI0zSj+p/GRIa8e4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329076055; i=@resistor.net; bh=glYOIrRljN2VX0m1QpfZi82Sq+zODmYSAAZ3zc4s2GY=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=jOSxggIGJVTUGvtegg0++WcR6cMkDbu8c08asc4GQWvc8U5iY3RJtZL1d1kz5Wg85 BLhNew2f9gfBNL2U+WqsmTVdwvUsXsb/C535LJPWM05WagDPTudE3altSl+H78rKWm ENnAMQm2PDGIFe6kGLllca9tZCi+8KIYyqyM0arY=
Message-Id: <6.2.5.6.2.20120212080705.05c630b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 12 Feb 2012 11:29:27 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <20120211160237.A388C18C170@mercury.lcs.mit.edu>
References: <20120211160237.A388C18C170@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:47:40 -0000

At 08:02 11-02-2012, Noel Chiappa wrote:
>In reality, the _only_ choice the IETF has is between:
>
>- Deploy CGNAT with messy ad-hoc assigned addresses (squatting, whatever)
>- Deploy CGNAT with an assigned address block

There is an IPR disclosure on file for RFC 6264 (Informative 
reference).  There is an IPR disclosure which may be related to one 
of the services mentioned in Section 5.2 of the 
draft.  draft-ietf-behave-lsn-requirements-05 discusses about common 
requirements for Carrier Grade NATs.  An IPR disclosure was filed.

The IPv4 address pool status is as follows:

                  IPv4 /8
  RIR Pool          18
  Reserved (IETF)   35
  Unadvertised      53
  Advertised       149

Research carried out in 2008 listed unofficial use of the following (IPv4) /8s:

  1, 2, 5, 14, 23, 39, 42, 100, 101, 107, 175 and 176

All those IPv4 /8s are currently allocated to RIRs.

Is an IPv4 address block assignment necessary for 
draft-ietf-behave-lsn-requirements-05?

Regards,
-sm


From mansaxel@besserwisser.org  Sun Feb 12 12:46:28 2012
Return-Path: <mansaxel@besserwisser.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 CC2EF21F8683 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 12:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0ELf8E6OZDc for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 12:46:28 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 194EF21F867E for <ietf@ietf.org>; Sun, 12 Feb 2012 12:46:27 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 3C1849E96; Sun, 12 Feb 2012 21:46:23 +0100 (CET)
Date: Sun, 12 Feb 2012 21:46:23 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: ietf@ietf.org
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120212204623.GL27669@besserwisser.org>
References: <20120212013903.955FC18C18A@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120212013903.955FC18C18A@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:46:28 -0000

On Sat, Feb 11, 2012 at 08:39:03PM -0500, Noel Chiappa wrote:
>     > From: Doug Barton <dougb@dougbarton.us>
> 
>     > We already have a way to make collisions "very unlikely," don't use
>     > either of 192.168.[01]. 
> 
> I gather that that's not desirable, because otherwise people wouldn't be
> asking for another block. Of course it could probably be made to work
> somehow - with enough thrust, etc, etc. But that's not the point - engineering
> is (or ought to be) all about balancing costs and benefits.

Close. The cost to these late adapters without sensible business plans
will be higher if they aren't given this allocation. Truth is, that the
same problem they are facing has been dealt with in corporate networks
for at least 14 years -- I do remember being the victim of a RFC1918
address plan with double NAT for private inter-company links in 1998.

The problem is known, solutions exist, and these people have no place
requesting a critically scarce resource just to buy themselves fewer
customer support calls. Fewer customer support calls one gets by building
a better network, not by crying to get community pity.

> If the people involved were asking for something incredibly
> painful/expensive in order to make their lives easier, the answer would
> rightly be 'no'. The cost would far outweigh the benefit. But they're not.
> All they're asking for is a modest chunk of address space, and the cost of
> doing that is not significant - we allocate chunks of space _all the time_.

Soon, "all the time" won't be. 
The IANA has no way of allocating this -- they've run out. 
Which RIR is going to part with a /10 then? APNIC has run out.  The rest
of the RIRen are, IIRC, operating in sunset mode, where allocations are 
_very_ restricted.

That is why address space should not be allocated. Because there _is_
a cost, the cost of not being able to allocate unique address space when
there is a more legitimate need than the proposed wasting of an entire
/10 to please those who did not do the right thing.  And to top that off,
they are too cheap to do the homework of proving their precarious
situation. They just state their need and expect us to accept it and
codify it in RFC format.

> But it is. As I said before, the IETF has precisely two choices:
> 
> - See CGN deployed using various hacks (e.g. squatting on space)
> - See CGN deployed using a block of space allocated for that purpose
> 
> Allocate, or don't allocate. That's the only choice.

This sounds like a bullying ultimatum. We are not there yet, the alley
is wider, and U-turns are possible.

The choice is and was between "do CGN using RFC1918" and "build a
network that takes advantage of the latest 15 years of developement
in networking".

One can argue whether there is significant short-term gains for a
commercial entity in doing the right thing as opposed to just cutting
corners. And, I firmly believe that any SDO not in touch with reality is
bordering on silly. But there is a definite difference between being a
tool for the shortsighted on the one hand and  crafting good solutions
to technical problems on the other.

-- 
Måns

From marka@isc.org  Sun Feb 12 13:25:36 2012
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 2A4A721F869D for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 13:25:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.4
X-Spam-Level: 
X-Spam-Status: No, score=-2.4 tagged_above=-999 required=5 tests=[AWL=-0.101,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ayji4hRrd-jj for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 13:25:35 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 9D28421F869F for <ietf@ietf.org>; Sun, 12 Feb 2012 13:25:35 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 861545F98AF; Sun, 12 Feb 2012 21:25:19 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:f180:78b1:c11c:a1e1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id B2A7E216C6A; Sun, 12 Feb 2012 21:25:17 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 9B43B1D2F47D; Mon, 13 Feb 2012 08:25:13 +1100 (EST)
To: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
From: Mark Andrews <marka@isc.org>
References: <20120212013903.955FC18C18A@mercury.lcs.mit.edu> <20120212204623.GL27669@besserwisser.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-reply-to: Your message of "Sun, 12 Feb 2012 21:46:23 BST." <20120212204623.GL27669@besserwisser.org>
Date: Mon, 13 Feb 2012 08:25:13 +1100
Message-Id: <20120212212513.9B43B1D2F47D@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:25:36 -0000

In message <20120212204623.GL27669@besserwisser.org>, =?iso-8859-1?Q?M=E5ns?= N
ilsson writes:
> On Sat, Feb 11, 2012 at 08:39:03PM -0500, Noel Chiappa wrote:
> >     > From: Doug Barton <dougb@dougbarton.us>
> > =
> 
> >     > We already have a way to make collisions "very unlikely," don't use
> >     > either of 192.168.[01]. =
> 
> > =
> 
> > I gather that that's not desirable, because otherwise people wouldn't be
> > asking for another block. Of course it could probably be made to work
> > somehow - with enough thrust, etc, etc. But that's not the point - engine=
> ering
> > is (or ought to be) all about balancing costs and benefits.
> 
> Close. The cost to these late adapters without sensible business plans
> will be higher if they aren't given this allocation.

How is this a "late adapter" problem?  You either have enough
addresses to give every customer a IPv4 address or you don't.  If
you don't have enough addresses you are going to have to use some
sort of CGN whether that is NAT444 or AFTR or some other transition
technology which shares IPv4 addresses.

Isn't the IETF's preferred transition strategy still "dual stack"
or are you thinking that ISP's that can't get enough IPv4 address
have to go IPv6 only?

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

From jnc@mercury.lcs.mit.edu  Sun Feb 12 13:34:42 2012
Return-Path: <jnc@mercury.lcs.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 1A74621F8685 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 13:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.297
X-Spam-Level: 
X-Spam-Status: No, score=-6.297 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyyiStlubNdX for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 13:34:41 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 91F2421F867E for <ietf@ietf.org>; Sun, 12 Feb 2012 13:34:41 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id B318E18C16D; Sun, 12 Feb 2012 16:34:40 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120212213440.B318E18C16D@mercury.lcs.mit.edu>
Date: Sun, 12 Feb 2012 16:34:40 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:34:42 -0000

    > From: Nilsson <mansaxel@besserwisser.org>

    > there _is_ a cost, the cost of not being able to allocate unique
    > address space when there is a more legitimate need than the proposed
    > wasting of an entire /10 to please those who did not do the right
    > thing. 

On the contrary, denying this block is likely to _accelerate_ usage of
what space remains, thereby penalizing the 'other users' whose interests
you _claim_ to be protecting.

If an ISP can't use a shared block, they'll go ask their RIR for a block -
and given that they demonstrably have the need (lots of customers), they
will get it. Multiply than by N providers.

Again, denying this block is just an attempt to punish ISPs who aren't
doing what you want - nothing else. There is _no_ good engineering reason
to deny this request.

    >> Allocate, or don't allocate. That's the only choice.

    > This sounds like a bullying ultimatum.

Not intended to be; I am not a provider, and have no connection to any
provider. This is just my take on what the reality of the situation is.

    > The choice is and was between "do CGN using RFC1918" and "build a
    > network that takes advantage of the latest 15 years of developement
    > in networking".

Don't you think any network that was going to do the second would have
already decided that? The ones who are going to do CGN are going to do CGN
- the only question is what block of address space they are going to use.
Denying them a block is not going to stop CGN.

	Noel

From marka@isc.org  Sun Feb 12 14:12:00 2012
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 8E87521F8688 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 14:12:00 -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=[AWL=-0.595, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9bqOWKtFfsK for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 14:12:00 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id B788C21F86E4 for <ietf@ietf.org>; Sun, 12 Feb 2012 14:11:59 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id E9D875F984C; Sun, 12 Feb 2012 22:11:37 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:f180:78b1:c11c:a1e1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 211DA216C6A; Sun, 12 Feb 2012 22:11:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 896CF1D2F5E0; Mon, 13 Feb 2012 09:11:30 +1100 (EST)
From: Mark Andrews <marka@isc.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-reply-to: Your message of "Mon, 13 Feb 2012 08:25:13 +1100."
Date: Mon, 13 Feb 2012 09:11:30 +1100
Message-Id: <20120212221130.896CF1D2F5E0@drugs.dv.isc.org>
Cc: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:12:00 -0000

Mark Andrews writes:
> 
> In message <20120212204623.GL27669@besserwisser.org>, =?iso-8859-1?Q?M=E5ns?=
>  N
> ilsson writes:
> > On Sat, Feb 11, 2012 at 08:39:03PM -0500, Noel Chiappa wrote:
> > >     > From: Doug Barton <dougb@dougbarton.us>
> > 
> > >     > We already have a way to make collisions "very unlikely," don't use
> > >     > either of 192.168.[01]. =
> > 
> > > I gather that that's not desirable, because otherwise people wouldn't be
> > > asking for another block. Of course it could probably be made to work
> > > somehow - with enough thrust, etc, etc. But that's not the point - engine
> =
> > ering
> > > is (or ought to be) all about balancing costs and benefits.
> > 
> > Close. The cost to these late adapters without sensible business plans
> > will be higher if they aren't given this allocation.
> 
> How is this a "late adapter" problem?  You either have enough
> addresses to give every customer a IPv4 address or you don't.  If
> you don't have enough addresses you are going to have to use some
> sort of CGN whether that is NAT444 or AFTR or some other transition
> technology which shares IPv4 addresses.

And if you restrict it to those that do IPv4 literals there isn't much
other than NAT444 and AFTR and how many cpe's support B4 at this point?
 
> Isn't the IETF's preferred transition strategy still "dual stack"
> or are you thinking that ISP's that can't get enough IPv4 address
> have to go IPv6 only?
> 
> Mark
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mansaxel@besserwisser.org  Sun Feb 12 14:29:17 2012
Return-Path: <mansaxel@besserwisser.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 05F0721F86A6 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 14:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vya0O5BCMHFA for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 14:29:16 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id C377321F86A5 for <ietf@ietf.org>; Sun, 12 Feb 2012 14:29:15 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id BA76F9E96; Sun, 12 Feb 2012 23:29:14 +0100 (CET)
Date: Sun, 12 Feb 2012 23:29:14 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120212222907.GM27669@besserwisser.org>
References: <20120212213440.B318E18C16D@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120212213440.B318E18C16D@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:29:17 -0000

On Sun, Feb 12, 2012 at 04:34:40PM -0500, Noel Chiappa wrote:
>     > From: Nilsson <mansaxel@besserwisser.org>
> 
>     > there _is_ a cost, the cost of not being able to allocate unique
>     > address space when there is a more legitimate need than the proposed
>     > wasting of an entire /10 to please those who did not do the right
>     > thing. 
> 
> On the contrary, denying this block is likely to _accelerate_ usage of
> what space remains, thereby penalizing the 'other users' whose interests
> you _claim_ to be protecting.

What happened to 

- See CGN deployed using various hacks (e.g. squatting on space)
- See CGN deployed using a block of space allocated for that purpose

...that were the ONLY two choices we have? 

Suddenly, you introduce a third. Maybe there is more to this... 
 
> If an ISP can't use a shared block, they'll go ask their RIR for a block -
> and given that they demonstrably have the need (lots of customers), they
> will get it. Multiply than by N providers.

Not any more. Let me quote from RIPE-530, the in-force allocation policy document for RIPE NCC: 

   Allocations for LIRs from the last /8
   On application for IPv4 resources LIRs will receive IPv4 addresses according to the following:
   
   LIRs may only receive one allocation from this /8. The size of the
   allocation made under this policy will be exactly one /22.
   
   LIRs receive only one /22, even if their needs justify a larger allocation.
   
   LIRs may apply for and receive this allocation once they meet the criteria
   to receive IPv4 address space according to the allocation policy in
   effect in the RIPE NCC service region at the time of application.
   
   Allocations will only be made to LIRs if they have already received an
   IPv6 allocation from an upstream LIR or the RIPE NCC.

		RIPE-530, section 5.6 (as copied from http://www.ripe.net/ripe/docs/ripe-530)

> Again, denying this block is just an attempt to punish ISPs who aren't
> doing what you want - nothing else. There is _no_ good engineering reason
> to deny this request.

How about "there are no addresses left"? 
 
>     >> Allocate, or don't allocate. That's the only choice.
> 
>     > This sounds like a bullying ultimatum.
> 
> Not intended to be; I am not a provider, and have no connection to any
> provider. This is just my take on what the reality of the situation is.
> 
>     > The choice is and was between "do CGN using RFC1918" and "build a
>     > network that takes advantage of the latest 15 years of developement
>     > in networking".
> 
> Don't you think any network that was going to do the second would have
> already decided that? The ones who are going to do CGN are going to do CGN
> - the only question is what block of address space they are going to use.
> Denying them a block is not going to stop CGN.

...which means that the allocation is unecessary ;-) 

Seriously, Doug Barton pointed out (and I agree) that 99% of the issues
with RFC1918 space usage in CGN will be dealt with by using a suitably
obscure part of 10/8 or simply 172.16/12. FWIW, most of Asia has been
running with layers of NAT for years. Using 1918.

Which stinks. That is why we have IPv6. I fully appreciate the need for
some legacy connectivity; even though this email conversation is made
(from my point of view) fully using IPv6, there are lots of other things
needing v4. 

Running v4 services in NAT and dual-stacking with global scope v6 will
give a good incitament to migrate important and E2E-sensitive applications
to v6, while preserving some kind of pseudo-reachability for v4 services.

-- 
Måns 

From jnc@mercury.lcs.mit.edu  Sun Feb 12 15:41:59 2012
Return-Path: <jnc@mercury.lcs.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 36AD021F86EB for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 15:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.33
X-Spam-Level: 
X-Spam-Status: No, score=-6.33 tagged_above=-999 required=5 tests=[AWL=0.269,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dPjT7HwgY2uE for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 15:41:58 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id B2AEC21F86D7 for <ietf@ietf.org>; Sun, 12 Feb 2012 15:41:57 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8F50D18C134; Sun, 12 Feb 2012 18:41:56 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120212234156.8F50D18C134@mercury.lcs.mit.edu>
Date: Sun, 12 Feb 2012 18:41:56 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:41:59 -0000

    > From: Nilsson <mansaxel@besserwisser.org>

    >> denying this block is likely to _accelerate_ usage of what space
    >> remains

    > What happened to

    >>> - See CGN deployed using various hacks (e.g. squatting on space)
    >>> - See CGN deployed using a block of space allocated for that purpose

    > ...that were the ONLY two choices we have?
    > Suddenly, you introduce a third.

No. 'Everyone allocating their own CGN block' falls under "various hacks" (i.e.
option i).

    > Let me quote from RIPE-530, the in-force allocation policy document
    > for RIPE NCC

Well, I guess European ISPs are going to be forced to squat, then (there are a
number of non-backbone-routed /8s allocated to things like intelligence
agencies, which are unlikely to appear on the backbone) - unless we can get a
common CGN block allocated from elsewhere.

	Noel

From joelja@bogus.com  Sun Feb 12 20:25:21 2012
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 D2B5921F865D; Sun, 12 Feb 2012 20:25:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.756
X-Spam-Level: 
X-Spam-Status: No, score=-102.756 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ujn3mPPzfiCA; Sun, 12 Feb 2012 20:25:21 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 48E2321F862D; Sun, 12 Feb 2012 20:25:21 -0800 (PST)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q1D4PCGD059614 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 13 Feb 2012 04:25:16 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F3890A6.3090308@bogus.com>
Date: Sun, 12 Feb 2012 20:25:10 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
References: <20120201150911.25955.80172.idtracker@ietfa.amsl.com> <CAAedzxqXaPtNkyGt-P9xzdxvPkgLXcGOr-f3q7BuRq9555duaw@mail.gmail.com> <8EA035DE-DAB9-4920-9BD6-75944848CA5D@cisco.com> <CAKD1Yr2xgkEeK7SaRjMZSbdJPs0u5FTozo0qa5MA4fda+SBcyw@mail.gmail.com> <4F329696.6000505@bogus.com> <CAKD1Yr2FpapZuz4fk1M1uqmG2Xgao_K=Houpnz0Jq2k56ZLMLg@mail.gmail.com>
In-Reply-To: <CAKD1Yr2FpapZuz4fk1M1uqmG2Xgao_K=Houpnz0Jq2k56ZLMLg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 13 Feb 2012 04:25:18 +0000 (UTC)
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:25:21 -0000

On 2/9/12 01:25 , Lorenzo Colitti wrote:
> On Thu, Feb 9, 2012 at 00:36, Joel jaeggli <joelja@bogus.com
> <mailto:joelja@bogus.com>> wrote:
> 
>     Ops is not marketing.
> 
> 
> And if I were looking for a marketing venue, a standards body that
> produces ASCII text documents read by a handful of engineers would not
> be high on my list. This is not about marketing.
>

Sorry for being so droll, I found it hard to restrain myself.

> 
>     If you're saying some flag day makes the contents of the document no
>     longer operationally relevant after a given date, I'll take the point
>     but disagree.
> 
> 
> I think you're missing my point.
> 
> It seems to me that approximately 30% of the non-biolerplate text in
> this draft discusses DNS whitelisting. (And in fact, in its original
> form the draft entirely on DNS whitelisting - hence the filename. The
> rest was added later.)
> 
> Whitelisting is a practice relevant to a few large websites (since
> nobody else is using it). It so happens that the websites that employ
> this practice are going to stop using it, all together. Given the cost
> and implications, I'd say practice is unlikely to be resurrected.

I do not belive that the selective (inclusive) return of A or A + AAAA
records on the basis of source address is likely to end on a particular
day. It may well for you and some others, which is fine, or you may find
it necessary again, or it may become a list of exclusions rather than
inclusions. I belive you're on record indicating as much. In any event
others may find it necessary.

> So, you decide to tell the whole story, and talk about whitelisting
> *and* World IPv6 Launch. Or you can decide that whitelisting will soon
> be irrelevant, and not talk about either whitelisting or World IPv6
> Launch. But you can't talk about whitelisting without talking about
> World IPv6 Launch, because if you do, your document is missing the key
> piece "how do you remove the whitelist", and that's a disservice to its
> readers.
> 
> To be more specific, at least section 5.5 ("it is unclear
> how implementers will judge when the network conditions will have
> changed sufficiently to justify turning off DNS Resolver Whitelisting
> and/or what the process and timing will be for discontinuing this
> practice") is now incorrect. It *is* clear, and it's what those
> implementers are doing as part of World IPv6 Launch.

Invidual service operators like you and I are likely to make decisions
on the basis of our instrumentation, we may well alter their behavior on
a uni or multilateral basis, and some of us may do so for world ipv6
launch. ipv4/v6 Transition is not something with a flag day however, and
I do not believe that the concerns embedded in the draft will be
fundamentally altered on 6/6/12.

> Does that make more sense?

yes, that doesn't imply that we're in concert however.

> Cheers,
> Lorenzo


From sm@resistor.net  Sun Feb 12 23:49:07 2012
Return-Path: <sm@resistor.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 BBAB121F86F1 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 23:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUtl4SMJEMtB for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2012 23:49: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 6B01921F8704 for <ietf@ietf.org>; Sun, 12 Feb 2012 23:49:05 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1D7mmh0022175 for <ietf@ietf.org>; Sun, 12 Feb 2012 23:48:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329119342; i=@resistor.net; bh=NaeD74Reay6cc+ktaM5XiYktIGMXwN34onxe61AVjh0=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=pJwFmaYD4e9KWygwsndlnxNJVZlz9xA3wIdxlc48+0OmtRRsdD6v8luh4HYkiofBG t5RSXsl45pxEfjnaF/5b4ock5HW6d3yIXsoPbaZaa0KUQuP5SNn7+Np6tS3V+MQgzm vEGvNxWFUAkQaoqaAXsbPksDciBGnqC2ah5UGNLQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329119342; i=@resistor.net; bh=NaeD74Reay6cc+ktaM5XiYktIGMXwN34onxe61AVjh0=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=nK5fEbFd5hL0+X7cFcmzRzegKajBS/uLS7by3ves9PVDqcq77ICv0H58ztN1SwosH 7bBoPSS2xyDiiJB2gDih4EFYdYEWjlHmm/UXFqUGwbDf06pgw9RBFhXzK/oWb4X1Lq zRtdOrVG7jJuFvWnud5aNEsJwMOzdKrIS4tYOoWc=
Message-Id: <6.2.5.6.2.20120212210635.08397a60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 12 Feb 2012 23:31:06 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
In-Reply-To: <20120207225848.10346.42650.idtracker@ietfa.amsl.com>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:49:07 -0000

At 14:58 07-02-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'IETF meeting attendees' Frequently Asked (travel) Questions'
>   <draft-george-travel-faq-03.txt> as an 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 2012-03-06. Exceptionally, comments may be

In Section 1:

   "more efficiently than waiting until someone sends an email to the
    XXattendees@ietf.org list in the days leading up to the meeting."

The XX is ambiguous.

In Section 2:

   "Therefore, this document is intended to be something that can be
    provided to host event organizers that may not have much familiarity
    with the IETF, so that they have a better sense of the information
    that attendees will find helpful."

The draft is written from am IETF perspective for an IETF audience. 
Does http://wikitravel.org/en/Paris provide answers to some of the 
questions in this draft?

   "In reading this document, one may ask, "why would such a
    technologically advanced and internet-savvy organization need such
    help?  Isn't that why search engines exist?"  And the answer is that
    yes, we can sometimes find what we're looking for with search
    engines, but that results in hundreds of people spending their time
    searching, which is not very efficient.  In addition, despite the"

If hundreds of people spent their time searching, there would have 
been more information on 
http://www.ietf.org/registration/MeetingWiki/wiki/doku.php  Or is it 
not efficient for people to share the information they have found?

The following people have contributed to the ietf83 section:

  Kevin P. Fleming
  Stephanie McCammon
  Amy Vezza
  Iljitsch van Beijnum
  Scott Brim

   "no matter how good online translation is getting, some of the most
    informative sites may be difficult for non-native speakers to"

Is this about informative sites being difficult for non-native 
speakers or for people from a specific part of the world?  I suggest 
that the author seeks feedback from people who use English as a 
second language.

Visa requirements is a one-liner whereas food considerations are 
discussed in several paragraphs.  Section 3.3 is labelled 
International considerations.  The entire document is about 
international considerations.

Regards,
-sm 


From wesley.george@twcable.com  Mon Feb 13 07:23:03 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4519C21F856D for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 07:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.49
X-Spam-Level: 
X-Spam-Status: No, score=-0.49 tagged_above=-999 required=5 tests=[AWL=-0.027,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r7ws8WtnMHdc for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 07:23:02 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 16E3A21F854B for <ietf@ietf.org>; Mon, 13 Feb 2012 07:23:02 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.73,411,1325480400"; d="scan'208";a="321411668"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 13 Feb 2012 10:21:37 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 13 Feb 2012 10:22:58 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 13 Feb 2012 10:22:57 -0500
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
Thread-Topic: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
Thread-Index: AczqJAd++XH3eY9ZRTKjQKlOS/+eDwAMzhmw
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377917392CC82B@PRVPEXVS03.corp.twcable.com>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120212210635.08397a60@resistor.net>
In-Reply-To: <6.2.5.6.2.20120212210635.08397a60@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:23:03 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
M
>
> In Section 1:
>
>    "more efficiently than waiting until someone sends an email to the
>     XXattendees@ietf.org list in the days leading up to the meeting."
>
> The XX is ambiguous.
[WEG] Well, it was intended to be generic (a variable to represent multiple=
 numbers). Are you saying ambiguous as in "this intent is unclear, use a di=
fferent method to represent this generically" or "you should use a specific=
 number as an example, e.g. 83attendees@ietf.org"?
Would "the meeting-specific attendees email list" be better?

> The draft is written from am IETF perspective for an IETF audience.
[WEG] It was written by an IETF person, in the IETF's process for managing =
documents. Within those constraints, it was meant to assume very little abo=
ut what people know about IETF such that it could be useful to a non-IETF a=
udience. If there's a point to this comment other than to be snarky, I'm mi=
ssing it.

> Does http://wikitravel.org/en/Paris provide answers to some of the
> questions in this draft?
[WEG] Probably. This draft is not about evaluating sources of information t=
o be provided for individual and specific IETF meetings. It is meant to be =
generic. I'd encourage you to post that link to the Paris IETF's wiki.

>     "but that results in hundreds of people spending their time
>     searching, which is not very efficient."
>
> If hundreds of people spent their time searching, there would have
> been more information on
> http://www.ietf.org/registration/MeetingWiki/wiki/doku.php  Or is it
> not efficient for people to share the information they have found?
[WEG] no one can force those who find an answer to their question (via what=
ever method) to post it to the wiki. The meeting wiki is only as good as it=
s level of contribution, and this document isn't making commentary on that =
problem. This is simply noting that lots of attendees need a similar set of=
 information.

>    "no matter how good online translation is getting, some of the most
>     informative sites may be difficult for non-native speakers to"
>
> Is this about informative sites being difficult for non-native
> speakers or for people from a specific part of the world?
[WEG] I think this is pretty self-explanatory taken in the context of the p=
receding sentences, but I'll attempt to clarify. When one is attempting to =
do research about a place one is planning to visit, if the site with the be=
st information is only available in the local language, and half of the sit=
e is flash or graphical text buttons, sending it to translate.google is not=
 going to translate the text contained in flash or images, which may make t=
he site difficult or impossible to use. The source and destination language=
/region is immaterial. This is simply defining a practical matter associate=
d with language barriers online.

> I suggest that the author seeks feedback from people who use English as a
> second language.
[WEG] The author has sought and received feedback from the IETF list multip=
le times prior to last call, and again now. One might be forgiven for assum=
ing that there are a few nonnative English speakers among the subscribers o=
f said list who have read the document. If those who use English as a secon=
d language have text to provide, he'll gladly accept it. Otherwise, maligni=
ng the document or its author because it attempts to cover language issues =
but was written by an native English speaker is not particularly productive=
.

> Visa requirements is a one-liner whereas food considerations are
> discussed in several paragraphs.
[WEG] The main posting on the IETF site regarding the specific meeting incl=
udes a link to one or more Visa information sites. IETF has been providing =
links to Visa information for years, as it is far more critical to foreign =
attendance than any of the other items discussed in this document. Therefor=
e I didn't spend a lot of time on it. The only part of the currently-provid=
ed visa information that I have seen complaints about is when the combinati=
on of the source and destination countries' embassies don't play nicely tog=
ether and Visas take too long to be practical. That is a much different pro=
blem. However, more than one person has commented about the limited text wi=
th regards to visas, so I'll attempt to bolster the Visa discussion slightl=
y, but suggested text is welcome.

 Section 3.3 is labelled
> International considerations.  The entire document is about
> international considerations.
[WEG] After reviewing what is in this section based on your comment, I'd ar=
gue the other way. Like the rest of the document, a large portion of it is =
not specific to international travel and may vary by region and municipalit=
y within the same country. I'm open to suggestions as to an alternate headi=
ng for section 3.3 that is more descriptive than "other."

Wes George

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From arturo.servin@gmail.com  Sat Feb 11 05:00:17 2012
Return-Path: <arturo.servin@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 2231421F856A for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 05:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w4yj1ZEl0QBf for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2012 05:00:11 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2026421F855A for <ietf@ietf.org>; Sat, 11 Feb 2012 05:00:11 -0800 (PST)
Received: by qcsq13 with SMTP id q13so165252qcs.31 for <ietf@ietf.org>; Sat, 11 Feb 2012 05:00:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=o5Hex/3gXHkI4UsmxSzBgwzaIrSHYG+tYHMJccRour0=; b=IZRn85Y9FEbSG+gPVZFb8s5XYr+eYeqHVbL7/L1M1xwXnlrMT/Nli2hG3P4nRxLYda QXzJ8bVdpYJBC30V1qnCsNAVJinGfXmjeRDSB9MafJWdPryRBry+QZEwuojSP3H57FGK kWluGqgasOTMAbmxbElWOo2E+xacmR3zmim9w=
Received: by 10.229.102.148 with SMTP id g20mr5814345qco.124.1328965210489; Sat, 11 Feb 2012 05:00:10 -0800 (PST)
Received: from [192.168.1.102] (r186-48-213-249.dialup.adsl.anteldata.net.uy. [186.48.213.249]) by mx.google.com with ESMTPS id dk2sm19781870qab.12.2012.02.11.05.00.07 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 11 Feb 2012 05:00:09 -0800 (PST)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Arturo Servin <arturo.servin@gmail.com>
In-Reply-To: <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
Date: Sat, 11 Feb 2012 11:00:04 -0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE91A108-BED5-4BBF-AF4E-D341C6D9769B@gmail.com>
References: <CB5A8851.4048F%c.donley@cablelabs.com> <077059305C20FC38FD924991@PST.JCK.COM> <CAC1-dt=wgQ-QpSWfFnBbgP8nWeiFCY=nxS8fpYfP1gb+BLiyxg@mail.gmail.com> <4F35969D.2000902@dougbarton.us> <CAC1-dtn+qS9_2NNJ1ChM84yB2Z97vECKqMnx_5MKUi8ow4iFVQ@mail.gmail.com>
To: Chris Grundemann <cgrundemann@gmail.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Mon, 13 Feb 2012 08:02:37 -0800
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:00:17 -0000

On 10 Feb 2012, at 22:12, Chris Grundemann wrote:

>>=20
>=20
> Are you volunteering to buy everyone on earth a new CPE? If not, who
> do you suggest will?

	I suggest the ISPs, they are charging for the service, right?

> My bet is that no one is willing to drop the
> billions of dollars required -

	Errors cost money. They decided not to invest in IPv6, now there =
is time to pay.

> if they were, we could just sign
> everyone up for IPv6 capable CPE and skip the whole debate... ;)
>=20
> Cheers,
> ~Chris

	For many of the reasons stated before, I think this space is not =
needed and I am against this proposal.

Regards,
/as



=09

=09=

From Ted.Lemon@nominum.com  Sat Feb 11 08:24:38 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7537E21F84B9; Sat, 11 Feb 2012 08:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.51
X-Spam-Level: 
X-Spam-Status: No, score=-106.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wrm4CJa6PWHr; Sat, 11 Feb 2012 08:24:38 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 84A3F21F8497; Sat, 11 Feb 2012 08:24:37 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTzaWRL0l725TjoS0phrPwfn0hGo2zTiD@postini.com; Sat, 11 Feb 2012 08:24:37 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 31ECA1B82C5; Sat, 11 Feb 2012 08:24:36 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 20188190052; Sat, 11 Feb 2012 08:24:36 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sat, 11 Feb 2012 08:24:30 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AQHM5SWUy8EqSdK3C0aOhQFr8l21aJY2slwAgAG8tQA=
Date: Sat, 11 Feb 2012 16:24:29 +0000
Message-ID: <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D29119CD5394A942A43CB1A96A908D22@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 13 Feb 2012 08:02:37 -0800
Cc: Ben Campbell <ben@nostrum.com>, The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:24:38 -0000

> [RM] The intention is to use this method only for environments with nativ=
e security mechanisms, such as the Broadband Access network. You are right =
it is not clearly said in the document I can add the following sentence at =
the end of the introduction in order to clarify this point:
>=20
> "This   mechanism is intended to be use in networks that already have nat=
ive security mechanisms that provide sufficient protection against
> spoofing of DHCP traffic."

It's probably worth revisiting the purpose of this mechanism.   The problem=
 that we are trying to solve is that people are reluctant to implement DHCP=
FORCERENEW because it's possible that an off-link attacker could more accur=
ately guess the timing of DHCP renewal messages by first sending a DHCPFORC=
ERENEW.   The mechanism in RFC3315 (DHCPv6), which this document mirrors fo=
r DHCPv4, uses a nonce to prevent an off-link attacker from successfully tr=
iggering a renewal on a client by sending DHCPFORCERENEW; since the attacke=
r is off-link, it doesn't have the nonce, and can't force a renewal.

An on-link attacker can always simply watch the DHCP renewal message go out=
 and respond to it, so this mechanism is useless for preventing on-link att=
acks, and hence the security of the nonce in the case of on-link attacks is=
n't relevant.  So the above text isn't needed.   It's possible that the doc=
ument doesn't clearly document the use case for this functionality; if so, =
you are free to take the above paragraph, Roberta, and modify it to suit yo=
ur purposes.   But I am against adding the text you proposed, because it ex=
cludes the bulk of use cases for the DHCPFORCERENEW nonce mechanism.

> [RM] This is because this mechanism relays on the authentication protocol=
 defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and there HMAC-=
MD5 is used.

Essentially HMAC-MD5 is being used here to package a secret into a chunk of=
 predictable size, and the fact that there are hacks for the mechanism isn'=
t terribly important because the only attacker we are attempting to foil is=
 one that doesn't have access to the cleartext or the ciphertext.=

From mrex@sap.com  Mon Feb 13 08:11:44 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5F521F8710 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 08:11:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.112
X-Spam-Level: 
X-Spam-Status: No, score=-10.112 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mhVWrF6Z600a for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 08:11:43 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1122C21F8679 for <ietf@ietf.org>; Mon, 13 Feb 2012 08:11:42 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q1DGBeZM014744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Feb 2012 17:11:40 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202131611.q1DGBdCt004543@fs4113.wdf.sap.corp>
Subject: Re: Last Call:
To: john-ietf@jck.com (John C Klensin)
Date: Mon, 13 Feb 2012 17:11:39 +0100 (MET)
In-Reply-To: <A697AE602B337417D34B37FF@PST.JCK.COM> from "John C Klensin" at Feb 11, 12 10:34:22 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: arturo.servin@gmail.com, ietf@ietf.org, sm@resistor.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:11:44 -0000

John C Klensin wrote:
> 
>Arturo Servin wrote:
>> 
>>Chris Grundemann wrote:
>>> 
>>> Are you volunteering to buy everyone on earth a new CPE? If
>>> not, who do you suggest will?
>> 
>> 	I suggest the ISPs, they are charging for the service, right?
>>...
>>> if they were, we could just sign
>>> everyone up for IPv6 capable CPE and skip the whole debate...
>>> ;)
> 
> So, Chris, if you expect this allocation will avoid the costs of
> signing everyone up for IPv6-capable CPE, what is your
> transition plan?  Or are you advocating an IPv4-forever model?


If CPE is meant to refer to the border router, then this appears like
a very short-sighted look at the real issue.

There are huge amounts of equipment in use that simply does not support IPv6,
other than border routers, like home multimedia and entertainment stuff
(Nintendo WII, Nintendo DS, Internet-enabled set-top-boxes & TV & Radio,
webcams, home NAS, etc.), which do not support IPv6,
so I don't see how IPv6 could be seen as a solution at all (it isn't).

So everyone who is suggesting IPv6 here, is actually
suggesting NAT 4664 over NAT 444.


-Martin



From jnc@mercury.lcs.mit.edu  Mon Feb 13 08:51:22 2012
Return-Path: <jnc@mercury.lcs.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 ED8B821F873B for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 08:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.357
X-Spam-Level: 
X-Spam-Status: No, score=-6.357 tagged_above=-999 required=5 tests=[AWL=0.242,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2J9AcsnIuuI for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 08:51:22 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 25DB721F873C for <ietf@ietf.org>; Mon, 13 Feb 2012 08:51:22 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 33C3618C14B; Mon, 13 Feb 2012 11:51:21 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120213165121.33C3618C14B@mercury.lcs.mit.edu>
Date: Mon, 13 Feb 2012 11:51:21 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:51:23 -0000

    > From: Arturo Servin <arturo.servin@gmail.com>

    >> Are you volunteering to buy everyone on earth a new CPE? If not, who
    >> do you suggest will?

    > I suggest the ISPs, they are charging for the service, right?

Lots of CPE is actually owned by the customers, not the ISPs. E.g. in our
house, both our cable modem and the router attached to it are ours.

(Not quite sure how CGN would work in such an ISP - I guess they'd assign
the customer's IP address, on our side of the cable modem, out of the CGN
block? 'traceroute' say our cable box has a 10. address on the far side,
even now.)

But, anyway, telling such ISPs 'go buy new CPE' just isn't an option.

    > Errors cost money. They decided not to invest in IPv6, now there is
    > time to pay.

Again, it's made cystal clear that the real goal of the opponents here is
to punish people for not adopting IPv6.

Don't you think this casts IPv6 in a really bad light - that the only way
to get people to adopt it is to force them into it, using whatever whips
and chains are available?

But I'll stop there, since we're not supposed to be getting de-railed into
IPv6.

	Noel

From john-ietf@jck.com  Mon Feb 13 09:47:52 2012
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 AD4C721F84F2 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 09:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.682
X-Spam-Level: 
X-Spam-Status: No, score=-102.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tNWYlv4m1P-R for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 09:47:51 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BB80621F84EC for <ietf@ietf.org>; Mon, 13 Feb 2012 09:47:51 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1RwzwL-0008vK-3f; Mon, 13 Feb 2012 12:43:49 -0500
Date: Mon, 13 Feb 2012 12:47:41 -0500
From: John C Klensin <john-ietf@jck.com>
To: mrex@sap.com
Subject: CGNs and shared space allocations (was: Re: Last Call:)
Message-ID: <D74AC197F2FFCB3983CFEEE2@PST.JCK.COM>
In-Reply-To: <201202131611.q1DGBdCt004543@fs4113.wdf.sap.corp>
References: <201202131611.q1DGBdCt004543@fs4113.wdf.sap.corp>
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
Cc: arturo.servin@gmail.com, ietf@ietf.org, sm@resistor.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:47:52 -0000

--On Monday, February 13, 2012 17:11 +0100 Martin Rex
<mrex@sap.com> wrote:

> John C Klensin wrote:
>> 
>> Arturo Servin wrote:
>>> 
>>> Chris Grundemann wrote:
>>>> 
>>>> Are you volunteering to buy everyone on earth a new CPE? If
>>>> not, who do you suggest will?
>>> 
>>> 	I suggest the ISPs, they are charging for the service,
>>> 	right? ...
>>>> if they were, we could just sign
>>>> everyone up for IPv6 capable CPE and skip the whole
>>>> debate... ;)
>> 
>> So, Chris, if you expect this allocation will avoid the costs
>> of signing everyone up for IPv6-capable CPE, what is your
>> transition plan?  Or are you advocating an IPv4-forever model?
> 
> 
> If CPE is meant to refer to the border router, then this
> appears like a very short-sighted look at the real issue.
> 
> There are huge amounts of equipment in use that simply does
> not support IPv6, other than border routers, like home
> multimedia and entertainment stuff (Nintendo WII, Nintendo DS,
> Internet-enabled set-top-boxes & TV & Radio, webcams, home
> NAS, etc.), which do not support IPv6,
> so I don't see how IPv6 could be seen as a solution at all (it
> isn't).
> 
> So everyone who is suggesting IPv6 here, is actually
> suggesting NAT 4664 over NAT 444.

Martin,

I think we have been over this territory before.   It certainly
isn't part of the current Last Call (I've changed the subject
line after it got truncated).

But, briefly and in the faint hope that an explanation from a
slightly different perspective might help, from where I sit it
looks like there are three families of IPv6 migration strategies:

(1) IPv6 packets on core network, replace or upgrade end network
border router to run IPv6, provide IPv6 on end network, expect
all devices on end network to be IPv6-capable (either natively
or dual-stack).    I agree with you that this is completely
unrealistic but it is also a complete strawman -- I know of no
one who understands the issues who is advocating it at this
point.

(2) IPv6 packets on core network, replace or upgrade end network
border router to be able to do protocol conversion address
translation as needed so that IPv4-only devices on the LAN
receive and send IPv4 packets.  That border device presents
public IPv6 addresses to the Internet, not (only) IPv4 addresses
(public or private)  There seem to be dozens of variations on
this theme, with, e.g., varying ideas about what to do about
IPv6-native or dual-stack devices on the LAN and whether to
temporarily provide public IPv4 addresses to the Internet as
well, but the two important things that all of the alternatives
have in common are that a customer with IPv6-capable devices can
reasonably expect to run IPv6 on them (and run them in the
traditional end to end mode with other IPv6 LANs and devices)
and that the translations are, at least in principle, under
customer control.

Note that, especially for ISPs that provide the customer
boundary devices as part of their services, one of the
variations is to install IPv6-only border equipment and tell
customers that, if they want to continue to run IPv4-only
devices, they need to obtain and install conversion boxes behind
the boundary devices (possibly subsidized but basically at their
own expense).  I would find that approach odious, but it is no
more odious than the choice faced by households with older
televisions in countries (or smaller areas) that are going
all-digital.  Indeed, as far as I can tell, it is _exactly_ the
same issue.


(3) IPv6 packets possibly on ISP core networks or at peering/
exchange points, but, other than large customers who can make
their own arrangements, end network border routers all speak
IPv4 (more or less exclusively) and present IPv4 addresses to
the network.  Whatever conversions are needed occur somewhere in
the middle of the network.   It seems to me that there are
several variations on this theme too but, if the motivation for
it includes "don't change any of the equipment on the user site
to be IPv6-capable" then devices on the LAN that are
IPv6-capable can't take advantage of it and devices on the LAN
that are IPv6-only can't operate (note the symmetry between that
situation and the argument you are making).  


Now a problem that some of us are having with CGNs (a member of
the third category but perhaps not the only one, or even only
one architecture), is that it doesn't seem to inherently involve
an IPv6 transition at all.  Maybe there are hybrid strategies
that make them an integral part of an IPv6 transition, but I'm
not sure I see them.  If end system LANs are going to be able to
receive IPv6 packets and/or use them internally then someone is
going to need to incur the cost of purchasing, installing, and
supporting IPv6-capable border equipment.  If avoiding the costs
of that equipment change (regardless of what else the equipment
could do) is a goal of a CGN-based strategy, then there is no
IPv6 transition strategy, only an IPv4 preservation one (and, to
me, one that reinvents many of the strengths and weaknesses of
the traditional PSTN Central Office Switch).

That doesn't mean the IETF should or should not allocate this
shared space block.  If an ISP has decided its best strategy
lies in CGNs (whether they have an IPv6 transition strategy or
the CGNs are code for an IPv4-only network that tied together
walled gardens (walled weed-patches?)), then I assume that,
absent pressures the IETF can't apply, they will do that.  If
they don't think they can use private address space for that
purpose, then either they will get this shared allocation, they
will get private space from the RIRs for running a CGN-based
architecture, or they will squat (well, maybe all three).  I
can't imagine an ISP who had decided on a CGN strategy deciding
to not go forward with it because the IETF (or even the IETF and
the RIRs) are resistant to that plan.    But that is really a
discussion about CDNs, not about the wisdom (or not) of making
this allocation.

   john



From sm@resistor.net  Mon Feb 13 10:32:57 2012
Return-Path: <sm@resistor.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 4348D21F87AB for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 10:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.607
X-Spam-Level: 
X-Spam-Status: No, score=-104.607 tagged_above=-999 required=5 tests=[AWL=1.992, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRUFwaRfW1yJ for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 10:32:55 -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 EA0CD21F87A4 for <ietf@ietf.org>; Mon, 13 Feb 2012 10:32:53 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1DIWjhd013274; Mon, 13 Feb 2012 10:32:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329157971; i=@resistor.net; bh=LoqAklQRlvRFXdljsBLYkcJBSKJ1cLfIPtnASGKnwxc=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Y/AH6ZVxARfSg6YQiCr2F5ociM6xh5xSr8AVTH9FppDWrCes40/KVnABwcXGt728G kxYM+M2NTWndGBLg4rCUsRT4XoFSWV3uiM6o6s3YV6pbLUfQA+nKtsV+8rSQ3LAvZ/ bnZyItp1eVcpHaw7Dwt2oqxhVbpxTI8uQQta7nUA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329157971; i=@resistor.net; bh=LoqAklQRlvRFXdljsBLYkcJBSKJ1cLfIPtnASGKnwxc=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=vrcFZ6u941OmERJ+E6baM7VlqBbtWiTMoZzYULUSW8w040CNTSWvuHmZNUPRMgNWq kzWhJIKdeqG6ZOdg475Ky0GfGL5J+doIMFmoDFhCgcRtcJqUoLC4loGMIVrCDE3epN OkpxkyoRuOX9og6o/Ffpz2nmpNla4AU+1FV+4SLY=
Message-Id: <6.2.5.6.2.20120213080009.09a6f450@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 13 Feb 2012 09:43:02 -0800
To: "George, Wes" <wesley.george@twcable.com>
From: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377917392CC82B@PRVPEXVS03.corp .twcable.com>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120212210635.08397a60@resistor.net> <DCC302FAA9FE5F4BBA4DCAD46569377917392CC82B@PRVPEXVS03.corp.twcable.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:32:57 -0000

Hi,
At 07:22 13-02-2012, George, Wes wrote:
>[WEG] Well, it was intended to be generic (a variable to represent 
>multiple numbers). Are you saying ambiguous as in "this intent is 
>unclear, use a different method to represent this generically" or 
>"you should use a specific number as an example, e.g. 83attendees@ietf.org"?
>Would "the meeting-specific attendees email list" be better?

I suggest using the example.  BTW, I understand what you meant by 
"XX".  See comment below.

>[WEG] It was written by an IETF person, in the IETF's process for 
>managing documents. Within those constraints, it was meant to assume 
>very little about what people know about IETF such that it could be 
>useful to a non-IETF audience. If there's a point to this comment 
>other than to be snarky, I'm missing it.

You could look at the content in terms of your target audience.  The 
draft mentions "host event organizers that may not have much 
familiarity with the IETF".  The first two sections are more like 
Last Call material to give IETF participants a sense of why the draft 
is intended to be published as a RFC.

The intent was not to be snarky.

Let's assume that you are a host and you have to find the 
information.  You can either take the points to cover "as-is" or 
you'll try and identify what information is important, what is useful 
and what is nice to have.  As an example, how to get to the venue 
might be important; how to does one differentiate between tap water 
and bottled in a restaurant is nice to have.

>[WEG] Probably. This draft is not about evaluating sources of 
>information to be provided for individual and specific IETF 
>meetings. It is meant to be generic. I'd encourage you to post that 
>link to the Paris IETF's wiki.

I don't have write access to the Wiki.

>[WEG] no one can force those who find an answer to their question 
>(via whatever method) to post it to the wiki. The meeting wiki is 
>only as good as its level of contribution, and this document isn't 
>making commentary on that problem. This is simply noting that lots 
>of attendees need a similar set of information.

I agree that the meeting wiki is only as good as the level of contribution.

>[WEG] I think this is pretty self-explanatory taken in the context 
>of the preceding sentences, but I'll attempt to clarify. When one is 
>attempting to do research about a place one is planning to visit, if 
>the site with the best information is only available in the local 
>language, and half of the site is flash or graphical text buttons, 
>sending it to translate.google is not going to translate the text 
>contained in flash or images, which may make the site difficult or 
>impossible to use. The source and destination language/region is 
>immaterial. This is simply defining a practical matter associated 
>with language barriers online.

To a layperson person, a "Flash" web site is as good as any other web 
site.  I understand your point about translating content.  My point 
was more about the information which the "average" attendee would 
look for.  See below.

>[WEG] The author has sought and received feedback from the IETF list 
>multiple times prior to last call, and again now. One might be 
>forgiven for assuming that there are a few nonnative English 
>speakers among the subscribers of said list who have read the 
>document. If those who use English as a second language have text to 
>provide, he'll gladly accept it. Otherwise, maligning the document 
>or its author because it attempts to cover language issues but was 
>written by an native English speaker is not particularly productive.

The point was not about whether you have attempted to get 
feedback.  I mentioned how you can get the kind of feedback to make 
the document more accessible to the target audience.

>[WEG] The main posting on the IETF site regarding the specific 
>meeting includes a link to one or more Visa information sites. IETF 
>has been providing links to Visa information for years, as it is far 
>more critical to foreign attendance than any of the other items 
>discussed in this document. Therefore I didn't spend a lot of time 
>on it. The only part of the currently-provided visa information that 
>I have seen complaints about is when the combination of the source 
>and destination countries' embassies don't play nicely together and 
>Visas take too long to be practical. That is a much different 
>problem. However, more than one person has commented about the 
>limited text with regards to visas, so I'll attempt to bolster the 
>Visa discussion slightly, but suggested text is welcome.

I clicked on the link on the IETF web site for visa information and I 
got to http://www.ietf.org/meeting/83/t-shirt-design-contest.html :-)

Visa information tends to be an issue for some participants.  The 
IAOC provides minimal information as it is not a travel agency yet. 
:-)  As a quick comment, people might generally look for the 
following information:

   (i)   Do I need a visa for the country (list of countries for 
which a visa is required)

   (ii)  List of embassies

   (iii) How long does the processing of the visa application generally take

   (iv)  Can I get a letter of invitation from the local host

   (v)   Requirements for visa application

>[WEG] After reviewing what is in this section based on your comment, 
>I'd argue the other way. Like the rest of the document, a large 
>portion of it is not specific to international travel and may vary 
>by region and municipality within the same country. I'm open to 
>suggestions as to an alternate heading for section 3.3 that is more 
>descriptive than "other."

A tourist might look for the following topics:

   (a) Planning your trip

   (b) Transportation

   (c) Health

   (d) Safety

   (e) Electricity

   (f) Communication

   (g) Accommodation

   (h) Climate

   (i) Money

   (j) Where to eat

   (k) Language

Everyone can find at least some information to get around if the 
destination is considered as international.  If the destination is 
considered as non-international travel, some of the information may 
be considered as obvious.

Regards,
-sm 


From ole@cisco.com  Mon Feb 13 11:02:37 2012
Return-Path: <ole@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 3B34521F84B4 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 11:02:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.626
X-Spam-Level: 
X-Spam-Status: No, score=-108.626 tagged_above=-999 required=5 tests=[AWL=1.973, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdDSKI8ggVtv for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 11:02:36 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB6D21F84AA for <ietf@ietf.org>; Mon, 13 Feb 2012 11:02:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=959; q=dns/txt; s=iport; t=1329159756; x=1330369356; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=vQDIosHmvZ/AjYz9DiqDudRE5JXPxMVQhmhZWbec7YE=; b=kdZy7ZaPPKAEJ/ay3Szf9auAEJxhU3IXRIjDHmdcS0UuvI2hWpA1P6XT Y575COrOsCRZ+55hDdh51k1j39hfZSJDBBMwYVOSabowHBDY82KXXuQlU Ovw0JO1BqnuecvEKEyYQTsuMF3Q8gnRM41hn5WvYcYEcwjV/tge6xIMpg c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANpdOU+rRDoI/2dsb2JhbABAA7AQgQeBcwEBBBIBAgEkPxALOwtXBhMioh4BgzEPAZshi04jBQgSBBACGhQBAxWEORUMgyIEiEqXe4dy
X-IronPort-AV: E=Sophos;i="4.73,412,1325462400"; d="scan'208";a="29984042"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 13 Feb 2012 19:02:36 +0000
Received: from sjc-vpn1-135.cisco.com (sjc-vpn1-135.cisco.com [10.21.96.135]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1DJ2Zl9024518; Mon, 13 Feb 2012 19:02:35 GMT
Date: Mon, 13 Feb 2012 11:02:35 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: SM <sm@resistor.net>
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
In-Reply-To: <6.2.5.6.2.20120213080009.09a6f450@resistor.net>
Message-ID: <alpine.OSX.2.01.1202131055080.5391@sjc-vpn1-135.cisco.com>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120212210635.08397a60@resistor.net> <DCC302FAA9FE5F4BBA4DCAD46569377917392CC82B@PRVPEXVS03.corp.twcable.com> <6.2.5.6.2.20120213080009.09a6f450@resistor.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:02:37 -0000

Wes,

As an additional example of "what can be done and has been done" you 
might want to point to http://hiroshima-info.info which is an example 
of a volunteer-contributed website (for IETF 76) which gives travel 
info from (I must admit) a "geek" perspective and from someone who has 
attended a lot of IETF meetings and similar events all over the world.

In my view, a lot of travel information is often provided from the 
perspective of "locals" instead of from the perspective of "visitors"
and the above example is intended to represent the latter, with a
specific category of visitor.

This was initially the placeholder info site for IETF76, it was later 
replaced (but still linked to) by the official WIDE host site.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo



From brian.e.carpenter@gmail.com  Mon Feb 13 12:13:14 2012
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 F360021F8731 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.441
X-Spam-Level: 
X-Spam-Status: No, score=-102.441 tagged_above=-999 required=5 tests=[AWL=-0.802, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9LlwYMvzmDd for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:13:13 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7947D21F8730 for <ietf@ietf.org>; Mon, 13 Feb 2012 12:13:13 -0800 (PST)
Received: by iagf6 with SMTP id f6so5629924iag.31 for <ietf@ietf.org>; Mon, 13 Feb 2012 12:13:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zjcEJV4kBz/MW7nh8hkgRS/kCcIeYgLVOLWVd+zp+Gw=; b=Zm6K3293/wtVh3YBZaRAvGOoVEhoBGnvajQOhtSY/iHsk/J61vJu46UQesuy2cdGE/ KrpKu40zhbSKG73kTFzJf5ULLP5DwlnLKHM65aClZ5xaRVehSXNRlOw3APWNinqZVc5y /XTA++z3SGG3vA/XcqRUEOu9lmE+XCwcVgMVc=
Received: by 10.50.217.130 with SMTP id oy2mr10285935igc.10.1329163993153; Mon, 13 Feb 2012 12:13:13 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id f8sm29651106ibl.6.2012.02.13.12.13.10 (version=SSLv3 cipher=OTHER); Mon, 13 Feb 2012 12:13:12 -0800 (PST)
Message-ID: <4F396ECD.7040002@gmail.com>
Date: Tue, 14 Feb 2012 09:13:01 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120213165121.33C3618C14B@mercury.lcs.mit.edu>
In-Reply-To: <20120213165121.33C3618C14B@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:13:14 -0000

On 2012-02-14 05:51, Noel Chiappa wrote:
>     > From: Arturo Servin <arturo.servin@gmail.com>
> 
>     >> Are you volunteering to buy everyone on earth a new CPE? If not, who
>     >> do you suggest will?
> 
>     > I suggest the ISPs, they are charging for the service, right?
> 
> Lots of CPE is actually owned by the customers, not the ISPs. E.g. in our
> house, both our cable modem and the router attached to it are ours.

Sure, that's very common, but these devices are consumer electronics and
will get gradually replaced by IPv6-supporting boxes as time goes on.
(That is not hand-waving, the generation of boxes with IPv6 support is
starting to appear.) Nobody, I think, is denying that there will be a long
period of coexistence as a result.

That is a separate question from this draft, which gives ISPs space for
*growing* their IPv4 customer base. I think that is what upsets people.

   Brian

From dougb@dougbarton.us  Mon Feb 13 12:34:24 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BF3421F84CD for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.588
X-Spam-Level: 
X-Spam-Status: No, score=-3.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eTTssA6urs4c for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:34:23 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB7A21F846F for <ietf@ietf.org>; Mon, 13 Feb 2012 12:34:23 -0800 (PST)
Received: (qmail 5233 invoked by uid 399); 13 Feb 2012 20:34:18 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 13 Feb 2012 20:34:18 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F3973C9.8090007@dougbarton.us>
Date: Mon, 13 Feb 2012 12:34:17 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120212213440.B318E18C16D@mercury.lcs.mit.edu>
In-Reply-To: <20120212213440.B318E18C16D@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:34:24 -0000

On 02/12/2012 13:34, Noel Chiappa wrote:
>     > From: Nilsson <mansaxel@besserwisser.org>
> 
>     > there _is_ a cost, the cost of not being able to allocate unique
>     > address space when there is a more legitimate need than the proposed
>     > wasting of an entire /10 to please those who did not do the right
>     > thing. 
> 
> On the contrary, denying this block is likely to _accelerate_ usage of
> what space remains, thereby penalizing the 'other users' whose interests
> you _claim_ to be protecting.
> 
> If an ISP can't use a shared block, they'll go ask their RIR for a block -
> and given that they demonstrably have the need (lots of customers), they
> will get it. Multiply than by N providers.

If the RIRs do not deny these requests there is likely to be a revolt.
OTOH that may be a good thing ....

As for your other 2 options:

> But it is. As I said before, the IETF has precisely two choices:
>
> - See CGN deployed using various hacks (e.g. squatting on space)

Incredibly unlikely to happen. The ISPs are smart enough to know that
this will cause them more headaches than its worth.

> - See CGN deployed using a block of space allocated for that purpose

If the IETF rightly denies this request then the ISPs are going to be
forced to use the proper option, 1918 space. Whatever customer support
costs they have to bear for the small percentage of customers that
actually manage to overlap will rightly be borne by the people who
created their own problems. Everyone wins.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From jnc@mercury.lcs.mit.edu  Mon Feb 13 12:42:59 2012
Return-Path: <jnc@mercury.lcs.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 8EED921F8570 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.379
X-Spam-Level: 
X-Spam-Status: No, score=-6.379 tagged_above=-999 required=5 tests=[AWL=0.220,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kuDWHwOf56gv for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:42:59 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 061E821F8564 for <ietf@ietf.org>; Mon, 13 Feb 2012 12:42:58 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 72BE918C168; Mon, 13 Feb 2012 15:42:58 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120213204258.72BE918C168@mercury.lcs.mit.edu>
Date: Mon, 13 Feb 2012 15:42:58 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:42:59 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > If the RIRs do not deny these requests there is likely to be a revolt.

On what grounds? The ISPs will come along and say 'I have X new customers,
please give me more space for them'. The former being true, on what ground can
the RIRs refuse (modulo cases like RIPE)?

    > If the IETF rightly denies this request then the ISPs are going to
    > be forced to use the proper option, 1918 space.

How? The IETF has neither police, nor an army.

	Noel

From drc@virtualized.org  Mon Feb 13 12:45:24 2012
Return-Path: <drc@virtualized.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 96BBF21F8635 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:45:24 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QLPDH1AK9xoH for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:45:24 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2993821F8575 for <ietf@ietf.org>; Mon, 13 Feb 2012 12:45:24 -0800 (PST)
Received: from [192.168.2.159] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 7828A1705A; Mon, 13 Feb 2012 20:45:23 +0000 (UTC)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <4F3973C9.8090007@dougbarton.us>
Date: Mon, 13 Feb 2012 12:45:22 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5657EE2-F892-4BD9-B503-71396F657839@virtualized.org>
References: <20120212213440.B318E18C16D@mercury.lcs.mit.edu> <4F3973C9.8090007@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1257)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:45:24 -0000

On Feb 13, 2012, at 12:34 PM, Doug Barton wrote:
>> If an ISP can't use a shared block, they'll go ask their RIR for a =
block -
>> and given that they demonstrably have the need (lots of customers), =
they
>> will get it. Multiply than by N providers.
>=20
> If the RIRs do not deny these requests there is likely to be a revolt.
> OTOH that may be a good thing ....

What grounds would an RIR have to deny this request?

>> - See CGN deployed using various hacks (e.g. squatting on space)
>=20
> Incredibly unlikely to happen. The ISPs are smart enough to know that
> this will cause them more headaches than its worth.

You're joking, right?

>> - See CGN deployed using a block of space allocated for that purpose
> If the IETF rightly denies this request then the ISPs are going to be
> forced to use the proper option, 1918 space.

No.  ISPs will do what makes business sense for them.  Some of these =
ISPs have already indicated that RFC 1918 won't work for them.  As such, =
they'll take whatever steps they feel is in their best interests.  =
Whether this is choosing some large block of (currently) unadvertised =
space or requesting a large block from their RIR (while they still can) =
is a decision they will make.

Regards,
-drc



From mrex@sap.com  Mon Feb 13 12:46:07 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38CE021F8575 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:46:07 -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=[AWL=0.129,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ON82ruJZ9ANg for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:46:06 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 1ACE121E803B for <ietf@ietf.org>; Mon, 13 Feb 2012 12:46:04 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1DKk2cK008384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Feb 2012 21:46:02 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Mon, 13 Feb 2012 21:46:01 +0100 (MET)
In-Reply-To: <4F396ECD.7040002@gmail.com> from "Brian E Carpenter" at Feb 14, 12 09:13:01 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:46:07 -0000

Brian E Carpenter wrote:
> 
> On 2012-02-14 05:51, Noel Chiappa wrote:
> >     > From: Arturo Servin <arturo.servin@gmail.com>
> > 
> >     >> Are you volunteering to buy everyone on earth a new CPE? If not, who
> >     >> do you suggest will?
> > 
> >     > I suggest the ISPs, they are charging for the service, right?
> > 
> > Lots of CPE is actually owned by the customers, not the ISPs. E.g. in our
> > house, both our cable modem and the router attached to it are ours.
> 
> Sure, that's very common, but these devices are consumer electronics and
> will get gradually replaced by IPv6-supporting boxes as time goes on.
> (That is not hand-waving, the generation of boxes with IPv6 support is
> starting to appear.) Nobody, I think, is denying that there will be a long
> period of coexistence as a result.
> 
> That is a separate question from this draft, which gives ISPs space for
> *growing* their IPv4 customer base. I think that is what upsets people.


The problem of ISP not newly shipping CPE that is not IPv6 capable
needs to be addressed by regulatory power (legistation), rather than
by ignorance of the part of the IETF.


ISPs *growing* their IPv4 customer base is a natural side effect
whenever ISPs allow customers to use equipment that they already
have (and might have been using with a different ISP before).


The vast majority of customers does not know or care about not having IPv6,
because there is _very_ few equipment that is vitally dependent on IPv6,
vs. huge amounts of equiment that requires IPv4.  If I had a CPE that
supported IPv6 (mine is from early 2006 an IPv4-only), my concern would
be how to reliably switch IPv6 off, because of the unsolved security and
privacy problems that IPv6 brings along.


It was the IETFs very own decision to build IPv6 in a fashion that it is
not transparently backwards compatible with IPv4.  If the is anyone to
blame for the current situation, than it is the IETF, not the consumers
or the ISPs (except for those folks at ISPs who participated in the
development of IPv6).


-Martin

From dougb@dougbarton.us  Mon Feb 13 12:58:04 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B512F21F8554 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:58:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.588
X-Spam-Level: 
X-Spam-Status: No, score=-3.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqor19GvTUYe for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 12:58:04 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB1221F854C for <ietf@ietf.org>; Mon, 13 Feb 2012 12:57:59 -0800 (PST)
Received: (qmail 7051 invoked by uid 399); 13 Feb 2012 20:57:53 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 13 Feb 2012 20:57:53 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F397950.7000001@dougbarton.us>
Date: Mon, 13 Feb 2012 12:57:52 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120212213440.B318E18C16D@mercury.lcs.mit.edu> <4F3973C9.8090007@dougbarton.us> <D5657EE2-F892-4BD9-B503-71396F657839@virtualized.org>
In-Reply-To: <D5657EE2-F892-4BD9-B503-71396F657839@virtualized.org>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:58:04 -0000

On 02/13/2012 12:45, David Conrad wrote:
> On Feb 13, 2012, at 12:34 PM, Doug Barton wrote:
>>> If an ISP can't use a shared block, they'll go ask their RIR for
>>> a block - and given that they demonstrably have the need (lots of
>>> customers), they will get it. Multiply than by N providers.
>> 
>> If the RIRs do not deny these requests there is likely to be a
>> revolt. OTOH that may be a good thing ....
> 
> What grounds would an RIR have to deny this request?

I haven't kept up to date on all of the RIRs' policies for granting
requests, but I don't recall seeing "give me a huge block so that I can
do CGN" as one of the established criteria.

>>> - See CGN deployed using various hacks (e.g. squatting on space)
>> 
>> Incredibly unlikely to happen. The ISPs are smart enough to know
>> that this will cause them more headaches than its worth.
> 
> You're joking, right?

Ok, let's assume I'm wrong. Then there are 2 options:

1. They squat on space that causes them (and their customers) pain. I'm
fine with that. Hopefully it will encourage their customers to move
away, thus causing more pain for the ISP.
2. They squat on space that doesn't cause pain. I don't like that
option, but it solves the problem, right?

>>> - See CGN deployed using a block of space allocated for that
>>> purpose
>> If the IETF rightly denies this request then the ISPs are going to
>> be forced to use the proper option, 1918 space.
> 
> No.  ISPs will do what makes business sense for them.  Some of these
> ISPs have already indicated that RFC 1918 won't work for them. 

I've already covered all the reasons I don't buy this in detail.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From rogerj@gmail.com  Mon Feb 13 13:37:11 2012
Return-Path: <rogerj@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 443D921E8049 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 13:37:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=-0.235, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVYRl20tLTIP for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 13:37:10 -0800 (PST)
Received: from mail-lpp01m020-f172.google.com (mail-lpp01m020-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5989321E803F for <ietf@ietf.org>; Mon, 13 Feb 2012 13:37:09 -0800 (PST)
Received: by lbbgk8 with SMTP id gk8so3166727lbb.31 for <ietf@ietf.org>; Mon, 13 Feb 2012 13:37:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=EBtERRehJ19jiPExngNn4AJFOUNh7V1e2E/vY53dqps=; b=TjMCotC3P8uA49m1cD7uwu6ZnIdVgCdeCzfxi9W9zagXx1A1LPPiEFJ44j2ioD02tQ 6mVYDA/BvwYtchE0GKDZsR8HdrcFA7Hx4jBhQ/rJ1FsTC3WdAfBNieyXced1qOW1Vy4Y QcAMNS6P3iR+rfrOyDP7j9+i7daAysdH3OdD4=
MIME-Version: 1.0
Received: by 10.112.29.6 with SMTP id f6mr6320814lbh.69.1329169028289; Mon, 13 Feb 2012 13:37:08 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Mon, 13 Feb 2012 13:37:08 -0800 (PST)
In-Reply-To: <4F3973C9.8090007@dougbarton.us>
References: <20120212213440.B318E18C16D@mercury.lcs.mit.edu> <4F3973C9.8090007@dougbarton.us>
Date: Mon, 13 Feb 2012 22:37:08 +0100
Message-ID: <CAKFn1SGwCFQ9VXm5RM9QEF4Jqs=WKBm=hcCgGwCCUb8Orcqhjg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:37:11 -0000

On Mon, Feb 13, 2012 at 9:34 PM, Doug Barton <dougb@dougbarton.us> wrote:
> On 02/12/2012 13:34, Noel Chiappa wrote:
>> =A0 =A0 > From: Nilsson <mansaxel@besserwisser.org>
>>
>> =A0 =A0 > there _is_ a cost, the cost of not being able to allocate uniq=
ue
>> =A0 =A0 > address space when there is a more legitimate need than the pr=
oposed
>> =A0 =A0 > wasting of an entire /10 to please those who did not do the ri=
ght
>> =A0 =A0 > thing.
>>
>> On the contrary, denying this block is likely to _accelerate_ usage of
>> what space remains, thereby penalizing the 'other users' whose interests
>> you _claim_ to be protecting.
>>
>> If an ISP can't use a shared block, they'll go ask their RIR for a block=
 -
>> and given that they demonstrably have the need (lots of customers), they
>> will get it. Multiply than by N providers.
>
> If the RIRs do not deny these requests there is likely to be a revolt.
> OTOH that may be a good thing ....
>
> As for your other 2 options:
>
>> But it is. As I said before, the IETF has precisely two choices:
>>
>> - See CGN deployed using various hacks (e.g. squatting on space)
>
> Incredibly unlikely to happen. The ISPs are smart enough to know that
> this will cause them more headaches than its worth.
>
>> - See CGN deployed using a block of space allocated for that purpose
>
> If the IETF rightly denies this request then the ISPs are going to be
> forced to use the proper option, 1918 space. Whatever customer support
> costs they have to bear for the small percentage of customers that
> actually manage to overlap will rightly be borne by the people who
> created their own problems. Everyone wins.

+1 :-)



I did original think it was the lesser evil to support this draft, but
I have now changed my mind. Plenty of arguments from so many on so
many points that I can't really see any reason anymore to support it.

So, no I don't support this draft.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From jnc@mercury.lcs.mit.edu  Mon Feb 13 13:46:54 2012
Return-Path: <jnc@mercury.lcs.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 1E86A21F8629 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 13:46:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.397
X-Spam-Level: 
X-Spam-Status: No, score=-6.397 tagged_above=-999 required=5 tests=[AWL=0.202,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LSDKdFwfWSK7 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 13:46:53 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 33B0F21F8624 for <ietf@ietf.org>; Mon, 13 Feb 2012 13:46:53 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id B08FA18C168; Mon, 13 Feb 2012 16:46:52 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120213214652.B08FA18C168@mercury.lcs.mit.edu>
Date: Mon, 13 Feb 2012 16:46:52 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:46:54 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > I haven't kept up to date on all of the RIRs' policies for granting
    > requests, but I don't recall seeing "give me a huge block so that I
    > can do CGN" as one of the established criteria.

An ISP needs a block of size X for CGN only if it has X customers, right?  So
they can legitimately go to an RIR and say "I have X customers, please give me
a block of size X". The fact that the block is not then advertized globally,
but only used to number their CGN'd network, is neither here nor there.

Needless to say, if multiple ISPs do this, it will use _more_ address space
than simply giving them all a CGN block to share. (Unless that's the _actual_
goal in opposing this, of course.)

    > I've already covered all the reasons I don't buy this in detail.

I can repeat "2+2=5" as many times as I like, but that won't make it true.

	Noel

From mohta@necom830.hpcl.titech.ac.jp  Mon Feb 13 13:52:51 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FE421F84FC for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 13:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.069
X-Spam-Level: 
X-Spam-Status: No, score=-0.069 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s8GazY8uxXVT for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 13:52:51 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id EF33321F8532 for <ietf@ietf.org>; Mon, 13 Feb 2012 13:52:50 -0800 (PST)
Received: (qmail 40588 invoked from network); 13 Feb 2012 22:07:28 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 13 Feb 2012 22:07:28 -0000
Message-ID: <4F3985ED.3040304@necom830.hpcl.titech.ac.jp>
Date: Tue, 14 Feb 2012 06:51:41 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
In-Reply-To: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:52:51 -0000

Martin Rex wrote:

> The problem of ISP not newly shipping CPE that is not IPv6 capable
> needs to be addressed by regulatory power (legistation),

That's how OSI failed.

> rather than by ignorance of the part of the IETF.

So will be IPv6 by IETF as a regulatory power to prohibit
address space allocation.

					Masataka Ohta

From touch@isi.edu  Mon Feb 13 14:00:35 2012
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 06AFF21E8024; Mon, 13 Feb 2012 14:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.97
X-Spam-Level: 
X-Spam-Status: No, score=-102.97 tagged_above=-999 required=5 tests=[AWL=-0.371, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oabNdD4Da4YD; Mon, 13 Feb 2012 14:00:34 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 1997521E801E; Mon, 13 Feb 2012 14:00:31 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q1DM0GPO008149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Feb 2012 14:00:16 -0800 (PST)
Message-ID: <4F3987F0.5050000@isi.edu>
Date: Mon, 13 Feb 2012 14:00:16 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, dhcwg@ietf.org
Subject: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:00:35 -0000

Hi, all,

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. The authors should consider this review together with 
any other last-call comments they receive. Please always CC 
tsv-dir@ietf.org if you reply to or forward this review.

This request was received Feb. 2, 2012.

This document describes an extension to DHCPv4 for the bulk query and 
transfer of current lease status over TCP.

The following transport issues were noted, and are significant:

UPDATES- The document updates DHCP with support for TCP, and as such 
this document seems like it should UPDATE RFC2131

PORT USE- Although DHCPv4 has an assigned TCP port, this document should 
clearly indicate that there is no other specified use of that port other 
than the bulk lease query described in this document

It should further explain why no other existing DHCP exchanges are not 
valid on the TCP port.

CONNECTION MANAGEMENT- The document describes the use of TCP connections 
for bulk transfer, but needs to be more specific about which side (relay 
client or server) closes the connection, under what circumstances, and 
with what mechanism (e.g., graceful CLOSE vs. ABORT, as per RFC 793)

sec 7.3 indicates some conditions for terminating connections; this 
section should indicate which side performs this, and by what method 
(CLOSE, ABORT)

this sec also allows connections to stay open after all pending 
transactions are complete (MAY); the rationale for this should be given, 
or the connection MUST be closed.

the same issue applies to sec 7.8 and 8 throughout; sec 8.5 is 
particularly problematic on this issue because it discusses aborting a 
request using in-band data, which may not be available if the connection 
is closed using ABORT. the state of other pending connection shsould be 
discussed too.

TIMEOUTS- Sec 6.3 defines a timeout for the TCP connection; is this 
intended to supercede any TCP timeout? or is it intended to be the min 
of the TCP timeout and the specified one?

This section should more carefully explain behavior when a connection is 
dropped and the reason - e.g., timeout, abort, close.

INTERLEAVING- sec 7.7 says that the server MUST interleave replies; 
there doesn't seem a valid reason for this requirement. clearly the 
receiver MUST tolerate interleaved replies. having the server interleave 
replies is relevant only if each request/reply has its own timeout -- 
which should be overridden if there is another response in progress 
anyway. This issue should be more clearly explained and motivated.

There were some other issues noted in this document. These comments 
appear below, and although not focused on transport issues, they 
represent significant issues that IMO should be addressed as well.

NOTE - regarding some terminology issues, I did not survey current DHCP 
RFCs for consistency, but IMO these terms should be corrected even if 
they are then inconsistent with existing specs.

Joe

-----------

Major non-transport issues:

- In many places the doc allows inaction to substitute for either 
positive or negative confirmation. IMO, this invites implementation 
errors, and should be avoided. E.g., status return codes, data source 
option missing, query-for-all-configured-IPs, etc.

- the data source option reserved codes need more detailed 
specification. if these are intended for future use, then they MUST be 
ignored by the receiver (at least). if they are to mean anything at all, 
at least one bit (typically all of them) MUST be set to zero by the 
transmitter for implementations that do not support any of the component 
fields.

further, the length of this option MUST be 1

- The protocol supports bulk transfer that is not data driven. This 
could represent a security vulnerability by exposing information that 
may not be on the data path (and thus already accessible) to a relay 
agent. This should be discussed in the security considerations section.

- Integer quantities should be referred to as "unsigned 32-bit integers" 
throughout.

- "VPN" is used throughout to refer to "private" addresses (RFC 1918); a 
VPN is not just private addressing.

- (this is a nit with all IDs, FWIW) SHOULD and SHOULD NOT are used 
throughout without context. Any time SHOULD is used instead of MUST (or 
SHOULD NOT rather than MUST NOT), it is useful to explain a viable 
exception. If no such exception exists, the rationale for selecting 
SHOULD over MUST should be included.

- It would be useful to explain why STATUS-CODE strings MUST NOT be 
null-terminated; is that a protocol violation, or are you just saying 
that NULLs are valid in these strings? the description should be clear 
that the string field describes the string length without any 
termination characters.

- start-time-of-state is expressed as an offset from base-time; this 
appears to be the only time indicated as an offset rather than as an 
absolute. That inconsistency invites implementation errors; IMO, this 
should be absolute too.

- option lengths: throughout, the doc refers to option lengths as being 
"an octet"; they are *indicated* in one octet. Some are constant (e.g., 
DCHP-STATE), some allow the contents of the octet to vary. Again, this 
is an *unsigned integer* octet.

- some of the information provided (in DHCP-STATE) goes beyond that of 
DHCP. It would be useful to motivate the need for this information in a 
bulk query, and why it is not similarly available for nodes using UDP 
(e.g., as an extension to DHCPv4, not just to the bulk transfer 
command). again, absence of state information should not indicate state. 
State should always be expressed explicitly. these states are further 
meaningless without a state diagram explaining them. if such a diagram 
is not possible (as noted at end of sec 6.2.7), then the states are 
irrelevant and the option should not be included.

- in sec 6.2.9 the term "not allowed" should be explained - are they 
reserved for future use and thus ignored? or are they "not allowed" - in 
which case the doc should indicate handling if they appear.

- sec 7.4 states that the clock skew of zero is desired; this assumes 
E2E delays under 1sec. An explanation of why this is desired should be 
given, as well as the consequences of it not.

Other non-transport issues:

- The document includes definitions and references to irrelevant 
deployment and implementation issues, notably DSLAMs, concentrators, and 
access concentrators. These should not appear formally; they should be 
used only to usefully illustrate currently intended uses.

- The doc refers to "real-time", which could imply requirements not 
supported. This should be replaced with "rapid".

- "absolute time" *indicates* (rather than contains) the number of 
seconds...

- "third party agent" should be explained, i.e., neither DHCP client nor 
DHCP server.

- "downstream" and "upstream" should be defined as both away from the 
server *and towards the client* ("away from the server" has two directions).

- sec 3 should refer to relays, and returning the entire set or 
individual bindings; there is no reason to explain the goals in terms of 
access concentrators.

- sec 3.2 appears to provide contradictory advice - caching is required, 
but should be avoided? it would be useful to resolve this inconsistency.

- sec 3.3 refers to 'fast path', but this term doesn't make sense in 
this context because fast-path is a forwarding issue. it would be useful 
to explain what you mean, and pick a different term

----





From marka@isc.org  Mon Feb 13 14:06:57 2012
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 3321521E802D for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAQ8yNmBd0Ny for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:06:56 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 00F1D21E8034 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:06:56 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 20DE45F98D6; Mon, 13 Feb 2012 22:06:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d135:8818:6f44:6e0c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 4E000216C6D; Mon, 13 Feb 2012 22:06:34 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 567361D3CFB3; Tue, 14 Feb 2012 09:06:27 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
In-reply-to: Your message of "Mon, 13 Feb 2012 21:46:01 BST." <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
Date: Tue, 14 Feb 2012 09:06:26 +1100
Message-Id: <20120213220627.567361D3CFB3@drugs.dv.isc.org>
Cc: ietf@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:06:57 -0000

In message <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Brian E Carpenter wrote:
> > 
> > On 2012-02-14 05:51, Noel Chiappa wrote:
> > >     > From: Arturo Servin <arturo.servin@gmail.com>
> > > 
> > >     >> Are you volunteering to buy everyone on earth a new CPE? If not, w
> ho
> > >     >> do you suggest will?
> > > 
> > >     > I suggest the ISPs, they are charging for the service, right?
> > > 
> > > Lots of CPE is actually owned by the customers, not the ISPs. E.g. in our
> > > house, both our cable modem and the router attached to it are ours.
> > 
> > Sure, that's very common, but these devices are consumer electronics and
> > will get gradually replaced by IPv6-supporting boxes as time goes on.
> > (That is not hand-waving, the generation of boxes with IPv6 support is
> > starting to appear.) Nobody, I think, is denying that there will be a long
> > period of coexistence as a result.
> > 
> > That is a separate question from this draft, which gives ISPs space for
> > *growing* their IPv4 customer base. I think that is what upsets people.
> 
> 
> The problem of ISP not newly shipping CPE that is not IPv6 capable
> needs to be addressed by regulatory power (legistation), rather than
> by ignorance of the part of the IETF.
> 
> 
> ISPs *growing* their IPv4 customer base is a natural side effect
> whenever ISPs allow customers to use equipment that they already
> have (and might have been using with a different ISP before).

You grow your IPv4 customer base by having new customers independent
of whether they are IPv6 customers as well.  I don't think there
is a customer that only wants to connect to IPv6 sites.

Having IPv6 doesn't even cut down on needing to supply IPv4 unless
you have bleeding edge IPv6 equipment.  People still need to connect
to IPv4 literals and that will, for a quite a while yet, mean
supplying a dual stack service.

NAT64 doesn't have a way to inform the CPE on the mapping needed.
It would be simple to do with DHCP but know one had written what
needs to be in the option.

Similarly 464XLAT doesn't provide a way for the CPE to find the
prefix.  Blindly performing 464XLAT has similar issues to blindly
performing 6to4.

DS-Lite only became a RFC in the second half of 2011.  It will take
some time for IPv6 equipment vendors to add support (hosts and
routers).

> The vast majority of customers does not know or care about not having IPv6,
> because there is _very_ few equipment that is vitally dependent on IPv6,
> vs. huge amounts of equiment that requires IPv4.  If I had a CPE that
> supported IPv6 (mine is from early 2006 an IPv4-only), my concern would
> be how to reliably switch IPv6 off, because of the unsolved security and
> privacy problems that IPv6 brings along.
> 
> 
> It was the IETFs very own decision to build IPv6 in a fashion that it is
> not transparently backwards compatible with IPv4.  If the is anyone to
> blame for the current situation, than it is the IETF, not the consumers
> or the ISPs (except for those folks at ISPs who participated in the
> development of IPv6).
> 
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From cb.list6@gmail.com  Mon Feb 13 14:12:57 2012
Return-Path: <cb.list6@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 9B6DF21F859B for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level: 
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LbACKj-wtLqa for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:12:55 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0E31721E8020 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:12:55 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so5187721pbc.31 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:12:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+vSymG1Pk8DI63iSt3MrVF7l5NpZyaVk8gqzZixLdrA=; b=BdQOLxzzPMDUp528IMiczYxQu4fk0RTl9/DbaFCgfq5kTgbGLR6HrseMpLaA2mzKeb bKTqCCFwaYChIyP0VG8oiuyF/9je11KKLc93hWYJssgKG2Mnme+hyL6rxQ2pJbB1ZKwE 5ahpioJ/qwXBv145UI8QHYZWgs/qFcuSKChW8=
MIME-Version: 1.0
Received: by 10.68.210.12 with SMTP id mq12mr50682809pbc.2.1329171173172; Mon, 13 Feb 2012 14:12:53 -0800 (PST)
Received: by 10.143.164.16 with HTTP; Mon, 13 Feb 2012 14:12:53 -0800 (PST)
In-Reply-To: <20120213220627.567361D3CFB3@drugs.dv.isc.org>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org>
Date: Mon, 13 Feb 2012 14:12:53 -0800
Message-ID: <CAD6AjGS1SQz9ns0epA+ysiwHO4EG=XZhH-XZASVN_vXaPCWGCg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
From: Cameron Byrne <cb.list6@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:12:57 -0000

On Mon, Feb 13, 2012 at 2:06 PM, Mark Andrews <marka@isc.org> wrote:
>
> In message <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>, Martin Rex =
writes
> :
>> Brian E Carpenter wrote:
>> >
>> > On 2012-02-14 05:51, Noel Chiappa wrote:
>> > > =A0 =A0 > From: Arturo Servin <arturo.servin@gmail.com>
>> > >
>> > > =A0 =A0 >> Are you volunteering to buy everyone on earth a new CPE? =
If not, w
>> ho
>> > > =A0 =A0 >> do you suggest will?
>> > >
>> > > =A0 =A0 > I suggest the ISPs, they are charging for the service, rig=
ht?
>> > >
>> > > Lots of CPE is actually owned by the customers, not the ISPs. E.g. i=
n our
>> > > house, both our cable modem and the router attached to it are ours.
>> >
>> > Sure, that's very common, but these devices are consumer electronics a=
nd
>> > will get gradually replaced by IPv6-supporting boxes as time goes on.
>> > (That is not hand-waving, the generation of boxes with IPv6 support is
>> > starting to appear.) Nobody, I think, is denying that there will be a =
long
>> > period of coexistence as a result.
>> >
>> > That is a separate question from this draft, which gives ISPs space fo=
r
>> > *growing* their IPv4 customer base. I think that is what upsets people=
.
>>
>>
>> The problem of ISP not newly shipping CPE that is not IPv6 capable
>> needs to be addressed by regulatory power (legistation), rather than
>> by ignorance of the part of the IETF.
>>
>>
>> ISPs *growing* their IPv4 customer base is a natural side effect
>> whenever ISPs allow customers to use equipment that they already
>> have (and might have been using with a different ISP before).
>
> You grow your IPv4 customer base by having new customers independent
> of whether they are IPv6 customers as well. =A0I don't think there
> is a customer that only wants to connect to IPv6 sites.
>
> Having IPv6 doesn't even cut down on needing to supply IPv4 unless
> you have bleeding edge IPv6 equipment. =A0People still need to connect
> to IPv4 literals and that will, for a quite a while yet, mean
> supplying a dual stack service.
>
> NAT64 doesn't have a way to inform the CPE on the mapping needed.
> It would be simple to do with DHCP but know one had written what
> needs to be in the option.
>
> Similarly 464XLAT doesn't provide a way for the CPE to find the
> prefix. =A0Blindly performing 464XLAT has similar issues to blindly
> performing 6to4.
>

464XLAT may indeed discover the PREF64 using
http://tools.ietf.org/html/draft-ietf-behave-nat64-discovery-heuristic-05

Running code says 464XLAT works with IPv4 literals, IPv4 referrals,
and IPv4 socket APIs.

CB

> DS-Lite only became a RFC in the second half of 2011. =A0It will take
> some time for IPv6 equipment vendors to add support (hosts and
> routers).
>
>> The vast majority of customers does not know or care about not having IP=
v6,
>> because there is _very_ few equipment that is vitally dependent on IPv6,
>> vs. huge amounts of equiment that requires IPv4. =A0If I had a CPE that
>> supported IPv6 (mine is from early 2006 an IPv4-only), my concern would
>> be how to reliably switch IPv6 off, because of the unsolved security and
>> privacy problems that IPv6 brings along.
>>
>>
>> It was the IETFs very own decision to build IPv6 in a fashion that it is
>> not transparently backwards compatible with IPv4. =A0If the is anyone to
>> blame for the current situation, than it is the IETF, not the consumers
>> or the ISPs (except for those folks at ISPs who participated in the
>> development of IPv6).
>>
>>
>> -Martin
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: marka@is=
c.org
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From touch@isi.edu  Mon Feb 13 14:16:31 2012
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 D7E1821E8012; Mon, 13 Feb 2012 14:16:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.963
X-Spam-Level: 
X-Spam-Status: No, score=-102.963 tagged_above=-999 required=5 tests=[AWL=-0.364, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SeVSuJxW9t0; Mon, 13 Feb 2012 14:16:31 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3CA21E8044; Mon, 13 Feb 2012 14:16:31 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q1DMG4GT010816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Feb 2012 14:16:04 -0800 (PST)
Message-ID: <4F398BA4.3010400@isi.edu>
Date: Mon, 13 Feb 2012 14:16:04 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, dhcwg@ietf.org
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu>
In-Reply-To: <4F3987F0.5050000@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:16:32 -0000

Hi, all,

One additional transport suggestion:

- it would be useful to include recommended configurations for TCP 
connections. Given these are multi-byte request/response exchanges, 
Nagle should be disabled, e.g.

Joe

On 2/13/2012 2:00 PM, Joe Touch wrote:
> Hi, all,
>
> 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. The authors should consider this review together with
> any other last-call comments they receive. Please always CC
> tsv-dir@ietf.org if you reply to or forward this review.
>
> This request was received Feb. 2, 2012.
>
> This document describes an extension to DHCPv4 for the bulk query and
> transfer of current lease status over TCP.
>
> The following transport issues were noted, and are significant:
>
> UPDATES- The document updates DHCP with support for TCP, and as such
> this document seems like it should UPDATE RFC2131
>
> PORT USE- Although DHCPv4 has an assigned TCP port, this document should
> clearly indicate that there is no other specified use of that port other
> than the bulk lease query described in this document
>
> It should further explain why no other existing DHCP exchanges are not
> valid on the TCP port.
>
> CONNECTION MANAGEMENT- The document describes the use of TCP connections
> for bulk transfer, but needs to be more specific about which side (relay
> client or server) closes the connection, under what circumstances, and
> with what mechanism (e.g., graceful CLOSE vs. ABORT, as per RFC 793)
>
> sec 7.3 indicates some conditions for terminating connections; this
> section should indicate which side performs this, and by what method
> (CLOSE, ABORT)
>
> this sec also allows connections to stay open after all pending
> transactions are complete (MAY); the rationale for this should be given,
> or the connection MUST be closed.
>
> the same issue applies to sec 7.8 and 8 throughout; sec 8.5 is
> particularly problematic on this issue because it discusses aborting a
> request using in-band data, which may not be available if the connection
> is closed using ABORT. the state of other pending connection shsould be
> discussed too.
>
> TIMEOUTS- Sec 6.3 defines a timeout for the TCP connection; is this
> intended to supercede any TCP timeout? or is it intended to be the min
> of the TCP timeout and the specified one?
>
> This section should more carefully explain behavior when a connection is
> dropped and the reason - e.g., timeout, abort, close.
>
> INTERLEAVING- sec 7.7 says that the server MUST interleave replies;
> there doesn't seem a valid reason for this requirement. clearly the
> receiver MUST tolerate interleaved replies. having the server interleave
> replies is relevant only if each request/reply has its own timeout --
> which should be overridden if there is another response in progress
> anyway. This issue should be more clearly explained and motivated.
>
> There were some other issues noted in this document. These comments
> appear below, and although not focused on transport issues, they
> represent significant issues that IMO should be addressed as well.
>
> NOTE - regarding some terminology issues, I did not survey current DHCP
> RFCs for consistency, but IMO these terms should be corrected even if
> they are then inconsistent with existing specs.
>
> Joe
>
> -----------
>
> Major non-transport issues:
>
> - In many places the doc allows inaction to substitute for either
> positive or negative confirmation. IMO, this invites implementation
> errors, and should be avoided. E.g., status return codes, data source
> option missing, query-for-all-configured-IPs, etc.
>
> - the data source option reserved codes need more detailed
> specification. if these are intended for future use, then they MUST be
> ignored by the receiver (at least). if they are to mean anything at all,
> at least one bit (typically all of them) MUST be set to zero by the
> transmitter for implementations that do not support any of the component
> fields.
>
> further, the length of this option MUST be 1
>
> - The protocol supports bulk transfer that is not data driven. This
> could represent a security vulnerability by exposing information that
> may not be on the data path (and thus already accessible) to a relay
> agent. This should be discussed in the security considerations section.
>
> - Integer quantities should be referred to as "unsigned 32-bit integers"
> throughout.
>
> - "VPN" is used throughout to refer to "private" addresses (RFC 1918); a
> VPN is not just private addressing.
>
> - (this is a nit with all IDs, FWIW) SHOULD and SHOULD NOT are used
> throughout without context. Any time SHOULD is used instead of MUST (or
> SHOULD NOT rather than MUST NOT), it is useful to explain a viable
> exception. If no such exception exists, the rationale for selecting
> SHOULD over MUST should be included.
>
> - It would be useful to explain why STATUS-CODE strings MUST NOT be
> null-terminated; is that a protocol violation, or are you just saying
> that NULLs are valid in these strings? the description should be clear
> that the string field describes the string length without any
> termination characters.
>
> - start-time-of-state is expressed as an offset from base-time; this
> appears to be the only time indicated as an offset rather than as an
> absolute. That inconsistency invites implementation errors; IMO, this
> should be absolute too.
>
> - option lengths: throughout, the doc refers to option lengths as being
> "an octet"; they are *indicated* in one octet. Some are constant (e.g.,
> DCHP-STATE), some allow the contents of the octet to vary. Again, this
> is an *unsigned integer* octet.
>
> - some of the information provided (in DHCP-STATE) goes beyond that of
> DHCP. It would be useful to motivate the need for this information in a
> bulk query, and why it is not similarly available for nodes using UDP
> (e.g., as an extension to DHCPv4, not just to the bulk transfer
> command). again, absence of state information should not indicate state.
> State should always be expressed explicitly. these states are further
> meaningless without a state diagram explaining them. if such a diagram
> is not possible (as noted at end of sec 6.2.7), then the states are
> irrelevant and the option should not be included.
>
> - in sec 6.2.9 the term "not allowed" should be explained - are they
> reserved for future use and thus ignored? or are they "not allowed" - in
> which case the doc should indicate handling if they appear.
>
> - sec 7.4 states that the clock skew of zero is desired; this assumes
> E2E delays under 1sec. An explanation of why this is desired should be
> given, as well as the consequences of it not.
>
> Other non-transport issues:
>
> - The document includes definitions and references to irrelevant
> deployment and implementation issues, notably DSLAMs, concentrators, and
> access concentrators. These should not appear formally; they should be
> used only to usefully illustrate currently intended uses.
>
> - The doc refers to "real-time", which could imply requirements not
> supported. This should be replaced with "rapid".
>
> - "absolute time" *indicates* (rather than contains) the number of
> seconds...
>
> - "third party agent" should be explained, i.e., neither DHCP client nor
> DHCP server.
>
> - "downstream" and "upstream" should be defined as both away from the
> server *and towards the client* ("away from the server" has two
> directions).
>
> - sec 3 should refer to relays, and returning the entire set or
> individual bindings; there is no reason to explain the goals in terms of
> access concentrators.
>
> - sec 3.2 appears to provide contradictory advice - caching is required,
> but should be avoided? it would be useful to resolve this inconsistency.
>
> - sec 3.3 refers to 'fast path', but this term doesn't make sense in
> this context because fast-path is a forwarding issue. it would be useful
> to explain what you mean, and pick a different term
>
> ----
>
>
>

From mansaxel@besserwisser.org  Mon Feb 13 14:17:50 2012
Return-Path: <mansaxel@besserwisser.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 91A0721E8012 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[AWL=2.000, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-ke2vUPEuhw for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:17:37 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [192.36.115.55]) by ietfa.amsl.com (Postfix) with ESMTP id D07CA21F849D for <ietf@ietf.org>; Mon, 13 Feb 2012 14:17:36 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 69BE99E96; Mon, 13 Feb 2012 23:17:08 +0100 (CET)
Date: Mon, 13 Feb 2012 23:17:08 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120213221702.GT27669@besserwisser.org>
References: <20120213204258.72BE918C168@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20120213204258.72BE918C168@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:17:50 -0000

On Mon, Feb 13, 2012 at 03:42:58PM -0500, Noel Chiappa wrote:
>     > From: Doug Barton <dougb@dougbarton.us>
> 
>     > If the RIRs do not deny these requests there is likely to be a revolt.
> 
> On what grounds? The ISPs will come along and say 'I have X new customers,
> please give me more space for them'. The former being true, on what ground can
> the RIRs refuse (modulo cases like RIPE)?

RIPE NCC is not unique; IIRC there has been extensive synchronisation between RIRen
on the subject of sunset allocations. 

I'd expect any RIR to more or less laugh at the request of a /10 (the
size of network we've been told (without any proof beyond handwaving)
is required to do CGN nicely) at this stage of address depletion.

APNIC: 

As of Friday, 15 April 2011, each new or existing APNIC account holder
is only eligible to request and receive delegations totalling a maximum
/22 worth of address space from the APNIC IPv4 address pool.

ARIN: 

Has 3-month consumption cap on allocations. Apparently not so low on
space as the others.

LACNIC: 

Has a /22 cap per LIR en route in its PDP. 

RIPE: 

Has a /22 rule, as discussed earlier. 

AFRINIC: 

I can't at the moment locate their policy, more than that they have
incorporated the "last five /8's" document as governing text in their
policy set. Pointers to text welcome. 

To sum things up, we are at the stage where a /10 is a laughable
proposition. The largest usable block (bar squatting on DOD space)
for CGN is 10/8. I'd suggest planning for it. That last /22 will probably
end up as P router addresses in MPLS core, since all vendors have dragged
their feet in implementing v6 MPLS.
 
>     > If the IETF rightly denies this request then the ISPs are going to
>     > be forced to use the proper option, 1918 space.
> 
> How? The IETF has neither police, nor an army.

It is either 10/8 or squat. No other alternatives exist. I'd expect
squatting on the "wrong" /8 to be punishable as a Homeland Security
Department -related crime, if one takes the US-centric view.

Folks, we've run out. 
-- 
Måns. 

From sm@resistor.net  Mon Feb 13 14:28:26 2012
Return-Path: <sm@resistor.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 05DE221E804A for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:28:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.934
X-Spam-Level: 
X-Spam-Status: No, score=-101.934 tagged_above=-999 required=5 tests=[AWL=-0.731, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FG-SR5-J+wti for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:28:25 -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 1BD0021E8049 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:28:25 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1DMS8WZ006974; Mon, 13 Feb 2012 14:28:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329172094; i=@resistor.net; bh=DUsWzBRFGyiE0XqfJ4vBrrOGwV81f79mMY4+jd2ypAY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Content-Transfer-Encoding; b=t6Xp92UBe4XMs/s2G26ILvHOZNjEuMERfY0e6vxAUUyoPF71JDflv7mSqWrDbYduY +1P2G15w6kTGxSdDBo7Na+D9k3DH4dGtgTmZKxGp740SnEeBYKLemgwqdlpARmiWmI pcm2bME995i5CZlCmlbnRFxNC+KuwKeqbyt3u6Vs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329172094; i=@resistor.net; bh=DUsWzBRFGyiE0XqfJ4vBrrOGwV81f79mMY4+jd2ypAY=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Content-Transfer-Encoding; b=egl4TILzQXiGJMXjueO/KtUEJ8hBnPQAm/zlz+gLhNpt4PtBOlCkU/8GWBamqoUsJ 3OrCX1f0naU4v0B64lTSGu7Tnhu3bbxf31hZS7twgUgCGMAcNTWxI4/cXCEftvsWxr F0ry4MQ2Ts5zAiO+14XlhE3Tgj8DOA+EGDfmi2vM=
Message-Id: <6.2.5.6.2.20120213130144.09cc4ce0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 13 Feb 2012 14:26:08 -0800
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <20120213204258.72BE918C168@mercury.lcs.mit.edu>
References: <20120213204258.72BE918C168@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:28:26 -0000

Hi Noel,
At 12:42 13-02-2012, Noel Chiappa wrote:
>On what grounds? The ISPs will come along and say 'I have X new customers,
>please give me more space for them'. The former being true, on what ground=
 can
>the RIRs refuse (modulo cases like RIPE)?

If you have X new customers and you ask a RIR to=20
give you more IPv4 space, I doubt that you would=20
get more space as the evaluation might require=20
more information ( e.g.=20
http://www.ripe.net/lir-services/resource-management/contact/ipv4-evaluation=
-procedures=20
).

Here's a comparison of RIR policies.  Please=20
refer to the document from each RIR for authoritative information.

   RIR      Period
           (months)
  AfriNIC    12      Minimum /22, no maximum
                     Demonstrate 80% efficient=20
utilization of last allocated space
                     or an immediate need that=20
requires more IP addresses than are
                     available in the most recent allocation.

  APNIC      12      Minimum /24, up to a maximum=20
/22 of the remaining available
                     space after 15 April 2011.
                     Demonstrate 80% efficient=20
utilization of all prior allocated space.

  ARIN        3      Minimum /22 for multihomed, otherwise /20, no maximum.
                     Demonstrate efficient=20
utilization of all previous allocations and
                     at least 80% of the most recent allocation.

  LACNIC     12      The policy for determining=20
the size of additional allocations is
                     based on the efficient=20
utilization of space within a time frame
                     of 12 months.
                     Demonstrate 80% efficient=20
utilization of all prior allocated space.
                     The applicant must already=20
have at least one IPv6 block assigned by
                     LACNIC or, if not, must=20
simultaneously request an initial IPv6 block
                     in accordance with the=20
corresponding applicable policy. If an
                     applicant has already been=20
assigned an IPv6 block, they shall submit
                     to LACNIC a brief document=20
describing their progress in the
                     implementation of IPv6.

  RIPE               Minimum /21, no maximum.
                     Demonstrate approximately=20
80% efficient utilization of all prior
                     allocated space.

                     Until 1 July 2010, up to 12=20
months.  Between 1 July 2010 =96 31
                     December 2010, up to nine=20
months Between 1 January 2011- 31 June
                     2011, up to six months  As=20
of 1 July 2011, up to three months

According to the above, you can still get an=20
allocation of IPv4 addresses.  The amount depends=20
on the regional policy.  Whether a /10 allocation=20
is possible from the above is an exercise left to the reader.

Regards,
-sm


From dougb@dougbarton.us  Mon Feb 13 14:32:49 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C435921E8010 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:32:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.589
X-Spam-Level: 
X-Spam-Status: No, score=-3.589 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BHqXDkjyG3H for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:32:49 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id C4A4721E8012 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:32:48 -0800 (PST)
Received: (qmail 27286 invoked by uid 399); 13 Feb 2012 22:32:43 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 13 Feb 2012 22:32:43 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F398F8A.4040107@dougbarton.us>
Date: Mon, 13 Feb 2012 14:32:42 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0) Gecko/20120201 Thunderbird/10.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120213214652.B08FA18C168@mercury.lcs.mit.edu>
In-Reply-To: <20120213214652.B08FA18C168@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:32:49 -0000

On 02/13/2012 13:46, Noel Chiappa wrote:
>     > From: Doug Barton <dougb@dougbarton.us>
> 
>     > I haven't kept up to date on all of the RIRs' policies for granting
>     > requests, but I don't recall seeing "give me a huge block so that I
>     > can do CGN" as one of the established criteria.
> 
> An ISP needs a block of size X for CGN only if it has X customers, right?  So
> they can legitimately go to an RIR and say "I have X customers, please give me
> a block of size X". The fact that the block is not then advertized globally,
> but only used to number their CGN'd network, is neither here nor there.

If they have a legitimate need for "more customers -> more space" I have
no problem with that. If they lie on their application about what they
are using it for ...

> Needless to say, if multiple ISPs do this, it will use _more_ address space
> than simply giving them all a CGN block to share. (Unless that's the _actual_
> goal in opposing this, of course.)

Um, no. I'm not trying to accelerate IPv4 runout. I get that it's an
important problem, and I've been working on solutions for it for many
years. But that doesn't mean I buy the arguments that have been put
forward so far about why this new block is "necessary" either.

>     > I've already covered all the reasons I don't buy this in detail.
> 
> I can repeat "2+2=5" as many times as I like, but that won't make it true.

2+2!=5 is a fact. What you and I are talking about are opinions. I
happen to think that my opinions are better grounded in facts and
knowledge about the topic than yours are, but at the end of the day we
could both be wrong about what actually does or doesn't happen.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From drc@virtualized.org  Mon Feb 13 14:36:37 2012
Return-Path: <drc@virtualized.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 A986621E805A for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TeG2sebwdz9b for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:36:37 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 456C321E8010 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:36:37 -0800 (PST)
Received: from [192.168.2.159] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id E28B21705A; Mon, 13 Feb 2012 22:36:36 +0000 (UTC)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20120213221702.GT27669@besserwisser.org>
Date: Mon, 13 Feb 2012 14:36:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2887BB44-2A93-4D20-B9CC-65D7B607743B@virtualized.org>
References: <20120213204258.72BE918C168@mercury.lcs.mit.edu> <20120213221702.GT27669@besserwisser.org>
To: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
X-Mailer: Apple Mail (2.1257)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:36:37 -0000

Mans,

On Feb 13, 2012, at 2:17 PM, M=E5ns Nilsson wrote:
> To sum things up, we are at the stage where a /10 is a laughable

> proposition.

Other than APNIC, I don't think this is correct.  Perhaps folks from the =
RIRs can confirm.

> It is either 10/8 or squat. No other alternatives exist. I'd expect
> squatting on the "wrong" /8 to be punishable as a Homeland Security
> Department -related crime, if one takes the US-centric view.

I doubt this, particularly since the use of the addresses we're talking =
about is entirely internal.

> Folks, we've run out.=20

"I'm not dead yet!" (to misquote Monty Python)

Regards,
-drc



From mansaxel@besserwisser.org  Mon Feb 13 14:46:35 2012
Return-Path: <mansaxel@besserwisser.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 4E4F021F864B for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:46:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.585
X-Spam-Level: 
X-Spam-Status: No, score=-4.585 tagged_above=-999 required=5 tests=[AWL=1.714,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBkEJKSWj2UQ for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 14:46:34 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [192.36.115.55]) by ietfa.amsl.com (Postfix) with ESMTP id AC9CD21F8648 for <ietf@ietf.org>; Mon, 13 Feb 2012 14:46:34 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 6A1259E96; Mon, 13 Feb 2012 23:46:05 +0100 (CET)
Date: Mon, 13 Feb 2012 23:46:05 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: David Conrad <drc@virtualized.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-ID: <20120213224600.GU27669@besserwisser.org>
References: <20120213204258.72BE918C168@mercury.lcs.mit.edu> <20120213221702.GT27669@besserwisser.org> <2887BB44-2A93-4D20-B9CC-65D7B607743B@virtualized.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2887BB44-2A93-4D20-B9CC-65D7B607743B@virtualized.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:46:35 -0000

On Mon, Feb 13, 2012 at 02:36:34PM -0800, David Conrad wrote:
> Mans,
> 
> On Feb 13, 2012, at 2:17 PM, Måns Nilsson wrote:
> > To sum things up, we are at the stage where a /10 is a laughable
> 
> > proposition.
> 
> Other than APNIC, I don't think this is correct.  Perhaps folks from the RIRs can confirm.

Reading from policy texts, it is. What is stuffed away in the RIR dungeons
might technically support such an allocation, of course. For some time still. 
 
> > It is either 10/8 or squat. No other alternatives exist. I'd expect
> > squatting on the "wrong" /8 to be punishable as a Homeland Security
> > Department -related crime, if one takes the US-centric view.
> 
> I doubt this, particularly since the use of the addresses we're talking about is entirely internal.

Internal schmernal. Stuff leaks. Either by people watching allocations
and going "Hey...." or by routing slip "Hey, this block ain't 1918,
let's route it...". 
 
> > Folks, we've run out. 
> 
> "I'm not dead yet!" (to misquote Monty Python)

The rumours are persistent, though. 

-- 
Måns. 

From marka@isc.org  Mon Feb 13 15:10:38 2012
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 A8AA621F8554 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 15:10:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eczHYbi8i-BR for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 15:10:38 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id A11C821F854E for <ietf@ietf.org>; Mon, 13 Feb 2012 15:10:37 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 2A38FC94BF; Mon, 13 Feb 2012 23:10:23 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d135:8818:6f44:6e0c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 9DC56216C6A; Mon, 13 Feb 2012 23:10:22 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 651041D3D713; Tue, 14 Feb 2012 10:10:12 +1100 (EST)
To: Cameron Byrne <cb.list6@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <CAD6AjGS1SQz9ns0epA+ysiwHO4EG=XZhH-XZASVN_vXaPCWGCg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
In-reply-to: Your message of "Mon, 13 Feb 2012 14:12:53 -0800." <CAD6AjGS1SQz9ns0epA+ysiwHO4EG=XZhH-XZASVN_vXaPCWGCg@mail.gmail.com>
Date: Tue, 14 Feb 2012 10:10:12 +1100
Message-Id: <20120213231012.651041D3D713@drugs.dv.isc.org>
Cc: ietf@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:10:38 -0000

In message <CAD6AjGS1SQz9ns0epA+ysiwHO4EG=XZhH-XZASVN_vXaPCWGCg@mail.gmail.com>
, Cameron Byrne writes:
> On Mon, Feb 13, 2012 at 2:06 PM, Mark Andrews <marka@isc.org> wrote:
> >
> > In message <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>, Martin Rex =
> writes
> > :
> >> Brian E Carpenter wrote:
> >> >
> >> > On 2012-02-14 05:51, Noel Chiappa wrote:
> >> > > =A0 =A0 > From: Arturo Servin <arturo.servin@gmail.com>
> >> > >
> >> > > =A0 =A0 >> Are you volunteering to buy everyone on earth a new CPE? =
> If not, w
> >> ho
> >> > > =A0 =A0 >> do you suggest will?
> >> > >
> >> > > =A0 =A0 > I suggest the ISPs, they are charging for the service, rig=
> ht?
> >> > >
> >> > > Lots of CPE is actually owned by the customers, not the ISPs. E.g. i=
> n our
> >> > > house, both our cable modem and the router attached to it are ours.
> >> >
> >> > Sure, that's very common, but these devices are consumer electronics a=
> nd
> >> > will get gradually replaced by IPv6-supporting boxes as time goes on.
> >> > (That is not hand-waving, the generation of boxes with IPv6 support is
> >> > starting to appear.) Nobody, I think, is denying that there will be a =
> long
> >> > period of coexistence as a result.
> >> >
> >> > That is a separate question from this draft, which gives ISPs space fo=
> r
> >> > *growing* their IPv4 customer base. I think that is what upsets people=
> .
> >>
> >>
> >> The problem of ISP not newly shipping CPE that is not IPv6 capable
> >> needs to be addressed by regulatory power (legistation), rather than
> >> by ignorance of the part of the IETF.
> >>
> >>
> >> ISPs *growing* their IPv4 customer base is a natural side effect
> >> whenever ISPs allow customers to use equipment that they already
> >> have (and might have been using with a different ISP before).
> >
> > You grow your IPv4 customer base by having new customers independent
> > of whether they are IPv6 customers as well. =A0I don't think there
> > is a customer that only wants to connect to IPv6 sites.
> >
> > Having IPv6 doesn't even cut down on needing to supply IPv4 unless
> > you have bleeding edge IPv6 equipment. =A0People still need to connect
> > to IPv4 literals and that will, for a quite a while yet, mean
> > supplying a dual stack service.
> >
> > NAT64 doesn't have a way to inform the CPE on the mapping needed.
> > It would be simple to do with DHCP but know one had written what
> > needs to be in the option.
> >
> > Similarly 464XLAT doesn't provide a way for the CPE to find the
> > prefix. =A0Blindly performing 464XLAT has similar issues to blindly
> > performing 6to4.
> >
> 
> 464XLAT may indeed discover the PREF64 using
> http://tools.ietf.org/html/draft-ietf-behave-nat64-discovery-heuristic-05

draft-ietf-behave-nat64-discovery-heuristic-05 really isn't a solution.

It doesn't say anything about choosing the A records such that there
is no abmiguity when look for the embedded address.

It doesn't have the exceptions which are part of DNS64.  This means
you can't use it reliably with dual stack internal and IPv6-only
external.

Below is the DNS64 configuration elements from named.

dns64 <netprefix> {
	break-dnssec <boolean>;
	clients { <address_match_element>; ... };
	exclude { <address_match_element>; ... };
	mapped { <address_match_element>; ... };
	recursive-only <boolean>;
	suffix <ipv6_address>;
};

While not all of them are required for IPv4 literals more than netprefix and
suffix are required which is all draft-ietf-behave-nat64-discovery-heuristic-05
delivers. 

> Running code says 464XLAT works with IPv4 literals, IPv4 referrals,
> and IPv4 socket APIs.

> CB
> 
> > DS-Lite only became a RFC in the second half of 2011. =A0It will take
> > some time for IPv6 equipment vendors to add support (hosts and
> > routers).
> >
> >> The vast majority of customers does not know or care about not having IP=
> v6,
> >> because there is _very_ few equipment that is vitally dependent on IPv6,
> >> vs. huge amounts of equiment that requires IPv4. =A0If I had a CPE that
> >> supported IPv6 (mine is from early 2006 an IPv4-only), my concern would
> >> be how to reliably switch IPv6 off, because of the unsolved security and
> >> privacy problems that IPv6 brings along.
> >>
> >>
> >> It was the IETFs very own decision to build IPv6 in a fashion that it is
> >> not transparently backwards compatible with IPv4. =A0If the is anyone to
> >> blame for the current situation, than it is the IETF, not the consumers
> >> or the ISPs (except for those folks at ISPs who participated in the
> >> development of IPv6).
> >>
> >>
> >> -Martin
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: marka@is=
> c.org
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From brian.e.carpenter@gmail.com  Mon Feb 13 16:17:25 2012
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 7089421E8022 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.406
X-Spam-Level: 
X-Spam-Status: No, score=-103.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YWWj3a19i8WZ for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:17:24 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id B417921E801A for <ietf@ietf.org>; Mon, 13 Feb 2012 16:17:24 -0800 (PST)
Received: by iagf6 with SMTP id f6so5963440iag.31 for <ietf@ietf.org>; Mon, 13 Feb 2012 16:17:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tdfc+Pn+tZgYwEyQxuWTcp8iG8fBk/4Wiztr3hwZ/po=; b=W83y3QUpU/vnY/q7w9mhFlowVmy0g0sqU101JOiRz2Ie5JkwsOfwbf105Psy8E9S8i 9zTCQeOde81dpFgUpbFHrV7vU2RQVTdmN4YowRT3cHDsXwnMoz5Nj6HMqf+fDQh97lmo y2V91ISyspuHf9Wc0yRqa99d8fPsAJveuyrSo=
Received: by 10.42.144.196 with SMTP id c4mr24679607icv.39.1329178644446; Mon, 13 Feb 2012 16:17:24 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id en8sm10951731igc.5.2012.02.13.16.17.21 (version=SSLv3 cipher=OTHER); Mon, 13 Feb 2012 16:17:23 -0800 (PST)
Message-ID: <4F39A81A.5020608@gmail.com>
Date: Tue, 14 Feb 2012 13:17:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org>
In-Reply-To: <20120213220627.567361D3CFB3@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:17:25 -0000

Martin Rex wrote:
...
>> It was the IETFs very own decision to build IPv6 in a fashion that it is
>> not transparently backwards compatible with IPv4.  If the is anyone to
>> blame for the current situation, than it is the IETF, not the consumers
>> or the ISPs (except for those folks at ISPs who participated in the
>> development of IPv6).

People say this from time to time, but it's a complete myth.

IPv4 provides no mechanism whatever for addresses greater than 32 bits.
Therefore, mathematically, there is no possible design for an IP with
bigger addresses that is transparently backwards compatible. We've known
that since at least 1992.

The design error was made in the late 1970s, when Louis Pouzin's advice
that catenet addresses should be variable length, with a format prefix,
was not taken during the design of IPv4.

(There were advocates of variable length addresses for IPng, but the
128 bit choice won on the grounds that it is enough for anything, which
32 bits clearly wasn't.)

   Brian (donning flameproof clothing)

From dhc@dcrocker.net  Mon Feb 13 16:32:18 2012
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 4591021E802E for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.633
X-Spam-Level: 
X-Spam-Status: No, score=-6.633 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jGOmGp1X9lwb for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:32:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A08BE21E801A for <ietf@ietf.org>; Mon, 13 Feb 2012 16:32:17 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1E0WAmj007824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Feb 2012 16:32:15 -0800
Message-ID: <4F39AB80.7060400@dcrocker.net>
Date: Mon, 13 Feb 2012 16:32:00 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com>
In-Reply-To: <4F39A81A.5020608@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 13 Feb 2012 16:32:15 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:32:18 -0000

On 2/13/2012 4:17 PM, Brian E Carpenter wrote:
> People say this from time to time, but it's a complete myth.

well, not completely...


> IPv4 provides no mechanism whatever for addresses greater than 32 bits.
> Therefore, mathematically, there is no possible design for an IP with
> bigger addresses that is transparently backwards compatible. We've known
> that since at least 1992.


The path that the IETF followed ensured the maximum amount of incompatibility. 
Really a completely independent stack.

In contrast, the IETF could easily have chose a path toward minimizing 
incompatibility that would have allowed IPv6 to interwork with IPv4, within the 
limitations of the v4 address space.

That is, the IETF could begun IPv6 by assigning to it IPv4 addresses, reserving 
the remainder for latter definition and allocation.  It could have targeted 
simple, basic reformatting at the IP level to permit early IPv6 adoption to 
require a minimal gateway for interworking with the IPv4 world.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From brian.e.carpenter@gmail.com  Mon Feb 13 16:38:36 2012
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 1E91F21F86D5 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.411
X-Spam-Level: 
X-Spam-Status: No, score=-103.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBI+PaMX+tkH for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:38:35 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC1621F868C for <ietf@ietf.org>; Mon, 13 Feb 2012 16:38:35 -0800 (PST)
Received: by iagf6 with SMTP id f6so5992504iag.31 for <ietf@ietf.org>; Mon, 13 Feb 2012 16:38:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WuBXX46xT4e5of8qaIjfbHqQ43SD1GxdJUrYah4s3W4=; b=qEdBhNK8MAZyq+kZ8hBzwgh3NRxTPGNGpEvkOlp0WuYnjkEKziU7dM7GzKg54Jdsrn rEWWbWXMkB9EOzGf/tEbdg8mZC9vusSO4cbhOhcV6RcrlUIkNMSbdrYPJCgyZVfmepv3 WQqEHwQrwFPkM/47UJtLDwDqW2vAuaKIdYu0A=
Received: by 10.50.178.106 with SMTP id cx10mr30708159igc.15.1329179915258; Mon, 13 Feb 2012 16:38:35 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id np10sm23281225igc.0.2012.02.13.16.38.32 (version=SSLv3 cipher=OTHER); Mon, 13 Feb 2012 16:38:34 -0800 (PST)
Message-ID: <4F39AD11.8080600@gmail.com>
Date: Tue, 14 Feb 2012 13:38:41 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com> <4F39AB80.7060400@dcrocker.net>
In-Reply-To: <4F39AB80.7060400@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:38:36 -0000

On 2012-02-14 13:32, Dave CROCKER wrote:
> 
> 
> On 2/13/2012 4:17 PM, Brian E Carpenter wrote:
>> People say this from time to time, but it's a complete myth.
> 
> well, not completely...
> 
> 
>> IPv4 provides no mechanism whatever for addresses greater than 32 bits.
>> Therefore, mathematically, there is no possible design for an IP with
>> bigger addresses that is transparently backwards compatible. We've known
>> that since at least 1992.
> 
> 
> The path that the IETF followed ensured the maximum amount of
> incompatibility. Really a completely independent stack.
> 
> In contrast, the IETF could easily have chose a path toward minimizing
> incompatibility that would have allowed IPv6 to interwork with IPv4,
> within the limitations of the v4 address space.
> 
> That is, the IETF could begun IPv6 by assigning to it IPv4 addresses,
> reserving the remainder for latter definition and allocation.  It could
> have targeted simple, basic reformatting at the IP level to permit early
> IPv6 adoption to require a minimal gateway for interworking with the
> IPv4 world.

There were very specific reasons why this was not done. And it doesn't
change the fact that an old-IP-only host cannot talk to a new-IP-only host
without a translator. It is that fact that causes our difficulties today.

    Brian

From dhc@dcrocker.net  Mon Feb 13 16:42:55 2012
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 622A921F8675 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.632
X-Spam-Level: 
X-Spam-Status: No, score=-6.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3R4ttDa8fyRc for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:42:54 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 859A021F8681 for <ietf@ietf.org>; Mon, 13 Feb 2012 16:42:54 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1E0glHF008312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Feb 2012 16:42:52 -0800
Message-ID: <4F39ADFD.7050202@dcrocker.net>
Date: Mon, 13 Feb 2012 16:42:37 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com> <4F39AB80.7060400@dcrocker.net> <4F39AD11.8080600@gmail.com>
In-Reply-To: <4F39AD11.8080600@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 13 Feb 2012 16:42:52 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:42:55 -0000

On 2/13/2012 4:38 PM, Brian E Carpenter wrote:
> There were very specific reasons why this was not done.

Is there a useful citation that covers this strategic decision?

Given that that decision was an essential part of what caused a roughly 15 year 
delay, it would be helpful to have it documented.


> And it doesn't
> change the fact that an old-IP-only host cannot talk to a new-IP-only host
> without a translator. It is that fact that causes our difficulties today.

The translator needed today is a complete gateway between two entirely 
incompatible protocols.  The one that I'm describing would have been a trivial 
re-formatter.

The development, deployment and interoperability differences between these is 
massive.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From randy@psg.com  Mon Feb 13 16:49:49 2012
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 638E221F870A for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3xNq2Aso7iu for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 16:49:49 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id F0A8921F8701 for <ietf@ietf.org>; Mon, 13 Feb 2012 16:49:48 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Rx6aZ-000LJZ-Lu; Tue, 14 Feb 2012 00:49:47 +0000
Date: Mon, 13 Feb 2012 16:49:47 -0800
Message-ID: <m2pqdijl1w.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
In-Reply-To: <4F39A81A.5020608@gmail.com>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:49:49 -0000

> IPv4 provides no mechanism whatever for addresses greater than 32 bits.
> Therefore, mathematically, there is no possible design for an IP with
> bigger addresses that is transparently backwards compatible. We've known
> that since at least 1992.

i guess you forget the discussion of variable length.  i hope we don't
have to rehash it here.

decisions were made.  some were quite bad.  v6 had some real zingers.
remember tla/nla?  no feature parity, such as dhcp (a war which has not
finished)?  it is almost as if it was designed to fail.

randy

From brian.e.carpenter@gmail.com  Mon Feb 13 19:09:18 2012
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 45DAE21F8709 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 19:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.415
X-Spam-Level: 
X-Spam-Status: No, score=-103.415 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8gKBdn1kFIf for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 19:09:17 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8AC7021F86EA for <ietf@ietf.org>; Mon, 13 Feb 2012 19:09:17 -0800 (PST)
Received: by iagf6 with SMTP id f6so6187686iag.31 for <ietf@ietf.org>; Mon, 13 Feb 2012 19:09:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=WJGVWa+gNLSC+Q3VOsqBoPgVznmWgDoOxaQGb4+BW1c=; b=L+1eEVdPkRnKz5fSJ55RzdZvUYuxdJSJ8mW0evS5wxpVPZsyPJD8TTlpNYHSQK89XW 5tNc/gibuCYyWlbT2WFIIY59m/VXTVATlHBUHhuZn9ZQF2kF91rFwzGf1fOPpI6Ryp7l BuJiKfZuhdC1zS0nwD7ANDU7br6UwL/9ZdW9g=
Received: by 10.50.155.170 with SMTP id vx10mr741816igb.22.1329188957075; Mon, 13 Feb 2012 19:09:17 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id uy10sm23931836igc.1.2012.02.13.19.09.14 (version=SSLv3 cipher=OTHER); Mon, 13 Feb 2012 19:09:16 -0800 (PST)
Message-ID: <4F39D062.206@gmail.com>
Date: Tue, 14 Feb 2012 16:09:22 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com> <4F39AB80.7060400@dcrocker.net> <4F39AD11.8080600@gmail.com> <4F39ADFD.7050202@dcrocker.net>
In-Reply-To: <4F39ADFD.7050202@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:09:18 -0000

On 2012-02-14 13:42, Dave CROCKER wrote:
> 
> 
> On 2/13/2012 4:38 PM, Brian E Carpenter wrote:
>> There were very specific reasons why this was not done.
> 
> Is there a useful citation that covers this strategic decision?

You may recall that at the time, we were very concerned about the
pre-CIDR growth rate in BGP and there was, iirc, a generalised
aversion to anything that would import the entire IPv4 BGP4 table
into IPv6. I don't recall without a lot of archive grepping whether
this was explicit in the IPng decision or whether it came a bit later.

> 
> Given that that decision was an essential part of what caused a roughly
> 15 year delay, it would be helpful to have it documented.
> 
> 
>> And it doesn't
>> change the fact that an old-IP-only host cannot talk to a new-IP-only
>> host
>> without a translator. It is that fact that causes our difficulties today.
> 
> The translator needed today is a complete gateway between two entirely
> incompatible protocols.  The one that I'm describing would have been a
> trivial re-formatter.
> 
> The development, deployment and interoperability differences between
> these is massive.

Honestly, having had an MSc student who benchmarked translation vs
application proxying vs native, I don't think so. The mechanics of
packet translation are trivial. The hard part is exactly the same as
with NAT44, caused by the shortage of IPv4 addresses and all the state
that goes with sharing the pool of transport ports for a single address.

On 2012-02-14 13:49, Randy Bush wrote:

> i guess you forget the discussion of variable length.  i hope we don't
> have to rehash it here.

I haven't forgotten. The worst row I ever had at an IETF meeting was
on that topic.

> decisions were made.  some were quite bad.  v6 had some real zingers.
> remember tla/nla?  no feature parity, such as dhcp (a war which has not
> finished)?  it is almost as if it was designed to fail.

DHCP for v4 was still wet behind the ears at that time, so this
wasn't as obvious then as it is now; there's a bit of 20/20 hindsight
here. But yes, we could of course have done better. Unfortunately my
time machine is broken.

    Brian

From mrex@sap.com  Mon Feb 13 19:29:37 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D0221F8754 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 19:29:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.121
X-Spam-Level: 
X-Spam-Status: No, score=-10.121 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iw2-+L1vpNPM for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 19:29:37 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id EAAD721F8733 for <ietf@ietf.org>; Mon, 13 Feb 2012 19:29:36 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1E3TUg9013498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2012 04:29:34 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202140329.q1E3TThE014618@fs4113.wdf.sap.corp>
Subject: Re: Backwards compatibility myth [Re: Last Call:
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Tue, 14 Feb 2012 04:29:29 +0100 (MET)
In-Reply-To: <4F39D062.206@gmail.com> from "Brian E Carpenter" at Feb 14, 12 04:09:22 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:29:37 -0000

Brian E Carpenter wrote:
> 
>Dave CROCKER wrote:
>> 
>> Brian E Carpenter wrote:
>>>
>>> There were very specific reasons why this was not done.
>> 
>> Is there a useful citation that covers this strategic decision?
> 
>You may recall that at the time, we were very concerned about the
>pre-CIDR growth rate in BGP and there was, iirc, a generalised
>aversion to anything that would import the entire IPv4 BGP4 table
>into IPv6. I don't recall without a lot of archive grepping whether
>this was explicit in the IPng decision or whether it came a bit later.

With the result that you have two independent routing tables
describing the entire internet instead of just one.  I do not see
a size benefit, only the possibility for seperate code so that
during development of IPv6, the old IPv4 code that carries the larger part
of the Internet traffic is subject to less changes and therefore
less new bugs.


> 
> > 
> > Given that that decision was an essential part of what caused a roughly
> > 15 year delay, it would be helpful to have it documented.
> > 
> > 
> >> And it doesn't
> >> change the fact that an old-IP-only host cannot talk to a new-IP-only
> >> host
> >> without a translator. It is that fact that causes our difficulties today.
> > 
> > The translator needed today is a complete gateway between two entirely
> > incompatible protocols.  The one that I'm describing would have been a
> > trivial re-formatter.
> > 
> > The development, deployment and interoperability differences between
> > these is massive.
> 
> Honestly, having had an MSc student who benchmarked translation vs
> application proxying vs native, I don't think so. The mechanics of
> packet translation are trivial. The hard part is exactly the same as
> with NAT44, caused by the shortage of IPv4 addresses and all the state
> that goes with sharing the pool of transport ports for a single address.

the difference in connection setup seems to huge, that folks
came up with the happy eyeballs proposal -- at an enormous cost
of change for apps that aren't multi-threaded or async multi-connect yet,
and extra load for the network and Server OS.

-Martin

From jnc@mercury.lcs.mit.edu  Mon Feb 13 19:53:21 2012
Return-Path: <jnc@mercury.lcs.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 063CA21E804A for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 19:53:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SmjRQ9A3405d for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 19:53:18 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 80B6F21E8043 for <ietf@ietf.org>; Mon, 13 Feb 2012 19:53:18 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1397C18C0D5; Mon, 13 Feb 2012 22:53:17 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
Message-Id: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu>
Date: Mon, 13 Feb 2012 22:53:17 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:53:21 -0000

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

    > The design error was made in the late 1970s, when Louis Pouzin's advice
    > that catenet addresses should be variable length, with a format prefix,
    > was not taken during the design of IPv4.

Ironically, TCP/IP had variable length addresses put in _twice_, and they were
removed both times! (You can't make this stuff up! :-)

- TCPv1 (no separate TCP and IP at that point) had variable lenth addresses
	of up to 15 4-bit nibbles

- TCP/IPv3 had variable lenth addresses of up to 15 8-bit bytes (but the
	'network number' part was supposed to be only the first byte, exactly
	like IPv4 in its early days)

This latter change happened shortly before I joined the project, otherwise no
doubt I would have strenously objected! :-)

	Noel

From mohta@necom830.hpcl.titech.ac.jp  Mon Feb 13 20:42:49 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3268C11E8076 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 20:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level: 
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10t-Xqgu4nhX for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 20:42:48 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 5632711E8075 for <ietf@ietf.org>; Mon, 13 Feb 2012 20:42:48 -0800 (PST)
Received: (qmail 43310 invoked from network); 14 Feb 2012 04:57:30 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 14 Feb 2012 04:57:30 -0000
Message-ID: <4F39E632.40200@necom830.hpcl.titech.ac.jp>
Date: Tue, 14 Feb 2012 13:42:26 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com> <4F39AB80.7060400@dcrocker.net> <4F39AD11.8080600@gmail.com>
In-Reply-To: <4F39AD11.8080600@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:42:49 -0000

Brian E Carpenter wrote:

> There were very specific reasons why this was not done. And it doesn't
> change the fact that an old-IP-only host cannot talk to a new-IP-only host
> without a translator. It is that fact that causes our difficulties today.

The fact is that an old-IP-only host can talk to a new-IP-only
host without a translator, if the new IP uses port numbers for
addressing/routing.

Though NAT is doing similar thing with translation, the
translation is not essential and can be reversed at end
systems using NAT information obtained through UPnP/PCP.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Mon Feb 13 20:51:31 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB03821E804A for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 20:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.075
X-Spam-Level: 
X-Spam-Status: No, score=-0.075 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6LPkakT0G-E for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 20:51:31 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id A711D21E8043 for <ietf@ietf.org>; Mon, 13 Feb 2012 20:51:30 -0800 (PST)
Received: (qmail 43392 invoked from network); 14 Feb 2012 05:06:25 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 14 Feb 2012 05:06:25 -0000
Message-ID: <4F39E849.90800@necom830.hpcl.titech.ac.jp>
Date: Tue, 14 Feb 2012 13:51:21 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120213165121.33C3618C14B@mercury.lcs.mit.edu> <4F396ECD.7040002@gmail.com>
In-Reply-To: <4F396ECD.7040002@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:51:31 -0000

Brian E Carpenter wrote:

> Sure, that's very common, but these devices are consumer electronics and
> will get gradually replaced by IPv6-supporting boxes as time goes on.

The problem is that IPv6 specification is still broken in
several ways to be not operational that existing boxes must
be replaced after the specification is fixed.

The more serious problem is that IPv6 people in IETF do
not admit IPv6 broken, which makes it impossible to fix
IPv6.

For an example, see my recent presentation at APOPS:

http://meetings.apnic.net/__data/assets/file/0018/38214/pathMTU.pdf

						Masataka Ohta

From rogerj@gmail.com  Tue Feb 14 00:16:13 2012
Return-Path: <rogerj@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 A73D921E8078 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 00:16:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level: 
X-Spam-Status: No, score=-3.001 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1G2Jc9jax4W for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 00:16:08 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id B1AC721E804D for <ietf@ietf.org>; Tue, 14 Feb 2012 00:16:06 -0800 (PST)
Received: by lahl5 with SMTP id l5so5538800lah.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 00:16:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Z8rhi+0r+lZpI54KJicS0K00/Unu/j3TcTlJg1mjYgY=; b=d9tXVE87jn43QkuND61w1GpliDL2wcTH12PuZfpU25RRUAO0EV0MmXygA5brxywubA iAz1/D+Xw/XQKeG9qDdT+0OjVtC3KKnIXbDHzQGM0zp9TGKVndPf5jF2I0piIcFC+4Y9 1gKtuzDgVudjlQCAdOSRhtGXTS4b/8IO3xIxI=
MIME-Version: 1.0
Received: by 10.112.85.233 with SMTP id k9mr6915192lbz.56.1329207363434; Tue, 14 Feb 2012 00:16:03 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Tue, 14 Feb 2012 00:16:03 -0800 (PST)
In-Reply-To: <20120213215230.B220B18C168@mercury.lcs.mit.edu>
References: <20120213215230.B220B18C168@mercury.lcs.mit.edu>
Date: Tue, 14 Feb 2012 09:16:03 +0100
Message-ID: <CAKFn1SFR4T-74+xjJM_3N0kmJfvrLjOpmrU4UuQMk41bN4uUkw@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: ietf@ietf.org, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 08:16:13 -0000

Sorry Noel but I choice to reply public to this one.

On Mon, Feb 13, 2012 at 10:52 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wr=
ote:
> =A0 =A0> IPv6 is The Key!
>
> If you think denying a CGN block will do anything at all to help IPv6,
> you're very confused.

quote out of context etc... but my change of mind from supporting this
draft to not supporting has nothing todo with IPv6 at all. Nothing.


It all boils down to RFC1918 space, there are 3 huge network blocks
there and double, tripple NAT work, just as well as CGN will (it will
break plenty of application either way).
* 10.0.0.0/8  ~16mill addresses
* 172.16.0.0/12  ~1mill addresses
* 192.168.0.0/16 ~65K addresses

I can't really see what difference another /10 will make really,
especially now that we're in essence out of IPv4 addresses. We're all
much better of with some pain  (address collision etc) during the
transition to IPv6 than to delay it even more.


And about your quote, yes we have to change to IPv6, there are at
currently no other options at all.

Sure there are plenty of not optimal design choice made, stupid things
(like we're wasting /64 due to EUI-64) etc etc, but that is an entire
other range of subject. Right now, we only have one real choice, move
to IPv6. Everything else is moving the pain around.





and for those that really really really want to continue to use IPv4,
well try to make 240/4 (E-class) usable... there you have an entire /4
instead of /10.
 240.0.0.0/4          Reserved for Future Use        [RFC1700, page 4]

I personally think that reservation should have been lifted years ago.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From rogerj@gmail.com  Tue Feb 14 00:24:21 2012
Return-Path: <rogerj@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 8B92E21E8048 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 00:24:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.038
X-Spam-Level: 
X-Spam-Status: No, score=-3.038 tagged_above=-999 required=5 tests=[AWL=0.261,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKYx2xhcQ-Xe for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 00:24:20 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id A9A9421E8027 for <ietf@ietf.org>; Tue, 14 Feb 2012 00:24:17 -0800 (PST)
Received: by lahl5 with SMTP id l5so5543906lah.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 00:24:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+Kj2EhIV7/3OqPcPpP+NiJogfICHf2pKzqy0308Ga8c=; b=SCnhtjbgNk89d08fyMMMSZGS0xj5KvEoEKXLJNQ+rrvWfw2Yt+cAw4zCyxgU9Ni1+S SfYcG0DXhmYaETKAbgLo+uJ3hs+raknrPxkJDVuMdZmN5p0Z3rYqjzAmGDmP4Z6htT0c aCN75Zto6HT6wW0ODgxd3xjvf1wESuXt3u674=
MIME-Version: 1.0
Received: by 10.112.85.233 with SMTP id k9mr6923859lbz.56.1329207856608; Tue, 14 Feb 2012 00:24:16 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Tue, 14 Feb 2012 00:24:16 -0800 (PST)
In-Reply-To: <4F39E849.90800@necom830.hpcl.titech.ac.jp>
References: <20120213165121.33C3618C14B@mercury.lcs.mit.edu> <4F396ECD.7040002@gmail.com> <4F39E849.90800@necom830.hpcl.titech.ac.jp>
Date: Tue, 14 Feb 2012 09:24:16 +0100
Message-ID: <CAKFn1SHvmfQzr4ZvrjPWQPGZ643Ee6tME4EZuFeOkk3gz5vq4Q@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 08:24:21 -0000

On Tue, Feb 14, 2012 at 5:51 AM, Masataka Ohta
<mohta@necom830.hpcl.titech.ac.jp> wrote:
> Brian E Carpenter wrote:
>
>> Sure, that's very common, but these devices are consumer electronics and
>> will get gradually replaced by IPv6-supporting boxes as time goes on.
>
> The problem is that IPv6 specification is still broken in
> several ways to be not operational that existing boxes must
> be replaced after the specification is fixed.
>
> The more serious problem is that IPv6 people in IETF do
> not admit IPv6 broken, which makes it impossible to fix
> IPv6.

Make a draft, gather your "supporters" and take that discussion on
6man wg. I'm sure there are people open to consider any arguments on
what's wrong/or not.

Either way, we're way passed changing any of the important parts of
IPv6. That has to be IPv6 v2 WITH backward compability to IPv6 (as we
currently know it).



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 14 01:11:38 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15B821F87B4 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 01:11:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.074
X-Spam-Level: 
X-Spam-Status: No, score=0.074 tagged_above=-999 required=5 tests=[AWL=-0.136,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aP32-kcPS7mk for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 01:11:38 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id B0FD421F8638 for <ietf@ietf.org>; Tue, 14 Feb 2012 01:11:37 -0800 (PST)
Received: (qmail 45312 invoked from network); 14 Feb 2012 09:25:53 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 14 Feb 2012 09:25:53 -0000
Message-ID: <4F3A251B.5050607@necom830.hpcl.titech.ac.jp>
Date: Tue, 14 Feb 2012 18:10:51 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: =?UTF-8?B?Um9nZXIgSsO4cmdlbnNlbg==?= <rogerj@gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <20120213165121.33C3618C14B@mercury.lcs.mit.edu> <4F396ECD.7040002@gmail.com> <4F39E849.90800@necom830.hpcl.titech.ac.jp> <CAKFn1SHvmfQzr4ZvrjPWQPGZ643Ee6tME4EZuFeOkk3gz5vq4Q@mail.gmail.com>
In-Reply-To: <CAKFn1SHvmfQzr4ZvrjPWQPGZ643Ee6tME4EZuFeOkk3gz5vq4Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 09:11:39 -0000

>> The more serious problem is that IPv6 people in IETF do
>> not admit IPv6 broken, which makes it impossible to fix
>> IPv6.
>
> Make a draft, gather your "supporters" and take that discussion on
> 6man wg. I'm sure there are people open to consider any arguments on
> what's wrong/or not.

Now, I'm tired of speaking with those who decided that IPv6
must be perfect.

They have been warned about 10 years ago.

Nowadays, I'm telling operators how IPv6 is broken to be
not operational.

> Either way, we're way passed changing any of the important parts of
> IPv6. That has to be IPv6 v2 WITH backward compability to IPv6 (as we
> currently know it).

A problem, maybe the worst operationally, of IPv6 is that IPv6
address is 16B, divine to remember, because of failed attempt
to have SLAAC.

As most operators are human, forget backward compatibility.

It is a lot easier for all the players to make IPv4 with NAT
end to end transparent.

					Masataka Ohta

From roberta.maglione@telecomitalia.it  Tue Feb 14 02:23:04 2012
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31FBD21F86EA; Tue, 14 Feb 2012 02:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.248
X-Spam-Level: 
X-Spam-Status: No, score=0.248 tagged_above=-999 required=5 tests=[AWL=0.967,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytzIAoNR8B2n; Tue, 14 Feb 2012 02:23:03 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by ietfa.amsl.com (Postfix) with ESMTP id 19EB321F85B8; Tue, 14 Feb 2012 02:23:03 -0800 (PST)
Received: from GRFHUB702BA020.griffon.local (10.188.101.112) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 14 Feb 2012 11:23:01 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by GRFHUB702BA020.griffon.local ([10.188.101.112]) with mapi; Tue, 14 Feb 2012 11:23:01 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Ben Campbell' <ben@nostrum.com>, Ted Lemon <Ted.Lemon@nominum.com>
Date: Tue, 14 Feb 2012 11:23:00 +0100
Subject: RE: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: Aczqk08e6IUgLj+qQM2pFobKJW9qmwAbyLQw
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FC5@GRFMBX704BA020.griffon.local>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
In-Reply-To: <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:23:04 -0000

Hello Ted and Bell,
 I tried to address both your comments by combining your proposals:
Basically I added the text suggested by Ted in the security considerations =
section and then I slightly modified the introduction in order to clarify t=
he applicability.
I've just posted version -04 that includes these changes together with the =
resolutions of some other comments we received during the review.
Please let me know if you have additional comments.
Thanks,
Regards,
Roberta

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]
Sent: luned=EC 13 febbraio 2012 22.06
To: Ted Lemon
Cc: Maglione Roberta; draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org; g=
en-art@ietf.org Review Team; The IETF; Henderickx, Wim (Wim); Ullio Mario
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03

On Feb 11, 2012, at 10:24 AM, Ted Lemon wrote:

>> [RM] The intention is to use this method only for environments with nati=
ve security mechanisms, such as the Broadband Access network. You are right=
 it is not clearly said in the document I can add the following sentence at=
 the end of the introduction in order to clarify this point:
>>
>> "This   mechanism is intended to be use in networks that already have na=
tive security mechanisms that provide sufficient protection against
>> spoofing of DHCP traffic."
>
> It's probably worth revisiting the purpose of this mechanism.   The probl=
em that we are trying to solve is that people are reluctant to implement DH=
CPFORCERENEW because it's possible that an off-link attacker could more acc=
urately guess the timing of DHCP renewal messages by first sending a DHCPFO=
RCERENEW.   The mechanism in RFC3315 (DHCPv6), which this document mirrors =
for DHCPv4, uses a nonce to prevent an off-link attacker from successfully =
triggering a renewal on a client by sending DHCPFORCERENEW; since the attac=
ker is off-link, it doesn't have the nonce, and can't force a renewal.
>
> An on-link attacker can always simply watch the DHCP renewal message go o=
ut and respond to it, so this mechanism is useless for preventing on-link a=
ttacks, and hence the security of the nonce in the case of on-link attacks =
isn't relevant.  So the above text isn't needed.   It's possible that the d=
ocument doesn't clearly document the use case for this functionality; if so=
, you are free to take the above paragraph, Roberta, and modify it to suit =
your purposes.   But I am against adding the text you proposed, because it =
excludes the bulk of use cases for the DHCPFORCERENEW nonce mechanism.

This is good information, and it would help to include it in the security c=
onsiderations. I meant (but failed) to  comment in my original review that =
the security considerations would benefit from a more detailed discussion a=
bout the properties of the mechanism, and what attacks or vulnerabilities i=
t is intended to mitigate. Your text above seems to do that.

>
>> [RM] This is because this mechanism relays on the authentication protoco=
l defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and there HMAC=
-MD5 is used.
>
> Essentially HMAC-MD5 is being used here to package a secret into a chunk =
of predictable size, and the fact that there are hacks for the mechanism is=
n't terribly important because the only attacker we are attempting to foil =
is one that doesn't have access to the cleartext or the ciphertext.

Do I infer correctly from your comment that the security properties of the =
mechanism don't really matter? That is, if the attacker we care about can't=
 eavesdrop in the first place, does this really need to be an HMAC?

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From daryl.tanner@blueyonder.co.uk  Tue Feb 14 06:19:42 2012
Return-Path: <daryl.tanner@blueyonder.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 2926521F875E for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5rOQqlcGLYj for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:19:41 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB7721F875A for <ietf@ietf.org>; Tue, 14 Feb 2012 06:19:41 -0800 (PST)
Received: by iagf6 with SMTP id f6so7102625iag.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 06:19:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.42.144.196 with SMTP id c4mr27857065icv.39.1329229181234; Tue, 14 Feb 2012 06:19:41 -0800 (PST)
Received: by 10.42.218.136 with HTTP; Tue, 14 Feb 2012 06:19:41 -0800 (PST)
X-Originating-IP: [92.239.43.71]
Date: Tue, 14 Feb 2012 14:19:41 +0000
Message-ID: <CAOw3xnbDd=rGajT4kw9s7tnhTkigvy5V+8O=5zxAfckFd3hZuQ@mail.gmail.com>
Subject: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Daryl Tanner <daryl.tanner@blueyonder.co.uk>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=90e6ba21224b2c2f9a04b8ed494e
X-Gm-Message-State: ALoCoQnCpGI+OAqx0ZDo8MUuNLh6B4Df5G2s/l/0L76E4gyyrhnT3YGMnBRTyB8cbaKQFj3vgaeM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:19:42 -0000

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

I support this updated draft, and I am keen for this to be published as a
BCP.

I believe the amendments in this revision clarify the usage and intended
purpose of the shared transition space.


Daryl

--90e6ba21224b2c2f9a04b8ed494e
Content-Type: text/html; charset=ISO-8859-1

I support this updated draft, and I am keen for this to be published as a BCP.<br><br>I believe the amendments in this revision clarify the usage and intended purpose of the shared transition space.<br><br><br>Daryl<br>

--90e6ba21224b2c2f9a04b8ed494e--

From dhc@dcrocker.net  Tue Feb 14 06:29:07 2012
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 42CD121F8677 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.331
X-Spam-Level: 
X-Spam-Status: No, score=-6.331 tagged_above=-999 required=5 tests=[AWL=-0.332, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Opq0zvS5dXr5 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:29:03 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5F97321F8629 for <ietf@ietf.org>; Tue, 14 Feb 2012 06:29:03 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1EESu4r027073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Feb 2012 06:29:01 -0800
Message-ID: <4F3A6F9D.3040303@dcrocker.net>
Date: Tue, 14 Feb 2012 06:28:45 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org> <4F39A81A.5020608@gmail.com> <4F39AB80.7060400@dcrocker.net> <4F39AD11.8080600@gmail.com> <4F39ADFD.7050202@dcrocker.net> <4F39D062.206@gmail.com>
In-Reply-To: <4F39D062.206@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 14 Feb 2012 06:29:01 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:29:07 -0000

On 2/13/2012 7:09 PM, Brian E Carpenter wrote:
> On 2012-02-14 13:42, Dave CROCKER wrote:
>>
>>
>> On 2/13/2012 4:38 PM, Brian E Carpenter wrote:
>>> There were very specific reasons why this was not done.
>>
>> Is there a useful citation that covers this strategic decision?
>
> You may recall that at the time, we were very concerned about the
> pre-CIDR growth rate in BGP and there was, iirc, a generalised
> aversion to anything that would import the entire IPv4 BGP4 table
> into IPv6.

So, an initial requirement that simply said "we need a larger address space" 
became "we need a larger address space, a new routing architecture, and a slew 
of other new mechanisms".

For an exercise like creating IPv6, this is called second system syndrome.[1] 
If often accounts for massive delays.  15 years qualifies.


>>> And it doesn't
>>> change the fact that an old-IP-only host cannot talk to a new-IP-only
>>> host
>>> without a translator. It is that fact that causes our difficulties today.
>>
>> The translator needed today is a complete gateway between two entirely
>> incompatible protocols.  The one that I'm describing would have been a
>> trivial re-formatter.
>>
>> The development, deployment and interoperability differences between
>> these is massive.
>
> Honestly, having had an MSc student who benchmarked translation vs
> application proxying vs native, I don't think so.

In theory, there is no difference between theory and practice...

By saying 'benchmarking' you appear to be referring to something like 
transformation time.  But notice that I gave a list that had nothing to do with 
cpu or i/o performance.

I fear that anyone who thinks that developing and operating a slightly enhanced 
router, such as I described, is the same as an application gateway probably does 
not understand the relative complexities or OA&M demands of either very well.


d/

[1][http://en.wikipedia.org/wiki/Second-system_effect
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jnc@mercury.lcs.mit.edu  Tue Feb 14 06:38:19 2012
Return-Path: <jnc@mercury.lcs.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 995B221F855D for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:38:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.426
X-Spam-Level: 
X-Spam-Status: No, score=-6.426 tagged_above=-999 required=5 tests=[AWL=0.173,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgSyZ42KZJIy for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:38:19 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1D0E321F8686 for <ietf@ietf.org>; Tue, 14 Feb 2012 06:38:19 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3DE2018C0CE; Tue, 14 Feb 2012 09:38:18 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Message-Id: <20120214143818.3DE2018C0CE@mercury.lcs.mit.edu>
Date: Tue, 14 Feb 2012 09:38:18 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:38:19 -0000

    > From: Roger Jorgensen <rogerj@gmail.com>

    > Sorry Noel but I choice to reply public to this one.

Ah, no, actually. Had you thought about it for a moment or two, you could
have realized that you could have made your point just as well without
publicly quoting my private email. But why am I not surprised?


    > It all boils down to RFC1918 space, there are 3 huge network blocks
    > there ... I can't really see what difference another /10 will make
    > really, especially now that we're in essence out of IPv4 addresses.

The issue is not whether it _can_ be made to work (in Milo's famous phrase,
'with enough thrust, anything will fly'). The issue is all about costs and
benefits.

Speaking of the costs, if we assign a block of size N, it's not as if N
people are not going to be able to get on the network as a result. To the
contrary, N*M people are going to be able to get on the network as a result.

Of course, the N would have had globally visible addresses, whereas the N*M
will not, but that dropoff in functionality does not seem to bother most
people: pretty much every wireless hub I've ever seen is also a NAT box. (I'm
not even sure if there's even a way to turn off the NAT functionality in the
one in our house - I don't recall one.) Given that most people are happy to
take the choice 'limited access is preferable to no access' in the wireless
case, I see no reason to doubt that they would, were they able to explicitly
make the choice, make the same choice here.

Allowing more people access to the Internet is a problem... how?

	Noel

From d3e3e3@gmail.com  Tue Feb 14 06:54:23 2012
Return-Path: <d3e3e3@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 EFAC621F8738 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.68
X-Spam-Level: 
X-Spam-Status: No, score=-103.68 tagged_above=-999 required=5 tests=[AWL=-1.082, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IzafY03+szL for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 06:54:23 -0800 (PST)
Received: from mail-lpp01m020-f172.google.com (mail-lpp01m020-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9C421F875B for <ietf@ietf.org>; Tue, 14 Feb 2012 06:54:22 -0800 (PST)
Received: by lbbgk8 with SMTP id gk8so3681122lbb.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 06:54:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9mrD5gxzbJJx8ajKVkdCEa+1jUYUGTwkE/R+UgdV4JM=; b=iBdqWhWc03HHjuf77SSch7Y0B7nB0B3LFIrlcpQwXVLnRdHANr9aFqcCcAq6PVq19k OybWrluMowDpb8FwAfLeWGNdVVP3zJgY0iO31qoDCKh6TTCEypmUi7EYaWWFuzfIwV16 MW9nzZ9xTa4/ri99BkEzQSuSvYMDPG1q/ORko=
MIME-Version: 1.0
Received: by 10.112.10.72 with SMTP id g8mr7667843lbb.12.1329231261957; Tue, 14 Feb 2012 06:54:21 -0800 (PST)
Received: by 10.112.88.42 with HTTP; Tue, 14 Feb 2012 06:54:21 -0800 (PST)
In-Reply-To: <CAOw3xnbDd=rGajT4kw9s7tnhTkigvy5V+8O=5zxAfckFd3hZuQ@mail.gmail.com>
References: <CAOw3xnbDd=rGajT4kw9s7tnhTkigvy5V+8O=5zxAfckFd3hZuQ@mail.gmail.com>
Date: Tue, 14 Feb 2012 09:54:21 -0500
Message-ID: <CAF4+nEERtpjGr33=f56rEuYf5PQO=w8p4HYvnTeiqghee5KiHg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Donald Eastlake <d3e3e3@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e0cb4efe3266317d1504b8edc583
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:54:24 -0000

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

I also support this draft.

Donald

On Tuesday, February 14, 2012, Daryl Tanner <daryl.tanner@blueyonder.co.uk>
wrote:
> I support this updated draft, and I am keen for this to be published as a
BCP.
>
> I believe the amendments in this revision clarify the usage and intended
purpose of the shared transition space.
>
>
> Daryl
>

-- 
Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

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

I also support this draft.<br><br>Donald<br><br>On Tuesday, February 14, 20=
12, Daryl Tanner &lt;<a href=3D"mailto:daryl.tanner@blueyonder.co.uk">daryl=
.tanner@blueyonder.co.uk</a>&gt; wrote:<br>&gt; I support this updated draf=
t, and I am keen for this to be published as a BCP.<br>
&gt;<br>&gt; I believe the amendments in this revision clarify the usage an=
d intended purpose of the shared transition space.<br>&gt;<br>&gt;<br>&gt; =
Daryl<br>&gt;<br><br>-- <br>Thanks,<br>Donald<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<br>
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)<br>=A0155 Beaver Str=
eet,=A0Milford, MA 01757 USA<br>=A0<a href=3D"mailto:d3e3e3@gmail.com" targ=
et=3D"_blank">d3e3e3@gmail.com</a><br>

--e0cb4efe3266317d1504b8edc583--

From ned+ietf@mauve.mrochek.com  Tue Feb 14 07:07:17 2012
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 5A36F21F87B1 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 07:07:17 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBiGaBYQPt8h for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 07:07:16 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 91E2221F87EF for <ietf@ietf.org>; Tue, 14 Feb 2012 07:07:16 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBYZWQRDK000SNQM@mauve.mrochek.com> for ietf@ietf.org; Tue, 14 Feb 2012 07:07:14 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBR11Q7E9S00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 14 Feb 2012 07:07:12 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OBYZWPJ4WM00ZUIL@mauve.mrochek.com>
Date: Tue, 14 Feb 2012 07:06:55 -0800 (PST)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
In-reply-to: "Your message dated Tue, 14 Feb 2012 14:19:41 +0000" <CAOw3xnbDd=rGajT4kw9s7tnhTkigvy5V+8O=5zxAfckFd3hZuQ@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <CAOw3xnbDd=rGajT4kw9s7tnhTkigvy5V+8O=5zxAfckFd3hZuQ@mail.gmail.com>
To: Daryl Tanner <daryl.tanner@blueyonder.co.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:07:17 -0000

> I support this updated draft, and I am keen for this to be published as a
> BCP.

+1

> I believe the amendments in this revision clarify the usage and intended
> purpose of the shared transition space.

+1

				Ned

From jeff.finkelstein@cox.com  Tue Feb 14 08:19:27 2012
Return-Path: <jeff.finkelstein@cox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD79421E800E for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 08:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUs2zZPLvOgV for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 08:19:27 -0800 (PST)
Received: from post6.cox.com (post6.cox.com [24.248.74.39]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5C521E8021 for <ietf@ietf.org>; Tue, 14 Feb 2012 08:19:22 -0800 (PST)
Received: from ([192.168.74.254]) by post6.cox.com with ESMTP with TLS id J041136114.29788302; Tue, 14 Feb 2012 11:19:16 -0500
Received: from CATL0MS102.corp.cox.com ([169.254.1.163]) by CATL0MS402.corp.cox.com ([10.62.236.89]) with mapi; Tue, 14 Feb 2012 11:19:15 -0500
From: <Jeff.Finkelstein@cox.com>
To: <ietf@ietf.org>
Date: Tue, 14 Feb 2012 11:19:12 -0500
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczrNEouFu3//fWiReu7u3yxqSNmNw==
Message-ID: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>
In-Reply-To: <01OBYZWPJ4WM00ZUIL@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:19:28 -0000

I support this draft as updated.


From sant9442@gmail.com  Tue Feb 14 08:31:25 2012
Return-Path: <sant9442@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 DE19A21E804D for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 08:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1TGL9+pyD1I for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 08:31:25 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF69921E8021 for <ietf@ietf.org>; Tue, 14 Feb 2012 08:31:24 -0800 (PST)
Received: by yhkk25 with SMTP id k25so113994yhk.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 08:31:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ovez9AZjltBzypwK6sM+GdN6aeTKG2AordKSVjh2t44=; b=TT8Un+jxl4n18lDBbFx3rt46fIPspJSlaeF4W5yfOymgc4XnO6TJEfkaMg03LIzOCk ZMvCqsIRNjvt4eOxdjMCOfGHpWGtQnmMvtJQJLNvIjYgUattLu6kzCq6Illp/V2HKhOM uwqxtLbUgFiNisth/vow8bLAl7lUHQwI7H+1M=
Received: by 10.236.155.225 with SMTP id j61mr27770590yhk.43.1329237084419; Tue, 14 Feb 2012 08:31:24 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id b2sm32124987anc.1.2012.02.14.08.31.21 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 14 Feb 2012 08:31:22 -0800 (PST)
Message-ID: <4F3A8C64.5070109@gmail.com>
Date: Tue, 14 Feb 2012 11:31:32 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Martin Rex <mrex@sap.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
In-Reply-To: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:31:26 -0000

+1.  One point I would like to make regarding not being encourage to 
move to IPv6, was increased when the RIRs established the new IPv4 
request "prove your need" policies.  It immediately strengthen the 
notion that we must keep our existing IPv4 Class C network because if 
we let it go, we might not be able to get it back.  If this policy was 
in place, when we first migrated to the net in the 90s', I could 
easily see a problem of being denied or hassled enough to show why our 
then new business plan should be enough.

IOW, the RIR policies only strengthen existing companies to be very 
careful about migrating to IPv6, which in itself is inherently complex 
and still long time. IPv4 is still required for reachability during 
any migration period which seems to me will be a very very long time.

Of course, a HDTV industry lobby can force federal legislation to 
force the migration and new equipment to be IPv6 ready.  But TVs is a 
consumer market mostly. With IP, its commercial interest as well, and 
there will be resistance if there is a major cost involved to make the 
change - or at least some federal subsidy will be demanded if its 
going to be forced.

Ma Bell did it right when they changed from 7 digit local calls to 
requiring the 10 digits today for new local area codes.  And this was 
before customers were legally allowed to "own" their phone numbers for 
life, make it transferable. I'm sure the ideal forward thinker at Ma 
Bell would of said, "If we are changing it number to 10, why not get 
ready and make it 16 or 20?"  I think that would be been harder to do 
to make that change. 10 was good because it was already part of the 
people's mindset to make the non-local call.  Not the same analogy of 
course, its possible to add more digits to reach any end-phone.  Not 
possible with IPv4 unless a port is used which is the only possible 
extension to it.

Anyway, I agree with your points regarding the realities.  IPv6 is a 
costly endeavor, IPv4 with NATs is what people are using at all 
levels, consumers and business, simply because of cost and it allows 
people to continue to operate at all levels.

--
HLS

Martin Rex wrote:
> Brian E Carpenter wrote:
>> On 2012-02-14 05:51, Noel Chiappa wrote:
>>>     > From: Arturo Servin <arturo.servin@gmail.com>
>>>
>>>     >> Are you volunteering to buy everyone on earth a new CPE? If not, who
>>>     >> do you suggest will?
>>>
>>>     > I suggest the ISPs, they are charging for the service, right?
>>>
>>> Lots of CPE is actually owned by the customers, not the ISPs. E.g. in our
>>> house, both our cable modem and the router attached to it are ours.
>> Sure, that's very common, but these devices are consumer electronics and
>> will get gradually replaced by IPv6-supporting boxes as time goes on.
>> (That is not hand-waving, the generation of boxes with IPv6 support is
>> starting to appear.) Nobody, I think, is denying that there will be a long
>> period of coexistence as a result.
>>
>> That is a separate question from this draft, which gives ISPs space for
>> *growing* their IPv4 customer base. I think that is what upsets people.
> 
> 
> The problem of ISP not newly shipping CPE that is not IPv6 capable
> needs to be addressed by regulatory power (legistation), rather than
> by ignorance of the part of the IETF.
> 
> 
> ISPs *growing* their IPv4 customer base is a natural side effect
> whenever ISPs allow customers to use equipment that they already
> have (and might have been using with a different ISP before).
> 
> 
> The vast majority of customers does not know or care about not having IPv6,
> because there is _very_ few equipment that is vitally dependent on IPv6,
> vs. huge amounts of equiment that requires IPv4.  If I had a CPE that
> supported IPv6 (mine is from early 2006 an IPv4-only), my concern would
> be how to reliably switch IPv6 off, because of the unsolved security and
> privacy problems that IPv6 brings along.
> 
> 
> It was the IETFs very own decision to build IPv6 in a fashion that it is
> not transparently backwards compatible with IPv4.  If the is anyone to
> blame for the current situation, than it is the IETF, not the consumers
> or the ISPs (except for those folks at ISPs who participated in the
> development of IPv6).
> 
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From owen@delong.com  Mon Feb 13 11:09:56 2012
Return-Path: <owen@delong.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B52EA21F86FA for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 11:09: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=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nwpExRabp32 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 11:09:55 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 45F0F21F8712 for <ietf@ietf.org>; Mon, 13 Feb 2012 11:09:54 -0800 (PST)
Received: from [IPv6:2620::930:0:ca2a:14ff:fe3e:d024] ([IPv6:2620:0:930:0:ca2a:14ff:fe3e:d024]) (authenticated bits=0) by owen.delong.com (8.14.1/8.14.1) with ESMTP id q1DJ5xMQ014854 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 13 Feb 2012 11:06:02 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com q1DJ5xMQ014854
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1329159962; bh=KphZ95XzEHgy7krzh4it4fzJNGE=; h=Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=Lal/6LGGnhUDDWSW8Mf1sQTwkPDVxuT3B8x2vFAxv6eCNWyBj5nR4glgrscR1V+ar OHisgnBZyPP3LT7kO7E52PQXhQ6n3zkzI3lyKdG61rR/ChRQGe99PRKYRJ50TLUrOt YHKaGdOkqwlswqqmvuM9mhrmRsrpVh/ZeXg91wkM=
Subject: Re: Another last call for draft-weil
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_014BCB8D-EF27-4D56-BD31-699A7E1EA2BF"
From: Owen DeLong <owen@delong.com>
In-Reply-To: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com>
Date: Mon, 13 Feb 2012 11:05:59 -0800
Message-Id: <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1251.1)
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (owen.delong.com [IPv6:2620:0:930::200:2]); Mon, 13 Feb 2012 11:06:02 -0800 (PST)
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: "draft-bdgks-arin-shared-transition-space@tools. org" <draft-bdgks-arin-shared-transition-space@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:09:56 -0000

--Apple-Mail=_014BCB8D-EF27-4D56-BD31-699A7E1EA2BF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I support draft-weil as revised. There is a vital need for this to move =
forward and the IETF should stop standing in the way and let ARIN =
allocate the space already.

Owen

On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote:

> Fellow BDGKS Authors,
>=20
> FYI: draft-weil is in another Last Call following an update that was =
requested by IESG Ads (on their December telechat, some ADs asked us to =
turn our request into a request for more 1918 space, but with a few =
caveats to home router manufacturers about not breaking when exposed to =
a CGN environment.). At this point we don't expect to change any minds. =
Basically everyone who is against the draft has spoken up. Now it is =
just a numbers game, we need to demonstrate significant support for the =
draft.
>=20
> If you do support this I-D and the allocation of the /10 for shared =
CGN use, please consider posting a statement of support.  Something as =
simple as "I support this draft as updated" or "I think the updated =
draft is more flexible, and would satisfy additional use cases that =
don't work with RFC1918 space" would be very helpful.
>=20
> You can respond to the "Last Call: =
<draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 =
Prefix for Shared Address Space) to BCP" thread or post individually to  =
ietf@ietf.org. Also, please feel free to encourage anyone else you know =
who supports the draft to make a similar post. Every statement we can =
gather is vital right now. Last call ends on Thursday, so reply's must =
be made before then. Thank you.
>=20
> Cheers,
> ~Chris


--Apple-Mail=_014BCB8D-EF27-4D56-BD31-699A7E1EA2BF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I =
support draft-weil as revised. There is a vital need for this to move =
forward and the IETF should stop standing in the way and let ARIN =
allocate the space =
already.<div><br></div><div>Owen</div><div><br><div><div>On Feb 13, =
2012, at 10:09 AM, Chris Grundemann wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: =
14px; font-family: Calibri, sans-serif; "><div>Fellow BDGKS =
Authors,</div><div><br></div><div><div style=3D"font-size: 14px; =
font-family: Calibri, sans-serif; ">FYI: draft-weil is in another Last =
Call following an update that was requested by IESG Ads&nbsp;(o<span =
class=3D"Apple-style-span" style=3D"font-size: medium; font-family: =
Calibri; ">n their December telechat, some ADs asked us to turn =
our&nbsp;</span><span class=3D"Apple-style-span" style=3D"font-family: =
Consolas; font-size: medium; "><span style=3D"font-family: Calibri; =
">request into a request for more 1918 space, but with a few caveats to =
home&nbsp;</span><span class=3D"Apple-style-span" style=3D"font-size: =
14px; font-family: Calibri, sans-serif; "><span class=3D"Apple-style-span"=
 style=3D"font-size: medium; font-family: Calibri; ">router =
manufacturers about not breaking when exposed to a CGN =
environment.)</span>. At this point we don't expect to change any minds. =
Basically everyone who is against the draft has spoken up. Now it is =
just a numbers game, we need to demonstrate significant support for the =
draft.</span></span></div><div style=3D"font-size: 14px; font-family: =
Calibri, sans-serif; "><br></div><div style=3D"font-size: 14px; =
font-family: Calibri, sans-serif; ">If you do support this I-D and the =
allocation of the /10 for shared CGN use, please consider posting a =
statement of support. &nbsp;<span class=3D"Apple-style-span" =
style=3D"font-family: Consolas; font-size: medium; "><span =
style=3D"font-family: Calibri; ">Something as simple as "I support this =
draft as updated" or "I think&nbsp;</span><span style=3D"font-family: =
Calibri; ">the updated draft is more flexible, and would satisfy =
additional use cases&nbsp;that don't work with RFC1918 space" would be =
very helpful.</span></span></div><div style=3D"font-size: 14px; =
font-family: Calibri, sans-serif; "><span class=3D"Apple-style-span" =
style=3D"font-family: Consolas; font-size: medium; "><span =
style=3D"font-family: Calibri; "><br></span></span></div><div =
style=3D"font-size: 14px; font-family: Calibri, sans-serif; ">You can =
respond to the "<span class=3D"Apple-style-span" style=3D"font-size: =
28px; font-family: Calibri; "><span id=3D":x0" class=3D"hP"><font =
class=3D"Apple-style-span" size=3D"3">Last Call: =
&lt;draft-wei<wbr>l-shared-t<wbr>ransition-<wbr>space-requ<wbr>est-14.txt<=
wbr>&gt; (IANA Reserved IPv4 Prefix for Shared Address Space) to =
BCP</font></span><span class=3D"Apple-style-span" style=3D"font-size: =
14px; font-family: Calibri, sans-serif; ">" thread or post individually =
to&nbsp;&nbsp;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>. Also, =
please feel free to encourage anyone else you know who supports the =
draft to make a similar post. Every statement we can gather is vital =
right now. Last call ends on Thursday, so reply's must be made before =
then. Thank you.</span></span></div><div style=3D"font-size: 14px; =
font-family: Calibri, sans-serif; "><span class=3D"Apple-style-span" =
style=3D"font-size: 28px; font-family: Calibri; "><span =
class=3D"Apple-style-span" style=3D"font-size: 14px; font-family: =
Calibri, sans-serif; "><br></span></span></div><div style=3D"font-size: =
14px; font-family: Calibri, sans-serif; "><span class=3D"Apple-style-span"=
 style=3D"font-size: 28px; font-family: Calibri; "><span =
class=3D"Apple-style-span" style=3D"font-size: 14px; font-family: =
Calibri, sans-serif; ">Cheers,</span></span></div><div style=3D"font-size:=
 14px; font-family: Calibri, sans-serif; "><span =
class=3D"Apple-style-span" style=3D"font-size: 28px; font-family: =
Calibri; "><span class=3D"Apple-style-span" style=3D"font-size: 14px; =
font-family: Calibri, sans-serif; =
">~Chris</span></span></div></div></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail=_014BCB8D-EF27-4D56-BD31-699A7E1EA2BF--

From ben@nostrum.com  Mon Feb 13 12:37:16 2012
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 0878A21E802A; Mon, 13 Feb 2012 12:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTR9jmPo2784; Mon, 13 Feb 2012 12:37:15 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 049A221E8029; Mon, 13 Feb 2012 12:37:14 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1DKbCd5031086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 14:37:13 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
Date: Mon, 13 Feb 2012 14:37:26 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A76A706-9B9C-4911-A4E6-AEC187385557@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: "'Henderickx, Wim \(Wim\)'" <wim.henderickx@alcatel-lucent.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:37:16 -0000

Hi, thanks for the response. See additional comments inline. (I removed =
sections for which no further comment seems necessary)

On Feb 10, 2012, at 7:52 AM, Maglione Roberta wrote:

[...]

>=20
> -- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.
>=20
> [RM] The intention is to use this method only for environments with =
native security mechanisms, such as the Broadband Access network. You =
are right it is not clearly said in the document I can add the following =
sentence at the end of the introduction in order to clarify this point:
>=20
> "This   mechanism is intended to be use in networks that already have =
native security mechanisms that provide sufficient protection against
> spoofing of DHCP traffic."

That helps, although I would suggest an additional sentence mentioning =
the specific risk in using it in environments without sufficient =
protection. I note, however, that Ted objected to this in a separate =
email--I will reply there as well.

>=20
>=20
> I think some additional text in (perhaps in the security =
considerations) is needed to explain either why the vulnerability to =
eavesdroppers is either okay in general, or limits the mechanism's use =
to environment where it is okay. It also seems like that, in the best =
case, this mechanism proves only that a Forcerenew request comes from =
the same DHCP server as in the original transaction, but otherwise does =
not prove anything about the identity of that server. If so, it would be =
worth mentioning it.
>=20
> [RM] That's correct this mechanism only proves only that a Forcerenew =
request comes from the same DHCP server: let me say this is a trade off =
between the total security provided by RFC 3118 and no security at all. =
In addition this method relays on the same mechanism already used for =
DHCPv6 Reconfigure message

Understood, and your suggested text from the previous comment mitigates =
this a bit. It would help to include text describing exactly what =
security properties you expect from the mechanism. (e.g. Proving (with =
limitations) that Forcerenew requests come from the same server as the =
original transaction response, etc.)

>=20
> -- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)
> [RM] This is because this mechanism relays on the authentication =
protocol defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and =
there HMAC-MD5 is used.

RFC 3315 was published in 2003. I'm not sure the general impression of =
HMACMD5 is the same now as it was in 2003. For example, =
http://www.ietf.org/mail-archive/web/cfrg/current/msg01197.html . I'm =
willing to accept that HMACMD5 is perfectly okay for this application, =
but it would be good to document more motivation than the fact it was =
used in 3315. If 3315 was being written today, would they use it? Is =
matching 3315 an important goal? I'm more interested in whether HMACMD5 =
is adequate for this particular use case based on today's knowledge =
about possible vulnerabilities or operational issues.

[I mentioned in my original review that I think this draft should get a =
SecDir review. They could certainly access whether hmacmd5 is an issue =
better than I can.]

>=20
> *** Minor issues:
>=20

[...]

>=20
> -- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."
>=20
> Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?
>=20
> [RM] For backward compatibility: if the client did not indicate its =
capability for this feature it means it is a legacy client and it does =
not support it, so the server should not send the nonce to this client

The text is not talking about sending the nonce--it's talking about =
sending the FORCERENEW_NONCE_CAPABLE option. Unless I read it wrong, it =
is saying the server SHOULD not advertise support unless the client has =
already indicated support.

>=20
> -- section 3.1.3, 5th paragraph: "...  computes an HMAC-MD5 of the =
Forcerenew message using the Forcerenew nonce ."
>=20
> Using it how? Is it the secret key for the HMAC calculation? (If so, =
why aren't we calling it a "key" in the first place?)
> [RM] based on the procedure specified in section 21.5 of RFC 3315

It would help to say that in the text.

[...]

>=20
>=20
> -- section 3.1.4, 4th paragraph: ".
> the client computes an HMAC-MD5 over the DHCP Forcerenew message, =
using the Forcerenew Nonce ."
>=20
> Using it how?
> [RM] based on the procedure specified in section 21.5 of RFC 3315
>=20

It would help to say that in the text.

> -- section 6:
>=20
> You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)
>=20

You did not address this in your response. I think the "why is this =
okay" part is probably covered by other discussion, but the "do they =
really need to be MitM" question remains.


[...]=

From ben@nostrum.com  Mon Feb 13 13:06:07 2012
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 DBBE921E8012; Mon, 13 Feb 2012 13:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iXXocE7lCV4m; Mon, 13 Feb 2012 13:06:06 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id E77B321E8022; Mon, 13 Feb 2012 13:06:05 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1DL62Q6035903 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 15:06:02 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com>
Date: Mon, 13 Feb 2012 15:06:16 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:06:07 -0000

On Feb 11, 2012, at 10:24 AM, Ted Lemon wrote:

>> [RM] The intention is to use this method only for environments with =
native security mechanisms, such as the Broadband Access network. You =
are right it is not clearly said in the document I can add the following =
sentence at the end of the introduction in order to clarify this point:
>>=20
>> "This   mechanism is intended to be use in networks that already have =
native security mechanisms that provide sufficient protection against
>> spoofing of DHCP traffic."
>=20
> It's probably worth revisiting the purpose of this mechanism.   The =
problem that we are trying to solve is that people are reluctant to =
implement DHCPFORCERENEW because it's possible that an off-link attacker =
could more accurately guess the timing of DHCP renewal messages by first =
sending a DHCPFORCERENEW.   The mechanism in RFC3315 (DHCPv6), which =
this document mirrors for DHCPv4, uses a nonce to prevent an off-link =
attacker from successfully triggering a renewal on a client by sending =
DHCPFORCERENEW; since the attacker is off-link, it doesn't have the =
nonce, and can't force a renewal.
>=20
> An on-link attacker can always simply watch the DHCP renewal message =
go out and respond to it, so this mechanism is useless for preventing =
on-link attacks, and hence the security of the nonce in the case of =
on-link attacks isn't relevant.  So the above text isn't needed.   It's =
possible that the document doesn't clearly document the use case for =
this functionality; if so, you are free to take the above paragraph, =
Roberta, and modify it to suit your purposes.   But I am against adding =
the text you proposed, because it excludes the bulk of use cases for the =
DHCPFORCERENEW nonce mechanism.

This is good information, and it would help to include it in the =
security considerations. I meant (but failed) to  comment in my original =
review that the security considerations would benefit from a more =
detailed discussion about the properties of the mechanism, and what =
attacks or vulnerabilities it is intended to mitigate. Your text above =
seems to do that.

>=20
>> [RM] This is because this mechanism relays on the authentication =
protocol defined in section 21.5 of RFC 3315 for DHCPv6 Reconfigure and =
there HMAC-MD5 is used.
>=20
> Essentially HMAC-MD5 is being used here to package a secret into a =
chunk of predictable size, and the fact that there are hacks for the =
mechanism isn't terribly important because the only attacker we are =
attempting to foil is one that doesn't have access to the cleartext or =
the ciphertext.

Do I infer correctly from your comment that the security properties of =
the mechanism don't really matter? That is, if the attacker we care =
about can't eavesdrop in the first place, does this really need to be an =
HMAC?=

From Ted.Lemon@nominum.com  Mon Feb 13 13:21:34 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F30B21E8038; Mon, 13 Feb 2012 13:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.523
X-Spam-Level: 
X-Spam-Status: No, score=-106.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AXwrF-XhHwXh; Mon, 13 Feb 2012 13:21:33 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 741C021E802A; Mon, 13 Feb 2012 13:21:33 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTzl+3AWBTH+ZBzbE8y6S311ALaG6upRI@postini.com; Mon, 13 Feb 2012 13:21:33 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6C0861B81E4; Mon, 13 Feb 2012 13:21:32 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 63025190052; Mon, 13 Feb 2012 13:21:32 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Mon, 13 Feb 2012 13:21:32 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AQHM5SWUy8EqSdK3C0aOhQFr8l21aJY2slwAgAG8tQCAA3NmAIAABEKA
Date: Mon, 13 Feb 2012 21:21:32 +0000
Message-ID: <EADDD673-E8FF-4579-9996-1E15C8933A70@nominum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
In-Reply-To: <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_EADDD673E8FF457999961E15C8933A70nominumcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:21:34 -0000

--_000_EADDD673E8FF457999961E15C8933A70nominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:
Do I infer correctly from your comment that the security properties of the =
mechanism don't really matter? That is, if the attacker we care about can't=
 eavesdrop in the first place, does this really need to be an HMAC?

Hm, I thought about that a bit more after I wrote my response.   The HMAC a=
llows us to avoid sending the nonce in the clear in the DHCPFORCERENEW.   I=
 don't think this adds any value from a security perspective, actually, eve=
n though it feels more comfortable.   I suspect it was put in in the origin=
al version simply because of that=97why send a secret over the wire when yo=
u don't have to?   However, the original motivation for using the mechanism=
 from RFC3315 was to avoid defining a new mechanism for a legacy protocol. =
  If we do need to change it, it's going to require a major rework of the d=
ocument, and a lot of delay, so if it causes no harm, I think that's not wo=
rth doing.

I too would like to see the text I proposed added to the security considera=
tions, so that we can be clear about what is being accomplished with this d=
raft.


--_000_EADDD673E8FF457999961E15C8933A70nominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <7B06EB66C931E64DA8CFADC779C71AD5@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Do
 I infer correctly from your comment that the security properties of the me=
chanism don't really matter? That is, if the attacker we care about can't e=
avesdrop in the first place, does this really need to be an HMAC?</span></b=
lockquote>
</div>
<br>
<div>Hm, I thought about that a bit more after I wrote my response. &nbsp; =
The HMAC allows us to avoid sending the nonce in the clear in the DHCPFORCE=
RENEW. &nbsp; I don't think this adds any value from a security perspective=
, actually, even though it feels more comfortable.
 &nbsp; I suspect it was put in in the original version simply because of t=
hat=97why send a secret over the wire when you don't have to? &nbsp; Howeve=
r, the original motivation for using the mechanism from RFC3315 was to avoi=
d defining a new mechanism for a legacy protocol.
 &nbsp; If we do need to change it, it's going to require a major rework of=
 the document, and a lot of delay, so if it causes no harm, I think that's =
not worth doing.</div>
<div><br>
</div>
<div>I too would like to see the text I proposed added to the security cons=
iderations, so that we can be clear about what is being accomplished with t=
his draft.</div>
<div><br>
</div>
</body>
</html>

--_000_EADDD673E8FF457999961E15C8933A70nominumcom_--

From ben@nostrum.com  Mon Feb 13 13:25:15 2012
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 4ABD421E803A; Mon, 13 Feb 2012 13:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLuApz9pbQM9; Mon, 13 Feb 2012 13:25:14 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 71D0F21E8038; Mon, 13 Feb 2012 13:25:14 -0800 (PST)
Received: from dn3-53.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1DLP3Fp038815 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Feb 2012 15:25:08 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758"
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <EADDD673-E8FF-4579-9996-1E15C8933A70@nominum.com>
Date: Mon, 13 Feb 2012 15:25:01 -0600
Message-Id: <D332B6D7-8855-44EE-8952-CACACCFE211D@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com> <EADDD673-E8FF-4579-9996-1E15C8933A70@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:25:15 -0000

--Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Feb 13, 2012, at 3:21 PM, Ted Lemon wrote:

> On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:
>> Do I infer correctly from your comment that the security properties =
of the mechanism don't really matter? That is, if the attacker we care =
about can't eavesdrop in the first place, does this really need to be an =
HMAC?
>=20
> Hm, I thought about that a bit more after I wrote my response.   The =
HMAC allows us to avoid sending the nonce in the clear in the =
DHCPFORCERENEW.   I don't think this adds any value from a security =
perspective, actually, even though it feels more comfortable.   I =
suspect it was put in in the original version simply because of that=97why=
 send a secret over the wire when you don't have to?   However, the =
original motivation for using the mechanism from RFC3315 was to avoid =
defining a new mechanism for a legacy protocol.   If we do need to =
change it, it's going to require a major rework of the document, and a =
lot of delay, so if it causes no harm, I think that's not worth doing.

I concur it's probably not worth changing at this point--but it does =
inform the "is MD5 good enough" discussion, which might make it worth =
mentioning in the security considerations.

>=20
> I too would like to see the text I proposed added to the security =
considerations, so that we can be clear about what is being accomplished =
with this draft.
>=20


--Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Feb 13, 2012, at 3:21 PM, Ted Lemon wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<div>
<div>On Feb 13, 2012, at 4:06 PM, Ben Campbell wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Do
 I infer correctly from your comment that the security properties of the =
mechanism don't really matter? That is, if the attacker we care about =
can't eavesdrop in the first place, does this really need to be an =
HMAC?</span></blockquote>
</div>
<br>
<div>Hm, I thought about that a bit more after I wrote my response. =
&nbsp; The HMAC allows us to avoid sending the nonce in the clear in the =
DHCPFORCERENEW. &nbsp; I don't think this adds any value from a security =
perspective, actually, even though it feels more comfortable.
 &nbsp; I suspect it was put in in the original version simply because =
of that=97why send a secret over the wire when you don't have to? &nbsp; =
However, the original motivation for using the mechanism from RFC3315 =
was to avoid defining a new mechanism for a legacy protocol.
 &nbsp; If we do need to change it, it's going to require a major rework =
of the document, and a lot of delay, so if it causes no harm, I think =
that's not worth doing.</div></div></blockquote><div><br></div><div>I =
concur it's probably not worth changing at this point--but it does =
inform the "is MD5 good enough" discussion, which might make it worth =
mentioning in the security considerations.</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>I too would like to see the text I proposed added to the security =
considerations, so that we can be clear about what is being accomplished =
with this draft.</div>
<div><br>
</div>
</div>

</blockquote></div><br></body></html>=

--Apple-Mail=_FD17B377-A142-41D5-8A0D-80B8A1583758--

From gdaley@au.logicalis.com  Mon Feb 13 18:58:05 2012
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7908821F8721 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 18:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level: 
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USXIFbHISwMa for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2012 18:58:04 -0800 (PST)
Received: from mail.syd.netstarnetworks.com (mail.syd.netstarnetworks.com [203.8.7.220]) by ietfa.amsl.com (Postfix) with ESMTP id 5074921F871E for <ietf@ietf.org>; Mon, 13 Feb 2012 18:58:03 -0800 (PST)
Received: from sdcexchht.netstarnetworks.com ([10.18.193.63]) by mail.syd.netstarnetworks.com (8.12.8/8.12.8) with ESMTP id q1E2vrt3019236 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 14 Feb 2012 13:57:58 +1100
Received: from SDCEXCHMS.netstarnetworks.com ([fe80::38ec:ea79:f4c9:acd6]) by sdcexchht.netstarnetworks.com ([::1]) with mapi; Tue, 14 Feb 2012 13:57:43 +1100
From: Greg Daley <gdaley@au.logicalis.com>
To: "'Randy Bush'" <randy@psg.com>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
Date: Tue, 14 Feb 2012 13:57:41 +1100
Subject: RE: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
Thread-Topic: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
Thread-Index: AczqspOJDrWvksLbSyCQ7LIeE80shgADsagw
Message-ID: <8155FD1BB2ABCD40AC6F8149BBE997E003AF8FDB619E@sdcexchms.netstarnetworks.com>
References: <201202132046.q1DKk1hN020697@fs4113.wdf.sap.corp> <20120213220627.567361D3CFB3@drugs.dv.isc.org>	<4F39A81A.5020608@gmail.com> <m2pqdijl1w.wl%randy@psg.com>
In-Reply-To: <m2pqdijl1w.wl%randy@psg.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: "'ietf@ietf.org'" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:58:05 -0000

Hi Randy and Brian,=20

I am sure the discussion of the discussion has been had before, but:
=20
> > IPv4 provides no mechanism whatever for addresses greater than 32 bits.
> > Therefore, mathematically, there is no possible design for an IP with
> > bigger addresses that is transparently backwards compatible. We've
> > known that since at least 1992.
>=20
> i guess you forget the discussion of variable length.  i hope we don't ha=
ve to
> rehash it here.
>=20
> decisions were made.  some were quite bad.  v6 had some real zingers.
> remember tla/nla?  no feature parity, such as dhcp (a war which has not
> finished)?  it is almost as if it was designed to fail.
>=20
> randy

I think that the compatibility issue is a key reason why adoption has been =
difficult.

Others are:=20

No compelling IPv6 only features
-> From my reading several key features were directed at IPv6 only original=
ly, like IPsec.  Successive works to provided all non-address IPv6 features=
 in IPv4.
-> This in part is being addressed by helpful capabilities such as DHCPv6PD=
 (although we could kill things entirely by back porting this to IPv4 ;-)

No local use benefit
-> Ostensibly deploying IPv6 only gets you (slightly) more work.=20
-> compare this to transformative technologies such as Ethernet and IPv4, w=
hich had a better price point and enabled new local capabilities, which did=
 not rely on neighbours adopting the same protocol.

Of course, these are short-sighted analysis.

Being able to uniquely address a peer device is a key benefit which we will=
 see drive adoption once 103.X/8 is gone.

Another key benefit is local addressability which handles organizational me=
rges/changes/private peering with ULAs (resolves the RFC-1918 collision pro=
blem).

For a few years I have been involved in an extremely pragmatic market where=
 people want to see the money they will save by deploying a networking tech=
nology.  What would get my customers adopting would be a compelling TCO arg=
ument.

Sincerely,

Greg Daley=20
Solutions Architect
Logicalis Australia Pty Ltd
gdaley@au.logicalis.com
t +61 3 8532 4042
m +61 401 772 770

From Ted.Lemon@nominum.com  Tue Feb 14 05:52:58 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF07C21F869D; Tue, 14 Feb 2012 05:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.625
X-Spam-Level: 
X-Spam-Status: No, score=-105.625 tagged_above=-999 required=5 tests=[AWL=-0.830, BAYES_00=-2.599, HTML_MESSAGE=0.001, LONGWORDS=1.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MVobxRrWo+0S; Tue, 14 Feb 2012 05:52:53 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id AD0C721F8602; Tue, 14 Feb 2012 05:52:50 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTzpnL5yiqIkdgypuBVSLf6UZjEJ4Esot@postini.com; Tue, 14 Feb 2012 05:52:51 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 11D6C1B82FC; Tue, 14 Feb 2012 05:52:47 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F38CF190052; Tue, 14 Feb 2012 05:52:46 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Tue, 14 Feb 2012 05:52:41 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-forcerenew-nonce-03
Thread-Index: AQHM5SWUy8EqSdK3C0aOhQFr8l21aJY2slwAgAG8tQCAA3NmAIAA3poAgAA6lIA=
Date: Tue, 14 Feb 2012 13:52:40 +0000
Message-ID: <F96A644A-5ABF-47E8-A519-FA6A252FA03B@nominum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FB2@GRFMBX704BA020.griffon.local> <CEA6CD8F-7DCD-448C-8C31-EC64FD9902A3@nominum.com> <F184B794-3D1D-4A5A-860E-288DF2600DD6@nostrum.com> <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FC5@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EC1467FC5@GRFMBX704BA020.griffon.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
Cc: Ben Campbell <ben@nostrum.com>, The IETF <ietf@ietf.org>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org" <draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "Henderickx, Wim \(Wim\)" <wim.henderickx@alcatel-lucent.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:52:59 -0000

--_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Feb 14, 2012, at 5:23 AM, Maglione Roberta wrote:
Please let me know if you have additional comments.

Thanks!   I think you should change this text in the introduction:


The mandatory authentication was
   originally motivated by a legitimate security concern whereby in some
   network environments DHCP messages can be spoofed and an attacker
   could more accurately guess the timing of DHCP renewal messages by
   first sending a FORCERENEW message.  However, in some networks native
   security mechanisms already provide sufficient protection against
   spoofing of DHCP traffic.  An example of such network is a Broadband
   Forum TR-101 [TR-101i2] compliant access network.  In such
   environments the mandatory coupling between FORCERENEW and DHCP
   Authentication [RFC3118] can be relaxed and a lighter authentication
   mechanism can be used for the FORCERENEW message.

To this:

[paragraph break]
The motivation for making authentication mandatory in DHCPFORCERENEW was to=
 prevent an off-network attacker from taking advantage of DHCPFORCERENEW to=
 accurately predict the timing of a DHCP renewal.   Without DHCPFORCERENEW,=
 DHCP renewal timing is under the control of the client, and an off-network=
 attacker has no way of predicting when it will happen, since it doesn't ha=
ve access to the exchange between the DHCP client and DHCP server.

However, the requirement to use the DHCP authentication described in RFC311=
8 is more stringent than is required for this use case, and has limited ado=
ption of DHCPFORCERENEW.   RFC3315 defines an authentication protocol using=
 a nonce to prevent off-network attackers from successfully causing clients=
 to renew.   Since the off-network attacker doesn't have access to the nonc=
e, it can't trick the client into renewing at a time of its choosing.

--_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <8FBF60972DBA3A448E23142F121884ED@nominum.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>
<div>On Feb 14, 2012, at 5:23 AM, Maglione Roberta wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Please
 let me know if you have additional comments.<br>
</span></blockquote>
</div>
<br>
<div>Thanks! &nbsp; I think you should change this text in the introduction=
:</div>
<div><br>
</div>
<div>
<pre style=3D"color: rgb(0, 0, 0); font-style: normal; font-variant: normal=
; font-weight: normal; letter-spacing: normal; line-height: normal; orphans=
: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; wido=
ws: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; word-wrap: break-word; white-space: pre-wrap; ">The mandator=
y authentication was
   originally motivated by a legitimate security concern whereby in some
   network environments DHCP messages can be spoofed and an attacker
   could more accurately guess the timing of DHCP renewal messages by
   first sending a FORCERENEW message.  However, in some networks native
   security mechanisms already provide sufficient protection against
   spoofing of DHCP traffic.  An example of such network is a Broadband
   Forum TR-101 [TR-101i2] compliant access network.  In such
   environments the mandatory coupling between FORCERENEW and DHCP
   Authentication [RFC3118] can be relaxed and a lighter authentication
   mechanism can be used for the FORCERENEW message.</pre>
<div><br>
</div>
</div>
<div>To this:</div>
<div><br>
</div>
<div>[paragraph break]</div>
<div>The motivation for making authentication mandatory in DHCPFORCERENEW w=
as to prevent an off-network attacker from taking advantage of DHCPFORCEREN=
EW to accurately predict the timing of a DHCP renewal. &nbsp; Without DHCPF=
ORCERENEW, DHCP renewal timing is under
 the control of the client, and an off-network attacker has no way of predi=
cting when it will happen, since it doesn't have access to the exchange bet=
ween the DHCP client and DHCP server.</div>
<div><br>
</div>
<div>However, the requirement to use the DHCP authentication described in R=
FC3118 is more stringent than is required for this use case, and has limite=
d adoption of DHCPFORCERENEW. &nbsp; RFC3315 defines an authentication prot=
ocol using a nonce to prevent off-network
 attackers from successfully causing clients to renew. &nbsp; Since the off=
-network attacker doesn't have access to the nonce, it can't trick the clie=
nt into renewing at a time of its choosing.</div>
</body>
</html>

--_000_F96A644A5ABF47E8A519FA6A252FA03Bnominumcom_--

From Hans.Thienpondt@staff.telenet.be  Tue Feb 14 07:08:49 2012
Return-Path: <Hans.Thienpondt@staff.telenet.be>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6E0421F8798 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 07:08:49 -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=[BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuNXPzRLHCKX for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 07:08:48 -0800 (PST)
Received: from smtp4.staff.telenet.be (smtp4.staff.telenet.be [212.123.14.85]) by ietfa.amsl.com (Postfix) with ESMTP id 2685221F875E for <ietf@ietf.org>; Tue, 14 Feb 2012 07:08:48 -0800 (PST)
Received: from PROD175.prod.telenet.be (Not Verified[10.0.42.12]) by smtp4.staff.telenet.be with MailMarshal (v6, 9, 8, 3800) id <B4f3a78fc0000>; Tue, 14 Feb 2012 16:08:44 +0100
Received: from PROD176.prod.telenet.be ([169.254.2.244]) by PROD175.prod.telenet.be ([10.0.42.12]) with mapi id 14.01.0289.001; Tue, 14 Feb 2012 16:08:46 +0100
From: Thienpondt Hans <Hans.Thienpondt@staff.telenet.be>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczrKopzWOexDZAeRs2KWXFhFi03yQ==
Date: Tue, 14 Feb 2012 15:08:45 +0000
Message-ID: <9C44A297E166ED4190C3533AF2E8486D13A90E@PROD176.prod.telenet.be>
Accept-Language: en-GB, nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.4.0.25]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 14 Feb 2012 08:41:38 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:08:49 -0000

http://tools.ietf.org/html/draft-weil-shared-transition-space-request-14

+1
I support this draft!

Best Regards,

Hans


--
Hans Thienpondt
Technology Engineer

Converged Network Engineering
Telenet NV
Liersesteenweg 4 - box 52
T: +32 15 33 30 24
2800 Mechelen - Belgium

*************************************************************

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informati=
e bevatten die vertrouwelijk is en/of beschermd door intellectuele eigend=
omsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). =
Elk gebruik van de informatie vervat in dit bericht (waaronder de volledi=
ge of gedeeltelijke reproductie of verspreiding onder elke vorm) door and=
ere personen dan de geadresseerde(n) is verboden. Indien u dit bericht pe=
r vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen =
en dit bericht te verwijderen.=20

This e-mail and any attachment thereto may contain information which is c=
onfidential and/or protected by intellectual property rights and are inte=
nded for the sole use of the addressees. Any use of the information conta=
ined herein (including but not limited to total or partial reproduction o=
r distribution in any form) by other persons than the addressees is prohi=
bited. If you have received this e-mail in error, please notify the sende=
r and delete its contents.

Ce courriel et les annexes eventuelles peuvent contenir des informations =
confidentielles et/ou protegees par des droits de propriete intellectuell=
e. Ce message est adresse exclusivement e son (ses) destinataire(s). Tout=
e utilisation du contenu de ce message (y compris la reproduction ou diff=
usion partielle ou complete sous toute forme) par une autre personne que =
le(s) destinataire(s) est formellement interdite. Si vous avez recu ce me=
ssage par erreur, veuillez prevenir l'expediteur du message et en detruir=
e le contenu.

*************************************************************

From braden@isi.edu  Tue Feb 14 09:31:11 2012
Return-Path: <braden@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 A669C21E8096 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:31:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MLH3VWre9XgB for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:31:10 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id B1BA821E807E for <ietf@ietf.org>; Tue, 14 Feb 2012 09:31:10 -0800 (PST)
Received: from [128.9.168.81] (rtb.isi.edu [128.9.168.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q1EHV1v5009010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 Feb 2012 09:31:01 -0800 (PST)
Message-ID: <4F3A9A55.8080908@isi.edu>
Date: Tue, 14 Feb 2012 09:31:01 -0800
From: Bob Braden <braden@isi.edu>
Organization: USC/ISI
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu>
In-Reply-To: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: braden@isi.edu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:31:11 -0000

On 2/13/2012 7:53 PM, Noel Chiappa wrote:
>      >  From: Brian E Carpenter<brian.e.carpenter@gmail.com>
>
>      >  The design error was made in the late 1970s, when Louis Pouzin's advice
>      >  that catenet addresses should be variable length, with a format prefix,
>      >  was not taken during the design of IPv4.
>
> Ironically, TCP/IP had variable length addresses put in _twice_, and they were
> removed both times! (You can't make this stuff up! :-)
Noel,

You probably remember this, but...

Within the ARPA-funded Internet research program that designed IP and 
TCP, Jon Postel and
Danny Cohen argued strenuously for variable length addresses. (This must 
have been
around 1979. I cannot name most of the other 10 people in the room, but 
I have
a clear mental picture of Jon, in the back of the room, fuming over this 
issue. Jon believed
intensely in protocol extensibility.)

However, Vint Cerf, the ARPA program manager, rules against variable 
length addresses and
decreed the fixed length 32 bit word-aligned addresses of RFC 791. His 
argument was that
TCP/IP had to be simple to implement if it were to succeed (and survive 
the juggernaut
of the ISO OSI protocol suite).

  System programmers of that day were familiar with word-aligned data
structures with fixed offsets, and variable length addresses seemed to 
be (and in fact
would be) harder to program and would make packet dumps harder to interpret.

It was a political as much as a technical judgment, and Vint may have 
been right ... we
can never know. We do know that IP eventually succeeded and OSI failed, 
but it
was a near thing for awhile. Of course, there were other factors in the 
success
of IP, such as Berkeley Unix.

It is to be noted that when it came time to define IPv6 some 20 years 
later, the IETF
stuck with fixed length internet addresses.

Bob Braden


From tglassey@earthlink.net  Tue Feb 14 09:33:55 2012
Return-Path: <tglassey@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 ABE8E21F876D for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.363
X-Spam-Level: 
X-Spam-Status: No, score=-1.363 tagged_above=-999 required=5 tests=[AWL=-1.823, BAYES_20=-0.74, J_CHICKENPOX_21=0.6, J_CHICKENPOX_91=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMwvpd0gNg6o for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:33:55 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id A4D9B21F86F9 for <ietf@ietf.org>; Tue, 14 Feb 2012 09:33:51 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=DkfFWszHSvhhpZsz+xOyD1Hqt/+Njeij09KHi5FxwF8bcXs9QDcHIEH6L6TPyKtn; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Opacus-Archived:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [216.171.124.254] (helo=[192.168.0.4]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1RxMGE-0007Ra-Ly; Tue, 14 Feb 2012 12:33:51 -0500
Message-ID: <4F3A9AFE.4070001@earthlink.net>
Date: Tue, 14 Feb 2012 09:33:50 -0800
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: Yet Another Reason?
References: <CAKhHsXHRB24bOq5HQp=hiBBzi_X+Gx==Y1Hoon3=1vC18JjdBQ@mail.gmail.com> <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
In-Reply-To: <CAC1-dt=gXGrohg6Cb8YLjFsW6bRTehvcYPnK9JQsmzOHmgQdMg@mail.gmail.com>
X-Opacus-Archived: none
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec790357a25444d396fb735089de74841ad2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 216.171.124.254
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:33:55 -0000

On 2/2/2012 3:05 PM, Chris Grundemann wrote:
> Hides the screen, nervous, pays cash... Sounds to me like anyone
> surfing pr0n at the "Internet Cafe" is now a suspected terrorist.z

You should go spend a week in the border towns in Israel before you make
such telling comments like that.

Todd

> 
> 
> On Thu, Feb 2, 2012 at 14:55, Alan Johnston <alan.b.johnston@gmail.com> wrote:
>> Is this yet another reason not to have IETF meetings in the USA? ;-)
>>
>>     http://yro.slashdot.org/story/12/02/02/1719221/do-you-like-online-privacy-you-may-be-a-terrorist
>>
>> The FBI and their would-be tipsters could be flat out trying
>> investigate everyone who uses encryption, anonymizer and privacy tools
>> on the Internet, or changes SIM cards in their mobile phone!  At least
>> "wearing T-shirts with inscrutable slogans" isn't on the list yet or
>> we'd all be rounded up...
>>
>> Seriously - who writes this stuff?
>>
>> - Alan -
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> 
> 
> 


-- 
Todd S. Glassey
This is from my personal email account and any materials from this
account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.

From BCheck@NCTA.com  Tue Feb 14 09:38:23 2012
Return-Path: <BCheck@NCTA.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F62E21E8095 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:38:23 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwFBtYq6JuEB for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:38:22 -0800 (PST)
Received: from mail-3.ncta.com (mail-3.ncta.com [209.23.210.3]) by ietfa.amsl.com (Postfix) with ESMTP id 100E921E8084 for <ietf@ietf.org>; Tue, 14 Feb 2012 09:38:22 -0800 (PST)
Received: from MAILSTORE-A.ncta.com ([::1]) by Mailhubcas.ncta.com ([::1]) with mapi id 14.01.0355.002; Tue, 14 Feb 2012 12:38:21 -0500
From: William Check <BCheck@NCTA.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczrKopzWOexDZAeRs2KWXFhFi03yQAPs98A
Date: Tue, 14 Feb 2012 17:38:20 +0000
Message-ID: <72072B73-F740-4A40-A01F-0A66E0C0E295@ncta.com>
References: <9C44A297E166ED4190C3533AF2E8486D13A90E@PROD176.prod.telenet.be>
In-Reply-To: <9C44A297E166ED4190C3533AF2E8486D13A90E@PROD176.prod.telenet.be>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.25.11.121]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F9BC0CB82FFE59459B43CFBC7582D7C7@ncta.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:38:23 -0000

+1, I support this draft=85  Bill Check


On Feb 14, 2012, at 10:08 AM, Thienpondt Hans wrote:

> http://tools.ietf.org/html/draft-weil-shared-transition-space-request-14
>=20
> +1
> I support this draft!
>=20
> Best Regards,
>=20
> Hans
>=20
>=20
> --
> Hans Thienpondt
> Technology Engineer
>=20
> Converged Network Engineering
> Telenet NV
> Liersesteenweg 4 - box 52
> T: +32 15 33 30 24
> 2800 Mechelen - Belgium
>=20
> *************************************************************
>=20
> Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informati=
e bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendom=
srechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk =
gebruik van de informatie vervat in dit bericht (waaronder de volledige of =
gedeeltelijke reproductie of verspreiding onder elke vorm) door andere pers=
onen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissi=
ng heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit beric=
ht te verwijderen.=20
>=20
> This e-mail and any attachment thereto may contain information which is c=
onfidential and/or protected by intellectual property rights and are intend=
ed for the sole use of the addressees. Any use of the information contained=
 herein (including but not limited to total or partial reproduction or dist=
ribution in any form) by other persons than the addressees is prohibited. I=
f you have received this e-mail in error, please notify the sender and dele=
te its contents.
>=20
> Ce courriel et les annexes eventuelles peuvent contenir des informations =
confidentielles et/ou protegees par des droits de propriete intellectuelle.=
 Ce message est adresse exclusivement e son (ses) destinataire(s). Toute ut=
ilisation du contenu de ce message (y compris la reproduction ou diffusion =
partielle ou complete sous toute forme) par une autre personne que le(s) de=
stinataire(s) est formellement interdite. Si vous avez recu ce message par =
erreur, veuillez prevenir l'expediteur du message et en detruire le contenu=
.
>=20
> *************************************************************
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From tglassey@earthlink.net  Tue Feb 14 09:42:37 2012
Return-Path: <tglassey@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 809B521F858E for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:42:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.778
X-Spam-Level: 
X-Spam-Status: No, score=-2.778 tagged_above=-999 required=5 tests=[AWL=-0.179, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsxLIytZKfRE for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:42:36 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by ietfa.amsl.com (Postfix) with ESMTP id E863421F85B7 for <ietf@ietf.org>; Tue, 14 Feb 2012 09:42:35 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=tK8G5fAEoXq8DXnT+zWdrbJ+SBla3Jyh0phsM13BQW53hoMTv2dg2mfEV5qjfhXj; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Opacus-Archived:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [216.171.124.254] (helo=[192.168.0.4]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1RxMOh-0007P2-Hf for ietf@ietf.org; Tue, 14 Feb 2012 12:42:35 -0500
Message-ID: <4F3A9D0B.3070604@earthlink.net>
Date: Tue, 14 Feb 2012 09:42:35 -0800
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Furthering discussions about BCP79 sanctions
References: <01a801cce827$60060e80$20122b80$@olddog.co.uk> <6.2.5.6.2.20120212011537.05c62e20@resistor.net> <03e501cce9b1$ed0f2e20$c72d8a60$@olddog.co.uk>
In-Reply-To: <03e501cce9b1$ed0f2e20$c72d8a60$@olddog.co.uk>
X-Opacus-Archived: none
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79acf3efac4dd5a06320b4b3bd0ea7e2fc350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 216.171.124.254
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:42:37 -0000

On 2/12/2012 10:12 AM, Adrian Farrel wrote:
> Hi SM,

So isnt the real issue that of informed consent? If you dont know that
someone else has already existing work is it their fault for not telling
the IETF?

If so then there would also need to be some form of process identical to
this for verifying that the people participating hold legal power of
attorney pertaining to that work for their sponsors, or they cannot make
any 'management decisions' pertaining to any project.

The misunderstanding in the IETF BCP78 and BCP79 documents is that
one-size fits all for IETF participants. It simply cannot - In fact many
participants are there to work on processes and efforts for their
sponsors who have no legal power of attorney for their sponsors what so
ever. This is part of the myriad of misrepresentations that the IETF and
its parent ISOC are still trying to get the rest of the world to swallow
IMHO.

Todd

> 
>>> There has been some discussion on this list about
>>> draft-farrresnickel-ipr-sanctions-00.  Thanks for the input.
>>>
>>> The conversation seems to be partitioned into:
>>> - discussion of sanctions and how to apply them
>>> - discussion of measures that can be taken to
>>>   help people to adhere to BCP79
>>
>> The following messages are about the "help people":
>>
>> http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html
>> http://www.ietf.org/mail-archive/web/marf/current/msg02081.html
> 
> Yes. I've been watching those threads, and I think that some other WGs are
> thinking of following similar procedures.
> 
>>> Furthermore, there is some debate about who should/can be responsible for
>>> applying sanctions.
> 
> [snip]
> 
>> In Appendix A:
>>
>>   "-  Does the large number of patents that the individual has authored
>>       provide any level of excuse for failing to notice that one of
>>       their patents covered the IETF work?"
>>
>> That should be "the individual has invented".
> 
> Yes.
> 
>> I suggest removing the above as prolific inventors should pay more
>> attention to BCP 79.  
> 
> I'm inclined to agree with you.
> 
> Others feel that there may be some mitigation in this case.
> 
> By listing the point, we are giving the WG chairs the opportunity to consider
> it. They may deduce that it provides an excuse, no excuse, or exacerbates the
> case.
> 
>> Section 6.1.2 of BCP 79 is about an IETF Participant's IPR in
>> Contributions by others.   Should sanctions be considered if the
>> individual participates and does not disclose?
> 
> Yes. That is certainly my intention in this document. All violations of BCP 79
> are cause to consider sanctions. The severity of the case may be judged by many
> factors, and I suppose that the level of "participation" may be one of these
> factors. I am hoping that Section 2.1 makes the first point clear, and Appendix
> A the second point.
> 
> Cheers,
> Adrian
> 
> 
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 


-- 
Todd S. Glassey
This is from my personal email account and any materials from this
account come with personal disclaimers.

Further I OPT OUT of any and all commercial emailings.

From cgrundemann@gmail.com  Tue Feb 14 09:45:10 2012
Return-Path: <cgrundemann@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 E17DD21E8029 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.677
X-Spam-Level: 
X-Spam-Status: No, score=-3.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7cXA-5dKjuxq for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:45:07 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id EE4BA21E8051 for <ietf@ietf.org>; Tue, 14 Feb 2012 09:45:06 -0800 (PST)
Received: by dakl33 with SMTP id l33so170543dak.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 09:45:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=kS4uZZF2d4kx5QAWiL78Y65e0VfqV6BsXkxtwClyzDE=; b=Ia5Mb2I+oFamg2ukmsF/Qn2ZLslp5jMEShL71qsjTn5C8SI7R3MR5H2B8uSj+QImpJ EZVIjoOAx2bAjN2CI8G7L3Ig+BN2pdMbQnEInM72YOsyj/Br1zyS3ZOo0ilL2DI+SDQM FrVVFXcnTFtJ6S3g0T4FB5xwILEmXTsKN6wE4=
MIME-Version: 1.0
Received: by 10.68.74.138 with SMTP id t10mr60484563pbv.126.1329241504261; Tue, 14 Feb 2012 09:45:04 -0800 (PST)
Received: by 10.68.60.200 with HTTP; Tue, 14 Feb 2012 09:45:04 -0800 (PST)
In-Reply-To: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
Date: Tue, 14 Feb 2012 10:45:04 -0700
Message-ID: <CAC1-dt=L1Rz-jm7H3v8YH=-ydBN=SpxD1G_2YUVF5tX2F3pAaA@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:45:10 -0000

Apologies for top posting rather than addressing specific
commentators, but there have been several misconceptions raised
several times that I felt should be addressed generically:

1) "We are out of IPv4 space / There's no-where to get this /10" -
There is already a /10 reserved by the ARIN community for this purpose
(as long as we don't drag our feet too long), please see:
https://www.arin.net/policy/proposals/2011_5.html

2) "Just use 1918 space" - I apologize for not having more data to
share, but I can tell you that I have spoken with numerous network
operators and NONE of them are willing to do this. ISPs will NOT use
RFC 1918 space, no matter how many times folks scream it from the tops
of ivory towers. Operational realities must sometimes trump ideals.

3) "CGN is bad" - This one is accurate. It has no bearing on this I-D
whatsoever though. Yes, CGN sucks and we want as few networks to use
it as possible. But, no matter what we do, some will have to deploy
it. This I-D is about helping reduce everyone's pain when they do.
Leaking squat space hurts more than just the one who leaks it...

4) "IPv6 is awesome" - Again, accurate but inconsequential here. IPv6
does not solve IPv4 connectivity issues. Operators are not solely
responsible for the lack of IPv6 penetration. Rather than throw stones
from our glass houses, we should focus on ensuring that the transition
can happen without shattering all of them.

I understand that many have strong emotional ties to their opinions.
My only hope is to point those with open minds in the right direction
as they seek to understand this issue more fully.

Cheers,
~Chris (speaking for myself, from an ivory tower made of glass)


On Mon, Jan 30, 2012 at 16:03, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider =
the following document:
> - 'IANA Reserved IPv4 Prefix for Shared CGN Space'
> =A0<draft-weil-shared-transition-space-request-14.txt> as a BCP
>
> On its December 15, 2011 telechat, the IESG reviewed version 10 of this
> document and requested various changes. These changes are reflected in
> the draft version 14 and the IESG now solicits community input on the
> changed text only. Please send substantive comments to the ietf@ietf.org
> mailing lists by 2012-02-16. 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
>
> =A0This document requests the allocation of an IPv4 /10 address block to
> =A0be used as Shared Address Space to accommodate the needs of Carrier
> =A0Grade Network Address Translation (CGN) devices. =A0It is anticipated
> =A0that Service Providers will use this Shared Address Space to number
> =A0the interfaces that connect CGN devices to Customer Premise Equipment
> =A0(CPE).
>
> =A0Shared Address Space is distinct from RFC1918 private address space
> =A0because it is intended for use on Service Provider networks.
> =A0However, it may be used as RFC 1918 private address space in certain
> =A0circumstances. =A0Details are provided in the text of this document.
>
> =A0As this document proposes the allocation of an additional special-use
> =A0IPv4 address block, it updates RFC 5735.
>
> The following text captures the most salient change between version 10 an=
d 14 of this document:
>
> =A0Shared Address Space is IPv4 address space designated for Service
> =A0 =A0 Provider use with the purpose of facilitating CGN deployment. =A0=
Also,
> =A0 =A0 Shared Address Space can be used as additional [RFC1918] space wh=
en
> =A0 =A0 at least one of the following conditions is true:
>
> =A0 =A0 o =A0Shared Address Space is not also used on the Service Provide=
r side
> =A0 =A0 =A0 =A0of the CPE.
>
> =A0 =A0 o =A0CPE routers behave correctly when using the same address blo=
ck on
> =A0 =A0 =A0 =A0both the internal and external interfaces.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-weil-shared-transition-space-reques=
t/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-weil-shared-transition-space-reques=
t/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce



--=20
@ChrisGrundemann
http://chrisgrundemann.com

From rcallon@juniper.net  Tue Feb 14 10:25:46 2012
Return-Path: <rcallon@juniper.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 9C19621F86B3 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:25:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6syqlcsSfOmf for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:25:46 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 79D2A21F866D for <ietf@ietf.org>; Tue, 14 Feb 2012 10:25:43 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTzqnIeLD8d4zYUsR56vzTrxsUTLA3lNX@postini.com; Tue, 14 Feb 2012 10:25:45 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 14 Feb 2012 10:25:07 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 14 Feb 2012 13:25:06 -0500
From: Ross Callon <rcallon@juniper.net>
To: Owen DeLong <owen@delong.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 14 Feb 2012 13:25:05 -0500
Subject: RE: Another last call for draft-weil
Thread-Topic: Another last call for draft-weil
Thread-Index: AczrN4nyqVHz1qmbSsm97A2pGasTHwADmhPg
Message-ID: <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com>
In-Reply-To: <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DF7F294AF4153D498141CBEFADB17704C70AD046BDEMBX01WFjnprn_"
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: e4081efb-6d29-443c-8708-750833aec629
Cc: "draft-bdgks-arin-shared-transition-space@tools. org" <draft-bdgks-arin-shared-transition-space@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:25:46 -0000

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

+1.

Ross

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Owe=
n DeLong
Sent: Monday, February 13, 2012 2:06 PM
To: ietf@ietf.org
Cc: draft-bdgks-arin-shared-transition-space@tools. org
Subject: Re: Another last call for draft-weil

I support draft-weil as revised. There is a vital need for this to move for=
ward and the IETF should stop standing in the way and let ARIN allocate the=
 space already.

Owen

On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote:


Fellow BDGKS Authors,

FYI: draft-weil is in another Last Call following an update that was reques=
ted by IESG Ads (on their December telechat, some ADs asked us to turn our =
request into a request for more 1918 space, but with a few caveats to home =
router manufacturers about not breaking when exposed to a CGN environment.)=
. At this point we don't expect to change any minds. Basically everyone who=
 is against the draft has spoken up. Now it is just a numbers game, we need=
 to demonstrate significant support for the draft.

If you do support this I-D and the allocation of the /10 for shared CGN use=
, please consider posting a statement of support.  Something as simple as "=
I support this draft as updated" or "I think the updated draft is more flex=
ible, and would satisfy additional use cases that don't work with RFC1918 s=
pace" would be very helpful.

You can respond to the "Last Call: <draft-weil-shared-transition-space-requ=
est-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP" th=
read or post individually to  ietf@ietf.org<mailto:ietf@ietf.org>. Also, pl=
ease feel free to encourage anyone else you know who supports the draft to =
make a similar post. Every statement we can gather is vital right now. Last=
 call ends on Thursday, so reply's must be made before then. Thank you.

Cheers,
~Chris


--_000_DF7F294AF4153D498141CBEFADB17704C70AD046BDEMBX01WFjnprn_
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=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><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;}
/* 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.apple-style-span
	{mso-style-name:apple-style-span;}
span.hp
	{mso-style-name:hp;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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=3DEN-US link=3Dblue vli=
nk=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: space;-webkit=
-line-break: after-white-space'><div class=3DWordSection1><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";colo=
r:#1F497D'>+1.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'>Ross<o:p></o:p></span></p><p c=
lass=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'bord=
er:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=
=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'> ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On=
 Behalf Of </b>Owen DeLong<br><b>Sent:</b> Monday, February 13, 2012 2:06 P=
M<br><b>To:</b> ietf@ietf.org<br><b>Cc:</b> draft-bdgks-arin-shared-transit=
ion-space@tools. org<br><b>Subject:</b> Re: Another last call for draft-wei=
l<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p><p class=3DMsoNormal>I support draft-weil as revised. There is a vital ne=
ed for this to move forward and the IETF should stop standing in the way an=
d let ARIN allocate the space already.<o:p></o:p></p><div><p class=3DMsoNor=
mal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Owen<o:p></o:p></p=
></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3D=
MsoNormal>On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote:<o:p></o:p><=
/p></div><p class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p class=3DM=
soNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"=
;color:black'>Fellow BDGKS Authors,<o:p></o:p></span></p></div><div><p clas=
s=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-s=
erif";color:black'><o:p>&nbsp;</o:p></span></p></div><div><div><p class=3DM=
soNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif"=
;color:black'>FYI: draft-weil is in another Last Call following an update t=
hat was requested by IESG Ads&nbsp;(o</span><span class=3Dapple-style-span>=
<span style=3D'font-size:13.5pt;font-family:"Calibri","sans-serif";color:bl=
ack'>n their December telechat, some ADs asked us to turn our&nbsp;request =
into a request for more 1918 space, but with a few caveats to home&nbsp;rou=
ter manufacturers about not breaking when exposed to a CGN environment.)</s=
pan></span><span class=3Dapple-style-span><span style=3D'font-size:10.5pt;f=
ont-family:"Calibri","sans-serif";color:black'>. At this point we don't exp=
ect to change any minds. Basically everyone who is against the draft has sp=
oken up. Now it is just a numbers game, we need to demonstrate significant =
support for the draft.</span></span><span style=3D'font-size:10.5pt;font-fa=
mily:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div><=
p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","=
sans-serif";color:black'><o:p>&nbsp;</o:p></span></p></div><div><p class=3D=
MsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif=
";color:black'>If you do support this I-D and the allocation of the /10 for=
 shared CGN use, please consider posting a statement of support. &nbsp;</sp=
an><span class=3Dapple-style-span><span style=3D'font-size:13.5pt;font-fami=
ly:"Calibri","sans-serif";color:black'>Something as simple as &quot;I suppo=
rt this draft as updated&quot; or &quot;I think&nbsp;the updated draft is m=
ore flexible, and would satisfy additional use cases&nbsp;that don't work w=
ith RFC1918 space&quot; would be very helpful.</span></span><span style=3D'=
font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt=
;font-family:"Calibri","sans-serif";color:black'><o:p>&nbsp;</o:p></span></=
p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-fami=
ly:"Calibri","sans-serif";color:black'>You can respond to the &quot;</span>=
<span class=3Dhp><span style=3D'font-family:"Calibri","sans-serif";color:bl=
ack'>Last Call: &lt;draft-weil-shared-transition-space-request-14.txt&gt; (=
IANA Reserved IPv4 Prefix for Shared Address Space) to BCP</span></span><sp=
an class=3Dapple-style-span><span style=3D'font-size:10.5pt;font-family:"Ca=
libri","sans-serif";color:black'>&quot; thread or post individually to&nbsp=
;&nbsp;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>. Also, please fee=
l free to encourage anyone else you know who supports the draft to make a s=
imilar post. Every statement we can gather is vital right now. Last call en=
ds on Thursday, so reply's must be made before then. Thank you.</span></spa=
n><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:=
black'><o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D=
'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p>&nbs=
p;</o:p></span></p></div><div><p class=3DMsoNormal><span class=3Dapple-styl=
e-span><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";c=
olor:black'>Cheers,</span></span><span style=3D'font-size:10.5pt;font-famil=
y:"Calibri","sans-serif";color:black'><o:p></o:p></span></p></div><div><p c=
lass=3DMsoNormal><span class=3Dapple-style-span><span style=3D'font-size:10=
.5pt;font-family:"Calibri","sans-serif";color:black'>~Chris</span></span><s=
pan style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:blac=
k'><o:p></o:p></span></p></div></div></div></div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p></div></div></body></html>=

--_000_DF7F294AF4153D498141CBEFADB17704C70AD046BDEMBX01WFjnprn_--

From sob@harvard.edu  Tue Feb 14 10:33:51 2012
Return-Path: <sob@harvard.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 B462721E8080 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.141
X-Spam-Level: 
X-Spam-Status: No, score=-102.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AUuBDqCxqCsl for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:33:51 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id D7ADE21E8058 for <ietf@ietf.org>; Tue, 14 Feb 2012 10:33:50 -0800 (PST)
Received: from exchange.university.harvard.edu (unknown [10.35.2.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 43BE7E8FB9 for <ietf@ietf.org>; Tue, 14 Feb 2012 13:33:50 -0500 (EST)
Received: from ENTWHUBT0000003.university.harvard.edu (192.168.36.24) by ENTWEDGE0000000.university.harvard.edu (10.35.2.151) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 14 Feb 2012 13:32:47 -0500
Received: from ENTWEXMB0000004.university.harvard.edu ([169.254.3.253]) by entwhubt0000003.university.harvard.edu ([192.168.36.24]) with mapi id 14.01.0355.002; Tue, 14 Feb 2012 13:33:40 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Another last call for draft-weil
Thread-Topic: Another last call for draft-weil
Thread-Index: AQHM60csfkIEGKmop0Smx4sp9fzGsQ==
Date: Tue, 14 Feb 2012 18:33:39 +0000
Message-ID: <5BB63F16-DA59-4B07-AA2B-457A1AF2B7F6@harvard.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [140.247.60.212]
Content-Type: text/html; charset="us-ascii"
Content-ID: <406DDF9FC6614444AEBA3CDD27A6D8B8@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:33:51 -0000

<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-lin=
e-break: after-white-space; ">
(not voting twice, my other address did not seem to work)
<div><br>
</div>
<div>&#43;1
<div><br>
<div>
<div>On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: brea=
k-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); ">&#43;1.<o:p></o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); ">Ross<o:p></o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div>
<div style=3D"border-right-style: none; border-bottom-style: none; border-l=
eft-style: none; border-width: initial; border-color: initial; border-top-s=
tyle: solid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; p=
adding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: 0in=
; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">From:=
</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;=
 ">&nbsp;<a href=3D"mailto:ietf-bounces@ietf.org" style=3D"color: blue; tex=
t-decoration: underline; ">ietf-bounces@ietf.org</a>&nbsp;[mailto:ietf-boun=
ces@ietf.org]&nbsp;<b>On
 Behalf Of&nbsp;</b>Owen DeLong<br>
<b>Sent:</b>&nbsp;Monday, February 13, 2012 2:06 PM<br>
<b>To:</b>&nbsp;<a href=3D"mailto:ietf@ietf.org" style=3D"color: blue; text=
-decoration: underline; ">ietf@ietf.org</a><br>
<b>Cc:</b>&nbsp;draft-bdgks-arin-shared-transition-space@tools. org<br>
<b>Subject:</b>&nbsp;Re: Another last call for draft-weil<o:p></o:p></span>=
</div>
</div>
</div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
I support draft-weil as revised. There is a vital need for this to move for=
ward and the IETF should stop standing in the way and let ARIN allocate the=
 space already.<o:p></o:p></div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
Owen<o:p></o:p></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<o:p>&nbsp;</o:p></div>
<div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote:<o:p></o:p></div>
</div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<br>
<br>
<o:p></o:p></div>
<div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; ">Fellow BDGKS Authors,<o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p>&nbsp;</o:p></span></div>
</div>
<div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; ">FYI: draft-weil is in another Last Call following an update that w=
as requested by IESG Ads&nbsp;(o</span><span class=3D"apple-style-span"><sp=
an style=3D"font-size: 13.5pt; font-family: Calibri, sans-serif; color: bla=
ck; ">n
 their December telechat, some ADs asked us to turn our&nbsp;request into a=
 request for more 1918 space, but with a few caveats to home&nbsp;router ma=
nufacturers about not breaking when exposed to a CGN environment.)</span></=
span><span class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; fon=
t-family: Calibri, sans-serif; color: black; ">.
 At this point we don't expect to change any minds. Basically everyone who =
is against the draft has spoken up. Now it is just a numbers game, we need =
to demonstrate significant support for the draft.</span></span><span style=
=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: black; "><o=
:p></o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p>&nbsp;</o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; ">If you do support this I-D and the allocation of the /10 for share=
d CGN use, please consider posting a statement of support. &nbsp;</span><sp=
an class=3D"apple-style-span"><span style=3D"font-size: 13.5pt; font-family=
: Calibri, sans-serif; color: black; ">Something
 as simple as &quot;I support this draft as updated&quot; or &quot;I think&=
nbsp;the updated draft is more flexible, and would satisfy additional use c=
ases&nbsp;that don't work with RFC1918 space&quot; would be very helpful.</=
span></span><span style=3D"font-size: 10.5pt; font-family: Calibri, sans-se=
rif; color: black; "><o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p>&nbsp;</o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; ">You can respond to the &quot;</span><span class=3D"hp"><span style=
=3D"font-family: Calibri, sans-serif; color: black; ">Last Call: &lt;draft-=
weil-shared-transition-space-request-14.txt&gt; (IANA
 Reserved IPv4 Prefix for Shared Address Space) to BCP</span></span><span c=
lass=3D"apple-style-span"><span style=3D"font-size: 10.5pt; font-family: Ca=
libri, sans-serif; color: black; ">&quot; thread or post individually to&nb=
sp;&nbsp;<a href=3D"mailto:ietf@ietf.org" style=3D"color: blue; text-decora=
tion: underline; ">ietf@ietf.org</a>.
 Also, please feel free to encourage anyone else you know who supports the =
draft to make a similar post. Every statement we can gather is vital right =
now. Last call ends on Thursday, so reply's must be made before then. Thank=
 you.</span></span><span style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: black; "><o:p></o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p>&nbsp;</o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; font-fam=
ily: Calibri, sans-serif; color: black; ">Cheers,</span></span><span style=
=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: black; "><o=
:p></o:p></span></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; font-fam=
ily: Calibri, sans-serif; color: black; ">~Chris</span></span><span style=
=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: black; "><o=
:p></o:p></span></div>
</div>
</div>
</div>
</div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<o:p>&nbsp;</o:p></div>
</div>
</div>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" style=3D"color: blue; text-decoration: und=
erline; ">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" style=3D"color: blue=
; text-decoration: underline; ">https://www.ietf.org/mailman/listinfo/ietf<=
/a><br>
</div>
</span></blockquote>
</div>
</div>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; f=
ont-family: Helvetica; font-style: normal; font-variant: normal; font-weigh=
t: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-al=
ign: -webkit-auto; text-indent: 0px; text-transform: none; white-space: nor=
mal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: n=
one; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-s=
ize: medium; "><br>
</span></div>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; f=
ont-family: Helvetica; font-style: normal; font-variant: normal; font-weigh=
t: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-al=
ign: -webkit-auto; text-indent: 0px; text-transform: none; white-space: nor=
mal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: n=
one; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-s=
ize: medium; "><br>
</span></div>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; c=
olor: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=
=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica;=
 font-style: normal; font-variant: normal; font-weight: normal; letter-spac=
ing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; tex=
t-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-s=
pacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertica=
l-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size=
-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Scott O Bradner</div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Senior Technology&nbsp;Consultant<br>
<br>
Harvard University Information Technology<br>
Innovation &amp; Architecture<br>
(P) &#43;1 (617) 495 3864<br>
29 Oxford St. Rm 407<br>
Cambridge, MA 02138<br>
<br>
<br>
</div>
</span></span></div>
<br>
</div>
</body>
</html>

From steve@shinkuro.com  Tue Feb 14 10:34:56 2012
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70EB621E80A7 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:34:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.772
X-Spam-Level: 
X-Spam-Status: No, score=-0.772 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, HELO_EQ_DSL=1.129, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJUVMxQf9ioy for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:34:56 -0800 (PST)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id BBB6721E80A5 for <ietf@ietf.org>; Tue, 14 Feb 2012 10:34:55 -0800 (PST)
Received: from [195.65.225.66] (HELO [192.168.12.177]) by execdsl.com (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 20269862; Tue, 14 Feb 2012 18:35:30 +0000
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu>
In-Reply-To: <4F3A9A55.8080908@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset=us-ascii
Message-Id: <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (9A405)
From: Steve Crocker <steve@shinkuro.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
Date: Tue, 14 Feb 2012 19:34:53 +0100
To: "braden@isi.edu" <braden@isi.edu>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:34:56 -0000

The word alignment issue was very strong and the router people had considera=
bly more influence than the host folks.  I tried to propose variable length a=
ddressing using four bit nibbles in August 1974 and I got no traction at all=
.

Steve

Sent from my iPhone

On Feb 14, 2012, at 6:31 PM, Bob Braden <braden@isi.edu> wrote:

> On 2/13/2012 7:53 PM, Noel Chiappa wrote:
>>     >  From: Brian E Carpenter<brian.e.carpenter@gmail.com>
>>=20
>>     >  The design error was made in the late 1970s, when Louis Pouzin's a=
dvice
>>     >  that catenet addresses should be variable length, with a format pr=
efix,
>>     >  was not taken during the design of IPv4.
>>=20
>> Ironically, TCP/IP had variable length addresses put in _twice_, and they=
 were
>> removed both times! (You can't make this stuff up! :-)
> Noel,
>=20
> You probably remember this, but...
>=20
> Within the ARPA-funded Internet research program that designed IP and TCP,=
 Jon Postel and
> Danny Cohen argued strenuously for variable length addresses. (This must h=
ave been
> around 1979. I cannot name most of the other 10 people in the room, but I h=
ave
> a clear mental picture of Jon, in the back of the room, fuming over this i=
ssue. Jon believed
> intensely in protocol extensibility.)
>=20
> However, Vint Cerf, the ARPA program manager, rules against variable lengt=
h addresses and
> decreed the fixed length 32 bit word-aligned addresses of RFC 791. His arg=
ument was that
> TCP/IP had to be simple to implement if it were to succeed (and survive th=
e juggernaut
> of the ISO OSI protocol suite).
>=20
> System programmers of that day were familiar with word-aligned data
> structures with fixed offsets, and variable length addresses seemed to be (=
and in fact
> would be) harder to program and would make packet dumps harder to interpre=
t.
>=20
> It was a political as much as a technical judgment, and Vint may have been=
 right ... we
> can never know. We do know that IP eventually succeeded and OSI failed, bu=
t it
> was a near thing for awhile. Of course, there were other factors in the su=
ccess
> of IP, such as Berkeley Unix.
>=20
> It is to be noted that when it came time to define IPv6 some 20 years late=
r, the IETF
> stuck with fixed length internet addresses.
>=20
> Bob Braden
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From sob@harvard.edu  Tue Feb 14 10:37:48 2012
Return-Path: <sob@harvard.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 1FAA521F8622 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:37:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.141
X-Spam-Level: 
X-Spam-Status: No, score=-102.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NRpT6ua0J-KO for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:37:47 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 6E50521F85F6 for <ietf@ietf.org>; Tue, 14 Feb 2012 10:37:47 -0800 (PST)
Received: from exchange.university.harvard.edu (unknown [10.35.2.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 265A3E89C8; Tue, 14 Feb 2012 13:37:43 -0500 (EST)
Received: from ENTWHUBT0000002.university.harvard.edu (192.168.36.23) by ENTWEDGE0000000.university.harvard.edu (10.35.2.151) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 14 Feb 2012 13:36:47 -0500
Received: from ENTWEXMB0000004.university.harvard.edu ([169.254.3.253]) by entwhubt0000002.university.harvard.edu ([192.168.36.46]) with mapi id 14.01.0355.002; Tue, 14 Feb 2012 13:37:40 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: Steve Crocker <steve@shinkuro.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
Thread-Topic: Variable length internet addresses in TCP/IP: history
Thread-Index: AQHM60e7HdsRjprAeEagt3ww6jYu8A==
Date: Tue, 14 Feb 2012 18:37:39 +0000
Message-ID: <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com>
In-Reply-To: <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [140.247.60.212]
Content-Type: text/html; charset="us-ascii"
Content-ID: <648EC24DB47ABA448BAAFB9D44F401FC@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:37:48 -0000

<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-lin=
e-break: after-white-space; ">
in the case of IPng, the router people wanted variable length but the host =
people (or at least some of them) did not
<div><br>
</div>
<div>Scott</div>
<div><br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; c=
olor: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=
=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica;=
 font-style: normal; font-variant: normal; font-weight: normal; letter-spac=
ing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; tex=
t-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-s=
pacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertica=
l-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size=
-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Scott O Bradner</div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Senior Technology&nbsp;Consultant<br>
<br>
Harvard University Information Technology<br>
Innovation &amp; Architecture<br>
(P) &#43;1 (617) 495 3864<br>
29 Oxford St. Rm 407<br>
Cambridge, MA 02138<br>
<br>
<br>
</div>
</span></span></div>
<br>
<div>
<div>On Feb 14, 2012, at 1:34 PM, Steve Crocker wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div>The word alignment issue was very strong and the router people had con=
siderably more influence than the host folks. &nbsp;I tried to propose vari=
able length addressing using four bit nibbles in August 1974 and I got no t=
raction at all.<br>
<br>
Steve<br>
<br>
Sent from my iPhone<br>
<br>
On Feb 14, 2012, at 6:31 PM, Bob Braden &lt;<a href=3D"mailto:braden@isi.ed=
u">braden@isi.edu</a>&gt; wrote:<br>
<br>
<blockquote type=3D"cite">On 2/13/2012 7:53 PM, Noel Chiappa wrote:<br>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">From: Brian E Carpenter&lt;<a href=3D"mailto:bria=
n.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;<br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">The design error was made in the late 1970s, when=
 Louis Pouzin's advice<br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">that catenet addresses should be variable length,=
 with a format prefix,<br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">
<blockquote type=3D"cite">was not taken during the design of IPv4.<br>
</blockquote>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">Ironically, TCP/IP had variable length addresses =
put in _twice_, and they were<br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite">removed both times! (You can't make this stuff up=
! :-)<br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">Noel,<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">You probably remember this, but...<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Within the ARPA-funded Internet research program =
that designed IP and TCP, Jon Postel and<br>
</blockquote>
<blockquote type=3D"cite">Danny Cohen argued strenuously for variable lengt=
h addresses. (This must have been<br>
</blockquote>
<blockquote type=3D"cite">around 1979. I cannot name most of the other 10 p=
eople in the room, but I have<br>
</blockquote>
<blockquote type=3D"cite">a clear mental picture of Jon, in the back of the=
 room, fuming over this issue. Jon believed<br>
</blockquote>
<blockquote type=3D"cite">intensely in protocol extensibility.)<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">However, Vint Cerf, the ARPA program manager, rul=
es against variable length addresses and<br>
</blockquote>
<blockquote type=3D"cite">decreed the fixed length 32 bit word-aligned addr=
esses of RFC 791. His argument was that<br>
</blockquote>
<blockquote type=3D"cite">TCP/IP had to be simple to implement if it were t=
o succeed (and survive the juggernaut<br>
</blockquote>
<blockquote type=3D"cite">of the ISO OSI protocol suite).<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">System programmers of that day were familiar with=
 word-aligned data<br>
</blockquote>
<blockquote type=3D"cite">structures with fixed offsets, and variable lengt=
h addresses seemed to be (and in fact<br>
</blockquote>
<blockquote type=3D"cite">would be) harder to program and would make packet=
 dumps harder to interpret.<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">It was a political as much as a technical judgmen=
t, and Vint may have been right ... we<br>
</blockquote>
<blockquote type=3D"cite">can never know. We do know that IP eventually suc=
ceeded and OSI failed, but it<br>
</blockquote>
<blockquote type=3D"cite">was a near thing for awhile. Of course, there wer=
e other factors in the success<br>
</blockquote>
<blockquote type=3D"cite">of IP, such as Berkeley Unix.<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">It is to be noted that when it came time to defin=
e IPv6 some 20 years later, the IETF<br>
</blockquote>
<blockquote type=3D"cite">stuck with fixed length internet addresses.<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">Bob Braden<br>
</blockquote>
<blockquote type=3D"cite"><br>
</blockquote>
<blockquote type=3D"cite">_______________________________________________<b=
r>
</blockquote>
<blockquote type=3D"cite">Ietf mailing list<br>
</blockquote>
<blockquote type=3D"cite"><a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a=
><br>
</blockquote>
<blockquote type=3D"cite"><a href=3D"https://www.ietf.org/mailman/listinfo/=
ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br>
</blockquote>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/ietf<br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

From presnick@qualcomm.com  Tue Feb 14 10:38:05 2012
Return-Path: <presnick@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 55DD721F8679 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id neZWdfHfw62H for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:38:03 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id F0DB221F856C for <ietf@ietf.org>; Tue, 14 Feb 2012 10:38:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329244682; x=1360780682; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: x-originating-ip; z=Message-ID:=20<4F3AAA08.2040204@qualcomm.com>|Date:=20Tu e,=2014=20Feb=202012=2012:38:00=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20<ietf@ietf.org>|CC:=20<Jeff.Fi nkelstein@cox.com>,=20Daryl=20Tanner=20<daryl.tanner@blue yonder.co.uk>,=0D=0A=09Donald=20Eastlake=20<d3e3e3@gmail. com>,=20"ned+ietf@mauve.mrochek.com"=0D=0A=09<ned+ietf@ma uve.mrochek.com>,=20Owen=20DeLong=20<owen@delong.com>,=20 Ross=20Callon=0D=0A=09<rcallon@juniper.net>|Subject:=20Re :=20Last=20Call:=20<draft-weil-shared-transition-space-re quest-14.txt>=0D=0A=20(IANA=20Reserved=20IPv4=20Prefix=20 for=20Shared=20Address=20Space)=20to=20BCP|References:=20 <CB5FF399.1B4E7%jeff.finkelstein@cox.com>|In-Reply-To:=20 <CB5FF399.1B4E7%jeff.finkelstein@cox.com>|Content-Type: =20multipart/alternative=3B=0D=0A=09boundary=3D"--------- ---020905020100030206030201"|X-Originating-IP:=20[172.30. 39.5]; bh=ggP4TISupdLoTZPkk6w1HwhLlj74b8VOwyNoqC5hIIE=; b=ZUiQA0lB4+HGUblEyZCQLUqR+eOYEznwednjz0O4CuoPJfUFfaOH2g0l TR/L0VwFMeVdt2fQFdJh77p1w3F7b9XAkEmTmFf8LLg8XGmqp21x0QvBs eK0Y/gNxBLctBD4sO+/IVCd6WkuFb//507lE2v+3M2b1iy1IjLXvCHdFR Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,6620"; a="160801632"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 14 Feb 2012 10:38:02 -0800
X-IronPort-AV: E=Sophos;i="4.73,417,1325491200";  d="scan'208,217";a="196208026"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 14 Feb 2012 10:38:02 -0800
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 14 Feb 2012 10:38:01 -0800
Message-ID: <4F3AAA08.2040204@qualcomm.com>
Date: Tue, 14 Feb 2012 12:38:00 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>
In-Reply-To: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>
Content-Type: multipart/alternative; boundary="------------020905020100030206030201"
X-Originating-IP: [172.30.39.5]
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, Owen DeLong <owen@delong.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:38:05 -0000

--------------020905020100030206030201
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

To the addressed folks who's messages appear below:

I'm not sure I understand what you're saying. There was some objection 
at the beginning of this thread by Wes George, Noel Chiappa, and Brian 
Carpenter. I agreed that the document could be misunderstood as 
encouraging the use of the space as 1918 space and proposed some 
replacement text. There seemed to be some agreement around that text. 
Are you now objecting to that replacement text and want -14 published as 
is? Do you think the document should say that the new allocation can be 
used as 1918 space? If so, please explain.

pr

On 2/14/12 8:54 AM, Donald Eastlake wrote:
> I also support this draft.

On 2/14/12 9:06 AM, ned+ietf@mauve.mrochek.com wrote:
> On Tuesday, February 14, 2012, Daryl Tanner<daryl.tanner@blueyonder.co.uk  <mailto:daryl.tanner@blueyonder.co.uk>>  wrote:
>> I support this updated draft, and I am keen for this to be published as a
>> BCP.
>>      
> +1
>
>    
>> I believe the amendments in this revision clarify the usage and intended
>> purpose of the shared transition space.
>>      
> +1
>
>    
On 2/14/12 10:19 AM, Jeff.Finkelstein@cox.com wrote:
> I support this draft as updated.
>    

On 2/13/12 1:05 PM, Owen DeLong wrote:
> I support draft-weil as revised. There is a vital need for this to 
> move forward and the IETF should stop standing in the way and let ARIN 
> allocate the space already.

On 2/14/12 12:25 PM, Ross Callon wrote:

> +1
>    

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


--------------020905020100030206030201
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">
To the addressed folks who's messages appear below:<br>
<br>
I'm not sure I understand what you're saying. There was some objection
at the beginning of this thread by Wes George, Noel Chiappa, and Brian
Carpenter. I agreed that the document could be misunderstood as
encouraging the use of the space as 1918 space and proposed some
replacement text. There seemed to be some agreement around that text.
Are you now objecting to that replacement text and want -14 published
as is? Do you think the document should say that the new allocation can
be used as 1918 space? If so, please explain.<br>
<br>
pr<br>
<br>
On 2/14/12 8:54 AM, Donald Eastlake wrote:
<blockquote
 cite="mid:CAF4+nEERtpjGr33=f56rEuYf5PQO=w8p4HYvnTeiqghee5KiHg@mail.gmail.com"
 type="cite">I also support this draft.<br>
</blockquote>
<br>
On 2/14/12 9:06 AM, <a class="moz-txt-link-abbreviated" href="mailto:ned+ietf@mauve.mrochek.com">ned+ietf@mauve.mrochek.com</a> wrote:
<blockquote cite="mid:01OBYZWPJ4WM00ZUIL@mauve.mrochek.com" type="cite">
  <pre wrap="">On Tuesday, February 14, 2012, Daryl Tanner &lt;<a
 moz-do-not-send="true" href="mailto:daryl.tanner@blueyonder.co.uk">daryl.tanner@blueyonder.co.uk</a>&gt; wrote:</pre>
  <blockquote type="cite">
    <pre wrap="">I support this updated draft, and I am keen for this to be published as a
BCP.
    </pre>
  </blockquote>
  <pre wrap="">+1

  </pre>
  <blockquote type="cite">
    <pre wrap="">I believe the amendments in this revision clarify the usage and intended
purpose of the shared transition space.
    </pre>
  </blockquote>
  <pre wrap="">
+1

  </pre>
</blockquote>
On 2/14/12 10:19 AM, <a class="moz-txt-link-abbreviated" href="mailto:Jeff.Finkelstein@cox.com">Jeff.Finkelstein@cox.com</a> wrote:
<blockquote cite="mid:CB5FF399.1B4E7%25jeff.finkelstein@cox.com"
 type="cite">
  <pre wrap="">I support this draft as updated.
  </pre>
</blockquote>
<br>
On 2/13/12 1:05 PM, Owen DeLong wrote:
<blockquote cite="mid:2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com"
 type="cite">I support draft-weil as revised. There is a vital need for
this to move
forward and the IETF should stop standing in the way and let ARIN
allocate the space already.</blockquote>
<br>
On 2/14/12 12:25 PM, Ross Callon wrote:<br>
<br>
<blockquote type="cite">
  <pre wrap="">+1
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102</pre>
</body>
</html>

--------------020905020100030206030201--

From drc@virtualized.org  Tue Feb 14 10:49:21 2012
Return-Path: <drc@virtualized.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 30AB521F86BD for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:49:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xsQn+cCjRkP for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:49:20 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 8125321F8697 for <ietf@ietf.org>; Tue, 14 Feb 2012 10:49:20 -0800 (PST)
Received: from [192.168.2.159] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id DDA041705A; Tue, 14 Feb 2012 18:49:19 +0000 (UTC)
Subject: Re: Another last call for draft-weil
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_15D6FC5D-5283-46DC-80C6-31F86195974D"
From: David Conrad <drc@virtualized.org>
In-Reply-To: <5BB63F16-DA59-4B07-AA2B-457A1AF2B7F6@harvard.edu>
Date: Tue, 14 Feb 2012 10:49:18 -0800
Message-Id: <AC72C29F-9AFD-482F-B8B1-4627A31A7611@virtualized.org>
References: <5BB63F16-DA59-4B07-AA2B-457A1AF2B7F6@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:49:21 -0000

--Apple-Mail=_15D6FC5D-5283-46DC-80C6-31F86195974D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I'm curious:  how is the IETF stopping ARIN from allocating the space?

Thanks,
-drc

On Feb 14, 2012, at 10:33 AM, Bradner, Scott wrote:

> (not voting twice, my other address did not seem to work)
>=20
> +1
>=20
> On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:
>=20
>> +1.
>> =20
>> Ross
>> =20
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Owen DeLong
>> Sent: Monday, February 13, 2012 2:06 PM
>> To: ietf@ietf.org
>> Cc: draft-bdgks-arin-shared-transition-space@tools. org
>> Subject: Re: Another last call for draft-weil
>> =20
>> I support draft-weil as revised. There is a vital need for this to =
move forward and the IETF should stop standing in the way and let ARIN =
allocate the space already.
>> =20
>> Owen

--Apple-Mail=_15D6FC5D-5283-46DC-80C6-31F86195974D
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I'm curious: &nbsp;how is the IETF stopping ARIN from allocating the space?</div><div><br></div><div>Thanks,</div><div>-drc</div><div><br><div><div>On Feb 14, 2012, at 10:33 AM, Bradner, Scott wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">

<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
(not voting twice, my other address did not seem to work)
<div><br>
</div>
<div>+1
<div><br>
<div>
<div>On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div lang="EN-US" link="blue" vlink="purple" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div class="WordSection1" style="page: WordSection1; ">
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">+1.<o:p></o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Ross<o:p></o:p></span></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div>
<div style="border-right-style: none; border-bottom-style: none; border-left-style: none; border-width: initial; border-color: initial; border-top-style: solid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: 0in; ">
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">&nbsp;<a href="mailto:ietf-bounces@ietf.org" style="color: blue; text-decoration: underline; ">ietf-bounces@ietf.org</a>&nbsp;[mailto:ietf-bounces@ietf.org]&nbsp;<b>On
 Behalf Of&nbsp;</b>Owen DeLong<br>
<b>Sent:</b>&nbsp;Monday, February 13, 2012 2:06 PM<br>
<b>To:</b>&nbsp;<a href="mailto:ietf@ietf.org" style="color: blue; text-decoration: underline; ">ietf@ietf.org</a><br>
<b>Cc:</b>&nbsp;draft-bdgks-arin-shared-transition-space@tools. org<br>
<b>Subject:</b>&nbsp;Re: Another last call for draft-weil<o:p></o:p></span></div>
</div>
</div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
I support draft-weil as revised. There is a vital need for this to move forward and the IETF should stop standing in the way and let ARIN allocate the space already.<o:p></o:p></div>
<div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style="margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; ">
Owen</div></div></div></div></span></blockquote></div></div></div></div></blockquote></div></div></body></html>
--Apple-Mail=_15D6FC5D-5283-46DC-80C6-31F86195974D--

From sob@harvard.edu  Tue Feb 14 10:51:29 2012
Return-Path: <sob@harvard.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 4A36021E809F for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:51:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.141
X-Spam-Level: 
X-Spam-Status: No, score=-102.141 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kRraTK-KxsYs for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:51:28 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id AA4A521E8087 for <ietf@ietf.org>; Tue, 14 Feb 2012 10:51:28 -0800 (PST)
Received: from exchange.university.harvard.edu (unknown [10.35.2.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 6128EE8F87; Tue, 14 Feb 2012 13:51:24 -0500 (EST)
Received: from ENTWHUBT0000003.university.harvard.edu (192.168.36.24) by ENTWEDGE0000001.university.harvard.edu (10.35.2.152) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 14 Feb 2012 13:50:33 -0500
Received: from ENTWEXMB0000004.university.harvard.edu ([169.254.3.253]) by entwhubt0000003.university.harvard.edu ([192.168.36.24]) with mapi id 14.01.0355.002; Tue, 14 Feb 2012 13:51:21 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: David Conrad <drc@virtualized.org>
Subject: Re: Another last call for draft-weil
Thread-Topic: Another last call for draft-weil
Thread-Index: AQHM60csfkIEGKmop0Smx4sp9fzGsQ==
Date: Tue, 14 Feb 2012 18:51:19 +0000
Message-ID: <4CB41BAC-5280-4E8C-ACAF-8445DD8209AC@harvard.edu>
References: <5BB63F16-DA59-4B07-AA2B-457A1AF2B7F6@harvard.edu> <AC72C29F-9AFD-482F-B8B1-4627A31A7611@virtualized.org>
In-Reply-To: <AC72C29F-9AFD-482F-B8B1-4627A31A7611@virtualized.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [140.247.60.212]
Content-Type: text/html; charset="us-ascii"
Content-ID: <F27B79FD102DF84C9E60762C8B9D99B9@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:51:29 -0000

<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-lin=
e-break: after-white-space; ">
the IAB advised ARIN that such assignments were in the purview of the IETF
<div><br>
</div>
<div>Scott</div>
<div><br>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; c=
olor: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=
=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica;=
 font-style: normal; font-variant: normal; font-weight: normal; letter-spac=
ing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; tex=
t-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-s=
pacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertica=
l-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size=
-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Scott O Bradner</div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
Senior Technology&nbsp;Consultant<br>
<br>
Harvard University Information Technology<br>
Innovation &amp; Architecture<br>
(P) &#43;1 (617) 495 3864<br>
29 Oxford St. Rm 407<br>
Cambridge, MA 02138<br>
<br>
<br>
</div>
</span></span></div>
<br>
<div>
<div>On Feb 14, 2012, at 1:49 PM, David Conrad wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>I'm curious: &nbsp;how is the IETF stopping ARIN from allocating the s=
pace?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>-drc</div>
<div><br>
<div>
<div>On Feb 14, 2012, at 10:33 AM, Bradner, Scott wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
(not voting twice, my other address did not seem to work)
<div><br>
</div>
<div>&#43;1
<div><br>
<div>
<div>On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: brea=
k-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div class=3D"WordSection1" style=3D"page: WordSection1; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); ">&#43;1.<o:p></o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); ">Ross<o:p></o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div>
<div style=3D"border-right-style: none; border-bottom-style: none; border-l=
eft-style: none; border-width: initial; border-color: initial; border-top-s=
tyle: solid; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; p=
adding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: 0in=
; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; ">From:=
</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;=
 ">&nbsp;<a href=3D"mailto:ietf-bounces@ietf.org" style=3D"color: blue; tex=
t-decoration: underline; ">ietf-bounces@ietf.org</a>&nbsp;[mailto:ietf-boun=
ces@ietf.org]&nbsp;<b>On
 Behalf Of&nbsp;</b>Owen DeLong<br>
<b>Sent:</b>&nbsp;Monday, February 13, 2012 2:06 PM<br>
<b>To:</b>&nbsp;<a href=3D"mailto:ietf@ietf.org" style=3D"color: blue; text=
-decoration: underline; ">ietf@ietf.org</a><br>
<b>Cc:</b>&nbsp;draft-bdgks-arin-shared-transition-space@tools. org<br>
<b>Subject:</b>&nbsp;Re: Another last call for draft-weil<o:p></o:p></span>=
</div>
</div>
</div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<o:p>&nbsp;</o:p></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
I support draft-weil as revised. There is a vital need for this to move for=
ward and the IETF should stop standing in the way and let ARIN allocate the=
 space already.<o:p></o:p></div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<o:p>&nbsp;</o:p></div>
</div>
<div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
Owen</div>
</div>
</div>
</div>
</span></blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

From christopher.morrow@gmail.com  Tue Feb 14 11:30:48 2012
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 6E33421E809F for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 11:30:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4KyQ8YktBZK for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 11:30:48 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E35CD21E801B for <ietf@ietf.org>; Tue, 14 Feb 2012 11:30:47 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so391218obb.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 11:30:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fyJfNPUWIYo6CMNc1F2x18DxbwlD5rgHsaSzXaAqyS0=; b=Bk5gxg3VM2m5p80WEBm5eu22KqOxQ8L0nxK/rA1HXIejanJnbri1czwA4Cvw/VY0ap eUOVrCUlIG+MxQhkT9wjVX+rHPnKvk8RXVTPUrDOxiqDCvlczE6PS/gWfZ0u1bsPPV4B IeA6VzPP/RjEKj6lJBgMh16qw/QCalujaC7uM=
MIME-Version: 1.0
Received: by 10.60.20.6 with SMTP id j6mr1135586oee.17.1329247847563; Tue, 14 Feb 2012 11:30:47 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.182.68.169 with HTTP; Tue, 14 Feb 2012 11:30:47 -0800 (PST)
In-Reply-To: <AC72C29F-9AFD-482F-B8B1-4627A31A7611@virtualized.org>
References: <5BB63F16-DA59-4B07-AA2B-457A1AF2B7F6@harvard.edu> <AC72C29F-9AFD-482F-B8B1-4627A31A7611@virtualized.org>
Date: Tue, 14 Feb 2012 14:30:47 -0500
X-Google-Sender-Auth: h6UjlBtDtvapIlGSQ8YWJfDOWi4
Message-ID: <CAL9jLaZCWnzz2mg-haUFap066LX7XjXAdno_QQ+dK6BFY6GmNQ@mail.gmail.com>
Subject: Re: Another last call for draft-weil
From: Christopher Morrow <morrowc.lists@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "Bradner, Scott" <sob@harvard.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:30:48 -0000

On Tue, Feb 14, 2012 at 1:49 PM, David Conrad <drc@virtualized.org> wrote:
> I'm curious: =A0how is the IETF stopping ARIN from allocating the space?
>

+1

though honestly I'm not a fan of the process.

> Thanks,
> -drc
>
> On Feb 14, 2012, at 10:33 AM, Bradner, Scott wrote:
>
> (not voting twice, my other address did not seem to work)
>
> +1
>
> On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:
>
> +1.
>
> Ross
>
> From:=A0ietf-bounces@ietf.org=A0[mailto:ietf-bounces@ietf.org]=A0On Behal=
f Of=A0Owen
> DeLong
> Sent:=A0Monday, February 13, 2012 2:06 PM
> To:=A0ietf@ietf.org
> Cc:=A0draft-bdgks-arin-shared-transition-space@tools. org
> Subject:=A0Re: Another last call for draft-weil
>
> I support draft-weil as revised. There is a vital need for this to move
> forward and the IETF should stop standing in the way and let ARIN allocat=
e
> the space already.
>
> Owen
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From ned+ietf@mauve.mrochek.com  Tue Feb 14 11:53:44 2012
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 3F70C21E8087 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 11:53: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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ucktbzt-PVHJ for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 11:53:41 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 250A521E8016 for <ietf@ietf.org>; Tue, 14 Feb 2012 11:53:40 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBZ9WSAF1S00763W@mauve.mrochek.com> for ietf@ietf.org; Tue, 14 Feb 2012 11:53:37 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBR11Q7E9S00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 14 Feb 2012 11:53:34 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>
Date: Tue, 14 Feb 2012 11:50:49 -0800 (PST)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-reply-to: "Your message dated Tue, 14 Feb 2012 12:38:00 -0600" <4F3AAA08.2040204@qualcomm.com>
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, Owen DeLong <owen@delong.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:53:44 -0000

> To the addressed folks who's messages appear below:

> I'm not sure I understand what you're saying. There was some objection
> at the beginning of this thread by Wes George, Noel Chiappa, and Brian
> Carpenter. I agreed that the document could be misunderstood as
> encouraging the use of the space as 1918 space and proposed some
> replacement text. There seemed to be some agreement around that text.
> Are you now objecting to that replacement text and want -14 published as
> is? Do you think the document should say that the new allocation can be
> used as 1918 space? If so, please explain.

Not sure how a +1 to a statement saying "I support this updated draft, and I
am keen for this to be published as a BCP." can be interpreted in any but one
way, or for that matter how it can be stated much differently.

Anyway, to use different words, I would like to see the current draft 
approved and published as a BCP. Clear enough?

				Ned

From lsawyer@gci.com  Tue Feb 14 11:57:27 2012
Return-Path: <lsawyer@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDAC421E8016 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 11:57:27 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JuMvbsiwFObJ for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 11:57:27 -0800 (PST)
Received: from mailgw1.gci.com (mailgw1.gci.com [209.165.141.90]) by ietfa.amsl.com (Postfix) with ESMTP id 1B18221F84A7 for <ietf@ietf.org>; Tue, 14 Feb 2012 11:57:27 -0800 (PST)
Received: from FNB1CAS01.gci.com (10.100.230.66) by mailgw1.gci.com (172.19.0.25) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 14 Feb 2012 10:58:00 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by FNB1CAS01.gci.com ([10.100.230.66]) with mapi; Tue, 14 Feb 2012 10:57:26 -0900
From: Leif Sawyer <lsawyer@gci.com>
To: Pete Resnick <presnick@qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 14 Feb 2012 10:57:24 -0900
Subject: RE: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczrSAHaMRFh49pZQY2aXRchPcnMVgACXlGg
Message-ID: <18B2C6E38A3A324986B392B2D18ABC5101D4D06FE6@fnb1mbx01.gci.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com>
In-Reply-To: <4F3AAA08.2040204@qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, Owen DeLong <owen@delong.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:57:27 -0000

Pete Resnick wrote:
> I'm not sure I understand what you're saying. There was some=20
> objection at the beginning of this thread by Wes George, Noel=20
> Chiappa, and Brian Carpenter. I agreed that the document=20
> could be misunderstood as encouraging the use of the space as=20
> 1918 space and proposed some replacement text. There seemed=20
> to be some agreement around that text. Are you now objecting=20
> to that replacement text and want -14 published as is? Do you=20
> think the document should say that the new allocation can be=20
> used as 1918 space? If so, please explain.


On the first hand,  I do support draft-weil. I think I
understand the use cases enough to see that it *is* required,
especially for large MSO's, and potentially larger enterprises.


On the other hand, I can see the confusion regarding "using RFC-1918 space =
*for this purpose*"  vs  "use this space as *additional RFC-1918*.  The for=
mer just doesn't work due to
unmanaged overlap.   The latter *seems* like it should work,
but if you play it out until the first vendor starts releasing
equipment that uses it, you've now joined the first-case scenerio.

On the gripping hand, I hate the back-and-forth quibbling over the tiniest =
motes, hoping that the delays will just make the problem disappear...

So yes, lets please move this draft forward, with the text cleaning stating=
 that it NOT be used as RFC-1918 space.

From presnick@qualcomm.com  Tue Feb 14 12:09:21 2012
Return-Path: <presnick@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 74BE721F8516 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VPaDX2qIYDGp for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:09:19 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 9283021F850F for <ietf@ietf.org>; Tue, 14 Feb 2012 12:09:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329250159; x=1360786159; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F3ABF6C.1030803@qualcomm.com>|Date:=20Tu e,=2014=20Feb=202012=2014:09:16=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20<ned+ietf@mauve.mrochek.com> |CC:=20<ietf@ietf.org>|Subject:=20Re:=20Last=20Call:=20<d raft-weil-shared-transition-space-request-14.txt>=0D=0A =20(IANA=20Reserved=20IPv4=20Prefix=20for=20Shared=20Addr ess=20Space)=20to=20BCP|References:=20<CB5FF399.1B4E7%jef f.finkelstein@cox.com>=09<4F3AAA08.2040204@qualcomm.com> =20<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>|In-Reply-To:=20 <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>|Content-Type:=20te xt/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=zxzZxxBqRg4r2L03LwKFbsudx4i85UsB7zlElzXnm60=; b=oVlluZ+y6wpOeqh3UqUclAeP1UAySNb3go0socbE1E59CeeVZHZj0Flk NVbiRlVwdobl5DBnkyWYMhTpNzgnr2HZodKS+rSQ7OH0taV3Vk/iWvZcm EpkC5UWdhpKVXzkVBwJJHvkWIrxwTsUD4u4ViFYZNcLkkLjd0qUHByDBR Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,6620"; a="163138111"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 14 Feb 2012 12:09:19 -0800
X-IronPort-AV: E=Sophos;i="4.73,417,1325491200"; d="scan'208";a="256388148"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 14 Feb 2012 12:09:18 -0800
Received: from Macintosh-4.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 14 Feb 2012 12:09:17 -0800
Message-ID: <4F3ABF6C.1030803@qualcomm.com>
Date: Tue, 14 Feb 2012 14:09:16 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ned+ietf@mauve.mrochek.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>	<4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:09:21 -0000

On 2/14/12 1:50 PM, ned+ietf@mauve.mrochek.com wrote:

>> Are you now objecting to that replacement text and want -14 published as
>> is? Do you think the document should say that the new allocation can be
>> used as 1918 space? If so, please explain.
>
> Not sure how a +1 to a statement saying "I support this updated draft, 
> and I
> am keen for this to be published as a BCP." can be interpreted in any 
> but one
> way, or for that matter how it can be stated much differently.
>
> Anyway, to use different words, I would like to see the current draft 
> approved and published as a BCP. Clear enough?

Nope. Perhaps my question was unclear. I'll try and ask my question 
again with different words:

Do you, or do you not, object to the proposed change that changes the 
text from saying, "This space may be used just as 1918 space" to "This 
space has limitations and cannot be used as 1918 space"? Nobody on the 
list objected to that new text. That new text significantly changes -14. 
You have stated your support for -14. Do you object to changing the text?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From ned+ietf@mauve.mrochek.com  Tue Feb 14 12:14:16 2012
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 B754621E80FC for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:14:16 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozHLQW3NbZJG for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:14:16 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id E1CDC21E80E0 for <ietf@ietf.org>; Tue, 14 Feb 2012 12:14:15 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBZANB4CRK001J6N@mauve.mrochek.com> for ietf@ietf.org; Tue, 14 Feb 2012 12:14:13 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OBR11Q7E9S00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 14 Feb 2012 12:14:06 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OBZAN65TN000ZUIL@mauve.mrochek.com>
Date: Tue, 14 Feb 2012 12:12:34 -0800 (PST)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-reply-to: "Your message dated Tue, 14 Feb 2012 14:09:16 -0600" <4F3ABF6C.1030803@qualcomm.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:14:17 -0000

> On 2/14/12 1:50 PM, ned+ietf@mauve.mrochek.com wrote:

> >> Are you now objecting to that replacement text and want -14 published as
> >> is? Do you think the document should say that the new allocation can be
> >> used as 1918 space? If so, please explain.
> >
> > Not sure how a +1 to a statement saying "I support this updated draft,
> > and I
> > am keen for this to be published as a BCP." can be interpreted in any
> > but one
> > way, or for that matter how it can be stated much differently.
> >
> > Anyway, to use different words, I would like to see the current draft
> > approved and published as a BCP. Clear enough?

> Nope. Perhaps my question was unclear. I'll try and ask my question
> again with different words:

> Do you, or do you not, object to the proposed change that changes the
> text from saying, "This space may be used just as 1918 space" to "This
> space has limitations and cannot be used as 1918 space"? Nobody on the
> list objected to that new text. That new text significantly changes -14.
> You have stated your support for -14. Do you object to changing the text?

I assumed the proposed change was in the current draft - isn't that how it's
supposed to be done? Anyway, I think the change is fine, but I also think
the draft is acceptable without it.

				Ned

From randy@psg.com  Tue Feb 14 12:35:16 2012
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 E385521F8620 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:35:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BhJ0cBAH0MYD for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:35:15 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 7E36421F847F for <ietf@ietf.org>; Tue, 14 Feb 2012 12:35:14 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RxP5k-000Omd-WD; Tue, 14 Feb 2012 20:35:13 +0000
Date: Tue, 14 Feb 2012 12:35:12 -0800
Message-ID: <m2d39hi267.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>	(IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <4F3ABF6C.1030803@qualcomm.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:35:16 -0000

> Do you, or do you not, object to the proposed change that changes the 
> text from saying, "This space may be used just as 1918 space" to "This 
> space has limitations and cannot be used as 1918 space"?

what silliness.  it will be used as rfc 1918 space no matter what the document
says.

nine years ago i was in bologna and did a traceroute out.  i was surprised 
to find that the isp was using un-announced us military space as rfc 1918 
space internal to their network.  this turns out to be common.

any thought that this is not just adding to rfc 1918 is pure bs.

randy



From amorris@amsl.com  Tue Feb 14 12:38:33 2012
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A87FD21E8045; Tue, 14 Feb 2012 12:38:33 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+9U4j-afkXf; Tue, 14 Feb 2012 12:38:23 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 1B14821E8019; Tue, 14 Feb 2012 12:38:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 15B6A12C891; Tue, 14 Feb 2012 12:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2KcHZk7143b; Tue, 14 Feb 2012 12:38:22 -0800 (PST)
Received: from [12.22.58.163] (unknown [12.22.58.163]) by c8a.amsl.com (Postfix) with ESMTPSA id EFDAC12C823; Tue, 14 Feb 2012 12:38:22 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Reminder: T-shirt Design Contest for IETF 83
Date: Tue, 14 Feb 2012 12:38:22 -0800
Message-Id: <9FE913F2-E516-468C-AFFB-DE0BB3C4E9D8@amsl.com>
To: ietf-announce@ietf.org, IETF-Discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:38:33 -0000

This is a reminder that the IAOC is conducting a T-Shirt Design Contest =
to develop a unique t-shirt for the Paris meeting. You have until this =
Friday, Feb 17 to submit your design for consideration. We've received =
two submissions so far and you can see them here: =
http://www.ietf.org/meeting/83/t-shirt-design-contest-submissions.html.

If you have design skills, or can strongarm someone else who does, =
please view this as an opportunity to show your support for the IETF. =
The Secretariat will take care of producing the shirts once the winning =
design is selected, and the purchase price (approximately $25 USD) will =
go to support the IETF.  Whoever submits the winning design will receive =
a free t-shirt.=20

Please send your design to tshirtcontest@ietf.org. Designs should be =
delivered as EPS or Adobe Illustrator files. A t-shirt template is =
available for download here: =
ietf.org/meeting/83/t-shirt-contest-template.eps. Your submission should =
include t-shirt color, and the design for both front and back of the =
shirt. Please note: designs should include the IETF logo, but cannot =
include any company logos. Like an Internet-Draft, a t-shirt design =
submission is authored by individuals.=20

Regards,
Alexa

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From lsawyer@gci.com  Tue Feb 14 12:40:46 2012
Return-Path: <lsawyer@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A0921E80E3 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:40:46 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yISIQdi6+Jxk for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:40:45 -0800 (PST)
Received: from mailgw2.gci.com (mailgw2.gci.com [209.165.141.87]) by ietfa.amsl.com (Postfix) with ESMTP id AD86D21E80E2 for <ietf@ietf.org>; Tue, 14 Feb 2012 12:40:45 -0800 (PST)
Received: from FNB1CAS01.gci.com (10.100.230.66) by mailgw2.gci.com (172.19.0.32) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 14 Feb 2012 11:40:42 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by FNB1CAS01.gci.com ([10.100.230.66]) with mapi; Tue, 14 Feb 2012 11:40:44 -0900
From: Leif Sawyer <lsawyer@gci.com>
To: Randy Bush <randy@psg.com>, Pete Resnick <presnick@qualcomm.com>
Date: Tue, 14 Feb 2012 11:40:42 -0900
Subject: RE: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczrWDD+QGIRRZI0Tuih11+4jauEXAAAEPjA
Message-ID: <18B2C6E38A3A324986B392B2D18ABC5101D4D0704B@fnb1mbx01.gci.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com>	<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com>
In-Reply-To: <m2d39hi267.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:40:46 -0000

Randy Bush writes:
> in response to Pete Resnick, who wrote:
>> Do you, or do you not, object to the proposed change that=20
>> changes the text from saying, "This space may be used just
>> as 1918 space" to "This space has limitations and cannot be
>> used as 1918 space"?
>=20
> what silliness.  it will be used as rfc 1918 space no matter=20
> what the document
> says.
>=20
> nine years ago i was in bologna and did a traceroute out.  i=20
> was surprised to find that the isp was using un-announced us
> military space as rfc 1918 space internal to their network.
>  this turns out to be common.
>=20
> any thought that this is not just adding to rfc 1918 is pure
> bs.


In that I completely agree with what Randy is saying, the point
that needs to be made is that this should not be officially
sanctioned as RFC-1918 space --  no manufacturer or programmer
should treat this netblock the same.


If some fly-by-night company chooses to use it on their own,
well, then they have chosen to operate outside the bounds of
the best-principles - exactly the same as in Randy's example.


From brian.e.carpenter@gmail.com  Tue Feb 14 12:47:29 2012
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 C1DA721E8018 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.427
X-Spam-Level: 
X-Spam-Status: No, score=-103.427 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cyQxU306lfT7 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:47:29 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3233621E8026 for <ietf@ietf.org>; Tue, 14 Feb 2012 12:47:29 -0800 (PST)
Received: by yenm3 with SMTP id m3so337673yen.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 12:47:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2Y2lrXBbvWl2h4taoJQi82i0LFe8Vtrsyp+UTMovwrA=; b=UwMjiZcGnjcWEa4uNsUILmyzOnV8oFbQT434fx6nSmO9E1hkhwpaNsqR3nPN+3G/jF 4cy5HLqHbuKBrUmL9t+nXDT6r0EyZTrRbtDAVe42xyHDPpNw1xFezUdo/s/o3+0JEmkm 22KTqElfZjx1mkygJ3Z93L8Y3KiUfMMCCxZNU=
Received: by 10.50.153.198 with SMTP id vi6mr37502581igb.30.1329252448603; Tue, 14 Feb 2012 12:47:28 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id wn7sm21186175igc.0.2012.02.14.12.47.25 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 12:47:27 -0800 (PST)
Message-ID: <4F3AC855.6010304@gmail.com>
Date: Wed, 15 Feb 2012 09:47:17 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>	<4F3AAA08.2040204@qualcomm.com>	<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>	<4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com>
In-Reply-To: <m2d39hi267.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:47:29 -0000

On 2012-02-15 09:35, Randy Bush wrote:
>> Do you, or do you not, object to the proposed change that changes the 
>> text from saying, "This space may be used just as 1918 space" to "This 
>> space has limitations and cannot be used as 1918 space"?
> 
> what silliness.  it will be used as rfc 1918 space no matter what the document
> says.

Of course it will. My suggestion was to change the text to "is not intended
to be used" instead of "can be used", hoping that would be viewed as a
fair warning.
http://www.ietf.org/mail-archive/web/ietf/current/msg71596.html

    Brian

> 
> nine years ago i was in bologna and did a traceroute out.  i was surprised 
> to find that the isp was using un-announced us military space as rfc 1918 
> space internal to their network.  this turns out to be common.
> 
> any thought that this is not just adding to rfc 1918 is pure bs.
> 
> randy
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From randy@psg.com  Tue Feb 14 12:49:35 2012
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 D1AA321E8018 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dV8ZCxdAlDgE for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:49:35 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E845321E80F1 for <ietf@ietf.org>; Tue, 14 Feb 2012 12:49:27 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RxPJX-000Ool-26; Tue, 14 Feb 2012 20:49:27 +0000
Date: Tue, 14 Feb 2012 12:49:26 -0800
Message-ID: <m2bop1m97t.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Leif Sawyer <lsawyer@gci.com>
Subject: Re: Last Call:	<draft-weil-shared-transition-space-request-14.txt>	(IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <18B2C6E38A3A324986B392B2D18ABC5101D4D0704B@fnb1mbx01.gci.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <18B2C6E38A3A324986B392B2D18ABC5101D4D0704B@fnb1mbx01.gci.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:49:36 -0000

> In that I completely agree with what Randy is saying, the point
> that needs to be made is that this should not be officially
> sanctioned as RFC-1918 space --  no manufacturer or programmer
> should treat this netblock the same.
> 
> If some fly-by-night company chooses to use it on their own,
> well, then they have chosen to operate outside the bounds of
> the best-principles - exactly the same as in Randy's example.

and the packets will be very ashamed, right?

we can say all the crap we want, but it will be used as 1918 space and,
like 1918 space, bgp announcesments of it will leak.  get over it.

randy

From adrian@olddog.co.uk  Tue Feb 14 12:53:14 2012
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 6FD3B21E8087 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:53:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2B4aWWZ-BGt for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:53:13 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 1B17221E801D for <ietf@ietf.org>; Tue, 14 Feb 2012 12:52:51 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1EKqkbU010073;  Tue, 14 Feb 2012 20:52:46 GMT
Received: from 950129200 (cust.static.46-14-88-128.swisscomdata.ch [46.14.88.128]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q1EKqh8s010051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 14 Feb 2012 20:52:45 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'todd glassey'" <tglassey@earthlink.net>
References: <01a801cce827$60060e80$20122b80$@olddog.co.uk>	<6.2.5.6.2.20120212011537.05c62e20@resistor.net>	<03e501cce9b1$ed0f2e20$c72d8a60$@olddog.co.uk> <4F3A9D0B.3070604@earthlink.net>
In-Reply-To: <4F3A9D0B.3070604@earthlink.net>
Subject: RE: Furthering discussions about BCP79 sanctions
Date: Tue, 14 Feb 2012 20:52:36 -0000
Message-ID: <030d01cceb5a$9a89d510$cf9d7f30$@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: AQGDJ+LkHplH6a9DlbHfpzKg2UOqLgICudWkAVJ8JTUBtMefIJaoFFYQ
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:53:14 -0000

Todd,

You may or may not be right about whether an individual can make a decision to
disclose. In my experience they often can't, but do have the power to
request/implore their employer to disclose.

On the other hand, they *do* have the power to not participate.

BCP79 offers this choice and I make no comment about which is preferable.
However, it is clear from BCP79 that individuals have the choice and the
responsibility to choose.

Thanks,
Adrian
 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of todd
> glassey
> Sent: 14 February 2012 17:43
> To: ietf@ietf.org
> Subject: Re: Furthering discussions about BCP79 sanctions
> 
> On 2/12/2012 10:12 AM, Adrian Farrel wrote:
> > Hi SM,
> 
> So isnt the real issue that of informed consent? If you dont know that
> someone else has already existing work is it their fault for not telling
> the IETF?
> 
> If so then there would also need to be some form of process identical to
> this for verifying that the people participating hold legal power of
> attorney pertaining to that work for their sponsors, or they cannot make
> any 'management decisions' pertaining to any project.
> 
> The misunderstanding in the IETF BCP78 and BCP79 documents is that
> one-size fits all for IETF participants. It simply cannot - In fact many
> participants are there to work on processes and efforts for their
> sponsors who have no legal power of attorney for their sponsors what so
> ever. This is part of the myriad of misrepresentations that the IETF and
> its parent ISOC are still trying to get the rest of the world to swallow
> IMHO.
> 
> Todd
> 
> >
> >>> There has been some discussion on this list about
> >>> draft-farrresnickel-ipr-sanctions-00.  Thanks for the input.
> >>>
> >>> The conversation seems to be partitioned into:
> >>> - discussion of sanctions and how to apply them
> >>> - discussion of measures that can be taken to
> >>>   help people to adhere to BCP79
> >>
> >> The following messages are about the "help people":
> >>
> >> http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html
> >> http://www.ietf.org/mail-archive/web/marf/current/msg02081.html
> >
> > Yes. I've been watching those threads, and I think that some other WGs are
> > thinking of following similar procedures.
> >
> >>> Furthermore, there is some debate about who should/can be responsible
> for
> >>> applying sanctions.
> >
> > [snip]
> >
> >> In Appendix A:
> >>
> >>   "-  Does the large number of patents that the individual has authored
> >>       provide any level of excuse for failing to notice that one of
> >>       their patents covered the IETF work?"
> >>
> >> That should be "the individual has invented".
> >
> > Yes.
> >
> >> I suggest removing the above as prolific inventors should pay more
> >> attention to BCP 79.
> >
> > I'm inclined to agree with you.
> >
> > Others feel that there may be some mitigation in this case.
> >
> > By listing the point, we are giving the WG chairs the opportunity to
consider
> > it. They may deduce that it provides an excuse, no excuse, or exacerbates
the
> > case.
> >
> >> Section 6.1.2 of BCP 79 is about an IETF Participant's IPR in
> >> Contributions by others.   Should sanctions be considered if the
> >> individual participates and does not disclose?
> >
> > Yes. That is certainly my intention in this document. All violations of BCP
79
> > are cause to consider sanctions. The severity of the case may be judged by
> many
> > factors, and I suppose that the level of "participation" may be one of these
> > factors. I am hoping that Section 2.1 makes the first point clear, and
Appendix
> > A the second point.
> >
> > Cheers,
> > Adrian
> >
> >
> >
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
> 
> 
> --
> Todd S. Glassey
> This is from my personal email account and any materials from this
> account come with personal disclaimers.
> 
> Further I OPT OUT of any and all commercial emailings.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From lsawyer@gci.com  Tue Feb 14 12:56:14 2012
Return-Path: <lsawyer@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA1521E8109 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:56:14 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EmY63oMYJbKB for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 12:56:14 -0800 (PST)
Received: from mailgw1.gci.com (mailgw1.gci.com [209.165.141.90]) by ietfa.amsl.com (Postfix) with ESMTP id EEFD821E8105 for <ietf@ietf.org>; Tue, 14 Feb 2012 12:56:13 -0800 (PST)
Received: from FNB1CAS01.gci.com (10.100.230.66) by mailgw1.gci.com (172.19.0.25) with Microsoft SMTP Server (TLS) id 8.2.234.1; Tue, 14 Feb 2012 11:56:48 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by FNB1CAS01.gci.com ([10.100.230.66]) with mapi; Tue, 14 Feb 2012 11:56:13 -0900
From: Leif Sawyer <lsawyer@gci.com>
To: Randy Bush <randy@psg.com>
Date: Tue, 14 Feb 2012 11:56:12 -0900
Subject: RE: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Topic: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
Thread-Index: AczrWpK19GFt7sRJSvmidTETBZBjgQAAEfNg
Message-ID: <18B2C6E38A3A324986B392B2D18ABC5101D4D07072@fnb1mbx01.gci.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com>	<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com>	<m2d39hi267.wl%randy@psg.com> <18B2C6E38A3A324986B392B2D18ABC5101D4D0704B@fnb1mbx01.gci.com> <m2bop1m97t.wl%randy@psg.com>
In-Reply-To: <m2bop1m97t.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:56:14 -0000

Randy Bush writes:
> in response to me:
> > In that I completely agree with what Randy is saying, the point
> > that needs to be made is that this should not be officially
> > sanctioned as RFC-1918 space --  no manufacturer or programmer
> > should treat this netblock the same.
> >=20
> > If some fly-by-night company chooses to use it on their own,
> > well, then they have chosen to operate outside the bounds of
> > the best-principles - exactly the same as in Randy's example.
>=20
> and the packets will be very ashamed, right?
>=20
> we can say all the crap we want, but it will be used as 1918=20
> space and, like 1918 space, bgp announcesments of it will leak.
> get over it.

And that's fine -- on a per-operator basis --  they chose their path.

What we're trying to avoid by explicitly NOT marking this as RFC-1918
space is  VENDORS  using it inside their equipment, thereby negating
the entire practical use of the space.




From tnadeau@lucidvision.com  Tue Feb 14 13:25:00 2012
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7B321E8108 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 13:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level: 
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[AWL=0.256,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGY-b-pbg6aR for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 13:24:59 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8103421E8104 for <ietf@ietf.org>; Tue, 14 Feb 2012 13:24:59 -0800 (PST)
Received: from [192.168.1.94] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id B61B92088EEF; Tue, 14 Feb 2012 16:24:58 -0500 (EST)
Subject: Re: Furthering discussions about BCP79 sanctions
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <030d01cceb5a$9a89d510$cf9d7f30$@olddog.co.uk>
Date: Tue, 14 Feb 2012 16:24:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <07FC7247-CB08-4721-A756-B0B6BFFF6DDA@lucidvision.com>
References: <01a801cce827$60060e80$20122b80$@olddog.co.uk>	<6.2.5.6.2.20120212011537.05c62e20@resistor.net>	<03e501cce9b1$ed0f2e20$c72d8a60$@olddog.co.uk> <4F3A9D0B.3070604@earthlink.net> <030d01cceb5a$9a89d510$cf9d7f30$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:25:00 -0000

	I agree with Adrian. Individuals come to the IETF, not =
companies. Sure they are employed by companies, but they also have to =
follow the rules stated in BCP79.   I am really tired of the myriad of =
excuses people have given in the past about why they have not been able =
to comply. Its a really, really simple thing to read and understand the =
rules about the IETF's IPR policy BEFORE you submit a draft (or speak at =
a meeting), and WG chairs go out of their way to give people a number of =
warnings and reminders about this.  If after all of that you disagree, =
then go home.

	--Tom

=09

> Todd,
>=20
> You may or may not be right about whether an individual can make a =
decision to
> disclose. In my experience they often can't, but do have the power to
> request/implore their employer to disclose.
>=20
> On the other hand, they *do* have the power to not participate.
>=20
> BCP79 offers this choice and I make no comment about which is =
preferable.
> However, it is clear from BCP79 that individuals have the choice and =
the
> responsibility to choose.
>=20
> Thanks,
> Adrian
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of todd
>> glassey
>> Sent: 14 February 2012 17:43
>> To: ietf@ietf.org
>> Subject: Re: Furthering discussions about BCP79 sanctions
>>=20
>> On 2/12/2012 10:12 AM, Adrian Farrel wrote:
>>> Hi SM,
>>=20
>> So isnt the real issue that of informed consent? If you dont know =
that
>> someone else has already existing work is it their fault for not =
telling
>> the IETF?
>>=20
>> If so then there would also need to be some form of process identical =
to
>> this for verifying that the people participating hold legal power of
>> attorney pertaining to that work for their sponsors, or they cannot =
make
>> any 'management decisions' pertaining to any project.
>>=20
>> The misunderstanding in the IETF BCP78 and BCP79 documents is that
>> one-size fits all for IETF participants. It simply cannot - In fact =
many
>> participants are there to work on processes and efforts for their
>> sponsors who have no legal power of attorney for their sponsors what =
so
>> ever. This is part of the myriad of misrepresentations that the IETF =
and
>> its parent ISOC are still trying to get the rest of the world to =
swallow
>> IMHO.
>>=20
>> Todd
>>=20
>>>=20
>>>>> There has been some discussion on this list about
>>>>> draft-farrresnickel-ipr-sanctions-00.  Thanks for the input.
>>>>>=20
>>>>> The conversation seems to be partitioned into:
>>>>> - discussion of sanctions and how to apply them
>>>>> - discussion of measures that can be taken to
>>>>>  help people to adhere to BCP79
>>>>=20
>>>> The following messages are about the "help people":
>>>>=20
>>>> http://www.ietf.org/mail-archive/web/ccamp/current/msg13082.html
>>>> http://www.ietf.org/mail-archive/web/marf/current/msg02081.html
>>>=20
>>> Yes. I've been watching those threads, and I think that some other =
WGs are
>>> thinking of following similar procedures.
>>>=20
>>>>> Furthermore, there is some debate about who should/can be =
responsible
>> for
>>>>> applying sanctions.
>>>=20
>>> [snip]
>>>=20
>>>> In Appendix A:
>>>>=20
>>>>  "-  Does the large number of patents that the individual has =
authored
>>>>      provide any level of excuse for failing to notice that one of
>>>>      their patents covered the IETF work?"
>>>>=20
>>>> That should be "the individual has invented".
>>>=20
>>> Yes.
>>>=20
>>>> I suggest removing the above as prolific inventors should pay more
>>>> attention to BCP 79.
>>>=20
>>> I'm inclined to agree with you.
>>>=20
>>> Others feel that there may be some mitigation in this case.
>>>=20
>>> By listing the point, we are giving the WG chairs the opportunity to
> consider
>>> it. They may deduce that it provides an excuse, no excuse, or =
exacerbates
> the
>>> case.
>>>=20
>>>> Section 6.1.2 of BCP 79 is about an IETF Participant's IPR in
>>>> Contributions by others.   Should sanctions be considered if the
>>>> individual participates and does not disclose?
>>>=20
>>> Yes. That is certainly my intention in this document. All violations =
of BCP
> 79
>>> are cause to consider sanctions. The severity of the case may be =
judged by
>> many
>>> factors, and I suppose that the level of "participation" may be one =
of these
>>> factors. I am hoping that Section 2.1 makes the first point clear, =
and
> Appendix
>>> A the second point.
>>>=20
>>> Cheers,
>>> Adrian
>>>=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>=20
>>=20
>>=20
>> --
>> Todd S. Glassey
>> This is from my personal email account and any materials from this
>> account come with personal disclaimers.
>>=20
>> Further I OPT OUT of any and all commercial emailings.
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From mrex@sap.com  Tue Feb 14 13:40:37 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547B121E8016 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 13:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.624
X-Spam-Level: 
X-Spam-Status: No, score=-9.624 tagged_above=-999 required=5 tests=[AWL=-0.375, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_BACKHAIR_44=1, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rtIuR8ophyBh for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 13:40:36 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 96A4021E8011 for <ietf@ietf.org>; Tue, 14 Feb 2012 13:40:36 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1ELeZsn029615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2012 22:40:35 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202142140.q1ELeYrK016229@fs4113.wdf.sap.corp>
Subject: Re: Variable length internet addresses in TCP/IP: history
To: braden@isi.edu
Date: Tue, 14 Feb 2012 22:40:34 +0100 (MET)
In-Reply-To: <4F3A9A55.8080908@isi.edu> from "Bob Braden" at Feb 14, 12 09:31:01 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:40:37 -0000

Bob Braden wrote:
> 
> Within the ARPA-funded Internet research program that designed IP and 
> TCP, Jon Postel and Danny Cohen argued strenuously for variable length
> addresses. (This must have been around 1979. I cannot name most of the
> other 10 people in the room, but I have a clear mental picture of Jon,
> in the back of the room, fuming over this issue. Jon believed
> intensely in protocol extensibility.)
> 
> However, Vint Cerf, the ARPA program manager, rules against variable 
> length addresses and decreed the fixed length 32 bit word-aligned
> addresses of RFC 791. His argument was that TCP/IP had to be simple
> to implement if it were to succeed (and survive the juggernaut
> of the ISO OSI protocol suite).

I'm quite OK with both, IPv4 fixed-length 32-bit addresses and
IPv6 fixed-length 128-bit addresses, and consider fixed-length
addresses reasonable.

What I really don't like is that IPv6 was not made to be transparently
backwards compatible (on the IPv4 address range), but instead a completely
different protocol that requires non-trivial translation IPv4<->IPv6.


One the one hand, the IETF was frowning upon NATs when they were
developed outside of the IETF.  But if you look at the IETFs
(lack of) migration plan, the translation that you need in order
to make old-IPv4 interoperate with new-IPv6, is actually worse than
an IPv4 NAT.


-Martin

From brian.e.carpenter@gmail.com  Tue Feb 14 14:34:10 2012
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 8423121E80E5 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 14:34:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.431
X-Spam-Level: 
X-Spam-Status: No, score=-103.431 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id buaMGLBtWDpe for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 14:34:10 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id D6C2121E80E1 for <ietf@ietf.org>; Tue, 14 Feb 2012 14:34:09 -0800 (PST)
Received: by iagf6 with SMTP id f6so579871iag.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 14:34:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xQuS2CO9BgkDmWKtP5LeaVUF4rQlwxPlccULDUXW6Ws=; b=KzZREIDyNAIgQG6iJG7G4Yt06A2hd1FRbIpoJxpHdtAsKH23DrV0hr+deCe67gaY7c nBpqUPl7FZWEaUxrkHIlUH6RrsIJ+YGCiNBMKPhVVs3FD19sgAZoejNYT3W2EmSvXwOY xxvh9Hy1hFYOFMadO4YY+m0wUSPFcx0U4bwtQ=
Received: by 10.42.155.193 with SMTP id v1mr5722284icw.26.1329258849477; Tue, 14 Feb 2012 14:34:09 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id x18sm1466298ibi.2.2012.02.14.14.34.06 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 14:34:08 -0800 (PST)
Message-ID: <4F3AE15F.7000601@gmail.com>
Date: Wed, 15 Feb 2012 11:34:07 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <201202142140.q1ELeYrK016229@fs4113.wdf.sap.corp>
In-Reply-To: <201202142140.q1ELeYrK016229@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:34:10 -0000

Martin,

> One the one hand, the IETF was frowning upon NATs when they were
> developed outside of the IETF.  But if you look at the IETFs
> (lack of) migration plan, the translation that you need in order
> to make old-IPv4 interoperate with new-IPv6, is actually worse than
> an IPv4 NAT.

I'm sorry, but *any* coexistence between RFC791-IPv4-only hosts and
hosts that are numbered out of an address space greater than 32 bits
requires some form of address sharing, address mapping, and translation.
It doesn't matter what choice we made back in 1994. Once you get to the
point where you've run out of 32 bit addresses and not every node can
support >32 bit addresses, you have the problem.

   Brian

From mrex@sap.com  Tue Feb 14 14:45:14 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A423521E803D for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 14:45:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.121
X-Spam-Level: 
X-Spam-Status: No, score=-10.121 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5sxKHCXaY+mJ for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 14:45:14 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9652B21E801D for <ietf@ietf.org>; Tue, 14 Feb 2012 14:45:13 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1EMjBF5003403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2012 23:45:11 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
Subject: Re: Variable length internet addresses in TCP/IP: history
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Tue, 14 Feb 2012 23:45:10 +0100 (MET)
In-Reply-To: <4F3AE15F.7000601@gmail.com> from "Brian E Carpenter" at Feb 15, 12 11:34:07 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:45:14 -0000

Brian E Carpenter wrote:
> 
> Martin,
> 
> > One the one hand, the IETF was frowning upon NATs when they were
> > developed outside of the IETF.  But if you look at the IETFs
> > (lack of) migration plan, the translation that you need in order
> > to make old-IPv4 interoperate with new-IPv6, is actually worse than
> > an IPv4 NAT.
> 
> I'm sorry, but *any* coexistence between RFC791-IPv4-only hosts and
> hosts that are numbered out of an address space greater than 32 bits
> requires some form of address sharing, address mapping, and translation.
> It doesn't matter what choice we made back in 1994. Once you get to the
> point where you've run out of 32 bit addresses and not every node can
> support >32 bit addresses, you have the problem.

But what is your point?

With a fully backwards compatible transparent addressing scheme,
a much larger fraction of the nodes would have switched to actively
use IPv6 many years ago.

You would not have two distinct routing tables for two independent
Internets, but a single routing table for a single Internet.

And the first network interfaces that would be using >32-bit
IP-addresses exclusively would have been networking equipment of
ISPs that does not need to be IPv4-addressable by everyone and his dog
anyway (that is not so much different from the /10 shared address space
that CGNs will be using).


The necessary changes to applications would be minimal,
the "happy eyeballs" contortion completely unnecessary
and the security assessment for an IPv6 enabled network
*MUCH* simpler.


-Martin

From marka@isc.org  Tue Feb 14 15:27:02 2012
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 97FCF21E8125 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 15:27:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nbJ1nkBEUXM6 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 15:27:02 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 1C20521E807F for <ietf@ietf.org>; Tue, 14 Feb 2012 15:27:02 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id EDC9A5F98AF; Tue, 14 Feb 2012 23:26:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:20ef:993:416e:bc7f]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id DF51D216C6B; Tue, 14 Feb 2012 23:26:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id F17091D537BF; Wed, 15 Feb 2012 10:26:41 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
Subject: Re: Variable length internet addresses in TCP/IP: history
In-reply-to: Your message of "Tue, 14 Feb 2012 23:45:10 BST." <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
Date: Wed, 15 Feb 2012 10:26:41 +1100
Message-Id: <20120214232641.F17091D537BF@drugs.dv.isc.org>
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:27:02 -0000

In message <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>, Martin Rex writes
:
> The necessary changes to applications would be minimal,
> the "happy eyeballs" contortion completely unnecessary
> and the security assessment for an IPv6 enabled network
> *MUCH* simpler.

Happy eyeballs just points out problems with multi-homing in general.
IPv4 has the *same* problem and sites spend 1000's of dollars working
around the issue which could have been addressed with a couple of
extra lines of code on the client side in most cases.

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

From bob.hinden@gmail.com  Tue Feb 14 15:56:21 2012
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 311441F0C4D for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 15:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.937
X-Spam-Level: 
X-Spam-Status: No, score=-102.937 tagged_above=-999 required=5 tests=[AWL=-0.578, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5rqwbuZXpaBk for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 15:56:20 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8811F0C44 for <ietf@ietf.org>; Tue, 14 Feb 2012 15:56:19 -0800 (PST)
Received: by iagf6 with SMTP id f6so677343iag.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 15:56:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=uTV29g+WtM9ndLdYWkirv/6eI5siMGl/Q7WX2sft37s=; b=IRu3EeMpVQpyMAysCZ6TMmKiietcfutZrF/PXmddMTRifn3N/dQ4rJwcAQN+7kLEHw qn0MWj/4Tm+WgdtNn9bihy7dWPuXChLoD+E66QCE5/i15grWKLi8i+ISleIqErsmqBwa wdWydrvncmH13uH2SMCwheKXT3Ttn4L9u+IpY=
Received: by 10.42.179.73 with SMTP id bp9mr29290398icb.10.1329263779610; Tue, 14 Feb 2012 15:56:19 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id mr24sm1893950ibb.1.2012.02.14.15.56.18 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 15:56:19 -0800 (PST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
Date: Tue, 14 Feb 2012 15:56:16 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9565EEEA-8732-4A47-90BB-9318E1ACB433@gmail.com>
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1084)
Cc: braden@isi.edu, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:56:21 -0000

Martin,

On Feb 14, 2012, at 2:45 PM, Martin Rex wrote:

> Brian E Carpenter wrote:
>>=20
>> Martin,
>>=20
>>> One the one hand, the IETF was frowning upon NATs when they were
>>> developed outside of the IETF.  But if you look at the IETFs
>>> (lack of) migration plan, the translation that you need in order
>>> to make old-IPv4 interoperate with new-IPv6, is actually worse than
>>> an IPv4 NAT.
>>=20
>> I'm sorry, but *any* coexistence between RFC791-IPv4-only hosts and
>> hosts that are numbered out of an address space greater than 32 bits
>> requires some form of address sharing, address mapping, and =
translation.
>> It doesn't matter what choice we made back in 1994. Once you get to =
the
>> point where you've run out of 32 bit addresses and not every node can
>> support >32 bit addresses, you have the problem.
>=20
> But what is your point?
>=20
> With a fully backwards compatible transparent addressing scheme,
> a much larger fraction of the nodes would have switched to actively
> use IPv6 many years ago.

Right, just like they could have deployed dual stack many years ago too.

The deployment problem was not due to technical issues, it was because =
the Internet changed to only deploy new technology that generated =
revenue in the short term.  After a lot of thought, I have come to the =
conclusion that it wouldn't have mattered what the IETF did, we would =
still be facing the same problems.  It wouldn't be seriously deployed =
until IPv4 address ran out.

These "if we had only done foo" discussions all miss the biggest =
deployment factor.

Bob




From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 14 16:07:39 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93C2E21E810F for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 16:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.065
X-Spam-Level: 
X-Spam-Status: No, score=-0.065 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02YNSX64V12i for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 16:07:39 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 8FF4D21E8124 for <ietf@ietf.org>; Tue, 14 Feb 2012 16:07:38 -0800 (PST)
Received: (qmail 64773 invoked from network); 15 Feb 2012 00:22:39 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Feb 2012 00:22:39 -0000
Message-ID: <4F3AF721.4070402@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 09:06:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <201202142140.q1ELeYrK016229@fs4113.wdf.sap.corp> <4F3AE15F.7000601@gmail.com>
In-Reply-To: <4F3AE15F.7000601@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:07:39 -0000

Brian E Carpenter wrote:

> I'm sorry, but *any* coexistence between RFC791-IPv4-only hosts and
> hosts that are numbered out of an address space greater than 32 bits
> requires some form of address sharing,

Sure.

> address mapping, and translation.

Not at all.

Realm Specific IP [RFC3102] is such an example without any
mapping nor translations. Abstract of the RFC states:

   This document examines the general framework of Realm Specific IP
   (RSIP).  RSIP is intended as a alternative to NAT in which the end-
   to-end integrity of packets is maintained.  We focus on
   implementation issues, deployment scenarios, and interaction with
   other layer-three protocols.

> It doesn't matter what choice we made back in 1994. Once you get to the
> point where you've run out of 32 bit addresses and not every node can
> support>32 bit addresses, you have the problem.

The only problem is that some people misinterpret it that
we had needed IPv6.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 14 16:11:23 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247B721E810F for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 16:11:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.067
X-Spam-Level: 
X-Spam-Status: No, score=-0.067 tagged_above=-999 required=5 tests=[AWL=0.023,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFXRBOLEWw-b for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 16:11:21 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 4BFDD21F855A for <ietf@ietf.org>; Tue, 14 Feb 2012 16:11:19 -0800 (PST)
Received: (qmail 64799 invoked from network); 15 Feb 2012 00:26:28 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Feb 2012 00:26:28 -0000
Message-ID: <4F3AF807.60703@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 09:10:47 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp> <20120214232641.F17091D537BF@drugs.dv.isc.org>
In-Reply-To: <20120214232641.F17091D537BF@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:11:23 -0000

Mark Andrews wrote:

> Happy eyeballs just points out problems with multi-homing in general.
> IPv4 has the *same* problem and sites spend 1000's of dollars working
> around the issue which could have been addressed with a couple of
> extra lines of code on the client side in most cases.

It's Brian Carpenter who refused to discuss such issues in
MULTI6 WG.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 14 16:13:34 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD98621E80D4 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 16:13:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.069
X-Spam-Level: 
X-Spam-Status: No, score=-0.069 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNF60cPdNcrp for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 16:13:34 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 23D4B21E813F for <ietf@ietf.org>; Tue, 14 Feb 2012 16:13:31 -0800 (PST)
Received: (qmail 64818 invoked from network); 15 Feb 2012 00:28:24 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Feb 2012 00:28:24 -0000
Message-ID: <4F3AF87A.8090808@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 09:12:42 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Let ARIN decide (was Re: Another last call for draft-weil)
References: <5BB63F16-DA59-4B07-AA2B-457A1AF2B7F6@harvard.edu> <AC72C29F-9AFD-482F-B8B1-4627A31A7611@virtualized.org> <4CB41BAC-5280-4E8C-ACAF-8445DD8209AC@harvard.edu>
In-Reply-To: <4CB41BAC-5280-4E8C-ACAF-8445DD8209AC@harvard.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:13:35 -0000

Bradner, Scott wrote:

> the IAB advised ARIN that such assignments were in the purview of the IETF

Then, isn't it enough for IETF to conclude "let ARIN decide"?

Are there any objections to conclude so?

						Masataka Ohta

From randy@psg.com  Tue Feb 14 17:09:52 2012
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 173C921F8617 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.914
X-Spam-Level: 
X-Spam-Status: No, score=-1.914 tagged_above=-999 required=5 tests=[AWL=-0.555, BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ni0hQxvSlAo for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:09:51 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B857021F85FD for <ietf@ietf.org>; Tue, 14 Feb 2012 17:09:51 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RxTNW-000PqR-KP; Wed, 15 Feb 2012 01:09:50 +0000
Date: Tue, 14 Feb 2012 17:09:50 -0800
Message-ID: <m2r4xwlx5t.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
In-Reply-To: <9565EEEA-8732-4A47-90BB-9318E1ACB433@gmail.com>
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp> <9565EEEA-8732-4A47-90BB-9318E1ACB433@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:09:52 -0000

> The deployment problem was not due to technical issues, it was because
> the Internet changed to only deploy new technology that generated
> revenue in the short term.  After a lot of thought, I have come to the
> conclusion that it wouldn't have mattered what the IETF did, we would
> still be facing the same problems.  It wouldn't be seriously deployed
> until IPv4 address ran out.

perhaps 'engineering' includes thinking about the costs of deployment.
perhaps backward compatibility would have reduced the costs.

randy, whose $dayjob did deploy very early

From mrex@sap.com  Tue Feb 14 17:12:14 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C85221F8638 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.129
X-Spam-Level: 
X-Spam-Status: No, score=-10.129 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5bvzpaBTGtnP for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:12:13 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7912121F865F for <ietf@ietf.org>; Tue, 14 Feb 2012 17:12:13 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q1F1CBSB015962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Feb 2012 02:12:11 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202150112.q1F1CB88028368@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
To: presnick@qualcomm.com (Pete Resnick)
Date: Wed, 15 Feb 2012 02:12:11 +0100 (MET)
In-Reply-To: <4F3ABF6C.1030803@qualcomm.com> from "Pete Resnick" at Feb 14, 12 02:09:16 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:12:14 -0000

Pete Resnick wrote:
> 
> Do you, or do you not, object to the proposed change that changes the 
> text from saying, "This space may be used just as 1918 space" to "This 
> space has limitations and cannot be used as 1918 space"? Nobody on the 
> list objected to that new text. That new text significantly changes -14. 
> You have stated your support for -14. Do you object to changing the text?

I support the document _with_ that proposed change to discourage
the (ab)use of that ARIN /10 CGN space as 1918 space.

-Martin

From presnick@qualcomm.com  Tue Feb 14 17:26:32 2012
Return-Path: <presnick@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 30A7421E8047 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.577
X-Spam-Level: 
X-Spam-Status: No, score=-106.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vD5Nd9R06H7W for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:26:31 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 81B2E21E803F for <ietf@ietf.org>; Tue, 14 Feb 2012 17:26:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329269191; x=1360805191; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F3B09C3.1090005@qualcomm.com>|Date:=20Tu e,=2014=20Feb=202012=2019:26:27=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Randy=20Bush=20<randy@psg.com> |CC:=20<ietf@ietf.org>|Subject:=20Re:=20Last=20Call:=09<d raft-weil-shared-transition-space-request-14.txt>=0D=0A =20(IANA=09Reserved=20IPv4=20Prefix=20for=20Shared=20Addr ess=20Space)=20to=20BCP|References:=20<CB5FF399.1B4E7%jef f.finkelstein@cox.com>=09<4F3AAA08.2040204@qualcomm.com> =09<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>=09<4F3ABF6C.103 0803@qualcomm.com>=20<m2d39hi267.wl%randy@psg.com> |In-Reply-To:=20<m2d39hi267.wl%randy@psg.com> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.39.5]; bh=gacAYuZRIMPALHlrYwGW6AF+hgQhKjgFi9daOefz8BU=; b=pdIXbMOmMqZNXxgmYE2eAvqKRIMEwuysV28D54mLZRnZ2cCMJG4PsVlN cYMzLxwbSr2/7Qv2fa/r+rScj7RgrmRm76hu+50/Cz71kd+Z4fC4rNQhn RlK3LPuyEV5K91vEgoVX7zKDk2Who/+qLv5z2JFdwGsLzSMQwvVRJCldn 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6620"; a="163225468"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 14 Feb 2012 17:26:31 -0800
X-IronPort-AV: E=Sophos;i="4.73,417,1325491200"; d="scan'208";a="184589048"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 14 Feb 2012 17:26:31 -0800
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 14 Feb 2012 17:26:30 -0800
Message-ID: <4F3B09C3.1090005@qualcomm.com>
Date: Tue, 14 Feb 2012 19:26:27 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>	<4F3AAA08.2040204@qualcomm.com>	<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>	<4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com>
In-Reply-To: <m2d39hi267.wl%randy@psg.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:26:32 -0000

On 2/14/12 2:35 PM, Randy Bush wrote:

> what silliness.  it will be used as rfc 1918 space no matter what the document
> says.
> [...]
> any thought that this is not just adding to rfc 1918 is pure bs.
>    

Of course it will be used as 1918 space. That's not the point of the text.

The text is saying, "You could read 1918 to say that we somehow promised 
that you would never be connected to a network run by someone other than 
yourself and see 1918 addresses on it. That's not an entirely 
intelligent reading, but we see how you can read it that way. So, if you 
built yourself a device where it isn't able to deal with 1918 addresses 
on its 'outside' interface that you were using on the 'inside' 
interfaces, we could see how that might happen. It was not at all smart 
of you to build your device that way, but you probably were technically 
within spec. Now we're adding some address space to the pool. It's not 
global and it's not routable, just the same as 1918 space. But we're 
letting you know right now: You *will* see these addresses on networks 
that you don't run. If you want to use this space the way that you used 
1918 space, peachy, but understand that if you're unable to deal with 
these addresses duplicating ones you're using, your device is toast. 
Deal with it."

Any thought that the text is saying something more than this is nonsense.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 14 17:51:08 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BAD921E8021 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.07
X-Spam-Level: 
X-Spam-Status: No, score=-0.07 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kAtRs9TF2z3V for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 17:51:07 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id BFD1521E8015 for <ietf@ietf.org>; Tue, 14 Feb 2012 17:51:06 -0800 (PST)
Received: (qmail 65601 invoked from network); 15 Feb 2012 02:06:08 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Feb 2012 02:06:08 -0000
Message-ID: <4F3B0F5D.7050506@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 10:50:21 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com>
In-Reply-To: <m2d39hi267.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:51:08 -0000

Randy Bush wrote:

> what silliness.  it will be used as rfc 1918 space no matter what the document
> says.

The difference is on how future conflicts can be resolved.

> nine years ago i was in bologna and did a traceroute out.  i was surprised
> to find that the isp was using un-announced us military space as rfc 1918
> space internal to their network.  this turns out to be common.

What if the military space is sold to public and announced?

Who is forced to renumber and why?

						Masataka Ohta

From victor.kuarsingh@gmail.com  Tue Feb 14 18:28:38 2012
Return-Path: <victor.kuarsingh@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 3BE0E21E8037 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 18:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.266
X-Spam-Level: 
X-Spam-Status: No, score=-3.266 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6XHG7ZsIyZKd for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 18:28:37 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 547B221E8010 for <ietf@ietf.org>; Tue, 14 Feb 2012 18:28:37 -0800 (PST)
Received: by iagf6 with SMTP id f6so855178iag.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 18:28:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=MunPQkxv1KoR3u/y/9Wyfu0yPBnieJDSKBYZwAEXtjo=; b=euH5xp21CirZdMbnkAtRt/UfyESwVwl7YrxVm+ploAzQWzohGUfv6MVSzTg53vNxij fiWilmlDYppYrRpYM+KUiWdc1bIGV9lzhbYp9rkmYqirD7rLV0xnZ+KPXaIbGhdUZgtI fFcm56WKECEXjbavAWnKE4csoZzUD11uxnB2A=
Received: by 10.50.149.162 with SMTP id ub2mr39463235igb.1.1329272915234; Tue, 14 Feb 2012 18:28:35 -0800 (PST)
Received: from [192.168.100.89] ([67.224.83.162]) by mx.google.com with ESMTPS id ng9sm2169919igc.3.2012.02.14.18.28.34 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 18:28:34 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Tue, 14 Feb 2012 21:28:31 -0500
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Randy Bush <randy@psg.com>, Leif Sawyer <lsawyer@gci.com>
Message-ID: <CB608221.15036%victor.kuarsingh@gmail.com>
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <m2bop1m97t.wl%randy@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:28:38 -0000

On 12-02-14 3:49 PM, "Randy Bush" <randy@psg.com> wrote:

>> In that I completely agree with what Randy is saying, the point
>> that needs to be made is that this should not be officially
>> sanctioned as RFC-1918 space --  no manufacturer or programmer
>> should treat this netblock the same.
>> 
>> If some fly-by-night company chooses to use it on their own,
>> well, then they have chosen to operate outside the bounds of
>> the best-principles - exactly the same as in Randy's example.
>
>and the packets will be very ashamed, right?
>
>we can say all the crap we want, but it will be used as 1918 space and,
>like 1918 space, bgp announcesments of it will leak.  get over it.

Sure, but with a well known address range, it's not just what one AS
leaks.. The other AS(s) can also block incoming.  That's one of the
benefits of a well known space for this.

For squat, good luck figuring out who is using what from where.

Victor K

>
>randy
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf



From victor.kuarsingh@gmail.com  Tue Feb 14 18:29:27 2012
Return-Path: <victor.kuarsingh@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 4AB2421E8037 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 18:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UlZEsocbM8w for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 18:29:26 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A354721E8010 for <ietf@ietf.org>; Tue, 14 Feb 2012 18:29:26 -0800 (PST)
Received: by iagf6 with SMTP id f6so856104iag.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 18:29:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=KnzS7PwZhviRuMDPfrsjegYyOQjciT33Jh/zucvnhIA=; b=rlBMoYXFd2Y4+w+mwnjmvM4M66S/a/3ia9LS3LLVy97oJXQVPybeqryzk9GIepJpRS PZwKfblISHsXYhg+QH1ulHQNCvdLsb6lMRTNYTmpTsXEU4Lpen02gRRuukep9Llm4QIn +Nk6ODomCWZTSqRzSgJybYJKEYvtjp+p469tc=
Received: by 10.50.168.10 with SMTP id zs10mr3750777igb.11.1329272964725; Tue, 14 Feb 2012 18:29:24 -0800 (PST)
Received: from [192.168.100.89] ([67.224.83.162]) by mx.google.com with ESMTPS id f26sm2651204ibc.9.2012.02.14.18.29.23 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 18:29:24 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Date: Tue, 14 Feb 2012 21:29:21 -0500
Subject: Re: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: William Check <BCheck@NCTA.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <CB60829F.1503A%victor.kuarsingh@gmail.com>
Thread-Topic: Last call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
In-Reply-To: <72072B73-F740-4A40-A01F-0A66E0C0E295@ncta.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:29:27 -0000

Support Draft as written +1.

Victor K

On 12-02-14 12:38 PM, "William Check" <BCheck@NCTA.com> wrote:

>+1, I support this draft=8A  Bill Check
>
>
>On Feb 14, 2012, at 10:08 AM, Thienpondt Hans wrote:
>
>> http://tools.ietf.org/html/draft-weil-shared-transition-space-request-14
>>=20
>> +1
>> I support this draft!
>>=20
>> Best Regards,
>>=20
>> Hans
>>=20
>>=20
>> --
>> Hans Thienpondt
>> Technology Engineer
>>=20
>> Converged Network Engineering
>> Telenet NV
>> Liersesteenweg 4 - box 52
>> T: +32 15 33 30 24
>> 2800 Mechelen - Belgium
>>=20
>> *************************************************************
>>=20
>> Dit e-mail bericht inclusief eventuele ingesloten bestanden kan
>>informatie bevatten die vertrouwelijk is en/of beschermd door
>>intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor
>>de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht
>>(waaronder de volledige of gedeeltelijke reproductie of verspreiding
>>onder elke vorm) door andere personen dan de geadresseerde(n) is
>>verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve
>>de afzender hiervan te verwittigen en dit bericht te verwijderen.
>>=20
>> This e-mail and any attachment thereto may contain information which is
>>confidential and/or protected by intellectual property rights and are
>>intended for the sole use of the addressees. Any use of the information
>>contained herein (including but not limited to total or partial
>>reproduction or distribution in any form) by other persons than the
>>addressees is prohibited. If you have received this e-mail in error,
>>please notify the sender and delete its contents.
>>=20
>> Ce courriel et les annexes eventuelles peuvent contenir des
>>informations confidentielles et/ou protegees par des droits de propriete
>>intellectuelle. Ce message est adresse exclusivement e son (ses)
>>destinataire(s). Toute utilisation du contenu de ce message (y compris
>>la reproduction ou diffusion partielle ou complete sous toute forme) par
>>une autre personne que le(s) destinataire(s) est formellement interdite.
>>Si vous avez recu ce message par erreur, veuillez prevenir l'expediteur
>>du message et en detruire le contenu.
>>=20
>> *************************************************************
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf



From brian.e.carpenter@gmail.com  Tue Feb 14 19:04:27 2012
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 5000321F8711 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 19:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.434
X-Spam-Level: 
X-Spam-Status: No, score=-103.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id seXqCIOP+27c for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 19:04:26 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCC221F870B for <ietf@ietf.org>; Tue, 14 Feb 2012 19:04:26 -0800 (PST)
Received: by iagf6 with SMTP id f6so896940iag.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 19:04:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rLZu6ripkPRDluVgAHLjPZFLwArhqOxYpBAP2G1r9mI=; b=a/6pBOuDvpRg08BYbIRINR4XdOAFPwD/Yspo8zqZjVFQt1MtJjcMWoL0hhXHRnUCj4 mQGP8YuHu+f5y0qz4EOEJRptz+gVc3Dqjc7ETzM59FHAYmbE+ZeZcX6wgAf5wqoWLNYm YjVo6w+wNFiRkA2ozntioZnVvGO9ycTuAK0ow=
Received: by 10.42.131.129 with SMTP id z1mr31312989ics.53.1329275066075; Tue, 14 Feb 2012 19:04:26 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id al9sm2316837igc.5.2012.02.14.19.04.23 (version=SSLv3 cipher=OTHER); Tue, 14 Feb 2012 19:04:25 -0800 (PST)
Message-ID: <4F3B20C4.9080001@gmail.com>
Date: Wed, 15 Feb 2012 16:04:36 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
In-Reply-To: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:04:27 -0000

On 2012-02-15 11:45, Martin Rex wrote:
> Brian E Carpenter wrote:
>> Martin,
>>
>>> One the one hand, the IETF was frowning upon NATs when they were
>>> developed outside of the IETF.  But if you look at the IETFs
>>> (lack of) migration plan, the translation that you need in order
>>> to make old-IPv4 interoperate with new-IPv6, is actually worse than
>>> an IPv4 NAT.
>> I'm sorry, but *any* coexistence between RFC791-IPv4-only hosts and
>> hosts that are numbered out of an address space greater than 32 bits
>> requires some form of address sharing, address mapping, and translation.
>> It doesn't matter what choice we made back in 1994. Once you get to the
>> point where you've run out of 32 bit addresses and not every node can
>> support >32 bit addresses, you have the problem.
> 
> But what is your point?
> 
> With a fully backwards compatible transparent addressing scheme,
> a much larger fraction of the nodes would have switched to actively
> use IPv6 many years ago.

Why? They would have needed updated stacks. The routers would
have need updated stacks. The servers would have needed updated
stacks. The firewalls would have needed updated stacks. The load
balancers would have needed updated stacks. Many MIBs would have
needed to be updated. DHCP servers would have needed to be updated.
ARP would have needed to be updated, and every routing protocol.

Why would the economic incentives have been significantly different?

> You would not have two distinct routing tables for two independent
> Internets, but a single routing table for a single Internet.

True, but why is this a particular advantage? It wouldn't have
affected the need for an update to BGP4, for example.

> 
> And the first network interfaces that would be using >32-bit
> IP-addresses exclusively would have been networking equipment of
> ISPs that does not need to be IPv4-addressable by everyone and his dog
> anyway (that is not so much different from the /10 shared address space
> that CGNs will be using).

Neither is it so much different from dual stack routing, which has been
working for, what, 15 years now? I don't see the comparison with CGN
though, which is a carefully engineered single bottleneck of failure,
in contrast to dynamic routing.

> The necessary changes to applications would be minimal,
> the "happy eyeballs" contortion completely unnecessary

As someone else said, this is to do with multihoming
and multi-interfacing; the fact that there are two address
lengths is a side-issue. We would still have needed to update
the socket interface to deal with >32 bit addresses, and ditto
the DNS.

> and the security assessment for an IPv6 enabled network
> *MUCH* simpler.

I agree that the fact that IPv6 has a different feature list
from IPv4 has provided entertainment for security analysts.

I will shut up on this topic and get back to IPv6 deployment.

    Brian


From dougb@dougbarton.us  Tue Feb 14 19:39:35 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 659BF21E8030 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 19:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.589
X-Spam-Level: 
X-Spam-Status: No, score=-3.589 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-jreZ+5B5FD for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 19:39:34 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7A85E21E8055 for <ietf@ietf.org>; Tue, 14 Feb 2012 19:39:34 -0800 (PST)
Received: (qmail 1243 invoked by uid 399); 15 Feb 2012 03:39:32 -0000
Received: from unknown (HELO 172-17-150-251.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 15 Feb 2012 03:39:32 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F3B28F3.4070607@dougbarton.us>
Date: Tue, 14 Feb 2012 19:39:31 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.1) Gecko/20120213 Thunderbird/10.0.1
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com>	<4F3AAA08.2040204@qualcomm.com>	<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com>	<4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com>
In-Reply-To: <4F3B09C3.1090005@qualcomm.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:39:35 -0000

On 02/14/2012 17:26, Pete Resnick wrote:
> Of course it will be used as 1918 space. That's not the point of the text.

My first reply in this most recent version of the thread pointed out
that now that we're finally willing to admit that if a new block is
issued it will be used as 1918 space then that leads to the obvious
conclusion that the *best* we can do with this draft is to kick the can
down the road, which is not enough justification for actually doing the
allocation.

I'll resist the urge to repeat the other points that I've already
repeated too often. :)

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From randy@psg.com  Tue Feb 14 19:40:10 2012
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 9778321E8081 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 19:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtCrBK0bWA27 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 19:40:10 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 214F221E8030 for <ietf@ietf.org>; Tue, 14 Feb 2012 19:40:10 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RxViz-00008X-7K; Wed, 15 Feb 2012 03:40:09 +0000
Date: Tue, 14 Feb 2012 19:40:08 -0800
Message-ID: <m2k43olq7b.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
In-Reply-To: <4F3B20C4.9080001@gmail.com>
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp> <4F3B20C4.9080001@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:40:10 -0000

> Why? They would have needed updated stacks. The routers would
> have need updated stacks. The servers would have needed updated
> stacks. The firewalls would have needed updated stacks. The load
> balancers would have needed updated stacks. Many MIBs would have
> needed to be updated. DHCP servers would have needed to be updated.
> ARP would have needed to be updated, and every routing protocol.

<rant>

the routers had v6 code in the mid to late '90s.  servers had the kame
stack before then.  etc etc etc.  except for dhcp, of course, as the v6
religious zealots did not want to allow dhcp, it would make enterprise
conversion too easy.

what we did not have was a way to deploy around the fracking
incompatibility.  it was not until 2001 or so that we could even run
useful dual stack, so we early deployers had two parallel networks for
some years.

religion has always been more important to the ietf than deployment.
look at dhcpv6, the zealots are still stonewalling router discovery.
look at the deprecation of nat-pt, now nat64/dns64.  it is as if the
ipv6 high priesthood did everything in their power to make ipv6
undeployable without very high cost.  and they have succeeded admirably.

so today, since the costs of ipv6 incompatibility and lack of feature
parity are still high, for some folk it is easier to deploy nat44444.
what a win for the internet.  congratulations.

randy

From cb.list6@gmail.com  Tue Feb 14 20:16:46 2012
Return-Path: <cb.list6@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 0EBF121E801C for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 20:16:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.461
X-Spam-Level: 
X-Spam-Status: No, score=-3.461 tagged_above=-999 required=5 tests=[AWL=0.137,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YUq65FGUur9K for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 20:16:45 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 69B7E21F84FD for <ietf@ietf.org>; Tue, 14 Feb 2012 20:16:45 -0800 (PST)
Received: by dakl33 with SMTP id l33so598115dak.31 for <ietf@ietf.org>; Tue, 14 Feb 2012 20:16:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jDFy9nRX06ZoIVSaeePeI3cHRIx4p4oiZ0JHAciYYOA=; b=FK0ARU1KfOlRXa5s4fCPnbzjCVw9Lmi/sFNesZ6IbuLS3wq9jrY2EdqEruBj8v4+j0 Z4Atuv9m9sy2O0EzG4Z+qSOxap/oq3K92blhWhdvHuAd0CJQMz8WrLFhXecr8nlKSBSC P3Emjsw05Il/qdG50UjYcbwcwN/0U9fnvBKcw=
MIME-Version: 1.0
Received: by 10.68.216.4 with SMTP id om4mr65641423pbc.19.1329279405246; Tue, 14 Feb 2012 20:16:45 -0800 (PST)
Received: by 10.143.164.16 with HTTP; Tue, 14 Feb 2012 20:16:45 -0800 (PST)
Received: by 10.143.164.16 with HTTP; Tue, 14 Feb 2012 20:16:45 -0800 (PST)
In-Reply-To: <m2k43olq7b.wl%randy@psg.com>
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp> <4F3B20C4.9080001@gmail.com> <m2k43olq7b.wl%randy@psg.com>
Date: Tue, 14 Feb 2012 20:16:45 -0800
Message-ID: <CAD6AjGRqYjbT5evyrorwQvcv0RtkNjzHSXz-d-vcYQQREizORw@mail.gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
From: Cameron Byrne <cb.list6@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=e89a8ff254f6c1c89904b8f8fae2
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:16:46 -0000

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

On Feb 14, 2012 7:40 PM, "Randy Bush" <randy@psg.com> wrote:
>
> > Why? They would have needed updated stacks. The routers would
> > have need updated stacks. The servers would have needed updated
> > stacks. The firewalls would have needed updated stacks. The load
> > balancers would have needed updated stacks. Many MIBs would have
> > needed to be updated. DHCP servers would have needed to be updated.
> > ARP would have needed to be updated, and every routing protocol.
>
> <rant>
>
> the routers had v6 code in the mid to late '90s.  servers had the kame
> stack before then.  etc etc etc.  except for dhcp, of course, as the v6
> religious zealots did not want to allow dhcp, it would make enterprise
> conversion too easy.
>
> what we did not have was a way to deploy around the fracking
> incompatibility.  it was not until 2001 or so that we could even run
> useful dual stack, so we early deployers had two parallel networks for
> some years.
>
> religion has always been more important to the ietf than deployment.
> look at dhcpv6, the zealots are still stonewalling router discovery.
> look at the deprecation of nat-pt, now nat64/dns64.  it is as if the
> ipv6 high priesthood did everything in their power to make ipv6
> undeployable without very high cost.  and they have succeeded admirably.
>
> so today, since the costs of ipv6 incompatibility and lack of feature
> parity are still high, for some folk it is easier to deploy nat44444.
> what a win for the internet.  congratulations.
>
> randy
>

</rant>

But, this pig too shall fly

Cb
_______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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

<p><br>
On Feb 14, 2012 7:40 PM, &quot;Randy Bush&quot; &lt;<a href=3D"mailto:randy=
@psg.com">randy@psg.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Why? They would have needed updated stacks. The routers would<br>
&gt; &gt; have need updated stacks. The servers would have needed updated<b=
r>
&gt; &gt; stacks. The firewalls would have needed updated stacks. The load<=
br>
&gt; &gt; balancers would have needed updated stacks. Many MIBs would have<=
br>
&gt; &gt; needed to be updated. DHCP servers would have needed to be update=
d.<br>
&gt; &gt; ARP would have needed to be updated, and every routing protocol.<=
br>
&gt;<br>
&gt; &lt;rant&gt;<br>
&gt;<br>
&gt; the routers had v6 code in the mid to late &#39;90s. =A0servers had th=
e kame<br>
&gt; stack before then. =A0etc etc etc. =A0except for dhcp, of course, as t=
he v6<br>
&gt; religious zealots did not want to allow dhcp, it would make enterprise=
<br>
&gt; conversion too easy.<br>
&gt;<br>
&gt; what we did not have was a way to deploy around the fracking<br>
&gt; incompatibility. =A0it was not until 2001 or so that we could even run=
<br>
&gt; useful dual stack, so we early deployers had two parallel networks for=
<br>
&gt; some years.<br>
&gt;<br>
&gt; religion has always been more important to the ietf than deployment.<b=
r>
&gt; look at dhcpv6, the zealots are still stonewalling router discovery.<b=
r>
&gt; look at the deprecation of nat-pt, now nat64/dns64. =A0it is as if the=
<br>
&gt; ipv6 high priesthood did everything in their power to make ipv6<br>
&gt; undeployable without very high cost. =A0and they have succeeded admira=
bly.<br>
&gt;<br>
&gt; so today, since the costs of ipv6 incompatibility and lack of feature<=
br>
&gt; parity are still high, for some folk it is easier to deploy nat44444.<=
br>
&gt; what a win for the internet. =A0congratulations.<br>
&gt;<br>
&gt; randy<br>
&gt;</p>
<p>&lt;/rant&gt;</p>
<p>But, this pig too shall fly</p>
<p>Cb<br>
 _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.iet=
f.org/mailman/listinfo/ietf</a><br>
</p>

--e89a8ff254f6c1c89904b8f8fae2--

From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 14 20:47:25 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7166621F8462 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 20:47:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.071
X-Spam-Level: 
X-Spam-Status: No, score=-0.071 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6IdNsbHiCy1l for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 20:47:25 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 4E48F21F858B for <ietf@ietf.org>; Tue, 14 Feb 2012 20:47:13 -0800 (PST)
Received: (qmail 66913 invoked from network); 15 Feb 2012 05:02:13 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 15 Feb 2012 05:02:13 -0000
Message-ID: <4F3B38BB.4080202@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 13:46:51 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp> <4F3B20C4.9080001@gmail.com>
In-Reply-To: <4F3B20C4.9080001@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:47:25 -0000

Brian E Carpenter wrote:

>> With a fully backwards compatible transparent addressing scheme,
>> a much larger fraction of the nodes would have switched to actively
>> use IPv6 many years ago.

> Why? They would have needed updated stacks. The routers would
> have need updated stacks. The servers would have needed updated
> stacks. The firewalls would have needed updated stacks. The load
> balancers would have needed updated stacks. Many MIBs would have
> needed to be updated. DHCP servers would have needed to be updated.
> ARP would have needed to be updated, and every routing protocol.

With Realm Specific IP [RFC3102]:

   This document examines the general framework of Realm Specific IP
   (RSIP).  RSIP is intended as a alternative to NAT in which the end-
   to-end integrity of packets is maintained.  We focus on
   implementation issues, deployment scenarios, and interaction with
   other layer-three protocols.

what is necessary are minor modification on IPv4/transport stack
of new (but not existing) hosts and minor extension of DHCP.

						Masataka Ohta

From mrex@sap.com  Tue Feb 14 23:09:10 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04B9121E8050 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 23:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.13
X-Spam-Level: 
X-Spam-Status: No, score=-10.13 tagged_above=-999 required=5 tests=[AWL=0.119,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGZmA4+Hi4q6 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 23:09:09 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id C630821E8013 for <ietf@ietf.org>; Tue, 14 Feb 2012 23:09:08 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1F78uiN015241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 15 Feb 2012 08:09:01 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202150708.q1F78tVk018586@fs4113.wdf.sap.corp>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
To: victor.kuarsingh@gmail.com (Victor Kuarsingh)
Date: Wed, 15 Feb 2012 08:08:55 +0100 (MET)
In-Reply-To: <CB608221.15036%victor.kuarsingh@gmail.com> from "Victor Kuarsingh" at Feb 14, 12 09:28:31 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:09:10 -0000

Victor Kuarsingh wrote:
> 
> "Randy Bush" <randy@psg.com> wrote:
> >
> >> In that I completely agree with what Randy is saying, the point
> >> that needs to be made is that this should not be officially
> >> sanctioned as RFC-1918 space --  no manufacturer or programmer
> >> should treat this netblock the same.
> >> 
> >> If some fly-by-night company chooses to use it on their own,
> >> well, then they have chosen to operate outside the bounds of
> >> the best-principles - exactly the same as in Randy's example.
> >
> >and the packets will be very ashamed, right?
> >
> >we can say all the crap we want, but it will be used as 1918 space and,
> >like 1918 space, bgp announcesments of it will leak.  get over it.
> 
> Sure, but with a well known address range, it's not just what one AS
> leaks.. The other AS(s) can also block incoming.  That's one of the
> benefits of a well known space for this.
> 
> For squat, good luck figuring out who is using what from where.

Considering the huge amounts of unused IPv4 address space,
why is there a need for squat space at all?

Out of curiosity, I tried to configure interface addresses from
0/8 or 240/4, but neither my Linux nor my Windows boxen allowed me that.
And lots of CPEs are based on Linux.  And a lot of that equiment
is used _much_ longer than its firmware is maintained by its vendor!

Any idea how long it takes to grow such hardwired restrictions out of
an installed base?

I wish there was more forward thinking among implementors.

One can not complain about the squat use of *assigned* space when all
of the unassigned address ranges have been made totally unusable by
implementors of IPv4 network stacks.


-Martin

From ynir@checkpoint.com  Tue Feb 14 23:51:03 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 691A921E800F for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 23:51:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.854
X-Spam-Level: 
X-Spam-Status: No, score=-9.854 tagged_above=-999 required=5 tests=[AWL=-0.495, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ROPiGVgSK2h for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 23:51:02 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1124121E8040 for <ietf@ietf.org>; Tue, 14 Feb 2012 23:51:01 -0800 (PST)
X-CheckPoint: {4F3B6009-0-1B221DC2-1FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q1F7oxJM018232;  Wed, 15 Feb 2012 09:50:59 +0200
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 15 Feb 2012 09:50:58 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Wed, 15 Feb 2012 09:50:57 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Bob Hinden <bob.hinden@gmail.com>
Date: Wed, 15 Feb 2012 09:50:56 +0200
Subject: Re: Variable length internet addresses in TCP/IP: history
Thread-Topic: Variable length internet addresses in TCP/IP: history
Thread-Index: AczrtozcjLJKLfj2SQeYnLgA2YnIRw==
Message-ID: <385CF164-AF32-4A72-89AE-E28033E0697B@checkpoint.com>
References: <201202142245.q1EMjAoU019793@fs4113.wdf.sap.corp> <9565EEEA-8732-4A47-90BB-9318E1ACB433@gmail.com>
In-Reply-To: <9565EEEA-8732-4A47-90BB-9318E1ACB433@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:51:03 -0000

On Feb 15, 2012, at 1:56 AM, Bob Hinden wrote:

> Martin,
>=20
> On Feb 14, 2012, at 2:45 PM, Martin Rex wrote:
>=20
>> Brian E Carpenter wrote:
>>>=20
>>> Martin,
>>>=20
>>>> One the one hand, the IETF was frowning upon NATs when they were
>>>> developed outside of the IETF.  But if you look at the IETFs
>>>> (lack of) migration plan, the translation that you need in order
>>>> to make old-IPv4 interoperate with new-IPv6, is actually worse than
>>>> an IPv4 NAT.
>>>=20
>>> I'm sorry, but *any* coexistence between RFC791-IPv4-only hosts and
>>> hosts that are numbered out of an address space greater than 32 bits
>>> requires some form of address sharing, address mapping, and translation=
.
>>> It doesn't matter what choice we made back in 1994. Once you get to the
>>> point where you've run out of 32 bit addresses and not every node can
>>> support >32 bit addresses, you have the problem.
>>=20
>> But what is your point?
>>=20
>> With a fully backwards compatible transparent addressing scheme,
>> a much larger fraction of the nodes would have switched to actively
>> use IPv6 many years ago.
>=20
> Right, just like they could have deployed dual stack many years ago too.
>=20
> The deployment problem was not due to technical issues, it was because th=
e Internet changed to only deploy new technology that generated revenue in =
the short term.  After a lot of thought, I have come to the conclusion that=
 it wouldn't have mattered what the IETF did, we would still be facing the =
same problems.  It wouldn't be seriously deployed until IPv4 address ran ou=
t.
>=20
> These "if we had only done foo" discussions all miss the biggest deployme=
nt factor.

I disagree with that. With things that take considerable effort to develop =
and deploy, any sane business or agency would do a cost/benefit analysis, a=
nd not deploy unless they can see how it pays off.=20

Smaller projects sometimes go under the radar. Maybe the cost-benefit analy=
sis says it's not worth doing a cost-benefit analysis. When investment is l=
ow, people do things even without assurances that those would in fact be ne=
eded. I'll leave example from our employer out of this thread.

If adding support for the next IP version in products was easy (say, 1-2 ma=
n-years for an OS, and 1-2 man months for an application), then Windows XP,=
 Mac OS 10.1 and whatever Linux was running at the time and Solaris 2.9 wou=
ld have had the support, and applications would follow quickly, long before=
 IPv4 addresses became scarce.

Yoav=

From dhc@dcrocker.net  Wed Feb 15 06:42:55 2012
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 9869121F8575 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 06:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=-0.640, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bp+Wvoc9tu9o for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 06:42:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 40ABA21F853E for <ietf@ietf.org>; Wed, 15 Feb 2012 06:42:51 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1FEgjnh029629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 15 Feb 2012 06:42:50 -0800
Message-ID: <4F3BC464.50300@dcrocker.net>
Date: Wed, 15 Feb 2012 06:42:44 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu>
In-Reply-To: <4F3A9A55.8080908@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 15 Feb 2012 06:42:50 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:42:55 -0000

G'day.

Always fun to watch an exchange among entrenched perspectives...


On 2/14/2012 9:31 AM, Bob Braden wrote:
> However, Vint Cerf, the ARPA program manager, rules against variable length
> addresses and decreed the fixed length 32 bit word-aligned addresses of RFC
> 791. His argument was that TCP/IP had to be simple to implement if it were to
> succeed (and survive the juggernaut of the ISO OSI protocol suite).

Experience with development, deployment and operations using a core construct is 
not irrelevant when trying to upgrade an infrastructure function.

As I recall, there was essentially no experience with variable length addresses 
-- and certainly no production experience -- then or even by the early 90s, when 
essentially the same decision was made and for essentially the same reason.[1]

It's not that variable length addressing is a bad idea; it's that it didn't get 
the research work and specification detail it needed, for introduction into what 
had become critical infrastructure.  What I recall during the IPng discussions 
of the early 90s was promotion of the /concept/ of variable length addressing 
but without the experiential base to provide assurance we knew how it would operate.

Clearly the motivation for variable-length addresses is a Good Thing, since 
having it work properly would save needing to do an infrastructure change to 
quadruple the address space every 2-3 decades.  (With 128-bit addressing, 
perhaps it will be longer; with the rapid expansion of the Internet, perhaps it 
will be sooner.)


But really I'll suggest that fixed-vs-variable addressing is essentially 
irrelevant to the question of transition ease and backward compatibility.  What 
mostly affects that is effort.  Development, deployment and operations effort. 
For an established infrastructure, the more a change is different from what 
already is used, the more effort it takes to introduce the new thing.  (Versions 
of this point have been made on this thread repeatedly by other folk, and mostly 
everyone is ignoring the premise. I'll add that for folk who have noted the 
potential significance of my occasional consonance with the views of John 
Klensin, please be aware that its occurrence with Randy Bush is considerably 
more rare...)


Among the arguments being used to miss the point are:

>
> On 2/14/2012 2:34 PM, Brian E Carpenter wrote:
>> I'm sorry, but*any*  coexistence between RFC791-IPv4-only hosts and
>> hosts that are numbered out of an address space greater than 32 bits
>> requires some form of address sharing, address mapping, and translation.
>> It doesn't matter what choice we made back in 1994. Once you get to the
>> point where you've run out of 32 bit addresses and not every node can
>> support>32 bit addresses, you have the problem.

This notes an objective reality about a limit, while entirely missing the 
potential benefit available until reaching it.  In this case, that was a 15-20 
year window.

If the design goal had been restricted to the original "increase the address 
space bits", without encumbering it with additional architecture and functional 
changes, and had been based on re-use of the existing IPv4 scheme, the initial 
upgrade could have:

    a) been with a module tacked on to existing IPv4 implementations and 
installed as a relatively minor software upgrade (albeit with some additional 
API hooks) to most implementations, rather than the traumatic installation of an 
entirely new stack

    b) used trivial format-mapping translators rather than having to deal with 
the software and operational complexities of gateways that have to reconcile 
independent address spaces and other functionality

    c) had essentially no incremental deployment or operations costs

This would have gotten the core of the larger address space mechanism deployed 
and operational long before it was needed, and the focus after that would have 
been restricted to /using/ the additional bits, rather than trying to solve a 
variety of additional problems.

Moving from re-using IPv4 addressing to expansion into new IPv6 bits for 
addressing could have then been a separate, incremental step.  An important one, 
certainly.  A step with its own challenges, sure.  But incremental and narrow.

The classic project management point for major change is to minimize critical 
dependencies.  Instead, the IPv6 increased them.


> On 2/14/2012 3:56 PM, Bob Hinden wrote:
>> The deployment problem was not due to technical issues, it was because the Internet changed to only deploy new technology that generated revenue in the short term.

The Arpanet did not convert to production use of TCP/IP until it was forced to 
by a central authority in 1983.  Long before 'revenue' was an issue.

Absent coercion like this, organizations do not incur the considerable cost of 
infrastructure change in the absence of a strongly-perceived need that will have 
reasonably immediate and significant benefit.  This is one of the very basic 
reasons that any change targeting longer-term benefit and with little-to-no 
short-term benefit needs to be made as painless as possible.  In this case, 
painless would have meant being as compatible as possible, with small increments 
of change.

That is, I claim that absent well-funded research efforts and/or the leverage of 
a central authority, the history of the Net has /always/ been to focus on 
immediate need, not long-term benefit.  (This includes the original motivations 
for inventing packet-switching. Lofty long-term visions notwithstanding, it was 
overcoming expensive [and fragile] long-haul telecom costs and 
hostile-environment outages that motivated the work. )



On 2/14/2012 7:04 PM, Brian E Carpenter wrote:
 >> You would not have two distinct routing tables for two independent
 >> Internets, but a single routing table for a single Internet.
 >
 > True, but why is this a particular advantage? It wouldn't have
 > affected the need for an update to BGP4, for example.

With the sort of highly-constrained upgrade I've described above, no immediate 
change to BGP would have been required.  That could have been deferred to a 
follow-on effort.  The same applies to DHCP re-use.


> On 2/14/2012 3:26 PM, Mark Andrews wrote:
>> Happy eyeballs just points out problems with multi-homing in general.

Multi-homing is a problem above the IP layer, not at it.  As classically noted, 
the problem starts with using addresses as identifiers.


d/

[1] Unless I've misread, my brother and Scott have exactly opposite memories of 
which constituencies ere lobbying for and against variable-length addressing.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From matthew.bocci@alcatel-lucent.com  Wed Feb 15 07:09:54 2012
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D6421F869A; Wed, 15 Feb 2012 07:09:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.795
X-Spam-Level: 
X-Spam-Status: No, score=-107.795 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gUfJx55fgyTN; Wed, 15 Feb 2012 07:09:53 -0800 (PST)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id 35D0321F866C; Wed, 15 Feb 2012 07:09:53 -0800 (PST)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q1FF9jwX032427 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 15 Feb 2012 16:09:48 +0100
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.34]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 15 Feb 2012 16:09:34 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 15 Feb 2012 16:09:31 +0100
Subject: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
Thread-Topic: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
Thread-Index: Aczr89KtIVI7SxkNRWultcFx3Ew+Sw==
Message-ID: <CB617B2B.23929%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CB617B2B23929matthewboccialcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13
Cc: Adrian Farrel <adrian@olddog.co.uk>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:09:54 -0000

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

During Auth 48, the authors of draft-ietf-pwe3-static-pw-status found some =
issues with the acknowledgement procedures in Section 5.3 of the draft that=
 we feel should be addressed before publication. Since the draft has alread=
y been through WG and IETF last call, we would like to highlight the propos=
ed changes to the working group and solicit feedback.

Best regards,

Matthew

Section 5.3, 3rd paragraph:
Reason for change:
The current suggested default refresh timer value is too short to allow sca=
ling
to very large numbers of PWs while minimising the overhead. It is also inco=
nsistent
with the suggested default requested in an ACK packet. Therefore we suggest=
 increasing
the default to 600secs.

OLD: The suggested default value for the refresh timer is 30 seconds.

NEW: The suggested default value for the refresh timer is 600 seconds.



Section 5.3, 4th paragraph:
Reason for change:
The current text requires that a receiving PE must acknowledge a PW status =
message
of 'clear all faults' in order to force a transmitter to stop sending PW st=
atus
messages at 1 second intervals.  We are concerned that a mandatory acknowle=
dgement
adds an unnecessary complexity to the protocol which is inconsistent with
the use of the acknowledgement as per the following section (5.3.1). Additi=
onally,
we are also concerned that this may cause problems if a transmitter
is flapping between 'clear all faults' and a non-zero value, and if the
acknowledgement is lost. We therefore suggest that the acknowledgement to
'clear all faults' be made optional, and that  the transmitter behavior be =
changed so
that it sends up to 3 status messages of zero in a row, and then goes silen=
t.

OLD:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however, it MUST be
acknowledged with a packet with a timer value of zero.  This will cause
the PE sending the PW status notification message with a PW status code
equal to zero to stop sending and to continue normal operation.


NEW:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however,
transmission will cease after 3 PW status messages have been sent. A PW
status message of zero MAY be acknowledged as per the procedures described
in Section 5.3.1. If it is acknowledged, then a timer
value of zero MUST be used.  This SHOULD cause the PE sending the PW status
notification message with a PW status code equal to zero to stop sending
 and to continue normal operation.


Section 5.3.1, 1st paragraph:
Reason for change:
The procedures currently defined in this paragraph can lead to a receiver
of the static status message timing out if it requests, throught the use of=
 the
ACK mechanism, a longer refresh timer from the transmitter. This is because=
 the
current text implies that the transmitter change its referesh timer immedia=
tely
on receipt of the ack packet from the receiver. The new text clarifies that
the refresh timer be updated at the end of the current refresh interval, as
well as making some other editorial clarifications.

OLD:
The PE receiving a PW OAM message containing a PW status message
can acknowledge the PW status message by simply building an almost
identical reply packet with the A bit set, and transmitting it on the PW
ACH back to the source of the PW status message.  The timer value set in
the reply packet SHOULD then be used by the PE as the new transmit
interval.  If the transmitting PE does not want to use the new timer
value (for local policy reasons, or because it simply cannot support
it), it MUST refresh the PW OAM message with the timer value it desires.
The receiving PE will then set its timeout timer according to the timer
value that is in the packet received, regardless of what timer value it
sent.  The receiving PE MUST NOT retry to set the timer value more than
once per timer value.

NEW:
A PE receiving a PW OAM message containing a PW status message MAY
acknowledge the PW status message by simply building a reply packet
with the same format and status code as the received PW OAM message,
but with the A bit set, and transmitting it on the PW ACh back
to the source of the PW OAM message.  The receiving PE MAY use the
refresh timer field in the acknowledgement packet to request a new
refresh interval from the originator of the PW OAM message. The timer
value set in the reply packet SHOULD then be used by the originator of
the PW OAM message as the new transmit interval.  If the requested
refresh timer value is used, the PW OAM message transmission interval is
only set to the new value and the new value sent in the next PW OAM
message, when the current timer expires. If the transmitting PE does not
want to use the new timer value (for local policy reasons, or because it
simply cannot support it), it MUST refresh the PW OAM message with the
timer value it desires. The receiving PE will then set its timeout timer
according to the new refresh timer value that is in the packet received,
regardless of what timer value it requested.  The receiving PE MUST NOT
request a new refresh timer value more than once per refresh interval.


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div><div><div>During Auth 48=
, the authors of draft-ietf-pwe3-static-pw-status found some issues with th=
e acknowledgement procedures in Section 5.3 of the draft that we feel shoul=
d be addressed before publication. Since the draft has already been through=
 WG and IETF last call, we would like to highlight the proposed changes to =
the working group and solicit feedback.</div><div><br></div><div><div>Best =
regards,</div><div><br></div><div>Matthew</div></div></div><div><br></div><=
div>Section 5.3, 3rd paragraph:</div><div>Reason for change:</div><div>The =
current suggested default refresh timer value is too short to allow scaling=
&nbsp;</div><div>to very large numbers of PWs while minimising the overhead=
. It is also inconsistent</div><div>with the suggested default requested in=
 an ACK packet. Therefore we suggest increasing</div><div>the default to 60=
0secs.</div><div><br></div><div>OLD: The suggested default value for the re=
fresh timer is 30 seconds.</div><div><br></div><div>NEW: The suggested defa=
ult value for the refresh timer is 600 seconds.</div><div><br></div><div><b=
r></div><div><br></div><div>Section 5.3, 4th paragraph:</div><div>Reason fo=
r change:</div><div>The current text requires that a receiving PE must ackn=
owledge a PW status message</div><div>of 'clear all faults' in order to for=
ce a transmitter to stop sending PW status</div><div>messages at 1 second i=
ntervals. &nbsp;We are concerned that a mandatory acknowledgement</div><div=
>adds an unnecessary complexity to the protocol which is inconsistent with<=
/div><div>the use of the acknowledgement as per the following section (5.3.=
1). Additionally,</div><div>we are also concerned that this may cause probl=
ems if a transmitter&nbsp;</div><div>is flapping between 'clear all faults'=
 and a non-zero value, and if the&nbsp;</div><div>acknowledgement is lost. =
We therefore&nbsp;suggest that the acknowledgement to&nbsp;</div><div>'clea=
r all faults' be made optional, and that &nbsp;the transmitter behavior be =
changed so&nbsp;</div><div>that it sends up to 3 status messages of&nbsp;ze=
ro in a row, and then goes silent.</div><div><br></div><div>OLD:&nbsp;</div=
><div>To clear a particular status fault, the PE need only send an</div><di=
v>updated message with the corresponding bit cleared. &nbsp;If the PW statu=
s</div><div>code is zero, the PW OAM message will be sent like any other PW=
 OAM</div><div>status message using the procedures described above; however=
, it MUST be</div><div>acknowledged with a packet with a timer value of zer=
o. &nbsp;This will cause</div><div>the PE sending the PW status notificatio=
n message with a PW status code</div><div>equal to zero to stop sending and=
 to continue normal operation.</div><div><br></div><div><br></div><div>NEW:=
&nbsp;</div><div>To clear a particular status fault, the PE need only send =
an</div><div>updated message with the corresponding bit cleared. &nbsp;If t=
he PW status</div><div>code is zero, the PW OAM message will be sent like a=
ny other PW OAM</div><div>status message using the procedures described abo=
ve; however,</div><div>transmission will cease after 3 PW status messages h=
ave been sent. A PW</div><div>status message of zero MAY be acknowledged as=
 per the procedures described&nbsp;</div><div>in Section 5.3.1. If it is ac=
knowledged, then a timer</div><div>value of zero MUST be used. &nbsp;This S=
HOULD cause the PE sending the PW status</div><div>notification message wit=
h a PW status code equal to zero to stop sending</div><div>&nbsp;and to con=
tinue normal operation.</div><div><br></div><div><br></div><div>Section 5.3=
.1, 1st paragraph:</div><div>Reason for change:</div><div>The procedures cu=
rrently defined in this paragraph can lead to a receiver</div><div>of the s=
tatic status message timing out if it requests, throught the use of the</di=
v><div>ACK mechanism, a longer refresh timer from the transmitter. This is =
because the</div><div>current text implies that the transmitter change its =
referesh timer immediately</div><div>on receipt of the ack packet from the =
receiver. The new text clarifies that&nbsp;</div><div>the refresh timer be =
updated at the end of the current refresh interval, as&nbsp;</div><div>well=
 as making some other editorial clarifications.</div><div><br></div><div>OL=
D:&nbsp;</div><div>The PE receiving a PW OAM message containing a PW status=
 message</div><div>can acknowledge the PW status message by simply building=
 an almost</div><div>identical reply packet with the A bit set, and transmi=
tting it on the PW</div><div>ACH back to the source of the PW status messag=
e. &nbsp;The timer value set in</div><div>the reply packet SHOULD then be u=
sed by the PE as the new transmit</div><div>interval. &nbsp;If the transmit=
ting PE does not want to use the new timer</div><div>value (for local polic=
y reasons, or because it simply cannot support</div><div>it), it MUST refre=
sh the PW OAM message with the timer value it desires.</div><div>The receiv=
ing PE will then set its timeout timer according to the timer</div><div>val=
ue that is in the packet received, regardless of what timer value it</div><=
div>sent. &nbsp;The receiving PE MUST NOT retry to set the timer value more=
 than</div><div>once per timer value.</div><div><br></div><div>NEW:&nbsp;</=
div><div>A PE receiving a PW OAM message containing a PW status message MAY=
</div><div>acknowledge the PW status message by simply building a reply pac=
ket&nbsp;</div><div>with the same format and status code as the received PW=
 OAM message,</div><div>but with the A bit set, and transmitting it on the =
PW ACh back</div><div>to the source of the PW OAM message. &nbsp;The receiv=
ing PE MAY use the</div><div>refresh timer field in the acknowledgement pac=
ket to request a new</div><div>refresh interval from the originator of the =
PW OAM message. The timer</div><div>value set in the reply packet SHOULD th=
en be used by the originator of</div><div>the PW OAM message as the new tra=
nsmit interval. &nbsp;If the requested</div><div>refresh timer value is use=
d, the PW OAM message transmission interval is</div><div>only set to the ne=
w value and the new value sent in the next PW OAM</div><div>message, when t=
he current timer expires. If the transmitting PE does not</div><div>want to=
 use the new timer value (for local policy reasons, or because it</div><div=
>simply cannot support it), it MUST refresh the PW OAM message with the</di=
v><div>timer value it desires. The receiving PE will then set its timeout t=
imer</div><div>according to the new refresh timer value that is in the pack=
et received,</div><div>regardless of what timer value it requested. &nbsp;T=
he receiving PE MUST NOT</div><div>request a new refresh timer value more t=
han once per refresh interval.</div><div><br></div></div></body></html>

--_000_CB617B2B23929matthewboccialcatellucentcom_--

From jason_livingood@cable.comcast.com  Wed Feb 15 07:52:51 2012
Return-Path: <jason_livingood@cable.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 E47FF21F8537; Wed, 15 Feb 2012 07:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.099
X-Spam-Level: 
X-Spam-Status: No, score=-105.099 tagged_above=-999 required=5 tests=[AWL=3.364, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jy0Gg8ubGhws; Wed, 15 Feb 2012 07:52:49 -0800 (PST)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfa.amsl.com (Postfix) with ESMTP id 48E5D21F8533; Wed, 15 Feb 2012 07:52:49 -0800 (PST)
Received: from ([24.40.56.114]) by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.151544428; Wed, 15 Feb 2012 10:52:17 -0500
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%11]) with mapi id 14.01.0355.002; Wed, 15 Feb 2012 10:52:17 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Thread-Index: AQHM6/nKbjYam0no7UGRxd2Rv+MjlA==
Date: Wed, 15 Feb 2012 15:52:16 +0000
Message-ID: <CB61222C.50472%jason_livingood@cable.comcast.com>
In-Reply-To: <CB5F3DFE.4FFE3%jason_livingood@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [24.40.55.72]
Content-Type: multipart/alternative; boundary="_000_CB61222C50472jasonlivingoodcablecomcastcom_"
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:52:51 -0000

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

To be more specific, at least section 5.5 ("it is unclear how implementers =
will judge when the network conditions will have changed sufficiently to ju=
stify turning off DNS Resolver Whitelisting and/or what the process and tim=
ing will be for discontinuing this practice") is now incorrect. It *is* cle=
ar, and it's what those implementers are doing as part of World IPv6 Launch=
.

Does that make more sense?

As the author, if it helps I plan to make the following change to Section 5=
.5 following the conclusion of IETF Last Call. I ran this by a few folks al=
ready and it seems broadly acceptable (have not heard from Lorenzo yet thou=
gh).

Jason

CURRENT 5.5:
5.5.  Turning Off DNS Resolver Whitelisting

Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. It is unclear how implementers will judge =
when the network conditions will have changed sufficiently to justify turni=
ng off DNS Resolver Whitelisting and/or what the process and timing will be=
 for discontinuing this practice, though the extent of IPv6 deployment to e=
nd users in networks, the state of IPv6-related impairment, and the maturit=
y of IPv6 operations are all clearly factors. However, implementers may wis=
h to take into consideration that, as a practical matter, it will be imposs=
ible to get to a point where there are no longer any IPv6-related impairmen=
ts; some reasonably small number of hosts will inevitably be left behind as=
 end users elect not to upgrade them or as some hosts are incapable of bein=
g upgraded.

PROPOSED 5.5 (NEW TEXT IN ALL CAPS):
5.5.  Turning Off DNS Resolver Whitelisting

Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. It is unclear how implementers will judge =
when the network conditions will have changed sufficiently to justify turni=
ng off DNS Resolver Whitelisting and/or what the process and timing will be=
 for discontinuing this practice, though the extent of IPv6 deployment to e=
nd users in networks, the state of IPv6-related impairment, and the maturit=
y of IPv6 operations are all clearly factors. However, SOME IMPLEMENTERS HA=
VE ANNOUNCED THAT THEY PLAN TO PERMANENTLY TURN OFF WHITELISTING BEGINNING =
ON WORLD IPV6 DAY IN JUNE 2012 [REFERENCE]. IN ANY CASE, implementers may w=
ish to take into consideration that, as a practical matter, it will be impo=
ssible to get to a point where there are no longer any IPv6-related impairm=
ents; some reasonably small number of hosts will inevitably be left behind =
as end users elect not to upgrade them or as some hosts are incapable of be=
ing upgraded.

<eom>

--_000_CB61222C50472jasonlivingoodcablecomcastcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <6226C31D1F287E4D9CFC5F915534CDA7@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
ly: Calibri, sans-serif; ">
<span id=3D"OLK_SRC_BODY_SECTION">
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-famil=
y: Calibri, sans-serif; ">
<div>
<div>
<div><span id=3D"OLK_SRC_BODY_SECTION">
<div class=3D"gmail_quote">
<div>To be more specific, at least section 5.5 (&quot;it is unclear how&nbs=
p;implementers will judge when the network conditions will have changed&nbs=
p;sufficiently to justify turning off DNS Resolver Whitelisting and/or&nbsp=
;what the process and timing will be for discontinuing
 this practice&quot;) is now incorrect. It *is* clear, and it's what those =
implementers are doing as part of World IPv6 Launch.</div>
<div><br>
</div>
<div>Does that make more sense?</div>
</div>
</span></div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>As the author, if it helps I plan to make the following change to Sect=
ion 5.5 following the conclusion of IETF Last Call. I ran this by a few fol=
ks already and it seems broadly acceptable (have not heard from Lorenzo yet=
 though).&nbsp;</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-famil=
y: Calibri, sans-serif; ">
<div>
<div>
<div>
<div>Jason</div>
<div><br>
</div>
<div><u>CURRENT 5.5:&nbsp;</u></div>
<div>
<h3 style=3D"font-family: helvetica, monaco, 'MS Sans Serif', arial, sans-s=
erif; font-weight: bold; font-style: normal; color: rgb(51, 51, 51); backgr=
ound-color: rgb(255, 255, 255); font-variant: normal; letter-spacing: norma=
l; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0p=
x; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<font class=3D"Apple-style-span" size=3D"3">5.5.&nbsp; Turning Off DNS Reso=
lver Whitelisting</font></h3>
<p style=3D"margin-left: 2em; margin-right: 2em; color: rgb(0, 0, 0); font-=
family: verdana, charcoal, helvetica, arial, sans-serif; font-style: normal=
; font-variant: normal; font-weight: normal; letter-spacing: normal; line-h=
eight: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text=
-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webki=
t-text-size-adjust: auto; -webkit-text-stroke-width: 0px; background-color:=
 rgb(255, 255, 255); ">
Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. It is unclear how implementers will judge =
when the network conditions will have changed sufficiently to justify turni=
ng off DNS Resolver Whitelisting
 and/or what the process and timing will be for discontinuing this practice=
, though the extent of IPv6 deployment to end users in networks, the state =
of IPv6-related impairment, and the maturity of IPv6 operations are all cle=
arly factors. However, implementers
 may wish to take into consideration that, as a practical matter, it will b=
e impossible to get to a point where there are no longer any IPv6-related i=
mpairments; some reasonably small number of hosts will inevitably be left b=
ehind as end users elect not to
 upgrade them or as some hosts are incapable of being upgraded.</p>
</div>
<div><u>PROPOSED 5.5 (NEW TEXT IN ALL CAPS):</u></div>
<div>
<h3 style=3D"font-family: helvetica, monaco, 'MS Sans Serif', arial, sans-s=
erif; font-weight: bold; font-style: normal; color: rgb(51, 51, 51); backgr=
ound-color: rgb(255, 255, 255); font-variant: normal; letter-spacing: norma=
l; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0p=
x; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<font class=3D"Apple-style-span" size=3D"3">5.5.&nbsp; Turning Off DNS Reso=
lver Whitelisting</font></h3>
<p style=3D"margin-left: 2em; margin-right: 2em; color: rgb(0, 0, 0); font-=
family: verdana, charcoal, helvetica, arial, sans-serif; font-style: normal=
; font-variant: normal; letter-spacing: normal; line-height: normal; orphan=
s: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; whi=
te-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: a=
uto; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); =
">
Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. It is unclear how implementers will judge =
when the network conditions will have changed sufficiently to justify turni=
ng off DNS Resolver Whitelisting
 and/or what the process and timing will be for discontinuing this practice=
, though the extent of IPv6 deployment to end users in networks, the state =
of IPv6-related impairment, and the maturity of IPv6 operations are all cle=
arly factors. However,&nbsp;<b>SOME IMPLEMENTERS
 HAVE ANNOUNCED THAT THEY PLAN TO PERMANENTLY TURN OFF WHITELISTING BEGINNI=
NG ON WORLD IPV6 DAY IN JUNE 2012 [REFERENCE]. IN ANY CASE</b>, implementer=
s may wish to take into consideration that, as a practical matter, it will =
be impossible to get to a point
 where there are no longer any IPv6-related impairments; some reasonably sm=
all number of hosts will inevitably be left behind as end users elect not t=
o upgrade them or as some hosts are incapable of being upgraded.</p>
<div>&lt;eom&gt;</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CB61222C50472jasonlivingoodcablecomcastcom_--

From kirk.erichsen@twcable.com  Tue Feb 14 09:19:44 2012
Return-Path: <kirk.erichsen@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1DAE21F8602 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:19:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wn5BdNti7CFA for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 09:19:44 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4B16E21F85F2 for <ietf@ietf.org>; Tue, 14 Feb 2012 09:19:44 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.73,417,1325480400"; d="scan'208";a="322133762"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 14 Feb 2012 12:19:29 -0500
Received: from PRVPEXVS09.corp.twcable.com ([10.136.163.39]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Tue, 14 Feb 2012 12:19:43 -0500
From: "Erichsen, Kirk" <kirk.erichsen@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 14 Feb 2012 12:19:42 -0500
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
Thread-Topic: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
Thread-Index: AQHM6zu8ljhO4HUadUOTr5Z/kOrteA==
Message-ID: <8F9F107F1A51524597A5D2E0F43EE9632AD416BD28@PRVPEXVS09.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 15 Feb 2012 08:10:46 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:19:44 -0000

I fully support this draft and would like to see it progress to conclusion =
without further delay.

With warm regard,

Kirk Erichsen
Principle Technology Engineer
Time Warner Cable
ATG West


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From sob@sobco.com  Tue Feb 14 10:29:02 2012
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 225C421F86D0 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.494
X-Spam-Level: 
X-Spam-Status: No, score=-0.494 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SE9UztOTunEm for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 10:29:01 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD0E21F86B3 for <ietf@ietf.org>; Tue, 14 Feb 2012 10:28:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id B9C29258F98B for <ietf@ietf.org>; Tue, 14 Feb 2012 13:28:58 -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 xm+8CTQum-xs for <ietf@ietf.org>; Tue, 14 Feb 2012 13:28:57 -0500 (EST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by sobco.sobco.com (Postfix) with ESMTPSA id D8F56258F973 for <ietf@ietf.org>; Tue, 14 Feb 2012 13:28:56 -0500 (EST)
From: Scott O Bradner <sob@sobco.com>
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_29B88600-399E-4093-80DE-2B89420D1CDD"
Subject: Re: Another last call for draft-weil
Date: Tue, 14 Feb 2012 13:28:56 -0500
In-Reply-To: <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net>
To: ietf@ietf.org
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net>
Message-Id: <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Wed, 15 Feb 2012 08:11:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:29:02 -0000

--Apple-Mail=_29B88600-399E-4093-80DE-2B89420D1CDD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

+1

On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:

> +1.
> =20
> Ross
> =20
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Owen DeLong
> Sent: Monday, February 13, 2012 2:06 PM
> To: ietf@ietf.org
> Cc: draft-bdgks-arin-shared-transition-space@tools. org
> Subject: Re: Another last call for draft-weil
> =20
> I support draft-weil as revised. There is a vital need for this to =
move forward and the IETF should stop standing in the way and let ARIN =
allocate the space already.
> =20
> Owen
> =20
> On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote:
>=20
>=20
> Fellow BDGKS Authors,
> =20
> FYI: draft-weil is in another Last Call following an update that was =
requested by IESG Ads (on their December telechat, some ADs asked us to =
turn our request into a request for more 1918 space, but with a few =
caveats to home router manufacturers about not breaking when exposed to =
a CGN environment.). At this point we don't expect to change any minds. =
Basically everyone who is against the draft has spoken up. Now it is =
just a numbers game, we need to demonstrate significant support for the =
draft.
> =20
> If you do support this I-D and the allocation of the /10 for shared =
CGN use, please consider posting a statement of support.  Something as =
simple as "I support this draft as updated" or "I think the updated =
draft is more flexible, and would satisfy additional use cases that =
don't work with RFC1918 space" would be very helpful.
> =20
> You can respond to the "Last Call: =
<draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 =
Prefix for Shared Address Space) to BCP" thread or post individually to  =
ietf@ietf.org. Also, please feel free to encourage anyone else you know =
who supports the draft to make a similar post. Every statement we can =
gather is vital right now. Last call ends on Thursday, so reply's must =
be made before then. Thank you.
> =20
> Cheers,
> ~Chris
> =20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail=_29B88600-399E-4093-80DE-2B89420D1CDD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">+1<div><br><div><div>On Feb 14, 2012, at 1:25 PM, Ross Callon =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); =
">+1.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Ross<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div><div style=3D"border-right-style: =
none; border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-top-style: solid; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: =
0in; "><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: =
0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:ietf-bounces@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">ietf-bounces@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>[mailto:ietf-bounces@ietf.org=
]<span class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Owen =
DeLong<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Monday, February 13, 2012 =
2:06 PM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:ietf@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">ietf@ietf.org</a><br><b>Cc:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>draft-bdgks-arin-shared-trans=
ition-space@tools. org<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: Another last call for =
draft-weil<o:p></o:p></span></div></div></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; ">I support draft-weil as =
revised. There is a vital need for this to move forward and the IETF =
should stop standing in the way and let ARIN allocate the space =
already.<o:p></o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
">Owen<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">On Feb 13, 2012, at 10:09 =
AM, Chris Grundemann wrote:<o:p></o:p></div></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><br><br><o:p></o:p></div><div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: black; ">Fellow BDGKS =
Authors,<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p>&nbsp;</o:p></span></div></div><div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: black; ">FYI: draft-weil is in another Last Call =
following an update that was requested by IESG Ads&nbsp;(o</span><span =
class=3D"apple-style-span"><span style=3D"font-size: 13.5pt; =
font-family: Calibri, sans-serif; color: black; ">n their December =
telechat, some ADs asked us to turn our&nbsp;request into a request for =
more 1918 space, but with a few caveats to home&nbsp;router =
manufacturers about not breaking when exposed to a CGN =
environment.)</span></span><span class=3D"apple-style-span"><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; ">. At this point we don't expect to change any minds. Basically =
everyone who is against the draft has spoken up. Now it is just a =
numbers game, we need to demonstrate significant support for the =
draft.</span></span><span style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; color: black; =
"><o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: black; =
"><o:p>&nbsp;</o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; ">If you do support this I-D and the allocation of the /10 for =
shared CGN use, please consider posting a statement of support. =
&nbsp;</span><span class=3D"apple-style-span"><span style=3D"font-size: =
13.5pt; font-family: Calibri, sans-serif; color: black; ">Something as =
simple as "I support this draft as updated" or "I think&nbsp;the updated =
draft is more flexible, and would satisfy additional use cases&nbsp;that =
don't work with RFC1918 space" would be very helpful.</span></span><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Calibri, sans-serif; color: =
black; "><o:p>&nbsp;</o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10.5pt; font-family: Calibri, =
sans-serif; color: black; ">You can respond to the "</span><span =
class=3D"hp"><span style=3D"font-family: Calibri, sans-serif; color: =
black; ">Last Call: =
&lt;draft-weil-shared-transition-space-request-14.txt&gt; (IANA Reserved =
IPv4 Prefix for Shared Address Space) to BCP</span></span><span =
class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; color: black; ">" thread or post =
individually to&nbsp;&nbsp;<a href=3D"mailto:ietf@ietf.org" =
style=3D"color: blue; text-decoration: underline; ">ietf@ietf.org</a>. =
Also, please feel free to encourage anyone else you know who supports =
the draft to make a similar post. Every statement we can gather is vital =
right now. Last call ends on Thursday, so reply's must be made before =
then. Thank you.</span></span><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; color: black; =
"><o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Calibri, sans-serif; color: black; =
"><o:p>&nbsp;</o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; color: black; =
">Cheers,</span></span><span style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; color: black; =
"><o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span =
class=3D"apple-style-span"><span style=3D"font-size: 10.5pt; =
font-family: Calibri, sans-serif; color: black; =
">~Chris</span></span><span style=3D"font-size: 10.5pt; font-family: =
Calibri, sans-serif; color: black; =
"><o:p></o:p></span></div></div></div></div></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; =
"><o:p>&nbsp;</o:p></div></div></div>_____________________________________=
__________<br>Ietf mailing list<br><a href=3D"mailto:Ietf@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">Ietf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/ietf</a><br></div></span></blockqu=
ote></div><br></div></body></html>=

--Apple-Mail=_29B88600-399E-4093-80DE-2B89420D1CDD--

From ben@nostrum.com  Tue Feb 14 12:11:47 2012
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 CFBD621E80E9; Tue, 14 Feb 2012 12:11:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGOUsh+SGZEP; Tue, 14 Feb 2012 12:11:44 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 112D321E80FC; Tue, 14 Feb 2012 12:11:40 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1EKBHu1068065 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 14 Feb 2012 14:11:18 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Followup Gen-ART Review on draft-ietf-dhc-forcerenew-nonce
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=windows-1252
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
Date: Tue, 14 Feb 2012 14:11:20 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <11343191-B00C-43DD-8C78-A746226C9566@nostrum.com>
References: <A57C4722-5E13-451E-ACB4-CAA8064FA68B@nostrum.com>
To: draft-ietf-dhc-forcerenew-nonce.all@tools.ietf.org
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Wed, 15 Feb 2012 08:12:21 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:11:50 -0000

Hi,

This is a followup on my Gen-ART review of =
draft-ietf-dhc-forcerenew-nonce-04, based on my previous review of =
version 03. In summary, this version is improved, but I still don't =
think it's ready for publication.


On Feb 6, 2012, at 5:17 PM, Ben Campbell wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-dhc-forcerenew-nonce-03
> Reviewer: Ben Campbell
> Review Date: 2012-02-06
> IETF LC End Date: 2012-02-06
>=20
> Summary:This draft is not quite ready for publication as a proposed =
standard. There are some potentially significant issues that should be =
addressed first.
>=20
> [Note: Hopefully this draft has had or will have a SecDir review, =
since it seems ripe for significant security implications.]
>=20

I didn't see a comment about whether this happened. I still recommend a =
SecDir review if one has not yet occurred.

>=20
> *** Major issues:
>=20
> -- I admit to not being a DHCP expert, but If I understand this draft =
correctly, it proposes to send what is effectively a secret-key in a =
DHCPACK request, then use that key to authenticate a force renew =
message. It seems like any eavesdropper could sniff that key, and use it =
to spoof force renew requests. The introduction mentions that there may =
be some environments where the use of RFC3118 authentication could be =
relaxed, and offers an example of such an environment. But nowhere does =
this draft appear to be limited in scope to such environments.=20
>=20
> I think some additional text in (perhaps in the security =
considerations) is needed to explain either why the vulnerability to =
eavesdroppers is either okay in general, or limits the mechanism's use =
to environment where it is okay. It also seems like that, in the best =
case, this mechanism proves only that a Forcerenew request comes from =
the same DHCP server as in the original transaction, but otherwise does =
not prove anything about the identity of that server. If so, it would be =
worth mentioning it.
>=20

This is improved by some changes to the introduction and the security =
considerations. But I still don't see a clear, normative statement about =
what environments this can be safely used in. I know Ted objected to =
Roberta's specific proposal, but I think to move forward this needs =
_some_ clear, concrete guidance about when to use or not to use it, or =
when 3118 authentication is more appropriate. Don't leave it up to the =
reader to draw the right conclusion.


> -- The mechanism appears to be limited to HMAC-MD5, and there does not =
appear to be any way of selecting other algorithms. Is HMAC-MD5 really =
sufficient as the only choice? Is there some expectation that stronger =
mechanisms or algorithm extensibility would be too expensive? (Perhaps =
the extensibility method would be to specify another mechanism that's =
identical except for a different HMAC algorithm. But if that's the =
intent it should be mentioned.)

There's a statement in the security considerations that "... security of =
the nonce in the case of on-link attacks isn't relevant." It would help =
drive the point home to add something to the effect that "Therefore =
HMAC-MD5 is by definition adequate for the purpose, and there is no need =
for an extensible HMAC mechanism."

>=20
> *** Minor issues:
>=20
> -- Section 1 "=20
> In such environments the mandatory coupling between FORCERENEW and =
DHCP Authentication [RFC3118] can be relaxed."
>=20
> It's not clear to me what connection that assertion has with this =
draft. Is there an intent that the proposed mechanisms be used only in =
such environments? I don't find any language scoping this proposal to =
any particular environment.

See comment under the first "major issue". I still think we need =
normative, concrete guidance about when to use or not to use this =
mechanism.

[...]


>=20
> -- section 3.1.3, 2nd paragraph: "The server SHOULD NOT include this =
option unless the client has indicated its capability in a DHCP =
Discovery message."
>=20
> Why not; what harm would it do? And on the other hand, if you want to =
discourage it, why not go all the way to "MUST NOT"?
>=20

I don't think my comment has been addressed by the discussion so far. I =
understand that the server should not insert a nonce unless the client =
has advertised support--but is it the author's intent that the server =
should not _advertise_ support unless the client has first advertised =
support?

Additionally, this update added the following text to the section:

> The=20
> server SHOULD NOT include the nonce in an ACK when responding to
>    a renew unless a nonce was generated.  This minimizes the number of
>    times the nonce is sent over the wire.


I don't understand the first sentence. Don't include a nonce unless you =
generated it first? That seems like a tautology. Do you mean to say =
unless the nonce was sent in a previous message? Or unless a _new_ nonce =
was generated?

[...]

>=20
> -- section 3.1.4, 1st paragraph: "DHCP servers that support Forcerenew =
nonce Protocol authentication MUST include the DHCP Forcerenew Nonce =
protocol authentication option=85"
>=20
> Only if the client advertised it, right? Otherwise, this seems to =
conflict with the previous SHOULD NOT.

The text is updated, but it still conflicts with the previous statement =
in 3.1.3, paragraph 2 that says the server SHOULD NOT insert the option =
unless the client first inserted it. (See comment above).

[...]


>=20
> -- section 6:
>=20
> You mention this mechanism is vulnerable to MiTM attacks. Why is this =
okay? Are there some environments where it is good enough and others =
where it is not? (Also, do they really need to be MitM attackers? Seems =
like any eavesdropper could learn the nonce.)

The text still refers to a MiTM attacker. Do you mean "on-link" =
attacker?=20

Otherwise, you've added text to motivate the mechanism for a specific =
use case. But I'd still like to see concrete guidance about when this =
draft is appropriate to use.

>=20
> *** Nits/editorial comments:
>=20
> -- Abstract, second sentence:
>=20
> I have trouble parsing this sentence. Are the propositions correct?

Partially fixed. Should "on the initial ACK" be "in the initial ACK"?

>=20
> -- Section 3.1.1,4th paragraph: "=85 configured to require =85"
>=20
> Do you mean configured to "require", or configured to "use"? I would =
normally take "requires" to mean that the server would not work with =
clients that don't advertise support for the mechanism.

You changed the text from "configured to require" to "requires". I'm =
still confused on whether "requires" means that the server will refuse =
to service clients that don't advertise support. This is in contrast to =
"use", which would mean to me the server would invoke the option if the =
client supports it, but still work with clients that don't support it.

[...]


From owen@delong.com  Tue Feb 14 14:40:02 2012
Return-Path: <owen@delong.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC24E21F8568 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 14:40:02 -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=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iI2ffAYYwqSE for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2012 14:40:02 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id BD41F21F8564 for <ietf@ietf.org>; Tue, 14 Feb 2012 14:40:01 -0800 (PST)
Received: from [IPv6:2620::930:0:ca2a:14ff:fe3e:d024] ([IPv6:2620:0:930:0:ca2a:14ff:fe3e:d024]) (authenticated bits=0) by owen.delong.com (8.14.1/8.14.1) with ESMTP id q1EMdBsX028164 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 14 Feb 2012 14:39:12 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com q1EMdBsX028164
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1329259154; bh=R90ITFAzGJfd5m3zNQgmJ0k3YI0=; h=Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=AMLaHicpyEKCUOk5DObyzDeHOW18CRUpz3crGb18G31EFnOQ+5MjwIsJspD1ZF1SV 5vntBKv7MZnBeM0ow49xL0cHAO+rnnKOVzRpKEWuicIPWIwlP8pWW4W09S+T39dM8a beIoYg0O7dd9HedcGEi+s27DlrBb+it0xAUzUBEI=
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8C3C431F-84D8-492D-9767-07BA6264A193"
From: Owen DeLong <owen@delong.com>
In-Reply-To: <4F3AAA08.2040204@qualcomm.com>
Date: Tue, 14 Feb 2012 14:39:11 -0800
Message-Id: <FCE11E3F-5BE1-407A-9560-005003338225@delong.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1251.1)
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (owen.delong.com [IPv6:2620:0:930::200:2]); Tue, 14 Feb 2012 14:39:14 -0800 (PST)
X-Mailman-Approved-At: Wed, 15 Feb 2012 08:12:36 -0800
Cc: ietf@ietf.org, "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:40:02 -0000

--Apple-Mail=_8C3C431F-84D8-492D-9767-07BA6264A193
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

I'm agnostic about the latest round of changes or not. I just want =
EITHER version to move forward soon!

Owen

On Feb 14, 2012, at 10:38 AM, Pete Resnick wrote:

> To the addressed folks who's messages appear below:
>=20
> I'm not sure I understand what you're saying. There was some objection =
at the beginning of this thread by Wes George, Noel Chiappa, and Brian =
Carpenter. I agreed that the document could be misunderstood as =
encouraging the use of the space as 1918 space and proposed some =
replacement text. There seemed to be some agreement around that text. =
Are you now objecting to that replacement text and want -14 published as =
is? Do you think the document should say that the new allocation can be =
used as 1918 space? If so, please explain.
>=20
> pr
>=20
> On 2/14/12 8:54 AM, Donald Eastlake wrote:
>>=20
>> I also support this draft.
>=20
> On 2/14/12 9:06 AM, ned+ietf@mauve.mrochek.com wrote:
>>=20
>> On Tuesday, February 14, 2012, Daryl Tanner =
<daryl.tanner@blueyonder.co.uk> wrote:
>>> I support this updated draft, and I am keen for this to be published =
as a
>>> BCP.
>>>    =20
>> +1
>>=20
>>  =20
>>> I believe the amendments in this revision clarify the usage and =
intended
>>> purpose of the shared transition space.
>>>    =20
>> +1
>>=20
>>  =20
> On 2/14/12 10:19 AM, Jeff.Finkelstein@cox.com wrote:
>>=20
>> I support this draft as updated.
>>  =20
>=20
> On 2/13/12 1:05 PM, Owen DeLong wrote:
>>=20
>> I support draft-weil as revised. There is a vital need for this to =
move forward and the IETF should stop standing in the way and let ARIN =
allocate the space already.
>=20
> On 2/14/12 12:25 PM, Ross Callon wrote:
>=20
>> +1
>>  =20
>=20
> --=20
> Pete Resnick <http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: =
(858)651-1102


--Apple-Mail=_8C3C431F-84D8-492D-9767-07BA6264A193
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'm agnostic about the latest round of changes or not. I just want EITHER version to move forward soon!<div><br></div><div>Owen</div><div><br><div><div>On Feb 14, 2012, at 10:38 AM, Pete Resnick wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">


  <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">

<div bgcolor="#ffffff" text="#000000">
To the addressed folks who's messages appear below:<br>
<br>
I'm not sure I understand what you're saying. There was some objection
at the beginning of this thread by Wes George, Noel Chiappa, and Brian
Carpenter. I agreed that the document could be misunderstood as
encouraging the use of the space as 1918 space and proposed some
replacement text. There seemed to be some agreement around that text.
Are you now objecting to that replacement text and want -14 published
as is? Do you think the document should say that the new allocation can
be used as 1918 space? If so, please explain.<br>
<br>
pr<br>
<br>
On 2/14/12 8:54 AM, Donald Eastlake wrote:
<blockquote cite="mid:CAF4+nEERtpjGr33=f56rEuYf5PQO=w8p4HYvnTeiqghee5KiHg@mail.gmail.com" type="cite">I also support this draft.<br>
</blockquote>
<br>
On 2/14/12 9:06 AM, <a class="moz-txt-link-abbreviated" href="mailto:ned+ietf@mauve.mrochek.com">ned+ietf@mauve.mrochek.com</a> wrote:
<blockquote cite="mid:01OBYZWPJ4WM00ZUIL@mauve.mrochek.com" type="cite">
  <pre wrap="">On Tuesday, February 14, 2012, Daryl Tanner &lt;<a moz-do-not-send="true" href="mailto:daryl.tanner@blueyonder.co.uk">daryl.tanner@blueyonder.co.uk</a>&gt; wrote:</pre>
  <blockquote type="cite">
    <pre wrap="">I support this updated draft, and I am keen for this to be published as a
BCP.
    </pre>
  </blockquote>
  <pre wrap="">+1

  </pre>
  <blockquote type="cite">
    <pre wrap="">I believe the amendments in this revision clarify the usage and intended
purpose of the shared transition space.
    </pre>
  </blockquote>
  <pre wrap="">+1

  </pre>
</blockquote>
On 2/14/12 10:19 AM, <a class="moz-txt-link-abbreviated" href="mailto:Jeff.Finkelstein@cox.com">Jeff.Finkelstein@cox.com</a> wrote:
<blockquote cite="mid:CB5FF399.1B4E7%25jeff.finkelstein@cox.com" type="cite">
  <pre wrap="">I support this draft as updated.
  </pre>
</blockquote>
<br>
On 2/13/12 1:05 PM, Owen DeLong wrote:
<blockquote cite="mid:2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com" type="cite">I support draft-weil as revised. There is a vital need for
this to move
forward and the IETF should stop standing in the way and let ARIN
allocate the space already.</blockquote>
<br>
On 2/14/12 12:25 PM, Ross Callon wrote:<br>
<br>
<blockquote type="cite">
  <pre wrap="">+1
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102</pre>
</div>

</blockquote></div><br></div></body></html>
--Apple-Mail=_8C3C431F-84D8-492D-9767-07BA6264A193--

From jmh@joelhalpern.com  Wed Feb 15 09:23:28 2012
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 3BA2E21F8730 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 09:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.965
X-Spam-Level: 
X-Spam-Status: No, score=-101.965 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_24=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Ga9GvnixVU5 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 09:23:24 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 6954821F85C2 for <ietf@ietf.org>; Wed, 15 Feb 2012 09:23:24 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 9F061CD23E for <ietf@ietf.org>; Wed, 15 Feb 2012 09:23:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 52A331C2B30 for <ietf@ietf.org>; Wed, 15 Feb 2012 09:23:23 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.155.34.51] (unknown [129.192.185.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E47F91C08BE for <ietf@ietf.org>; Wed, 15 Feb 2012 09:23:22 -0800 (PST)
Message-ID: <4F3BEA08.7020909@joelhalpern.com>
Date: Wed, 15 Feb 2012 12:23:20 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Another last call for draft-weil
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com>
In-Reply-To: <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:23:28 -0000

I agree.  This needs to be published by the IETF as an RFC. the current 
form is quite suitable for that.

Yours,
Joel

On 2/14/2012 1:28 PM, Scott O Bradner wrote:
> +1
>
> On Feb 14, 2012, at 1:25 PM, Ross Callon wrote:
>
>> +1.
>> Ross
>> *From:*ietf-bounces@ietf.org
>> <mailto:ietf-bounces@ietf.org>[mailto:ietf-bounces@ietf.org]*On Behalf
>> Of*Owen DeLong
>> *Sent:*Monday, February 13, 2012 2:06 PM
>> *To:*ietf@ietf.org <mailto:ietf@ietf.org>
>> *Cc:*draft-bdgks-arin-shared-transition-space@tools. org
>> *Subject:*Re: Another last call for draft-weil
>> I support draft-weil as revised. There is a vital need for this to
>> move forward and the IETF should stop standing in the way and let ARIN
>> allocate the space already.
>> Owen
>> On Feb 13, 2012, at 10:09 AM, Chris Grundemann wrote:
>>
>>
>> Fellow BDGKS Authors,
>> FYI: draft-weil is in another Last Call following an update that was
>> requested by IESG Ads (on their December telechat, some ADs asked us
>> to turn our request into a request for more 1918 space, but with a few
>> caveats to home router manufacturers about not breaking when exposed
>> to a CGN environment.). At this point we don't expect to change any
>> minds. Basically everyone who is against the draft has spoken up. Now
>> it is just a numbers game, we need to demonstrate significant support
>> for the draft.
>> If you do support this I-D and the allocation of the /10 for shared
>> CGN use, please consider posting a statement of support. Something as
>> simple as "I support this draft as updated" or "I think the updated
>> draft is more flexible, and would satisfy additional use cases that
>> don't work with RFC1918 space" would be very helpful.
>> You can respond to the "Last Call:
>> <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved
>> IPv4 Prefix for Shared Address Space) to BCP" thread or post
>> individually to ietf@ietf.org <mailto:ietf@ietf.org>. Also, please
>> feel free to encourage anyone else you know who supports the draft to
>> make a similar post. Every statement we can gather is vital right now.
>> Last call ends on Thursday, so reply's must be made before then. Thank
>> you.
>> Cheers,
>> ~Chris
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org <mailto:Ietf@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ietf
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From jnc@mercury.lcs.mit.edu  Wed Feb 15 10:23:44 2012
Return-Path: <jnc@mercury.lcs.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 1D8C321E804E for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 10:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.25
X-Spam-Level: 
X-Spam-Status: No, score=-5.25 tagged_above=-999 required=5 tests=[AWL=-1.065,  BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vt2eDOPU1bza for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 10:23:39 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 7D56C21E8051 for <ietf@ietf.org>; Wed, 15 Feb 2012 10:23:39 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 4D6E818C0CD; Wed, 15 Feb 2012 13:23:38 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
Message-Id: <20120215182338.4D6E818C0CD@mercury.lcs.mit.edu>
Date: Wed, 15 Feb 2012 13:23:38 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:23:44 -0000

    > From: Bob Braden <braden@isi.edu>

    > You probably remember this, but...

I was on the very edge at the time (more below), but yes. A few things that
caught my eye (including a minor date offset - I like to get noise out of the
record before it gets engrained):


    > argued strenuously for variable length addresses. (This must have
    > been around 1979. I cannot name most of the other 10 people in the
    > room, but I have a clear mental picture of Jon, in the back of the
    > room, fuming over this issue. Jon believed intensely in protocol
    > extensibility.)

There was a discussion about this on the internet-history list (although
in the content of TCP/IP-v4's birthday) back at the end of March, 2006:

  http://mailman.postel.org/pipermail/internet-history/2006-March/date.html

It turned out that the relevant meeting was the one held at MIT on 15-16
June 1978 (minutes are in IEN-68); the final formats for TCP4 and IPv4
were picked on 16 June, and documented in IEN-44 ("Latest Header Formats")
immediately thereafter.

I don't know about Jon or Danny, but I have a _very_ clear memory of David
Reed coming out of the meeting and being totally disgusted! (My office was
just a few feet down the hall from the conference room - I wasn't in the
meeting, I guess I wasn't considered 'real' enough yet! My first meeting
was the August, 1978 meeting.)


    > His argument was that TCP/IP had to be simple to implement if it
    > were to succeed
    > ...
    > variable length addresses seemed to be (and in fact would be) harder
    > to program and would make packet dumps harder to interpret.

The sad part is that we could have had our cake, and eaten it too! If we'd
kept the variable length packet format, and said 'for now, the only supported
length is 4', we'd have had the best of both worlds: simple implementations,
and longer-term flexibility. (I have no problems with implementation hacks:
e.g. the early MIT router code for subnets initially had a 'MyANet' static
variable in it, which was non-0 on a subnetted network! :-)

It would have been so _easy_, if only we'd thought of it!  And look how much
it would have saved us!!  Oh well, 20/20 hindsight. But this need to have a
perfect balance between implementability and long-term flexibility is a lesson
that has stayed with me very forcefully.


    > (and survive the juggernaut of the ISO OSI protocol suite).

I don't really recall the ISO suite being a big concern at that point? I
know some years later it was, but it was totally off my personal radar at
that point.

I do recall very clearly some mutterings in the hallway after the June 78
meeting about the number of pointer registers available at interrupt time
in TENEX (although to be fair I doubt that was the reason fixed-length was
chosen)!

	Noel

From martin@millnert.se  Wed Feb 15 10:29:32 2012
Return-Path: <martin@millnert.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 D5B9921F853B for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 10:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.129
X-Spam-Level: 
X-Spam-Status: No, score=-2.129 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZRAvyReY4WO for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 10:29:32 -0800 (PST)
Received: from ncis.csbnet.se (ncis.csbnet.se [95.80.1.101]) by ietfa.amsl.com (Postfix) with ESMTP id 536D721F853A for <ietf@ietf.org>; Wed, 15 Feb 2012 10:29:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id 6068078D; Wed, 15 Feb 2012 19:27:11 +0100 (CET)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lI-Sg6--5udi; Wed, 15 Feb 2012 19:27:11 +0100 (CET)
Received: from [192.168.120.227] (h-189-4.a189.priv.bahnhof.se [85.24.189.4]) by ncis.csbnet.se (Postfix) with ESMTPSA id 25C7415C; Wed, 15 Feb 2012 19:27:10 +0100 (CET)
Message-ID: <1329330563.5382.6.camel@davinci.millnert.se>
Subject: Re: Variable length internet addresses in TCP/IP: history
From: Martin Millnert <martin@millnert.se>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Date: Wed, 15 Feb 2012 19:29:23 +0100
In-Reply-To: <20120215182338.4D6E818C0CD@mercury.lcs.mit.edu>
References: <20120215182338.4D6E818C0CD@mercury.lcs.mit.edu>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-97ZikbE1HFxS9c3rv5TP"
X-Mailer: Evolution 3.0.3-3 
Mime-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:29:32 -0000

--=-97ZikbE1HFxS9c3rv5TP
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, 2012-02-15 at 13:23 -0500, Noel Chiappa wrote:
> The sad part is that we could have had our cake, and eaten it too!=20

If a (hierarchical) variable length addressing would not have mandated a
hierarchical routing as well, then yeah, cake would have tasted well as
it remained there on the table.

/M

--=-97ZikbE1HFxS9c3rv5TP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

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

iQIcBAABAgAGBQJPO/mDAAoJEKgraNdZrwxM5bwP+wQ3pPrX+HM1jveDS86q/LMt
I+DvbKBx+pYezX68KH4Om3DdAekO1njGFSUu0D67K5LJkt2wcDu4RO3jElnU6BAm
pBhL74j5synHA8cY9ed7gt8QdKw4ccpAlh1EG2q3c8SEIKxOVxivgwb5nTLksiCv
6RmeTrvVGPzctakIT3Heh4K0ShoE4ryL6xU6bVRO0mG3xolBDR4+qC9AibZACuz3
sIoIg9iyX8ITS3Nnte2IPxo/X8sqVuPOajnbUQsYx4LcSQSDGGeAFuvFMwKYMgg0
L3aLtyVCZ43qcy9394nVpATXYsARWXhlw/jkUb3sMlgICKuAI4RvjUFipZRJerHi
lgo5R+eyjnrLPCUd/NCJBXt38e/w8JpuFIm++6rAllqH84Ah5wEbEYYe2SUdPnuK
LWRut47NN5xffHvq6fJVrHtecXFBV2Edg1ViIei5yS5WwuOZsrx+qwPTs1LOSShp
bNiLHfffMjIb8VtIVPRNjJqRL+eVSOApW/mbehX0EcH6y4gs73vcK3dN6tpn9mjY
/E0Z9JZZO3u0ethkx/lF5G70KqEEpfEizAeWw64DnJPkolC6+x0akN2b+e2sgsEr
lZf1q/W7ReH3DfaeWsyqKf9exzZUedNPaNVlpxVOmsiJmKFFIquUcmdWESWyyf4B
rWimqMg/irnt7dep95Yp
=ko71
-----END PGP SIGNATURE-----

--=-97ZikbE1HFxS9c3rv5TP--


From brian.e.carpenter@gmail.com  Wed Feb 15 11:36:34 2012
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 10D0921E8032 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 11:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.5
X-Spam-Level: 
X-Spam-Status: No, score=-103.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cr5Jm5qfXWJZ for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 11:36:33 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB4621E8027 for <ietf@ietf.org>; Wed, 15 Feb 2012 11:36:33 -0800 (PST)
Received: by eekc41 with SMTP id c41so508585eek.31 for <ietf@ietf.org>; Wed, 15 Feb 2012 11:36:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jHrWwfN4U/yrmYqI8r4GBD9xsNmfQgqNlxJnbhdEyGE=; b=aycmYcowf847zBH5+O7zwmHPmV8F51oOEVY5XoRGkK8lfrTPd6Qf/2RPGpSbNO+RBT HnrN0V3h34Q7D+WgHvgengBIMnHZv/5JDGQSjJaSqVq9inNqGokZRYXMlDiyu0pN6ily SwYMOvbz4ICHRsyRx4sQ75cD7K95KuCmXidIU=
Received: by 10.213.34.9 with SMTP id j9mr405707ebd.117.1329334591911; Wed, 15 Feb 2012 11:36:31 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id v51sm14352031eef.2.2012.02.15.11.36.29 (version=SSLv3 cipher=OTHER); Wed, 15 Feb 2012 11:36:31 -0800 (PST)
Message-ID: <4F3C0935.9090909@gmail.com>
Date: Thu, 16 Feb 2012 08:36:21 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-garcia-shim6-applicability-03.txt> (Applicability Statement for the Level 3 Multihoming Shim Protocol (Shim6)) to Informational RFC
References: <20120215171232.17722.64289.idtracker@ietfa.amsl.com>
In-Reply-To: <20120215171232.17722.64289.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:36:34 -0000

I'd like to support this draft, having reviewed it carefully. Shim6
is running code whose time will come, and this document is useful
background for implementation and deployment.

Regards
   Brian Carpenter

From jnc@mercury.lcs.mit.edu  Wed Feb 15 11:45:29 2012
Return-Path: <jnc@mercury.lcs.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 E495A21E8083 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 11:45:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.398
X-Spam-Level: 
X-Spam-Status: No, score=-6.398 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3katpb2bMs0H for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 11:45:29 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 173D121E804E for <ietf@ietf.org>; Wed, 15 Feb 2012 11:45:28 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 8E08E18C0CB; Wed, 15 Feb 2012 14:45:28 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Backwards compatibility myth [Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>]
Message-Id: <20120215194528.8E08E18C0CB@mercury.lcs.mit.edu>
Date: Wed, 15 Feb 2012 14:45:28 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:45:30 -0000

    > From: jnc@mercury.lcs.mit.edu (Noel Chiappa)

    > Ironically, TCP/IP had variable length addresses put in _twice_, and
    > they were removed both times!

Sigh, another correction for the record: it was _three_ times!!! Early
versions of IPv4 (IEN-28, confusingly titled "Draft Internetwork Protocol
Specification: Version 2" - it was actually somewhere between 3.1 and 4;
then IEN-41) also had them; they were removed shortly thereafter (IEN-44).

(Excuse me if I'm having a hard time keep track of this; they got put in
and taken out so many times my head is spinning... :-)

	Noel

From wch.ietf@gmail.com  Wed Feb 15 10:57:41 2012
Return-Path: <wch.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 96FF621F8518 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 10:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7rH-KXtMPAAy for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 10:57:41 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 14D9921F848B for <ietf@ietf.org>; Wed, 15 Feb 2012 10:57:41 -0800 (PST)
Received: by yenm3 with SMTP id m3so973229yen.31 for <ietf@ietf.org>; Wed, 15 Feb 2012 10:57:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=WysnG/whY95QTDbmhd1b3dmKGyORVb6hGgQIsGyLk64=; b=czsEE4TWKiWTo0E9XnB6JK2F8L4KhIUkL8EeGKYdspXJ14h5Zh7gpk6UrEi8SSDw2y 4U5p7meHH8ZPf0R41znchth74R+5Q+30kuk9oi6gEjVQtgeQz5orzdkm3J5l5JBhTWYf C2oQUJU3WBZUgYjEN69De63Md+skIlEP4fxPQ=
MIME-Version: 1.0
Received: by 10.101.7.36 with SMTP id k36mr280799ani.58.1329332259941; Wed, 15 Feb 2012 10:57:39 -0800 (PST)
Received: by 10.236.109.20 with HTTP; Wed, 15 Feb 2012 10:57:39 -0800 (PST)
Date: Wed, 15 Feb 2012 12:57:39 -0600
Message-ID: <CABVnFjtrayYGnhv26p2KTAR3UWXsBZBfaaFrSRLDr1MBADTtgA@mail.gmail.com>
Subject: Last Call: draft-weil-shared-transition-space-request-14.txt (IANA Reserved IPv4 Prefix for Shared Address Space)
From: William Hale <wch.ietf@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001636c92c32246c8a04b90549f2
X-Mailman-Approved-At: Wed, 15 Feb 2012 11:54:38 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:57:41 -0000

--001636c92c32246c8a04b90549f2
Content-Type: text/plain; charset=ISO-8859-1

I support this draft as updated.

William Hale

--001636c92c32246c8a04b90549f2
Content-Type: text/html; charset=ISO-8859-1

I support this draft as updated.<br><br>William Hale<br>

--001636c92c32246c8a04b90549f2--

From lea.roberts@stanford.edu  Wed Feb 15 12:02:50 2012
Return-Path: <lea.roberts@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 4862421F8545 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 12:02:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.38
X-Spam-Level: 
X-Spam-Status: No, score=-4.38 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, TVD_SPACE_RATIO=2.219]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KMFlha7EVhQY for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 12:02:49 -0800 (PST)
Received: from smtp.stanford.edu (smtp4.Stanford.EDU [171.67.219.84]) by ietfa.amsl.com (Postfix) with ESMTP id A78AB21F8537 for <ietf@ietf.org>; Wed, 15 Feb 2012 12:02:48 -0800 (PST)
Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 4777E1B1ABD for <ietf@ietf.org>; Wed, 15 Feb 2012 12:02:48 -0800 (PST)
Received: from networking.stanford.edu (networking.Stanford.EDU [171.64.20.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id 1490F1B1AAE for <ietf@ietf.org>; Wed, 15 Feb 2012 12:02:48 -0800 (PST)
Received: from networking.stanford.edu (localhost.localdomain [127.0.0.1]) by networking.stanford.edu (Postfix) with SMTP id D9CDCE7C0D6 for <ietf@ietf.org>; Wed, 15 Feb 2012 12:02:47 -0800 (PST)
Received: by networking.stanford.edu (Postfix, from userid 9759) id B3923E7C0DC; Wed, 15 Feb 2012 12:02:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by networking.stanford.edu (Postfix) with ESMTP id A8EFAE7C0D6 for <ietf@ietf.org>; Wed, 15 Feb 2012 12:02:47 -0800 (PST)
Date: Wed, 15 Feb 2012 12:02:47 -0800 (PST)
From: Lea Roberts <lea.roberts@stanford.edu>
X-X-Sender: rgr@networking.stanford.edu
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt>
In-Reply-To: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
Message-ID: <alpine.DEB.2.00.1202151202170.30224@networking.stanford.edu>
References: <20120130230332.4239.59749.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:02:50 -0000

support



From stephen@sprunk.org  Wed Feb 15 13:11:25 2012
Return-Path: <stephen@sprunk.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 24DF621E8086 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:11:24 -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=[BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuNWnM6tJvFz for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:11:22 -0800 (PST)
Received: from nm21-vm0.access.bullet.mail.mud.yahoo.com (nm21-vm0.access.bullet.mail.mud.yahoo.com [66.94.236.31]) by ietfa.amsl.com (Postfix) with SMTP id 7147921E80AC for <ietf@ietf.org>; Wed, 15 Feb 2012 13:11:21 -0800 (PST)
Received: from [66.94.237.197] by nm21.access.bullet.mail.mud.yahoo.com with NNFMP; 15 Feb 2012 21:11:13 -0000
Received: from [66.94.237.106] by tm8.access.bullet.mail.mud.yahoo.com with NNFMP; 15 Feb 2012 21:11:13 -0000
Received: from [127.0.0.1] by omp1011.access.mail.mud.yahoo.com with NNFMP; 15 Feb 2012 21:11:13 -0000
X-Yahoo-Newman-Id: 903440.11272.bm@omp1011.access.mail.mud.yahoo.com
Received: (qmail 54884 invoked from network); 15 Feb 2012 21:11:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1329340273; bh=CYPmDa8SdyWY/c9qRJc64E52/5vnqVpYpaeSHhXc9fY=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type; b=yz1Vi5PNgUTZqbhFCJXxCBIzXSPbozpH02fDA3Bv9Y3gNsZC+GbGjDYxoIW5as21QloTDJWwMTlFHZZmsZuWOo4DcDpF7JJT0y5A+dHUGdhnSRmy33uF2A31OZGhnYLMrwd/ZvgDqwdpb1sebitD6f1gZaKF8HX5V0kf5aSF1zw=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: wPMQBQYVM1m_6jOvnDmZD8MWNSNs.D_kBc8O9kWNxZy8qJV wYEuNtqYmh9r2L0CoH_kdKA1Imea4kmcM2aEUlbBH5a.aWm2OZCqfnknoKGZ Zben7v.c_675usu1D_UUxosQH0gE27aiSpvYucs3T5P0lBW06iznh2zLJHTC yp5ssHV3TkFEhvtFHgNNsJU2m7TU9f5Qrgp4L11KhVhEBhN1jmkc7eXuSoBs E90hoLiP6N_OHCSLUhAPURrbr.mVTW.mN4w4bPuOdUxh2cMSOG2lsy4iRDzZ wK3tw4g33QhD1pGxL2vfWfW9QRCZZ492aXXZXAhfmUSVhnMmfjWpvCaMUnuP vMs6XtWwAz_or9EVG0H4oVmKYIGJaLCktSAAAqwRgnilHkjavtzie3q_gNpg 8pg--
X-Yahoo-SMTP: EYvcGKyswBB8plhV5pc8yMz3blwA5zta_j4l
Received: from [192.168.1.67] (stephen@99.136.83.110 with plain) by smtp103.sbc.mail.mud.yahoo.com with SMTP; 15 Feb 2012 13:11:13 -0800 PST
Message-ID: <4F3C1F31.6010209@sprunk.org>
Date: Wed, 15 Feb 2012 15:10:09 -0600
From: Stephen Sprunk <stephen@sprunk.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:7.0) Gecko/20110929 Thunderbird/7.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net>
In-Reply-To: <4F3BC464.50300@dcrocker.net>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040905050807080509060700"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:11:25 -0000

This is a cryptographically signed message in MIME format.

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

On 15-Feb-12 08:42, Dave CROCKER wrote:
> As I recall, there was essentially no experience with variable length
> addresses -- and certainly no production experience -- then or even by
> the early 90s, when essentially the same decision was made and for
> essentially the same reason.[1]
>
> It's not that variable length addressing is a bad idea; it's that it
> didn't get the research work and specification detail it needed, for
> introduction into what had become critical infrastructure.  What I
> recall during the IPng discussions of the early 90s was promotion of
> the /concept/ of variable length addressing but without the
> experiential base to provide assurance we knew how it would operate.

The problem with variable-length addressing that, in practice, one needs
to specify a maximum length.  The result, therefore, is that you don't
have variable-length addresses at all but rather fixed-length addresses
with a shorthand encoding for unused bits.

S

--=20
Stephen Sprunk         "God does not play dice."  --Albert Einstein
CCIE #3723         "God is an inveterate gambler, and He throws the
K5SSS        dice at every possible opportunity." --Stephen Hawking



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFNjCC
BTIwggMaoAMCAQICAwrjmDANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmlu
ZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0xMTEw
MjkxOTQ0MzRaFw0xMjA0MjYxOTQ0MzRaMD0xGDAWBgNVBAMTD0NBY2VydCBXb1QgVXNlcjEh
MB8GCSqGSIb3DQEJARYSc3RlcGhlbkBzcHJ1bmsub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA1qAUmWE5Nv/9HFl7f52VrEoGqhbYG1rPE7go13pSxgUBi02iDNKyDTJH
b/CswpO/FE9p34QbUlnOXY3LRrLh+/NaS496breDA8mRKCceNHIPaiK3Mwpl0q787WQalrp9
mBV2jKHobOMOWbtNiuYSq6k4qfqIvFJvGOsgizcqeMjjLyR8GimjGCQYuH2o970PhlNidpAj
mVMCBehc3RhjmevEn4ydIL7j0bmFj9YuLxaoISq6icdh7VFxqAzdEbHhQHKp1N8aNq5yhcWD
M//Bq8MpMd1+zNse/pVc7/42G5iArYkImUbu/P48PgR8ZX9D59hJxP7kRyKVT9dbTNkh4wID
AQABo4H+MIH7MAwGA1UdEwEB/wQCMAAwVgYJYIZIAYb4QgENBEkWR1RvIGdldCB5b3VyIG93
biBjZXJ0aWZpY2F0ZSBmb3IgRlJFRSBoZWFkIG92ZXIgdG8gaHR0cDovL3d3dy5DQWNlcnQu
b3JnMEAGA1UdJQQ5MDcGCCsGAQUFBwMEBggrBgEFBQcDAgYKKwYBBAGCNwoDBAYKKwYBBAGC
NwoDAwYJYIZIAYb4QgQBMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcwAYYWaHR0cDovL29j
c3AuY2FjZXJ0Lm9yZzAdBgNVHREEFjAUgRJzdGVwaGVuQHNwcnVuay5vcmcwDQYJKoZIhvcN
AQEFBQADggIBAHPCEzZYLQv9nbi+t3K2rPQdv6FVfH5UwC+dDdd3y/fng5/SJqqloAcF9z2j
72m5V3s/ZNryPnnrvBRa6nffbw3zam+uHLwPXseMlaRRG2QDfLH4TIqA8jskOYcGh17cbCZD
BC867EmxUMxAUEZpebomJcWRXnvYo9b5MnJIx8i/tbmuwWd2LAK0tzmZwbEnH6RtFloLwgSh
JO9AelRuw9Llw0gwXKnAG1wssncEXu54Rw1O6Dor8kRAXC5pnGocdw3ltTypB7+28dKXWguh
LOuXpf5H3IIL5EIoWu4NGhiOJNqu1ZksZIWAMPjbv7VKBQvJVvI2J5FGIgl96zu4vb2rlRso
BCaA1KiLXYxpgs9zsqFr+zeLLOITD+PB69c1EFzC+9DflZO+kkVGUeg+SuYbosoZQowrw7pc
4rZ1d86KiIfl7NTew7BCrRMqMhBbnprgLRjxilcSL8YyyN3y9fcNDQb4Fd+6hWC8BBMbZ/OR
IcKwk5aW75CjZKvILoxjQ+BKE7HxwbG3wQ6p+hDwov+PlN7qd08to4w31sBbLkeGHW20Ihkg
NG0dQkA7UwapW6hUzoIaoGGP3C1pWSB511pbxBWkyHAatX50Ebp1s1sC4yttVwnRF5wsyVhA
NkefOMh3/yPexf4+VMY7R0O7sVsyG6BrSKv6Bqe+Att38RieMYIDlDCCA5ACAQEwgYAweTEQ
MA4GA1UEChMHUm9vdCBDQTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYD
VQQDExlDQSBDZXJ0IFNpZ25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0
QGNhY2VydC5vcmcCAwrjmDAJBgUrDgMCGgUAoIIB6DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN
AQcBMBwGCSqGSIb3DQEJBTEPFw0xMjAyMTUyMTEwMDlaMCMGCSqGSIb3DQEJBDEWBBS/KIUh
CwDwSAshyG69/+xOvAKd8jBfBgkqhkiG9w0BCQ8xUjBQMAsGCWCGSAFlAwQBAjAKBggqhkiG
9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcN
AwICASgwgZEGCSsGAQQBgjcQBDGBgzCBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRo
b3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDCuOYMIGTBgsqhkiG
9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3
LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkq
hkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDCuOYMA0GCSqGSIb3DQEBAQUABIIBADTL
UV/4iVb3eY5qNv3w2gdUM6zA5pJ/fbkqLXAKIVrxQYuUEfGVWMWLhJfADZURd0RCy3kzmcp9
0nImwCCyiEEGHy0lJquQQVx+z2o+lUdwr1k9naVmFJG/hYSWLr0EBsgxqeqohsaP+sAC+k0v
aobwkn3y9Di7NKInadCNv1q4xpyfRAxYI3id88Woa3LDLhEMELgy9VtFzKHWlMLK11ebkrrf
gpH+ZL/biF3StWx4n+Zj6ORdR3KCHunOk1HDgPLDqgAfk3sLOIQKY1lBxEUBtIKlv+ZsWgce
1QjeoSj0RTKgWQknVfwlsd5w1on/UOmFS3KJep3XN7t/N9yPQEUAAAAAAAA=
--------------ms040905050807080509060700--

From narten@us.ibm.com  Wed Feb 15 13:32:02 2012
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 62A6921E80A1 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.325
X-Spam-Level: 
X-Spam-Status: No, score=-109.325 tagged_above=-999 required=5 tests=[AWL=1.274, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BM0KpZJ3s+A4 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:32:01 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id AED5821E8027 for <ietf@ietf.org>; Wed, 15 Feb 2012 13:32:01 -0800 (PST)
Received: from /spool/local 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>; Wed, 15 Feb 2012 14:32:01 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 15 Feb 2012 14:31:59 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 939E619D8053; Wed, 15 Feb 2012 14:31:53 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q1FLVm6D064496; Wed, 15 Feb 2012 14:31:49 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q1FLVlAS018181; Wed, 15 Feb 2012 14:31:48 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-205-222.mts.ibm.com [9.65.205.222]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q1FLVkXP018012 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Feb 2012 14:31:47 -0700
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q1FLVB9E028114; Wed, 15 Feb 2012 16:31:11 -0500
Message-Id: <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com>
To: iesg@ietf.org
Subject: Re: WG Review: Recharter of Locator/ID Separation Protocol (lisp) 
In-reply-to: <20120214222316.CF29521E800E@ietfa.amsl.com>
References: <20120214222316.CF29521E800E@ietfa.amsl.com>
Comments: In-reply-to IESG Secretary <iesg-secretary@ietf.org> message dated "Tue, 14 Feb 2012 14:23:16 -0800."
Date: Wed, 15 Feb 2012 16:31:11 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12021521-3270-0000-0000-0000040D58FB
Cc: ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:32:02 -0000

A WG Review message for this WG already went out a month ago.

What has changed to necessitate another Last Call?

Could the-powers-that-be please make it easier for those who might
care to understand if there is something here that we should know and
possibly comment about?

A simple explanation, or a pointer to diffs, etc. would do the job
nicely.

Thomas


From dhc@dcrocker.net  Wed Feb 15 13:36:07 2012
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 412E221F84D3 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:36:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level: 
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvWs9PUOxAnF for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:36:03 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B12D21F8462 for <ietf@ietf.org>; Wed, 15 Feb 2012 13:36:03 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1FLZvTG007463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 15 Feb 2012 13:36:02 -0800
Message-ID: <4F3C253C.5010208@dcrocker.net>
Date: Wed, 15 Feb 2012 13:35:56 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org>
In-Reply-To: <4F3C1F31.6010209@sprunk.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 15 Feb 2012 13:36:02 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:36:07 -0000

On 2/15/2012 1:10 PM, Stephen Sprunk wrote:
> The problem with variable-length addressing that, in practice, one needs
> to specify a maximum length.

In some practical terms, perhaps, but there are extensibility schemes that allow 
the payload (addressing bits, in this case, to go on forever, in theoretical terms.


 > The result, therefore, is that you don't
> have variable-length addresses at all but rather fixed-length addresses
> with a shorthand encoding for unused bits.

For most variable-length schemes, yes, but not all.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From steve@shinkuro.com  Wed Feb 15 13:39:27 2012
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D404221F8545 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[AWL=0.349,  BAYES_00=-2.599, HELO_EQ_DSL=1.129]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ec3xgV4PBhN1 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:39:22 -0800 (PST)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 7749221F853D for <ietf@ietf.org>; Wed, 15 Feb 2012 13:39:22 -0800 (PST)
Received: from [69.143.222.58] (HELO [10.0.1.5]) by execdsl.com (CommuniGate Pro SMTP 5.1.16) with ESMTPS id 20272353; Wed, 15 Feb 2012 21:39:59 +0000
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <4F3C1F31.6010209@sprunk.org>
Date: Wed, 15 Feb 2012 16:39:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <00203589-3310-4A59-80A3-CC2D237D4427@shinkuro.com>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org>
To: Stephen Sprunk <stephen@sprunk.org>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:39:28 -0000

This is essentially correct.  The apparent conceptual difference is that =
a variable length address looks more like source routing.  The end =
system owns only a small part of the total address; the rest is the =
network portion, fashioned to seem like a source route.  Depending on =
how the address is interpreted, the division of the network portion into =
routing steps will be specified in advance or will be interpreted at =
each step.  The latter alllows gradual evolution of the network by =
consolidating small switches into larger ones.

The transition to CIDR within IPv4 accomplished pretty much the same =
thing and had the same benefits.  Nonetheless, 32 bits just isn't =
enough.  The only way variable length address would have provided a =
smooth transition is if there had been room to increase the length of =
the address after some years of use.  Well, if we had left room in the =
address field for more than 32 bits, we'd have had the same advantage.  =
But we didn't.

Steve

On Feb 15, 2012, at 4:10 PM, Stephen Sprunk wrote:

> On 15-Feb-12 08:42, Dave CROCKER wrote:
>> As I recall, there was essentially no experience with variable length
>> addresses -- and certainly no production experience -- then or even =
by
>> the early 90s, when essentially the same decision was made and for
>> essentially the same reason.[1]
>>=20
>> It's not that variable length addressing is a bad idea; it's that it
>> didn't get the research work and specification detail it needed, for
>> introduction into what had become critical infrastructure.  What I
>> recall during the IPng discussions of the early 90s was promotion of
>> the /concept/ of variable length addressing but without the
>> experiential base to provide assurance we knew how it would operate.
>=20
> The problem with variable-length addressing that, in practice, one =
needs
> to specify a maximum length.  The result, therefore, is that you don't
> have variable-length addresses at all but rather fixed-length =
addresses
> with a shorthand encoding for unused bits.
>=20
> S
>=20
> --=20
> Stephen Sprunk         "God does not play dice."  --Albert Einstein
> CCIE #3723         "God is an inveterate gambler, and He throws the
> K5SSS        dice at every possible opportunity." --Stephen Hawking
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rbarnes@bbn.com  Wed Feb 15 13:39:33 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01A1F21E80BF for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.505
X-Spam-Level: 
X-Spam-Status: No, score=-106.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1m+JF0JqjPPA for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:39:28 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8B35521F853D for <ietf@ietf.org>; Wed, 15 Feb 2012 13:39:28 -0800 (PST)
Received: from [128.89.255.14] (port=51032) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1RxmZS-0002GP-FL; Wed, 15 Feb 2012 16:39:26 -0500
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <4F3C253C.5010208@dcrocker.net>
Date: Wed, 15 Feb 2012 16:39:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEA18A00-6ACE-40E0-B598-D2417684648C@bbn.com>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org> <4F3C253C.5010208@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1251.1)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:39:33 -0000

>> The problem with variable-length addressing that, in practice, one =
needs
>> to specify a maximum length.
>=20
> In some practical terms, perhaps, but there are extensibility schemes =
that allow the payload (addressing bits, in this case, to go on forever, =
in theoretical terms.

I look forward to your design for a forwarding plane based on streaming =
addresses :)

Does anyone really think that we'll need more than 128 bits?

--Richard



> > The result, therefore, is that you don't
>> have variable-length addresses at all but rather fixed-length =
addresses
>> with a shorthand encoding for unused bits.
>=20
> For most variable-length schemes, yes, but not all.
>=20
> d/
>=20
> --=20
>=20
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From wbeebee@cisco.com  Wed Feb 15 13:41:58 2012
Return-Path: <wbeebee@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 6F55F21E80C7 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:41:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level: 
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxy6pBm+VaCZ for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:41:54 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 747B921E80B9 for <ietf@ietf.org>; Wed, 15 Feb 2012 13:41:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wbeebee@cisco.com; l=353; q=dns/txt; s=iport; t=1329342114; x=1330551714; h=date:subject:from:to:message-id:in-reply-to:mime-version: content-transfer-encoding; bh=5MzmdZNbsgtvPMLYHv6xCbleaUU95E6+gJv0UOTT+SE=; b=Mqy/+3Oh5vxFuZDaJ89iVCHq8c8ZYw6SjE3Ix4MVEmtp0RhEVo2wC4/b AuGQ1djWJOve6QEfpohbfsNc9+vdMoR40CrVxwVs/xSwWDHstqYYJ3Xlp 3TJF0oLj3pdrSLfjx/D7vd6CJP2g3vLx/fO2osCm8H2geEHDoPe6bRbPd E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnEJAKIlPE+tJV2c/2dsb2JhbABDiVmnCgKBB4FyAQEBAwESAScCAU4BCIEdAQEEATSHXZsNAZ5Vi3I8AQIpCQEIBQECAQKDVgGDbASITYxpjkeEPw
X-IronPort-AV: E=Sophos;i="4.73,425,1325462400"; d="scan'208";a="59273340"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 15 Feb 2012 21:41:54 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id q1FLfse9017989;  Wed, 15 Feb 2012 21:41:54 GMT
Received: from xmb-rcd-201.cisco.com ([72.163.62.208]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 15 Feb 2012 15:41:53 -0600
Received: from 161.44.175.128 ([161.44.175.128]) by XMB-RCD-201.cisco.com ([72.163.62.208]) with Microsoft Exchange Server HTTP-DAV ;  Wed, 15 Feb 2012 21:41:53 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Wed, 15 Feb 2012 16:41:52 -0500
Subject: Re: Variable length internet addresses in TCP/IP: history
From: Wes Beebee <wbeebee@cisco.com>
To: <dcrocker@bbiw.net>, <ietf@ietf.org>
Message-ID: <CB6190D0.1A74BC%wbeebee@cisco.com>
Thread-Topic: Variable length internet addresses in TCP/IP: history
Thread-Index: AczsKqDzT6hGjy0TeEGQYDjHii2+IA==
In-Reply-To: <4F3C253C.5010208@dcrocker.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 15 Feb 2012 21:41:53.0632 (UTC) FILETIME=[A1EC9600:01CCEC2A]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:41:58 -0000

>> The problem with variable-length addressing that, in practice, one needs
>> to specify a maximum length.
> 
> In some practical terms, perhaps, but there are extensibility schemes that
> allow 
> the payload (addressing bits, in this case, to go on forever, in theoretical
> terms.

One example would be a linked-list of strides...

- Wes


From dhc@dcrocker.net  Wed Feb 15 13:47:01 2012
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 23D0021E80C3 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level: 
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4e+OtzhKbZv for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 13:46:56 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 911C321E803D for <ietf@ietf.org>; Wed, 15 Feb 2012 13:46:56 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1FLklWW007677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Feb 2012 13:46:52 -0800
Message-ID: <4F3C27C6.5050409@dcrocker.net>
Date: Wed, 15 Feb 2012 13:46:46 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org> <4F3C253C.5010208@dcrocker.net> <DEA18A00-6ACE-40E0-B598-D2417684648C@bbn.com>
In-Reply-To: <DEA18A00-6ACE-40E0-B598-D2417684648C@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 15 Feb 2012 13:46:52 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:47:01 -0000

On 2/15/2012 1:39 PM, Richard Barnes wrote:
>>> The problem with variable-length addressing that, in practice, one needs
>>> to specify a maximum length.
>>
>> In some practical terms, perhaps, but there are extensibility schemes that allow the payload (addressing bits, in this case, to go on forever, in theoretical terms.
>
> I look forward to your design for a forwarding plane based on streaming addresses :)
>
> Does anyone really think that we'll need more than 128 bits?


You might have missed my opening qualification by refererring to practical terms 
as an actual limit?

I was responding to a comment about design limitations; I wasn't recommending 
infinite-length addressing.

I wasn't being as theoretical as one might assume.  Although I had no direct 
hands-on, some of the folks on this list did:

 
<http://en.wikipedia.org/wiki/Word_%28computer_architecture%29#Variable_word_architectures


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jnc@mercury.lcs.mit.edu  Wed Feb 15 14:14:08 2012
Return-Path: <jnc@mercury.lcs.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 D5C4121E80AD for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 14:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.408
X-Spam-Level: 
X-Spam-Status: No, score=-6.408 tagged_above=-999 required=5 tests=[AWL=0.191,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R8Hz99P5eHbK for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 14:14:08 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2537D21E8032 for <ietf@ietf.org>; Wed, 15 Feb 2012 14:14:07 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 87B8B18C0A9; Wed, 15 Feb 2012 17:14:07 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
Message-Id: <20120215221407.87B8B18C0A9@mercury.lcs.mit.edu>
Date: Wed, 15 Feb 2012 17:14:07 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:14:09 -0000

    > From: Steve Crocker <steve@shinkuro.com>

    > a variable length address looks more like source routing.
    > ...
    > the network portion, fashioned to seem like a source route.
    > ... the division of the network portion into routing steps will be
    > specified in advance or will be interpreted at each step.

This is sort of tangential, and I apologize for that, but...

I hear this assertion (that hierarchical addresses are effectively a
source route) a fair amount, and I'd like to push back on it, because I
think it's somewhat misleading, and confuses beginners more than it helps
them.

The thing is that at each level, a hierarchical address is _very limited_ in
what it can pick as the 'next hop' of the 'source route': it cannot go
sideways in the hierarchy (e.g. from A.p to A.q), and it cannot go up
(e.g. from A.p to B). It can only select one of the 'next layer down'
elements: i.e. from A.p, it can only select one of A.p.1 ... A.p.{n}.

It may seem in some ways a bit like a route, but it's really not (and,
like I said, I have seen beginners get terribly confused in trying to fit
it into that paradigm).

	Noel

From smb@cs.columbia.edu  Wed Feb 15 14:30:02 2012
Return-Path: <smb@cs.columbia.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 53C3421F86DF for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 14:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.549
X-Spam-Level: 
X-Spam-Status: No, score=-5.549 tagged_above=-999 required=5 tests=[AWL=1.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id In09+zbtGLQ3 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 14:29:58 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by ietfa.amsl.com (Postfix) with ESMTP id D151821F86DA for <ietf@ietf.org>; Wed, 15 Feb 2012 14:29:57 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q1FMTtq1001689 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2012 17:29:55 -0500 (EST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu>
Date: Wed, 15 Feb 2012 17:29:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu>
To: "Bradner, Scott" <sob@harvard.edu>
X-Mailer: Apple Mail (2.1257)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:30:02 -0000

Scott, if memory serves you and I wanted the high-order 2 bits of the =
IPng
address to select between 64, 128, 192, and 256-bit addresses -- and =
when
we couldn't get that we got folks to agree on 128-bit addresses instead =
of
64-bit, which is what had been on the table.

On Feb 14, 2012, at 1:37 39PM, Bradner, Scott wrote:

> in the case of IPng, the router people wanted variable length but the =
host people (or at least some of them) did not
>=20
> Scott
>=20
> Scott O Bradner
> Senior Technology Consultant
>=20
> Harvard University Information Technology
> Innovation & Architecture
> (P) +1 (617) 495 3864
> 29 Oxford St. Rm 407
> Cambridge, MA 02138
>=20
>=20
>=20
> On Feb 14, 2012, at 1:34 PM, Steve Crocker wrote:
>=20
>> The word alignment issue was very strong and the router people had =
considerably more influence than the host folks.  I tried to propose =
variable length addressing using four bit nibbles in August 1974 and I =
got no traction at all.
>>=20
>> Steve
>>=20
>> Sent from my iPhone
>>=20
>> On Feb 14, 2012, at 6:31 PM, Bob Braden <braden@isi.edu> wrote:
>>=20
>>> On 2/13/2012 7:53 PM, Noel Chiappa wrote:
>>>>> From: Brian E Carpenter<brian.e.carpenter@gmail.com>
>>>>=20
>>>>> The design error was made in the late 1970s, when Louis Pouzin's =
advice
>>>>> that catenet addresses should be variable length, with a format =
prefix,
>>>>> was not taken during the design of IPv4.
>>>>=20
>>>> Ironically, TCP/IP had variable length addresses put in _twice_, =
and they were
>>>> removed both times! (You can't make this stuff up! :-)
>>> Noel,
>>>=20
>>> You probably remember this, but...
>>>=20
>>> Within the ARPA-funded Internet research program that designed IP =
and TCP, Jon Postel and
>>> Danny Cohen argued strenuously for variable length addresses. (This =
must have been
>>> around 1979. I cannot name most of the other 10 people in the room, =
but I have
>>> a clear mental picture of Jon, in the back of the room, fuming over =
this issue. Jon believed
>>> intensely in protocol extensibility.)
>>>=20
>>> However, Vint Cerf, the ARPA program manager, rules against variable =
length addresses and
>>> decreed the fixed length 32 bit word-aligned addresses of RFC 791. =
His argument was that
>>> TCP/IP had to be simple to implement if it were to succeed (and =
survive the juggernaut
>>> of the ISO OSI protocol suite).
>>>=20
>>> System programmers of that day were familiar with word-aligned data
>>> structures with fixed offsets, and variable length addresses seemed =
to be (and in fact
>>> would be) harder to program and would make packet dumps harder to =
interpret.
>>>=20
>>> It was a political as much as a technical judgment, and Vint may =
have been right ... we
>>> can never know. We do know that IP eventually succeeded and OSI =
failed, but it
>>> was a near thing for awhile. Of course, there were other factors in =
the success
>>> of IP, such as Berkeley Unix.
>>>=20
>>> It is to be noted that when it came time to define IPv6 some 20 =
years later, the IETF
>>> stuck with fixed length internet addresses.
>>>=20
>>> Bob Braden
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From rcallon@juniper.net  Wed Feb 15 14:45:32 2012
Return-Path: <rcallon@juniper.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 61D1021E80DA for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 14:45:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bIQHM1XXHcuX for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 14:45:31 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id AB21821E80DD for <ietf@ietf.org>; Wed, 15 Feb 2012 14:45:23 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTzw1g0F5iO/+89gE6AYxLFzbboCZhmio@postini.com; Wed, 15 Feb 2012 14:45:31 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 15 Feb 2012 14:44:55 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Wed, 15 Feb 2012 17:44:54 -0500
From: Ross Callon <rcallon@juniper.net>
To: Stephen Sprunk <stephen@sprunk.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 15 Feb 2012 17:44:53 -0500
Subject: RE: Variable length internet addresses in TCP/IP: history
Thread-Topic: Variable length internet addresses in TCP/IP: history
Thread-Index: AczsJndqsTL5SSlPSJOpBZxSEJDYDQAC2Xqg
Message-ID: <DF7F294AF4153D498141CBEFADB17704C70B451054@EMBX01-WF.jnpr.net>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org>
In-Reply-To: <4F3C1F31.6010209@sprunk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: f8e27f27-03b2-4c3e-9447-119194e72cb6
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:45:32 -0000

QnV0IHRoZSBtYXhpbXVtIGZvciBpbXBsZW1lbnRhdGlvbiBpcyBub3QgbmVjZXNzYXJpbHkgdGhl
IG1heGltdW0gZm9yIHRoZSBwYWNrZXQgZm9ybWF0LiANCg0KVGh1cyBvbmUgY291bGQgaGF2ZSBz
dGFydGVkIHdpdGggYSB2YXJpYWJsZSBsZW5ndGggYWRkcmVzcyBmb3JtYXQsIGJ1dCBzYWlkICJG
b3IgdGhlIGltbWVkaWF0ZSBmdXR1cmUgd2Ugd2lsbCBhbHdheXMgcGljayBhIGxlbmd0aCBvZiAz
MiBiaXRzIi4gVGhlbiBhdCBzb21lIHBvaW50IHdlIGNvdWxkIGhhdmUgc2FpZCAiaW4gNSB5ZWFy
cyB3ZSBhcmUgZ29pbmcgdG8gc3RhcnQgYXNzaWduaW5nIDY0IGJpdCBhZGRyZXNzZXMsIHlvdSBN
VVNUIHVwZGF0ZSB5b3VyIGltcGxlbWVudGF0aW9ucyB0byBzdXBwb3J0IHRoaXMgYXMgd2VsbCAt
LSBzYW1lIHBhY2tldCBmb3JtYXQgYW5kIGV2ZXJ5dGhpbmcgZWxzZSBzdGF5cyB0aGUgc2FtZSIu
IA0KDQpXZSB3b3VsZCBoYXZlIG5lZWRlZCB0byBiZSB2ZXJ5IGNhcmVmdWwgdG8gZW5zdXJlIHRo
YXQgdGhlIHBhY2tldCBmb3JtYXRzIGFsbG93aW5nIHZhcmlhYmxlIGxlbmd0aHMgYXBwbGllZCB0
byBhbGwgcHJvdG9jb2xzIHRoYXQgY2Fycnkgb3IgdXNlIElQIGFkZHJlc3NlcyAoc3VjaCBhcyBE
TlMgcmVjb3JkcywgLi4uKS4gU3VjaCBhcmNoaXRlY3R1cmFsIGNhcmUgaXMgbm90IGVhc3kgdG8g
ZW5mb3JjZS4gDQoNCldoZXRoZXIgZXZlcnlvbmUgYWN0dWFsbHkgd291bGQgaGF2ZSB1cGRhdGVk
IHRoZWlyIGltcGxlbWVudGF0aW9ucyBpcyBhbm90aGVyIGlzc3VlIC0tIGJ1dCBhdCBsZWFzdCBp
biB0aGVvcnkgaXQgKm1pZ2h0KiBoYXZlIGJlZW4gc2ltcGxlciB0aGFuIHVwZ3JhZGluZyB0byBh
IG5ldyB2ZXJzaW9uIG9mIElQLiANCg0KT2YgY291cnNlLCBzaW5jZSB3ZSBkb24ndCBoYXZlIHRp
bWUgbWFjaGluZXMsIGl0IGlzIHRvbyBsYXRlIHRvIGNoYW5nZSBvdXIgcGFzdCAoYW5kIHdlIHdp
bGwgbm90ZSB0aGF0IG90aGVyIHR5cGVzIG9mIG5ldHdvcmtzIGhhdmUgcnVuIG91dCBvZiBhZGRy
ZXNzZXMgLyBkaWdpdHMgLyBhcmVhIGNvZGVzICBhbHNvKS4gDQoNClJvc3MNCg0KLS0tLS1Pcmln
aW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFN0ZXBoZW4gU3BydW5rDQpTZW50OiBX
ZWRuZXNkYXksIEZlYnJ1YXJ5IDE1LCAyMDEyIDQ6MTAgUE0NClRvOiBpZXRmQGlldGYub3JnDQpT
dWJqZWN0OiBSZTogVmFyaWFibGUgbGVuZ3RoIGludGVybmV0IGFkZHJlc3NlcyBpbiBUQ1AvSVA6
IGhpc3RvcnkNCg0KT24gMTUtRmViLTEyIDA4OjQyLCBEYXZlIENST0NLRVIgd3JvdGU6DQo+IEFz
IEkgcmVjYWxsLCB0aGVyZSB3YXMgZXNzZW50aWFsbHkgbm8gZXhwZXJpZW5jZSB3aXRoIHZhcmlh
YmxlIGxlbmd0aA0KPiBhZGRyZXNzZXMgLS0gYW5kIGNlcnRhaW5seSBubyBwcm9kdWN0aW9uIGV4
cGVyaWVuY2UgLS0gdGhlbiBvciBldmVuIGJ5DQo+IHRoZSBlYXJseSA5MHMsIHdoZW4gZXNzZW50
aWFsbHkgdGhlIHNhbWUgZGVjaXNpb24gd2FzIG1hZGUgYW5kIGZvcg0KPiBlc3NlbnRpYWxseSB0
aGUgc2FtZSByZWFzb24uWzFdDQo+DQo+IEl0J3Mgbm90IHRoYXQgdmFyaWFibGUgbGVuZ3RoIGFk
ZHJlc3NpbmcgaXMgYSBiYWQgaWRlYTsgaXQncyB0aGF0IGl0DQo+IGRpZG4ndCBnZXQgdGhlIHJl
c2VhcmNoIHdvcmsgYW5kIHNwZWNpZmljYXRpb24gZGV0YWlsIGl0IG5lZWRlZCwgZm9yDQo+IGlu
dHJvZHVjdGlvbiBpbnRvIHdoYXQgaGFkIGJlY29tZSBjcml0aWNhbCBpbmZyYXN0cnVjdHVyZS4g
IFdoYXQgSQ0KPiByZWNhbGwgZHVyaW5nIHRoZSBJUG5nIGRpc2N1c3Npb25zIG9mIHRoZSBlYXJs
eSA5MHMgd2FzIHByb21vdGlvbiBvZg0KPiB0aGUgL2NvbmNlcHQvIG9mIHZhcmlhYmxlIGxlbmd0
aCBhZGRyZXNzaW5nIGJ1dCB3aXRob3V0IHRoZQ0KPiBleHBlcmllbnRpYWwgYmFzZSB0byBwcm92
aWRlIGFzc3VyYW5jZSB3ZSBrbmV3IGhvdyBpdCB3b3VsZCBvcGVyYXRlLg0KDQpUaGUgcHJvYmxl
bSB3aXRoIHZhcmlhYmxlLWxlbmd0aCBhZGRyZXNzaW5nIHRoYXQsIGluIHByYWN0aWNlLCBvbmUg
bmVlZHMNCnRvIHNwZWNpZnkgYSBtYXhpbXVtIGxlbmd0aC4gIFRoZSByZXN1bHQsIHRoZXJlZm9y
ZSwgaXMgdGhhdCB5b3UgZG9uJ3QNCmhhdmUgdmFyaWFibGUtbGVuZ3RoIGFkZHJlc3NlcyBhdCBh
bGwgYnV0IHJhdGhlciBmaXhlZC1sZW5ndGggYWRkcmVzc2VzDQp3aXRoIGEgc2hvcnRoYW5kIGVu
Y29kaW5nIGZvciB1bnVzZWQgYml0cy4NCg0KUw0KDQotLSANClN0ZXBoZW4gU3BydW5rICAgICAg
ICAgIkdvZCBkb2VzIG5vdCBwbGF5IGRpY2UuIiAgLS1BbGJlcnQgRWluc3RlaW4NCkNDSUUgIzM3
MjMgICAgICAgICAiR29kIGlzIGFuIGludmV0ZXJhdGUgZ2FtYmxlciwgYW5kIEhlIHRocm93cyB0
aGUNCks1U1NTICAgICAgICBkaWNlIGF0IGV2ZXJ5IHBvc3NpYmxlIG9wcG9ydHVuaXR5LiIgLS1T
dGVwaGVuIEhhd2tpbmcNCg0KDQo=

From smb@cs.columbia.edu  Wed Feb 15 15:40:49 2012
Return-Path: <smb@cs.columbia.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 C836F21F862F for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 15:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.637
X-Spam-Level: 
X-Spam-Status: No, score=-5.637 tagged_above=-999 required=5 tests=[AWL=0.962,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMDSGzNTm5EY for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 15:40:45 -0800 (PST)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id F05C221F862D for <ietf@ietf.org>; Wed, 15 Feb 2012 15:40:44 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q1FNehT4022701 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2012 18:40:43 -0500 (EST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <DF7F294AF4153D498141CBEFADB17704C70B451054@EMBX01-WF.jnpr.net>
Date: Wed, 15 Feb 2012 18:40:43 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3070E143-CB5B-48CE-A2A0-78C0D3C780EB@cs.columbia.edu>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org> <DF7F294AF4153D498141CBEFADB17704C70B451054@EMBX01-WF.jnpr.net>
To: Ross Callon <rcallon@juniper.net>
X-Mailer: Apple Mail (2.1257)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: Stephen Sprunk <stephen@sprunk.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:40:50 -0000

On Feb 15, 2012, at 5:44 53PM, Ross Callon wrote:

> But the maximum for implementation is not necessarily the maximum for =
the packet format.=20
>=20
> Thus one could have started with a variable length address format, but =
said "For the immediate future we will always pick a length of 32 bits". =
Then at some point we could have said "in 5 years we are going to start =
assigning 64 bit addresses, you MUST update your implementations to =
support this as well -- same packet format and everything else stays the =
same".=20
>=20
> We would have needed to be very careful to ensure that the packet =
formats allowing variable lengths applied to all protocols that carry or =
use IP addresses (such as DNS records, ...). Such architectural care is =
not easy to enforce.=20
>=20
> Whether everyone actually would have updated their implementations is =
another issue -- but at least in theory it *might* have been simpler =
than upgrading to a new version of IP.=20

One argument against the 64/128/192/256 proposal was that untested code =
paths would be buggy.  Very true -- which is why we should have done =
things like use 192-bit addresses for loopback, 256 for multicast, 128 =
for root servers, etc.
>=20
> Of course, since we don't have time machines, it is too late to change =
our past (and we will note that other types of networks have run out of =
addresses / digits / area codes  also).=20


Fred Brooks has noted (in the context of computer address spaces) that =
every successful architecture has eventually run out of bits.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From mohta@necom830.hpcl.titech.ac.jp  Wed Feb 15 16:41:20 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB641F0C4A for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 16:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.072
X-Spam-Level: 
X-Spam-Status: No, score=-0.072 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mA23xx-O3k61 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 16:41:19 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 051681F0C46 for <ietf@ietf.org>; Wed, 15 Feb 2012 16:41:18 -0800 (PST)
Received: (qmail 81261 invoked from network); 16 Feb 2012 00:56:36 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 16 Feb 2012 00:56:36 -0000
Message-ID: <4F3C507E.7050408@necom830.hpcl.titech.ac.jp>
Date: Thu, 16 Feb 2012 09:40:30 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <4F3BC464.50300@dcrocker.net> <4F3C1F31.6010209@sprunk.org> <00203589-3310-4A59-80A3-CC2D237D4427@shinkuro.com>
In-Reply-To: <00203589-3310-4A59-80A3-CC2D237D4427@shinkuro.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:41:20 -0000

Steve Crocker wrote:

> The only way variable length address would have provided a
> smooth transition is if there had been room to increase the
> length of the address after some years of use.

Bottom up approach to extend address length toward port numbers,
thus, worked, is working and will keep working with or without
NAT.

If necessary, we can have new TCP, UDP and other transport
protocols with 32 or 48 bit long port numbers without changing
core routers, though it requires minor modifications to transport
and application code.

Anyway the current 48 bit space of IPv4 addresses and 16 bit port
numbers will be suffice for a decade or two.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Wed Feb 15 16:44:10 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD4921E800E for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 16:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.073
X-Spam-Level: 
X-Spam-Status: No, score=-0.073 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbiM9emGpnV7 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 16:44:09 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 539F221F8532 for <ietf@ietf.org>; Wed, 15 Feb 2012 16:44:09 -0800 (PST)
Received: (qmail 81279 invoked from network); 16 Feb 2012 00:59:37 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 16 Feb 2012 00:59:37 -0000
Message-ID: <4F3C5132.9050905@necom830.hpcl.titech.ac.jp>
Date: Thu, 16 Feb 2012 09:43:30 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu>
In-Reply-To: <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:44:10 -0000

Steven Bellovin wrote:

> Scott, if memory serves you and I wanted the high-order 2 bits of the IPng
> address to select between 64, 128, 192, and 256-bit addresses -- and when
> we couldn't get that we got folks to agree on 128-bit addresses instead of
> 64-bit, which is what had been on the table.

Thus, IPv6 was mortally wounded from the beginning.

					Masataka Ohta

From smb@cs.columbia.edu  Wed Feb 15 19:58:20 2012
Return-Path: <smb@cs.columbia.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 8B29421E800F for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 19:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.711
X-Spam-Level: 
X-Spam-Status: No, score=-5.711 tagged_above=-999 required=5 tests=[AWL=0.888,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UU7vwlysA4Mz for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 19:58:16 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by ietfa.amsl.com (Postfix) with ESMTP id 6551221E800E for <ietf@ietf.org>; Wed, 15 Feb 2012 19:58:16 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q1G3wCED022360 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2012 22:58:14 -0500 (EST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <4F3C5132.9050905@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Feb 2012 22:58:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu> <4F3C5132.9050905@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@NECOM830.HPCL.TITECH.AC.JP>
X-Mailer: Apple Mail (2.1257)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:58:20 -0000

On Feb 15, 2012, at 7:43 30PM, Masataka Ohta wrote:

> Steven Bellovin wrote:
>=20
>> Scott, if memory serves you and I wanted the high-order 2 bits of the =
IPng
>> address to select between 64, 128, 192, and 256-bit addresses -- and =
when
>> we couldn't get that we got folks to agree on 128-bit addresses =
instead of
>> 64-bit, which is what had been on the table.
>=20
> Thus, IPv6 was mortally wounded from the beginning.

The history is vastly more complex than that.  However, this particular =
decision
was just about the last one the IPng directorate made before reporting =
back to
the IETF -- virtually everything else in the basic IPv6 design had =
already
been agreed-to.  It was a long, painful effort, with a lot of debate =
over very
many of the points that have been discussed over and over again.  I =
don't think
this was "the" wrong decision.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From rogerj@gmail.com  Thu Feb 16 01:34:19 2012
Return-Path: <rogerj@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 91FA621F8581 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 01:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.067
X-Spam-Level: 
X-Spam-Status: No, score=-3.067 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M--j-HU+MiKW for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 01:34:15 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id BB44921F860E for <ietf@ietf.org>; Thu, 16 Feb 2012 01:34:14 -0800 (PST)
Received: by lahl5 with SMTP id l5so2467322lah.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 01:34:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=4LsG8lkqWHYwlauGY0K4OSOanNobOXEDhUcFUEZWRco=; b=KnytGGP9iESDL6Yn5FwZ34k/NiOQmIEPYUfg7/ixl1sUhlVdL8yVfwNbFbpkdBuD1b 1fR2ABERPFnlGmFgz2ieI1fMGReLxGBbAUzhZ97GndrgU6+SR4GLXwFOPvw2gcjn57wF v+A7J6WmGXLRvzrapkcE8p1PpTebXkqA8uuDY=
MIME-Version: 1.0
Received: by 10.152.108.49 with SMTP id hh17mr1254006lab.0.1329384853579; Thu, 16 Feb 2012 01:34:13 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Thu, 16 Feb 2012 01:34:13 -0800 (PST)
In-Reply-To: <8F9F107F1A51524597A5D2E0F43EE9632AD416BD28@PRVPEXVS09.corp.twcable.com>
References: <8F9F107F1A51524597A5D2E0F43EE9632AD416BD28@PRVPEXVS09.corp.twcable.com>
Date: Thu, 16 Feb 2012 10:34:13 +0100
Message-ID: <CAKFn1SGxzvNh_n09CaY5+Ke+s7Uq8nvX9H-TgN7QykouQ+nQUA@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 09:34:19 -0000

not replying specific to this mail but to the tons that have arrived
lately, are there some confusion out there that it is the amount of
"votes" on ietf@ that make a do/do not on a draft? ... or just me
missunderstanding this?


anyway, great to see people participate :-)

--- Roger J ---

On Tue, Feb 14, 2012 at 6:19 PM, Erichsen, Kirk
<kirk.erichsen@twcable.com> wrote:
> I fully support this draft and would like to see it progress to conclusio=
n without further delay.
>
> With warm regard,
>
> Kirk Erichsen
> Principle Technology Engineer
> Time Warner Cable
> ATG West
>
>
> This E-mail and any of its attachments may contain Time Warner Cable prop=
rietary information, which is privileged, confidential, or subject to copyr=
ight belonging to Time Warner Cable. This E-mail is intended solely for the=
 use of the individual or entity to which it is addressed. If you are not t=
he intended recipient of this E-mail, you are hereby notified that any diss=
emination, distribution, copying, or action taken in relation to the conten=
ts of and attachments to this E-mail is strictly prohibited and may be unla=
wful. If you have received this E-mail in error, please notify the sender i=
mmediately and permanently delete the original and any copy of this E-mail =
and any printout.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From matthew.bocci@alcatel-lucent.com  Thu Feb 16 02:05:25 2012
Return-Path: <matthew.bocci@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5573F21F86F2; Thu, 16 Feb 2012 02:05:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.802
X-Spam-Level: 
X-Spam-Status: No, score=-105.802 tagged_above=-999 required=5 tests=[AWL=-1.854, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Deso07Afb70X; Thu, 16 Feb 2012 02:05:23 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by ietfa.amsl.com (Postfix) with ESMTP id AEE7F21F871D; Thu, 16 Feb 2012 02:05:10 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q1G9xrAL005020 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 16 Feb 2012 11:03:20 +0100
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.34]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Thu, 16 Feb 2012 11:02:53 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 16 Feb 2012 11:02:51 +0100
Subject: Re: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
Thread-Topic: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
Thread-Index: AczskiYGRqS0mn8KS3+tOKP48PqizA==
Message-ID: <CB6284AB.23A4E%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <FE60A4E52763E84B935532D7D9294FF1322B42FE15@EUSAACMS0715.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CB6284AB23A4Ematthewboccialcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80
Cc: "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:05:25 -0000

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

Greg,

That is fine with me.

Best regards

Matthew

On 15/02/2012 22:14, "Gregory Mirsky" <gregory.mirsky@ericsson.com<mailto:g=
regory.mirsky@ericsson.com>> wrote:

Dear Matthew, Authors, et al.,
I think that new text of fourth para in Section 5.3 adds some confusion. If=
 intension is to stop sending 'all clear' after three one-second intervals =
went unacknowledged but before refresh timer expires then perhpas new text =
can be more explicit:
NEW:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however,
transmission will cease after 3 PW status messages have been sent at one se=
cond intervals and before refresh timer expires. A PW
status message of zero MAY be acknowledged as per the procedures described
in Section 5.3.1. If it is acknowledged, then a timer
value of zero MUST be used.  This SHOULD cause the PE sending the PW status
notification message with a PW status code equal to zero to stop sending
 and to continue normal operation.

    Regards,
        Greg

________________________________
From: pwe3-bounces@ietf.org<mailto:pwe3-bounces@ietf.org> [mailto:pwe3-boun=
ces@ietf.org] On Behalf Of Bocci, Matthew (Matthew)
Sent: Wednesday, February 15, 2012 7:10 AM
To: pwe3@ietf.org<mailto:pwe3@ietf.org>; ietf@ietf.org<mailto:ietf@ietf.org=
>
Cc: pwe3-chairs@tools.ietf.org<mailto:pwe3-chairs@tools.ietf.org>; Stewart =
Bryant
Subject: [PWE3] Auth48 comments on draft-ietf-pwe3-static-pw-status-10

During Auth 48, the authors of draft-ietf-pwe3-static-pw-status found some =
issues with the acknowledgement procedures in Section 5.3 of the draft that=
 we feel should be addressed before publication. Since the draft has alread=
y been through WG and IETF last call, we would like to highlight the propos=
ed changes to the working group and solicit feedback.

Best regards,

Matthew

Section 5.3, 3rd paragraph:
Reason for change:
The current suggested default refresh timer value is too short to allow sca=
ling
to very large numbers of PWs while minimising the overhead. It is also inco=
nsistent
with the suggested default requested in an ACK packet. Therefore we suggest=
 increasing
the default to 600secs.

OLD: The suggested default value for the refresh timer is 30 seconds.

NEW: The suggested default value for the refresh timer is 600 seconds.



Section 5.3, 4th paragraph:
Reason for change:
The current text requires that a receiving PE must acknowledge a PW status =
message
of 'clear all faults' in order to force a transmitter to stop sending PW st=
atus
messages at 1 second intervals.  We are concerned that a mandatory acknowle=
dgement
adds an unnecessary complexity to the protocol which is inconsistent with
the use of the acknowledgement as per the following section (5.3.1). Additi=
onally,
we are also concerned that this may cause problems if a transmitter
is flapping between 'clear all faults' and a non-zero value, and if the
acknowledgement is lost. We therefore suggest that the acknowledgement to
'clear all faults' be made optional, and that  the transmitter behavior be =
changed so
that it sends up to 3 status messages of zero in a row, and then goes silen=
t.

OLD:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however, it MUST be
acknowledged with a packet with a timer value of zero.  This will cause
the PE sending the PW status notification message with a PW status code
equal to zero to stop sending and to continue normal operation.


NEW:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however,
transmission will cease after 3 PW status messages have been sent. A PW
status message of zero MAY be acknowledged as per the procedures described
in Section 5.3.1. If it is acknowledged, then a timer
value of zero MUST be used.  This SHOULD cause the PE sending the PW status
notification message with a PW status code equal to zero to stop sending
 and to continue normal operation.


Section 5.3.1, 1st paragraph:
Reason for change:
The procedures currently defined in this paragraph can lead to a receiver
of the static status message timing out if it requests, throught the use of=
 the
ACK mechanism, a longer refresh timer from the transmitter. This is because=
 the
current text implies that the transmitter change its referesh timer immedia=
tely
on receipt of the ack packet from the receiver. The new text clarifies that
the refresh timer be updated at the end of the current refresh interval, as
well as making some other editorial clarifications.

OLD:
The PE receiving a PW OAM message containing a PW status message
can acknowledge the PW status message by simply building an almost
identical reply packet with the A bit set, and transmitting it on the PW
ACH back to the source of the PW status message.  The timer value set in
the reply packet SHOULD then be used by the PE as the new transmit
interval.  If the transmitting PE does not want to use the new timer
value (for local policy reasons, or because it simply cannot support
it), it MUST refresh the PW OAM message with the timer value it desires.
The receiving PE will then set its timeout timer according to the timer
value that is in the packet received, regardless of what timer value it
sent.  The receiving PE MUST NOT retry to set the timer value more than
once per timer value.

NEW:
A PE receiving a PW OAM message containing a PW status message MAY
acknowledge the PW status message by simply building a reply packet
with the same format and status code as the received PW OAM message,
but with the A bit set, and transmitting it on the PW ACh back
to the source of the PW OAM message.  The receiving PE MAY use the
refresh timer field in the acknowledgement packet to request a new
refresh interval from the originator of the PW OAM message. The timer
value set in the reply packet SHOULD then be used by the originator of
the PW OAM message as the new transmit interval.  If the requested
refresh timer value is used, the PW OAM message transmission interval is
only set to the new value and the new value sent in the next PW OAM
message, when the current timer expires. If the transmitting PE does not
want to use the new timer value (for local policy reasons, or because it
simply cannot support it), it MUST refresh the PW OAM message with the
timer value it desires. The receiving PE will then set its timeout timer
according to the new refresh timer value that is in the packet received,
regardless of what timer value it requested.  The receiving PE MUST NOT
request a new refresh timer value more than once per refresh interval.


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 14px; font-family: Calibri, sans-serif; "><div>Greg,</div><div><br></di=
v><div>That is fine with me.</div><div><br></div><div>Best regards</div><di=
v><br></div><div>Matthew</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTI=
ON"><div><div>On 15/02/2012 22:14, "Gregory Mirsky" &lt;<a href=3D"mailto:g=
regory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt; wrote:</div=
></div><div><br></div><blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"=
 style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><=
div><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-as=
cii"><meta content=3D"MSHTML 6.00.6002.18538" name=3D"GENERATOR"><div style=
=3D"FONT-SIZE: 14px; COLOR: rgb(0,0,0); FONT-FAMILY: Calibri, sans-serif; W=
ORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-w=
hite-space"><div dir=3D"ltr" align=3D"left"><span class=3D"153090422-150220=
12"><font face=3D"Arial" size=3D"2">Dear Matthew, Authors, et al.,</font></=
span></div><div dir=3D"ltr" align=3D"left"><span class=3D"153090422-1502201=
2"><font face=3D"Arial" size=3D"2">I=20
think that new text of fourth para in Section 5.3 adds some confusion. If=20
intension is to stop sending 'all clear' after three one-second intervals w=
ent=20
unacknowledged but before refresh timer expires then perhpas new text can b=
e=20
more explicit:</font></span></div><div dir=3D"ltr" align=3D"left"><span cla=
ss=3D"153090422-15022012"><div>NEW:&nbsp;</div><div>To clear a particular s=
tatus fault, the PE need only send an</div><div>updated message with the co=
rresponding bit cleared. &nbsp;If the PW=20
status</div><div>code is zero, the PW OAM message will be sent like any oth=
er PW OAM</div><div>status message using the procedures described above; ho=
wever,</div><div>transmission will cease after 3 PW status messages have be=
en sent<span class=3D"153090422-15022012"> <em><u>at one second intervals a=
nd before refresh=20
timer expires</u></em></span>. A PW</div><div>status message of zero MAY be=
 acknowledged as per the procedures=20
described&nbsp;</div><div>in Section 5.3.1. If it is acknowledged, then a t=
imer</div><div>value of zero MUST be used. &nbsp;This SHOULD cause the PE s=
ending the PW=20
status</div><div>notification message with a PW status code equal to zero t=
o stop=20
sending</div><div>&nbsp;and to continue normal operation.</div></span></div=
><div dir=3D"ltr" align=3D"left"><span class=3D"153090422-15022012"><font s=
ize=3D"4"></font></span>&nbsp;</div><div dir=3D"ltr" align=3D"left"><span c=
lass=3D"153090422-15022012">&nbsp;&nbsp;&nbsp; <font face=3D"Arial" size=3D=
"2">Regards,</font></span></div><div dir=3D"ltr" align=3D"left"><span class=
=3D"153090422-15022012">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font fa=
ce=3D"Arial" size=3D"2">Greg</font></span></div><br><div class=3D"OutlookMe=
ssageHeader" lang=3D"en-us" dir=3D"ltr" align=3D"left"><hr tabindex=3D"-1">=
<font face=3D"Tahoma" size=3D"2"><b>From:</b> <a href=3D"mailto:pwe3-bounce=
s@ietf.org">pwe3-bounces@ietf.org</a>=20
[<a href=3D"mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</a>]=
 <b>On Behalf Of </b>Bocci, Matthew=20
(Matthew)<br><b>Sent:</b> Wednesday, February 15, 2012 7:10 AM<br><b>To:</b=
>=20
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a>; <a href=3D"mailto:ietf@=
ietf.org">ietf@ietf.org</a><br><b>Cc:</b> <a href=3D"mailto:pwe3-chairs@too=
ls.ietf.org">pwe3-chairs@tools.ietf.org</a>; Stewart=20
Bryant<br><b>Subject:</b> [PWE3] Auth48 comments on=20
draft-ietf-pwe3-static-pw-status-10<br></font><br></div><div></div><div><di=
v><div>During Auth 48, the authors of draft-ietf-pwe3-static-pw-status foun=
d some=20
issues with the acknowledgement procedures in Section 5.3 of the draft that=
 we=20
feel should be addressed before publication. Since the draft has already be=
en=20
through WG and IETF last call, we would like to highlight the proposed chan=
ges=20
to the working group and solicit feedback.</div><div><br></div><div><div>Be=
st regards,</div><div><br></div><div>Matthew</div></div></div><div><br></di=
v><div>Section 5.3, 3rd paragraph:</div><div>Reason for change:</div><div>T=
he current suggested default refresh timer value is too short to allow=20
scaling&nbsp;</div><div>to very large numbers of PWs while minimising the o=
verhead. It is also=20
inconsistent</div><div>with the suggested default requested in an ACK packe=
t. Therefore we suggest=20
increasing</div><div>the default to 600secs.</div><div><br></div><div>OLD: =
The suggested default value for the refresh timer is 30 seconds.</div><div>=
<br></div><div>NEW: The suggested default value for the refresh timer is 60=
0 seconds.</div><div><br></div><div><br></div><div><br></div><div>Section 5=
.3, 4th paragraph:</div><div>Reason for change:</div><div>The current text =
requires that a receiving PE must acknowledge a PW status=20
message</div><div>of 'clear all faults' in order to force a transmitter to =
stop sending PW=20
status</div><div>messages at 1 second intervals. &nbsp;We are concerned tha=
t a mandatory=20
acknowledgement</div><div>adds an unnecessary complexity to the protocol wh=
ich is inconsistent=20
with</div><div>the use of the acknowledgement as per the following section =
(5.3.1).=20
Additionally,</div><div>we are also concerned that this may cause problems =
if a=20
transmitter&nbsp;</div><div>is flapping between 'clear all faults' and a no=
n-zero value, and if=20
the&nbsp;</div><div>acknowledgement is lost. We therefore&nbsp;suggest that=
 the acknowledgement=20
to&nbsp;</div><div>'clear all faults' be made optional, and that &nbsp;the =
transmitter=20
behavior be changed so&nbsp;</div><div>that it sends up to 3 status message=
s of&nbsp;zero in a row, and then goes=20
silent.</div><div><br></div><div>OLD:&nbsp;</div><div>To clear a particular=
 status fault, the PE need only send an</div><div>updated message with the =
corresponding bit cleared. &nbsp;If the PW=20
status</div><div>code is zero, the PW OAM message will be sent like any oth=
er PW OAM</div><div>status message using the procedures described above; ho=
wever, it MUST=20
be</div><div>acknowledged with a packet with a timer value of zero. &nbsp;T=
his will=20
cause</div><div>the PE sending the PW status notification message with a PW=
 status=20
code</div><div>equal to zero to stop sending and to continue normal operati=
on.</div><div><br></div><div><br></div><div>NEW:&nbsp;</div><div>To clear a=
 particular status fault, the PE need only send an</div><div>updated messag=
e with the corresponding bit cleared. &nbsp;If the PW=20
status</div><div>code is zero, the PW OAM message will be sent like any oth=
er PW OAM</div><div>status message using the procedures described above; ho=
wever,</div><div>transmission will cease after 3 PW status messages have be=
en sent. A=20
PW</div><div>status message of zero MAY be acknowledged as per the procedur=
es=20
described&nbsp;</div><div>in Section 5.3.1. If it is acknowledged, then a t=
imer</div><div>value of zero MUST be used. &nbsp;This SHOULD cause the PE s=
ending the PW=20
status</div><div>notification message with a PW status code equal to zero t=
o stop=20
sending</div><div>&nbsp;and to continue normal operation.</div><div><br></d=
iv><div><br></div><div>Section 5.3.1, 1st paragraph:</div><div>Reason for c=
hange:</div><div>The procedures currently defined in this paragraph can lea=
d to a=20
receiver</div><div>of the static status message timing out if it requests, =
throught the use of=20
the</div><div>ACK mechanism, a longer refresh timer from the transmitter. T=
his is because=20
the</div><div>current text implies that the transmitter change its referesh=
 timer=20
immediately</div><div>on receipt of the ack packet from the receiver. The n=
ew text clarifies=20
that&nbsp;</div><div>the refresh timer be updated at the end of the current=
 refresh interval,=20
as&nbsp;</div><div>well as making some other editorial clarifications.</div=
><div><br></div><div>OLD:&nbsp;</div><div>The PE receiving a PW OAM message=
 containing a PW status message</div><div>can acknowledge the PW status mes=
sage by simply building an almost</div><div>identical reply packet with the=
 A bit set, and transmitting it on the=20
PW</div><div>ACH back to the source of the PW status message. &nbsp;The tim=
er value set=20
in</div><div>the reply packet SHOULD then be used by the PE as the new tran=
smit</div><div>interval. &nbsp;If the transmitting PE does not want to use =
the new=20
timer</div><div>value (for local policy reasons, or because it simply canno=
t support</div><div>it), it MUST refresh the PW OAM message with the timer =
value it=20
desires.</div><div>The receiving PE will then set its timeout timer accordi=
ng to the=20
timer</div><div>value that is in the packet received, regardless of what ti=
mer value=20
it</div><div>sent. &nbsp;The receiving PE MUST NOT retry to set the timer v=
alue more=20
than</div><div>once per timer value.</div><div><br></div><div>NEW:&nbsp;</d=
iv><div>A PE receiving a PW OAM message containing a PW status message MAY<=
/div><div>acknowledge the PW status message by simply building a reply=20
packet&nbsp;</div><div>with the same format and status code as the received=
 PW OAM message,</div><div>but with the A bit set, and transmitting it on t=
he PW ACh back</div><div>to the source of the PW OAM message. &nbsp;The rec=
eiving PE MAY use=20
the</div><div>refresh timer field in the acknowledgement packet to request =
a new</div><div>refresh interval from the originator of the PW OAM message.=
 The timer</div><div>value set in the reply packet SHOULD then be used by t=
he originator=20
of</div><div>the PW OAM message as the new transmit interval. &nbsp;If the =
requested</div><div>refresh timer value is used, the PW OAM message transmi=
ssion interval=20
is</div><div>only set to the new value and the new value sent in the next P=
W OAM</div><div>message, when the current timer expires. If the transmittin=
g PE does=20
not</div><div>want to use the new timer value (for local policy reasons, or=
 because=20
it</div><div>simply cannot support it), it MUST refresh the PW OAM message =
with=20
the</div><div>timer value it desires. The receiving PE will then set its ti=
meout=20
timer</div><div>according to the new refresh timer value that is in the pac=
ket=20
received,</div><div>regardless of what timer value it requested. &nbsp;The =
receiving PE MUST=20
NOT</div><div>request a new refresh timer value more than once per refresh =
interval.</div><div><br></div></div></div></div></blockquote></span></body>=
</html>

--_000_CB6284AB23A4Ematthewboccialcatellucentcom_--

From martin@millnert.se  Thu Feb 16 02:43:20 2012
Return-Path: <martin@millnert.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 71AD721F876D for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 02:43:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZhb5D5CopFY for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 02:43:19 -0800 (PST)
Received: from ncis.csbnet.se (ncis.csbnet.se [95.80.1.101]) by ietfa.amsl.com (Postfix) with ESMTP id 5200521F8778 for <ietf@ietf.org>; Thu, 16 Feb 2012 02:43:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id EA1C25E1 for <ietf@ietf.org>; Thu, 16 Feb 2012 11:40:46 +0100 (CET)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hw079lIlUI+0 for <ietf@ietf.org>; Thu, 16 Feb 2012 11:40:46 +0100 (CET)
Received: from [192.168.120.227] (h-189-4.a189.priv.bahnhof.se [85.24.189.4]) by ncis.csbnet.se (Postfix) with ESMTPSA id BEC422B0 for <ietf@ietf.org>; Thu, 16 Feb 2012 11:40:46 +0100 (CET)
Message-ID: <1329388980.5382.44.camel@davinci.millnert.se>
Subject: Re: Last Call:	<draft-weil-shared-transition-space-request-14.txt> (IANA	Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Martin Millnert <martin@millnert.se>
To: ietf@ietf.org
Date: Thu, 16 Feb 2012 11:43:00 +0100
In-Reply-To: <4F3B09C3.1090005@qualcomm.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com>	<01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-vIiRWIQGGwZFOoqgaBS9"
X-Mailer: Evolution 3.0.3-3 
Mime-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:43:20 -0000

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

On Tue, 2012-02-14 at 19:26 -0600, Pete Resnick wrote:
> On 2/14/12 2:35 PM, Randy Bush wrote:
>=20
> > what silliness.  it will be used as rfc 1918 space no matter what the d=
ocument
> > says.
> > [...]
> > any thought that this is not just adding to rfc 1918 is pure bs.
> >   =20
>=20
> Of course it will be used as 1918 space. That's not the point of the text=
.

No support.

For the various reasons people have put forth, and my own below, this
draft should not be put through.

> The text is saying, "You could read 1918 to say that we somehow promised=
=20
> that you would never be connected to a network run by someone other than=
=20
> yourself and see 1918 addresses on it. That's not an entirely=20
> intelligent reading, but we see how you can read it that way. So, if you=
=20
> built yourself a device where it isn't able to deal with 1918 addresses=
=20
> on its 'outside' interface that you were using on the 'inside'=20
> interfaces, we could see how that might happen. It was not at all smart=
=20
> of you to build your device that way, but you probably were technically=
=20
> within spec. Now we're adding some address space to the pool. It's not=
=20
> global and it's not routable, just the same as 1918 space. But we're=20
> letting you know right now: You *will* see these addresses on networks=
=20
> that you don't run. If you want to use this space the way that you used=
=20
> 1918 space, peachy, but understand that if you're unable to deal with=20
> these addresses duplicating ones you're using, your device is toast.=20
> Deal with it."

This is 100% matched by an allocation of globally unique space from a
RIR, shared by whoever the interested parties are.=20
  The IETF *need not* specify any BCP on how to improve NAT444
"CGN"-scale alone, because such action is attached with high risk of
leading to a local maximum in a plot of the state of the Internet,
rather than towards a global maximum.

Citing RFC6264, "An Incremental Carrier-Grade NAT (CGN) for IPv6
Transition" warns:
   Carrier-Grade NAT (CGN) [CGN-REQS], also called NAT444 CGN or Large
   Scale NAT, compounds IPv4 operational problems when used alone but
   does nothing to encourage IPv4 to IPv6 transition.  Deployment of
   NAT444 CGN allows ISPs to delay the transition and therefore causes
   double transition costs (once to add CGN and again to support IPv6).

The draft as written, makes no effort to require the RFC6264 or
equivalent approaches to a IPv6 transition, to the CGN deployments it
specifies v4 address space for. All carrot, no stick.
  I believe the state of the Internet would be much more reliably
improved by the RIRs each having (for the purpose of being able to serve
their own users) one /10 special allocation for this purpose, which they
can assign to multiple users upon demonstrating, under contract, they
are transitioning to IPv6 according to 6264, or equivalent.

As written there is no effort to mitigate the risk mentioned in the
quote above, and I can't support a draft that will hurt the Internet and
neither should you.

Best,
Martin

--=-vIiRWIQGGwZFOoqgaBS9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

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

iQIcBAABAgAGBQJPPN20AAoJEKgraNdZrwxMZEYP/1F7MHmZxa2ppThRwl01/m5B
uMgHn+hNTapkLj7UBB8oTU5QXSJRE5WWWpLI8v0sNJ6M9WF9yG1b33CLPB1R+RlR
cUUgXpKVttNsSA0fILmEx25F1IFD1NgUmH5UkEZPxrTFaU4+llZDVPgtIiLSUlwO
lfUL/Cgd9JhArPuC/k8knGBwaWCAGRsfFcT+OVNK1vZUkA2TNZ0Q3IWb1jhdvn+7
7oUHeMSusWyzcGmeCS636Txr00+qeXUrmdbefiOcIgFAxRbj9s5o9nHEIfCWwps5
QrQGsHV3wnr4NHWRoJ2QHHpzEtaUwmOyyJxX8L1K0vk3fx7U5ZmTevsF+2+DHIha
ErNQNpvjTxZeECePypNn9AqHbtwflYCSHTk6eyHVb3gQQ/DVvLQ2X23oWZkfMVai
sMLeEUtdlPV+IFyZvJbXNf/ZUHcHdvQ+gzppUqllLilno/XszvZUz6uV9ISZKkRu
CRuNWkY9pyrT0AedIHblOn7z4DqK8yUsrFxV1zUHpfsXN/PfKAlVwKGM8yM73VLX
1PgVGqipLtGbZkbxnR0mh6r2zKTezvF/H1UdBhlcn2mOQH/qY5BvTSoXKbC67Q/a
rU8jab4XvDyZhyGYe3X7HfcG1n69WareN2N4lWu6jZl+U+5RMEriuOGBs6ykl13d
qR3NlC29joylGGN63LBp
=liWg
-----END PGP SIGNATURE-----

--=-vIiRWIQGGwZFOoqgaBS9--


From stbryant@cisco.com  Thu Feb 16 03:48:40 2012
Return-Path: <stbryant@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 2C36C21F8574; Thu, 16 Feb 2012 03:48:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.448
X-Spam-Level: 
X-Spam-Status: No, score=-109.448 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dw6gJKsQV5J; Thu, 16 Feb 2012 03:48:36 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id DD6E121F8557; Thu, 16 Feb 2012 03:48:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=25782; q=dns/txt; s=iport; t=1329392893; x=1330602493; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=G8sjRuwM3BgkAh1Fu99TmAgA4o4HWL6wXsA5Zk3Kq6s=; b=RGx/Gvcp/nrYI1kVSmNGb88ClqyRuqvNNvf6WXhmSWM8GGZyhlPaP52D kd3shHnHvSbg1LhgpXV0Wm3YLy7/7LZ36g5k3Lun3Q7D0worrSR39Zqmx z5MnE1/7jZOIZxsjzHLYKGSlg9CXFuAx4jcFa5PlY0dcy5OrgNsCJZYV4 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAM7sPE+Q/khN/2dsb2JhbABDglGuEoEHgXIBAQEEEgECAWIBEAsRBAEBAQkWAQcHCQMCAQIBNAkIBgEMAQUCAQEeh2afDQGDMQ8Bkx6LYgICBAMBAgECAQEDBgICAQYEAgQBBQI5AYNUGwUGKwMCBAQFDAGDKgSCXZJakmg
X-IronPort-AV: E=Sophos;i="4.73,428,1325462400"; d="scan'208,217";a="66284791"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 16 Feb 2012 11:48:07 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q1GBm7Y8004744; Thu, 16 Feb 2012 11:48:07 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-45.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q1GBm6MR004467; Thu, 16 Feb 2012 11:48:07 GMT
Message-ID: <4F3CECF5.5020806@cisco.com>
Date: Thu, 16 Feb 2012 11:48:05 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
References: <CB6284AB.23A4E%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CB6284AB.23A4E%matthew.bocci@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="------------040602080900040000010009"
Cc: Gregory Mirsky <gregory.mirsky@ericsson.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 11:48:40 -0000

This is a multi-part message in MIME format.
--------------040602080900040000010009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Having spoken to a number of the authors at length
I think  the text changes that Matthew has proposed
are correct (with Greg's change) and thank the authors
for picking this up.

I propose to let this sit until a week tomorrow (23/Feb)
and provided that there are no technical issues with the
proposed changes I will ask the RFC Editor to make
the changes and to publish the RFC.

- Stewart


On 16/02/2012 10:02, Bocci, Matthew (Matthew) wrote:
> Greg,
>
> That is fine with me.
>
> Best regards
>
> Matthew
>
> On 15/02/2012 22:14, "Gregory Mirsky" <gregory.mirsky@ericsson.com 
> <mailto:gregory.mirsky@ericsson.com>> wrote:
>
>     Dear Matthew, Authors, et al.,
>     I think that new text of fourth para in Section 5.3 adds some
>     confusion. If intension is to stop sending 'all clear' after three
>     one-second intervals went unacknowledged but before refresh timer
>     expires then perhpas new text can be more explicit:
>     NEW:
>     To clear a particular status fault, the PE need only send an
>     updated message with the corresponding bit cleared.  If the PW status
>     code is zero, the PW OAM message will be sent like any other PW OAM
>     status message using the procedures described above; however,
>     transmission will cease after 3 PW status messages have been
>     sent/_at one second intervals and before refresh timer expires_/. A PW
>     status message of zero MAY be acknowledged as per the procedures
>     described
>     in Section 5.3.1. If it is acknowledged, then a timer
>     value of zero MUST be used.  This SHOULD cause the PE sending the
>     PW status
>     notification message with a PW status code equal to zero to stop
>     sending
>      and to continue normal operation.
>     Regards,
>     Greg
>
>     ------------------------------------------------------------------------
>     *From:* pwe3-bounces@ietf.org <mailto:pwe3-bounces@ietf.org>
>     [mailto:pwe3-bounces@ietf.org] *On Behalf Of *Bocci, Matthew (Matthew)
>     *Sent:* Wednesday, February 15, 2012 7:10 AM
>     *To:* pwe3@ietf.org <mailto:pwe3@ietf.org>; ietf@ietf.org
>     <mailto:ietf@ietf.org>
>     *Cc:* pwe3-chairs@tools.ietf.org
>     <mailto:pwe3-chairs@tools.ietf.org>; Stewart Bryant
>     *Subject:* [PWE3] Auth48 comments on
>     draft-ietf-pwe3-static-pw-status-10
>
>     During Auth 48, the authors of draft-ietf-pwe3-static-pw-status
>     found some issues with the acknowledgement procedures in Section
>     5.3 of the draft that we feel should be addressed before
>     publication. Since the draft has already been through WG and IETF
>     last call, we would like to highlight the proposed changes to the
>     working group and solicit feedback.
>
>     Best regards,
>
>     Matthew
>
>     Section 5.3, 3rd paragraph:
>     Reason for change:
>     The current suggested default refresh timer value is too short to
>     allow scaling
>     to very large numbers of PWs while minimising the overhead. It is
>     also inconsistent
>     with the suggested default requested in an ACK packet. Therefore
>     we suggest increasing
>     the default to 600secs.
>
>     OLD: The suggested default value for the refresh timer is 30 seconds.
>
>     NEW: The suggested default value for the refresh timer is 600 seconds.
>
>
>
>     Section 5.3, 4th paragraph:
>     Reason for change:
>     The current text requires that a receiving PE must acknowledge a
>     PW status message
>     of 'clear all faults' in order to force a transmitter to stop
>     sending PW status
>     messages at 1 second intervals.  We are concerned that a mandatory
>     acknowledgement
>     adds an unnecessary complexity to the protocol which is
>     inconsistent with
>     the use of the acknowledgement as per the following section
>     (5.3.1). Additionally,
>     we are also concerned that this may cause problems if a transmitter
>     is flapping between 'clear all faults' and a non-zero value, and
>     if the
>     acknowledgement is lost. We therefore suggest that the
>     acknowledgement to
>     'clear all faults' be made optional, and that  the transmitter
>     behavior be changed so
>     that it sends up to 3 status messages of zero in a row, and then
>     goes silent.
>
>     OLD:
>     To clear a particular status fault, the PE need only send an
>     updated message with the corresponding bit cleared.  If the PW status
>     code is zero, the PW OAM message will be sent like any other PW OAM
>     status message using the procedures described above; however, it
>     MUST be
>     acknowledged with a packet with a timer value of zero.  This will
>     cause
>     the PE sending the PW status notification message with a PW status
>     code
>     equal to zero to stop sending and to continue normal operation.
>
>
>     NEW:
>     To clear a particular status fault, the PE need only send an
>     updated message with the corresponding bit cleared.  If the PW status
>     code is zero, the PW OAM message will be sent like any other PW OAM
>     status message using the procedures described above; however,
>     transmission will cease after 3 PW status messages have been sent.
>     A PW
>     status message of zero MAY be acknowledged as per the procedures
>     described
>     in Section 5.3.1. If it is acknowledged, then a timer
>     value of zero MUST be used.  This SHOULD cause the PE sending the
>     PW status
>     notification message with a PW status code equal to zero to stop
>     sending
>      and to continue normal operation.
>
>
>     Section 5.3.1, 1st paragraph:
>     Reason for change:
>     The procedures currently defined in this paragraph can lead to a
>     receiver
>     of the static status message timing out if it requests, throught
>     the use of the
>     ACK mechanism, a longer refresh timer from the transmitter. This
>     is because the
>     current text implies that the transmitter change its referesh
>     timer immediately
>     on receipt of the ack packet from the receiver. The new text
>     clarifies that
>     the refresh timer be updated at the end of the current refresh
>     interval, as
>     well as making some other editorial clarifications.
>
>     OLD:
>     The PE receiving a PW OAM message containing a PW status message
>     can acknowledge the PW status message by simply building an almost
>     identical reply packet with the A bit set, and transmitting it on
>     the PW
>     ACH back to the source of the PW status message.  The timer value
>     set in
>     the reply packet SHOULD then be used by the PE as the new transmit
>     interval.  If the transmitting PE does not want to use the new timer
>     value (for local policy reasons, or because it simply cannot support
>     it), it MUST refresh the PW OAM message with the timer value it
>     desires.
>     The receiving PE will then set its timeout timer according to the
>     timer
>     value that is in the packet received, regardless of what timer
>     value it
>     sent.  The receiving PE MUST NOT retry to set the timer value more
>     than
>     once per timer value.
>
>     NEW:
>     A PE receiving a PW OAM message containing a PW status message MAY
>     acknowledge the PW status message by simply building a reply packet
>     with the same format and status code as the received PW OAM message,
>     but with the A bit set, and transmitting it on the PW ACh back
>     to the source of the PW OAM message.  The receiving PE MAY use the
>     refresh timer field in the acknowledgement packet to request a new
>     refresh interval from the originator of the PW OAM message. The timer
>     value set in the reply packet SHOULD then be used by the originator of
>     the PW OAM message as the new transmit interval.  If the requested
>     refresh timer value is used, the PW OAM message transmission
>     interval is
>     only set to the new value and the new value sent in the next PW OAM
>     message, when the current timer expires. If the transmitting PE
>     does not
>     want to use the new timer value (for local policy reasons, or
>     because it
>     simply cannot support it), it MUST refresh the PW OAM message with the
>     timer value it desires. The receiving PE will then set its timeout
>     timer
>     according to the new refresh timer value that is in the packet
>     received,
>     regardless of what timer value it requested.  The receiving PE
>     MUST NOT
>     request a new refresh timer value more than once per refresh interval.
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



--------------040602080900040000010009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Having spoken to a number of the authors at length<br>
    I think&nbsp; the text changes that Matthew has proposed<br>
    are correct (with Greg's change) and thank the authors<br>
    for picking this up.<br>
    <br>
    I propose to let this sit until a week tomorrow (23/Feb)<br>
    and provided that there are no technical issues with the <br>
    proposed changes I will ask the RFC Editor to make<br>
    the changes and to publish the RFC.<br>
    <br>
    - Stewart<br>
    <br>
    <br>
    On 16/02/2012 10:02, Bocci, Matthew (Matthew) wrote:
    <blockquote
      cite="mid:CB6284AB.23A4E%25matthew.bocci@alcatel-lucent.com"
      type="cite">
      <div>Greg,</div>
      <div><br>
      </div>
      <div>That is fine with me.</div>
      <div><br>
      </div>
      <div>Best regards</div>
      <div><br>
      </div>
      <div>Matthew</div>
      <div><br>
      </div>
      <span id="OLK_SRC_BODY_SECTION">
        <div>
          <div>On 15/02/2012 22:14, "Gregory Mirsky" &lt;<a
              moz-do-not-send="true"
              href="mailto:gregory.mirsky@ericsson.com">gregory.mirsky@ericsson.com</a>&gt;
            wrote:</div>
        </div>
        <div><br>
        </div>
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <meta http-equiv="Content-Type" content="text/html;
              charset=ISO-8859-1">
            <meta content="MSHTML 6.00.6002.18538" name="GENERATOR">
            <div style="FONT-SIZE: 14px; COLOR: rgb(0,0,0); FONT-FAMILY:
              Calibri, sans-serif; WORD-WRAP: break-word;
              -webkit-nbsp-mode: space; -webkit-line-break:
              after-white-space">
              <div dir="ltr" align="left"><span
                  class="153090422-15022012"><font face="Arial" size="2">Dear
                    Matthew, Authors, et al.,</font></span></div>
              <div dir="ltr" align="left"><span
                  class="153090422-15022012"><font face="Arial" size="2">I
                    think that new text of fourth para in Section 5.3
                    adds some confusion. If intension is to stop sending
                    'all clear' after three one-second intervals went
                    unacknowledged but before refresh timer expires then
                    perhpas new text can be more explicit:</font></span></div>
              <div dir="ltr" align="left"><span
                  class="153090422-15022012">
                  <div>NEW:&nbsp;</div>
                  <div>To clear a particular status fault, the PE need
                    only send an</div>
                  <div>updated message with the corresponding bit
                    cleared. &nbsp;If the PW status</div>
                  <div>code is zero, the PW OAM message will be sent
                    like any other PW OAM</div>
                  <div>status message using the procedures described
                    above; however,</div>
                  <div>transmission will cease after 3 PW status
                    messages have been sent<span
                      class="153090422-15022012"> <em><u>at one second
                          intervals and before refresh timer expires</u></em></span>.
                    A PW</div>
                  <div>status message of zero MAY be acknowledged as per
                    the procedures described&nbsp;</div>
                  <div>in Section 5.3.1. If it is acknowledged, then a
                    timer</div>
                  <div>value of zero MUST be used. &nbsp;This SHOULD cause
                    the PE sending the PW status</div>
                  <div>notification message with a PW status code equal
                    to zero to stop sending</div>
                  <div>&nbsp;and to continue normal operation.</div>
                </span></div>
              <div dir="ltr" align="left"><span
                  class="153090422-15022012"></span>&nbsp;</div>
              <div dir="ltr" align="left"><span
                  class="153090422-15022012">&nbsp;&nbsp;&nbsp; <font face="Arial"
                    size="2">Regards,</font></span></div>
              <div dir="ltr" align="left"><span
                  class="153090422-15022012">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <font face="Arial"
                    size="2">Greg</font></span></div>
              <br>
              <div class="OutlookMessageHeader" dir="ltr" align="left"
                lang="en-us">
                <hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b>
                  <a moz-do-not-send="true"
                    href="mailto:pwe3-bounces@ietf.org">pwe3-bounces@ietf.org</a>
                  [<a moz-do-not-send="true"
                    href="mailto:pwe3-bounces@ietf.org">mailto:pwe3-bounces@ietf.org</a>]
                  <b>On Behalf Of </b>Bocci, Matthew (Matthew)<br>
                  <b>Sent:</b> Wednesday, February 15, 2012 7:10 AM<br>
                  <b>To:</b> <a moz-do-not-send="true"
                    href="mailto:pwe3@ietf.org">pwe3@ietf.org</a>; <a
                    moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a><br>
                  <b>Cc:</b> <a moz-do-not-send="true"
                    href="mailto:pwe3-chairs@tools.ietf.org">pwe3-chairs@tools.ietf.org</a>;
                  Stewart Bryant<br>
                  <b>Subject:</b> [PWE3] Auth48 comments on
                  draft-ietf-pwe3-static-pw-status-10<br>
                </font><br>
              </div>
              <div>
                <div>
                  <div>During Auth 48, the authors of
                    draft-ietf-pwe3-static-pw-status found some issues
                    with the acknowledgement procedures in Section 5.3
                    of the draft that we feel should be addressed before
                    publication. Since the draft has already been
                    through WG and IETF last call, we would like to
                    highlight the proposed changes to the working group
                    and solicit feedback.</div>
                  <div><br>
                  </div>
                  <div>
                    <div>Best regards,</div>
                    <div><br>
                    </div>
                    <div>Matthew</div>
                  </div>
                </div>
                <div><br>
                </div>
                <div>Section 5.3, 3rd paragraph:</div>
                <div>Reason for change:</div>
                <div>The current suggested default refresh timer value
                  is too short to allow scaling&nbsp;</div>
                <div>to very large numbers of PWs while minimising the
                  overhead. It is also inconsistent</div>
                <div>with the suggested default requested in an ACK
                  packet. Therefore we suggest increasing</div>
                <div>the default to 600secs.</div>
                <div><br>
                </div>
                <div>OLD: The suggested default value for the refresh
                  timer is 30 seconds.</div>
                <div><br>
                </div>
                <div>NEW: The suggested default value for the refresh
                  timer is 600 seconds.</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Section 5.3, 4th paragraph:</div>
                <div>Reason for change:</div>
                <div>The current text requires that a receiving PE must
                  acknowledge a PW status message</div>
                <div>of 'clear all faults' in order to force a
                  transmitter to stop sending PW status</div>
                <div>messages at 1 second intervals. &nbsp;We are concerned
                  that a mandatory acknowledgement</div>
                <div>adds an unnecessary complexity to the protocol
                  which is inconsistent with</div>
                <div>the use of the acknowledgement as per the following
                  section (5.3.1). Additionally,</div>
                <div>we are also concerned that this may cause problems
                  if a transmitter&nbsp;</div>
                <div>is flapping between 'clear all faults' and a
                  non-zero value, and if the&nbsp;</div>
                <div>acknowledgement is lost. We therefore&nbsp;suggest that
                  the acknowledgement to&nbsp;</div>
                <div>'clear all faults' be made optional, and that &nbsp;the
                  transmitter behavior be changed so&nbsp;</div>
                <div>that it sends up to 3 status messages of&nbsp;zero in a
                  row, and then goes silent.</div>
                <div><br>
                </div>
                <div>OLD:&nbsp;</div>
                <div>To clear a particular status fault, the PE need
                  only send an</div>
                <div>updated message with the corresponding bit cleared.
                  &nbsp;If the PW status</div>
                <div>code is zero, the PW OAM message will be sent like
                  any other PW OAM</div>
                <div>status message using the procedures described
                  above; however, it MUST be</div>
                <div>acknowledged with a packet with a timer value of
                  zero. &nbsp;This will cause</div>
                <div>the PE sending the PW status notification message
                  with a PW status code</div>
                <div>equal to zero to stop sending and to continue
                  normal operation.</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>NEW:&nbsp;</div>
                <div>To clear a particular status fault, the PE need
                  only send an</div>
                <div>updated message with the corresponding bit cleared.
                  &nbsp;If the PW status</div>
                <div>code is zero, the PW OAM message will be sent like
                  any other PW OAM</div>
                <div>status message using the procedures described
                  above; however,</div>
                <div>transmission will cease after 3 PW status messages
                  have been sent. A PW</div>
                <div>status message of zero MAY be acknowledged as per
                  the procedures described&nbsp;</div>
                <div>in Section 5.3.1. If it is acknowledged, then a
                  timer</div>
                <div>value of zero MUST be used. &nbsp;This SHOULD cause the
                  PE sending the PW status</div>
                <div>notification message with a PW status code equal to
                  zero to stop sending</div>
                <div>&nbsp;and to continue normal operation.</div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Section 5.3.1, 1st paragraph:</div>
                <div>Reason for change:</div>
                <div>The procedures currently defined in this paragraph
                  can lead to a receiver</div>
                <div>of the static status message timing out if it
                  requests, throught the use of the</div>
                <div>ACK mechanism, a longer refresh timer from the
                  transmitter. This is because the</div>
                <div>current text implies that the transmitter change
                  its referesh timer immediately</div>
                <div>on receipt of the ack packet from the receiver. The
                  new text clarifies that&nbsp;</div>
                <div>the refresh timer be updated at the end of the
                  current refresh interval, as&nbsp;</div>
                <div>well as making some other editorial clarifications.</div>
                <div><br>
                </div>
                <div>OLD:&nbsp;</div>
                <div>The PE receiving a PW OAM message containing a PW
                  status message</div>
                <div>can acknowledge the PW status message by simply
                  building an almost</div>
                <div>identical reply packet with the A bit set, and
                  transmitting it on the PW</div>
                <div>ACH back to the source of the PW status message.
                  &nbsp;The timer value set in</div>
                <div>the reply packet SHOULD then be used by the PE as
                  the new transmit</div>
                <div>interval. &nbsp;If the transmitting PE does not want to
                  use the new timer</div>
                <div>value (for local policy reasons, or because it
                  simply cannot support</div>
                <div>it), it MUST refresh the PW OAM message with the
                  timer value it desires.</div>
                <div>The receiving PE will then set its timeout timer
                  according to the timer</div>
                <div>value that is in the packet received, regardless of
                  what timer value it</div>
                <div>sent. &nbsp;The receiving PE MUST NOT retry to set the
                  timer value more than</div>
                <div>once per timer value.</div>
                <div><br>
                </div>
                <div>NEW:&nbsp;</div>
                <div>A PE receiving a PW OAM message containing a PW
                  status message MAY</div>
                <div>acknowledge the PW status message by simply
                  building a reply packet&nbsp;</div>
                <div>with the same format and status code as the
                  received PW OAM message,</div>
                <div>but with the A bit set, and transmitting it on the
                  PW ACh back</div>
                <div>to the source of the PW OAM message. &nbsp;The receiving
                  PE MAY use the</div>
                <div>refresh timer field in the acknowledgement packet
                  to request a new</div>
                <div>refresh interval from the originator of the PW OAM
                  message. The timer</div>
                <div>value set in the reply packet SHOULD then be used
                  by the originator of</div>
                <div>the PW OAM message as the new transmit interval.
                  &nbsp;If the requested</div>
                <div>refresh timer value is used, the PW OAM message
                  transmission interval is</div>
                <div>only set to the new value and the new value sent in
                  the next PW OAM</div>
                <div>message, when the current timer expires. If the
                  transmitting PE does not</div>
                <div>want to use the new timer value (for local policy
                  reasons, or because it</div>
                <div>simply cannot support it), it MUST refresh the PW
                  OAM message with the</div>
                <div>timer value it desires. The receiving PE will then
                  set its timeout timer</div>
                <div>according to the new refresh timer value that is in
                  the packet received,</div>
                <div>regardless of what timer value it requested. &nbsp;The
                  receiving PE MUST NOT</div>
                <div>request a new refresh timer value more than once
                  per refresh interval.</div>
                <div><br>
                </div>
              </div>
            </div>
          </div>
        </blockquote>
      </span>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------040602080900040000010009--

From john-ietf@jck.com  Thu Feb 16 06:04:10 2012
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 DE3B321F875A for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.679
X-Spam-Level: 
X-Spam-Status: No, score=-102.679 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06Q4U0eYa9aD for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:04:10 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 60FA821F857A for <ietf@ietf.org>; Thu, 16 Feb 2012 06:04:10 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ry1sT-000Fgf-Um; Thu, 16 Feb 2012 09:00:05 -0500
Date: Thu, 16 Feb 2012 09:04:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: Scott O Bradner <sob@sobco.com>
Subject: IETF Last Calls and Godwin-like rules
Message-ID: <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
In-Reply-To: <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:04:11 -0000

A current Last Call has apparently brought on another of the
"please tell all your friends to send in supportive notes, even
if they don't say much of anything substantive" campaigns that
we see from time to time.  When those notes come from people who
do not routinely participate on IETF lists, they provide very
little real information unless we have suddenly taken up voting
or otherwise counting notes.  Whatever we might otherwise think
of company positions, a note that said "I work for <xyz> and we
need this and intend to implement and deploy it" would be real
information that the community could consider where "I am an
individual and +1" does not.   Sadly, such endorsements,
especially from people who are not active IETF participants, add
to the noise and might prevent someone who was still genuinely
trying to understand the pros and cons (presumably including all
of the IESG) from seeing a new and substantive argument, no
matter how well-grounded.

I note that there are some folks in the community who seem to
favor these campaigns when they like the cause and not if they
do not.

But I wonder whether, in the interest of noise reduction and/or
support of our "no voting, even by active participants"
position, there be any sympathy for a Godwin-like rule that the
first appearance of many no-information "I support this"
endorsements from people and constituencies who are not regular
participants on the IETF list should immediately trigger a state
in which all further statements from that "side" would be
ignored or would end the discussion entirely?

Yes, I see the difficulties in figuring out the details of such
a rule and implementing it and am mostly joking.   Mostly.

     john



From mansaxel@besserwisser.org  Thu Feb 16 06:09:21 2012
Return-Path: <mansaxel@besserwisser.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 1975821F8758 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0hQE7IWvpLO for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:09:20 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 872E421F86E0 for <ietf@ietf.org>; Thu, 16 Feb 2012 06:09:20 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 62C81A1FC; Thu, 16 Feb 2012 15:09:17 +0100 (CET)
Date: Thu, 16 Feb 2012 15:09:17 +0100
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: IETF Last Calls and Godwin-like rules
Message-ID: <20120216140917.GB9972@besserwisser.org>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE"
Content-Disposition: inline
In-Reply-To: <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org, Scott O Bradner <sob@sobco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:09:21 -0000

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

Subject: IETF Last Calls and Godwin-like rules Date: Thu, Feb 16, 2012 at 0=
9:04:03AM -0500 Quoting John C Klensin (john-ietf@jck.com):

=2E..

> first appearance of many no-information "I support this"
> endorsements from people and constituencies who are not regular
> participants on the IETF list should immediately trigger a state
> in which all further statements from that "side" would be
> ignored or would end the discussion entirely?
>=20
> Yes, I see the difficulties in figuring out the details of such
> a rule and implementing it and am mostly joking.   Mostly.

I support this.=20

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
YOW!!  Everybody out of the GENETIC POOL!

--xXmbgvnjoT4axfJE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iEYEARECAAYFAk89Dg0ACgkQ02/pMZDM1cX8ZgCgi9VNRCXYfIGhCllIo1Qj40vh
/54AmwXDCy0naSBGJlIc5Izt3qHGF8hN
=kcFH
-----END PGP SIGNATURE-----

--xXmbgvnjoT4axfJE--

From ynir@checkpoint.com  Thu Feb 16 06:13:16 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E3C921F86FE for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.312
X-Spam-Level: 
X-Spam-Status: No, score=-10.312 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7oUHFPFL+koc for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:13:15 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id BEFBF21F86A6 for <ietf@ietf.org>; Thu, 16 Feb 2012 06:13:14 -0800 (PST)
X-CheckPoint: {4F3D0B11-1-1B221DC2-1FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q1GED7bK002569;  Thu, 16 Feb 2012 16:13:07 +0200
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 16 Feb 2012 16:13:07 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 16 Feb 2012 16:13:07 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Date: Thu, 16 Feb 2012 16:13:09 +0200
Subject: Re: IETF Last Calls and Godwin-like rules
Thread-Topic: IETF Last Calls and Godwin-like rules
Thread-Index: AczstRqUNBVx2ZbDSbGu9w+m9GhrIA==
Message-ID: <01E3BA65-42A3-47EE-B09D-9144AD981FD6@checkpoint.com>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM> <20120216140917.GB9972@besserwisser.org>
In-Reply-To: <20120216140917.GB9972@besserwisser.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:13:16 -0000

On Feb 16, 2012, at 4:09 PM, M=E5ns Nilsson wrote:

> Subject: IETF Last Calls and Godwin-like rules Date: Thu, Feb 16, 2012 at=
 09:04:03AM -0500 Quoting John C Klensin (john-ietf@jck.com):
>=20
> ...
>=20
>> first appearance of many no-information "I support this"
>> endorsements from people and constituencies who are not regular
>> participants on the IETF list should immediately trigger a state
>> in which all further statements from that "side" would be
>> ignored or would end the discussion entirely?
>>=20
>> Yes, I see the difficulties in figuring out the details of such
>> a rule and implementing it and am mostly joking.   Mostly.
>=20
> I support this.=20

+1=

From dhc@dcrocker.net  Thu Feb 16 06:24:06 2012
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 3C78621F8705 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level: 
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RwD1MRs1kPXR for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:24:02 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1895521F86EF for <ietf@ietf.org>; Thu, 16 Feb 2012 06:24:02 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1GENuel004618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Feb 2012 06:24:01 -0800
Message-ID: <4F3D117A.1060404@dcrocker.net>
Date: Thu, 16 Feb 2012 06:23:54 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM> <20120216140917.GB9972@besserwisser.org>
In-Reply-To: <20120216140917.GB9972@besserwisser.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 16 Feb 2012 06:24:02 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:24:06 -0000

On 2/16/2012 6:09 AM, Måns Nilsson wrote:
>> Yes, I see the difficulties in figuring out the details of such
>> a rule and implementing it and am mostly joking.   Mostly.
>
> I support this.


You support the joking?

Or is it that you support vague rules that are unenforceable and will generate 
more heat than light?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ynir@checkpoint.com  Thu Feb 16 06:34:55 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7400721F865D for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.465
X-Spam-Level: 
X-Spam-Status: No, score=-10.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUyUpIWHMJ8A for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:34:54 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 58B2B21F8648 for <ietf@ietf.org>; Thu, 16 Feb 2012 06:34:54 -0800 (PST)
X-CheckPoint: {4F3D1024-0-1B221DC2-1FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q1GEYqY8009078;  Thu, 16 Feb 2012 16:34:52 +0200
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 16 Feb 2012 16:34:52 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 16 Feb 2012 16:34:51 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: John C Klensin <john-ietf@jck.com>
Date: Thu, 16 Feb 2012 16:34:53 +0200
Subject: Re: IETF Last Calls and Godwin-like rules
Thread-Topic: IETF Last Calls and Godwin-like rules
Thread-Index: AczsuCQLiL6gV5iOQjypxRpxPl6+4w==
Message-ID: <2FEED975-B133-4BD8-9187-DFD6B17F7A73@checkpoint.com>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
In-Reply-To: <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:34:55 -0000

On Feb 16, 2012, at 4:04 PM, John C Klensin wrote:

> A current Last Call has apparently brought on another of the
> "please tell all your friends to send in supportive notes, even
> if they don't say much of anything substantive" campaigns that
> we see from time to time.  When those notes come from people who
> do not routinely participate on IETF lists, they provide very
> little real information unless we have suddenly taken up voting
> or otherwise counting notes.  Whatever we might otherwise think
> of company positions, a note that said "I work for <xyz> and we
> need this and intend to implement and deploy it" would be real
> information that the community could consider where "I am an
> individual and +1" does not.   Sadly, such endorsements,
> especially from people who are not active IETF participants, add
> to the noise and might prevent someone who was still genuinely
> trying to understand the pros and cons (presumably including all
> of the IESG) from seeing a new and substantive argument, no
> matter how well-grounded.
>=20
> I note that there are some folks in the community who seem to
> favor these campaigns when they like the cause and not if they
> do not.
>=20
> But I wonder whether, in the interest of noise reduction and/or
> support of our "no voting, even by active participants"
> position, there be any sympathy for a Godwin-like rule that the
> first appearance of many no-information "I support this"
> endorsements from people and constituencies who are not regular
> participants on the IETF list should immediately trigger a state
> in which all further statements from that "side" would be
> ignored or would end the discussion entirely?
>=20
> Yes, I see the difficulties in figuring out the details of such
> a rule and implementing it and am mostly joking.   Mostly.

Because we don't vote, the show of support with all the +1s really doesn't =
amount to much. I don't think even promises to implement carry much weight =
at last call. By the time some proposal has gone to last call, especially I=
ETF last call, the issue of whether this will be useful to someone should h=
ave already been settled.

I think that an endorsement like "I work for Cisco and we intend to impleme=
nt this in every one of our products" is useful. But it's not nearly as use=
ful as "this is a terrible idea, and doing this will prevent IPv6 from ever=
 gaining traction". The objections raised in last call are really the point=
, not the endorsements.

Yoav



From rogerj@gmail.com  Thu Feb 16 06:48:37 2012
Return-Path: <rogerj@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 7639321F86C8 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:48:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.09
X-Spam-Level: 
X-Spam-Status: No, score=-3.09 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bcx54cmS+3KF for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 06:48:33 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id DAA9621F86A6 for <ietf@ietf.org>; Thu, 16 Feb 2012 06:48:32 -0800 (PST)
Received: by lahl5 with SMTP id l5so2905059lah.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 06:48:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=HpMo3lxnt1G0eGsHXp8+obN5f+QdHwd7J2VWtxRP+TU=; b=T+nUU/rZH9Kd/9XIIB7rQffGdSHbuo7mIWYhZk+1Y72y8O/I5erspPINusC6wAQN9D 8k76Dy3blOB43BXz1H4+T7jXvCJhC0sqimFXCcf+/uRkO2o70aYwHOuTGtb3v/h8BSjU Kd7ul94PEhZi4i2plzQ2YktomxPOlbjUvHoSo=
MIME-Version: 1.0
Received: by 10.152.108.49 with SMTP id hh17mr2055903lab.0.1329403710919; Thu, 16 Feb 2012 06:48:30 -0800 (PST)
Received: by 10.112.27.169 with HTTP; Thu, 16 Feb 2012 06:48:30 -0800 (PST)
In-Reply-To: <2FEED975-B133-4BD8-9187-DFD6B17F7A73@checkpoint.com>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM> <2FEED975-B133-4BD8-9187-DFD6B17F7A73@checkpoint.com>
Date: Thu, 16 Feb 2012 15:48:30 +0100
Message-ID: <CAKFn1SG2mAgZeH1woH0NDj7Ry59Apoei==4UE+TObH=XaQTJTQ@mail.gmail.com>
Subject: Re: IETF Last Calls and Godwin-like rules
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:48:37 -0000

On Thu, Feb 16, 2012 at 3:34 PM, Yoav Nir <ynir@checkpoint.com> wrote:
<snip>
> I think that an endorsement like "I work for Cisco and we intend to imple=
ment this in every one of our products" is useful. But it's not nearly as u=
seful as "this is a terrible idea, and doing this will prevent IPv6 from ev=
er gaining traction". The objections raised in last call are really the poi=
nt, not the endorsements.


Think I've read somewhere that the ground of good engineering (the E
in IETF) are being able to argue against your own idea, search and
look for flaws in it, and all in the name of testing it to see how it
can be made even better, is it good enough? Or simple to consider the
bigger picture, can my idea hurt the rest no matter how good it is?
There are great and very good ideas out there that isolated are
fantastic, but considered in just a bit bigger picture are horrible,
they've ruin everything around them.

So, when lots of people are all for something without mention or
willing to discusse the bad sides... that's scary as I see it.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From ynir@checkpoint.com  Thu Feb 16 07:12:38 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F01521F83EF for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.321
X-Spam-Level: 
X-Spam-Status: No, score=-10.321 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVfquV9rLi3h for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:12:37 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id BC73021F87F4 for <ietf@ietf.org>; Thu, 16 Feb 2012 07:12:30 -0800 (PST)
X-CheckPoint: {4F3D18D8-0-1B221DC2-1FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q1GFBxdY019754;  Thu, 16 Feb 2012 17:11:59 +0200
Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 16 Feb 2012 17:11:58 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Thu, 16 Feb 2012 17:11:58 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: =?iso-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
Date: Thu, 16 Feb 2012 17:12:01 +0200
Subject: Re: IETF Last Calls and Godwin-like rules
Thread-Topic: IETF Last Calls and Godwin-like rules
Thread-Index: AczsvVODIoNUJd07T+uHUBTuAuHVpQ==
Message-ID: <9BBAF712-D199-4950-A516-33C830756BEC@checkpoint.com>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM> <2FEED975-B133-4BD8-9187-DFD6B17F7A73@checkpoint.com> <CAKFn1SG2mAgZeH1woH0NDj7Ry59Apoei==4UE+TObH=XaQTJTQ@mail.gmail.com>
In-Reply-To: <CAKFn1SG2mAgZeH1woH0NDj7Ry59Apoei==4UE+TObH=XaQTJTQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:12:38 -0000

On Feb 16, 2012, at 4:48 PM, Roger J=F8rgensen wrote:

> On Thu, Feb 16, 2012 at 3:34 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> <snip>
>> I think that an endorsement like "I work for Cisco and we intend to impl=
ement this in every one of our products" is useful. But it's not nearly as =
useful as "this is a terrible idea, and doing this will prevent IPv6 from e=
ver gaining traction". The objections raised in last call are really the po=
int, not the endorsements.
>=20
>=20
> Think I've read somewhere that the ground of good engineering (the E
> in IETF) are being able to argue against your own idea, search and
> look for flaws in it, and all in the name of testing it to see how it
> can be made even better, is it good enough? Or simple to consider the
> bigger picture, can my idea hurt the rest no matter how good it is?
> There are great and very good ideas out there that isolated are
> fantastic, but considered in just a bit bigger picture are horrible,
> they've ruin everything around them.

I agree. IPv4 forever using CGNs may work for a lot of people and a lot of =
uses. If people remain double- or triple-natted it won't matter a bit to th=
e big web sites.=20

It's far more important to hear what is not going to work with this solutio=
n.

It's great if you can find such deficiencies in your own ideas, but we stil=
l need design reviews, code reviews, QA departments and IETF last calls so =
that others can get at your idea.=

From jnc@mercury.lcs.mit.edu  Thu Feb 16 07:33:20 2012
Return-Path: <jnc@mercury.lcs.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 EADA221F86AB for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:33:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.418
X-Spam-Level: 
X-Spam-Status: No, score=-6.418 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RgVBVxom6Ytd for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:33:19 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBD121F8657 for <ietf@ietf.org>; Thu, 16 Feb 2012 07:33:19 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 29DBE18C0A7; Thu, 16 Feb 2012 10:33:18 -0500 (EST)
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
Message-Id: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu>
Date: Thu, 16 Feb 2012 10:33:18 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:33:20 -0000

    > From: John C Klensin <john-ietf@jck.com>

    > When those notes come from people who do not routinely participate on
    > IETF lists

Well, that's the $64 million question, right? I mean, I don't personally
subscribe to every IETF-related list, so I have no idea if the people who are
posting are active in some subset of the IETF, just not (previously) this
list. And does someone have to have spoken up on a list, to have just as much
right to an opinion as a frequent poster? Some people are just naturally quiet.

I'd say that if anyone has been subscribed to any IETF list _prior_ to the
call to 'join in', their opinion ought to have just as much weight as those
of us who have historically been more wordy on the main list.

	Noel

From cgrundemann@gmail.com  Thu Feb 16 07:43:19 2012
Return-Path: <cgrundemann@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 667BE21F85DA for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.669
X-Spam-Level: 
X-Spam-Status: No, score=-3.669 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qnQwcVyW0yBq for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:43:14 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id C46DA21F85AE for <ietf@ietf.org>; Thu, 16 Feb 2012 07:43:14 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2796215pbc.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 07:43:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=obGLsgEhJFB+mI6MxtOwtiqn6EOtmBusF8j04D5hFuE=; b=RnJsNXEqxnEaxpH5QTvyUtXsTa9q2bgtOgDe4KGlLTKEiY0ar8jNzDuDCnmUbAxByE sEK/zvdG6WN+BUob1TfcAatmwLyaYCLxbxTabcqLPjzJoM56Vpc6bGUIRVLBjd/jx2iH TWeWzTvsMWbart7OJ4tmxQ+LR94vDiZYbM9zo=
MIME-Version: 1.0
Received: by 10.68.193.232 with SMTP id hr8mr9278596pbc.158.1329406994627; Thu, 16 Feb 2012 07:43:14 -0800 (PST)
Received: by 10.68.60.200 with HTTP; Thu, 16 Feb 2012 07:43:14 -0800 (PST)
In-Reply-To: <1329388980.5382.44.camel@davinci.millnert.se>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se>
Date: Thu, 16 Feb 2012 08:43:14 -0700
Message-ID: <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: Martin Millnert <martin@millnert.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:43:19 -0000

On Thu, Feb 16, 2012 at 03:43, Martin Millnert <martin@millnert.se> wrote:

> This is 100% matched by an allocation of globally unique space from a
> RIR, shared by whoever the interested parties are.
> =A0The IETF *need not* specify any BCP on how to improve NAT444
> "CGN"-scale alone, because such action is attached with high risk of
> leading to a local maximum in a plot of the state of the Internet,
> rather than towards a global maximum.
>
> Citing RFC6264, "An Incremental Carrier-Grade NAT (CGN) for IPv6
> Transition" warns:
> =A0 Carrier-Grade NAT (CGN) [CGN-REQS], also called NAT444 CGN or Large
> =A0 Scale NAT, compounds IPv4 operational problems when used alone but
> =A0 does nothing to encourage IPv4 to IPv6 transition. =A0Deployment of
> =A0 NAT444 CGN allows ISPs to delay the transition and therefore causes
> =A0 double transition costs (once to add CGN and again to support IPv6).
>
> The draft as written, makes no effort to require the RFC6264 or
> equivalent approaches to a IPv6 transition, to the CGN deployments it
> specifies v4 address space for. All carrot, no stick.
> =A0I believe the state of the Internet would be much more reliably
> improved by the RIRs each having (for the purpose of being able to serve
> their own users) one /10 special allocation for this purpose, which they
> can assign to multiple users upon demonstrating, under contract, they
> are transitioning to IPv6 according to 6264, or equivalent.
>
> As written there is no effort to mitigate the risk mentioned in the
> quote above, and I can't support a draft that will hurt the Internet and
> neither should you.

Apologies for my bluntness, but this argument is a complete
misinterpretation of the facts on the ground. This draft is not about
encouraging nor facilitating CGN deployments. Allocating a /10 for
inside CGN addressing use _will not_ make anyone deploy CGN who would
not have otherwise done so. Not allocating a /10 for inside CGN
addressing use _will not_ stop anyone from deploying CGN who would
have otherwise done so. In fact, neither you nor I nor the IETF can
stop operators who must deploy CGN for business continuity from doing
so. What we can do, is ensure that when those folks who must deploy
CGN do so, that they break the Internet as little as possible. And
_that_ is what this I-D seeks to accomplish. And that is why I support
it, and why you should too.

Cheers,
~Chris


> Best,
> Martin
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



--=20
@ChrisGrundemann
http://chrisgrundemann.com

From cgrundemann@gmail.com  Thu Feb 16 07:55:38 2012
Return-Path: <cgrundemann@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 1986F21F8715 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYXcIdT0XLws for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:55:30 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id BDE8E21F864D for <ietf@ietf.org>; Thu, 16 Feb 2012 07:55:25 -0800 (PST)
Received: by dakl33 with SMTP id l33so2302733dak.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 07:55:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=/f0LVzVu7Sytiuu2jBqwKBG2GKmOzkvHZP7kTnxDQ1c=; b=D5YmqTinZrbhkJUN7QlPSxBFg34rYMzQMtftQPIW4K/d2Ed9/ZOfCQQrp0gQhvv1Vh D6zU8OSfL/ngVTCSDGGXVfFH5UVv4S0HE6Pu+9oAcXLh9ZYT+10dpdY6qQ91nZoRBekh yhTk7icbQJ017ax5D9Zu8Xt59mFinKS+X2guA=
MIME-Version: 1.0
Received: by 10.68.216.195 with SMTP id os3mr9363406pbc.137.1329407725573; Thu, 16 Feb 2012 07:55:25 -0800 (PST)
Received: by 10.68.60.200 with HTTP; Thu, 16 Feb 2012 07:55:25 -0800 (PST)
In-Reply-To: <CAKFn1SGxzvNh_n09CaY5+Ke+s7Uq8nvX9H-TgN7QykouQ+nQUA@mail.gmail.com>
References: <8F9F107F1A51524597A5D2E0F43EE9632AD416BD28@PRVPEXVS09.corp.twcable.com> <CAKFn1SGxzvNh_n09CaY5+Ke+s7Uq8nvX9H-TgN7QykouQ+nQUA@mail.gmail.com>
Date: Thu, 16 Feb 2012 08:55:25 -0700
Message-ID: <CAC1-dtmpsWRZQ_QwO6CpdKGYo5++KWZU+mGxkB=cjYfPMd2okw@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP'
From: Chris Grundemann <cgrundemann@gmail.com>
To: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:55:38 -0000

On Thu, Feb 16, 2012 at 02:34, Roger J=F8rgensen <rogerj@gmail.com> wrote:
> not replying specific to this mail but to the tons that have arrived
> lately, are there some confusion out there that it is the amount of
> "votes" on ietf@ that make a do/do not on a draft? ... or just me
> missunderstanding this?

It is my understanding that the IETF operates in an open, bottom-up,
consensus-based manor and thus that all voices, taken in context, are
important in all decisions made.

> anyway, great to see people participate :-)

It is indeed.
~Chris


> --- Roger J ---
>
> Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
> rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
> http://www.jorgensen.no=A0=A0 | roger@jorgensen.no
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf



--=20
@ChrisGrundemann
http://chrisgrundemann.com

From akatlas@gmail.com  Thu Feb 16 07:59:34 2012
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 B0F9121F8546 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:59:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.207
X-Spam-Level: 
X-Spam-Status: No, score=-3.207 tagged_above=-999 required=5 tests=[AWL=0.392,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPhxhrAdrwF3 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 07:59:30 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 625CB21F84FE for <ietf@ietf.org>; Thu, 16 Feb 2012 07:59:30 -0800 (PST)
Received: by iagf6 with SMTP id f6so3688987iag.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 07:59:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=npfAzsYp/VdPNCfGhNUSCmnPg0DiGMAZz/kN72a0DLI=; b=vHZskqT13AOEKrncitAfOPE4BCkB4ch7xcuUV4YYNnYHa4dRS1D+904DAkuhtZ8Q4G wZi4ophWprsp6LlqCbKTPfIHmBURkFI4nyoqb4axWtnAMnXqGdGTbgKQwEN4rDL1K+fz JM+yCS7KwoqBVoOsUF13ecAkTrSEHIy4U2+NY=
MIME-Version: 1.0
Received: by 10.42.174.71 with SMTP id u7mr2869129icz.44.1329407970022; Thu, 16 Feb 2012 07:59:30 -0800 (PST)
Received: by 10.50.87.197 with HTTP; Thu, 16 Feb 2012 07:59:29 -0800 (PST)
In-Reply-To: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu>
References: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu>
Date: Thu, 16 Feb 2012 10:59:29 -0500
Message-ID: <CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8se9QXE2n=n7XQ@mail.gmail.com>
Subject: Re: IETF Last Calls and Godwin-like rules
From: Alia Atlas <akatlas@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:59:34 -0000

For what it is worth, those who I've seen commenting in the +1 fashion
recently are primarily people I've known to be active in the IETF for
years - including some WG chairs.

I don't think this is an effort to round up external voters - but
rather encouragement to others inside IETF to publicly speak up.

Alia

who usually doesn't post much on the general IETF list either

On Thu, Feb 16, 2012 at 10:33 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wr=
ote:
> =A0 =A0> From: John C Klensin <john-ietf@jck.com>
>
> =A0 =A0> When those notes come from people who do not routinely participa=
te on
> =A0 =A0> IETF lists
>
> Well, that's the $64 million question, right? I mean, I don't personally
> subscribe to every IETF-related list, so I have no idea if the people who=
 are
> posting are active in some subset of the IETF, just not (previously) this
> list. And does someone have to have spoken up on a list, to have just as =
much
> right to an opinion as a frequent poster? Some people are just naturally =
quiet.
>
> I'd say that if anyone has been subscribed to any IETF list _prior_ to th=
e
> call to 'join in', their opinion ought to have just as much weight as tho=
se
> of us who have historically been more wordy on the main list.
>
> =A0 =A0 =A0 =A0Noel
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From sm@resistor.net  Thu Feb 16 08:16:00 2012
Return-Path: <sm@resistor.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 3547A21F85E0 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.632
X-Spam-Level: 
X-Spam-Status: No, score=-103.632 tagged_above=-999 required=5 tests=[AWL=0.967, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WRaKlmeIn7N for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:15:54 -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 B290521F8546 for <ietf@ietf.org>; Thu, 16 Feb 2012 08:15:54 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1GGFmIt019743; Thu, 16 Feb 2012 08:15:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329408953; i=@resistor.net; bh=T7Ws+ZLrxJbLv0FOeqfZQcyViViVBEZyMJq0GleCmPM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=pAO+6fzqTT8yWNnct8+TbZ6qR1Pqigmkb/qjQXfMP0pFPN1nnM+24q+a1W13furTv 2oLW1lx7hQdAXErUq7w7PiuG186YVSxSYKauLhUavXA9mpCrjOf+givgMUoE7XycRH xuFPb4//oIofszF6S6Vzf/PXUaZ7PqtFjv8YN/7M=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329408953; i=@resistor.net; bh=T7Ws+ZLrxJbLv0FOeqfZQcyViViVBEZyMJq0GleCmPM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=auHH7iDMNDRwTXBSqh64PCDOtjusQCjnqZlCYCtUJQhzrU8HHhQrk4ANzXdiAx2DH ogLEB5EKRVrDkIzxEcp0kwIZYtttAoV6WHfDdkMGoCLhUJMGpDjIMIZQ6vcl5Vsgea zoYf4dHudBmodDKP8XlKG/nmLTF9VVRyvmYmDbA4=
Message-Id: <6.2.5.6.2.20120216063504.08854130@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 16 Feb 2012 07:46:52 -0800
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: IETF Last Calls and Godwin-like rules
In-Reply-To: <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:16:00 -0000

Hi John,
At 06:04 16-02-2012, John C Klensin wrote:
>A current Last Call has apparently brought on another of the
>"please tell all your friends to send in supportive notes, even
>if they don't say much of anything substantive" campaigns that
>we see from time to time.  When those notes come from people who
>do not routinely participate on IETF lists, they provide very
>little real information unless we have suddenly taken up voting

Letter-writing campaigns occur every now and then.  As there isn't 
any vote count, the effort can end up in a diluted form.

>individual and +1" does not.   Sadly, such endorsements,
>especially from people who are not active IETF participants, add
>to the noise and might prevent someone who was still genuinely
>trying to understand the pros and cons (presumably including all
>of the IESG) from seeing a new and substantive argument, no
>matter how well-grounded.

Last year, someone discussed about how a "+1" could be read and some 
people were offended.   Maybe authors should be given the choice to 
have their proposal evaluated by counting the votes or to have the 
evaluation which is based on substantive comments.  Nobody would be 
offended then.

Regards,
-sm 


From martin@millnert.se  Thu Feb 16 08:35:45 2012
Return-Path: <martin@millnert.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 8171921F876C for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BsjVrm1t5Zig for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:35:45 -0800 (PST)
Received: from ncis.csbnet.se (ncis.csbnet.se [95.80.1.101]) by ietfa.amsl.com (Postfix) with ESMTP id A0C3A21F86B3 for <ietf@ietf.org>; Thu, 16 Feb 2012 08:35:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id 6CA6B790; Thu, 16 Feb 2012 17:33:20 +0100 (CET)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U1kxeKyOOGi5; Thu, 16 Feb 2012 17:33:20 +0100 (CET)
Received: from [192.168.120.227] (h-189-4.a189.priv.bahnhof.se [85.24.189.4]) by ncis.csbnet.se (Postfix) with ESMTPSA id 23F1A2B0; Thu, 16 Feb 2012 17:33:20 +0100 (CET)
Message-ID: <1329410134.5382.72.camel@davinci.millnert.se>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Martin Millnert <martin@millnert.se>
To: Chris Grundemann <cgrundemann@gmail.com>
Date: Thu, 16 Feb 2012 17:35:34 +0100
In-Reply-To: <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-x282PsrsUjK06W8H8QTH"
X-Mailer: Evolution 3.0.3-3 
Mime-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:35:45 -0000

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

Dear Chris,

On Thu, 2012-02-16 at 08:43 -0700, Chris Grundemann wrote:
> On Thu, Feb 16, 2012 at 03:43, Martin Millnert <martin@millnert.se> wrote=
:
>=20
> > This is 100% matched by an allocation of globally unique space from a
> > RIR, shared by whoever the interested parties are.
> >  The IETF *need not* specify any BCP on how to improve NAT444
> > "CGN"-scale alone, because such action is attached with high risk of
> > leading to a local maximum in a plot of the state of the Internet,
> > rather than towards a global maximum.
> >
> > Citing RFC6264, "An Incremental Carrier-Grade NAT (CGN) for IPv6
> > Transition" warns:
> >   Carrier-Grade NAT (CGN) [CGN-REQS], also called NAT444 CGN or Large
> >   Scale NAT, compounds IPv4 operational problems when used alone but
> >   does nothing to encourage IPv4 to IPv6 transition.  Deployment of
> >   NAT444 CGN allows ISPs to delay the transition and therefore causes
> >   double transition costs (once to add CGN and again to support IPv6).
> >
> > The draft as written, makes no effort to require the RFC6264 or
> > equivalent approaches to a IPv6 transition, to the CGN deployments it
> > specifies v4 address space for. All carrot, no stick.
> >  I believe the state of the Internet would be much more reliably
> > improved by the RIRs each having (for the purpose of being able to serv=
e
> > their own users) one /10 special allocation for this purpose, which the=
y
> > can assign to multiple users upon demonstrating, under contract, they
> > are transitioning to IPv6 according to 6264, or equivalent.
> >
> > As written there is no effort to mitigate the risk mentioned in the
> > quote above, and I can't support a draft that will hurt the Internet an=
d
> > neither should you.
>=20
> Apologies for my bluntness, but this argument is a complete
> misinterpretation of the facts on the ground.=20

Taking:
   This draft is not about encouraging nor facilitating CGN deployments.=
=20
   Allocating a /10 for inside CGN addressing use _will not_ make anyone
   deploy CGN who would not have otherwise done so. Not allocating a /10
   for inside CGN addressing use _will not_ stop anyone from deploying
   CGN who would have otherwise done so.=20
+
   What we can do, is ensure that when those folks who must deploy
   CGN do so, that they break the Internet as little as possible. And
   _that_ is what this I-D seeks to accomplish.

you seem to be of the opinion that improving the feasibility of CGN, by
making it suck less, will not have any impact on potential set of
networks who are deploying it, or in what way they will deploy it.

You seem to want me to believe that:=20
  - there is a fixed set of networks, who are going to deploy either:
    - a sucky IPv4 network, or,=20
    - a less sucky IPv4 network,=20
  - it would be entirely depending on the passing of this draft,=20
  - the failure of passing of this draft somehow will exclude from these
networks the possibility of obtaining non-RFC1918 space in another way,
for example as I outlined

The latter two points seem a bit far-fetched.

I'm curious how you can possibly have sufficient knowledge to make those
statements as *facts*, rather than opinions, informed as the may be (but
of limited scope -- I think it unlikely you've spoken to every network
on the planet).

   In fact, neither you nor I nor the IETF can stop operators who must=20
   deploy CGN for business continuity from doing so.

I hold no such illusions.  What the IETF ought to do however, IMHO, is
to point them in a good direction. I don't see that happening in this
document.

A less-sucky IPv4-run-out access network is still a local maxima
compared to the global maxima of DS.
  Convince me that our journey to reach the global maxima will not be
negatively affected by this document, and gain my support.

Kind regards,
Martin

--=-x282PsrsUjK06W8H8QTH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

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

iQIcBAABAgAGBQJPPTBWAAoJEKgraNdZrwxMNNgP/1c2oMTr//v+ilhIgfpblVOw
VNOiRP1FnfvpKIyhGSLZPr3CocibcjQjHs6qdeCaMkaqEFTjsZ5ZJg3Lpup9SwiG
W5lzzrndLIAvTmfC6lSEg3KjA7Al6yfWzT9hPleLt/M6RjA71TBs5Sy6Ml++oefb
/AjvdNTk0ORQl/STKBDXifab99eK2965IVEqk7ZUEeQCQOBBKa+Tty84jBWly+vV
SjSWdK0qm1vnZSLhrH/tgo5jP+H1jBV70uqRvXZF7TvqyL6uo/SQHqiVcWa+8bhR
/RUnQIHMxfF2OdGJCr9+sgej2ek/Xu4iEOYlQ8X0mtm935hvUoLyfRf4ZKcoPXMG
FNwRuconR/ReN9iKVX0VQjCABSrb7Vm9QPbYbZDJmG8Y/U6qaNoByeV51Joxq0i6
ra17zGT78r6bYvekiiLYKFlmW+nfdf+o2IcdouZkFPt/aljhYYNLYgAQkgEMT7/v
t+Nx2P5+TIZBCDRYZU/1e99y5AgTZkSONBOhkZG1NKOZ07YsOqCU2E8jHvoC1fMr
IASsXFgzGWtgn/A5cXcdCDa4UKNMk1bQjBuOd27Bvt7QsP/Vwa7uyoeHS7Z9E/E+
174ShA7uORDIpyMSBFQEkFZBKTyWZD/wl2AKFqN9oxKTaKRCkedmtlDUFG3uyVyi
9bRmhxZkbcO/tz50NfpI
=SFTu
-----END PGP SIGNATURE-----

--=-x282PsrsUjK06W8H8QTH--


From sagriffith@gci.com  Wed Feb 15 12:13:32 2012
Return-Path: <sagriffith@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6CD21F8585 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 12:13: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=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AiNHHjzYj9jq for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 12:13:31 -0800 (PST)
Received: from mailgw1.gci.com (mailgw1.gci.com [209.165.141.90]) by ietfa.amsl.com (Postfix) with ESMTP id AF3FB21F8504 for <ietf@ietf.org>; Wed, 15 Feb 2012 12:13:31 -0800 (PST)
Received: from FNB1CAS01.gci.com (10.100.230.66) by mailgw1.gci.com (172.19.0.25) with Microsoft SMTP Server (TLS) id 8.2.234.1; Wed, 15 Feb 2012 11:14:03 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by FNB1CAS01.gci.com ([10.100.230.66]) with mapi; Wed, 15 Feb 2012 11:13:30 -0900
From: Scott A Griffith <sagriffith@gci.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 15 Feb 2012 11:13:29 -0900
Subject: draft-weil last call:  IANA Reserved IPv4 Prefix for Shared Address Space
Thread-Topic: draft-weil last call:  IANA Reserved IPv4 Prefix for Shared Address Space
Thread-Index: AczsHkjT1OHWG5AiQHWsVh0//NJPWA==
Message-ID: <CB6143D9.2DC4F%sagriffith@gci.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CB6143D92DC4Fsagriffithgcicom_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
X-Mailman-Approved-At: Thu, 16 Feb 2012 08:46:33 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:13:32 -0000

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

I support the current draft-weil as recently updated.  I believe the update=
d draft is more flexible, and would satisfy additional use cases that don't=
 work with RFC1918 space.

Thanks

Scott Griffith
GCI Product Manager
Anchorage, AK

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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); "><div =
style=3D"font-family: Calibri, sans-serif; font-size: 14px; "><span class=
=3D"Apple-style-span" style=3D"font-family: Consolas; font-size: medium; ">=
<span style=3D"font-family: Calibri; ">I support the current draft-weil as =
recently updated. &nbsp;I believe </span><span style=3D"font-family: Calibr=
i; ">the updated draft is more flexible, and would satisfy additional use c=
ases&nbsp;that don't work with RFC1918 space.</span></span></div><div style=
=3D"font-family: Calibri, sans-serif; font-size: 14px; "><span class=3D"App=
le-style-span" style=3D"font-family: Consolas; font-size: medium; "><span s=
tyle=3D"font-family: Calibri; "><br></span></span></div><div style=3D"font-=
family: Calibri, sans-serif; font-size: 14px; "><span class=3D"Apple-style-=
span" style=3D"font-family: Consolas; font-size: medium; "><span style=3D"f=
ont-family: Calibri; ">Thanks</span></span></div><div style=3D"font-family:=
 Calibri, sans-serif; font-size: 14px; "><span class=3D"Apple-style-span" s=
tyle=3D"font-family: Consolas; font-size: medium; "><span style=3D"font-fam=
ily: Calibri; "><br></span></span></div><div style=3D"font-family: Calibri,=
 sans-serif; font-size: 14px; "><span class=3D"Apple-style-span" style=3D"f=
ont-family: Consolas; font-size: medium; "><span style=3D"font-family: Cali=
bri; ">Scott Griffith</span></span></div><div style=3D"font-family: Calibri=
, sans-serif; font-size: 14px; "><span class=3D"Apple-style-span" style=3D"=
font-family: Consolas; font-size: medium; "><span style=3D"font-family: Cal=
ibri; ">GCI Product Manager</span></span></div><div style=3D"font-family: C=
alibri, sans-serif; font-size: 14px; "><span class=3D"Apple-style-span" sty=
le=3D"font-family: Consolas; font-size: medium; "><span style=3D"font-famil=
y: Calibri; ">Anchorage, AK</span></span></div></body></html>

--_000_CB6143D92DC4Fsagriffithgcicom_--

From d.sturek@att.net  Wed Feb 15 12:16:33 2012
Return-Path: <d.sturek@att.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 4FACD21F8649 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 12:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.329
X-Spam-Level: 
X-Spam-Status: No, score=0.329 tagged_above=-999 required=5 tests=[AWL=-0.328,  BAYES_20=-0.74, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVEoJNZAnhQH for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2012 12:16:29 -0800 (PST)
Received: from nm27-vm0.access.bullet.mail.sp2.yahoo.com (nm27-vm0.access.bullet.mail.sp2.yahoo.com [98.139.44.188]) by ietfa.amsl.com (Postfix) with SMTP id 712B021F863B for <ietf@ietf.org>; Wed, 15 Feb 2012 12:16:29 -0800 (PST)
Received: from [98.139.44.100] by nm27.access.bullet.mail.sp2.yahoo.com with NNFMP; 15 Feb 2012 20:16:25 -0000
Received: from [98.139.44.74] by tm5.access.bullet.mail.sp2.yahoo.com with NNFMP; 15 Feb 2012 20:16:25 -0000
Received: from [127.0.0.1] by omp1011.access.mail.sp2.yahoo.com with NNFMP; 15 Feb 2012 20:16:25 -0000
X-Yahoo-Newman-Id: 15733.11521.bm@omp1011.access.mail.sp2.yahoo.com
Received: (qmail 42811 invoked from network); 15 Feb 2012 20:16:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1329336984; bh=9//eMKfSrbNWWZ151e6QQ+tVmh5KDkiLvPWwfS16j+s=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic:Mime-version:Content-type; b=lWSusMSPqLdxo47UKeosHETE9eY6Sfy+DHryJeoUDgklpP75w0GT/lbDLkGuV6rV422jYmdboKHCFySu3MECYKoCfn6406iJlTLVLHhf2quevZXiS46+Uz6B7+Qh5gVbUWUX5IRj3PsrRIteaVSl/1wU/xky7N5OoC47CKl4jY8=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 1lBqAVsVM1l9crRbHCgjPcDn7gcgCKgHDV7IPhuyoPKJYv1 NaEBuQZgq.5fZYCJUjDAYFwsS3ReHZQv2OVMES9JKlUcRHwoP4wcxgpMlMVo dF5dxVLdGu_uMgNKzpQxU9qCk.Xd_4c_iMw9O.E8AfLAMCDpX0DrMfhhx4Xu zUjo8Q0Xnvkksc5hzWCpVpDUJ6dz6ppKTD4vMUk8F3CGcx064O6dV3laLn7g ac.rWpBN2sQvU9i6UE1jSGrLiKpdQVyo9Yu.vmyhHgcyqFhKj2VrlqpAAqzB SY5gsQXVKYGDPaeAWoPEjttDV8tpqJanU3DqK5HnkNXkV2IBZ5TcyLegPMeT mthcTUHaCkLdRG.fHPggkTT9AFTDUb4WYc5x6K.x0zLnTSk9dbv9nEeBrxAw 0sOCrhwigWCvgBdkO4ZejD3p9lbvcufkpuEmw6.YCxkAcaSRzRXh44xrLrKF NziU__FdvCAT9OTcRhWbOZZFnp1Po6EB0cLtTa0ACpNjZDWiWbEZdqo9Ufd7 f9VZYC6f_2poJ52sx_AG8vWfcv95Ecj2vQ_.suNO_mxE-
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
Received: from [10.1.1.133] (d.sturek@174.78.56.227 with login) by smtp106.sbc.mail.gq1.yahoo.com with SMTP; 15 Feb 2012 12:16:24 -0800 PST
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Wed, 15 Feb 2012 12:16:13 -0800
Subject: re:   [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
From: Don Sturek <d.sturek@att.net>
To: <ietf@ietf.org>
Message-ID: <CB61528D.105E5%d.sturek@att.net>
Thread-Topic: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3412152984_772512"
X-Mailman-Approved-At: Thu, 16 Feb 2012 08:46:33 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:16:33 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3412152984_772512
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

This is less a substantive comment but one more on process=8A=8A..

Here is the history of WGLC:

http://www.ietf.org/mail-archive/web/core/current/msg02427.html

http://www.ietf.org/mail-archive/web/core/current/msg01414.html

Here is the history:

http://datatracker.ietf.org/doc/draft-ietf-core-link-format/history/


A couple of points:
1)  I work in a commercial group (ZigBee Alliance) using IETF standards for
commercial deployment.  We have several work groups interested in CoAP but
were waiting for a stable version to determine whether it was usable or not
for their application (things like home automation, commercial automation).
We had assumed that since the original WGLC (rev =AD02) and since there were
multiple iterations on the document (see the history) that the document was
not final.
2)  The second WGLC was only 1 week in duration and occurred over the US
Thanksgiving holiday.  I completely missed that.  Even so, there were 3 mor=
e
revisions after that so not sure it was obvious that this was actually the
final WGLC for the document.

I mention the above since I think it would be useful to actually have a ful=
l
1 month last call on this document.  I think there were several of us that
were surprised by the referral of the document to the IESG and who were
planning to do a final review at WGLC (which apparently we missed=8A.).

Also, is it normal to have so many revisions after WGLC?   Having WGLC in
Jan. 2011 on rev =AD02 and then the version referred to IESG as rev =AD12 a yea=
r
later seems strange.

Thanks for your consideration,

Don Sturek





--B_3412152984_772512
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div>This is less a substantive c=
omment but one more on process&#8230;&#8230;..</div><div><br></div><div>Here=
 is the history of WGLC:</div><div><br></div><div><div style=3D"font-family: C=
onsolas; font-size: medium; "><a href=3D"http://www.ietf.org/mail-archive/web/=
core/current/msg02427.html">http://www.ietf.org/mail-archive/web/core/curren=
t/msg02427.html</a></div><div style=3D"font-family: Consolas; font-size: mediu=
m; "><br></div><div style=3D"font-family: Consolas; font-size: medium; "><a hr=
ef=3D"http://www.ietf.org/mail-archive/web/core/current/msg01414.html">http://=
www.ietf.org/mail-archive/web/core/current/msg01414.html</a></div></div><div=
 style=3D"font-family: Consolas; font-size: medium; "><br></div><div style=3D"fo=
nt-family: Consolas; font-size: medium; ">Here is the history:</div><div sty=
le=3D"font-family: Consolas; font-size: medium; "><br></div><div style=3D"font-f=
amily: Consolas; font-size: medium; "><a href=3D"http://datatracker.ietf.org/d=
oc/draft-ietf-core-link-format/history/">http://datatracker.ietf.org/doc/dra=
ft-ietf-core-link-format/history/</a></div><div style=3D"font-family: Consolas=
; font-size: medium; "><br></div><div style=3D"font-family: Consolas; font-siz=
e: medium; "><br></div><div style=3D"font-family: Consolas; font-size: medium;=
 ">A couple of points:</div><div style=3D"font-family: Consolas; font-size: me=
dium; ">1) &nbsp;I work in a commercial group (ZigBee Alliance) using IETF s=
tandards for commercial deployment. &nbsp;We have several work groups intere=
sted in CoAP but were waiting for a stable version to determine whether it w=
as usable or not for their application (things like home automation, commerc=
ial automation). &nbsp;We had assumed that since the original WGLC (rev &#82=
11;02) and since there were multiple iterations on the document (see the his=
tory) that the document was not final.</div><div style=3D"font-family: Consola=
s; font-size: medium; ">2) &nbsp;The second WGLC was only 1 week in duration=
 and occurred over the US Thanksgiving holiday. &nbsp;I completely missed th=
at. &nbsp;Even so, there were 3 more revisions after that so not sure it was=
 obvious that this was actually the final WGLC for the document.</div><div s=
tyle=3D"font-family: Consolas; font-size: medium; "><br></div><div style=3D"font=
-family: Consolas; font-size: medium; ">I mention the above since I think it=
 would be useful to actually have a full 1 month last call on this document.=
 &nbsp;I think there were several of us that were surprised by the referral =
of the document to the IESG and who were planning to do a final review at WG=
LC (which apparently we missed&#8230;.).</div><div style=3D"font-family: Conso=
las; font-size: medium; "><br></div><div style=3D"font-family: Consolas; font-=
size: medium; ">Also, is it normal to have so many revisions after WGLC? &nb=
sp; Having WGLC in Jan. 2011 on rev &#8211;02 and then the version referred =
to IESG as rev &#8211;12 a year later seems strange.</div><div style=3D"font-f=
amily: Consolas; font-size: medium; "><br></div><div style=3D"font-family: Con=
solas; font-size: medium; ">Thanks for your consideration,</div><div style=3D"=
font-family: Consolas; font-size: medium; "><br></div><div style=3D"font-famil=
y: Consolas; font-size: medium; ">Don Sturek</div><div style=3D"font-family: C=
onsolas; font-size: medium; "><br></div><div style=3D"font-family: Consolas; f=
ont-size: medium; "><br></div></body></html>

--B_3412152984_772512--



From gregory.mirsky@ericsson.com  Wed Feb 15 14:14:26 2012
Return-Path: <gregory.mirsky@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 521D021F85C4; Wed, 15 Feb 2012 14:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.423
X-Spam-Level: 
X-Spam-Status: No, score=-5.423 tagged_above=-999 required=5 tests=[AWL=-1.125, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dKwr1tiW1N71; Wed, 15 Feb 2012 14:14:24 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id A08F921F84D6; Wed, 15 Feb 2012 14:14:24 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id q1FMEADV022038 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Feb 2012 16:14:15 -0600
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.1.105]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Wed, 15 Feb 2012 17:14:11 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 15 Feb 2012 17:14:10 -0500
Subject: RE: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
Thread-Topic: Auth48 comments on draft-ietf-pwe3-static-pw-status-10
Thread-Index: Aczr89KtIVI7SxkNRWultcFx3Ew+SwAOetDg
Message-ID: <FE60A4E52763E84B935532D7D9294FF1322B42FE15@EUSAACMS0715.eamcs.ericsson.se>
References: <CB617B2B.23929%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CB617B2B.23929%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FE60A4E52763E84B935532D7D9294FF1322B42FE15EUSAACMS0715e_"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 16 Feb 2012 08:46:33 -0800
Cc: "pwe3-chairs@tools.ietf.org" <pwe3-chairs@tools.ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:14:26 -0000

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

Dear Matthew, Authors, et al.,
I think that new text of fourth para in Section 5.3 adds some confusion. If=
 intension is to stop sending 'all clear' after three one-second intervals =
went unacknowledged but before refresh timer expires then perhpas new text =
can be more explicit:
NEW:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however,
transmission will cease after 3 PW status messages have been sent at one se=
cond intervals and before refresh timer expires. A PW
status message of zero MAY be acknowledged as per the procedures described
in Section 5.3.1. If it is acknowledged, then a timer
value of zero MUST be used.  This SHOULD cause the PE sending the PW status
notification message with a PW status code equal to zero to stop sending
 and to continue normal operation.

    Regards,
        Greg

________________________________
From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Boc=
ci, Matthew (Matthew)
Sent: Wednesday, February 15, 2012 7:10 AM
To: pwe3@ietf.org; ietf@ietf.org
Cc: pwe3-chairs@tools.ietf.org; Stewart Bryant
Subject: [PWE3] Auth48 comments on draft-ietf-pwe3-static-pw-status-10

During Auth 48, the authors of draft-ietf-pwe3-static-pw-status found some =
issues with the acknowledgement procedures in Section 5.3 of the draft that=
 we feel should be addressed before publication. Since the draft has alread=
y been through WG and IETF last call, we would like to highlight the propos=
ed changes to the working group and solicit feedback.

Best regards,

Matthew

Section 5.3, 3rd paragraph:
Reason for change:
The current suggested default refresh timer value is too short to allow sca=
ling
to very large numbers of PWs while minimising the overhead. It is also inco=
nsistent
with the suggested default requested in an ACK packet. Therefore we suggest=
 increasing
the default to 600secs.

OLD: The suggested default value for the refresh timer is 30 seconds.

NEW: The suggested default value for the refresh timer is 600 seconds.



Section 5.3, 4th paragraph:
Reason for change:
The current text requires that a receiving PE must acknowledge a PW status =
message
of 'clear all faults' in order to force a transmitter to stop sending PW st=
atus
messages at 1 second intervals.  We are concerned that a mandatory acknowle=
dgement
adds an unnecessary complexity to the protocol which is inconsistent with
the use of the acknowledgement as per the following section (5.3.1). Additi=
onally,
we are also concerned that this may cause problems if a transmitter
is flapping between 'clear all faults' and a non-zero value, and if the
acknowledgement is lost. We therefore suggest that the acknowledgement to
'clear all faults' be made optional, and that  the transmitter behavior be =
changed so
that it sends up to 3 status messages of zero in a row, and then goes silen=
t.

OLD:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however, it MUST be
acknowledged with a packet with a timer value of zero.  This will cause
the PE sending the PW status notification message with a PW status code
equal to zero to stop sending and to continue normal operation.


NEW:
To clear a particular status fault, the PE need only send an
updated message with the corresponding bit cleared.  If the PW status
code is zero, the PW OAM message will be sent like any other PW OAM
status message using the procedures described above; however,
transmission will cease after 3 PW status messages have been sent. A PW
status message of zero MAY be acknowledged as per the procedures described
in Section 5.3.1. If it is acknowledged, then a timer
value of zero MUST be used.  This SHOULD cause the PE sending the PW status
notification message with a PW status code equal to zero to stop sending
 and to continue normal operation.


Section 5.3.1, 1st paragraph:
Reason for change:
The procedures currently defined in this paragraph can lead to a receiver
of the static status message timing out if it requests, throught the use of=
 the
ACK mechanism, a longer refresh timer from the transmitter. This is because=
 the
current text implies that the transmitter change its referesh timer immedia=
tely
on receipt of the ack packet from the receiver. The new text clarifies that
the refresh timer be updated at the end of the current refresh interval, as
well as making some other editorial clarifications.

OLD:
The PE receiving a PW OAM message containing a PW status message
can acknowledge the PW status message by simply building an almost
identical reply packet with the A bit set, and transmitting it on the PW
ACH back to the source of the PW status message.  The timer value set in
the reply packet SHOULD then be used by the PE as the new transmit
interval.  If the transmitting PE does not want to use the new timer
value (for local policy reasons, or because it simply cannot support
it), it MUST refresh the PW OAM message with the timer value it desires.
The receiving PE will then set its timeout timer according to the timer
value that is in the packet received, regardless of what timer value it
sent.  The receiving PE MUST NOT retry to set the timer value more than
once per timer value.

NEW:
A PE receiving a PW OAM message containing a PW status message MAY
acknowledge the PW status message by simply building a reply packet
with the same format and status code as the received PW OAM message,
but with the A bit set, and transmitting it on the PW ACh back
to the source of the PW OAM message.  The receiving PE MAY use the
refresh timer field in the acknowledgement packet to request a new
refresh interval from the originator of the PW OAM message. The timer
value set in the reply packet SHOULD then be used by the originator of
the PW OAM message as the new transmit interval.  If the requested
refresh timer value is used, the PW OAM message transmission interval is
only set to the new value and the new value sent in the next PW OAM
message, when the current timer expires. If the transmitting PE does not
want to use the new timer value (for local policy reasons, or because it
simply cannot support it), it MUST refresh the PW OAM message with the
timer value it desires. The receiving PE will then set its timeout timer
according to the new refresh timer value that is in the packet received,
regardless of what timer value it requested.  The receiving PE MUST NOT
request a new refresh timer value more than once per refresh interval.


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6002.18538" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"FONT-SIZE: 14px; COLOR: rgb(0,0,0); FONT-FAMILY: Calibri, sans-ser=
if; WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: af=
ter-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D153090422-15022012><FONT face=3DA=
rial=20
size=3D2>Dear Matthew, Authors, et al.,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D153090422-15022012><FONT face=3DA=
rial size=3D2>I=20
think that new text of fourth para in Section 5.3 adds some confusion. If=20
intension is to stop sending 'all clear' after three one-second intervals w=
ent=20
unacknowledged but before refresh timer expires then perhpas new text can b=
e=20
more explicit:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D153090422-15022012>
<DIV>NEW:&nbsp;</DIV>
<DIV>To clear a particular status fault, the PE need only send an</DIV>
<DIV>updated message with the corresponding bit cleared. &nbsp;If the PW=20
status</DIV>
<DIV>code is zero, the PW OAM message will be sent like any other PW OAM</D=
IV>
<DIV>status message using the procedures described above; however,</DIV>
<DIV>transmission will cease after 3 PW status messages have been sent<SPAN=
=20
class=3D153090422-15022012> <EM><U>at one second intervals and before refre=
sh=20
timer expires</U></EM></SPAN>. A PW</DIV>
<DIV>status message of zero MAY be acknowledged as per the procedures=20
described&nbsp;</DIV>
<DIV>in Section 5.3.1. If it is acknowledged, then a timer</DIV>
<DIV>value of zero MUST be used. &nbsp;This SHOULD cause the PE sending the=
 PW=20
status</DIV>
<DIV>notification message with a PW status code equal to zero to stop=20
sending</DIV>
<DIV>&nbsp;and to continue normal operation.</DIV></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D153090422-15022012><FONT=20
size=3D4></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D153090422-15022012>&nbsp;&nbsp;&n=
bsp; <FONT=20
face=3DArial size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN=20
class=3D153090422-15022012>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT=
=20
face=3DArial size=3D2>Greg</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> pwe3-bounces@ietf.org=20
[mailto:pwe3-bounces@ietf.org] <B>On Behalf Of </B>Bocci, Matthew=20
(Matthew)<BR><B>Sent:</B> Wednesday, February 15, 2012 7:10 AM<BR><B>To:</B=
>=20
pwe3@ietf.org; ietf@ietf.org<BR><B>Cc:</B> pwe3-chairs@tools.ietf.org; Stew=
art=20
Bryant<BR><B>Subject:</B> [PWE3] Auth48 comments on=20
draft-ietf-pwe3-static-pw-status-10<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>
<DIV>
<DIV>During Auth 48, the authors of draft-ietf-pwe3-static-pw-status found =
some=20
issues with the acknowledgement procedures in Section 5.3 of the draft that=
 we=20
feel should be addressed before publication. Since the draft has already be=
en=20
through WG and IETF last call, we would like to highlight the proposed chan=
ges=20
to the working group and solicit feedback.</DIV>
<DIV><BR></DIV>
<DIV>
<DIV>Best regards,</DIV>
<DIV><BR></DIV>
<DIV>Matthew</DIV></DIV></DIV>
<DIV><BR></DIV>
<DIV>Section 5.3, 3rd paragraph:</DIV>
<DIV>Reason for change:</DIV>
<DIV>The current suggested default refresh timer value is too short to allo=
w=20
scaling&nbsp;</DIV>
<DIV>to very large numbers of PWs while minimising the overhead. It is also=
=20
inconsistent</DIV>
<DIV>with the suggested default requested in an ACK packet. Therefore we su=
ggest=20
increasing</DIV>
<DIV>the default to 600secs.</DIV>
<DIV><BR></DIV>
<DIV>OLD: The suggested default value for the refresh timer is 30 seconds.<=
/DIV>
<DIV><BR></DIV>
<DIV>NEW: The suggested default value for the refresh timer is 600=20
seconds.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>Section 5.3, 4th paragraph:</DIV>
<DIV>Reason for change:</DIV>
<DIV>The current text requires that a receiving PE must acknowledge a PW st=
atus=20
message</DIV>
<DIV>of 'clear all faults' in order to force a transmitter to stop sending =
PW=20
status</DIV>
<DIV>messages at 1 second intervals. &nbsp;We are concerned that a mandator=
y=20
acknowledgement</DIV>
<DIV>adds an unnecessary complexity to the protocol which is inconsistent=20
with</DIV>
<DIV>the use of the acknowledgement as per the following section (5.3.1).=20
Additionally,</DIV>
<DIV>we are also concerned that this may cause problems if a=20
transmitter&nbsp;</DIV>
<DIV>is flapping between 'clear all faults' and a non-zero value, and if=20
the&nbsp;</DIV>
<DIV>acknowledgement is lost. We therefore&nbsp;suggest that the acknowledg=
ement=20
to&nbsp;</DIV>
<DIV>'clear all faults' be made optional, and that &nbsp;the transmitter=20
behavior be changed so&nbsp;</DIV>
<DIV>that it sends up to 3 status messages of&nbsp;zero in a row, and then =
goes=20
silent.</DIV>
<DIV><BR></DIV>
<DIV>OLD:&nbsp;</DIV>
<DIV>To clear a particular status fault, the PE need only send an</DIV>
<DIV>updated message with the corresponding bit cleared. &nbsp;If the PW=20
status</DIV>
<DIV>code is zero, the PW OAM message will be sent like any other PW OAM</D=
IV>
<DIV>status message using the procedures described above; however, it MUST=
=20
be</DIV>
<DIV>acknowledged with a packet with a timer value of zero. &nbsp;This will=
=20
cause</DIV>
<DIV>the PE sending the PW status notification message with a PW status=20
code</DIV>
<DIV>equal to zero to stop sending and to continue normal operation.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>NEW:&nbsp;</DIV>
<DIV>To clear a particular status fault, the PE need only send an</DIV>
<DIV>updated message with the corresponding bit cleared. &nbsp;If the PW=20
status</DIV>
<DIV>code is zero, the PW OAM message will be sent like any other PW OAM</D=
IV>
<DIV>status message using the procedures described above; however,</DIV>
<DIV>transmission will cease after 3 PW status messages have been sent. A=20
PW</DIV>
<DIV>status message of zero MAY be acknowledged as per the procedures=20
described&nbsp;</DIV>
<DIV>in Section 5.3.1. If it is acknowledged, then a timer</DIV>
<DIV>value of zero MUST be used. &nbsp;This SHOULD cause the PE sending the=
 PW=20
status</DIV>
<DIV>notification message with a PW status code equal to zero to stop=20
sending</DIV>
<DIV>&nbsp;and to continue normal operation.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>Section 5.3.1, 1st paragraph:</DIV>
<DIV>Reason for change:</DIV>
<DIV>The procedures currently defined in this paragraph can lead to a=20
receiver</DIV>
<DIV>of the static status message timing out if it requests, throught the u=
se of=20
the</DIV>
<DIV>ACK mechanism, a longer refresh timer from the transmitter. This is be=
cause=20
the</DIV>
<DIV>current text implies that the transmitter change its referesh timer=20
immediately</DIV>
<DIV>on receipt of the ack packet from the receiver. The new text clarifies=
=20
that&nbsp;</DIV>
<DIV>the refresh timer be updated at the end of the current refresh interva=
l,=20
as&nbsp;</DIV>
<DIV>well as making some other editorial clarifications.</DIV>
<DIV><BR></DIV>
<DIV>OLD:&nbsp;</DIV>
<DIV>The PE receiving a PW OAM message containing a PW status message</DIV>
<DIV>can acknowledge the PW status message by simply building an almost</DI=
V>
<DIV>identical reply packet with the A bit set, and transmitting it on the=
=20
PW</DIV>
<DIV>ACH back to the source of the PW status message. &nbsp;The timer value=
 set=20
in</DIV>
<DIV>the reply packet SHOULD then be used by the PE as the new transmit</DI=
V>
<DIV>interval. &nbsp;If the transmitting PE does not want to use the new=20
timer</DIV>
<DIV>value (for local policy reasons, or because it simply cannot support</=
DIV>
<DIV>it), it MUST refresh the PW OAM message with the timer value it=20
desires.</DIV>
<DIV>The receiving PE will then set its timeout timer according to the=20
timer</DIV>
<DIV>value that is in the packet received, regardless of what timer value=20
it</DIV>
<DIV>sent. &nbsp;The receiving PE MUST NOT retry to set the timer value mor=
e=20
than</DIV>
<DIV>once per timer value.</DIV>
<DIV><BR></DIV>
<DIV>NEW:&nbsp;</DIV>
<DIV>A PE receiving a PW OAM message containing a PW status message MAY</DI=
V>
<DIV>acknowledge the PW status message by simply building a reply=20
packet&nbsp;</DIV>
<DIV>with the same format and status code as the received PW OAM message,</=
DIV>
<DIV>but with the A bit set, and transmitting it on the PW ACh back</DIV>
<DIV>to the source of the PW OAM message. &nbsp;The receiving PE MAY use=20
the</DIV>
<DIV>refresh timer field in the acknowledgement packet to request a new</DI=
V>
<DIV>refresh interval from the originator of the PW OAM message. The timer<=
/DIV>
<DIV>value set in the reply packet SHOULD then be used by the originator=20
of</DIV>
<DIV>the PW OAM message as the new transmit interval. &nbsp;If the=20
requested</DIV>
<DIV>refresh timer value is used, the PW OAM message transmission interval=
=20
is</DIV>
<DIV>only set to the new value and the new value sent in the next PW OAM</D=
IV>
<DIV>message, when the current timer expires. If the transmitting PE does=20
not</DIV>
<DIV>want to use the new timer value (for local policy reasons, or because=
=20
it</DIV>
<DIV>simply cannot support it), it MUST refresh the PW OAM message with=20
the</DIV>
<DIV>timer value it desires. The receiving PE will then set its timeout=20
timer</DIV>
<DIV>according to the new refresh timer value that is in the packet=20
received,</DIV>
<DIV>regardless of what timer value it requested. &nbsp;The receiving PE MU=
ST=20
NOT</DIV>
<DIV>request a new refresh timer value more than once per refresh=20
interval.</DIV>
<DIV><BR></DIV></DIV></BODY></HTML>

--_000_FE60A4E52763E84B935532D7D9294FF1322B42FE15EUSAACMS0715e_--

From melinda.shore@gmail.com  Thu Feb 16 08:49:20 2012
Return-Path: <melinda.shore@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 989BF21F87D5 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id llK8uTJk8RyF for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:49:19 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id A726521F8492 for <ietf@ietf.org>; Thu, 16 Feb 2012 08:49:19 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2860717pbc.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 08:49:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=57U6IFAsYYEk5fhgdeO3+jsLBy4XSVdgih8qwz0MH3A=; b=WWktaHxd5zgMmNC+fWGnlKiLp/WKg/65cGmKHEoNiTabUNV5qX70jYSG6/RzlE0uPq SAHD3J/u6Zs1xw+mYHJx+4kisKfDdsOakQNNMU8yY7/buanIEzF5fNymhRshp27mLvIT LZe6ZhutHm4V+zdmpCIeFh28pdyEs6tPLKVjw=
Received: by 10.68.73.138 with SMTP id l10mr15510677pbv.22.1329410959543; Thu, 16 Feb 2012 08:49:19 -0800 (PST)
Received: from polypro.local (209-193-56-188-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.56.188]) by mx.google.com with ESMTPS id q10sm14291529pbb.10.2012.02.16.08.49.17 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 16 Feb 2012 08:49:18 -0800 (PST)
Message-ID: <4F3D338B.8000203@gmail.com>
Date: Thu, 16 Feb 2012 07:49:15 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.26) Gecko/20120129 Lightning/1.0b2 Thunderbird/3.1.18
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu> <CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8se9QXE2n=n7XQ@mail.gmail.com>
In-Reply-To: <CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8se9QXE2n=n7XQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:49:20 -0000

On 2/16/12 6:59 AM, Alia Atlas wrote:
> For what it is worth, those who I've seen commenting in the +1 fashion
> recently are primarily people I've known to be active in the IETF for
> years - including some WG chairs.

I tend to be involved with different working groups from the ones
John is, and I've assumed (forgive me) that he's seeing something
somewhere that I'm not.  I've certainly seen the behavior he's
describing (flood of non-participants "voting").  I think there's
a difference between someone who's been contributing all along
participating in a consensus call by posting "+1" and someone
whom you can't tell whether or not actually read the draft posting
"+1" and it would be surprising indeed if the person responsible
for determining consensus (the chair) treated them as equal in
weight.

Actually, come to think of it, we've seen a certain amount of this
concerning the draft-weil-shared-transition-space-request draft.

Anyway, I take the situation that John's describing as annoying
but not an actual problem - we don't decide by voting.

Melinda

From nick@inex.ie  Thu Feb 16 08:58:12 2012
Return-Path: <nick@inex.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 5A82921F855F for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:58:12 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zt+3wOotIvyC for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 08:58:11 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id C669321F881A for <ietf@ietf.org>; Thu, 16 Feb 2012 08:58:07 -0800 (PST)
X-Envelope-To: <ietf@ietf.org>
Received: from cupcake.internal.acquirer.com (inet-gw.acquirer.com [87.198.142.10]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q1GGwqnV060204 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Feb 2012 16:58:53 GMT (envelope-from nick@inex.ie)
Message-ID: <4F3D359C.7020907@inex.ie>
Date: Thu, 16 Feb 2012 16:58:04 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com> <1329410134.5382.72.camel@davinci.millnert.se>
In-Reply-To: <1329410134.5382.72.camel@davinci.millnert.se>
X-Enigmail-Version: 1.3.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:58:12 -0000

On 16/02/2012 16:35, Martin Millnert wrote:
> You seem to want me to believe that: 
>   - there is a fixed set of networks, who are going to deploy either:
>     - a sucky IPv4 network, or, 
>     - a less sucky IPv4 network, 
>   - it would be entirely depending on the passing of this draft, 
>   - the failure of passing of this draft somehow will exclude from these
> networks the possibility of obtaining non-RFC1918 space in another way,
> for example as I outlined
> 
> The latter two points seem a bit far-fetched.

Martin,

Far-fetched - like all straw men.

> I'm curious how you can possibly have sufficient knowledge to make those
> statements as *facts*, rather than opinions, informed as the may be (but
> of limited scope -- I think it unlikely you've spoken to every network
> on the planet).

More straw men.  Look, we're adults here: please present good arguments.

The bottom line for this ID is that address space will be required for CGN,
and rfc1918 doesn't cut it for reasons described in the ID.  This means
that the address space must come from somewhere else.  The choices are:

1. one or more shared pools allocated by RIRs/IANA/whatever
2. private pools, each of which come from the carriers' own address blocks

option #1 is by definition more efficient than #2.

At least one of the RIRs has indicated that they cannot assign this space
due to charter problems.

There is no particular reason to allocate this space on a regional basis,
unless for some reason you believe that you can force carriers only to use
this shared address space for specific purposes - and I cannot see why you
think that this is remotely feasible for shared address space.  Private
address space, perhaps.  But certainly not shared address space.

The core function of a RIR is to guarantee that if they allocate you a
bunch of numbers, that they haven't allocated the same bunch of numbers to
someone else.  Therefore by definition they have no particular authority
over the way that shared address space might be used internally by a carrier.

Incidentally, I support this draft.

Nick

From cgrundemann@gmail.com  Thu Feb 16 09:09:30 2012
Return-Path: <cgrundemann@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 1A4FD21F8734 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.645
X-Spam-Level: 
X-Spam-Status: No, score=-3.645 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AL6az66r9FuW for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:09:25 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC6921F8732 for <ietf@ietf.org>; Thu, 16 Feb 2012 09:09:25 -0800 (PST)
Received: by dakl33 with SMTP id l33so2373382dak.31 for <ietf@ietf.org>; Thu, 16 Feb 2012 09:09:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=X/cVhK1S3wB/fNV0MRbnQq2o7ToDXisjfsdcMWZoXTY=; b=bTySIx3rrUZfrKP1uSaZcCHw1z/FBhNKUCfw7J9Uxo3qxBV8pDaGHk9jv04MVoUPIY p9SexAW2xMdf09oI8U5dMZ2iFCOHwojDmrMhgrCcqPei7vOsYJ9lSzzMDhpxBPjW1Mgi K4EQPNktS4XeiChqTc7ZkA4/0RRI86xyOgkO8=
MIME-Version: 1.0
Received: by 10.68.219.234 with SMTP id pr10mr15799019pbc.11.1329412165159; Thu, 16 Feb 2012 09:09:25 -0800 (PST)
Received: by 10.68.60.200 with HTTP; Thu, 16 Feb 2012 09:09:25 -0800 (PST)
In-Reply-To: <1329410134.5382.72.camel@davinci.millnert.se>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com> <1329410134.5382.72.camel@davinci.millnert.se>
Date: Thu, 16 Feb 2012 10:09:25 -0700
Message-ID: <CAC1-dt=Yb4y04vi9csX36MiC6eCsD8aT11BFARMvdeQ3nA+Yhg@mail.gmail.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Chris Grundemann <cgrundemann@gmail.com>
To: Martin Millnert <martin@millnert.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:09:30 -0000

On Thu, Feb 16, 2012 at 09:35, Martin Millnert <martin@millnert.se> wrote:
> Dear Chris,
>
> On Thu, 2012-02-16 at 08:43 -0700, Chris Grundemann wrote:
>> On Thu, Feb 16, 2012 at 03:43, Martin Millnert <martin@millnert.se> wrot=
e:
>>
>> > This is 100% matched by an allocation of globally unique space from a
>> > RIR, shared by whoever the interested parties are.
>> > =A0The IETF *need not* specify any BCP on how to improve NAT444
>> > "CGN"-scale alone, because such action is attached with high risk of
>> > leading to a local maximum in a plot of the state of the Internet,
>> > rather than towards a global maximum.
>> >
>> > Citing RFC6264, "An Incremental Carrier-Grade NAT (CGN) for IPv6
>> > Transition" warns:
>> > =A0 Carrier-Grade NAT (CGN) [CGN-REQS], also called NAT444 CGN or Larg=
e
>> > =A0 Scale NAT, compounds IPv4 operational problems when used alone but
>> > =A0 does nothing to encourage IPv4 to IPv6 transition. =A0Deployment o=
f
>> > =A0 NAT444 CGN allows ISPs to delay the transition and therefore cause=
s
>> > =A0 double transition costs (once to add CGN and again to support IPv6=
).
>> >
>> > The draft as written, makes no effort to require the RFC6264 or
>> > equivalent approaches to a IPv6 transition, to the CGN deployments it
>> > specifies v4 address space for. All carrot, no stick.
>> > =A0I believe the state of the Internet would be much more reliably
>> > improved by the RIRs each having (for the purpose of being able to ser=
ve
>> > their own users) one /10 special allocation for this purpose, which th=
ey
>> > can assign to multiple users upon demonstrating, under contract, they
>> > are transitioning to IPv6 according to 6264, or equivalent.
>> >
>> > As written there is no effort to mitigate the risk mentioned in the
>> > quote above, and I can't support a draft that will hurt the Internet a=
nd
>> > neither should you.
>>
>> Apologies for my bluntness, but this argument is a complete
>> misinterpretation of the facts on the ground.
>
> Taking:
> =A0 This draft is not about encouraging nor facilitating CGN deployments.
> =A0 Allocating a /10 for inside CGN addressing use _will not_ make anyone
> =A0 deploy CGN who would not have otherwise done so. Not allocating a /10
> =A0 for inside CGN addressing use _will not_ stop anyone from deploying
> =A0 CGN who would have otherwise done so.
> +
> =A0 What we can do, is ensure that when those folks who must deploy
> =A0 CGN do so, that they break the Internet as little as possible. And
> =A0 _that_ is what this I-D seeks to accomplish.
>
> you seem to be of the opinion that improving the feasibility of CGN, by
> making it suck less, will not have any impact on potential set of
> networks who are deploying it, or in what way they will deploy it.

Correct.

> You seem to want me to believe that:
> =A0- there is a fixed set of networks, who are going to deploy either:
> =A0 =A0- a sucky IPv4 network, or,
> =A0 =A0- a less sucky IPv4 network,
> =A0- it would be entirely depending on the passing of this draft,
> =A0- the failure of passing of this draft somehow will exclude from these
> networks the possibility of obtaining non-RFC1918 space in another way,
> for example as I outlined
>
> The latter two points seem a bit far-fetched.

Not quite, let me try again.

I am stating that:
 - Dual-Stack requires both IPv4 and IPv6 addresses
 - There is a non-zero number of networks which will exhaust all
available IPv4 resources before the world is able to fully transition
to IPv6
 - These networks must choose one of either:
  -- Go out of business
  -- Find a new way to provide IPv4 connections to customers
 - NAT44* CGN will be chosen by a non-zero number of these networks
 - This decision is independent of what addresses they will use inside
of the CGN (No one wants to go through two transitions. Folks who
deploy CGN do so because they must. As such, the addresses used are an
afterthought. The cost of CGN and it's alternatives are what drive the
decision, not this I-D or the addresses it seeks to reserve.)

> I'm curious how you can possibly have sufficient knowledge to make those
> statements as *facts*, rather than opinions, informed as the may be (but
> of limited scope -- I think it unlikely you've spoken to every network
> on the planet).

You are again correct, I have not spoken to every network on the
planet. I have spoken to many. Several in the Asia/Pacific region have
already experienced the chain of events I outlined above.

Further, my job is to understand the IPv6 transition and as such, much
of my time is dedicated to creating this understanding. I do not make
these claims lightly.

> =A0 In fact, neither you nor I nor the IETF can stop operators who must
> =A0 deploy CGN for business continuity from doing so.
>
> I hold no such illusions. =A0What the IETF ought to do however, IMHO, is
> to point them in a good direction. I don't see that happening in this
> document.
>
> A less-sucky IPv4-run-out access network is still a local maxima
> compared to the global maxima of DS.
> =A0Convince me that our journey to reach the global maxima will not be
> negatively affected by this document, and gain my support.

Once an operator has decided that they have no other choices remaining
and that they must deploy CGN, they then have to decide how to
architect that deployment. One of the architectural decisions to be
made (and the one we are concerned with here) is what addresses to use
within the CGN. They have several options:

- Globally Unique "Public" Addresses
This option burns addresses that they or others could use to number
devices that actually require a unique address, this is a net loss to
the Internet.

- RFC 1918 "Private" Addresses
The chance for collision and the low margins of residential broadband
make this option a non-starter. Nothing any of us say will convince
any substantial number of operators to shoot themselves in the foot in
this way.

- Class E Addresses
Too much equipment is hard coded to reject these addresses. It simply
will not work in time to make a difference.

- "Squat" Addresses
Without a shared address space, this is the likely winner. Squatting
on someone else's address space works and is free. A misconfigured
filter allows these to leak however, another net loss to an un-borked
Internet.

- "Shared" Addresses
This is the solution put forth in the I-D under discussion here. This
allows an alternative that is attractive to operators and can be
managed (since it is a known prefix). If one operator leaks routes,
others will have filters in place. This option removes the least
amount of addresses from the remaining free pools thus allowing
Dual-Stack to work in the most possible networks. All in all, this is
the best way to ensure a less broken Internet than any of the other
options can provide.

Again, we are not talking about encouraging or discouraging CGN use,
that is outside the scope of this discussion. What we can do is "point
them in a good direction" when they must deploy it...

Cheers,
~Chris

PS - See https://tools.ietf.org/html/draft-bdgks-arin-shared-transition-spa=
ce-03#section-2.2
for a more detailed analysis of these alternate options.


> Kind regards,
> Martin



--=20
@ChrisGrundemann
http://chrisgrundemann.com

From martin@millnert.se  Thu Feb 16 09:16:53 2012
Return-Path: <martin@millnert.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 4070B21F87E4 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:16:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KOZ7rdRzecdz for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:16:52 -0800 (PST)
Received: from ncis.csbnet.se (ncis.csbnet.se [95.80.1.101]) by ietfa.amsl.com (Postfix) with ESMTP id 4770D21F8636 for <ietf@ietf.org>; Thu, 16 Feb 2012 09:16:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id CABEC790; Thu, 16 Feb 2012 18:14:29 +0100 (CET)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxIakgW+7fHo; Thu, 16 Feb 2012 18:14:29 +0100 (CET)
Received: from [192.168.120.227] (h-189-4.a189.priv.bahnhof.se [85.24.189.4]) by ncis.csbnet.se (Postfix) with ESMTPSA id 5B9AA2B0; Thu, 16 Feb 2012 18:14:28 +0100 (CET)
Message-ID: <1329412602.5382.83.camel@davinci.millnert.se>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Martin Millnert <martin@millnert.se>
To: Nick Hilliard <nick@inex.ie>
Date: Thu, 16 Feb 2012 18:16:42 +0100
In-Reply-To: <4F3D359C.7020907@inex.ie>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com> <1329410134.5382.72.camel@davinci.millnert.se> <4F3D359C.7020907@inex.ie>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-FIoHvhqYYVHyjuGalQH0"
X-Mailer: Evolution 3.0.3-3 
Mime-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:16:53 -0000

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

Hi Nick,

On Thu, 2012-02-16 at 16:58 +0000, Nick Hilliard wrote:
> There is no particular reason to allocate this space on a regional
> basis, unless for some reason you believe that you can force carriers
> only to use this shared address space for specific purposes - and I
> cannot see why you think that this is remotely feasible for shared
> address space.  Private address space, perhaps.  But certainly not
> shared address space.=20

I'm not sure why a contract with a RIR would be less enforceable than
this I-D. On the contrary, I think the chances of correct use are higher
in that scenario than the other.

It's just bits, you know. IPv4-code on the general internet certainly
won't care about these bits. Routing policy however, may.  I do not see
how having the BCP makes any difference, if the allocation comes from
the RIR in either case, provided there is at least one RIR which can
assign address space to an entity who will share it.

Best,
Martin

--=-FIoHvhqYYVHyjuGalQH0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

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

iQIcBAABAgAGBQJPPTn6AAoJEKgraNdZrwxM7ZMQAIssaLCHup9wu1ga5nsGn5jk
1duxF1UKeAbqXR/jPUG2wZX7je9c78v4GwBx1o88mcW8jJNeQm9lSSTBsQzxXFN1
PEVzbNlBJS2IfQxOiUhUQ3HAzo2vvl9LZymKCCa8rpiFCbhPFEewEVkuXH3+Q9Pf
ZZEdl8hvVc2FQ6yTbOnav1biDXxnJi8X4gq0ngDr2scfseaagVFwS4PLNQUYz3b/
HJqefxX8kBpPX6Di3F70fkQRBui96jxn/TpBEsQR27zCkubY+qxsb6NZaII4gsoX
Evxsca0GGhFUrTXh9JpnBRA2VXyeXUK5860UaZBTqHC37yLRnLxm4B+nhkz13Mgh
o/5iqBEIeW7V9Us63gXmhOHQ5uJvfFE+9piNTe6YbJIvD1gCMxopqSxyEgli7AYH
8mQUC296yADba+28mjDsiDDRcO0mwXQR3CwOP4qyyEcDzvPRLemGf0/J2SLBbYKp
FQTXxNqf+vR8fmf5yGH/ky8+OLKNvkTZg+ySSuR4bDSNaWnXCb0Gv0JQ4bMonXvH
SYv9q5ecrdAc2HTOnEGv27satyCIS903ETMJE6cuquCYavBX2gI66S0xHgs3NN6u
mWIxNLniUURP+q8v+9UCjE3X7Jx4dBMI8Gk/ftJTdEwYilOivSovkGb+vNp5cHdR
y9ST1wiX+E3E0Bu1pp21
=19YJ
-----END PGP SIGNATURE-----

--=-FIoHvhqYYVHyjuGalQH0--


From narten@us.ibm.com  Thu Feb 16 09:30:33 2012
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 2BA1121F872D for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:30:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.756
X-Spam-Level: 
X-Spam-Status: No, score=-109.756 tagged_above=-999 required=5 tests=[AWL=0.843, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4xKbUmMVgSJ for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:30:29 -0800 (PST)
Received: from e37.co.us.ibm.com (e37.co.us.ibm.com [32.97.110.158]) by ietfa.amsl.com (Postfix) with ESMTP id 53AE621F8672 for <ietf@ietf.org>; Thu, 16 Feb 2012 09:30:29 -0800 (PST)
Received: from /spool/local by e37.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 2012 10:30:25 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e37.co.us.ibm.com (192.168.1.137) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 16 Feb 2012 10:30:23 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 91AADC40002; Thu, 16 Feb 2012 10:30:22 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q1GHPnbg132570; Thu, 16 Feb 2012 10:30:22 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q1GHBEhV024115; Thu, 16 Feb 2012 10:11:14 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-49-146-173.mts.ibm.com [9.49.146.173]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q1GHB34Q023066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Feb 2012 10:11:05 -0700
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q1GHAPk1016460; Thu, 16 Feb 2012 12:10:25 -0500
Message-Id: <201202161710.q1GHAPk1016460@cichlid.raleigh.ibm.com>
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
In-reply-to: <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
Comments: In-reply-to John Scudder <jgs@juniper.net> message dated "Thu, 16 Feb 2012 09:00:19 -0800."
Date: Thu, 16 Feb 2012 12:10:24 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12021617-7408-0000-0000-000002B8334E
Cc: "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:30:33 -0000

Hi John.

Turns out Jari sent a message with an overview of the changes. But it
only went to the lisp mailing list, to which I'm not subscribed. 

See http://www.ietf.org/mail-archive/web/lisp/current/msg03674.html

That is the sort of explanation I was looking for.

But since re-chartering is an IETF-wide discussion, I think it would
be helpful that these sorts of things get mentioned in the "WG Review"
messages. That would be helpful to the broader community.

Thomas


From martin@millnert.se  Thu Feb 16 09:38:40 2012
Return-Path: <martin@millnert.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 AB74511E8072 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:38:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.182
X-Spam-Level: 
X-Spam-Status: No, score=-2.182 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HELO_EQ_SE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K6wGmiMZW1bP for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:38:40 -0800 (PST)
Received: from ncis.csbnet.se (ncis.csbnet.se [95.80.1.101]) by ietfa.amsl.com (Postfix) with ESMTP id AA8DA21F883C for <ietf@ietf.org>; Thu, 16 Feb 2012 09:38:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id 4FA64790; Thu, 16 Feb 2012 18:36:16 +0100 (CET)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.csbnet.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4f7ikCkSGb2V; Thu, 16 Feb 2012 18:36:16 +0100 (CET)
Received: from [192.168.120.227] (h-189-4.a189.priv.bahnhof.se [85.24.189.4]) by ncis.csbnet.se (Postfix) with ESMTPSA id 0EE3C2B0; Thu, 16 Feb 2012 18:36:15 +0100 (CET)
Message-ID: <1329413910.5382.101.camel@davinci.millnert.se>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
From: Martin Millnert <martin@millnert.se>
To: Chris Grundemann <cgrundemann@gmail.com>
Date: Thu, 16 Feb 2012 18:38:30 +0100
In-Reply-To: <CAC1-dt=Yb4y04vi9csX36MiC6eCsD8aT11BFARMvdeQ3nA+Yhg@mail.gmail.com>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com> <1329410134.5382.72.camel@davinci.millnert.se> <CAC1-dt=Yb4y04vi9csX36MiC6eCsD8aT11BFARMvdeQ3nA+Yhg@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-gPIltK+QUfDv4LokDqhj"
X-Mailer: Evolution 3.0.3-3 
Mime-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:38:40 -0000

--=-gPIltK+QUfDv4LokDqhj
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Chris,

On Thu, 2012-02-16 at 10:09 -0700, Chris Grundemann wrote:
> On Thu, Feb 16, 2012 at 09:35, Martin Millnert <martin@millnert.se> wrote=
:
<snip>
> > you seem to be of the opinion that improving the feasibility of CGN, by
> > making it suck less, will not have any impact on potential set of
> > networks who are deploying it, or in what way they will deploy it.
>=20
> Correct.

.. except for the part of actually changing what addresses they put on
the inside, which the I-D is about.  Perhaps it's splitting hairs
whether that constitutes a "change" or not, but if it's not a change,
it's weird that it would improve the quality of the network. :-)

<snip>

> I am stating that:
>  - Dual-Stack requires both IPv4 and IPv6 addresses
>  - There is a non-zero number of networks which will exhaust all
> available IPv4 resources before the world is able to fully transition
> to IPv6
>  - These networks must choose one of either:
>   -- Go out of business
>   -- Find a new way to provide IPv4 connections to customers
>  - NAT44* CGN will be chosen by a non-zero number of these networks
>  - This decision is independent of what addresses they will use inside
> of the CGN (No one wants to go through two transitions. Folks who
> deploy CGN do so because they must. As such, the addresses used are an
> afterthought. The cost of CGN and it's alternatives are what drive the
> decision, not this I-D or the addresses it seeks to reserve.)

In the end, I suppose, networks who do not also roll-out DS in
combination with NAT44* CGN, are a blessing for their competition...
where such competition physically exists.

> > I'm curious how you can possibly have sufficient knowledge to make thos=
e
> > statements as *facts*, rather than opinions, informed as the may be (bu=
t
> > of limited scope -- I think it unlikely you've spoken to every network
> > on the planet).
>=20
> You are again correct, I have not spoken to every network on the
> planet. I have spoken to many. Several in the Asia/Pacific region have
> already experienced the chain of events I outlined above.

Check. (I'm aware, as well.)

> Further, my job is to understand the IPv6 transition and as such, much
> of my time is dedicated to creating this understanding. I do not make
> these claims lightly.

Cool. I haven't/certainly didn't mean to suggest you did.

> >   In fact, neither you nor I nor the IETF can stop operators who must
> >   deploy CGN for business continuity from doing so.
> >
> > I hold no such illusions.  What the IETF ought to do however, IMHO, is
> > to point them in a good direction. I don't see that happening in this
> > document.
> >
> > A less-sucky IPv4-run-out access network is still a local maxima
> > compared to the global maxima of DS.
> >  Convince me that our journey to reach the global maxima will not be
> > negatively affected by this document, and gain my support.
>=20
> Once an operator has decided that they have no other choices remaining
> and that they must deploy CGN, they then have to decide how to
> architect that deployment. One of the architectural decisions to be
> made (and the one we are concerned with here) is what addresses to use
> within the CGN. They have several options:
>=20
> - Globally Unique "Public" Addresses
> This option burns addresses that they or others could use to number
> devices that actually require a unique address, this is a net loss to
> the Internet.
>=20
> - RFC 1918 "Private" Addresses
> The chance for collision and the low margins of residential broadband
> make this option a non-starter. Nothing any of us say will convince
> any substantial number of operators to shoot themselves in the foot in
> this way.
>=20
> - Class E Addresses
> Too much equipment is hard coded to reject these addresses. It simply
> will not work in time to make a difference.
>=20
> - "Squat" Addresses
> Without a shared address space, this is the likely winner. Squatting
> on someone else's address space works and is free. A misconfigured
> filter allows these to leak however, another net loss to an un-borked
> Internet.
>=20
> - "Shared" Addresses
> This is the solution put forth in the I-D under discussion here. This
> allows an alternative that is attractive to operators and can be
> managed (since it is a known prefix). If one operator leaks routes,
> others will have filters in place. This option removes the least
> amount of addresses from the remaining free pools thus allowing
> Dual-Stack to work in the most possible networks. All in all, this is
> the best way to ensure a less broken Internet than any of the other
> options can provide.

Not seeing a limitation to NAT444, you left out various alternatives
which have integrated IPv6/DS. Alternatives which, once installed, will
lead to a steady (comparing with the v4-only case) reduction in load on
the CGN equipment, as the world increasingly moves towards DS/v6-only.=20

Such alternatives may not apply to the CGN variant NAT444, which I ACK
the I-D addresses.

> Again, we are not talking about encouraging or discouraging CGN use,
> that is outside the scope of this discussion. What we can do is "point
> them in a good direction" when they must deploy it...

I agree, and would like the direction we point them in to include the
case for DS.  There's always the risk there are very ill-advised
networks around, who push through such upgrades without simultaneously
enabling (a gradual roll-out of) DS, perhaps for nothing else than lack
of sufficient knowledge!

Thanks!

Best,
Martin

--=-gPIltK+QUfDv4LokDqhj
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

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

iQIcBAABAgAGBQJPPT8WAAoJEKgraNdZrwxMsgsP/ip97KNfbDJjMIkFsaRqNsQn
CzGLABWSh+X5v28/ChoMuxl5zZjsWWLNWPj+OmzaR18FifZWWniltKhQgbEzMMgl
beZt6NdQJVXF/GyGjfZfWRegXsXZhswhUbZsGqvZgviKPvngAfS9xZLM1H3DWxBa
uklVOOh5YkPk3iGww9BOPFWY9PuhphoJTNrHboduq0+0JL8g3nrPfIaH6wbts3zR
3Mh8LG9wxcqd1NSCLWgtp6RQbjydVYiNTQiW8EeuBrPYOLk+D0r62R+8sq99ieIT
blYMmaG0UcmVTj5sEwrFjABu5tB3ADvId0kC/QyPOXf1Lmy7p1bdxF+97KOSM4oT
CmpBRo2W5pyXyVwFBD5JhHpkOTSopCRqeFcdsG1iNEmxZKt9jC+7/IJ1zAbX77b9
iRU0PugNqtPeKbQbxhBz/pbvgYyZib4ahtMPxBvvLtRlQZxYg32obMc0SZTQIi7p
wCIp0W3QzbHMHO1xdu1y6X4U2sEk3mKics5tlEozgnbnr9rqdlBb2mPmgBPGiyek
CPOv3p++zCjGyQbsOoVbUMmNcgOG609gs7Qb/Yvnfc0TYdjWQ4sg0PmizoAhJynM
HFinWYggHU6KjhCWWbm3Jp8upQ9twjH0/q8HICdXguBmKpNNEPbsP4MS8Ba57mRF
qe1bILyzXc2YDUsdIKZK
=c/i+
-----END PGP SIGNATURE-----

--=-gPIltK+QUfDv4LokDqhj--


From jgs@juniper.net  Thu Feb 16 09:01:51 2012
Return-Path: <jgs@juniper.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 C1B0621F8885; Thu, 16 Feb 2012 09:01:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.555
X-Spam-Level: 
X-Spam-Status: No, score=-6.555 tagged_above=-999 required=5 tests=[AWL=0.044,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BmrXM8mG3cbl; Thu, 16 Feb 2012 09:01:51 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id C155221F887F; Thu, 16 Feb 2012 09:01:50 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTz02eoyZh6qiblZbHgzCnX8ZOOc5Ed1T@postini.com; Thu, 16 Feb 2012 09:01:51 PST
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Thu, 16 Feb 2012 09:00:20 -0800
From: John Scudder <jgs@juniper.net>
To: Thomas Narten <narten@us.ibm.com>
Date: Thu, 16 Feb 2012 09:00:19 -0800
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: AczszHc80IPY7GmzT5Wq7GMDQHAsNw==
Message-ID: <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com>
In-Reply-To: <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 16 Feb 2012 09:43:04 -0800
Cc: "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:01:51 -0000

Hi Thomas,

On Feb 15, 2012, at 4:31 PM, Thomas Narten wrote:

> A WG Review message for this WG already went out a month ago.
>=20
> What has changed to necessitate another Last Call?
>=20
> Could the-powers-that-be please make it easier for those who might
> care to understand if there is something here that we should know and
> possibly comment about?
>=20
> A simple explanation, or a pointer to diffs, etc. would do the job
> nicely.

Good question! I did go back and diff the last couple of versions and thoug=
h this isn't the exhaustive diff, these are the key changes that caught my =
eye:

This text was lost from the previous draft charter:

This analysis will explain what
role LISP can play in scalable routing. The analysis should also look at
scalability and levels of state required for encapsulation,
decapsulation, liveness, and so on as well as the manageability and
operability of LISP. Specifically, the group will work on:

- documenting areas that need experimentation
- summarizing the results of implementation, experiments, and deployment
  experience
- describing the implications of employing LISP
- operational guidance for using LISP

And so were these Goals and Milestones:

Jun 2012    Forward to the IESG an operational document which should
           include cache management and ETR synchronization
           techniques (draft-ietf-lisp-deployment).

Dec 2013    Publish an example cache management specification.

Jun 2014    Summarize results of specifying, implementing, and testing
           LISP and forward to IESG and/or IRTF.

Jun 2014    Analyze and document the implications of LISP deployments in
           Internet topologies and forward to IESG for publication.

I'm not sure why these were removed, and I would like to see them reinstate=
d or at least have a discussion about their removal.

Thanks,

--John=

From jgs@juniper.net  Thu Feb 16 09:37:06 2012
Return-Path: <jgs@juniper.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 E637D21F8812; Thu, 16 Feb 2012 09:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.86
X-Spam-Level: 
X-Spam-Status: No, score=-5.86 tagged_above=-999 required=5 tests=[AWL=-0.657,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F+Bdxf-NLx8I; Thu, 16 Feb 2012 09:36:59 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id B920721F87E9; Thu, 16 Feb 2012 09:36:58 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKTz0+hxZlPh7yRzv/SJMMwHBXXsnD1IQw@postini.com; Thu, 16 Feb 2012 09:36:59 PST
Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB01-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 16 Feb 2012 09:35:15 -0800
Received: from [172.16.13.201] ([172.16.13.201])	by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q1GHZE124205; Thu, 16 Feb 2012 09:35:14 -0800 (PST)	(envelope-from jgs@juniper.net)
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <201202161710.q1GHAPk1016460@cichlid.raleigh.ibm.com>
From: "John G. Scudder" <jgs@juniper.net>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <201202161710.q1GHAPk1016460@cichlid.raleigh.ibm.com>
Message-ID: <94FA36DB-2FDA-4F3D-B406-E60EDC86AD64@juniper.net>
Date: Thu, 16 Feb 2012 12:34:39 -0500
To: Thomas Narten <narten@us.ibm.com>
MIME-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (9A405)
X-EXCLAIMER-MD-CONFIG: f8e27f27-03b2-4c3e-9447-119194e72cb6
X-Mailman-Approved-At: Thu, 16 Feb 2012 09:43:04 -0800
Cc: "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:37:06 -0000

Thanks, Thomas. In case it's not obvious, Jari's message isn't responsive to=
 the points I raised in my own message so I'll look forward to discussing th=
ose.=20

--John

On Feb 16, 2012, at 12:10 PM, Thomas Narten <narten@us.ibm.com> wrote:

> Hi John.
>=20
> Turns out Jari sent a message with an overview of the changes. But it
> only went to the lisp mailing list, to which I'm not subscribed.=20
>=20
> See http://www.ietf.org/mail-archive/web/lisp/current/msg03674.html
>=20
> That is the sort of explanation I was looking for.
>=20
> But since re-chartering is an IETF-wide discussion, I think it would
> be helpful that these sorts of things get mentioned in the "WG Review"
> messages. That would be helpful to the broader community.
>=20
> Thomas
>=20

From tglassey@certichron.com  Thu Feb 16 04:30:54 2012
Return-Path: <tglassey@certichron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEE3521F87DF; Thu, 16 Feb 2012 04:30:54 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMsInlqKnDPO; Thu, 16 Feb 2012 04:30:50 -0800 (PST)
Received: from m1plsmtpa01-07.prod.mesa1.secureserver.net (m1plsmtpa01-07.prod.mesa1.secureserver.net [64.202.165.186]) by ietfa.amsl.com (Postfix) with ESMTP id A85CF21F87C7; Thu, 16 Feb 2012 04:30:50 -0800 (PST)
Received: from [192.168.1.100] ([67.180.133.66]) by m1plsmtpa01-07.prod.mesa1.secureserver.net with  id acWp1i0031S6wJB01cWpr5; Thu, 16 Feb 2012 05:30:49 -0700
Message-ID: <4F3CF6F8.6030804@certichron.com>
Date: Thu, 16 Feb 2012 04:30:48 -0800
From: Todd Glassey <tglassey@certichron.com>
Organization: certichron.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: dnsop@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
Subject: SEARS - Search Engine Address Resolution Service (and Protocol)
X-Opacus-Archived: none
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 16 Feb 2012 09:47:43 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:30:54 -0000

So SEARS is a method of replacing the DNS roots with a well-known
service portal providing a Google or other SE based access model.  The
session can interface with traditional HTTP or DNS-Lookup Ports to
deliver content or addresses to a browser in the form of a HTTP redirection.

The protocol specification is almost done and is intended to make
threats of attacks against the DNS roots less of an issue.

Todd

-- 
Todd S. Glassey - CISM CIFI
CTO Certichron Inc

This message contains information which may be confidential and/or
privileged. Unless you are the intended recipient (or authorized to
receive for the intended recipient), you may not read, use, copy or
disclose to anyone the message or any information contained in the
message. If you have received the message in error, please advise the
sender by reply e-mail and delete the message and any attachment(s)
thereto without retaining any copies.

Further we have a formal OPT OUT Policy posted on our website pertaining
to the use of any Email Addresses gleaned or taken from any source, web,
mailing lists, previous customer lists etc. In all instances we choose
to formally OPT OUT and this notice constitutes formal disclosure that
you may not collect, buy or sell or provide access to this email address
or any pertaining to our DNS MX Record Publication License posted on the
web at http://www-wp.certichron.com/?page_id=3947.

From jhw@apple.com  Thu Feb 16 09:54:27 2012
Return-Path: <jhw@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 8E7D621F87EC for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8fYCdPVyyI5 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 09:54:27 -0800 (PST)
Received: from mail-out.apple.com (crispin.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 1095821F8810 for <ietf@ietf.org>; Thu, 16 Feb 2012 09:54:27 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0LZH00F6AZ297UX4@mail-out.apple.com> for ietf@ietf.org; Thu, 16 Feb 2012 09:54:25 -0800 (PST)
X-AuditID: 1180711d-b7cf2ae000006b02-9d-4f3d42cf1bec
Received: from [17.153.97.199] (Unknown_Domain [17.153.97.199]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate)	by relay13.apple.com (Apple SCV relay) with SMTP id 66.53.27394.1D24D3F4; Thu, 16 Feb 2012 09:54:25 -0800 (PST)
From: james woodyatt <jhw@apple.com>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Date: Thu, 16 Feb 2012 09:54:22 -0800
Message-id: <262C8D31-87D4-49CB-BA84-B24DE261BA8B@apple.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOJMWRmVeSWpSXmKPExsUiODPxuO5FJ1t/g+M/FSyebZzP4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujE3bf7IXfOCs6H3wiL2B8T97FyMnh4SAicSno4+ZIWwxiQv3 1rN1MXJxCAlMZZI4+m8rK0iCTUBF4tvlu0wgNrOAlsSNfy+hbG2JZQtfM4M0CAu0M0q82rCb BSTBIqAqseXeETYQm1fARuL6neVgcREBPYl5u98yQcQNJWa+ameF2CwrcfvgfqYJjDyzkOyY hWTHLCQtCxiZVzEKFqXmJFYaGuslFhTkpOol5+duYgQFR0Oh7A7G/T/5DzEKcDAq8fAmGdr6 C7EmlhVX5h5ilOBgVhLhzZcBCvGmJFZWpRblxxeV5qQWH2KU5mBREue1NrbxFxJITyxJzU5N LUgtgskycXBKNTDu2G0RmF//MbHqqlZs8cHSKuueVy5XzLhtbk54X77qG7vZtA8nP879HcSV 8mHR242GMmxcUi6n/4vPyHP5cZBdexOv1Mu7col/AtbVLVzJdU68TG3atFKWD4KhacsfmH8S f2enu8O9/VSzgcDiw2va6ld/VPi/fr3wuqTV33nqFN+w1ibyS7xUYinOSDTUYi4qTgQAxXsS CAoCAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:54:27 -0000

everyone--

My position on this draft remains unchanged.  It is far too forgiving of the 6to4-PMT [I-D.kuarsingh-v6ops-6to4-provider-managed-tunnel] proposal, which I regard as abominable.  That reason alone, in my judgment, is sufficient grounds that it should not be published.  I also share the concerns of most of the opponents of this draft.

My recommendation regarding this draft, to the people inside Apple who implement customer-edge router functions, is to ignore it.  It is too late to add the shared transition space to the list of special-use addresses excluded from use as 6to4 tunnel endpoints in all the units already deployed in the field.  Such a disruption to existing customer configurations is generally unacceptable behavior for software updates.  Also, while it might seem reasonable to add the new space to the list of special-use addresses only in *forthcoming* products that support a 6to4 tunnel router feature, that too is unlikely ever to happen. (Note well: we don't comment publicly about the features of unreleased products.)

Shorter james: this draft is a bad idea; please don't publish it.


--
james woodyatt <jhw@apple.com>
member of technical staff, core os networking




From cabo@tzi.org  Thu Feb 16 10:02:18 2012
Return-Path: <cabo@tzi.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 61CF821F88A5 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 10:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.052
X-Spam-Level: 
X-Spam-Status: No, score=-106.052 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7rPVyl0CTql for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 10:02:17 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 86C5321F889E for <ietf@ietf.org>; Thu, 16 Feb 2012 10:02:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q1GI26Na003431; Thu, 16 Feb 2012 19:02:06 +0100 (CET)
Received: from [192.168.217.103] (p5B3E6073.dip.t-dialin.net [91.62.96.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 30B5F840; Thu, 16 Feb 2012 19:02:06 +0100 (CET)
Subject: Re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CB61528D.105E5%d.sturek@att.net>
Date: Thu, 16 Feb 2012 19:02:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3488C487-AD31-446F-A907-E8AD6852FBAB@tzi.org>
References: <CB61528D.105E5%d.sturek@att.net>
To: Don Sturek <d.sturek@att.net>
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:02:18 -0000

Hi Don,

thanks for the feedback.

link-format has been essentially stable for the better part of a year =
now (as the result of dispatching of the comments on the first WGLC in =
-03, IIRC).  It has been used in a number of informal interop events, =
and the feedback always was that it did its job and there were few, if =
any, problems.

Yes, there have been many minor revisions since, mostly on the editorial =
front.
There is a difference between a spec implementers close to the WG =
process can use and the one you want in the permanent record for =
everybody to use.
We also needed to get the ABNF right to cover some fringe cases.

When these small fixes were completed in response to the results of the =
second WGLC, I had briefly planned to do a third WGLC, but then I didn't =
really see a reason any more to do so.  (BTW, I'm not aware of a concept =
of "final WGLC", and I have never qualified a WGLC as such.  The "L" in =
WGLC already means "last", as in final.)

As a general observation on the IETF WG process: the increase of the =
number on the document does not mean there is substantial change.  In =
particular during what I'm referring to as the "ID-nits phase" when a =
document is getting dressed up for going forward, it may take a couple =
of small editorial rounds to get all the various classes of things =
crossed and dotted. =20
Please do avail yourself of the tools pages to review the diffs to see =
whether there still is substantial change or just Brownian motion.  On a =
more general note, WGLC is not the only time WG members need to look at =
a document.

Putting WGLCs on top of distracting events like IETF meetings or =
important holidays is something most WG chairs actively try to avoid.  I =
already put in an allowance for the November IETF in the second WGLC, =
and I'm sorry if I forgot about adding more allowance for US =
Thanksgiving Day.  (There has been ample time since to submit any late =
feedback.)

All that said, we're in luck and have an IETF last call that follows the =
WG consensus process in the procedures, and this is a great opportunity =
for additional input. =20
I'm certainly looking forward to yours.

Gr=FC=DFe, Carsten


From john-ietf@jck.com  Thu Feb 16 10:57:17 2012
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 29D3E21F882B for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 10:57:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level: 
X-Spam-Status: No, score=-102.676 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qr+zhZnbHIc1 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 10:57:16 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3F67821F8828 for <ietf@ietf.org>; Thu, 16 Feb 2012 10:57:16 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ry6S9-000GMW-BF; Thu, 16 Feb 2012 13:53:13 -0500
Date: Thu, 16 Feb 2012 13:57:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
Message-ID: <B98604249282C2EF64A38441@PST.JCK.COM>
In-Reply-To: <4F3D338B.8000203@gmail.com>
References: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu> <CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8se9QXE2n=n7XQ@mail.gmail.com> <4F3D338B.8000203@gmail.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:57:17 -0000

--On Thursday, February 16, 2012 07:49 -0900 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 2/16/12 6:59 AM, Alia Atlas wrote:
>> For what it is worth, those who I've seen commenting in the
>> +1 fashion recently are primarily people I've known to be
>> active in the IETF for years - including some WG chairs.

> I tend to be involved with different working groups from the
> ones
> John is, and I've assumed (forgive me) that he's seeing
> something
> somewhere that I'm not.  I've certainly seen the behavior he's
> describing (flood of non-participants "voting").  I think
> there's
> a difference between someone who's been contributing all along
> participating in a consensus call by posting "+1" and someone
> whom you can't tell whether or not actually read the draft
> posting
> "+1" and it would be surprising indeed if the person
> responsible
> for determining consensus (the chair) treated them as equal in
> weight.

Exactly.   I've also seen very clear situations in the past in
which people who haven't participated and haven't studied the
drafts have been rounded up on a mailing list associated with a
non-IETF body to "vote" in a particular way (fwiw, the worst
example I recall was with an IPR issue).
 
> Actually, come to think of it, we've seen a certain amount of
> this
> concerning the draft-weil-shared-transition-space-request
> draft.

As you point out, I'm not in a good position to judge and was
trying to not do so.  However, I did see a piece of a note to
what appeared to be a non-IETF list suggesting that people go
record their endorsements on the grounds that numbers count.
The note that started this thread was intended, in part, to
point out that numbers of otherwise-content-free endorsements
don't count very much (or shouldn't).  I hoped to make that
point before someone in the opposing group made an effort to
round up all of his friends and acquaintances.

> Anyway, I take the situation that John's describing as annoying
> but not an actual problem - we don't decide by voting.

And the particular thread started by
draft-weil-shared-transition has gone on long enough that I
assume that every IESG member, and especially the ADs who are
most relevant, are painfully aware of the issue.

There is one sense in which it is maybe an actual problem but it
isn't the voting issue (or lack thereof).  IMO, there are two
reasons why it is beneficial to have Last Call discussions on
the IETF list, rather than predominantly in private notes to the
IESG.  One is that we all get to know what the IESG is getting
told (except when the exceptions mentioned in the Last Call
announcement applies -- cases that I think it is important to
preserve).  But the other and IMO far more important reason is
that it is educational for the community: it may help people who
haven't made up their minds to do so and help others to better
understand the tradeoffs.    But, for both of those groups of
people, notes that are high in information content --
considerations and perspectives that have not appeared on the
list before, new facts and arguments-- are very useful.  People
repeating themselves and their positions are not and simply
endorsements aren't much more so - from the standpoint of
someone trying to read the discussions to build a better
understanding, both are pretty much noise (and bogus arguments
aren't much better).  And, since all of us are busy noise in a
long thread does tend to cause some messages that might contain
signal to get lost.

I don't believe anything can be "done about" the more noisy
behavior.  I can, however, hope that raising sensitivity to it
might help, if only a little, to reduce the rate at which it
increases.

    john


From dworley@avaya.com  Thu Feb 16 11:21:44 2012
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0810A21E8068 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.955
X-Spam-Level: 
X-Spam-Status: No, score=-102.955 tagged_above=-999 required=5 tests=[AWL=-0.356, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxNc5eizcMVG for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:21:43 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6570D21E8053 for <ietf@ietf.org>; Thu, 16 Feb 2012 11:21:43 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EABBXPU/GmAcF/2dsb2JhbABEsGiBB4FyAQEBAQMSKDQbAgEIDQEDBAEBHxAyHQgBAQQBEggapSKbVYtuMwYGBA8BHgMDAwKDYwEuEoJSYwSITpJojQc
X-IronPort-AV: E=Sophos;i="4.73,430,1325480400"; d="scan'208";a="232378535"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 16 Feb 2012 14:21:21 -0500
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Feb 2012 14:14:56 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.137]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 16 Feb 2012 14:21:19 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Todd Glassey <tglassey@certichron.com>, IETF Discussion Mailing List <ietf@ietf.org>
Date: Thu, 16 Feb 2012 14:20:50 -0500
Subject: RE: SEARS - Search Engine Address Resolution Service (and Protocol)
Thread-Topic: SEARS - Search Engine Address Resolution Service (and Protocol)
Thread-Index: Aczs0x4j21ZpYbHDTNemL80tsWZpDAADPmEi
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B226F573C30@DC-US1MBEX4.global.avaya.com>
References: <4F3CF6F8.6030804@certichron.com>
In-Reply-To: <4F3CF6F8.6030804@certichron.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:21:44 -0000

How do you find the "well-known service portal" if DNS isn't working?

Dale

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Todd Glass=
ey [tglassey@certichron.com]
Sent: Thursday, February 16, 2012 7:30 AM
To: dnsop@ietf.org; IETF Discussion Mailing List
Subject: SEARS - Search Engine Address Resolution Service (and Protocol)

So SEARS is a method of replacing the DNS roots with a well-known
service portal providing a Google or other SE based access model.  The
session can interface with traditional HTTP or DNS-Lookup Ports to
deliver content or addresses to a browser in the form of a HTTP redirection=
.

The protocol specification is almost done and is intended to make
threats of attacks against the DNS roots less of an issue.

Todd

From jnc@mercury.lcs.mit.edu  Thu Feb 16 11:42:05 2012
Return-Path: <jnc@mercury.lcs.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 C0E3621F885C for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.426
X-Spam-Level: 
X-Spam-Status: No, score=-6.426 tagged_above=-999 required=5 tests=[AWL=0.173,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8GJ+F0ERKW8 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:42:05 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 59AB221F885B for <ietf@ietf.org>; Thu, 16 Feb 2012 11:42:05 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id A407418C0A7; Thu, 16 Feb 2012 14:42:04 -0500 (EST)
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
Message-Id: <20120216194204.A407418C0A7@mercury.lcs.mit.edu>
Date: Thu, 16 Feb 2012 14:42:04 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:42:05 -0000

    > From: John C Klensin <john-ietf@jck.com>

    > people who haven't participated and haven't studied the drafts

This isn't exactly about a complicated protocol: it's about whether to assign
an address block or not.

	Noel

From drc@virtualized.org  Thu Feb 16 11:42:44 2012
Return-Path: <drc@virtualized.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 775FE21F87D4 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:42:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.774
X-Spam-Level: 
X-Spam-Status: No, score=-2.774 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3Knx5P7VAVt for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:42:44 -0800 (PST)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id EB99E21F87CA for <ietf@ietf.org>; Thu, 16 Feb 2012 11:42:43 -0800 (PST)
Received: from [10.0.1.3] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 2A9921705A; Thu, 16 Feb 2012 19:42:43 +0000 (UTC)
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <4F3D359C.7020907@inex.ie>
Date: Thu, 16 Feb 2012 11:42:40 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A0C9A95-30A0-40F7-9A11-FA23C3B79EBD@virtualized.org>
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com> <1329410134.5382.72.camel@davinci.millnert.se> <4F3D359C.7020907@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:42:44 -0000

On Feb 16, 2012, at 8:58 AM, Nick Hilliard wrote:
> The bottom line for this ID is that address space will be required for =
CGN,
> and rfc1918 doesn't cut it for reasons described in the ID.  This =
means
> that the address space must come from somewhere else.  The choices =
are:
>=20
> 1. one or more shared pools allocated by RIRs/IANA/whatever
> 2. private pools, each of which come from the carriers' own address =
blocks

3. private pools, independently chosen by ISPs using some method from =
allocated space (aka squat space).

> option #1 is by definition more efficient than #2.

and option #1 is safer than option #3.

> There is no particular reason to allocate this space on a regional =
basis,

I'd say it would be silly to do so -- what would be the point?

> Incidentally, I support this draft.

One implication of draft-weil not being accepted is that it will likely =
accelerate IPv4 free pool exhaustion as the folks interested in =
draft-weil will simply go out and get blocks from their RIRs while they =
still can.  I will admit a small part of me finds this appealing as it =
would end the seemingly interminable rearrangement of deck chairs on the =
IPv4 address policy-wonk Titanic.

Regards,
-drc


From cabo@tzi.org  Thu Feb 16 11:43:37 2012
Return-Path: <cabo@tzi.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 C68DF21E805A for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.068
X-Spam-Level: 
X-Spam-Status: No, score=-106.068 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvMQ7IkdiFpM for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 11:43:33 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id B266321E8052 for <ietf@ietf.org>; Thu, 16 Feb 2012 11:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q1GJhL1W014271; Thu, 16 Feb 2012 20:43:22 +0100 (CET)
Received: from [192.168.217.103] (p5B3E6073.dip.t-dialin.net [91.62.96.115]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 991438A1; Thu, 16 Feb 2012 20:43:21 +0100 (CET)
Subject: Re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CB628F41.10678%d.sturek@att.net>
Date: Thu, 16 Feb 2012 20:43:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC1C3C8E-EB7D-45C0-9708-5E0C1A25A2A9@tzi.org>
References: <CB628F41.10678%d.sturek@att.net>
To: Don Sturek <d.sturek@att.net>
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:43:38 -0000

On Feb 16, 2012, at 19:52, Don Sturek wrote:

> Hi Carsten,
>=20
> Somehow, luck is not how I would have described the process.
>=20
> I think if you thought it important enough to do a WGLC in November =
2011,
> you maybe should have made it for longer than a week

I did.

> and avoided the US
> Thanksgiving holiday.

As I said, I didn't have that on the radar, so I didn't compensate for =
both the IETF and the US Thanksgiving Day.
Sorry about that.
Not including the winter holidays, there were two more months for making =
comments since.

> We had several groups interested in possibly using CoAP but I was =
holding
> off looking at the draft until WGLC.  I guess with the response below, =
the
> guidance will be to use what is there else find another solution

Wait a minute, maybe there is some underlying confusion here.

This last-call is about the CoRE link-format. =20
The link-format spec and the CoAP protocol are rather loosely coupled, =
technically speaking.

CoAP is not even in first WGLC yet (but getting close).

If you do need some time beyond the usual two-week WGLC to review the =
CoAP documents, now probably would be a good time to start the review =
for

  "Constrained Application Protocol (CoAP)", 31-Oct-11, =
<draft-ietf-core-coap-08.txt>

  "Blockwise transfers in CoAP", 15-Feb-12, =
<draft-ietf-core-block-08.txt>

  "Observing Resources in CoAP", 14-Feb-12, =
<draft-ietf-core-observe-04.txt>

The core-coap spec hasn't been updated recently and therefore carries =
the bulk of the remaining open tickets (six); please review them at
	http://trac.tools.ietf.org/wg/core/trac/report
(I recommend the format of report 9.)
There are proposals for resolution of most of the remaining tickets, and =
we would love to receive your input so we can make good technical =
decisions even before the documents go to WGLC.

It is worth pointing out that the main technical substance of the =
documents has been stable since about March 2011 (core-coap) and since =
mid-2011 (-observe, -block).  Feedback from the multiple implementations =
has been quite positive, so this should all be stable enough for a =
thorough review.=20

> (fortunately, the work you are doing can be replaced with other =
solutions
> if does not map to our commercial needs).

Why the sour grapes?

This WG has a history of being very open and supportive for all =
technical input received.
There is no take-it-or-leave-it at all.
But you do have to speak up, or you won't be heard.

The best way to contribute to IETF WG work is, indeed, taking part in =
the work before WGLC.

> I think I will have a look at the diffs.  I was on the reflector and =
seem
> to recall more than just editorials going in to the specification =
after
> the first WGLC (which I recall at the time being wildly premature with
> respect to the maturity of CoAP.....)

We did the link-format WGLC in January 2011 because the author thought =
it was ready and nobody in the WG spoke up to stop it.
The feedback was quite positive, and the changes resulting from the =
review were useful but small.
It probably was right to wait for November for the 2nd WGLC because CoAP =
was still stabilizing, but it turns out there was no impact.

I don't understand the comment about maturity, but maybe again you are =
referring to CoAP -- a WGLC for CoAP in January 2011 might have been =
rather early indeed.

But for now let's stick to the link-format document -- this is what's =
being last-called this month.
It is a short document, and it is mainly about making an existing RFC =
(RFC 5988) accessible to the CoRE space.

Gr=FC=DFe, Carsten


From marka@isc.org  Thu Feb 16 12:51:18 2012
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 73E7911E80C1 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 12:51:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9q1oejCTsaZ2 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 12:51:17 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id B604111E80C0 for <ietf@ietf.org>; Thu, 16 Feb 2012 12:51:15 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 9C1635F9899; Thu, 16 Feb 2012 20:50:59 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6965:eba7:eff6:1242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 2839D216C6B; Thu, 16 Feb 2012 20:50:57 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 88E1A1D8C83D; Fri, 17 Feb 2012 07:50:53 +1100 (EST)
To: Yoav Nir <ynir@checkpoint.com>
From: Mark Andrews <marka@isc.org>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com> <2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com> <DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net> <06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com> <E87DF8416E72BA1CA5D8CD18@PST.JCK.COM> <2FEED975-B133-4BD8-9187-DFD6B17F7A73@checkpoint.com> <CAKFn1SG2mAgZeH1woH0NDj7Ry59Apoei==4UE+TObH=XaQTJTQ@mail.gmail.com> <9BBAF712-D199-4950-A516-33C830756BEC@checkpoint.com>
Subject: Re: IETF Last Calls and Godwin-like rules
In-reply-to: Your message of "Thu, 16 Feb 2012 17:12:01 +0200." <9BBAF712-D199-4950-A516-33C830756BEC@checkpoint.com>
Date: Fri, 17 Feb 2012 07:50:53 +1100
Message-Id: <20120216205053.88E1A1D8C83D@drugs.dv.isc.org>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:51:18 -0000

In message <9BBAF712-D199-4950-A516-33C830756BEC@checkpoint.com>, Yoav Nir writes:
> 
> On Feb 16, 2012, at 4:48 PM, Roger J=F8rgensen wrote:
> 
> > On Thu, Feb 16, 2012 at 3:34 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> > <snip>
> >> I think that an endorsement like "I work for Cisco and we intend to impl=
> ement this in every one of our products" is useful. But it's not nearly as =
> useful as "this is a terrible idea, and doing this will prevent IPv6 from e=
> ver gaining traction". The objections raised in last call are really the po=
> int, not the endorsements.
> > =
> 
> > =
> 
> > Think I've read somewhere that the ground of good engineering (the E
> > in IETF) are being able to argue against your own idea, search and
> > look for flaws in it, and all in the name of testing it to see how it
> > can be made even better, is it good enough? Or simple to consider the
> > bigger picture, can my idea hurt the rest no matter how good it is?
> > There are great and very good ideas out there that isolated are
> > fantastic, but considered in just a bit bigger picture are horrible,
> > they've ruin everything around them.
> 
> I agree. IPv4 forever using CGNs may work for a lot of people and a lot of =
> uses. If people remain double- or triple-natted it won't matter a bit to th=
> e big web sites. =
> 
> 
> It's far more important to hear what is not going to work with this solutio=
> n.
> 
> It's great if you can find such deficiencies in your own ideas, but we stil=
> l need design reviews, code reviews, QA departments and IETF last calls so =
> that others can get at your idea.

To all of you saying that this only supports IPv4 only boxes.  How
do I connect up my Windows XP (with IPv6 enabled) or later box,
Linux box (from anywhere in the last decade), *BSD box (from anywhere
in the last decade), Apple box (from anywhere in the last decade)
and get both IPv4 and IPv6 without being handed a IPv4 address via
DHCP.  That list pretty much covers the home computer space of dual
stack computer space.

People keep saying IPv6 provides additional solutions, and it does,
however there is a enormous dual stack legacy device problem out
there and saying "go IPv6 only" just isn't a viable for those devices
yet.  They still need a IPv4 address via DHCP which has all the
issues a IPv4-only box has.

There are dual stack CPE routers today that won't provide IPv4
unless there is address space provided via DHCP.  I've got one and
at some point my ISP will need to go the CGN route for IPv4.  I
don't know if there will be a firmware update to support IPv4 over
IPv6 or if there is it will match the solution my ISP will choose.

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

From nick@inex.ie  Thu Feb 16 14:15:35 2012
Return-Path: <nick@inex.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 B799121F881D for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 14:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyABmOwIkhhE for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 14:15:35 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id D74D321E807A for <ietf@ietf.org>; Thu, 16 Feb 2012 14:15:33 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.foobar.org ([IPv6:2001:4d68:2002:100:b07a:544e:9734:d48]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q1GMGBGi063304 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 16 Feb 2012 22:16:17 GMT (envelope-from nick@inex.ie)
Message-ID: <4F3D7FFA.1080401@inex.ie>
Date: Thu, 16 Feb 2012 22:15:22 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: Last Call: <draft-weil-shared-transition-space-request-14.txt> (IANA Reserved IPv4 Prefix for Shared Address Space) to BCP
References: <CB5FF399.1B4E7%jeff.finkelstein@cox.com> <4F3AAA08.2040204@qualcomm.com> <01OBZ9WQSHWY00ZUIL@mauve.mrochek.com> <4F3ABF6C.1030803@qualcomm.com> <m2d39hi267.wl%randy@psg.com> <4F3B09C3.1090005@qualcomm.com> <1329388980.5382.44.camel@davinci.millnert.se> <CAC1-dtnJ77PgMmfeYJHZfO13C10ckznuseVyEECAb8dUPoj1ew@mail.gmail.com> <1329410134.5382.72.camel@davinci.millnert.se> <4F3D359C.7020907@inex.ie> <5A0C9A95-30A0-40F7-9A11-FA23C3B79EBD@virtualized.org>
In-Reply-To: <5A0C9A95-30A0-40F7-9A11-FA23C3B79EBD@virtualized.org>
X-Enigmail-Version: 1.3.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:15:35 -0000

On 16/02/2012 19:42, David Conrad wrote:
> One implication of draft-weil not being accepted is that it will likely
> accelerate IPv4 free pool exhaustion as the folks interested in
> draft-weil will simply go out and get blocks from their RIRs while they
> still can.  I will admit a small part of me finds this appealing as it
> would end the seemingly interminable rearrangement of deck chairs on the
> IPv4 address policy-wonk Titanic.

This deck-chair rearrangement stuff is as predictable as it is pointless.
The only good point about the ID is that at least it puts most carriers on
the same footing and gives them some level of ability to continue to
support their customers' ipv4 connectivity requirements.  In its absence, a
lot of providers will end up using even worse alternatives.

Nick

From nick@inex.ie  Thu Feb 16 14:29:31 2012
Return-Path: <nick@inex.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 CB3F521F887E for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 14:29:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpoAqUCS8TRd for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 14:29:31 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 2254721F887D for <ietf@ietf.org>; Thu, 16 Feb 2012 14:29:30 -0800 (PST)
X-Envelope-To: <ietf@ietf.org>
Received: from crumpet.foobar.org ([IPv6:2001:4d68:2002:100:b07a:544e:9734:d48]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q1GMUCCr063433 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Feb 2012 22:30:17 GMT (envelope-from nick@inex.ie)
Message-ID: <4F3D8343.4060504@inex.ie>
Date: Thu, 16 Feb 2012 22:29:23 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120216194204.A407418C0A7@mercury.lcs.mit.edu>
In-Reply-To: <20120216194204.A407418C0A7@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.3.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:29:31 -0000

On 16/02/2012 19:42, Noel Chiappa wrote:
> This isn't exactly about a complicated protocol: it's about whether to assign
> an address block or not.

It's a quintessential bike-shed problem.  The only reason that people are
moaning about it so much is that they understand the concept of address
allocation.  If the ID concerned a more difficult but important topic, it
would have been waved through hundreds of emails ago.

If every draft got this much attention, we'd still be arguing about X.400
to SMTP gateways.

Nick


From lars@netapp.com  Thu Feb 16 15:36:47 2012
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 4472321E806A for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 15:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.931
X-Spam-Level: 
X-Spam-Status: No, score=-9.931 tagged_above=-999 required=5 tests=[AWL=-0.131, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id guaOxuWWJiyt for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 15:36:42 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 7D54021E8056 for <ietf@ietf.org>; Thu, 16 Feb 2012 15:36:42 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.73,432,1325491200";  d="p7s'?scan'208";a="626173123"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 16 Feb 2012 15:36:42 -0800
Received: from sacrsexc2-prd.hq.netapp.com (sacrsexc2-prd.hq.netapp.com [10.99.115.28]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q1GNafBm029766; Thu, 16 Feb 2012 15:36:41 -0800 (PST)
Received: from SACMVEXC4-PRD.hq.netapp.com ([10.99.115.26]) by sacrsexc2-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 Feb 2012 15:36:37 -0800
Received: from VMWEXCEHT01-PRD.hq.netapp.com ([10.106.76.239]) by SACMVEXC4-PRD.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 16 Feb 2012 15:36:36 -0800
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.193]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.02.0247.003; Thu, 16 Feb 2012 15:36:36 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: IRTF IPR Disclosure Rules 
Thread-Topic: IRTF IPR Disclosure Rules 
Thread-Index: AQHM7QPSYCdby6fPREy39i9rk25vCQ==
Date: Thu, 16 Feb 2012 23:36:35 +0000
Message-ID: <CE53CC86-34F5-41C2-AE6B-44E99FBB7B57@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_1008073F-641C-44C0-AB26-4F2316EF683F"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-OriginalArrivalTime: 16 Feb 2012 23:36:36.0599 (UTC) FILETIME=[D2E7C070:01CCED03]
Cc: IAB IAB <iab@iab.org>, Internet Research Steering Group <irsg@irtf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:36:47 -0000

--Apple-Mail=_1008073F-641C-44C0-AB26-4F2316EF683F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Until now, the IRTF didn't have a clearly formulated statement of how =
IPR is handled by the organization. For the last year, the IRSG has been =
discussing this topic with the IETF's legal counsel and other community =
members with a deep understanding of the issues.

The result of this discussion is a short statement describing the IRTF's =
IPR disclosure rules, which you can find below as well as online at =
http://irtf.org/ipr. The short version is: the IRTF follows the IETF's =
IPR disclosure rules. Because researchers participating in the IRTF may =
not be very familiar with the IETF's rules, the IRTF IPR disclosure =
rules describe what is required of the individual participant in the =
most common cases.

Just as the IETF, the IRTF expects participants to be familiar with =
these rules and follow them when they make contributions.

Please email any comments or questions to irtf-discuss@irtf.org.

Lars Eggert
IRTF Chair

---

IRTF IPR Disclosure Rules

The IRTF follows the IETF IPR disclosure rules. This is a summary
of these rules as they relate to IRTF research group discussions,
mailing lists and Internet Drafts:

- If you include your own or your employer's IPR in a contribution
  to an IRTF research group, then you must file an IPR disclosure
  with the IETF.

- If you recognize your own or your employer's IPR in someone else's
  contribution and you are participating in the discussions in the
  research group relating to that contribution, then you must file
  an IPR disclosure with the IETF. Even if you are not participating
  in the discussion, the IRTF still requests that you file an IPR
  disclosure with the IETF.

- Finally, the IRTF requests that you file an IPR disclosure with
  the IETF if you recognize IPR owned by others in any IRTF
  contribution.

You may file an IPR disclosure here:
http://www.ietf.org/ipr/file-disclosure

See RFC 3979 (BCP 79) for definitions of "IPR" and "contribution"
and for the detailed rules (substituting "IRTF" for "IETF").


--Apple-Mail=_1008073F-641C-44C0-AB26-4F2316EF683F
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDIxNjIzMzYzOFowIwYJKoZIhvcNAQkEMRYEFPQl
Eex3CBTWI1MrF1E6EbyV9Uk4MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBABe8FMGo
3eFJOCJ8Z/XMyrhhII9zsstfUEWA8R9B3/+gvpDZI/IDpSEkJ2uYuLGG4BAAlnXVBN+LVik8waow
PBP466vN5DAk1hY8/3Q7Mc3WsbWfiXCu0Fqvpn3MTnzSJaMRlvAXG+8iINCvSMzji7QFYOv5wEt4
ACD+ELFzrL9KfBwOaPJokIZdYpt2HE0ZuRJ6B6dtiMIpomjewrXG8yNNY5ybV9jFsZL5yusisydL
TswtMscx2gN5gFdJyqP/o1Qgoz+hrXv4WYVw0kChg3TRbuJEBygVOkNMts3nkbWIhNY0abA5vHpU
3MyXcP7BEf1OqViT6mS6DxBFO/VDjfsAAAAAAAA=

--Apple-Mail=_1008073F-641C-44C0-AB26-4F2316EF683F--

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb 16 17:23:46 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9218821E8081 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 17:23:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.074
X-Spam-Level: 
X-Spam-Status: No, score=-0.074 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6u4j8yMUfQV2 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 17:23:46 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C29FD21E807F for <ietf@ietf.org>; Thu, 16 Feb 2012 17:23:44 -0800 (PST)
Received: (qmail 98126 invoked from network); 17 Feb 2012 01:39:18 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 17 Feb 2012 01:39:18 -0000
Message-ID: <4F3DABF8.1050006@necom830.hpcl.titech.ac.jp>
Date: Fri, 17 Feb 2012 10:23:04 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: SEARS - Search Engine Address Resolution Service (and Protocol)
References: <4F3CF6F8.6030804@certichron.com>
In-Reply-To: <4F3CF6F8.6030804@certichron.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:23:46 -0000

Todd Glassey wrote:

> So SEARS is a method of replacing the DNS roots with a well-known
> service portal providing a Google or other SE based access model.  The
> session can interface with traditional HTTP or DNS-Lookup Ports to
> deliver content or addresses to a browser in the form of a HTTP redirection.

It's no different from plain search engine with "I'm feeling
lucky" turned on.

> The protocol specification is almost done and is intended to make
> threats of attacks against the DNS roots less of an issue.

I heard that Anonymous is planning to attack root servers.

Is it google who hired them to promote SEARS. :-)

Anyway, root servers are (or will be) anycast with a lot less
centralized management than google servers that they are more
resistant against attacks.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb 16 17:31:21 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 676F821E809B for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 17:31:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.075
X-Spam-Level: 
X-Spam-Status: No, score=-0.075 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHS-vBL8F145 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 17:31:21 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 98C4721E8095 for <ietf@ietf.org>; Thu, 16 Feb 2012 17:31:07 -0800 (PST)
Received: (qmail 98225 invoked from network); 17 Feb 2012 01:46:53 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 17 Feb 2012 01:46:53 -0000
Message-ID: <4F3DADBF.8030006@necom830.hpcl.titech.ac.jp>
Date: Fri, 17 Feb 2012 10:30:39 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu> <4F3C5132.9050905@necom830.hpcl.titech.ac.jp> <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu>
In-Reply-To: <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:31:21 -0000

Steven Bellovin wrote:

>> Thus, IPv6 was mortally wounded from the beginning.
> 
> The history is vastly more complex than that.  However, this particular decision
> was just about the last one the IPng directorate made before reporting back to
> the IETF -- virtually everything else in the basic IPv6 design had already
> been agreed-to.

I understand that, unlike 64 bit, 128 bit enables MAC based
SLAAC with full of states, which is as fatal as addresses
with 32 hexadecimal characters.

> I don't think this was "the" wrong decision.

Isn't it obvious that, with a lot more than 1% penetration of the
Internet to the world today, we don't need address length much more
than 32 bits?

						Masataka Ohta

From jmh@joelhalpern.com  Thu Feb 16 18:26:19 2012
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 A3EA821F863D; Thu, 16 Feb 2012 18:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dcLRd7C92ur1; Thu, 16 Feb 2012 18:26:19 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 2F07721F863B; Thu, 16 Feb 2012 18:26:19 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id CE475CAD41; Thu, 16 Feb 2012 18:26:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id DCBBC1C087F; Thu, 16 Feb 2012 18:26:16 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [172.17.114.244] (207.47.24.2.static.nextweb.net [207.47.24.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id A23231C0152; Thu, 16 Feb 2012 18:26:16 -0800 (PST)
Message-ID: <4F3DBAC7.1010805@joelhalpern.com>
Date: Thu, 16 Feb 2012 21:26:15 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
In-Reply-To: <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:26:19 -0000

If I may separate issues for a moment,
the absence of milestones is because Terry and I have to come up with a 
proposal for them which matche sthe revised goals.

If you read the rest of the differences, you will see that the general 
question of what LISP is aimed at providing is indeed still there.

The largest single difference is the addition of the architecture draft, 
which the IESG considers a gating item for any of the longer term work 
(such as the security solutions or the additional mapping system.

Some of the apparent removal is because, as Jari stated, the IESG has 
requested that the working group focus on fewer deliverables.

Yours,
Joel

On 2/16/2012 12:00 PM, John Scudder wrote:
> Hi Thomas,
>
> On Feb 15, 2012, at 4:31 PM, Thomas Narten wrote:
>
>> A WG Review message for this WG already went out a month ago.
>>
>> What has changed to necessitate another Last Call?
>>
>> Could the-powers-that-be please make it easier for those who might
>> care to understand if there is something here that we should know and
>> possibly comment about?
>>
>> A simple explanation, or a pointer to diffs, etc. would do the job
>> nicely.
>
> Good question! I did go back and diff the last couple of versions and though this isn't the exhaustive diff, these are the key changes that caught my eye:
>
> This text was lost from the previous draft charter:
>
> This analysis will explain what
> role LISP can play in scalable routing. The analysis should also look at
> scalability and levels of state required for encapsulation,
> decapsulation, liveness, and so on as well as the manageability and
> operability of LISP. Specifically, the group will work on:
>
> - documenting areas that need experimentation
> - summarizing the results of implementation, experiments, and deployment
>    experience
> - describing the implications of employing LISP
> - operational guidance for using LISP
>
> And so were these Goals and Milestones:
>
> Jun 2012    Forward to the IESG an operational document which should
>             include cache management and ETR synchronization
>             techniques (draft-ietf-lisp-deployment).
>
> Dec 2013    Publish an example cache management specification.
>
> Jun 2014    Summarize results of specifying, implementing, and testing
>             LISP and forward to IESG and/or IRTF.
>
> Jun 2014    Analyze and document the implications of LISP deployments in
>             Internet topologies and forward to IESG for publication.
>
> I'm not sure why these were removed, and I would like to see them reinstated or at least have a discussion about their removal.
>
> Thanks,
>
> --John

From smb@cs.columbia.edu  Thu Feb 16 18:46:59 2012
Return-Path: <smb@cs.columbia.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 EEA1621E8028 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 18:46:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.774
X-Spam-Level: 
X-Spam-Status: No, score=-5.774 tagged_above=-999 required=5 tests=[AWL=0.825,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n45+QY8RLDJH for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 18:46:54 -0800 (PST)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id 3A24D21E8036 for <ietf@ietf.org>; Thu, 16 Feb 2012 18:46:52 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q1H2knck011414 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2012 21:46:50 -0500 (EST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <4F3DADBF.8030006@necom830.hpcl.titech.ac.jp>
Date: Thu, 16 Feb 2012 21:46:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F27A1E6-A631-476E-B158-F0DCD39123C2@cs.columbia.edu>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu> <4F3C5132.9050905@necom830.hpcl.titech.ac.jp> <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu> <4F3DADBF.8030006@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@NECOM830.HPCL.TITECH.AC.JP>
X-Mailer: Apple Mail (2.1257)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:46:59 -0000

On Feb 16, 2012, at 8:30 39PM, Masataka Ohta wrote:

> Steven Bellovin wrote:
>=20
>>> Thus, IPv6 was mortally wounded from the beginning.
>>=20
>> The history is vastly more complex than that.  However, this =
particular decision
>> was just about the last one the IPng directorate made before =
reporting back to
>> the IETF -- virtually everything else in the basic IPv6 design had =
already
>> been agreed-to.
>=20
> I understand that, unlike 64 bit, 128 bit enables MAC based
> SLAAC with full of states, which is as fatal as addresses
> with 32 hexadecimal characters.

That decision came later.  In fact, the deficiencies of relying on MACs =
were
discussed quite frequently in the directorate.
>=20
>> I don't think this was "the" wrong decision.
>=20
> Isn't it obvious that, with a lot more than 1% penetration of the
> Internet to the world today, we don't need address length much more
> than 32 bits?

No.  I did and I do think that 64 bits was inadequate.

Why?  Apart from the fact that if this transition is painful, the next
one will be well-nigh impossible, having more bits lets us find creative
ways to use the address space.  Stateless autoconfig is one example,
though I realize it's controversial.  ID/locator split, which I've been
a proponent of for very many years, works a lot better with more bits,
because it allows topological addressing both within and outside an
organization.


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From narten@us.ibm.com  Thu Feb 16 21:53:10 2012
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 359E921F86BE for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 21:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.312
X-Spam-Level: 
X-Spam-Status: No, score=-109.312 tagged_above=-999 required=5 tests=[AWL=1.288, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OTFfcX22CheK for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 21:53:09 -0800 (PST)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 27C8721F86BD for <ietf@ietf.org>; Thu, 16 Feb 2012 21:53:08 -0800 (PST)
Received: from /spool/local by e39.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 2012 22:53:06 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 16 Feb 2012 22:53:05 -0700
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 7D1F019D8048 for <ietf@ietf.org>; Thu, 16 Feb 2012 22:53:00 -0700 (MST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q1H5r4Xj115390 for <ietf@ietf.org>; Thu, 16 Feb 2012 22:53:04 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q1H5r36d031337 for <ietf@ietf.org>; Thu, 16 Feb 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q1H5r3dM031313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Feb 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q1H5r2gj024843 for <ietf@ietf.org>; Fri, 17 Feb 2012 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q1H5r2TJ024811 for ietf@ietf.org; Fri, 17 Feb 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201202170553.q1H5r2TJ024811@rotala.raleigh.ibm.com>
Date: Fri, 17 Feb 2012 00:53:02 -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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12021705-4242-0000-0000-000000CC43EE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 05:53:10 -0000

Total of 227 messages in the last 7 days.
 
script run at: Fri Feb 17 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.49% |   17 |  5.04% |    94840 | jnc@mercury.lcs.mit.edu
  7.05% |   16 |  4.74% |    89192 | mohta@necom830.hpcl.titech.ac.jp
  5.73% |   13 |  5.01% |    94286 | dougb@dougbarton.us
  3.08% |    7 |  6.99% |   131545 | randy@psg.com
  3.96% |    9 |  3.35% |    63069 | mansaxel@besserwisser.org
  3.96% |    9 |  3.23% |    60665 | brian.e.carpenter@gmail.com
  3.08% |    7 |  3.07% |    57656 | cgrundemann@gmail.com
  2.64% |    6 |  3.04% |    57137 | presnick@qualcomm.com
  3.08% |    7 |  2.60% |    48838 | dhc@dcrocker.net
  3.08% |    7 |  2.29% |    43115 | mrex@sap.com
  2.64% |    6 |  2.65% |    49796 | sm@resistor.net
  2.64% |    6 |  2.52% |    47425 | marka@isc.org
  2.64% |    6 |  2.49% |    46889 | john-ietf@jck.com
  2.64% |    6 |  2.22% |    41802 | rogerj@gmail.com
  2.20% |    5 |  2.52% |    47443 | martin@millnert.se
  1.76% |    4 |  2.21% |    41620 | ben@nostrum.com
  1.32% |    3 |  2.43% |    45792 | sob@harvard.edu
  1.76% |    4 |  1.58% |    29728 | ynir@checkpoint.com
  1.76% |    4 |  1.55% |    29083 | drc@virtualized.org
  1.76% |    4 |  1.49% |    27990 | smb@cs.columbia.edu
  0.88% |    2 |  2.26% |    42482 | matthew.bocci@alcatel-lucent.com
  1.32% |    3 |  1.64% |    30892 | ted.lemon@nominum.com
  1.32% |    3 |  1.61% |    30321 | cb.list6@gmail.com
  1.32% |    3 |  1.23% |    23046 | adrian@olddog.co.uk
  1.32% |    3 |  1.14% |    21411 | narten@us.ibm.com
  1.32% |    3 |  1.06% |    19853 | nick@inex.ie
  1.32% |    3 |  1.02% |    19227 | lsawyer@gci.com
  1.32% |    3 |  0.93% |    17492 | ned+ietf@mauve.mrochek.com
  0.88% |    2 |  1.36% |    25618 | touch@isi.edu
  0.88% |    2 |  1.24% |    23419 | rcallon@juniper.net
  0.88% |    2 |  1.24% |    23394 | owen@delong.com
  0.88% |    2 |  1.24% |    23361 | roberta.maglione@telecomitalia.it
  0.44% |    1 |  1.68% |    31609 | stbryant@cisco.com
  0.88% |    2 |  0.86% |    16132 | cabo@tzi.org
  0.88% |    2 |  0.85% |    15910 | jmh@joelhalpern.com
  0.88% |    2 |  0.81% |    15241 | tglassey@earthlink.net
  0.88% |    2 |  0.78% |    14663 | victor.kuarsingh@gmail.com
  0.44% |    1 |  1.21% |    22716 | gregory.mirsky@ericsson.com
  0.88% |    2 |  0.76% |    14386 | joelja@bogus.com
  0.88% |    2 |  0.75% |    14098 | steve@shinkuro.com
  0.88% |    2 |  0.70% |    13233 | jgs@juniper.net
  0.44% |    1 |  1.03% |    19345 | sob@sobco.com
  0.44% |    1 |  0.78% |    14652 | jason_livingood@cable.comcast.com
  0.44% |    1 |  0.77% |    14430 | lars@netapp.com
  0.44% |    1 |  0.66% |    12403 | d.sturek@att.net
  0.44% |    1 |  0.60% |    11291 | stephen@sprunk.org
  0.44% |    1 |  0.58% |    10948 | wesley.george@twcable.com
  0.44% |    1 |  0.52% |     9869 | sant9442@gmail.com
  0.44% |    1 |  0.52% |     9867 | tnadeau@lucidvision.com
  0.44% |    1 |  0.51% |     9604 | rdroms.ietf@gmail.com
  0.44% |    1 |  0.41% |     7791 | sagriffith@gci.com
  0.44% |    1 |  0.40% |     7540 | gdaley@au.logicalis.com
  0.44% |    1 |  0.39% |     7426 | c.donley@cablelabs.com
  0.44% |    1 |  0.39% |     7281 | bcheck@ncta.com
  0.44% |    1 |  0.38% |     7082 | d3e3e3@gmail.com
  0.44% |    1 |  0.37% |     6994 | bob.hinden@gmail.com
  0.44% |    1 |  0.37% |     6988 | hans.thienpondt@staff.telenet.be
  0.44% |    1 |  0.37% |     6892 | jhw@apple.com
  0.44% |    1 |  0.36% |     6749 | ole@cisco.com
  0.44% |    1 |  0.36% |     6740 | braden@isi.edu
  0.44% |    1 |  0.35% |     6608 | akatlas@gmail.com
  0.44% |    1 |  0.35% |     6569 | melinda.shore@gmail.com
  0.44% |    1 |  0.35% |     6510 | morrowc.lists@gmail.com
  0.44% |    1 |  0.34% |     6449 | arturo.servin@gmail.com
  0.44% |    1 |  0.34% |     6304 | dworley@avaya.com
  0.44% |    1 |  0.33% |     6263 | amorris@amsl.com
  0.44% |    1 |  0.33% |     6250 | wbeebee@cisco.com
  0.44% |    1 |  0.33% |     6153 | nomcom-chair@ietf.org
  0.44% |    1 |  0.32% |     6072 | kirk.erichsen@twcable.com
  0.44% |    1 |  0.32% |     6014 | tglassey@certichron.com
  0.44% |    1 |  0.31% |     5756 | daryl.tanner@blueyonder.co.uk
  0.44% |    1 |  0.30% |     5684 | rbarnes@bbn.com
  0.44% |    1 |  0.30% |     5658 | wch.ietf@gmail.com
  0.44% |    1 |  0.29% |     5494 | lea.roberts@stanford.edu
  0.44% |    1 |  0.26% |     4970 | jeff.finkelstein@cox.com
--------+------+--------+----------+------------------------
100.00% |  227 |100.00% |  1881061 | Total


From randy@psg.com  Thu Feb 16 23:00:42 2012
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 5133A21F881B for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 23:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level: 
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=0.118,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKlPfRv1Q0Xk for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 23:00:42 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id EECCC21F8818 for <ietf@ietf.org>; Thu, 16 Feb 2012 23:00:41 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RyHo6-0008HF-TR; Fri, 17 Feb 2012 07:00:39 +0000
Date: Thu, 16 Feb 2012 23:00:38 -0800
Message-ID: <m2ehtudjvt.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Nick Hilliard <nick@inex.ie>
Subject: Re: IETF Last Calls and Godwin-like rules
In-Reply-To: <4F3D8343.4060504@inex.ie>
References: <20120216194204.A407418C0A7@mercury.lcs.mit.edu> <4F3D8343.4060504@inex.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:00:42 -0000

> It's a quintessential bike-shed problem.  The only reason that people are
> moaning about it so much is that they understand the concept of address
> allocation.

exactly.  they understand the concept.  and, like many things where the
surface seems easy, everyone thinks they're an expert.

randy

From jari.arkko@piuha.net  Fri Feb 17 04:46:09 2012
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 3C25B21F87BE; Fri, 17 Feb 2012 04:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukAt+P2hG1WV; Fri, 17 Feb 2012 04:46:08 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1C621F87B7; Fri, 17 Feb 2012 04:46:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 411022D35A; Fri, 17 Feb 2012 14:46:06 +0200 (EET)
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 a2mzuIFzAsyw; Fri, 17 Feb 2012 14:46:05 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 910502CC3C; Fri, 17 Feb 2012 14:46:05 +0200 (EET)
Message-ID: <4F3E4C0D.5060105@piuha.net>
Date: Fri, 17 Feb 2012 14:46:05 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com>
In-Reply-To: <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: lisp@ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:46:09 -0000

On 15.02.2012 23:31, Thomas Narten wrote:
> A WG Review message for this WG already went out a month ago.
>
> What has changed to necessitate another Last Call?
>
> Could the-powers-that-be please make it easier for those who might
> care to understand if there is something here that we should know and
> possibly comment about?
>
> A simple explanation, or a pointer to diffs, etc. would do the job
> nicely.
>

I should have sent the e-mail to the ietf@ietf.org list as well.

Looks like you found the e-mail from the WG mailing list later in the thread, so I am not repeating it here any more. Long story short, the IESG members had plenty of opinions about what the working group should be doing, given the recent experience of processing many documents from the working group.

I do agree that it would be useful to post the same message to other places where the review went. Sorry, I missed it in this case (or, to be precise, I was too busy to craft a second message focused on the recharter part only before you took notice...)

Jari


From jari.arkko@piuha.net  Fri Feb 17 04:58:05 2012
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 7C75321F8535; Fri, 17 Feb 2012 04:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6a2ZY5cuzrW3; Fri, 17 Feb 2012 04:58:05 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 99F2121F8533; Fri, 17 Feb 2012 04:58:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E58622D35A; Fri, 17 Feb 2012 14:58:03 +0200 (EET)
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 mLDYXSI4HD8n; Fri, 17 Feb 2012 14:58:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 249212CC3C; Fri, 17 Feb 2012 14:58:03 +0200 (EET)
Message-ID: <4F3E4EDB.7070509@piuha.net>
Date: Fri, 17 Feb 2012 14:58:03 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
In-Reply-To: <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:58:05 -0000

John,

The IESG had no specific objection to these parts, but we made the charter in general shorter and reformulated some of the results. In particular, the idea was to put much of the material that you pointed to into the "LISP impacts" document. In general, the IESG felt that we had to go back a bit, and describe more of the big picture - the architecture, what problem we are addressing, what the results and downsides are - than the technical details. But it was not intended that topics like scalability and amount of state could be left out.

I do agree that the description of the impacts document is short at the moment, is there something that you'd like to lift to put in the new charter?

Jari

On 16.02.2012 19:00, John Scudder wrote:
> Hi Thomas,
>
> On Feb 15, 2012, at 4:31 PM, Thomas Narten wrote:
>
>> A WG Review message for this WG already went out a month ago.
>>
>> What has changed to necessitate another Last Call?
>>
>> Could the-powers-that-be please make it easier for those who might
>> care to understand if there is something here that we should know and
>> possibly comment about?
>>
>> A simple explanation, or a pointer to diffs, etc. would do the job
>> nicely.
> Good question! I did go back and diff the last couple of versions and though this isn't the exhaustive diff, these are the key changes that caught my eye:
>
> This text was lost from the previous draft charter:
>
> This analysis will explain what
> role LISP can play in scalable routing. The analysis should also look at
> scalability and levels of state required for encapsulation,
> decapsulation, liveness, and so on as well as the manageability and
> operability of LISP. Specifically, the group will work on:
>
> - documenting areas that need experimentation
> - summarizing the results of implementation, experiments, and deployment
>    experience
> - describing the implications of employing LISP
> - operational guidance for using LISP
>
> And so were these Goals and Milestones:
>
> Jun 2012    Forward to the IESG an operational document which should
>             include cache management and ETR synchronization
>             techniques (draft-ietf-lisp-deployment).
>
> Dec 2013    Publish an example cache management specification.
>
> Jun 2014    Summarize results of specifying, implementing, and testing
>             LISP and forward to IESG and/or IRTF.
>
> Jun 2014    Analyze and document the implications of LISP deployments in
>             Internet topologies and forward to IESG for publication.
>
> I'm not sure why these were removed, and I would like to see them reinstated or at least have a discussion about their removal.
>
> Thanks,
>
> --John


From dhc@dcrocker.net  Fri Feb 17 05:41:42 2012
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 CA2ED21F8810 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 05:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level: 
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YZFv6oMaMDjQ for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 05:41:42 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E3EDA21F8803 for <ietf@ietf.org>; Fri, 17 Feb 2012 05:41:41 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1HDfTVJ012494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Feb 2012 05:41:34 -0800
Message-ID: <4F3E5906.5070902@dcrocker.net>
Date: Fri, 17 Feb 2012 05:41:26 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu> <4F3C5132.9050905@necom830.hpcl.titech.ac.jp> <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu> <4F3DADBF.8030006@necom830.hpcl.titech.ac.jp> <8F27A1E6-A631-476E-B158-F0DCD39123C2@cs.columbia.edu>
In-Reply-To: <8F27A1E6-A631-476E-B158-F0DCD39123C2@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 17 Feb 2012 05:41:35 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:41:42 -0000

On 2/16/2012 6:46 PM, Steven Bellovin wrote:
> Why?  Apart from the fact that if this transition is painful, the next
> one will be well-nigh impossible, having more bits lets us find creative
> ways to use the address space.


Not to single out Steve, but my recollection is that that view was at the core 
of much of the thinking about v6, certainly in the early-/mid-90s.  "We only get 
this one (last) opportunity to make changes, so we'd better add everything we 
think we'll (ever) need."

The view is wrong.

Changing an established infrastructure is of course (a lot) more difficult and 
expensive than creating a new one, but infrastructures can and do get changed.

There is a difference between saying "we need to make all of the changes that we 
know we need now, versus saying we need to anticipate all of the changes we are 
going to need to make."

Steve's phrasing points to the latter and that winds up as a fantasy exercise 
which adds complexity and delay.  It also tends to add the wrong things in the 
wrong way.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dhc@dcrocker.net  Fri Feb 17 05:44:36 2012
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 9B05A21F8821 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 05:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level: 
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASYpQpF+u3DP for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 05:44:35 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7EE3521F86D0 for <ietf@ietf.org>; Fri, 17 Feb 2012 05:44:34 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1HDiRqJ012638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 17 Feb 2012 05:44:32 -0800
Message-ID: <4F3E59B7.1090609@dcrocker.net>
Date: Fri, 17 Feb 2012 05:44:23 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu> <CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8se9QXE2n=n7XQ@mail.gmail.com> <4F3D338B.8000203@gmail.com>
In-Reply-To: <4F3D338B.8000203@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 17 Feb 2012 05:44:32 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:44:36 -0000

On 2/16/2012 8:49 AM, Melinda Shore wrote:
> Anyway, I take the situation that John's describing as annoying
> but not an actual problem - we don't decide by voting.


Right.

And perhaps the focus for this issue should be on the ability of the (relatively 
few) folk making decisions to distinguish between substantive vs. political 
input, rather than on trying to prevent the political input.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From julian.reschke@gmx.de  Fri Feb 17 07:54:03 2012
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 DF3CF21F8777 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 07:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.377
X-Spam-Level: 
X-Spam-Status: No, score=-104.377 tagged_above=-999 required=5 tests=[AWL=-1.778, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVOlNyGX5HnC for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 07:54:02 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id EEBC521F871C for <ietf@ietf.org>; Fri, 17 Feb 2012 07:54:01 -0800 (PST)
Received: (qmail invoked by alias); 17 Feb 2012 15:54:00 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.83]) [217.91.35.233] by mail.gmx.net (mp031) with SMTP; 17 Feb 2012 16:54:00 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18Ypg8M17AYMq1FTWcTZZYMH3KUHZUwNvevAUw9DF xTyLLCQag+LP3q
Message-ID: <4F3E7816.4070709@gmx.de>
Date: Fri, 17 Feb 2012 16:53:58 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-reschke-http-status-308-05.txt> (The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)) to Experimental RFC
References: <20120217144555.26744.99147.idtracker@ietfa.amsl.com>
In-Reply-To: <20120217144555.26744.99147.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: HTTP Working Group <ietf-http-wg@w3.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:54:04 -0000

(FYI)

Also, an HTML version with feedback links is available at 
<http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-05.html>.

Best regards, Julian

On 2012-02-17 15:45, The IESG wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent
>     Redirect)'
>    <draft-reschke-http-status-308-05.txt>  as an Experimental 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 2012-03-16. 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 the additional HyperText Transfer Protocol
>     (HTTP) Status Code 308 (Permanent Redirect).
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-reschke-http-status-308/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-reschke-http-status-308/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


From beldmit@gmail.com  Thu Feb 16 10:17:21 2012
Return-Path: <beldmit@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 0632821E802E; Thu, 16 Feb 2012 10:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPdUzEvxeKEz; Thu, 16 Feb 2012 10:17:14 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF7BC21E801F; Thu, 16 Feb 2012 10:17:14 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2943257pbc.31 for <multiple recipients>; Thu, 16 Feb 2012 10:17:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WZ9x7SeqtGOU/Hju8RaHzZfHvlZC9FgSOr0rSQN5fD0=; b=V/NwR6njpo3gAi0VxHvQzEVHSGX71EtOsvayd+y+Q4UYRU7w6MHgT1Ggl2BwOENUVu I2QNIyu8E8GImIFk9rsvm7MJ5O99pqESrpxrvon0t0CGX2tG04DoDLDx8Ou2VbjzoLRU jkwSkGFWrvE9MH3idFjsj1nuaNRz50HrOj17U=
MIME-Version: 1.0
Received: by 10.68.130.233 with SMTP id oh9mr16156018pbb.92.1329416234507; Thu, 16 Feb 2012 10:17:14 -0800 (PST)
Received: by 10.68.230.103 with HTTP; Thu, 16 Feb 2012 10:17:14 -0800 (PST)
In-Reply-To: <4F3CF6F8.6030804@certichron.com>
References: <4F3CF6F8.6030804@certichron.com>
Date: Thu, 16 Feb 2012 22:17:14 +0400
Message-ID: <CADqLbzK+_cRu-RzsiTr-J3j8yJ6bo398Y1Bje-U7r5yPQz+iiA@mail.gmail.com>
Subject: Re: [DNSOP] SEARS - Search Engine Address Resolution Service (and Protocol)
From: Dmitry Belyavsky <beldmit@gmail.com>
To: Todd Glassey <tglassey@certichron.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 17 Feb 2012 08:07:20 -0800
Cc: dnsop@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:17:21 -0000

Greetings!

Is there a more or less complete description of SEARS? Google can't
find anything instead this or that trade companies, Wikipedia shows
some people and some trade companies too...

On Thu, Feb 16, 2012 at 4:30 PM, Todd Glassey <tglassey@certichron.com> wro=
te:
> So SEARS is a method of replacing the DNS roots with a well-known
> service portal providing a Google or other SE based access model. =C2=A0T=
he
> session can interface with traditional HTTP or DNS-Lookup Ports to
> deliver content or addresses to a browser in the form of a HTTP redirecti=
on.
>
> The protocol specification is almost done and is intended to make
> threats of attacks against the DNS roots less of an issue.
>
> Todd
>
> --
> Todd S. Glassey - CISM CIFI
> CTO Certichron Inc
>
> This message contains information which may be confidential and/or
> privileged. Unless you are the intended recipient (or authorized to
> receive for the intended recipient), you may not read, use, copy or
> disclose to anyone the message or any information contained in the
> message. If you have received the message in error, please advise the
> sender by reply e-mail and delete the message and any attachment(s)
> thereto without retaining any copies.
>
> Further we have a formal OPT OUT Policy posted on our website pertaining
> to the use of any Email Addresses gleaned or taken from any source, web,
> mailing lists, previous customer lists etc. In all instances we choose
> to formally OPT OUT and this notice constitutes formal disclosure that
> you may not collect, buy or sell or provide access to this email address
> or any pertaining to our DNS MX Record Publication License posted on the
> web at http://www-wp.certichron.com/?page_id=3D3947.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



--=20
SY, Dmitry Belyavsky

From d.sturek@att.net  Thu Feb 16 10:52:20 2012
Return-Path: <d.sturek@att.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 8D5CD11E80AA for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 10:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.135
X-Spam-Level: 
X-Spam-Status: No, score=-1.135 tagged_above=-999 required=5 tests=[AWL=1.464,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZ7gZwrBQTjo for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 10:52:19 -0800 (PST)
Received: from nm8.access.bullet.mail.sp2.yahoo.com (nm8.access.bullet.mail.sp2.yahoo.com [98.139.44.135]) by ietfa.amsl.com (Postfix) with SMTP id BBD1B11E80A1 for <ietf@ietf.org>; Thu, 16 Feb 2012 10:52:19 -0800 (PST)
Received: from [98.139.44.107] by nm8.access.bullet.mail.sp2.yahoo.com with NNFMP; 16 Feb 2012 18:52:19 -0000
Received: from [98.139.44.91] by tm12.access.bullet.mail.sp2.yahoo.com with NNFMP; 16 Feb 2012 18:52:19 -0000
Received: from [127.0.0.1] by omp1028.access.mail.sp2.yahoo.com with NNFMP; 16 Feb 2012 18:52:19 -0000
X-Yahoo-Newman-Id: 698302.31235.bm@omp1028.access.mail.sp2.yahoo.com
Received: (qmail 81345 invoked from network); 16 Feb 2012 18:52:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1329418339; bh=GqvBMcH+yvtu9MjCUDGO+xrf79W7xpir5sGdaP9goEM=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:User-Agent:Date:Subject:From:To:CC:Message-ID:Thread-Topic:In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; b=AUr+eUA0NXJV4YaG6e2aSAmxx45o9oiE6SJDr8TIL+dC05P1NMskxvNWO9b0MEaZVU9iMYv9TRCkK4CHrgXtKmuBIzHDxb873WiCS0yASQHM8t085pdfVDzewCOdAtyV+0flZwdXcEm0gvzt0bGk2lkiZu249NCCWnt70p38Uqw=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: CXFf4wMVM1mo1wJIfOSltJYzl8gh1Y6BfzVZXzYFgRF5VBG ELmfC3uo3YPwzKjeWFnql4VfGkcToxc_f4x78q2VBoAarizXjBEPBVFg76_U 7FNGZcakCh2H7sdq.2PDksM2CKdY5ioxob_GwV1ZeIb2R3OwKPSOwIalEH21 Vlr78l1_kCzi2n.Wxqq78evLOCIfx04YMcn_SIWZ3awQ4L7D5zefniAWw62R WjRI8ojcd0WS9eV.u7Hxf__A22pw_NQ37FcUuvlQdZd.PzwaLY8dbv7PqcSh gRjfnoGuQfQUBj2YIm0busYaEswOfcuwWj1fTohwB.VBsnLZGD8SXhBaPEFg 7XiAKGuEn3xLBjPcLytQOBI1AOwPEuagasEmPTN3V32FkLvipiOUqbdsMrKc TDl2qvoCV2UFYB0Uzg.5tCynu2440oEPdGA--
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
Received: from [10.1.1.108] (d.sturek@174.78.56.227 with login) by smtp114.sbc.mail.ne1.yahoo.com with SMTP; 16 Feb 2012 10:52:18 -0800 PST
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Thu, 16 Feb 2012 10:52:13 -0800
Subject: Re: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
From: Don Sturek <d.sturek@att.net>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <CB628F41.10678%d.sturek@att.net>
Thread-Topic: [core] Last Call: <draft-ietf-core-link-format-11.txt> (CoRE Link Format) to Proposed Standard
In-Reply-To: <3488C487-AD31-446F-A907-E8AD6852FBAB@tzi.org>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Mailman-Approved-At: Fri, 17 Feb 2012 08:07:35 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:52:20 -0000

Hi Carsten,

Somehow, luck is not how I would have described the process.

I think if you thought it important enough to do a WGLC in November 2011,
you maybe should have made it for longer than a week and avoided the US
Thanksgiving holiday.

We had several groups interested in possibly using CoAP but I was holding
off looking at the draft until WGLC.  I guess with the response below, the
guidance will be to use what is there else find another solution
(fortunately, the work you are doing can be replaced with other solutions
if does not map to our commercial needs).

I think I will have a look at the diffs.  I was on the reflector and seem
to recall more than just editorials going in to the specification after
the first WGLC (which I recall at the time being wildly premature with
respect to the maturity of CoAP.....)

Don





On 2/16/12 10:02 AM, "Carsten Bormann" <cabo@tzi.org> wrote:

>Hi Don,
>
>thanks for the feedback.
>
>link-format has been essentially stable for the better part of a year now
>(as the result of dispatching of the comments on the first WGLC in -03,
>IIRC).  It has been used in a number of informal interop events, and the
>feedback always was that it did its job and there were few, if any,
>problems.
>
>Yes, there have been many minor revisions since, mostly on the editorial
>front.
>There is a difference between a spec implementers close to the WG process
>can use and the one you want in the permanent record for everybody to use.
>We also needed to get the ABNF right to cover some fringe cases.
>
>When these small fixes were completed in response to the results of the
>second WGLC, I had briefly planned to do a third WGLC, but then I didn't
>really see a reason any more to do so.  (BTW, I'm not aware of a concept
>of "final WGLC", and I have never qualified a WGLC as such.  The "L" in
>WGLC already means "last", as in final.)
>
>As a general observation on the IETF WG process: the increase of the
>number on the document does not mean there is substantial change.  In
>particular during what I'm referring to as the "ID-nits phase" when a
>document is getting dressed up for going forward, it may take a couple of
>small editorial rounds to get all the various classes of things crossed
>and dotted. =20
>Please do avail yourself of the tools pages to review the diffs to see
>whether there still is substantial change or just Brownian motion.  On a
>more general note, WGLC is not the only time WG members need to look at a
>document.
>
>Putting WGLCs on top of distracting events like IETF meetings or
>important holidays is something most WG chairs actively try to avoid.  I
>already put in an allowance for the November IETF in the second WGLC, and
>I'm sorry if I forgot about adding more allowance for US Thanksgiving
>Day.  (There has been ample time since to submit any late feedback.)
>
>All that said, we're in luck and have an IETF last call that follows the
>WG consensus process in the procedures, and this is a great opportunity
>for additional input.
>I'm certainly looking forward to yours.
>
>Gr=FC=DFe, Carsten
>



From tglassey@certichron.com  Thu Feb 16 14:09:15 2012
Return-Path: <tglassey@certichron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B8D21F879A for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 14:09: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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-ZR5hRFWeSO for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2012 14:09:11 -0800 (PST)
Received: from p3plsmtpa06-07.prod.phx3.secureserver.net (p3plsmtpa06-07.prod.phx3.secureserver.net [173.201.192.108]) by ietfa.amsl.com (Postfix) with SMTP id B87C521F878E for <ietf@ietf.org>; Thu, 16 Feb 2012 14:09:10 -0800 (PST)
Received: (qmail 29450 invoked from network); 16 Feb 2012 22:02:30 -0000
Received: from unknown (67.180.133.66) by p3plsmtpa06-07.prod.phx3.secureserver.net (173.201.192.108) with ESMTP; 16 Feb 2012 22:02:30 -0000
Message-ID: <4F3D7CF3.9070305@certichron.com>
Date: Thu, 16 Feb 2012 14:02:27 -0800
From: Todd Glassey <tglassey@certichron.com>
Organization: certichron.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: SEARS - Search Engine Address Resolution Service (and Protocol)
References: <4F3CF6F8.6030804@certichron.com> <CD5674C3CD99574EBA7432465FC13C1B226F573C30@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B226F573C30@DC-US1MBEX4.global.avaya.com>
X-Opacus-Archived: none
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 17 Feb 2012 08:07:36 -0800
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:09:15 -0000

On 2/16/2012 11:20 AM, Worley, Dale R (Dale) wrote:
> How do you find the "well-known service portal" if DNS isn't working?

You have to manually enter a fail-over providers address when you
install it.

Todd

> 
> Dale
> 
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Todd Glassey [tglassey@certichron.com]
> Sent: Thursday, February 16, 2012 7:30 AM
> To: dnsop@ietf.org; IETF Discussion Mailing List
> Subject: SEARS - Search Engine Address Resolution Service (and Protocol)
> 
> So SEARS is a method of replacing the DNS roots with a well-known
> service portal providing a Google or other SE based access model.  The
> session can interface with traditional HTTP or DNS-Lookup Ports to
> deliver content or addresses to a browser in the form of a HTTP redirection.
> 
> The protocol specification is almost done and is intended to make
> threats of attacks against the DNS roots less of an issue.
> 
> Todd
> 
> 


-- 
Todd S. Glassey - CISM CIFI
CTO Certichron Inc

This message contains information which may be confidential and/or
privileged. Unless you are the intended recipient (or authorized to
receive for the intended recipient), you may not read, use, copy or
disclose to anyone the message or any information contained in the
message. If you have received the message in error, please advise the
sender by reply e-mail and delete the message and any attachment(s)
thereto without retaining any copies.

Further we have a formal OPT OUT Policy posted on our website pertaining
to the use of any Email Addresses gleaned or taken from any source, web,
mailing lists, previous customer lists etc. In all instances we choose
to formally OPT OUT and this notice constitutes formal disclosure that
you may not collect, buy or sell or provide access to this email address
or any pertaining to our DNS MX Record Publication License posted on the
web at http://www-wp.certichron.com/?page_id=3947.

From gtw@gtwassociates.com  Fri Feb 17 08:41:24 2012
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9497D21E8045 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 08:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level: 
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_50=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PbjJhpVYQdgv for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 08:41:23 -0800 (PST)
Received: from mail4.primary.net (mail4.primary.net [216.87.38.199]) by ietfa.amsl.com (Postfix) with ESMTP id 356A721E8038 for <ietf@ietf.org>; Fri, 17 Feb 2012 08:41:23 -0800 (PST)
Received: from pool-173-66-7-49.washdc.fios.verizon.net ([173.66.7.49]:1287 helo=gtwassociates) by mail4.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1RyQrv-0003k1-TR; Fri, 17 Feb 2012 10:41:16 -0600
Message-ID: <7BBE70A23475408EBF62991D30DF47B7@gtwassociates>
From: "George Willingmyre" <gtw@gtwassociates.com>
To: "John C Klensin" <john-ietf@jck.com>, "SM" <sm@resistor.net>
References: <CB5E9FDF.4DCE%c.grundemann@cablelabs.com><2F5AF14A-BC87-4F34-BCB6-842F5722A1F2@delong.com><DF7F294AF4153D498141CBEFADB17704C70AD046BD@EMBX01-WF.jnpr.net><06627D4F-EE80-4D33-8AB9-AF51D9076A6F@sobco.com><E87DF8416E72BA1CA5D8CD18@PST.JCK.COM> <6.2.5.6.2.20120216063504.08854130@resistor.net>
Subject: Re: IETF Last Calls and Godwin-like rules
Date: Fri, 17 Feb 2012 11:40:54 -0500
Organization: GTW Associates
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0511_01CCED69.02394B40"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: George Willingmyre <gtw@gtwassociates.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:41:24 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0511_01CCED69.02394B40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

potential "vote packers"  in voluntary consensus standards processes =
take heed of 1988 Supreme Court affirmation of lower court award of $3.8 =
million in damages (before trebling)  antitrust liability of  Allied =
Tube & Conduit Corp when packing NFPA process
http://www.gtwassociates.com/answers/Cases/AlliedTube.htm
Supreme Court  affirmed
In its complaint, plaintiff Indian Head, Inc. (Carlon) charged that =
defendant Allied Tube & Conduit Corp. had conspired to prevent inclusion =
of Carlon's product in industry standards. The jury found for Carlon, =
and awarded it $3.8 million in damages (before trebling).
Allied Tube v. Indian Head, Inc. - 486 U.S. 492 (1988)
Before the meeting was held, petitioner, the Nation's largest producer =
of steel conduit, members of the steel industry, other steel conduit =
manufacturers, and independent sales agents collectively agreed to =
exclude respondent's product from the 1981 Code by packing the annual =
meeting with new Association members whose only function was to vote =
against respondent's proposal.

George T. Willingmyre, P.E.
President, GTW Associates
Spencerville, MD USA 20868
301.421.4138
www.gtwassociates.com

----- Original Message -----=20
From: "SM" <sm@resistor.net>
To: "John C Klensin" <john-ietf@jck.com>
Cc: <ietf@ietf.org>
Sent: Thursday, February 16, 2012 10:46 AM
Subject: Re: IETF Last Calls and Godwin-like rules


> Hi John,
> At 06:04 16-02-2012, John C Klensin wrote:
>>A current Last Call has apparently brought on another of the
>>"please tell all your friends to send in supportive notes, even
>>if they don't say much of anything substantive" campaigns that
>>we see from time to time.  When those notes come from people who
>>do not routinely participate on IETF lists, they provide very
>>little real information unless we have suddenly taken up voting
>=20
> Letter-writing campaigns occur every now and then.  As there isn't=20
> any vote count, the effort can end up in a diluted form.
>=20
>>individual and +1" does not.   Sadly, such endorsements,
>>especially from people who are not active IETF participants, add
>>to the noise and might prevent someone who was still genuinely
>>trying to understand the pros and cons (presumably including all
>>of the IESG) from seeing a new and substantive argument, no
>>matter how well-grounded.
>=20
> Last year, someone discussed about how a "+1" could be read and some=20
> people were offended.   Maybe authors should be given the choice to=20
> have their proposal evaluated by counting the votes or to have the=20
> evaluation which is based on substantive comments.  Nobody would be=20
> offended then.
>=20
> Regards,
> -sm=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
------=_NextPart_000_0511_01CCED69.02394B40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19190">
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV>
<H1><FONT size=3D2 face=3DArial>potential "vote packers"&nbsp; in =
voluntary=20
consensus standards processes take heed of 1988 Supreme =
Court&nbsp;affirmation=20
of lower court award of $3.8 million in damages (before trebling)=20
&nbsp;antitrust liability of&nbsp; Allied Tube &amp; Conduit =
Corp&nbsp;when=20
packing NFPA process</FONT></H1>
<H1><FONT size=3D2 face=3DArial><A=20
href=3D"http://www.gtwassociates.com/answers/Cases/AlliedTube.htm">http:/=
/www.gtwassociates.com/answers/Cases/AlliedTube.htm</A></FONT></H1>
<DIV><FONT size=3D2 face=3DArial>Supreme Court&nbsp; =
affirmed</FONT></DIV>
<H1><FONT size=3D2 face=3DArial>In its complaint, plaintiff Indian Head, =
Inc.=20
(Carlon) charged that defendant Allied Tube &amp; Conduit Corp. had =
conspired to=20
prevent inclusion of Carlon's product in industry standards. The jury =
found for=20
Carlon, and awarded it $3.8 million in damages (before =
trebling).</FONT></H1>
<H1><FONT size=3D2 face=3DArial>Allied Tube v. Indian Head, Inc. - 486 =
U.S. 492=20
(1988)</FONT></H1></DIV>
<DIV><FONT size=3D2 face=3DArial>Before the meeting was held, =
petitioner, the=20
Nation's largest producer of steel conduit, members of the steel =
industry, other=20
steel conduit manufacturers, and independent sales agents collectively =
agreed to=20
exclude respondent's product from the 1981 Code by packing the annual =
meeting=20
with new Association members whose only function was to vote against=20
respondent's proposal.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>George T. Willingmyre, =
P.E.<BR>President, GTW=20
Associates<BR>Spencerville, MD USA 20868<BR>301.421.4138<BR></FONT><A=20
href=3D"http://www.gtwassociates.com"><FONT size=3D2=20
face=3DArial>www.gtwassociates.com</FONT></A></DIV>
<DIV><FONT size=3D2 face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2 face=3DArial>----- Original Message ----- </FONT>
<DIV><FONT size=3D2 face=3DArial>From: "SM" &lt;</FONT><A=20
href=3D"mailto:sm@resistor.net"><FONT size=3D2=20
face=3DArial>sm@resistor.net</FONT></A><FONT size=3D2 =
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>To: "John C Klensin" &lt;</FONT><A=20
href=3D"mailto:john-ietf@jck.com"><FONT size=3D2=20
face=3DArial>john-ietf@jck.com</FONT></A><FONT size=3D2 =
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Cc: &lt;</FONT><A =
href=3D"mailto:ietf@ietf.org"><FONT=20
size=3D2 face=3DArial>ietf@ietf.org</FONT></A><FONT size=3D2=20
face=3DArial>&gt;</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Sent: Thursday, February 16, 2012 10:46 =

AM</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Subject: Re: IETF Last Calls and =
Godwin-like=20
rules</FONT></DIV></DIV>
<DIV><FONT face=3DArial><BR><FONT size=3D2></FONT></FONT></DIV><FONT =
size=3D2=20
face=3DArial>&gt; Hi John,<BR>&gt; At 06:04 16-02-2012, John C Klensin=20
wrote:<BR>&gt;&gt;A current Last Call has apparently brought on another =
of=20
the<BR>&gt;&gt;"please tell all your friends to send in supportive =
notes,=20
even<BR>&gt;&gt;if they don't say much of anything substantive" =
campaigns=20
that<BR>&gt;&gt;we see from time to time.&nbsp; When those notes come =
from=20
people who<BR>&gt;&gt;do not routinely participate on IETF lists, they =
provide=20
very<BR>&gt;&gt;little real information unless we have suddenly taken up =

voting<BR>&gt; <BR>&gt; Letter-writing campaigns occur every now and =
then.&nbsp;=20
As there isn't <BR>&gt; any vote count, the effort can end up in a =
diluted=20
form.<BR>&gt; <BR>&gt;&gt;individual and +1" does not.&nbsp;&nbsp; =
Sadly, such=20
endorsements,<BR>&gt;&gt;especially from people who are not active IETF=20
participants, add<BR>&gt;&gt;to the noise and might prevent someone who =
was=20
still genuinely<BR>&gt;&gt;trying to understand the pros and cons =
(presumably=20
including all<BR>&gt;&gt;of the IESG) from seeing a new and substantive=20
argument, no<BR>&gt;&gt;matter how well-grounded.<BR>&gt; <BR>&gt; Last =
year,=20
someone discussed about how a "+1" could be read and some <BR>&gt; =
people were=20
offended.&nbsp;&nbsp; Maybe authors should be given the choice to =
<BR>&gt; have=20
their proposal evaluated by counting the votes or to have the <BR>&gt;=20
evaluation which is based on substantive comments.&nbsp; Nobody would be =

<BR>&gt; offended then.<BR>&gt; <BR>&gt; Regards,<BR>&gt; -sm <BR>&gt; =
<BR>&gt;=20
_______________________________________________<BR>&gt; Ietf mailing=20
list<BR>&gt; </FONT><A href=3D"mailto:Ietf@ietf.org"><FONT size=3D2=20
face=3DArial>Ietf@ietf.org</FONT></A><BR><FONT size=3D2 =
face=3DArial>&gt; </FONT><A=20
href=3D"https://www.ietf.org/mailman/listinfo/ietf"><FONT size=3D2=20
face=3DArial>https://www.ietf.org/mailman/listinfo/ietf</FONT></A><BR><FO=
NT size=3D2=20
face=3DArial>&gt;</FONT></BODY></HTML>

------=_NextPart_000_0511_01CCED69.02394B40--


From presnick@qualcomm.com  Fri Feb 17 09:45:53 2012
Return-Path: <presnick@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 4DED921F8753 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 09:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqcCw3gmK-sR for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 09:45:52 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 5F90721F8752 for <ietf@ietf.org>; Fri, 17 Feb 2012 09:45:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329500752; x=1361036752; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F3E924B.8060203@qualcomm.com>|Date:=20Fr i,=2017=20Feb=202012=2011:45:47=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20<dcrocker@bbiw.net>|CC:=20Dave =20CROCKER=20<dhc@dcrocker.net>,=20<ietf@ietf.org> |Subject:=20Re:=20IETF=20Last=20Calls=20and=20Godwin-like =20rules|References:=20<20120216153318.29DBE18C0A7@mercur y.lcs.mit.edu>=09<CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8s e9QXE2n=3Dn7XQ@mail.gmail.com>=09<4F3D338B.8000203@gmail. com>=20<4F3E59B7.1090609@dcrocker.net>|In-Reply-To:=20<4F 3E59B7.1090609@dcrocker.net>|Content-Type:=20text/plain =3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=AQiSUVuG1JfL8WiGfwms9MQWIaeOTJbTQW5hIUhw4P4=; b=eDOvuA/14Ux7uxBXsTO0RH2PLQvs77thWgw0mpxzre2z5ipy6161ohtD ptnPjVIGjnsh+Xy/+FLdOM0xxinKCzZLYXTR5n1T+Czss2ri/Vqe9Ej8H Ln4atoZqdAKSFkfVc/yNLgX6kXQNdz/P3CrsEGFFTq78ol5ifu2Hmi7w5 g=;
X-IronPort-AV: E=McAfee;i="5400,1158,6623"; a="164127209"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 17 Feb 2012 09:45:49 -0800
X-IronPort-AV: E=Sophos;i="4.73,438,1325491200"; d="scan'208";a="259424782"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 17 Feb 2012 09:45:49 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 17 Feb 2012 09:45:49 -0800
Message-ID: <4F3E924B.8060203@qualcomm.com>
Date: Fri, 17 Feb 2012 11:45:47 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <dcrocker@bbiw.net>
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120216153318.29DBE18C0A7@mercury.lcs.mit.edu>	<CAG4d1reqd-ego44KkdbnFUHT2ZQHrJjE+YBf8se9QXE2n=n7XQ@mail.gmail.com>	<4F3D338B.8000203@gmail.com> <4F3E59B7.1090609@dcrocker.net>
In-Reply-To: <4F3E59B7.1090609@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:45:53 -0000

On 2/17/12 7:44 AM, Dave CROCKER wrote:

> And perhaps the focus for this issue should be on the ability of the 
> (relatively few) folk making decisions to distinguish between 
> substantive vs. political input, rather than on trying to prevent the 
> political input.

Getting the folk who evaluate consensus to distinguish between 
substantive and political input is certainly primary, though (hopefully) 
they already are able to do so. An important secondary goal is also to 
make sure that the folk giving substantive input understand that the 
folk evaluating it *do* take their input into account and *don't* take 
the political input into account. Too often, the mere posting of these 
content-free "endorsements" causes those who do contribute substantively 
to post their own retorts, muddying the record of the conversation. 
Further, if the decision happens to go the way of the "endorsements", 
people who have made substantive comments express displeasure at the 
"vote packing".

We do need to make sure that the folks evaluating consensus know that 
"voting doesn't count" and that their decisions are made by consensus on 
the technical issues, not the number of people speaking. But we also 
need to make sure that community understands that "voting doesn't count" 
and that they are confident it is enforced. That might mean that 
occasionally we have to publicly say things like, "You do realize that 
we are ignoring this" to people who post the political input.

(I again glance over at my edit buffer with the beginnings of a short 
essay "On consensus and humming" and think, "I've really got to finish 
that.")

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From lsawyer@gci.com  Fri Feb 17 09:56:27 2012
Return-Path: <lsawyer@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43E4D21F85E7 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 09:56:27 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRIOeIv+4y4c for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 09:56:26 -0800 (PST)
Received: from mailgw1.gci.com (mailgw1.gci.com [209.165.141.90]) by ietfa.amsl.com (Postfix) with ESMTP id 9D9B221F85B6 for <ietf@ietf.org>; Fri, 17 Feb 2012 09:56:26 -0800 (PST)
Received: from dtn1cas01.gci.com (10.100.4.60) by mailgw1.gci.com (172.19.0.25) with Microsoft SMTP Server (TLS) id 8.2.234.1; Fri, 17 Feb 2012 08:56:50 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by dtn1cas01.gci.com ([10.100.4.60]) with mapi; Fri, 17 Feb 2012 08:56:24 -0900
From: Leif Sawyer <lsawyer@gci.com>
To: Randy Bush <randy@psg.com>, Nick Hilliard <nick@inex.ie>
Date: Fri, 17 Feb 2012 08:56:23 -0900
Subject: RE: IETF Last Calls and Godwin-like rules
Thread-Topic: IETF Last Calls and Godwin-like rules
Thread-Index: AcztQeObD1ihQV7pR16/UmNONWjX0gAWdncQ
Message-ID: <18B2C6E38A3A324986B392B2D18ABC5101D4DD6542@fnb1mbx01.gci.com>
References: <20120216194204.A407418C0A7@mercury.lcs.mit.edu> <4F3D8343.4060504@inex.ie> <m2ehtudjvt.wl%randy@psg.com>
In-Reply-To: <m2ehtudjvt.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:56:27 -0000

Randy Bush speaketh:
> in reply to: Nick Hilliard
>> It's a quintessential bike-shed problem.  The only reason=20
>> that people are moaning about it so much is that they understand
>> the concept of address allocation.
>=20
> exactly.  they understand the concept.  and, like many things=20
> where the surface seems easy, everyone thinks they're an expert.

Ugh.

Who gets to decide who the experts are?

Who gets to decide what voice they get?

Why should the "working expert" be penalized because they don't favor
sitting on a mailing list slogging through the minutae of everyday
issues that don't impact them, just for speaking up when they are
being affected?


You'll note that I didn't just "vote-stuff"  but have actively
participated in trying to show my reasoning for support.  I've
sat on the MSO-IPv6 working group for the last 2 years, and=20
draft-weil went to OPSAWG, I followed it there.

And then it came over here.



Are you telling me, that because I haven't participated in any other
discussions, that I may not be "an expert" in my field, or that I=20
don't get a voice?  Even though I've been working with IPv6 for >7 years,
and was the first person in Alaska to have a working production network
available at my job?  And to convince my company, that yes, IPv6 is worth
fighting for?  And to push back at vendors until they supported it?=20
And filed and helped fix bugs?

I say that it is not *your* call.


I say that unless *you* are supporting >200k users on an IPv4 network with
the threat of no additional public IPv4 space looming, and the REQUIREMENT
that you not only maintain but GROW your business...

... if *YOU* *RANDY*  are not doing that... then *YOU* are not an expert.


Of course, that's not fair either.  And I would be loathe to actually
do such a thing.

But I would be careful about throwing stones around...

From jnc@mercury.lcs.mit.edu  Fri Feb 17 09:59:10 2012
Return-Path: <jnc@mercury.lcs.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 3FADC21F878A for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 09:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.434
X-Spam-Level: 
X-Spam-Status: No, score=-6.434 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRVz97mSzNLb for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 09:59:09 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id AF93121F8789 for <ietf@ietf.org>; Fri, 17 Feb 2012 09:59:09 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 9EAA718C097; Fri, 17 Feb 2012 12:59:08 -0500 (EST)
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
Message-Id: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>
Date: Fri, 17 Feb 2012 12:59:08 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:59:10 -0000

    > From: Pete Resnick <presnick@qualcomm.com>

    > We do need to make sure that the folks evaluating consensus know
    > that "voting doesn't count" and that their decisions are made by
    > consensus on the technical issues, not the number of people speaking.

Yes, but how do you tell where the consensus is if 97% of the people in the
'room' haven't expressed an opinion? The 'me too' posts do serve a purpose in
giving a larger sample size (provided, of course, that they are from long-time
IETF partipants).

	Noel

From bob.hinden@gmail.com  Fri Feb 17 10:10:48 2012
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 9D49F21F8667 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.553
X-Spam-Level: 
X-Spam-Status: No, score=-103.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgA93rj9yS8x for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:10:45 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 54AE921F865E for <ietf@ietf.org>; Fri, 17 Feb 2012 10:10:44 -0800 (PST)
Received: by dakl33 with SMTP id l33so3680976dak.31 for <ietf@ietf.org>; Fri, 17 Feb 2012 10:10:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=uPGes/nqF2FU34NpQlbDVRgMJLH4DutJVGEjRTdP/9E=; b=hk7zbce0N7PBndatQmAKBx2Es3M1oJqGce3bXVZ+hEEB8q29mtd5TsrXOx1kJTgsl6 sv+D7g8qSozTX9cO89dze6/gO4bDgQ60Vsw3omDew8pvxgtwG0Qs5BdjFFznpRyJHp+6 6ExjwrHOou3YVKkY1TIXlHCkm5DqnyZn2RAC4=
Received: by 10.68.75.135 with SMTP id c7mr26537232pbw.43.1329502243545; Fri, 17 Feb 2012 10:10:43 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id p9sm17296468pbb.9.2012.02.17.10.10.41 (version=SSLv3 cipher=OTHER); Fri, 17 Feb 2012 10:10:41 -0800 (PST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <8F27A1E6-A631-476E-B158-F0DCD39123C2@cs.columbia.edu>
Date: Fri, 17 Feb 2012 10:10:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <91957AEB-3DBF-4547-A0A5-B5FA77CB5A92@gmail.com>
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu> <4F3C5132.9050905@necom830.hpcl.titech.ac.jp> <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu> <4F3DADBF.8030006@necom830.hpcl.titech.ac.jp> <8F27A1E6-A631-476E-B158-F0DCD39123C2@cs.columbia.edu>
To: Steven Bellovin <smb@cs.columbia.edu>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:10:48 -0000

Steve,

On Feb 16, 2012, at 6:46 PM, Steven Bellovin wrote:

>=20
> On Feb 16, 2012, at 8:30 39PM, Masataka Ohta wrote:
>=20
>> Steven Bellovin wrote:
>>=20
>>>> Thus, IPv6 was mortally wounded from the beginning.
>>>=20
>>> The history is vastly more complex than that.  However, this =
particular decision
>>> was just about the last one the IPng directorate made before =
reporting back to
>>> the IETF -- virtually everything else in the basic IPv6 design had =
already
>>> been agreed-to.
>>=20
>> I understand that, unlike 64 bit, 128 bit enables MAC based
>> SLAAC with full of states, which is as fatal as addresses
>> with 32 hexadecimal characters.
>=20
> That decision came later.  In fact, the deficiencies of relying on =
MACs were
> discussed quite frequently in the directorate.


And that's why the standard allows for other types of identifiers to be =
used to create Interface Identifiers.


>>=20
>>> I don't think this was "the" wrong decision.
>>=20
>> Isn't it obvious that, with a lot more than 1% penetration of the
>> Internet to the world today, we don't need address length much more
>> than 32 bits?
>=20
> No.  I did and I do think that 64 bits was inadequate.
>=20
> Why?  Apart from the fact that if this transition is painful, the next
> one will be well-nigh impossible, having more bits lets us find =
creative
> ways to use the address space.  Stateless autoconfig is one example,
> though I realize it's controversial.  ID/locator split, which I've =
been
> a proponent of for very many years, works a lot better with more bits,
> because it allows topological addressing both within and outside an
> organization.
>=20

To confirm what your are saying about an ID/locator split in IPv6, that =
the other reason why we went with 128-bit address with a 64/64 split as =
the common case and defining IIDs that indicate if they have global =
uniqueness.  This creates a framework that an ID/locator split could be =
implemented. =20

Opinions vary if ID/locator split is useful, but we have a framework =
that would allow it without having to roll out another version of IP.  A =
win IMHO.

Bob



From dhc@dcrocker.net  Fri Feb 17 10:18:50 2012
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 75D3421F86AB for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level: 
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[AWL=0.002,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id um488MpBPFFE for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:18:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id ED03A21F8686 for <ietf@ietf.org>; Fri, 17 Feb 2012 10:18:42 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q1HIIbRv019492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 17 Feb 2012 10:18:42 -0800
Message-ID: <4F3E99FA.4070608@dcrocker.net>
Date: Fri, 17 Feb 2012 10:18:34 -0800
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>
In-Reply-To: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 17 Feb 2012 10:18:42 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:18:50 -0000

On 2/17/2012 9:59 AM, Noel Chiappa wrote:
> (provided, of course, that they are from long-time
> IETF partipants).


Noel,

Given that Nomcom membership can be granted to folk who have attended only a few 
recent meetings and without any requirement that they know or have done anything 
in the IETF, exactly what do you mean by "long-time IETF participants".

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jnc@mercury.lcs.mit.edu  Fri Feb 17 10:32:43 2012
Return-Path: <jnc@mercury.lcs.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 E31E321F854A for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:32:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.441
X-Spam-Level: 
X-Spam-Status: No, score=-6.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETUj353O0BNT for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:32:43 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 105BD21F855D for <ietf@ietf.org>; Fri, 17 Feb 2012 10:32:41 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 2267518C09A; Fri, 17 Feb 2012 13:32:41 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Variable length internet addresses in TCP/IP: history
Message-Id: <20120217183241.2267518C09A@mercury.lcs.mit.edu>
Date: Fri, 17 Feb 2012 13:32:41 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:32:44 -0000

    > From: Bob Hinden <bob.hinden@gmail.com>

    > the other reason why we went with 128-bit address with a 64/64 split
    > as the common case and defining IIDs that indicate if they have
    > global uniqueness. This creates a framework that an ID/locator split
    > could be implemented. ... we have a framework that would allow it
    > without having to roll out another version of IP. 

Alas, the inclusion of _both halves_ of the IPv6 address in the TCP
checksum means the framework you speak of is basically useless for an
identity/location split.

	Noel

From randy@psg.com  Fri Feb 17 10:35:02 2012
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 5992321F85D8 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:35:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.485
X-Spam-Level: 
X-Spam-Status: No, score=-2.485 tagged_above=-999 required=5 tests=[AWL=0.114,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACAOismot+tm for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:35:01 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 74DC821F85D1 for <ietf@ietf.org>; Fri, 17 Feb 2012 10:35:01 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1RySe1-000A2j-Mt; Fri, 17 Feb 2012 18:34:57 +0000
Date: Fri, 17 Feb 2012 10:34:56 -0800
Message-ID: <m2zkch5mwf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Leif Sawyer <lsawyer@gci.com>
Subject: Re: IETF Last Calls and Godwin-like rules
In-Reply-To: <18B2C6E38A3A324986B392B2D18ABC5101D4DD6542@fnb1mbx01.gci.com>
References: <20120216194204.A407418C0A7@mercury.lcs.mit.edu> <4F3D8343.4060504@inex.ie> <m2ehtudjvt.wl%randy@psg.com> <18B2C6E38A3A324986B392B2D18ABC5101D4DD6542@fnb1mbx01.gci.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:35:02 -0000

> Who gets to decide who the experts are?

i listen the folk actually implementing and actually using.  i also
listen to researchers with expertise in the field.  the ietf politicians
are already in my ~/.procmailrc.  you are welcome to listen to whom you
wish.

> Are you telling me, that because I haven't participated in any other
> discussions

i was not telling you anything, though i wonder why you are so
defensive.

randy

From lsawyer@gci.com  Fri Feb 17 10:37:50 2012
Return-Path: <lsawyer@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADEA721E8028 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:37:50 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRKdeLswMaSt for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 10:37:50 -0800 (PST)
Received: from mailgw1.gci.com (mailgw1.gci.com [209.165.141.90]) by ietfa.amsl.com (Postfix) with ESMTP id F300721E8015 for <ietf@ietf.org>; Fri, 17 Feb 2012 10:37:49 -0800 (PST)
Received: from dtn1cas01.gci.com (10.100.4.60) by mailgw1.gci.com (172.19.0.25) with Microsoft SMTP Server (TLS) id 8.2.234.1; Fri, 17 Feb 2012 09:38:14 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by dtn1cas01.gci.com ([10.100.4.60]) with mapi; Fri, 17 Feb 2012 09:37:48 -0900
From: Leif Sawyer <lsawyer@gci.com>
To: Randy Bush <randy@psg.com>
Date: Fri, 17 Feb 2012 09:37:46 -0900
Subject: RE: IETF Last Calls and Godwin-like rules
Thread-Topic: IETF Last Calls and Godwin-like rules
Thread-Index: AcztotvUdskuCKmlR2+JoVZNJpzExwAACnzA
Message-ID: <18B2C6E38A3A324986B392B2D18ABC5101D4DD659F@fnb1mbx01.gci.com>
References: <20120216194204.A407418C0A7@mercury.lcs.mit.edu> <4F3D8343.4060504@inex.ie>	<m2ehtudjvt.wl%randy@psg.com> <18B2C6E38A3A324986B392B2D18ABC5101D4DD6542@fnb1mbx01.gci.com> <m2zkch5mwf.wl%randy@psg.com>
In-Reply-To: <m2zkch5mwf.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:37:50 -0000

Randy Bush respondeth...
> > Who gets to decide who the experts are?
>=20
> i listen the folk actually implementing and actually using.  i also
> listen to researchers with expertise in the field.  the ietf=20
> politicians
> are already in my ~/.procmailrc.  you are welcome to listen=20
> to whom you
> wish.
>=20
> > Are you telling me, that because I haven't participated in any other
> > discussions
>=20
> i was not telling you anything, though i wonder why you are so
> defensive.


I asked not for myself, but for those who do not or cannot speak.


And your answer speaks volumes.

From bob.hinden@gmail.com  Fri Feb 17 11:11:17 2012
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 BE8BB21F866E for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.512
X-Spam-Level: 
X-Spam-Status: No, score=-103.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3d4SE1T7Kx9y for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:11:15 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8154F21F85CC for <ietf@ietf.org>; Fri, 17 Feb 2012 11:11:09 -0800 (PST)
Received: by dakl33 with SMTP id l33so3735559dak.31 for <ietf@ietf.org>; Fri, 17 Feb 2012 11:10:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=Q4QuI8bmtJNpjSZIEvbCz/OlQ6LoKG8qY5qarLicXIU=; b=mLr7nX7U8aZkbFul4WywRkwTJxVW0m9IsTXRxpkAIFuUxqMgM7hogjRNcJhQZ+q8DT WsdjFu3ghEIla4w8e7OpaEYAcq8uY7QWyswuSbsZdZqnPedbKwyu39rX8JGwxQBhxHkz HSLUK9SmkRBlDev9bJ9j6Tx4wYjxfYhTBh0qE=
Received: by 10.68.239.229 with SMTP id vv5mr26955015pbc.88.1329505859019; Fri, 17 Feb 2012 11:10:59 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id j3sm5834122pbb.29.2012.02.17.11.10.56 (version=SSLv3 cipher=OTHER); Fri, 17 Feb 2012 11:10:57 -0800 (PST)
Subject: Re: Variable length internet addresses in TCP/IP: history
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <20120217183241.2267518C09A@mercury.lcs.mit.edu>
Date: Fri, 17 Feb 2012 11:10:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D7F1A74-276C-413A-8980-A013590635BD@gmail.com>
References: <20120217183241.2267518C09A@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1084)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:11:17 -0000

Noel,

On Feb 17, 2012, at 10:32 AM, Noel Chiappa wrote:

>> From: Bob Hinden <bob.hinden@gmail.com>
>=20
>> the other reason why we went with 128-bit address with a 64/64 split
>> as the common case and defining IIDs that indicate if they have
>> global uniqueness. This creates a framework that an ID/locator split
>> could be implemented. ... we have a framework that would allow it
>> without having to roll out another version of IP.=20
>=20
> Alas, the inclusion of _both halves_ of the IPv6 address in the TCP
> checksum means the framework you speak of is basically useless for an
> identity/location split.
>=20

That's why I described it as a framework.  The TCP pseudo-checksum would =
have to change and likely the addition of some sort of authentication at =
connection establishment to associate an identifiers with a set of =
locators.  Not trivial, but doable. =20

Bob





From presnick@qualcomm.com  Fri Feb 17 11:14:31 2012
Return-Path: <presnick@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 6EBDD21F86FF for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:14:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LH+a7r+jt84z for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:14:30 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E102621F8540 for <ietf@ietf.org>; Fri, 17 Feb 2012 11:14:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329506070; x=1361042070; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F3EA70A.1070306@qualcomm.com>|Date:=20Fr i,=2017=20Feb=202012=2013:14:18=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Noel=20Chiappa=20<jnc@mercury. lcs.mit.edu>|CC:=20<ietf@ietf.org>|Subject:=20Re:=20IETF =20Last=20Calls=20and=20Godwin-like=20rules|References: =20<20120217175908.9EAA718C097@mercury.lcs.mit.edu> |In-Reply-To:=20<20120217175908.9EAA718C097@mercury.lcs.m it.edu>|Content-Type:=20text/plain=3B=20charset=3D"ISO-88 59-1"=3B=20format=3Dflowed|Content-Transfer-Encoding:=207 bit|X-Originating-IP:=20[172.30.48.1]; bh=gtSs6T5QgCAN9778x6t1Hzq2UtGmMiHtwVHEhIUGCxs=; b=kcA9wfj24pVdqxBOLSgT4TNvncvqitfvhZAoEPEN1otAhll8pE0Mvayn 2sOVQrPeY8BUT1+TnI4uYWG28TE+o/LiGdGDLG0vU5Uwm7eWNGhkCKG8k Co+PO8D+ibKImid/Dw7l75VvCOxXYjjST0Hb+pz/xZxlu0t2so9SzoRY1 g=;
X-IronPort-AV: E=McAfee;i="5400,1158,6623"; a="161858506"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 17 Feb 2012 11:14:24 -0800
X-IronPort-AV: E=Sophos;i="4.73,438,1325491200"; d="scan'208";a="259518073"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 17 Feb 2012 11:14:24 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 17 Feb 2012 11:14:23 -0800
Message-ID: <4F3EA70A.1070306@qualcomm.com>
Date: Fri, 17 Feb 2012 13:14:18 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>
In-Reply-To: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:14:31 -0000

On 2/17/12 11:59 AM, Noel Chiappa wrote:
>      >  From: Pete Resnick<presnick@qualcomm.com>
>
>      >  We do need to make sure that the folks evaluating consensus know
>      >  that "voting doesn't count" and that their decisions are made by
>      >  consensus on the technical issues, not the number of people speaking.
>
> Yes, but how do you tell where the consensus is if 97% of the people in the
> 'room' haven't expressed an opinion?

Condensing part of my unfinished essay to a few sentences: You decide 
consensus based on open issues, not on number of voices. If folks have 
brought up unanswered objections, there's not consensus yet (rough or 
otherwise). If all objections have been answered (even if the answer is 
simply a well-reasoned, "We understand that that is an issue, but for 
these other reasons, we're not solving that problem", and there is not 
significant objection to dismissing the issue), then the presumption is 
that there is at least rough consensus.

If the 97% haven't expressed an opinion, you presume that they are not 
filing objections and are therefore consenting. Consensus is all about 
consent, not expressed agreement. Objection is the only way for there 
not to be consensus.

> The 'me too' posts do serve a purpose in
> giving a larger sample size (provided, of course, that they are from long-time
> IETF partipants).
>    

Not to me. I don't see what they add.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From brian.e.carpenter@gmail.com  Fri Feb 17 11:41:41 2012
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 6E3FA21F8693 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:41:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.503
X-Spam-Level: 
X-Spam-Status: No, score=-103.503 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Q7krsPWum-G for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:41:41 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id A8F7A21F8692 for <ietf@ietf.org>; Fri, 17 Feb 2012 11:41:40 -0800 (PST)
Received: by eekc41 with SMTP id c41so1483393eek.31 for <ietf@ietf.org>; Fri, 17 Feb 2012 11:41:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=t8bk36XXVp8a4ag8+iqtkl/9nWYDG1rGzfBJ+VgEqHo=; b=eJK5UfQ9wVep1d9yWov4JkvhRXzGWCJoGPHL8Wn5TNXy0fnJs4p9aR/Ct12motG+yu EiT65W4UpxsnRV6pORuOXeogklNZhzSarrL9oC9Dq3kCJPLtzvZlOAUu9Rmwn4gkZh13 P4YFc5JIJay1JG+UeyL+voeZtwNQn02GhCr8Q=
Received: by 10.213.26.198 with SMTP id f6mr1400124ebc.25.1329507699837; Fri, 17 Feb 2012 11:41:39 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id y14sm12603599eef.10.2012.02.17.11.41.36 (version=SSLv3 cipher=OTHER); Fri, 17 Feb 2012 11:41:39 -0800 (PST)
Message-ID: <4F3EAD62.4050702@gmail.com>
Date: Sat, 18 Feb 2012 08:41:22 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120217183241.2267518C09A@mercury.lcs.mit.edu> <8D7F1A74-276C-413A-8980-A013590635BD@gmail.com>
In-Reply-To: <8D7F1A74-276C-413A-8980-A013590635BD@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:41:41 -0000

On 2012-02-18 08:10, Bob Hinden wrote:
> Noel,
> 
> On Feb 17, 2012, at 10:32 AM, Noel Chiappa wrote:
> 
>>> From: Bob Hinden <bob.hinden@gmail.com>
>>> the other reason why we went with 128-bit address with a 64/64 split
>>> as the common case and defining IIDs that indicate if they have
>>> global uniqueness. This creates a framework that an ID/locator split
>>> could be implemented. ... we have a framework that would allow it
>>> without having to roll out another version of IP. 
>> Alas, the inclusion of _both halves_ of the IPv6 address in the TCP
>> checksum means the framework you speak of is basically useless for an
>> identity/location split.
>>
> 
> That's why I described it as a framework.  The TCP pseudo-checksum would have to change and likely the addition of some sort of authentication at connection establishment to associate an identifiers with a set of locators.  Not trivial, but doable.  

Authentication is not just doable, but done, in shim6. However,
shim6 ducks the checksum issue by being a shim. ILNP deals with
it up front, but is a bigger change from vanilla IPv6. The
flexibility is there, but it's academic until we get IPv6 widely
deployed.

   Brian

From ajs@anvilwalrusden.com  Fri Feb 17 11:52:55 2012
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 802D821F8692 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:52:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.932
X-Spam-Level: 
X-Spam-Status: No, score=-0.932 tagged_above=-999 required=5 tests=[AWL=-1.332, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_INFO=1.448, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bftHAswOw8eb for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 11:52:54 -0800 (PST)
Received: from pdx-1.yitter.info (unknown [174.140.166.76]) by ietfa.amsl.com (Postfix) with ESMTP id EFA8421F85B5 for <ietf@ietf.org>; Fri, 17 Feb 2012 11:52:44 -0800 (PST)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ajs@anvilwalrusden.com) by pdx-1.yitter.info (Postfix) with ESMTPSA id 33C23A35809F for <ietf@ietf.org>; Fri, 17 Feb 2012 11:52:44 -0800 (PST)
Date: Fri, 17 Feb 2012 14:52:41 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
Message-ID: <20120217195241.GH31662@mail.yitter.info>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F3EA70A.1070306@qualcomm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:52:55 -0000

On Fri, Feb 17, 2012 at 01:14:18PM -0600, Pete Resnick wrote:
> >The 'me too' posts do serve a purpose in

> Not to me. I don't see what they add.

It seems to me that the PROTO write up has a question that suggests
they add something.  It asks whether the WG is solidly behind
something, or whether there are actually just two or three people
interested and everybody else not paying attention.

I think that is an important question to answer, because the answer to
an important question that is just (for some reason) getting ignored
by a large number of IETF participants probably shouldn't be regarded
as IETF consensus in any sense.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From melinda.shore@gmail.com  Fri Feb 17 12:10:20 2012
Return-Path: <melinda.shore@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 69BF821F8535 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 12:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUWo3RS+ZCDR for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 12:10:19 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7AB21F8532 for <ietf@ietf.org>; Fri, 17 Feb 2012 12:10:19 -0800 (PST)
Received: by dakl33 with SMTP id l33so3784812dak.31 for <ietf@ietf.org>; Fri, 17 Feb 2012 12:10:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=gXSxMieXR3x9SiyC/FLHgfjO7J1pUbQw/3Z4U1Cqaoo=; b=l9cPxbmv2uEtQX90HXWFBz1y+H+fuNSHdRYKmn8O97Oc3D+kd+h7BKPuJSuUS60TXE 2VtKQp6mYJrINCmQ1voNV4FI11khVM8KY5EdWvaASXCKG2sLfErh6DOqYINsEjQGHUYa kqcC0Ds9HHyRCQaBpQzhRjXgXsxFxvOvGIHbg=
Received: by 10.68.72.9 with SMTP id z9mr27779852pbu.124.1329509419292; Fri, 17 Feb 2012 12:10:19 -0800 (PST)
Received: from polypro.local (209-193-56-188-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.56.188]) by mx.google.com with ESMTPS id b4sm17515211pbc.7.2012.02.17.12.10.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 17 Feb 2012 12:10:18 -0800 (PST)
Message-ID: <4F3EB428.1080803@gmail.com>
Date: Fri, 17 Feb 2012 11:10:16 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.26) Gecko/20120129 Lightning/1.0b2 Thunderbird/3.1.18
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>	<4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info>
In-Reply-To: <20120217195241.GH31662@mail.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:10:20 -0000

On 2/17/12 10:52 AM, Andrew Sullivan wrote:
> It seems to me that the PROTO write up has a question that suggests
> they add something.  It asks whether the WG is solidly behind
> something, or whether there are actually just two or three people
> interested and everybody else not paying attention.

What is a "working group"?

Melinda

From presnick@qualcomm.com  Fri Feb 17 12:30:47 2012
Return-Path: <presnick@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 90F261F0C4D for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 12:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tsb6Pui1HLRe for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 12:30:46 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 748D81F0C54 for <ietf@ietf.org>; Fri, 17 Feb 2012 12:30:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329510646; x=1361046646; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F3EB8DA.3070807@qualcomm.com>|Date:=20Fr i,=2017=20Feb=202012=2014:30:18=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Andrew=20Sullivan=20<ajs@anvil walrusden.com>|CC:=20<ietf@ietf.org>|Subject:=20Re:=20IET F=20Last=20Calls=20and=20Godwin-like=20rules|References: =20<20120217175908.9EAA718C097@mercury.lcs.mit.edu>=09<4F 3EA70A.1070306@qualcomm.com>=20<20120217195241.GH31662@ma il.yitter.info>|In-Reply-To:=20<20120217195241.GH31662@ma il.yitter.info>|Content-Type:=20text/plain=3B=20charset =3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=tZrPeWQyhlysBJm5tGFcwzu6WIWsj1dsd7T6dsaaQJk=; b=P4JBHD/PBHRAZk8fcdLg9dR/x8SzNS9fJMjlkC/f3sITdnWh7XlEud5h POYGbtDRgo4bd4HsfpRmdg4N1b1+LCtgWiiehWYLxriHOTp80rR1ZNsiM OE7qmScNL9SKJBSRn9/lI45nrbqxHn6bBSv5lT2CCJTCN9X5XjyNNhu6K c=;
X-IronPort-AV: E=McAfee;i="5400,1158,6623"; a="164186008"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 17 Feb 2012 12:30:21 -0800
X-IronPort-AV: E=Sophos;i="4.73,438,1325491200"; d="scan'208";a="185313767"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 17 Feb 2012 12:30:21 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 17 Feb 2012 12:30:20 -0800
Message-ID: <4F3EB8DA.3070807@qualcomm.com>
Date: Fri, 17 Feb 2012 14:30:18 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>	<4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info>
In-Reply-To: <20120217195241.GH31662@mail.yitter.info>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:30:47 -0000

On 2/17/12 1:52 PM, Andrew Sullivan wrote:
> On Fri, Feb 17, 2012 at 01:14:18PM -0600, Pete Resnick wrote:
>    
>>> The 'me too' posts do serve a purpose in
>>>        
>> Not to me. I don't see what they add.
>>      
> It seems to me that the PROTO write up has a question that suggests
> they add something.  It asks whether the WG is solidly behind
> something, or whether there are actually just two or three people
> interested and everybody else not paying attention.
>
> I think that is an important question to answer, because the answer to
> an important question that is just (for some reason) getting ignored
> by a large number of IETF participants probably shouldn't be regarded
> as IETF consensus in any sense.
>    

I agree, it's an important question to answer, but I'd suggest it is 
orthogonal to the worth of what I'm referring to as 'me too' posts.

If there's a conversation on a mailing list, even if it is among two or 
three people, I do want to know whether other people are listening (and 
thereby consenting) or whether they're sleeping. In a physical room, I 
can see the difference between "nodding of heads" and "nodding off"; not 
so easy on a mailing list. So, replying *to a particular point* during a 
discussion with the occasional, "Yup, she's right on the mark" or "I 
couldn't have said it better myself" or even "+1" when it comes from 
folks who have participated in the past is certainly a good thing, and 
it scales in a WG (since a chair/shepherd has a handle on who's 
participating and who's not).

At Last Call time (WG LC, and even moreso IETF LC), I don't find it 
useful. Last Call is a time for figuring out whether all outstanding 
objections have been addressed. If objections come up and someone agrees 
with the objection, or if there's an answer to an objection and someone 
agrees with that answer, *and I happen to know the person who is doing 
the agreeing*, then a "+1" might be useful as a sanity check. But if 
there's no outstanding objection to be answered, I don't see what "I 
agree this should be published" or "Me too" on such messages adds to my 
ability to judge consensus. I'm happy to go on the assumption that 
silence is consent. I'll trust that some folks have read and discussed 
the document.

Now, this all goes pear-shaped if there hasn't ever been any reading and 
having a real discussion. There's got to be some indication that some 
reasonable number of folks have been awake. But I can't figure that out 
from 'me too' posts unless I'm already well aware that those people are 
awake and have been participating, in which case the 'me too' didn't add 
anything.

In the small, 'me toos' (of a certain sort) can work. In the large, I 
stand by my claim: "I don't see what they add."

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From sm@resistor.net  Fri Feb 17 12:52:32 2012
Return-Path: <sm@resistor.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 DEF2621E8072 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 12:52:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.641
X-Spam-Level: 
X-Spam-Status: No, score=-102.641 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qeg2hdUgNdhu for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 12:52:30 -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 6FDE621E8074 for <ietf@ietf.org>; Fri, 17 Feb 2012 12:52:30 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1HKqMgj020772; Fri, 17 Feb 2012 12:52:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329511947; i=@resistor.net; bh=lOpm8tDaEgrY3KZ/iLOm/f6jb7LNGphmtS0XpsRNzsA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=EZr0jACnoibMCLRK/VA+fcg+h+h74J4WmGOr/uViriolEoMIe3Y1GhC8xqCA8K4rN /cQBGMvWfsQ3c20x7dfuIYxWHSjb26JrXeM9yf/Chkkl/JDxSh/Qalx3AfnW08GYe1 a+4zP2j21VvZbEXO5XU6yIIoSE18M6CUkshEybMU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329511947; i=@resistor.net; bh=lOpm8tDaEgrY3KZ/iLOm/f6jb7LNGphmtS0XpsRNzsA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=SRAIRemy3Kca/j5GZRIre3hMjTLvS8BA4K+dvE7Vx3jNOxCI9waEvCECEPP5rIFmD uZt5ILP59lA6AMLJp7SknRd+AdFOA3DNHT4Wq5DMg1txZ7Kx0PHGBk8bODzj0hml8H LGYadPrkHPNsKegbmdxPYeUak0DnHz49XJEK6nUY=
Message-Id: <6.2.5.6.2.20120217122457.0a83fd18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 17 Feb 2012 12:51:37 -0800
To: Melinda Shore <melinda.shore@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: IETF Last Calls and Godwin-like rules
In-Reply-To: <4F3EB428.1080803@gmail.com>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB428.1080803@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:52:32 -0000

Hi Melinda,
At 12:10 17-02-2012, Melinda Shore wrote:
>What is a "working group"?

It is a group, comprised of technically competent participants, 
governed by a charter which:

   1. lists relevant administrative information for the group

   2. specifies the direction or objectives of the working group and
      describes the approach that will be taken to achieve the goals;
      and

   3. Enumerates a set of milestones together with time frames for their
      completion.

The group is autonomous; it determines most of the details of its own 
operation with respect to session participation, reaching closure, etc.

For more information, see BCP 25.

Regards,
-sm


From cgrundemann@gmail.com  Fri Feb 17 13:18:56 2012
Return-Path: <cgrundemann@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 E2BC211E8075 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.641
X-Spam-Level: 
X-Spam-Status: No, score=-3.641 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKkxikMXtad9 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:18:55 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id DF47821F8593 for <ietf@ietf.org>; Fri, 17 Feb 2012 13:18:55 -0800 (PST)
Received: by dakl33 with SMTP id l33so3839240dak.31 for <ietf@ietf.org>; Fri, 17 Feb 2012 13:18:55 -0800 (PST)
Received-SPF: pass (google.com: domain of cgrundemann@gmail.com designates 10.68.220.4 as permitted sender) client-ip=10.68.220.4; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of cgrundemann@gmail.com designates 10.68.220.4 as permitted sender) smtp.mail=cgrundemann@gmail.com; dkim=pass header.i=cgrundemann@gmail.com
Received: from mr.google.com ([10.68.220.4]) by 10.68.220.4 with SMTP id ps4mr35223826pbc.32.1329513535766 (num_hops = 1); Fri, 17 Feb 2012 13:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qL4DjdLc97e3aXQojSGVzWbbHyW+WpE9waYaGSo5FmA=; b=fWccMHEWEngbzPD2SBRAJpVm0Zah2iCLYezy6MmmfjsxohX44kixgEjWKw9bc/nXyO lUccCe8HUWukkgVsr5sLU1sLsYR+n/rX6HhzJ/9+g7u/X+IzepcU8x53kmFCs8Q3q4sp h415p6a6H6Rs1ArURijVpo1p09h8P0ta3Q93A=
MIME-Version: 1.0
Received: by 10.68.220.4 with SMTP id ps4mr28563255pbc.32.1329513535699; Fri, 17 Feb 2012 13:18:55 -0800 (PST)
Received: by 10.68.60.200 with HTTP; Fri, 17 Feb 2012 13:18:55 -0800 (PST)
In-Reply-To: <4F3EB8DA.3070807@qualcomm.com>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB8DA.3070807@qualcomm.com>
Date: Fri, 17 Feb 2012 14:18:55 -0700
Message-ID: <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com>
Subject: Re: IETF Last Calls and Godwin-like rules
From: Chris Grundemann <cgrundemann@gmail.com>
To: Pete Resnick <presnick@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:18:57 -0000

> *and I happen to know the person who is doing the agreeing*

I keep hearing statements along these lines and it's a bit unnerving.
Either participation in the IETF is open, or it isn't. When a person's
opinion/view/thoughts/words/etc. are judged exclusively by "do I know
this person" then you have an Old Boys Club, not an open body.

How many people have time to read and respond to every email on every
mailing list everywhere in the world that is discussing something
relevant to them? Not many. Especially in the operator community,
people have jobs, projects, and duties that keep them from being
active in every discussion that they are interested in. Relegating
them to second class citizens (or stripping their citizenship
altogether) because they are actually spending time running a network
seems counter intuitive to me.

We should allow everyone to participate in the best way that they can
if we want them to participate at all - and if we don't, then perhaps
the ITU provides a better model for keeping the rif-raf out of
standards creation...

With hope for the future,
~Chris


> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

-- 
@ChrisGrundemann
http://chrisgrundemann.com

From stpeter@stpeter.im  Fri Feb 17 13:23:43 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A4211E8089 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QTnS-fRA9-Z for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:23:42 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3D36111E8076 for <ietf@ietf.org>; Fri, 17 Feb 2012 13:23:42 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id F359C40058; Fri, 17 Feb 2012 14:34:40 -0700 (MST)
Message-ID: <4F3EC55B.9060603@stpeter.im>
Date: Fri, 17 Feb 2012 14:23:39 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: Chris Grundemann <cgrundemann@gmail.com>
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB8DA.3070807@qualcomm.com> <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com>
In-Reply-To: <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:23:43 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2/17/12 2:18 PM, Chris Grundemann wrote:
>> *and I happen to know the person who is doing the agreeing*
> 
> I keep hearing statements along these lines and it's a bit
> unnerving. Either participation in the IETF is open, or it isn't.
> When a person's opinion/view/thoughts/words/etc. are judged
> exclusively by "do I know this person" then you have an Old Boys
> Club, not an open body.

Chris, I think Pete meant that if he happens to know the personal
context of the person who says "+1" then he can impute some meaning to
it (because he knows the person has been following the discussion,
knows what that person's concerns have been in past threads, etc.). He
is not saying that you need to be part of the club in order to gain a
hearing, only that if he doesn't know you then a mere +1 carries less
(or no) weight with him.

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk8+xVsACgkQNL8k5A2w/vx8UwCgptyPIxtXJH2+xexpuFGzoO/d
To0An2IF6fuHcLe0IYLYtEGRZ1xjcsxu
=rUY5
-----END PGP SIGNATURE-----

From cgrundemann@gmail.com  Fri Feb 17 13:29:57 2012
Return-Path: <cgrundemann@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 DE00C11E8094 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:29:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.638
X-Spam-Level: 
X-Spam-Status: No, score=-3.638 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2BO1ivByW-t for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:29:56 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id D601E11E808D for <ietf@ietf.org>; Fri, 17 Feb 2012 13:29:56 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so4347400pbc.31 for <ietf@ietf.org>; Fri, 17 Feb 2012 13:29:56 -0800 (PST)
Received-SPF: pass (google.com: domain of cgrundemann@gmail.com designates 10.68.136.4 as permitted sender) client-ip=10.68.136.4; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of cgrundemann@gmail.com designates 10.68.136.4 as permitted sender) smtp.mail=cgrundemann@gmail.com; dkim=pass header.i=cgrundemann@gmail.com
Received: from mr.google.com ([10.68.136.4]) by 10.68.136.4 with SMTP id pw4mr20349157pbb.74.1329514196773 (num_hops = 1); Fri, 17 Feb 2012 13:29:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2cg4ckU5r8zjmjJU6Ti6PZlqPt0rENUrfuJdB7FNMrw=; b=xYr8bJia7LdIVH1a1n5ga6QD8eg3Jte+a8sAa9Q+HYdM8xMOZ3Gmo99Lfi0Z+CFrAX Ea6TLNhhMBr4cV39gA95rvworhWTKAg+4SGANYNhy5UWobcErYLRYlZ1zavnFQSrYV6M GeG4nf/+f/pvJiPnc0YdN7UzIvxYMQnhL1CQk=
MIME-Version: 1.0
Received: by 10.68.136.4 with SMTP id pw4mr16404627pbb.74.1329514196734; Fri, 17 Feb 2012 13:29:56 -0800 (PST)
Received: by 10.68.60.200 with HTTP; Fri, 17 Feb 2012 13:29:56 -0800 (PST)
In-Reply-To: <4F3EC55B.9060603@stpeter.im>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB8DA.3070807@qualcomm.com> <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com> <4F3EC55B.9060603@stpeter.im>
Date: Fri, 17 Feb 2012 14:29:56 -0700
Message-ID: <CAC1-dtkSijEJ_m33qLxsLc19osje14FjfiSivP4t-87M=un7fw@mail.gmail.com>
Subject: Re: IETF Last Calls and Godwin-like rules
From: Chris Grundemann <cgrundemann@gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:29:58 -0000

On Fri, Feb 17, 2012 at 14:23, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2/17/12 2:18 PM, Chris Grundemann wrote:
>>> *and I happen to know the person who is doing the agreeing*
>>
>> I keep hearing statements along these lines and it's a bit
>> unnerving. Either participation in the IETF is open, or it isn't.
>> When a person's opinion/view/thoughts/words/etc. are judged
>> exclusively by "do I know this person" then you have an Old Boys
>> Club, not an open body.
>
> Chris, I think Pete meant that if he happens to know the personal
> context of the person who says "+1" then he can impute some meaning to
> it (because he knows the person has been following the discussion,
> knows what that person's concerns have been in past threads, etc.). He
> is not saying that you need to be part of the club in order to gain a
> hearing, only that if he doesn't know you then a mere +1 carries less
> (or no) weight with him.

I did not mean to call Pete (or anyone else) out directly, as I am
sure many/most individuals commenting here have the best intentions. I
did want to respond to what seems to be a common sentiment that has
appeared in this thread (and elsewhere previously) regarding new or
quiet participants vs. long time active participants. Hopefully my
concern is unwarranted.

Cheers,
~Chris

>
> Peter
>
> - --
> Peter Saint-Andre
> https://stpeter.im/
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk8+xVsACgkQNL8k5A2w/vx8UwCgptyPIxtXJH2+xexpuFGzoO/d
> To0An2IF6fuHcLe0IYLYtEGRZ1xjcsxu
> =rUY5
> -----END PGP SIGNATURE-----



-- 
@ChrisGrundemann
http://chrisgrundemann.com

From paul.hoffman@vpnc.org  Fri Feb 17 13:34:23 2012
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 AFCA521F85CC for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eA440sNi+UUv for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:34:23 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 318EB21F85C9 for <ietf@ietf.org>; Fri, 17 Feb 2012 13:34:23 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1HLYKnJ052289 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 17 Feb 2012 14:34:20 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: IETF Last Calls and Godwin-like rules
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F3EC55B.9060603@stpeter.im>
Date: Fri, 17 Feb 2012 13:34:20 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5C12EC1-82FB-4970-BAD4-601D26CF75B3@vpnc.org>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB8DA.3070807@qualcomm.com> <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com> <4F3EC55B.9060603@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
Cc: Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:34:23 -0000

On Feb 17, 2012, at 1:23 PM, Peter Saint-Andre wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On 2/17/12 2:18 PM, Chris Grundemann wrote:
>>> *and I happen to know the person who is doing the agreeing*
>>=20
>> I keep hearing statements along these lines and it's a bit
>> unnerving. Either participation in the IETF is open, or it isn't.
>> When a person's opinion/view/thoughts/words/etc. are judged
>> exclusively by "do I know this person" then you have an Old Boys
>> Club, not an open body.
>=20
> Chris, I think Pete meant that if he happens to know the personal
> context of the person who says "+1" then he can impute some meaning to
> it (because he knows the person has been following the discussion,
> knows what that person's concerns have been in past threads, etc.). He
> is not saying that you need to be part of the club in order to gain a
> hearing, only that if he doesn't know you then a mere +1 carries less
> (or no) weight with him.

I hope Pete meant something a bit more than that. In specific, I hope he =
meant:

if he happens to know the personal
context of the person who says "+1" then he can impute some meaning to
it, but if he doesn't know the personal context, then he needs to
put effort into finding it out

That is, in a WG where you are leading a consensus call, if you get a =
significant number of +1s or -1s from people who haven't participated in =
the conversation to date, it is your responsibility to try to find out =
why. "I just got started" is a perfectly good reason, as is "I have been =
following this silently but this is the first thing I thought was =
important"; "I was told to join the list and vote" is also context that =
is good to know.

All of this, of course, argues against the proposal that started this =
thread.

--Paul Hoffman


From john-ietf@jck.com  Fri Feb 17 13:47:58 2012
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 DF4CB21F8480 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.673
X-Spam-Level: 
X-Spam-Status: No, score=-102.673 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPX2IRCKPBCo for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 13:47:58 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4680811E8076 for <ietf@ietf.org>; Fri, 17 Feb 2012 13:47:58 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1RyVan-000JHX-5w; Fri, 17 Feb 2012 16:43:49 -0500
Date: Fri, 17 Feb 2012 16:47:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: IETF Last Calls and Godwin-like rules
Message-ID: <54BDB629FA12FFC1AC4D1BBF@PST.JCK.COM>
In-Reply-To: <B5C12EC1-82FB-4970-BAD4-601D26CF75B3@vpnc.org>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB8DA.3070807@qualcomm.com> <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com> <4F3EC55B.9060603@stpeter.im> <B5C12EC1-82FB-4970-BAD4-601D26CF75B3@vpnc.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
Cc: Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:47:59 -0000

--On Friday, February 17, 2012 13:34 -0800 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> All of this, of course, argues against the proposal that
> started this thread.

And I want to repeat, once more, that there was no proposal.
There was an observation about what I consider a problem.  That
observation was intended to make it clear that the problem I saw
was the noise, not the content of anyone's remarks and the
degree to which they should be considered.  Then there was a
comment, intended in jest, about a way to cut the noise off.

I did intend to start a small discussion about people trying to
round others up to make endorsements but the intent had more to
do with raising consciousness than about making new rules.  Over
the last few decades, I've been pretty consistent about my
position about trying to create finely-tuned rules in the IETF
and that position has never been "another layer of rules,
especially rules that require hair-splitting or knowing what
people are actually thinking, will help solve basic problems.

The people who have suggested to me offlist that it would have
been wiser to not say anything until I found a time when there
were no controversial issues in IETF Last Call were almost
certainly correct.  Sorry about that.

If what I said and when I said it confused people, I apologize
for my sense of humor.  It wouldn't be the first time others
have concluded that my sense of humor is bizarre and made
excessive inferences on that basis.

     john




From presnick@qualcomm.com  Fri Feb 17 14:02:30 2012
Return-Path: <presnick@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 EB75F21E8067 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 14:02:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.578
X-Spam-Level: 
X-Spam-Status: No, score=-106.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnoYcsUXA2wT for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 14:02:30 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id E664E21E8058 for <ietf@ietf.org>; Fri, 17 Feb 2012 14:02:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329516149; x=1361052149; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F3ECE71.30102@qualcomm.com>|Date:=20Fri, =2017=20Feb=202012=2016:02:25=20-0600|From:=20Pete=20Resn ick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Paul=20Hoffman=20<paul.hoffman @vpnc.org>|CC:=20Peter=20Saint-Andre=20<stpeter@stpeter.i m>,=20<ietf@ietf.org>|Subject:=20Re:=20IETF=20Last=20Call s=20and=20Godwin-like=20rules|References:=20<201202171759 08.9EAA718C097@mercury.lcs.mit.edu>=09<4F3EA70A.1070306@q ualcomm.com>=09<20120217195241.GH31662@mail.yitter.info> =09<4F3EB8DA.3070807@qualcomm.com>=09<CAC1-dtnExzYXUsueB1 nQwmEafoD_xMVVvbp5CHoPwc=3D+9F7mUA@mail.gmail.com>=09<4F3 EC55B.9060603@stpeter.im>=20<B5C12EC1-82FB-4970-BAD4-601D 26CF75B3@vpnc.org>|In-Reply-To:=20<B5C12EC1-82FB-4970-BAD 4-601D26CF75B3@vpnc.org>|Content-Type:=20text/plain=3B=20 charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=ufYQQoG/r2S56Xfwf+lwo3Q3tBqFciynF4LczgOqy9I=; b=Lmh9ZOTN34cNNd290AC/llTManhaxgAnrqChgqGhch3vdnAOP7YR6tfr qceqL2I5B5InRj+Y+15L9D2EXRZ3k4SSM7trUnHeJ6Gi7lGr7l6n+puPp OiV7ThUxuHosHs8DxzQw+xg3PWsWbv6mXVWtl9Uys3xdphqmvBpwWXTQi 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6623"; a="164215595"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 17 Feb 2012 14:02:29 -0800
X-IronPort-AV: E=Sophos;i="4.73,438,1325491200"; d="scan'208";a="171199008"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 17 Feb 2012 14:02:30 -0800
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 17 Feb 2012 14:02:29 -0800
Message-ID: <4F3ECE71.30102@qualcomm.com>
Date: Fri, 17 Feb 2012 16:02:25 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: IETF Last Calls and Godwin-like rules
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu>	<4F3EA70A.1070306@qualcomm.com>	<20120217195241.GH31662@mail.yitter.info>	<4F3EB8DA.3070807@qualcomm.com>	<CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com>	<4F3EC55B.9060603@stpeter.im> <B5C12EC1-82FB-4970-BAD4-601D26CF75B3@vpnc.org>
In-Reply-To: <B5C12EC1-82FB-4970-BAD4-601D26CF75B3@vpnc.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:02:31 -0000

On 2/17/12 3:34 PM, Paul Hoffman wrote:
> On Feb 17, 2012, at 1:23 PM, Peter Saint-Andre wrote:
>
>    
>> On 2/17/12 2:18 PM, Chris Grundemann wrote:
>>
>>      
>>>> *and I happen to know the person who is doing the agreeing*
>>>>          
>>> I keep hearing statements along these lines and it's a bit
>>> unnerving. Either participation in the IETF is open, or it isn't.
>>> When a person's opinion/view/thoughts/words/etc. are judged
>>> exclusively by "do I know this person" then you have an Old Boys
>>> Club, not an open body.
>>>        
>> Chris, I think Pete meant that if he happens to know the personal
>> context of the person who says "+1" then he can impute some meaning to
>> it (because he knows the person has been following the discussion,
>> knows what that person's concerns have been in past threads, etc.). He
>> is not saying that you need to be part of the club in order to gain a
>> hearing, only that if he doesn't know you then a mere +1 carries less
>> (or no) weight with him.
>>      
> I hope Pete meant something a bit more than that. In specific, I hope he meant:
>
> if he happens to know the personal
> context of the person who says "+1" then he can impute some meaning to
> it, but if he doesn't know the personal context, then he needs to
> put effort into finding it out
>    

+1. ;-)

I think I might be able to decipher what Pete meant. I think Paul and 
Peter have it mostly right.

If there's an ongoing discussion and on a technical point someone says, 
"+1", I might know what that means. If the person who said "+1" has been 
participating in the rest of the conversation and I have the context of 
what that person knows, what points they've made in the past, etc., then 
I surely understand how to take the "+1". As I said, not a whole lot of 
data, but a sanity check on the point being discussed. But if a random 
participant who has said nothing to date in the discussion simply says, 
"+1", I have no idea how to give that any weight. Is this someone who 
was instructed to come along and give a "+1", but has no idea what the 
technical conversation is about? Or is it an otherwise silent expert on 
the subject? The only way I can figure out what a "person's 
opinion/view/thoughts/words/etc." are is for us to engage with 
eachother. I do not believe that "+1" constitutes engagement. I don't 
even think, "I support this document" constitutes engagement without a 
whole lot of other historical context. If you haven't been participating 
in the conversations, you should not expect your "+1"s to be given much 
weight.

It is absolutely true that this is an open body. But that doesn't mean 
it's a voting democracy. It's a consensus organization. Your mere 
presence doesn't count. It's your participating in the consensus that 
does. Participating means explaining and objecting and defending and 
discussing. 'Me too' is not one of those things unless you've already 
done a lot of engaging already.

> That is, in a WG where you are leading a consensus call, if you get a significant number of +1s or -1s from people who haven't participated in the conversation to date, it is your responsibility to try to find out why. "I just got started" is a perfectly good reason, as is "I have been following this silently but this is the first thing I thought was important"; "I was told to join the list and vote" is also context that is good to know.
>    

I'd add that it is also the responsibility of the participants to make 
sure that they do explain why they have said "+1". This is a human 
endeavor. I might "+1" something on the expectation that "of course the 
chair knows who I am and what I know about this topic." The chair may 
instead be thinking, "OK, so this is some random schmo that his company 
sent to say 'me too'." That's a fail on both of our parts, not just the 
chair.

> All of this, of course, argues against the proposal that started this thread.
>    

Noting that the supposed "proposal" was hyperbole, I will point to my 
initial reply to Dave: We still do need to occasionally call out 
publicly that we all recognize that political 'me toos' don't count. In 
fact, we ought not do counting at all.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From touch@isi.edu  Fri Feb 17 14:47:35 2012
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 3A20D11E808D; Fri, 17 Feb 2012 14:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.7
X-Spam-Level: 
X-Spam-Status: No, score=-102.7 tagged_above=-999 required=5 tests=[AWL=-0.701, BAYES_00=-2.599, J_CHICKENPOX_65=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ys3F7jkPHeFk; Fri, 17 Feb 2012 14:47:33 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 41A8F11E80A1; Fri, 17 Feb 2012 14:47:33 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q1HMlPXL021294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Feb 2012 14:47:25 -0800 (PST)
Message-ID: <4F3ED8FC.6020400@isi.edu>
Date: Fri, 17 Feb 2012 14:47:24 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Kim Kinnear <kkinnear@cisco.com>
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com>
In-Reply-To: <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, dhcwg@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:47:35 -0000

Hi, Kim,

First, thank you for your detailed response to my quite lengthy review.

Some further clarifications and confirmations appear below.

Joe

On 2/17/2012 12:09 PM, Kim Kinnear wrote:
>
> Joe,
>
> Thank you for your review.
>
> My responses are indented, below...
>
> On Feb 13, 2012, at 5:00 PM, Joe Touch wrote:
>
>> Hi, all,
>>
> > 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. The authors should
>> consider this review together with any other last-call comments
>> they receive. Please always CC tsv-dir@ietf.org if you reply to or
>> forward this review.
>>
>> This request was received Feb. 2, 2012.
>>
>> This document describes an extension to DHCPv4 for the bulk query
>> andtransfer of current lease status over TCP.
>>
>> The following transport issues were noted, and are significant:
>>
>> UPDATES- The document updates DHCP with support for TCP, and as
>> suchthis document seems like it should UPDATE RFC2131
>
> 	While this document clearly builds on RFC 2131, it
> 	doesn't actually change anything that anyone is doing
> 	that is currently based on RFC 2131.  My understanding of
> 	"updates" is that, in order to understand the first RFC
> 	(in this case, RFC 2131), you need to read all of the
> 	RFC's that "update" it.  That isn't the case here -- you
> 	can be very happy reading and implementing DHCPv4 by
> 	reading RFC 2131 and never have to know that DHCPv4 Bulk
> 	Leasequery exists.  In general, in the DHC WG, we seem to
> 	set a pretty high bar for what "udpates" another RFC.  I
> 	don't see that this document has met those requirements.
> 	But this isn't really my call.  I'll let Ralph Droms and
> 	the DHC WG chairs decide on this one, and I'll do
> 	whatever they tell me to do.

Agreed. FWIW, my "bar" for that is whether implementing DHCPv4 as per 
RFC 2131 is changed by this doc. If DHCP fundamentally starts requiring 
TCP port support, then this doc then changes the spec as described in 
2131 IMO.

Here are the reasons I think it DOES modify DHCP:

	- Sec 10 requests option codes that extend the tables defined
	in the original RFC

I couldn't locate a recommendation on whether DHCP servers MAY implement 
this extension, SHOULD, or MUST (did I miss it? if not, it should be 
added). Regardless, that too would be a reason for this as an update to 
2131. It's only NOT an update if this service is independent, IMO, and 
it doesn't read that way to me.

>> PORT USE- Although DHCPv4 has an assigned TCP port, this document
>> should clearly indicate that there is no other specified use of that
>>. port other than the bulk lease query described in this document
>
> 	Sure.
>>
>> It should further explain why no other existing DHCP exchanges are
>> not valid on the TCP port.
>
> 	I've been taken to task by various IETF folks at
> 	varying levels of seniority for explaining too *much* of
> 	the "why".  My understanding is that this is a protocol
> 	specification and not a design document, and as such it
> 	is not only not necessary but frequently
> 	counter-productive to give lots of justifications for the
> 	decisions made when constructing the protocol.
>
> 	In this case, I can't speak for the wG at large, because
> 	we never proposed anything else.  The reason we didn't
> 	propose anything else was that we didn't want to "update"
> 	RFC 2131 with a new way to do DHCPv4 in general.  But
> 	that all kind of comes down to "because we said so".  We
> 	were trying to keep this draft focused.  But if I put
> 	words in the document which say that, someone in the WG
> 	would tell me to take them out.
>
> 	I have no problem motivating the "interesting" decisions
> 	we've made, or perhaps the contentious ones, but this one
> 	was a no-brainer that never even came up (to the best of
> 	my memory).
>
> 	Having said all of that, I'll put something in that says
> 	that we were trying to keep it simple.

Thanks. In this case, it's important to suggest why others should not 
add conventional DHCP query support to the TCP port.

>> CONNECTION MANAGEMENT- The document describes the use of TCP
>> connections for bulk transfer, but needs to be more specific about which
>> side (relay client or server) closes the connection, under what
>> circumstances, and with what mechanism (e.g., graceful CLOSE vs. ABORT,
>> as per RFC 793)
>
> 	Here is what we have now, 7.8 is for clients, 8.5 is for
> 	servers:
>
>> 7.8.  Closing Connections  [Client Section]
>>
>>     The requestor SHOULD close the connection after the
>>     DHCPLEASEQUERYDONE message is received for the last outstanding query
>>     that it has sent, if it has no more queries to send.

Under what conditions is it useful to not close at this time, and if so, 
when/why is it eventually closed?

In this case it's also useful to explain what "no more queries to send" 
means - are clients encouraged to keep the connection open in case there 
are more to send, or do you expect that the client knows when it opens 
the connection whether it has more to send - and if so, shouldn't it 
have already sent them?

>>
>> 8.5.  Closing Connections   [Server Section]
>>
>>     The DHCPv4 server SHOULD start a timer for BULK_LQ_DATA_TIMEOUT
>>     seconds for a particular connection after it sends a
>>     DHCPLEASEQUERYDONE message over that connection and if there is no
>>     current query outstanding for that connection.  It should clear this

Is this a SHOULD?

And should the timer be cleared or restarted?

Under what conditions is it useful to not close at this time, and if so, 
when/why is it closed?

>>     timer if a query arrives over that connection.  If the timer expires,
>>     the DHCPv4 server should close the connection.

Is this a SHOULD, as well?

Again, under what conditions is it useful to not close at this time, and 
if so, when/why is it closed?

>>     The server MUST close its end of the TCP connection if it encounters
>>     an error sending data on the connection.  The server MUST close its
>>     end of the TCP connection if it finds that it has to abort an in-
>>     process request.  A server aborting an in-process request SHOULD
>>     attempt to signal that to its requestors by using the QueryTerminated
>>     status code in the status-code option in a DHCPLEASEQUERYDONE
>>     message, including a message string indicating details of the reason
>>     for the abort.   If the server detects that the requesting end of the
>>     connection has been closed, the server MUST close its end of the
>>     connection.

OK. I found it a bit confusing to have this in separate places, but I 
viewed this from the transport perspective. This is fine.

> 	All connections are closed with a graceful CLOSE, and not
> 	with an ABORT.  I'll add that to the document.
>
> 	I'm at a loss to know how to be more specific about which
> 	side of the connection closes the connection.  There are
> 	rules for the client in 7.8, and rules for the server in
> 	8.5.

Somewhere you should state that the protocol exchange typically involves 
the client closing the connection, and that the server closes only under 
exceptions.

>> sec 7.3 indicates some conditions for terminating connections; this
>> section should indicate which side performs this, and by what
>> method(CLOSE, ABORT)
>
> 	Section 7.3 discusses in two places where the "requestor" may
> 	drop the connection.  The term "requestor" is used to
> 	indicate which "side" performs the actions.  All of
> 	Section 7 is about "Requestor Behavior", and the specific
> 	details of section 7.3 in all cases indicate that the
> 	instructions for dealing with the connection concern the
> 	"requestor" explicitly.
>
> 	I'll enhance the explanation to include that CLOSE should
> 	be used.
>
> 	If there is a specific set of instructions that are
> 	unclear, I don't see them, so it would help me if you
> 	could give me more detailed guidance than "Section 7.3".
> 	Thanks.

It's probably sufficient to replace "requestor" with "client" to be 
consistent. However, this section then supercedes the description in 7.8 
and 8.5 above - i.e., you are handling exceptions on the client side as 
well.

I.e., 7.8 needs to include the exception cases listed in 7.3, or they 
should just be moved there.

>>> this sec also allows connections to stay open after all pending
>>> transactions are complete (MAY); the rationale for this should be
>>> given, or the connection MUST be closed.
>
> 	I will add some words which clarify the reasons why you
> 	might want to leave the connection open after all pending
> 	transactions are complete.

FWIW, again this contradicts 7.8 which says the client SHOULD close 
after the response is received if it has no more queries to send.

This says "MAY" leave open. That's not the complement to SHOULD close.

>> the same issue applies to sec 7.8 and 8 throughout; sec 8.5 is
>> particularly problematic on this issue because it discusses aborting a
>> request using in-band data, which may not be available if the connection
>> is closed using ABORT. the state of other pending connection shsould be
>> discussed too.
>
> 	The in-band data is not required for proper protocol
> 	operation, it is valuable because it can limit the amount
> 	of data required when and if the connection is
> 	reestablished.  All connections are closed by CLOSE.  I
> 	assume that, in your comment, "other pending
> 	connection[s]" means other data flows that might exist on
> 	the TCP connection that is coming down.  I will add some
> 	words that say that those Bulk Leasequery data flows will
> 	also be stopped.

OK.

>> TIMEOUTS- Sec 6.3 defines a timeout for the TCP connection; is
>> this intended to supercede any TCP timeout? or is it intended to be
>> the min of the TCP timeout and the specified one?
>
> 	The BULK_LQ_DATA_TIMEOUT is completely application
> 	specific and essentially independent of the underlying
> 	connection timeout.  I will add words to that effect
> 	in the document.

OK.

>> This section should more carefully explain behavior when a
>> connection is dropped and the reason - e.g., timeout, abort,
>> close.
> 	
> 	The application employing Bulk Leasequery doesn't
> 	care about *why* the connection went away.  It
> 	doesn't have to know if it was abort, close, or
> 	timeout.  I will say that in this section.

Hmm. I would think that this information would be passed up to the 
application.

>> INTERLEAVING- sec 7.7 says that the server MUST interleave
>> replies;
>> there doesn't seem a valid reason for this requirement. clearly the
>> receiver MUST tolerate interleaved replies. having the server interleave
>> replies is relevant only if each request/reply has its own timeout --
>> which should be overridden if there is another response in progress
>> anyway. This issue should be more clearly explained and motivated.
>
> 	Robert Sparks offered clarification, which I like
> 	a lot and have already agreed to use:

I didn't see that; can you send that to tsv-dir@ietf.org and me?

>> 	Is the requirement you are really trying to capture "MUST
>> 	NOT block sending replies on new queries until all
>> 	replies for the existing query are complete."?
>>
>> There were some other issues noted in this document. These
>> comments appear below, and although not focused on transport
>> issues, they represent significant issues that IMO should be
>> addressed as well.
>>
>> NOTE - regarding some terminology issues, I did not survey current
>> DHCP RFCs for consistency, but IMO these terms should be corrected
>> even if they are then inconsistent with existing specs.
>> Joe
>>
>> -----------
>>
>> Major non-transport issues:
>>
>> - In many places the doc allows inaction to substitute for either
>> positive or negative confirmation. IMO, this invites implementation
>> errors, and should be avoided. E.g., status return codes, data source
>> option missing, query-for-all-configured-IPs, etc.
>
> 	While I personally tend to agree with you on this one, I
> 	have clear direction from the DHC WG that this is *not*
> 	the approach that the WG wants to take.  Here is the
> 	status code text:
>
>>     A status-code option MAY appear in the options field of a DHCPv4
>>     message.  If the status-code option does not appear, it is assumed
>>     that the operation was successful.  The status-code option SHOULD NOT
>>     appear in a message which is successful unless there is some text
>>     string that needs to be communicated to the requestor.
>
> 	This was wrangled over at some length in the DHC WG,
> 	and this was the way that it needed to be to pass
> 	last call.  I don't feel that I can change it
> 	at this time.

AOK. I'll go down on the record as noting this as a bad idea that 
invites erroneous implementations, and the IESG can decide what it wants 
to recommend.

>>
>> - the data source option reserved codes need more detailed
>> specification. if these are intended for future use, then they MUST be
>> ignored by the receiver (at least). if they are to mean anything at all,
>> at least one bit (typically all of them) MUST be set to zero by the
>> transmitter for implementations that do not support any of the component
>> fields.
>>
>> further, the length of this option MUST be 1
>
> 	Yes, subsequent to the creation of this section,
> 	Amanda Baber of IANA enlightened me regarding
> 	the different between RESERVED and UNASSIGNED.
> 	These should be UNASSIGNED, and I will add words
> 	that say that a receiver should ignore the
> 	bits that are unassigned.

Good.

>>
>> - The protocol supports bulk transfer that is not data driven.
>> This could represent a security vulnerability by exposing
>> information that may not be on the data path (and thus already
>> accessible) to a relay agent. This should be discussed in the
>> security considerations section.
>
> 	All data that is exposed has already been
> 	exposed using UDP to regular DHCP port.   But please see
> 	my response to Stephen Farrell (which is too long to include
> 	here) to see if it covers the issues about which you
> 	have concerns.

Again, I didn't see it; please send a copy to tsv-dir@ietf.org

>>
>> - Integer quantities should be referred to as "unsigned 32-bit integers" throughout.
>
> 	Good point (though some are 16 bits).  The signed-ness is not
> 	specified and should be.  I'll make sure that it is.

AOK.

>>
>> - "VPN" is used throughout to refer to "private" addresses (RFC 1918); a VPN is not just private addressing.
>
> 	Hmm.  Actually, VPN in this document does not refer to RFC 1918
> 	private addressing.  If this is important to you, could you
> 	be more specific as to your concern?

OK. I don't understand how it's being used, but if it's consistent with 
the rest of DHCP, that's fine.

However, I got thrown off by your use of 10.x.x.x.

There are appropriate addresses to use as examples in RFCs - see RFC 
5737, and please change this example accordingly.

>> - (this is a nit with all IDs, FWIW) SHOULD and SHOULD NOT are
>> used throughout without context. Any time SHOULD is used instead of
>> MUST (or SHOULD NOT rather than MUST NOT), it is useful to explain
>> a viable exception. If no such exception exists, the rationale for
>> selecting SHOULD over MUST should be included.
>
> 	This is an interesting approach, which is new to me.  I
> 	can see the value in looking for viable exceptions.  I
> 	think justifying SHOULD and not MUST is a bit much, and
> 	wouldn't make it through the "keep it short and simple"
> 	filters that the DHC WG seems to place on DHC drafts.
> 	But as I said, I'll look at every SHOULD (NOT) and see if
> 	I can find concise examples of reasons.  But I'm
> 	concerned that this will greatly lengthen the draft.

I would argue that any SHOULD that cannot be justified ought to be 
converted to a MUST ;-) That still keeps it short.

>> - It would be useful to explain why STATUS-CODE strings MUST NOT
>> be null-terminated; is that a protocol violation, or are you just
>> saying that NULLs are valid in these strings? the description
>> should be clear that the string field describes the string length
>> without any termination characters.
>
> 	I will clarify this.  Nulls are not allowed in the strings.
> 	DHCP options have an unfortunate history where some
> 	large vendors null terminated their strings even though
> 	they were not supposed to, so now we always make a big
> 	deal out of it so it doesn't happen again.

Good.

>> - start-time-of-state is expressed as an offset from base-time;
>> this appears to be the only time indicated as an offset rather than
>> as an absolute. That inconsistency invites implementation errors;
>> IMO, this should be absolute too.
>
> 	There are two kinds of time options here, input options
> 	and output options.  The input options are all absolute
> 	times.  The output options are all offset times from the
> 	base time (which by design is the only absolute time in
> 	the output packets).

That'd be very useful to explain this way. Is this typical for DHCP? 
It's quite confusing IMO.

 >       ...There are several input options
> 	defined in this document.  The start-time-of-state is the
> 	only output option defined in this draft.  It is defined
> 	as a offset to the base time in large part because the
> 	*other* output options that are used in the DHCP packet
> 	are *also* offsets to the base time.  These options are
> 	not new, but are options that already exist in other
> 	RFC's.  So, while it looks like the state-time-of-state
> 	is the odd man out at first glance, it actually is an
> 	offset time because the *other* options with which it
> 	will appear are also offset times.
>
>>
>> - option lengths: throughout, the doc refers to option lengths as
>> being "an octet"; they are *indicated* in one octet. Some are constant
>> (e.g., DCHP-STATE), some allow the contents of the octet to vary. Again,
>> this is an *unsigned integer* octet.
>
> 	Yes, the size of an option is stored in
> 	one octet.  So, yes, the length is *indicated*
> 	by the value in that one octet.
>
> 	But the length may be 1 octet, it may be
> 	5 octets, it may vary between 8 and 10 octets.
>
> 	I don't understand your concern.  Are you	
> 	saying that the length should not be
> 	stated to be "1 octet" or "5 octets"?

The length should be "indicated in 1 octet". I'm just suggesting a 
change to the way it's described. When you say "the length is an octet", 
that is ambiguous and can mean that the length value is 1, not just that 
this value is stored in one octet.

> 	I will fix the integer to be specifically
> 	unsigned (as previously indicated).
>>
>> - some of the information provided (in DHCP-STATE) goes beyond
>> that of DHCP. It would be useful to motivate the need for this
>> information in a bulk query, and why it is not similarly available
>> for nodes using UDP (e.g., as an extension to DHCPv4, not just to
>> the bulk transfer command). again, absence of state information
>> should not indicate state. State should always be expressed
>> explicitly. these states are further meaningless without a state
>> diagram explaining them. if such a diagram is not possible (as
>> noted at end of sec 6.2.7), then the states are irrelevant and the
>> option should not be included.
>
> 	The state transition diagram can certainly be drawn, but
> 	as it is fully connected, such a picture conveys no
> 	useful information.

It's sufficient to indicate this then.

 >	... The transitions are not themselves
> 	useful in any case, as the the Bulk Leasequery is a
> 	snapshot of information at one instant of time.  There is
> 	every reason to assume that as the state moves from one
> 	value to another that an external entity would not see
> 	all (or even many) of these transitions.  This is a
> 	snapshot of the DHCP state, and could be nothing else in
> 	the environment of Bulk Leasequery.
>
> 	The reason why the state transition graph is fully
> 	connected is due to the common practice in DHCPv4 of
> 	having two servers running in a failover relationship.
> 	There are then two state machines for the lease state,
> 	and at times one "leads" and the other "follows", and at
> 	other times the other "leads" and its partner "follows".
> 	So, examined individually, the state machines for each
> 	individual failover partner is fully connected because at
> 	any time it may receive an update from its partner that
> 	it decides to accept that will simply "set" the state to
> 	the value supplied by the partner.
>
> 	All of this is orthogonal to the Bulk Leasequery protocol
> 	-- except that we want the user of the Bulk Leasequery
> 	protocol to be able to make sense out of information
> 	supplied by each of the failover partners.  Or any
> 	partners running any increased availability solution.
>
> 	So, that is the reason why the dhcp-state option exists
> 	at all -- to allow the user of Bulk Leasequery to make
> 	sense out of the results of sending a Bulk Leasequery to
> 	two different (but cooperating) DHCPv4 servers.
>
> 	The DHC WG felt that this information was worthwhile to
> 	have in this document, and I agree (or we wouldn't have
> 	put it in).

Using the failover case as a justification would be helpful.

> > - in sec 6.2.9 the term "not allowed" should be explained - are
>> they reserved for future use and thus ignored? or are they "not
>> allowed" - in which case the doc should indicate handling if they
>> appear.
>
> 	Ah, good catch.  The "not allowed" will become UNASSIGNED,
> 	based on my conversation with Amanda Baber of IANA.
> 	I will add words that suggest that they should be
> 	ignored.
>
> 	The point of this table is, actually, not how to
> 	handle them (that is the up to the vpn-option draft/RFC),
> 	but rather to define a single new value.

AOK.

>> - sec 7.4 states that the clock skew of zero is desired; this
>> assumes E2E delays under 1sec. An explanation of why this is
>> desired should be given, as well as the consequences of it not.
>
> 	I have given specific instructions on how to handle non-zero
> 	clock skews.  There are no "consequences".  You code it
> 	so that it works with non-zero clock skew.  Period.
>
> 	It is desired because it is less confusing to humans.

I would argue that this then irrelevant, and there should be no 
statement about a skew of zero being preferred, since it could drive 
implementations that way unnecessarily.

>> Other non-transport issues:
>>
>> - The document includes definitions and references to irrelevant
>> deployment and implementation issues, notably DSLAMs, concentrators, and
>> access concentrators. These should not appear formally; they should be
>> used only to usefully illustrate currently intended uses.
>
> 	These appear in the text in order to give
> 	the otherwise abstract design goals some concrete
> 	examples.   We already removed a lot of the design
> 	goals, are you suggesting that they all be removed?

Actually, yes, except as examples in the intro/motivation. Elsewhere 
they are IMO distracting.

>> - The doc refers to "real-time", which could imply requirements not supported. This should be replaced with "rapid".
>
> 	I'll fix this.
>>
>> - "absolute time" *indicates* (rather than contains) the number of seconds...
>
> 	I'll fix this.
>>
>> - "third party agent" should be explained, i.e., neither DHCP client nor DHCP server.
>
> 	I will fix this.
>>
>> - "downstream" and "upstream" should be defined as both away from the server *and towards the client* ("away from the server" has two directions).
>
> 	Sure, I'll add these words.

AOK to all above.

>> - sec 3 should refer to relays, and returning the entire set or
>> individual bindings; there is no reason to explain the goals in terms of
>> access concentrators.
>
> 	I don't know about this.  I could certainly change it,
> 	but is this really important to you?  There was quite a
> 	bit of negotiation in the WG about these examples.  I
> 	don't want to restart that discussion and have it all
> 	over again.  Does this really matter that much to you?

The examples should focus on client/server/relay terminology. If other 
example terms are used, they should be parenthetical examples:

	relay (e.g., at a concentrator)

The point is that this is relevant without the concentrator. A 
concentrator is just one current example of where a relay exists, not 
the only one.

>> - sec 3.2 appears to provide contradictory advice - caching is required, but should be avoided? it would be useful to resolve this inconsistency.
>
> 	Use of Bulk Leasequery is designed to help you avoid
> 	caching.

OK - it'd be useful to be clear on that in sec 3.2.

>> - sec 3.3 refers to 'fast path', but this term doesn't make sense in this context because fast-path is a forwarding issue. it would be useful to explain what you mean, and pick a different term
>
> 	Yes, it is a forwarding issue, and many devices
> 	will not forward unless they know that they are forwarding
> 	to a device that has received a valid DHCPv4 address.
> 	The point (well, one point) of Bulk Leasequery is to
> 	allow these forwarders to gather data so that they
> 	can make the correct decision in the fast path.

Per-IP validation of that sort of permission isn't a fast-path decision. 
Fast-path involves forwarding and policy decisions (which are not 
typically /32 decisions).

It would be useful to say this information is useful so such routers can 
make the appropriate decision, but the path (fast or slow) is irrelevant 
IMO.

> ------------
>
> 	Regards -- Kim
>
>

From hgs@cs.columbia.edu  Fri Feb 17 20:26:45 2012
Return-Path: <hgs@cs.columbia.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 D198021E8013 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 20:26:45 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aoo0r+7Rngud for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2012 20:26:45 -0800 (PST)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id F041F21E801D for <ietf@ietf.org>; Fri, 17 Feb 2012 20:26:44 -0800 (PST)
Received: from dhcp-13-122.cs.columbia.edu (dhcp-13-122.cs.columbia.edu [128.59.13.122]) (user=hgs10 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q1I4Qh4L023895 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 17 Feb 2012 23:26:43 -0500 (EST)
Subject: Re: IETF Last Calls and Godwin-like rules
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <4F3EA70A.1070306@qualcomm.com>
Date: Fri, 17 Feb 2012 23:26:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDF9C212-4E1B-4067-8EAE-D78B98892C72@cs.columbia.edu>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1257)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 04:26:45 -0000

You are assuming that the truth value of statements can be decided by an =
impartial, technically-competent observer. In some of the recent =
discussions, many of the claims were "X is (not) going to do Y in the =
future" or "Using X may cause Y do to something". Unless the observer =
has a crystal ball, such statements are hard to evaluate objectively. In =
that case, predictions made by a larger number of (reasonably-informed) =
individuals may well have more weight, under the not-unreasonable =
assumption that conventional wisdom is often right.

Henning

On Feb 17, 2012, at 2:14 PM, Pete Resnick wrote:

> On 2/17/12 11:59 AM, Noel Chiappa wrote:
>>     >  From: Pete Resnick<presnick@qualcomm.com>
>>=20
>>     >  We do need to make sure that the folks evaluating consensus =
know
>>     >  that "voting doesn't count" and that their decisions are made =
by
>>     >  consensus on the technical issues, not the number of people =
speaking.
>>=20
>> Yes, but how do you tell where the consensus is if 97% of the people =
in the
>> 'room' haven't expressed an opinion?
>=20
> Condensing part of my unfinished essay to a few sentences: You decide =
consensus based on open issues, not on number of voices. If folks have =
brought up unanswered objections, there's not consensus yet (rough or =
otherwise). If all objections have been answered (even if the answer is =
simply a well-reasoned, "We understand that that is an issue, but for =
these other reasons, we're not solving that problem", and there is not =
significant objection to dismissing the issue), then the presumption is =
that there is at least rough consensus.
>=20
> If the 97% haven't expressed an opinion, you presume that they are not =
filing objections and are therefore consenting. Consensus is all about =
consent, not expressed agreement. Objection is the only way for there =
not to be consensus.
>=20
>> The 'me too' posts do serve a purpose in
>> giving a larger sample size (provided, of course, that they are from =
long-time
>> IETF partipants).
>>  =20
>=20
> Not to me. I don't see what they add.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: =
(858)651-1102
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From touch@isi.edu  Fri Feb 17 22:50:28 2012
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 608D121E8021; Fri, 17 Feb 2012 22:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itzW6+9d6I6e; Fri, 17 Feb 2012 22:50:23 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 41D1821E8014; Fri, 17 Feb 2012 22:50:19 -0800 (PST)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id q1I6napv021472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 Feb 2012 22:49:46 -0800 (PST)
Message-ID: <4F3F4A00.1010508@isi.edu>
Date: Fri, 17 Feb 2012 22:49:36 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <4F398BA4.3010400@isi.edu> <E5250394-BEAE-4733-910C-115BD7801CC7@cisco.com>
In-Reply-To: <E5250394-BEAE-4733-910C-115BD7801CC7@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, dhcwg@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:50:28 -0000

Hi, Kim,

On 2/17/2012 12:22 PM, Kim Kinnear wrote:
>
> On Feb 13, 2012, at 5:16 PM, Joe Touch wrote:
>
>> Hi, all,
>>
>> One additional transport suggestion:
>>
>> - it would be useful to include recommended configurations for TCP
>> connections. Given these are multi-byte request/response exchanges,
>> Nagle should be disabled, e.g.
 >
> 	One of the co-authors had this to
> 	say:
>>
>>    A bone headed implementation (either client or server) might send
>>    bits and pieces of a message (for example, it would be easy for
>>    an implementation to send the 2 bytes for the length of the
>>    message in one request and then the message in a second). This is
>>    exactly what you want the TCP protections for. So, I think we
>>    should be silent on this issue.  I also can't see how there is
>>    any harm in leaving it enabled (even in a 'clean'
>>    implementation).

The harm is that Nagle will then eat into your own specifications (in 
this document) for minimums for timeouts.

This is exactly where a protocol document should be specific - 
interactions between the transport and other layers (and is one of the 
key reasons for transport directorate review).

Joe

> 	I tend to agree with him -- I don't see that this 	
> 	is going to cause a problem if we don't disable
> 	it.  But maybe I'm missing something.  Is there
> 	an important problem if we don't specify this one
> 	way or another?
>
> 	Thanks -- Kim
>
>
>>
>> Joe
>>
>> On 2/13/2012 2:00 PM, Joe Touch wrote:
>>> Hi, all,
>>>
>>> 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. The authors should consider this review together with
>>> any other last-call comments they receive. Please always CC
>>> tsv-dir@ietf.org if you reply to or forward this review.
>>>
>>> This request was received Feb. 2, 2012.
>>>
>>> This document describes an extension to DHCPv4 for the bulk query and
>>> transfer of current lease status over TCP.
>>>
>>> The following transport issues were noted, and are significant:
>>>
>>> UPDATES- The document updates DHCP with support for TCP, and as such
>>> this document seems like it should UPDATE RFC2131
>>>
>>> PORT USE- Although DHCPv4 has an assigned TCP port, this document should
>>> clearly indicate that there is no other specified use of that port other
>>> than the bulk lease query described in this document
>>>
>>> It should further explain why no other existing DHCP exchanges are not
>>> valid on the TCP port.
>>>
>>> CONNECTION MANAGEMENT- The document describes the use of TCP connections
>>> for bulk transfer, but needs to be more specific about which side (relay
>>> client or server) closes the connection, under what circumstances, and
>>> with what mechanism (e.g., graceful CLOSE vs. ABORT, as per RFC 793)
>>>
>>> sec 7.3 indicates some conditions for terminating connections; this
>>> section should indicate which side performs this, and by what method
>>> (CLOSE, ABORT)
>>>
>>> this sec also allows connections to stay open after all pending
>>> transactions are complete (MAY); the rationale for this should be given,
>>> or the connection MUST be closed.
>>>
>>> the same issue applies to sec 7.8 and 8 throughout; sec 8.5 is
>>> particularly problematic on this issue because it discusses aborting a
>>> request using in-band data, which may not be available if the connection
>>> is closed using ABORT. the state of other pending connection shsould be
>>> discussed too.
>>>
>>> TIMEOUTS- Sec 6.3 defines a timeout for the TCP connection; is this
>>> intended to supercede any TCP timeout? or is it intended to be the min
>>> of the TCP timeout and the specified one?
>>>
>>> This section should more carefully explain behavior when a connection is
>>> dropped and the reason - e.g., timeout, abort, close.
>>>
>>> INTERLEAVING- sec 7.7 says that the server MUST interleave replies;
>>> there doesn't seem a valid reason for this requirement. clearly the
>>> receiver MUST tolerate interleaved replies. having the server interleave
>>> replies is relevant only if each request/reply has its own timeout --
>>> which should be overridden if there is another response in progress
>>> anyway. This issue should be more clearly explained and motivated.
>>>
>>> There were some other issues noted in this document. These comments
>>> appear below, and although not focused on transport issues, they
>>> represent significant issues that IMO should be addressed as well.
>>>
>>> NOTE - regarding some terminology issues, I did not survey current DHCP
>>> RFCs for consistency, but IMO these terms should be corrected even if
>>> they are then inconsistent with existing specs.
>>>
>>> Joe
>>>
>>> -----------
>>>
>>> Major non-transport issues:
>>>
>>> - In many places the doc allows inaction to substitute for either
>>> positive or negative confirmation. IMO, this invites implementation
>>> errors, and should be avoided. E.g., status return codes, data source
>>> option missing, query-for-all-configured-IPs, etc.
>>>
>>> - the data source option reserved codes need more detailed
>>> specification. if these are intended for future use, then they MUST be
>>> ignored by the receiver (at least). if they are to mean anything at all,
>>> at least one bit (typically all of them) MUST be set to zero by the
>>> transmitter for implementations that do not support any of the component
>>> fields.
>>>
>>> further, the length of this option MUST be 1
>>>
>>> - The protocol supports bulk transfer that is not data driven. This
>>> could represent a security vulnerability by exposing information that
>>> may not be on the data path (and thus already accessible) to a relay
>>> agent. This should be discussed in the security considerations section.
>>>
>>> - Integer quantities should be referred to as "unsigned 32-bit integers"
>>> throughout.
>>>
>>> - "VPN" is used throughout to refer to "private" addresses (RFC 1918); a
>>> VPN is not just private addressing.
>>>
>>> - (this is a nit with all IDs, FWIW) SHOULD and SHOULD NOT are used
>>> throughout without context. Any time SHOULD is used instead of MUST (or
>>> SHOULD NOT rather than MUST NOT), it is useful to explain a viable
>>> exception. If no such exception exists, the rationale for selecting
>>> SHOULD over MUST should be included.
>>>
>>> - It would be useful to explain why STATUS-CODE strings MUST NOT be
>>> null-terminated; is that a protocol violation, or are you just saying
>>> that NULLs are valid in these strings? the description should be clear
>>> that the string field describes the string length without any
>>> termination characters.
>>>
>>> - start-time-of-state is expressed as an offset from base-time; this
>>> appears to be the only time indicated as an offset rather than as an
>>> absolute. That inconsistency invites implementation errors; IMO, this
>>> should be absolute too.
>>>
>>> - option lengths: throughout, the doc refers to option lengths as being
>>> "an octet"; they are *indicated* in one octet. Some are constant (e.g.,
>>> DCHP-STATE), some allow the contents of the octet to vary. Again, this
>>> is an *unsigned integer* octet.
>>>
>>> - some of the information provided (in DHCP-STATE) goes beyond that of
>>> DHCP. It would be useful to motivate the need for this information in a
>>> bulk query, and why it is not similarly available for nodes using UDP
>>> (e.g., as an extension to DHCPv4, not just to the bulk transfer
>>> command). again, absence of state information should not indicate state.
>>> State should always be expressed explicitly. these states are further
>>> meaningless without a state diagram explaining them. if such a diagram
>>> is not possible (as noted at end of sec 6.2.7), then the states are
>>> irrelevant and the option should not be included.
>>>
>>> - in sec 6.2.9 the term "not allowed" should be explained - are they
>>> reserved for future use and thus ignored? or are they "not allowed" - in
>>> which case the doc should indicate handling if they appear.
>>>
>>> - sec 7.4 states that the clock skew of zero is desired; this assumes
>>> E2E delays under 1sec. An explanation of why this is desired should be
>>> given, as well as the consequences of it not.
>>>
>>> Other non-transport issues:
>>>
>>> - The document includes definitions and references to irrelevant
>>> deployment and implementation issues, notably DSLAMs, concentrators, and
>>> access concentrators. These should not appear formally; they should be
>>> used only to usefully illustrate currently intended uses.
>>>
>>> - The doc refers to "real-time", which could imply requirements not
>>> supported. This should be replaced with "rapid".
>>>
>>> - "absolute time" *indicates* (rather than contains) the number of
>>> seconds...
>>>
>>> - "third party agent" should be explained, i.e., neither DHCP client nor
>>> DHCP server.
>>>
>>> - "downstream" and "upstream" should be defined as both away from the
>>> server *and towards the client* ("away from the server" has two
>>> directions).
>>>
>>> - sec 3 should refer to relays, and returning the entire set or
>>> individual bindings; there is no reason to explain the goals in terms of
>>> access concentrators.
>>>
>>> - sec 3.2 appears to provide contradictory advice - caching is required,
>>> but should be avoided? it would be useful to resolve this inconsistency.
>>>
>>> - sec 3.3 refers to 'fast path', but this term doesn't make sense in
>>> this context because fast-path is a forwarding issue. it would be useful
>>> to explain what you mean, and pick a different term
>>>
>>> ----
>>>
>>>
>>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>

From rdroms.ietf@gmail.com  Sat Feb 18 04:39:31 2012
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 514EB21F84E2; Sat, 18 Feb 2012 04:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.474
X-Spam-Level: 
X-Spam-Status: No, score=-103.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GebVYFaplKM3; Sat, 18 Feb 2012 04:39:30 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6502821F84E0; Sat, 18 Feb 2012 04:39:30 -0800 (PST)
Received: by qan41 with SMTP id 41so4479209qan.10 for <multiple recipients>; Sat, 18 Feb 2012 04:39:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=7KIYHoOY9UUUKl1bMMQjArWgQNTzvmGfnSo85uPJ9Og=; b=v2Bbg8XHeiPSJk/K6KbKCTMHuCF5E5v6s3iPmmyXJeonGeP/i4bVKoSLvIKoEjQwd1 MyWlC+xd97ScO6H76N98S6IdC0mtzwA78FntTo6NG1hKZveOX0WotPH7EkI1GkW2ecDu SpxDa740Ccgnm1A9QbxTwF3S1CtQPZFgu3W7E=
Received: by 10.229.136.199 with SMTP id s7mr7663590qct.145.1329568767811; Sat, 18 Feb 2012 04:39:27 -0800 (PST)
Received: from rtp-rdroms-8916.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id o8sm32990678qan.11.2012.02.18.04.39.25 (version=SSLv3 cipher=OTHER); Sat, 18 Feb 2012 04:39:26 -0800 (PST)
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4F3ED8FC.6020400@isi.edu>
Date: Sat, 18 Feb 2012 07:39:23 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE23A10C-D05B-4221-98A8-70FA97D550FB@gmail.com>
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1251.1)
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:39:31 -0000

Joe, Kim...

On Feb 17, 2012, at 5:47 PM 2/17/12, Joe Touch wrote:

> Hi, Kim,
>=20
> First, thank you for your detailed response to my quite lengthy =
review.
>=20
> Some further clarifications and confirmations appear below.
>=20
> Joe
>=20
> On 2/17/2012 12:09 PM, Kim Kinnear wrote:
>>=20
>> Joe,
>>=20
>> Thank you for your review.
>>=20
>> My responses are indented, below...
>>=20
>> On Feb 13, 2012, at 5:00 PM, Joe Touch wrote:
>>=20
>>> Hi, all,
>>>=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. The authors should
>>> consider this review together with any other last-call comments
>>> they receive. Please always CC tsv-dir@ietf.org if you reply to or
>>> forward this review.
>>>=20
>>> This request was received Feb. 2, 2012.
>>>=20
>>> This document describes an extension to DHCPv4 for the bulk query
>>> andtransfer of current lease status over TCP.
>>>=20
>>> The following transport issues were noted, and are significant:
>>>=20
>>> UPDATES- The document updates DHCP with support for TCP, and as
>>> suchthis document seems like it should UPDATE RFC2131
>>=20
>> 	While this document clearly builds on RFC 2131, it
>> 	doesn't actually change anything that anyone is doing
>> 	that is currently based on RFC 2131.  My understanding of
>> 	"updates" is that, in order to understand the first RFC
>> 	(in this case, RFC 2131), you need to read all of the
>> 	RFC's that "update" it.  That isn't the case here -- you
>> 	can be very happy reading and implementing DHCPv4 by
>> 	reading RFC 2131 and never have to know that DHCPv4 Bulk
>> 	Leasequery exists.  In general, in the DHC WG, we seem to
>> 	set a pretty high bar for what "udpates" another RFC.  I
>> 	don't see that this document has met those requirements.
>> 	But this isn't really my call.  I'll let Ralph Droms and
>> 	the DHC WG chairs decide on this one, and I'll do
>> 	whatever they tell me to do.
>=20
> Agreed. FWIW, my "bar" for that is whether implementing DHCPv4 as per =
RFC 2131 is changed by this doc. If DHCP fundamentally starts requiring =
TCP port support, then this doc then changes the spec as described in =
2131 IMO.

Joe - I don't see that this document fundamentally requires TCP port =
support for DHCP operation as described in RFC 2131.  This document =
describes a protocol that is closely related to but independent of RFC =
2131, and a server based on RFC 2131 can perform all the DHCP functions =
in RFC 2131 without considering this document.  So, I can see your point =
but I disagree that this document updates RFC 2131.

> Here are the reasons I think it DOES modify DHCP:
>=20
> 	- Sec 10 requests option codes that extend the tables defined
> 	in the original RFC
>=20
> I couldn't locate a recommendation on whether DHCP servers MAY =
implement this extension, SHOULD, or MUST (did I miss it? if not, it =
should be added). Regardless, that too would be a reason for this as an =
update to 2131. It's only NOT an update if this service is independent, =
IMO, and it doesn't read that way to me.

There are other RFCs that add new, independent functions to DHCP without =
making changes to RFC 2131 (e.g., RFC 4388), which are not listed as =
updating RFC 2131.

- Ralph
>=20


From sm@resistor.net  Sat Feb 18 11:55:40 2012
Return-Path: <sm@resistor.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 6818421F8545 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2012 11:55:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.64
X-Spam-Level: 
X-Spam-Status: No, score=-103.64 tagged_above=-999 required=5 tests=[AWL=0.959, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60YWK88-gqwt for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2012 11:55:36 -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 0073021F8546 for <ietf@ietf.org>; Sat, 18 Feb 2012 11:55:35 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1IJtSUE011423; Sat, 18 Feb 2012 11:55:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1329594933; i=@resistor.net; bh=9meV8ZayUaz3bIn7XQtTC6kza59LlmayZCpkv7exczg=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=H24jvNAD+ZtShS8Pl+OMnpcdMig7fKI2bb2D5pJrsvtUO0EYnRqJdF65zR9AjssF8 tXtZ6xnKH5T5HlCXAu3s/d2GnN7HuN3k7SSHR5IffFpvZfP05APEnIPvT/RJcHjJXv T7S1DCE3dV8B0mZJb/VlO0IxoKeSbFBCnAwRmChM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1329594933; i=@resistor.net; bh=9meV8ZayUaz3bIn7XQtTC6kza59LlmayZCpkv7exczg=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=B6IWb4W23++IgaipZETgboVY8LtKJxG/F4dOkgeGeuCWpE+dqQ2bMxvcW/qlMb3L+ xt1P4QFwnuGez79bKzl5kasRHJGFgDQPn9r9sncF/N7MDB1oTp7t3Q/KtSBwP4Jj3E /QLRpvKq24x6KBHPNTG23FE/wKD28ITX8DVcoC5Q=
Message-Id: <6.2.5.6.2.20120218093408.08bddbf0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 18 Feb 2012 11:53:36 -0800
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: IETF Last Calls and Godwin-like rules
In-Reply-To: <54BDB629FA12FFC1AC4D1BBF@PST.JCK.COM>
References: <20120217175908.9EAA718C097@mercury.lcs.mit.edu> <4F3EA70A.1070306@qualcomm.com> <20120217195241.GH31662@mail.yitter.info> <4F3EB8DA.3070807@qualcomm.com> <CAC1-dtnExzYXUsueB1nQwmEafoD_xMVVvbp5CHoPwc=+9F7mUA@mail.gmail.com> <4F3EC55B.9060603@stpeter.im> <B5C12EC1-82FB-4970-BAD4-601D26CF75B3@vpnc.org> <54BDB629FA12FFC1AC4D1BBF@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:55:40 -0000

At 13:47 17-02-2012, John C Klensin wrote:
>I did intend to start a small discussion about people trying to
>round others up to make endorsements but the intent had more to
>do with raising consciousness than about making new rules.  Over

Some people might say that it was courageous of you to do that.  Now, 
the question is what "courageous" means. :-)

The following topics generated high traffic on this list:

   shared address space - money

   mpls-tp-oam - SDO

   two-maturity - IETF politics

   6to4-historic - ivory tower

   tls-authz - ideology


Three of the above made it through the IESG.  One of them came out of 
a WG.  One of them was clearly a letter-writing campaign.  That 
delayed but did not change the outcome.  If the "wisdom of the 
crowds" was applied, the outcome would have been the reverse.  It 
would be interesting to know what materially affected the 
decision-making in the above.

BTW, there is nothing wrong with raising consciousness about border 
collies as long as you do not mention who is the sheep.

Regards,
-sm  


From mohta@necom830.hpcl.titech.ac.jp  Mon Feb 20 01:14:50 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05A0321F86F8 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2012 01:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.669
X-Spam-Level: 
X-Spam-Status: No, score=0.669 tagged_above=-999 required=5 tests=[AWL=-0.730,  BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VyAEdLxmYQB for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2012 01:14:49 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 7368421F8619 for <ietf@ietf.org>; Mon, 20 Feb 2012 01:14:48 -0800 (PST)
Received: (qmail 36293 invoked from network); 20 Feb 2012 09:31:14 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 20 Feb 2012 09:31:14 -0000
Message-ID: <4F420EE5.20909@necom830.hpcl.titech.ac.jp>
Date: Mon, 20 Feb 2012 18:14:13 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Variable length internet addresses in TCP/IP: history
References: <20120214035317.1397C18C0D5@mercury.lcs.mit.edu> <4F3A9A55.8080908@isi.edu> <0A4CECD7-D588-4E41-A103-41C4775B92E2@shinkuro.com> <E7DE6F55-53D2-48E8-9436-F4DD1D9CA097@harvard.edu> <50728774-C6AC-4A2B-9F3E-14302D834AE0@cs.columbia.edu> <4F3C5132.9050905@necom830.hpcl.titech.ac.jp> <DEF75C24-6381-4C8B-A803-E65DD01E26AE@cs.columbia.edu> <4F3DADBF.8030006@necom830.hpcl.titech.ac.jp> <8F27A1E6-A631-476E-B158-F0DCD39123C2@cs.columbia.edu> <91957AEB-3DBF-4547-A0A5-B5FA77CB5A92@gmail.com>
In-Reply-To: <91957AEB-3DBF-4547-A0A5-B5FA77CB5A92@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 09:14:50 -0000

Bob Hinden wrote:

>> ID/locator split, which I've been
>> a proponent of for very many years, works a lot better with more bits,
>> because it allows topological addressing both within and outside an
>> organization.

> To confirm what your are saying about an ID/locator split in
> IPv6, that the other reason why we went with 128-bit address
> with a 64/64 split as the common case and defining IIDs
> that indicate if they have global uniqueness.  This creates
> a framework that an ID/locator split could be implemented.

I actually implemented such a system about 10 years ago
and it worked fine.

It was an experiment for hosts to use multiple IPv4 and IPv6
addresses, some of which may have ID/loc separation. DNS
was used for ID->loc mapping. Mobility was also supported
with multiple home locators and multiple foreign locators.

We did something related to end to end multihoming and
happy eyeball.

ID locator separation was good, because it requires about
half amount of space to store multiple addresses sharing
an ID.

Moreover, rewriting destination locators enables elegant
forwarding from home agents to mobile nodes without
tunneling (and associated MTU tax), if transport check
sums do not involve locators.

But, that's all. It was not very interesting that I
abandoned further work on it after government funding
period expired.

> Opinions vary if ID/locator split is useful, but we have a
> framework that would allow it without having to roll
> out another version of IP.  A win IMHO.

Assuming address must be 16B long, it may be good to
have ID/loc separation.

However, if we have choice, having 8B long addresses
is much better, because it is more compact than 16B
address with ID/loc separation.

Even with 8B addresses, we can rewrite destination addresses,
if there is a destination header option (or a mandatory field)
"original destination address" to be used to confirm transport
identity and checksum.

So, along with the failure with a lot of confusion to have
SLAAC, we can conclude that IPv6 addresses should have been
8B long.

Maybe, even with the current IPv6 packet format, routers
can look only at first 8B of addresses and ignore the
latter 8B (used as "original source/destination address"
for source/destination address rewriting).

						Masataka Ohta

From julian.reschke@gmx.de  Mon Feb 20 11:50:01 2012
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 B789221F855E for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2012 11:50:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.239
X-Spam-Level: 
X-Spam-Status: No, score=-104.239 tagged_above=-999 required=5 tests=[AWL=-1.640, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uSgpXM898oVz for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2012 11:50:01 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 7E4E921F853E for <ietf@ietf.org>; Mon, 20 Feb 2012 11:50:00 -0800 (PST)
Received: (qmail invoked by alias); 20 Feb 2012 19:49:59 -0000
Received: from p3EE270E3.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.112.227] by mail.gmx.net (mp039) with SMTP; 20 Feb 2012 20:49:59 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19K4asPMq5KKSH3ThSxizmSx96VetrfnMgiS13MKm 5n9CEUqruE83oV
Message-ID: <4F42A3E5.5030109@gmx.de>
Date: Mon, 20 Feb 2012 20:49:57 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
References: <20120211004840.7836.15484.idtracker@ietfa.amsl.com>
In-Reply-To: <20120211004840.7836.15484.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:50:01 -0000

On 2012-02-11 01:48, The IESG wrote:
>
> The IESG has received a request from the Reliable Multicast Transport WG
> (rmt) to consider the following document:
> - 'FLUTE - File Delivery over Unidirectional Transport'
>    <draft-ietf-rmt-flute-revised-13.txt>  as a 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 2012-02-24. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> ...

Here are a few comments, mainly of editorial nature:

Below my review notes; just mechanical checks, and some checks on the 
relation to HTTP header fields...:

Section 3:

"File name (usually, this can be concluded from the URI). In the above 
example: "file.txt"."

...or the Content-Disposition header field (RFC 6266).

"File type, expressed as MIME media type. In the above example: 
"text/plain"."

s/MIME media type/internet media type/


3.4.2:

"Where the MD5 message digest is described, the attribute "Content-MD5" 
MUST be used for the purpose as defined in [RFC2616]."

Note that Content-MD5 is gone from HTTPbis.

XML-Schema: I believe the spec should state what to do with invalid 
input. Are there extension points (like ignoring unknown elements in 
extension namespaces)?

"It is RECOMMENDED that the new attributes applied in the FDT are in the 
format of MIME fields and are either defined in the HTTP/1.1 
specification [RFC2616] or another well-known specification."

As this is a normative requirement it needs to be clarified what header 
fields are used? HTTP? MIME?

Also, well-known is irrelevant, we have a registry for header fields.

8.1:

Actually, what's requested is a URN for the XML namespace 
("urn:ietf:params:xml:ns:fdt"). That's fine; I don't think the XML 
schema needs to be registered. Otherwise, see 
<http://tools.ietf.org/html/rfc3688#section-3.2>.

8.2:

Has the media type registration been reviewed on ietf-types?

8.3:

You need to define the IANA procedure (see RFC 5226).

Appendix B:

The example contains a schemaLocation with a relative (URI) reference 
("ietf-flute-fdt.xsd"). That's misleading, right?


References:

Please cite W3C spec with their full details, like this:

<http://greenbytes.de/tech/webdav/rfc2629xslt/w3c-references.html#ref-REC-xmlschema-1-20010502>

Speaking of which; shouldn't you cite the Second Edition?

[RMT-SIMPLE-AUTH]: this should be cited using the default ID style, in 
which case xml2rfc will add the helpful "work-in-progress" label

Should RFC2357 be in the references?

You may want to cite RFC3986 (URI).

Formatting: I note that in-document links haven't been generated using 
xml2rfc's linking features; this way references to section numbers can 
break easily. I did not check those.

Best regards, Julian

From stephen.farrell@cs.tcd.ie  Tue Feb 21 10:26:38 2012
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 4140021F88D4; Tue, 21 Feb 2012 10:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0F0VlWv3qAbT; Tue, 21 Feb 2012 10:26:33 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 3539D21F889C; Tue, 21 Feb 2012 10:26:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 52ABA171D04; Tue, 21 Feb 2012 18:26:32 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1329848787; bh=vZfhfdI2JPt+S5 wBz+xyq8oBWnZfs7Cypgr8LqSsrLI=; b=W64wwWj7pP0qB02XfGLWmZgYA30s2J cjOVRxbTnaLFe3pIzD3WAR33Am/H40BzgSu4n0o+fmztc91XcgDaUmWCllITCx8E FSZqbVATa/vudvBHMd1zyP5DwuuTofCScbi0GxcVRgdaXKISmvaGVEk+2LOhNCrJ v0olf5R39ddHFdBMl7LbgmF0T7ssXLiRx4XZndacy6Okcx2DgPkFQiVwLaNqBNBI pvqEpd/GhS8RhkeHC3CkiuSjt/uBQTGSrvlMvFfVyXeXfyVuvu97ByIlVkCiKh8K z1jy5r+v3mVnYKV7WEGy1ydromEO6UNu4gAMTWXTNrHgKge9l5/7rckg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id czoRHLUbD36N; Tue, 21 Feb 2012 18:26:27 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id DB40A171CFD; Tue, 21 Feb 2012 18:26:26 +0000 (GMT)
Message-ID: <4F43E1D3.4070201@cs.tcd.ie>
Date: Tue, 21 Feb 2012 18:26:27 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: iesg@ietf.org
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>
In-Reply-To: <20120221181006.43AB121F87BF@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:26:38 -0000

Down below, for the proposed HTTP/2.0 work it says:

 > * Reflecting modern security requirements and practices

In some earlier discussion I asked what "modern" means
there. It seems to mean at least working well with TLS,
but I'm not sure what else is meant, if anything.

In particular, I think it'd be good to try get better
(more usable, more secure etc.) HTTP authentication
defined as a built-in part of HTTP/2.0.

My initial take is that if we're not going to do this
for a major revision of the protocol, then when are we
going to do it? So I'd like to see that included.

The counter argument offered was that better HTTP
authentication is complex and probably hard to get right
and so would be better handled separately.

While that's not an unreasonable point, my counter-counter
argument is that it doesn't seem to have worked very well
so far.

It was also argued that this charter is scoped to just
allow for selection of an initial candidate for HTTP/2.0
and there'd be another re-charter to follow based on that
selected candidate, so that discussion of specific
security features would be better done after that when
there's a specific protocol on which to do work.

My worry about that is that in practice the main
security aspects of a putative HTTP/2.0 will be very
hard to change at that point, so I'd like to see it
discussed as part of this phase of the work.

What do others think?

Thanks,
Stephen.

PS: When I say "like" above, that's what I'd personally
like, not a position that I'm adopting as a security AD.
(Alhough that'd be a fairly predictable position I guess:-)


On 02/21/2012 06:10 PM, IESG Secretary wrote:
> A modified charter has been submitted for the Hypertext Transfer
> Protocol Bis (httpbis) working group in the Applications Area of the
> IETF.  The IESG has not made any determination as yet.  The modified
> charter is provided below for informational purposes only.  Please send
> your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
> February 28, 2012.
>
> Hypertext Transfer Protocol Bis (httpbis)
> =========================================
>
> Charter
> Last Modified: 2012-02-09
>
> Current Status: Active Working Group
>
> Chair(s):
>      Mark Nottingham<mnot@mnot.net>
>
> Applications Area Director(s):
>      Pete Resnick<presnick@qualcomm.com>
>      Peter Saint-Andre<stpeter@stpeter.im>
>
> Applications Area Advisor:
>      Peter Saint-Andre<stpeter@stpeter.im>
>
> Mailing Lists:
>      General Discussion:ietf-http-wg@w3.org
>      To Subscribe:      ietf-http-wg-request@w3.org
>          In Body:       subscribe
>      Archive:           http://lists.w3.org/Archives/Public/ietf-http-wg/
>
> Description of Working Group
> ----------------------------
>
> This Working Group is charged with maintaining and developing
> the "core" specifications for HTTP.
>
> The Working Group's specification deliverables are:
> * A document (or set of documents) that is suitable to supersede RFC
>   2616 (HTTP/1.1) and move RFC 2817 to Historic status
> * A document cataloguing the security properties of HTTP/1.1
> * A document that specifies HTTP/2.0 an improved binding of HTTP's
>   semantics to the underlying transport.
>
> ### HTTP/1.1
>
> HTTP is one of the most successful and widely-used protocols on the
> Internet today. However, its specification has several editorial issues.
> Additionally, after years of implementation and extension, several
> ambiguities have become evident, impairing interoperability and the
> ability to easily implement and use HTTP.
>
> The working group will refine RFC2616 to:
> * Incorporate errata and updates (e.g., references, IANA registries,
>   ABNF)
> * Fix editorial problems which have led to misunderstandings of the
>   specification
> * Clarify conformance requirements
> * Remove known ambiguities where they affect interoperability
> * Clarify existing methods of extensibility
> * Remove or deprecate those features that are not widely implemented
>   and also unduly affect interoperability
> * Where necessary, add implementation advice
> * Document the security properties of HTTP and its associated
>   mechanisms (e.g., Basic and Digest authentication, cookies, TLS) for
>   common applications
>
> It will also incorporate the generic authentication framework from RFC
> 2617, without obsoleting or updating that specification's definition of
> the Basic and Digest schemes.
>
> Finally, it will incorporate relevant portions of RFC 2817 (in
> particular, the CONNECT method and advice on the use of Upgrade), so
> that that specification can be moved to Historic status.
>
> In doing so, it should consider:
> * Implementer experience
> * Demonstrated use of HTTP
> * Impact on existing implementations and deployments
>
> ### HTTP/2.0
>
> There is emerging implementation experience and interest in a protocol
> that retains the semantics of HTTP, without the legacy of HTTP/1.x
> message framing and syntax, which have been identified as hampering
> performance and encouraging misuse of the underlying transport.
>
> As such, there is an opportunity to create a new major
> (non-wire-compatible) version of HTTP.
>
> To do this, the Working Group will solicit candidates for this work from
> the community, to be submitted as Internet-Drafts. Expected focus areas
> for candidates include:
>
> * Significantly improved perceived performance in common use cases
>   (e.g., browsers, mobile)
> * More efficient use of network resources; in particular, reducing the
>   need to use multiple TCP connections
> * Ability to be deployed on today's Internet, using IPv4 and IPv6, in
>   the presence of NATs
> * Maintaining HTTP's ease of deployment
> * Reflecting modern security requirements and practices
>
> Although proposals are not required to meet all of these goals, it is
> expected that the resulting work (if undertaken) will be chartered to
> meet them (and therefore, selecting one that meets the majority of them
> as a starting point is in everyone's interest).
>
> The Working Group will then select a starting point for the new work
> based upon the following criteria:
>
> * Compatibility with HTTP/1.1 semantics; i.e., it must be possible to
>   pass through a HTTP/1.1 message with reasonable fidelity
> * Broad implementer interest (e.g., from Web browsers, "back-end"
>   or "web api" uses of HTTP, servers, intermediaries, CDNs, etc.)
>
> Changes to the existing semantics of HTTP are out of scope in order to
> preserve the meaning of messages that might cross a 1.1 -->  2.0 -->  1.1
> request chain. However, the resulting effort may define new semantics to
> further the goals above, along with suitable extensibility mechanisms
> for defining additional semantics.
>
> If the Working Group forms consensus around a proposal to use as a
> starting point, it is expected it will re-charter to begin work on that
> document (or set of documents). The resulting work will be known as
> "HTTP/2.0", unless the Working Group determines that this isn't suitable
> (e.g., for interoperability).
>
> Although work on this new version will begin in parallel with completion
> of work on HTTP/1.1, the Working Group will prioritize HTTP/1.1 work
> until it is complete.
>
> Goals and Milestones
> ---------------------
>
>    Done        First HTTP/1.1 Revision Internet Draft
>
>    Done        First HTTP Security Properties Internet Draft
>
>    Feb 2012    Working Group Last Call for HTTP/1.1 Revision
>
>    Feb 2012    Working Group Last Call for HTTP Security Properties
>
>    Feb 2012    Call for Proposals for HTTP/2.0
>
>    Apr 2012    Submit HTTP/1.1 Revision to IESG for consideration as a
>                Proposed Standard
>
>    Apr 2012    Submit HTTP Security Properties to IESG for
>                consideration as Informational RFC
>
>    June 2012   Re-charter to work on HTTP/2.0
>
> ###
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>

From julian.reschke@gmx.de  Tue Feb 21 10:33:18 2012
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 B4D2D21F8900 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 10:33:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.41
X-Spam-Level: 
X-Spam-Status: No, score=-104.41 tagged_above=-999 required=5 tests=[AWL=-1.811, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xSC8FGKLG-qt for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 10:33:18 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 1C62921F88FF for <ietf@ietf.org>; Tue, 21 Feb 2012 10:33:17 -0800 (PST)
Received: (qmail invoked by alias); 21 Feb 2012 18:33:09 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp038) with SMTP; 21 Feb 2012 19:33:09 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19TpeVESBpTFcNMG95D7qy1ZbQ5tFegp4OlHOAxlf TwAdjteVSoUf/O
Message-ID: <4F43E364.4040706@gmx.de>
Date: Tue, 21 Feb 2012 19:33:08 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie>
In-Reply-To: <4F43E1D3.4070201@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: mnot@mnot.net, iesg@ietf.org, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:33:18 -0000

On 2012-02-21 19:26, Stephen Farrell wrote:
>
> Down below, for the proposed HTTP/2.0 work it says:
>
>  > * Reflecting modern security requirements and practices
>
> In some earlier discussion I asked what "modern" means
> there. It seems to mean at least working well with TLS,
> but I'm not sure what else is meant, if anything.
>
> In particular, I think it'd be good to try get better
> (more usable, more secure etc.) HTTP authentication
> defined as a built-in part of HTTP/2.0.
>
> My initial take is that if we're not going to do this
> for a major revision of the protocol, then when are we
> going to do it? So I'd like to see that included.
>
> The counter argument offered was that better HTTP
> authentication is complex and probably hard to get right
> and so would be better handled separately.

I believe this should be orthogonal to HTTP/2.0. Is there a specific 
thing that makes it impossible to use the existing authentication framework?

> ...

Best regards, Julian

From stephen.farrell@cs.tcd.ie  Tue Feb 21 10:37:18 2012
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 7A12D21E800E; Tue, 21 Feb 2012 10:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CbEYGDi9zL7L; Tue, 21 Feb 2012 10:37:13 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id A552F21E8010; Tue, 21 Feb 2012 10:37:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 09557171CFD; Tue, 21 Feb 2012 18:37:12 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1329849431; bh=AlCMV/MNyen9pi 4m8merGz6snae4PHBqyG1wj7h2H2Q=; b=iVoH8FDvdHoGxxa253z0XCWbz1Blv/ 580Cl5SAYXhp6NHWL6vvvCnMLCBdNFs9eUgialYy7wScwfrBZduQpOM+9x1fWXKU iTAYJw3nNrnx7SRb8gnmLTwkmIUJKHjxOVcxaQYrfLKpYvSUsASXWdPg9BlAxW4O 4qlC+tnLH5AAd2NuI9dhpoeOIG1i7WZQpVsvDkXRvuelselmx6dGgUnEGaJt+mNQ u0i0NMNJ/kBkUXcdHrDNeJkoElJw1dxp+pSFhRhRGh5uZxRrwE85wdq+lvDjcBIC Oyrrh3bvhtjrQgD29DeWGU3qmcr46k5vognt7C4YpNKM5Ua/f8fCUMyw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id W0Paum+Ao8Lb; Tue, 21 Feb 2012 18:37:11 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 5D496171C28; Tue, 21 Feb 2012 18:37:11 +0000 (GMT)
Message-ID: <4F43E458.6030705@cs.tcd.ie>
Date: Tue, 21 Feb 2012 18:37:12 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de>
In-Reply-To: <4F43E364.4040706@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:37:18 -0000

On 02/21/2012 06:33 PM, Julian Reschke wrote:
> On 2012-02-21 19:26, Stephen Farrell wrote:
>>
>> Down below, for the proposed HTTP/2.0 work it says:
>>
>> > * Reflecting modern security requirements and practices
>>
>> In some earlier discussion I asked what "modern" means
>> there. It seems to mean at least working well with TLS,
>> but I'm not sure what else is meant, if anything.
>>
>> In particular, I think it'd be good to try get better
>> (more usable, more secure etc.) HTTP authentication
>> defined as a built-in part of HTTP/2.0.
>>
>> My initial take is that if we're not going to do this
>> for a major revision of the protocol, then when are we
>> going to do it? So I'd like to see that included.
>>
>> The counter argument offered was that better HTTP
>> authentication is complex and probably hard to get right
>> and so would be better handled separately.
>
> I believe this should be orthogonal to HTTP/2.0. Is there a specific
> thing that makes it impossible to use the existing authentication
> framework?

Who knows? We don't have a protocol on the table yet. I
would imagine that some level of backwards compatibility
would be a requirement of course, or at least an issue to
be considered.

But the existing HTTP client authentication is also not
necessarily very useful, and there have been a number of
efforts to improve on that, none of which seem to have
gotten sufficient traction to get widely deployed/used.
Maybe HTTP/2.0 is a good time to try fix that.

S.


>
>> ...
>
> Best regards, Julian

From julian.reschke@gmx.de  Tue Feb 21 10:50:15 2012
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 55CCC21F8866 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 10:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.414
X-Spam-Level: 
X-Spam-Status: No, score=-104.414 tagged_above=-999 required=5 tests=[AWL=-1.815, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lyJA5xpq7Ge for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 10:50:14 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 1353621F8852 for <ietf@ietf.org>; Tue, 21 Feb 2012 10:50:13 -0800 (PST)
Received: (qmail invoked by alias); 21 Feb 2012 18:50:05 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp024) with SMTP; 21 Feb 2012 19:50:05 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19Y9Gp1oAhYCOL8Uu8O98gC3ANDH2AZ5z47Dnaesr N6gw5Ql75vUSz2
Message-ID: <4F43E75C.2010309@gmx.de>
Date: Tue, 21 Feb 2012 19:50:04 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie>
In-Reply-To: <4F43E458.6030705@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: mnot@mnot.net, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:50:15 -0000

On 2012-02-21 19:37, Stephen Farrell wrote:
> ...
>> I believe this should be orthogonal to HTTP/2.0. Is there a specific
>> thing that makes it impossible to use the existing authentication
>> framework?
>
> Who knows? We don't have a protocol on the table yet. I
> would imagine that some level of backwards compatibility
> would be a requirement of course, or at least an issue to
> be considered.
>
> But the existing HTTP client authentication is also not
> necessarily very useful, and there have been a number of
> efforts to improve on that, none of which seem to have
> gotten sufficient traction to get widely deployed/used.
> Maybe HTTP/2.0 is a good time to try fix that.

Well, we have an existing authentication framework. It would be 
interesting to find out what's missing from it.

Best regards, Julian

From kkinnear@cisco.com  Fri Feb 17 12:09:18 2012
Return-Path: <kkinnear@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 CC93821F8532; Fri, 17 Feb 2012 12:09:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id benCEYQovy4h; Fri, 17 Feb 2012 12:09:16 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3C721F852F; Fri, 17 Feb 2012 12:09:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=kkinnear@cisco.com; l=20951; q=dns/txt; s=iport; t=1329509356; x=1330718956; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=lWj6YbbdBYvb7Tqc/iutQdy5Sofl7uewZ4IUbiDcOPw=; b=GcaR+tofADHIvndICPEwuLRlBmEnIO41pzs76GnWaeQE5oTIGdsNGL1R Gz7+RaPeAJNnVtKKmFZ7zYBiWjVcijPAbtScvxb5SW8A4pizfmrnJXi5V L/ou8esmOiWzgnCkmJ1FyUFLw38yweW28VoNcaqNz8zBY+ZvTEcwBBb1A M=;
X-IronPort-AV: E=Sophos;i="4.73,439,1325462400"; d="scan'208";a="59866612"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 17 Feb 2012 20:09:15 +0000
Received: from bxb-vpn3-383.cisco.com (bxb-vpn3-383.cisco.com [10.86.249.127]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1HK9EjC024859; Fri, 17 Feb 2012 20:09:14 GMT
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <4F3987F0.5050000@isi.edu>
Date: Fri, 17 Feb 2012 15:09:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com>
References: <4F3987F0.5050000@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 21 Feb 2012 11:19:52 -0800
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:09:19 -0000

Joe,

Thank you for your review.

My responses are indented, below...

On Feb 13, 2012, at 5:00 PM, Joe Touch wrote:

> Hi, all,
>=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. The authors should consider this =
review together with any other last-call comments they receive. Please =
always CC tsv-dir@ietf.org if you reply to or forward this review.
>=20
> This request was received Feb. 2, 2012.
>=20
> This document describes an extension to DHCPv4 for the bulk query and =
transfer of current lease status over TCP.
>=20
> The following transport issues were noted, and are significant:
>=20
> UPDATES- The document updates DHCP with support for TCP, and as such =
this document seems like it should UPDATE RFC2131

	While this document clearly builds on RFC 2131, it
	doesn't actually change anything that anyone is doing
	that is currently based on RFC 2131.  My understanding of
	"updates" is that, in order to understand the first RFC
	(in this case, RFC 2131), you need to read all of the
	RFC's that "update" it.  That isn't the case here -- you
	can be very happy reading and implementing DHCPv4 by
	reading RFC 2131 and never have to know that DHCPv4 Bulk
	Leasequery exists.  In general, in the DHC WG, we seem to
	set a pretty high bar for what "udpates" another RFC.  I
	don't see that this document has met those requirements.
	But this isn't really my call.  I'll let Ralph Droms and
	the DHC WG chairs decide on this one, and I'll do
	whatever they tell me to do.
>=20

>=20
> PORT USE- Although DHCPv4 has an assigned TCP port, this document =
should clearly indicate that there is no other specified use of that =
port other than the bulk lease query described in this document

	Sure.
>=20
> It should further explain why no other existing DHCP exchanges are not =
valid on the TCP port.

	I've been taken to task by various IETF folks at
	varying levels of seniority for explaining too *much* of
	the "why".  My understanding is that this is a protocol
	specification and not a design document, and as such it
	is not only not necessary but frequently
	counter-productive to give lots of justifications for the
	decisions made when constructing the protocol.

	In this case, I can't speak for the wG at large, because
	we never proposed anything else.  The reason we didn't
	propose anything else was that we didn't want to "update"
	RFC 2131 with a new way to do DHCPv4 in general.  But
	that all kind of comes down to "because we said so".  We
	were trying to keep this draft focused.  But if I put
	words in the document which say that, someone in the WG
	would tell me to take them out.

	I have no problem motivating the "interesting" decisions
	we've made, or perhaps the contentious ones, but this one
	was a no-brainer that never even came up (to the best of
	my memory).

	Having said all of that, I'll put something in that says
	that we were trying to keep it simple.
>=20

>=20
> CONNECTION MANAGEMENT- The document describes the use of TCP =
connections for bulk transfer, but needs to be more specific about which =
side (relay client or server) closes the connection, under what =
circumstances, and with what mechanism (e.g., graceful CLOSE vs. ABORT, =
as per RFC 793)

	Here is what we have now, 7.8 is for clients, 8.5 is for
	servers:

> 7.8.  Closing Connections  [Client Section]
>=20
>    The requestor SHOULD close the connection after the
>    DHCPLEASEQUERYDONE message is received for the last outstanding =
query
>    that it has sent, if it has no more queries to send.
>=20
> 8.5.  Closing Connections   [Server Section]
>=20
>    The DHCPv4 server SHOULD start a timer for BULK_LQ_DATA_TIMEOUT
>    seconds for a particular connection after it sends a
>    DHCPLEASEQUERYDONE message over that connection and if there is no
>    current query outstanding for that connection.  It should clear =
this
>    timer if a query arrives over that connection.  If the timer =
expires,
>    the DHCPv4 server should close the connection.
>=20
>    The server MUST close its end of the TCP connection if it =
encounters
>    an error sending data on the connection.  The server MUST close its
>    end of the TCP connection if it finds that it has to abort an in-
>    process request.  A server aborting an in-process request SHOULD
>    attempt to signal that to its requestors by using the =
QueryTerminated
>    status code in the status-code option in a DHCPLEASEQUERYDONE
>    message, including a message string indicating details of the =
reason
>    for the abort.   If the server detects that the requesting end of =
the
>    connection has been closed, the server MUST close its end of the
>    connection.

	All connections are closed with a graceful CLOSE, and not
	with an ABORT.  I'll add that to the document.

	I'm at a loss to know how to be more specific about which
	side of the connection closes the connection.  There are
	rules for the client in 7.8, and rules for the server in
	8.5.


> sec 7.3 indicates some conditions for terminating connections; this =
section should indicate which side performs this, and by what method =
(CLOSE, ABORT)

	Section 7.3 discusses in two places where the "requestor" may
	drop the connection.  The term "requestor" is used to
	indicate which "side" performs the actions.  All of
	Section 7 is about "Requestor Behavior", and the specific
	details of section 7.3 in all cases indicate that the
	instructions for dealing with the connection concern the
	"requestor" explicitly.

	I'll enhance the explanation to include that CLOSE should
	be used.

	If there is a specific set of instructions that are
	unclear, I don't see them, so it would help me if you
	could give me more detailed guidance than "Section 7.3". =20
	Thanks.

>=20
> this sec also allows connections to stay open after all pending =
transactions are complete (MAY); the rationale for this should be given, =
or the connection MUST be closed.

	I will add some words which clarify the reasons why you
	might want to leave the connection open after all pending
	transactions are complete.
>=20
> the same issue applies to sec 7.8 and 8 throughout; sec 8.5 is =
particularly problematic on this issue because it discusses aborting a =
request using in-band data, which may not be available if the connection =
is closed using ABORT. the state of other pending connection shsould be =
discussed too.

	The in-band data is not required for proper protocol
	operation, it is valuable because it can limit the amount
	of data required when and if the connection is
	reestablished.  All connections are closed by CLOSE.  I
	assume that, in your comment, "other pending
	connection[s]" means other data flows that might exist on
	the TCP connection that is coming down.  I will add some
	words that say that those Bulk Leasequery data flows will
	also be stopped.
>=20
> TIMEOUTS- Sec 6.3 defines a timeout for the TCP connection; is this =
intended to supercede any TCP timeout? or is it intended to be the min =
of the TCP timeout and the specified one?

	The BULK_LQ_DATA_TIMEOUT is completely application
	specific and essentially independent of the underlying
	connection timeout.  I will add words to that effect
	in the document.
>=20
> This section should more carefully explain behavior when a connection =
is dropped and the reason - e.g., timeout, abort, close.
=09
	The application employing Bulk Leasequery doesn't
	care about *why* the connection went away.  It
	doesn't have to know if it was abort, close, or
	timeout.  I will say that in this section.
>=20
> INTERLEAVING- sec 7.7 says that the server MUST interleave replies; =
there doesn't seem a valid reason for this requirement. clearly the =
receiver MUST tolerate interleaved replies. having the server interleave =
replies is relevant only if each request/reply has its own timeout -- =
which should be overridden if there is another response in progress =
anyway. This issue should be more clearly explained and motivated.

	Robert Sparks offered clarification, which I like
	a lot and have already agreed to use:
>=20
> 	Is the requirement you are really trying to capture "MUST
> 	NOT block sending replies on new queries until all
> 	replies for the existing query are complete."?
>=20


> There were some other issues noted in this document. These comments =
appear below, and although not focused on transport issues, they =
represent significant issues that IMO should be addressed as well.
>=20
> NOTE - regarding some terminology issues, I did not survey current =
DHCP RFCs for consistency, but IMO these terms should be corrected even =
if they are then inconsistent with existing specs.
>=20
> Joe
>=20
> -----------
>=20
> Major non-transport issues:
>=20
> - In many places the doc allows inaction to substitute for either =
positive or negative confirmation. IMO, this invites implementation =
errors, and should be avoided. E.g., status return codes, data source =
option missing, query-for-all-configured-IPs, etc.
=09

	While I personally tend to agree with you on this one, I
	have clear direction from the DHC WG that this is *not*
	the approach that the WG wants to take.  Here is the
	status code text:

>    A status-code option MAY appear in the options field of a DHCPv4
>    message.  If the status-code option does not appear, it is assumed
>    that the operation was successful.  The status-code option SHOULD =
NOT
>    appear in a message which is successful unless there is some text
>    string that needs to be communicated to the requestor.

	This was wrangled over at some length in the DHC WG,
	and this was the way that it needed to be to pass
	last call.  I don't feel that I can change it
	at this time.
=09
>=20
> - the data source option reserved codes need more detailed =
specification. if these are intended for future use, then they MUST be =
ignored by the receiver (at least). if they are to mean anything at all, =
at least one bit (typically all of them) MUST be set to zero by the =
transmitter for implementations that do not support any of the component =
fields.
>=20
> further, the length of this option MUST be 1

	Yes, subsequent to the creation of this section,
	Amanda Baber of IANA enlightened me regarding
	the different between RESERVED and UNASSIGNED.
	These should be UNASSIGNED, and I will add words
	that say that a receiver should ignore the
	bits that are unassigned.
>=20
> - The protocol supports bulk transfer that is not data driven. This =
could represent a security vulnerability by exposing information that =
may not be on the data path (and thus already accessible) to a relay =
agent. This should be discussed in the security considerations section.

	All data that is exposed has already been
	exposed using UDP to regular DHCP port.   But please see
	my response to Stephen Farrell (which is too long to include
	here) to see if it covers the issues about which you
	have concerns.
>=20
> - Integer quantities should be referred to as "unsigned 32-bit =
integers" throughout.

	Good point (though some are 16 bits).  The signed-ness is not
	specified and should be.  I'll make sure that it is.
>=20
> - "VPN" is used throughout to refer to "private" addresses (RFC 1918); =
a VPN is not just private addressing.

	Hmm.  Actually, VPN in this document does not refer to RFC 1918
	private addressing.  If this is important to you, could you
	be more specific as to your concern?
>=20
> - (this is a nit with all IDs, FWIW) SHOULD and SHOULD NOT are used =
throughout without context. Any time SHOULD is used instead of MUST (or =
SHOULD NOT rather than MUST NOT), it is useful to explain a viable =
exception. If no such exception exists, the rationale for selecting =
SHOULD over MUST should be included.

	This is an interesting approach, which is new to me.  I
	can see the value in looking for viable exceptions.  I
	think justifying SHOULD and not MUST is a bit much, and
	wouldn't make it through the "keep it short and simple"
	filters that the DHC WG seems to place on DHC drafts.
	But as I said, I'll look at every SHOULD (NOT) and see if
	I can find concise examples of reasons.  But I'm
	concerned that this will greatly lengthen the draft.
>=20
> - It would be useful to explain why STATUS-CODE strings MUST NOT be =
null-terminated; is that a protocol violation, or are you just saying =
that NULLs are valid in these strings? the description should be clear =
that the string field describes the string length without any =
termination characters.

	I will clarify this.  Nulls are not allowed in the strings.
	DHCP options have an unfortunate history where some
	large vendors null terminated their strings even though
	they were not supposed to, so now we always make a big
	deal out of it so it doesn't happen again.
>=20
> - start-time-of-state is expressed as an offset from base-time; this =
appears to be the only time indicated as an offset rather than as an =
absolute. That inconsistency invites implementation errors; IMO, this =
should be absolute too.

	There are two kinds of time options here, input options
	and output options.  The input options are all absolute
	times.  The output options are all offset times from the
	base time (which by design is the only absolute time in
	the output packets).  There are several input options
	defined in this document.  The start-time-of-state is the
	only output option defined in this draft.  It is defined
	as a offset to the base time in large part because the
	*other* output options that are used in the DHCP packet
	are *also* offsets to the base time.  These options are
	not new, but are options that already exist in other
	RFC's.  So, while it looks like the state-time-of-state
	is the odd man out at first glance, it actually is an
	offset time because the *other* options with which it
	will appear are also offset times.
>=20

>=20
> - option lengths: throughout, the doc refers to option lengths as =
being "an octet"; they are *indicated* in one octet. Some are constant =
(e.g., DCHP-STATE), some allow the contents of the octet to vary. Again, =
this is an *unsigned integer* octet.

	Yes, the size of an option is stored in
	one octet.  So, yes, the length is *indicated*
	by the value in that one octet.

	But the length may be 1 octet, it may be
	5 octets, it may vary between 8 and 10 octets.

	I don't understand your concern.  Are you=09
	saying that the length should not be
	stated to be "1 octet" or "5 octets"?

	I will fix the integer to be specifically
	unsigned (as previously indicated).=20
>=20
> - some of the information provided (in DHCP-STATE) goes beyond that of =
DHCP. It would be useful to motivate the need for this information in a =
bulk query, and why it is not similarly available for nodes using UDP =
(e.g., as an extension to DHCPv4, not just to the bulk transfer =
command). again, absence of state information should not indicate state. =
State should always be expressed explicitly. these states are further =
meaningless without a state diagram explaining them. if such a diagram =
is not possible (as noted at end of sec 6.2.7), then the states are =
irrelevant and the option should not be included.

	The state transition diagram can certainly be drawn, but
	as it is fully connected, such a picture conveys no
	useful information.  The transitions are not themselves
	useful in any case, as the the Bulk Leasequery is a
	snapshot of information at one instant of time.  There is
	every reason to assume that as the state moves from one
	value to another that an external entity would not see
	all (or even many) of these transitions.  This is a
	snapshot of the DHCP state, and could be nothing else in
	the environment of Bulk Leasequery.

	The reason why the state transition graph is fully
	connected is due to the common practice in DHCPv4 of
	having two servers running in a failover relationship.
	There are then two state machines for the lease state,
	and at times one "leads" and the other "follows", and at
	other times the other "leads" and its partner "follows".
	So, examined individually, the state machines for each
	individual failover partner is fully connected because at
	any time it may receive an update from its partner that
	it decides to accept that will simply "set" the state to
	the value supplied by the partner.

	All of this is orthogonal to the Bulk Leasequery protocol
	-- except that we want the user of the Bulk Leasequery
	protocol to be able to make sense out of information
	supplied by each of the failover partners.  Or any
	partners running any increased availability solution.

	So, that is the reason why the dhcp-state option exists
	at all -- to allow the user of Bulk Leasequery to make
	sense out of the results of sending a Bulk Leasequery to
	two different (but cooperating) DHCPv4 servers.

	The DHC WG felt that this information was worthwhile to
	have in this document, and I agree (or we wouldn't have
	put it in).

>=20
> - in sec 6.2.9 the term "not allowed" should be explained - are they =
reserved for future use and thus ignored? or are they "not allowed" - in =
which case the doc should indicate handling if they appear.

	Ah, good catch.  The "not allowed" will become UNASSIGNED,
	based on my conversation with Amanda Baber of IANA.
	I will add words that suggest that they should be
	ignored.

	The point of this table is, actually, not how to
	handle them (that is the up to the vpn-option draft/RFC),
	but rather to define a single new value.
>=20
> - sec 7.4 states that the clock skew of zero is desired; this assumes =
E2E delays under 1sec. An explanation of why this is desired should be =
given, as well as the consequences of it not.

	I have given specific instructions on how to handle non-zero
	clock skews.  There are no "consequences".  You code it
	so that it works with non-zero clock skew.  Period.

	It is desired because it is less confusing to humans.

>=20
> Other non-transport issues:
>=20
> - The document includes definitions and references to irrelevant =
deployment and implementation issues, notably DSLAMs, concentrators, and =
access concentrators. These should not appear formally; they should be =
used only to usefully illustrate currently intended uses.

	These appear in the text in order to give=20
	the otherwise abstract design goals some concrete
	examples.   We already removed a lot of the design
	goals, are you suggesting that they all be removed?

>=20
> - The doc refers to "real-time", which could imply requirements not =
supported. This should be replaced with "rapid".

	I'll fix this.
>=20
> - "absolute time" *indicates* (rather than contains) the number of =
seconds...

	I'll fix this.
>=20
> - "third party agent" should be explained, i.e., neither DHCP client =
nor DHCP server.

	I will fix this.
>=20
> - "downstream" and "upstream" should be defined as both away from the =
server *and towards the client* ("away from the server" has two =
directions).

	Sure, I'll add these words.
>=20
> - sec 3 should refer to relays, and returning the entire set or =
individual bindings; there is no reason to explain the goals in terms of =
access concentrators.

	I don't know about this.  I could certainly change it,
	but is this really important to you?  There was quite a
	bit of negotiation in the WG about these examples.  I
	don't want to restart that discussion and have it all
	over again.  Does this really matter that much to you?
>=20

>=20
> - sec 3.2 appears to provide contradictory advice - caching is =
required, but should be avoided? it would be useful to resolve this =
inconsistency.

	Use of Bulk Leasequery is designed to help you avoid
	caching.
>=20
> - sec 3.3 refers to 'fast path', but this term doesn't make sense in =
this context because fast-path is a forwarding issue. it would be useful =
to explain what you mean, and pick a different term

	Yes, it is a forwarding issue, and many devices
	will not forward unless they know that they are forwarding
	to a device that has received a valid DHCPv4 address.
	The point (well, one point) of Bulk Leasequery is to
	allow these forwarders to gather data so that they
	can make the correct decision in the fast path.

------------

	Regards -- Kim



From kkinnear@cisco.com  Fri Feb 17 12:22:00 2012
Return-Path: <kkinnear@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 894D921F86DF; Fri, 17 Feb 2012 12:22:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TiIwTZNyL6uq; Fri, 17 Feb 2012 12:21:59 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0F921F86DC; Fri, 17 Feb 2012 12:21:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=kkinnear@cisco.com; l=9842; q=dns/txt; s=iport; t=1329510118; x=1330719718; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=gf0mH1lLrcWJvWuvKT9col+C5uZVvCxsYC75xxU/cVw=; b=JAH9NpeBxszqiiI1lpKXWDuBz+USFiWQ3R24CaLTYsE1mOPOnJ/4S5DT RyT6HM0Ymg69uhMN3GDoTrU8vLqNEyQXd2+5ykA+IYXgW1E5srjY0GGVY VhW5XN6Fhxm/DNfCZi8ywS/R2yoMMNoeqPfvrt5nzK3lwk8sTX67cVZtN g=;
X-IronPort-AV: E=Sophos;i="4.73,439,1325462400"; d="scan'208";a="29371038"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 17 Feb 2012 20:21:58 +0000
Received: from bxb-vpn3-383.cisco.com (bxb-vpn3-383.cisco.com [10.86.249.127]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1HKLvlx015547; Fri, 17 Feb 2012 20:21:57 GMT
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <4F398BA4.3010400@isi.edu>
Date: Fri, 17 Feb 2012 15:22:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5250394-BEAE-4733-910C-115BD7801CC7@cisco.com>
References: <4F3987F0.5050000@isi.edu> <4F398BA4.3010400@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Tue, 21 Feb 2012 11:20:15 -0800
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:22:00 -0000

On Feb 13, 2012, at 5:16 PM, Joe Touch wrote:

> Hi, all,
>=20
> One additional transport suggestion:
>=20
> - it would be useful to include recommended configurations for TCP =
connections. Given these are multi-byte request/response exchanges, =
Nagle should be disabled, e.g.

	One of the co-authors had this to
	say:
>=20
>   A bone headed implementation (either client or server) might send
>   bits and pieces of a message (for example, it would be easy for
>   an implementation to send the 2 bytes for the length of the
>   message in one request and then the message in a second). This is
>   exactly what you want the TCP protections for. So, I think we
>   should be silent on this issue.  I also can't see how there is
>   any harm in leaving it enabled (even in a 'clean'
>   implementation).
>=20

	I tend to agree with him -- I don't see that this =09
	is going to cause a problem if we don't disable
	it.  But maybe I'm missing something.  Is there
	an important problem if we don't specify this one
	way or another?

	Thanks -- Kim


>=20
> Joe
>=20
> On 2/13/2012 2:00 PM, Joe Touch wrote:
>> Hi, all,
>>=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. The authors should consider this review together =
with
>> any other last-call comments they receive. Please always CC
>> tsv-dir@ietf.org if you reply to or forward this review.
>>=20
>> This request was received Feb. 2, 2012.
>>=20
>> This document describes an extension to DHCPv4 for the bulk query and
>> transfer of current lease status over TCP.
>>=20
>> The following transport issues were noted, and are significant:
>>=20
>> UPDATES- The document updates DHCP with support for TCP, and as such
>> this document seems like it should UPDATE RFC2131
>>=20
>> PORT USE- Although DHCPv4 has an assigned TCP port, this document =
should
>> clearly indicate that there is no other specified use of that port =
other
>> than the bulk lease query described in this document
>>=20
>> It should further explain why no other existing DHCP exchanges are =
not
>> valid on the TCP port.
>>=20
>> CONNECTION MANAGEMENT- The document describes the use of TCP =
connections
>> for bulk transfer, but needs to be more specific about which side =
(relay
>> client or server) closes the connection, under what circumstances, =
and
>> with what mechanism (e.g., graceful CLOSE vs. ABORT, as per RFC 793)
>>=20
>> sec 7.3 indicates some conditions for terminating connections; this
>> section should indicate which side performs this, and by what method
>> (CLOSE, ABORT)
>>=20
>> this sec also allows connections to stay open after all pending
>> transactions are complete (MAY); the rationale for this should be =
given,
>> or the connection MUST be closed.
>>=20
>> the same issue applies to sec 7.8 and 8 throughout; sec 8.5 is
>> particularly problematic on this issue because it discusses aborting =
a
>> request using in-band data, which may not be available if the =
connection
>> is closed using ABORT. the state of other pending connection shsould =
be
>> discussed too.
>>=20
>> TIMEOUTS- Sec 6.3 defines a timeout for the TCP connection; is this
>> intended to supercede any TCP timeout? or is it intended to be the =
min
>> of the TCP timeout and the specified one?
>>=20
>> This section should more carefully explain behavior when a connection =
is
>> dropped and the reason - e.g., timeout, abort, close.
>>=20
>> INTERLEAVING- sec 7.7 says that the server MUST interleave replies;
>> there doesn't seem a valid reason for this requirement. clearly the
>> receiver MUST tolerate interleaved replies. having the server =
interleave
>> replies is relevant only if each request/reply has its own timeout --
>> which should be overridden if there is another response in progress
>> anyway. This issue should be more clearly explained and motivated.
>>=20
>> There were some other issues noted in this document. These comments
>> appear below, and although not focused on transport issues, they
>> represent significant issues that IMO should be addressed as well.
>>=20
>> NOTE - regarding some terminology issues, I did not survey current =
DHCP
>> RFCs for consistency, but IMO these terms should be corrected even if
>> they are then inconsistent with existing specs.
>>=20
>> Joe
>>=20
>> -----------
>>=20
>> Major non-transport issues:
>>=20
>> - In many places the doc allows inaction to substitute for either
>> positive or negative confirmation. IMO, this invites implementation
>> errors, and should be avoided. E.g., status return codes, data source
>> option missing, query-for-all-configured-IPs, etc.
>>=20
>> - the data source option reserved codes need more detailed
>> specification. if these are intended for future use, then they MUST =
be
>> ignored by the receiver (at least). if they are to mean anything at =
all,
>> at least one bit (typically all of them) MUST be set to zero by the
>> transmitter for implementations that do not support any of the =
component
>> fields.
>>=20
>> further, the length of this option MUST be 1
>>=20
>> - The protocol supports bulk transfer that is not data driven. This
>> could represent a security vulnerability by exposing information that
>> may not be on the data path (and thus already accessible) to a relay
>> agent. This should be discussed in the security considerations =
section.
>>=20
>> - Integer quantities should be referred to as "unsigned 32-bit =
integers"
>> throughout.
>>=20
>> - "VPN" is used throughout to refer to "private" addresses (RFC =
1918); a
>> VPN is not just private addressing.
>>=20
>> - (this is a nit with all IDs, FWIW) SHOULD and SHOULD NOT are used
>> throughout without context. Any time SHOULD is used instead of MUST =
(or
>> SHOULD NOT rather than MUST NOT), it is useful to explain a viable
>> exception. If no such exception exists, the rationale for selecting
>> SHOULD over MUST should be included.
>>=20
>> - It would be useful to explain why STATUS-CODE strings MUST NOT be
>> null-terminated; is that a protocol violation, or are you just saying
>> that NULLs are valid in these strings? the description should be =
clear
>> that the string field describes the string length without any
>> termination characters.
>>=20
>> - start-time-of-state is expressed as an offset from base-time; this
>> appears to be the only time indicated as an offset rather than as an
>> absolute. That inconsistency invites implementation errors; IMO, this
>> should be absolute too.
>>=20
>> - option lengths: throughout, the doc refers to option lengths as =
being
>> "an octet"; they are *indicated* in one octet. Some are constant =
(e.g.,
>> DCHP-STATE), some allow the contents of the octet to vary. Again, =
this
>> is an *unsigned integer* octet.
>>=20
>> - some of the information provided (in DHCP-STATE) goes beyond that =
of
>> DHCP. It would be useful to motivate the need for this information in =
a
>> bulk query, and why it is not similarly available for nodes using UDP
>> (e.g., as an extension to DHCPv4, not just to the bulk transfer
>> command). again, absence of state information should not indicate =
state.
>> State should always be expressed explicitly. these states are further
>> meaningless without a state diagram explaining them. if such a =
diagram
>> is not possible (as noted at end of sec 6.2.7), then the states are
>> irrelevant and the option should not be included.
>>=20
>> - in sec 6.2.9 the term "not allowed" should be explained - are they
>> reserved for future use and thus ignored? or are they "not allowed" - =
in
>> which case the doc should indicate handling if they appear.
>>=20
>> - sec 7.4 states that the clock skew of zero is desired; this assumes
>> E2E delays under 1sec. An explanation of why this is desired should =
be
>> given, as well as the consequences of it not.
>>=20
>> Other non-transport issues:
>>=20
>> - The document includes definitions and references to irrelevant
>> deployment and implementation issues, notably DSLAMs, concentrators, =
and
>> access concentrators. These should not appear formally; they should =
be
>> used only to usefully illustrate currently intended uses.
>>=20
>> - The doc refers to "real-time", which could imply requirements not
>> supported. This should be replaced with "rapid".
>>=20
>> - "absolute time" *indicates* (rather than contains) the number of
>> seconds...
>>=20
>> - "third party agent" should be explained, i.e., neither DHCP client =
nor
>> DHCP server.
>>=20
>> - "downstream" and "upstream" should be defined as both away from the
>> server *and towards the client* ("away from the server" has two
>> directions).
>>=20
>> - sec 3 should refer to relays, and returning the entire set or
>> individual bindings; there is no reason to explain the goals in terms =
of
>> access concentrators.
>>=20
>> - sec 3.2 appears to provide contradictory advice - caching is =
required,
>> but should be avoided? it would be useful to resolve this =
inconsistency.
>>=20
>> - sec 3.3 refers to 'fast path', but this term doesn't make sense in
>> this context because fast-path is a forwarding issue. it would be =
useful
>> to explain what you mean, and pick a different term
>>=20
>> ----
>>=20
>>=20
>>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Sat Feb 18 07:29:44 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1F121F8559; Sat, 18 Feb 2012 07:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.498
X-Spam-Level: 
X-Spam-Status: No, score=-106.498 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TEzSzkEXPqOq; Sat, 18 Feb 2012 07:29:43 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 586F121F84D3; Sat, 18 Feb 2012 07:29:43 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTz/D5pI3Txhl7KHoVHwiLE8YXOsghj0R@postini.com; Sat, 18 Feb 2012 07:29:43 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4E04A1B85E2; Sat, 18 Feb 2012 07:29:42 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 42A49190083; Sat, 18 Feb 2012 07:29:42 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sat, 18 Feb 2012 07:29:42 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Thread-Topic: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Thread-Index: AQHM6qpvAqOZiGrj4kydaKDtgkZBbZZCENSAgAAsLgCAARgHAA==
Date: Sat, 18 Feb 2012 15:29:41 +0000
Message-ID: <C84410EE-1D8C-494B-8BEA-030C6CBCABC1@nominum.com>
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu>
In-Reply-To: <4F3ED8FC.6020400@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_C84410EE1D8C494B8BEA030C6CBCABC1nominumcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 21 Feb 2012 11:20:56 -0800
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "<draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>" <draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:29:44 -0000

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

On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
Thanks. In this case, it's important to suggest why others should not add c=
onventional DHCP query support to the TCP port.

The idea of doing DHCP stateful autoconfiguration over TCP is nonsensical: =
DHCP clients start out with no IP address, so it is not possible for them t=
o do TCP.

The reason for sharing option codes is to avoid confusion: since existing D=
HCPLEASEQUERY option codes come out of the same namespace as DHCP options, =
if we were to propose that options in this documentation come out of a diff=
erent namespace, we would have to declare that new namespace, which would h=
ave some options and option codes in common with the existing namespace.   =
This doesn't add value.

Historically, we have never said that when an option code is added, that up=
dates RFC2131 (really, it would make more sense to say it updated RFC2132 i=
f we were to go there, since RFC2132 is the document that describes DHCP op=
tions).   So it would be surprising and unconventional if this document wer=
e said to update either RFC2131 or RFC2132 simply because it defined one or=
 more new option codes.


--_000_C84410EE1D8C494B8BEA030C6CBCABC1nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <A28D587E16F0F24C97B9075D02FB2EE1@nominum.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; ">
<div>
<div>On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Thanks.
 In this case, it's important to suggest why others should not add conventi=
onal DHCP query support to the TCP port.<br>
</span></blockquote>
</div>
<br>
<div>The idea of doing DHCP stateful autoconfiguration over TCP is nonsensi=
cal: DHCP clients start out with no IP address, so it is not possible for t=
hem to do TCP.</div>
<div><br>
</div>
<div>The reason for sharing option codes is to avoid confusion: since exist=
ing DHCPLEASEQUERY option codes come out of the same namespace as DHCP opti=
ons, if we were to propose that options in this documentation come out of a=
 different namespace, we would have
 to declare that new namespace, which would have some options and option co=
des in common with the existing namespace. &nbsp; This doesn't add value.</=
div>
<div><br>
</div>
<div>Historically, we have never said that when an option code is added, th=
at updates RFC2131 (really, it would make more sense to say it updated RFC2=
132 if we were to go there, since RFC2132 is the document that describes DH=
CP options). &nbsp; So it would be surprising
 and unconventional if this document were said to update either RFC2131 or =
RFC2132 simply because it defined one or more new option codes.</div>
<div><br>
</div>
</body>
</html>

--_000_C84410EE1D8C494B8BEA030C6CBCABC1nominumcom_--

From jgs@juniper.net  Mon Feb 20 12:07:39 2012
Return-Path: <jgs@juniper.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 60A9621F87E6; Mon, 20 Feb 2012 12:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.489
X-Spam-Level: 
X-Spam-Status: No, score=-6.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRKmGrXO5BLn; Mon, 20 Feb 2012 12:07:38 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id EF1D521F8793; Mon, 20 Feb 2012 12:07:37 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKT0KoA/xbFsMl8sgdthOFtWqrttItV0Dx@postini.com; Mon, 20 Feb 2012 12:07:38 PST
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Mon, 20 Feb 2012 12:07:00 -0800
From: John Scudder <jgs@juniper.net>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Mon, 20 Feb 2012 12:06:58 -0800
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: AczwCzRJw3iM7wjfRRmX7r5+mkCpdw==
Message-ID: <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net>
In-Reply-To: <4F3E4EDB.7070509@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 21 Feb 2012 11:21:09 -0800
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:07:39 -0000

Jari,

I appreciate that brevity is desirable. I think in this case, the compressi=
on process may have been unintentionally lossy. Let me say what in my view =
was lost:

1. In discussions within the LISP WG it's frequently stated that experiment=
ation will resolve some disputed question. Given this WG reliance on experi=
mentation to resolve architectural issues, it seems desirable that such exp=
erimentation be recognized as a first-class output of the group, on a par w=
ith the architecture itself (something you have identified as a high priori=
ty). As with any experiment, it's important to document the experiments tha=
t were performed, and their outcomes.
  I do see that this is captured at a high level here: "It is expected that=
 the results of specifying, implementing, and testing LISP will be fed to t=
he general efforts at the IETF and IRTF to understand which type of a solut=
ion is optimal." However, there are no milestones to correspond with this e=
xpectation. It generally seems sensible to have a milestone for each expect=
ation. Below I propose adding one.

2. LISP relies on caching, but it has been difficult to carry on architectu=
ral discussion and analysis of LISP because cache management is unspecified=
. In such WG discussions, it's common for it to be asserted that the proble=
m is solvable, but the solution is left 'as an exercise for the reader' or =
similar. To enable this impasse to be resolved, it was agreed that an examp=
le cache management specification would be produced. This would enable disc=
ussion about something concrete without resorting to argument by emphatic a=
ssertion.

3. ETR synchronization is an important component for correct functioning of=
 the overall LISP system but similar to caching, it has been difficult to h=
ave a concrete discussion about it. Similar to the above, this is why the p=
revious version of the charter had an milestone for documenting it.

Broadly, these points have in common that they remind us that the LISP WG h=
as a stated bias for working towards the concrete and the quantifiable. I t=
hink that is the high-order bit of what has been lost.

You ask for something to lift to put in the new charter. Here are some sugg=
ested edits:

Add:

DATE TBD: Publish an example cache management specification.

DATE TBD: Publish an example ETR synchronization specification.

Since you mention prioritizing the architecture document, one other alterna=
tive would be to explicitly call out the above two items as needing to be a=
ddressed in that document. This might make sense insofar as these are both =
needs that arose in the process of trying to work through the LISP architec=
ture (i.e. they identify incompletely documented or worked-out areas of the=
 architecture).

DATE TBD: Summarize results of specifying, implementing, and testing
LISP and forward to IESG and/or IRTF.

(The 'summarize' item does not seem to be what you're envisioning for the '=
impact' work item, but if that's incorrect I would be OK with making that w=
ork item more explicit by adding the above text or similar.)

Thanks,

--John

On Feb 17, 2012, at 7:58 AM, Jari Arkko wrote:

John,

The IESG had no specific objection to these parts, but we made the charter =
in general shorter and reformulated some of the results. In particular, the=
 idea was to put much of the material that you pointed to into the "LISP im=
pacts" document. In general, the IESG felt that we had to go back a bit, an=
d describe more of the big picture - the architecture, what problem we are =
addressing, what the results and downsides are - than the technical details=
. But it was not intended that topics like scalability and amount of state =
could be left out.

I do agree that the description of the impacts document is short at the mom=
ent, is there something that you'd like to lift to put in the new charter?

Jari

On 16.02.2012 19:00, John Scudder wrote:
Hi Thomas,

On Feb 15, 2012, at 4:31 PM, Thomas Narten wrote:

A WG Review message for this WG already went out a month ago.

What has changed to necessitate another Last Call?

Could the-powers-that-be please make it easier for those who might
care to understand if there is something here that we should know and
possibly comment about?

A simple explanation, or a pointer to diffs, etc. would do the job
nicely.
Good question! I did go back and diff the last couple of versions and thoug=
h this isn't the exhaustive diff, these are the key changes that caught my =
eye:

This text was lost from the previous draft charter:

This analysis will explain what
role LISP can play in scalable routing. The analysis should also look at
scalability and levels of state required for encapsulation,
decapsulation, liveness, and so on as well as the manageability and
operability of LISP. Specifically, the group will work on:

- documenting areas that need experimentation
- summarizing the results of implementation, experiments, and deployment
  experience
- describing the implications of employing LISP
- operational guidance for using LISP

And so were these Goals and Milestones:

Jun 2012    Forward to the IESG an operational document which should
           include cache management and ETR synchronization
           techniques (draft-ietf-lisp-deployment).

Dec 2013    Publish an example cache management specification.

Jun 2014    Summarize results of specifying, implementing, and testing
           LISP and forward to IESG and/or IRTF.

Jun 2014    Analyze and document the implications of LISP deployments in
           Internet topologies and forward to IESG for publication.

I'm not sure why these were removed, and I would like to see them reinstate=
d or at least have a discussion about their removal.

Thanks,

--John



From lorenzo@google.com  Mon Feb 20 23:54:54 2012
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 016C221E8026 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2012 23:54:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.61
X-Spam-Level: 
X-Spam-Status: No, score=-102.61 tagged_above=-999 required=5 tests=[AWL=0.366, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Av3D5GhcNM7v for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2012 23:54:53 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id EC0FE21F85E6 for <ietf@ietf.org>; Mon, 20 Feb 2012 23:54:52 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so9441178obb.31 for <ietf@ietf.org>; Mon, 20 Feb 2012 23:54:52 -0800 (PST)
Received-SPF: pass (google.com: domain of lorenzo@google.com designates 10.182.86.201 as permitted sender) client-ip=10.182.86.201; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of lorenzo@google.com designates 10.182.86.201 as permitted sender) smtp.mail=lorenzo@google.com; dkim=pass header.i=lorenzo@google.com
Received: from mr.google.com ([10.182.86.201]) by 10.182.86.201 with SMTP id r9mr11546671obz.8.1329810892361 (num_hops = 1); Mon, 20 Feb 2012 23:54:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=pl2aBo8/+kOfCbr1UrJnhJkPjNYk+qxWEsGdRGaKS/A=; b=b9EgbeeL/V05TyjsN5rgUavwOb8rCBYmQjt5NfYILukPcdJvt+D0seOoeRTm3NAqpb fyzI2u7cY8K2Aml23M91sXjZjDucuaSyJooNRHA1mrB7cmuM/RH9eO75VLX1/Gh1a3xK rxbaDu75Br86zS9NpWLfopIxMxEejtQ/cw9I4=
Received: by 10.182.86.201 with SMTP id r9mr9847665obz.8.1329810892310; Mon, 20 Feb 2012 23:54:52 -0800 (PST)
Received: by 10.182.86.201 with SMTP id r9mr9847659obz.8.1329810892215; Mon, 20 Feb 2012 23:54:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.5.67 with HTTP; Mon, 20 Feb 2012 23:54:32 -0800 (PST)
In-Reply-To: <CB61222C.50472%jason_livingood@cable.comcast.com>
References: <CB5F3DFE.4FFE3%jason_livingood@cable.comcast.com> <CB61222C.50472%jason_livingood@cable.comcast.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 21 Feb 2012 16:54:32 +0900
Message-ID: <CAKD1Yr2n91=8n3n=Nh=zXFy8Rpzj_8D0C=sQQ2B8N0PGEgEQnQ@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Content-Type: multipart/alternative; boundary=f46d0445183bd954b704b974b9de
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQkfjurSdHcXkeLJWh55c3setRY8AoTCTtB05MyAAENMu/IbON/RySXz4Z3CCpQltng6EhDh7KhKvIiT879NjguO8XB/E1qNtxlafNljpQFTfWhaZ4aUm73y53BSXFw+24QEUNbB
X-Mailman-Approved-At: Tue, 21 Feb 2012 11:21:38 -0800
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:54:54 -0000

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

On Thu, Feb 16, 2012 at 00:52, Livingood, Jason <
Jason_Livingood@cable.comcast.com> wrote:

>      To be more specific, at least section 5.5 ("it is unclear
> how implementers will judge when the network conditions will have
> changed sufficiently to justify turning off DNS Resolver Whitelisting
> and/or what the process and timing will be for discontinuing this
> practice") is now incorrect. It *is* clear, and it's what those
> implementers are doing as part of World IPv6 Launch.
>
>  Does that make more sense?
>
>
>  As the author, if it helps I plan to make the following change to
> Section 5.5 following the conclusion of IETF Last Call. I ran this by a few
> folks already and it seems broadly acceptable (have not heard from Lorenzo
> yet though).
>
>     Jason
>
>  *CURRENT 5.5: *
>  5.5.  Turning Off DNS Resolver Whitelisting
>
> Domains that choose to implement DNS Resolver Whitelisting generally
> consider it to be a temporary measure. It is unclear how implementers will
> judge when the network conditions will have changed sufficiently to justify
> turning off DNS Resolver Whitelisting and/or what the process and timing
> will be for discontinuing this practice, though the extent of IPv6
> deployment to end users in networks, the state of IPv6-related impairment,
> and the maturity of IPv6 operations are all clearly factors. However,
> implementers may wish to take into consideration that, as a practical
> matter, it will be impossible to get to a point where there are no longer
> any IPv6-related impairments; some reasonably small number of hosts will
> inevitably be left behind as end users elect not to upgrade them or as some
> hosts are incapable of being upgraded.
>  *PROPOSED 5.5 (NEW TEXT IN ALL CAPS):*
>  5.5.  Turning Off DNS Resolver Whitelisting
>
> Domains that choose to implement DNS Resolver Whitelisting generally
> consider it to be a temporary measure. It is unclear how implementers will
> judge when the network conditions will have changed sufficiently to justify
> turning off DNS Resolver Whitelisting and/or what the process and timing
> will be for discontinuing this practice, though the extent of IPv6
> deployment to end users in networks, the state of IPv6-related impairment,
> and the maturity of IPv6 operations are all clearly factors. However, *SOME
> IMPLEMENTERS HAVE ANNOUNCED THAT THEY PLAN TO PERMANENTLY TURN OFF
> WHITELISTING BEGINNING ON WORLD IPV6 DAY IN JUNE 2012 [REFERENCE]. IN ANY
> CASE*, implementers may wish to take into consideration that, as a
> practical matter, it will be impossible to get to a point where there are
> no longer any IPv6-related impairments; some reasonably small number of
> hosts will inevitably be left behind as end users elect not to upgrade them
> or as some hosts are incapable of being upgraded.
> <eom>
>

I think the suggested change does not go far enough. The
"high-service-level domains" that prompted this draft to be written, and
all the implementers I'm currently aware of, are decommissioning the
practice.

So the paragraph that states, "It is unclear how implementers will judge
when the network conditions will have changed sufficiently to justify
turning off DNS Resolver Whitelisting and/or what the process and timing
will be for discontinuing this practice" is still incorrect. Can you just
remove the paragraph and start the section with "Many implementers have
announced that they plan to permanently turn off whitelisting beginning
on..." ?

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


<br><br><div class=3D"gmail_quote">On Thu, Feb 16, 2012 at 00:52, Livingood=
, Jason <span dir=3D"ltr">&lt;<a href=3D"mailto:Jason_Livingood@cable.comca=
st.com">Jason_Livingood@cable.comcast.com</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">





<div style=3D"font-size:16px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<span>
<blockquote style=3D"BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0=
 0 5">
<div>
<div style=3D"font-size:16px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div>
<div>
<div><span>
<div class=3D"gmail_quote"><div class=3D"im">
<div>To be more specific, at least section 5.5 (&quot;it is unclear how=A0i=
mplementers will judge when the network conditions will have changed=A0suff=
iciently to justify turning off DNS Resolver Whitelisting and/or=A0what the=
 process and timing will be for discontinuing
 this practice&quot;) is now incorrect. It *is* clear, and it&#39;s what th=
ose implementers are doing as part of World IPv6 Launch.</div>
<div><br>
</div>
</div><div class=3D"im"><div>Does that make more sense?</div>
</div></div>
</span></div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>As the author, if it helps I plan to make the following change to Sect=
ion 5.5 following the conclusion of IETF Last Call. I ran this by a few fol=
ks already and it seems broadly acceptable (have not heard from Lorenzo yet=
 though).=A0</div>


<div><br>
</div>
<span>
<div>
<div style=3D"font-size:16px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div>
<div>
<div>
<div>Jason</div>
<div><br>
</div>
<div><u>CURRENT 5.5:=A0</u></div>
<div>
<h3 style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;text=
-align:-webkit-auto;font-style:normal;font-weight:bold;line-height:normal;c=
olor:rgb(51,51,51);text-transform:none;white-space:normal;font-family:helve=
tica,monaco,&#39;MS Sans Serif&#39;,arial,sans-serif;word-spacing:0px">


<font size=3D"3">5.5.=A0 Turning Off DNS Resolver Whitelisting</font></h3>
<p style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;text-=
align:-webkit-auto;font-style:normal;font-weight:normal;margin-right:2em;li=
ne-height:normal;text-transform:none;margin-left:2em;white-space:normal;fon=
t-family:verdana,charcoal,helvetica,arial,sans-serif;word-spacing:0px">


Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. It is unclear how implementers will judge =
when the network conditions will have changed sufficiently to justify turni=
ng off DNS Resolver Whitelisting
 and/or what the process and timing will be for discontinuing this practice=
, though the extent of IPv6 deployment to end users in networks, the state =
of IPv6-related impairment, and the maturity of IPv6 operations are all cle=
arly factors. However, implementers
 may wish to take into consideration that, as a practical matter, it will b=
e impossible to get to a point where there are no longer any IPv6-related i=
mpairments; some reasonably small number of hosts will inevitably be left b=
ehind as end users elect not to
 upgrade them or as some hosts are incapable of being upgraded.</p>
</div>
<div><u>PROPOSED 5.5 (NEW TEXT IN ALL CAPS):</u></div>
<div>
<h3 style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;text=
-align:-webkit-auto;font-style:normal;font-weight:bold;line-height:normal;c=
olor:rgb(51,51,51);text-transform:none;white-space:normal;font-family:helve=
tica,monaco,&#39;MS Sans Serif&#39;,arial,sans-serif;word-spacing:0px">


<font size=3D"3">5.5.=A0 Turning Off DNS Resolver Whitelisting</font></h3>
<p style=3D"text-indent:0px;letter-spacing:normal;font-variant:normal;text-=
align:-webkit-auto;font-style:normal;margin-right:2em;line-height:normal;te=
xt-transform:none;margin-left:2em;white-space:normal;font-family:verdana,ch=
arcoal,helvetica,arial,sans-serif;word-spacing:0px">


Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. It is unclear how implementers will judge =
when the network conditions will have changed sufficiently to justify turni=
ng off DNS Resolver Whitelisting
 and/or what the process and timing will be for discontinuing this practice=
, though the extent of IPv6 deployment to end users in networks, the state =
of IPv6-related impairment, and the maturity of IPv6 operations are all cle=
arly factors. However,=A0<b>SOME IMPLEMENTERS
 HAVE ANNOUNCED THAT THEY PLAN TO PERMANENTLY TURN OFF WHITELISTING BEGINNI=
NG ON WORLD IPV6 DAY IN JUNE 2012 [REFERENCE]. IN ANY CASE</b>, implementer=
s may wish to take into consideration that, as a practical matter, it will =
be impossible to get to a point
 where there are no longer any IPv6-related impairments; some reasonably sm=
all number of hosts will inevitably be left behind as end users elect not t=
o upgrade them or as some hosts are incapable of being upgraded.</p>
<div>&lt;eom&gt;</div></div></div></div></div></div></div></span></div></bl=
ockquote><div><br></div><div>I think the suggested change does not go far e=
nough. The &quot;high-service-level domains&quot; that prompted this draft =
to be written, and all the implementers I&#39;m currently aware of, are dec=
ommissioning the practice.</div>

<div><br></div><div>So the paragraph that states, &quot;It is unclear how i=
mplementers will judge when the network conditions will have changed suffic=
iently to justify turning off DNS Resolver Whitelisting and/or what the pro=
cess and timing will be for discontinuing this practice&quot; is still inco=
rrect. Can you just remove the paragraph and start the section with &quot;M=
any implementers have announced that they plan to permanently turn off whit=
elisting beginning on...&quot; ?</div>

</div>

--f46d0445183bd954b704b974b9de--

From robert@hernady.cz  Tue Feb 21 05:51:20 2012
Return-Path: <robert@hernady.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 CA08021F86D7 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 05:51:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.61
X-Spam-Level: 
X-Spam-Status: No, score=0.61 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Can+4PqXhIUM for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 05:51:20 -0800 (PST)
Received: from mail.firma6p.cz (mail.firma6p.cz [85.207.51.98]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB8A21F86D0 for <ietf@ietf.org>; Tue, 21 Feb 2012 05:51:18 -0800 (PST)
Received: from POSTAK1.firma6p.cz ([fe80::1846:13ff:5ea7:18b1]) by postak1.firma6p.cz ([fe80::1846:13ff:5ea7:18b1%11]) with mapi id 14.01.0355.002; Tue, 21 Feb 2012 14:51:16 +0100
From: Robert Hernady <robert@hernady.cz>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Explanation of the OCSP sign request 
Thread-Topic: Explanation of the OCSP sign request 
Thread-Index: AczwnKmZeAa6NgQVQdKrLgfe7t0r+g==
Date: Tue, 21 Feb 2012 13:51:16 +0000
Message-ID: <A025E9A3487E4B44B7112C4430DA8252A3BA1A05@postak1.firma6p.cz>
Accept-Language: cs-CZ, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.0.1]
Content-Type: multipart/alternative; boundary="_000_A025E9A3487E4B44B7112C4430DA8252A3BA1A05postak1firma6pc_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 21 Feb 2012 11:22:12 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:52:52 -0000

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

Hi,

I'm looking for the better understanding for the RFC 2560  Online Certifica=
te Status Protocol - OCSP.

The section 4.1 defines the ASN.1 structure for the OCSP request. Follows t=
he shortened structure.

OCSPRequest
   TBSRequest
   OPTIONAL Signature,

where the signature is marked as OPTIONAL. That one leads to the conclusion=
 that signing of the OCSP request is not required and the implementer of th=
e OCSP client MAY digitally sign that request.

But the section 2.3  Exception Cases defines error types and one of them is=
 "-sigRequired"

   The response "sigRequired" is returned in cases where the server
   requires the client sign the request in order to construct a
   response.


Does it mean that in that case the signature of the request becomes mandato=
ry? Does it mean that OCSP clients that have not implemented OCSP request s=
igning after are breaking this RFC?

Thanks in advance

Robert Hernady

--_000_A025E9A3487E4B44B7112C4430DA8252A3BA1A05postak1firma6pc_
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)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:CS;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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"CS" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;m looking for the bette=
r understanding for the RFC
</span>2560&nbsp; Online Certificate Status Protocol &#8211; OCSP.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The section 4.1 defines the <span lang=3D"EN-US">ASN=
.1 structure for the OCSP request. Follows the shortened structure.
</span><span lang=3D"EN-US" style=3D"font-size:12.0pt;color:#1F497D;mso-far=
east-language:CS"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">O=
CSPRequest
</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Cou=
rier New&quot;;color:black;mso-fareast-language:CS"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">&=
nbsp;&nbsp;&nbsp;TBSRequest
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US" s=
tyle=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black">&=
nbsp;&nbsp;&nbsp;OPTIONAL Signature,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US">w=
here the signature is marked as OPTIONAL. That one leads to the conclusion =
that signing of the OCSP request is not required and the implementer of the=
 OCSP client MAY digitally sign that request.
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US">B=
ut the section 2.3&nbsp; Exception Cases defines error types and one of the=
m is &#8220;&#8212;sigRequired&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:CS">&nbsp;&nbsp; The response &quot;si=
gRequired&quot; is returned in cases where the server<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:CS">&nbsp;&nbsp; requires the client s=
ign the request in order to construct a<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;mso-fareast-language:CS">&nbsp;&nbsp; response.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span lang=3D"EN-US"><=
o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Does it mean that in that case =
the signature of the request becomes mandatory? Does it mean that OCSP clie=
nts that have not implemented OCSP request signing after are breaking this =
RFC?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks in advance<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Robert Hernady<o:p></o:p></span=
></p>
</div>
</body>
</html>

--_000_A025E9A3487E4B44B7112C4430DA8252A3BA1A05postak1firma6pc_--

From jason_livingood@cable.comcast.com  Tue Feb 21 11:38:11 2012
Return-Path: <jason_livingood@cable.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 A2C6621E807E; Tue, 21 Feb 2012 11:38:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.164
X-Spam-Level: 
X-Spam-Status: No, score=-103.164 tagged_above=-999 required=5 tests=[AWL=-1.934, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6GyP-mpV8Ri; Tue, 21 Feb 2012 11:38:10 -0800 (PST)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id A636921E807B; Tue, 21 Feb 2012 11:38:10 -0800 (PST)
Received: from ([24.40.56.114]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.6844449; Tue, 21 Feb 2012 12:27:44 -0700
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%11]) with mapi id 14.01.0355.002; Tue, 21 Feb 2012 14:38:05 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-v6-aaaa-whitelisting-implications-08.txt> (Considerations for Transitioning Content to IPv6) to Informational RFC
Thread-Index: AQHM6/nKbjYam0no7UGRxd2Rv+MjlJZHV/UAgABwwIA=
Date: Tue, 21 Feb 2012 19:38:05 +0000
Message-ID: <CB6958DA.51145%jason_livingood@cable.comcast.com>
In-Reply-To: <CAKD1Yr2n91=8n3n=Nh=zXFy8Rpzj_8D0C=sQQ2B8N0PGEgEQnQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [24.40.56.165]
Content-Type: multipart/alternative; boundary="_000_CB6958DA51145jasonlivingoodcablecomcastcom_"
MIME-Version: 1.0
Cc: v6ops v6ops WG <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:38:11 -0000

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

On 2/21/12 2:54 AM, "Lorenzo Colitti" <lorenzo@google.com<mailto:lorenzo@go=
ogle.com>> wrote:
I think the suggested change does not go far enough. The "high-service-leve=
l domains" that prompted this draft to be written, and all the implementers=
 I'm currently aware of, are decommissioning the practice.

So the paragraph that states, "It is unclear how implementers will judge wh=
en the network conditions will have changed sufficiently to justify turning=
 off DNS Resolver Whitelisting and/or what the process and timing will be f=
or discontinuing this practice" is still incorrect. Can you just remove the=
 paragraph and start the section with "Many implementers have announced tha=
t they plan to permanently turn off whitelisting beginning on..." ?

I've changed it around to the following:

Domains that choose to implement DNS Resolver Whitelisting generally consid=
er it to be a temporary measure. Many implementers have announced that they=
 plan to permanently turn off DNS Resolver Whitelisting beginning on the da=
te of the World IPv6 Launch, on June 6, 2012 <xref target=3D'World IPv6 Lau=
nch'/>. For any implementers that do not turn off DNS Resolver Whitelisting=
 at that time, it may be unclear how each and every one will judge when the=
 network conditions to have changed sufficiently to justify turning off DNS=
 Resolver Whitelisting. That being said, it is clear that the extent of IPv=
6 deployment to end users in networks, the state of IPv6-related impairment=
, and the maturity of IPv6 operations are all important factors. Any such i=
mplementers may wish to take into consideration that, as a practical matter=
, it will be impossible to get to a point where there are no longer any IPv=
6-related impairments; some reasonably small number of hosts will inevitabl=
y be left behind as end users elect not to upgrade them or as some hosts ar=
e incapable of being upgraded.


Thanks for your input,
Jason

--_000_CB6958DA51145jasonlivingoodcablecomcastcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <BD034777E2CDE34A83C566640B19C386@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
ly: Calibri, sans-serif; ">
<span id=3D"OLK_SRC_BODY_SECTION">
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT:=
 #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div class=3D"gmail_quote">
<div style=3D"font-size:16px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div>On 2/21/12 2:54 AM, &quot;Lorenzo Colitti&quot; &lt;<a href=3D"mailto:=
lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:</div>
</div>
<div>I think the suggested change does not go far enough. The &quot;high-se=
rvice-level domains&quot; that prompted this draft to be written, and all t=
he implementers I'm currently aware of, are decommissioning the practice.</=
div>
<div><br>
</div>
<div>So the paragraph that states, &quot;It is unclear how implementers wil=
l judge when the network conditions will have changed sufficiently to justi=
fy turning off DNS Resolver Whitelisting and/or what the process and timing=
 will be for discontinuing this practice&quot;
 is still incorrect. Can you just remove the paragraph and start the sectio=
n with &quot;Many implementers have announced that they plan to permanently=
 turn off whitelisting beginning on...&quot; ?</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>I've changed it around to the following:</div>
<div><br>
</div>
<div><b>Domains that choose to implement DNS Resolver Whitelisting generall=
y consider it to be a temporary measure. Many implementers have announced t=
hat they plan to permanently turn off DNS Resolver Whitelisting beginning o=
n the date of the World IPv6 Launch,
 on June 6, 2012 &lt;xref target=3D'World IPv6 Launch'/&gt;. For any implem=
enters that do not turn off DNS Resolver Whitelisting at that time, it may =
be unclear how each and every one will judge when the network conditions to=
 have changed sufficiently to justify turning
 off DNS Resolver Whitelisting. That being said, it is clear that the exten=
t of IPv6 deployment to end users in networks, the state of IPv6-related im=
pairment, and the maturity of IPv6 operations are all important factors. An=
y such implementers may wish to
 take into consideration that, as a practical matter, it will be impossible=
 to get to a point where there are no longer any IPv6-related impairments; =
some reasonably small number of hosts will inevitably be left behind as end=
 users elect not to upgrade them
 or as some hosts are incapable of being upgraded.</b></div>
<div><b><br>
</b></div>
<div><b><br>
</b></div>
<div>Thanks for your input,</div>
<div>Jason</div>
</body>
</html>

--_000_CB6958DA51145jasonlivingoodcablecomcastcom_--

From mrex@sap.com  Tue Feb 21 11:55:54 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACFE21E809F for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 11:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.06
X-Spam-Level: 
X-Spam-Status: No, score=-10.06 tagged_above=-999 required=5 tests=[AWL=0.189,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJoLS1Wwtd-W for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 11:55:54 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 9BECB21E80A0 for <ietf@ietf.org>; Tue, 21 Feb 2012 11:55:53 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q1LJtjNu007038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 21 Feb 2012 20:55:45 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202211955.q1LJteHi015283@fs4113.wdf.sap.corp>
Subject: Re: Explanation of the OCSP sign request
To: robert@hernady.cz (Robert Hernady)
Date: Tue, 21 Feb 2012 20:55:40 +0100 (MET)
In-Reply-To: <A025E9A3487E4B44B7112C4430DA8252A3BA1A05@postak1.firma6p.cz> from "Robert Hernady" at Feb 21, 12 01:51:16 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:55:54 -0000

Robert Hernady wrote:
> 
> I'm looking for the better understanding for the
> RFC 2560  Online Certificate Status Protocol - OCSP.
> 
> The section 4.1 defines the ASN.1 structure for the OCSP request.
> Follows the shortened structure.
> 
> OCSPRequest
>    TBSRequest
>    OPTIONAL Signature,
> 
> where the signature is marked as OPTIONAL. That one leads to the
> conclusion that signing of the OCSP request is not required and
> the implementer of the OCSP client MAY digitally sign that request.
> 
> But the section 2.3  Exception Cases defines error types and one
> of them is "-sigRequired"
> 
>    The response "sigRequired" is returned in cases where the server
>    requires the client sign the request in order to construct a
>    response.
> 
> 
> Does it mean that in that case the signature of the request becomes
> mandatory? Does it mean that OCSP clients that have not implemented
> OCSP request signing after are breaking this RFC?


OCSP servers that are requiring an OCSP request to be signed are not
"breaking" the protocol, but preclude interoperability with the vast
majority of potential peers, by using a standardized protocol option
to implement a very restrictive policy in whose OCSP requests they answer.

Whether such a policy is configured for an OCSP responder is a
deployment decision of the consumer of the technology.

Breaking interop is the logical result when requiring the use of
optional protocol features, so it has to be assumed the operator
of an OCSP responder that requires signatures on OCSP request explicitly
desires the non-interoperability outcome.  I don't see a standardized
indication of acceptable certification_authorities for the signature
on the OCSP request to accompany the "sigRequired" OCSPResponseStatus,
so this policy can be expected to work only for extremely small groups
of RPs, matching the following preconditions:

    - all RPs in the PKI have implemented the optional protocol feature
      "signed OCSP requests"
    - all RPs in the PKI have out-of-band knowledge of certificate issuers
      acceptable to that OCSP responder for signing OCSP requests.
    - all RPs in the PKI have signing PKI credentials issued by one of
      those certificate issuers acceptable to the OCSP responder.

-Martin

From presnick@qualcomm.com  Tue Feb 21 12:32:54 2012
Return-Path: <presnick@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 0FBEE11E807F for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 12:32:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.579
X-Spam-Level: 
X-Spam-Status: No, score=-106.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9-raq4YgXO6 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 12:32:49 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 98C2B11E8088 for <ietf@ietf.org>; Tue, 21 Feb 2012 12:32:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1329856368; x=1361392368; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F43FF5C.6060003@qualcomm.com>|Date:=20Tu e,=2021=20Feb=202012=2014:32:28=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20IETF-Discussion=20list=20<ietf @ietf.org>|Subject:=20Conclusion=20of=20Last=20Call=20for =20draft-ietf-sieve-convert=20and=20draft-ietf-sieve-noti fy-sip-message|Content-Type:=20text/plain=3B=20charset=3D "ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=Iz6dlsm40d6DOMSW+V9qjr3GEMD/7/HADrnL3+AaWsk=; b=WV/PuDPM8ER/ynDc5vWdNPcMdF2o3aeY30pYDxYEfffP+ueFlZ3FTOsw lPDpHd7IoxVLtab5oV0ZZXAGiAO3E8a8tJ64NouXzD1IPhOMwMSsxilQN UfIvS0xRSHci/dIQS5764wuyhL6ZLfH8u+Nt7K2zPZQcrM8mgX31VCACW g=;
X-IronPort-AV: E=McAfee;i="5400,1158,6626"; a="165068439"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 21 Feb 2012 12:32:32 -0800
X-IronPort-AV: E=Sophos;i="4.73,457,1325491200"; d="scan'208";a="171787687"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 21 Feb 2012 12:32:32 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 21 Feb 2012 12:32:31 -0800
Message-ID: <4F43FF5C.6060003@qualcomm.com>
Date: Tue, 21 Feb 2012 14:32:28 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: IETF-Discussion list <ietf@ietf.org>
Subject: Conclusion of Last Call for draft-ietf-sieve-convert and draft-ietf-sieve-notify-sip-message
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:32:54 -0000

I wanted to inform the community of the results of the second Last Call 
issued for draft-ietf-sieve-convert and 
draft-ietf-sieve-notify-sip-message. To remind you of the circumstances: 
After these two documents were approved by the IESG and sent on to the 
RFC Editor, an IPR disclosure was made pertaining to each of them 
indicating that one of the document editors for both documents was also 
the listed inventor for the disclosed patent. The disclosures were made 
by the document editor's employer and indicate that the date of the 
patent filings was prior to the adoption of these two drafts by the 
SIEVE working group. The RFC Editor was asked to suspend their work on 
the documents, and a second Last Call was made.

After reviewing discussions in the SIEVE WG and on the IETF mailing 
list, the chairs have decided (and I support) that, because of the 
failure to disclose the IPR as required by BCP 79 (RFC 3979), and as per 
RFC 2418 Section 6.1, the following actions are appropriate and will be 
taken:

- The document editor in question is no longer a document editor for 
these two documents.
- The person's name will be removed from the front page of the documents 
and from the Authors' Address section.
- The person's name will be added to the Acknowledgments section of both 
documents to identify that he did contribute text to the drafts.
- The RFC Editor will be asked to continue processing and publication of 
these drafts as RFCs.

We will be notifying the RFC Editor of this decision presently.

Meanwhile, the employer of the document editor in question has made 
followup disclosures on each of the documents, saying that they 
"covenant not to assert any such claim against any party for making, 
using, selling, offering for sale or importing a product that implements 
the corresponding part of the specification." The full text of the 
disclosures can be seen here:

https://datatracker.ietf.org/ipr/1680/
https://datatracker.ietf.org/ipr/1681/

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From stephen.farrell@cs.tcd.ie  Tue Feb 21 14:19:32 2012
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 9104721F8633; Tue, 21 Feb 2012 14:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2o48WUfXVRut; Tue, 21 Feb 2012 14:19:31 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 995C521F862F; Tue, 21 Feb 2012 14:19:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 580B8171CFD; Tue, 21 Feb 2012 22:19:30 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1329862770; bh=jKExa3zGtQKpr3 4w/OaU4I889GOABc8PGlcRxPT4asI=; b=6qouvOOY8VoFLQYHO05KlTj+nFks4K E7dL4IzgEsMlGBuO8t+C9Qo5l6M40RSxlq7IAZWGlCUC/afvIyffP/3r6xyhHFLR ZvTtBtla53jv60oeZXuVoY0rHnGs6MEsUWeMAngQMkNlxstr5DIno5tEugVwKsGo OiBm/HqlGPEFJn+Yb2aKV1FESblLMpz8KmbWh0aeDedHrX5PeNP74nJmCyOlRL4w hPiCXXVT7j+i6yCa4gwdSyrObXGvo129ekmi5XJw7n153e9miF5Gsl5LNUGHfGua MHDDWSuSCfN8PjXfvZzGz/q8qCwHTtJtUuLGSufXBku/wEEJqg4wqzIg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Lh8fOcTD7hD1; Tue, 21 Feb 2012 22:19:30 +0000 (GMT)
Received: from [10.87.48.9] (unknown [86.42.23.218]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 9BC13171C28; Tue, 21 Feb 2012 22:19:28 +0000 (GMT)
Message-ID: <4F441870.8010206@cs.tcd.ie>
Date: Tue, 21 Feb 2012 22:19:28 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de>
In-Reply-To: <4F43E75C.2010309@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:19:32 -0000

Hi Julian,

On 02/21/2012 06:50 PM, Julian Reschke wrote:
> On 2012-02-21 19:37, Stephen Farrell wrote:
>> ...
>>> I believe this should be orthogonal to HTTP/2.0. Is there a specific
>>> thing that makes it impossible to use the existing authentication
>>> framework?
>>
>> Who knows? We don't have a protocol on the table yet. I
>> would imagine that some level of backwards compatibility
>> would be a requirement of course, or at least an issue to
>> be considered.
>>
>> But the existing HTTP client authentication is also not
>> necessarily very useful, and there have been a number of
>> efforts to improve on that, none of which seem to have
>> gotten sufficient traction to get widely deployed/used.
>> Maybe HTTP/2.0 is a good time to try fix that.
>
> Well, we have an existing authentication framework. It would be
> interesting to find out what's missing from it.

Fair point.

I would wonder whether that framework could be used
as-is if HTTP/2.0 does do away "with the of HTTP/1.x
message framing and syntax" but I guess some equivalent
functionality could be defined in that case.

So as in my initial mail the 1st question here is, what
does "modern" mean in this draft charter? E.g. does it
mean "same as the current framework with different
bits" or something else? If so, what?

And then should it include adding some new options
or MTI auth schemes as part of HTTP/2.0 or even looking
at that? (I think it ought to include trying for that
personally, even if there is a higher-than-usual risk
of failure.)

S

From barryleiba.mailing.lists@gmail.com  Tue Feb 21 14:36:12 2012
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 217A311E80C4; Tue, 21 Feb 2012 14:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.957
X-Spam-Level: 
X-Spam-Status: No, score=-102.957 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nsJEizMRD6B4; Tue, 21 Feb 2012 14:36:11 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7E79711E807F; Tue, 21 Feb 2012 14:36:11 -0800 (PST)
Received: by yhkk25 with SMTP id k25so3637627yhk.31 for <multiple recipients>; Tue, 21 Feb 2012 14:36:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wlAI9qGqrdpI0Qg+bLo1pTtyRBTmLqE4kMNDOl6q+Mg=; b=ZTReime3Jgul61jmJ+PaYPa4w9qHQHm25x7JtMj6v3Via61cJ8h+25gwqn+7THp4rB W3fnLN4Io06XL4ubnY5FJiI5x2wslMQqSh2pWMVhpRHjjWhBSnR1r8HuW1GC5EP92Jvm eVvsklmHyzejO37wo4t9U/nuQuBqw8bHiZZ48=
MIME-Version: 1.0
Received: by 10.236.79.202 with SMTP id i50mr30176471yhe.61.1329863771173; Tue, 21 Feb 2012 14:36:11 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.58.20 with HTTP; Tue, 21 Feb 2012 14:36:11 -0800 (PST)
In-Reply-To: <CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com>
Date: Tue, 21 Feb 2012 17:36:11 -0500
X-Google-Sender-Auth: UljDvpXDS1VBlo33hwVtAJ_qLBU
Message-ID: <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Barry Leiba <barryleiba@computer.org>
To: Robert Collins <robertc@squid-cache.org>
Content-Type: multipart/alternative; boundary=20cf30051430ae31e804b9810945
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, IETF-Discussion <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:36:12 -0000

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

>
> browser id, openid, and oauth are all authentication frameworks built
> on top of HTTP
>

OAuth is an authorization framework, not an authentication one.  Please be
careful to make the distinction.

What we're looking at here is the need for an HTTP authentication system
that (for example) doesn't send reusable credentials, is less susceptible
to spoofing attacks, and so on.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">browser id, openid, and oauth are all authen=
tication frameworks built<br>on top of HTTP<br>
</blockquote><div><br></div><div>OAuth is an authorization framework, not a=
n authentication one. =A0Please be careful to make the distinction.</div><d=
iv><br></div><div>What we&#39;re looking at here is the need for an HTTP au=
thentication system that (for example) doesn&#39;t send reusable credential=
s, is less susceptible to spoofing attacks, and so on.</div>
<div><br></div><div>Barry=A0</div>

--20cf30051430ae31e804b9810945--

From mnot@mnot.net  Tue Feb 21 14:40:15 2012
Return-Path: <mnot@mnot.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 D777B21F87A8; Tue, 21 Feb 2012 14:40:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d4Tg4+hrVyOF; Tue, 21 Feb 2012 14:40:15 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id B0A2711E80D2; Tue, 21 Feb 2012 14:40:14 -0800 (PST)
Received: from [192.168.0.100] (unknown [101.170.32.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0828C50A64; Tue, 21 Feb 2012 17:40:01 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F441870.8010206@cs.tcd.ie>
Date: Wed, 22 Feb 2012 09:40:02 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1251.1)
Cc: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:40:16 -0000

On 22/02/2012, at 9:19 AM, Stephen Farrell wrote:

>=20
> Hi Julian,
>=20
> On 02/21/2012 06:50 PM, Julian Reschke wrote:
>> On 2012-02-21 19:37, Stephen Farrell wrote:
>>> ...
>>>> I believe this should be orthogonal to HTTP/2.0. Is there a =
specific
>>>> thing that makes it impossible to use the existing authentication
>>>> framework?
>>>=20
>>> Who knows? We don't have a protocol on the table yet. I
>>> would imagine that some level of backwards compatibility
>>> would be a requirement of course, or at least an issue to
>>> be considered.
>>>=20
>>> But the existing HTTP client authentication is also not
>>> necessarily very useful, and there have been a number of
>>> efforts to improve on that, none of which seem to have
>>> gotten sufficient traction to get widely deployed/used.
>>> Maybe HTTP/2.0 is a good time to try fix that.
>>=20
>> Well, we have an existing authentication framework. It would be
>> interesting to find out what's missing from it.
>=20
> Fair point.
>=20
> I would wonder whether that framework could be used
> as-is if HTTP/2.0 does do away "with the of HTTP/1.x
> message framing and syntax" but I guess some equivalent
> functionality could be defined in that case.

That shouldn't affect the framework at all. At most, you'd have to =
define how to re-serialise the current syntax if you don't have a way to =
"tunnel" it (since HTTP/1.1 passthrough is required).


> So as in my initial mail the 1st question here is, what
> does "modern" mean in this draft charter? E.g. does it
> mean "same as the current framework with different
> bits" or something else? If so, what?

As discussed off-list, I'd be happy to drop this phrase from *this* =
charter, in anticipation of it being worked out in discussions about the =
*next* one.


> And then should it include adding some new options
> or MTI auth schemes as part of HTTP/2.0 or even looking
> at that? (I think it ought to include trying for that
> personally, even if there is a higher-than-usual risk
> of failure.)


Based on past experience, I think the risk is very high, and we don't =
need to pile any more risk onto this particular project.=20

Also, most of the discussions about authentication and associated =
problems on the Web are *not* exclusive to HTTP or even protocol =
artefacts; they include concerns like UI and human factors, integration =
into hypertext, etc. As such, what we really need is a "whole of stack" =
focus on Web authentication; shoving it into this particular WG will, =
IMO, lead to a predictable failure.

Regards,


--
Mark Nottingham
http://www.mnot.net/





From tbray@textuality.com  Tue Feb 21 14:46:15 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1CA521F87DA; Tue, 21 Feb 2012 14:46:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.455
X-Spam-Level: 
X-Spam-Status: No, score=-1.455 tagged_above=-999 required=5 tests=[AWL=1.522,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvdVk2DkvlJC; Tue, 21 Feb 2012 14:46:15 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id E676A21F87D6; Tue, 21 Feb 2012 14:46:14 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so10563574obb.31 for <multiple recipients>; Tue, 21 Feb 2012 14:46:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.89.65 with SMTP id bm1mr14226759obb.52.1329864374544; Tue, 21 Feb 2012 14:46:14 -0800 (PST)
Received: by 10.182.137.69 with HTTP; Tue, 21 Feb 2012 14:46:14 -0800 (PST)
X-Originating-IP: [76.10.184.127]
In-Reply-To: <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
Date: Tue, 21 Feb 2012 14:46:14 -0800
Message-ID: <CAHBU6iuNhkPGZ5M3FyM2aZmqzVmRW2iRvtyQaYhk65s4FuVZDg@mail.gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Tim Bray <tbray@textuality.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmKXEf5q3jkTgNs9YYFun0Ve0QGjDPkEa3fy6eKYfWP41v2fxF62q1wS+9XfKg2Wx4b8ydg
Cc: Julian Reschke <julian.reschke@gmx.de>, iesg@ietf.org, IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:46:15 -0000

[in-line]

On Tue, Feb 21, 2012 at 2:40 PM, Mark Nottingham <mnot@mnot.net> wrote:
>> And then should it include adding some new options
>> or MTI auth schemes as part of HTTP/2.0 or even looking
>> at that? (I think it ought to include trying for that
>> personally, even if there is a higher-than-usual risk
>> of failure.)
>
>
> Based on past experience, I think the risk is very high, and we don't need to pile any more risk onto this particular project.

+1

HTTP's ability to be equipped with security technology has been
adequate, and I haven't heard much argument that its semantics were
the big obstacle to newer/better security.  Preserving its semantics
means its successor should be equally adequate.

Mnot is *understating* the risk of loading up the charter with this stuff. -T

From stephen.farrell@cs.tcd.ie  Tue Feb 21 14:53:15 2012
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 652B811E80E7; Tue, 21 Feb 2012 14:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yODFexdqWeak; Tue, 21 Feb 2012 14:53:14 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 3875111E80E4; Tue, 21 Feb 2012 14:53:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id A0F1F171CFD; Tue, 21 Feb 2012 22:53:13 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1329864793; bh=TShQetokzfKhXU 5DKCINSps7zffzcCTxUOw/cYPTffQ=; b=MWaVVMPz7xxiArjSf3yYEUjJR0jNEn RtEs46isJaVM0QTQFsMwtD9s9OGEb8I7oP1xpu2oR3I0BKK/wRfNRAWbvh6fT+BB Es8qqJW4tsFqHDP/ab7aE2xtw5sx3+W3JHFOK46ydablVQPE8bg1j8ZpHtekCE3D gIOrtVdIUdCu1dR9LK78HJu/yUVOmK8wZa45RpEIRVG5GlBuuhgA+cgWEZ4qzZ25 K+KVSmWQfRSsy3wdfKT1rPAWdW3rEHbYKP+n0buXotqGwQy4gjmqIDD9yR3ue3FE 7lRXaFd4/ucwuPrwpYjD8iOnKuPEMH4gadY0rBEzOrZbrQ7id16YfyTQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id pSVJBfCAUREE; Tue, 21 Feb 2012 22:53:13 +0000 (GMT)
Received: from [10.87.48.9] (unknown [86.42.23.218]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id BF6C7171C28; Tue, 21 Feb 2012 22:53:12 +0000 (GMT)
Message-ID: <4F442058.5070804@cs.tcd.ie>
Date: Tue, 21 Feb 2012 22:53:12 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
In-Reply-To: <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, iesg@ietf.org, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:53:27 -0000

On 02/21/2012 10:40 PM, Mark Nottingham wrote:
>
> On 22/02/2012, at 9:19 AM, Stephen Farrell wrote:
>

>> So as in my initial mail the 1st question here is, what
>> does "modern" mean in this draft charter? E.g. does it
>> mean "same as the current framework with different
>> bits" or something else? If so, what?
>
> As discussed off-list, I'd be happy to drop this phrase from *this* charter, in anticipation of it being worked out in discussions about the *next* one.

Well, I think the phrase does need to be replaced
by something else all right.

I'm reluctant to omit mention of security entirely
of course and do want to know what's gonna be done
for authentication in a putative HTTP/2.0.

Like I said, I'm pretty skeptical that any significant
change to security properties will be achievable at
that next charter stage.

>> And then should it include adding some new options
>> or MTI auth schemes as part of HTTP/2.0 or even looking
>> at that? (I think it ought to include trying for that
>> personally, even if there is a higher-than-usual risk
>> of failure.)
>
>
> Based on past experience, I think the risk is very high, and we don't need to pile any more risk onto this particular project.

Based on past experience the milestones for this will be
wildly optimistic and it'll really take five years so at
the end of 2017 we'll be right where we are in terms of
HTTP authentication for all of which time HTTP authentication
will be the "next thing" to do. (Ok, I'm exaggerating a
bit there.)

I think both experiences are valid.

> Also, most of the discussions about authentication and associated problems on the Web are *not* exclusive to HTTP or even protocol artefacts; they include concerns like UI and human factors, integration into hypertext, etc. As such, what we really need is a "whole of stack" focus on Web authentication; shoving it into this particular WG will, IMO, lead to a predictable failure.

It is true that many sites don't use HTTP authentication
for UI reasons. I don't think it follows that doing nothing
is the right approach. (Well, one could argue to remove all
user authentication from HTTP I guess - is that one of the
proposals?)

Cheers,
S.



From mnot@mnot.net  Tue Feb 21 14:55:48 2012
Return-Path: <mnot@mnot.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 DED4F11E80E7; Tue, 21 Feb 2012 14:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.599
X-Spam-Level: 
X-Spam-Status: No, score=-104.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXMjv0Y+EJwf; Tue, 21 Feb 2012 14:55:48 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id EAF3411E80F6; Tue, 21 Feb 2012 14:55:45 -0800 (PST)
Received: from [192.168.0.100] (unknown [101.170.32.89]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9006950A5D; Tue, 21 Feb 2012 17:55:42 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F442058.5070804@cs.tcd.ie>
Date: Wed, 22 Feb 2012 09:55:41 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F042342-7C6A-4ED4-9A67-591644D3D5D6@mnot.net>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net> <4F442058.5070804@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1251.1)
Cc: Julian Reschke <julian.reschke@gmx.de>, iesg@ietf.org, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:55:49 -0000

Stephen,=20

The approach we're advocating for this WG is to solicit well-formed =
proposals, select one and develop it.=20

If there isn't one for HTTP authentication, how are you advocating we =
proceed?

Regards,



On 22/02/2012, at 9:53 AM, Stephen Farrell wrote:

>=20
>=20
> On 02/21/2012 10:40 PM, Mark Nottingham wrote:
>>=20
>> On 22/02/2012, at 9:19 AM, Stephen Farrell wrote:
>>=20
>=20
>>> So as in my initial mail the 1st question here is, what
>>> does "modern" mean in this draft charter? E.g. does it
>>> mean "same as the current framework with different
>>> bits" or something else? If so, what?
>>=20
>> As discussed off-list, I'd be happy to drop this phrase from *this* =
charter, in anticipation of it being worked out in discussions about the =
*next* one.
>=20
> Well, I think the phrase does need to be replaced
> by something else all right.
>=20
> I'm reluctant to omit mention of security entirely
> of course and do want to know what's gonna be done
> for authentication in a putative HTTP/2.0.
>=20
> Like I said, I'm pretty skeptical that any significant
> change to security properties will be achievable at
> that next charter stage.
>=20
>>> And then should it include adding some new options
>>> or MTI auth schemes as part of HTTP/2.0 or even looking
>>> at that? (I think it ought to include trying for that
>>> personally, even if there is a higher-than-usual risk
>>> of failure.)
>>=20
>>=20
>> Based on past experience, I think the risk is very high, and we don't =
need to pile any more risk onto this particular project.
>=20
> Based on past experience the milestones for this will be
> wildly optimistic and it'll really take five years so at
> the end of 2017 we'll be right where we are in terms of
> HTTP authentication for all of which time HTTP authentication
> will be the "next thing" to do. (Ok, I'm exaggerating a
> bit there.)
>=20
> I think both experiences are valid.
>=20
>> Also, most of the discussions about authentication and associated =
problems on the Web are *not* exclusive to HTTP or even protocol =
artefacts; they include concerns like UI and human factors, integration =
into hypertext, etc. As such, what we really need is a "whole of stack" =
focus on Web authentication; shoving it into this particular WG will, =
IMO, lead to a predictable failure.
>=20
> It is true that many sites don't use HTTP authentication
> for UI reasons. I don't think it follows that doing nothing
> is the right approach. (Well, one could argue to remove all
> user authentication from HTTP I guess - is that one of the
> proposals?)
>=20
> Cheers,
> S.
>=20
>=20

--
Mark Nottingham
http://www.mnot.net/





From msk@cloudmark.com  Tue Feb 21 14:56:43 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D90B11E80F7 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 14:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level: 
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOhFqkssDDIq for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 14:56:40 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 95A4911E810E for <ietf@ietf.org>; Tue, 21 Feb 2012 14:56:40 -0800 (PST)
Received: from malice.corp.cloudmark.com (172.22.10.71) by exch-htcas901.corp.cloudmark.com (172.22.10.73) with Microsoft SMTP Server (TLS) id 14.1.355.2; Tue, 21 Feb 2012 14:56:39 -0800
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Tue, 21 Feb 2012 14:56:39 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 21 Feb 2012 14:56:41 -0800
Subject: A nuance of interoperability reports
Thread-Topic: A nuance of interoperability reports
Thread-Index: Aczw7BNFnldVbPy+RuajKBqFOOPUDA==
Message-ID: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5833273385BB34F99288B3648C4F06F19C9A7DE5CEXCHC2corpclo_"
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:56:43 -0000

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

We like to see interoperability reports contain information about features =
of a protocol that are used vs. unused, so that if and when the protocol se=
eks advancement along the standards track, we can decide whether we want to=
 keep it in the revision.

Should we consider a protocol feature only used by abusive actors to be one=
 that deserves to be kept, or is only legitimate use worth considering?

-MSK

--_000_F5833273385BB34F99288B3648C4F06F19C9A7DE5CEXCHC2corpclo_
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=3DGenerator content=3D"Micros=
oft Word 12 (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:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>We like to see i=
nteroperability reports contain information about features of a protocol th=
at are used vs. unused, so that if and when the protocol seeks advancement =
along the standards track, we can decide whether we want to keep it in the =
revision.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Should we consider a protocol feature only used by abusive act=
ors to be one that deserves to be kept, or is only legitimate use worth con=
sidering?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>-MSK<o:p></o:p></p></div></body></html>=

--_000_F5833273385BB34F99288B3648C4F06F19C9A7DE5CEXCHC2corpclo_--

From stephen.farrell@cs.tcd.ie  Tue Feb 21 15:01:16 2012
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 B7CA911E80F7; Tue, 21 Feb 2012 15:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.199
X-Spam-Level: 
X-Spam-Status: No, score=-104.199 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJhH3QoMe9a6; Tue, 21 Feb 2012 15:01:12 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 5F97021F86A6; Tue, 21 Feb 2012 15:01:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id B7980171CFD; Tue, 21 Feb 2012 23:01:11 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1329865271; bh=P2YlDrrz9CJtEm XtuobT6gwuW2+4ghS47onP2WLcJYM=; b=2BV70WitC8KHL2SDXdi5UZMBrG24CP Rlfk3KnZCJ2+sgwcLapd4MCw/Vhe/3rFlQJFawRbY+viZs5c6g1HAbGxtJkb582b p9WP0wwJ1eU/8Aa+/vlpF/L3pP2HpridstmJHcx60WjlxMFb4ZQICdPWA6A6CnPS PUdIGhL2VoiHxmrvmZNIJu7EcTH60zd46m6TeqgjTZRh+TbQ16Q+CgTaU8SUbFyH ZDnRuULAwNyDRxCBGRJTTuhqLAdqtzvH3b288N3rcxW9gwqnnxoM6N4ANZ2nd2vN Z7DlPzwVAiz8NyKKab2u5dg0sGPrK5E+RznJmpd/Gf0CByYIxOkDcJdg==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id qnXlHpQlC7vI; Tue, 21 Feb 2012 23:01:11 +0000 (GMT)
Received: from [10.87.48.9] (unknown [86.42.23.218]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id DD26D171C28; Tue, 21 Feb 2012 23:01:10 +0000 (GMT)
Message-ID: <4F442235.1060209@cs.tcd.ie>
Date: Tue, 21 Feb 2012 23:01:09 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net> <4F442058.5070804@cs.tcd.ie> <8F042342-7C6A-4ED4-9A67-591644D3D5D6@mnot.net>
In-Reply-To: <8F042342-7C6A-4ED4-9A67-591644D3D5D6@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:01:16 -0000

On 02/21/2012 10:55 PM, Mark Nottingham wrote:
> Stephen,
>
> The approach we're advocating for this WG is to solicit well-formed proposals, select one and develop it.
>
> If there isn't one for HTTP authentication, how are you advocating we proceed?

I'm not thinking now in terms of advocating a specific
proposal for how to proceed.

Right now, I'm interested in what others reviewing the
draft charter think about this topic. That's the point
of having this discussion in the open like this.

(So maybe I should shut up for a while:-)

S

>
> Regards,
>
>
>
> On 22/02/2012, at 9:53 AM, Stephen Farrell wrote:
>
>>
>>
>> On 02/21/2012 10:40 PM, Mark Nottingham wrote:
>>>
>>> On 22/02/2012, at 9:19 AM, Stephen Farrell wrote:
>>>
>>
>>>> So as in my initial mail the 1st question here is, what
>>>> does "modern" mean in this draft charter? E.g. does it
>>>> mean "same as the current framework with different
>>>> bits" or something else? If so, what?
>>>
>>> As discussed off-list, I'd be happy to drop this phrase from *this* charter, in anticipation of it being worked out in discussions about the *next* one.
>>
>> Well, I think the phrase does need to be replaced
>> by something else all right.
>>
>> I'm reluctant to omit mention of security entirely
>> of course and do want to know what's gonna be done
>> for authentication in a putative HTTP/2.0.
>>
>> Like I said, I'm pretty skeptical that any significant
>> change to security properties will be achievable at
>> that next charter stage.
>>
>>>> And then should it include adding some new options
>>>> or MTI auth schemes as part of HTTP/2.0 or even looking
>>>> at that? (I think it ought to include trying for that
>>>> personally, even if there is a higher-than-usual risk
>>>> of failure.)
>>>
>>>
>>> Based on past experience, I think the risk is very high, and we don't need to pile any more risk onto this particular project.
>>
>> Based on past experience the milestones for this will be
>> wildly optimistic and it'll really take five years so at
>> the end of 2017 we'll be right where we are in terms of
>> HTTP authentication for all of which time HTTP authentication
>> will be the "next thing" to do. (Ok, I'm exaggerating a
>> bit there.)
>>
>> I think both experiences are valid.
>>
>>> Also, most of the discussions about authentication and associated problems on the Web are *not* exclusive to HTTP or even protocol artefacts; they include concerns like UI and human factors, integration into hypertext, etc. As such, what we really need is a "whole of stack" focus on Web authentication; shoving it into this particular WG will, IMO, lead to a predictable failure.
>>
>> It is true that many sites don't use HTTP authentication
>> for UI reasons. I don't think it follows that doing nothing
>> is the right approach. (Well, one could argue to remove all
>> user authentication from HTTP I guess - is that one of the
>> proposals?)
>>
>> Cheers,
>> S.
>>
>>
>
> --
> Mark Nottingham
> http://www.mnot.net/
>
>
>
>

From rbarnes@bbn.com  Tue Feb 21 17:45:00 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D8F21F8739 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 17:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.509
X-Spam-Level: 
X-Spam-Status: No, score=-106.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ty8CVE5MPe8B for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2012 17:44:59 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8738121F8737 for <ietf@ietf.org>; Tue, 21 Feb 2012 17:44:59 -0800 (PST)
Received: from [128.89.255.142] (port=54485) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1S01GI-000GRR-Uu; Tue, 21 Feb 2012 20:44:55 -0500
Subject: Re: A nuance of interoperability reports
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com>
Date: Tue, 21 Feb 2012 20:44:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E76AF74-6753-4572-B5C2-2E50AC167223@bbn.com>
References: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:45:00 -0000

Seems like it depends on your definitions of "abusive" and "legitimate". =
 Do you have an example? =20


On Feb 21, 2012, at 5:56 PM, Murray S. Kucherawy wrote:

> We like to see interoperability reports contain information about =
features of a protocol that are used vs. unused, so that if and when the =
protocol seeks advancement along the standards track, we can decide =
whether we want to keep it in the revision.
> =20
> Should we consider a protocol feature only used by abusive actors to =
be one that deserves to be kept, or is only legitimate use worth =
considering?
> =20
> -MSK
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From mcr@sandelman.ca  Tue Feb 21 19:14:36 2012
Return-Path: <mcr@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 6053521F891A; Tue, 21 Feb 2012 19:14:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.66
X-Spam-Level: 
X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ym03fUbI0ml; Tue, 21 Feb 2012 19:14:31 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C0E4321F8917; Tue, 21 Feb 2012 19:14:31 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 8343F3449A; Tue, 21 Feb 2012 22:12:07 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 494819827A; Tue, 21 Feb 2012 22:14:29 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 42C4398182; Tue, 21 Feb 2012 22:14:29 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-Reply-To: <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com> <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 21 Feb 2012 22:14:29 -0500
Message-ID: <10774.1329880469@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, Robert Collins <robertc@squid-cache.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:14:36 -0000

>>>>> "Barry" == Barry Leiba <barryleiba@computer.org> writes:
    Barry> OAuth is an authorization framework, not an authentication
    Barry> one.  Please be careful to make the distinction.

    Barry> What we're looking at here is the need for an HTTP
    Barry> authentication system that (for example) doesn't send
    Barry> reusable credentials, is less susceptible to spoofing
    Barry> attacks, and so on.

and is implemented in HTTP, not in terms of HTML forms, yet has all the 
flexibility of the HTML form method?

Or is that still out of scope?

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From dwm@xpasc.com  Tue Feb 21 23:04:46 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E033B21F85B8; Tue, 21 Feb 2012 23:04:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=-3.962, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkKEusQCrNdi; Tue, 21 Feb 2012 23:04:46 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDE521F84DC; Tue, 21 Feb 2012 23:04:46 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id E9F8F3F6DB; Wed, 22 Feb 2012 07:04:45 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q1M74j05023989; Tue, 21 Feb 2012 23:04:45 -0800
Date: Tue, 21 Feb 2012 23:04:45 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-Reply-To: <10774.1329880469@marajade.sandelman.ca>
Message-ID: <Pine.LNX.4.64.1202212302010.17875@egate.xpasc.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com> <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com> <10774.1329880469@marajade.sandelman.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a120AD3GD2zQ1vr-1L2304k
X-CLX-Spam: false
Cc: "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:04:47 -0000

On Tue, 21 Feb 2012, Michael Richardson wrote:

> 
> >>>>> "Barry" == Barry Leiba <barryleiba@computer.org> writes:
>     Barry> OAuth is an authorization framework, not an authentication
>     Barry> one.  Please be careful to make the distinction.
> 
>     Barry> What we're looking at here is the need for an HTTP
>     Barry> authentication system that (for example) doesn't send
>     Barry> reusable credentials, is less susceptible to spoofing
>     Barry> attacks, and so on.
> 
> and is implemented in HTTP, not in terms of HTML forms, yet has all the 
> flexibility of the HTML form method?

And includes the ability for the user to logoff / the server reset the 
login?

From julian.reschke@gmx.de  Wed Feb 22 00:39:39 2012
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 E1E1321F87EF for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 00:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.137
X-Spam-Level: 
X-Spam-Status: No, score=-104.137 tagged_above=-999 required=5 tests=[AWL=-1.538, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Puel6P9WyElZ for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 00:39:39 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id EDE8D21F87EB for <ietf@ietf.org>; Wed, 22 Feb 2012 00:39:38 -0800 (PST)
Received: (qmail invoked by alias); 22 Feb 2012 08:39:37 -0000
Received: from p5DCC3E21.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.62.33] by mail.gmx.net (mp030) with SMTP; 22 Feb 2012 09:39:37 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19katFm/M5khoLAE6cDp7TPTyLqEGfzaLGS440i5q wtBhnr2gyQGpfV
Message-ID: <4F44A9C5.8010404@gmx.de>
Date: Wed, 22 Feb 2012 09:39:33 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>,  "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com> <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com> <10774.1329880469@marajade.sandelman.ca> <Pine.LNX.4.64.1202212302010.17875@egate.xpasc.com>
In-Reply-To: <Pine.LNX.4.64.1202212302010.17875@egate.xpasc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 08:39:40 -0000

On 2012-02-22 08:04, David Morris wrote:
>
>
> On Tue, 21 Feb 2012, Michael Richardson wrote:
>
>>
>>>>>>> "Barry" == Barry Leiba<barryleiba@computer.org>  writes:
>>      Barry>  OAuth is an authorization framework, not an authentication
>>      Barry>  one.  Please be careful to make the distinction.
>>
>>      Barry>  What we're looking at here is the need for an HTTP
>>      Barry>  authentication system that (for example) doesn't send
>>      Barry>  reusable credentials, is less susceptible to spoofing
>>      Barry>  attacks, and so on.
>>
>> and is implemented in HTTP, not in terms of HTML forms, yet has all the
>> flexibility of the HTML form method?
>
> And includes the ability for the user to logoff / the server reset the
> login?

Is that a protocol problem or a user agent problem?

-- > <http://lists.w3.org/Archives/Public/www-archive/2012Jan/0023.html>

Best regards, Julian

From hsantos@isdg.net  Wed Feb 22 02:06:50 2012
Return-Path: <hsantos@isdg.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 0EF9B21F8877 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 02:06:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[AWL=0.456,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szt72r4yjSPr for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 02:06:49 -0800 (PST)
Received: from news.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 56BFC21F8883 for <ietf@ietf.org>; Wed, 22 Feb 2012 02:06:48 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1604; t=1329905197; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=tKvsx2sXOQlEaozOcslB6bfOwuE=; b=MTSH0wFMWdJazl9lxcS9 tDbfXDpHMyKKStEwCCZSF8QLGENPSI1eoCUjDjMuBrYCGr3mhp4WNRsJYtuOW44G nHGPacCK2zczjn3vE5pIIz8t8InNq1gHPml3tapMlWEHZE2LJ3CUdd/dX5C9aPt5 Kq6orawfF8GCCP6orgFu/Rg=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 22 Feb 2012 05:06:37 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3107041995.88546.4320; Wed, 22 Feb 2012 05:06:36 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1604; t=1329904955; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=U3FYWoD 7MtZNvRaKddVkG3ZAsxm3jbTY/12cxEM8iXI=; b=AgLbKy+oJYtQEoxNSZx4z2n LnIgb/a6BR9pL/0D1Rrrdja/8u2FN6tSvlz5alX2/BjJnhSQsD4o54e7UAKI2fo+ DXzBJFxUR4WCaGzpD4XSfbDxxoX4OrHhljrIIdhPXI+zsGqGU5Qg0IeuZKS1RDNv YrBXNtOU003XQOQysrYQ=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 22 Feb 2012 05:02:35 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3705977814.18853.7572; Wed, 22 Feb 2012 05:02:34 -0500
Message-ID: <4F44BE37.2020904@isdg.net>
Date: Wed, 22 Feb 2012 05:06:47 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de>	<4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de>	<CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com>	<CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>	<10774.1329880469@marajade.sandelman.ca>	<Pine.LNX.4.64.1202212302010.17875@egate.xpasc.com> <4F44A9C5.8010404@gmx.de>
In-Reply-To: <4F44A9C5.8010404@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:06:50 -0000

Julian Reschke wrote:

>> And includes the ability for the user to logoff / the server reset the
>> login?
> 
> Is that a protocol problem or a user agent problem?
> 
> -- > <http://lists.w3.org/Archives/Public/www-archive/2012Jan/0023.html>
> 

Possibly both.

First, its a non-issue with cookie based authentication methods 
(server side fancy login forms) but it is by using a cookie condition 
can you emulate a "Logoff" concept with HTTP BASIC/DIGEST AUTH due to 
the browser current persistent nature to continue reissing 
BASIC/DIGEST authenticated credentials until a 403 is issued.

The cookie i.e. "SESSION-OVER" is required to trap/trigger/recognized 
when a 403 condition should be used upon subsequent requests.  That 
will cause the Browser to forget (either full or partially the current 
credentials). Depending on the browser, it could mean a lost of 
reusing them without typing them until the browser is completely closed.

But without a cookie, there is no logoff button concept with HTTP 
AUTH.   So the question is does HTTP AUTH requires cookies to work. 
Since it does not, if a clearing of the credentials perhaps with a new 
40x or redefinition of the existing 40x, is desired, it also has to be 
based on not requiring a cookie.

In regards to the generic problem statement Barry stated, sounds to me 
that this calls for a persistent IP session level management concept. 
  A related question is to decide who is going to be asking for the 
initial credentials, the browser or a server-side login form concept?

-- 
Hector Santos, CTO
http://www.santronics.com




From hsantos@isdg.net  Wed Feb 22 02:48:45 2012
Return-Path: <hsantos@isdg.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 1BF8A21F8973 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 02:48:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.450,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikNGZHWQ7At7 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 02:48:43 -0800 (PST)
Received: from groups.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5289621F8969 for <ietf@ietf.org>; Wed, 22 Feb 2012 02:48:43 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1535; t=1329907718; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=xRgi2gAP7JDct2mJPBoqtvJiCdI=; b=Nn38yTt7KXSFxel8KppK GEhhDlqq5DeOvI8Lj6v7Ra7DQVBrRvKYz2a7qdsJ5rCieaTZZtW/OSDvhPRfWH0o 1MVuTv6j0qRjZhwlnSRRasbwC+asv7JgiCIs10AAJ7lz7q3sKHZqV360BEi1zKLS RL1zDHZl5j4HtRigtMqNbNQ=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 22 Feb 2012 05:48:38 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3109562409.88546.228; Wed, 22 Feb 2012 05:48:36 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1535; t=1329907477; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=u2H8+xw odSApSQUlVPoiyRnmL03myQ+5p9VdrJ0mzWw=; b=OgPKBRoHrVp08yX2eFm4jCv k33/kgY42lwCeABj54iUkAQN3RpqZkP08ZLzdEiN4aiDRan78YZT8MCN+XJFja+F roc+SkVeafUaDKQQtte9wq7DFSpu7iyL8PZLbTy6wjWwYWsTcIicVMh9DbAkNHXo YXvWJdKODEMDm+St4ONM=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 22 Feb 2012 05:44:37 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3708500626.18858.7368; Wed, 22 Feb 2012 05:44:37 -0500
Message-ID: <4F44C813.6030702@isdg.net>
Date: Wed, 22 Feb 2012 05:48:51 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de>	<4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de>	<CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com> <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
In-Reply-To: <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, Robert Collins <robertc@squid-cache.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:48:45 -0000

Barry Leiba wrote:
>> browser id, openid, and oauth are all authentication frameworks built
>> on top of HTTP
>>
> 
> OAuth is an authorization framework, not an authentication one.  Please be
> careful to make the distinction.
> 
> What we're looking at here is the need for an HTTP authentication system
> that (for example) doesn't send reusable credentials, is less susceptible
> to spoofing attacks, and so on.

Hi Barry, maybe I should review the drafts (or not), but if its hasn't
been considered, this sounds like the only way possible is with a
persistent IP connection session management concept.

I can relate it based on our PCI framework for the web server and much
of the modeling was based on our existing non-http multi-device
hosting servers already 100% based on a persistent connection IP or
line, channel.  Definitely works in areas where only one browser or
machine is allowed.

I was looking forwarding to further exploring WebSockets to possible
be part of (revitaling) this solution as well, since it work nicely
with the persistent IP concept with the backend.

On a related note, some web sites do this and I first saw it with
facebook where it knows where I am logging in from. In a recent philly
trip, I tried to log on and interestingly got a new login form where
it indicated I was at a different location. I had to verify who I was
again, if I recall via my email/login account at gmail.com.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com



From msk@cloudmark.com  Wed Feb 22 06:55:26 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3D4121F86DA for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 06:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYtc83HJEjpP for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 06:55:25 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id C134E21F86D8 for <ietf@ietf.org>; Wed, 22 Feb 2012 06:55:07 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Wed, 22 Feb 2012 06:55:07 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: A nuance of interoperability reports
Thread-Topic: A nuance of interoperability reports
Thread-Index: Aczw7BNFnldVbPy+RuajKBqFOOPUDAAWo3YAAArBo4A=
Date: Wed, 22 Feb 2012 14:55:06 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392803E486@exch-mbx901.corp.cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com> <3E76AF74-6753-4572-B5C2-2E50AC167223@bbn.com>
In-Reply-To: <3E76AF74-6753-4572-B5C2-2E50AC167223@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:55:26 -0000

> -----Original Message-----
> From: Richard Barnes [mailto:rbarnes@bbn.com]
> Sent: Tuesday, February 21, 2012 5:45 PM
> To: Murray S. Kucherawy
> Cc: ietf@ietf.org
> Subject: Re: A nuance of interoperability reports
>=20
> Seems like it depends on your definitions of "abusive" and
> "legitimate".  Do you have an example?

For a contrived example, let's say a registered HTTP header field that's on=
ly ever found to be present in web pages used by bad actors, but lots of th=
em.  Then HTTPbis comes up for standards track advancement and they're clea=
ning out the cruft.  Would marking that field as deprecated or removing it =
completely be justified?

-MSK

From randy@psg.com  Wed Feb 22 07:02:16 2012
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 8414621F87E5 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 07:02:16 -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=[AWL=0.109,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A4mdHrpvdEep for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 07:02:14 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 7D14B21F87E0 for <ietf@ietf.org>; Wed, 22 Feb 2012 07:02:10 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1S0Dho-0001H5-0I; Wed, 22 Feb 2012 15:02:09 +0000
Date: Wed, 22 Feb 2012 20:32:05 +0530
Message-ID: <m2obsqap3m.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: A nuance of interoperability reports
In-Reply-To: <9452079D1A51524AA5749AD23E00392803E486@exch-mbx901.corp.cloudmark.com>
References: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com> <3E76AF74-6753-4572-B5C2-2E50AC167223@bbn.com> <9452079D1A51524AA5749AD23E00392803E486@exch-mbx901.corp.cloudmark.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:02:16 -0000

i think what richard was trying to hint is that the same tool can be
used for both good and bad.  and we can't predict that, just because it
has been used for bad yesteday, it will not be used for good in the rosy
future.

randy

From wjhns1@hardakers.net  Wed Feb 22 07:03:42 2012
Return-Path: <wjhns1@hardakers.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 2794021F87E5; Wed, 22 Feb 2012 07:03: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=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODdD9JrcNB4W; Wed, 22 Feb 2012 07:03:41 -0800 (PST)
Received: from mail.hardakers.net (unknown [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id A89D821F87E1; Wed, 22 Feb 2012 07:03:41 -0800 (PST)
Received: from localhost (unknown [IPv6:2001:470:1f00:187:224:7eff:fe6b:2b3e]) by mail.hardakers.net (Postfix) with ESMTPSA id 63D36913; Wed, 22 Feb 2012 07:03:38 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net> <4F442058.5070804@cs.tcd.ie> <8F042342-7C6A-4ED4-9A67-591644D3D5D6@mnot.net> <4F442235.1060209@cs.tcd.ie>
Date: Wed, 22 Feb 2012 07:03:37 -0800
In-Reply-To: <4F442235.1060209@cs.tcd.ie> (Stephen Farrell's message of "Tue,  21 Feb 2012 23:01:09 +0000")
Message-ID: <0llinuoqpi.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Julian Reschke <julian.reschke@gmx.de>, Mark Nottingham <mnot@mnot.net>, IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:03:42 -0000

>>>>> On Tue, 21 Feb 2012 23:01:09 +0000, Stephen Farrell <stephen.farrell@cs.tcd.ie> said:

>> The approach we're advocating for this WG is to solicit well-formed
>> proposals, select one and develop it.
>> 
>> If there isn't one for HTTP authentication, how are you advocating we proceed?

SF> Right now, I'm interested in what others reviewing the
SF> draft charter think about this topic. That's the point
SF> of having this discussion in the open like this.

IMHO, if you want security to be well integrated into the next version
of the protocol, then it should be thought about up front.  The IETF
doesn't have a great track record of adding security later to protocols
in a way that is seamless and integrated.

And if you don't put thinking about security in the "solicitation
request" charter version, then you may well end up in the state that
Mark is worried about: none of the answers have security considered.

I think the charter should definitely have a requirement indicating that
proposals must explain how security techniques would fit into it in the
future, even if they don't fully define the solution/extension itself.
-- 
Wes Hardaker
SPARTA, Inc.

From scott@kitterman.com  Wed Feb 22 07:13:05 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2734021F87C7 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 07:13:05 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nbPdxk47E67C for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 07:12:59 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id D52E021F87FB for <ietf@ietf.org>; Wed, 22 Feb 2012 07:12:58 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 28EAA20E40CC; Wed, 22 Feb 2012 10:12:57 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1329923577; bh=bewwgjY2ciarT1qkW+O/5/CuFYRQy1I+7/6olwEYXEs=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=LBiAxjDpHbrPNWGFKsG+kad1ckMsIHxsG6ZwA+Y/pbT1oUiCwFXqL7Nzy+eIGaEtk TlftvWWZOyh5b5d2b7g937gtniDgI78pQoNM17qwVjyvnYcVOQ/XXNkJ9QOuMTLm39 3HHzMLifibnQNkJtGGyCyTS0ZeHVhvFsWANU5aKw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 0B8BD20E4064;  Wed, 22 Feb 2012 10:12:56 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: A nuance of interoperability reports
Date: Wed, 22 Feb 2012 10:12:56 -0500
Message-ID: <3748844.HmnPoMxxk4@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <m2obsqap3m.wl%randy@psg.com>
References: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com> <9452079D1A51524AA5749AD23E00392803E486@exch-mbx901.corp.cloudmark.com> <m2obsqap3m.wl%randy@psg.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:13:05 -0000

On Wednesday, February 22, 2012 08:32:05 PM Randy Bush wrote:
> i think what richard was trying to hint is that the same tool can be
> used for both good and bad.  and we can't predict that, just because it
> has been used for bad yesteday, it will not be used for good in the rosy
> future.

Yes, but the same argument can be made about unused features.  Just because a 
feature wasn't used so far, we can't predict the future.  It may be useful.

If there's not non-abusive deployment, then it seems reasonable to treat that 
as non-deployment of the feature.

Scott K

From dwm@xpasc.com  Wed Feb 22 07:25:19 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8742521F882B; Wed, 22 Feb 2012 07:25:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.58
X-Spam-Level: 
X-Spam-Status: No, score=-5.58 tagged_above=-999 required=5 tests=[AWL=-2.981,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-Nsjwd5ASgT; Wed, 22 Feb 2012 07:25:18 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id C1B6F21F87A9; Wed, 22 Feb 2012 07:25:17 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 03CFB3F7B4; Wed, 22 Feb 2012 15:25:17 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q1MFPGN4028428; Wed, 22 Feb 2012 07:25:16 -0800
Date: Wed, 22 Feb 2012 07:25:16 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: "'HTTP Working Group'" <ietf-http-wg@w3.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-Reply-To: <4F44A9C5.8010404@gmx.de>
Message-ID: <Pine.LNX.4.64.1202220713520.28289@egate.xpasc.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com> <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com> <10774.1329880469@marajade.sandelman.ca> <Pine.LNX.4.64.1202212302010.17875@egate.xpasc.com> <4F44A9C5.8010404@gmx.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a110AD3GD2zQ1vr-1M0725H
X-CLX-Spam: false
Cc: IETF-Discussion <ietf@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IETF-Discussion <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, 'HTTP Working Group' <ietf-http-wg@w3.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:25:19 -0000

On Wed, 22 Feb 2012, Julian Reschke wrote:

> On 2012-02-22 08:04, David Morris wrote:
> > 
> > 
> > On Tue, 21 Feb 2012, Michael Richardson wrote:
> > 
> > > 
> > > > > > > > "Barry" == Barry Leiba<barryleiba@computer.org>  writes:
> > >      Barry>  OAuth is an authorization framework, not an authentication
> > >      Barry>  one.  Please be careful to make the distinction.
> > > 
> > >      Barry>  What we're looking at here is the need for an HTTP
> > >      Barry>  authentication system that (for example) doesn't send
> > >      Barry>  reusable credentials, is less susceptible to spoofing
> > >      Barry>  attacks, and so on.
> > > 
> > > and is implemented in HTTP, not in terms of HTML forms, yet has all the
> > > flexibility of the HTML form method?
> > 
> > And includes the ability for the user to logoff / the server reset the
> > login?
> 
> Is that a protocol problem or a user agent problem?
> 
> -- > <http://lists.w3.org/Archives/Public/www-archive/2012Jan/0023.html>

I consider it a protocol issue in the same way that authentication is a
protocol issue.

The question I was responding to was one of adoption by application
developers and is in addition to the lack of application control over
the current authenticate dialog. A "use case" if you will.

The JS approach isn't really adequate because not all user agents
execute the payload. Second 1/2 of the "use case."

I'm not advocating that this be solved as part of the Recharter/2.0
activity, I'm neutral on the where question.

From randy@psg.com  Wed Feb 22 07:49:32 2012
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 1E4BA21F86CF for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 07:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.491
X-Spam-Level: 
X-Spam-Status: No, score=-2.491 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KIp54szNd4BV for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 07:49:31 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 6818021F86BA for <ietf@ietf.org>; Wed, 22 Feb 2012 07:49:31 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <randy@psg.com>) id 1S0ERd-0001Q2-SU; Wed, 22 Feb 2012 15:49:30 +0000
Date: Wed, 22 Feb 2012 21:19:26 +0530
Message-ID: <m2mx8aamwp.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: A nuance of interoperability reports
In-Reply-To: <3748844.HmnPoMxxk4@scott-latitude-e6320>
References: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com> <9452079D1A51524AA5749AD23E00392803E486@exch-mbx901.corp.cloudmark.com> <m2obsqap3m.wl%randy@psg.com> <3748844.HmnPoMxxk4@scott-latitude-e6320>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:49:32 -0000

>> i think what richard was trying to hint is that the same tool can be
>> used for both good and bad.  and we can't predict that, just because
>> it has been used for bad yesteday, it will not be used for good in
>> the rosy future.
> 
> Yes, but the same argument can be made about unused features.  Just
> because a feature wasn't used so far, we can't predict the future.  It
> may be useful.
> 
> If there's not non-abusive deployment, then it seems reasonable to
> treat that as non-deployment of the feature.

i thought that an interop report is about what has been implemented, not
what has been used.

randy

From adrien@qbik.com  Tue Feb 21 14:38:23 2012
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 00E3111E80CF; Tue, 21 Feb 2012 14:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.54
X-Spam-Level: 
X-Spam-Status: No, score=-3.54 tagged_above=-999 required=5 tests=[AWL=-0.941,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iy7oXmqbkpZs; Tue, 21 Feb 2012 14:38:22 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id D063D11E807F; Tue, 21 Feb 2012 14:38:21 -0800 (PST)
Received: From sago.qbik.com (unverified [192.168.0.3]) by SMTP Server [192.168.0.1] (WinGate SMTP Receiver v7.1.0 (Build 3385)) with SMTP id <0018876218@smtp.qbik.com>; Wed, 22 Feb 2012 11:38:12 +1300
Received: From [192.168.0.10] (unverified [192.168.0.10]) by SMTP Server [192.168.0.3] (WinGate SMTP Receiver v7.0.8 (Build 3364)) with SMTP id <0010063297@sago.qbik.com>; Wed, 22 Feb 2012 11:38:05 +1300
Message-ID: <4F441CCD.4020907@qbik.com>
Date: Wed, 22 Feb 2012 11:38:05 +1300
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120216 Thunderbird/11.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de>
In-Reply-To: <4F43E75C.2010309@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Feb 2012 08:52:32 -0800
Cc: mnot@mnot.net, IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:38:23 -0000

Hi Julian,

On 02/21/2012 06:50 PM, Julian Reschke wrote:
> On 2012-02-21 19:37, Stephen Farrell wrote:
>> ...
>>> I believe this should be orthogonal to HTTP/2.0. Is there a specific
>>> thing that makes it impossible to use the existing authentication
>>> framework?
>>
>> Who knows? We don't have a protocol on the table yet. I
>> would imagine that some level of backwards compatibility
>> would be a requirement of course, or at least an issue to
>> be considered.
>>
>> But the existing HTTP client authentication is also not
>> necessarily very useful, and there have been a number of
>> efforts to improve on that, none of which seem to have
>> gotten sufficient traction to get widely deployed/used.
>> Maybe HTTP/2.0 is a good time to try fix that.
>
> Well, we have an existing authentication framework. It would be
> interesting to find out what's missing from it.

session support with login and logout would be good.  I know it's a can 
of worms, with some serious security implications.

But this is why no websites use HTTP auth to speak of, which makes it 
difficult to do integrated authentication.

Adrien

From hsantos@santronics.com  Wed Feb 22 02:44:49 2012
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAC4721F8940 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 02:44:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level: 
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[AWL=0.592,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAhsP6mDRL0f for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 02:44:48 -0800 (PST)
Received: from groups.winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B2A9621F8925 for <ietf@ietf.org>; Wed, 22 Feb 2012 02:44:42 -0800 (PST)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1543; t=1329907471; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=B5AoOUL TtRiwDO0HLpyJdOTNN+E=; b=c/utdXySZzND2bNkSs+4MfA4exPD8wg4cMqPSk3 59eoJx3F/pATvbzr/sr007n3xF+0OhhZ4ulTYRq3HqRviAkU3XVB8eDOg3daKz/x WfRZmbsZmgJjrSrS7qD7ZBjH429wrK7H7oIGPOgncvY2kUYNo6E1JTh7wA+GeCHb TvsI=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Wed, 22 Feb 2012 05:44:31 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3109316396.88546.1664; Wed, 22 Feb 2012 05:44:30 -0500
Message-ID: <4F44C721.5080204@santronics.com>
Date: Wed, 22 Feb 2012 05:44:49 -0500
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de>	<4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de>	<CAJ3HoZ3JHbcwhYEnyYbKTp+6oY1ZjsLxM6pFQEApnFMKOAhGzA@mail.gmail.com> <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
In-Reply-To: <CAC4RtVB==09BD79S2wesGuZtbsNy3NCwQzKvHUTKNZPG0Br1Gg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Feb 2012 08:52:33 -0800
Cc: "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, Robert Collins <robertc@squid-cache.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:44:49 -0000

Barry Leiba wrote:
>> browser id, openid, and oauth are all authentication frameworks built
>> on top of HTTP
>>
> 
> OAuth is an authorization framework, not an authentication one.  Please be
> careful to make the distinction.
> 
> What we're looking at here is the need for an HTTP authentication system
> that (for example) doesn't send reusable credentials, is less susceptible
> to spoofing attacks, and so on.

Hi Barry, maybe I should review the drafts (or not), but if its hasn't 
been considered, this sounds like the only way possible is with a 
persistent IP connection session management concept.

I can relate it based on our PCI framework for the web server and much 
of the modeling was based on our existing non-http multi-device 
hosting servers already 100% based on a persistent connection IP or 
line, channel.  Definitely works in areas where only one browser or 
machine is allowed.

I was looking forwarding to further exploring WebSockets to possible 
be part of (revitaling) this solution as well, since it work nicely 
with the persistent IP concept with the backend.

On a related note, some web sites do this and I first saw it with 
facebook where it knows where I am logging in from. In a recent philly 
trip, I tried to log on and interestingly got a new login form where 
it indicated I was at a different location. I had to verify who I was 
again, if I recall via my email/login account at gmail.com.

-- 
Sincerely

Hector Santos
http://www.santronics.com
jabber: hector@jabber.isdg.net



From ietfdbh@comcast.net  Wed Feb 22 05:05:09 2012
Return-Path: <ietfdbh@comcast.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 79CCB21F87AD for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 05:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.226
X-Spam-Level: 
X-Spam-Status: No, score=-102.226 tagged_above=-999 required=5 tests=[AWL=0.373, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUQPBM0Jf+gT for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 05:05:01 -0800 (PST)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by ietfa.amsl.com (Postfix) with ESMTP id 3E19B21F8680 for <ietf@ietf.org>; Wed, 22 Feb 2012 05:05:01 -0800 (PST)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta14.westchester.pa.mail.comcast.net with comcast id d0Sz1i0041YDfWL5E151af; Wed, 22 Feb 2012 13:05:01 +0000
Received: from [192.168.1.33] ([71.233.85.150]) by omta20.westchester.pa.mail.comcast.net with comcast id d14x1i0033Ecudz3g14zuA; Wed, 22 Feb 2012 13:05:01 +0000
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Wed, 22 Feb 2012 08:04:54 -0500
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: David Harrington <ietfdbh@comcast.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Mark Nottingham <mnot@mnot.net>
Message-ID: <CB6A507F.13D92%ietfdbh@comcast.net>
Thread-Topic: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-Reply-To: <4F442235.1060209@cs.tcd.ie>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Feb 2012 08:52:33 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:05:09 -0000

Hi,

Having been involved in adding security after-the-fact to SNMP, and to
Syslog, and adding authorization after-the-fact to netconf, I know it is
extremely difficult to add security "later".

I strongly believe that if http is going to be redesigned enough to
justify a 2.0 label, then security should be part of its design from the
start. Therefore I think that security should be addressed as part of the
http 2.0 effort, not after the fact.

I can understand the concerns about doing both at the same time increasing
the risk to both, and that serializing the work might reduce the risk. So
I suggest you COULD design the web security standard first, and then
design HTTP 2.0 to take the updated web security standards into
consideration. Web security will be easier if it doesn't need to somehow
fit into an HTTP 2.0 that didn't consider a viable security approach
up-front.

--
David Harrington
Director, Transport Area
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 2/21/12 6:01 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>
>On 02/21/2012 10:55 PM, Mark Nottingham wrote:
>> Stephen,
>>
>> The approach we're advocating for this WG is to solicit well-formed
>>proposals, select one and develop it.
>>
>> If there isn't one for HTTP authentication, how are you advocating we
>>proceed?
>
>I'm not thinking now in terms of advocating a specific
>proposal for how to proceed.
>
>Right now, I'm interested in what others reviewing the
>draft charter think about this topic. That's the point
>of having this discussion in the open like this.
>
>(So maybe I should shut up for a while:-)
>
>S
>
>>
>> Regards,
>>
>>
>>
>> On 22/02/2012, at 9:53 AM, Stephen Farrell wrote:
>>
>>>
>>>
>>> On 02/21/2012 10:40 PM, Mark Nottingham wrote:
>>>>
>>>> On 22/02/2012, at 9:19 AM, Stephen Farrell wrote:
>>>>
>>>
>>>>> So as in my initial mail the 1st question here is, what
>>>>> does "modern" mean in this draft charter? E.g. does it
>>>>> mean "same as the current framework with different
>>>>> bits" or something else? If so, what?
>>>>
>>>> As discussed off-list, I'd be happy to drop this phrase from *this*
>>>>charter, in anticipation of it being worked out in discussions about
>>>>the *next* one.
>>>
>>> Well, I think the phrase does need to be replaced
>>> by something else all right.
>>>
>>> I'm reluctant to omit mention of security entirely
>>> of course and do want to know what's gonna be done
>>> for authentication in a putative HTTP/2.0.
>>>
>>> Like I said, I'm pretty skeptical that any significant
>>> change to security properties will be achievable at
>>> that next charter stage.
>>>
>>>>> And then should it include adding some new options
>>>>> or MTI auth schemes as part of HTTP/2.0 or even looking
>>>>> at that? (I think it ought to include trying for that
>>>>> personally, even if there is a higher-than-usual risk
>>>>> of failure.)
>>>>
>>>>
>>>> Based on past experience, I think the risk is very high, and we don't
>>>>need to pile any more risk onto this particular project.
>>>
>>> Based on past experience the milestones for this will be
>>> wildly optimistic and it'll really take five years so at
>>> the end of 2017 we'll be right where we are in terms of
>>> HTTP authentication for all of which time HTTP authentication
>>> will be the "next thing" to do. (Ok, I'm exaggerating a
>>> bit there.)
>>>
>>> I think both experiences are valid.
>>>
>>>> Also, most of the discussions about authentication and associated
>>>>problems on the Web are *not* exclusive to HTTP or even protocol
>>>>artefacts; they include concerns like UI and human factors,
>>>>integration into hypertext, etc. As such, what we really need is a
>>>>"whole of stack" focus on Web authentication; shoving it into this
>>>>particular WG will, IMO, lead to a predictable failure.
>>>
>>> It is true that many sites don't use HTTP authentication
>>> for UI reasons. I don't think it follows that doing nothing
>>> is the right approach. (Well, one could argue to remove all
>>> user authentication from HTTP I guess - is that one of the
>>> proposals?)
>>>
>>> Cheers,
>>> S.
>>>
>>>
>>
>> --
>> Mark Nottingham
>> http://www.mnot.net/
>>
>>
>>
>>



From atlunde@panix.com  Wed Feb 22 08:32:28 2012
Return-Path: <atlunde@panix.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0C621F881A; Wed, 22 Feb 2012 08:32:28 -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=-2.599, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EE8djfgoMuLx; Wed, 22 Feb 2012 08:32:28 -0800 (PST)
Received: from mailbackend.panix.com (mailbackend2.panix.com [166.84.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id 053EC21F8802; Wed, 22 Feb 2012 08:32:27 -0800 (PST)
Received: from [129.105.233.63] (socrates.tss.northwestern.edu [129.105.233.63]) by mailbackend.panix.com (Postfix) with ESMTP id 9C4DF2EA4A; Wed, 22 Feb 2012 11:32:26 -0500 (EST)
Message-ID: <4F451893.8000205@panix.com>
Date: Wed, 22 Feb 2012 10:32:19 -0600
From: Albert Lunde <atlunde@panix.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf-http-wg@w3.org
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net> <4F442058.5070804@cs.tcd.ie> <8F042342-7C6A-4ED4-9A67-591644D3D5D6@mnot.net> <4F442235.1060209@cs.tcd.ie>
In-Reply-To: <4F442235.1060209@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Feb 2012 08:52:34 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:33:54 -0000

It seems like what would be useful would be a way of bringing in trusted 
third-parties into authentication that didn't look like a 
man-in-the-middle attack, and didn't rely on JavaScript.

SAML "federation" (e.g. Shibboleth) is layered on top of HTML+HTTP,
but it, and most of the other existing WebSSO systems, rely on 
JavaScript tricks somewhere in their process.

Trusted third parties are presently more the domain of certificates or 
Kerberos, than HTTP as such.

SASL is another framework for layering authentication onto protocols, 
that's been worked on considerably. But I don't know if it can meet the 
needs of the browser-based market now being served by 
forms+cookies+JavaScript.

Finding a single authentication/authorization framework that serves the 
needs of both browser and non-broswer clients is hard.

Scott Cantor has written a lot about why global logout for Shibboleth is 
hard to implement. Part of that may rest on the underlying legacy 
mechanisms they are using, but it's also a communication problem.

Having a local logout that really meant "stop sending cookies and 
credentials for realm X to these servers" and/or authentication realms 
that spanned servers might help, I don't know.

-- 
     Albert Lunde  albert-lunde@northwestern.edu
                   atlunde@panix.com  (address for personal mail)

From rja.lists@gmail.com  Wed Feb 22 09:01:52 2012
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 A1FCD21F86BA for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 09:01:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.606
X-Spam-Level: 
X-Spam-Status: No, score=-3.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NSew3lDAiong for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 09:01:52 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7895B21F86A8 for <ietf@ietf.org>; Wed, 22 Feb 2012 09:01:50 -0800 (PST)
Received: by qan41 with SMTP id 41so416632qan.10 for <ietf@ietf.org>; Wed, 22 Feb 2012 09:01:50 -0800 (PST)
Received-SPF: pass (google.com: domain of rja.lists@gmail.com designates 10.229.136.16 as permitted sender) client-ip=10.229.136.16; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of rja.lists@gmail.com designates 10.229.136.16 as permitted sender) smtp.mail=rja.lists@gmail.com; dkim=pass header.i=rja.lists@gmail.com
Received: from mr.google.com ([10.229.136.16]) by 10.229.136.16 with SMTP id p16mr23777776qct.24.1329930110057 (num_hops = 1); Wed, 22 Feb 2012 09:01:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=Q8mmS/0ye+bzMzZOl8XzzZpF7b58p/M+/nbjIq1AYKE=; b=JaE5Isqy/pQqnUpg6VP4UDXtt+7N3Ig8KzSSPcFk/oQrL+3KgoHByirsriidDYyY8X DHv9CfX7uziRn9v1hIB9TDzTYgoeOMvLHgpVxzqlQjpW8mN+XQqa3IZpebj78ZZZ3QSs ZbnZ3Z44lDvagxc0WTu3mNPCqrfDMbjOC+sys=
Received: by 10.229.136.16 with SMTP id p16mr20061808qct.24.1329930109961; Wed, 22 Feb 2012 09:01:49 -0800 (PST)
Received: from [10.30.20.12] (pool-96-225-134-175.nrflva.fios.verizon.net. [96.225.134.175]) by mx.google.com with ESMTPS id dm8sm67354235qab.18.2012.02.22.09.01.48 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Feb 2012 09:01:48 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Date: Wed, 22 Feb 2012 12:01:47 -0500
Message-Id: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:01:52 -0000

Earlier, Barry Leiba wrote, in part:
> What we're looking at here is the need for an HTTP authentication
> system that (for example) doesn't send reusable credentials,
> is less susceptible to spoofing attacks, and so on.

+1

More generally, I support the concerns raised by Stephen Farrell, 
Wes Hardaker, and others that if *any* work is to be done on HTTP, 
then improving the authentication/confidentiality properties 
ought to be a mandatory part of that work.

The IETF has LOTS of experience that if strong(er) security
mechanisms are not *required* in a WG Charter *very explicitly*,
then that work will not happen at all.

Security that works well and is practical to implement 
needs to be designed-in, not bolted-on later.

Separately, I would also like to see the known-weak cryptographic
algorithms/modes (i.e. published literature indicates that
an algorithm, a mode, or both is weak) that are included with HTTP
(as separate from being part of TLS) formally get deprecated as part 
of any HTTPbis work.   For example, the WG ought to consider
deprecating the use of the MD5, UNIXsum, and UNIXcksum algorithms
within HTTP Digests [RFC-2617] [RFC-3230].

Yours,

Ran




From paul.hoffman@vpnc.org  Wed Feb 22 09:31:54 2012
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 266FF21F87C9; Wed, 22 Feb 2012 09:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AsLu1RdrRhxZ; Wed, 22 Feb 2012 09:31:53 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id B5D3D21F8714; Wed, 22 Feb 2012 09:31:53 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1MHVphA074521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Feb 2012 10:31:51 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CB6A507F.13D92%ietfdbh@comcast.net>
Date: Wed, 22 Feb 2012 09:31:50 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org>
References: <CB6A507F.13D92%ietfdbh@comcast.net>
To: The IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:31:54 -0000

The earnest calls for better authentication on this thread appear to =
ignore the fact that the very things that are being requested were put =
out of scope for the websec WG in their charter. I hope that no one =
things that a WG in the Applications Area will be better equipped to =
come up with a better authentication mechanism than one in the Security =
Area.

Asking the HTTPheads to guess what the securityheads might want is not a =
good way to design HTTP 2.0.

Proposal: leave the httpbis WG charter as-is and re-charter the websec =
WG to consider what is needed in the HTTP authentication model. Later, =
recharter the websec WG to, you know, actually do the security work for =
authentication.

--Paul Hoffman=

From stpeter@stpeter.im  Wed Feb 22 09:39:24 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41D8221F8609; Wed, 22 Feb 2012 09:39:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PaLrcKMtyumK; Wed, 22 Feb 2012 09:39:20 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 61A6921F85DD; Wed, 22 Feb 2012 09:39:16 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B11EA40058; Wed, 22 Feb 2012 10:50:30 -0700 (MST)
Message-ID: <4F452842.3050905@stpeter.im>
Date: Wed, 22 Feb 2012 10:39:14 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org>
In-Reply-To: <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf-http-wg@w3.org, The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:39:24 -0000

On 2/22/12 10:31 AM, Paul Hoffman wrote:
> The earnest calls for better authentication on this thread appear to
> ignore the fact that the very things that are being requested were
> put out of scope for the websec WG in their charter. I hope that no
> one things that a WG in the Applications Area will be better equipped
> to come up with a better authentication mechanism than one in the
> Security Area.

The WebSec WG is in the Applications Area.

> Asking the HTTPheads to guess what the securityheads might want is
> not a good way to design HTTP 2.0.

Probably not.

> Proposal: leave the httpbis WG charter as-is and re-charter the
> websec WG to consider what is needed in the HTTP authentication
> model. Later, recharter the websec WG to, you know, actually do the
> security work for authentication.

Or charter a separate WG to focus on HTTP authentication. (You might
recall that the BoF leading to formation of the WebSec WG was entitled
HASMAT = "HTTP Application Security Minus Authentication and Transport"
or somesuch.)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From paul.hoffman@vpnc.org  Wed Feb 22 09:52:40 2012
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 F22EA21F8847; Wed, 22 Feb 2012 09:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eUeNIGQkaWDx; Wed, 22 Feb 2012 09:52:38 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7838021F8843; Wed, 22 Feb 2012 09:52:38 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1MHqb3r075663 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Feb 2012 10:52:37 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F452842.3050905@stpeter.im>
Date: Wed, 22 Feb 2012 09:52:37 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3272FD67-C0BF-4408-8908-3F877F813398@vpnc.org>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
Cc: ietf-http-wg@w3.org, The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:52:40 -0000

On Feb 22, 2012, at 9:39 AM, Peter Saint-Andre wrote:

> The WebSec WG is in the Applications Area.

Yeeps! My apologies. I guess seeing a room full of security regulars =
made me forget.

--Paul Hoffman


From stephen.farrell@cs.tcd.ie  Wed Feb 22 10:35:32 2012
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 7E6D521F86F0; Wed, 22 Feb 2012 10:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s2-21b7tP8eU; Wed, 22 Feb 2012 10:35:22 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 0113621F86D9; Wed, 22 Feb 2012 10:35:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id B305B171CDD; Wed, 22 Feb 2012 18:35:20 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1329935720; bh=OBB0DGAI3P8Nqq whXd8hOmXNRqCQX8DRrMVz1rVEXow=; b=GaZwI69MLGw157/7RCXQdgWJhiQK6N hc+D9XO14d5qzCEA4w5W1smjV2LlbKDNjL6ScjTSKUvm42pTMsQ0Z+1F5QQ+3z/K Fd1CZ2X8GQOGchhPe/1iRrgpbtzd9weJt/SM2zgiuwCII87kGv6dzou6QuuYPDyj sUYi9x1mEMyFLeZQ0L+30Vd4W9GPoLD46/UtTmooq0Khv6WgU86S6EUqpLn0P3Be PWireygJH/Uz9H0fKuYWUbs26FF7Z64kueodd8ZvVhsy4Xix/fiy2WqYckbmX0xL D8Ee4bWUSixntT8MUdXedgoV2o0I91m5vaqChhkef/gCX+b6xznVV7mw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id d8xtqMi3Gqul; Wed, 22 Feb 2012 18:35:20 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c] (unknown [IPv6:2001:770:10:203:a288:b4ff:fe9c:bc5c]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id F11FF171CDB; Wed, 22 Feb 2012 18:35:17 +0000 (GMT)
Message-ID: <4F453565.1000208@cs.tcd.ie>
Date: Wed, 22 Feb 2012 18:35:17 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <3272FD67-C0BF-4408-8908-3F877F813398@vpnc.org>
In-Reply-To: <3272FD67-C0BF-4408-8908-3F877F813398@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:35:32 -0000

On 02/22/2012 05:52 PM, Paul Hoffman wrote:
> On Feb 22, 2012, at 9:39 AM, Peter Saint-Andre wrote:
>
>> The WebSec WG is in the Applications Area.
>
> Yeeps! My apologies. I guess seeing a room full of security regulars made me forget.
>

Regardless of that you do have a fair point that asking
apps folks to do stuff that'll please security folks might
be asking for trouble:-)

However, the counter to that is that security folks doing
stuff without enough apps input might produce something that
won't get adopted which also doesn't produce the right end
result.

Anyway, I think this topic, if tackled, won't lack
interested participants and will get plenty of security
and apps input no matter how we organise it.

S.


From paul.hoffman@vpnc.org  Wed Feb 22 10:40:02 2012
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 2D12D21F86FE; Wed, 22 Feb 2012 10:40:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkPMi0YawVaZ; Wed, 22 Feb 2012 10:40:01 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 796BB21F86FA; Wed, 22 Feb 2012 10:40:01 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1MIdnlX078299 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 22 Feb 2012 11:39:50 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F453565.1000208@cs.tcd.ie>
Date: Wed, 22 Feb 2012 10:39:49 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6697C0B0-FE11-45D3-A300-CEF1496D4688@vpnc.org>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <3272FD67-C0BF-4408-8908-3F877F813398@vpnc.org> <4F453565.1000208@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:40:02 -0000

On Feb 22, 2012, at 10:35 AM, Stephen Farrell wrote:

> Regardless of that you do have a fair point that asking
> apps folks to do stuff that'll please security folks might
> be asking for trouble:-)
>=20
> However, the counter to that is that security folks doing
> stuff without enough apps input might produce something that
> won't get adopted which also doesn't produce the right end
> result.
>=20
> Anyway, I think this topic, if tackled, won't lack
> interested participants and will get plenty of security
> and apps input no matter how we organise it.


Peter St.Andre's suggestion of a separate WG to deal specifically with =
HTTP authentication seems like the best way to be sure both sets of =
parties are fully involved. If the IESG charters it within the next few =
months, the HTTP 2.0 work can be informed by any changes (if any) that =
are needed.

--Paul Hoffman


From mrex@sap.com  Wed Feb 22 12:21:31 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76C8C21F85E4 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 12:21:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.054
X-Spam-Level: 
X-Spam-Status: No, score=-10.054 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AHaDLd7Lh-Ul for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 12:21:24 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 8766021F85E6 for <ietf@ietf.org>; Wed, 22 Feb 2012 12:21:24 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1MKLKKD004698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Feb 2012 21:21:20 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202222021.q1MKLKcg008488@fs4113.wdf.sap.corp>
Subject: Re: A nuance of interoperability reports
To: msk@cloudmark.com (Murray S. Kucherawy)
Date: Wed, 22 Feb 2012 21:21:20 +0100 (MET)
In-Reply-To: <9452079D1A51524AA5749AD23E00392803E486@exch-mbx901.corp.cloudmark.com> from "Murray S. Kucherawy" at Feb 22, 12 02:55:06 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:21:31 -0000

Murray S. Kucherawy wrote:
> 
> > From: Richard Barnes [mailto:rbarnes@bbn.com]
> > 
> > Seems like it depends on your definitions of "abusive" and
> > "legitimate".  Do you have an example?
> 
> For a contrived example, let's say a registered HTTP header field
> that's only ever found to be present in web pages used by bad actors,
> but lots of them.

Such as "P3P:" ?   :-D

-Martin

http://www.h-online.com/security/news/item/Google-also-bypassed-cookie-settings-in-Internet-Explorer-1438781.html

From stpeter@stpeter.im  Wed Feb 22 13:18:50 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2697321F8601; Wed, 22 Feb 2012 13:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.625
X-Spam-Level: 
X-Spam-Status: No, score=-102.625 tagged_above=-999 required=5 tests=[AWL=-0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GRtoW4ntcDA8; Wed, 22 Feb 2012 13:18:49 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 352E821F850D; Wed, 22 Feb 2012 13:18:48 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8524740058; Wed, 22 Feb 2012 14:30:03 -0700 (MST)
Message-ID: <4F455BB6.3070205@stpeter.im>
Date: Wed, 22 Feb 2012 14:18:46 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <3272FD67-C0BF-4408-8908-3F877F813398@vpnc.org> <4F453565.1000208@cs.tcd.ie> <6697C0B0-FE11-45D3-A300-CEF1496D4688@vpnc.org>
In-Reply-To: <6697C0B0-FE11-45D3-A300-CEF1496D4688@vpnc.org>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:18:50 -0000

On 2/22/12 11:39 AM, Paul Hoffman wrote:
> On Feb 22, 2012, at 10:35 AM, Stephen Farrell wrote:
> 
>> Regardless of that you do have a fair point that asking apps folks
>> to do stuff that'll please security folks might be asking for
>> trouble:-)
>> 
>> However, the counter to that is that security folks doing stuff
>> without enough apps input might produce something that won't get
>> adopted which also doesn't produce the right end result.
>> 
>> Anyway, I think this topic, if tackled, won't lack interested
>> participants and will get plenty of security and apps input no
>> matter how we organise it.
> 
> 
> Peter St.Andre's suggestion of a separate WG to deal specifically
> with HTTP authentication seems like the best way to be sure both sets
> of parties are fully involved. If the IESG charters it within the
> next few months, the HTTP 2.0 work can be informed by any changes (if
> any) that are needed.

By the way, I forwarded this message to the http-auth@ietf.org list
(yes, we already have a discussion list for these topics). The small
sample of replies indicates that (1) folks would prefer to broaden the
topic to web authentication, not strictly HTTP authentication and (2)
not everyone who is interested in these topics subscribes to the more
general ietf-http-wg@w3.org list.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From ron.even.tlv@gmail.com  Wed Feb 22 15:40:06 2012
Return-Path: <ron.even.tlv@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 C9EA121E8050; Wed, 22 Feb 2012 15:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.367
X-Spam-Level: 
X-Spam-Status: No, score=-3.367 tagged_above=-999 required=5 tests=[AWL=0.231,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpwZvZ4wAJrx; Wed, 22 Feb 2012 15:40:06 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 02BC721F8531; Wed, 22 Feb 2012 15:40:01 -0800 (PST)
Received: by eaal12 with SMTP id l12so261733eaa.31 for <multiple recipients>; Wed, 22 Feb 2012 15:40:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=KQhhBURyITiGAXIL35LoeX3T1R6+AZ/hnxt2aQ046Lo=; b=KF2bj7yKPea0I2gp4E5Y20jHp/bUQs1/FQaiSlto7jJuAc3OTotNJAGjB/bSPvVFsb zV0d9cty+SHGuiUNLl5vd/5t7bbCnRr1dR0joda/FdUed/Db0g1MGZ/Ox1eWe57SNjlF W7f2aGXNxNJriWhPMj66+M8r3N3e585QWMNMk=
Received: by 10.14.28.140 with SMTP id g12mr13150906eea.85.1329954001101; Wed, 22 Feb 2012 15:40:01 -0800 (PST)
Received: from windows8d787f9 ([109.67.208.29]) by mx.google.com with ESMTPS id n52sm108120844eea.5.2012.02.22.15.39.59 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Feb 2012 15:40:00 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-pcn-3-in-1-encoding.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-pcn-3-in-1-encoding-08
Date: Thu, 23 Feb 2012 01:39:35 +0200
Message-ID: <4f457cd0.4c200e0a.1409.2ad9@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0177_01CCF1CC.00BE5DC0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AczxuzunxXMMWgy+R726JyrlFSsFTw==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:40:07 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0177_01CCF1CC.00BE5DC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

Please resolve these comments along with any other Last Call comments you
may receive.

 

Document: draft-ietf-pcn-3-in-1-encoding-08

Reviewer: Roni Even

Review Date:2012-2-23

IETF LC End Date: 2012-2-23

IESG Telechat date:

 

Summary: This draft is ready for publication as a Standards Track RFC.

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

Section 1 4th paragraph "tunnelling"

 

 


------=_NextPart_000_0177_01CCF1CC.00BE5DC0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(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;}
@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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
pcn-3-in-1-encoding-08<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;2&#8211;23<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;2&#8211;23<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as a </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Standards =
Track RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editor=
ial comments:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section 1 =
4<sup>th</sup> paragraph &#8220;</span><span =
style=3D'font-family:"Courier =
New"'>tunnelling&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0177_01CCF1CC.00BE5DC0--


From lear@cisco.com  Wed Feb 22 22:38:47 2012
Return-Path: <lear@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 3758911E8083; Wed, 22 Feb 2012 22:38:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRPUjlUXFjCz; Wed, 22 Feb 2012 22:38:46 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2346211E807F; Wed, 22 Feb 2012 22:38:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=130; q=dns/txt; s=iport; t=1329979126; x=1331188726; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Ijq5NE2Rcuw/4vJJnVbK427ue9khtO+nJVlhci9yec0=; b=BQ54CMDWCaoN4wDieX2+/Kxsrd7/Ee/8olVICNDd3UtWH6aJvgfP3NdP el5nN7as1skG3tPT1ANGyKR5txNXbGQlWCJ+5EsgSZsoGki4H16eoBoHi XxzOlp+fQEkP3LSjsr09Wk7LOghmSrrtaySWqeHUNDYJld+u5JvL3w25N 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqUjAGbeRU+Q/khN/2dsb2JhbABEhTSsHQEDAYEGgQeBcwEBAQQSARBWEAsOCgICBSECAg8CRgYNAQcBAR6nXgGMZYoegS+MAgECCwQFCgMDBwMCBQoIAQsBAQEBAgECAoNGgQJPCoMFgRYElTiSbg
X-IronPort-AV: E=Sophos;i="4.73,468,1325462400"; d="scan'208";a="130314992"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 23 Feb 2012 06:38:45 +0000
Received: from dhcp-10-55-89-149.cisco.com (dhcp-10-55-89-149.cisco.com [10.55.89.149]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q1N6cigx009726; Thu, 23 Feb 2012 06:38:44 GMT
Message-ID: <4F45DEF4.202@cisco.com>
Date: Thu, 23 Feb 2012 07:38:44 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net>
In-Reply-To: <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:38:47 -0000

On 2/20/12 9:06 PM, John Scudder wrote:
> Jari,
>
>
> 2. LISP relies on caching,

LISP-ALT relies on caching.

Eliot

From salvatore.loreto@ericsson.com  Thu Feb 23 00:04:16 2012
Return-Path: <salvatore.loreto@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 04ADF21F8483; Thu, 23 Feb 2012 00:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.673
X-Spam-Level: 
X-Spam-Status: No, score=-109.673 tagged_above=-999 required=5 tests=[AWL=0.925, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzeoteohHzIs; Thu, 23 Feb 2012 00:04:14 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF4021F8474; Thu, 23 Feb 2012 00:04:13 -0800 (PST)
X-AuditID: c1b4fb3d-b7bb7ae0000007b2-20-4f45f2fb4184
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 6A.8A.01970.BF2F54F4; Thu, 23 Feb 2012 09:04:12 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.213.0; Thu, 23 Feb 2012 09:04:11 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 756F32321; Thu, 23 Feb 2012 10:04:11 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 5B60451C4F; Thu, 23 Feb 2012 10:04:11 +0200 (EET)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id E31EB5110D; Thu, 23 Feb 2012 10:04:10 +0200 (EET)
Message-ID: <4F45F2FA.70000@ericsson.com>
Date: Thu, 23 Feb 2012 10:04:10 +0200
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <4F441870.8010206@cs.tcd.ie> <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
In-Reply-To: <87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net>
Content-Type: multipart/alternative; boundary="------------090600000208000002070401"
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: AAAAAA==
Cc: Julian Reschke <julian.reschke@gmx.de>, "iesg@ietf.org" <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 08:04:16 -0000

--------------090600000208000002070401
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

On 2/22/12 12:40 AM, Mark Nottingham wrote:
> Also, most of the discussions about authentication and associated problems on the Web are*not*  exclusive to HTTP or even protocol artefacts; they include concerns like UI and human factors, integration into hypertext, etc. As such, what we really need is a "whole of stack" focus on Web authentication; shoving it into this particular WG will, IMO, lead to a predictable failure.
I agree with Mark on this point

/Salvatore
>
> Regards,
>
>
> --
> Mark Nottingham
> http://www.mnot.net/



--------------090600000208000002070401
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 2/22/12 12:40 AM, Mark Nottingham wrote:
    <blockquote cite="mid:87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net"
      type="cite">
      <pre wrap="">Also, most of the discussions about authentication and associated problems on the Web are <b class="moz-txt-star"><span class="moz-txt-tag">*</span>not<span class="moz-txt-tag">*</span></b> exclusive to HTTP or even protocol artefacts; they include concerns like UI and human factors, integration into hypertext, etc. As such, what we really need is a "whole of stack" focus on Web authentication; shoving it into this particular WG will, IMO, lead to a predictable failure.</pre>
    </blockquote>
    I agree with Mark on this point<br>
    <br>
    /Salvatore<br>
    <blockquote cite="mid:87902BF0-3CFC-4CA6-824C-7982ED1020A6@mnot.net"
      type="cite">
      <pre wrap="">

Regards,


--
Mark Nottingham
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.mnot.net/">http://www.mnot.net/</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">
</pre>
  </body>
</html>

--------------090600000208000002070401--

From lear@cisco.com  Thu Feb 23 04:48:00 2012
Return-Path: <lear@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 A5ED921F8763; Thu, 23 Feb 2012 04:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.24
X-Spam-Level: 
X-Spam-Status: No, score=-110.24 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IWdVT9PAv6uq; Thu, 23 Feb 2012 04:48:00 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 79A5521F8752; Thu, 23 Feb 2012 04:47:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=1810; q=dns/txt; s=iport; t=1330001279; x=1331210879; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=bEXBy+n8xN8TlOUT4qnF/UwhJctyGFF+pg9i87vGmuc=; b=LItNHu2yKkQFVGEHwURHilVd4P5yr9iTXU5wdbzuWKpSWd0EKiC1xUlo dvtcNYv+sB2jmvjm1cPTXpvRv9FYOPW5GSPz5Woq3NkUdCuQ72wzUyCdt iNbKnXpIWTQr+5pYVIlfZnoyVNoHNEXFSFtrAimFvePbdFpXOnQamTJOK U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACQ1Rk+Q/khL/2dsb2JhbABEhTStKYEHgWoFBAEBAQQSARBVARALAwEUCRYLAgIJAwIBAgFFBg0BBwEBHoUmgi6gFgGMZYoyjXADCAEMBQMChRAHCoMFgRYElTiSbg
X-IronPort-AV: E=Sophos;i="4.73,470,1325462400";  d="scan'208,217";a="130356471"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 23 Feb 2012 12:47:58 +0000
Received: from dhcp-10-55-89-149.cisco.com (dhcp-10-55-89-149.cisco.com [10.55.89.149]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1NClwNu013471; Thu, 23 Feb 2012 12:47:58 GMT
Message-ID: <4F46357D.3050300@cisco.com>
Date: Thu, 23 Feb 2012 13:47:57 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Damien Saucez <damien.saucez@gmail.com>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F45DEF4.202@cisco.com> <C4643BCE-9CFC-4C3D-A4D8-1813CF616A35@gmail.com>
In-Reply-To: <C4643BCE-9CFC-4C3D-A4D8-1813CF616A35@gmail.com>
X-Enigmail-Version: 1.3.5
Content-Type: multipart/alternative; boundary="------------010405080704050603080501"
Cc: John Scudder <jgs@juniper.net>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:48:00 -0000

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

Damian, others,

On 2/23/12 11:15 AM, Damien Saucez wrote:
> Hello Eliot,
>
> May I ask you why you say that LISP+ALT relies on caching?
>
> LISP+ALT is just a BGP based overlay, where is the caching
> there (is the BGP RIB that you consider as a cache?).

An investigation I ran looked at the possibility of doing a "push"
versus "pull" of the mappings.  It's not where the main LISP group went,
but it is possible.  To be fair there is still caching of state, but the
performance profile.  See draft-lear-lisp-nerd.

    Eliot


--------------010405080704050603080501
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">
    Damian, others,<br>
    <br>
    On 2/23/12 11:15 AM, Damien Saucez wrote:
    <blockquote
      cite="mid:C4643BCE-9CFC-4C3D-A4D8-1813CF616A35@gmail.com"
      type="cite">
      <pre wrap="">Hello Eliot,

May I ask you why you say that LISP+ALT relies on caching?

LISP+ALT is just a BGP based overlay, where is the caching
there (is the BGP RIB that you consider as a cache?).</pre>
    </blockquote>
    <br>
    An investigation I ran looked at the possibility of doing a "push"
    versus "pull" of the mappings.Â  It's not where the main LISP group
    went, but it is possible.Â  To be fair there is still caching of
    state, but the performance profile.Â  See draft-lear-lisp-nerd.<br>
    <br>
    <blockquote>Eliot<br>
    </blockquote>
  </body>
</html>

--------------010405080704050603080501--

From sant9442@gmail.com  Thu Feb 23 06:43:14 2012
Return-Path: <sant9442@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 5008321F881F for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 06:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.833
X-Spam-Level: 
X-Spam-Status: No, score=-2.833 tagged_above=-999 required=5 tests=[AWL=-0.526, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZiP8L2LSFWDi for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 06:43:13 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4E91621F881E for <ietf@ietf.org>; Thu, 23 Feb 2012 06:43:13 -0800 (PST)
Received: by yenm3 with SMTP id m3so673237yen.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 06:43:12 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.143.40 as permitted sender) client-ip=10.236.143.40; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.143.40 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.143.40]) by 10.236.143.40 with SMTP id k28mr3083125yhj.112.1330008192914 (num_hops = 1); Thu, 23 Feb 2012 06:43:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=uRrce3XHbdvpKef+jvb6w6MIMWKI+y1dECQ8AMK/aQw=; b=UoF/0UfrOiPiZeYA9r+vGT3im8fCHQOksyWKTWIw3Mbck91v+VRWXeKChSdXjb1d1Y Va3l2ToeQvEisCN5hm/fbGPJGgoempYWXXnso0PsUonJwwW7q3HyROuBfGB7kIuoVgRE 0wfshXu2nl44ASX499eMLU78uR5m9uB+PJrlM=
Received: by 10.236.143.40 with SMTP id k28mr2478000yhj.112.1330008192864; Thu, 23 Feb 2012 06:43:12 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id l2sm2436856anq.12.2012.02.23.06.43.09 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Feb 2012 06:43:11 -0800 (PST)
Message-ID: <4F46507F.6030603@gmail.com>
Date: Thu, 23 Feb 2012 09:43:11 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: A nuance of interoperability reports
References: <201202222021.q1MKLKcg008488@fs4113.wdf.sap.corp>
In-Reply-To: <201202222021.q1MKLKcg008488@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:43:14 -0000

Martin Rex wrote:
> Murray S. Kucherawy wrote:
>>> From: Richard Barnes [mailto:rbarnes@bbn.com]
>>>
>>> Seems like it depends on your definitions of "abusive" and
>>> "legitimate".  Do you have an example?
>> For a contrived example, let's say a registered HTTP header field
>> that's only ever found to be present in web pages used by bad actors,
>> but lots of them.
> 
> Such as "P3P:" ?   :-D

Be afraid, be very afraid!

> http://www.h-online.com/security/news/item/Google-also-bypassed-cookie-settings-in-Internet-Explorer-1438781.html


Thanks for the link Martin, helping to make sense of all the GooKids 
Inc., hoopla and no thanks for needing the pencil in time to get our 
operator P3P resources updated. :)

--
HLS

From julian.reschke@gmx.de  Thu Feb 23 08:13:29 2012
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 E012021F8839 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 08:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.47
X-Spam-Level: 
X-Spam-Status: No, score=-104.47 tagged_above=-999 required=5 tests=[AWL=-1.871, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9eEvR2K4F71 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 08:13:29 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id E08A421F883C for <ietf@ietf.org>; Thu, 23 Feb 2012 08:13:28 -0800 (PST)
Received: (qmail invoked by alias); 23 Feb 2012 16:13:27 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp012) with SMTP; 23 Feb 2012 17:13:27 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/7QMoh8qr7iB2SLS/331st2NuANfodu2nLXUeR// NC3hfsgeZFFrA3
Message-ID: <4F4665A1.9010508@gmx.de>
Date: Thu, 23 Feb 2012 17:13:21 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com>
In-Reply-To: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:13:30 -0000

On 2012-02-22 18:01, RJ Atkinson wrote:
> Earlier, Barry Leiba wrote, in part:
>> What we're looking at here is the need for an HTTP authentication
>> system that (for example) doesn't send reusable credentials,
>> is less susceptible to spoofing attacks, and so on.
>
> +1
>
> More generally, I support the concerns raised by Stephen Farrell,
> Wes Hardaker, and others that if *any* work is to be done on HTTP,
> then improving the authentication/confidentiality properties
> ought to be a mandatory part of that work.

I'm still waiting for somebody to explain why this can't already be 
defined as HTTP/1.1 authentication mechanism.

> The IETF has LOTS of experience that if strong(er) security
> mechanisms are not *required* in a WG Charter *very explicitly*,
> then that work will not happen at all.

Whether work happens nor not IMHO depends on getting the right people.

> Security that works well and is practical to implement
> needs to be designed-in, not bolted-on later.

I would say: security needs to be orthogonal.

> Separately, I would also like to see the known-weak cryptographic
> algorithms/modes (i.e. published literature indicates that
> an algorithm, a mode, or both is weak) that are included with HTTP
> (as separate from being part of TLS) formally get deprecated as part
> of any HTTPbis work.   For example, the WG ought to consider
> deprecating the use of the MD5, UNIXsum, and UNIXcksum algorithms
> within HTTP Digests [RFC-2617] [RFC-3230].

So far HTTPbis was not chartered to revise any existing auth scheme 
(just the framework).

Best regards, Julian

From woolf@isc.org  Wed Feb 22 09:12:14 2012
Return-Path: <woolf@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 60F5321F86B1 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 09:12:14 -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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V1Ro9+lqKkTC for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 09:12:13 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 8A35221F8646 for <ietf@ietf.org>; Wed, 22 Feb 2012 09:12:13 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id CFEA6C9422; Wed, 22 Feb 2012 17:12:06 +0000 (UTC) (envelope-from woolf@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10265) id AC848216C3B; Wed, 22 Feb 2012 17:12:06 +0000 (UTC)
Date: Wed, 22 Feb 2012 17:12:06 +0000
From: Suzanne Woolf <woolf@isc.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: A nuance of interoperability reports
Message-ID: <20120222171206.GE19790@bikeshed.isc.org>
References: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F5833273385BB34F99288B3648C4F06F19C9A7DE5C@EXCH-C2.corp.cloudmark.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Thu, 23 Feb 2012 08:14:54 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:58:43 -0000

On Tue, Feb 21, 2012 at 02:56:41PM -0800, Murray S. Kucherawy wrote:
> We like to see interoperability reports contain information about
> features of a protocol that are used vs. unused, so that if and when
> the protocol seeks advancement along the standards track, we can
> decide whether we want to keep it in the revision.

I'd support Randy's point about implemented vs. used for an
"interoperability" report, but only because I think of the
"assessment" part as separate, not unnecessary.

Such assessments need to consider what's implemented, what's used, and
yes, probably some element of context for both. However:

> Should we consider a protocol feature only used by abusive actors to
> be one that deserves to be kept, or is only legitimate use worth
> considering?

....is an overly simplistic way to pose the question.

Aside from the difficulty of judging "legitimate" use, there's the
question of why the feature is in the protocol in the first
place. Presumably protocol features exist because people anticipate
some net benefit from including them, and it seems that the right
question when deciding whether to keep a feature is not only whether
it's provided some benefit so far (i.e. it's implemented and used) but
also, if it hasn't, why not? 

In answering the "why" question, "We haven't needed it yet but we
expect to in the following use case in the next 18 months" leads in a
very different direction to "so far, it's useful only to attackers
working against us" or to "the problem still exists but we have a
better way to solve it" or to "the use case never materialized in
practice."

A slightly broader discussion of how the real-world deployment of the
protocol resembles (or doesn't) the anticipated deployment seems more
useful than trying to answer the question you're posing here.

It's difficult to have such a discussion without ratholing, but it
seems to me that the same can be said of trying to define "legitimate"
use.


Suzanne


From lear@cisco.com  Wed Feb 22 21:57:06 2012
Return-Path: <lear@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 5A29F21F85D8 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 21:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.618
X-Spam-Level: 
X-Spam-Status: No, score=-109.618 tagged_above=-999 required=5 tests=[AWL=-0.878, BAYES_20=-0.74, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2Erj53LQHtJ for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 21:57:05 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8124321F8575 for <ietf@ietf.org>; Wed, 22 Feb 2012 21:57:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=9298; q=dns/txt; s=iport; t=1329976624; x=1331186224; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=umtCUc4U6QLhdEzdoX6X9gh0BfWvdI03KwMfomjNx1E=; b=hMI3P+N2jERzUq35PxQPqUv4JTq8fIbQEg//mDFD0LqI6VGVOMEEemTq EZfaHCTkHUtjkA3BWhaQnQ61qxdVBQwmb7j0+yDYgzXPCoHrNkQtRfKSJ iDXJPc8EcM5ZXETLwwe0fMuCD4iVfT/RaulsDsw1XsRwFJ30hrPXypOb5 0=;
X-Files: None : None
X-IronPort-AV: E=Sophos;i="4.73,468,1325462400";  d="eml'208?scan'208,208";a="66852616"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 23 Feb 2012 05:57:03 +0000
Received: from dhcp-10-55-89-149.cisco.com (dhcp-10-55-89-149.cisco.com [10.55.89.149]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1N5v20X032583; Thu, 23 Feb 2012 05:57:02 GMT
Message-ID: <4F45D52E.1080101@cisco.com>
Date: Thu, 23 Feb 2012 06:57:02 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>, Kim Davies <kim.davies@icann.org>, Michelle Cotton <michelle.cotton@icann.org>, Bernard Aboba <bernard.aboba@gmail.com>, Pete Resnick <presnick@qualcomm.com>, Peter Saint-Andre <Peter.SaintAndre@webex.com>, Elise Gerich <elise.gerich@icann.org>, Robert Elz <kre@munnari.OZ.AU>
Subject: Fwd: Re: [tz] Astrolabe dismisses suit.
References: <20120223003759.GZ10521@multics.mit.edu>
In-Reply-To: <20120223003759.GZ10521@multics.mit.edu>
X-Enigmail-Version: 1.3.5
X-Forwarded-Message-Id: <20120223003759.GZ10521@multics.mit.edu>
Content-Type: multipart/mixed; boundary="------------070708000805070406060608"
X-Mailman-Approved-At: Thu, 23 Feb 2012 08:15:31 -0800
Cc: IETF Discussion <ietf@ietf.org>, "Lynn St.Amour" <st.amour@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 05:57:06 -0000

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

Russ, Michelle, Elise, Kim, Bernard, Rob,

I'm passing along a note from JHawk that contains a press release from
EFF regarding the dismissal of the lawsuit against TZ Database
maintainers Arthur David Olson and Paul Eggert.  This lawsuit was wrong
from the beginning and disruptive to the volunteers and the industry. 
I'm very glad that Astrolabe has withdrawn it, and I'm thankful to the
EFF for their full-throated defense of Arthur David Olson, to you and
the IESG and ICANN staff, and to Rob Elz for having taken an active hand
(in Rob's case a VERY active hand) in seeing that this good work continues.

Eliot


--------------070708000805070406060608
Content-Type: message/rfc822;
 name="Re: [tz] Astrolabe dismisses suit_.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Re: [tz] Astrolabe dismisses suit_.eml"

X-Mozilla-Keys: 
Received: from xbh-ams-101.cisco.com ([144.254.74.71]) by xmb-ams-105.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Thu, 23 Feb 2012 01:55:48 +0100
Received: from xbh-rcd-301.cisco.com ([72.163.63.8]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Thu, 23 Feb 2012 01:55:48 +0100
Received: from rcdn-iport-9.cisco.com ([173.37.86.80]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);
	 Wed, 22 Feb 2012 18:55:46 -0600
Received: from rcdn-core-1.cisco.com ([173.37.93.152])
  by rcdn-iport-9.cisco.com with ESMTP; 23 Feb 2012 00:55:46 +0000
Received: from rcdn-inbound-d.cisco.com (rcdn-inbound-d.cisco.com [72.163.7.173])
	by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1N0tkVB024661;
	Thu, 23 Feb 2012 00:55:46 GMT
Authentication-Results: rcdn-inbound-d.cisco.com; dkim=neutral (message not signed) header.i=none
X-from-outside-Cisco: 208.77.188.100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlQCAOiNRU/QTbxkmWdsb2JhbABEslciAQEBAQEICwsHFCeBcwEBAQQBAQEPAScMCiwDAQIGAQEKEQMBAicIAwEQOyEFHYdomUMBlXKJAwSMdg4CEwUDCQ4LAw8NAgcdCoUWAQQGAgMuGhKDPASIT4xokwyBPg
X-IronPort-AV: E=Sophos;i="4.73,467,1325462400"; 
   d="scan'208";a="28533343"
Received: from mm.icann.org ([208.77.188.100])
  by rcdn-inbound-d.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Feb 2012 00:55:45 +0000
Received: from mm.icann.org (localhost.localdomain [127.0.0.1])
	by mm.icann.org (8.13.8/8.13.8) with ESMTP id q1N0s6P4026269;
	Thu, 23 Feb 2012 00:54:19 GMT
Received: from pechora6.dc.icann.org (pechora6.icann.org
	[IPv6:2620:0:2830:201::1:72] (may be forged))
	by mm.icann.org (8.13.8/8.13.8) with ESMTP id q1N0s4Ro026266
	for <tz@mm.icann.org>; Thu, 23 Feb 2012 00:54:04 GMT
Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU
	[18.9.25.13])
	by pechora6.dc.icann.org (8.13.8/8.13.8) with ESMTP id q1N0rhbF010481
	for <tz@iana.org>; Thu, 23 Feb 2012 00:54:04 GMT
X-AuditID: 1209190d-b7fbf6d0000008ba-47-4f458a699d92
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36])
	by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP
	id 64.0A.02234.96A854F4; Wed, 22 Feb 2012 19:38:01 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id q1N0c1qj016775; 
	Wed, 22 Feb 2012 19:38:01 -0500
Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73])
	(authenticated bits=56) (User authenticated as jhawk@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q1N0bx6l007409
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Wed, 22 Feb 2012 19:38:00 -0500 (EST)
Received: (from jhawk@localhost) by multics.mit.edu (8.12.9.20060308)
	id q1N0bx52010641; Wed, 22 Feb 2012 19:37:59 -0500 (EST)
Date: Wed, 22 Feb 2012 19:37:59 -0500
From: John Hawkinson <jhawk@mit.edu>
To: tz@iana.org
Message-ID: <20120223003759.GZ10521@multics.mit.edu>
References: <20120222210958.GN10521@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120222210958.GN10521@multics.mit.edu>
User-Agent: Mutt/1.5.15 (2007-05-28)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKIsWRmVeSWpSXmKPExsUixG6nopvZ5epvMLtL0+L1lBZWi8f/pjA5
	MHn0yHssfNjDGMAUxWWTkpqTWZZapG+XwJWx4ccdtoK5EhUvWw6xNjD+Fe5i5OSQEDCRmH3s
	GBuELSZx4d56IJuLQ0hgH6PEu4ndjBDOBkaJ7lu/oJwDTBJf5lxnhXAaGCWW/v8A1MPBwSKg
	KvFvnifIKDYBFYk532+yg9giAvwSTz7PZgGxhQXUJNp/XwSzeYFWv1g5E2y1EJDd27EAKi4o
	cXLmEzCbWUBL4sa/l0wg45kFpCWW/+MACXMKmEpsezCNEcQWBVo1beIvpgmMgrOQdM9C0j0L
	oXsBI/MqRtmU3Crd3MTMnOLUZN3i5MS8vNQiXSO93MwSvdSU0k2MoNDllOTdwfjuoNIhRgEO
	RiUe3oXsrv5CrIllxZW5hxglOZiURHkrO4FCfEn5KZUZicUZ8UWlOanFhxglOJiVRHi54oFy
	vCmJlVWpRfkwKWkOFiVxXlWtd35CAumJJanZqakFqUUwWRkODiUJ3o8gQwWLUtNTK9Iyc0oQ
	0kwcnCDDeYCGi3aBDC8uSMwtzkyHyJ9iVJQS590M0iwAksgozYPrhaWWV4ziQK8I8z4AqeIB
	piW47ldAg5mABrf8dwQZXJKIkJJqYHRfZd15sU04RPvQlB1e83nTHl/6sOn1Q5az5duSjjzd
	vObY88o6ZWufRJNz2wNmnO3/8+Bcep3mLN7L8QdbVq8Nfh85Z7f/n46fsbpvOE1z+jl2XEhT
	m/7LXZxN7XJNbYqswr64Ez/3cFc+TPa686rK9w7n8YKaX1Z7Hj2b+uDizAf2THd1uw8osRRn
	JBpqMRcVJwIAA2PJpwgDAAA=
X-Greylist: Delayed for 00:15:42 by milter-greylist-4.2.3
	(pechora6.dc.icann.org [192.0.46.72]);
	Thu, 23 Feb 2012 00:54:04 +0000 (UTC)
Subject: Re: [tz] Astrolabe dismisses suit.
X-BeenThere: tz@iana.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Time Zone Database discussion <tz.iana.org>
List-Unsubscribe: <https://mm.icann.org/mailman/listinfo/tz>,
	<mailto:tz-request@iana.org?subject=unsubscribe>
List-Archive: <http://mm.icann.org/pipermail/tz>
List-Post: <mailto:tz@iana.org>
List-Help: <mailto:tz-request@iana.org?subject=help>
List-Subscribe: <https://mm.icann.org/mailman/listinfo/tz>,
	<mailto:tz-request@iana.org?subject=subscribe>
Sender: tz-bounces@iana.org
Errors-To: tz-bounces@iana.org
Return-Path: tz-bounces@iana.org
X-OriginalArrivalTime: 23 Feb 2012 00:55:46.0263 (UTC) FILETIME=[E0677670:01CCF1C5]

The EFF issued the below press release this afternoon
with statements from Astrolabe.

--jhawk@mit.edu
  John Hawkinson


Subject: EFF Wins Protection for Time Zone Database
X-RSS-ID: https://www.eff.org/rss/69783 at https://www.eff.org
X-RSS-URL:
	https://www.eff.org/press/releases/eff-wins-protection-time-zone-database
Date: Wed, 22 Feb 2012 23:41:37 -0000
From: "Deeplinks: rebecca"

Copyright Lawsuit Threatened Essential Tool for Engineers Around the World

San Francisco - The Electronic Frontier Foundation (EFF) is pleased to
announce that a copyright lawsuit threatening an important database of
time zone information has been dismissed. The astrology software
company that filed the lawsuit, Astrolabe, has also apologized and
agreed to a 'covenant not to sue' going forward, which will help
protect the database from future baseless legal actions and
disruptions.

Software engineers around the world depend on the time zone database
to make sure that time-stamps for email and other files work correctly
no matter where you are. However, last September, Astrolabe filed a
lawsuit against Arthur David Olson and Paul Eggert -- the researchers
who coordinated the database's development for decades -- because the
database includes information from an atlas in which Astrolabe claimed
to own copyright. But facts -- like what time the sun rises -- are
not copyrightable. EFF, along with co-counsel Adam Kessel and Olivia
Nguyen at the Boston office of Fish & Richardson P.C, promptly signed
on to defend Olson and Eggert and protect this essential tool. In
January, EFF advised Astrolabe that Olson and Eggert would move for
sanctions if Astrolabe did not withdraw its complaint. Today's
dismissal followed.

In a statement, Astrolabe said, "Astrolabe's lawsuit against Mr. Olson
and Mr. Eggert was based on a flawed understanding of the law. We now
recognize that historical facts are no one's property and,
accordingly, are withdrawing our Complaint. We deeply regret the
disruption that our lawsuit caused for the volunteers who maintain the
TZ database, and for Internet users."

"It's a fundamental principle of copyright law that facts are not
copyrightable, and Astrolabe should have known that," said EFF
Intellectual Property Director Corynne McSherry. "While the lawsuit
should never have been filed, we're pleased that the legal threat to
an important resource has been eliminated.

"We are grateful that EFF and its co-counsel at Fish & Richardson were
able to step in and assist us, so that we could help ensure the TZ
database would continue to be available," said Eggert and Olson.

For more on this case:  
[https://www.eff.org/cases/astrolabe-v-olson][1]

Contacts:

Corynne McSherry  
   Intellectual Property Director  
   Electronic Frontier Foundation  
   corynne@eff.org

Mitch Stoltz  
   Staff Attorney  
   Electronic Frontier Foundation  
   mitch@eff.org

   [1]: https://www.eff.org/cases/astrolabe-v-olson

URL: https://www.eff.org/press/releases/eff-wins-protection-time-zone-database


--------------070708000805070406060608--

From damien.saucez@gmail.com  Thu Feb 23 02:15:13 2012
Return-Path: <damien.saucez@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 0CFAC21F8557; Thu, 23 Feb 2012 02:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level: 
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_43=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2A9QHaeLQKvs; Thu, 23 Feb 2012 02:15:12 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id B88C721F84DA; Thu, 23 Feb 2012 02:15:10 -0800 (PST)
Received: by wibhm9 with SMTP id hm9so776225wib.31 for <multiple recipients>; Thu, 23 Feb 2012 02:15:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=c2vtgB2GuN1ckRr+VxmIUD6LoyHlg/yQbEuypt3cirY=; b=qFG/sRMoGpgLIWVkHrgkWyCCzxIDXjp7V+jQiL8jYFWU6IMTxQpjTEgLPe0/ae6/nS y3kHMPbrliJl50sF3VGaUN6mVsWHJkmtQADWqZlxKyfbNOHTwoQcVJiyUXk8j3vHWPiS 3NNNaNvJ5QO+Q6F/HOfHico9rOByJWY37JP+4=
Received: by 10.180.101.165 with SMTP id fh5mr1425449wib.10.1329992109961; Thu, 23 Feb 2012 02:15:09 -0800 (PST)
Received: from faucon.inria.fr (faucon.inria.fr. [138.96.201.73]) by mx.google.com with ESMTPS id dr5sm4608899wib.0.2012.02.23.02.15.08 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Feb 2012 02:15:09 -0800 (PST)
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Damien Saucez <damien.saucez@gmail.com>
In-Reply-To: <4F45DEF4.202@cisco.com>
Date: Thu, 23 Feb 2012 11:15:07 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <C4643BCE-9CFC-4C3D-A4D8-1813CF616A35@gmail.com>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F45DEF4.202@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Thu, 23 Feb 2012 08:15:41 -0800
Cc: John Scudder <jgs@juniper.net>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:15:13 -0000

Hello Eliot,

May I ask you why you say that LISP+ALT relies on caching?

LISP+ALT is just a BGP based overlay, where is the caching
there (is the BGP RIB that you consider as a cache?).

Cheers,

Damien Saucez

On 23 Feb 2012, at 07:38, Eliot Lear wrote:

> 
> 
> On 2/20/12 9:06 PM, John Scudder wrote:
>> Jari,
>> 
>> 
>> 2. LISP relies on caching,
> 
> LISP-ALT relies on caching.
> 
> Eliot
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp


From DanielC@orckit.com  Thu Feb 23 02:35:29 2012
Return-Path: <DanielC@orckit.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57F7421F863C for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 02:35:29 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aaRotBb-QENJ for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 02:35:28 -0800 (PST)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [109.226.33.14]) by ietfa.amsl.com (Postfix) with ESMTP id 06C4621F84C8 for <ietf@ietf.org>; Thu, 23 Feb 2012 02:35:27 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
Date: Thu, 23 Feb 2012 12:35:20 +0200
Message-ID: <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
In-Reply-To: <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
Thread-Index: AQGdS0dQFbRu6GyAeWPtVTnp+xX6JJaoU1awgAFDNYA=
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk>
From: "Daniel Cohn" <DanielC@orckit.com>
To: <ietf@ietf.org>
X-Mailman-Approved-At: Thu, 23 Feb 2012 08:15:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:35:29 -0000

Support - as there is no foreseen shortage in ACH types, I don't see a
reason why this code point should not be allocated to an ITU developed
protocol that is already deployed in the field.

DC

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 22 February 2012 15:13
> To: IETF-Announce
> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
> Informational RFC
>=20
>=20
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational 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 2012-03-21. 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
>    This document assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3

From ietfdbh@comcast.net  Wed Feb 22 09:37:49 2012
Return-Path: <ietfdbh@comcast.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 3396021F87F9 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 09:37:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.26
X-Spam-Level: 
X-Spam-Status: No, score=-102.26 tagged_above=-999 required=5 tests=[AWL=0.339, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BogyLAfb5nrm for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2012 09:37:42 -0800 (PST)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5D98B21F86F8 for <ietf@ietf.org>; Wed, 22 Feb 2012 09:37:39 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta05.westchester.pa.mail.comcast.net with comcast id d3s21i00H1uE5Es555dfPk; Wed, 22 Feb 2012 17:37:39 +0000
Received: from [192.168.1.33] ([71.233.85.150]) by omta16.westchester.pa.mail.comcast.net with comcast id d5dd1i00Y3Ecudz3c5debX; Wed, 22 Feb 2012 17:37:39 +0000
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Wed, 22 Feb 2012 12:37:34 -0500
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: David Harrington <ietfdbh@comcast.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>, The IESG <iesg@ietf.org>
Message-ID: <CB6A9206.14171%ietfdbh@comcast.net>
Thread-Topic: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-Reply-To: <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Thu, 23 Feb 2012 08:15:55 -0800
Cc: IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:37:49 -0000

Point taken.

--
David Harrington
Director, Transport Area
Internet Engineering Task Force (IETF)
Ietfdbh@comcast.net
+1-603-828-1401





On 2/22/12 12:31 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>The earnest calls for better authentication on this thread appear to
>ignore the fact that the very things that are being requested were put
>out of scope for the websec WG in their charter. I hope that no one
>things that a WG in the Applications Area will be better equipped to come
>up with a better authentication mechanism than one in the Security Area.
>
>Asking the HTTPheads to guess what the securityheads might want is not a
>good way to design HTTP 2.0.
>
>Proposal: leave the httpbis WG charter as-is and re-charter the websec WG
>to consider what is needed in the HTTP authentication model. Later,
>recharter the websec WG to, you know, actually do the security work for
>authentication.
>
>--Paul Hoffman



From mrex@sap.com  Thu Feb 23 08:52:12 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D46621F86CE for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 08:52:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.06
X-Spam-Level: 
X-Spam-Status: No, score=-10.06 tagged_above=-999 required=5 tests=[AWL=0.189,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftr2LTaSas-E for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 08:52:11 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 7805721F86FF for <ietf@ietf.org>; Thu, 23 Feb 2012 08:52:08 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q1NGq0jG008164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Feb 2012 17:52:05 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>
Subject: Re: Variable length internet addresses in TCP/IP: history
To: bob.hinden@gmail.com (Bob Hinden)
Date: Thu, 23 Feb 2012 17:51:59 +0100 (MET)
In-Reply-To: <9565EEEA-8732-4A47-90BB-9318E1ACB433@gmail.com> from "Bob Hinden" at Feb 14, 12 03:56:16 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: braden@isi.edu, bob.hinden@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:52:12 -0000

Bob Hinden wrote:
> 
> Martin Rex wrote:
> > 
> > With a fully backwards compatible transparent addressing scheme,
> > a much larger fraction of the nodes would have switched to actively
> > use IPv6 many years ago.
> 
> Right, just like they could have deployed dual stack many years ago too.

Just two days ago I had an extremeley disappointing experience with IPv6.
Windows XP 64-bit (aka Win2003sp2) on a local network with a private
DNS universe, IPv4 only network, Windows IPv6 protocol stack installed
but IPv6 active only on the two virtual network interfaces of VMware.

Somehow the DNS servers configured in the network settings had performed
only a partial zone reload and were replying only to some queries,
failing some DNS queries with server failure or timeout,
and one DNS zone had become completely invisible.

I noticed the problem suddenly during work because every new connection
took ~16 seconds delay to complete.  Wondering what was wrong, I started
wireshark.

I saw Windows2003 send out 23 DNS lookups for AAAA records for the
requested hostname over the course of 16 seconds (some of which returned
server failure, some of which failed with no such name),
until Windows 2003 finally decided to also try a DNS A query--which got
immediately successfully answered and the connection was established.
The delay affected each and every connection attempt, even when contacting
the same host repeatedly (although there is a DNScache service running...).

Disabling IPv6 on all network adapters did not stop this Windows AAAA frenzy,
I had to actually uninstall the IPv6 protocol stack (an action which
immediately kills *ALL* network connectivity of the machine and requires
a reboot to recover...) for this AAAA nonsense to end.

During the past few years I had two similar encounters with sudden severe
connectivity problems on a Windows XP and a Linux installation, and
both times, the problem disappeared when I disabled IPv6.

It is also significantly easier to configure the firewall for IPv4-only...

-Martin

From rja.lists@gmail.com  Thu Feb 23 09:59:19 2012
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 069F821F8518 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 09:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.606
X-Spam-Level: 
X-Spam-Status: No, score=-3.606 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsIeeaatszV6 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 09:59:18 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4146E21F8517 for <ietf@ietf.org>; Thu, 23 Feb 2012 09:59:18 -0800 (PST)
Received: by qcsq13 with SMTP id q13so22121qcs.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 09:59:17 -0800 (PST)
Received-SPF: pass (google.com: domain of rja.lists@gmail.com designates 10.229.75.216 as permitted sender) client-ip=10.229.75.216; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of rja.lists@gmail.com designates 10.229.75.216 as permitted sender) smtp.mail=rja.lists@gmail.com; dkim=pass header.i=rja.lists@gmail.com
Received: from mr.google.com ([10.229.75.216]) by 10.229.75.216 with SMTP id z24mr1760988qcj.50.1330019957736 (num_hops = 1); Thu, 23 Feb 2012 09:59:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=GSF7Gy6LmHNkOx3VnrxaOyVpbjKo1sjMiBbkWM8sRnQ=; b=AMeENf2mvroyFUR6bnt9tZwMA8dKs3OJjeroxmpjhWBY7lINXcKoFRaMkkV8X87P/A mCn5OiHq6f4AhsnaOQWfZsHCIZtFtEw4WAKxIZio/cwnCBmfqL2wUijkVpLLlSZzCxGe 6cCRcdvABUYfMnnD62dlMFZkcPCKyxoyNhcDI=
Received: by 10.229.75.216 with SMTP id z24mr1505292qcj.50.1330019957668; Thu, 23 Feb 2012 09:59:17 -0800 (PST)
Received: from [10.30.20.12] (pool-96-225-134-175.nrflva.fios.verizon.net. [96.225.134.175]) by mx.google.com with ESMTPS id hi8sm5566441qab.3.2012.02.23.09.59.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Feb 2012 09:59:16 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <4F4665A1.9010508@gmx.de>
Date: Thu, 23 Feb 2012 12:59:15 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <0FABC4E8-3B45-4B19-B2C7-B1494DEC00F4@gmail.com>
References: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com> <4F4665A1.9010508@gmx.de>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1257)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:59:19 -0000

On 23  Feb 2012, at 11:13 , Julian Reschke wrote:
> On 2012-02-22 18:01, RJ Atkinson wrote:
>> Security that works well and is practical to implement
>> needs to be designed-in, not bolted-on later.
> 
> I would say: security needs to be orthogonal.

There are at least 2 decades of experience that
security has to be design-in, rather than bolted-on,
for it to work well -- and for it to be practical
to implement.

I hear that you don't agree, but the IETF experience
on this specific point really is quite clear.  Add-on 
security doesn't work.

Yours,

Ran


From lsawyer@gci.com  Thu Feb 23 10:02:30 2012
Return-Path: <lsawyer@gci.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABB721F8768 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 10:02:30 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTys4GhzP9Pn for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 10:02:29 -0800 (PST)
Received: from mailgw2.gci.com (mailgw2.gci.com [209.165.141.87]) by ietfa.amsl.com (Postfix) with ESMTP id 632A421F853A for <ietf@ietf.org>; Thu, 23 Feb 2012 10:02:29 -0800 (PST)
Received: from FNB1CAS01.gci.com (10.100.230.66) by mailgw2.gci.com (172.19.0.32) with Microsoft SMTP Server (TLS) id 8.2.234.1; Thu, 23 Feb 2012 09:02:16 -0900
Received: from fnb1mbx01.gci.com ([10.100.230.59]) by FNB1CAS01.gci.com ([10.100.230.66]) with mapi; Thu, 23 Feb 2012 09:02:22 -0900
From: Leif Sawyer <lsawyer@gci.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 23 Feb 2012 09:00:29 -0900
Subject: RE: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Topic: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Index: AczyVOnzSI4ZKiwjRn6vS47F2HP4egAAB1VS
Message-ID: <18B2C6E38A3A324986B392B2D18ABC5101D32135AB@fnb1mbx01.gci.com>
References: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com> <4F4665A1.9010508@gmx.de>, <0FABC4E8-3B45-4B19-B2C7-B1494DEC00F4@gmail.com>
In-Reply-To: <0FABC4E8-3B45-4B19-B2C7-B1494DEC00F4@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:02:30 -0000

I've got the last 2 decades of experience trying to deal with security on t=
he network.

95% is dealing with the peculiarities of the "bolt-on"  after-thoughts.

I would much prefer seeing security  designed-in, with the flexibility to d=
eal with
the future...

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of RJ Atkinso=
n [rja.lists@gmail.com]
Sent: Thursday, February 23, 2012 8:59 AM
To: ietf@ietf.org
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpb=
is)

On 23  Feb 2012, at 11:13 , Julian Reschke wrote:
> On 2012-02-22 18:01, RJ Atkinson wrote:
>> Security that works well and is practical to implement
>> needs to be designed-in, not bolted-on later.
>
> I would say: security needs to be orthogonal.

There are at least 2 decades of experience that
security has to be design-in, rather than bolted-on,
for it to work well -- and for it to be practical
to implement.

I hear that you don't agree, but the IETF experience
on this specific point really is quite clear.  Add-on
security doesn't work.

Yours,

Ran

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf=

From wesley.george@twcable.com  Thu Feb 23 11:49:08 2012
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE7F21F8885 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 11:49:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.509
X-Spam-Level: 
X-Spam-Status: No, score=-0.509 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAjxHdr2Tk5f for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 11:49:07 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2CB21F8872 for <ietf@ietf.org>; Thu, 23 Feb 2012 11:49:07 -0800 (PST)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.73,470,1325480400"; d="scan'208";a="327157799"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 23 Feb 2012 14:47:56 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Thu, 23 Feb 2012 14:48:39 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 23 Feb 2012 14:48:38 -0500
Subject: RE: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
Thread-Topic: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC
Thread-Index: Aczl7ByaxbGX+HUFS2qmr23L7R4iHQMd8zjQ
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377917397FC8D1@PRVPEXVS03.corp.twcable.com>
References: <20120207225848.10346.42650.idtracker@ietfa.amsl.com>
In-Reply-To: <20120207225848.10346.42650.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:49:08 -0000

Revision -04 has been posted which I believe addresses all of the comments =
received thus far.

http://tools.ietf.org/html/draft-george-travel-faq-04

Thanks,

Wes George

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.o=
rg]
> On Behalf Of The IESG
> Sent: Tuesday, February 07, 2012 5:59 PM
> To: IETF-Announce
> Subject: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attend=
ees'
> Frequently Asked (travel) Questions) to Informational RFC
>
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IETF meeting attendees' Frequently Asked (travel) Questions'
>   <draft-george-travel-faq-03.txt> as an 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 2012-03-06. 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 attempts to provide a list of the common Frequently
>    Asked Questions (FAQs) that IETF meeting attendees often ask
>    regarding travel logistics and local information.  It is intended to
>    assist those who are willing to provide local information, so that if
>    they wish to pre-populate answers to some or all of these questions
>    either in the IETF Wiki or a meeting-specific site, they have a
>    reasonably complete list of ideas to draw from.  It is not meant as a
>    list of required information that the host or secretariat needs to
>    provide, merely as a guideline.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-george-travel-faq/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-george-travel-faq/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From brian.e.carpenter@gmail.com  Thu Feb 23 13:32:38 2012
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 53DCB21F8875 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 13:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.508
X-Spam-Level: 
X-Spam-Status: No, score=-103.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SEnWIGTdeeJO for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 13:32:37 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABBD21F887B for <ietf@ietf.org>; Thu, 23 Feb 2012 13:32:37 -0800 (PST)
Received: by eekc41 with SMTP id c41so674423eek.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 13:32:36 -0800 (PST)
Received-SPF: pass (google.com: domain of brian.e.carpenter@gmail.com designates 10.14.22.16 as permitted sender) client-ip=10.14.22.16; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of brian.e.carpenter@gmail.com designates 10.14.22.16 as permitted sender) smtp.mail=brian.e.carpenter@gmail.com; dkim=pass header.i=brian.e.carpenter@gmail.com
Received: from mr.google.com ([10.14.22.16]) by 10.14.22.16 with SMTP id s16mr1820390ees.2.1330032756524 (num_hops = 1); Thu, 23 Feb 2012 13:32:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+tCM1a8oClCF9xqx1cXv+6wL9+CA3uGYftvhbMTzKAw=; b=T4mIi4oaKp493ARmpZMOwlv7J5i8qBjQnWKQ36FWvgR50lClvaAt+B5wOzRe5iV8aB rr14E6egj54wfjHP90+GG4TeNqC7m+K2XdaymcFK/YRMi3mVqzTai778p9+NqKMeCgze REgMnPAKQvz/kAEyS6S4XzJav+Q27oDzj+R6c=
Received: by 10.14.22.16 with SMTP id s16mr1425615ees.2.1330032756366; Thu, 23 Feb 2012 13:32:36 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id u9sm9768140eem.11.2012.02.23.13.32.33 (version=SSLv3 cipher=OTHER); Thu, 23 Feb 2012 13:32:35 -0800 (PST)
Message-ID: <4F46B06B.6010908@gmail.com>
Date: Fri, 24 Feb 2012 10:32:27 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mrex@sap.com
Subject: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>
In-Reply-To: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: braden@isi.edu, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:32:38 -0000

Martin,

Yes, the issues with an unconditional "prefer IPv6" approach
have been noted, and operating systems of the vintages you
mention certainly deserved criticism. In fact this has been a
major focus of IPv6 operational discussions, and lies behind
things like the DNS whitelisting method, the happy-eyeballs
work, and my own RFC 6343.

Old news; unfortunately it means you need new o/s versions.
Disabling 6to4 and Teredo unless they are known to be working
well is a good start, however.

Regards
   Brian Carpenter

On 2012-02-24 05:51, Martin Rex wrote:
> Bob Hinden wrote:
>> Martin Rex wrote:
>>> With a fully backwards compatible transparent addressing scheme,
>>> a much larger fraction of the nodes would have switched to actively
>>> use IPv6 many years ago.
>> Right, just like they could have deployed dual stack many years ago too.
> 
> Just two days ago I had an extremeley disappointing experience with IPv6.
> Windows XP 64-bit (aka Win2003sp2) on a local network with a private
> DNS universe, IPv4 only network, Windows IPv6 protocol stack installed
> but IPv6 active only on the two virtual network interfaces of VMware.
> 
> Somehow the DNS servers configured in the network settings had performed
> only a partial zone reload and were replying only to some queries,
> failing some DNS queries with server failure or timeout,
> and one DNS zone had become completely invisible.
> 
> I noticed the problem suddenly during work because every new connection
> took ~16 seconds delay to complete.  Wondering what was wrong, I started
> wireshark.
> 
> I saw Windows2003 send out 23 DNS lookups for AAAA records for the
> requested hostname over the course of 16 seconds (some of which returned
> server failure, some of which failed with no such name),
> until Windows 2003 finally decided to also try a DNS A query--which got
> immediately successfully answered and the connection was established.
> The delay affected each and every connection attempt, even when contacting
> the same host repeatedly (although there is a DNScache service running...).
> 
> Disabling IPv6 on all network adapters did not stop this Windows AAAA frenzy,
> I had to actually uninstall the IPv6 protocol stack (an action which
> immediately kills *ALL* network connectivity of the machine and requires
> a reboot to recover...) for this AAAA nonsense to end.
> 
> During the past few years I had two similar encounters with sudden severe
> connectivity problems on a Windows XP and a Linux installation, and
> both times, the problem disappeared when I disabled IPv6.
> 
> It is also significantly easier to configure the firewall for IPv4-only...
> 
> -Martin
> 

From ned+ietf@mauve.mrochek.com  Thu Feb 23 14:00:55 2012
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 D7D2921F85D9 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:00:55 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l1Lj2J1hgK5g for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:00:54 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8568921F85D4 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:00:54 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCBYZN2T34012JKT@mauve.mrochek.com> for ietf@ietf.org; Thu, 23 Feb 2012 14:00:52 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCBX82X8F400ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 23 Feb 2012 14:00:49 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com>
Date: Thu, 23 Feb 2012 13:51:50 -0800 (PST)
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
In-reply-to: "Your message dated Fri, 24 Feb 2012 10:32:27 +1300" <4F46B06B.6010908@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330034458; i=@mrochek.com; bh=KAu6ej3wbwa0+GmUEqPFe3Y3h5bRkffbAhnzmnekdMk=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=PaiDt3VAjLSGCk4wt4ADZxqMLbBHVA5TY29ThELhZGz8emNTTyyADZ8lLwS/sM2QR fPgZrPsmiYp2L47xE3S9lrrX6UF8FdXBJLKzBo0AZdbC65B+UBxV9VZ9gOcuTt8oIB bOlTiIqgANK8f27YIs4K/yaH205LMtl5nOvocVNI=
Cc: Bob Hinden <bob.hinden@gmail.com>, braden@isi.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:00:56 -0000

> Yes, the issues with an unconditional "prefer IPv6" approach
> have been noted, and operating systems of the vintages you
> mention certainly deserved criticism. In fact this has been a
> major focus of IPv6 operational discussions, and lies behind
> things like the DNS whitelisting method, the happy-eyeballs
> work, and my own RFC 6343.

> Old news; unfortunately it means you need new o/s versions.
> Disabling 6to4 and Teredo unless they are known to be working
> well is a good start, however.

Old news perhaps, but an unavoidable consequence of this is that the
oft-repeated assertions that various systems have been "IPv6 ready for over 10
years" don't involve a useful definition of the term "ready".

				Ned



From jhutz@cmu.edu  Thu Feb 23 14:28:11 2012
Return-Path: <jhutz@cmu.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 B9A2F21F86F2; Thu, 23 Feb 2012 14:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LJ826cb+VsAG; Thu, 23 Feb 2012 14:28:11 -0800 (PST)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by ietfa.amsl.com (Postfix) with ESMTP id E500A21F86E3; Thu, 23 Feb 2012 14:28:10 -0800 (PST)
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id q1NMS8Gk016988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Feb 2012 17:28:08 -0500 (EST)
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <7489_1330034399_q1NLxvMv002895_AC54B54D-8DAA-4D98-9A1E-FDEC36612A60@cisco.com>
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <7489_1330034399_q1NLxvMv002895_AC54B54D-8DAA-4D98-9A1E-FDEC36612A60@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 23 Feb 2012 17:28:07 -0500
Message-ID: <1330036087.24486.25.camel@minbar.fac.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.196
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, jhutz@cmu.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:28:11 -0000

On Thu, 2012-02-23 at 17:00 -0500, Kim Kinnear wrote:
> > This says "MAY" leave open. That's not the complement to SHOULD close.
> 
> 	We don't really care if you keep it open or not.  Really.
> 	If you think that you will be happier, keep it open.  If
> 	you think it is simpler to close it (as I do), then close
> 	it.  Different people (different authors even!) have different
> 	ideas about how they would structure the code for this.  That's
> 	ok.  The point about all of this open/closed/multiple-operations
> 	stuff it to leave it up to the implementor.  Period.  We are
> 	not trying to tell them exactly how to implement this.   We
> 	are trying to focus on the protocol aspects, and leave understood.

That's not what SHOULD means.  An RFC2119 SHOULD is very strong; if the
spec doesn't care what an implementation does, don't use SHOULD.

-- Jeff


From dougb@dougbarton.us  Thu Feb 23 14:32:07 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C46D11E807F for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:32:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.589
X-Spam-Level: 
X-Spam-Status: No, score=-3.589 tagged_above=-999 required=5 tests=[AWL=0.010,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-twFN-S7cKW for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:32:07 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 97BBE11E8074 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:32:06 -0800 (PST)
Received: (qmail 15733 invoked by uid 399); 23 Feb 2012 22:32:00 -0000
Received: from unknown (HELO 172-17-197-151.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Feb 2012 22:32:00 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F46BE5F.1030807@dougbarton.us>
Date: Thu, 23 Feb 2012 14:31:59 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:32:07 -0000

On 02/23/2012 13:51, ned+ietf@mauve.mrochek.com wrote:
> Old news perhaps, but an unavoidable consequence of this is that the
> oft-repeated assertions that various systems have been "IPv6 ready for over 10
> years" don't involve a useful definition of the term "ready".

The OP specified "IPv4 only network." I suspect that if he had IPv6
connectivity his experience would have been quite different. I happily
use Windows XP on a dual-stack network, for example.


Doug (well, maybe "happily" is too strong a word, but you get the idea)

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From dougb@dougbarton.us  Thu Feb 23 14:33:31 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732DA11E8088 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.59
X-Spam-Level: 
X-Spam-Status: No, score=-3.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2M7o6TRn8-1f for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:33:30 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9770311E8074 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:33:30 -0800 (PST)
Received: (qmail 16915 invoked by uid 399); 23 Feb 2012 22:33:26 -0000
Received: from unknown (HELO 172-17-197-151.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Feb 2012 22:33:26 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F46BEB5.9020108@dougbarton.us>
Date: Thu, 23 Feb 2012 14:33:25 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2
MIME-Version: 1.0
To: Leif Sawyer <lsawyer@gci.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com> <4F4665A1.9010508@gmx.de>, <0FABC4E8-3B45-4B19-B2C7-B1494DEC00F4@gmail.com> <18B2C6E38A3A324986B392B2D18ABC5101D32135AB@fnb1mbx01.gci.com>
In-Reply-To: <18B2C6E38A3A324986B392B2D18ABC5101D32135AB@fnb1mbx01.gci.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:33:31 -0000

I don't *quite* go back 2 decades, but a big +1 to "all my experiences
with bolt-on security have been bad."


Doug


On 02/23/2012 10:00, Leif Sawyer wrote:
> I've got the last 2 decades of experience trying to deal with security on the network.
> 
> 95% is dealing with the peculiarities of the "bolt-on"  after-thoughts.
> 
> I would much prefer seeing security  designed-in, with the flexibility to deal with
> the future...
> 
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of RJ Atkinson [rja.lists@gmail.com]
> Sent: Thursday, February 23, 2012 8:59 AM
> To: ietf@ietf.org
> Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
> 
> On 23  Feb 2012, at 11:13 , Julian Reschke wrote:
>> On 2012-02-22 18:01, RJ Atkinson wrote:
>>> Security that works well and is practical to implement
>>> needs to be designed-in, not bolted-on later.
>>
>> I would say: security needs to be orthogonal.
> 
> There are at least 2 decades of experience that
> security has to be design-in, rather than bolted-on,
> for it to work well -- and for it to be practical
> to implement.
> 
> I hear that you don't agree, but the IETF experience
> on this specific point really is quite clear.  Add-on
> security doesn't work.
> 
> Yours,
> 
> Ran



-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From tbray@textuality.com  Thu Feb 23 14:35:25 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C1A21F874A for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:35:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.091
X-Spam-Level: 
X-Spam-Status: No, score=-3.091 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBCvSfo6ybHm for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:35:24 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 629A321F8715 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:35:24 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so2359724obb.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:35:24 -0800 (PST)
Received-SPF: pass (google.com: domain of tbray@textuality.com designates 10.60.1.230 as permitted sender) client-ip=10.60.1.230; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tbray@textuality.com designates 10.60.1.230 as permitted sender) smtp.mail=tbray@textuality.com
Received: from mr.google.com ([10.60.1.230]) by 10.60.1.230 with SMTP id 6mr1243040oep.42.1330036524119 (num_hops = 1); Thu, 23 Feb 2012 14:35:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.60.1.230 with SMTP id 6mr1092870oep.42.1330036524009; Thu, 23 Feb 2012 14:35:24 -0800 (PST)
Received: by 10.182.137.69 with HTTP; Thu, 23 Feb 2012 14:35:23 -0800 (PST)
X-Originating-IP: [76.10.184.127]
In-Reply-To: <18B2C6E38A3A324986B392B2D18ABC5101D32135AB@fnb1mbx01.gci.com>
References: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com> <4F4665A1.9010508@gmx.de> <0FABC4E8-3B45-4B19-B2C7-B1494DEC00F4@gmail.com> <18B2C6E38A3A324986B392B2D18ABC5101D32135AB@fnb1mbx01.gci.com>
Date: Thu, 23 Feb 2012 14:35:23 -0800
Message-ID: <CAHBU6it_nD8eoMNf_d2CDJ=_Vnok+T1gs2W48qDjvPuKLXj99w@mail.gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Tim Bray <tbray@textuality.com>
To: Leif Sawyer <lsawyer@gci.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnG9rgJuhNooLQ5JJErqY6jyolF8r/nDchwKyv96SebRejb4XKJO6vQlmhRLUmaFpxCaXoC
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:35:25 -0000

Your points granted, the feeling of the HTTP-using community is, by
and large, that HTTP security/authz as it stands is =93good enough=94.
Are you arguing that the security of HTTP 2.0 should be required to be
qualitatively better?  If so, someone is going to need to provide some
useful language to put in the draft charter so that we can argue about
specifics not armwaving.
-Tim

On Thu, Feb 23, 2012 at 10:00 AM, Leif Sawyer <lsawyer@gci.com> wrote:
> I've got the last 2 decades of experience trying to deal with security on=
 the network.
>
> 95% is dealing with the peculiarities of the "bolt-on" =A0after-thoughts.
>
> I would much prefer seeing security =A0designed-in, with the flexibility =
to deal with
> the future...
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of RJ Atkin=
son [rja.lists@gmail.com]
> Sent: Thursday, February 23, 2012 8:59 AM
> To: ietf@ietf.org
> Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (htt=
pbis)
>
> On 23 =A0Feb 2012, at 11:13 , Julian Reschke wrote:
>> On 2012-02-22 18:01, RJ Atkinson wrote:
>>> Security that works well and is practical to implement
>>> needs to be designed-in, not bolted-on later.
>>
>> I would say: security needs to be orthogonal.
>
> There are at least 2 decades of experience that
> security has to be design-in, rather than bolted-on,
> for it to work well -- and for it to be practical
> to implement.
>
> I hear that you don't agree, but the IETF experience
> on this specific point really is quite clear. =A0Add-on
> security doesn't work.
>
> Yours,
>
> Ran
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From dougb@dougbarton.us  Thu Feb 23 14:38:27 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3449211E808F for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:38:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.59
X-Spam-Level: 
X-Spam-Status: No, score=-3.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUXzFTZnSL0r for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:38:26 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2320811E8074 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:38:26 -0800 (PST)
Received: (qmail 21345 invoked by uid 399); 23 Feb 2012 22:38:25 -0000
Received: from unknown (HELO 172-17-197-151.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Feb 2012 22:38:25 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F46BFDF.3070703@dougbarton.us>
Date: Thu, 23 Feb 2012 14:38:23 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2
MIME-Version: 1.0
To: iesg@ietf.org
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>
In-Reply-To: <20120221181006.43AB121F87BF@ietfa.amsl.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, ietf-http-wg@w3.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:38:27 -0000

For my money it would be quite important for an HTTP 2.0 definition to
make SRV DNS records a full-fledged participant in the standard. Minimum
once a month there is someone asking for help on bind-users@ for which
the answer is, "The solution to that _would_ be SRV records, if they
were supported."

2782 was published 12 years ago this month. I suppose it can be
considered mature enough to deploy at this point? :)


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From julian.reschke@gmx.de  Thu Feb 23 14:42:14 2012
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 7CAAD11E808F for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:42:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.298
X-Spam-Level: 
X-Spam-Status: No, score=-104.298 tagged_above=-999 required=5 tests=[AWL=-1.699, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aa4yjhCJdP-k for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:42:13 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 36EF611E808E for <ietf@ietf.org>; Thu, 23 Feb 2012 14:42:13 -0800 (PST)
Received: (qmail invoked by alias); 23 Feb 2012 22:42:11 -0000
Received: from p3EE2628B.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.98.139] by mail.gmx.net (mp038) with SMTP; 23 Feb 2012 23:42:11 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/Q8NQavqXQSKj5ZdVw0ezufmP6iyJqaEJAunkEi3 WTHhNR8e3zSloC
Message-ID: <4F46C0C1.3090803@gmx.de>
Date: Thu, 23 Feb 2012 23:42:09 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CCF7D639-2059-4836-8A0D-F0C44FDF0352@gmail.com> <4F4665A1.9010508@gmx.de>, <0FABC4E8-3B45-4B19-B2C7-B1494DEC00F4@gmail.com> <18B2C6E38A3A324986B392B2D18ABC5101D32135AB@fnb1mbx01.gci.com> <4F46BEB5.9020108@dougbarton.us>
In-Reply-To: <4F46BEB5.9020108@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:42:14 -0000

On 2012-02-23 23:33, Doug Barton wrote:
> I don't *quite* go back 2 decades, but a big +1 to "all my experiences
> with bolt-on security have been bad."

bolt-on != modular/optional

If you want to "require" security in whatever comes out of this 
activity, you better define what security means, and also explain what 
keeps you from doing it right now.

Again: is there anything in the HTTP/1.1 authentication *framework* that 
prevents a "good" authentication scheme to be defined? I really like to 
know.

Best regards, Julian

From ned+ietf@mauve.mrochek.com  Thu Feb 23 14:50:42 2012
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 2C21821F8754 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:50: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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVo2bhVu-Go7 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:50:40 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA6F21F8746 for <ietf@ietf.org>; Thu, 23 Feb 2012 14:50:37 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCC0QADNTS006J12@mauve.mrochek.com> for ietf@ietf.org; Thu, 23 Feb 2012 14:50:35 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCBX82X8F400ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 23 Feb 2012 14:50:33 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCC0Q95CCK00ZUIL@mauve.mrochek.com>
Date: Thu, 23 Feb 2012 14:48:33 -0800 (PST)
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
In-reply-to: "Your message dated Thu, 23 Feb 2012 14:31:59 -0800" <4F46BE5F.1030807@dougbarton.us>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330037441; i=@mrochek.com; bh=rMTsOFvJD12Eh9b/h6MAhRxaRFYQWYnCQRReaTSXVDk=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=JRBC4mJob7xvGVwnAXlI5Nq2qF+dnGyDYi328O8H/YpEFNejuM6Q+o3pgBJCO7Q1t ICMBI6bElOokHwKeaioKtN8JsTJY/S7zMFG9dbX1hPIm+N2VUfBFEHGJSg8Nkif222 V1Y5TqRdkRw7zKcNJon1yuMjlEIYjXr66XSVuqhc=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:50:42 -0000

> On 02/23/2012 13:51, ned+ietf@mauve.mrochek.com wrote:
> > Old news perhaps, but an unavoidable consequence of this is that the
> > oft-repeated assertions that various systems have been "IPv6 ready for over 10
> > years" don't involve a useful definition of the term "ready".

> The OP specified "IPv4 only network." I suspect that if he had IPv6
> connectivity his experience would have been quite different. I happily
> use Windows XP on a dual-stack network, for example.

And systems running these old OS versions never under any circumstances move
from one network to another where connectivity conditions change. Riiight.

				Ned

From dougb@dougbarton.us  Thu Feb 23 14:55:57 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E344B21F8802 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.591
X-Spam-Level: 
X-Spam-Status: No, score=-3.591 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4KcgMSyFxVD for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:55:55 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4C42121F87FC for <ietf@ietf.org>; Thu, 23 Feb 2012 14:55:55 -0800 (PST)
Received: (qmail 9666 invoked by uid 399); 23 Feb 2012 22:55:38 -0000
Received: from unknown (HELO 172-17-197-151.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Feb 2012 22:55:38 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F46C3E9.8010603@dougbarton.us>
Date: Thu, 23 Feb 2012 14:55:37 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCC0Q95CCK00ZUIL@mauve.mrochek.com>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:55:57 -0000

On 02/23/2012 14:48, Ned Freed wrote:
>> On 02/23/2012 13:51, ned+ietf@mauve.mrochek.com wrote:
>>> Old news perhaps, but an unavoidable consequence of this is that the
>>> oft-repeated assertions that various systems have been "IPv6 ready for over 10
>>> years" don't involve a useful definition of the term "ready".
> 
>> The OP specified "IPv4 only network." I suspect that if he had IPv6
>> connectivity his experience would have been quite different. I happily
>> use Windows XP on a dual-stack network, for example.
> 
> And systems running these old OS versions never under any circumstances move
> from one network to another where connectivity conditions change. Riiight.

Brian already covered "unconditional prefer-IPv6 was a painful lesson
learned," and I'm not saying that those older systems did it right. What
I am saying is that for most values of "IPv6 Ready" which included
putting the system on an actual IPv6 network, they worked as advertised.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From ned+ietf@mauve.mrochek.com  Thu Feb 23 14:58:46 2012
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 4A13321F8842 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:58:46 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2woZc5A3qDU for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 14:58:45 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 84B8D21F883F for <ietf@ietf.org>; Thu, 23 Feb 2012 14:58:45 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCC10CL8W0017M8Y@mauve.mrochek.com> for ietf@ietf.org; Thu, 23 Feb 2012 14:58:42 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCBX82X8F400ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 23 Feb 2012 14:58:39 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCC10B11TC00ZUIL@mauve.mrochek.com>
Date: Thu, 23 Feb 2012 14:57:23 -0800 (PST)
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
In-reply-to: "Your message dated Thu, 23 Feb 2012 14:55:37 -0800" <4F46C3E9.8010603@dougbarton.us>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com> <4F46C3E9.8010603@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330037928; i=@mrochek.com; bh=ILraONDmW90J5dWsIR4NRatcDlASsZaqRzVbh+CszO8=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=fcxho6zN3Xue0olq/85tk0/GflWqPxXa4t9cb2pX16x8YgilqqRrgdhvpboIV3VTQ jkH/8OV21I0E7zgJItXIxKtak9L6XoSeeT8k19uV3AY63qSfJBHskWQ1/7B5/1yxBL 1KzrljGkm6EpulxQh51wT4cG6jIDDDQOkGId7TYA=
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:58:46 -0000

> On 02/23/2012 14:48, Ned Freed wrote:
> >> On 02/23/2012 13:51, ned+ietf@mauve.mrochek.com wrote:
> >>> Old news perhaps, but an unavoidable consequence of this is that the
> >>> oft-repeated assertions that various systems have been "IPv6 ready for over 10
> >>> years" don't involve a useful definition of the term "ready".
> >
> >> The OP specified "IPv4 only network." I suspect that if he had IPv6
> >> connectivity his experience would have been quite different. I happily
> >> use Windows XP on a dual-stack network, for example.
> >
> > And systems running these old OS versions never under any circumstances move
> > from one network to another where connectivity conditions change. Riiight.

> Brian already covered "unconditional prefer-IPv6 was a painful lesson
> learned," and I'm not saying that those older systems did it right. What
> I am saying is that for most values of "IPv6 Ready" which included
> putting the system on an actual IPv6 network, they worked as advertised.

Which brings us right back to my original point: This definition of "ready" is
operationally meaningless in many cases.

				Ned

From marka@isc.org  Thu Feb 23 15:25:06 2012
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 D206521F870A for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 15:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmFXYOQwas5w for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 15:25:06 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id D30CE21F86DA for <ietf@ietf.org>; Thu, 23 Feb 2012 15:25:05 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 69002C942D; Thu, 23 Feb 2012 23:24:53 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:968:e107:e473:6b83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 0B300216C33; Thu, 23 Feb 2012 23:24:53 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id CE9BD1DC450C; Fri, 24 Feb 2012 10:24:48 +1100 (EST)
To: ned+ietf@mauve.mrochek.com
From: Mark Andrews <marka@isc.org>
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com> <4F46C3E9.8010603@dougbarton.us> <01OCC10B11TC00ZUIL@mauve.mrochek.com>
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
In-reply-to: Your message of "Thu, 23 Feb 2012 14:57:23 -0800." <01OCC10B11TC00ZUIL@mauve.mrochek.com>
Date: Fri, 24 Feb 2012 10:24:48 +1100
Message-Id: <20120223232448.CE9BD1DC450C@drugs.dv.isc.org>
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:25:07 -0000

In message <01OCC10B11TC00ZUIL@mauve.mrochek.com>, ned+ietf@mauve.mrochek.com w
rites:
> > On 02/23/2012 14:48, Ned Freed wrote:
> > >> On 02/23/2012 13:51, ned+ietf@mauve.mrochek.com wrote:
> > >>> Old news perhaps, but an unavoidable consequence of this is that the
> > >>> oft-repeated assertions that various systems have been "IPv6 ready for 
> over 10
> > >>> years" don't involve a useful definition of the term "ready".
> > >
> > >> The OP specified "IPv4 only network." I suspect that if he had IPv6
> > >> connectivity his experience would have been quite different. I happily
> > >> use Windows XP on a dual-stack network, for example.
> > >
> > > And systems running these old OS versions never under any circumstances m
> ove
> > > from one network to another where connectivity conditions change. Riiight
> .
> 
> > Brian already covered "unconditional prefer-IPv6 was a painful lesson
> > learned," and I'm not saying that those older systems did it right. What
> > I am saying is that for most values of "IPv6 Ready" which included
> > putting the system on an actual IPv6 network, they worked as advertised.
> 
> Which brings us right back to my original point: This definition of "ready" i
> s
> operationally meaningless in many cases.
 
I contend that OS are IPv6 ready to exactly the same extent as they
are IPv4 ready.  This isn't a IPv6 readiness issue.  It is a
*application* multi-homing readiness issue.  The applications do
not handle unreachable addresses, irrespective of their type, well.
The address selection rules just made this blinding obvious when
you are on a badly configured network.

No one expect a disconnected IPv4 network to work well when the
applications are getting unreachable addresses.  Why do they expect
a IPv6 network to work well under those conditions?

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

From ned+ietf@mauve.mrochek.com  Thu Feb 23 15:50:04 2012
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 333BD21E803F for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 15:50:04 -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=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0fC8b7mUEIQp for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 15:50:03 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB7921E8037 for <ietf@ietf.org>; Thu, 23 Feb 2012 15:50:03 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCC2SXRAWG013GLF@mauve.mrochek.com> for ietf@ietf.org; Thu, 23 Feb 2012 15:50:00 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCBX82X8F400ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 23 Feb 2012 15:49:56 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCC2SVPRDW00ZUIL@mauve.mrochek.com>
Date: Thu, 23 Feb 2012 15:32:25 -0800 (PST)
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
In-reply-to: "Your message dated Fri, 24 Feb 2012 10:24:48 +1100" <20120223232448.CE9BD1DC450C@drugs.dv.isc.org>
MIME-version: 1.0
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com> <4F46C3E9.8010603@dougbarton.us> <01OCC10B11TC00ZUIL@mauve.mrochek.com> <20120223232448.CE9BD1DC450C@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330041006; i=@mrochek.com; bh=gbZb55Ff8o4ynMENzKK2O7axNAw9wbA9baUcNZGNRss=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version:	 References:To;  b=cmL7Od8764cPaHUGRRYwE/DwYkHyffq6mLiMOBQkYEE/WVdBTQ4s3UCv9rXlyaNBM CxJgqBUwxoyjEyr9mp78u+Lk7h2/pSbrkHgDG0ZPZbU86PX9SaayqpeVdcSVf0iY7x 6Fm6ko0FDkM9/Jk0zg+Zkmbx3VEiyjPGMQOmRn3Y=
Cc: ned+ietf@mauve.mrochek.com, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:50:04 -0000

> In message <01OCC10B11TC00ZUIL@mauve.mrochek.com>, ned+ietf@mauve.mrochek.com w
> rites:
> > > On 02/23/2012 14:48, Ned Freed wrote:
> > > >> On 02/23/2012 13:51, ned+ietf@mauve.mrochek.com wrote:
> > > >>> Old news perhaps, but an unavoidable consequence of this is that the
> > > >>> oft-repeated assertions that various systems have been "IPv6 ready for
> > over 10
> > > >>> years" don't involve a useful definition of the term "ready".
> > > >
> > > >> The OP specified "IPv4 only network." I suspect that if he had IPv6
> > > >> connectivity his experience would have been quite different. I happily
> > > >> use Windows XP on a dual-stack network, for example.
> > > >
> > > > And systems running these old OS versions never under any circumstances m
> > ove
> > > > from one network to another where connectivity conditions change. Riiight
> > .
> >
> > > Brian already covered "unconditional prefer-IPv6 was a painful lesson
> > > learned," and I'm not saying that those older systems did it right. What
> > > I am saying is that for most values of "IPv6 Ready" which included
> > > putting the system on an actual IPv6 network, they worked as advertised.
> >
> > Which brings us right back to my original point: This definition of "ready" i
> > s
> > operationally meaningless in many cases.
 
> I contend that OS are IPv6 ready to exactly the same extent as they
> are IPv4 ready.  This isn't a IPv6 readiness issue.  It is a
> *application* multi-homing readiness issue.  The applications do
> not handle unreachable addresses, irrespective of their type, well.
> The address selection rules just made this blinding obvious when
> you are on a badly configured network.

That's because the choice has recently been made that the place to deal with
this problem is in applications themselves. I happen to think this is an
exceptionally poor choice - the right way to do it is to provide a proper
network API that hides network selection details, rather than demanding every
application out there solve the problem separately.

And yes, I'm familiar with the line of reasoning that says applications are too
varied in their needs, or their internal environments conflict with the
necessary use of threads, or whatever. I don't buy any of it. Yes, such
applications exist, but like most things there's a sweet spot that solves a
significant fraction of the problem.

> No one expect a disconnected IPv4 network to work well when the
> applications are getting unreachable addresses.  Why do they expect
> a IPv6 network to work well under those conditions?

First, you're comparing apples and oranges. Losing all network connectivity is
very different thing from losing partial network connectivity. Nobody expects
an applications that's totally dependent on the network to work without
connectivity. That's just silly.

But with other sorts of applications, I *do* have that expectation. I often
work from places without any network connectivity using applications that
employ networking as part of their function but also do non-networked stuff,
and pretty much without exception they handle the transition fine, and have
done so for years.

Then again, I use a Mac. I have no idea what the state of play of Windows or
Linux apps is in this regard.

				Ned

From mrex@sap.com  Thu Feb 23 15:52:26 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E011821E8056 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 15:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.061
X-Spam-Level: 
X-Spam-Status: No, score=-10.061 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BAhDzve8OHIc for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 15:52:26 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 18A0221E8053 for <ietf@ietf.org>; Thu, 23 Feb 2012 15:52:25 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q1NNqOCB026370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 24 Feb 2012 00:52:24 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201202232352.q1NNqNiq011915@fs4113.wdf.sap.corp>
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses
To: marka@isc.org (Mark Andrews)
Date: Fri, 24 Feb 2012 00:52:23 +0100 (MET)
In-Reply-To: <20120223232448.CE9BD1DC450C@drugs.dv.isc.org> from "Mark Andrews" at Feb 24, 12 10:24:48 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ned+ietf@mauve.mrochek.com, ned.freed@mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:52:27 -0000

Mark Andrews wrote:
> 
> ned+ietf@mauve.mrochek.com writes:
> > 
> > Which brings us right back to my original point: This definition of 
> > "ready" is operationally meaningless in many cases.

Correct.

>  
> I contend that OS are IPv6 ready to exactly the same extent as they
> are IPv4 ready.  This isn't a IPv6 readiness issue.  It is a
> *application* multi-homing readiness issue.  The applications do
> not handle unreachable addresses, irrespective of their type, well.
> The address selection rules just made this blinding obvious when
> you are on a badly configured network.

There was *NO* multihoming involved at all.

The OS of my primary workmachine has in IPv6 protocol stack with
an extremely bogus design that pretty much precludes any kind
of migration and testing.  It delays sending DNS A lookups (in favour
to AAAA lookups) for whooping 16 seconds to DNS servers for which
only an IPv4 address is known over an interface that is IPv4-only
with a default route over that very same IPv4-only interface.
And even disabling IPv6 on the two virtual network interfaces
did not stop that non-sensical behaviour.

It just doesn't make sense to send out less DNS A lookups than
DNS AAAA lookup, and even less to delay DNS A queries for 16 seconds.

The only solution was to rip IPv6 out of the OS entirely.  Luckily
I had access to the console of the machine, because when requesting
uninstall of that (inactive) IPv6 protocol stack, the machine
immediately dropped *ALL* networking on all interfaces,
ipconfig /all gives an empty list, as if remote administration
of servers was a concept completely unknown to the OS vendor.


If there is desire for widespread adoption of some new protocol
or feature, than it is a very very very very bad idea to create
such an extremely misbehaved implementation.  And it's not like
"this is brand new and we didn't have time yet to fix this bug".


-Martin

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb 23 16:38:03 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDF411E8081 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 16:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.05
X-Spam-Level: 
X-Spam-Status: No, score=-0.05 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V1N2qIsUV3d7 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 16:38:03 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 58A4C11E8079 for <ietf@ietf.org>; Thu, 23 Feb 2012 16:38:01 -0800 (PST)
Received: (qmail 94996 invoked from network); 24 Feb 2012 00:55:34 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 24 Feb 2012 00:55:34 -0000
Message-ID: <4F46DB95.3040208@necom830.hpcl.titech.ac.jp>
Date: Fri, 24 Feb 2012 09:36:37 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com> <4F46C3E9.8010603@dougbarton.us> <01OCC10B11TC00ZUIL@mauve.mrochek.com> <20120223232448.CE9BD1DC450C@drugs.dv.isc.org>
In-Reply-To: <20120223232448.CE9BD1DC450C@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:38:03 -0000

Mark Andrews wrote:

>>> Brian already covered "unconditional prefer-IPv6 was a painful lesson
>>> learned," and I'm not saying that those older systems did it right.

You learned a wrong lesson, then.

The essential problem is that there is half hearted support
for handling multiple addresses.

It is not an operational problem but a fundamental defects
of protocols.

> I contend that OS are IPv6 ready to exactly the same extent as they
> are IPv4 ready.  This isn't a IPv6 readiness issue.  It is a
> *application* multi-homing readiness issue.  The applications do
> not handle unreachable addresses, irrespective of their type, well.

In part, it is an application problem. However, it is also an
IP layer problem.

> The address selection rules just made this blinding obvious when
> you are on a badly configured network.

The half hearted address selection rules will keep causing
this kind of problems, until IPv6 specification is
fundamentally fixed.

> No one expect a disconnected IPv4 network to work well when the
> applications are getting unreachable addresses.  Why do they expect
> a IPv6 network to work well under those conditions?

With proper IP layer support, which is lacking, which means
IPv6 specification is not ready to handle multiple addresses,
which means hosts are not IPv6 ready to handle multiple
addresses, we can expect applications work well if one of
an address among many works and rest of the addresses are
unreachable.

						Masataka Ohta

PS

IPv4, of course, is not ready to handle multiple addresses
properly, which causes some problems for multihomed hosts.

But it is not a serious problem because IPv4 hosts do not
have to have IPv6 addresses.

From brian.e.carpenter@gmail.com  Thu Feb 23 16:42:03 2012
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 ABDD111E8094 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 16:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.508
X-Spam-Level: 
X-Spam-Status: No, score=-103.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pcJ4kXBgxj2R for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 16:42:03 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id E177111E8086 for <ietf@ietf.org>; Thu, 23 Feb 2012 16:42:02 -0800 (PST)
Received: by eaal12 with SMTP id l12so752729eaa.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 16:42:02 -0800 (PST)
Received-SPF: pass (google.com: domain of brian.e.carpenter@gmail.com designates 10.14.95.8 as permitted sender) client-ip=10.14.95.8;
Authentication-Results: mr.google.com; spf=pass (google.com: domain of brian.e.carpenter@gmail.com designates 10.14.95.8 as permitted sender) smtp.mail=brian.e.carpenter@gmail.com; dkim=pass header.i=brian.e.carpenter@gmail.com
Received: from mr.google.com ([10.14.95.8]) by 10.14.95.8 with SMTP id o8mr2077965eef.111.1330044122210 (num_hops = 1); Thu, 23 Feb 2012 16:42:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sJBDnqW8e9ypVSHOpHK5cPozGRBcoAANxV0hbjeuDFw=; b=flWksEu1h0wJlVifbJxf9KReLMPeHwjLQ4EqWnfk23kY5KbVnCr2F1ezJeGxELVwfI 6sZuUp9swyb5SKbUNMpTphL6Ui/J7xSldpywSkiK5O4Ttapx3I1bT2guAVM+n3Cwdurd 4LY9MdEHdPOyFtDDEnfD5AqM4as8pcTHHq50E=
Received: by 10.14.95.8 with SMTP id o8mr1601987eef.111.1330044122084; Thu, 23 Feb 2012 16:42:02 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id n52sm11577354eea.5.2012.02.23.16.41.58 (version=SSLv3 cipher=OTHER); Thu, 23 Feb 2012 16:42:01 -0800 (PST)
Message-ID: <4F46DCD1.40608@gmail.com>
Date: Fri, 24 Feb 2012 13:41:53 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>	<4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com>	<4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com>	<4F46C3E9.8010603@dougbarton.us> <01OCC10B11TC00ZUIL@mauve.mrochek.com>	<20120223232448.CE9BD1DC450C@drugs.dv.isc.org> <01OCC2SVPRDW00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCC2SVPRDW00ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:42:03 -0000

On 2012-02-24 12:32, ned+ietf@mauve.mrochek.com wrote:
>> In message <01OCC10B11TC00ZUIL@mauve.mrochek.com>, ned+ietf@mauve.mrochek.com w
>> rites:

...
>> I contend that OS are IPv6 ready to exactly the same extent as they
>> are IPv4 ready.  This isn't a IPv6 readiness issue.  It is a
>> *application* multi-homing readiness issue.  The applications do
>> not handle unreachable addresses, irrespective of their type, well.
>> The address selection rules just made this blinding obvious when
>> you are on a badly configured network.
> 
> That's because the choice has recently been made that the place to deal with
> this problem is in applications themselves. I happen to think this is an
> exceptionally poor choice - the right way to do it is to provide a proper
> network API that hides network selection details, rather than demanding every
> application out there solve the problem separately.

I wish, I *really* wish, that it worked. Making it work, by one technique
or another, is not a new topic, even when only IPv4 connectivity
was at issue. Those things are often called 'connection managers'
and are largely based on trial and error or reachability probes.

Then there are efforts like SCTP and MPTCP to solve it in the transport
layer, and shim6 to solve it in the network layer (for IPv6 only, but the
issue is the same). These solutions are also essentially based on
trial and error, and need to be supported by both hosts.

> And yes, I'm familiar with the line of reasoning that says applications are too
> varied in their needs, or their internal environments conflict with the
> necessary use of threads, or whatever. I don't buy any of it. Yes, such
> applications exist, but like most things there's a sweet spot that solves a
> significant fraction of the problem.

That's been part of Java for some years (since 1.5 iirc). But it
*doesn't* solve precisely the problem that Martin was describing,
where a stack falsely believes that it has IPv6 connectivity but
in fact it doesn't. In that sort of situation, short of manual
intervention, something like happy-eyeballs seems to be needed in
order for the application to fix things up when the network layer
is confused.

And no, I'm not happy with this, but it seems to be reality.

   Brian

From marka@isc.org  Thu Feb 23 16:51:52 2012
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 86FAC11E80B2 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 16:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XAYELf2IpkK for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 16:51:51 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id DA80211E80A3 for <ietf@ietf.org>; Thu, 23 Feb 2012 16:51:22 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 229685F9899; Fri, 24 Feb 2012 00:51:05 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:968:e107:e473:6b83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 0C835216C31; Fri, 24 Feb 2012 00:51:03 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 310671DC4ADA; Fri, 24 Feb 2012 11:50:55 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201202232352.q1NNqNiq011915@fs4113.wdf.sap.corp>
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses
In-reply-to: Your message of "Fri, 24 Feb 2012 00:52:23 BST." <201202232352.q1NNqNiq011915@fs4113.wdf.sap.corp>
Date: Fri, 24 Feb 2012 11:50:54 +1100
Message-Id: <20120224005055.310671DC4ADA@drugs.dv.isc.org>
Cc: ned+ietf@mauve.mrochek.com, ned.freed@mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:51:52 -0000

In message <201202232352.q1NNqNiq011915@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > ned+ietf@mauve.mrochek.com writes:
> > > 
> > > Which brings us right back to my original point: This definition of 
> > > "ready" is operationally meaningless in many cases.
> 
> Correct.
> 
> >  
> > I contend that OS are IPv6 ready to exactly the same extent as they
> > are IPv4 ready.  This isn't a IPv6 readiness issue.  It is a
> > *application* multi-homing readiness issue.  The applications do
> > not handle unreachable addresses, irrespective of their type, well.
> > The address selection rules just made this blinding obvious when
> > you are on a badly configured network.
> 
> There was *NO* multihoming involved at all.

What addresses were there on the loopback interface?  If there were
IPv4 and IPv6 addresses then it was dual stack multi-homed machine.
Applications need to work over the loopback interface as much as
they need to work over a external interface.  Having a IPv4 address
on the loopback interface is NOT a given.  A application MUST work
over the loopback interface when it does not have a IPv4 address.

I've yet to work on a machine that was not multi-homed to some
extent.  All of the machines I've worked on in the last 25 years
have had multiple interfaces.

> The OS of my primary workmachine has in IPv6 protocol stack with
> an extremely bogus design that pretty much precludes any kind
> of migration and testing.  It delays sending DNS A lookups (in favour
> to AAAA lookups) for whooping 16 seconds to DNS servers for which
> only an IPv4 address is known over an interface that is IPv4-only
> with a default route over that very same IPv4-only interface.
> And even disabling IPv6 on the two virtual network interfaces
> did not stop that non-sensical behaviour.

If there is a 16 second delay you can blame the authoritative server
adminstrators for either installing a non RFC compliant nameserver
or misconfiguring a delegation which is detectable by looking at
the negative response.  The returned records are inconsistent with
the delegation.  DNSSEC however will help fix this as broken
delegation like this don't work for positive signed answers either
with a general purpose nameserver whereas that can be overlooked
with simple testing in a non DNSSEC environment.

A RFC 1035 compliant nameserver is quite capable of answering "I
have no type 28 records at this name" or this name doesn't exist
to a type 28 query.

A RFC 1035 recursive server should also handle the lookup and return
of type 28 records as opaque blobs of data.  This is why compression
pointers are only supported on "well known types" in RFC 1035 so
it could handle records that it doesn't know the internal structure
of.

The only thing a RFC 1035 server can't do is serve AAAA records.
Serving AAAA records requires a newer server.

Secondly there is no evidence that asking for AAAA records is due to
a OS problem or a application problem.  Without reading the source
code there is no way to know.

> It just doesn't make sense to send out less DNS A lookups than
> DNS AAAA lookup, and even less to delay DNS A queries for 16 seconds.

Actually it can make sense to make AAAA queries. Knowing whether
there are AAAA addresses or not can change how you behave when you
can't reach the machine over IPv4 assuming there are A records.

> The only solution was to rip IPv6 out of the OS entirely.  Luckily
> I had access to the console of the machine, because when requesting
> uninstall of that (inactive) IPv6 protocol stack, the machine
> immediately dropped *ALL* networking on all interfaces,
> ipconfig /all gives an empty list, as if remote administration
> of servers was a concept completely unknown to the OS vendor.
> 
> If there is desire for widespread adoption of some new protocol
> or feature, than it is a very very very very bad idea to create
> such an extremely misbehaved implementation.  And it's not like
> "this is brand new and we didn't have time yet to fix this bug".

Making a AAAA should add 1 round trip lookup,  in most cases that's
much less than 200ms to the startup of a application assuming no
caching.  If there is caching or overlapping queries the additional
time can drop to nano seconds.

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

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb 23 17:06:13 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2820811E808C for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.051
X-Spam-Level: 
X-Spam-Status: No, score=-0.051 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08qWOTRoNN1M for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:06:12 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 5A15111E808A for <ietf@ietf.org>; Thu, 23 Feb 2012 17:06:12 -0800 (PST)
Received: (qmail 95228 invoked from network); 24 Feb 2012 01:24:05 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 24 Feb 2012 01:24:05 -0000
Message-ID: <4F46E243.206@necom830.hpcl.titech.ac.jp>
Date: Fri, 24 Feb 2012 10:05:07 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues with "prefer IPv6" [Re: Variable length internet addresses in TCP/IP: history]
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp> <4F46B06B.6010908@gmail.com> <01OCBYZLOQEQ00ZUIL@mauve.mrochek.com> <4F46BE5F.1030807@dougbarton.us> <01OCC0Q95CCK00ZUIL@mauve.mrochek.com> <4F46C3E9.8010603@dougbarton.us> <01OCC10B11TC00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCC10B11TC00ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:06:13 -0000

ned+ietf@mauve.mrochek.com wrote:

> This definition of "ready" is operationally meaningless in many cases.

The meaningful question is whether we have to modify code or not.

If we have to, a host is not ready. And, if it is not an
implementation problem, protocols must be fixed.

If we don't have to, it's an operational issue.

						Masataka Ohta

From fielding@gbiv.com  Thu Feb 23 17:13:48 2012
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B850911E80A2; Thu, 23 Feb 2012 17:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.799
X-Spam-Level: 
X-Spam-Status: No, score=-105.799 tagged_above=-999 required=5 tests=[AWL=-3.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-eYhqGPhpiP; Thu, 23 Feb 2012 17:13:48 -0800 (PST)
Received: from homiemail-a24.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id E853011E808A; Thu, 23 Feb 2012 17:13:47 -0800 (PST)
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id A98E92C8057; Thu, 23 Feb 2012 17:13:47 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=gbiv.com; b=nNEhS0e+pXfKemB/ SKTgI1CJBGVYRH4bFvJH5+gKo/iMVnWLQ8F3Yn5CHYFBAxrjUpMeNKoh2aaQG3P4 y2xoBmaMz3olsgDi22Q4FaDvyoSeJT96YnTpH3PKZK0kDS7+WjYvl43pumevLtyk n+kdkN5uQjtyhx0cX4cpoNVJ4Pk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=WcqGEOrtxyKrqTXbxPP8KcOhpvw=; b=YniZvqgDZ2guK6GNWsQOE8FMGqT4 lg4MvbvSj5GFP+uDQqfUxMjNk8Mv7YtCsSOkqFC1U6Aucdw0WFZpoAc1bHXdElW3 NTrQMfPhMZXOJ7mOSAvvq9qP/7BZcLj076unLP+l5U99zcXIaytSOHBxh6ptBEbX BB+JtBOh13iLVQQ=
Received: from [10.134.89.83] (unknown [75.103.10.98]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id 7C9DC2C8055;  Thu, 23 Feb 2012 17:13:47 -0800 (PST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <4F452842.3050905@stpeter.im>
Date: Thu, 23 Feb 2012 17:13:53 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
Cc: ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:13:48 -0000

On Feb 22, 2012, at 9:39 AM, Peter Saint-Andre wrote:

> On 2/22/12 10:31 AM, Paul Hoffman wrote:
>> The earnest calls for better authentication on this thread appear to
>> ignore the fact that the very things that are being requested were
>> put out of scope for the websec WG in their charter. I hope that no
>> one things that a WG in the Applications Area will be better equipped
>> to come up with a better authentication mechanism than one in the
>> Security Area.
> 
> The WebSec WG is in the Applications Area.
> 
>> Asking the HTTPheads to guess what the securityheads might want is
>> not a good way to design HTTP 2.0.
> 
> Probably not.
> 
>> Proposal: leave the httpbis WG charter as-is and re-charter the
>> websec WG to consider what is needed in the HTTP authentication
>> model. Later, recharter the websec WG to, you know, actually do the
>> security work for authentication.
> 
> Or charter a separate WG to focus on HTTP authentication. (You might
> recall that the BoF leading to formation of the WebSec WG was entitled
> HASMAT = "HTTP Application Security Minus Authentication and Transport"
> or somesuch.)

Please understand that this exact same discussion was had in 1994 and
the IESG decided that the applications area couldn't possibly do this
work on their own, so they created a security area working group to
handle it.  That HTTP Security group, which was dominated by folks who
did not have any implementations of HTTP, decided to ignore the problem
for which they were chartered and instead invented SHTTP.

More importantly, the effect of that decision was that the people who
get work done at the IETF were prevented from improving HTTP's auth
mechanisms because it was out of scope, while the people who had it
in scope had no corresponding incentive to get it DONE.

Every time this topic comes up, people want to shove it off to some
other working group that is somehow going to magically get off its
collective ass and do real work.  Why?  It doesn't work.  It never
has worked.  We've gone through four iterations now of revising HTTP,
each one starting off with the same discussion, and each one concluding
that auth would be better owned by someone else.

There is nobody else.

How many times do we have to do this before we declare insanity?
I don't care how much risk it adds to the HTTP charter.  They are
all just meaningless deadlines anyway.  If we want HTTP to have
something other than Basic (1993) and Digest (1995) authentication,
then it had better be part of *this* charter so that the proposals
can address them.

....Roy

From tbray@textuality.com  Thu Feb 23 17:18:57 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCCD811E8099 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMhpxMZhv86I for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:18:57 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5881521F871C for <ietf@ietf.org>; Thu, 23 Feb 2012 17:18:57 -0800 (PST)
Received: by obbwd15 with SMTP id wd15so2527227obb.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 17:18:57 -0800 (PST)
Received-SPF: pass (google.com: domain of tbray@textuality.com designates 10.60.21.134 as permitted sender) client-ip=10.60.21.134; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tbray@textuality.com designates 10.60.21.134 as permitted sender) smtp.mail=tbray@textuality.com
Received: from mr.google.com ([10.60.21.134]) by 10.60.21.134 with SMTP id v6mr34078oee.52.1330046337099 (num_hops = 1); Thu, 23 Feb 2012 17:18:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.60.21.134 with SMTP id v6mr29885oee.52.1330046336993; Thu, 23 Feb 2012 17:18:56 -0800 (PST)
Received: by 10.182.137.69 with HTTP; Thu, 23 Feb 2012 17:18:56 -0800 (PST)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com>
Date: Thu, 23 Feb 2012 17:18:56 -0800
Message-ID: <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Tim Bray <tbray@textuality.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlEbLlm1PFADUdmudLzOUG2QnQftr2tlEwYewQgPBpyDjeaS15zZb7sm/hvb+qSE4ZKsaha
Cc: The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:18:58 -0000

On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fielding <fielding@gbiv.com> wrote:

> How many times do we have to do this before we declare insanity?
> I don't care how much risk it adds to the HTTP charter. =A0They are
> all just meaningless deadlines anyway. =A0If we want HTTP to have
> something other than Basic (1993) and Digest (1995) authentication,
> then it had better be part of *this* charter so that the proposals
> can address them.

Well, Digest already isn't used by anyone :)

Seriously, someone needs to propose some charter language or this
discussion is a no-op.  -Tim

From paul.hoffman@vpnc.org  Thu Feb 23 17:23:47 2012
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 A17F621E802B; Thu, 23 Feb 2012 17:23:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.637
X-Spam-Level: 
X-Spam-Status: No, score=-102.637 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cczlZoz-Bmvd; Thu, 23 Feb 2012 17:23:47 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 15F8A21E802A; Thu, 23 Feb 2012 17:23:47 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1O1NjS8045795 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 Feb 2012 18:23:46 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com>
Date: Thu, 23 Feb 2012 17:23:45 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FBC37226-CDB3-4669-8E39-E9CE8A1681C1@vpnc.org>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
X-Mailer: Apple Mail (2.1257)
Cc: ietf-http-wg@w3.org, The IESG <iesg@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:23:47 -0000

On Feb 23, 2012, at 5:13 PM, Roy T. Fielding wrote:

> I don't care how much risk it adds to the HTTP charter.  They are
> all just meaningless deadlines anyway.  If we want HTTP to have
> something other than Basic (1993) and Digest (1995) authentication,
> then it had better be part of *this* charter so that the proposals
> can address them.


If only it were that simple. If the answer is "design an HTTP auth =
mechanism that is better than Digest", then this is a tractable goal. If =
it is "get IETF consensus on that auth mechanism", then it isn't. The =
latter has proven to be impossible because people say (possibly rightly) =
that web developers don't want auth mechanisms that use the browser =
chrome: they want auth in HTML, and anything that relies on the browser =
chrome is insufficient.

Notice how the topic changed from "HTTP" to "web" for the security =
discussion but not for the httpbis charter discussion? That topic-change =
has derailed the HTTP authentication discussions at recent (and =
not-so-recent) IETF meetings.

If the charter has "develop HTTP authentication mechanisms beyond =
Digest", that's great: we already have seen about five proposals in the =
past few years for those, some of them with security analyses. If the =
charter says "...and specify one that is mandatory to implement", that =
seems prone to consensus failure because of religion about =
zero-knowledge proofs versus operational simplicity, but I would be =
overjoyed to be wrong about that.

--Paul Hoffman


From fielding@gbiv.com  Thu Feb 23 17:24:03 2012
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FAE821E802D; Thu, 23 Feb 2012 17:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.456
X-Spam-Level: 
X-Spam-Status: No, score=-105.456 tagged_above=-999 required=5 tests=[AWL=-2.857, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P71zTKGMhqkG; Thu, 23 Feb 2012 17:24:02 -0800 (PST)
Received: from homiemail-a96.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 464C221E8018; Thu, 23 Feb 2012 17:24:02 -0800 (PST)
Received: from homiemail-a96.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTP id 109373B800D; Thu, 23 Feb 2012 17:24:02 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=gbiv.com; b=a+LKSGo/mrL1N8k3 NgpLMq6M5RbB08pSEsYPD9zuc1XtT0YtIqZMKMJEwMqviR2c9jSw1h/f5DW5TBKJ brGpJGEsfAfx7ucbPnJ96aaJm2DB6xtZatM3N8aqNGQ1kLVpEXZO/a95escjAxD6 woVXzv0rRNzAKl0xuFgBZ//gYdk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=FVrutAdiCHaLsSY//ra40BQ8oBw=; b=GfhEw76hhqKfjQak+sQFDujrqZBR KDr1sVy66GGqOMjIR4/iHWsBpT8YC93EsE960JknMxgz2sy1PUEgcKZC+C6rRh2x pcDRCzaa3h1G3qjKoEcS33tyw65TU6HscyFLLwvfzBH9sJA3s45JrjbIFnIGWDoo EUnHrT64O8MpRKo=
Received: from [10.134.89.83] (unknown [75.103.10.98]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTPSA id 9C0C93B800C;  Thu, 23 Feb 2012 17:24:01 -0800 (PST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com>
Date: Thu, 23 Feb 2012 17:24:07 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1257)
Cc: The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:24:03 -0000

On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
> On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fielding <fielding@gbiv.com> wrote:
> 
>> How many times do we have to do this before we declare insanity?
>> I don't care how much risk it adds to the HTTP charter.  They are
>> all just meaningless deadlines anyway.  If we want HTTP to have
>> something other than Basic (1993) and Digest (1995) authentication,
>> then it had better be part of *this* charter so that the proposals
>> can address them.
> 
> Well, Digest already isn't used by anyone :)

A popular misconception because it works unseen.  See tools.ietf.org

> Seriously, someone needs to propose some charter language or this
> discussion is a no-op.  -Tim

"Proposals for new HTTP authentication schemes are in scope."

....Roy

From tbray@textuality.com  Thu Feb 23 17:34:23 2012
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9A821F8498 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.56
X-Spam-Level: 
X-Spam-Status: No, score=-3.56 tagged_above=-999 required=5 tests=[AWL=-0.583,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fSe5GWJz44cY for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:34:23 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5F721F85E7 for <ietf@ietf.org>; Thu, 23 Feb 2012 17:34:22 -0800 (PST)
Received: by pbcwz7 with SMTP id wz7so2101777pbc.31 for <ietf@ietf.org>; Thu, 23 Feb 2012 17:34:22 -0800 (PST)
Received-SPF: pass (google.com: domain of tbray@textuality.com designates 10.68.226.231 as permitted sender) client-ip=10.68.226.231; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tbray@textuality.com designates 10.68.226.231 as permitted sender) smtp.mail=tbray@textuality.com
Received: from mr.google.com ([10.68.226.231]) by 10.68.226.231 with SMTP id rv7mr1453533pbc.59.1330047262501 (num_hops = 1); Thu, 23 Feb 2012 17:34:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.226.231 with SMTP id rv7mr1184659pbc.59.1330047262429; Thu, 23 Feb 2012 17:34:22 -0800 (PST)
Received: by 10.142.246.6 with HTTP; Thu, 23 Feb 2012 17:34:22 -0800 (PST)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
Date: Thu, 23 Feb 2012 17:34:22 -0800
Message-ID: <CAHBU6iu1_8P6d5y1EnEZKgX6aa2OU6qUUaWoFsbn2ovujFBurA@mail.gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Tim Bray <tbray@textuality.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnFabNkfMgVKO55mYbyz+FnHbaVBR+sV2T6dK5pK6dFXDiiJeWc4ApmLGzEA9ds1jLdQuEM
Cc: The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, ietf-http-wg@w3.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:34:23 -0000

On Thu, Feb 23, 2012 at 5:24 PM, Roy T. Fielding <fielding@gbiv.com> wrote:

>> Seriously, someone needs to propose some charter language or this
>> discussion is a no-op. =A0-Tim
>
> "Proposals for new HTTP authentication schemes are in scope."

+1

I don=92t think we=92ll get one, but in the unlikely event someone can
build consensus for something, there=92s no reason to brand it as
out-of-bounds.  -T

From marka@isc.org  Thu Feb 23 17:43:29 2012
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 4DB8421E802D for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPBZBikVY1LX for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 17:43:28 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 7491021E802C for <ietf@ietf.org>; Thu, 23 Feb 2012 17:43:25 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id ECC48C9476; Fri, 24 Feb 2012 01:43:11 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:968:e107:e473:6b83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 916F6216C36; Fri, 24 Feb 2012 01:43:11 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 46B201DC58AE; Fri, 24 Feb 2012 12:43:05 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>
Subject: Re: Variable length internet addresses in TCP/IP: history
In-reply-to: Your message of "Thu, 23 Feb 2012 17:51:59 BST." <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>
Date: Fri, 24 Feb 2012 12:43:04 +1100
Message-Id: <20120224014305.46B201DC58AE@drugs.dv.isc.org>
Cc: braden@isi.edu, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:43:29 -0000

In message <201202231651.q1NGpxgL017137@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Bob Hinden wrote:
> > 
> > Martin Rex wrote:
> > > 
> > > With a fully backwards compatible transparent addressing scheme,
> > > a much larger fraction of the nodes would have switched to actively
> > > use IPv6 many years ago.
> > 
> > Right, just like they could have deployed dual stack many years ago too.
> 
> Just two days ago I had an extremeley disappointing experience with IPv6.
> Windows XP 64-bit (aka Win2003sp2) on a local network with a private
> DNS universe, IPv4 only network, Windows IPv6 protocol stack installed
> but IPv6 active only on the two virtual network interfaces of VMware.
> 
> Somehow the DNS servers configured in the network settings had performed
> only a partial zone reload and were replying only to some queries,
> failing some DNS queries with server failure or timeout,
> and one DNS zone had become completely invisible.
> 
> I noticed the problem suddenly during work because every new connection
> took ~16 seconds delay to complete.  Wondering what was wrong, I started
> wireshark.
> 
> I saw Windows2003 send out 23 DNS lookups for AAAA records for the
> requested hostname over the course of 16 seconds (some of which returned
> server failure, some of which failed with no such name),
> until Windows 2003 finally decided to also try a DNS A query--which got
> immediately successfully answered and the connection was established.
> The delay affected each and every connection attempt, even when contacting
> the same host repeatedly (although there is a DNScache service running...).
> 
> Disabling IPv6 on all network adapters did not stop this Windows AAAA frenzy,
> I had to actually uninstall the IPv6 protocol stack (an action which
> immediately kills *ALL* network connectivity of the machine and requires
> a reboot to recover...) for this AAAA nonsense to end.
> 
> During the past few years I had two similar encounters with sudden severe
> connectivity problems on a Windows XP and a Linux installation, and
> both times, the problem disappeared when I disabled IPv6.
> 
> It is also significantly easier to configure the firewall for IPv4-only...
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

We (ISC) learned a long time ago (last century) that partial DNS
service for a zone is worse than total failure for a zone.  By
totally failing a zone on error it gets fixed instead of trying to
limp by on partial service.

I also suspect the search algorithm is not stopping on NOERROR
NODATA or SERVFAIL.  Searches really should stop on both those
conditions.  By stopping I mean not going onto the next element
in the search list without getting a NXDOMAIN response.  You
can ask multiple servers on SERVFAIL.

I've been arguing this for around 10+ years.

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

From fielding@gbiv.com  Thu Feb 23 18:21:18 2012
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D77621E8018; Thu, 23 Feb 2012 18:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.266
X-Spam-Level: 
X-Spam-Status: No, score=-105.266 tagged_above=-999 required=5 tests=[AWL=-2.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLtqg6khRdrq; Thu, 23 Feb 2012 18:21:17 -0800 (PST)
Received: from homiemail-a64.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id 90D8421E8015; Thu, 23 Feb 2012 18:21:16 -0800 (PST)
Received: from homiemail-a64.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTP id CF0D2438072; Thu, 23 Feb 2012 18:21:15 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to; q=dns; s=gbiv.com; b=dEwKUf4Z6ij1+e+X g3sE/i9l2xjclJJgoHnnwJLbAN+VtEZH4pmjcqaNM5v8u9rAdDK8IDr9WbcpExB0 7uA1fWz4LgUPerkoQct+l6HZDNTdWQC30NxcPMazZexczkzKkXFPeiiXSLRbkZvJ xzgGhRrGLSE0RKnQFh+PEQbS8cs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=baVk1ZboZ7v/pgCAUGni+NgY0bA=; b=2YNOywKcopT8iruELojGNwF4vS4x ahnxOQwrCf8DrGBs5N69eWs/xuT9/9tQvQ7csLHYQqwWSKmfgIH2efqf9ijZI53r b1qZ+GxVndGwGJsoXqlkWKzwqNQ0CwIjqHdUqynQTvjVNyxW1AJ7zL+SNjjxPYM+ rq0jRn8iVXXLDmI=
Received: from [10.134.89.83] (unknown [75.103.10.98]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a64.g.dreamhost.com (Postfix) with ESMTPSA id 9882343806C;  Thu, 23 Feb 2012 18:21:15 -0800 (PST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <FBC37226-CDB3-4669-8E39-E9CE8A1681C1@vpnc.org>
Date: Thu, 23 Feb 2012 18:21:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <916D055A-DAE4-47D9-AE8D-4261EA1DA59F@gbiv.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <FBC37226-CDB3-4669-8E39-E9CE8A1681C1@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1257)
Cc: ietf-http-wg@w3.org, The IESG <iesg@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:21:18 -0000

On Feb 23, 2012, at 5:23 PM, Paul Hoffman wrote:
> On Feb 23, 2012, at 5:13 PM, Roy T. Fielding wrote:
>=20
>> I don't care how much risk it adds to the HTTP charter.  They are
>> all just meaningless deadlines anyway.  If we want HTTP to have
>> something other than Basic (1993) and Digest (1995) authentication,
>> then it had better be part of *this* charter so that the proposals
>> can address them.
>=20
>=20
> If only it were that simple. If the answer is "design an HTTP auth =
mechanism that is better than Digest", then this is a tractable goal. If =
it is "get IETF consensus on that auth mechanism", then it isn't. The =
latter has proven to be impossible because people say (possibly rightly) =
that web developers don't want auth mechanisms that use the browser =
chrome: they want auth in HTML, and anything that relies on the browser =
chrome is insufficient.

I don't need IETF consensus, just rough consensus and running code,
and I have no need to satisfy folks who think the Web is a browser.
The hard part is deploying anything that is incompatible with
already-deployed clients without letting them fall back to basic.

It is a trivial problem compared to choosing a new, non-MIME syntax.

What "web developers" want is based on what they can do today,
not what they can expect from an entirely new protocol.

> Notice how the topic changed from "HTTP" to "web" for the security =
discussion but not for the httpbis charter discussion? That topic-change =
has derailed the HTTP authentication discussions at recent (and =
not-so-recent) IETF meetings.


It didn't derail them.  They were not on any rails to begin with.

The problem with defining security in a separate group without
shipping implementations is that there is no need to compromise,
no need to identify and resolve specific use cases, and no need
to do something better than nothing.

If we add a requirement to HTTP/2.0 that user authentication MUST
be accomplished via a mechanism not subject to UI spoofing,
then that's what people will implement (if they implement at all).
The protocol can give the server all the control it wants over the
display of a background or separate window explaining what to do
in that other mechanism-not-subject-to-spoofing.  Give people just
enough rope to solve that problem without hanging themselves, and
the rest of HTTP (non-browser clients) can implement right now.

> If the charter has "develop HTTP authentication mechanisms beyond =
Digest", that's great: we already have seen about five proposals in the =
past few years for those, some of them with security analyses. If the =
charter says "...and specify one that is mandatory to implement", that =
seems prone to consensus failure because of religion about =
zero-knowledge proofs versus operational simplicity, but I would be =
overjoyed to be wrong about that.

I'd be happy with several imperfect mechanisms with differing
trade-offs that can be implemented in parallel.

....Roy


From mnot@mnot.net  Thu Feb 23 18:47:29 2012
Return-Path: <mnot@mnot.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 C48F611E8073; Thu, 23 Feb 2012 18:47:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.872
X-Spam-Level: 
X-Spam-Status: No, score=-104.872 tagged_above=-999 required=5 tests=[AWL=-2.273, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8+jkZyOEzH8; Thu, 23 Feb 2012 18:47:29 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDE221F85B5; Thu, 23 Feb 2012 18:47:28 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.53.7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4B8AA22E1EB; Thu, 23 Feb 2012 21:47:20 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
Date: Fri, 24 Feb 2012 13:47:18 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FE51BFF-EB61-40FA-8882-5E8AA4783B27@mnot.net>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
To: Roy T. Fielding <fielding@gbiv.com>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:47:29 -0000

On 24/02/2012, at 12:24 PM, Roy T. Fielding wrote:

> On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
>> On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fielding <fielding@gbiv.com> =
wrote:
>>=20
>>> How many times do we have to do this before we declare insanity?
>>> I don't care how much risk it adds to the HTTP charter.  They are
>>> all just meaningless deadlines anyway.  If we want HTTP to have
>>> something other than Basic (1993) and Digest (1995) authentication,
>>> then it had better be part of *this* charter so that the proposals
>>> can address them.
>>=20
>> Well, Digest already isn't used by anyone :)
>=20
> A popular misconception because it works unseen.  See tools.ietf.org
>=20
>> Seriously, someone needs to propose some charter language or this
>> discussion is a no-op.  -Tim
>=20
> "Proposals for new HTTP authentication schemes are in scope."

No one has said they're out of scope; this discussion has been about =
whether -- at this point in time, before we have proposals -- we require =
the outcome to jump through some particular hoop regarding security.=20


Cheers,



--
Mark Nottingham   http://www.mnot.net/




From marka@isc.org  Thu Feb 23 18:55:05 2012
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 73E2B11E80A2; Thu, 23 Feb 2012 18:55:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mbHTpUAcGEoB; Thu, 23 Feb 2012 18:55:05 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 08A1E21F8661; Thu, 23 Feb 2012 18:54:52 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 77264C9468; Fri, 24 Feb 2012 02:54:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:968:e107:e473:6b83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 26E62216C31; Fri, 24 Feb 2012 02:54:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 00F1A1DC6AEB; Fri, 24 Feb 2012 13:54:33 +1100 (EST)
To: Doug Barton <dougb@dougbarton.us>
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-reply-to: Your message of "Thu, 23 Feb 2012 14:38:23 -0800." <4F46BFDF.3070703@dougbarton.us>
Date: Fri, 24 Feb 2012 13:54:32 +1100
Message-Id: <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org>
Cc: mnot@mnot.net, IETF Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:55:05 -0000

In message <4F46BFDF.3070703@dougbarton.us>, Doug Barton writes:
> For my money it would be quite important for an HTTP 2.0 definition to
> make SRV DNS records a full-fledged participant in the standard. Minimum
> once a month there is someone asking for help on bind-users@ for which
> the answer is, "The solution to that _would_ be SRV records, if they
> were supported."
> 
> 2782 was published 12 years ago this month. I suppose it can be
> considered mature enough to deploy at this point? :)

+1000

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

From narten@us.ibm.com  Thu Feb 23 21:53:10 2012
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 B1E2B21F86CE for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 21:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.455
X-Spam-Level: 
X-Spam-Status: No, score=-109.455 tagged_above=-999 required=5 tests=[AWL=1.144, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EJg7xF5rjTaW for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2012 21:53:09 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 24FEC21F8738 for <ietf@ietf.org>; Thu, 23 Feb 2012 21:53:08 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 24 Feb 2012 00:53:07 -0500
Received: from d01dlp01.pok.ibm.com (9.56.224.56) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 24 Feb 2012 00:53:05 -0500
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id C57CB38C8052 for <ietf@ietf.org>; Fri, 24 Feb 2012 00:53:04 -0500 (EST)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q1O5r4bP3465318 for <ietf@ietf.org>; Fri, 24 Feb 2012 00:53:04 -0500
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q1O5r4Lp005302 for <ietf@ietf.org>; Fri, 24 Feb 2012 03:53:04 -0200
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q1O5r3YK005291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 24 Feb 2012 03:53:04 -0200
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q1O5r31b025656 for <ietf@ietf.org>; Fri, 24 Feb 2012 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q1O5r2Sm025642 for ietf@ietf.org; Fri, 24 Feb 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201202240553.q1O5r2Sm025642@rotala.raleigh.ibm.com>
Date: Fri, 24 Feb 2012 00:53:02 -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-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12022405-7182-0000-0000-000000E11393
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 05:53:11 -0000

Total of 126 messages in the last 7 days.
 
script run at: Fri Feb 24 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.76% |    6 |  5.34% |    52292 | stephen.farrell@cs.tcd.ie
  5.56% |    7 |  4.52% |    44276 | julian.reschke@gmx.de
  3.97% |    5 |  4.66% |    45616 | presnick@qualcomm.com
  3.97% |    5 |  3.04% |    29764 | paul.hoffman@vpnc.org
  3.17% |    4 |  3.21% |    31432 | marka@isc.org
  1.59% |    2 |  4.67% |    45719 | touch@isi.edu
  3.17% |    4 |  2.83% |    27695 | ned+ietf@mauve.mrochek.com
  3.17% |    4 |  2.66% |    26026 | tbray@textuality.com
  3.17% |    4 |  2.61% |    25530 | mrex@sap.com
  1.59% |    2 |  4.15% |    40615 | kkinnear@cisco.com
  3.17% |    4 |  2.46% |    24109 | dougb@dougbarton.us
  2.38% |    3 |  2.98% |    29169 | lear@cisco.com
  3.17% |    4 |  2.13% |    20811 | randy@psg.com
  2.38% |    3 |  2.47% |    24165 | fielding@gbiv.com
  2.38% |    3 |  2.44% |    23904 | brian.e.carpenter@gmail.com
  2.38% |    3 |  2.17% |    21203 | mnot@mnot.net
  2.38% |    3 |  2.00% |    19590 | mohta@necom830.hpcl.titech.ac.jp
  2.38% |    3 |  1.93% |    18847 | lsawyer@gci.com
  2.38% |    3 |  1.89% |    18476 | stpeter@stpeter.im
  2.38% |    3 |  1.79% |    17491 | dhc@dcrocker.net
  1.59% |    2 |  1.66% |    16200 | hsantos@isdg.net
  1.59% |    2 |  1.55% |    15202 | ietfdbh@comcast.net
  1.59% |    2 |  1.50% |    14697 | cgrundemann@gmail.com
  1.59% |    2 |  1.45% |    14217 | bob.hinden@gmail.com
  1.59% |    2 |  1.44% |    14079 | jari.arkko@piuha.net
  1.59% |    2 |  1.41% |    13792 | msk@cloudmark.com
  1.59% |    2 |  1.37% |    13361 | rja.lists@gmail.com
  1.59% |    2 |  1.36% |    13298 | sm@resistor.net
  1.59% |    2 |  1.32% |    12892 | dwm@xpasc.com
  1.59% |    2 |  1.01% |     9880 | jnc@mercury.lcs.mit.edu
  0.79% |    1 |  1.66% |    16239 | lorenzo@google.com
  0.79% |    1 |  1.41% |    13804 | gtw@gtwassociates.com
  0.79% |    1 |  1.24% |    12148 | robert@hernady.cz
  0.79% |    1 |  1.20% |    11777 | ron.even.tlv@gmail.com
  0.79% |    1 |  1.12% |    11002 | jgs@juniper.net
  0.79% |    1 |  1.10% |    10770 | jason_livingood@cable.comcast.com
  0.79% |    1 |  1.09% |    10670 | narten@us.ibm.com
  0.79% |    1 |  1.04% |    10168 | ted.lemon@nominum.com
  0.79% |    1 |  0.96% |     9444 | d.sturek@att.net
  0.79% |    1 |  0.92% |     9053 | rdroms.ietf@gmail.com
  0.79% |    1 |  0.85% |     8308 | salvatore.loreto@ericsson.com
  0.79% |    1 |  0.83% |     8116 | wesley.george@twcable.com
  0.79% |    1 |  0.74% |     7203 | hsantos@santronics.com
  0.79% |    1 |  0.73% |     7192 | beldmit@gmail.com
  0.79% |    1 |  0.73% |     7191 | hgs@cs.columbia.edu
  0.79% |    1 |  0.72% |     7080 | barryleiba@computer.org
  0.79% |    1 |  0.71% |     6993 | woolf@isc.org
  0.79% |    1 |  0.71% |     6982 | tglassey@certichron.com
  0.79% |    1 |  0.71% |     6930 | danielc@orckit.com
  0.79% |    1 |  0.67% |     6593 | sant9442@gmail.com
  0.79% |    1 |  0.66% |     6504 | john-ietf@jck.com
  0.79% |    1 |  0.65% |     6374 | atlunde@panix.com
  0.79% |    1 |  0.64% |     6272 | mcr@sandelman.ca
  0.79% |    1 |  0.64% |     6252 | damien.saucez@gmail.com
  0.79% |    1 |  0.64% |     6228 | wjhns1@hardakers.net
  0.79% |    1 |  0.63% |     6160 | adrien@qbik.com
  0.79% |    1 |  0.62% |     6085 | scott@kitterman.com
  0.79% |    1 |  0.61% |     5971 | jhutz@cmu.edu
  0.79% |    1 |  0.60% |     5871 | melinda.shore@gmail.com
  0.79% |    1 |  0.57% |     5532 | ajs@anvilwalrusden.com
  0.79% |    1 |  0.56% |     5455 | rbarnes@bbn.com
--------+------+--------+----------+------------------------
100.00% |  126 |100.00% |   978715 | Total


From paf@frobbit.se  Thu Feb 23 22:18:06 2012
Return-Path: <paf@frobbit.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 593FB21F8855; Thu, 23 Feb 2012 22:18:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mpmO3eWpG0GB; Thu, 23 Feb 2012 22:18:05 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5BA21F8850; Thu, 23 Feb 2012 22:18:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 4AC7D132869F6; Fri, 24 Feb 2012 07:18:02 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mI4+whaUcMLy; Fri, 24 Feb 2012 07:18:02 +0100 (CET)
Received: from [172.20.10.2] (host-95-199-11-11.mobileonline.telia.com [95.199.11.11]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 86BB2132869EF; Fri, 24 Feb 2012 07:18:01 +0100 (CET)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org>
Date: Fri, 24 Feb 2012 07:18:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3506C53-D3FC-4814-9F41-1BD404119499@frobbit.se>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1257)
Cc: iesg@ietf.org, mnot@mnot.net, ietf-http-wg@w3.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:18:06 -0000

On 24 feb 2012, at 03:54, Mark Andrews wrote:

> In message <4F46BFDF.3070703@dougbarton.us>, Doug Barton writes:
>> For my money it would be quite important for an HTTP 2.0 definition =
to
>> make SRV DNS records a full-fledged participant in the standard. =
Minimum
>> once a month there is someone asking for help on bind-users@ for =
which
>> the answer is, "The solution to that _would_ be SRV records, if they
>> were supported."
>>=20
>> 2782 was published 12 years ago this month. I suppose it can be
>> considered mature enough to deploy at this point? :)
>=20
> +1000

Indeed. Including how to handle the comparison of domain name in the URL =
/ domain name in the target in the SRV with the domain name in a cert. =
I.e. relationship with DANE.

   Patrik


From stephen.farrell@cs.tcd.ie  Fri Feb 24 04:54:21 2012
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 8A32021F8554; Fri, 24 Feb 2012 04:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mndBkG7m2Ajr; Fri, 24 Feb 2012 04:54:20 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 9549221F8652; Fri, 24 Feb 2012 04:54:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id A61CE171C3D; Fri, 24 Feb 2012 12:54:15 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330088054; bh=dNA8PvlM4oqlhF PBZauZkipgDHMnpVm8gEWVy3NSW4E=; b=6+XgK594Z/HnyWE24Q1UjkdnAq5Egi LdmNicJ5isKtY+b7CSdxHQFcI6PvX7L5Pw2qS9V5wr4jWVfFx997VBNgBcZQLR1k Dctl40xiQ89tej7+J6cFt6KFJrC0PJiKgYg5aDXssB7zsRcjniJ8df0ZveolDy5l hVrFWnS0+7tC8KYg7nuxEzjU+6tqyZv0hRK7EJxNZbTW/gBdu5F99HDTJo6CV+J9 heCpue/7EoU7rtuZUjyTlpQUyxvDjGCy+T/bHMXYQa/vt35k50LP0pP30eGprWKp ApmnQFDyrQE7L/wmys3FmybMAemQlytF7YcQlSXQSYz/Coty5j1w29ug==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id JrH9Zr-fEUbp; Fri, 24 Feb 2012 12:54:14 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id AA6A4171C3B; Fri, 24 Feb 2012 12:54:10 +0000 (GMT)
Message-ID: <4F478872.8020103@cs.tcd.ie>
Date: Fri, 24 Feb 2012 12:54:10 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "Roy T. Fielding" <fielding@gbiv.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
In-Reply-To: <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:54:21 -0000

On 02/24/2012 01:24 AM, Roy T. Fielding wrote:
> On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
>> On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fielding<fielding@gbiv.com>  wrote:
>>
>>> How many times do we have to do this before we declare insanity?
>>> I don't care how much risk it adds to the HTTP charter.  They are
>>> all just meaningless deadlines anyway.  If we want HTTP to have
>>> something other than Basic (1993) and Digest (1995) authentication,
>>> then it had better be part of *this* charter so that the proposals
>>> can address them.
>>
>> Well, Digest already isn't used by anyone :)
>
> A popular misconception because it works unseen.  See tools.ietf.org
>
>> Seriously, someone needs to propose some charter language or this
>> discussion is a no-op.  -Tim
>
> "Proposals for new HTTP authentication schemes are in scope."

How would a plan like the following look to folks:

- httpbis is chartered to include auth mechanism work as
   per the above (or whatever text goes into the charter)
- that'll generate a slew of proposals, some good, some
   bad, some better-than-current and some too complex
- plan is for httpbis to pick something (one or more if
   they want, but one better-than-current one is the goal)
- give all the above a short timeframe (this year, pick
   which to work on at the same time as re-chartering for
   the details of HTTP/2.0 maybe)
- httpbis pick what they want, (zero or more) and go
   do their stuff

- if there's still enough interest in some proposals
   that were not picked by httpbis we then try charter a sec
   area wg to develop experimental specs for those so
   they're off the critical path for httpbis (the rest die
   unloved;-)
- those experimental specs would be REQUIRED to work with
   http/1.1 and/or http/2.0 (as appropriate) with no change
   required to http; that'd be in the charter for that
   putative sec wg
- that sec wg charter might also say that the putative
   wg is not allowed to add new schemes until the
   originally chartered ones are completed (to avoid
   people turning up every week with their shiny new
   scheme)

Might that be a way forward that'll give enough folks
enough of what they want/need?

Cheers,
S.

From paul.hoffman@vpnc.org  Fri Feb 24 07:02:46 2012
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 A979121F86E8; Fri, 24 Feb 2012 07:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.657
X-Spam-Level: 
X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o4jdN2V-OBiO; Fri, 24 Feb 2012 07:02:43 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id EC69C21F8807; Fri, 24 Feb 2012 07:02:42 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1OF2bv1073065 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Feb 2012 08:02:38 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F478872.8020103@cs.tcd.ie>
Date: Fri, 24 Feb 2012 07:02:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDE9205F-4B8C-47A6-AF12-B654E23590E4@vpnc.org>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:02:46 -0000

On Feb 24, 2012, at 4:54 AM, Stephen Farrell wrote:

>> "Proposals for new HTTP authentication schemes are in scope."
>=20
> How would a plan like the following look to folks:
>=20
> - httpbis is chartered to include auth mechanism work as
>  per the above (or whatever text goes into the charter)

> - that'll generate a slew of proposals, some good, some
>  bad, some better-than-current and some too complex
> - plan is for httpbis to pick something (one or more if
>  they want, but one better-than-current one is the goal)
> - give all the above a short timeframe (this year, pick
>  which to work on at the same time as re-chartering for
>  the details of HTTP/2.0 maybe)
> - httpbis pick what they want, (zero or more) and go
>  do their stuff
>=20
> - if there's still enough interest in some proposals
>  that were not picked by httpbis we then try charter a sec
>  area wg to develop experimental specs for those so
>  they're off the critical path for httpbis (the rest die
>  unloved;-)
> - those experimental specs would be REQUIRED to work with
>  http/1.1 and/or http/2.0 (as appropriate) with no change
>  required to http; that'd be in the charter for that
>  putative sec wg
> - that sec wg charter might also say that the putative
>  wg is not allowed to add new schemes until the
>  originally chartered ones are completed (to avoid
>  people turning up every week with their shiny new
>  scheme)
>=20
> Might that be a way forward that'll give enough folks
> enough of what they want/need?


It would, but I would like to give a counter-proposal that I think will =
use people's different talents better:

- new wg on developing http authentication mechanisms is chartered soon =
(BoF in Paris); call it the ham wg
- httpbis is chartered to follow the work of the ham wg and is required =
to make sure that the authentication framework in http 2.0 works for as =
many of the proposals from the ham wg as possible
- ham wg is responsible for most of what you list above
- http2.0 document says "the mandatory to implement auth mechanisms are =
named in that RFC over there", which comes from the ham wg

There will be overlap in wg membership, but not nearly as much as would =
be needed for your proposal.

--Paul Hoffman


From ajs@anvilwalrusden.com  Fri Feb 24 07:38:19 2012
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 A55C121F87EB; Fri, 24 Feb 2012 07:38:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level: 
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgbZn0ycq8b5; Fri, 24 Feb 2012 07:38:19 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 117CD21F87E3; Fri, 24 Feb 2012 07:38:19 -0800 (PST)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id E4C611ECB420; Fri, 24 Feb 2012 15:38:17 +0000 (UTC)
Date: Fri, 24 Feb 2012 10:38:19 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Message-ID: <20120224153818.GE48576@mail.yitter.info>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: iesg@ietf.org, mnot@mnot.net, ietf-http-wg@w3.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:38:19 -0000

On Fri, Feb 24, 2012 at 01:54:32PM +1100, Mark Andrews wrote:
> 
> In message <4F46BFDF.3070703@dougbarton.us>, Doug Barton writes:
> > 
> > 2782 was published 12 years ago this month. I suppose it can be
> > considered mature enough to deploy at this point? :)
> 
> +1000

Over in spfbis, people are arguing that the SPF RRTYPE should be
deprecated and abandoned in SPF because nobody uses it because of
practical difficulties in getting new RRTYPEs deployed.  What makes us
think that the arguments in favour of SRV are going to find more
fertile ground?

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From paf@frobbit.se  Fri Feb 24 07:58:44 2012
Return-Path: <paf@frobbit.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 CC23121F8813; Fri, 24 Feb 2012 07:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HsWXlMP9NlKS; Fri, 24 Feb 2012 07:58:43 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id D4E6521F876F; Fri, 24 Feb 2012 07:58:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 6E620132958B4; Fri, 24 Feb 2012 16:58:37 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dea0ALbzjTEa; Fri, 24 Feb 2012 16:58:37 +0100 (CET)
Received: from host-78-64-116-200.homerun.telia.com (host-78-64-116-200.homerun.telia.com [78.64.116.200]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 2C0C4132958AC; Fri, 24 Feb 2012 16:58:37 +0100 (CET)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <20120224153818.GE48576@mail.yitter.info>
Date: Fri, 24 Feb 2012 16:58:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1257)
Cc: mnot@mnot.net, IETF Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:58:44 -0000

On 24 feb 2012, at 16:38, Andrew Sullivan wrote:

> Over in spfbis, people are arguing that the SPF RRTYPE should be
> deprecated and abandoned in SPF because nobody uses it because of
> practical difficulties in getting new RRTYPEs deployed.  What makes us
> think that the arguments in favour of SRV are going to find more
> fertile ground?

Because people disagree on whether it is actually hard to get new =
RRTYPEs deployed.

I for example do completely disagree on it being hard. Sure, your user =
interface in the gui of your favorite $EDITOR might not support the new =
RRTYPE, but should that constrain deployment of good standards?

   Patrik


From iesg@ietf.org  Fri Feb 24 08:07:11 2012
Return-Path: <iesg@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 87D1B21F889C; Fri, 24 Feb 2012 08:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OplBWFtBexGj; Fri, 24 Feb 2012 08:07:11 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 2533F21F8898; Fri, 24 Feb 2012 08:07:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 21EEC12C8A0; Fri, 24 Feb 2012 08:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mjAAglm8UeJ; Fri, 24 Feb 2012 08:07:11 -0800 (PST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) by c8a.amsl.com (Postfix) with ESMTPSA id BC21012C89F; Fri, 24 Feb 2012 08:07:10 -0800 (PST)
From: The IESG <iesg@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: draft-weil-shared-transition-space-request
Date: Fri, 24 Feb 2012 11:07:09 -0500
Message-Id: <B0D4AC4D-4F13-4EBF-A932-21C6F2798D6C@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Cc: IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:07:11 -0000

Colleagues,

The IESG has observed very rough consensus in favor of the allocation =
proposed in draft-weil-shared-transition-space-request. Therefore, the =
IESG will approve the draft. In order to acknowledge dissenting opinions =
and clarify the IETF position regarding IPv6, the IESG will attach the =
following note:

"A number of operators have expressed a need for the special
 purpose IPv4 address allocation described by this document.
 During deliberations, the IETF community demonstrated very
 rough consensus in favor of the allocation.

 While operational expedients, including the special purpose
 address allocation described in this document, may help solve
 a short-term operational problem, the IESG and the IETF remain
 committed to the deployment of IPv6."

Regards,
The IESG=

From kkinnear@cisco.com  Thu Feb 23 10:57:48 2012
Return-Path: <kkinnear@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 2E3F621F886E; Thu, 23 Feb 2012 10:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.811
X-Spam-Level: 
X-Spam-Status: No, score=-9.811 tagged_above=-999 required=5 tests=[AWL=0.788,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BJynROU20KU; Thu, 23 Feb 2012 10:57:45 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 830DE21F886B; Thu, 23 Feb 2012 10:57:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=kkinnear@cisco.com; l=5791; q=dns/txt; s=iport; t=1330023465; x=1331233065; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=AtY+3SfoIG3K/vdXefATS/2aE9hk6YJ5JLwaUDy3tck=; b=HdDrllu7XDVKo/AGHkPjY0YmW/+stjAt6HaxiWLwxgP7q8MMk5lVOBHc Dm3JPuYT6qA8zKnRmPsO70Pn7YmnrEgbW7d+KEyY5x/WiezVYAF3n/X8B 1qesccP+PuaEOXkga56HeE/50XOqZSIMDyZ8d7gjxkqwOYFZsfQvq8Sw+ 0=;
X-IronPort-AV: E=Sophos;i="4.73,471,1325462400"; d="scan'208";a="32044454"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 23 Feb 2012 18:57:45 +0000
Received: from [161.44.65.167] ([161.44.65.167]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1NIviWr031652; Thu, 23 Feb 2012 18:57:44 GMT
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <4F3ED8FC.6020400@isi.edu>
Date: Thu, 23 Feb 2012 13:57:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF25BE45-19EF-4D73-850E-2EA9045370F6@cisco.com>
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 24 Feb 2012 08:20:05 -0800
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:57:48 -0000

Joe,

There were two things that I referenced in response to your initial
review that you hadn't seen.  More details on those below:


On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:

--------------------------------------------

>> INTERLEAVING- sec 7.7 says that the server MUST interleave
>> replies;
>> there doesn't seem a valid reason for this requirement. clearly the
>> receiver MUST tolerate interleaved replies. having the server =
interleave
>> replies is relevant only if each request/reply has its own timeout --
>> which should be overridden if there is another response in progress
>> anyway. This issue should be more clearly explained and motivated.
>=20
> 	Robert Sparks offered clarification, which I like
> 	a lot and have already agreed to use:

I didn't see that; can you send that to tsv-dir@ietf.org and me?

>> 	Is the requirement you are really trying to capture "MUST
>> 	NOT block sending replies on new queries until all
>> 	replies for the existing query are complete."?

	I wasn't clear here -- the entire result of our
	discussion was captured in the text above.

	Note that a server does not *have* to support multiple
	queries on the same connection.  If, however, a server
	chooses to do so, then the following discussion is
	operative:

	Based on my discussion with Robert Sparks, the sentence:

	  "A server that is processing multiple queries
	  simultaneously MUST interleave replies to the multiple
	  queries within the stream of reply messages it sends."

	will be replaced by the sentence:

	  "The server MUST NOT block sending replies on new
	  queries until all replies for the existing query are
	  complete."

-------------------------------------------------

>>>=20
>>> - The protocol supports bulk transfer that is not data driven.
>>> This could represent a security vulnerability by exposing
>>> information that may not be on the data path (and thus already
>>> accessible) to a relay agent. This should be discussed in the
>>> security considerations section.
>>=20
>> 	All data that is exposed has already been
>> 	exposed using UDP to regular DHCP port.   But please see
>> 	my response to Stephen Farrell (which is too long to include
>> 	here) to see if it covers the issues about which you
>> 	have concerns.
>=20
> Again, I didn't see it; please send a copy to tsv-dir@ietf.org
>=20

	There are two related posts that I will include here
	in order to keep this discussion in some kind of order.

	Here are the words that I proposed to Stephen which
	he accepted:

  There are two specific issues regarding Bulk Leasequery
  security that deserve explicit mention.  The first is
  preventing information that Bulk Leasequery can provide from
  reaching clients who are not authorized to receive such
  information.  The second is ensuring that authorized clients of
  the Bulk Leasequery capability receive accurate information
  from the Server (and that this information is not disrupted in
  transit).

  To prevent information leakage to unauthorized clients Servers
  SHOULD restrict Bulk Leasequery connections and
  DHCPBULKLEASEQUERY messages to certain requestors, either
  through explicit configuration of the Server itself or by
  employing external network elements to provide such
  restrictions.  In particular, the typical DHCPv4 client SHOULD
  NOT be allowed to receive a response to a Bulk Leasequery
  request, and some technique MUST exist to allow prevention of
  such access in any environment where Bulk Leasequery is
  deployed.

  Connections not from permitted requestors SHOULD be closed
  immediately, to avoid server connection resource exhaustion or
  alternatively, simply not be allowed to reach the server at
  all.  Servers SHOULD have the capability to restrict certain
  requestors to certain query types.  Servers MAY reply to
  queries that are not permitted with the DHCPLEASEQUERYDONE
  message with a status-code option status of NotAllowed, or MAY
  simply close the connection.

  To prevent disruption and malicious corruption of Bulk
  Leasequery data flows between the server and authorized clients
  these data flows SHOULD transit only secured networks.   These
  data flows are typically infrastructure oriented, and there is
  usually no reason to have them flowing over networks where such
  attacks are likely.  In the rare cases where these data flows
  might need to be sent through unsecured networks, they MUST
  sent over connections secured through means external to the
  DHCPv4/DHCPv6 server and its client(s) (e.g., through VPN's).

	Here is Ted Lemon's reply to Stephen's suggestion about
	using SSH/TLS to secure the data flows of DHCPv4
	Bulk Leasequery:

=46rom Ted Lemon, Feb 22 2012, 10:37:12 EST:

The main reason why TLS wasn't included is that there is zero
chance of anyone using it.   In practice this protocol is useful
only in a very specific sort of application: communications
between the core of an ISP network and the edge of the ISP
network.   Encrypting everything would be quite expensive; the
value of the data that would be acquired in an attack is low; the
risk that there could be an attacker that would do this is low,
since it would require physical access.   Furthermore, if someone
does break in, they can just collect this data with a sniffer.

Given these considerations, the additional verbiage and testing
required for TLS support seemed unnecessary and potentially
damaging, since untested code is vulnerable code.   The working
group did actually consider requesting that the authors add TLS
to the document, but concluded that it was not worthwhile.

-----------------------------

	Regards -- Kim






From kkinnear@cisco.com  Thu Feb 23 13:59:55 2012
Return-Path: <kkinnear@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 BE7E921E8025; Thu, 23 Feb 2012 13:59:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level: 
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, J_CHICKENPOX_65=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QW9flqGzQ9MZ; Thu, 23 Feb 2012 13:59:53 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 943DF21E8021; Thu, 23 Feb 2012 13:59:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=kkinnear@cisco.com; l=22227; q=dns/txt; s=iport; t=1330034393; x=1331243993; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=YC0faeSnfaHioawVbtTf88vj9PEe6zWQ9cNDdwKR7Yc=; b=gjVsOIXSy4FuBROjdiUdT4e9ewY2Uv3oUEJ0y2/SxyXUO7gyVEM1P9FF DHuZFBiO/Ub4Gl2b4rf/0ktvQKtXDRFKS+rc8baAAJuTXxlac7hbBe41b f/bz1In0pPvjT9RQCi2MiNyU4aacowdiuDwdV2r5DvBet8+Dqnq0XXGgN 0=;
X-IronPort-AV: E=Sophos;i="4.73,472,1325462400"; d="scan'208";a="32088099"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 23 Feb 2012 21:59:53 +0000
Received: from [161.44.65.167] ([161.44.65.167]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q1NLxq3A013957; Thu, 23 Feb 2012 21:59:52 GMT
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <4F3ED8FC.6020400@isi.edu>
Date: Thu, 23 Feb 2012 17:00:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC54B54D-8DAA-4D98-9A1E-FDEC36612A60@cisco.com>
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 24 Feb 2012 08:20:17 -0800
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:59:55 -0000

Joe,

I've edited the the email trail to try to concentrate on
the remaining open issues.  I've also removed the two
issues that were included in the email I sent you an hour
or so ago, since I expect that they will be covered in
continuations of that thread.

To summarize, there are 3 issues remaining that are
not included below:

1. The NAGLE issue you raised, which has its own thread.

2. The two issues:

	a) Interleaving

	b) Possible security vulnerability if data
	is available that wasn't already in the data
	path.

3. The ? issues remaining, below.  I think that
the number could be 0, but probably not.

Regards -- Kim



On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:

> Hi, Kim,
>=20
> First, thank you for your detailed response to my quite lengthy =
review.
>=20
> Some further clarifications and confirmations appear below.
>=20
> Joe
>=20
> On 2/17/2012 12:09 PM, Kim Kinnear wrote:
>>=20
>> Joe,
>>=20
>> Thank you for your review.
>>=20
>> My responses are indented, below...
>>=20
>> On Feb 13, 2012, at 5:00 PM, Joe Touch wrote:
>>=20
>>> Hi, all,
>>>=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. The authors should
>>> consider this review together with any other last-call comments
>>> they receive. Please always CC tsv-dir@ietf.org if you reply to or
>>> forward this review.
>>>=20
>>> This request was received Feb. 2, 2012.
>>>=20
>>> This document describes an extension to DHCPv4 for the bulk query
>>> andtransfer of current lease status over TCP.
>>>=20
>>> The following transport issues were noted, and are significant:
>=20
>>> CONNECTION MANAGEMENT- The document describes the use of TCP
>>> connections for bulk transfer, but needs to be more specific about =
which
>>> side (relay client or server) closes the connection, under what
>>> circumstances, and with what mechanism (e.g., graceful CLOSE vs. =
ABORT,
>>> as per RFC 793)
>>=20
>> 	Here is what we have now, 7.8 is for clients, 8.5 is for
>> 	servers:
>>=20
>>> 7.8.  Closing Connections  [Client Section]
>>>=20
>>>    The requestor SHOULD close the connection after the
>>>    DHCPLEASEQUERYDONE message is received for the last outstanding =
query
>>>    that it has sent, if it has no more queries to send.
>=20
> Under what conditions is it useful to not close at this time, and if =
so, when/why is it eventually closed?
>=20
> In this case it's also useful to explain what "no more queries to =
send" means - are clients encouraged to keep the connection open in case =
there are more to send, or do you expect that the client knows when it =
opens the connection whether it has more to send - and if so, shouldn't =
it have already sent them?

	These are not uninteresting questions, but they are over
	the line from protocol specification and into
	implementation in my view.  I can certainly imagine that
	the requestor has multiple queries to send but has chosen
	to send them serially instead of in parallel (on the same
	connection or on different connections).  That would be
	way that the requestor might know that it had more
	queries to send.  It might have a queue of them.

	I will add this to the document:

	"If a requestor doesn't know if it has more queries to
	send or not, then it SHOULD close the connection."


>=20
>>>=20
>>> 8.5.  Closing Connections   [Server Section]
>>>=20
>>>    The DHCPv4 server SHOULD start a timer for BULK_LQ_DATA_TIMEOUT
>>>    seconds for a particular connection after it sends a
>>>    DHCPLEASEQUERYDONE message over that connection and if there is =
no
>>>    current query outstanding for that connection.  It should clear =
this
>=20
> Is this a SHOULD?

	Yes, I'll change it.
>=20
> And should the timer be cleared or restarted?

	I was thinking of them as the same thing, but restarted
	is probably better language.  I'll change it.
>=20
> Under what conditions is it useful to not close at this time, and if =
so, when/why is it closed?

	All of these SHOULDs derive from the fundamental SHOULD
	about starting a timer.  You don't *have* to have a timer
	to implement this protocol.  You SHOULD use a timer, but
	you don't *have* to.  I can imagine other ways to dealing
	with closing dead connections which don't involve timers.
	No, I really don't want to put them into the document.
	But the initial SHOULD says that if you don't use a
	timer, you can still say that you implement this
	capability.
>=20
>>>    timer if a query arrives over that connection.  If the timer =
expires,
>>>    the DHCPv4 server should close the connection.
>=20
> Is this a SHOULD, as well?

	Yes, thanks, I'll change it.
>=20
> Again, under what conditions is it useful to not close at this time, =
and if so, when/why is it closed?

	Again, this is a SHOULD because you don't even have to
	have a timer.  But even if you have a timer, you don't
	have to close it when the timer goes off.  You might want
	to be "smarter" about something, or use some external
	information not represented here to make what you
	consider a better decision.  The SHOULD allows you to do
	that without causing you to wonder if you really support
	the document.

>>>    The server MUST close its end of the TCP connection if it =
encounters
>>>    an error sending data on the connection.  The server MUST close =
its
>>>    end of the TCP connection if it finds that it has to abort an in-
>>>    process request.  A server aborting an in-process request SHOULD
>>>    attempt to signal that to its requestors by using the =
QueryTerminated
>>>    status code in the status-code option in a DHCPLEASEQUERYDONE
>>>    message, including a message string indicating details of the =
reason
>>>    for the abort.   If the server detects that the requesting end of =
the
>>>    connection has been closed, the server MUST close its end of the
>>>    connection.
>=20
> OK. I found it a bit confusing to have this in separate places, but I =
viewed this from the transport perspective. This is fine.
>=20
>> 	All connections are closed with a graceful CLOSE, and not
>> 	with an ABORT.  I'll add that to the document.
>>=20
>> 	I'm at a loss to know how to be more specific about which
>> 	side of the connection closes the connection.  There are
>> 	rules for the client in 7.8, and rules for the server in
>> 	8.5.
>=20
> Somewhere you should state that the protocol exchange typically =
involves the client closing the connection, and that the server closes =
only under exceptions.

	Ok.  I'll do that.
>=20
>>> sec 7.3 indicates some conditions for terminating connections; this
>>> section should indicate which side performs this, and by what
>>> method(CLOSE, ABORT)
>>=20
>> 	Section 7.3 discusses in two places where the "requestor" may
>> 	drop the connection.  The term "requestor" is used to
>> 	indicate which "side" performs the actions.  All of
>> 	Section 7 is about "Requestor Behavior", and the specific
>> 	details of section 7.3 in all cases indicate that the
>> 	instructions for dealing with the connection concern the
>> 	"requestor" explicitly.
>>=20
>> 	I'll enhance the explanation to include that CLOSE should
>> 	be used.
>>=20
>> 	If there is a specific set of instructions that are
>> 	unclear, I don't see them, so it would help me if you
>> 	could give me more detailed guidance than "Section 7.3".
>> 	Thanks.
>=20
> It's probably sufficient to replace "requestor" with "client" to be =
consistent.

	Requestor is the entity sending in the DHCPv4 Bulk Leasequery.
	Client is the entity that has a DHCPv4 address and whose
	information shows up in the data part of the DHCPv4 Bulk
	Leasequery requests.  Client would not be consistent.

> However, this section then supercedes the description in 7.8 and 8.5 =
above - i.e., you are handling exceptions on the client side as well.

	I will enhance section 7.8 to indicate that requestors
	have to handle exception conditions and their intended
	actions.
>=20
> I.e., 7.8 needs to include the exception cases listed in 7.3, or they =
should just be moved there.

	Yes.
>=20
>>>> this sec also allows connections to stay open after all pending
>>>> transactions are complete (MAY); the rationale for this should be
>>>> given, or the connection MUST be closed.
>>=20
>> 	I will add some words which clarify the reasons why you
>> 	might want to leave the connection open after all pending
>> 	transactions are complete.
>=20
> FWIW, again this contradicts 7.8 which says the client SHOULD close =
after the response is received if it has no more queries to send.

	The rationale is that you might know from information not
	part of this document that you had more queries to send
	soon, even though you don't have them now.
>=20
> This says "MAY" leave open. That's not the complement to SHOULD close.

	We don't really care if you keep it open or not.  Really.
	If you think that you will be happier, keep it open.  If
	you think it is simpler to close it (as I do), then close
	it.  Different people (different authors even!) have different
	ideas about how they would structure the code for this.  That's
	ok.  The point about all of this open/closed/multiple-operations
	stuff it to leave it up to the implementor.  Period.  We are
	not trying to tell them exactly how to implement this.   We
	are trying to focus on the protocol aspects, and leave =
understood.


>>> This section should more carefully explain behavior when a
>>> connection is dropped and the reason - e.g., timeout, abort,
>>> close.
>> =09
>> 	The application employing Bulk Leasequery doesn't
>> 	care about *why* the connection went away.  It
>> 	doesn't have to know if it was abort, close, or
>> 	timeout.  I will say that in this section.
>=20
> Hmm. I would think that this information would be passed up to the =
application.

	It might, but we don't care.  Do you think we should?
	If the connection is gone, it is gone.  I don't think
	I care which syscall caused it.
>=20
>>>=20
>>> There were some other issues noted in this document. These
>>> comments appear below, and although not focused on transport
>>> issues, they represent significant issues that IMO should be
>>> addressed as well.
>>>=20
>>> NOTE - regarding some terminology issues, I did not survey current
>>> DHCP RFCs for consistency, but IMO these terms should be corrected
>>> even if they are then inconsistent with existing specs.
>>> Joe
>>>=20
>>> -----------
>>>=20
>>> Major non-transport issues:
>>>=20
>>>=20
>=20
>>>=20
>>> - "VPN" is used throughout to refer to "private" addresses (RFC =
1918); a VPN is not just private addressing.
>>=20
>> 	Hmm.  Actually, VPN in this document does not refer to RFC 1918
>> 	private addressing.  If this is important to you, could you
>> 	be more specific as to your concern?
>=20
> OK. I don't understand how it's being used, but if it's consistent =
with the rest of DHCP, that's fine.
>=20
> However, I got thrown off by your use of 10.x.x.x.
>=20
> There are appropriate addresses to use as examples in RFCs - see RFC =
5737, and please change this example accordingly.

	I will replace the reference to 10.x.x.x with a reference
	to RFC 1918 addresses.  Which is the point that I was trying
	to make, not about some example address.
>=20
>=20
>>>=20
>=20
>>> - start-time-of-state is expressed as an offset from base-time;
>>> this appears to be the only time indicated as an offset rather than
>>> as an absolute. That inconsistency invites implementation errors;
>>> IMO, this should be absolute too.
>>=20
>> 	There are two kinds of time options here, input options
>> 	and output options.  The input options are all absolute
>> 	times.  The output options are all offset times from the
>> 	base time (which by design is the only absolute time in
>> 	the output packets).
>=20
> That'd be very useful to explain this way. Is this typical for DHCP? =
It's quite confusing IMO.

	DHCP times are traditionally in duration from "now", to not have
	to deal with clock skew issues (other than ongoing drift/skew).

	We introduced the base-time to work with that, and we kept
	the query times in absolute time.  I'll add words to explain
	that.
>=20
> >       ...There are several input options
>> 	defined in this document.  The start-time-of-state is the
>> 	only output option defined in this draft.  It is defined
>> 	as a offset to the base time in large part because the
>> 	*other* output options that are used in the DHCP packet
>> 	are *also* offsets to the base time.  These options are
>> 	not new, but are options that already exist in other
>> 	RFC's.  So, while it looks like the state-time-of-state
>> 	is the odd man out at first glance, it actually is an
>> 	offset time because the *other* options with which it
>> 	will appear are also offset times.
>>=20
>>>=20
>>> - option lengths: throughout, the doc refers to option lengths as
>>> being "an octet"; they are *indicated* in one octet. Some are =
constant
>>> (e.g., DCHP-STATE), some allow the contents of the octet to vary. =
Again,
>>> this is an *unsigned integer* octet.
>>=20
>> 	Yes, the size of an option is stored in
>> 	one octet.  So, yes, the length is *indicated*
>> 	by the value in that one octet.
>>=20
>> 	But the length may be 1 octet, it may be
>> 	5 octets, it may vary between 8 and 10 octets.
>>=20
>> 	I don't understand your concern.  Are you=09
>> 	saying that the length should not be
>> 	stated to be "1 octet" or "5 octets"?
>=20
> The length should be "indicated in 1 octet". I'm just suggesting a =
change to the way it's described. When you say "the length is an octet", =
that is ambiguous and can mean that the length value is 1, not just that =
this value is stored in one octet.

	Ok, I'll fix that.
>=20
>> 	I will fix the integer to be specifically
>> 	unsigned (as previously indicated).
>>>=20
>>> - some of the information provided (in DHCP-STATE) goes beyond
>>> that of DHCP. It would be useful to motivate the need for this
>>> information in a bulk query, and why it is not similarly available
>>> for nodes using UDP (e.g., as an extension to DHCPv4, not just to
>>> the bulk transfer command). again, absence of state information
>>> should not indicate state. State should always be expressed
>>> explicitly. these states are further meaningless without a state
>>> diagram explaining them. if such a diagram is not possible (as
>>> noted at end of sec 6.2.7), then the states are irrelevant and the
>>> option should not be included.
>>=20
>> 	The state transition diagram can certainly be drawn, but
>> 	as it is fully connected, such a picture conveys no
>> 	useful information.
>=20
> It's sufficient to indicate this then.
>=20
> >	... The transitions are not themselves
>> 	useful in any case, as the the Bulk Leasequery is a
>> 	snapshot of information at one instant of time.  There is
>> 	every reason to assume that as the state moves from one
>> 	value to another that an external entity would not see
>> 	all (or even many) of these transitions.  This is a
>> 	snapshot of the DHCP state, and could be nothing else in
>> 	the environment of Bulk Leasequery.
>>=20
>> 	The reason why the state transition graph is fully
>> 	connected is due to the common practice in DHCPv4 of
>> 	having two servers running in a failover relationship.
>> 	There are then two state machines for the lease state,
>> 	and at times one "leads" and the other "follows", and at
>> 	other times the other "leads" and its partner "follows".
>> 	So, examined individually, the state machines for each
>> 	individual failover partner is fully connected because at
>> 	any time it may receive an update from its partner that
>> 	it decides to accept that will simply "set" the state to
>> 	the value supplied by the partner.
>>=20
>> 	All of this is orthogonal to the Bulk Leasequery protocol
>> 	-- except that we want the user of the Bulk Leasequery
>> 	protocol to be able to make sense out of information
>> 	supplied by each of the failover partners.  Or any
>> 	partners running any increased availability solution.
>>=20
>> 	So, that is the reason why the dhcp-state option exists
>> 	at all -- to allow the user of Bulk Leasequery to make
>> 	sense out of the results of sending a Bulk Leasequery to
>> 	two different (but cooperating) DHCPv4 servers.
>>=20
>> 	The DHC WG felt that this information was worthwhile to
>> 	have in this document, and I agree (or we wouldn't have
>> 	put it in).
>=20
> Using the failover case as a justification would be helpful.

	Failover isn't an IETF standard, and so we try to step
	carefully around it possible existence.  I don't think
	I could get this document through back through the DHC WG
	if I mentioned failover, so I don't think this is going
	to work.
>>=20
>=20
>>> - sec 7.4 states that the clock skew of zero is desired; this
>>> assumes E2E delays under 1sec. An explanation of why this is
>>> desired should be given, as well as the consequences of it not.
>>=20
>> 	I have given specific instructions on how to handle non-zero
>> 	clock skews.  There are no "consequences".  You code it
>> 	so that it works with non-zero clock skew.  Period.
>>=20
>> 	It is desired because it is less confusing to humans.
>=20
> I would argue that this then irrelevant, and there should be no =
statement about a skew of zero being preferred, since it could drive =
implementations that way unnecessarily.

	I believe that the other reason we like zero skew is=20
	that it tends to expose fewer bugs in people's code,
	so keeping the admonishment that it is a better=20
	answer seems to add some value.
>=20
>>> Other non-transport issues:
>>>=20
>>> - The document includes definitions and references to irrelevant
>>> deployment and implementation issues, notably DSLAMs, concentrators, =
and
>>> access concentrators. These should not appear formally; they should =
be
>>> used only to usefully illustrate currently intended uses.
>>=20
>> 	These appear in the text in order to give
>> 	the otherwise abstract design goals some concrete
>> 	examples.   We already removed a lot of the design
>> 	goals, are you suggesting that they all be removed?
>=20
> Actually, yes, except as examples in the intro/motivation. Elsewhere =
they are IMO distracting.

	DSLAM, concentrator, and access concentrator appear only
	in Section 3, Design Goals -- which is precisely the =
intro/motivation
	for this document.  They don't appear (at least to my text =
search
	engine) elsewhere.  So I think we have done what you want.
>=20
>=20
>>> - sec 3 should refer to relays, and returning the entire set or
>>> individual bindings; there is no reason to explain the goals in =
terms of
>>> access concentrators.
>>=20
>> 	I don't know about this.  I could certainly change it,
>> 	but is this really important to you?  There was quite a
>> 	bit of negotiation in the WG about these examples.  I
>> 	don't want to restart that discussion and have it all
>> 	over again.  Does this really matter that much to you?
>=20
> The examples should focus on client/server/relay terminology. If other =
example terms are used, they should be parenthetical examples:
>=20
> 	relay (e.g., at a concentrator)
>=20
> The point is that this is relevant without the concentrator. A =
concentrator is just one current example of where a relay exists, not =
the only one.

	True, and I will say that.   There was too much discussion
	of these examples to remove them, but while they are
	important to the process of getting through the DHC WG
	review, they are not of significant importance technically.

	So, I will add a sentence discussing the fact that a=20
	concentrator is just an example.
>=20
>>> - sec 3.2 appears to provide contradictory advice - caching is =
required, but should be avoided? it would be useful to resolve this =
inconsistency.
>>=20
>> 	Use of Bulk Leasequery is designed to help you avoid
>> 	caching.
>=20
> OK - it'd be useful to be clear on that in sec 3.2.

	I will say that in Section 3.2.
>=20
>>> - sec 3.3 refers to 'fast path', but this term doesn't make sense in =
this context because fast-path is a forwarding issue. it would be useful =
to explain what you mean, and pick a different term
>>=20
>> 	Yes, it is a forwarding issue, and many devices
>> 	will not forward unless they know that they are forwarding
>> 	to a device that has received a valid DHCPv4 address.
>> 	The point (well, one point) of Bulk Leasequery is to
>> 	allow these forwarders to gather data so that they
>> 	can make the correct decision in the fast path.
>=20
> Per-IP validation of that sort of permission isn't a fast-path =
decision. Fast-path involves forwarding and policy decisions (which are =
not typically /32 decisions).
>=20
> It would be useful to say this information is useful so such routers =
can make the appropriate decision, but the path (fast or slow) is =
irrelevant IMO.

        Yes, fast-path is a forwarding issue, and I believe
	the intent of this section was to mention that the
	information returned by Leasequery is useful when
	deciding to forward a packet -- and that Bulk Leasequery
	gives you the information you need to decide to forward
	or not in advance of seeing the packet (when it is too
	late to deal with it in the fast path).

	I am not convinced that this should be changed.


	Regards -- Kim

>=20
>> ------------
>>=20
>> 	Regards -- Kim
>>=20
>>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From w@1wt.eu  Thu Feb 23 23:25:15 2012
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64D5A21E801B; Thu, 23 Feb 2012 23:25:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.684
X-Spam-Level: 
X-Spam-Status: No, score=-5.684 tagged_above=-999 required=5 tests=[AWL=-3.641, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61lvGW0FItir; Thu, 23 Feb 2012 23:25:15 -0800 (PST)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 86C6421E800C; Thu, 23 Feb 2012 23:25:13 -0800 (PST)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id q1O7P4xs003920; Fri, 24 Feb 2012 08:25:04 +0100
Date: Fri, 24 Feb 2012 08:25:03 +0100
From: Willy Tarreau <w@1wt.eu>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Message-ID: <20120224072503.GH1306@1wt.eu>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <FBC37226-CDB3-4669-8E39-E9CE8A1681C1@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FBC37226-CDB3-4669-8E39-E9CE8A1681C1@vpnc.org>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Fri, 24 Feb 2012 08:20:44 -0800
Cc: "Roy T. Fielding" <fielding@gbiv.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 07:25:15 -0000

On Thu, Feb 23, 2012 at 05:23:45PM -0800, Paul Hoffman wrote:
> If only it were that simple. If the answer is "design an HTTP auth mechanism
> that is better than Digest", then this is a tractable goal. If it is "get
> IETF consensus on that auth mechanism", then it isn't. The latter has proven
> to be impossible because people say (possibly rightly) that web developers
> don't want auth mechanisms that use the browser chrome: they want auth in
> HTML, and anything that relies on the browser chrome is insufficient.

Maybe but you still need HTTP-based auth for proxies anyway. Also, I
partially disagree with your point, seeing the number of applications
in enterprise which rely on the hated NTLM auth which is also HTTP-based ;
they're using it because it's transparent to the user, and enterprise
customers do ask for such transparent auth schemes.

There would also be much less need for cookies if auth was carried by the
browser, and this would let the user log off. So I think there's a need
for this.

Regards,
Willy


From john-ietf@jck.com  Fri Feb 24 08:43:43 2012
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 9ADC321F881B; Fri, 24 Feb 2012 08:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAgjfN4LyitD; Fri, 24 Feb 2012 08:43:42 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B89A421F8813; Fri, 24 Feb 2012 08:43:42 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S0yAy-0007rM-EG; Fri, 24 Feb 2012 11:39:20 -0500
Date: Fri, 24 Feb 2012 11:43:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Message-ID: <DC8A7C4316C6F97607CFBCC6@PST.JCK.COM>
In-Reply-To: <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se>
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
Cc: mnot@mnot.net, IETF Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:43:43 -0000

--On Friday, February 24, 2012 16:58 +0100 Patrik =
F=C3=A4ltstr=C3=B6m
<paf@frobbit.se> wrote:

> On 24 feb 2012, at 16:38, Andrew Sullivan wrote:
>=20
>> Over in spfbis, people are arguing that the SPF RRTYPE should
>> be deprecated and abandoned in SPF because nobody uses it
>> because of practical difficulties in getting new RRTYPEs
>> deployed.  What makes us think that the arguments in favour
>> of SRV are going to find more fertile ground?
>=20
> Because people disagree on whether it is actually hard to get
> new RRTYPEs deployed.
>=20
> I for example do completely disagree on it being hard. Sure,
> your user interface in the gui of your favorite $EDITOR might
> not support the new RRTYPE, but should that constrain
> deployment of good standards?

Patrik,

While I don't see it as hard as Andrew does, I don't see it as
easy either.  The problem isn't one's favorite $EDITOR.  It is
the number of folks who, for lots of reasons, haven't upgraded
from operating systems, resolvers, etc., that don't support
newer RRTYPES.   Remember that, while Windows 7 is getting some
of the market share that Vista never did, there are still a huge
number of XP systems out there -- many of them in the hands of
people and organizations who aren't going to make the hardware
investment to upgrade in a difficult economy.  The situation
with the Mac platform actually isn't much better -- I know a lot
of people who haven't (and can't) upgrade from OS 9, much less
to the latest carnivorous feline. =20

SRV has the advantage of many year's head start and more utility
to more protocols over, e.g., SPF but the reality remains that,
if some users have support for an important new RRTYPE and
others don't, we have either an inconsistent user experience
(more confusion, more support calls, etc.) or, as we have seen
with DNAME, a need to carry around complex workarounds that can
lead to bugs, vunerabilities, or, ahem, inconsistent user
experience.

And, fwiw, I'm actually much more concerned about use of the DNS
for any part of the process if we don't have broad consensus in
and between the IETF and the implementer community about whether
IRIs or URIs are authoritative and about how domain names
containing IDN labels are encoded in either.   I'm equally
concerned if some organization of our mutual acquaintance is
determined to declare the existence of equivalent names in the
DNS that will create user expectations that certs and comparison
mechanisms cannot support.

--On Thursday, February 23, 2012 14:38 -0800 Doug Barton
<dougb@dougbarton.us> wrote:

> 2782 was published 12 years ago this month. I suppose it can =
be
> considered mature enough to deploy at this point? :)

One might wish.  But real maturity has to be based on
implementation and deployment, not just publication dates.   I
note, for example, that RFC 736 (an old favorite example of mine
for several reasons) was published over 34 years ago is, like
2782, still at Proposed Standard, and, sadly, hasn't gone
anywhere (at least in the last decade or so).   Certainly it is
elderly as Internet protocols go, but I don't think the leap
from "elderly" to "mature" is obviously justified.

    john


From ajs@anvilwalrusden.com  Fri Feb 24 09:14:33 2012
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 BF9EA21F8680 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 09:14:33 -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=[AWL=0.151,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7hx88mbDWUOS for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 09:14:32 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id DB7F921F867F for <ietf@ietf.org>; Fri, 24 Feb 2012 09:14:27 -0800 (PST)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 1DF3E1ECB41D for <ietf@ietf.org>; Fri, 24 Feb 2012 17:14:27 +0000 (UTC)
Date: Fri, 24 Feb 2012 12:14:28 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
Message-ID: <20120224171427.GJ48576@mail.yitter.info>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:14:33 -0000

cc:s trimmed.  I'm not on the w3c list anyway, and I don't think the
IESG cares about this detail.

On Fri, Feb 24, 2012 at 04:58:36PM +0100, Patrik FÃ¤ltstrÃ¶m wrote:
> 
> Because people disagree on whether it is actually hard to get new RRTYPEs deployed.
> 
> I for example do completely disagree on it being hard. Sure, your user interface in the gui of your favorite $EDITOR might not support the new RRTYPE, but should that constrain deployment of good standards?
> 

Before those who think DNS weenies never listen to real-world problems
jump in, I want to point out what _I_ understand to be a problem.  If
you're a DNS geek, then the natural thing to think is, "This is easy.
You just send a well-crafted UDP packet.  How hard could that be?
Once the typecode is assigned, what's the problem with sending an
unknown RR?"

If you're most application programmers, however, the entire conversation
ended at "send a well-crafted UDP packet".  Your libraries don't
support injecting well-crafted UDP packets, and you have no idea how
to do that, and it's incredibly stupid, and why would anyone think
that was reasonable anyway?

If you're most sysadmins, the entire conversation ended at "My tools
don't know what TYPE1234 is."  

If we seriously think that DNS RRTYPEs ought to be useful extensions
to people, we're going to have to make them _easy_ to deploy, not just
possible.  I have no idea how to solve this problem, though.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From scott@kitterman.com  Fri Feb 24 09:47:12 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50C821F88A1 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 09:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cU0ExJIuWJqh for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 09:47:12 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id E0A1A21F88A0 for <ietf@ietf.org>; Fri, 24 Feb 2012 09:47:11 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 3D6CD20E40CC; Fri, 24 Feb 2012 12:47:11 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330105631; bh=JKFsxucQ/YZTGrsDC8edN961hwLidZFXGDws9qppuaE=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=P2aMmkTwXRswXPz2buqGqUcMVrBrZzXrqylWYAwk7WtXl27SYgOy7NbkUnD+UOQ0Q msSvXxYLicSoThnWxkqHwFtid33Rtb2MMlg9cHa8/o43aiC8OI0YnN4QnOmmx7OXYW yHqh3bDkyxefSoGOK24NvhUkAuQKcbmBhNqV5oE4=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 1E95D20E4083;  Fri, 24 Feb 2012 12:47:10 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
Date: Fri, 24 Feb 2012 12:47:10 -0500
Message-ID: <1473887.qQLEpWRMlg@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <20120224171427.GJ48576@mail.yitter.info>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <20120224171427.GJ48576@mail.yitter.info>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:47:12 -0000

On Friday, February 24, 2012 12:14:28 PM Andrew Sullivan wrote:
> cc:s trimmed.  I'm not on the w3c list anyway, and I don't think the
> IESG cares about this detail.
>=20
> On Fri, Feb 24, 2012 at 04:58:36PM +0100, Patrik F=E4ltstr=F6m wrote:=

> > Because people disagree on whether it is actually hard to get new
> > RRTYPEs deployed.
> >=20
> > I for example do completely disagree on it being hard. Sure, your u=
ser
> > interface in the gui of your favorite $EDITOR might not support the=
 new
> > RRTYPE, but should that constrain deployment of good standards?
> Before those who think DNS weenies never listen to real-world problem=
s
> jump in, I want to point out what _I_ understand to be a problem.  If=

> you're a DNS geek, then the natural thing to think is, "This is easy.=

> You just send a well-crafted UDP packet.  How hard could that be?
> Once the typecode is assigned, what's the problem with sending an
> unknown RR?"
>=20
> If you're most application programmers, however, the entire conversat=
ion
> ended at "send a well-crafted UDP packet".  Your libraries don't
> support injecting well-crafted UDP packets, and you have no idea how
> to do that, and it's incredibly stupid, and why would anyone think
> that was reasonable anyway?
>=20
> If you're most sysadmins, the entire conversation ended at "My tools
> don't know what TYPE1234 is."
>=20
> If we seriously think that DNS RRTYPEs ought to be useful extensions
> to people, we're going to have to make them _easy_ to deploy, not jus=
t
> possible.  I have no idea how to solve this problem, though.

It's occured to me that it might be useful to pre-allocate some new typ=
es=20
without a current use assigned (e.g. TXT1, TXT2, TXT3) so that there's =
time=20
for them to be integrated into tools before they are needed.  Of course=
 not=20
everyone will implement an unused, but allocated type, but it might be =
enough=20
to make a worthwhile difference in this problem.

The biggest issue with new type deployment is that for a new protocol t=
o get=20
deployment it needs the new type assigned.  For a new type to get assig=
ned,=20
there needs to be some indication it will get deployed.  So there is of=
ten a=20
work around using existing types, but then once the new protocol is dep=
loyed=20
with the workaround old type there's no incentive to migrate.  The only=
 way to=20
break this cycle is to have something readily available for initial use=
 with=20
protocol experimentation.

Scott K

From ajs@anvilwalrusden.com  Fri Feb 24 09:57:52 2012
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 995C221F873C for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 09:57:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yI3rBlAVu-Eg for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 09:57:52 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 195D321F86F1 for <ietf@ietf.org>; Fri, 24 Feb 2012 09:57:51 -0800 (PST)
Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 4AE621ECB41D for <ietf@ietf.org>; Fri, 24 Feb 2012 17:57:51 +0000 (UTC)
Date: Fri, 24 Feb 2012 12:57:49 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
Message-ID: <20120224175748.GN48576@mail.yitter.info>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <20120224171427.GJ48576@mail.yitter.info> <1473887.qQLEpWRMlg@scott-latitude-e6320>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1473887.qQLEpWRMlg@scott-latitude-e6320>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:57:52 -0000

On Fri, Feb 24, 2012 at 12:47:10PM -0500, Scott Kitterman wrote:

> It's occured to me that it might be useful to pre-allocate some new
> types without a current use assigned (e.g. TXT1, TXT2, TXT3) so that
> there's time for them to be integrated into tools before they are
> needed.

How could you integrate a pre-allocated type when you don't know what
its format is?  If you knew how to do that, you could just deal with
unknown RRTPYEs, and then having TYPE99 wouldn't be a problem anyway.

> protocol to get deployment it needs the new type assigned.  For a
> new type to get assigned, there needs to be some indication it will
> get deployed. 

Absolutely false.  RRTYPE assignment is by expert review, and the last
reviews, while late and a little careless about process, were not in
any way held up by the possibility (or lack thereof) of use.  Nobody
is reluctant to assign RRTPYEs.  We have lots of numbers.  There may
have been problems with this in the past, but not at least since I've
been DNSEXT WG co-chair, which is several years now.

> type there's no incentive to migrate.  The only way to break this
> cycle is to have something readily available for initial use with
> protocol experimentation.

There's lots of room for that, too.  The range 65280-65534 is for
private use.  You can do whatever you like there.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From scott@kitterman.com  Fri Feb 24 10:06:40 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1FF21F88C1 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 10:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJbYc-LRhwl6 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 10:06:39 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 4C25B21F88BF for <ietf@ietf.org>; Fri, 24 Feb 2012 10:06:39 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id D7A7920E40CC; Fri, 24 Feb 2012 13:06:38 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330106798; bh=PioPJknJhAZoJU3j6UvgwicP3Q4064w/FE0dbLnho5g=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=l6Tp7ep5ENj7DcyJPYHMIiBdoXrWua7Bbgt9QwR6BBmB1nDa16FbTXpVT9x+BV2NF uJqavxtWE+JyoqO/1bbyLvoV2rW1P4CKO6MYGNgMHP9iyZhRrGw7o5B/oHBnolnjG9 kFfKlTJIXLWFBrGJSlW3RM98uJOWdf2O/7lBVFmA=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id BE0DC20E4083;  Fri, 24 Feb 2012 13:06:38 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
Date: Fri, 24 Feb 2012 13:06:38 -0500
Message-ID: <1370954.fA4nZvz4lC@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <20120224175748.GN48576@mail.yitter.info>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <1473887.qQLEpWRMlg@scott-latitude-e6320> <20120224175748.GN48576@mail.yitter.info>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:06:40 -0000

On Friday, February 24, 2012 12:57:49 PM Andrew Sullivan wrote:
> On Fri, Feb 24, 2012 at 12:47:10PM -0500, Scott Kitterman wrote:
> > It's occured to me that it might be useful to pre-allocate some new
> > types without a current use assigned (e.g. TXT1, TXT2, TXT3) so that
> > there's time for them to be integrated into tools before they are
> > needed.
> 
> How could you integrate a pre-allocated type when you don't know what
> its format is?  If you knew how to do that, you could just deal with
> unknown RRTPYEs, and then having TYPE99 wouldn't be a problem anyway.

If there had been a TXT1 ... N in 2004, SPF (to put an example) could have 
picked TXT1 (assuming it wasn't used by something else).  Then later the label 
could have been changed to SPF once usage was established and standardized.

Then a few years later, DomainKeys could have used TXT2 (or whatever) for it's 
key records.  As it was, a new rr type wasn't (AFAICT) given serious 
consideration.

I'd give them all a format of text and if a protocol needs something more 
specific than that it can interpret it at the application level.

> > protocol to get deployment it needs the new type assigned.  For a
> > new type to get assigned, there needs to be some indication it will
> > get deployed.
> 
> Absolutely false.  RRTYPE assignment is by expert review, and the last
> reviews, while late and a little careless about process, were not in
> any way held up by the possibility (or lack thereof) of use.  Nobody
> is reluctant to assign RRTPYEs.  We have lots of numbers.  There may
> have been problems with this in the past, but not at least since I've
> been DNSEXT WG co-chair, which is several years now.

OK.  My one experience with this was the assignment of Type 99 as Type SPF.  
It wasn't done until very shortly before RFC 4408 was published (and by then 
it was far too late).  If it's different now, then my idea my well be obsolete.

> > type there's no incentive to migrate.  The only way to break this
> > cycle is to have something readily available for initial use with
> > protocol experimentation.
> 
> There's lots of room for that, too.  The range 65280-65534 is for
> private use.  You can do whatever you like there.

Yes, but that still assumes a transition to a new rr type when the protocol 
matures.  The one experience that we have with trying to do this (that I know 
of) doesn't inspire confidence that this is a reasonable expectation.

Scott K

From Ed.Lewis@neustar.biz  Fri Feb 24 10:18:31 2012
Return-Path: <Ed.Lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90D1521F8811 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 10:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.31
X-Spam-Level: 
X-Spam-Status: No, score=-106.31 tagged_above=-999 required=5 tests=[AWL=0.289, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j+JBOSFPxLD7 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 10:18:31 -0800 (PST)
Received: from stora.ogud.com (stora.ogud.com [66.92.146.20]) by ietfa.amsl.com (Postfix) with ESMTP id D683821F8807 for <ietf@ietf.org>; Fri, 24 Feb 2012 10:18:30 -0800 (PST)
Received: from Work-Laptop-2.local (nyttbox.md.ogud.com [10.20.30.4]) by stora.ogud.com (8.14.4/8.14.4) with ESMTP id q1OIIShc034528; Fri, 24 Feb 2012 13:18:29 -0500 (EST) (envelope-from Ed.Lewis@neustar.biz)
Received: from [192.168.129.155] by Work-Laptop-2.local (PGP Universal service); Fri, 24 Feb 2012 13:18:29 -0500
X-PGP-Universal: processed; by Work-Laptop-2.local on Fri, 24 Feb 2012 13:18:29 -0500
Mime-Version: 1.0
Message-Id: <a06240800cb6d835daba2@[192.168.129.155]>
In-Reply-To: <1370954.fA4nZvz4lC@scott-latitude-e6320>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <1473887.qQLEpWRMlg@scott-latitude-e6320> <20120224175748.GN48576@mail.yitter.info> <1370954.fA4nZvz4lC@scott-latitude-e6320>
Date: Fri, 24 Feb 2012 13:18:24 -0500
To: <ietf@ietf.org>
From: Edward Lewis <Ed.Lewis@neustar.biz>
Subject: Re: DNS RRTYPEs, 	the difficulty with (was: WG Review: Recharter of Hypertext Transfer 	Protocol Bis (httpbis))
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Scanned-By: MIMEDefang 2.72 on 10.20.30.4
Cc: ed.lewis@neustar.biz
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:18:31 -0000

At 13:06 -0500 2/24/12, Scott Kitterman wrote:

>If there had been a TXT1 ... N in 2004, SPF (to put an example) could have
>picked TXT1 (assuming it wasn't used by something else).  Then later the label
>could have been changed to SPF once usage was established and standardized.
>
>Then a few years later, DomainKeys could have used TXT2 (or whatever) for it's
>key records.  As it was, a new rr type wasn't (AFAICT) given serious
>consideration.

What is described here is a problem with registering the types rather 
than getting the DNS protocol to handle the new types.  Perhaps we 
need the registry of types to have rudimentary parsing rules for the 
type (a "flying car" dream).

The barrier to reserving a number was, at one time, undefined.  Then 
it was defined.  (I can't say it's ever been lowered, but in a sense, 
merely defining it lowers it.)  Perhaps the barrier is still too high.

The fear is that if numbers are assigned too easily they will be 
toyed with and discarded and someday we will run out.  The fear is 
that we cannot reclaim the numbers.  If we can over come the latter 
fear, the first should also disappear.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis
NeuStar                    You can leave a voice message at +1-571-434-5468

2012...time to reuse those 1984 calendars!

From sant9442@gmail.com  Fri Feb 24 13:50:22 2012
Return-Path: <sant9442@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 CDCAF21F872D for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 13:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.745
X-Spam-Level: 
X-Spam-Status: No, score=-2.745 tagged_above=-999 required=5 tests=[AWL=-0.438, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ah0dkU53ger3 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 13:50:22 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C0C6121F872A for <ietf@ietf.org>; Fri, 24 Feb 2012 13:50:21 -0800 (PST)
Received: by ghbg16 with SMTP id g16so1561594ghb.31 for <ietf@ietf.org>; Fri, 24 Feb 2012 13:50:21 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.72.170 as permitted sender) client-ip=10.236.72.170; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.72.170 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.72.170]) by 10.236.72.170 with SMTP id t30mr8245752yhd.101.1330120221448 (num_hops = 1); Fri, 24 Feb 2012 13:50:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=uGITVw4AEWRI5hZShwvcTBlkPLQ/eFT54Eq9gPV+mdA=; b=mKZrIqEamPg3Q4SFuPWRhJEMejTza8ksnrA8VoJ9quA180BLP5aeb0AWshLiO9h+41 dNq7zowPWhX+cJsEx3HoEcBULpHgh9jufdjcXveItyadskF0D5IxJk+raobc70VHjegL JapkEXAB1VT40S7XKAEd0NLbGHT8zIYg8r5Ww=
Received: by 10.236.72.170 with SMTP id t30mr6251299yhd.101.1330120221411; Fri, 24 Feb 2012 13:50:21 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id b4sm9954414anb.22.2012.02.24.13.50.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 24 Feb 2012 13:50:20 -0800 (PST)
Message-ID: <4F4805FF.5050100@gmail.com>
Date: Fri, 24 Feb 2012 16:49:51 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DNS RRTYPEs, 	the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320> <a06240800cb6d835daba2@[192.168.129.155]>
In-Reply-To: <a06240800cb6d835daba2@[192.168.129.155]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:50:23 -0000

+1

As an implementator of all these new mouse trap protocols with TXT 
based solutions, some borrowing the same namespace, some using 
different namespaces, it doesn't escape me to continue getting the 
utopian idea (ignoring the technical issues) that it will be "sweet" 
if they all can be collected under one single DNS call.



Edward Lewis wrote:
> At 13:06 -0500 2/24/12, Scott Kitterman wrote:
> 
>> If there had been a TXT1 ... N in 2004, SPF (to put an example) could 
>> have
>> picked TXT1 (assuming it wasn't used by something else).  Then later 
>> the label
>> could have been changed to SPF once usage was established and 
>> standardized.
>>
>> Then a few years later, DomainKeys could have used TXT2 (or whatever) 
>> for it's
>> key records.  As it was, a new rr type wasn't (AFAICT) given serious
>> consideration.
> 
> What is described here is a problem with registering the types rather 
> than getting the DNS protocol to handle the new types.  Perhaps we need 
> the registry of types to have rudimentary parsing rules for the type (a 
> "flying car" dream).
> 
> The barrier to reserving a number was, at one time, undefined.  Then it 
> was defined.  (I can't say it's ever been lowered, but in a sense, 
> merely defining it lowers it.)  Perhaps the barrier is still too high.
> 
> The fear is that if numbers are assigned too easily they will be toyed 
> with and discarded and someday we will run out.  The fear is that we 
> cannot reclaim the numbers.  If we can over come the latter fear, the 
> first should also disappear.
> 

From ynir@checkpoint.com  Fri Feb 24 14:16:36 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5430B21F8642; Fri, 24 Feb 2012 14:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.448
X-Spam-Level: 
X-Spam-Status: No, score=-10.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HK1wgJAUJ7rI; Fri, 24 Feb 2012 14:16:35 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 59B0821F8605; Fri, 24 Feb 2012 14:16:26 -0800 (PST)
X-CheckPoint: {4F4807FD-1-1B221DC2-1FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q1OMG9FV015474;  Sat, 25 Feb 2012 00:16:09 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sat, 25 Feb 2012 00:16:09 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Date: Sat, 25 Feb 2012 00:16:09 +0200
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Topic: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Index: AczzQeiQwNzv2Us/TPqjWCoFeYXysQ==
Message-ID: <A8ECD869-385D-4D3D-BD4F-A19F96ACE031@checkpoint.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>	<4F478872.8020103@cs.tcd.ie> <FDE9205F-4B8C-47A6-AF12-B654E23590E4@vpnc.org>
In-Reply-To: <FDE9205F-4B8C-47A6-AF12-B654E23590E4@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: The IESG <iesg@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:16:36 -0000

On Feb 24, 2012, at 5:02 PM, Paul Hoffman wrote:

> On Feb 24, 2012, at 4:54 AM, Stephen Farrell wrote:
>=20
>>> "Proposals for new HTTP authentication schemes are in scope."
>>=20
>> How would a plan like the following look to folks:
>>=20
>> - httpbis is chartered to include auth mechanism work as
>> per the above (or whatever text goes into the charter)

<snip/>

>>=20
>> Might that be a way forward that'll give enough folks
>> enough of what they want/need?
>=20
>=20
> It would, but I would like to give a counter-proposal that I think will u=
se people's different talents better:
>=20
> - new wg on developing http authentication mechanisms is chartered soon (=
BoF in Paris); call it the ham wg
> - httpbis is chartered to follow the work of the ham wg and is required t=
o make sure that the authentication framework in http 2.0 works for as many=
 of the proposals from the ham wg as possible
> - ham wg is responsible for most of what you list above
> - http2.0 document says "the mandatory to implement auth mechanisms are n=
amed in that RFC over there", which comes from the ham wg
>=20
> There will be overlap in wg membership, but not nearly as much as would b=
e needed for your proposal.

I like the idea, but there is always the danger of the HAM working group ei=
ther getting stuck with multiple non-interoperable proposals like we've see=
n at IPsecME with the PAKE work.

There is also the possibility of getting stuck with conflicting requirement=
s. For example, there will be a need to use existing user databases (RADIUS=
/DIAMETER servers, LDAP directories), but that is hard to reconcile with th=
e preference for ZKPs.

I'm not really worried, because HTTP/2.0 is bound to take a long time, and =
there will be plenty of opportunity for chair and ADs to step in and interv=
ene if the wg actually does that.

On a more technical note, we are 12 days past the cutoff date for new BoF s=
ession requests, so it's probably too late for a BoF in Paris.=20

Yoav


From marka@isc.org  Fri Feb 24 14:56:54 2012
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 CE65221F865C for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 14:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Level: 
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[AWL=-0.147, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGroV7eIESOS for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 14:56:54 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 1BFBE21F8648 for <ietf@ietf.org>; Fri, 24 Feb 2012 14:56:54 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id E7C545F98B1; Fri, 24 Feb 2012 22:56:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:19cd:13a9:7603:7c9e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 6F067216C31; Fri, 24 Feb 2012 22:56:07 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id BDCDA1DCE7C6; Sat, 25 Feb 2012 09:56:03 +1100 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <20120224171427.GJ48576@mail.yitter.info>
Subject: Re: DNS RRTYPEs, the difficulty with (was: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis))
In-reply-to: Your message of "Fri, 24 Feb 2012 12:14:28 CDT." <20120224171427.GJ48576@mail.yitter.info>
Date: Sat, 25 Feb 2012 09:56:03 +1100
Message-Id: <20120224225603.BDCDA1DCE7C6@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:56:54 -0000

In message <20120224171427.GJ48576@mail.yitter.info>, Andrew Sullivan writes:
> cc:s trimmed.  I'm not on the w3c list anyway, and I don't think the
> IESG cares about this detail.
> 
> On Fri, Feb 24, 2012 at 04:58:36PM +0100, Patrik FÃ¤ltstrÃ¶m wrote:
> > 
> > Because people disagree on whether it is actually hard to get new 
> RRTYPEs deployed.
> > 
> > I for example do completely disagree on it being hard. Sure, your user 
> interface in the gui of your favorite $EDITOR might not support the new 
> RRTYPE, but should that constrain deployment of good standards?
> > 
> 
> Before those who think DNS weenies never listen to real-world problems
> jump in, I want to point out what _I_ understand to be a problem.  If
> you're a DNS geek, then the natural thing to think is, "This is easy.
> You just send a well-crafted UDP packet.  How hard could that be?
> Once the typecode is assigned, what's the problem with sending an
> unknown RR?"
> 
> If you're most application programmers, however, the entire conversation
> ended at "send a well-crafted UDP packet".  Your libraries don't
> support injecting well-crafted UDP packets, and you have no idea how
> to do that, and it's incredibly stupid, and why would anyone think
> that was reasonable anyway?
> 
> If you're most sysadmins, the entire conversation ended at "My tools
> don't know what TYPE1234 is."  
> 
> If we seriously think that DNS RRTYPEs ought to be useful extensions
> to people, we're going to have to make them _easy_ to deploy, not just
> possible.  I have no idea how to solve this problem, though.
> 
> Best,
> 
> A

It's a simple library call in Windows to get SRV records returned.  What
windows doesn't have is the ability to lookup new types but SRV has been
supported for over a decade now.

	DNS_STATUS WINAPI DnsQuery(
	  __in         PCTSTR lpstrName,
	  __in         WORD wType,
	  __in         DWORD Options,
	  __inout_opt  PVOID pExtra,
	  __out_opt    PDNS_RECORD *ppQueryResultsSet,
	  __out_opt    PVOID *pReserved
	);

http://msdn.microsoft.com/en-us/library/windows/desktop/ms682016(v=vs.85).aspx

Posix: though you do have to parse the result.
int
res_query(const char *dname, int class, int type, u_char *answer, int anslen);

There are libraries that will extact the records and return them
as a list of length data blobs.  You just need to parse the individual
records.

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

From touch@isi.edu  Fri Feb 24 16:08:55 2012
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 9BE2B21E8013; Fri, 24 Feb 2012 16:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.959
X-Spam-Level: 
X-Spam-Status: No, score=-102.959 tagged_above=-999 required=5 tests=[AWL=-0.360, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TFNJiCzOXdw; Fri, 24 Feb 2012 16:08:54 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 1037021E801A; Fri, 24 Feb 2012 16:08:54 -0800 (PST)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1P08W1n004092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Feb 2012 16:08:35 -0800 (PST)
Message-ID: <4F482681.4030607@isi.edu>
Date: Fri, 24 Feb 2012 16:08:33 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Kim Kinnear <kkinnear@cisco.com>
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <DF25BE45-19EF-4D73-850E-2EA9045370F6@cisco.com>
In-Reply-To: <DF25BE45-19EF-4D73-850E-2EA9045370F6@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, dhcwg@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:08:55 -0000

Hi, Kim,

On 2/23/2012 10:57 AM, Kim Kinnear wrote:
>
> Joe,
>
> There were two things that I referenced in response to your initial
> review that you hadn't seen.  More details on those below:
>
>
> On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
>
> --------------------------------------------
>
>>> INTERLEAVING- sec 7.7 says that the server MUST interleave
>>> replies;
>>> there doesn't seem a valid reason for this requirement. clearly the
>>> receiver MUST tolerate interleaved replies. having the server interleave
>>> replies is relevant only if each request/reply has its own timeout --
>>> which should be overridden if there is another response in progress
>>> anyway. This issue should be more clearly explained and motivated.
>>
>> 	Robert Sparks offered clarification, which I like
>> 	a lot and have already agreed to use:
>
> I didn't see that; can you send that to tsv-dir@ietf.org and me?
>
>>> 	Is the requirement you are really trying to capture "MUST
>>> 	NOT block sending replies on new queries until all
>>> 	replies for the existing query are complete."?
>
> 	I wasn't clear here -- the entire result of our
> 	discussion was captured in the text above.

Thanks for the clarification.

> 	Note that a server does not *have* to support multiple
> 	queries on the same connection.  If, however, a server
> 	chooses to do so, then the following discussion is
> 	operative:
>
> 	Based on my discussion with Robert Sparks, the sentence:
>
> 	  "A server that is processing multiple queries
> 	  simultaneously MUST interleave replies to the multiple
> 	  queries within the stream of reply messages it sends."
>
> 	will be replaced by the sentence:
>
> 	  "The server MUST NOT block sending replies on new
> 	  queries until all replies for the existing query are
> 	  complete."

That's awkward. I know you intend this to mean "replies to new queries 
MUST NOT block on the current response", but it also reads as implying 
"the server MUST not block on the current response, but can block after 
that".

Perhaps "the server MUST NOT allow any one response to block other 
pending responses; where multiple responses are pending, they MUST be 
interleaved (round-robin per-request? round-robin weighted by response 
length? other?)."

> -------------------------------------------------
>
>>>>
>>>> - The protocol supports bulk transfer that is not data driven.
>>>> This could represent a security vulnerability by exposing
>>>> information that may not be on the data path (and thus already
>>>> accessible) to a relay agent. This should be discussed in the
>>>> security considerations section.
>>>
>>> 	All data that is exposed has already been
>>> 	exposed using UDP to regular DHCP port.   But please see
>>> 	my response to Stephen Farrell (which is too long to include
>>> 	here) to see if it covers the issues about which you
>>> 	have concerns.
>>
>> Again, I didn't see it; please send a copy to tsv-dir@ietf.org
>
> 	There are two related posts that I will include here
> 	in order to keep this discussion in some kind of order.
>
> 	Here are the words that I proposed to Stephen which
> 	he accepted:
>
>    There are two specific issues regarding Bulk Leasequery
>    security that deserve explicit mention.  The first is
>    preventing information that Bulk Leasequery can provide from
>    reaching clients who are not authorized to receive such
>    information.  The second is ensuring that authorized clients of
>    the Bulk Leasequery capability receive accurate information
>    from the Server (and that this information is not disrupted in
>    transit).
>
>    To prevent information leakage to unauthorized clients Servers
>    SHOULD restrict Bulk Leasequery connections and
>    DHCPBULKLEASEQUERY messages to certain requestors, either
>    through explicit configuration of the Server itself or by
>    employing external network elements to provide such
>    restrictions.  In particular, the typical DHCPv4 client SHOULD
>    NOT be allowed to receive a response to a Bulk Leasequery
>    request, and some technique MUST exist to allow prevention of
>    such access in any environment where Bulk Leasequery is
>    deployed.
>
>    Connections not from permitted requestors SHOULD be closed
>    immediately, to avoid server connection resource exhaustion or
>    alternatively, simply not be allowed to reach the server at
>    all.  Servers SHOULD have the capability to restrict certain
>    requestors to certain query types.  Servers MAY reply to
>    queries that are not permitted with the DHCPLEASEQUERYDONE
>    message with a status-code option status of NotAllowed, or MAY
>    simply close the connection.
>
>    To prevent disruption and malicious corruption of Bulk
>    Leasequery data flows between the server and authorized clients
>    these data flows SHOULD transit only secured networks.   These
>    data flows are typically infrastructure oriented, and there is
>    usually no reason to have them flowing over networks where such
>    attacks are likely.  In the rare cases where these data flows
>    might need to be sent through unsecured networks, they MUST
>    sent over connections secured through means external to the
>    DHCPv4/DHCPv6 server and its client(s) (e.g., through VPN's).
>
> 	Here is Ted Lemon's reply to Stephen's suggestion about
> 	using SSH/TLS to secure the data flows of DHCPv4
> 	Bulk Leasequery:
>
>> From Ted Lemon, Feb 22 2012, 10:37:12 EST:
>
> The main reason why TLS wasn't included is that there is zero
> chance of anyone using it.

IMO, that's an insufficient reason; the Internet is rife with protocols 
that nobody would look at - until they did ;-)

> ...In practice this protocol is useful
> only in a very specific sort of application: communications
> between the core of an ISP network and the edge of the ISP
> network.

Either:
	a) if this is true, then the protocol needs a mechanism
	to *enforce* its use *only* in this sort of environment
or
	b) IMO, it *will* be used elsewhere, and such use should
	be anticipated in its design

I favor the latter approach, but either one is a path forward.

Joe

>... Encrypting everything would be quite expensive; the
> value of the data that would be acquired in an attack is low; the
> risk that there could be an attacker that would do this is low,
> since it would require physical access.   Furthermore, if someone
> does break in, they can just collect this data with a sniffer.
>
> Given these considerations, the additional verbiage and testing
> required for TLS support seemed unnecessary and potentially
> damaging, since untested code is vulnerable code.   The working
> group did actually consider requesting that the authors add TLS
> to the document, but concluded that it was not worthwhile.
>
> -----------------------------
>
> 	Regards -- Kim
>
>
>
>
>

From touch@isi.edu  Fri Feb 24 16:28:56 2012
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 8C07921E801F; Fri, 24 Feb 2012 16:28:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.626
X-Spam-Level: 
X-Spam-Status: No, score=-102.626 tagged_above=-999 required=5 tests=[AWL=-0.627, BAYES_00=-2.599, J_CHICKENPOX_65=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ie+1wGzS7AIz; Fri, 24 Feb 2012 16:28:54 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 9177021E8013; Fri, 24 Feb 2012 16:28:54 -0800 (PST)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1P0ScKG011678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Feb 2012 16:28:41 -0800 (PST)
Message-ID: <4F482B37.9060709@isi.edu>
Date: Fri, 24 Feb 2012 16:28:39 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <AC54B54D-8DAA-4D98-9A1E-FDEC36612A60@cisco.com>
In-Reply-To: <AC54B54D-8DAA-4D98-9A1E-FDEC36612A60@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, IETF discussion list <ietf@ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, dhcwg@ietf.org, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:28:56 -0000

Hi, Kim,

On 2/23/2012 2:00 PM, Kim Kinnear wrote:
>
> Joe,
>
> I've edited the the email trail to try to concentrate on
> the remaining open issues.  I've also removed the two
> issues that were included in the email I sent you an hour
> or so ago, since I expect that they will be covered in
> continuations of that thread.
>
> To summarize, there are 3 issues remaining that are
> not included below:
>
> 1. The NAGLE issue you raised, which has its own thread.
>
> 2. The two issues:
>
> 	a) Interleaving
>
> 	b) Possible security vulnerability if data
> 	is available that wasn't already in the data
> 	path.
>
> 3. The ? issues remaining, below.  I think that
> the number could be 0, but probably not.
>
> Regards -- Kim
>
>
>
> On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
>
>> Hi, Kim,
>>
>> First, thank you for your detailed response to my quite lengthy review.
>>
>> Some further clarifications and confirmations appear below.
>>
>> Joe
>>
>> On 2/17/2012 12:09 PM, Kim Kinnear wrote:
>>>
>>> Joe,
>>>
>>> Thank you for your review.
>>>
>>> My responses are indented, below...
>>>
>>> On Feb 13, 2012, at 5:00 PM, Joe Touch wrote:
>>>
>>>> Hi, all,
>>>>
>>>> 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. The authors should
>>>> consider this review together with any other last-call comments
>>>> they receive. Please always CC tsv-dir@ietf.org if you reply to or
>>>> forward this review.
>>>>
>>>> This request was received Feb. 2, 2012.
>>>>
>>>> This document describes an extension to DHCPv4 for the bulk query
>>>> andtransfer of current lease status over TCP.
>>>>
>>>> The following transport issues were noted, and are significant:
>>
>>>> CONNECTION MANAGEMENT- The document describes the use of TCP
>>>> connections for bulk transfer, but needs to be more specific about which
>>>> side (relay client or server) closes the connection, under what
>>>> circumstances, and with what mechanism (e.g., graceful CLOSE vs. ABORT,
>>>> as per RFC 793)
>>>
>>> 	Here is what we have now, 7.8 is for clients, 8.5 is for
>>> 	servers:
>>>
>>>> 7.8.  Closing Connections  [Client Section]
>>>>
>>>>     The requestor SHOULD close the connection after the
>>>>     DHCPLEASEQUERYDONE message is received for the last outstanding query
>>>>     that it has sent, if it has no more queries to send.
>>
>> Under what conditions is it useful to not close at this time, and if so, when/why is it eventually closed?
>>
>> In this case it's also useful to explain what "no more queries to send" means - are clients encouraged to keep the connection open in case there are more to send, or do you expect that the client knows when it opens the connection whether it has more to send - and if so, shouldn't it have already sent them?
>
> 	These are not uninteresting questions, but they are over
> 	the line from protocol specification and into
> 	implementation in my view.

While I agree, were that true then the doc would not have *any* advice 
on what to do in these cases. I'm suggesting that the advice should be 
consistent. Omitting it all would be fine too.

>       I can certainly imagine that
> 	the requestor has multiple queries to send but has chosen
> 	to send them serially instead of in parallel (on the same
> 	connection or on different connections).  That would be
> 	way that the requestor might know that it had more
> 	queries to send.  It might have a queue of them.
>
> 	I will add this to the document:
>
> 	"If a requestor doesn't know if it has more queries to
> 	send or not, then it SHOULD close the connection."

That works.

>>>> 8.5.  Closing Connections   [Server Section]
>>>>
>>>>     The DHCPv4 server SHOULD start a timer for BULK_LQ_DATA_TIMEOUT
>>>>     seconds for a particular connection after it sends a
>>>>     DHCPLEASEQUERYDONE message over that connection and if there is no
>>>>     current query outstanding for that connection.  It should clear this
>>
>> Is this a SHOULD?
>
> 	Yes, I'll change it.
>>
>> And should the timer be cleared or restarted?
>
> 	I was thinking of them as the same thing, but restarted
> 	is probably better language.  I'll change it.

AOK. "Cleared" could mean that there is no longer a timer running.

>> Under what conditions is it useful to not close at this time, and if so, when/why is it closed?
>
> 	All of these SHOULDs derive from the fundamental SHOULD
> 	about starting a timer.  You don't *have* to have a timer
> 	to implement this protocol.  You SHOULD use a timer, but
> 	you don't *have* to.  I can imagine other ways to dealing
> 	with closing dead connections which don't involve timers.
> 	No, I really don't want to put them into the document.
> 	But the initial SHOULD says that if you don't use a
> 	timer, you can still say that you implement this
> 	capability.

IMO, you're using SHOULD above in non-2119 ways. SHOULD implies there's 
a significant issue with either the protocol or implementation that has 
exceptions. You're just saying "implementations will save resources by 
using a timer and conserving the open connections". IMO, if that's the 
goal, then it'd be preferable to make the recommendation that way, 
rather than using 2119 language.

>>>>     timer if a query arrives over that connection.  If the timer expires,
>>>>     the DHCPv4 server should close the connection.
>>
>> Is this a SHOULD, as well?
>
> 	Yes, thanks, I'll change it.
>>
>> Again, under what conditions is it useful to not close at this time, and if so, when/why is it closed?
>
> 	Again, this is a SHOULD because you don't even have to
> 	have a timer.  But even if you have a timer, you don't
> 	have to close it when the timer goes off.  You might want
> 	to be "smarter" about something, or use some external
> 	information not represented here to make what you
> 	consider a better decision.  The SHOULD allows you to do
> 	that without causing you to wonder if you really support
> 	the document.

Again, this is good reason to reword the timer issue as "try to conserve 
connections; try to reuse them for multiple requests from the same 
relay, and try to close them as soon as all pending queries are 
complete; the method for doing so is left to the implementer".

Otherwise IMO you'll have people deriving correctness from whether the 
connection stays open or not.

>>>>     The server MUST close its end of the TCP connection if it encounters
>>>>     an error sending data on the connection.  The server MUST close its
>>>>     end of the TCP connection if it finds that it has to abort an in-
>>>>     process request.  A server aborting an in-process request SHOULD
>>>>     attempt to signal that to its requestors by using the QueryTerminated
>>>>     status code in the status-code option in a DHCPLEASEQUERYDONE
>>>>     message, including a message string indicating details of the reason
>>>>     for the abort.   If the server detects that the requesting end of the
>>>>     connection has been closed, the server MUST close its end of the
>>>>     connection.
>>
>> OK. I found it a bit confusing to have this in separate places, but I viewed this from the transport perspective. This is fine.
>>
>>> 	All connections are closed with a graceful CLOSE, and not
>>> 	with an ABORT.  I'll add that to the document.
>>>
>>> 	I'm at a loss to know how to be more specific about which
>>> 	side of the connection closes the connection.  There are
>>> 	rules for the client in 7.8, and rules for the server in
>>> 	8.5.
>>
>> Somewhere you should state that the protocol exchange typically involves the client closing the connection, and that the server closes only under exceptions.
>
> 	Ok.  I'll do that.
>>
>>>> sec 7.3 indicates some conditions for terminating connections; this
>>>> section should indicate which side performs this, and by what
>>>> method(CLOSE, ABORT)
>>>
>>> 	Section 7.3 discusses in two places where the "requestor" may
>>> 	drop the connection.  The term "requestor" is used to
>>> 	indicate which "side" performs the actions.  All of
>>> 	Section 7 is about "Requestor Behavior", and the specific
>>> 	details of section 7.3 in all cases indicate that the
>>> 	instructions for dealing with the connection concern the
>>> 	"requestor" explicitly.
>>>
>>> 	I'll enhance the explanation to include that CLOSE should
>>> 	be used.
>>>
>>> 	If there is a specific set of instructions that are
>>> 	unclear, I don't see them, so it would help me if you
>>> 	could give me more detailed guidance than "Section 7.3".
>>> 	Thanks.
>>
>> It's probably sufficient to replace "requestor" with "client" to be consistent.
>
> 	Requestor is the entity sending in the DHCPv4 Bulk Leasequery.

Then you mean relay?

> 	Client is the entity that has a DHCPv4 address and whose
> 	information shows up in the data part of the DHCPv4 Bulk
> 	Leasequery requests.  Client would not be consistent.

AOK. (see above; then use "relay" here).

>> However, this section then supercedes the description in 7.8 and 8.5 above - i.e., you are handling exceptions on the client side as well.
>
> 	I will enhance section 7.8 to indicate that requestors
> 	have to handle exception conditions and their intended
> 	actions.

AOK.

>>
>> I.e., 7.8 needs to include the exception cases listed in 7.3, or they should just be moved there.
>
> 	Yes.
>>
>>>>> this sec also allows connections to stay open after all pending
>>>>> transactions are complete (MAY); the rationale for this should be
>>>>> given, or the connection MUST be closed.
>>>
>>> 	I will add some words which clarify the reasons why you
>>> 	might want to leave the connection open after all pending
>>> 	transactions are complete.
>>
>> FWIW, again this contradicts 7.8 which says the client SHOULD close after the response is received if it has no more queries to send.
>
> 	The rationale is that you might know from information not
> 	part of this document that you had more queries to send
> 	soon, even though you don't have them now.

See discussion above about rewording this all to "conserve resources 
where possible", rather than making specific recommendations as to how 
to do so.

>> This says "MAY" leave open. That's not the complement to SHOULD close.
>
> 	We don't really care if you keep it open or not.  Really.
> 	If you think that you will be happier, keep it open.  If
> 	you think it is simpler to close it (as I do), then close
> 	it.  Different people (different authors even!) have different
> 	ideas about how they would structure the code for this.  That's
> 	ok.  The point about all of this open/closed/multiple-operations
> 	stuff it to leave it up to the implementor.  Period.  We are
> 	not trying to tell them exactly how to implement this.   We
> 	are trying to focus on the protocol aspects, and leave understood.

Yet further rationale to reword as above.

>>>> This section should more carefully explain behavior when a
>>>> connection is dropped and the reason - e.g., timeout, abort,
>>>> close.
>>> 	
>>> 	The application employing Bulk Leasequery doesn't
>>> 	care about *why* the connection went away.  It
>>> 	doesn't have to know if it was abort, close, or
>>> 	timeout.  I will say that in this section.
>>
>> Hmm. I would think that this information would be passed up to the application.
>
> 	It might, but we don't care.  Do you think we should?
> 	If the connection is gone, it is gone.  I don't think
> 	I care which syscall caused it

I think that this info should be passed up to the app, as per RFC 1122.

I do think that apps would do different things - log the error 
differently at least, or retry in some cases but not others.

>>>> There were some other issues noted in this document. These
>>>> comments appear below, and although not focused on transport
>>>> issues, they represent significant issues that IMO should be
>>>> addressed as well.
>>>>
>>>> NOTE - regarding some terminology issues, I did not survey current
>>>> DHCP RFCs for consistency, but IMO these terms should be corrected
>>>> even if they are then inconsistent with existing specs.
>>>> Joe
>>>>
>>>> -----------
>>>>
>>>> Major non-transport issues:
>>>>
>>>>
>>
>>>>
>>>> - "VPN" is used throughout to refer to "private" addresses (RFC 1918); a VPN is not just private addressing.
>>>
>>> 	Hmm.  Actually, VPN in this document does not refer to RFC 1918
>>> 	private addressing.  If this is important to you, could you
>>> 	be more specific as to your concern?
>>
>> OK. I don't understand how it's being used, but if it's consistent with the rest of DHCP, that's fine.
>>
>> However, I got thrown off by your use of 10.x.x.x.
>>
>> There are appropriate addresses to use as examples in RFCs - see RFC 5737, and please change this example accordingly.
>
> 	I will replace the reference to 10.x.x.x with a reference
> 	to RFC 1918 addresses.  Which is the point that I was trying
> 	to make, not about some example address.

AOK.

>>
>>
>>>>
>>
>>>> - start-time-of-state is expressed as an offset from base-time;
>>>> this appears to be the only time indicated as an offset rather than
>>>> as an absolute. That inconsistency invites implementation errors;
>>>> IMO, this should be absolute too.
>>>
>>> 	There are two kinds of time options here, input options
>>> 	and output options.  The input options are all absolute
>>> 	times.  The output options are all offset times from the
>>> 	base time (which by design is the only absolute time in
>>> 	the output packets).
>>
>> That'd be very useful to explain this way. Is this typical for DHCP? It's quite confusing IMO.
>
> 	DHCP times are traditionally in duration from "now", to not have
> 	to deal with clock skew issues (other than ongoing drift/skew).
>
> 	We introduced the base-time to work with that, and we kept
> 	the query times in absolute time.  I'll add words to explain
> 	that.

AOK.

>>
>>>        ...There are several input options
>>> 	defined in this document.  The start-time-of-state is the
>>> 	only output option defined in this draft.  It is defined
>>> 	as a offset to the base time in large part because the
>>> 	*other* output options that are used in the DHCP packet
>>> 	are *also* offsets to the base time.  These options are
>>> 	not new, but are options that already exist in other
>>> 	RFC's.  So, while it looks like the state-time-of-state
>>> 	is the odd man out at first glance, it actually is an
>>> 	offset time because the *other* options with which it
>>> 	will appear are also offset times.
>>>
>>>>
>>>> - option lengths: throughout, the doc refers to option lengths as
>>>> being "an octet"; they are *indicated* in one octet. Some are constant
>>>> (e.g., DCHP-STATE), some allow the contents of the octet to vary. Again,
>>>> this is an *unsigned integer* octet.
>>>
>>> 	Yes, the size of an option is stored in
>>> 	one octet.  So, yes, the length is *indicated*
>>> 	by the value in that one octet.
>>>
>>> 	But the length may be 1 octet, it may be
>>> 	5 octets, it may vary between 8 and 10 octets.
>>>
>>> 	I don't understand your concern.  Are you	
>>> 	saying that the length should not be
>>> 	stated to be "1 octet" or "5 octets"?
>>
>> The length should be "indicated in 1 octet". I'm just suggesting a change to the way it's described. When you say "the length is an octet", that is ambiguous and can mean that the length value is 1, not just that this value is stored in one octet.
>
> 	Ok, I'll fix that.
>>
>>> 	I will fix the integer to be specifically
>>> 	unsigned (as previously indicated).
>>>>
>>>> - some of the information provided (in DHCP-STATE) goes beyond
>>>> that of DHCP. It would be useful to motivate the need for this
>>>> information in a bulk query, and why it is not similarly available
>>>> for nodes using UDP (e.g., as an extension to DHCPv4, not just to
>>>> the bulk transfer command). again, absence of state information
>>>> should not indicate state. State should always be expressed
>>>> explicitly. these states are further meaningless without a state
>>>> diagram explaining them. if such a diagram is not possible (as
>>>> noted at end of sec 6.2.7), then the states are irrelevant and the
>>>> option should not be included.
>>>
>>> 	The state transition diagram can certainly be drawn, but
>>> 	as it is fully connected, such a picture conveys no
>>> 	useful information.
>>
>> It's sufficient to indicate this then.
>>
>>> 	... The transitions are not themselves
>>> 	useful in any case, as the the Bulk Leasequery is a
>>> 	snapshot of information at one instant of time.  There is
>>> 	every reason to assume that as the state moves from one
>>> 	value to another that an external entity would not see
>>> 	all (or even many) of these transitions.  This is a
>>> 	snapshot of the DHCP state, and could be nothing else in
>>> 	the environment of Bulk Leasequery.
>>>
>>> 	The reason why the state transition graph is fully
>>> 	connected is due to the common practice in DHCPv4 of
>>> 	having two servers running in a failover relationship.
>>> 	There are then two state machines for the lease state,
>>> 	and at times one "leads" and the other "follows", and at
>>> 	other times the other "leads" and its partner "follows".
>>> 	So, examined individually, the state machines for each
>>> 	individual failover partner is fully connected because at
>>> 	any time it may receive an update from its partner that
>>> 	it decides to accept that will simply "set" the state to
>>> 	the value supplied by the partner.
>>>
>>> 	All of this is orthogonal to the Bulk Leasequery protocol
>>> 	-- except that we want the user of the Bulk Leasequery
>>> 	protocol to be able to make sense out of information
>>> 	supplied by each of the failover partners.  Or any
>>> 	partners running any increased availability solution.
>>>
>>> 	So, that is the reason why the dhcp-state option exists
>>> 	at all -- to allow the user of Bulk Leasequery to make
>>> 	sense out of the results of sending a Bulk Leasequery to
>>> 	two different (but cooperating) DHCPv4 servers.
>>>
>>> 	The DHC WG felt that this information was worthwhile to
>>> 	have in this document, and I agree (or we wouldn't have
>>> 	put it in).
>>
>> Using the failover case as a justification would be helpful.
>
> 	Failover isn't an IETF standard, and so we try to step
> 	carefully around it possible existence.  I don't think
> 	I could get this document through back through the DHC WG
> 	if I mentioned failover, so I don't think this is going
> 	to work.

FWIW, I don't think that creating this level of detail about state 
feedback achieves the goal; it codifies support for a non-standard 
mechanism.

IMO, that issue deserves some light, not a shadowy corner. I'll leave it 
to the WG to decide, though - this isn't a transport issue.

>>
>>>> - sec 7.4 states that the clock skew of zero is desired; this
>>>> assumes E2E delays under 1sec. An explanation of why this is
>>>> desired should be given, as well as the consequences of it not.
>>>
>>> 	I have given specific instructions on how to handle non-zero
>>> 	clock skews.  There are no "consequences".  You code it
>>> 	so that it works with non-zero clock skew.  Period.
>>>
>>> 	It is desired because it is less confusing to humans.
>>
>> I would argue that this then irrelevant, and there should be no statement about a skew of zero being preferred, since it could drive implementations that way unnecessarily.
>
> 	I believe that the other reason we like zero skew is
> 	that it tends to expose fewer bugs in people's code,
> 	so keeping the admonishment that it is a better
> 	answer seems to add some value.

That's a good reason to avoid the admonishment, IMO. If the code breaks, 
it should break early and often. "Expecting" a particular skew 
encourages bad programming IMO.

>>
>>>> Other non-transport issues:
>>>>
>>>> - The document includes definitions and references to irrelevant
>>>> deployment and implementation issues, notably DSLAMs, concentrators, and
>>>> access concentrators. These should not appear formally; they should be
>>>> used only to usefully illustrate currently intended uses.
>>>
>>> 	These appear in the text in order to give
>>> 	the otherwise abstract design goals some concrete
>>> 	examples.   We already removed a lot of the design
>>> 	goals, are you suggesting that they all be removed?
>>
>> Actually, yes, except as examples in the intro/motivation. Elsewhere they are IMO distracting.
>
> 	DSLAM, concentrator, and access concentrator appear only
> 	in Section 3, Design Goals -- which is precisely the intro/motivation
> 	for this document.  They don't appear (at least to my text search
> 	engine) elsewhere.  So I think we have done what you want.

Design goals is Sec 3; the intro is Sec 1. I'm saying using this 
terminology in the intro (sec 1) is fine, but in the design goals (sec 
3) is distracting.

>>>> - sec 3 should refer to relays, and returning the entire set or
>>>> individual bindings; there is no reason to explain the goals in terms of
>>>> access concentrators.
>>>
>>> 	I don't know about this.  I could certainly change it,
>>> 	but is this really important to you?  There was quite a
>>> 	bit of negotiation in the WG about these examples.  I
>>> 	don't want to restart that discussion and have it all
>>> 	over again.  Does this really matter that much to you?
>>
>> The examples should focus on client/server/relay terminology. If other example terms are used, they should be parenthetical examples:
>>
>> 	relay (e.g., at a concentrator)
>>
>> The point is that this is relevant without the concentrator. A concentrator is just one current example of where a relay exists, not the only one.
>
> 	True, and I will say that.   There was too much discussion
> 	of these examples to remove them, but while they are
> 	important to the process of getting through the DHC WG
> 	review, they are not of significant importance technically.
>
> 	So, I will add a sentence discussing the fact that a
> 	concentrator is just an example.

AOK.

>>
>>>> - sec 3.2 appears to provide contradictory advice - caching is required, but should be avoided? it would be useful to resolve this inconsistency.
>>>
>>> 	Use of Bulk Leasequery is designed to help you avoid
>>> 	caching.
>>
>> OK - it'd be useful to be clear on that in sec 3.2.
>
> 	I will say that in Section 3.2.

AOK

>>
>>>> - sec 3.3 refers to 'fast path', but this term doesn't make sense in this context because fast-path is a forwarding issue. it would be useful to explain what you mean, and pick a different term
>>>
>>> 	Yes, it is a forwarding issue, and many devices
>>> 	will not forward unless they know that they are forwarding
>>> 	to a device that has received a valid DHCPv4 address.
>>> 	The point (well, one point) of Bulk Leasequery is to
>>> 	allow these forwarders to gather data so that they
>>> 	can make the correct decision in the fast path.
>>
>> Per-IP validation of that sort of permission isn't a fast-path decision. Fast-path involves forwarding and policy decisions (which are not typically /32 decisions).
>>
>> It would be useful to say this information is useful so such routers can make the appropriate decision, but the path (fast or slow) is irrelevant IMO.
>
>          Yes, fast-path is a forwarding issue, and I believe
> 	the intent of this section was to mention that the
> 	information returned by Leasequery is useful when
> 	deciding to forward a packet -- and that Bulk Leasequery
> 	gives you the information you need to decide to forward
> 	or not in advance of seeing the packet (when it is too
> 	late to deal with it in the fast path).
>

The issue is that fast-path contrasts to slow-path. Filtering is always 
fast-path where supported in the hardware, and slow-path where not.

The point of the bulk leasequery is to allow forwarders to filter. 
*where* they filter is irrelevant, and not made slower or faster solely 
by whether the bulk leasequery is there. "fast path" isn't relevant to 
the issue.

> 	I am not convinced that this should be changed.
>
>
> 	Regards -- Kim
>
>>
>>> ------------
>>>
>>> 	Regards -- Kim
>>>
>>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>

From touch@isi.edu  Fri Feb 24 16:34:13 2012
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 CD57021E8013; Fri, 24 Feb 2012 16:34:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.874
X-Spam-Level: 
X-Spam-Status: No, score=-102.874 tagged_above=-999 required=5 tests=[AWL=-0.275, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZSsiBi8lmh4b; Fri, 24 Feb 2012 16:34:13 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 2030A21F860B; Fri, 24 Feb 2012 16:34:03 -0800 (PST)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1P0WuLm013869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Feb 2012 16:32:59 -0800 (PST)
Message-ID: <4F482C39.9020909@isi.edu>
Date: Fri, 24 Feb 2012 16:32:57 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <AE23A10C-D05B-4221-98A8-70FA97D550FB@gmail.com>
In-Reply-To: <AE23A10C-D05B-4221-98A8-70FA97D550FB@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org, TSV Dir <tsv-dir@ietf.org>, dhcwg@ietf.org, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:34:14 -0000

Hi, Ralph,

On 2/18/2012 4:39 AM, Ralph Droms wrote:
> Joe, Kim...
>
> On Feb 17, 2012, at 5:47 PM 2/17/12, Joe Touch wrote:
>
>> Hi, Kim,
>>
>> First, thank you for your detailed response to my quite lengthy review.
>>
>> Some further clarifications and confirmations appear below.
>>
>> Joe
>>
>> On 2/17/2012 12:09 PM, Kim Kinnear wrote:
>>>
>>> Joe,
>>>
>>> Thank you for your review.
>>>
>>> My responses are indented, below...
>>>
>>> On Feb 13, 2012, at 5:00 PM, Joe Touch wrote:
>>>
>>>> Hi, all,
>>>>
>>>> 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. The authors should
>>>> consider this review together with any other last-call comments
>>>> they receive. Please always CC tsv-dir@ietf.org if you reply to or
>>>> forward this review.
>>>>
>>>> This request was received Feb. 2, 2012.
>>>>
>>>> This document describes an extension to DHCPv4 for the bulk query
>>>> andtransfer of current lease status over TCP.
>>>>
>>>> The following transport issues were noted, and are significant:
>>>>
>>>> UPDATES- The document updates DHCP with support for TCP, and as
>>>> suchthis document seems like it should UPDATE RFC2131
>>>
>>> 	While this document clearly builds on RFC 2131, it
>>> 	doesn't actually change anything that anyone is doing
>>> 	that is currently based on RFC 2131.  My understanding of
>>> 	"updates" is that, in order to understand the first RFC
>>> 	(in this case, RFC 2131), you need to read all of the
>>> 	RFC's that "update" it.  That isn't the case here -- you
>>> 	can be very happy reading and implementing DHCPv4 by
>>> 	reading RFC 2131 and never have to know that DHCPv4 Bulk
>>> 	Leasequery exists.  In general, in the DHC WG, we seem to
>>> 	set a pretty high bar for what "udpates" another RFC.  I
>>> 	don't see that this document has met those requirements.
>>> 	But this isn't really my call.  I'll let Ralph Droms and
>>> 	the DHC WG chairs decide on this one, and I'll do
>>> 	whatever they tell me to do.
>>
>> Agreed. FWIW, my "bar" for that is whether implementing DHCPv4 as
>> per RFC 2131 is changed by this doc. If DHCP fundamentally starts
>> requiring TCP port support, then this doc then changes the spec as
>> described in 2131 IMO.
>
> Joe - I don't see that this document fundamentally requires TCP port
> support for DHCP operation as described in RFC 2131. This document
> describes a protocol that is closely related to but independent of RFC
> 2131, and a server based on RFC 2131 can perform all the DHCP functions
> in RFC 2131 without considering this document. So, I can see your point
> but I disagree that this document updates RFC 2131.

Fair enough, but then I'll put on my IANA hat and note that this then is
no longer the complementary TCP protocol to DHCP. By your argument, it's
a new service, and should have a separate TCP port and service name.

Joe

From touch@isi.edu  Fri Feb 24 16:40:44 2012
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 CEBC521E8021; Fri, 24 Feb 2012 16:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.853
X-Spam-Level: 
X-Spam-Status: No, score=-102.853 tagged_above=-999 required=5 tests=[AWL=-0.254, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bcVj9nZM402H; Fri, 24 Feb 2012 16:40:44 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 3240121E8019; Fri, 24 Feb 2012 16:40:44 -0800 (PST)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id q1P0ds7v016392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Feb 2012 16:39:57 -0800 (PST)
Message-ID: <4F482DDC.1020509@isi.edu>
Date: Fri, 24 Feb 2012 16:39:56 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <C84410EE-1D8C-494B-8BEA-030C6CBCABC1@nominum.com>
In-Reply-To: <C84410EE-1D8C-494B-8BEA-030C6CBCABC1@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "<draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>" <draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:40:45 -0000

Hi, Ted,

On 2/18/2012 7:29 AM, Ted Lemon wrote:
> On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
>> Thanks. In this case, it's important to suggest why others should not
>> add conventional DHCP query support to the TCP port.
>
> The idea of doing DHCP stateful autoconfiguration over TCP is
> nonsensical: DHCP clients start out with no IP address, so it is not
> possible for them to do TCP.

That's true for the initial request, but not for lease renewal.

> The reason for sharing option codes is to avoid confusion: since
> existing DHCPLEASEQUERY option codes come out of the same namespace as
> DHCP options,

Which doesn't need to happen if this is a completely different service...

> if we were to propose that options in this documentation
> come out of a different namespace, we would have to declare that new
> namespace, which would have some options and option codes in common with
> the existing namespace. This doesn't add value.

It avoids misrepresenting this as related.

> Historically, we have never said that when an option code is added, that
> updates RFC2131 (really, it would make more sense to say it updated
> RFC2132 if we were to go there, since RFC2132 is the document that
> describes DHCP options).

Fair enough - 2132.

> So it would be surprising and unconventional if
> this document were said to update either RFC2131 or RFC2132 simply
> because it defined one or more new option codes.

OK, so although I disagree that this is the correct procedure, if it's 
typical for DHCP then that's reasonable.

Joe

From mnot@mnot.net  Fri Feb 24 18:05:12 2012
Return-Path: <mnot@mnot.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 D34A421E8027; Fri, 24 Feb 2012 18:05:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.886
X-Spam-Level: 
X-Spam-Status: No, score=-104.886 tagged_above=-999 required=5 tests=[AWL=-2.287, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id emNx3uwNr-rN; Fri, 24 Feb 2012 18:05:12 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id E7FFB21E8025; Fri, 24 Feb 2012 18:05:11 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.53.7]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4D72D22E1EB; Fri, 24 Feb 2012 21:05:03 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F478872.8020103@cs.tcd.ie>
Date: Sat, 25 Feb 2012 13:05:00 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:05:13 -0000

Hi Stephen,

On 24/02/2012, at 11:54 PM, Stephen Farrell wrote:

>=20
> On 02/24/2012 01:24 AM, Roy T. Fielding wrote:
>> On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
>>> On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fielding<fielding@gbiv.com>  =
wrote:
>>>=20
>>>> How many times do we have to do this before we declare insanity?
>>>> I don't care how much risk it adds to the HTTP charter.  They are
>>>> all just meaningless deadlines anyway.  If we want HTTP to have
>>>> something other than Basic (1993) and Digest (1995) authentication,
>>>> then it had better be part of *this* charter so that the proposals
>>>> can address them.
>>>=20
>>> Well, Digest already isn't used by anyone :)
>>=20
>> A popular misconception because it works unseen.  See tools.ietf.org
>>=20
>>> Seriously, someone needs to propose some charter language or this
>>> discussion is a no-op.  -Tim
>>=20
>> "Proposals for new HTTP authentication schemes are in scope."
>=20
> How would a plan like the following look to folks:
>=20
> - httpbis is chartered to include auth mechanism work as
>  per the above (or whatever text goes into the charter)
> - that'll generate a slew of proposals, some good, some
>  bad, some better-than-current and some too complex
> - plan is for httpbis to pick something (one or more if
>  they want, but one better-than-current one is the goal)
> - give all the above a short timeframe (this year, pick
>  which to work on at the same time as re-chartering for
>  the details of HTTP/2.0 maybe)
> - httpbis pick what they want, (zero or more) and go
>  do their stuff

Is the goal for HTTPbis "one or more" or "zero or more"? I see both =
above.

Again - I'm absolutely fine with soliciting proposals, but requiring =
output is a different thing.

Thanks,


--
Mark Nottingham   http://www.mnot.net/




From dougb@dougbarton.us  Fri Feb 24 19:57:29 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22CD521F862A for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 19:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.591
X-Spam-Level: 
X-Spam-Status: No, score=-3.591 tagged_above=-999 required=5 tests=[AWL=0.008,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXGoMyE9rjKC for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 19:57:28 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 1D28D21F8627 for <ietf@ietf.org>; Fri, 24 Feb 2012 19:57:27 -0800 (PST)
Received: (qmail 14400 invoked by uid 399); 25 Feb 2012 03:57:24 -0000
Received: from unknown (HELO 172-17-197-151.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Feb 2012 03:57:24 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F485C22.90302@dougbarton.us>
Date: Fri, 24 Feb 2012 19:57:22 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info>
In-Reply-To: <20120224153818.GE48576@mail.yitter.info>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf-http-wg@w3.org, mnot@mnot.net, IETF Discussion <ietf@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:57:29 -0000

On 02/24/2012 07:38, Andrew Sullivan wrote:
> On Fri, Feb 24, 2012 at 01:54:32PM +1100, Mark Andrews wrote:
>>
>> In message <4F46BFDF.3070703@dougbarton.us>, Doug Barton writes:
>>>
>>> 2782 was published 12 years ago this month. I suppose it can be
>>> considered mature enough to deploy at this point? :)
>>
>> +1000
> 
> Over in spfbis, people are arguing that the SPF RRTYPE should be
> deprecated and abandoned in SPF because nobody uses it because of
> practical difficulties in getting new RRTYPEs deployed.  What makes us
> think that the arguments in favour of SRV are going to find more
> fertile ground?

Because I emphasized the point that SRV has been around for 12 years? I
have enough experience to know how difficult it is to deploy new RRs.
SRV is not new.


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From touch@isi.edu  Fri Feb 24 22:01:39 2012
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 88CFC21F8533; Fri, 24 Feb 2012 22:01:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.835
X-Spam-Level: 
X-Spam-Status: No, score=-104.835 tagged_above=-999 required=5 tests=[AWL=1.764, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDeC68OTlqFZ; Fri, 24 Feb 2012 22:01:38 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4296021F8513; Fri, 24 Feb 2012 22:01:38 -0800 (PST)
Received: from [192.168.1.100] (pool-71-105-89-105.lsanca.dsl-w.verizon.net [71.105.89.105]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q1P60rWQ013488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Feb 2012 22:01:02 -0800 (PST)
Message-ID: <4F487915.2070002@isi.edu>
Date: Fri, 24 Feb 2012 22:00:53 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <C84410EE-1D8C-494B-8BEA-030C6CBCABC1@nominum.com> <4F482DDC.1020509@isi.edu> <9B0B764E-6619-41F5-BCEC-12CB5CC5570C@nominum.com>
In-Reply-To: <9B0B764E-6619-41F5-BCEC-12CB5CC5570C@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "<draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>" <draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:01:39 -0000

On 2/24/2012 7:35 PM, Ted Lemon wrote:
> On Feb 24, 2012, at 7:39 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>> OK, so although I disagree that this is the correct procedure, if it's
>> typical for DHCP then that's reasonable.
>
> So just to be clear here, it seems that you are withdrawing your request
> that we create a new IANA registry and to say that this document updates
> RFC2131 or RFC2132, right?

I made an observation and a suggestion about those issues. They are not 
transport issues, so I consider them individual position only, and defer 
to the WG on how to proceed.

Joe


From stephen.farrell@cs.tcd.ie  Sat Feb 25 05:46:29 2012
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 5185121F85CC; Sat, 25 Feb 2012 05:46:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fJiRURjbVywY; Sat, 25 Feb 2012 05:46:27 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id B001821F85C6; Sat, 25 Feb 2012 05:46:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 11AE6171C9E; Sat, 25 Feb 2012 13:46:26 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330177584; bh=lVDM9DgHd1F6dG GlsNeGD2sSSK+A9knmt1w+5vdGQ8I=; b=Q1mEJD66vQVzElzVcDMSmINWryWKs0 B+PrNYu0D+BcJdgGX/vXAfKnu8vdlXi5ohU9gavHyu7TZMjMEVwyZ8IUAJJeGQwg z2/86cTn0KFqfTVEOgZCejkxwzHZtIxhPmV9RE1yX1gkvCzSUHHPiCyfyEF6zgMy MxnbfZYT0kPzyqDG7At46wXrzlB2aQt8guQaHNUag1C5mEqGsrr9aYX2ne59jv7S oOoPKrGCJ0ju8FEZ5gVgvxTFVIjzc2V8OKN694Ye5XFAaq7VsK0j2LmYWo+AkniH B8jji6uYjDSlA852Um0eIk/HC1WGaVbvM4hw4rNrrBj4ApW2ODZ+tpGA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id kc3UKCi77-WU; Sat, 25 Feb 2012 13:46:24 +0000 (GMT)
Received: from [10.87.48.7] (unknown [86.42.23.11]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 8C573171C2F; Sat, 25 Feb 2012 13:46:20 +0000 (GMT)
Message-ID: <4F48E62C.5020902@cs.tcd.ie>
Date: Sat, 25 Feb 2012 13:46:20 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net>
In-Reply-To: <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:46:29 -0000

Hiya,

On 02/25/2012 02:05 AM, Mark Nottingham wrote:
> Hi Stephen,
>
> On 24/02/2012, at 11:54 PM, Stephen Farrell wrote:
>
>>
>> On 02/24/2012 01:24 AM, Roy T. Fielding wrote:
>>> On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
>>>> On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fielding<fielding@gbiv.com>   wrote:
>>>>
>>>>> How many times do we have to do this before we declare insanity?
>>>>> I don't care how much risk it adds to the HTTP charter.  They are
>>>>> all just meaningless deadlines anyway.  If we want HTTP to have
>>>>> something other than Basic (1993) and Digest (1995) authentication,
>>>>> then it had better be part of *this* charter so that the proposals
>>>>> can address them.
>>>>
>>>> Well, Digest already isn't used by anyone :)
>>>
>>> A popular misconception because it works unseen.  See tools.ietf.org
>>>
>>>> Seriously, someone needs to propose some charter language or this
>>>> discussion is a no-op.  -Tim
>>>
>>> "Proposals for new HTTP authentication schemes are in scope."
>>
>> How would a plan like the following look to folks:
>>
>> - httpbis is chartered to include auth mechanism work as
>>   per the above (or whatever text goes into the charter)
>> - that'll generate a slew of proposals, some good, some
>>   bad, some better-than-current and some too complex
>> - plan is for httpbis to pick something (one or more if
>>   they want, but one better-than-current one is the goal)
>> - give all the above a short timeframe (this year, pick
>>   which to work on at the same time as re-chartering for
>>   the details of HTTP/2.0 maybe)
>> - httpbis pick what they want, (zero or more) and go
>>   do their stuff
>
> Is the goal for HTTPbis "one or more" or "zero or more"? I see both above.
>
> Again - I'm absolutely fine with soliciting proposals, but requiring output is a different thing.

Yeah that's a tricky one. While one might like to
see "one or more" in both places that might not be
practical.

In the proposal above the goal is that httpbis pick one
or more but recognising the reality that we might not get
a new proposal that httpbis will accept and that folks
will really implement and deploy.

So:
    Goal = one or more
    Reluctant recognition of reality = zero or more

With this plan if httpbis in fact select zero new proposals
that would represent a failure for all concerned. The "zero
or more" term is absolutely not intended to provide a way to
just punt on the question.

Such a failure at the point where httpbis was re-chartering
to work on a HTTP/2.0 selection with no better security than
we now have is probably better evaluated as a whole - I
guess the question for the IETF/IESG at that point would
be whether the Internet would be better with or without
such a beast, or better waiting a while until the security
thing did get fixed.

I can imagine an argument might ensue about that;-)

S

> Thanks,
>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From julian.reschke@gmx.de  Sat Feb 25 06:04:16 2012
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 00AA021F8657 for <ietf@ietfa.amsl.com>; Sat, 25 Feb 2012 06:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.189
X-Spam-Level: 
X-Spam-Status: No, score=-104.189 tagged_above=-999 required=5 tests=[AWL=-1.590, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3mhNDvLbszjo for <ietf@ietfa.amsl.com>; Sat, 25 Feb 2012 06:04:14 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 4D13121F8650 for <ietf@ietf.org>; Sat, 25 Feb 2012 06:04:14 -0800 (PST)
Received: (qmail invoked by alias); 25 Feb 2012 14:04:12 -0000
Received: from p5DCC3D19.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.61.25] by mail.gmx.net (mp071) with SMTP; 25 Feb 2012 15:04:12 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+Z3M8J62qZsCbPSfRscNARSELM0ZuY9rTnPhvFEb O79qyVzxFCk1lB
Message-ID: <4F48EA4B.6050500@gmx.de>
Date: Sat, 25 Feb 2012 15:03:55 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie>
In-Reply-To: <4F48E62C.5020902@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:04:16 -0000

On 2012-02-25 14:46, Stephen Farrell wrote:
> ...
> Yeah that's a tricky one. While one might like to
> see "one or more" in both places that might not be
> practical.
>
> In the proposal above the goal is that httpbis pick one
> or more but recognising the reality that we might not get
> a new proposal that httpbis will accept and that folks
> will really implement and deploy.
>
> So:
> Goal = one or more
> Reluctant recognition of reality = zero or more
>
> With this plan if httpbis in fact select zero new proposals
> that would represent a failure for all concerned. The "zero
> or more" term is absolutely not intended to provide a way to
> just punt on the question.
>
> Such a failure at the point where httpbis was re-chartering
> to work on a HTTP/2.0 selection with no better security than
> we now have is probably better evaluated as a whole - I
> guess the question for the IETF/IESG at that point would
> be whether the Internet would be better with or without
> such a beast, or better waiting a while until the security
> thing did get fixed.
>
> I can imagine an argument might ensue about that;-)
> ...

If we just need a new authentication scheme, nothing stops people from 
working on that right now. I don't see how that should affect HTTP/2.0.

If the "right" way to do security needs changes in the HTTP/1.1 
authentication framework, then we should fix/augment/tune HTTP/1.1. It's 
not going to go away anytime soon.

Best regards, Julian

From stephen.farrell@cs.tcd.ie  Sat Feb 25 06:13:32 2012
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 A919D21F8665; Sat, 25 Feb 2012 06:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.354
X-Spam-Level: 
X-Spam-Status: No, score=-103.354 tagged_above=-999 required=5 tests=[AWL=-0.755, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Z3idOQBzGEP; Sat, 25 Feb 2012 06:13:31 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 91A7921F8664; Sat, 25 Feb 2012 06:13:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 8CDCA171C9E; Sat, 25 Feb 2012 14:13:29 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330179209; bh=Q4h03/bi1NlX6N 4sqdG5QM66LCK3825szWkM6T1EIIM=; b=e2ttlZ71mSVXZoIf4NMvw53QvTK6kq A0k8WxcVRh+6MOVe+M7/VSl2XR0tLE4xfC5Q5KHcm3Vk2vCm6NLPihpzHLcu1CkI rRBpWXM4Riusn8ZqpRb4Ecqxh5XT2Sf5BFGAIhVMnEz8J1qkYGYjId3bA8OaHtyu ZSf/8lZZsdJAT4+VC6w0ISpP1I9d0HyFUfq0y/aXsfd6SyjisS8JbejVHTOPL+a5 nddmxvRSbHGtSU+w33hjqjZGtMHex3uN5tgHK4oy/6LeJO18jbJH/rlWNk9y8aN6 EPmtJ3hAB6E5KLC/slZZ3S6dv8OiqsqYbYPTlIlX5lITJXbldQHYMROQ==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id mso+fpT23TQn; Sat, 25 Feb 2012 14:13:29 +0000 (GMT)
Received: from [10.87.48.7] (unknown [86.42.23.11]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A6D4C171C2F; Sat, 25 Feb 2012 14:13:27 +0000 (GMT)
Message-ID: <4F48EC87.4040302@cs.tcd.ie>
Date: Sat, 25 Feb 2012 14:13:27 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de>
In-Reply-To: <4F48EA4B.6050500@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:13:33 -0000

On 02/25/2012 02:03 PM, Julian Reschke wrote:
> On 2012-02-25 14:46, Stephen Farrell wrote:
>> ...
>> Yeah that's a tricky one. While one might like to
>> see "one or more" in both places that might not be
>> practical.
>>
>> In the proposal above the goal is that httpbis pick one
>> or more but recognising the reality that we might not get
>> a new proposal that httpbis will accept and that folks
>> will really implement and deploy.
>>
>> So:
>> Goal = one or more
>> Reluctant recognition of reality = zero or more
>>
>> With this plan if httpbis in fact select zero new proposals
>> that would represent a failure for all concerned. The "zero
>> or more" term is absolutely not intended to provide a way to
>> just punt on the question.
>>
>> Such a failure at the point where httpbis was re-chartering
>> to work on a HTTP/2.0 selection with no better security than
>> we now have is probably better evaluated as a whole - I
>> guess the question for the IETF/IESG at that point would
>> be whether the Internet would be better with or without
>> such a beast, or better waiting a while until the security
>> thing did get fixed.
>>
>> I can imagine an argument might ensue about that;-)
>> ...
>
> If we just need a new authentication scheme, nothing stops people from
> working on that right now.

I don't agree with you there - the perceived low probability that
something will be deployed is a real disincentive here. We have had
people wanting to do work on this and have been told there's no point
because it won't get adopted.

 > I don't see how that should affect HTTP/2.0.

Well, a number of people have noticed that current schemes
are getting long in the tooth and fixing stuff like that when
you do a major rev of a protocol is quite a reasonable thing
to do.

> If the "right" way to do security needs changes in the HTTP/1.1
> authentication framework, then we should fix/augment/tune HTTP/1.1. It's
> not going to go away anytime soon.

Sure, I agree with that and think the plan above allows for it.

S

>
> Best regards, Julian
>

From julian.reschke@gmx.de  Sat Feb 25 06:20:58 2012
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 125D821F8669 for <ietf@ietfa.amsl.com>; Sat, 25 Feb 2012 06:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.155
X-Spam-Level: 
X-Spam-Status: No, score=-104.155 tagged_above=-999 required=5 tests=[AWL=-1.556, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ui4N1smlrfyT for <ietf@ietfa.amsl.com>; Sat, 25 Feb 2012 06:20:57 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 74EFA21F8655 for <ietf@ietf.org>; Sat, 25 Feb 2012 06:20:56 -0800 (PST)
Received: (qmail invoked by alias); 25 Feb 2012 14:20:55 -0000
Received: from p5DCC3D19.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.61.25] by mail.gmx.net (mp020) with SMTP; 25 Feb 2012 15:20:55 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX187KRxJEsQ7Hbl4CtSbGM31rgN9WwiYYNvoZ27NI0 erQpIO3DAFMbAh
Message-ID: <4F48EE34.3020504@gmx.de>
Date: Sat, 25 Feb 2012 15:20:36 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie>
In-Reply-To: <4F48EC87.4040302@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:20:58 -0000

On 2012-02-25 15:13, Stephen Farrell wrote:
>
>
> On 02/25/2012 02:03 PM, Julian Reschke wrote:
>> On 2012-02-25 14:46, Stephen Farrell wrote:
>>> ...
>>> Yeah that's a tricky one. While one might like to
>>> see "one or more" in both places that might not be
>>> practical.
>>>
>>> In the proposal above the goal is that httpbis pick one
>>> or more but recognising the reality that we might not get
>>> a new proposal that httpbis will accept and that folks
>>> will really implement and deploy.
>>>
>>> So:
>>> Goal = one or more
>>> Reluctant recognition of reality = zero or more
>>>
>>> With this plan if httpbis in fact select zero new proposals
>>> that would represent a failure for all concerned. The "zero
>>> or more" term is absolutely not intended to provide a way to
>>> just punt on the question.
>>>
>>> Such a failure at the point where httpbis was re-chartering
>>> to work on a HTTP/2.0 selection with no better security than
>>> we now have is probably better evaluated as a whole - I
>>> guess the question for the IETF/IESG at that point would
>>> be whether the Internet would be better with or without
>>> such a beast, or better waiting a while until the security
>>> thing did get fixed.
>>>
>>> I can imagine an argument might ensue about that;-)
>>> ...
>>
>> If we just need a new authentication scheme, nothing stops people from
>> working on that right now.
>
> I don't agree with you there - the perceived low probability that
> something will be deployed is a real disincentive here. We have had
> people wanting to do work on this and have been told there's no point
> because it won't get adopted.

Just checking: so you think what's needed is a normative requirement to 
implement the new scheme? Do you really believe that that's what holding 
up improvements in this area?

>  > I don't see how that should affect HTTP/2.0.
>
> Well, a number of people have noticed that current schemes
> are getting long in the tooth and fixing stuff like that when
> you do a major rev of a protocol is quite a reasonable thing
> to do.

If there's something from with the framework, let's fix the framework. 
That's already covered by the current charter, no?

>> If the "right" way to do security needs changes in the HTTP/1.1
>> authentication framework, then we should fix/augment/tune HTTP/1.1. It's
>> not going to go away anytime soon.
>
> Sure, I agree with that and think the plan above allows for it.

My point being: this is something we already do in httpbis. What's 
missing is concrete bug reports.

Best regards, Julian


From stephen.farrell@cs.tcd.ie  Sat Feb 25 09:44:40 2012
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 41D8B21F850D; Sat, 25 Feb 2012 09:44:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.71
X-Spam-Level: 
X-Spam-Status: No, score=-103.71 tagged_above=-999 required=5 tests=[AWL=-1.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YIIqlfRwEAvU; Sat, 25 Feb 2012 09:44:39 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 452DA21F84F4; Sat, 25 Feb 2012 09:44:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 1D1D9171C9F; Sat, 25 Feb 2012 17:44:38 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330191877; bh=5elK1ogBqvvXX9 ZomC1U+qBY2Z92bL6gR1NMlUVd5y8=; b=T/4DkMWBMOY2+iQkZuK45jDdiIMXLv /aOQtEbU3qewNTOA6NC7VnmR30FDvU4Yqz5AJQJ5hJ67zb5H7odqRLUFt5RTcPBq W1L7NGvVrHf2onUZvDsXLKK06pX+GBA1Z+XoxEBTdKyG9Alw3gLlqhuL+XrC5mYq YwpnvH8wZ+zKsAh2NwW5O3+5ikT5kaquZaZmJDHT5LIiaUIgrmM+L/juqVonew3T JwSSvJd3/Du6JhV6Q4/HRivs0kzVwZ2bq/0udeYhO+uvA1uLi8rypxLs1EYJbakZ 3/VkRUasHAnvxOzA0KwhpceQRDBDtjZXCY5q1PbyDtPD+w+rXCX61ipw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id m7gj9IaugPny; Sat, 25 Feb 2012 17:44:37 +0000 (GMT)
Received: from [10.87.48.7] (unknown [86.42.23.11]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 322D1171C9E; Sat, 25 Feb 2012 17:44:35 +0000 (GMT)
Message-ID: <4F491E02.9020207@cs.tcd.ie>
Date: Sat, 25 Feb 2012 17:44:34 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <4F48EE34.3020504@gmx.de>
In-Reply-To: <4F48EE34.3020504@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:44:40 -0000

On 02/25/2012 02:20 PM, Julian Reschke wrote:
> On 2012-02-25 15:13, Stephen Farrell wrote:
>> On 02/25/2012 02:03 PM, Julian Reschke wrote:
>>>
>>> If we just need a new authentication scheme, nothing stops people from
>>> working on that right now.
>>
>> I don't agree with you there - the perceived low probability that
>> something will be deployed is a real disincentive here. We have had
>> people wanting to do work on this and have been told there's no point
>> because it won't get adopted.
>
> Just checking: so you think what's needed is a normative requirement to
> implement the new scheme? Do you really believe that that's what holding
> up improvements in this area?

The first thing is not something I said and I don't know quite what
it means so its also not something I believe. I therefore also do not
believe the 2nd thing.

>> > I don't see how that should affect HTTP/2.0.
>>
>> Well, a number of people have noticed that current schemes
>> are getting long in the tooth and fixing stuff like that when
>> you do a major rev of a protocol is quite a reasonable thing
>> to do.
>
> If there's something from with the framework, let's fix the framework.
> That's already covered by the current charter, no?

I don't think fixing or changing the framework will give us better
auth schemes by itself. (Better auth schemes may or may not require
changes to the framework, I dunno.)

So I think you're raising a side issue here really.

S

>>> If the "right" way to do security needs changes in the HTTP/1.1
>>> authentication framework, then we should fix/augment/tune HTTP/1.1. It's
>>> not going to go away anytime soon.
>>
>> Sure, I agree with that and think the plan above allows for it.
>
> My point being: this is something we already do in httpbis. What's
> missing is concrete bug reports.
>
> Best regards, Julian
>
>

From julian.reschke@gmx.de  Sat Feb 25 10:24:09 2012
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 3D12521F8618 for <ietf@ietfa.amsl.com>; Sat, 25 Feb 2012 10:24:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.146
X-Spam-Level: 
X-Spam-Status: No, score=-104.146 tagged_above=-999 required=5 tests=[AWL=-1.547, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4gIRR8vHHzpC for <ietf@ietfa.amsl.com>; Sat, 25 Feb 2012 10:24:08 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 4C2A521F85DA for <ietf@ietf.org>; Sat, 25 Feb 2012 10:24:08 -0800 (PST)
Received: (qmail invoked by alias); 25 Feb 2012 18:24:07 -0000
Received: from p5DCC3D19.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.61.25] by mail.gmx.net (mp032) with SMTP; 25 Feb 2012 19:24:07 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19ArH1AEhFAHHppMG3S8jPNX+dIB6qHS28C/dHm61 EvKepMbXUh2kP1
Message-ID: <4F49271C.5030509@gmx.de>
Date: Sat, 25 Feb 2012 19:23:24 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <4F48EE34.3020504@gmx.de> <4F491E02.9020207@cs.tcd.ie>
In-Reply-To: <4F491E02.9020207@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:24:09 -0000

On 2012-02-25 18:44, Stephen Farrell wrote:
> ...
> I don't think fixing or changing the framework will give us better
> auth schemes by itself. (Better auth schemes may or may not require
> changes to the framework, I dunno.)
>
> So I think you're raising a side issue here really.
> ...

Well, I'm one of the editors of the authentication framework spec, so if 
there's something wrong with it, I'd like to know.

So if we collectively think that the framework probably is ok, and that 
we *do* need a new authentication scheme, what's stopping us to start 
that activity *right now*?

Best regards, Julian

From stephen.farrell@cs.tcd.ie  Sat Feb 25 10:29:14 2012
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 B7A9A21F8576; Sat, 25 Feb 2012 10:29:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.907
X-Spam-Level: 
X-Spam-Status: No, score=-103.907 tagged_above=-999 required=5 tests=[AWL=-1.308, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5526Qu-qcU1x; Sat, 25 Feb 2012 10:29:14 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 1009521F8562; Sat, 25 Feb 2012 10:29:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 5A018171C9E; Sat, 25 Feb 2012 18:29:13 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330194553; bh=n8J5MX/BvylIVs vV/B/z6sUPMAwyn9hl0KHk5lPt01s=; b=DS4EQgSWnt5pPney/zD22Y9Yxx+Auo onwmS2Ai8bT9tRRK01sfs93qUagxH6CJn/uovRBDADi7aKRknhFrkcxf95Uk6nKK Ow6WX8AASfMVo7mkCam2Q1vrWfvopkuiw3/p+67hV3gf1h7xn8zRpWw09pJ1YQyJ NrUJ+IOehNEMcFKiEJ7Z7/cvLM4Iqrt7sQCKv2WRNUYvLcLv9QXkRJNstDPk2N/Z sJL7j336U0Nk1huD4eTMwXMMxUfVm/5KeGU38IzhpvLByfqJwGEW3zFALOfv249f PcAJVPK1aiIVCoTF0GounB1vxIme72oo0/k4IE9GMYL+M5pzF5/ZAmXA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id Iigkqo8Nj1GA; Sat, 25 Feb 2012 18:29:13 +0000 (GMT)
Received: from [10.87.48.7] (unknown [86.42.23.11]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id E8ABC171C2F; Sat, 25 Feb 2012 18:29:10 +0000 (GMT)
Message-ID: <4F492876.4060108@cs.tcd.ie>
Date: Sat, 25 Feb 2012 18:29:10 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <4F48EE34.3020504@gmx.de> <4F491E02.9020207@cs.tcd.ie> <4F49271C.5030509@gmx.de>
In-Reply-To: <4F49271C.5030509@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:29:14 -0000

On 02/25/2012 06:23 PM, Julian Reschke wrote:
> On 2012-02-25 18:44, Stephen Farrell wrote:
>> ...
>> I don't think fixing or changing the framework will give us better
>> auth schemes by itself. (Better auth schemes may or may not require
>> changes to the framework, I dunno.)
>>
>> So I think you're raising a side issue here really.
>> ...
>
> Well, I'm one of the editors of the authentication framework spec, so if
> there's something wrong with it, I'd like to know.
>
> So if we collectively think that the framework probably is ok, and that
> we *do* need a new authentication scheme, what's stopping us to start
> that activity *right now*?

I believe I answered just that question from you earlier today.
So you must be looking for someone else's answer I guess. Or
perhaps I'm confused.

S

From mnot@mnot.net  Sat Feb 25 15:25:13 2012
Return-Path: <mnot@mnot.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 F271421F84F9; Sat, 25 Feb 2012 15:25:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.762
X-Spam-Level: 
X-Spam-Status: No, score=-104.762 tagged_above=-999 required=5 tests=[AWL=-2.293, BAYES_00=-2.599, SARE_RMML_Stock10=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zUjyh0Rtu3uU; Sat, 25 Feb 2012 15:25:12 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5C721F84F5; Sat, 25 Feb 2012 15:25:11 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.33.226]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 633F422E256; Sat, 25 Feb 2012 18:25:03 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F48EC87.4040302@cs.tcd.ie>
Date: Sun, 26 Feb 2012 10:25:00 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:25:13 -0000

On 26/02/2012, at 1:13 AM, Stephen Farrell wrote:
>>=20
>> If we just need a new authentication scheme, nothing stops people =
from
>> working on that right now.
>=20
> I don't agree with you there - the perceived low probability that
> something will be deployed is a real disincentive here. We have had
> people wanting to do work on this and have been told there's no point
> because it won't get adopted.

Let's speak plainly here.

It's not hard for new things to be deployed -- there are lots of new =
things being deployed on the Web right now.

What IS hard is forcing browser vendors to deploy something that they =
don't think is going to work, or that they're not terribly interested =
in.

They are VERY VERY VERY interested in security, as are many other people =
in the broader community. If the IETF were to come up with a viable =
proposal that solves their problems, they would beat down this =
organisation's doors.

The IETF may have some smart people, and they may have ideas about Web =
security, but that doesn't necessarily make them into workable solutions =
for the various stakeholders. The discussion about Web security is much =
broader, involving not only the browser vendors, but also organisations =
like the W3C, IIW, etc.

Using HTTP/2.0 as a mechanism to shortcut all of this and force what =
people in the IETF think is a good solution down implementers' throats =
is going to lead to a very predictable and messy fail.


> With this plan if httpbis in fact select zero new proposals
> that would represent a failure for all concerned. The "zero
> or more" term is absolutely not intended to provide a way to
> just punt on the question.

This makes me very uncomfortable. How hard and long do we have to try =
before we convince you that we're not punting?


> Such a failure at the point where httpbis was re-chartering
> to work on a HTTP/2.0 selection with no better security than
> we now have is probably better evaluated as a whole - I
> guess the question for the IETF/IESG at that point would
> be whether the Internet would be better with or without
> such a beast, or better waiting a while until the security
> thing did get fixed.


If we "wait a while until the security thing [does] get fixed", I'll =
gladly bet any amount of money you care to name that SPDY will gain =
market traction so quickly as to make any HTTP/2.0 effort in IETF =
completely backwards-looking. Refer to the debacle with Cookies for one =
such example.

So, again, I'm fine with allowing new authentication schemes to be =
proposed, in the off chance that some genius will suddenly propose =
something that meets all of the myriad requirements (that still aren't =
well-defined) and gets consensus and buy-in from implementers.=20

However, requiring us to output such a beast and gating HTTP/2.0 on it =
is effectively asking us to spin our wheels for n years. And the folks =
working on SPDY will - quite rightly - walk away and do their work =
somewhere more sane.

And I still don't see why it's necessary to do this all in one effort. =
Julian's point was that the only technical reason to combine =
authentication work with re-specifying HTTP is to make the new =
authentication scheme MTI. Otherwise, the work can be done separately. =
Roy has expressed interest in coming up with a new scheme that isn't =
necessarily targeted at browsers -- which is great, but I don't see why =
it has to be part of this WG.

We potentially have a LOT of work on our plate, and that work is =
channeling the energy behind a new serialisation of HTTP into something =
worthy of being called HTTP. Doing research and development on Web =
security is a very different kind of work, and the two don't mix well, =
IME.



--
Mark Nottingham   http://www.mnot.net/




From stephen.farrell@cs.tcd.ie  Sat Feb 25 16:40:21 2012
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 0193421F852C; Sat, 25 Feb 2012 16:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.469
X-Spam-Level: 
X-Spam-Status: No, score=-102.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_RMML_Stock10=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YDSubKcEzkSC; Sat, 25 Feb 2012 16:40:20 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id D52D121F853B; Sat, 25 Feb 2012 16:40:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 75BB9171C9E; Sun, 26 Feb 2012 00:40:17 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330216816; bh=XQyx9E8rn/yBeU U2HIPAzSntogfzgO8JO0sX1xTumjs=; b=bAp4nb7vHFlBOQgywYCo9TK67ZF2sb SnuWB3u4LbXTlzwFj4dY2qAMdws434jSllPOGRCxIkGFLf0bXt19d/bDK3Oi0qXC 5loy5iYVEZpjZvtaH9XnfGVBuSumknSyXCL2myql2GxUo0fAL4tTqm65QYZbpPYI AS97uunYZSX3rDqR/A1ndswkCeIZCFESdUv3/szeCdbcqpn1Z0zH4IxR+sJzgrJ8 Fy4J8/H4GQmawGVsbuJuhRUQ9uaUw/2cIeMSXbSEc43YbAvkIAnu3kkVjEph8ZRb y/UaaVu2bEkcR2yzZy32HWwsecu5k/N0WhqSdSHI5rrjAee1F71ATqVw==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id vOzkuBdpk2wv; Sun, 26 Feb 2012 00:40:16 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.27.138]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 5706E171C2F; Sun, 26 Feb 2012 00:40:13 +0000 (GMT)
Message-ID: <4F497F6D.8050503@cs.tcd.ie>
Date: Sun, 26 Feb 2012 00:40:13 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net>
In-Reply-To: <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:40:21 -0000

Mark,

I was going to respond blow-by-blow but there's not much
point in that, other than to say that your mail seems to
me a tad over the top.

(Maybe you misinterpreted me describing what might happen
as some kind of threat to try slow people down or something,
I don't know. I do know that I don't do that kind of thing
and if I tried I probably wouldn't be very good at it anyway;-)

Anyway, I think we should focus on a way forward that attempts
progress on what we appear to agree is the desirable outcome:

 > They are VERY VERY VERY interested in security, as are many other
 > people in the broader community. If the IETF were to come up with a
 > viable proposal that solves their problems, they would beat down this
 > organisation's doors.

I proposed a plan that I think might allow us to make progress
on that. I believe we could.

S



On 02/25/2012 11:25 PM, Mark Nottingham wrote:
>
> On 26/02/2012, at 1:13 AM, Stephen Farrell wrote:
>>>
>>> If we just need a new authentication scheme, nothing stops people from
>>> working on that right now.
>>
>> I don't agree with you there - the perceived low probability that
>> something will be deployed is a real disincentive here. We have had
>> people wanting to do work on this and have been told there's no point
>> because it won't get adopted.
>
> Let's speak plainly here.
>
> It's not hard for new things to be deployed -- there are lots of new things being deployed on the Web right now.
>
> What IS hard is forcing browser vendors to deploy something that they don't think is going to work, or that they're not terribly interested in.
>
> They are VERY VERY VERY interested in security, as are many other people in the broader community. If the IETF were to come up with a viable proposal that solves their problems, they would beat down this organisation's doors.
>
> The IETF may have some smart people, and they may have ideas about Web security, but that doesn't necessarily make them into workable solutions for the various stakeholders. The discussion about Web security is much broader, involving not only the browser vendors, but also organisations like the W3C, IIW, etc.
>
> Using HTTP/2.0 as a mechanism to shortcut all of this and force what people in the IETF think is a good solution down implementers' throats is going to lead to a very predictable and messy fail.
>
>
>> With this plan if httpbis in fact select zero new proposals
>> that would represent a failure for all concerned. The "zero
>> or more" term is absolutely not intended to provide a way to
>> just punt on the question.
>
> This makes me very uncomfortable. How hard and long do we have to try before we convince you that we're not punting?
>
>
>> Such a failure at the point where httpbis was re-chartering
>> to work on a HTTP/2.0 selection with no better security than
>> we now have is probably better evaluated as a whole - I
>> guess the question for the IETF/IESG at that point would
>> be whether the Internet would be better with or without
>> such a beast, or better waiting a while until the security
>> thing did get fixed.
>
>
> If we "wait a while until the security thing [does] get fixed", I'll gladly bet any amount of money you care to name that SPDY will gain market traction so quickly as to make any HTTP/2.0 effort in IETF completely backwards-looking. Refer to the debacle with Cookies for one such example.
>
> So, again, I'm fine with allowing new authentication schemes to be proposed, in the off chance that some genius will suddenly propose something that meets all of the myriad requirements (that still aren't well-defined) and gets consensus and buy-in from implementers.
>
> However, requiring us to output such a beast and gating HTTP/2.0 on it is effectively asking us to spin our wheels for n years. And the folks working on SPDY will - quite rightly - walk away and do their work somewhere more sane.
>
> And I still don't see why it's necessary to do this all in one effort. Julian's point was that the only technical reason to combine authentication work with re-specifying HTTP is to make the new authentication scheme MTI. Otherwise, the work can be done separately. Roy has expressed interest in coming up with a new scheme that isn't necessarily targeted at browsers -- which is great, but I don't see why it has to be part of this WG.
>
> We potentially have a LOT of work on our plate, and that work is channeling the energy behind a new serialisation of HTTP into something worthy of being called HTTP. Doing research and development on Web security is a very different kind of work, and the two don't mix well, IME.
>
>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From mnot@mnot.net  Sat Feb 25 16:44:41 2012
Return-Path: <mnot@mnot.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 43C0321F84D5; Sat, 25 Feb 2012 16:44:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.756
X-Spam-Level: 
X-Spam-Status: No, score=-104.756 tagged_above=-999 required=5 tests=[AWL=-2.287, BAYES_00=-2.599, SARE_RMML_Stock10=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NuAa4RtrlLAj; Sat, 25 Feb 2012 16:44:40 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2889421F84D3; Sat, 25 Feb 2012 16:44:40 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.33.226]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B81B622E1F4; Sat, 25 Feb 2012 19:44:32 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F497F6D.8050503@cs.tcd.ie>
Date: Sun, 26 Feb 2012 11:44:29 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net> <4F497F6D.8050503@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:44:41 -0000

On 26/02/2012, at 11:40 AM, Stephen Farrell wrote:

>=20
> Mark,
>=20
> I was going to respond blow-by-blow but there's not much
> point in that, other than to say that your mail seems to
> me a tad over the top.

Sorry if you think so. I'm VERY sensitive to the risks that we're =
undertaking here, and I want to be crystal-clear about what we're going =
to do. As I saw it, your path forward was a risky one.


> (Maybe you misinterpreted me describing what might happen
> as some kind of threat to try slow people down or something,
> I don't know. I do know that I don't do that kind of thing
> and if I tried I probably wouldn't be very good at it anyway;-)

It may not have been your intent; my concern was that the effect would =
be the same.


> Anyway, I think we should focus on a way forward that attempts
> progress on what we appear to agree is the desirable outcome:
>=20
> > They are VERY VERY VERY interested in security, as are many other
> > people in the broader community. If the IETF were to come up with a
> > viable proposal that solves their problems, they would beat down =
this
> > organisation's doors.
>=20
> I proposed a plan that I think might allow us to make progress
> on that. I believe we could.

OK, great.=20

Could you please explain why you think tying this effort to HTTP/2.0 is =
necessary to achieve that? To me that's the critical bit, and I still =
haven't seen the reasoning (perhaps I missed it).

Thanks,


>=20
> S
>=20
>=20
>=20
> On 02/25/2012 11:25 PM, Mark Nottingham wrote:
>>=20
>> On 26/02/2012, at 1:13 AM, Stephen Farrell wrote:
>>>>=20
>>>> If we just need a new authentication scheme, nothing stops people =
from
>>>> working on that right now.
>>>=20
>>> I don't agree with you there - the perceived low probability that
>>> something will be deployed is a real disincentive here. We have had
>>> people wanting to do work on this and have been told there's no =
point
>>> because it won't get adopted.
>>=20
>> Let's speak plainly here.
>>=20
>> It's not hard for new things to be deployed -- there are lots of new =
things being deployed on the Web right now.
>>=20
>> What IS hard is forcing browser vendors to deploy something that they =
don't think is going to work, or that they're not terribly interested =
in.
>>=20
>> They are VERY VERY VERY interested in security, as are many other =
people in the broader community. If the IETF were to come up with a =
viable proposal that solves their problems, they would beat down this =
organisation's doors.
>>=20
>> The IETF may have some smart people, and they may have ideas about =
Web security, but that doesn't necessarily make them into workable =
solutions for the various stakeholders. The discussion about Web =
security is much broader, involving not only the browser vendors, but =
also organisations like the W3C, IIW, etc.
>>=20
>> Using HTTP/2.0 as a mechanism to shortcut all of this and force what =
people in the IETF think is a good solution down implementers' throats =
is going to lead to a very predictable and messy fail.
>>=20
>>=20
>>> With this plan if httpbis in fact select zero new proposals
>>> that would represent a failure for all concerned. The "zero
>>> or more" term is absolutely not intended to provide a way to
>>> just punt on the question.
>>=20
>> This makes me very uncomfortable. How hard and long do we have to try =
before we convince you that we're not punting?
>>=20
>>=20
>>> Such a failure at the point where httpbis was re-chartering
>>> to work on a HTTP/2.0 selection with no better security than
>>> we now have is probably better evaluated as a whole - I
>>> guess the question for the IETF/IESG at that point would
>>> be whether the Internet would be better with or without
>>> such a beast, or better waiting a while until the security
>>> thing did get fixed.
>>=20
>>=20
>> If we "wait a while until the security thing [does] get fixed", I'll =
gladly bet any amount of money you care to name that SPDY will gain =
market traction so quickly as to make any HTTP/2.0 effort in IETF =
completely backwards-looking. Refer to the debacle with Cookies for one =
such example.
>>=20
>> So, again, I'm fine with allowing new authentication schemes to be =
proposed, in the off chance that some genius will suddenly propose =
something that meets all of the myriad requirements (that still aren't =
well-defined) and gets consensus and buy-in from implementers.
>>=20
>> However, requiring us to output such a beast and gating HTTP/2.0 on =
it is effectively asking us to spin our wheels for n years. And the =
folks working on SPDY will - quite rightly - walk away and do their work =
somewhere more sane.
>>=20
>> And I still don't see why it's necessary to do this all in one =
effort. Julian's point was that the only technical reason to combine =
authentication work with re-specifying HTTP is to make the new =
authentication scheme MTI. Otherwise, the work can be done separately. =
Roy has expressed interest in coming up with a new scheme that isn't =
necessarily targeted at browsers -- which is great, but I don't see why =
it has to be part of this WG.
>>=20
>> We potentially have a LOT of work on our plate, and that work is =
channeling the energy behind a new serialisation of HTTP into something =
worthy of being called HTTP. Doing research and development on Web =
security is a very different kind of work, and the two don't mix well, =
IME.
>>=20
>>=20
>>=20
>> --
>> Mark Nottingham   http://www.mnot.net/
>>=20
>>=20
>>=20
>>=20

--
Mark Nottingham   http://www.mnot.net/




From stephen.farrell@cs.tcd.ie  Sat Feb 25 17:32:17 2012
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 9FEC921F847C; Sat, 25 Feb 2012 17:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.469
X-Spam-Level: 
X-Spam-Status: No, score=-104.469 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, SARE_RMML_Stock10=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76HX6ddEZGpX; Sat, 25 Feb 2012 17:32:16 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id 70BFA21F85F3; Sat, 25 Feb 2012 17:32:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 9A738171C9E; Sun, 26 Feb 2012 01:32:15 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330219934; bh=SCmLm2tZHPA8ld ltH7RNqDn+DLAc2JrSKLAJI6MsmRA=; b=CoIlXTFxI4zirY2wsND3N5YPIqDp70 6ShKvvxN3I5F/rZ1xYQwyFHf7Bs4M1sF36qJ2h2VDNrQ8j467DMnqaQZU3xSVZhe DMP7WMSoBg9eD0UcQTyuz+Z5ea5yyCtMIScwvrcAQ8CTXCZGR/K3rOnBGm/YF3EA 9g+vUualbx4EIGnjFKDzFKjcO4K7XxOr167zCEJ62J/UsNlXuJZN5Ql/5mIByd8X KM4lQFjLFQhy0sr6REhliB+whGanFBIPM0ZAcoCVSEdmAG7DwojtiGi1qdkal0w/ AQNq+ISz5C2Hd15Os0ptEqfICgXpEXbzBfDmfL3JLW7AmgGzSxltvrnA==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id qmUqBddEuH5B; Sun, 26 Feb 2012 01:32:14 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.27.138]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id BEAA5171C2F; Sun, 26 Feb 2012 01:32:12 +0000 (GMT)
Message-ID: <4F498B9B.1030707@cs.tcd.ie>
Date: Sun, 26 Feb 2012 01:32:11 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net> <4F497F6D.8050503@cs.tcd.ie> <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net>
In-Reply-To: <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:32:17 -0000

On 02/26/2012 12:44 AM, Mark Nottingham wrote:
>
> On 26/02/2012, at 11:40 AM, Stephen Farrell wrote:
>
>>
>> Mark,
>>
>> I was going to respond blow-by-blow but there's not much
>> point in that, other than to say that your mail seems to
>> me a tad over the top.
>
> Sorry if you think so. I'm VERY sensitive to the risks that we're undertaking here,

Fair 'nuff. I consider my self fairly insensitive generally
which of course means I don't care what others think about
that:-)

 > and I want to be crystal-clear about what we're going to do.
 > As I saw it, your path forward was a risky one.

I don't get that. I'd be interested in why it appears that way
to you and if there are ways to reduce risk but still try
make progress on security stuff.

>> (Maybe you misinterpreted me describing what might happen
>> as some kind of threat to try slow people down or something,
>> I don't know. I do know that I don't do that kind of thing
>> and if I tried I probably wouldn't be very good at it anyway;-)
>
> It may not have been your intent; my concern was that the effect would be the same.

Don't get that either. I think I just pointed out the obvious
based on the proposed charter - at the point of the next proposed
re-charter, there'll be IETF/IESG review.

>> Anyway, I think we should focus on a way forward that attempts
>> progress on what we appear to agree is the desirable outcome:
>>
>>> They are VERY VERY VERY interested in security, as are many other
>>> people in the broader community. If the IETF were to come up with a
>>> viable proposal that solves their problems, they would beat down this
>>> organisation's doors.
>>
>> I proposed a plan that I think might allow us to make progress
>> on that. I believe we could.
>
> OK, great.
>
> Could you please explain why you think tying this effort to HTTP/2.0 is necessary to achieve that? To me that's the critical bit, and I still haven't seen the reasoning (perhaps I missed it).

That's a fair question that doesn't have a good and quick
answer, and some of the argument applies to the httpbis wg
and not to HTTP/2.0 per se.

Caveats: this is probably something that needs more bandwidth
than mail; most of the points below were already raised by
others on this thread (though I didn't go back through all
the mail yet) and this is not in any particular ordering.

- We've not really improved this in over a decade. Its time.
- The community's appreciation of better security has
   changed in that time as well so maybe its more tractable
   now and we've more experience of real attacks.
- Improving security after the fact is not a good plan.
- Thinking a separate security WG could provide an answer
   that'd be adopted seems less likely to work to some. (It
   does seem more likely to work for some others admittedly.)
- A backwards-incompatible change (if needed) could be
   done much more easily when changing HTTP. Its at least
   time to explore the area with that possibility in mind..
- A scheme less susceptible to phishing that got deployed
   could be very valuable. Its not ridiculous to think that
   might require breaking backwards compatibility somehow.

So, a bunch of things. Maybe none individually compelling.
But arguably taken together sufficiently convincing that
not attempting again to do something here would really be
inexcusable.

And yes, I do recognise that attempting to solve this does
add some risk. Most good things do.

S.


> Thanks,
>
>
>>
>> S
>>
>>
>>
>> On 02/25/2012 11:25 PM, Mark Nottingham wrote:
>>>
>>> On 26/02/2012, at 1:13 AM, Stephen Farrell wrote:
>>>>>
>>>>> If we just need a new authentication scheme, nothing stops people from
>>>>> working on that right now.
>>>>
>>>> I don't agree with you there - the perceived low probability that
>>>> something will be deployed is a real disincentive here. We have had
>>>> people wanting to do work on this and have been told there's no point
>>>> because it won't get adopted.
>>>
>>> Let's speak plainly here.
>>>
>>> It's not hard for new things to be deployed -- there are lots of new things being deployed on the Web right now.
>>>
>>> What IS hard is forcing browser vendors to deploy something that they don't think is going to work, or that they're not terribly interested in.
>>>
>>> They are VERY VERY VERY interested in security, as are many other people in the broader community. If the IETF were to come up with a viable proposal that solves their problems, they would beat down this organisation's doors.
>>>
>>> The IETF may have some smart people, and they may have ideas about Web security, but that doesn't necessarily make them into workable solutions for the various stakeholders. The discussion about Web security is much broader, involving not only the browser vendors, but also organisations like the W3C, IIW, etc.
>>>
>>> Using HTTP/2.0 as a mechanism to shortcut all of this and force what people in the IETF think is a good solution down implementers' throats is going to lead to a very predictable and messy fail.
>>>
>>>
>>>> With this plan if httpbis in fact select zero new proposals
>>>> that would represent a failure for all concerned. The "zero
>>>> or more" term is absolutely not intended to provide a way to
>>>> just punt on the question.
>>>
>>> This makes me very uncomfortable. How hard and long do we have to try before we convince you that we're not punting?
>>>
>>>
>>>> Such a failure at the point where httpbis was re-chartering
>>>> to work on a HTTP/2.0 selection with no better security than
>>>> we now have is probably better evaluated as a whole - I
>>>> guess the question for the IETF/IESG at that point would
>>>> be whether the Internet would be better with or without
>>>> such a beast, or better waiting a while until the security
>>>> thing did get fixed.
>>>
>>>
>>> If we "wait a while until the security thing [does] get fixed", I'll gladly bet any amount of money you care to name that SPDY will gain market traction so quickly as to make any HTTP/2.0 effort in IETF completely backwards-looking. Refer to the debacle with Cookies for one such example.
>>>
>>> So, again, I'm fine with allowing new authentication schemes to be proposed, in the off chance that some genius will suddenly propose something that meets all of the myriad requirements (that still aren't well-defined) and gets consensus and buy-in from implementers.
>>>
>>> However, requiring us to output such a beast and gating HTTP/2.0 on it is effectively asking us to spin our wheels for n years. And the folks working on SPDY will - quite rightly - walk away and do their work somewhere more sane.
>>>
>>> And I still don't see why it's necessary to do this all in one effort. Julian's point was that the only technical reason to combine authentication work with re-specifying HTTP is to make the new authentication scheme MTI. Otherwise, the work can be done separately. Roy has expressed interest in coming up with a new scheme that isn't necessarily targeted at browsers -- which is great, but I don't see why it has to be part of this WG.
>>>
>>> We potentially have a LOT of work on our plate, and that work is channeling the energy behind a new serialisation of HTTP into something worthy of being called HTTP. Doing research and development on Web security is a very different kind of work, and the two don't mix well, IME.
>>>
>>>
>>>
>>> --
>>> Mark Nottingham   http://www.mnot.net/
>>>
>>>
>>>
>>>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From mnot@mnot.net  Sat Feb 25 17:54:15 2012
Return-Path: <mnot@mnot.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 71A0121F861E; Sat, 25 Feb 2012 17:54:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.814
X-Spam-Level: 
X-Spam-Status: No, score=-104.814 tagged_above=-999 required=5 tests=[AWL=-2.215, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PfJZtzxRAvhD; Sat, 25 Feb 2012 17:54:14 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 67F7421F861D; Sat, 25 Feb 2012 17:54:14 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.33.226]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D6F1722E253; Sat, 25 Feb 2012 20:54:06 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F498B9B.1030707@cs.tcd.ie>
Date: Sun, 26 Feb 2012 12:54:02 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D14BBB56-C76F-438B-8509-2333923FE19B@mnot.net>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net> <4F497F6D.8050503@cs.tcd.ie> <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net> <4F498B9B.1030707@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1257)
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:54:15 -0000

On 26/02/2012, at 12:32 PM, Stephen Farrell wrote:

>> Could you please explain why you think tying this effort to HTTP/2.0 =
is necessary to achieve that? To me that's the critical bit, and I still =
haven't seen the reasoning (perhaps I missed it).
>=20
> That's a fair question that doesn't have a good and quick
> answer, and some of the argument applies to the httpbis wg
> and not to HTTP/2.0 per se.

Aha. If we can decouple the auth work from the HTTP/2.0 deliverable, I'm =
less concerned -- although we're going to be quite busy.=20

For *this* re-charter, can we only solicit proposals for auth, and make =
the decision about what/if we'll go ahead in the *next* re-charter?=20

I.e., I'd like to wait before we decide on both pieces (the wire =
protocol and auth) before making commitments, or even plans. Part of the =
selection process for the wire protocol is determining implementer =
interest, and gathering the same information about the auth proposals =
will shed a lot more light on this conversation, I think.


> Caveats: this is probably something that needs more bandwidth
> than mail; most of the points below were already raised by
> others on this thread (though I didn't go back through all
> the mail yet) and this is not in any particular ordering.

That's OK - we'll be in Paris soon.

> - We've not really improved this in over a decade. Its time.

Don't disagree.

> - The community's appreciation of better security has
>  changed in that time as well so maybe its more tractable
>  now and we've more experience of real attacks.
> - Improving security after the fact is not a good plan.

Of course.

> - Thinking a separate security WG could provide an answer
>  that'd be adopted seems less likely to work to some. (It
>  does seem more likely to work for some others admittedly.)

Yes, there are arguments on both sides.

> - A backwards-incompatible change (if needed) could be
>  done much more easily when changing HTTP. Its at least
>  time to explore the area with that possibility in mind..

Hmm. One of the core ideas we're moving forward with is that 2.0 is =
semantically compatible with 1.x, even if it isn't syntactically.=20

> - A scheme less susceptible to phishing that got deployed
>  could be very valuable. Its not ridiculous to think that
>  might require breaking backwards compatibility somehow.

Agreed, but I think that's much more about the browser UI than about the =
wire protocol.

> So, a bunch of things. Maybe none individually compelling.
> But arguably taken together sufficiently convincing that
> not attempting again to do something here would really be
> inexcusable.
>=20
> And yes, I do recognise that attempting to solve this does
> add some risk. Most good things do.

Absolutely.

Cheers,


--
Mark Nottingham   http://www.mnot.net/




From ynir@checkpoint.com  Sun Feb 26 01:44:30 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F70B21F8507; Sun, 26 Feb 2012 01:44:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.451
X-Spam-Level: 
X-Spam-Status: No, score=-10.451 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YfJYxz7ZcpZb; Sun, 26 Feb 2012 01:44:29 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1667621F8501; Sun, 26 Feb 2012 01:44:28 -0800 (PST)
X-CheckPoint: {4F49FAB1-0-1B221DC2-1FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q1Q9iNWH007812;  Sun, 26 Feb 2012 11:44:23 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Sun, 26 Feb 2012 11:44:22 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Mark Nottingham <mnot@mnot.net>
Date: Sun, 26 Feb 2012 11:44:22 +0200
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Topic: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Index: Acz0azfK51/x3lkvSw+qpEidKkJfrw==
Message-ID: <3B23D486-B6B0-4BF4-8B23-9CC2BB911DD6@checkpoint.com>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>	<4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net>	<4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de>	<4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net>	<4F497F6D.8050503@cs.tcd.ie> <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net>
In-Reply-To: <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: The IESG <iesg@ietf.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 09:44:30 -0000

On Feb 26, 2012, at 2:44 AM, Mark Nottingham wrote:

>=20
>>=20
>> I proposed a plan that I think might allow us to make progress
>> on that. I believe we could.
>=20
> OK, great.=20
>=20
> Could you please explain why you think tying this effort to HTTP/2.0 is n=
ecessary to achieve that? To me that's the critical bit, and I still haven'=
t seen the reasoning (perhaps I missed it).

I think I have *an* answer to this, though probably not *the* answer.

There's two stages to adoption - implementation and roll-out. Obviously you=
 can't roll out "new authentication" before the browsers and servers implem=
ent it. For my website, I wouldn't roll out new auth if only one or two of =
the browsers out there implemented it. Even if all the big ones (IE, Firefo=
x, Chrome, Opera) did, I would still have to provide a backwards compatibil=
ity authentication scheme to support older browsers. This would lead to bot=
h inconsistent UI and to ugly javascript that detects the browser version, =
and makes the roll-out slower.

If any HTTP/2.0 browser is bound to have "new authentication" it makes thin=
gs much easier.

This could be circumvented by adding request headers that advertise capabil=
ities, but I don't think we like those much.

Yoav



From mohta@necom830.hpcl.titech.ac.jp  Sun Feb 26 05:51:02 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF04321F854D for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2012 05:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.154
X-Spam-Level: *
X-Spam-Status: No, score=1.154 tagged_above=-999 required=5 tests=[AWL=-1.170,  BAYES_40=-0.185, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TKFhL4L-oxjN for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2012 05:51:02 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 3076821F8523 for <ietf@ietf.org>; Sun, 26 Feb 2012 05:51:01 -0800 (PST)
Received: (qmail 71288 invoked from network); 26 Feb 2012 14:09:37 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 26 Feb 2012 14:09:37 -0000
Message-ID: <4F4A38A2.2060201@necom830.hpcl.titech.ac.jp>
Date: Sun, 26 Feb 2012 22:50:26 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: [pcp] Last Call: <draft-ietf-pcp-base-23.txt> (Port Control Protocol (PCP))	to Proposed Standard
References: <20120213144208.21185.46414.idtracker@ietfa.amsl.com>
In-Reply-To: <20120213144208.21185.46414.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:51:03 -0000

The IESG wrote:

> The IESG has received a request from the Port Control Protocol WG (pcp)
> to consider the following document:
> - 'Port Control Protocol (PCP)'
>    <draft-ietf-pcp-base-23.txt>  as a 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 2012-02-27.

The protocol lacks transaction IDs and is fatally broken.

That is, the protocol is expected to generate refresh request
packets and expect response packets.

However, as all the request packets are expected to be
identical, it is impossible to have correspondences between
request and response packets.

So, if requests are sent at 0, 5, 240, 245, 480 and 485 seconds
and responses with lifetime of 300 are received at 10, 250 and
490 seconds, it is impossible to know which request corresponds
to the response at 490 seconds.

If the response is generated against request at 485 second,
remaining lifetime of the response is 295 seconds.

However, if the response is generated against request at 0
second, lifetime of the response has expired 190 seconds ago.

But, without transaction ID to distinguish requests and
responses, the worst case must be assumed, which means
the response must be interpreted that lifetime expired
190 seconds ago, which means all the subsequent responses
are meaningless because their lifetime must be interpreted
to have expired.

					Masataka Ohta

From julian.reschke@gmx.de  Sun Feb 26 06:54:29 2012
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 EFDAD21F849C for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2012 06:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.158
X-Spam-Level: 
X-Spam-Status: No, score=-104.158 tagged_above=-999 required=5 tests=[AWL=-1.559, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ER9UGQgD6vn4 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2012 06:54:29 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id DD95521F849A for <ietf@ietf.org>; Sun, 26 Feb 2012 06:54:28 -0800 (PST)
Received: (qmail invoked by alias); 26 Feb 2012 14:54:27 -0000
Received: from p5DCC23AE.dip.t-dialin.net (EHLO [192.168.178.36]) [93.204.35.174] by mail.gmx.net (mp002) with SMTP; 26 Feb 2012 15:54:27 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+7RW54HoK7vUShwaKaW/wanOfBwgdk2Uvo6WkaCs QxG2Rxcjdx4Wz+
Message-ID: <4F4A4792.1010108@gmx.de>
Date: Sun, 26 Feb 2012 15:54:10 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>	<4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net>	<4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de>	<4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net>	<4F497F6D.8050503@cs.tcd.ie> <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net> <3B23D486-B6B0-4BF4-8B23-9CC2BB911DD6@checkpoint.com>
In-Reply-To: <3B23D486-B6B0-4BF4-8B23-9CC2BB911DD6@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Mark Nottingham <mnot@mnot.net>, IETF-Discussion Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:54:30 -0000

On 2012-02-26 10:44, Yoav Nir wrote:
> ...
>> Could you please explain why you think tying this effort to HTTP/2.0 is necessary to achieve that? To me that's the critical bit, and I still haven't seen the reasoning (perhaps I missed it).
>
> I think I have *an* answer to this, though probably not *the* answer.
>
> There's two stages to adoption - implementation and roll-out. Obviously you can't roll out "new authentication" before the browsers and servers implement it. For my website, I wouldn't roll out new auth if only one or two of the browsers out there implemented it. Even if all the big ones (IE, Firefox, Chrome, Opera) did, I would still have to provide a backwards compatibility authentication scheme to support older browsers. This would lead to both inconsistent UI and to ugly javascript that detects the browser version, and makes the roll-out slower.

You can send multiple challenges in one response.

We could also define a way to make HTML-form-based login an HTTP scheme 
(see <http://tools.ietf.org/id/draft-broyer-http-cookie-auth-00.txt>) to 
integrate better what people use today.

> If any HTTP/2.0 browser is bound to have "new authentication" it makes things much easier.
>
> This could be circumvented by adding request headers that advertise capabilities, but I don't think we like those much.

I don't believe we need those. If we do, we should retrofit this into 
1.1 as well.

Anyway, I see lots of theoretical discussion about process. What's 
needed is people doing the actual work, both spec-wise and 
implementation-wise. That's the critical problem.

Best regards, Julian

From tevfik.sahin@turktelekom.com.tr  Sun Feb 26 07:09:25 2012
Return-Path: <tevfik.sahin@turktelekom.com.tr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE2E321F849B; Sun, 26 Feb 2012 07:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.236
X-Spam-Level: *
X-Spam-Status: No, score=1.236 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_TR=0.935, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHBhpKmTmESV; Sun, 26 Feb 2012 07:09:25 -0800 (PST)
Received: from mail.turktelekom.com.tr (mx01.turktelekom.com.tr [212.175.13.103]) by ietfa.amsl.com (Postfix) with ESMTP id 21BD921F848B; Sun, 26 Feb 2012 07:09:23 -0800 (PST)
Received: from (unknown [10.6.98.102]) by AVGW-TT-2.turktelekom.com.tr with smtp id 7889_cad9_dc906de2_608b_11e1_ad97_0022196c83b7; Sun, 26 Feb 2012 17:09:24 +0200
Received: from S000CHS02.turktelekom.intra (10.6.98.202) by S000EDG02.turktelekom.intra (10.6.98.102) with Microsoft SMTP Server (TLS) id 14.2.247.3; Sun, 26 Feb 2012 17:04:42 +0200
Received: from S000MBX01.turktelekom.intra ([fe80::f93e:bfa0:cd47:50cc]) by S000CHS02.turktelekom.intra ([fe80::68ff:d05b:7cf8:2c7b%27]) with mapi id 14.02.0247.003; Sun, 26 Feb 2012 17:04:39 +0200
From: =?utf-8?B?VEVWRsSwSyDFnkFIxLBO?= <tevfik.sahin@turktelekom.com.tr>
To: Mark Nottingham <mnot@mnot.net>, Yoav Nir <ynir@checkpoint.com>
Subject: RE: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Topic: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Thread-Index: AQHM8MZzB6OckiKrhUGDr8GiGGECwpZIMxIA//9ZgACAAAOYAIAAOoIAgAAFvwCAAAOuAIAAALGAgAABh4CAAOu+AIAASpQAgAACEgCAAhFcgIAAAWkAgAABc4CAAMDMAIAA3PUAgADD8wCAAATqgIAAAqmAgACaGgCAABUEgIAAqNWA///vNACAAHsA4w==
Date: Sun, 26 Feb 2012 15:04:38 +0000
Message-ID: <b9TKdqspKX6J@0b0mpBFf>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com>	<4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net>	<4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de>	<4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net>	<4F497F6D.8050503@cs.tcd.ie> <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net>, <3B23D486-B6B0-4BF4-8B23-9CC2BB911DD6@checkpoint.com>
In-Reply-To: <3B23D486-B6B0-4BF4-8B23-9CC2BB911DD6@checkpoint.com>
Accept-Language: tr-TR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-NAI-Spam-Report: 2 Rules triggered *  0.2 -- GEN_SPAM_FEATRE *  0 -- RV4143
X-NAI-Spam-Version: 2.2.0.9309 : core <4143> : streams <732386> : uri <1072446>
Cc: IETF-Discussion Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:09:25 -0000

WmMNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBZb2F2IE5pcg0KU2VudDogIDI2
LjAyLjIwMTIsIDExOjQ1DQpUbzogTWFyayBOb3R0aW5naGFtDQpDYzogVGhlIElFU0c7IGlldGYt
aHR0cC13Z0B3My5vcmcgR3JvdXA7IElFVEYtRGlzY3Vzc2lvbiBEaXNjdXNzaW9uDQpTdWJqZWN0
OiBSZTogV0cgUmV2aWV3OiBSZWNoYXJ0ZXIgb2YgSHlwZXJ0ZXh0IFRyYW5zZmVyIFByb3RvY29s
IEJpcyAoaHR0cGJpcykNCg0KDQpPbiBGZWIgMjYsIDIwMTIsIGF0IDI6NDQgQU0sIE1hcmsgTm90
dGluZ2hhbSB3cm90ZToNCg0KPg0KPj4NCj4+IEkgcHJvcG9zZWQgYSBwbGFuIHRoYXQgSSB0aGlu
ayBtaWdodCBhbGxvdyB1cyB0byBtYWtlIHByb2dyZXNzDQo+PiBvbiB0aGF0LiBJIGJlbGlldmUg
d2UgY291bGQuDQo+DQo+IE9LLCBncmVhdC4NCj4NCj4gQ291bGQgeW91IHBsZWFzZSBleHBsYWlu
IHdoeSB5b3UgdGhpbmsgdHlpbmcgdGhpcyBlZmZvcnQgdG8gSFRUUC8yLjAgaXMgbmVjZXNzYXJ5
IHRvIGFjaGlldmUgdGhhdD8gVG8gbWUgdGhhdCdzIHRoZSBjcml0aWNhbCBiaXQsIGFuZCBJIHN0
aWxsIGhhdmVuJ3Qgc2VlbiB0aGUgcmVhc29uaW5nIChwZXJoYXBzIEkgbWlzc2VkIGl0KS4NCg0K
SSB0aGluayBJIGhhdmUgKmFuKiBhbnN3ZXIgdG8gdGhpcywgdGhvdWdoIHByb2JhYmx5IG5vdCAq
dGhlKiBhbnN3ZXIuDQoNClRoZXJlJ3MgdHdvIHN0YWdlcyB0byBhZG9wdGlvbiAtIGltcGxlbWVu
dGF0aW9uIGFuZCByb2xsLW91dC4gT2J2aW91c2x5IHlvdSBjYW4ndCByb2xsIG91dCAibmV3IGF1
dGhlbnRpY2F0aW9uIiBiZWZvcmUgdGhlIGJyb3dzZXJzIGFuZCBzZXJ2ZXJzIGltcGxlbWVudCBp
dC4gRm9yIG15IHdlYnNpdGUsIEkgd291bGRuJ3Qgcm9sbCBvdXQgbmV3IGF1dGggaWYgb25seSBv
bmUgb3IgdHdvIG9mIHRoZSBicm93c2VycyBvdXQgdGhlcmUgaW1wbGVtZW50ZWQgaXQuIEV2ZW4g
aWYgYWxsIHRoZSBiaWcgb25lcyAoSUUsIEZpcmVmb3gsIENocm9tZSwgT3BlcmEpIGRpZCwgSSB3
b3VsZCBzdGlsbCBoYXZlIHRvIHByb3ZpZGUgYSBiYWNrd2FyZHMgY29tcGF0aWJpbGl0eSBhdXRo
ZW50aWNhdGlvbiBzY2hlbWUgdG8gc3VwcG9ydCBvbGRlciBicm93c2Vycy4gVGhpcyB3b3VsZCBs
ZWFkIHRvIGJvdGggaW5jb25zaXN0ZW50IFVJIGFuZCB0byB1Z2x5IGphdmFzY3JpcHQgdGhhdCBk
ZXRlY3RzIHRoZSBicm93c2VyIHZlcnNpb24sIGFuZCBtYWtlcyB0aGUgcm9sbC1vdXQgc2xvd2Vy
Lg0KDQpJZiBhbnkgSFRUUC8yLjAgYnJvd3NlciBpcyBib3VuZCB0byBoYXZlICJuZXcgYXV0aGVu
dGljYXRpb24iIGl0IG1ha2VzIHRoaW5ncyBtdWNoIGVhc2llci4NCg0KVGhpcyBjb3VsZCBiZSBj
aXJjdW12ZW50ZWQgYnkgYWRkaW5nIHJlcXVlc3QgaGVhZGVycyB0aGF0IGFkdmVydGlzZSBjYXBh
YmlsaXRpZXMsIGJ1dCBJIGRvbid0IHRoaW5rIHdlIGxpa2UgdGhvc2UgbXVjaC4NCg0KWW9hdg0K
DQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpJZXRm
IG1haWxpbmcgbGlzdA0KSWV0ZkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pZXRmDQoNCg0KDQrigJxUaGlzIE1lc3NhZ2UgKGluY2x1ZGluZyBhbnkgYXR0
YWNobWVudHMpIGNvbnRhaW5zIGNvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBhbmQgaXMgaW50ZW5k
ZWQgb25seSBmb3IgdGhlIGluZGl2aWR1YWwgbmFtZWQuIElmIHlvdSBhcmUgbm90IHRoZSBuYW1l
ZCBhZHJlc3NlZSBvciBub3QgcmVsYXRlZCB3aXRoIHRoZSBjb250ZW50IG9mIHRoaXMgTWVzc2Fn
ZSwgeW91IGFyZSBmb3JiaWRkZW4gdG8gcmVhZCwgZGlzc2VtaW5hdGUsIGRpc3RyaWJ1dGUsIGNv
cHksIHJlcHJvZHVjZSBvciBtb2RpZnkgdGhpcyBtYWlsIGJ5IG91ciBDb21wYW55LiBQbGVhc2Ug
bm90ZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBpZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGUt
bWFpbCBieSBtaXN0YWtlIGFuZCBkZWxldGUgdGhpcyBlLW1haWwgZnJvbSB5b3VyIHN5c3RlbS4g
RS1tYWlsIHRyYW5zbWlzc29uIGNhbiBub3QgYmUgZ3VhcmFudGVlZCB0byBiZSBzZWN1cmUgb3Ig
ZXJyb3ItZnJlZSBhcyB0aGUgbWFpbCBtYXkgYXJyaXZlIGxhdGUgb3IgaW5jb21wbGV0ZSBvciB0
aGUgaW5mb3JtYXRpb24gY291bGQgYmUgaW50ZXJjZXB0ZWQsIGNvcnJ1cHRlZCwgbG9zdCwgZGVz
dHJveWVkLCBhbWVuZGVkLCAsIG9yIGNvbnRhaW4gdmlydXNlcy4gVGhlIHNlbmRlciB0aGVyZWZv
cmUgZG9lcyBub3QgYWNjZXB0IGxpYWJpbGl0eSBmb3IgYW55IGVycm9ycywgbG9zcyBvZiBpbnRl
Z3JpdHkgb3IgY29uZmlkZW50aWFsaXR5IG9yIG9tbWlzc2lvbnMgaW4gdGhlIGNvbnRlbnRzIG9m
IHRoaXMgTWVzc2FnZSBvciBmb3IgdGhlIGluZm9ybWF0aW9uIHRyYW5zbWlzc2lvbiwgcmVjZXB0
aW9uLCBzdG9yYWdlIG9mIHVzZSBvZiBzdWNoIGluIGFueSB3YXkgd2hhdHNvZXZlciwgd2hpY2gg
YXJpc2UgYXMgYSByZXN1bHQgb2YgZS1tYWlsIHRyYW5zbWlzc2lvbi4gQW55IG9waW5pb25zIGV4
cHJlc3NlZCBpbiB0aGlzIG1lc3NhZ2UgYXJlIHRob3NlIG9mIHRoZSBhdXRob3IgYW5kIG1heSBu
b3QgbmVjZXNzYXJpbHkgcmVmbGVjdCB0aGUgb3BpbmlvbnMgb2YgT3VyIENvbXBhbnkuDQoNCkNv
cHlyaWdodCBpbiBkb2N1bWVudHMgY3JlYXRlZCBieSBvciBvbiBiZWhhbGYgb2Ygb3VyIENvbXBh
bnkgcmVtYWlucyB2ZXN0ZWQgaW4gdXMsIGFuZCB3ZSBhc3NlcnQgYWxsIG9mIG91ciBtb3JhbCBh
bmQgaW50ZWxsZWN0dWFsIHByb3BlcnR5IHJpZ2h0cy7igJ0NCg0KDQrigJxCdSBtZXNhaiAodmUg
ZWtsZXJpKSBnaXpsaSBiaWxnaSBpw6dlcm1la3RlZGlyIHZlIHNhZGVjZSBnw7ZuZGVyaWxlbiBr
acWfaXllIHnDtm5lbGlrdGlyLiBCdSBlLW1haWxpbiBtdWhhdGFixLEgZGXEn2lsc2VuaXogdmV5
YSBpw6dlcmnEn2kgaWxlIGlsZ2luaXogeW9rc2EsIMWeaXJrZXRpbWl6aW4gb25hecSxIG9sbWFr
c8SxesSxbiBidSBtZXNhasSxbiBva3VubWFzxLEsIGRlxJ9pxZ90aXJpbG1lc2ksIGtvcHlhbGFu
bWFzxLEsIMO8w6fDvG5jw7wga2nFn2lsZXJlIGHDp8Sxa2xhbm1hc8SxLCB5YXnEsW5sYW5tYXPE
sSwgaWbFn2EgZWRpbG1lc2kgdmV5YSBpbGV0aWxtZXNpIHlhc2FrdMSxci4gQnUgbWVzYWrEsW4g
Z8O2bmRlcmlsbWVrIGlzdGVuZGnEn2kga2nFn2kgZGXEn2lsc2VuaXogKHlhIGRhIGJ1IGUtcG9z
dGEnecSxIHlhbmzEscWfbMSxa2xhIGFsZMSxeXNhbsSxeiksIGzDvHRmZW4geW9sbGF5YW4ga2nF
n2l5aSBoZW1lbiBoYWJlcmRhciBlZGluaXogdmUgbWVzYWrEsSBzaXN0ZW1pbml6ZGVuIGRlcmhh
bCBzaWxpbml6LiBFLW1haWwgaWxldGltaW5pbiBnw7x2ZW5saSB2ZXlhIGhhdGFzxLF6IG9sZHXE
n3VudW4gZ2FyYW50aXNpIG9sbWFkxLHEn8SxbmRhbiBnZcOnIHZleWEgZWtzaWsgaWxldGltIHZl
eWEgacOnZXJpayB2ZSBiaWxnaWxlcmRlIGVrc2lrbGlrLCBrYXnEsXAsIGRlxJ9pxZ9pa2xpayB2
ZXlhIHZpcsO8cyBvbGFiaWxpci4gQnUgbmVkZW5sZSwgYnUgbWVzYWrEsW4gaWxldGltaW5kZW4g
ZG9sYXnEsSwgZ8O2bmRlcmVuLCBpw6dlcmlrdGVraSBoYXRhLCBla3Npa2xpaywgZG/En3J1bHXE
n3VuIHZlIGdpemxpbGnEn2luIGlobGFsaW5kZW4gdmV5YSBidSB5b2xsYSBiaWxnaSBwYXlsYcWf
xLFtxLEsIGlsZXRpbWksIGRlcG9sYW5tYXPEsSBnaWJpIGhlcmhhbmdpIGJpciBrdWxsYW7EsW3E
sW5kYW4gaGnDp2JpciDFn2VraWxkZSBzb3J1bWx1IGRlxJ9pbGRpci4gQnUgbWVzYWrEsW4gacOn
ZXJpxJ9pIHlhemFyxLFuYSBhaXQgb2x1cCwgxZ5pcmtldGltaXppbiBnw7Zyw7zFn2xlcmluaSBp
w6dlcm1leWViaWxpci4NCg0KQnUgbWVzYWrEsW4gacOnZXJpxJ9pbmRlIGdlw6dlbiDFnmlya2V0
aW1pemluIGFkIHZleWEgbmFuxLFtYSB5YXJhdMSxbGFuIGZpa3JpIHZlIHPEsW5haSBoYWtsYXIg
xZ5pcmtldGltaXplIGFpdCBvbHVwLCBtYWRkaSB2ZSBtYW5ldmkgdMO8bSBoYWtsYXLEsSDFnmly
a2V0aW1pemRlIHNha2zEsWTEsXIu4oCdDQo=

From stephen.farrell@cs.tcd.ie  Sun Feb 26 13:49:37 2012
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 B10CA21F84B5; Sun, 26 Feb 2012 13:49:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.534
X-Spam-Level: 
X-Spam-Status: No, score=-104.534 tagged_above=-999 required=5 tests=[AWL=-1.935, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ek6lYxcIAyak; Sun, 26 Feb 2012 13:49:36 -0800 (PST)
Received: from scss.tcd.ie (hermes.scss.tcd.ie [IPv6:2001:770:10:200:889f:cdff:fe8d:ccd2]) by ietfa.amsl.com (Postfix) with ESMTP id A08C821F8499; Sun, 26 Feb 2012 13:49:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id D1A39171C7D; Sun, 26 Feb 2012 21:49:34 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1330292974; bh=cSHBSFSY5I4jr/ zvBxBuQAriRdyYvLhUKveb7onUePo=; b=v07h7lTgNHLN6PLfvIV3p9WxqZDykJ bJAbNT9nhiOfl8TgEwhKPFqjJChXGTag2KFB4NdUGQu8wts66mcqQ6ZW2538XjvA wLZuAuvfmbbPnKYzxxX6zIfsDbIkiBoJDZHEwkgRtqtTPoX+NcYoUOHeCvffL9jr dmevr0t65XZiz32Gw85ZvqIxVyglNtobUFhVIyueL6MDYADkCViHvgZmIQU5rywx 83EPlpiaZzbEHuo+DfLAOCB7hVawujuqC4wIH9AGeiyut/ti0AWy8aqcLDV39J+3 5qagmpgpJWuYBrwOPmCbwz0kqlPdhq8j5rlSdp/6k9W6RSLY1L6p3/4A==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id CEdfWukYwCsk; Sun, 26 Feb 2012 21:49:34 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.27.138]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id CA575171BFF; Sun, 26 Feb 2012 21:49:31 +0000 (GMT)
Message-ID: <4F4AA8EA.5020608@cs.tcd.ie>
Date: Sun, 26 Feb 2012 21:49:30 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <F3264756-52C3-4ABD-BF37-9500582F987F@mnot.net> <4F497F6D.8050503@cs.tcd.ie> <A07BCB40-13BA-47D2-AED5-D33D5A564724@mnot.net> <4F498B9B.1030707@cs.tcd.ie> <D14BBB56-C76F-438B-8509-2333923FE19B@mnot.net>
In-Reply-To: <D14BBB56-C76F-438B-8509-2333923FE19B@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:49:38 -0000

On 02/26/2012 01:54 AM, Mark Nottingham wrote:
>
> On 26/02/2012, at 12:32 PM, Stephen Farrell wrote:
>
>>> Could you please explain why you think tying this effort to HTTP/2.0 is necessary to achieve that? To me that's the critical bit, and I still haven't seen the reasoning (perhaps I missed it).
>>
>> That's a fair question that doesn't have a good and quick
>> answer, and some of the argument applies to the httpbis wg
>> and not to HTTP/2.0 per se.
>
> Aha. If we can decouple the auth work from the HTTP/2.0 deliverable, I'm less concerned -- although we're going to be quite busy.
>
> For *this* re-charter, can we only solicit proposals for auth, and make the decision about what/if we'll go ahead in the *next* re-charter?
>
> I.e., I'd like to wait before we decide on both pieces (the wire protocol and auth) before making commitments, or even plans. Part of the selection process for the wire protocol is determining implementer interest, and gathering the same information about the auth proposals will shed a lot more light on this conversation, I think.

Right, that's pretty close to what I proposed.

Let's see if we hear supportive noises or howls of outrage or silence.

I think I'd suggest to keep the idea of chartering a sec wg to pick up
the pieces that httpbis doesn't want to progress, once that situation 
becomes clear. All going well, that'd result in some experimental RFCs
that could be picked up with little effort should events warrant. But
that doesn't directly impact on httpbis I guess.

S.




>
>> Caveats: this is probably something that needs more bandwidth
>> than mail; most of the points below were already raised by
>> others on this thread (though I didn't go back through all
>> the mail yet) and this is not in any particular ordering.
>
> That's OK - we'll be in Paris soon.
>
>> - We've not really improved this in over a decade. Its time.
>
> Don't disagree.
>
>> - The community's appreciation of better security has
>>   changed in that time as well so maybe its more tractable
>>   now and we've more experience of real attacks.
>> - Improving security after the fact is not a good plan.
>
> Of course.
>
>> - Thinking a separate security WG could provide an answer
>>   that'd be adopted seems less likely to work to some. (It
>>   does seem more likely to work for some others admittedly.)
>
> Yes, there are arguments on both sides.
>
>> - A backwards-incompatible change (if needed) could be
>>   done much more easily when changing HTTP. Its at least
>>   time to explore the area with that possibility in mind..
>
> Hmm. One of the core ideas we're moving forward with is that 2.0 is semantically compatible with 1.x, even if it isn't syntactically.
>
>> - A scheme less susceptible to phishing that got deployed
>>   could be very valuable. Its not ridiculous to think that
>>   might require breaking backwards compatibility somehow.
>
> Agreed, but I think that's much more about the browser UI than about the wire protocol.
>
>> So, a bunch of things. Maybe none individually compelling.
>> But arguably taken together sufficiently convincing that
>> not attempting again to do something here would really be
>> inexcusable.
>>
>> And yes, I do recognise that attempting to solve this does
>> add some risk. Most good things do.
>
> Absolutely.
>
> Cheers,
>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From Feng.f.Huang@alcatel-sbell.com.cn  Sun Feb 26 19:58:17 2012
Return-Path: <Feng.f.Huang@alcatel-sbell.com.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 AFC0721E8014 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2012 19:58:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.706
X-Spam-Level: 
X-Spam-Status: No, score=0.706 tagged_above=-999 required=5 tests=[AWL=-0.898,  BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LUqqfKTdHpIB for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2012 19:58:17 -0800 (PST)
Received: from cnshjsmin03.alcatel-sbell.com.cn (cnshjsmin03.alcatel-sbell.com.cn [211.144.215.47]) by ietfa.amsl.com (Postfix) with ESMTP id 2B83C21E8017 for <ietf@ietf.org>; Sun, 26 Feb 2012 19:58:15 -0800 (PST)
X-AuditID: ac189297-b7c66ae0000047b3-7a-4f4aff5294e5
Received: from CNSHJCASHUB03.ad4.ad.alcatel.com (Unknown_Domain [135.251.50.73]) by cnshjsmin03.alcatel-sbell.com.cn (Symantec Brightmail Gateway) with SMTP id 03.F0.18355.25FFA4F4; Mon, 27 Feb 2012 11:58:10 +0800 (HKT)
Received: from CNSHJMBX01.ad4.ad.alcatel.com ([135.251.50.101]) by CNSHJCASHUB03.ad4.ad.alcatel.com ([135.251.50.73]) with mapi id 14.01.0323.000; Mon, 27 Feb 2012 11:58:10 +0800
From: HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an	Associated Channel Code Point for Use byITU-T Ethernet	based	OAM) to Informational RFC
Thread-Topic: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an	Associated Channel Code Point for Use byITU-T Ethernet	based	OAM) to Informational RFC
Thread-Index: AQGdS0dQFbRu6GyAeWPtVTnp+xX6JJaoU1awgAFDNYCABc0QYA==
Date: Mon, 27 Feb 2012 03:58:09 +0000
Message-ID: <796B6F5769D3E140A2BC3AAF7AC8D57F0A85B5@cnshjmbx01>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
In-Reply-To: <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.24.143.193]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:58:17 -0000

KzENCg0KVGhlIEludGVybmV0IEVuZ2luZWVyaW5nIFRhc2sgRm9yY2UgKElFVEYpIGlzIGEgbGFy
Z2Ugb3BlbiBpbnRlcm5hdGlvbmFsIGNvbW11bml0eSwgaXQgc2hvdWxkIHN1cHBvcnQgcnVubmlu
ZyBjb2RlIGhhcyBiZWVuIGRlcGxveWVkIGluIHJlYWwgbmV0d29yay4NCg0KUXVvdGUgZnJvbSBE
YXZpZCBDbGFyazogIldlIHJlamVjdCBraW5ncywgcHJlc2lkZW50cyBhbmQgdm90aW5nLiBXZSBi
ZWxpZXZlIGluIHJvdWdoIGNvbnNlbnN1cyBhbmQgcnVubmluZyBjb2RlIi4NCg0KQi5SLg0KRmVu
Zw0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0
Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBEYW5pZWwg
Q29obg0KU2VudDogMjAxMsTqMtTCMjPI1SAxODozNQ0KVG86IGlldGZAaWV0Zi5vcmcNClN1Ympl
Y3Q6IFJFOiBbUFdFM10gRlc6IExhc3QgQ2FsbDogPGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNv
ZGUtcG9pbnQtMDMudHh0PihBbGxvY2F0aW9uIG9mIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2Rl
IFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldCBiYXNlZCBPQU0pIHRvIEluZm9ybWF0aW9u
YWwgUkZDDQoNClN1cHBvcnQgLSBhcyB0aGVyZSBpcyBubyBmb3Jlc2VlbiBzaG9ydGFnZSBpbiBB
Q0ggdHlwZXMsIEkgZG9uJ3Qgc2VlIGENCnJlYXNvbiB3aHkgdGhpcyBjb2RlIHBvaW50IHNob3Vs
ZCBub3QgYmUgYWxsb2NhdGVkIHRvIGFuIElUVSBkZXZlbG9wZWQNCnByb3RvY29sIHRoYXQgaXMg
YWxyZWFkeSBkZXBsb3llZCBpbiB0aGUgZmllbGQuDQoNCkRDDQoNCj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0Zi1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnIFttYWls
dG86aWV0Zi1hbm5vdW5jZS0NCj4gYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFRoZSBJ
RVNHDQo+IFNlbnQ6IDIyIEZlYnJ1YXJ5IDIwMTIgMTU6MTMNCj4gVG86IElFVEYtQW5ub3VuY2UN
Cj4gU3ViamVjdDogTGFzdCBDYWxsOiA8ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2lu
dC0wMy50eHQ+DQooQWxsb2NhdGlvbiBvZg0KYW4NCj4gQXNzb2NpYXRlZCBDaGFubmVsIENvZGUg
UG9pbnQgZm9yIFVzZSBieSBJVFUtVCBFdGhlcm5ldCBiYXNlZCBPQU0pIHRvDQo+IEluZm9ybWF0
aW9uYWwgUkZDDQo+IA0KPiANCj4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9t
IGFuIGluZGl2aWR1YWwgc3VibWl0dGVyIHRvDQpjb25zaWRlcg0KPiB0aGUgZm9sbG93aW5nIGRv
Y3VtZW50Og0KPiAtICdBbGxvY2F0aW9uIG9mIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBv
aW50IGZvciBVc2UgYnkgSVRVLVQNCj4gICAgRXRoZXJuZXQgYmFzZWQgT0FNJw0KPiAgIDxkcmFm
dC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4gYXMgYW4gSW5mb3JtYXRpb25h
bCBSRkMNCj4gDQo+IFRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4
dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0cw0KPiBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlv
bi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8gdGhlDQo+IGlldGZAaWV0Zi5v
cmcgbWFpbGluZyBsaXN0cyBieSAyMDEyLTAzLTIxLiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBt
YXkNCmJlDQo+IHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwg
cGxlYXNlIHJldGFpbiB0aGUNCj4gYmVnaW5uaW5nIG9mIHRoZSBTdWJqZWN0IGxpbmUgdG8gYWxs
b3cgYXV0b21hdGVkIHNvcnRpbmcuDQo+IA0KPiBBYnN0cmFjdA0KPiANCj4gICAgVGhpcyBkb2N1
bWVudCBhc3NpZ25zIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBUeXBlIGNvZGUgcG9pbnQgZm9yDQo+
ICAgIGNhcnJ5aW5nIEV0aGVybmV0IGJhc2VkIE9wZXJhdGlvbnMsIEFkbWluaXN0cmF0aW9uLCBh
bmQgTWFuYWdlbWVudA0KPiAgICBtZXNzYWdlcyBpbiB0aGUgTVBMUyBHZW5lcmljIEFzc29jaWF0
ZWQgQ2hhbm5lbCAoRy1BQ2gpLg0KPiANCj4gVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0K
PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWJldHRzLWl0dS1vYW0tYWNo
LWNvZGUtcG9pbnQvDQo+IA0KPiBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+
IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gt
Y29kZS1wb2ludC8NCj4gDQo+IA0KPiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBzdWJt
aXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+IElFVEYtQW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+IElF
VEYtQW5ub3VuY2VAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9pZXRmLWFubm91bmNlDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQpwd2UzIG1haWxpbmcgbGlzdA0KcHdlM0BpZXRmLm9yZw0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wd2UzDQpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXw0KSWV0ZiBtYWlsaW5nIGxpc3QNCklldGZAaWV0Zi5v
cmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zg0K

From vesely@tana.it  Mon Feb 27 02:44:08 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7F021F8680 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 02:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.645
X-Spam-Level: 
X-Spam-Status: No, score=-4.645 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tfIBeDLVJw8n for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 02:44:07 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 157BE21F8691 for <ietf@ietf.org>; Mon, 27 Feb 2012 02:44:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330339445; bh=b0MwnIrVDDszvNshBeDV/PIYsSu7gLEegD517mqvJA8=; l=799; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=AVMKZDfxqbGJjFAYihh3Zo3Tm7bjKKPw/cREQxZbRep2/pS5r0HaZWfZ2pZrs+1m2 okHvjHAWEnOtnBpyAGIOTlyVhqDk3/Yi2n+J56wwaDHVa70e+OVOVnjscIMJVEnSlz 4ecobQYNKFUoOtukCY9pGKAJ0KyBI7WplQNbOBVs=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 27 Feb 2012 11:44:05 +0100 id 00000000005DC035.000000004F4B5E75.00000D75
Message-ID: <4F4B5E74.7070403@tana.it>
Date: Mon, 27 Feb 2012 11:44:04 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <1473887.qQLEpWRMlg@scott-latitude-e6320> <20120224175748.GN48576@mail.yitter.info> <1370954.fA4nZvz4lC@scott-latitude-e6320>
In-Reply-To: <1370954.fA4nZvz4lC@scott-latitude-e6320>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 10:44:08 -0000

On 24/Feb/12 19:06, Scott Kitterman wrote:
> On Friday, February 24, 2012 12:57:49 PM Andrew Sullivan wrote:
>> 
>> How could you integrate a pre-allocated type when you don't know what
>> its format is?  If you knew how to do that, you could just deal with
>> unknown RRTPYEs, and then having TYPE99 wouldn't be a problem anyway.
> 
> I'd give them all a format of text and if a protocol needs something more 
> specific than that it can interpret it at the application level.

Publishing RRs requires proper formatting, though.  In most cases,
tools could work equally well without knowing whether a type is
registered or not.  They could rely upon symbolic specifications, see
http://datatracker.ietf.org/doc/draft-levine-dnsextlang/ , leaving it
to sysadmins to install official specs.


From stbryant@cisco.com  Mon Feb 27 05:01:28 2012
Return-Path: <stbryant@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 2A90621F86EB for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:01:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.588
X-Spam-Level: 
X-Spam-Status: No, score=-110.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qOB5qoCXOHc for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:01:27 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2439D21F8545 for <ietf@ietf.org>; Mon, 27 Feb 2012 05:01:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2541; q=dns/txt; s=iport; t=1330347687; x=1331557287; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=MSHBaltldbka2WUoR0O+CMlbuklzygHVz3nhW8uHRaw=; b=byp0uL1UClkr8O/77vUZnA6VNyfX8V2IqSOYJY7O/eu9PE7F7PWRv4mG jMti9k2cjb9NWGp+i2WKAcuSd6LowJ1oYoekuMFPxhvpkM8Fp/ks8IF53 DoJGzdkyLlrrF6PDpQ+d5aHtRkhJIPJMXTKysUa14T+Ca3ln9kdkinvww M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAB1+S0+Q/khL/2dsb2JhbABDsziBB4FzAQEBBAEBAQ8BAgEiNgoBDAQLEQQBAQEJFgQEBwkDAgECARUfCAEIBg0BBQIBAR6HZAugdgGDMQ8BkyqMewcZAQwEAgIHBgQDBAMIBAoHDwEKCQKFGAEBDQEBBAELCgEFAwUHAQMGBAoIBIMsBJU9km4
X-IronPort-AV: E=Sophos;i="4.73,490,1325462400"; d="scan'208";a="67149834"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 27 Feb 2012 13:01:23 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1RD1NCK011064; Mon, 27 Feb 2012 13:01:23 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q1RD1Mui029888; Mon, 27 Feb 2012 13:01:22 GMT
Message-ID: <4F4B7EA2.7070305@cisco.com>
Date: Mon, 27 Feb 2012 13:01:22 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Daniel Cohn <DanielC@orckit.com>
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
In-Reply-To: <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:01:28 -0000

Daniel

Shortage of ACh types was never an issue.

The issue issue is the concerns articulated in
draft-sprecher-mpls-tp-oam-considerations

Stewart


On 23/02/2012 10:35, Daniel Cohn wrote:
> Support - as there is no foreseen shortage in ACH types, I don't see a
> reason why this code point should not be allocated to an ITU developed
> protocol that is already deployed in the field.
>
> DC
>
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>
>>
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>     Ethernet based OAM'
>>    <draft-betts-itu-oam-ach-code-point-03.txt>  as an 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 2012-03-21. 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 assigns an Associated Channel Type code point for
>>     carrying Ethernet based Operations, Administration, and Management
>>     messages in the MPLS Generic Associated Channel (G-ACh).
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From loa@pi.nu  Mon Feb 27 05:08:05 2012
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 98B2021F8710 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.53
X-Spam-Level: 
X-Spam-Status: No, score=-99.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJ+Lmea9Cdbc for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:08:05 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id ACA8A21F870F for <ietf@ietf.org>; Mon, 27 Feb 2012 05:08:04 -0800 (PST)
Received: from [10.156.44.222] (unknown [192.165.126.77]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 500F42A8002; Mon, 27 Feb 2012 14:08:01 +0100 (CET)
Message-ID: <4F4B8031.5080404@pi.nu>
Date: Mon, 27 Feb 2012 14:08:01 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an	Associated Channel Code Point for Use byITU-T Ethernet	based	OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <796B6F5769D3E140A2BC3AAF7AC8D57F0A85B5@cnshjmbx01>
In-Reply-To: <796B6F5769D3E140A2BC3AAF7AC8D57F0A85B5@cnshjmbx01>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:08:05 -0000

Feng,

there is an interesting contradiction in your position.

You quote Dave when he says "We reject presidents and kings ...".

Yet you seen to support the political intervention by certain
nations in the MPLS-TP project!

Why is that?

/Loa

On 2012-02-27 04:58, HUANG Feng F wrote:
> +1
> 
> The Internet Engineering Task Force (IETF) is a large open international community, it should support running code has been deployed in real network.
> 
> Quote from David Clark: "We reject kings, presidents and voting. We believe in rough consensus and running code".
> 
> B.R.
> Feng
> 
> 
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Daniel Cohn
> Sent: 2012Äê2ÔÂ23ÈÕ 18:35
> To: ietf@ietf.org
> Subject: RE: [PWE3] FW: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
> 
> Support - as there is no foreseen shortage in ACH types, I don't see a
> reason why this code point should not be allocated to an ITU developed
> protocol that is already deployed in the field.
> 
> DC
> 
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>
>>
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>     Ethernet based OAM'
>>    <draft-betts-itu-oam-ach-code-point-03.txt>  as an 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 2012-03-21. 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 assigns an Associated Channel Type code point for
>>     carrying Ethernet based Operations, Administration, and Management
>>     messages in the MPLS Generic Associated Channel (G-ACh).
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
> 
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                             +46 767 72 92 13

From stbryant@cisco.com  Mon Feb 27 05:14:10 2012
Return-Path: <stbryant@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 7401821F870F for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:14:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.363
X-Spam-Level: 
X-Spam-Status: No, score=-109.363 tagged_above=-999 required=5 tests=[AWL=-1.214, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BN-vSO++5qzH for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:14:09 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2C33821F86F5 for <ietf@ietf.org>; Mon, 27 Feb 2012 05:14:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=3773; q=dns/txt; s=iport; t=1330348449; x=1331558049; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=GYRI6V0e8DUIz46dUHy4QDG5Gd4DzfzzQFeP/652EXs=; b=TZjFzzbtMV7nuEJ1Wksamk5B76YkwrgmNzklcunATBuGfWCY7+bzDitK XCm+YwwswrUC34CzXSO9PjfxD7fFgCHBA3qJjAEaPi5pcvPVnpSiVu7Yb tNDrRYcaoE5f1u/2z78x5CEVcNheFvBJHFmIyg8KVgZmY937MuFSLn976 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAHuAS0+Q/khM/2dsb2JhbABDhTmtf4EHgXMBAQEEAQEBDwECARwBOwoBDAQJAhEEAQEBBAUWBAQFAgkDAgECARUfCAEIBg0BBQIBARAOh2QLoHsBgzEPAYkeCIoEgSuLUAEGDgUFAQEMBDwPAQoLhRgBAQ0BBQwKAQUDBQcBAwYECggEghKBGgSIIY0ckm4
X-IronPort-AV: E=Sophos;i="4.73,490,1325462400"; d="scan'208";a="67151244"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 27 Feb 2012 13:14:08 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1RDE7PK003778; Mon, 27 Feb 2012 13:14:07 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q1RDE6gt000672; Mon, 27 Feb 2012 13:14:07 GMT
Message-ID: <4F4B819E.4090800@cisco.com>
Date: Mon, 27 Feb 2012 13:14:06 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: HUANG Feng F <Feng.f.Huang@alcatel-sbell.com.cn>
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an	Associated Channel Code Point for Use byITU-T Ethernet	based	OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <796B6F5769D3E140A2BC3AAF7AC8D57F0A85B5@cnshjmbx01>
In-Reply-To: <796B6F5769D3E140A2BC3AAF7AC8D57F0A85B5@cnshjmbx01>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:14:10 -0000

Feng

Surely you agree with me that the primary consideration is that
we should do what what we collectively believe is best for the
Internet in the long term?

There are many cases where the IETF has been presented with
an existing implementation, but the collective view is that
the pre-standards implementation is NOT RECOMMENDED
for deployment going forward.

Draft spercher-mpls-tp-oam-considerations raises a number
of concerns with the deployment of the proposal that
underlines draft-betts-itu-oam-ach-code-point, which
surely need to be taken into consideration.

- Stewart


On 27/02/2012 03:58, HUANG Feng F wrote:
> +1
>
> The Internet Engineering Task Force (IETF) is a large open international community, it should support running code has been deployed in real network.
>
> Quote from David Clark: "We reject kings, presidents and voting. We believe in rough consensus and running code".
>
> B.R.
> Feng
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Daniel Cohn
> Sent: 2012Äê2ÔÂ23ÈÕ 18:35
> To: ietf@ietf.org
> Subject: RE: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
>
> Support - as there is no foreseen shortage in ACH types, I don't see a
> reason why this code point should not be allocated to an ITU developed
> protocol that is already deployed in the field.
>
> DC
>
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>
>>
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>    Ethernet based OAM'
>>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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 2012-03-21. 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 assigns an Associated Channel Type code point for
>>    carrying Ethernet based Operations, Administration, and Management
>>    messages in the MPLS Generic Associated Channel (G-ACh).
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From loa@pi.nu  Mon Feb 27 05:51:55 2012
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 B6BAA21F8711 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.775
X-Spam-Level: 
X-Spam-Status: No, score=-99.775 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7E0lrUPNQGR8 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 05:51:54 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id AC15421F86FD for <ietf@ietf.org>; Mon, 27 Feb 2012 05:51:53 -0800 (PST)
Received: from [10.156.44.222] (unknown [192.165.126.77]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id 918FE2A8002 for <ietf@ietf.org>; Mon, 27 Feb 2012 14:51:50 +0100 (CET)
Message-ID: <4F4B8A75.6000207@pi.nu>
Date: Mon, 27 Feb 2012 14:51:49 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <4F4B7EA2.7070305@cisco.com>
In-Reply-To: <4F4B7EA2.7070305@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 13:51:55 -0000

All,

I agree with Stewart, while shortage of code points might be a reason
to think twice before allocating one, "abundance" in itself is never
a reason to allocate code points.

I'm way less inclined to approve of this draft in the condition it
is now. Actually I believe that we should think very careful before
approving it at all.

/Loa

On 2012-02-27 14:01, Stewart Bryant wrote:
>
> Daniel
>
> Shortage of ACh types was never an issue.
>
> The issue issue is the concerns articulated in
> draft-sprecher-mpls-tp-oam-considerations
>
> Stewart
>
>
> On 23/02/2012 10:35, Daniel Cohn wrote:
>> Support - as there is no foreseen shortage in ACH types, I don't see a
>> reason why this code point should not be allocated to an ITU developed
>> protocol that is already deployed in the field.
>>
>> DC
>>
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>> bounces@ietf.org] On Behalf Of The IESG
>>> Sent: 22 February 2012 15:13
>>> To: IETF-Announce
>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>> (Allocation of
>> an
>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>>> Informational RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to
>> consider
>>> the following document:
>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>> Ethernet based OAM'
>>> <draft-betts-itu-oam-ach-code-point-03.txt> as an 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 2012-03-21. 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 assigns an Associated Channel Type code point for
>>> carrying Ethernet based Operations, Administration, and Management
>>> messages in the MPLS Generic Associated Channel (G-ACh).
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From tnadeau@lucidvision.com  Mon Feb 27 06:17:36 2012
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1D9D21F8703 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 06:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rtI7MugX-X3 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 06:17:36 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0F26321F8713 for <ietf@ietf.org>; Mon, 27 Feb 2012 06:17:36 -0800 (PST)
Received: from [192.168.1.58] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 70CB91519B1; Mon, 27 Feb 2012 09:17:35 -0500 (EST)
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <4F4B7EA2.7070305@cisco.com> <4F4B8A75.6000207@pi.nu>
In-Reply-To: <4F4B8A75.6000207@pi.nu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <EF630828-0EE9-4277-97AA-540E2A3BB92F@lucidvision.com>
X-Mailer: iPad Mail (9A405)
From: Thomas D Nadeau <tnadeau@lucidvision.com>
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
Date: Mon, 27 Feb 2012 09:17:34 -0500
To: Loa Andersson <loa@pi.nu>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:17:37 -0000

+1 on both points.



On Feb 27, 2012, at 8:51 AM, Loa Andersson <loa@pi.nu> wrote:

> All,
> 
> I agree with Stewart, while shortage of code points might be a reason
> to think twice before allocating one, "abundance" in itself is never
> a reason to allocate code points.
> 
> I'm way less inclined to approve of this draft in the condition it
> is now. Actually I believe that we should think very careful before
> approving it at all.
> 
> /Loa
> 
> On 2012-02-27 14:01, Stewart Bryant wrote:
>> 
>> Daniel
>> 
>> Shortage of ACh types was never an issue.
>> 
>> The issue issue is the concerns articulated in
>> draft-sprecher-mpls-tp-oam-considerations
>> 
>> Stewart
>> 
>> 
>> On 23/02/2012 10:35, Daniel Cohn wrote:
>>> Support - as there is no foreseen shortage in ACH types, I don't see a
>>> reason why this code point should not be allocated to an ITU developed
>>> protocol that is already deployed in the field.
>>> 
>>> DC
>>> 
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 22 February 2012 15:13
>>>> To: IETF-Announce
>>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of
>>> an
>>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>>>> Informational RFC
>>>> 
>>>> 
>>>> The IESG has received a request from an individual submitter to
>>> consider
>>>> the following document:
>>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>> Ethernet based OAM'
>>>> <draft-betts-itu-oam-ach-code-point-03.txt> as an 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 2012-03-21. 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 assigns an Associated Channel Type code point for
>>>> carrying Ethernet based Operations, Administration, and Management
>>>> messages in the MPLS Generic Associated Channel (G-ACh).
>>>> 
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>> 
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>> 
>>>> 
>>>> No IPR declarations have been submitted directly on this I-D.
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>> 
>> 
>> 
> 
> -- 
> 
> 
> Loa Andersson                         email: loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From stbryant@cisco.com  Mon Feb 27 06:58:52 2012
Return-Path: <stbryant@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 9A97521F8717; Mon, 27 Feb 2012 06:58:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.578
X-Spam-Level: 
X-Spam-Status: No, score=-110.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6YZOcO2umvr; Mon, 27 Feb 2012 06:58:51 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC1021F8700; Mon, 27 Feb 2012 06:58:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2752; q=dns/txt; s=iport; t=1330354731; x=1331564331; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=KhlJZJa0sbJUdr07hkR00mNdh6znAnT56bhFmbSPIwU=; b=StaJS9oEij4Tp2wcHto78PzgWI+CRGOdOlsOVPeeqr2mm0aKVkY4ZYvt 2tnoVcMz6j9XtNka76LMFhgV3obJdfNlh9y93PJAO85nQiDs0uruNZRtJ Gi27dzkuOKwixQsv5VdLdC8hoBYd4UxtBwUJDaf1iYaZAI2yuQL2VPDaI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACGZS0+Q/khL/2dsb2JhbABCsyaBB4FzAQEBBAEBAQ8BAgEiNgoBDAQLEQQBAQEJFgQEBwkDAgECARUfCAEIEwEFAgEBHodkC5kAAYMxDwGbGox5AgsCEwILBAICBwYEAwQDCAQKBw8BCgkChRgBAQ0BAQQBCwoBBQMFBwEDBgQKCAQOgx4ElT2Sbg
X-IronPort-AV: E=Sophos;i="4.73,491,1325462400"; d="scan'208";a="67167014"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 27 Feb 2012 14:58:50 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q1REwjHZ013243; Mon, 27 Feb 2012 14:58:45 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q1REwet3006673; Mon, 27 Feb 2012 14:58:41 GMT
Message-ID: <4F4B9A20.9010909@cisco.com>
Date: Mon, 27 Feb 2012 14:58:40 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: pwe3@ietf.org
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <4F4B92E0.4010907@cisco.com>
In-Reply-To: <4F4B92E0.4010907@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org >> IETF Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.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: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 14:58:52 -0000

PWE3 WG

Please see the note further down the thread requesting that
any discussion take place on ietf@ietf.org

Stewart

On 27/02/2012 14:27, Stewart Bryant wrote:
>
> My understanding is that the Recommendation called up by
> this draft proposes this as a new OAM be used for PWs.
>
> I do not think that PWE3 has considered the implications
> of adding this OAM in a PW context.
>
> - Stewart
>
> On 22/02/2012 15:16, Adrian Farrel wrote:
>> Hi PWE3 WG,
>>
>> You will want to be aware of this IETF Last Call.
>>
>> Please send any comments as per the instructions for IETF Last Call 
>> (i.e., see
>> below) and not to the MPLS mailing list.
>>
>> Thanks,
>> Adrian
>>
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>> bounces@ietf.org] On Behalf Of The IESG
>>> Sent: 22 February 2012 15:13
>>> To: IETF-Announce
>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>  
>>> (Allocation of
>> an
>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>>> Informational RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to 
>>> consider
>>> the following document:
>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>     Ethernet based OAM'
>>> <draft-betts-itu-oam-ach-code-point-03.txt>  as an 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 2012-03-21. 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 assigns an Associated Channel Type code point for
>>>     carrying Ethernet based Operations, Administration, and Management
>>>     messages in the MPLS Generic Associated Channel (G-ACh).
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From tglassey@certichron.com  Fri Feb 24 04:23:36 2012
Return-Path: <tglassey@certichron.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E88121F86CE for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 04:23:36 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OG16NJgJ-170 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 04:23:36 -0800 (PST)
Received: from p3plsmtpa01-02.prod.phx3.secureserver.net (p3plsmtpa01-02.prod.phx3.secureserver.net [72.167.82.82]) by ietfa.amsl.com (Postfix) with SMTP id CF0B721F86C3 for <ietf@ietf.org>; Fri, 24 Feb 2012 04:23:33 -0800 (PST)
Received: (qmail 4249 invoked from network); 24 Feb 2012 12:16:53 -0000
Received: from unknown (67.180.133.66) by p3plsmtpa01-02.prod.phx3.secureserver.net (72.167.82.82) with ESMTP; 24 Feb 2012 12:16:53 -0000
Message-ID: <4F477FAF.2030501@certichron.com>
Date: Fri, 24 Feb 2012 04:16:47 -0800
From: Todd Glassey <tglassey@certichron.com>
Organization: certichron.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>, dnsop@ietf.org
Subject: DNS Rule Transmission is a new tool in anti-spam controls
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:23:36 -0000

I want to point out that the ability and use of DNS to transmit policy 
statements is a valuable tool in dealing with certain types of DMA 
sponsored emails which many of us wish would go away.

The idea of being able to send a statement of the use rules for a MX 
record for instance is a very powerful process in new networking models 
which are more policy driven in form.

Clearly the TXT records can carry these types of statements but it would 
seem to make sense to allow some pre-approved tags and response mandates 
to be used as well.

Todd
-- 
Todd S. Glassey - CISM CIFI
CTO Certichron Inc

This message contains information which may be confidential and/or 
privileged. Unless you are the intended recipient (or authorized to 
receive for the intended recipient), you may not read, use, copy or 
disclose to anyone the message or any information contained in the 
message. If you have received the message in error, please advise the 
sender by reply e-mail and delete the message and any attachment(s) 
thereto without retaining any copies.

Further we have a formal OPT OUT Policy posted on our website pertaining 
to the use of any Email Addresses gleaned or taken from any source, web, 
mailing lists, previous customer lists etc. In all instances we choose 
to formally OPT OUT and this notice constitutes formal disclosure that 
you may not collect, buy or sell or provide access to this email address 
or any pertaining to our DNS MX Record Publication License posted on the 
web at http://www-wp.certichron.com/?page_id=3947.

From patrik@frobbit.se  Fri Feb 24 08:57:27 2012
Return-Path: <patrik@frobbit.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 0B61621F87F9; Fri, 24 Feb 2012 08:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.903
X-Spam-Level: 
X-Spam-Status: No, score=-100.903 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V2DXxXpWnQnX; Fri, 24 Feb 2012 08:57:26 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 2A65521F867F; Fri, 24 Feb 2012 08:57:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 109A813296F5F; Fri, 24 Feb 2012 17:57:25 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5qaVaibRMNu; Fri, 24 Feb 2012 17:57:24 +0100 (CET)
Received: from [95.209.79.91] (95.209.79.91.bredband.tre.se [95.209.79.91]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id BA11E13296F58; Fri, 24 Feb 2012 17:57:24 +0100 (CET)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <DC8A7C4316C6F97607CFBCC6@PST.JCK.COM>
In-Reply-To: <DC8A7C4316C6F97607CFBCC6@PST.JCK.COM>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <5B092333-30BD-481B-8E6A-F41DB5C586C2@frobbit.se>
X-Mailer: iPad Mail (9A405)
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <patrik@frobbit.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Date: Fri, 24 Feb 2012 17:57:31 +0100
To: John C Klensin <john-ietf@jck.com>
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
Cc: IETF Discussion <ietf@ietf.org>, =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>, "mnot@mnot.net" <mnot@mnot.net>, "iesg@ietf.org" <iesg@ietf.org>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:57:27 -0000

On 24 feb 2012, at 17:43, John C Klensin <john-ietf@jck.com> wrote:

> It is
> the number of folks who, for lots of reasons, haven't upgraded
> from operating systems, resolvers, etc., that don't support
> newer RRTYPES.

As I said, people disagree... ;-)

As far as I know, there is nothing in any of the operating systems you menti=
on that prohibits an application to send a random udp packet, and because of=
 that your application can include a resolver library.

What is a problem are the cases where DNS is not used at all at the end node=
, but instead other name binding/lookup protocols combined with a firewall p=
olicy that because of this can and is blocking udp+tcp/53 in various ways.

That said, I still ask when it is, in general, time to just move forward. I s=
ee for example many other reasons why people should not use that old softwar=
e. IE6 for example. Yes, economically constrained situations exists, but tha=
t problem do not go away by having us not start using SRV or HTTP/1.1 or SNI=
 or HTML5.0 or...pick your favourite. And with SPF, that is not used by the e=
dge node either.

I am asking more generally why specifically this DNS issue is so stuck, beca=
use I think that is unfair. We upgrade other protocols...

But my point is, people disagree. As we see here ;-)

   Patrik


From david.black@emc.com  Fri Feb 24 17:15:20 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E143421F8658 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 17:15:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.688
X-Spam-Level: 
X-Spam-Status: No, score=-109.688 tagged_above=-999 required=5 tests=[AWL=0.911, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DAWzUdgyppr1 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2012 17:15:19 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id 90DDA21F8650 for <ietf@ietf.org>; Fri, 24 Feb 2012 17:15:19 -0800 (PST)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1P1FHrX022688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Feb 2012 20:15:18 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Fri, 24 Feb 2012 20:15:11 -0500
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1P1FAdq011782; Fri, 24 Feb 2012 20:15:11 -0500
Received: from mx14a.corp.emc.com ([169.254.1.157]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Fri, 24 Feb 2012 20:15:10 -0500
From: <david.black@emc.com>
To: <wesley.george@twcable.com>
Date: Fri, 24 Feb 2012 20:15:09 -0500
Subject: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC 
Thread-Topic: Re: Last Call: <draft-george-travel-faq-03.txt> (IETF meeting attendees' Frequently Asked (travel) Questions) to Informational RFC 
Thread-Index: AczzWuqa8fFaRL9XQG+hVthReXMjCw==
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E05AEAF024A@MX14A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
Cc: david.black@emc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:15:21 -0000

This looks very useful.  I have a few suggestions for the -04 version.

(1) The addition of non-flight options to 3.1 is a good idea.  That should =
be
complemented by adding a sentence to the end of 3.1.1 (Transit between the =
airport
and primary hotels) to say that if non-rail options are included, then corr=
esponding
info for them (e.g., how to get to/from the train station) should be includ=
ed,
although train stations are often more convenient to the meeting venue than=
 airports.

(2) In 3.1.1.1 to this bullet:
   o  Description of "official" taxis if appropriate
I'd suggest adding "and advice on avoiding common taxi scams if appropriate=
".

This is often not appropriate, but there are a (small) number of cities tha=
t are
notorious for taxi scams; I think it helps to mention that here, even thoug=
h scams are
noted in general in the Health and Safety section (3.3.1).

(3) In 3.7 Tourism, it might be good to add a suggestion to mention notable=
 local
events occurring during the meeting week that may be of interest - perhaps =
a local
festival, although this suggestion was motivated by the wonderful fireworks=
 in Quebec
City.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From Ted.Lemon@nominum.com  Fri Feb 24 19:35:08 2012
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742AF11E8073; Fri, 24 Feb 2012 19:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.527
X-Spam-Level: 
X-Spam-Status: No, score=-106.527 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojokC7JmUG7v; Fri, 24 Feb 2012 19:35:07 -0800 (PST)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 2209C21E8015; Fri, 24 Feb 2012 19:35:06 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKT0hW6YBVohHNZ3S+MrbC484sSGsJcT8+@postini.com; Fri, 24 Feb 2012 19:35:06 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1CFED1B83F4; Fri, 24 Feb 2012 19:35:05 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 11B5119005D; Fri, 24 Feb 2012 19:35:05 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0247.003; Fri, 24 Feb 2012 19:35:05 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Thread-Topic: [dhcwg] TSVDIR review of draft-ietf-dhc-dhcpv4-bulk-leasequery
Thread-Index: AQHM6qpvAqOZiGrj4kydaKDtgkZBbZZCENSAgAAsLgCAARgHAIAKB7wAgAAw7gA=
Date: Sat, 25 Feb 2012 03:35:04 +0000
Message-ID: <9B0B764E-6619-41F5-BCEC-12CB5CC5570C@nominum.com>
References: <4F3987F0.5050000@isi.edu> <EBB60E5C-8661-467B-A04C-4BAB70717C51@cisco.com> <4F3ED8FC.6020400@isi.edu> <C84410EE-1D8C-494B-8BEA-030C6CBCABC1@nominum.com> <4F482DDC.1020509@isi.edu>
In-Reply-To: <4F482DDC.1020509@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_9B0B764E661941F5BCEC12CB5CC5570Cnominumcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
Cc: IETF discussion list <ietf@ietf.org>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "<draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>" <draft-ietf-dhc-dhcpv4-bulk-leasequery@tools.ietf.org>, TSV Dir <tsv-dir@ietf.org>, "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 03:35:08 -0000

--_000_9B0B764E661941F5BCEC12CB5CC5570Cnominumcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Feb 24, 2012, at 7:39 PM, Joe Touch <touch@isi.edu<mailto:touch@isi.edu>=
> wrote:
OK, so although I disagree that this is the correct procedure, if it's typi=
cal for DHCP then that's reasonable.

So just to be clear here, it seems that you are withdrawing your request th=
at we create a new IANA registry and to say that this document updates RFC2=
131 or RFC2132, right?


--_000_9B0B764E661941F5BCEC12CB5CC5570Cnominumcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <5DD14084ED08444C9C55DE9B0833BD60@nominum.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>
<div>On Feb 24, 2012, at 7:39 PM, Joe Touch &lt;<a href=3D"mailto:touch@isi=
.edu">touch@isi.edu</a>&gt;&nbsp;wrote:</div>
<blockquote type=3D"cite"><span style=3D"color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: normal; l=
etter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit=
-auto; text-indent: 0px; text-transform: none; white-space: normal; widows:=
 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-=
width: 0px; font-size: medium; display: inline !important; float: none; ">O=
K,
 so although I disagree that this is the correct procedure, if it's typical=
 for DHCP then that's reasonable.</span><br style=3D"color: rgb(0, 0, 0); f=
ont-family: Helvetica; font-style: normal; font-variant: normal; font-weigh=
t: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-al=
ign: -webkit-auto; text-indent: 0px; text-transform: none; white-space: nor=
mal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-=
text-stroke-width: 0px; font-size: medium; ">
</blockquote>
</div>
<br>
<div>So just to be clear here, it seems that you are withdrawing your reque=
st that we create a new IANA registry and to say that this document updates=
 RFC2131 or RFC2132, right?</div>
<div><br>
</div>
</body>
</html>

--_000_9B0B764E661941F5BCEC12CB5CC5570Cnominumcom_--

From adrien@qbik.com  Sat Feb 25 17:54:13 2012
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 64B2621F861E; Sat, 25 Feb 2012 17:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level: 
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=-0.884, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PH17bY+s4cPI; Sat, 25 Feb 2012 17:54:12 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id ABF8E21F861D; Sat, 25 Feb 2012 17:54:11 -0800 (PST)
Received: From [192.168.1.10] (unverified [125.237.241.8]) by SMTP Server [210.55.214.35] (WinGate SMTP Receiver v7.1.0 (Build 3386)) with SMTP id <0018883943@smtp.qbik.com>; Sun, 26 Feb 2012 14:54:07 +1300
Message-ID: <4F4990B9.7040807@qbik.com>
Date: Sun, 26 Feb 2012 14:54:01 +1300
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120216 Thunderbird/11.0
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de>
In-Reply-To: <4F48EA4B.6050500@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:54:13 -0000

I wonder if it would be helpful for people to outline what they expect 
are the issues to be solved by doing more work on an HTTP auth mechanism.

I get the feeling that some think the scope would encompass providing 
auth support for web applications, whereas others are mainly concerned 
with the transport level auth.

IMO http auth is not particularly suited to solve the issues required 
for web site authors, for the simple issue of administrative boundaries 
and realms of accounts.

For example the web server that sits on an OS that has 1 user database, 
yet hosts 10 web sites each of which require their own independent user 
database, and require the ability to create and destroy accounts, and 
these accounts NOT be OS ones (i.e. not grant any access to the OS).  
Sure these issues could be engineered around, but it would add to the 
current scope (for change) every web application that currently manages 
accounts (a great deal of them).

If we're just talking about transport auth, then what's wrong with 
something like kerberos.  As for server logging a client out, the auth 
mechanism would need a token that can be revoked by the server, since 
one cannot rely on client co-operation in such a matter.  A kerberos 
ticket seems to fit this bill.  then we'd just need a mechanism for a 
client to request revokation (logout).  It is also AFAIK supported on 
all server platforms, unlike any auth mechanism that requires access to 
plaintext passwords at the server end - these are not always available.

Adrien


On 26/02/2012 3:03 a.m., Julian Reschke wrote:
> On 2012-02-25 14:46, Stephen Farrell wrote:
>> ...
>> Yeah that's a tricky one. While one might like to
>> see "one or more" in both places that might not be
>> practical.
>>
>> In the proposal above the goal is that httpbis pick one
>> or more but recognising the reality that we might not get
>> a new proposal that httpbis will accept and that folks
>> will really implement and deploy.
>>
>> So:
>> Goal = one or more
>> Reluctant recognition of reality = zero or more
>>
>> With this plan if httpbis in fact select zero new proposals
>> that would represent a failure for all concerned. The "zero
>> or more" term is absolutely not intended to provide a way to
>> just punt on the question.
>>
>> Such a failure at the point where httpbis was re-chartering
>> to work on a HTTP/2.0 selection with no better security than
>> we now have is probably better evaluated as a whole - I
>> guess the question for the IETF/IESG at that point would
>> be whether the Internet would be better with or without
>> such a beast, or better waiting a while until the security
>> thing did get fixed.
>>
>> I can imagine an argument might ensue about that;-)
>> ...
>
> If we just need a new authentication scheme, nothing stops people from 
> working on that right now. I don't see how that should affect HTTP/2.0.
>
> If the "right" way to do security needs changes in the HTTP/1.1 
> authentication framework, then we should fix/augment/tune HTTP/1.1. 
> It's not going to go away anytime soon.
>
> Best regards, Julian
>

-- 
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com


From w@1wt.eu  Sat Feb 25 22:28:31 2012
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAB7221F860D; Sat, 25 Feb 2012 22:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.506
X-Spam-Level: 
X-Spam-Status: No, score=-5.506 tagged_above=-999 required=5 tests=[AWL=-3.763, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, SARE_WEOFFER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvmdvbxXZdK3; Sat, 25 Feb 2012 22:28:31 -0800 (PST)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id D663D21F85F3; Sat, 25 Feb 2012 22:28:29 -0800 (PST)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id q1Q6SIYD013568; Sun, 26 Feb 2012 07:28:18 +0100
Date: Sun, 26 Feb 2012 07:28:18 +0100
From: Willy Tarreau <w@1wt.eu>
To: Adrien de Croy <adrien@qbik.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Message-ID: <20120226062818.GG8633@1wt.eu>
References: <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F4990B9.7040807@qbik.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F4990B9.7040807@qbik.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:28:31 -0000

Hi Adrien,

On Sun, Feb 26, 2012 at 02:54:01PM +1300, Adrien de Croy wrote:
> 
> I wonder if it would be helpful for people to outline what they expect 
> are the issues to be solved by doing more work on an HTTP auth mechanism.
> 
> I get the feeling that some think the scope would encompass providing 
> auth support for web applications, whereas others are mainly concerned 
> with the transport level auth.

I am personally concerned with the risk that new auth schemes continue
to mix messages and transport. I don't think we need to define these new
schemes, we just need to ensure the new protocol offers provision for
doing the things right. I'd like to ensure we never get a new NTLM-like
design error which forces every implementation to break the HTTP model
to try to be compatible.

Also, (that's not directly related to auth) it would be nice if we could
have a random session ID in messages that browsers would send to help the
whole intermediary chain select the appropriate server. A simple hash on
this session ID would make load balancing much easier and much more reliable
than any other algorithm right now and would definitely help when challenge
based auth schemes are needed.

(...)
> If we're just talking about transport auth, then what's wrong with 
> something like kerberos.  As for server logging a client out, the auth 
> mechanism would need a token that can be revoked by the server, since 
> one cannot rely on client co-operation in such a matter.  A kerberos 
> ticket seems to fit this bill.  then we'd just need a mechanism for a 
> client to request revokation (logout).  It is also AFAIK supported on 
> all server platforms, unlike any auth mechanism that requires access to 
> plaintext passwords at the server end - these are not always available.

It is comparable to what is already done with cookies in most applications
(ie I have nothing against this). We just have to keep in mind that auth
methods will change with time. Many applications right now expect two-factor
auth and/or some complex UI adaptations to protect against malware. That's
why I think that our work on supporting auth should mainly ensure we offer
the solid blocks for building new auth schemes and don't necessarily need
to define these schemes ourselves.

Regards,
Willy


From w@1wt.eu  Sat Feb 25 22:40:36 2012
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C409821F8577; Sat, 25 Feb 2012 22:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.468
X-Spam-Level: 
X-Spam-Status: No, score=-5.468 tagged_above=-999 required=5 tests=[AWL=-3.725, BAYES_00=-2.599, HELO_IS_SMALL6=0.556, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0IIH8SkGdxp; Sat, 25 Feb 2012 22:40:36 -0800 (PST)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 0681D21F857D; Sat, 25 Feb 2012 22:40:35 -0800 (PST)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id q1Q6eP7e013597; Sun, 26 Feb 2012 07:40:25 +0100
Date: Sun, 26 Feb 2012 07:40:25 +0100
From: Willy Tarreau <w@1wt.eu>
To: Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <patrik@frobbit.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Message-ID: <20120226064025.GH8633@1wt.eu>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <DC8A7C4316C6F97607CFBCC6@PST.JCK.COM> <5B092333-30BD-481B-8E6A-F41DB5C586C2@frobbit.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5B092333-30BD-481B-8E6A-F41DB5C586C2@frobbit.se>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Mon, 27 Feb 2012 09:19:55 -0800
Cc: IETF Discussion <ietf@ietf.org>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>, "mnot@mnot.net" <mnot@mnot.net>, "iesg@ietf.org" <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 06:40:36 -0000

On Fri, Feb 24, 2012 at 05:57:31PM +0100, Patrik Fältström wrote:
> I am asking more generally why specifically this DNS issue is so stuck,
> because I think that is unfair. We upgrade other protocols...

Because in HTTP, anybody can be anywhere. You can have client-side proxies,
server-side gateways, load balancers, etc... everyone in this chain may or
may not resolve, it's only a matter of configuration and architecture choice.
There are plenty of places where clients won't access public resolvers at all
and rely on their proxies for this. So you can't make use of DNS to improve
these users' experience.

Also, DNS is SLLLLOOOOWWWWW. It's fast enough to send a mail. But for HTTP
it adds too much latency. Some people in the mobile world would like to be
able to configure an explicit proxy on their smartphones in order to avoid
a very expensive round trip before fetching an object : at 20 host names
on a web page, 300 ms round trip means 6 seconds are lost to resolve these
objects if they can't be totally parallelized.

DNS suggestion is something going back and forth regularly. I think that
people who try to push it hard only see the very simple case where users
have a direct low-latency internet connection. The reality is much much
different. This well reflected by the fact that in the end, after many
proposals, it has still not been adopted !

Regards,
Willy


From sant9442@gmail.com  Mon Feb 27 09:33:26 2012
Return-Path: <sant9442@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 31A9421F8831 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 09:33:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.329
X-Spam-Level: 
X-Spam-Status: No, score=-3.329 tagged_above=-999 required=5 tests=[AWL=0.270,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gHUzLGEeva3v for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 09:33:25 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7308F21F8575 for <ietf@ietf.org>; Mon, 27 Feb 2012 09:33:25 -0800 (PST)
Received: by yhpp34 with SMTP id p34so554657yhp.31 for <ietf@ietf.org>; Mon, 27 Feb 2012 09:33:25 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.184.8 as permitted sender) client-ip=10.236.184.8; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.184.8 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.184.8]) by 10.236.184.8 with SMTP id r8mr22804129yhm.110.1330364005082 (num_hops = 1); Mon, 27 Feb 2012 09:33:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=tZGAwQhs0a11nH0gf3NFWco9D70jCsVcuT6ay3nxYoc=; b=kyDCyPcATd0rMh/hypGfp1z9JyHTbj+flCO0gYur5G/ZEFgaQtQk6Yy/lzUjw7QjaA 9HzKsrUNCj0csiGnhyh5sjIwK3hFz2WmCxPj0bYhoRNqMnB/NekTWVFQMRz73R1SDUaV l+/WQehTA+a0rDGPPeYhd1Vk2fkyftQZ5ncQM=
Received: by 10.236.184.8 with SMTP id r8mr17023919yhm.110.1330364005025; Mon, 27 Feb 2012 09:33:25 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id i4sm24050321anm.5.2012.02.27.09.33.22 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 09:33:23 -0800 (PST)
Message-ID: <4F4BBE5D.20905@gmail.com>
Date: Mon, 27 Feb 2012 12:33:17 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320> <4F4B5E74.7070403@tana.it>
In-Reply-To: <4F4B5E74.7070403@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 17:33:26 -0000

Alessandro Vesely wrote:
> On 24/Feb/12 19:06, Scott Kitterman wrote:
>> On Friday, February 24, 2012 12:57:49 PM Andrew Sullivan wrote:
>>> How could you integrate a pre-allocated type when you don't know what
>>> its format is?  If you knew how to do that, you could just deal with
>>> unknown RRTPYEs, and then having TYPE99 wouldn't be a problem anyway.
>> I'd give them all a format of text and if a protocol needs something more 
>> specific than that it can interpret it at the application level.
> 
> Publishing RRs requires proper formatting, though.  In most cases,
> tools could work equally well without knowing whether a type is
> registered or not.  They could rely upon symbolic specifications, see
> http://datatracker.ietf.org/doc/draft-levine-dnsextlang/ , leaving it
> to sysadmins to install official specs.

I am extremely interested to know how RFC3597 "Handling of Unknown DNS 
Resource Record (RR) Types" is viewed today as a still ongoing 
prevalent issues.

Back around that time from (up to around 2007/2008), I would never 
even bother with any protocol consideration using new RR types or more 
specifically, allows the publishing with a high confidence the 
passthru recursive necessary would be feasibly successful.

I would like to poise this general question to the IETF/DNS community:

     Given higher modern DNS server support for unnamed types, should
     new protocols continues to pursue new RR types or does the
     DNS Community believe this original infrastructure ideal is no longer
     necessary and new protocols can use TXT records with a high
     degree of DNS support confidence for robustness.

Many new protocols use the TXT records simply as a fast entry, high 
support mechanism to store data on DNS.  Is the mindset today such 
that this is still desirable, is there an DNS impact with this on 
going direction?

Consider the point of view of a developer exploring a new protocol, 
should he focus on using TXT only and now sweat any IETF/DNS community 
endorsement or should he/she also include a considering for a new RR 
type in the design?

Thanks

---
Hector Santos/CTO
Santronics Software, Inc.




From sant9442@gmail.com  Mon Feb 27 10:02:26 2012
Return-Path: <sant9442@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 3790D21F87DB; Mon, 27 Feb 2012 10:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.742
X-Spam-Level: 
X-Spam-Status: No, score=-2.742 tagged_above=-999 required=5 tests=[AWL=-0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfojENlIXJp0; Mon, 27 Feb 2012 10:02:25 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7EBC521F87C7; Mon, 27 Feb 2012 10:02:25 -0800 (PST)
Received: by yhpp34 with SMTP id p34so575676yhp.31 for <multiple recipients>; Mon, 27 Feb 2012 10:02:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=v8yYWzIiXiC68zVBflQsHmJJEp9uWhuCVWnLPGkynC4=; b=c0FCh/I9oKu9jo79hz+FCPt6rLUC5Z3400LJfDXc8y6PPLlZ3F7nf/SZ5jCtuPlwn+ ODKxgP+WFssU/t6lpBCAKMMSSBrK96pzDFyEf8aSzsCSyHqquylgLv30tU7sew73zQOS /J9rLtMi+nTcYzfDOYy8kUC4cnRfc7eILd2CI=
Received: by 10.236.179.67 with SMTP id g43mr16985488yhm.66.1330365745098; Mon, 27 Feb 2012 10:02:25 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id n10sm24171831ani.8.2012.02.27.10.02.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 10:02:24 -0800 (PST)
Message-ID: <4F4BC52A.70507@gmail.com>
Date: Mon, 27 Feb 2012 13:02:18 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Todd Glassey <tglassey@certichron.com>
Subject: Re: DNS Rule Transmission is a new tool in anti-spam controls
References: <4F477FAF.2030501@certichron.com>
In-Reply-To: <4F477FAF.2030501@certichron.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dnsop@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 18:02:26 -0000

Todd Glassey wrote:
> I want to point out that the ability and use of DNS to transmit policy 
> statements is a valuable tool in dealing with certain types of DMA 
> sponsored emails which many of us wish would go away.

But we are also encouraging them to do so. It is now BCP by the DMA 
community to support these new Email "Mouse Trap" policy based mechanisms.

My view is that the *power* is in the domain policy fault detection 
for compliancy. So at the top level, as long as they are domain 
compliant as expected for all, they should be treated equally as just 
another anonymous domain transaction exposing their policies.

> The idea of being able to send a statement of the use rules for a MX 
> record for instance is a very powerful process in new networking models 
> which are more policy driven in form.

+1, again, in my view, when enforced from a fault detection standpoint 
the higher payoff is more realized.

> Clearly the TXT records can carry these types of statements but it would 
> seem to make sense to allow some pre-approved tags and response mandates 
> to be used as well.

+1.  I see the "issue" as following:

1) Using the same name space where there is no standard for the 
separation of "TXT" strings requiring the the individual protocols to 
have its own string detection mechanism.

2) Due to#1 and the lower feasibility of using RR types, use a special 
namespace (subdomain).

Some existing protocols such as AD and XMPP would not get wide support 
until RR types such as SRV was widely supported.  And even then, for 
backward compatibility, had to include fall back for widest support 
discovery.

A major part of the dilemma is the overhead with the migration path 
with the hope its only a initial short term impact, but an eventual 
long term benefit in lowering the impact on DNS.

I believe what is required is a Batch call of Multiple Query Packets 
under a single call feature to be proposed for DNS servers to support 
because currently the recommendation is to use an async emulation of 
two independent by managed DNS calls.

I see this helping with the usage and consideration of new protocols 
considering new RR types but may have to first use a fast entry, 
widest support TXT record mechanism just to get started.  This will 
automatically cause a migration requirement.

Thanks

Hector Santos/CTO
Santronics Software, Inc.

From john-ietf@jck.com  Mon Feb 27 11:41:23 2012
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 4B24621F87DB; Mon, 27 Feb 2012 11:41:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.609
X-Spam-Level: 
X-Spam-Status: No, score=-102.609 tagged_above=-999 required=5 tests=[AWL=-0.310, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 975OLVFCmMF4; Mon, 27 Feb 2012 11:41:22 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6A01521F86F6; Mon, 27 Feb 2012 11:41:22 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S26NX-000G8L-It; Mon, 27 Feb 2012 14:36:59 -0500
Date: Mon, 27 Feb 2012 14:41:15 -0500
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <patrik@frobbit.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Message-ID: <CE143B85CCFB2EDB6A7B260C@PST.JCK.COM>
In-Reply-To: <5B092333-30BD-481B-8E6A-F41DB5C586C2@frobbit.se>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <DC8A7C4316C6F97607CFBCC6@PST.JCK.COM> <5B092333-30BD-481B-8E6A-F41DB5C586C2@frobbit.se>
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
Cc: iesg@ietf.org, mnot@mnot.net, IETF Discussion <ietf@ietf.org>, ietf-http-wg@w3.org, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:41:23 -0000

--On Friday, February 24, 2012 17:57 +0100 Patrik =
F=C3=A4ltstr=C3=B6m
<patrik@frobbit.se> wrote:

>=20
>=20
> On 24 feb 2012, at 17:43, John C Klensin <john-ietf@jck.com>
> wrote:
>=20
>> It is
>> the number of folks who, for lots of reasons, haven't =
upgraded
>> from operating systems, resolvers, etc., that don't support
>> newer RRTYPES.
>=20
> As I said, people disagree... ;-)

> As far as I know, there is nothing in any of the operating
> systems you mention that prohibits an application to send a
> random udp packet, and because of that your application can
> include a resolver library.
>=20
> What is a problem are the cases where DNS is not used at all
> at the end node, but instead other name binding/lookup
> protocols combined with a firewall policy that because of this
> can and is blocking udp+tcp/53 in various ways.

I'd suggest that there are two other problems.  One is that
per-application resolver setups pretty much prevent caching of
any flavor (possibly not an issue if one opens applications,
keeps them open for a long time, and uses different target sites
with different applications, but, if that scenario has been
studied wrt frequency, I'm not aware of it).  The other, more
important, issue is that it just about guarantees an
inconsistent user experience wrt the treatment of names. =20

Of course those are tradeoffs against locally-improved
functionality and reasonable people can disagree about how
important those issues are wrt the other considerations.


> That said, I still ask when it is, in general, time to just
> move forward. I see for example many other reasons why people
> should not use that old software. IE6 for example. Yes,
> economically constrained situations exists, but that problem
> do not go away by having us not start using SRV or HTTP/1.1 or
> SNI or HTML5.0 or...pick your favourite. And with SPF, that is
> not used by the edge node either.
>=20
> I am asking more generally why specifically this DNS issue is
> so stuck, because I think that is unfair. We upgrade other
> protocols...

Where I probably agree with you is that I think that we need to
evaluate costs, benefits, and risks and to do so against an
understanding and hope that we will have _many_ more Internet
users a decade from now than we do today.  Accepting the latter
may justify changes even more painful than transition to a new
RRTYPE if we understand that we are inconveniencing a relatively
small number of people today in order to make things much better
for a far larger future number.  And that is why I have never
believed in arguments for guaranteed absolute forward
compatibility in Internet, and Internet-like, situations.

> But my point is, people disagree. As we see here ;-)

Indeed.  Even though I would hope that we can at least mostly
agree about the facts even if we disagree about the tradeoffs to
which they lead.

    john


From paf@frobbit.se  Mon Feb 27 11:43:08 2012
Return-Path: <paf@frobbit.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 9845B21F87F8 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 11:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SsWfUA9krQxw for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 11:43:08 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id DA2A521F87E9 for <ietf@ietf.org>; Mon, 27 Feb 2012 11:43:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 95D5B132E3DE4; Mon, 27 Feb 2012 20:43:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyttBtqLTc+4; Mon, 27 Feb 2012 20:43:06 +0100 (CET)
Received: from [192.165.72.14] (unknown [192.165.72.14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 55270132E3DDD; Mon, 27 Feb 2012 20:43:06 +0100 (CET)
Subject: Re: DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <4F4BBE5D.20905@gmail.com>
Date: Mon, 27 Feb 2012 20:43:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320> <4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:43:08 -0000

On 27 feb 2012, at 18:33, Hector wrote:

> I would like to poise this general question to the IETF/DNS community:
>=20
>    Given higher modern DNS server support for unnamed types, should
>    new protocols continues to pursue new RR types or does the
>    DNS Community believe this original infrastructure ideal is no =
longer
>    necessary and new protocols can use TXT records with a high
>    degree of DNS support confidence for robustness.
>=20
> Many new protocols use the TXT records simply as a fast entry, high =
support mechanism to store data on DNS. Is the mindset today such that =
this is still desirable, is there an DNS impact with this on going =
direction?

I have not heard anything else than arguments in RFC5507 against reusing =
same RRType for many different kind of use.

5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., R.
     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=3D44045 bytes)
     (Status: INFORMATIONAL)

So, still, no, you should not reuse TXT. You should have your own =
RRType. Other choices makes your design very complex.

Yes, many people will still disagree with me, using arguments I do not =
agree with...

  Patrik


From msk@cloudmark.com  Mon Feb 27 11:57:59 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6F121F87F3 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 11:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PFwnC53q-V9U for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 11:57:59 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 5734621F87EF for <ietf@ietf.org>; Mon, 27 Feb 2012 11:57:59 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Mon, 27 Feb 2012 11:57:58 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DNS RRTYPEs, the difficulty with
Thread-Topic: DNS RRTYPEs, the difficulty with
Thread-Index: AQHM9TzFjL91hLxbakSZS7QQB//GaZZRh2qAgAAkQwD//3w1EA==
Date: Mon, 27 Feb 2012 19:57:58 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <1473887.qQLEpWRMlg@scott-latitude-e6320> <20120224175748.GN48576@mail.yitter.info> <1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com> <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se>
In-Reply-To: <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:57:59 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of P=
atrik F=E4ltstr=F6m
> Sent: Monday, February 27, 2012 11:43 AM
> To: Hector
> Cc: ietf@ietf.org
> Subject: Re: DNS RRTYPEs, the difficulty with
>=20
> I have not heard anything else than arguments in RFC5507 against
> reusing same RRType for many different kind of use.
>=20
> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., R.
>      Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=3D44045 bytes)
>      (Status: INFORMATIONAL)
>=20
> So, still, no, you should not reuse TXT. You should have your own
> RRType. Other choices makes your design very complex.
>=20
> Yes, many people will still disagree with me, using arguments I do not
> agree with...

The conclusion of Section 3.5 of that document doesn't really address the f=
irst bullet in the same section, namely that the user interface by which th=
e new RRType would get added to a zone often doesn't support doing so.  Tha=
t's turned out to be a serious problem with, for example, the deployment of=
 the SPF record (RRType 99).

To accommodate user interface limitations, the RFC that defined SPF (2006) =
included use of TXT as a "backup" to enable a period of transition.  Collec=
ted evidence shows that a lot of clients do query the type, but fewer than =
5% of participating sites ever publish it even after six years.

In an ideal world I'd also like to see us move in the direction that RFC550=
7 promotes, but it seems we still aren't there yet.

-MSK

From sant9442@gmail.com  Mon Feb 27 12:19:43 2012
Return-Path: <sant9442@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 BD70F21F86FD for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level: 
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A+wW9At4tArH for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:19:43 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E85521F869D for <ietf@ietf.org>; Mon, 27 Feb 2012 12:19:43 -0800 (PST)
Received: by yhpp34 with SMTP id p34so672035yhp.31 for <ietf@ietf.org>; Mon, 27 Feb 2012 12:19:42 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.116.195 as permitted sender) client-ip=10.236.116.195; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.116.195 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.116.195]) by 10.236.116.195 with SMTP id g43mr23636711yhh.26.1330373982960 (num_hops = 1); Mon, 27 Feb 2012 12:19:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=y2AczkAhAAqqTzLI76SUZtBuYciyQc96EnGZsAcVGJU=; b=W8ORdxGzCS7Rk2I0JlXXJwguLdlQDZH9NeKTT2O6dP3yhha+pVs9aLqdg6A1IJ6M0j uj/jMI3lsrrTsn7O9v9ZVMlmECDDg55nYFTP6ZH48Wp+y2IHCDbKMWpkNCVxti40ThCI x7w9aijP1TqUb1tRpIO7aZ9mEB2YKAdtZ4tJY=
Received: by 10.236.116.195 with SMTP id g43mr17724726yhh.26.1330373982901; Mon, 27 Feb 2012 12:19:42 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id n72sm40860430yhh.21.2012.02.27.12.19.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 12:19:42 -0800 (PST)
Message-ID: <4F4BE558.6090908@gmail.com>
Date: Mon, 27 Feb 2012 15:19:36 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com> <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se>
In-Reply-To: <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:19:43 -0000

Thanks Patrick.

Is there an element, or include, the "Simplicity" argument that has 
been presented to you?

Thats the feeling I am getting - Fast entry, don' sweat the DNS impact 
and today, its high OS/software, DB speeds and overall robustness is 
good enough.  Once upon a time, the idea of redundancy (calls) was a 
concern, at least that seem to be the general mindset, but over time, 
I have seen statements that we shouldn't worry about it - just do it! 
  Better caching resolves much of the redundancy related overhead 
concerns.

PS: I agree with your position.

>> I would like to poise this general question to the IETF/DNS community:
>>
>>    Given higher modern DNS server support for unnamed types, should
>>    new protocols continues to pursue new RR types or does the
>>    DNS Community believe this original infrastructure ideal is no longer
>>    necessary and new protocols can use TXT records with a high
>>    degree of DNS support confidence for robustness.
>>
>> Many new protocols use the TXT records simply as a fast entry, high support mechanism to store data on DNS. Is the mindset today such that this is still desirable, is there an DNS impact with this on going direction?
> 
> I have not heard anything else than arguments in RFC5507 against reusing same RRType for many different kind of use.
> 
> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., R.
>      Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=44045 bytes)
>      (Status: INFORMATIONAL)
> 
> So, still, no, you should not reuse TXT. You should have your own RRType. Other choices makes your design very complex.
> 
> Yes, many people will still disagree with me, using arguments I do not agree with...
> 
>   Patrik
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From paf@frobbit.se  Mon Feb 27 12:30:40 2012
Return-Path: <paf@frobbit.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 C8EBA21F84B8 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJdfq0kkLILF for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:30:40 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id C6F2D21F849D for <ietf@ietf.org>; Mon, 27 Feb 2012 12:30:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 69415132E4FA1; Mon, 27 Feb 2012 21:30:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yXQAjYe-kfn; Mon, 27 Feb 2012 21:30:38 +0100 (CET)
Received: from [192.165.72.14] (unknown [192.165.72.14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 1E0AC132E4F9A; Mon, 27 Feb 2012 21:30:38 +0100 (CET)
Subject: Re: DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <4F4BE558.6090908@gmail.com>
Date: Mon, 27 Feb 2012 21:30:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1012B983-D6EB-4148-ADF4-D05874A7C4D1@frobbit.se>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com> <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se> <4F4BE558.6090908@gmail.com>
To: Hector <sant9442@gmail.com>
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:30:40 -0000

On 27 feb 2012, at 21:19, Hector wrote:

> Thanks Patrick.
>=20
> Is there an element, or include, the "Simplicity" argument that has =
been presented to you?
>=20
> Thats the feeling I am getting - Fast entry, don' sweat the DNS impact =
and today, its high OS/software, DB speeds and overall robustness is =
good enough.  Once upon a time, the idea of redundancy (calls) was a =
concern, at least that seem to be the general mindset, but over time, I =
have seen statements that we shouldn't worry about it - just do it!  =
Better caching resolves much of the redundancy related overhead =
concerns.
>=20
> PS: I agree with your position.

The arguments I hear are I think very unfortunate, but I of course =
understand them. They include for example:

- GUI (as in actual web interface or such) does not support the RRType

Example: Many DNS hosting providers do not allow even NAPTR or SRV =
RRTypes today. Even fewer URI or SPF.

- Code in for example bind and other name server software do not support =
the new RRType

Example: Even if one use Emacs, VI or whatever else txt tool one have to =
add the RR using hex which for complicated RRTypes might be very hard to =
calculate.

- The protocol used in clients is not DNS

Example: The actual lookup can only be of data that is proxied to =
various RRTypes that are "known"

- Local software do not handle new RRTypes

Example: Programmer want to use some resolver library that only support =
a subset of RRTypes that exists, and to use other RRTypes one must use =
"unknown" RRType or be able to at least enumerate exactly the #id of the =
RRType itself, and then parse the raw data that comes back.

- Firewall software do not handle new RRTypes

Example: Deep packet inspection of DNS flow(s) do only allow certain DNS =
RRTypes to pass through

...and more...

I do though think limiting us to certain types will have impact not only =
for effective use of HTTP and other protocols (I think we need SRV, URI =
etc), but also have impact on for example deployment of DNSSEC.

The first (successful) step was to ensure DNS core software do =
understand "unknown RRTypes" which I claim is now deployed "in the =
core". Edge is still questionable (see above).

I do not want to give up proper deployment though. I just do not do =
that.

Some people with very old software that can not be updated will loose. =
They will not get the new features new RRTypes can give.

Yes, a pain. But...we just must be able to get new RRTypes deployed. And =
not give up.

   Patrik

>>> I would like to poise this general question to the IETF/DNS =
community:
>>>=20
>>>   Given higher modern DNS server support for unnamed types, should
>>>   new protocols continues to pursue new RR types or does the
>>>   DNS Community believe this original infrastructure ideal is no =
longer
>>>   necessary and new protocols can use TXT records with a high
>>>   degree of DNS support confidence for robustness.
>>>=20
>>> Many new protocols use the TXT records simply as a fast entry, high =
support mechanism to store data on DNS. Is the mindset today such that =
this is still desirable, is there an DNS impact with this on going =
direction?
>> I have not heard anything else than arguments in RFC5507 against =
reusing same RRType for many different kind of use.
>> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., =
R.
>>     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=3D44045 =
bytes)
>>     (Status: INFORMATIONAL)
>> So, still, no, you should not reuse TXT. You should have your own =
RRType. Other choices makes your design very complex.
>> Yes, many people will still disagree with me, using arguments I do =
not agree with...
>>  Patrik
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From paul.hoffman@vpnc.org  Mon Feb 27 12:32:18 2012
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 2D0FD21F84B8 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v7cX4hzB7dKs for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:32:17 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id A742621F849D for <ietf@ietf.org>; Mon, 27 Feb 2012 12:32:17 -0800 (PST)
Received: from sn87.proper.com (sn87.proper.com [75.101.18.87]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1RKWC6i048150 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 27 Feb 2012 13:32:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>
Date: Mon, 27 Feb 2012 12:32:11 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <1473887.qQLEpWRMlg@scott-latitude-e6320> <20120224175748.GN48576@mail.yitter.info> <1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com> <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:32:18 -0000

On Feb 27, 2012, at 11:57 AM, Murray S. Kucherawy wrote:

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of Patrik F=E4ltstr=F6m
>> Sent: Monday, February 27, 2012 11:43 AM
>> To: Hector
>> Cc: ietf@ietf.org
>> Subject: Re: DNS RRTYPEs, the difficulty with
>>=20
>> I have not heard anything else than arguments in RFC5507 against
>> reusing same RRType for many different kind of use.
>>=20
>> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., =
R.
>>     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=3D44045 =
bytes)
>>     (Status: INFORMATIONAL)
>>=20
>> So, still, no, you should not reuse TXT. You should have your own
>> RRType. Other choices makes your design very complex.
>>=20
>> Yes, many people will still disagree with me, using arguments I do =
not
>> agree with...
>=20
> The conclusion of Section 3.5 of that document doesn't really address =
the first bullet in the same section, namely that the user interface by =
which the new RRType would get added to a zone often doesn't support =
doing so.  That's turned out to be a serious problem with, for example, =
the deployment of the SPF record (RRType 99).

Which user interfaces are people using to add RRtype 99? If you are =
having them edit zone files by hand well, yes, that would not work real =
well for SPF. If there is a simple tool that takes the needed =
information and create a standard-formatted record that can be =
copy-and-pasted, it would make use of that RRtype much easier. If no =
such tool exists, I propose that it can be created easily.

--Paul Hoffman


From scott@kitterman.com  Mon Feb 27 12:35:22 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C845B21F8698 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRhwSsNBd3rR for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 12:35:22 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0D47D21F867C for <ietf@ietf.org>; Mon, 27 Feb 2012 12:35:13 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 992C120E40E0; Mon, 27 Feb 2012 15:35:12 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330374912; bh=wMgswrcVKhavitWjKav8jVcA5UVk8cnxlvD0Uvh8Rhg=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=ClUirJDcuf8QChWdYUW25lJg+fzpklaNvDoxfd3zc+u+/dPAdyuT5wZ6GEqlK242N dYue4HXUgM0GNwUntdnwJCvI+d6Tz8VFlej1s4fMY33Lqw6jy21sWl0dlC2Om1r3oz MErJwd/2PCg43OmLTqTQCvoFbilNV2Nr4TprH3Rk=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 7FAF920E40A4;  Mon, 27 Feb 2012 15:35:12 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Mon, 27 Feb 2012 15:35:11 -0500
Message-ID: <3503462.Q2aCvq3QGU@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 20:35:22 -0000

On Monday, February 27, 2012 12:32:11 PM Paul Hoffman wrote:
> On Feb 27, 2012, at 11:57 AM, Murray S. Kucherawy wrote:
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Beha=
lf
> >> Of Patrik F=E4ltstr=F6m Sent: Monday, February 27, 2012 11:43 AM
> >> To: Hector
> >> Cc: ietf@ietf.org
> >> Subject: Re: DNS RRTYPEs, the difficulty with
> >>=20
> >> I have not heard anything else than arguments in RFC5507 against
> >> reusing same RRType for many different kind of use.
> >>=20
> >> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed.=
, R.
> >>=20
> >>     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=3D44045
> >>     bytes)
> >>     (Status: INFORMATIONAL)
> >>=20
> >> So, still, no, you should not reuse TXT. You should have your own
> >> RRType. Other choices makes your design very complex.
> >>=20
> >> Yes, many people will still disagree with me, using arguments I do=
 not
> >> agree with...
> >=20
> > The conclusion of Section 3.5 of that document doesn't really addre=
ss
> > the first bullet in the same section, namely that the user interfac=
e by
> > which the new RRType would get added to a zone often doesn't suppor=
t
> > doing so.  That's turned out to be a serious problem with, for exam=
ple,
> > the deployment of the SPF record (RRType 99).
> Which user interfaces are people using to add RRtype 99? If you are h=
aving
> them edit zone files by hand well, yes, that would not work real well=
 for
> SPF. If there is a simple tool that takes the needed information and =
create
> a standard-formatted record that can be copy-and-pasted, it would mak=
e use
> of that RRtype much easier. If no such tool exists, I propose that it=
 can
> be created easily.

We've published a script to take a Type TXT SPF record and give a Type =
SPF=20
output as part of the pyspf library since very shortly after Type SPF w=
as=20
assigned.  It's been around for years, so the lack of that type of tool=
 isn't=20
an issue.

Scott K

From sant9442@gmail.com  Mon Feb 27 13:03:57 2012
Return-Path: <sant9442@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 99E3221E8014 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 13:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.663
X-Spam-Level: 
X-Spam-Status: No, score=-2.663 tagged_above=-999 required=5 tests=[AWL=-0.304, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDwRc+ZenPRW for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 13:03:57 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6192E21E800C for <ietf@ietf.org>; Mon, 27 Feb 2012 13:03:51 -0800 (PST)
Received: by yenm5 with SMTP id m5so577661yen.31 for <ietf@ietf.org>; Mon, 27 Feb 2012 13:03:51 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.175.36 as permitted sender) client-ip=10.236.175.36; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.175.36 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.175.36]) by 10.236.175.36 with SMTP id y24mr23182490yhl.64.1330376631078 (num_hops = 1); Mon, 27 Feb 2012 13:03:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GXwrgzwBghucsOhnwzmCEK5JQoKnghCHTzwUSE7lrjg=; b=rVLt/4dhGaiaCopXndtjVXaOp/NP52/F3rg3bb4t6N2dgQvLfa1FojugL12b/ETDSn XyFroQRPYLZkp9SADHs8Oc/u6pu6F2KcbvBnbGxdCJ7xN0GnyccpXAwVZdZwBqadpyle u+qJg+fhO/PIMLChtKb7FI3IYxuF5Ycj19vfs=
Received: by 10.236.175.36 with SMTP id y24mr17377529yhl.64.1330376631020; Mon, 27 Feb 2012 13:03:51 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id n63sm41195720yhb.8.2012.02.27.13.03.49 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 13:03:50 -0800 (PST)
Message-ID: <4F4BEFB0.3030700@gmail.com>
Date: Mon, 27 Feb 2012 16:03:44 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it>	<4F4BBE5D.20905@gmail.com>	<C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se>	<4F4BE558.6090908@gmail.com> <1012B983-D6EB-4148-ADF4-D05874A7C4D1@frobbit.se>
In-Reply-To: <1012B983-D6EB-4148-ADF4-D05874A7C4D1@frobbit.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:03:57 -0000

Patrick, I agree 100% with your well stated, outlined functional and 
technical position, which is why I want to get a feel for what is the 
current mindset which seems to be one of simplicity and not one that 
no longer relates or less concern with the original ideals of using 
specific RR types optimizes DNS large scale application usage.  Yes, I 
don't think we should give up.

The specific case is with SPF and it 2006 fast track WG consensus to 
include a registration for a new type 99 SPF type. It help appease 
many of the DNS concerns and perhaps would help with the IETF politics 
(endorsement).  That is how I saw it.

Yet, giving the practically realities, our own implementation disabled 
the SPF type lookup, and like many I believe think, it would be a 
useless wasted call.

Now a new BIS effort has started and to my surprise the original 
environment migration path of first getting clients to support types, 
the data evidence have shown that original intent right on, a short 
term hiccups and expectation for the necessity of getting DNS servers 
to be updated and a long term expectation that the new RR type would 
be eventually be dominate and successful.  In the mean time, some 
initial overhead would be expected.

But what has happen is that its now a "Who's Who" using it criteria as 
a measuring stick to abandon the new type.  I am sure there will be 
those who say that is not the criteria and thats find, I understand it.

It is excludes what the original ideal and intention was and all 
evidence is showing that the migration path expected is on par and 
right on, - get the clients to support both before a new BIS 
specification can safely recommend a pure single RR type to be 
published rather than both    type 99 and TXT.

So I believe revisiting the original ideal goal will help in these 
decisions regarding the exploration of using new RR types - not a 
"who's who" highly subjective criteria that has nothing to do with 
with the fundamental ideal of improving DNS operations.

I'm not getting any traction using this fundamental consideration and 
its odd to me, to be frank.


ï¿½ wrote:
> On 27 feb 2012, at 21:19, Hector wrote:
> 
>> Thanks Patrick.
>>
>> Is there an element, or include, the "Simplicity" argument that has been presented to you?
>>
>> Thats the feeling I am getting - Fast entry, don' sweat the DNS impact and today, its high OS/software, DB speeds and overall robustness is good enough.  Once upon a time, the idea of redundancy (calls) was a concern, at least that seem to be the general mindset, but over time, I have seen statements that we shouldn't worry about it - just do it!  Better caching resolves much of the redundancy related overhead concerns.
>>
>> PS: I agree with your position.
> 
> The arguments I hear are I think very unfortunate, but I of course understand them. They include for example:
> 
> - GUI (as in actual web interface or such) does not support the RRType
> 
> Example: Many DNS hosting providers do not allow even NAPTR or SRV RRTypes today. Even fewer URI or SPF.
> 
> - Code in for example bind and other name server software do not support the new RRType
> 
> Example: Even if one use Emacs, VI or whatever else txt tool one have to add the RR using hex which for complicated RRTypes might be very hard to calculate.
> 
> - The protocol used in clients is not DNS
> 
> Example: The actual lookup can only be of data that is proxied to various RRTypes that are "known"
> 
> - Local software do not handle new RRTypes
> 
> Example: Programmer want to use some resolver library that only support a subset of RRTypes that exists, and to use other RRTypes one must use "unknown" RRType or be able to at least enumerate exactly the #id of the RRType itself, and then parse the raw data that comes back.
> 
> - Firewall software do not handle new RRTypes
> 
> Example: Deep packet inspection of DNS flow(s) do only allow certain DNS RRTypes to pass through
> 
> ...and more...
> 
> I do though think limiting us to certain types will have impact not only for effective use of HTTP and other protocols (I think we need SRV, URI etc), but also have impact on for example deployment of DNSSEC.
> 
> The first (successful) step was to ensure DNS core software do understand "unknown RRTypes" which I claim is now deployed "in the core". Edge is still questionable (see above).
> 
> I do not want to give up proper deployment though. I just do not do that.
> 
> Some people with very old software that can not be updated will loose. They will not get the new features new RRTypes can give.
> 
> Yes, a pain. But...we just must be able to get new RRTypes deployed. And not give up.
> 
>    Patrik
> 
>>>> I would like to poise this general question to the IETF/DNS community:
>>>>
>>>>   Given higher modern DNS server support for unnamed types, should
>>>>   new protocols continues to pursue new RR types or does the
>>>>   DNS Community believe this original infrastructure ideal is no longer
>>>>   necessary and new protocols can use TXT records with a high
>>>>   degree of DNS support confidence for robustness.
>>>>
>>>> Many new protocols use the TXT records simply as a fast entry, high support mechanism to store data on DNS. Is the mindset today such that this is still desirable, is there an DNS impact with this on going direction?
>>> I have not heard anything else than arguments in RFC5507 against reusing same RRType for many different kind of use.
>>> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., R.
>>>     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=44045 bytes)
>>>     (Status: INFORMATIONAL)
>>> So, still, no, you should not reuse TXT. You should have your own RRType. Other choices makes your design very complex.
>>> Yes, many people will still disagree with me, using arguments I do not agree with...
>>>  Patrik
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From marka@isc.org  Mon Feb 27 13:49:07 2012
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 1215621E801A for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 13:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level: 
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[AWL=0.153,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRlFYfv3b6IW for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 13:49:06 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 0932121E800C for <ietf@ietf.org>; Mon, 27 Feb 2012 13:49:06 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 695FE5F9891; Mon, 27 Feb 2012 21:48:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:99bb:33d4:f25c:36e7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id ACCF1216C33; Mon, 27 Feb 2012 21:48:38 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 79A4D1DDACC9; Tue, 28 Feb 2012 08:48:21 +1100 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org> <3503462.Q2aCvq3QGU@scott-latitude-e6320>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Mon, 27 Feb 2012 15:35:11 CDT." <3503462.Q2aCvq3QGU@scott-latitude-e6320>
Date: Tue, 28 Feb 2012 08:48:21 +1100
Message-Id: <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:49:07 -0000

In message <3503462.Q2aCvq3QGU@scott-latitude-e6320>, Scott Kitterman writes:
> On Monday, February 27, 2012 12:32:11 PM Paul Hoffman wrote:
> > On Feb 27, 2012, at 11:57 AM, Murray S. Kucherawy wrote:
> > >> -----Original Message-----
> > >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> > >> Of Patrik F=E4ltstr=F6m Sent: Monday, February 27, 2012 11:43 AM
> > >> To: Hector
> > >> Cc: ietf@ietf.org
> > >> Subject: Re: DNS RRTYPEs, the difficulty with
> > >> =
> 
> > >> I have not heard anything else than arguments in RFC5507 against
> > >> reusing same RRType for many different kind of use.
> > >> =
> 
> > >> 5507 Design Choices When Expanding the DNS. IAB, P. Faltstrom, Ed., R.
> > >> =
> 
> > >>     Austein, Ed., P. Koch, Ed.. April 2009. (Format: TXT=3D44045
> > >>     bytes)
> > >>     (Status: INFORMATIONAL)
> > >> =
> 
> > >> So, still, no, you should not reuse TXT. You should have your own
> > >> RRType. Other choices makes your design very complex.
> > >> =
> 
> > >> Yes, many people will still disagree with me, using arguments I do not
> > >> agree with...
> > > =
> 
> > > The conclusion of Section 3.5 of that document doesn't really address
> > > the first bullet in the same section, namely that the user interface by
> > > which the new RRType would get added to a zone often doesn't support
> > > doing so.  That's turned out to be a serious problem with, for example,
> > > the deployment of the SPF record (RRType 99).
> > Which user interfaces are people using to add RRtype 99? If you are having
> > them edit zone files by hand well, yes, that would not work real well for
> > SPF. If there is a simple tool that takes the needed information and crea=
> te
> > a standard-formatted record that can be copy-and-pasted, it would make use
> > of that RRtype much easier. If no such tool exists, I propose that it can
> > be created easily.
> 
> We've published a script to take a Type TXT SPF record and give a Type SPF =
> 
> output as part of the pyspf library since very shortly after Type SPF was =
> 
> assigned.  It's been around for years, so the lack of that type of tool isn=
> 't =
> 
> an issue.
> 
> Scott K

My user interface is "vi".

RFC 4408 April 2006

revision 1.1
date: 2005-07-14 16:46:44 +1000;  author: marka;  state: Exp;
branches:  1.1.2;
1892.   [func]          Support for SPF rdata type. [RT #15033]

It was first available in BIND 9.4.0 (Feb 2007) earlier still if
you were willing to run alpha/beta/rc.

OS vendors could have supplied it earlier.

cp lib/dns/rdata/generic/txt_16.c lib/dns/rdata/generic/spf_19.c
cp lib/dns/rdata/generic/txt_16.h lib/dns/rdata/generic/spf_19.h

s/TXT/SPF/
s/txt/spf/
s/16/99/

make clean
make

You don't even have to touch a Makefile.   After that all the tools
that come with BIND support SPF.

If I remember correctly someone did something like that and made it
available.  Its definitely been done for a number of new types.

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

From marka@isc.org  Mon Feb 27 13:58:12 2012
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 C14BE21E803A for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 13:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.802
X-Spam-Level: 
X-Spam-Status: No, score=-1.802 tagged_above=-999 required=5 tests=[AWL=-0.495, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8zTVnbhwVRB for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 13:58:12 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 5208D21E802F for <ietf@ietf.org>; Mon, 27 Feb 2012 13:58:12 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id A032A5F9899; Mon, 27 Feb 2012 21:57:56 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:99bb:33d4:f25c:36e7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 88CE9216C31; Mon, 27 Feb 2012 21:57:54 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 2F7AA1DDB084; Tue, 28 Feb 2012 08:57:46 +1100 (EST)
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org> <3503462.Q2aCvq3QGU@scott-latitude-e6320> <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Tue, 28 Feb 2012 08:48:21 +1100." <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
Date: Tue, 28 Feb 2012 08:57:45 +1100
Message-Id: <20120227215746.2F7AA1DDB084@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 21:58:12 -0000

Additionally, java and python both support unknown types.  Adding
new types in both of these appears to be straight forward.  C has
always suppported unkown types.  If your favourite language / OS
doesn't support unknown types complain to the developer / vendor.

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

From msk@cloudmark.com  Mon Feb 27 14:16:35 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5B121F864E for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:16:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSBcfAHaxKN1 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:16:34 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id 6026D21F8631 for <ietf@ietf.org>; Mon, 27 Feb 2012 14:16:34 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Mon, 27 Feb 2012 14:16:33 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DNS RRTYPEs, the difficulty with
Thread-Topic: DNS RRTYPEs, the difficulty with
Thread-Index: AQHM9ZmFjL91hLxbakSZS7QQB//GaZZRTluw
Date: Mon, 27 Feb 2012 22:16:33 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org> <3503462.Q2aCvq3QGU@scott-latitude-e6320> <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
In-Reply-To: <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:16:35 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of M=
ark Andrews
> Sent: Monday, February 27, 2012 1:48 PM
> To: Scott Kitterman
> Cc: ietf@ietf.org
> Subject: Re: DNS RRTYPEs, the difficulty with
>=20
> My user interface is "vi".

Mine too.

> revision 1.1
> date: 2005-07-14 16:46:44 +1000;  author: marka;  state: Exp;
> branches:  1.1.2;
> 1892.   [func]          Support for SPF rdata type. [RT #15033]
>=20
> It was first available in BIND 9.4.0 (Feb 2007) earlier still if you
> were willing to run alpha/beta/rc.
>=20
> OS vendors could have supplied it earlier.

The question is not whether the nameservers themselves support it (we know =
these days that they do), but rather the user interfaces that many people h=
ave to use to create records.  For example, several web-based "domain contr=
ol panel" things for virtual web site hosting know how to add the common ty=
pes, but not others.  This has even challenged deployment of DKIM, which do=
esn't have its own RRType and re-uses TXT, because it's strange for some pe=
ople to post a big base64 blob into a web form for which the label is "host=
name/address" or some such.

-MSK

From scott@kitterman.com  Mon Feb 27 14:17:58 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8154B21E8042 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:17:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaFzuupmpchU for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:17:57 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id B66AD21E802B for <ietf@ietf.org>; Mon, 27 Feb 2012 14:17:57 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id B1A0920E40E0; Mon, 27 Feb 2012 17:17:56 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330381076; bh=R+cc/1xp8yM0Jxx5otnTewTyFcYGs8Ed/ZpGhm5Nn30=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=IDViMuTYW17EQoF6HhpLhH/8EFyFvoPCd4lwTKHLLFMKojGyWtvjELzeP8xtQgxNn D9F4RMx2SXwovJ8oWsJFlla5DkP075B+zmXm4ZJY3+Hj5H40JLaoCIT3CGNyeyiQya JUwSBDXghkN0uObvQn6lF6o4hI2n7RbQrvyx30cY=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 9458F20E40A4;  Mon, 27 Feb 2012 17:17:56 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Mon, 27 Feb 2012 17:17:56 -0500
Message-ID: <4282977.WyujTem3qu@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <3503462.Q2aCvq3QGU@scott-latitude-e6320> <20120227214821.79A4D1DDACC9@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:17:58 -0000

On Tuesday, February 28, 2012 08:48:21 AM Mark Andrews wrote:
...
> My user interface is "vi".
...
This puts you firmly in the group of technical people who will have no problem 
deploying new RR types.  Most domain owners don't fall into that group and the 
user interfaces they use still don't support Type SPF even after more than 
half a decade.

Scott K

P.S.  That's my user interface too.

From dougb@dougbarton.us  Mon Feb 27 14:27:00 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC2A821E8026 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:27:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.689
X-Spam-Level: 
X-Spam-Status: No, score=-3.689 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MnYODxx4TMql for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:27:00 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id DFC7B21E804B for <ietf@ietf.org>; Mon, 27 Feb 2012 14:26:59 -0800 (PST)
Received: (qmail 27662 invoked by uid 399); 27 Feb 2012 22:26:57 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 27 Feb 2012 22:26:57 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F4C0331.3060700@dougbarton.us>
Date: Mon, 27 Feb 2012 14:26:57 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <1473887.qQLEpWRMlg@scott-latitude-e6320> <20120224175748.GN48576@mail.yitter.info> <1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com> <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:27:00 -0000

On 2/27/2012 11:57 AM, Murray S. Kucherawy wrote:
> To accommodate user interface limitations, the RFC that defined SPF (2006) included use of TXT as a "backup" to enable a period of transition.  Collected evidence shows that a lot of clients do query the type, but fewer than 5% of participating sites ever publish it even after six years.
> 
> In an ideal world I'd also like to see us move in the direction that RFC5507 promotes, but it seems we still aren't there yet.

It's important to understand the history here. The problem of "old
software chokes on new RR types" was a known issue way back when, and
3597 came out in Sept. 2003 to help address it. When 4408 came out
defining SPF in April of 2006 support for 3597 was still being rolled
out, and was nowhere near the point where it could be safely assumed in
even a meaningful minority of the deployed base.

The error for SPF came with the TXT bootstrap version. It's easy to see
now (whether it was easy to see then or not is water under the bridge at
this point) that this was a mistake. As painful as it would have been
back in 2006 to wait for support for 3597 and/or the SPF RRtype to
propagate, we would be in a much better situation *now* if we had waited.

So, what we need to do is learn from that experience. 8.5 years later
support for 3597 is a very reasonable thing to expect, and with AAAA,
DNSSEC, etc. we're well past the era where hidebound DNS software is an
acceptable operational model.

Do I believe that insisting on new RRtypes will be a pain-free
experience? Of course not. But if we don't insist on it at this point,
every day we delay it becomes more and more painful, not less.

To circle back to my suggestion that SRV be an integral part of any new
HTTP effort, it's 12 years old, so predates both of the above. :)


Doug

-- 

	It's always a long day; 86400 doesn't fit into a short.

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/


From sant9442@gmail.com  Mon Feb 27 14:35:06 2012
Return-Path: <sant9442@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 2D00D21F85D0 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[AWL=-0.303,  BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7MOz+mSBd9Fg for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 14:35:05 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id CBA4921F85CF for <ietf@ietf.org>; Mon, 27 Feb 2012 14:35:01 -0800 (PST)
Received: by ghbg16 with SMTP id g16so2580638ghb.31 for <ietf@ietf.org>; Mon, 27 Feb 2012 14:35:01 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.173.132 as permitted sender) client-ip=10.236.173.132; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.173.132 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.173.132]) by 10.236.173.132 with SMTP id v4mr24130178yhl.78.1330382101501 (num_hops = 1); Mon, 27 Feb 2012 14:35:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=i0Tf5CLP0NUFnZSYhTO7PiEcbPia1Ln9CVDdapZ0wUc=; b=q83tgtxAoKe8fyEHvjJR4NeQ7SzN+lzFRWReBVoGDOKBbOipEB2qbhctMWKXgVwZn6 NF1Y+mm8nwbVW09hR5OIIXW4UtR3IveLybnFH+I1epdOJZPGvhqiHfEMRSkmo9Q/KftS 8dZpNuVnBOnjjs8RwzIhoaaUNWeinKpBILSho=
Received: by 10.236.173.132 with SMTP id v4mr18107672yhl.78.1330382101455; Mon, 27 Feb 2012 14:35:01 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id v21sm32303983yhk.3.2012.02.27.14.34.59 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 14:35:00 -0800 (PST)
Message-ID: <4F4C050C.8020401@gmail.com>
Date: Mon, 27 Feb 2012 17:34:52 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>	<0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org>	<3503462.Q2aCvq3QGU@scott-latitude-e6320>	<20120227214821.79A4D1DDACC9@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:35:06 -0000

Murray S. Kucherawy wrote:
>> -----Original Message-----
>>
>> OS vendors could have supplied it earlier.
> 
> The question is not whether the nameservers themselves support it (we know these days that they do), but rather the user interfaces that many people have to use to create records.  For example, several web-based "domain control panel" things for virtual web site hosting know how to add the common types, but not others.  This has even challenged deployment of DKIM, which doesn't have its own RRType and re-uses TXT, because it's strange for some people to post a big base64 blob into a web form for which the label is "hostname/address" or some such.

These are valid widest total infrastructure support goals, but I don't 
believe its (and I believe RC5507 and Patrick is stating) are valid 
arguments against the usage and promotion of using RR types.  Well 
understood, but not an excuse to abandon the ideal because in my 
personal view a "Simplicity" factor has emerged with many ISPs 
offering WEB-based DNS management frontends. I don' think that means 
it wasn't possible for them to support new RR type record input - some 
simply took the path to least support resistance.

Any-hoo, that is why i poise the question in regards to what are the 
new "ideals."

Just consider, Murray, it isn't a big deal in 2006 for SPF/MARID 
efforts, then it would had never came up as a suggestion as a IETF/DNS 
community endorsement appeasing idea to help mode the I-D for what 
become RFC 4408.  After all, SPF already had a long list of IETF key 
cogs who were militantly against it - and some who are still are now 
deciding its BIS future.

The essence I am getting from limited WG participant leading these 
efforts, is that it doesn't matter any more, don't bother to even 
consider it any more. Its a waste of time.

-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com

From marka@isc.org  Mon Feb 27 14:48:29 2012
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 5C0C621E8026; Mon, 27 Feb 2012 14:48:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=0.158,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VwzL3FJg+lFc; Mon, 27 Feb 2012 14:48:28 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id B635C21E801E; Mon, 27 Feb 2012 14:48:28 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 772EAC941E; Mon, 27 Feb 2012 22:48:11 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:99bb:33d4:f25c:36e7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 1C561216C36; Mon, 27 Feb 2012 22:48:11 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 4964A1DDBB0C; Tue, 28 Feb 2012 09:48:03 +1100 (EST)
To: Willy Tarreau <w@1wt.eu>
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F46BFDF.3070703@dougbarton.us> <20120224025433.00F1A1DC6AEB@drugs.dv.isc.org> <20120224153818.GE48576@mail.yitter.info> <D7E6B990-3A02-4999-A6EB-2A3585D29B45@frobbit.se> <DC8A7C4316C6F97607CFBCC6@PST.JCK.COM> <5B092333-30BD-481B-8E6A-F41DB5C586C2@frobbit.se> <20120226064025.GH8633@1wt.eu>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-reply-to: Your message of "Sun, 26 Feb 2012 07:40:25 BST." <20120226064025.GH8633@1wt.eu>
Date: Tue, 28 Feb 2012 09:48:03 +1100
Message-Id: <20120227224803.4964A1DDBB0C@drugs.dv.isc.org>
Cc: IETF Discussion <ietf@ietf.org>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <patrik@frobbit.se>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>, "mnot@mnot.net" <mnot@mnot.net>, "iesg@ietf.org" <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:48:29 -0000

In message <20120226064025.GH8633@1wt.eu>, Willy Tarreau writes:
> On Fri, Feb 24, 2012 at 05:57:31PM +0100, Patrik F=E4ltstr=F6m wrote:
> > I am asking more generally why specifically this DNS issue is so stuck,
> > because I think that is unfair. We upgrade other protocols...

> 
> Because in HTTP, anybody can be anywhere. You can have client-side proxies,
> server-side gateways, load balancers, etc... everyone in this chain may or
> may not resolve, it's only a matter of configuration and architecture choic=
> e.
> There are plenty of places where clients won't access public resolvers at a=
> ll
> and rely on their proxies for this. So you can't make use of DNS to improve
> these users' experience.

Proxies can lookup SRV records.  They already lookup A and AAAA records.
 
> Also, DNS is SLLLLOOOOWWWWW. It's fast enough to send a mail. But for HTTP
> it adds too much latency. Some people in the mobile world would like to be
> able to configure an explicit proxy on their smartphones in order to avoid
> a very expensive round trip before fetching an object : at 20 host names
> on a web page, 300 ms round trip means 6 seconds are lost to resolve these
> objects if they can't be totally parallelized.

If they can't be parallelized then you can blame the page developer.

As for SRV you can always do SRV + AAAA + A in parallel.

> DNS suggestion is something going back and forth regularly. I think that
> people who try to push it hard only see the very simple case where users
> have a direct low-latency internet connection. The reality is much much
> different. This well reflected by the fact that in the end, after many
> proposals, it has still not been adopted !
> 
> Regards,
> Willy
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Mon Feb 27 15:05:22 2012
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 801A421F85BE for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 15:05:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[AWL=0.156,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxqT6x29Ii-z for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 15:05:22 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id E6EF221F8599 for <ietf@ietf.org>; Mon, 27 Feb 2012 15:05:21 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id B69005F9887; Mon, 27 Feb 2012 23:05:06 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:99bb:33d4:f25c:36e7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id AACFC216C36; Mon, 27 Feb 2012 23:05:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 5EF111DDBE1F; Tue, 28 Feb 2012 10:04:57 +1100 (EST)
To: Hector <sant9442@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org> <3503462.Q2aCvq3QGU@scott-latitude-e6320> <20120227214821.79A4D1DDACC9@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com> <4F4C050C.8020401@gmail.com>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Mon, 27 Feb 2012 17:34:52 CDT." <4F4C050C.8020401@gmail.com>
Date: Tue, 28 Feb 2012 10:04:56 +1100
Message-Id: <20120227230457.5EF111DDBE1F@drugs.dv.isc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:05:22 -0000

Many web interfaces are little more than line text editors with a pulldown
list for the type.  Very few are more than that.  The data just gets passed,
as text, to a backend which adds it to a database / zone.  Lots of those
backends already support the new type.  The only change that needs to be
made is to add a type to the pull down list.

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

From msk@cloudmark.com  Mon Feb 27 15:11:25 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E3221E800C for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 15:11:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8tHiOoEYR5l for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 15:11:19 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id E8D0C21F857A for <ietf@ietf.org>; Mon, 27 Feb 2012 15:11:19 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Mon, 27 Feb 2012 15:11:19 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DNS RRTYPEs, the difficulty with
Thread-Topic: DNS RRTYPEs, the difficulty with
Thread-Index: AQHM9aQ4jL91hLxbakSZS7QQB//GaZZRXsrA
Date: Mon, 27 Feb 2012 23:11:18 +0000
Message-ID: <9452079D1A51524AA5749AD23E0039280499B0@exch-mbx901.corp.cloudmark.com>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org> <3503462.Q2aCvq3QGU@scott-latitude-e6320> <20120227214821.79A4D1DDACC9@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com> <4F4C050C.8020401@gmail.com> <20120227230457.5EF111DDBE1F@drugs.dv.isc.org>
In-Reply-To: <20120227230457.5EF111DDBE1F@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:11:25 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of M=
ark Andrews
> Sent: Monday, February 27, 2012 3:05 PM
> To: Hector
> Cc: ietf@ietf.org
> Subject: Re: DNS RRTYPEs, the difficulty with
>=20
> Many web interfaces are little more than line text editors with a
> pulldown list for the type.  Very few are more than that.  The data
> just gets passed, as text, to a backend which adds it to a database /
> zone.  Lots of those backends already support the new type.  The only
> change that needs to be made is to add a type to the pull down list.

Right, and I think we're facing the fact that people just aren't doing that=
 despite these fine RFCs we've been citing.  Now what?

-MSK

From sant9442@gmail.com  Mon Feb 27 15:26:14 2012
Return-Path: <sant9442@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 7E73621E8049 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 15:26:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lqyBjdoZukwJ for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 15:26:14 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6F29D21E803C for <ietf@ietf.org>; Mon, 27 Feb 2012 15:26:09 -0800 (PST)
Received: by yenm5 with SMTP id m5so642795yen.31 for <ietf@ietf.org>; Mon, 27 Feb 2012 15:26:09 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.191.105 as permitted sender) client-ip=10.236.191.105; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.191.105 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.191.105]) by 10.236.191.105 with SMTP id f69mr25074589yhn.23.1330385169131 (num_hops = 1); Mon, 27 Feb 2012 15:26:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=UFinihRVKI6NpemYd+Csshcl6XeyrJukEzYSO4lnizE=; b=VMUz5py9+GPqzKM1GRVaC319bEXVZFN8CEsJgwSCDhBlzkhYBW5/WTb/nprapCLKLh a4L1WFdmF49YC0n/vlUaVQVQV+uvCOLZ22i+nzoxAfMLF37gZMzft+oupmJg/U8mGa4P wo/rbGFt2V9bzNwCo2QFHoD+BWHhJt0yvVBRk=
Received: by 10.236.191.105 with SMTP id f69mr18811779yhn.23.1330385169087; Mon, 27 Feb 2012 15:26:09 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id s10sm25607400anl.17.2012.02.27.15.26.06 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 15:26:07 -0800 (PST)
Message-ID: <4F4C1106.4020806@gmail.com>
Date: Mon, 27 Feb 2012 18:25:58 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>	<0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org>	<3503462.Q2aCvq3QGU@scott-latitude-e6320>	<20120227214821.79A4D1DDACC9@drugs.dv.isc.org>	<9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com>	<4F4C050C.8020401@gmail.com> <20120227230457.5EF111DDBE1F@drugs.dv.isc.org>
In-Reply-To: <20120227230457.5EF111DDBE1F@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:26:14 -0000

Mark Andrews wrote:
> Many web interfaces are little more than line text editors with a pulldown
> list for the type.  Very few are more than that.  The data just gets passed,
> as text, to a backend which adds it to a database / zone.  Lots of those
> backends already support the new type.  The only change that needs to be
> made is to add a type to the pull down list.
> 

In one support case, gigantic isp to remain nameless, the addition of 
new TXT-based protocol support now caused "wildcard conflicts" between 
SPF and DKIM.

Customer to us: What records to I add?

Us: Use our tool-generated records and contact ISP - they should have 
a "Total DNS management" web based system, to add the generated 
records there.

They did, there was a conflict with getting DKIM records and SPF 
records, two different name spaces.

Us: Constant ISP, they should allow you to separate SPF and DKIM records.

ISP to Customer:  Nothing wrong, its all fine.  Just add it under TXT.

Customer to US:  Is this your BUG?

Us: It has to be the ISP, lets check it out - Remote support.

There was no specific way to separate TXT records, it was all lump 
under one input.

US: Contact ISP, tell them what we told you.

Customer to US:  VOILA, fixed, ISP fixed it with a special prefix you 
add to the record.

Basically, what they did was independent of the pull down, the 
editable field allowed you to add the subdomain prefix.

Whatever! :)

Agree, it isn't so far to update the frontend, but we can't always 
blame the ISP when the specification isn't all clear. If the 
impression is that TXT is good enough, then the expense to do code 
change is less justified.


From conte@isoc.org  Mon Feb 27 16:22:46 2012
Return-Path: <conte@isoc.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 3802621E8015 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 16:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.369
X-Spam-Level: 
X-Spam-Status: No, score=-101.369 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeir4zbQzm5z for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 16:22:45 -0800 (PST)
Received: from smtp167.iad.emailsrvr.com (smtp167.iad.emailsrvr.com [207.97.245.167]) by ietfa.amsl.com (Postfix) with ESMTP id 5D29921E800C for <ietf@ietf.org>; Mon, 27 Feb 2012 16:22:40 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp26.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 944BAA8571 for <ietf@ietf.org>; Mon, 27 Feb 2012 19:22:39 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp26.relay.iad1a.emailsrvr.com (Authenticated sender: conte-AT-isoc.org) with ESMTPSA id 52E31A8559 for <ietf@ietf.org>; Mon, 27 Feb 2012 19:22:39 -0500 (EST)
From: Steve Conte <conte@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: ISOC Fellowship to the IETF (IETF 84 and 85)
Date: Mon, 27 Feb 2012 16:22:38 -0800
Message-Id: <FAC3E692-CFB6-4189-A867-B2F093A7FF66@isoc.org>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 00:22:46 -0000

(apologies for splattercasting)

Dear Colleagues,

The Internet Society has announced that it is inviting applications for =
its latest Internet Society Fellowships to the IETF.  The Fellowship =
programme allows engineers from emerging and developing economies to =
attend an Internet Engineering Task Force (IETF) meeting.

As you know, the IETF is the Internet's premier standards-making body, =
responsible for the development of protocols used in IP-based networks. =
IETF participants represent an international community of network =
designers, operators, vendors, and researchers involved in the technical =
operation of the Internet and the continuing evolution of Internet =
architecture.

Fellowships will be awarded through a competitive application process. =
The Internet Society is currently accepting fellowship applications for =
the next two IETF meetings:

 * IETF 84, July 29 - August 3, 2012, Vancouver, BC, Canada

 * IETF 85, November 4-9, 2012, Atlanta, GA, USA

=20
=
http://www.internetsociety.org/what-we-do/education-and-leadership-program=
mes/next-generation-leaders/ietf-fellowships
=20

Fellowship applications for both IETF meetings are due by 23 March 2012.


I encourage you to pass on information about this program to individuals =
involved in your network that have a keen interest in the Internet =
standardisation activities of the IETF.

The Internet Society Fellowships to the IETF are sponsored by Afilias, =
Google, Microsoft, and Intel.

If you have questions, please do not hesitate to contact Steve Conte =
<conte@isoc.org>.

Kind Regards,
Steve Conte
-----
Steve Conte
Internet Leadership Programmes
The Internet Society
conte@isoc.org





From marka@isc.org  Mon Feb 27 17:05:08 2012
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 3C4E921F85BD for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level: 
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[AWL=0.154,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vVBDmPwbsAqS for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:05:07 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA5821F85B4 for <ietf@ietf.org>; Mon, 27 Feb 2012 17:05:07 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 0D0345F98B7; Tue, 28 Feb 2012 01:04:50 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:99bb:33d4:f25c:36e7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 19384216C31; Tue, 28 Feb 2012 01:04:45 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id AE92C1DDCEDA; Tue, 28 Feb 2012 12:04:40 +1100 (EST)
To: Hector <sant9442@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <0B48FF80-2155-4F06-B613-7EAE104D5CBE@vpnc.org> <3503462.Q2aCvq3QGU@scott-latitude-e6320> <20120227214821.79A4D1DDACC9@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E0039280498B3@exch-mbx901.corp.cloudmark.com> <4F4C050C.8020401@gmail.com> <20120227230457.5EF111DDBE1F@drugs.dv.isc.org> <4F4C1106.4020806@gmail.com>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Mon, 27 Feb 2012 18:25:58 CDT." <4F4C1106.4020806@gmail.com>
Date: Tue, 28 Feb 2012 12:04:40 +1100
Message-Id: <20120228010440.AE92C1DDCEDA@drugs.dv.isc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:05:08 -0000

In message <4F4C1106.4020806@gmail.com>, Hector writes:
> Mark Andrews wrote:
> > Many web interfaces are little more than line text editors with a pulldown
> > list for the type.  Very few are more than that.  The data just gets passed,
> > as text, to a backend which adds it to a database / zone.  Lots of those
> > backends already support the new type.  The only change that needs to be
> > made is to add a type to the pull down list.
> > 
> 
> In one support case, gigantic isp to remain nameless, the addition of 
> new TXT-based protocol support now caused "wildcard conflicts" between 
> SPF and DKIM.
> 
> Customer to us: What records to I add?
> 
> Us: Use our tool-generated records and contact ISP - they should have 
> a "Total DNS management" web based system, to add the generated 
> records there.
> 
> They did, there was a conflict with getting DKIM records and SPF 
> records, two different name spaces.

Which is one of the reasons DNS people argued and argued and argued
that TXT was not the right solution for DKIM.  The IETF can still
correct this by adding a DKIM type and deprecating the prefix. :-)

> Us: Constant ISP, they should allow you to separate SPF and DKIM records.
> 
> ISP to Customer:  Nothing wrong, its all fine.  Just add it under TXT.
> 
> Customer to US:  Is this your BUG?
> 
> Us: It has to be the ISP, lets check it out - Remote support.
> 
> There was no specific way to separate TXT records, it was all lump 
> under one input.
> 
> US: Contact ISP, tell them what we told you.
> 
> Customer to US:  VOILA, fixed, ISP fixed it with a special prefix you 
> add to the record.

No.  You just need a interface that lets you specify the domain name of
the record you are adding. 
 
> Basically, what they did was independent of the pull down, the 
> editable field allowed you to add the subdomain prefix.
> 
> Whatever! :)
> 
> Agree, it isn't so far to update the frontend, but we can't always 
> blame the ISP when the specification isn't all clear. If the 
> impression is that TXT is good enough, then the expense to do code 
> change is less justified.
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From johnl@iecc.com  Mon Feb 27 17:47:16 2012
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 2D88E21F851D for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.482
X-Spam-Level: 
X-Spam-Status: No, score=-110.482 tagged_above=-999 required=5 tests=[AWL=0.717, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YyOTtcy7-RNo for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:47:15 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6E35E21F8517 for <ietf@ietf.org>; Mon, 27 Feb 2012 17:47:15 -0800 (PST)
Received: (qmail 42915 invoked from network); 28 Feb 2012 01:47:09 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 Feb 2012 01:47:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f4c321d.xn--hew.k1202; i=johnl@user.iecc.com; bh=bDOdt8Y9U/AHas+5Q6gNXj/L+gow14O6eGZ5z9ucNYU=; b=GBWG3i+cX4wzdmVgd1uv9wbkZN1nqX3axJrJfc0JnFGtxkwso9FZkV4YpP/aSeoDzRr4MKzeUvGo4oqXUhrsaqt0LbZtdgcPIiIx9UOT6JRkn5SLhj97sfcQ9ZqdXipLd4m9U2q4NbMn/NpnlNkE3Xpep+Slo/ApsIwi6N9wZ3w=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 28 Feb 2012 01:46:47 -0000
Message-ID: <20120228014647.2144.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:47:16 -0000

>In an ideal world I'd also like to see us move in the direction that
>RFC5507 promotes, but it seems we still aren't there yet.

I'm still hoping to get some more feedback on

draft-levine-dnsextlang-02.txt

R's,
John

From johnl@iecc.com  Mon Feb 27 17:50:04 2012
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 D4BCB21E8026 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.501
X-Spam-Level: 
X-Spam-Status: No, score=-110.501 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SpoE0EQo53AY for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:50:04 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 2616521E800C for <ietf@ietf.org>; Mon, 27 Feb 2012 17:50:03 -0800 (PST)
Received: (qmail 44315 invoked from network); 28 Feb 2012 01:50:03 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 Feb 2012 01:50:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f4c32cb.xn--i8sz2z.k1202; i=johnl@user.iecc.com; bh=XNfBY6GPDWIUvYFVAIyn5gtzOyFdcIJ7lm8UVBXs/zE=; b=qdxLk/wW0T4okOnFuwMmOnvpQHsGGysOv/1fvn+fp2ur727v9F5KCRbL4sQTm5h32R9YEs4w5tq3Ck20aFSRZYOCThjjEbWf6wSNieGC6ZBKyJ0uFSTrXIkir4ZBrqxgLJN/m2eUZiWL+CMkhBYiHO30OADgW51IRqWS19juJPo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 28 Feb 2012 01:49:41 -0000
Message-ID: <20120228014941.2168.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <20120228010440.AE92C1DDCEDA@drugs.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:50:04 -0000

>> In one support case, gigantic isp to remain nameless, the addition of 
>> new TXT-based protocol support now caused "wildcard conflicts" between 
>> SPF and DKIM.

Since DKIM uses prefixed names, this is not a problem on any actual
deployment of DKIM.  

It's true, you can't do _domainkey.*.example.com, but this is a well
known limitation on prefixed names at least since they were invented
for SRV records.

R's,
John

From johnl@iecc.com  Mon Feb 27 17:56:29 2012
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 A900D21E8029 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:56:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.519
X-Spam-Level: 
X-Spam-Status: No, score=-110.519 tagged_above=-999 required=5 tests=[AWL=0.680, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuOicArYryEC for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 17:56:29 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C529221E8026 for <ietf@ietf.org>; Mon, 27 Feb 2012 17:56:28 -0800 (PST)
Received: (qmail 46784 invoked from network); 28 Feb 2012 01:56:28 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 Feb 2012 01:56:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f4c344c.xn--30v786c.k1202; i=johnl@user.iecc.com; bh=IypAHt2U3TTID5w9pvuga7BeVFgO7gMF9OlOY1u6dRE=; b=Q98ypyGOm+1vwuxeOF8BstzQOh/N1UA151Gg/zujewzWDlS1LMFLn6zXGd6ZKMPtgm+rw/bChS1nr/BxsIjVDrSkH3vARRx8B6tq+qF2wg3M6YgZIDs4vohdMNCaBHn4hcx4UAO/7FKSsEyNuZudYqqV+4IV0lnPz2Y923brTXY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 28 Feb 2012 01:56:06 -0000
Message-ID: <20120228015606.2227.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <4F4C0331.3060700@dougbarton.us>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 01:56:29 -0000

>So, what we need to do is learn from that experience. 8.5 years later
>support for 3597 is a very reasonable thing to expect, and with AAAA,
>DNSSEC, etc. we're well past the era where hidebound DNS software is an
>acceptable operational model.

There are indeed very few current DNS servers that can't be persuaded
to serve up arbitrary record types, but as we've been saying over and
over, that's not the problem.

The problem is provisioning software.  We weenies can stuff anything
into our DNS servers we want, because we use vi and emacs and (in my
case) custom perl scripts.  For the other 99.5% of the world, what
they can put in their DNS zones is limited to whatever the web
provisioning software at their registrar or ISP or web host supports,
and I challenge you to find any that supports SPF records.

R's,
John



From paul.hoffman@vpnc.org  Mon Feb 27 18:13:45 2012
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 5A5B321F8498 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 18:13:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.673
X-Spam-Level: 
X-Spam-Status: No, score=-102.673 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bhP9BSzgqEL9 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 18:13:44 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id DC72A21F8497 for <ietf@ietf.org>; Mon, 27 Feb 2012 18:13:44 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q1S2DdeL059273 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 27 Feb 2012 19:13:41 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20120228015606.2227.qmail@joyce.lan>
Date: Mon, 27 Feb 2012 18:13:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <91EA8941-7CD8-4EC4-9D0C-19BC1A896EAC@vpnc.org>
References: <20120228015606.2227.qmail@joyce.lan>
To: "John Levine" <johnl@iecc.com>
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:13:45 -0000

On Feb 27, 2012, at 5:56 PM, John Levine wrote:

> The problem is provisioning software.  We weenies can stuff anything
> into our DNS servers we want, because we use vi and emacs and (in my
> case) custom perl scripts.  For the other 99.5% of the world, what
> they can put in their DNS zones is limited to whatever the web
> provisioning software at their registrar or ISP or web host supports,
> and I challenge you to find any that supports SPF records.


Er, so? If the tool to bundle up the needed bits for SPF-as-text and =
SPF-as-binary are similarly trivial, why should we care if people who =
want to use a feature of the Internet can't persuade their provider to =
make a trivial change.

Soon, y'all will be saying we should give up on DNSSEC because so few =
registrars support it in their web UIs.

--Paul Hoffman


From johnl@iecc.com  Mon Feb 27 18:46:45 2012
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 6B04121E8041 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 18:46:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.537
X-Spam-Level: 
X-Spam-Status: No, score=-110.537 tagged_above=-999 required=5 tests=[AWL=0.662, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjvbUd-JXNOt for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 18:46:44 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 99A2021E802B for <ietf@ietf.org>; Mon, 27 Feb 2012 18:46:44 -0800 (PST)
Received: (qmail 64876 invoked from network); 28 Feb 2012 02:46:43 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 28 Feb 2012 02:46:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f4c4013.xn--btvx9d.k1202; i=johnl@user.iecc.com; bh=m8GduzmvfakNAYspKdFnRX80aDs1kv4e0KtTQVDQvsU=; b=MmmfK0K9dg/1NISFywtfHc3en9iMFcALqCJhCtVK8IqUjLKpTjfLMZGEMGXWhaNUS5CN5ye63XXIJ0gu8sl9qoXxAETABJ7B4g0XEQ0pN4WNg9cyd0ZCaBTIEs+Fa6p+59pW6kJxmn3RPxwN68VtvEoj0YU67F1s5Ing5qA2HwI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 28 Feb 2012 02:46:20 -0000
Message-ID: <20120228024620.2400.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <91EA8941-7CD8-4EC4-9D0C-19BC1A896EAC@vpnc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:46:45 -0000

>Er, so? If the tool to bundle up the needed bits for SPF-as-text and
>SPF-as-binary are similarly trivial, why should we care if people who
>want to use a feature of the Internet can't persuade their provider to
>make a trivial change.

Because there's no point in checking records that don't exist.  RFC
4408 has been out for six years, and people who run large mail systems
report that the number of type 99 records is basically zero.  To
several significant digits, all type 99 queries are wasted traffic.

>Soon, y'all will be saying we should give up on DNSSEC because so few
>registrars support it in their web UIs.

Registrars will because they have to. The registries (or maybe ICANN)
will beat them up.

I'm looking forward to a couple of decades of the DNS crowd
complaining that there's no DNSSEC at zone cuts below TLDs, while
remaining impervious to the concept that it's because upgrading
provisioning to handle them is even harder than upgrades for simple
records like type 99.

R's,
John

From sant9442@gmail.com  Mon Feb 27 18:58:22 2012
Return-Path: <sant9442@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 9EC1D21E8043 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 18:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=-0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qkz95pXyNFYa for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2012 18:58:22 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE5521E8042 for <ietf@ietf.org>; Mon, 27 Feb 2012 18:58:22 -0800 (PST)
Received: by ggnp2 with SMTP id p2so742811ggn.31 for <ietf@ietf.org>; Mon, 27 Feb 2012 18:58:21 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.170.193 as permitted sender) client-ip=10.236.170.193; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.170.193 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.170.193]) by 10.236.170.193 with SMTP id p41mr25498583yhl.15.1330397901892 (num_hops = 1); Mon, 27 Feb 2012 18:58:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vSNCR/IvP0rC7Hf00byOY9KcjTbB94mErTcczvWpA4k=; b=XFSA006xIV/IRj6wwSRw5blOrZHzwaOaxdsJSw8q7PawrSDjbYvqSenPlbykQeAJzf 0WCnKLnlZhCypaSP4flyQb8sHCi0lv/iiruVotJ9Wpg2PlUnhUh1exMYVMSeafvFa39q yalzroe6+64v23yZc9fQ5Q2iTv83Yes8Vir9E=
Received: by 10.236.170.193 with SMTP id p41mr19170739yhl.15.1330397901800; Mon, 27 Feb 2012 18:58:21 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id g21sm21843601ani.13.2012.02.27.18.58.20 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 27 Feb 2012 18:58:21 -0800 (PST)
Message-ID: <4F4C42BE.7010806@gmail.com>
Date: Mon, 27 Feb 2012 21:58:06 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228024620.2400.qmail@joyce.lan>
In-Reply-To: <20120228024620.2400.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 02:58:22 -0000

John Levine wrote:
>> Er, so? If the tool to bundle up the needed bits for SPF-as-text and
>> SPF-as-binary are similarly trivial, why should we care if people who
>> want to use a feature of the Internet can't persuade their provider to
>> make a trivial change.
> 
> Because there's no point in checking records that don't exist.  RFC
> 4408 has been out for six years, and people who run large mail systems
> report that the number of type 99 records is basically zero.  To
> several significant digits, all type 99 queries are wasted traffic.

However, that was the original migration path expected which has 
finally materialized - Getting clients to support both record types 99 
and TXT first before recommending type 99 only publishing can be 
considered.  It would not have been feasible nor reasonable to 
recommend type 99 only publishing in 4408.

To the surprise of many, clients are doing the expected behavior of 
dual type queries - all expected to come with a short term waste.

Now its time for the BIS update to declare, pardon the pun, "Route 99" 
is now paved and safe to drive (begin publishing type 99 records).

--
HLS



From vesely@tana.it  Tue Feb 28 04:33:08 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D4A21F85C0 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 04:33:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.647
X-Spam-Level: 
X-Spam-Status: No, score=-4.647 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6pIgU12RGjv for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 04:33:07 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id BD15E21F8566 for <ietf@ietf.org>; Tue, 28 Feb 2012 04:33:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330432379; bh=9hK8V8o9uuu22co3C0o8n7A0qv/cUJi/JIW5L2y/br4=; l=1074; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=WChBVDQQ+YqfwcQAym6QXlUBob8jZbZTv+x/3YFssn/sFV6vQXu+/h+k2uH/Xxq5p tO2Pvs37XIBBnT5hlbwAkZy3yhjWn7P0Ag0xlP6nrZ7JkhpB5w6ZyHYYhVIHweCaTb TLS82EYnaRu5OYy7EZ5ObRgeQ9colbH0J445x6Xg=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 28 Feb 2012 13:32:59 +0100 id 00000000005DC045.000000004F4CC97B.00007984
Message-ID: <4F4CC97A.20002@tana.it>
Date: Tue, 28 Feb 2012 13:32:58 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>	<1473887.qQLEpWRMlg@scott-latitude-e6320>	<20120224175748.GN48576@mail.yitter.info>	<1370954.fA4nZvz4lC@scott-latitude-e6320>	<4F4B5E74.7070403@tana.it> <4F4BBE5D.20905@gmail.com> <C75AFFC5-1E06-41FF-97B5-22CB67AAC33D@frobbit.se> <4F4BE558.6090908@gmail.com> <1012B983-D6EB-4148-ADF4-D05874A7C4D1@frobbit.se>
In-Reply-To: <1012B983-D6EB-4148-ADF4-D05874A7C4D1@frobbit.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 12:33:08 -0000

On 27/Feb/12 21:30, Patrik FÃ¤ltstrÃ¶m wrote:
>
> Yes, a pain. But...we just must be able to get new RRTypes
> deployed. And not give up.

I agree it is a praiseworthy task to pursue the diffusion of unknown
RRTypes.  However, it cannot be piggybacked on client protocols, that
have their own difficulties and version life cycles.  When it will be
possible to deploy unknown types, protocols that nowadays reuse TXT
will convert to their own type, taking advantage of binary formats and
unambiguous querying.

There have to be transition periods, during which TXT records are
accepted for backward compatibility.  However, when a new protocol's
version implies using a different record type, backward compatibility
should result from supporting the old version.  To allow both TXT and
a specific RRType --especially one that uses multiple bytes to encode
a 4-bit version number-- to serve exactly the same protocol versions
is an /unfounded excuse/ that does nothing to encourage the diffusion
of that RRType.  For SPF, it just doubled the number of queries.

From hallam@gmail.com  Tue Feb 28 07:17:29 2012
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 6E45021F86C8 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 07:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.415
X-Spam-Level: 
X-Spam-Status: No, score=-3.415 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhl+22BwEerW for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 07:17:28 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 89F5B21F86B9 for <ietf@ietf.org>; Tue, 28 Feb 2012 07:17:28 -0800 (PST)
Received: by ghbg16 with SMTP id g16so2885537ghb.31 for <ietf@ietf.org>; Tue, 28 Feb 2012 07:17:28 -0800 (PST)
Received-SPF: pass (google.com: domain of hallam@gmail.com designates 10.60.12.231 as permitted sender) client-ip=10.60.12.231; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of hallam@gmail.com designates 10.60.12.231 as permitted sender) smtp.mail=hallam@gmail.com; dkim=pass header.i=hallam@gmail.com
Received: from mr.google.com ([10.60.12.231]) by 10.60.12.231 with SMTP id b7mr6947344oec.38.1330442248134 (num_hops = 1); Tue, 28 Feb 2012 07:17:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=UeKGdaJLnitoXxrkKtU7Q3gg2+lz8VYJ7WzN/v1nEDs=; b=CaaZKE5T/Pw6HIx5k0GY4nOr7+6UOjJeDDDu4vGpQVTDq0iEatzfFpjwTyVHl1twWq HB5IiS+qNIhYvgdXV1LplsXiEOE9VpDCHxQUPZ6Jl0XRqPHcw4q2glL9WkmAQqc/ybJm vl8j4pHkljvNlulWydX+IKOcvU6N0sg/nDTl8=
MIME-Version: 1.0
Received: by 10.60.12.231 with SMTP id b7mr6168495oec.38.1330442248013; Tue, 28 Feb 2012 07:17:28 -0800 (PST)
Received: by 10.182.170.9 with HTTP; Tue, 28 Feb 2012 07:17:27 -0800 (PST)
In-Reply-To: <9FE913F2-E516-468C-AFFB-DE0BB3C4E9D8@amsl.com>
References: <9FE913F2-E516-468C-AFFB-DE0BB3C4E9D8@amsl.com>
Date: Tue, 28 Feb 2012 07:17:27 -0800
Message-ID: <CAMm+Lwg_zAOHO+U-f927qqdu4Yh9CPgbucOsQHCgT1Rhkr4-6g@mail.gmail.com>
Subject: Re: Reminder: T-shirt Design Contest for IETF 83
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 15:17:29 -0000

It may be intentional or not. But one of the designs has the eiffel
tower centered on the wearer's crotch area. This makes for an
interesting visual effect when worn

A previous conference at which I attended (1st Web conference) had a
similar unfortunate juxtaposition with the Jet D'Eau in Lake Geneva.


On Tue, Feb 14, 2012 at 12:38 PM, Alexa Morris <amorris@amsl.com> wrote:
> This is a reminder that the IAOC is conducting a T-Shirt Design Contest t=
o develop a unique t-shirt for the Paris meeting. You have until this Frida=
y, Feb 17 to submit your design for consideration. We've received two submi=
ssions so far and you can see them here: http://www.ietf.org/meeting/83/t-s=
hirt-design-contest-submissions.html.
>
> If you have design skills, or can strongarm someone else who does, please=
 view this as an opportunity to show your support for the IETF. The Secreta=
riat will take care of producing the shirts once the winning design is sele=
cted, and the purchase price (approximately $25 USD) will go to support the=
 IETF. =A0Whoever submits the winning design will receive a free t-shirt.
>
> Please send your design to tshirtcontest@ietf.org. Designs should be deli=
vered as EPS or Adobe Illustrator files. A t-shirt template is available fo=
r download here: ietf.org/meeting/83/t-shirt-contest-template.eps. Your sub=
mission should include t-shirt color, and the design for both front and bac=
k of the shirt. Please note: designs should include the IETF logo, but cann=
ot include any company logos. Like an Internet-Draft, a t-shirt design subm=
ission is authored by individuals.
>
> Regards,
> Alexa
>
> ----------
> Alexa Morris / Executive Director / IETF
> 48377 Fremont Blvd., Suite 117, Fremont, CA =A094538
> Phone: +1.510.492.4089 / Fax: +1.510.492.4001
> Email: amorris@amsl.com
>
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce



--=20
Website: http://hallambaker.com/

From john@jlc.net  Tue Feb 28 08:42:22 2012
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 E66F221F86D7 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 08:42:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.428
X-Spam-Level: 
X-Spam-Status: No, score=-106.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJcIAfs+B4s9 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 08:42:22 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6F94E21F8601 for <ietf@ietf.org>; Tue, 28 Feb 2012 08:42:22 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 4C9B333C88; Tue, 28 Feb 2012 11:42:22 -0500 (EST)
Date: Tue, 28 Feb 2012 11:42:22 -0500
From: John Leslie <john@jlc.net>
To: John Levine <johnl@iecc.com>
Subject: Re: DNS RRTYPEs, the difficulty with
Message-ID: <20120228164222.GG42092@verdi>
References: <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com> <20120228014647.2144.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120228014647.2144.qmail@joyce.lan>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 16:42:23 -0000

John Levine <johnl@iecc.com> wrote:
> 
> I'm still hoping to get some more feedback on
> 
> draft-levine-dnsextlang-02.txt

   "We believe in rough consensus and running code."

   I'm happy to contribute to the "rough consensus" once I see running
code, perpaps for bind and perl-script registrar interfaces.

--
John Leslie <john@jlc.net>

From bschlies@cisco.com  Tue Feb 28 11:45:16 2012
Return-Path: <bschlies@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 0FAEC21F8631 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 11:45:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11114i3dDIOC for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 11:45:15 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 596D921F862F for <ietf@ietf.org>; Tue, 28 Feb 2012 11:45:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=bschlies@cisco.com; l=848; q=dns/txt; s=iport; t=1330458315; x=1331667915; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=NwTB/3OB547T8e6hO+VSNDwGSF18+V3PW3M41kQQNYk=; b=H6rx/3cvToTJNEUBNvpqfwJvO/ExCkD2XUO0+voowWSjQ2C1o3KkBeqC cwVQSC3t4L1VRVEfiBnnHspx1gAdU5Ln8eh7pHfzgh3/WuF5psBVXBzUA EosbFC9ktLcO8RE4EsWw4heNvnim0iT3GDIgWrSLGrJRxOzCYgyoTLexM g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOItTU+rRDoI/2dsb2JhbABDFrNQgQeBdwEBAQMBEgEnPwULC0ZXBhwWA4dhBAyhDQGXJI0fAg0CCAIKAQYLAgYHDwYBCgMDAwKFAg8JBwMBAwYLCg4HBAYagkljBIhPjHCTEQ
X-IronPort-AV: E=Sophos;i="4.73,497,1325462400"; d="scan'208";a="33017999"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 28 Feb 2012 19:45:15 +0000
Received: from dhcp-171-71-146-239.cisco.com (dhcp-171-71-146-239.cisco.com [171.71.146.239]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q1SJjF0c017591; Tue, 28 Feb 2012 19:45:15 GMT
Subject: Re: Reminder: T-shirt Design Contest for IETF 83
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Benson Schliesser <bschlies@cisco.com>
In-Reply-To: <CAMm+Lwg_zAOHO+U-f927qqdu4Yh9CPgbucOsQHCgT1Rhkr4-6g@mail.gmail.com>
Date: Tue, 28 Feb 2012 11:45:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E95A5F06-C7C1-4EA2-A91B-902B06732CAD@cisco.com>
References: <9FE913F2-E516-468C-AFFB-DE0BB3C4E9D8@amsl.com> <CAMm+Lwg_zAOHO+U-f927qqdu4Yh9CPgbucOsQHCgT1Rhkr4-6g@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 19:45:16 -0000

On Feb 28, 2012, at 7:17 AM, Phillip Hallam-Baker wrote:

> It may be intentional or not. But one of the designs has the eiffel
> tower centered on the wearer's crotch area. This makes for an
> interesting visual effect when worn

I suspect you might be referring to my submission of the "Eiffel network =
diagram" t-shirt design. =
(http://www.queuefull.net/~bensons/2012/02/28/eiffel-network/)

It was certainly not intentional. Funny that I hadn't noticed it before, =
but now that you've pointed it out, it's obvious every time I look at =
the picture...

Fortunately, another design has won the contest, so this won't be an =
issue. See http://www.ietf.org/meeting/83/t-shirt-design-contest.html.

And congratulations to the winning design! It's very well done and =
should make an attractive t-shirt.

Cheers,
-Benson


From sant9442@gmail.com  Tue Feb 28 14:07:12 2012
Return-Path: <sant9442@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 2EE2621E8018 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.193
X-Spam-Level: 
X-Spam-Status: No, score=-3.193 tagged_above=-999 required=5 tests=[AWL=0.406,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AH1R1xBoyfMq for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:07:11 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 716DC21E802D for <ietf@ietf.org>; Tue, 28 Feb 2012 14:07:11 -0800 (PST)
Received: by ghbg16 with SMTP id g16so3186559ghb.31 for <ietf@ietf.org>; Tue, 28 Feb 2012 14:07:08 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.92.228 as permitted sender) client-ip=10.236.92.228; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.92.228 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.92.228]) by 10.236.92.228 with SMTP id j64mr6667291yhf.31.1330466828969 (num_hops = 1); Tue, 28 Feb 2012 14:07:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=DHkRlaeHTUG/xc3f9vlLJJ/JSepZuE6He9BE1xLU4MU=; b=LDZURh819i9P1jvRNjLWI1PyJpdmqxxnPxxReDSgLk9W3VGlL+yIu3Y6oNVLOgvGwG qBMYkmhvLEKhivjhfuxIz1CjCMlMLo5WHttdjO45UM+H/dO4ML6Cok4eStDjb0hFjO/R uJyZjm+iFziMr7mxR9Fb/bDo5N0QGUL0+2DZE=
Received: by 10.236.92.228 with SMTP id j64mr5238011yhf.31.1330466828913; Tue, 28 Feb 2012 14:07:08 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id o11sm31013501anl.11.2012.02.28.14.07.05 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Feb 2012 14:07:07 -0800 (PST)
Message-ID: <4F4D5007.9080802@gmail.com>
Date: Tue, 28 Feb 2012 17:07:03 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <9452079D1A51524AA5749AD23E00392804928A@exch-mbx901.corp.cloudmark.com>	<20120228014647.2144.qmail@joyce.lan> <20120228164222.GG42092@verdi>
In-Reply-To: <20120228164222.GG42092@verdi>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:07:12 -0000

John Leslie wrote:
> John Levine <johnl@iecc.com> wrote:
>> I'm still hoping to get some more feedback on
>>
>> draft-levine-dnsextlang-02.txt
> 
>    "We believe in rough consensus and running code."
>
>    I'm happy to contribute to the "rough consensus" once I see running
> code, perpaps for bind and perl-script registrar interfaces.

How people do it, is how people learn.  :)

--
HLS

From dougb@dougbarton.us  Tue Feb 28 14:23:39 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C9121F8493 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.686
X-Spam-Level: 
X-Spam-Status: No, score=-3.686 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIB3bRz1dJOU for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:23:39 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id E158E21F8494 for <ietf@ietf.org>; Tue, 28 Feb 2012 14:23:38 -0800 (PST)
Received: (qmail 29394 invoked by uid 399); 28 Feb 2012 22:23:32 -0000
Received: from unknown (HELO ?172.17.198.245?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 28 Feb 2012 22:23:32 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F4D53E2.5080803@dougbarton.us>
Date: Tue, 28 Feb 2012 14:23:30 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan>
In-Reply-To: <20120228015606.2227.qmail@joyce.lan>
X-Enigmail-Version: 1.3.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:23:39 -0000

On 2/27/2012 5:56 PM, John Levine wrote:

> The problem is provisioning software.  We weenies can stuff anything
> into our DNS servers we want, because we use vi and emacs and (in my
> case) custom perl scripts.  For the other 99.5% of the world, what
> they can put in their DNS zones is limited to whatever the web
> provisioning software at their registrar or ISP or web host supports,
> and I challenge you to find any that supports SPF records.

I have been both the author and a consumer of the types of interfaces
that you're describing, and I had a very peripheral role in the work to
evangelize interface support for new TLDs, IPv6, and DNSSEC; so I'm
familiar with the issue. My experience with these issues tells me that
when there is demand to support a new RRtype, it will be supported.

So, once again, we need to learn from the mistakes that were made with
SPF. Here is how life goes in most busy enterprise environments:

Intelligent sysadmin: We need to deploy SPF
Boss: How does it work?
I: Well, eventually it will have its own DNS RR, but for now it works
with TXT records
B: Ok, put those TXT records in
<time passes>
I: It's now possible to use SPF RRs for SPF, so I need to make some
changes, do some testing, etc.
B: Are the TXT records working now?
I: Well yes, but ...
B: We have more important priorities that I need you to spend your time
on, leave the thing that's working alone.

Or, put more simply, your conclusion seems to be that we can never add
new RRs. Given that adding new RRs is crucial to the growth of the
Internet, I reject that conclusion completely.


Doug

-- 
    If you're never wrong, you're not trying hard enough

From scott@kitterman.com  Tue Feb 28 14:33:31 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B0E21F8525 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lByKK88I5pE7 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:33:24 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 39DAE21F8522 for <ietf@ietf.org>; Tue, 28 Feb 2012 14:33:24 -0800 (PST)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 5FAB3D04083; Tue, 28 Feb 2012 16:33:23 -0600 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330468403; bh=eoRPhhJ3SHe4mhNLgpMytCtk3PePQZzEq99c+PoTh3Y=; h=References:In-Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Subject:From:Date:To:Message-ID; b=KxpeNUuAWug3CWMuj3MaFRRyhSUH0R/anMP7eqH032bN9YVBmWNDBNccAIC5sjNoB mEGcBXngU3UcUaPsrpSbGJ8aWFehBiqJwgAPV2MG1rn/l9opvNzVPdDQXeoE39yvcD zClqe8VbN2Cza0RwQATAVs2a3jKpFqI8IDJkeGRs=
Received: from [192.168.111.101] (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 2398FD04062;  Tue, 28 Feb 2012 16:33:23 -0600 (CST)
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us>
User-Agent: K-9 Mail for Android
In-Reply-To: <4F4D53E2.5080803@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: DNS RRTYPEs, the difficulty with
From: Scott Kitterman <scott@kitterman.com>
Date: Tue, 28 Feb 2012 17:31:36 -0500
To: ietf@ietf.org
Message-ID: <0b7e91ed-d286-4065-a91a-79032bf6aa0d@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:33:31 -0000

Doug Barton <dougb@dougbarton.us> wrote:

>On 2/27/2012 5:56 PM, John Levine wrote:
>
>> The problem is provisioning software.  We weenies can stuff anything
>> into our DNS servers we want, because we use vi and emacs and (in my
>> case) custom perl scripts.  For the other 99.5% of the world, what
>> they can put in their DNS zones is limited to whatever the web
>> provisioning software at their registrar or ISP or web host supports,
>> and I challenge you to find any that supports SPF records.
>
>I have been both the author and a consumer of the types of interfaces
>that you're describing, and I had a very peripheral role in the work to
>evangelize interface support for new TLDs, IPv6, and DNSSEC; so I'm
>familiar with the issue. My experience with these issues tells me that
>when there is demand to support a new RRtype, it will be supported.
>
>So, once again, we need to learn from the mistakes that were made with
>SPF. Here is how life goes in most busy enterprise environments:
>
>Intelligent sysadmin: We need to deploy SPF
>Boss: How does it work?
>I: Well, eventually it will have its own DNS RR, but for now it works
>with TXT records
>B: Ok, put those TXT records in
><time passes>
>I: It's now possible to use SPF RRs for SPF, so I need to make some
>changes, do some testing, etc.
>B: Are the TXT records working now?
>I: Well yes, but ...
>B: We have more important priorities that I need you to spend your time
>on, leave the thing that's working alone.
>
>Or, put more simply, your conclusion seems to be that we can never add
>new RRs. Given that adding new RRs is crucial to the growth of the
>Internet, I reject that conclusion completely.

The original SPF work was done outside the IETF, so no amount of "Hey, you can't do that" would have made a difference. Unless it's dead easy for new designs to use new RR Types it will be very difficult to get them deployed.

It's not dead easy until the more global deployment problems are solved.

Scott K


From msk@cloudmark.com  Tue Feb 28 14:35:37 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F5C21E801A for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:35:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.595
X-Spam-Level: 
X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b5+CRbm8WSEL for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:35:32 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id D15EA21E8018 for <ietf@ietf.org>; Tue, 28 Feb 2012 14:35:29 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Tue, 28 Feb 2012 14:35:29 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DNS RRTYPEs, the difficulty with
Thread-Topic: DNS RRTYPEs, the difficulty with
Thread-Index: AQHM9TzFjL91hLxbakSZS7QQB//GaZZRh2qAgAAkQwD//3w1EIAAsZWAgAA6bwCAAVbvAP//fC7w
Date: Tue, 28 Feb 2012 22:35:28 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.com>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us>
In-Reply-To: <4F4D53E2.5080803@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:35:37 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of D=
oug Barton
> Sent: Tuesday, February 28, 2012 2:24 PM
> To: John Levine
> Cc: ietf@ietf.org
> Subject: Re: DNS RRTYPEs, the difficulty with
>=20
> Intelligent sysadmin: We need to deploy SPF
> Boss: How does it work?
> I: Well, eventually it will have its own DNS RR, but for now it works
> with TXT records
> B: Ok, put those TXT records in
> <time passes>
> I: It's now possible to use SPF RRs for SPF, so I need to make some
> changes, do some testing, etc.
> B: Are the TXT records working now?
> I: Well yes, but ...
> B: We have more important priorities that I need you to spend your time
> on, leave the thing that's working alone.
>=20
> Or, put more simply, your conclusion seems to be that we can never add
> new RRs. Given that adding new RRs is crucial to the growth of the
> Internet, I reject that conclusion completely.

Your scenario illustrated the problem nicely: People started SPF with TXT r=
ecords because they were available and the road to a new RRType was seen as=
 a steep one.  Once that was even a little bit deployed, it became practica=
lly irreversible.  The same happened with DKIM, and then VBR, and now it's =
basically common practice to use naming tricks to sidestep the RRType argum=
ents.

I think the right endgame here is to make sure new RRTypes are accessible t=
o those that want to have them.  This will remove the temptation to start w=
ith TXT and, ultimately, stay there.

-MSK

From marka@isc.org  Tue Feb 28 14:59:47 2012
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 4850821F8474 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:59:47 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g+2vUNioNDHY for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 14:59:46 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 63B7A21F8472 for <ietf@ietf.org>; Tue, 28 Feb 2012 14:59:46 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 21BB35F9865; Tue, 28 Feb 2012 22:59:29 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d5c5:dd9e:52fb:735d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id B4C65216C31; Tue, 28 Feb 2012 22:59:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 23ABF1DE9EC2; Wed, 29 Feb 2012 09:59:19 +1100 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <0b7e91ed-d286-4065-a91a-79032bf6aa0d@email.android.com>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Tue, 28 Feb 2012 17:31:36 CDT." <0b7e91ed-d286-4065-a91a-79032bf6aa0d@email.android.com>
Date: Wed, 29 Feb 2012 09:59:18 +1100
Message-Id: <20120228225919.23ABF1DE9EC2@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 22:59:47 -0000

In message <0b7e91ed-d286-4065-a91a-79032bf6aa0d@email.android.com>, Scott Kitte
rman writes:
> 
> 
> Doug Barton <dougb@dougbarton.us> wrote:
> 
> >On 2/27/2012 5:56 PM, John Levine wrote:
> >
> >> The problem is provisioning software.  We weenies can stuff anything
> >> into our DNS servers we want, because we use vi and emacs and (in my
> >> case) custom perl scripts.  For the other 99.5% of the world, what
> >> they can put in their DNS zones is limited to whatever the web
> >> provisioning software at their registrar or ISP or web host supports,
> >> and I challenge you to find any that supports SPF records.
> >
> >I have been both the author and a consumer of the types of interfaces
> >that you're describing, and I had a very peripheral role in the work to
> >evangelize interface support for new TLDs, IPv6, and DNSSEC; so I'm
> >familiar with the issue. My experience with these issues tells me that
> >when there is demand to support a new RRtype, it will be supported.
> >
> >So, once again, we need to learn from the mistakes that were made with
> >SPF. Here is how life goes in most busy enterprise environments:
> >
> >Intelligent sysadmin: We need to deploy SPF
> >Boss: How does it work?
> >I: Well, eventually it will have its own DNS RR, but for now it works
> >with TXT records
> >B: Ok, put those TXT records in
> ><time passes>
> >I: It's now possible to use SPF RRs for SPF, so I need to make some
> >changes, do some testing, etc.
> >B: Are the TXT records working now?
> >I: Well yes, but ...
> >B: We have more important priorities that I need you to spend your time
> >on, leave the thing that's working alone.
> >
> >Or, put more simply, your conclusion seems to be that we can never add
> >new RRs. Given that adding new RRs is crucial to the growth of the
> >Internet, I reject that conclusion completely.
> 
> The original SPF work was done outside the IETF, so no amount of "Hey, you can
> 't do that" would have made a difference. Unless it's dead easy for new design
> s to use new RR Types it will be very difficult to get them deployed.
> 
> It's not dead easy until the more global deployment problems are solved.
> 
> Scott K

As someone who has deploy a new type globally it isn't that hard.
The hardest part as convincing the IESG that I wasn't trying to
cirumvent what was happening with DNSSEC.  I've even taken it from
a private type (65323) to a documented type (32769).

	http://tools.ietf.org/html/rfc4431

Yes, I work for a name server vendor but nothing I did couldn't
have been done by anyone else.  We get have the occassional submission
of code to support a new type.  We also get requests to add a new type.

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

From johnl@iecc.com  Tue Feb 28 15:06:41 2012
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 C844021F84B4 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.362
X-Spam-Level: 
X-Spam-Status: No, score=-102.362 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTX73Q1+jDq1 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:06:41 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CE1E621F84AA for <ietf@ietf.org>; Tue, 28 Feb 2012 15:06:40 -0800 (PST)
Received: (qmail 291 invoked from network); 28 Feb 2012 23:06:39 -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:vbr-info:user-agent:cleverness; s=122.4f4d5dff.k1202; bh=AhggdWD4nhO8fdC9kx83/swVwXowupGkwoNsbuS9nkU=; b=cIFvtV+e7kK8nc+DLecw07lfcmcgagF3ytWpDOb2Rt7sVmQKWQfcmpVOTL+F8PascHBchllR8cs4TFW0eWTUFKYu8Zte9kDVvkL7GBAsB1Wqtno3DnCZHzyKY1633wbixnBexSYjabXfmJcor16ohyqSMFRqt76tYCak8K5Vc28=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 28 Feb 2012 23:06:17 -0000
Date: 28 Feb 2012 18:06:38 -0500
Message-ID: <alpine.BSF.2.00.1202281745310.7969@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Doug Barton" <dougb@dougbarton.us>
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <4F4D53E2.5080803@dougbarton.us>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:06:41 -0000

In your little dialog, the boss was entirely reasonable -- the practical 
benefit from implementing SPF records would be zip.

> Or, put more simply, your conclusion seems to be that we can never add
> new RRs. Given that adding new RRs is crucial to the growth of the
> Internet, I reject that conclusion completely.

No, I'm saying that it would be a lot more productive to help people 
improve their provisioning systems, rather than say how stupid they are 
for not doing what we want.  Even now, there are precious few provisioning 
systems that support AAAA records, and even fewer that support DNSSEC.  I 
hacked support for AAAA into mine, but as far as I can tell, none of my 
users other than me is using them.  I added SPF records, but then took 
them out when my DNS mirror complained that he was getting strange error 
messages.

By the way, what's your opinion of draft-levine-dnsextlang-02?

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From marka@isc.org  Tue Feb 28 15:18:23 2012
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 4740D21E802A for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:18:23 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8g4lXaihrC9c for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:18:22 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 6971A21E802C for <ietf@ietf.org>; Tue, 28 Feb 2012 15:18:22 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id C60595F9865; Tue, 28 Feb 2012 23:18:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d5c5:dd9e:52fb:735d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A73AB216C33; Tue, 28 Feb 2012 23:18:06 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 52EB41DE9F99; Wed, 29 Feb 2012 10:17:53 +1100 (EST)
To: "Murray S. Kucherawy" <msk@cloudmark.com>
From: Mark Andrews <marka@isc.org>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.com>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Tue, 28 Feb 2012 22:35:28 -0000." <9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.com>
Date: Wed, 29 Feb 2012 10:17:52 +1100
Message-Id: <20120228231753.52EB41DE9F99@drugs.dv.isc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:18:23 -0000

In message <9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.co
m>, "Murray S. Kucherawy" writes:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Doug
>  Barton
> > Sent: Tuesday, February 28, 2012 2:24 PM
> > To: John Levine
> > Cc: ietf@ietf.org
> > Subject: Re: DNS RRTYPEs, the difficulty with
> > 
> > Intelligent sysadmin: We need to deploy SPF
> > Boss: How does it work?
> > I: Well, eventually it will have its own DNS RR, but for now it works
> > with TXT records
> > B: Ok, put those TXT records in
> > <time passes>
> > I: It's now possible to use SPF RRs for SPF, so I need to make some
> > changes, do some testing, etc.
> > B: Are the TXT records working now?
> > I: Well yes, but ...
> > B: We have more important priorities that I need you to spend your time
> > on, leave the thing that's working alone.
> > 
> > Or, put more simply, your conclusion seems to be that we can never add
> > new RRs. Given that adding new RRs is crucial to the growth of the
> > Internet, I reject that conclusion completely.
> 
> Your scenario illustrated the problem nicely: People started SPF with TXT reco
> rds because they were available and the road to a new RRType was seen as a ste
> ep one.  Once that was even a little bit deployed, it became practically irrev
> ersible.  The same happened with DKIM, and then VBR, and now it's basically co
> mmon practice to use naming tricks to sidestep the RRType arguments.
> 
> I think the right endgame here is to make sure new RRTypes are accessible to t
> hose that want to have them.  This will remove the temptation to start with TX
> T and, ultimately, stay there.

They are there.  They were there when SPF was being developed.  They
were there when DKIM was being developed.  It's just the neigh
sayers won out.

Libresolv has supported unknown types for 25 years.  Other C libraries
support them.  dnspython supports them.  dnsjava supports them.  It
really isn't hard to get a length tagged blob of data back to the
application.

Authoritative nameservers support them.  Recursive nameservers
support them and always have modulo bugs.

If your DNS hosting company doesn't support them find another one
or complain to them.  You are paying them to host your DNS services
and this is a basic part of the job.

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

From ben@nostrum.com  Tue Feb 28 15:34:24 2012
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 8C78F21F8472; Tue, 28 Feb 2012 15:34:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.255
X-Spam-Level: 
X-Spam-Status: No, score=-102.255 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_92=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNiCanWg9zKy; Tue, 28 Feb 2012 15:34:24 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF98121F8470; Tue, 28 Feb 2012 15:34:23 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q1SNYMB3099708 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Feb 2012 17:34:22 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03
Date: Tue, 28 Feb 2012 17:34:27 -0600
Message-Id: <03557735-170E-422A-B507-45A07DEC22AE@nostrum.com>
To: draft-ietf-mext-mip6-tls.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:34:24 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-mext-mip6-tls-03
Reviewer: Ben Campbell
Review Date: 2012-02-28
IETF LC End Date: 2012-02-29
IESG Telechat date: 2012-03-01

Note: Since the Telechat review deadline is a day before the end of the =
IETF last call, this review serves both as a Telechat review and an IETF =
Last Call review.

Summary: This draft is basically ready for publication as an =
experimental RFC. There are some clarification issues that might should =
be addressed prior to publication.

Major issues:

None


Minor issues:

-- general:=20

The draft seems to be missing information on how to match TLS =
certificates to identities for HAC authentication.

-- section 1, paragraph 1, last sentence: "Client implementation =
experience has shown that the use of IKE(v2)/IPsec with Mobile IPv6 is =
fairly complex."

It might be worth elaborating on why this is true. Could this be solved =
with a cleaner software architecture rather than a protocol change?

-- section 5.4:  "The actual domain name used in queries is up to the =
deployment to decide and out of scope of this specification."
=20
This seems under specified for SRV

-- 5.7.4:

Are more than one DNS server allowed for each protocol?

-- 5.8:

I find this section confusing,as the first and second paragraphs seem to =
make contradictory statements about the authentication, particularly =
about the use of PSK. I think you are talking about authentication of =
the HAC in the TLS handshake vs an higher level authentication of the MN =
using PSK or EAP. I think this could use some clarification, as both =
paragraphs talks about authentication between the MN and HAC without =
mentioning direction.

Note that this is more clear in the security considerations section, but =
it would help for it to be more clear here.

-- 5.9, 2nd to last paragraph:

How do the first and last sentences relate? It seems to say set it to =
"1", except for this case in which you set it to "1".

-- 8.1:

Is this registry only for TLS based MIPv6? If so, does it need to be =
explicitly constrained to not used for MIPv6 in general?




Nits/editorial comments:

-- section 4.1:=20

A picture showing the element and key relationships could be helpful =
here.

-- section 4.3, third paragraph:

Please expand BA on first mention

--section 4.3, "Security association validity times", : "hours or weeks"

Hours _to_ weeks?

-- section 4.3, "selected cyphersuite": " The selected algorithms SHOULD =
be one of the mutually supported ciphersuites"

How could it be otherwise? (i.e. why the SHOULD, and is this really =
normative vs descriptive?)

-- section 4.4: "Home Agent IP Address" : "Concerns both IPv6 and IPv4 =
home agent addresses."

Dual stack only?  (same applies to "Home Address" section)

-- section 5.1, second paragraph: "All data inside the Content portion =
of the message container MUST be encoded using octets."

I suspect I'm missing a subtlety here--but how else could you do it? Is =
this intended to imply a byte-field, or to imply no additional encoding =
is used?

-- section 5.2: "=46rom now on, we use TypeValue header (TV-header) term =
to refer request-response message content HTTP-like headers."
=20
Maybe that should be moved to the terminology section?

-- section 5.3, 2nd paragraph: "The MN is also the peer that always =
sends only request messages and the HAC only sends response messages."

I'm having trouble parsing. Is their a spurious "always"?

-- section 5.5 : "same to that used by HTTP"

same _as_?

-- section 5.5.5

s/till/until

-- 5.5.8, 1st sentence:

Sentence fragment. Missing words?

-- 5.9, first paragraph:

Sentence fragment.

-- 5.9, 2nd to last paragraph:

s/"In case the"/"In the case that the"

-- 9:

A general discussion of threats would be helpful. Some aspects are =
scattered in the subsections, but a summary in one place would be nice.

-- 9.2:=20

It's not clear to me if the text in the "Dictionary Attack" section is =
actually related to dictionary attacks.


-- 6.1:

A picture of the general packet format would be nice. You've got them =
later for specific packet types, but no "general" picture.

--6.2:=20

Section seems mostly redundant to 6.1

-- 6.3:

Please expand HoTI on first use.

-- 7:

Please expand CoTI/CoT on first use

-- 8.3:

I'm not sure I understand the mnemonic relevance of "HALTSEC"






From scott@kitterman.com  Tue Feb 28 15:38:55 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE57921E8046 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:38:55 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wjIhStbj4Aa4 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:38:47 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8050421E8062 for <ietf@ietf.org>; Tue, 28 Feb 2012 15:38:47 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id F01FA20E40E0; Tue, 28 Feb 2012 18:38:46 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330472327; bh=9QXGMp8vD9LxM2oZF2mRB/Z1NjKfwzqwfrsijmZwTQ4=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=J9Yk8w1eeJWXmguANT606NKAeR4memkiOFwQ6iLuYkng0VDsDqzBHsHwBvY6/xFzG FxAGu6bUM0V654Sde6oVoVUwcqNkfMaY8K7SZQcknQPi2U2gfjEFstLQcdVYiw8qDZ q5u8phPikcnEUVXIKgkg9I+9O6IIQuQZWjSnjRZA=
Received: from scott-latitude-e6320.localnet (140.239.105.162.ptr.us.xo.net [140.239.105.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id CCE5120E4099;  Tue, 28 Feb 2012 18:38:46 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Tue, 28 Feb 2012 18:38:45 -0500
Message-ID: <2522391.bzDDO1QXaX@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <20120228231753.52EB41DE9F99@drugs.dv.isc.org>
References: <20120228015606.2227.qmail@joyce.lan> <9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.com> <20120228231753.52EB41DE9F99@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:38:55 -0000

On Wednesday, February 29, 2012 10:17:52 AM Mark Andrews wrote:
> In message
> <9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.co
> m>, "Murray S. Kucherawy" writes:
> > > -----Original Message-----
> > > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> > > Of Doug>  
> >  Barton
> >  
> > > Sent: Tuesday, February 28, 2012 2:24 PM
> > > To: John Levine
> > > Cc: ietf@ietf.org
> > > Subject: Re: DNS RRTYPEs, the difficulty with
> > > 
> > > Intelligent sysadmin: We need to deploy SPF
> > > Boss: How does it work?
> > > I: Well, eventually it will have its own DNS RR, but for now it
> > > works
> > > with TXT records
> > > B: Ok, put those TXT records in
> > > <time passes>
> > > I: It's now possible to use SPF RRs for SPF, so I need to make some
> > > changes, do some testing, etc.
> > > B: Are the TXT records working now?
> > > I: Well yes, but ...
> > > B: We have more important priorities that I need you to spend your
> > > time
> > > on, leave the thing that's working alone.
> > > 
> > > Or, put more simply, your conclusion seems to be that we can never
> > > add
> > > new RRs. Given that adding new RRs is crucial to the growth of the
> > > Internet, I reject that conclusion completely.
> > 
> > Your scenario illustrated the problem nicely: People started SPF with
> > TXT reco rds because they were available and the road to a new RRType
> > was seen as a ste ep one.  Once that was even a little bit deployed, it
> > became practically irrev ersible.  The same happened with DKIM, and
> > then VBR, and now it's basically co mmon practice to use naming tricks
> > to sidestep the RRType arguments.
> > 
> > I think the right endgame here is to make sure new RRTypes are
> > accessible to t hose that want to have them.  This will remove the
> > temptation to start with TX T and, ultimately, stay there.
> 
> They are there.  They were there when SPF was being developed.  They
> were there when DKIM was being developed.  It's just the neigh
> sayers won out.
> 
> Libresolv has supported unknown types for 25 years.  Other C libraries
> support them.  dnspython supports them.  dnsjava supports them.  It
> really isn't hard to get a length tagged blob of data back to the
> application.
> 
> Authoritative nameservers support them.  Recursive nameservers
> support them and always have modulo bugs.
> 
> If your DNS hosting company doesn't support them find another one
> or complain to them.  You are paying them to host your DNS services
> and this is a basic part of the job.

To what hosting company should I switch if I want to publish SPF records of 
Type SPF?

Scott K

From scott@kitterman.com  Tue Feb 28 15:42:57 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DFAD21F851D for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:42:57 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7uLIPWd2Nrn for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 15:42:50 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id ECB9221F851C for <ietf@ietf.org>; Tue, 28 Feb 2012 15:42:49 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 2AD9B20E40E0; Tue, 28 Feb 2012 18:42:40 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330472566; bh=L74zx+AuY7/RXcDQcyXnc1Sc8xVbIak0pSikk0CqWZQ=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=qX/j1SJcGGWIulbczR5lwxxkLkglRF7VP6ddWkkGpCgiYXLubOgR4G4OWWvG8J/G8 R+vs2o/G09wq8wHJHXxVd3tzf+vAv4IQEnvNhy6UhfQ2E/Iq/+YIVzI9nITUMb9ksk vgL5YGKQn2ejtE5Bcof/+pUWdhxNxOuzafeDzPkE=
Received: from scott-latitude-e6320.localnet (140.239.105.162.ptr.us.xo.net [140.239.105.162]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 06EFB20E4099;  Tue, 28 Feb 2012 18:42:39 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Tue, 28 Feb 2012 18:42:39 -0500
Message-ID: <5812481.i6m9oFvNsy@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F4D53E2.5080803@dougbarton.us>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 2012 23:42:57 -0000

On Tuesday, February 28, 2012 02:23:30 PM Doug Barton wrote:
> On 2/27/2012 5:56 PM, John Levine wrote:
> > The problem is provisioning software.  We weenies can stuff anything
> > into our DNS servers we want, because we use vi and emacs and (in my
> > case) custom perl scripts.  For the other 99.5% of the world, what
> > they can put in their DNS zones is limited to whatever the web
> > provisioning software at their registrar or ISP or web host supports,
> > and I challenge you to find any that supports SPF records.
> 
> I have been both the author and a consumer of the types of interfaces
> that you're describing, and I had a very peripheral role in the work to
> evangelize interface support for new TLDs, IPv6, and DNSSEC; so I'm
> familiar with the issue. My experience with these issues tells me that
> when there is demand to support a new RRtype, it will be supported.
> 
> So, once again, we need to learn from the mistakes that were made with
> SPF. Here is how life goes in most busy enterprise environments:
> 
> Intelligent sysadmin: We need to deploy SPF
> Boss: How does it work?
> I: Well, eventually it will have its own DNS RR, but for now it works
> with TXT records
> B: Ok, put those TXT records in
> <time passes>
> I: It's now possible to use SPF RRs for SPF, so I need to make some
> changes, do some testing, etc.
> B: Are the TXT records working now?
> I: Well yes, but ...
> B: We have more important priorities that I need you to spend your time
> on, leave the thing that's working alone.
> 
> Or, put more simply, your conclusion seems to be that we can never add
> new RRs. Given that adding new RRs is crucial to the growth of the
> Internet, I reject that conclusion completely.

Here is a suggestion for those who are convinced using a new RR type in 
getting a new protocol deployed is now trivially easy and people who don't 
want to do it are lazy/whiners/ignorant/whatever:

A few weeks ago a new effort was announced in the mail authentication space 
called DMARC (see dmarc.org).  It's a brand new protocol that so far has 
minimal deployment.  It currently uses and underscored TXT subdomain, but it 
should be an ideal candidate for a new RR.

Why don't you volunteer to help them navigate through what needs to be done to 
succeed in getting deployment with a new RR type.  If you can manage it, 
that'll be the existence proof that it can be done.

Scott K

From sant9442@gmail.com  Tue Feb 28 16:52:42 2012
Return-Path: <sant9442@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 5E6D021F87BA for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 16:52:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.22
X-Spam-Level: 
X-Spam-Status: No, score=-3.22 tagged_above=-999 required=5 tests=[AWL=0.379,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5WHBurjHysHq for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 16:52:41 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id C137C21F87B3 for <ietf@ietf.org>; Tue, 28 Feb 2012 16:52:41 -0800 (PST)
Received: by ggnp2 with SMTP id p2so1338716ggn.31 for <ietf@ietf.org>; Tue, 28 Feb 2012 16:52:40 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.175.36 as permitted sender) client-ip=10.236.175.36; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.175.36 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.175.36]) by 10.236.175.36 with SMTP id y24mr31114074yhl.64.1330476760762 (num_hops = 1); Tue, 28 Feb 2012 16:52:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iitpavahMKguRjKAFSYFZI2w1wxrJa2SAt12D2BlANk=; b=Rx7cCJ/66S+HP+JS12Vf/nNwZQOL9g/rZEIJYWa3Npm2Jpz6T4lZftfht9s3nbSUrk zrcSHeVvX2/sU6qBygGvZL1eD1Mu0fNPzlKamg/V8RbXMQfxI19HemIlLYMf7CZdrO5N eLRJwK3jPDYlg/VkDt2BxBE7WeTxcz5q5zN1k=
Received: by 10.236.175.36 with SMTP id y24mr23590092yhl.64.1330476760665; Tue, 28 Feb 2012 16:52:40 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id m30sm15734211yhe.15.2012.02.28.16.52.38 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Feb 2012 16:52:39 -0800 (PST)
Message-ID: <4F4D76D5.5030202@gmail.com>
Date: Tue, 28 Feb 2012 19:52:37 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan>	<9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.com>	<20120228231753.52EB41DE9F99@drugs.dv.isc.org> <2522391.bzDDO1QXaX@scott-latitude-e6320>
In-Reply-To: <2522391.bzDDO1QXaX@scott-latitude-e6320>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 00:52:42 -0000

Scott Kitterman wrote:

>> If your DNS hosting company doesn't support them find another one
>> or complain to them.  You are paying them to host your DNS services
>> and this is a basic part of the job.
> 
> To what hosting company should I switch if I want to publish SPF records of 
> Type SPF?

SMTP hosting systems are not stuck using their ISP's primary name 
servers currently limited in their customer's UI management of 
domain(s) zone file(s).

You could always use your own name server or use another that is more 
flexible. No need to switch ISPs. Some may even allow you to do 
offline editing (export/import) of your zone files.

If you don't wish to have your own primary DNS server, there are many 
out there you can switch to, some even free, and perhaps for only 
using a faster, more 24x7 reliable name server than their ISP's name 
servers who could be tier limiting the customer.

I've gone through this issue a # of times just with SRV with customers 
and their ISPs was limited in the UI in some way. Not an issue today 
with SRV,  but the idea of installing or switching the name servers 
was always a last recourse option considered.

Yet, even if the ISP or with your own name server you added the SPF 
type, that still didn't mean all query paths taken would be 
successful. It could work 100% with testing short distance paths and 
locally, but from a remote different path?  It may not work.  That was 
the early RFC3597 issues I experienced that basically made you just 
punt of the idea of using new RR type with the obvious overhead waste. 
  But my experience today, the RFC3597 issues are much less.  I would 
not hesitate to finally enabling SPF type as a default option in our 
wares, at least give a new look for reasonable feasible results on par 
with the migration that has materialized.

--
HLS

From scott@kitterman.com  Tue Feb 28 17:23:41 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A42E521F86B1 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IhsUxS5g2Cbn for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:23:40 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 5068321F86A6 for <ietf@ietf.org>; Tue, 28 Feb 2012 17:23:40 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id B584E20E40E0; Tue, 28 Feb 2012 20:23:39 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330478619; bh=lV3roE04qCARq5tZTFdvyf+EAhCotOI36uQbFf5l2rk=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=CUiui2YgKCGb+6EOHNbrlk0ZES1oanM+NOvqSxo+4IAe5UfrtmOkXweHEz+CXihc+ j/Y8/Ctmq87oPBOWU+Y/vyENPoXSgLujeYCoPqJT2QlXc6I6Xkk0eed1hRH/A0hfOG GQoxDgbHxzddjFASO4Bgf9ZiKm5nW+NvRhWdI1dU=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 9692020E4099;  Tue, 28 Feb 2012 20:23:39 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Tue, 28 Feb 2012 20:23:38 -0500
Message-ID: <1840235.J1ONmZxlFS@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F4D76D5.5030202@gmail.com>
References: <20120228015606.2227.qmail@joyce.lan> <2522391.bzDDO1QXaX@scott-latitude-e6320> <4F4D76D5.5030202@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 01:23:41 -0000

On Tuesday, February 28, 2012 07:52:37 PM Hector wrote:
> Scott Kitterman wrote:
> >> If your DNS hosting company doesn't support them find another one
> >> or complain to them.  You are paying them to host your DNS services
> >> and this is a basic part of the job.
> > 
> > To what hosting company should I switch if I want to publish SPF records
> > of Type SPF?
> 
> SMTP hosting systems are not stuck using their ISP's primary name
> servers currently limited in their customer's UI management of
> domain(s) zone file(s).
> 
> You could always use your own name server or use another that is more
> flexible. No need to switch ISPs. Some may even allow you to do
> offline editing (export/import) of your zone files.
> 
> If you don't wish to have your own primary DNS server, there are many
> out there you can switch to, some even free, and perhaps for only
> using a faster, more 24x7 reliable name server than their ISP's name
> servers who could be tier limiting the customer.
> 
> I've gone through this issue a # of times just with SRV with customers
> and their ISPs was limited in the UI in some way. Not an issue today
> with SRV,  but the idea of installing or switching the name servers
> was always a last recourse option considered.
> 
> Yet, even if the ISP or with your own name server you added the SPF
> type, that still didn't mean all query paths taken would be
> successful. It could work 100% with testing short distance paths and
> locally, but from a remote different path?  It may not work.  That was
> the early RFC3597 issues I experienced that basically made you just
> punt of the idea of using new RR type with the obvious overhead waste.
>   But my experience today, the RFC3597 issues are much less.  I would
> not hesitate to finally enabling SPF type as a default option in our
> wares, at least give a new look for reasonable feasible results on par
> with the migration that has materialized.

Hector,

I know all about how I could publish SPF records.  You are missing my point.

In the previous message it was suggested that people who use a hosted DNS 
service should switch if their service doesn't support Type SPF.  The problem 
is that, as far as I'm aware, none of them do.  

I have not determined any source of economic motivation to get that to change.  
"Support this or I'll take my business to someone that does" is an empty 
threat unless someone actually does.  It's also not something anyone other 
than DNS purists would worry about.  No one is going to switch providers and 
risk downtime in order to publish a record that to a very, very close 
approximation accomplished nothing.

Scott K

From sant9442@gmail.com  Tue Feb 28 17:24:30 2012
Return-Path: <sant9442@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 1674F21F854C for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.243
X-Spam-Level: 
X-Spam-Status: No, score=-3.243 tagged_above=-999 required=5 tests=[AWL=0.356,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOM-mWQSU63C for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:24:29 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7B99221F853D for <ietf@ietf.org>; Tue, 28 Feb 2012 17:24:29 -0800 (PST)
Received: by yhpp34 with SMTP id p34so1419790yhp.31 for <ietf@ietf.org>; Tue, 28 Feb 2012 17:24:29 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.153.6 as permitted sender) client-ip=10.236.153.6; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.153.6 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.153.6]) by 10.236.153.6 with SMTP id e6mr31634416yhk.113.1330478669217 (num_hops = 1); Tue, 28 Feb 2012 17:24:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2eDTXLl8YcbgwCzaVvlDQ9+yUSyb7345xJeoeftiE7k=; b=HgGUoW06NsIklXFxFp/wDWzafZzkObyEtcKUcD5uTA7Rx27R2yZ9NlZjGbt+bJIK3e Sr2ckrgCAxsy/dZF+Lt9/0XNy2RkxUsgxQ4OG0UekXdfn5RktNtTl92KybtO0h7KPzYI hIz1mmFJ72dSBaBdRHhatQuh09DDosVTZ1P6w=
Received: by 10.236.153.6 with SMTP id e6mr23993975yhk.113.1330478669030; Tue, 28 Feb 2012 17:24:29 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id g7sm51694252yhm.5.2012.02.28.17.24.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Feb 2012 17:24:27 -0800 (PST)
Message-ID: <4F4D7E4A.2040209@gmail.com>
Date: Tue, 28 Feb 2012 20:24:26 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan>	<4F4D53E2.5080803@dougbarton.us>	<9452079D1A51524AA5749AD23E00392804C720@exch-mbx901.corp.cloudmark.com> <20120228231753.52EB41DE9F99@drugs.dv.isc.org>
In-Reply-To: <20120228231753.52EB41DE9F99@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 01:24:30 -0000

Mark Andrews wrote:

>
> ...
>
> If your DNS hosting company doesn't support them find another one
> or complain to them.  You are paying them to host your DNS services
> and this is a basic part of the job.

+1.

We have our own primary server and use GoDaddy as my domains 
registrar. I have all my domains  name server fields pointing to our 
name servers, except for one testing domain specifically left to use 
the Godaddy hosting and name servers for this exact purpose of seeing 
what GUI DNS management and hosting features are available and how it 
evolved.

I just went to the site now to see whats there now and saw two new things:

1) The GUI is now pushing the addition of DNSSEC records with splash 
box shown when you start the DNS manager.

          "No DNSSEC record found"

and a URL link to explain more and a link to begin adding one.  It was 
becoming annoying to continue to popup up.

2) Promotion of a premium DNS management service. Curious to see if

         "New! Add new RR type support!"

was an premium feature, I didn't see it outlined. Nothing screams out 
regarding support for new RR types or adding your own.

You were always able to always download, edit, upload  your zone file. 
Didn't check to see if that was still available or removed.


--
HLS

From johnl@iecc.com  Tue Feb 28 17:37:01 2012
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 EF27D21F8748 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.569
X-Spam-Level: 
X-Spam-Status: No, score=-110.569 tagged_above=-999 required=5 tests=[AWL=0.630, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JkXdLRys1cCW for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:36:56 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7291E21F8746 for <ietf@ietf.org>; Tue, 28 Feb 2012 17:36:56 -0800 (PST)
Received: (qmail 66105 invoked from network); 29 Feb 2012 01:36:54 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 29 Feb 2012 01:36:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f4d8136.xn--hew.k1202; i=johnl@user.iecc.com; bh=/0RAvKjQQSPOsa+ICaqmxdOazpSXLI+KeaW7hGu2F3g=; b=t8t0rxBAY6fBXrrXo+1KPTjILYSsOVR8kZcCLFBp/zVxXD/9PJXRfGfcTq2ePODALM8o3tv5Et/XfGmCYg6EdoyZw7J3com2gatfxTc9AIxmTPiGAs+d4Jw5ss0jzEnebYo9AYrnNiAQbI6Kg9OuUtljetUMN7StnUYLb64meOM=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 29 Feb 2012 01:36:32 -0000
Message-ID: <20120229013632.9326.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <20120228231753.52EB41DE9F99@drugs.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 01:37:02 -0000

>If your DNS hosting company doesn't support them find another one
>or complain to them.  You are paying them to host your DNS services
>and this is a basic part of the job.

Can you suggest some DNS hosting companies that provide support for
provisioning SPF records?  I'm not aware of any.

R's,
John

From marka@isc.org  Tue Feb 28 17:53:59 2012
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 852E421F8746 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:53:59 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Moad7e0kGV7A for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:53:59 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id D08AE21F8740 for <ietf@ietf.org>; Tue, 28 Feb 2012 17:53:58 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 836735F9899; Wed, 29 Feb 2012 01:53:38 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d5c5:dd9e:52fb:735d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 30CD7216C31; Wed, 29 Feb 2012 01:53:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id B408D1DEB152; Wed, 29 Feb 2012 12:53:30 +1100 (EST)
To: "John Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120229013632.9326.qmail@joyce.lan>
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "29 Feb 2012 01:36:32 -0000." <20120229013632.9326.qmail@joyce.lan>
Date: Wed, 29 Feb 2012 12:53:30 +1100
Message-Id: <20120229015330.B408D1DEB152@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 01:53:59 -0000

In message <20120229013632.9326.qmail@joyce.lan>, "John Levine" writes:
> >If your DNS hosting company doesn't support them find another one
> >or complain to them.  You are paying them to host your DNS services
> >and this is a basic part of the job.
> 
> Can you suggest some DNS hosting companies that provide support for
> provisioning SPF records?  I'm not aware of any.

SPF is listed.  http://dyn.com/dns/dns-comparison/
 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From johnl@iecc.com  Tue Feb 28 17:57:10 2012
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 E1FBE21F8686 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:57:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.37
X-Spam-Level: 
X-Spam-Status: No, score=-102.37 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJI8XZo5NsDQ for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 17:57:10 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 12D7F21F8681 for <ietf@ietf.org>; Tue, 28 Feb 2012 17:57:03 -0800 (PST)
Received: (qmail 73822 invoked from network); 29 Feb 2012 01:56:59 -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:vbr-info:user-agent:cleverness; s=1205c.4f4d85eb.k1202; bh=D5r5KlFRGe20TuqPBwFAN+mtwlDmWXf8aUKKHCFitOY=; b=vAxn1c4GEYMIYVjMPtHHIa5AZRDMKH2zTAYTxiwppF0b3TObn0Cql7HwAyVqYDIg1eW4B2mOfOLaXwOL8pLhVNLUVN1rG9kP/wi6gkFael1pCcxv43qyaA9+iQdOy52M3qk09eI8BPyySutotnvL8YtpUCfzcz52KyUirDzHWiU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Feb 2012 01:56:37 -0000
Date: 28 Feb 2012 20:56:59 -0500
Message-ID: <alpine.BSF.2.00.1202282055330.43471@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: DNS RRTYPEs, the difficulty with
In-Reply-To: <20120229015330.B408D1DEB152@drugs.dv.isc.org>
References: <20120229013632.9326.qmail@joyce.lan> <20120229015330.B408D1DEB152@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 01:57:11 -0000

> SPF is listed.  http://dyn.com/dns/dns-comparison/

Hmmn, only on the premium $30/mo and up packages, not on the cheap ones. 
There must be a moral here.

By the way, what do you think of draft-levine-dnsextlang-02 ?

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From ned+ietf@mauve.mrochek.com  Tue Feb 28 18:17:01 2012
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 7434D21E80C1 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 18:17:01 -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=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XHyhpEmekUm for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 18:17:00 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 61ACF21E80C0 for <ietf@ietf.org>; Tue, 28 Feb 2012 18:16:56 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCJ7DT2PLC002FOF@mauve.mrochek.com> for ietf@ietf.org; Tue, 28 Feb 2012 18:16:54 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCI1CWJADS00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 28 Feb 2012 18:16:51 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCJ7DRTMT600ZUIL@mauve.mrochek.com>
Date: Tue, 28 Feb 2012 17:54:58 -0800 (PST)
Subject: Re: DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Tue, 28 Feb 2012 20:23:38 -0500" <1840235.J1ONmZxlFS@scott-latitude-e6320>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120228015606.2227.qmail@joyce.lan> <2522391.bzDDO1QXaX@scott-latitude-e6320> <4F4D76D5.5030202@gmail.com> <1840235.J1ONmZxlFS@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330481828; i=@mrochek.com; bh=sjKVBgGYFKU3FL6xdZwY9X1basOV7KHxPFt0hNReRfI=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=NU5e+14HDgZNQZBh5Bm856AsJBkMk8p/t+Hnkh5pH0LZFUq5XVxkQyQT7ElxwVgWW kwBfErm1qrtX+S0a3vf2BiLzVqO0Z8TsV10njvzsVlgJRmjDEWDo0gnupX6SWOlPMk FPOUJtgPS7GVQpIv9Bwth365EmsVgSFbuyZw4CxM=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 02:17:01 -0000

> In the previous message it was suggested that people who use a hosted DNS
> service should switch if their service doesn't support Type SPF.  The problem
> is that, as far as I'm aware, none of them do.

Perhaps in some cases it's because the person or persons who want to publish
SPF records are not the ones who make the decision about which hosted DNS
service provider to use, and are unable to make a sufficient case for a change
to those who do have the authority to make it.

It's also the case that even when the ability to publish such records exists,
the person or persons who want to do so may not have the necessary access or
authority and have no way to get it.

Only today we were dealing with a customer who was asking about what options
our product provides for overriding entries in his own DNS domain with local
information. Yes, you read that right: The companies DNS has bogus stuff in it
that cannot or will not be corrected. Such requests are unfortunately not
uncommon.

All that said, a suggestion: Patrik published a pretty good list of most of the 
issues that arise when attempting to deploy new RRTYPEs. Some of those, like
the lack of GUI pulldowns in some hosting provider web interfaces, are clearly
beyond the IETF's purview to address. But others, like the formatting issues in
zone master files that arise when a new RRTYPE is defined, are things we can
address. (And no, external scripts to do the format conversion are not a
sufficient solution to this problem.)

So might I suggest that instead of arging about the operational realities of
deploying new RRTYPEs - which  appears to be turning into yet another retelling
of the parable about the blind men and the elephant - we instead turn our
attention to activities that would actually address parts of the problem.

In particular, John Levine has already written a draft that attempts to address
the formatting issues by defining a simple format extension language. That
might be a good place to start. (I've already sent him my review comments in
private email.)

				Ned

From stewe@stewe.org  Tue Feb 28 18:51:30 2012
Return-Path: <stewe@stewe.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 19D0921E803D for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 18:51:30 -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=[AWL=1.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AG4a4BGtfM85 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 18:51:29 -0800 (PST)
Received: from TX2EHSOBE005.bigfish.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 5004921E8071 for <ietf@ietf.org>; Tue, 28 Feb 2012 18:51:29 -0800 (PST)
Received: from mail193-tx2-R.bigfish.com (10.9.14.246) by TX2EHSOBE005.bigfish.com (10.9.40.25) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 Feb 2012 02:51:28 +0000
Received: from mail193-tx2 (localhost [127.0.0.1])	by mail193-tx2-R.bigfish.com (Postfix) with ESMTP id 69310403C1; Wed, 29 Feb 2012 02:51:28 +0000 (UTC)
X-SpamScore: -35
X-BigFish: PS-35(zz1dbaL1432N1453M98dKzz1202h1082kzz1033IL8275bh8275dhz2fh2a8h668h839h944h)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT002.namprd07.prod.outlook.com; RD:none; EFVD:NLI
Received-SPF: pass (mail193-tx2: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT002.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail193-tx2 (localhost.localdomain [127.0.0.1]) by mail193-tx2 (MessageSwitch) id 1330483886660268_10117; Wed, 29 Feb 2012 02:51:26 +0000 (UTC)
Received: from TX2EHSMHS006.bigfish.com (unknown [10.9.14.237])	by mail193-tx2.bigfish.com (Postfix) with ESMTP id 9BDB03E004A; Wed, 29 Feb 2012 02:51:26 +0000 (UTC)
Received: from BL2PRD0710HT002.namprd07.prod.outlook.com (157.56.240.133) by TX2EHSMHS006.bigfish.com (10.9.99.106) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 Feb 2012 02:51:26 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.239]) by BL2PRD0710HT002.namprd07.prod.outlook.com ([10.255.102.37]) with mapi id 14.16.0123.000; Wed, 29 Feb 2012 02:51:25 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "John R. Levine" <johnl@iecc.com>, Mark Andrews <marka@isc.org>
Subject: Re: DNS RRTYPEs, the difficulty with
Thread-Topic: DNS RRTYPEs, the difficulty with
Thread-Index: AQHM9m8xFa9Niuu8mEq8K5fV+EmtmJZTGEIAgAAE7eaAAADKgP//iRYA
Date: Wed, 29 Feb 2012 02:51:24 +0000
Message-ID: <CB72D214.83AB7%stewe@stewe.org>
In-Reply-To: <alpine.BSF.2.00.1202282055330.43471@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5A19E897249D4C4A92955960D5FEF52F@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 02:51:30 -0000

Godaddy, basic domain hosting at $10 per .com, allows you to set an SPF
record.
Stephan

On 2.28.2012 17:56 , "John R. Levine" <johnl@iecc.com> wrote:

>> SPF is listed.  http://dyn.com/dns/dns-comparison/
>
>Hmmn, only on the premium $30/mo and up packages, not on the cheap ones.
>There must be a moral here.
>
>By the way, what do you think of draft-levine-dnsextlang-02 ?
>
>Regards,
>John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for
>Dummies",
>Please consider the environment before reading this e-mail. http://jl.ly
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf
>



From scott@kitterman.com  Tue Feb 28 20:28:58 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C696C21E8036 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 20:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mQCsPdhZ5YRf for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 20:28:58 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id DF0EF21E8010 for <ietf@ietf.org>; Tue, 28 Feb 2012 20:28:57 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 28E6320E40D8; Tue, 28 Feb 2012 23:28:57 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330489737; bh=3cRaW+ByHb1y3XujHSJXOW4q7syiZ+nQ72Ue6MNl2iQ=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=iYOlyAMb8HfGCR/8WMLSX37rKUevIpiGw0ec7vCmNjiLBw2GDdlrgMmLpRC2WBQD8 +k7sAH/i4rURd0/YCv1FF53A0rkcia4sxskPk036GS0bMJrMrPUxQbplX/O4bmKyuP Ly/lFOrS5fhyohNveBk5jmzNZZ2rTDBhW+H1i7T4=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 0872520E4064;  Tue, 28 Feb 2012 23:28:56 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Tue, 28 Feb 2012 23:28:56 -0500
Message-ID: <166313775.RIOu00OFM7@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <CB72D214.83AB7%stewe@stewe.org>
References: <CB72D214.83AB7%stewe@stewe.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 04:28:58 -0000

On Wednesday, February 29, 2012 02:51:24 AM Stephan Wenger wrote:
> Godaddy, basic domain hosting at $10 per .com, allows you to set an SPF
> record.
> Stephan

Of type TXT or type SPF?  I checked with someone who has domains at Go Daddy 
and they couldn't find a mechanism for publishing Type SPF records.

Scott K

From sant9442@gmail.com  Tue Feb 28 21:02:14 2012
Return-Path: <sant9442@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 1F6A521E800C for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 21:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDWYGNek5zkj for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 21:02:13 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8F03921E803D for <ietf@ietf.org>; Tue, 28 Feb 2012 21:02:13 -0800 (PST)
Received: by yenm5 with SMTP id m5so1339453yen.31 for <ietf@ietf.org>; Tue, 28 Feb 2012 21:02:13 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.197.41 as permitted sender) client-ip=10.236.197.41; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.197.41 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.197.41]) by 10.236.197.41 with SMTP id s29mr33743591yhn.7.1330491733293 (num_hops = 1); Tue, 28 Feb 2012 21:02:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=QfSh46IzFbUIFblXzjKAuGNElUyy6vD1ByBzgbg0bLg=; b=qMfFwEiXHfteLcQVICOy4Y8XCCZ+Zz3MnB3D4nff1s+DRJSoZGd8iIVoK6R4siqLXf CV+gaJIhxOU/HsvVJoQM7iv7e7j6hpNTWULclPejLunly0zi9uQrQZqDaNFqVCSNnZiB NQ03hkLZQQNY78IBPe0n8rBLM1XOpjsDOkroA=
Received: by 10.236.197.41 with SMTP id s29mr25593826yhn.7.1330491733256; Tue, 28 Feb 2012 21:02:13 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id v26sm12058238yhk.1.2012.02.28.21.02.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Feb 2012 21:02:12 -0800 (PST)
Message-ID: <4F4DB155.4040204@gmail.com>
Date: Wed, 29 Feb 2012 00:02:13 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <CB72D214.83AB7%stewe@stewe.org> <166313775.RIOu00OFM7@scott-latitude-e6320>
In-Reply-To: <166313775.RIOu00OFM7@scott-latitude-e6320>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 05:02:14 -0000

Scott Kitterman wrote:
> On Wednesday, February 29, 2012 02:51:24 AM Stephan Wenger wrote:
>> Godaddy, basic domain hosting at $10 per .com, allows you to set an SPF
>> record.
>> Stephan
> 
> Of type TXT or type SPF?  I checked with someone who has domains at Go Daddy 
> and they couldn't find a mechanism for publishing Type SPF records.

Long time customer of GoDaddy, I don't ever recall support for SPF 
type or any new RR type outside the common ones, and even then I 
believe SRV came later with newer UIs and as I see today, a BIG PUSH 
to get you to add a DNSSEC record with an annoying POPUP box when you 
enter the DNS manager.

I don't know if it does it on a cookie basis, but I just noticed it today.

The only way I can see with GoDaddy is to export your zone file, edit 
offline and then import.

What I think Stephan is pointing out, is that even though you always 
had the ability to add a TXT record, there was an advanced special SPF 
"marketing" option to select to got it started to add the TXT record. 
  I don't recall it being a SPF rule wizard though, unless its changed 
today.

--
HLS

From scott@kitterman.com  Tue Feb 28 21:11:16 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0683921F8480 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 21:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRCCxTN0DAzK for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 21:11:10 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id B593421F847B for <ietf@ietf.org>; Tue, 28 Feb 2012 21:11:10 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 3685F20E40D8; Wed, 29 Feb 2012 00:11:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330492270; bh=z5J1djDeyN7ZG9V4FHV9zyQ3ObXZd7129vV5Zw7gJvw=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=PBtFJ+o+h/Hldr780bUWV7Mjq/ED2t8axT3E4yFl1XcQCF+PoD9hBkraQlDsk9MWI kJa1n9gPyUlJ2tdddPj1KsWpRExqmRnMCSJ1XxwMy8i7kVX7FR3sLzzyEO3y5zQCse zqOHMA0S9Pf8g9SueAynxGYL2LjGKskPpX9QWmFU=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 1CF6120E4064;  Wed, 29 Feb 2012 00:11:09 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
Date: Wed, 29 Feb 2012 00:11:09 -0500
Message-ID: <1651247.ES0MIno53m@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F4DB155.4040204@gmail.com>
References: <CB72D214.83AB7%stewe@stewe.org> <166313775.RIOu00OFM7@scott-latitude-e6320> <4F4DB155.4040204@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 05:11:16 -0000

On Wednesday, February 29, 2012 12:02:13 AM Hector wrote:
> Scott Kitterman wrote:
> > On Wednesday, February 29, 2012 02:51:24 AM Stephan Wenger wrote:
> >> Godaddy, basic domain hosting at $10 per .com, allows you to set an
> >> SPF
> >> record.
> >> Stephan
> > 
> > Of type TXT or type SPF?  I checked with someone who has domains at Go
> > Daddy and they couldn't find a mechanism for publishing Type SPF
> > records.
> Long time customer of GoDaddy, I don't ever recall support for SPF
> type or any new RR type outside the common ones, and even then I
> believe SRV came later with newer UIs and as I see today, a BIG PUSH
> to get you to add a DNSSEC record with an annoying POPUP box when you
> enter the DNS manager.
> 
> I don't know if it does it on a cookie basis, but I just noticed it today.
> 
> The only way I can see with GoDaddy is to export your zone file, edit
> offline and then import.
> 
> What I think Stephan is pointing out, is that even though you always
> had the ability to add a TXT record, there was an advanced special SPF
> "marketing" option to select to got it started to add the TXT record.
>   I don't recall it being a SPF rule wizard though, unless its changed
> today.

I checked again and I'm told when adding a record there's an option to add an 
SPF record, but the record it adds is of Type TXT.

Scott K

From stewe@stewe.org  Tue Feb 28 21:27:09 2012
Return-Path: <stewe@stewe.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 7762821E8039 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 21:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nzctd8WtCUzE for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 21:27:08 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8F03421E8077 for <ietf@ietf.org>; Tue, 28 Feb 2012 21:27:06 -0800 (PST)
Received: from mail164-ch1-R.bigfish.com (10.43.68.243) by CH1EHSOBE001.bigfish.com (10.43.70.51) with Microsoft SMTP Server id 14.1.225.23; Wed, 29 Feb 2012 05:27:05 +0000
Received: from mail164-ch1 (localhost [127.0.0.1])	by mail164-ch1-R.bigfish.com (Postfix) with ESMTP id E817D300165; Wed, 29 Feb 2012 05:27:05 +0000 (UTC)
X-SpamScore: -27
X-BigFish: PS-27(zz9371I1432N98dKzz1202h1082kzz1033IL8275bh8275dhz2fh2a8h668h839h944h)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT005.namprd07.prod.outlook.com; RD:none; EFVD:NLI
Received-SPF: pass (mail164-ch1: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT005.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail164-ch1 (localhost.localdomain [127.0.0.1]) by mail164-ch1 (MessageSwitch) id 1330493223770468_18575; Wed, 29 Feb 2012 05:27:03 +0000 (UTC)
Received: from CH1EHSMHS012.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.246])	by mail164-ch1.bigfish.com (Postfix) with ESMTP id B7FDA2C0104;	Wed, 29 Feb 2012 05:27:03 +0000 (UTC)
Received: from BL2PRD0710HT005.namprd07.prod.outlook.com (157.56.240.133) by CH1EHSMHS012.bigfish.com (10.43.70.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 29 Feb 2012 05:27:03 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.239]) by BL2PRD0710HT005.namprd07.prod.outlook.com ([10.255.102.40]) with mapi id 14.16.0123.000; Wed, 29 Feb 2012 05:27:02 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Scott Kitterman <scott@kitterman.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DNS RRTYPEs, the difficulty with
Thread-Topic: DNS RRTYPEs, the difficulty with
Thread-Index: AQHM9m8xFa9Niuu8mEq8K5fV+EmtmJZTGEIAgAAE7eaAAADKgP//iRYAgAChXgCAAAlNgIAAAn+A//9+TQA=
Date: Wed, 29 Feb 2012 05:27:02 +0000
Message-ID: <CB72F6EA.83ACA%stewe@stewe.org>
In-Reply-To: <1651247.ES0MIno53m@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.5]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D5BB19C8543CA341B47923192A085FC0@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 05:27:09 -0000

Confirmed.  The menu option says "add SPF", but you end up with a TXT
record.
Embarrassed,
Stephan

On 2.28.2012 21:11 , "Scott Kitterman" <scott@kitterman.com> wrote:

>On Wednesday, February 29, 2012 12:02:13 AM Hector wrote:
>> Scott Kitterman wrote:
>> > On Wednesday, February 29, 2012 02:51:24 AM Stephan Wenger wrote:
>> >> Godaddy, basic domain hosting at $10 per .com, allows you to set an
>> >> SPF
>> >> record.
>> >> Stephan
>> >=20
>> > Of type TXT or type SPF?  I checked with someone who has domains at Go
>> > Daddy and they couldn't find a mechanism for publishing Type SPF
>> > records.
>> Long time customer of GoDaddy, I don't ever recall support for SPF
>> type or any new RR type outside the common ones, and even then I
>> believe SRV came later with newer UIs and as I see today, a BIG PUSH
>> to get you to add a DNSSEC record with an annoying POPUP box when you
>> enter the DNS manager.
>>=20
>> I don't know if it does it on a cookie basis, but I just noticed it
>>today.
>>=20
>> The only way I can see with GoDaddy is to export your zone file, edit
>> offline and then import.
>>=20
>> What I think Stephan is pointing out, is that even though you always
>> had the ability to add a TXT record, there was an advanced special SPF
>> "marketing" option to select to got it started to add the TXT record.
>>   I don't recall it being a SPF rule wizard though, unless its changed
>> today.
>
>I checked again and I'm told when adding a record there's an option to
>add an=20
>SPF record, but the record it adds is of Type TXT.
>
>Scott K
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf
>



From daedulus@btconnect.com  Wed Feb 29 02:13:09 2012
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 E9F7F21F8889 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 02:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[AWL=-1.240, BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nI7Te9yNEl7U for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 02:13:09 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by ietfa.amsl.com (Postfix) with ESMTP id A636C21F8807 for <ietf@ietf.org>; Wed, 29 Feb 2012 02:13:07 -0800 (PST)
Received: from host86-163-139-217.range86-163.btcentralplus.com (HELO pc6) ([86.163.139.217]) by c2beaomr07.btconnect.com with SMTP id GLQ26466; Wed, 29 Feb 2012 10:13:04 +0000 (GMT)
Message-ID: <00b201ccf6c2$46a7eb80$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Pete Resnick" <presnick@qualcomm.com>, "IETF-Discussion list" <ietf@ietf.org>
References: <4F43FF5C.6060003@qualcomm.com>
Subject: Re: Conclusion of Last Call for draft-ietf-sieve-convert anddraft-ietf-sieve-notify-sip-message
Date: Wed, 29 Feb 2012 10:12:27 +0100
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-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0301.4F4DFA2F.00FA, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.2.29.93619:17:7.944, ip=86.163.139.217, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, __C230066_P5, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4F4DFA30.0041,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 10:13:10 -0000

Pete

I agree with what you have done but would like to see it recorded in something
more accessible than an e-mail archive.  Could it be added to the data tracker,
under IESG evaluation or IESG writeup or some such?

Tom Petch


----- Original Message -----
From: "Pete Resnick" <presnick@qualcomm.com>
To: "IETF-Discussion list" <ietf@ietf.org>
Sent: Tuesday, February 21, 2012 9:32 PM
> I wanted to inform the community of the results of the second Last Call
> issued for draft-ietf-sieve-convert and
> draft-ietf-sieve-notify-sip-message. To remind you of the circumstances:
> After these two documents were approved by the IESG and sent on to the
> RFC Editor, an IPR disclosure was made pertaining to each of them
> indicating that one of the document editors for both documents was also
> the listed inventor for the disclosed patent. The disclosures were made
> by the document editor's employer and indicate that the date of the
> patent filings was prior to the adoption of these two drafts by the
> SIEVE working group. The RFC Editor was asked to suspend their work on
> the documents, and a second Last Call was made.
>
> After reviewing discussions in the SIEVE WG and on the IETF mailing
> list, the chairs have decided (and I support) that, because of the
> failure to disclose the IPR as required by BCP 79 (RFC 3979), and as per
> RFC 2418 Section 6.1, the following actions are appropriate and will be
> taken:
>
> - The document editor in question is no longer a document editor for
> these two documents.
> - The person's name will be removed from the front page of the documents
> and from the Authors' Address section.
> - The person's name will be added to the Acknowledgments section of both
> documents to identify that he did contribute text to the drafts.
> - The RFC Editor will be asked to continue processing and publication of
> these drafts as RFCs.
>
> We will be notifying the RFC Editor of this decision presently.
>
> Meanwhile, the employer of the document editor in question has made
> followup disclosures on each of the documents, saying that they
> "covenant not to assert any such claim against any party for making,
> using, selling, offering for sale or importing a product that implements
> the corresponding part of the specification." The full text of the
> disclosures can be seen here:
>
> https://datatracker.ietf.org/ipr/1680/
> https://datatracker.ietf.org/ipr/1681/
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
>


From vesely@tana.it  Wed Feb 29 04:06:55 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35F8821F86A0 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 04:06:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.648
X-Spam-Level: 
X-Spam-Status: No, score=-4.648 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzpWRtcCWPJl for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 04:06:54 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 4304521F869C for <ietf@ietf.org>; Wed, 29 Feb 2012 04:06:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330517212; bh=aF3fFYMZCTDXRIsMzDgTp21A9L0+OJVGHvbd31y2Ios=; l=2885; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=QItH2JIGwp3bk0PqI4d/z9vnUpG36rifvt5ju3Gqd/N6nFzRzmGS4VeRp4zHXvJ7O +fL9tY2f+GFde8SwEC+2P67VGGkIynBb2urI+kTlo/pI20CP6tNWmRu+NMo2Spa2G4 /n5rGUDVAjSgzW4cDiyShy4z8pSeKUbr4F0CMxr4=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 29 Feb 2012 13:06:52 +0100 id 00000000005DC039.000000004F4E14DC.00004FFC
Message-ID: <4F4E14DC.9050200@tana.it>
Date: Wed, 29 Feb 2012 13:06:52 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan> <2522391.bzDDO1QXaX@scott-latitude-e6320> <4F4D76D5.5030202@gmail.com> <1840235.J1ONmZxlFS@scott-latitude-e6320> <01OCJ7DRTMT600ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCJ7DRTMT600ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 12:06:55 -0000

On 29/Feb/12 02:54, ned+ietf@mauve.mrochek.com wrote:
> 
> All that said, a suggestion: Patrik published a pretty good list of
> most of the issues that arise when attempting to deploy new
> RRTYPEs. Some of those, like the lack of GUI pulldowns in some
> hosting provider web interfaces, are clearly beyond the IETF's
> purview to address. But others, like the formatting issues in zone
> master files that arise when a new RRTYPE is defined, are things we
> can address. (And no, external scripts to do the format conversion
> are not a sufficient solution to this problem.)

Why?  I realize there's lots of wisdom in those words, but I can
hardly catch sight of it.  LIFO, why are RR2txt/txt2RR not sufficient
for formatting master zones?  And why cannot those same scripts be
invoked by a provider's web form?

For responses and zone transfers, Patrik distinguished between "core"
and "edge" deployments.  I heard about NotImp responses and mirroring
difficulties.  What is the current status?

> So might I suggest that instead of arguing about the operational
> realities of deploying new RRTYPEs - which  appears to be turning
> into yet another retelling of the parable about the blind men and
> the elephant - we instead turn our attention to activities that
> would actually address parts of the problem.

The phrase "rough consensus and running code" must be meant to be in
that order, because consensus makes the difference between /runnable/
and /running/ code.  Indeed, that parable often ends with "Then the
king/president explained to the blind men...", so we'd have to replace
that part with something that we can believe in, anyway.

> In particular, John Levine has already written a draft that
> attempts to address the formatting issues by defining a simple
> format extension language. That might be a good place to start.
> (I've already sent him my review comments in private email.)

I agree it's a clever spec, and I believe it's not overly hard to code
a couple of generic RR2txt/txt2RR scripts that use such symbolic
descriptions.  However, if we want to tackle some protocols, we had
better add an alternative stanza syntax for "tag=value" kinds of
record, and/or provide for type-specific external utilities.

But shouldn't we reach consensus on a migration strategy before we
discuss the tactics?  RFC 6195 says a new RR type should not be
allocated in case:

 5.  An excessive number of RRTYPE values is being requested when the
     purpose could be met with a smaller number or with Private Use
     values.

That criterion apparently matches requesting a new type and at the
same time reusing TXT.  RFC 5507 elucidates good principles and
reasons why adding a new RR type is a better solution than reusing
TXT, but it doesn't say that doing both solutions at the same time
results in a parody of those principles.

From hsantos@santronics.com  Tue Feb 28 18:01:47 2012
Return-Path: <hsantos@santronics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74ED721E8021 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 18:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.151
X-Spam-Level: 
X-Spam-Status: No, score=-2.151 tagged_above=-999 required=5 tests=[AWL=0.448,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBQNrOzsd9dY for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2012 18:01:46 -0800 (PST)
Received: from mail.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E708921F8795 for <ietf@ietf.org>; Tue, 28 Feb 2012 18:01:43 -0800 (PST)
DKIM-Signature: v=1; d=santronics.com; s=tms1; a=rsa-sha1; c=simple/relaxed; l=7480; t=1330480893; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=DjnKVin g2FZd/hFRUGyzwT6Yfx4=; b=N6NhQjRrSa4my8+1aOXew70t58nKNV/AORf49tD RNNcZVWSa040QsSTnczcG0bLxim7LrFo6HOao0l/8K+8UN47ZTmCh2x2AhpjhU+P fj9YS1+ogjMXUEew1HvrT8hKRGaFlmQaK1AKW7D49amzXketDElmHYH7lBVIc/Am GJPQ=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Tue, 28 Feb 2012 21:01:33 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 3682730909.94651.3376; Tue, 28 Feb 2012 21:01:31 -0500
Message-ID: <4F4D86F8.9050606@santronics.com>
Date: Tue, 28 Feb 2012 21:01:28 -0500
From: Hector Santos <hsantos@santronics.com>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan>	<2522391.bzDDO1QXaX@scott-latitude-e6320>	<4F4D76D5.5030202@gmail.com> <1840235.J1ONmZxlFS@scott-latitude-e6320>
In-Reply-To: <1840235.J1ONmZxlFS@scott-latitude-e6320>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 29 Feb 2012 08:07:02 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 02:01:47 -0000

Offlist. I will have an public reply to the message, maybe. I just 
want to hopefully show some basic more friendly approach to your 
statements from one that basically begins a friction:

Scott:

    I know all about how I could publish SPF records.  You are missing 
my point.

Revised friendly, no friction.

    Yes, but perhaps you may missed my points....

Why? because I did not miss your point and I could easily say:

    "Scott, I always saw your point, the problem is you are missing the
     point of others."

So in essence, it shows we are talking pass each other and the way you 
stated just feeds into the people like Murray's who will now say, "He 
is always missing the point."

So understand your  MAIN point and always did and that is why I 
started with this thread when I asked:

     Given higher modern DNS server support for unnamed types, should
     new protocols continues to pursue new RR types or does the
     DNS Community believe this original infrastructure ideal is no longer
     necessary and new protocols can use TXT records with a high
     degree of DNS support confidence for robustness.

And why you see most, if not all of the infrastructure people who 
posted, including Patrick, Mark, Paul and others like Burton express 
the same belief that new RR types are preferred.

Every one of us agreed that there are valid arguments and issues, and 
that is why I am saying

    "Ok, is it still a preferred ideal and are the issues are too 
problematic,
     and also importantly, the HARDWARE/SOFTWARE and DATABASES have 
improved
     so much that it means many of the early and current concerns 
obsolete."

See that last point - even current concerns regarding wasted calls. 
If you argue the point that it is WASTED CALLS, then you are making an 
infrastructure consideration that it will benefit DNS large scale 
usage by not use new RR types that already have a TXT backup.

But that is not the argument you are making, you are using low usage, 
and its even harder to see that as valid, when A) its not "honest" and 
B) the migration we wanted is exactly that happen.

Try to understand these subtle points because if you believe it was 
important, then you may see that the solution is to now promote the 
publishing in order to begin getting a payoff with the clients already 
doing the SPF type call.  I would also suggest that we help embark a 
technical sales marketing campaign to get hosting companies to begin 
supporting  the new IETF protocols with their specific RR types.

Scott say:

    No one is going to switch providers and risk downtime in order to 
publish a
    record that to a very, very close approximation accomplished nothing.

Revised friendly text:

    I suspect or don't have the confidence domain owners will switch 
providers
    and risk downtime in order to publish a record that to a very, very
    close approximation accomplished nothing.

Why?

Highly subjective.  Its a crystal ball opinion and one that comes with 
very high potential to see  domains beginning to use SPF types, 
especially those who have an Infrastructure Optimizing belief that it 
will help with contributing to a lesser SPF TXT only impact on DNS.

You completely ignore that I stated. Before the migration evidence 
shown that has proved the original intent was correct, I was 100% with 
you.  But the migration path that was discovered, I am 100% eager now 
to support it.

You ignored the next step for the migration now that clients are 
ready, promoting SPF type publishing perhaps starting with a dual 
publishing as well as the next migration expected.

And finally, you might be not aware of, but if you are, then ignoring, 
the very important points in the DNSOPS thread I started with Paul 
Vixie input showing perhaps what is the solution we should be repeated 
with Additional Info queries like it was with A/MX records.

    http://www.ietf.org/mail-archive/web/dnsop/current/msg09447.html
    http://www.ietf.org/mail-archive/web/dnsop/current/msg09451.html
    http://www.ietf.org/mail-archive/web/dnsop/current/msg09453.html


What I am saying use a solid engineering logic based on technical 
merit, and not a "practically factor" to dismiss what is still 
important considerations.  The reason overall is that you are are 
saying these ISP will never change and that is a "prediction" that can 
be very easily become untrue.

All it takes a better IETF promotion and marketing to get more ISP to 
support new RR types.


Scott Kitterman wrote:
> On Tuesday, February 28, 2012 07:52:37 PM Hector wrote:
>> Scott Kitterman wrote:
>>>> If your DNS hosting company doesn't support them find another one
>>>> or complain to them.  You are paying them to host your DNS services
>>>> and this is a basic part of the job.
>>> To what hosting company should I switch if I want to publish SPF records
>>> of Type SPF?
>> SMTP hosting systems are not stuck using their ISP's primary name
>> servers currently limited in their customer's UI management of
>> domain(s) zone file(s).
>>
>> You could always use your own name server or use another that is more
>> flexible. No need to switch ISPs. Some may even allow you to do
>> offline editing (export/import) of your zone files.
>>
>> If you don't wish to have your own primary DNS server, there are many
>> out there you can switch to, some even free, and perhaps for only
>> using a faster, more 24x7 reliable name server than their ISP's name
>> servers who could be tier limiting the customer.
>>
>> I've gone through this issue a # of times just with SRV with customers
>> and their ISPs was limited in the UI in some way. Not an issue today
>> with SRV,  but the idea of installing or switching the name servers
>> was always a last recourse option considered.
>>
>> Yet, even if the ISP or with your own name server you added the SPF
>> type, that still didn't mean all query paths taken would be
>> successful. It could work 100% with testing short distance paths and
>> locally, but from a remote different path?  It may not work.  That was
>> the early RFC3597 issues I experienced that basically made you just
>> punt of the idea of using new RR type with the obvious overhead waste.
>>   But my experience today, the RFC3597 issues are much less.  I would
>> not hesitate to finally enabling SPF type as a default option in our
>> wares, at least give a new look for reasonable feasible results on par
>> with the migration that has materialized.
> 
> Hector,
> 
> I know all about how I could publish SPF records.  You are missing my point.
> 
> In the previous message it was suggested that people who use a hosted DNS 
> service should switch if their service doesn't support Type SPF.  The problem 
> is that, as far as I'm aware, none of them do.  
> 
> I have not determined any source of economic motivation to get that to change.  
> "Support this or I'll take my business to someone that does" is an empty 
> threat unless someone actually does.  It's also not something anyone other 
> than DNS purists would worry about.  No one is going to switch providers and 
> risk downtime in order to publish a record that to a very, very close 
> approximation accomplished nothing.
> 
> Scott K
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

-- 
Sincerely

Hector Santos
http://www.santronics.com
jabber: hector@jabber.isdg.net


From jouni.korhonen@nsn.com  Tue Feb 28 23:14:22 2012
Return-Path: <jouni.korhonen@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C890B21F85B4; Tue, 28 Feb 2012 23:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_92=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISdmzJ3cyVvP; Tue, 28 Feb 2012 23:14:22 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8E84321F855A; Tue, 28 Feb 2012 23:14:21 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q1T7EJa8012121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Feb 2012 08:14:19 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q1T7EDwg022419; Wed, 29 Feb 2012 08:14:19 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 29 Feb 2012 08:14:18 +0100
Received: from 10.144.254.14 ([10.144.254.14]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) via Exchange Front-End Server demuexc023.nsn-intra.net ([10.150.128.36]) with Microsoft Exchange Server HTTP-DAV ; Wed, 29 Feb 2012 07:14:18 +0000
User-Agent: Microsoft-Entourage/12.32.0.111121
Date: Wed, 29 Feb 2012 09:14:16 +0200
Subject: Re: Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03
From: Jouni Korhonen <jouni.korhonen@nsn.com>
To: ext Ben Campbell <ben@nostrum.com>, <draft-ietf-mext-mip6-tls.all@tools.ietf.org>
Message-ID: <CB739CE8.143E2%jouni.korhonen@nsn.com>
Thread-Topic: Gen-ART LC/Telechat review of draft-ietf-mext-mip6-tls-03
Thread-Index: Acz2sb7wE1W7YQs4502UdTOzhMgCUQ==
In-Reply-To: <03557735-170E-422A-B507-45A07DEC22AE@nostrum.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Feb 2012 07:14:18.0706 (UTC) FILETIME=[C08DBB20:01CCF6B1]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 5263
X-purgate-ID: 151667::1330499660-000015E0-4D29BBA1/0-0/0-0
X-Mailman-Approved-At: Wed, 29 Feb 2012 08:07:22 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 07:14:22 -0000

Thanks Ben for a thorough review. Very good comments indeed. We'll come back
to this in a bit.. you know -00 deadline approaching and such ;)

- Jouni


On 2/29/12 1:34 AM, "ext Ben Campbell" <ben@nostrum.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
> 
> Document: draft-ietf-mext-mip6-tls-03
> Reviewer: Ben Campbell
> Review Date: 2012-02-28
> IETF LC End Date: 2012-02-29
> IESG Telechat date: 2012-03-01
> 
> Note: Since the Telechat review deadline is a day before the end of the IETF
> last call, this review serves both as a Telechat review and an IETF Last Call
> review.
> 
> Summary: This draft is basically ready for publication as an experimental RFC.
> There are some clarification issues that might should be addressed prior to
> publication.
> 
> Major issues:
> 
> None
> 
> 
> Minor issues:
> 
> -- general: 
> 
> The draft seems to be missing information on how to match TLS certificates to
> identities for HAC authentication.
> 
> -- section 1, paragraph 1, last sentence: "Client implementation experience
> has shown that the use of IKE(v2)/IPsec with Mobile IPv6 is fairly complex."
> 
> It might be worth elaborating on why this is true. Could this be solved with a
> cleaner software architecture rather than a protocol change?
> 
> -- section 5.4:  "The actual domain name used in queries is up to the
> deployment to decide and out of scope of this specification."
>  
> This seems under specified for SRV
> 
> -- 5.7.4:
> 
> Are more than one DNS server allowed for each protocol?
> 
> -- 5.8:
> 
> I find this section confusing,as the first and second paragraphs seem to make
> contradictory statements about the authentication, particularly about the use
> of PSK. I think you are talking about authentication of the HAC in the TLS
> handshake vs an higher level authentication of the MN using PSK or EAP. I
> think this could use some clarification, as both paragraphs talks about
> authentication between the MN and HAC without mentioning direction.
> 
> Note that this is more clear in the security considerations section, but it
> would help for it to be more clear here.
> 
> -- 5.9, 2nd to last paragraph:
> 
> How do the first and last sentences relate? It seems to say set it to "1",
> except for this case in which you set it to "1".
> 
> -- 8.1:
> 
> Is this registry only for TLS based MIPv6? If so, does it need to be
> explicitly constrained to not used for MIPv6 in general?
> 
> 
> 
> 
> Nits/editorial comments:
> 
> -- section 4.1: 
> 
> A picture showing the element and key relationships could be helpful here.
> 
> -- section 4.3, third paragraph:
> 
> Please expand BA on first mention
> 
> --section 4.3, "Security association validity times", : "hours or weeks"
> 
> Hours _to_ weeks?
> 
> -- section 4.3, "selected cyphersuite": " The selected algorithms SHOULD be
> one of the mutually supported ciphersuites"
> 
> How could it be otherwise? (i.e. why the SHOULD, and is this really normative
> vs descriptive?)
> 
> -- section 4.4: "Home Agent IP Address" : "Concerns both IPv6 and IPv4 home
> agent addresses."
> 
> Dual stack only?  (same applies to "Home Address" section)
> 
> -- section 5.1, second paragraph: "All data inside the Content portion of the
> message container MUST be encoded using octets."
> 
> I suspect I'm missing a subtlety here--but how else could you do it? Is this
> intended to imply a byte-field, or to imply no additional encoding is used?
> 
> -- section 5.2: "From now on, we use TypeValue header (TV-header) term to
> refer request-response message content HTTP-like headers."
>  
> Maybe that should be moved to the terminology section?
> 
> -- section 5.3, 2nd paragraph: "The MN is also the peer that always sends only
> request messages and the HAC only sends response messages."
> 
> I'm having trouble parsing. Is their a spurious "always"?
> 
> -- section 5.5 : "same to that used by HTTP"
> 
> same _as_?
> 
> -- section 5.5.5
> 
> s/till/until
> 
> -- 5.5.8, 1st sentence:
> 
> Sentence fragment. Missing words?
> 
> -- 5.9, first paragraph:
> 
> Sentence fragment.
> 
> -- 5.9, 2nd to last paragraph:
> 
> s/"In case the"/"In the case that the"
> 
> -- 9:
> 
> A general discussion of threats would be helpful. Some aspects are scattered
> in the subsections, but a summary in one place would be nice.
> 
> -- 9.2: 
> 
> It's not clear to me if the text in the "Dictionary Attack" section is
> actually related to dictionary attacks.
> 
> 
> -- 6.1:
> 
> A picture of the general packet format would be nice. You've got them later
> for specific packet types, but no "general" picture.
> 
> --6.2: 
> 
> Section seems mostly redundant to 6.1
> 
> -- 6.3:
> 
> Please expand HoTI on first use.
> 
> -- 7:
> 
> Please expand CoTI/CoT on first use
> 
> -- 8.3:
> 
> I'm not sure I understand the mnemonic relevance of "HALTSEC"
> 
> 
> 
> 
> 


From vincent.roca@inria.fr  Wed Feb 29 07:53:59 2012
Return-Path: <vincent.roca@inria.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 DC38E21F86E8 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 07:53:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.916
X-Spam-Level: 
X-Spam-Status: No, score=-109.916 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T72mDpApCCxy for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 07:53:58 -0800 (PST)
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by ietfa.amsl.com (Postfix) with ESMTP id E266721F8679 for <ietf@ietf.org>; Wed, 29 Feb 2012 07:53:57 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.73,503,1325458800"; d="scan'208";a="133641772"
Received: from geve.inrialpes.fr ([194.199.24.116]) by mail4-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 29 Feb 2012 16:53:56 +0100
Subject: Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <CB72DAA8.19D17%ietfdbh@comcast.net>
Date: Wed, 29 Feb 2012 16:53:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
References: <CB72DAA8.19D17%ietfdbh@comcast.net>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 29 Feb 2012 08:07:53 -0800
Cc: rmt-chairs@tools.ietf.org, draft-ietf-rmt-flute-revised@tools.ietf.org, ietf@ietf.org, Rod Walsh <roderick.walsh@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 15:54:00 -0000

Hello Julian,


>> I note that draft-ietf-rmt-flute-revised is on the agenda. Just =
wanted
>> to note that I haven't seen any feedback to my LC comments on the
>> ietf-discuss mailing list...

I didn't see you initial email (I'm not not on the ietf@ietf.org mailing =
list), which explains
why you didn't receive any feedback.

---
Co-authors: there are a few comments for which I'd appreciate to have =
your input.
They are prefixed with: "=3D> Co-authors".
---

>> Here are a few comments, mainly of editorial nature:
>>=20
>> Below my review notes; just mechanical checks, and some checks on the
>> relation to HTTP header fields...:
>>=20
>> Section 3:
>>=20
>> "File name (usually, this can be concluded from the URI). In the =
above
>> example: "file.txt"."
>>=20
>> ...or the Content-Disposition header field (RFC 6266).

VR: The sender can freely choose a solution to convey the filename. We
suggest to use the URI to that purpose. What you suggest =
(Content-Disposition)
is an alternative. Current text seems to be appropriate in the sense =
that:
1- it only suggests one solution;
2- it does not close the door, and using another solution remains valid;
I'm also a little bit confused by what RFC6266 / RFC2616 say, namely =
that
Content-Disposition is not part of HTTP/1.1.

My feeling is to let the text as it is today. If anybody else has a =
different opinion...


>> "File type, expressed as MIME media type. In the above example:
>> "text/plain"."
>>=20
>> s/MIME media type/internet media type/

VR: okay, Internet media type is indeed the appropriate term. Corrected.

NEW:
          File type, expressed as Internet Media Types (often
          referred to as "MIME Media Types"). In the above example: =
"text/plain".


>> 3.4.2:
>>=20
>> "Where the MD5 message digest is described, the attribute =
"Content-MD5"
>> MUST be used for the purpose as defined in [RFC2616]."
>>=20
>> Note that Content-MD5 is gone from HTTPbis.

VR: We are not using MD5 message digest to protect ourselves from
deliberate attacks, but only as a reasonable way to be confident of the
decoded object integrity WRT transmission or FLUTE/ALC processing
errors. The probability of message digest collision is in that case so
small it makes sense to still use it for that purpose.

Additionally, "Content-MD5" is part of the 3GPP MBMS Rel.6 =
specifications.
Removing it altogether from the FLUTE-revised document would be an
error from a backward compatibility point of view, even if we know that
this version is not backward compatible.

My feeling is to leave it as it is to minimize differences WRT to =
RFC3926.


>> XML-Schema: I believe the spec should state what to do with invalid
>> input. Are there extension points (like ignoring unknown elements in
>> extension namespaces)?

VR: it seems reasonable, indeed. I'd like to hear other opinions.
What about the following text (last sentence is added)?

NEW:
         Any valid FDT Instance MUST use the above XML Schema. This way
          FDT provides extensibility to support private attributes =
within the
          file description entries. Those could be, for example, the
          attributes related to the delivery of the file (timing, packet
          transmission rate, etc.). Unsupported private attributes =
SHOULD be
          silently ignored by a FLUTE receiver.

=3D> Co-authors, do you agree?


>> "It is RECOMMENDED that the new attributes applied in the FDT are in =
the
>> format of MIME fields and are either defined in the HTTP/1.1
>> specification [RFC2616] or another well-known specification."
>>=20
>> As this is a normative requirement it needs to be clarified what =
header
>> fields are used? HTTP? MIME?

VR: Sorry, I don't understand the point (my HTTP/MIME understanding
is probably too limited).


>> Also, well-known is irrelevant, we have a registry for header fields.

VR: Right. I've added a pointer to the IANA Internet Media Type registry
and an informative reference. However I prefer to keep the "or another
well-known specification" part of the sentence, since removing it might
create issues.

NEW:
   It is RECOMMENDED that the new attributes applied in the FDT are in =
the=20
   format of MIME fields and are either defined in the HTTP/1.1
   specification [RFC2616], or another well-known specification, or in
   IANA registry [IANAmediatypes].

NEW reference:
   [IANAmediatypes]
              IANA, "IANA Media Types registry",
              URL: http://www.iana.org/assignments/media-types/.


>> 8.1:
>>=20
>> Actually, what's requested is a URN for the XML namespace
>> ("urn:ietf:params:xml:ns:fdt"). That's fine; I don't think the XML
>> schema needs to be registered. Otherwise, see
>> <http://tools.ietf.org/html/rfc3688#section-3.2>.

VR: So we keep it as it is. That's what you mean?


>> 8.2:
>>=20
>> Has the media type registration been reviewed on ietf-types?

VR: I cannot answer.
=3D> Co-authors, can you say what has been done (or not)?


>> 8.3:
>>=20
>> You need to define the IANA procedure (see RFC 5226).

VR: We received several comments from IANA. I'll address them all
globally.


>> Appendix B:
>>=20
>> The example contains a schemaLocation with a relative (URI) reference
>> ("ietf-flute-fdt.xsd"). That's misleading, right?

VR: I cannot answer (not in my field of expertise).
=3D> Co-authors, what do you suggest to address this comment?


>> References:
>>=20
>> Please cite W3C spec with their full details, like this:
>>=20
>> =
<http://greenbytes.de/tech/webdav/rfc2629xslt/w3c-references.html#ref-REC-=

>> xmlschema-1-20010502>
>>=20
>> Speaking of which; shouldn't you cite the Second Edition?

VR: Done, I've added URL for these two documents, and we now refer to =
the
Second Edition. I think FLUTE usage of XML Schema is simple enough not
to be broken by the Second Edition of these documents.


>> [RMT-SIMPLE-AUTH]: this should be cited using the default ID style, =
in
>> which case xml2rfc will add the helpful "work-in-progress" label

VR: my Simple-Auth document is already in the RFC Ed Queue, so it will
soon be assigned an RFC number...


>> Should RFC2357 be in the references?

VR: It makes sense since it is referenced. Added as an Informative =
Reference.


>> You may want to cite RFC3986 (URI).

VR: Added as an Informative Reference.


>> Formatting: I note that in-document links haven't been generated =
using
>> xml2rfc's linking features; this way references to section numbers =
can
>> break easily. I did not check those.
>>=20
>> Best regards, Julian

Thanks a lot for your detailed review. That's helpful.
Cheers,

   Vincent


NB: I've added Rod separately to the CC list. Please keep it since his =
previous
email address is no longer valid and the draft-ietf-rmt-flute-revised =
alias will only
be updated after I've submitted version -14 of this I-D.=

From sm@resistor.net  Wed Feb 29 08:54:08 2012
Return-Path: <sm@resistor.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 58D3721F86C4 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 08:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Level: 
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4oaaWJ8q9QW for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 08: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 9EA8821F8684 for <ietf@ietf.org>; Wed, 29 Feb 2012 08:54:04 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q1TGrwwQ027009 for <ietf@ietf.org>; Wed, 29 Feb 2012 08:54:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330534444; i=@resistor.net; bh=QfLJ7To4yRpa8CgRUh3nMACNR7oemeG69tVi0pozS4E=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=VaD5Uohjq3OafDLZFjxkQbKRfsdvqFbKIrF1iQn4v5JCrp39BUa8pRcWsuVMhu/M3 /NV6vymftCCfBIa+LzLTJ/f8FR+H79YQVI/YAVpgw5hQ7RfBX99PKw6eA8ZynXeTbw J/1sbDWRep64E79FWPqotQo49n9BpBWknzMIC2CM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330534444; i=@resistor.net; bh=QfLJ7To4yRpa8CgRUh3nMACNR7oemeG69tVi0pozS4E=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=iyKibsj3R61iVLL+1wKyVeQLinivkzq4XlNiOC65UMWKUYHwGm2UKgb1aAU9qemEe /iSNliTmk1gg/AoawBMOZy6Z5CehlW8itVgdfyRjEsAaUPyx7FFUJ6Ufgk3rDV/hu1 /gjg9fAlv9WM0q8+OxHYGAb10bGF6CC+pRr42zd0=
Message-Id: <6.2.5.6.2.20120229083209.0a4b6268@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 Feb 2012 08:53:01 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
In-Reply-To: <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
References: <CB72DAA8.19D17%ietfdbh@comcast.net> <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 16:54:08 -0000

At 07:53 29-02-2012, Vincent Roca wrote:
>I didn't see you initial email (I'm not not on the ietf@ietf.org 
>mailing list), which explains why you didn't receive any feedback.

That explains why the authors did not respond to the comments.  It 
does not explain why the working group asked the IETF Community to 
review the draft.  Or is the working group using ietf@ as a 
unidirectional transport? :-)

 From the Introduction Section:

   "This document defines FLUTE version 2, a protocol for unidirectional
    delivery of files over the Internet.  This specification is not
    backwards compatible with the previous experimental version defined
    in [RFC3926]"

The Write-up mentions that this draft represents the solid consensus 
of the working group.  It also mentions that "The document is of high 
quality and has been subject to extensive review in its Internet 
Draft and Experimental RFC forms.  The revised draft represents a 
modest set of changes from the original Experimental RFC 3926.  These 
changes are clearly described in the document".  This "modest set of 
changes" affects the IPR status of the document.  The question which 
one might ask is why do a modest set of changes then.

Regards,
-sm 


From presnick@qualcomm.com  Wed Feb 29 10:03:38 2012
Return-Path: <presnick@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 5C7ED21F8705 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 10:03:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.273
X-Spam-Level: 
X-Spam-Status: No, score=-106.273 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mHky8fdyzpeJ for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 10:03:35 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA4321F86D3 for <ietf@ietf.org>; Wed, 29 Feb 2012 10:03:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1330538615; x=1362074615; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F4E686F.2050404@qualcomm.com>|Date:=20We d,=2029=20Feb=202012=2013:03:27=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20t.petch=20<daedulus@btconnect. com>|CC:=20IETF-Discussion=20list=20<ietf@ietf.org> |Subject:=20Re:=20Conclusion=20of=20Last=20Call=20for=20d raft-ietf-sieve-convert=09anddraft-ietf-sieve-notify-sip- message|References:=20<4F43FF5C.6060003@qualcomm.com>=20< 00b201ccf6c2$46a7eb80$4001a8c0@gateway.2wire.net> |In-Reply-To:=20<00b201ccf6c2$46a7eb80$4001a8c0@gateway.2 wire.net>|Content-Type:=20text/plain=3B=20charset=3D"ISO- 8859-1"=3B=20format=3Dflowed|Content-Transfer-Encoding: =207bit|X-Originating-IP:=20[172.30.39.5]; bh=imr9CKWG6keUjRLMsqrHnDLXeL0dzjOPiWxQdwnMk7k=; b=H/iAZvDepoNbfohWf8AsMKvVx+5U+osil4D+bd5sscc2TvKjOkF/uK6F j9yqkY6IJYvO4lQSMNytmW+9lIJuqsVVZ5dS+dgNI70Ht6UyQO2QMNHoI Q7YmxeIgCmkKz2WYYPh178m2qXOl7yw04Am9UIU4OkoLDKxhSxh8h0Ake o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6634"; a="167585829"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine01.qualcomm.com with ESMTP; 29 Feb 2012 10:03:34 -0800
X-IronPort-AV: E=Sophos;i="4.73,502,1325491200"; d="scan'208";a="119500433"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 29 Feb 2012 10:03:34 -0800
Received: from Macintosh-4.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Wed, 29 Feb 2012 10:03:33 -0800
Message-ID: <4F4E686F.2050404@qualcomm.com>
Date: Wed, 29 Feb 2012 13:03:27 -0500
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: t.petch <daedulus@btconnect.com>
Subject: Re: Conclusion of Last Call for draft-ietf-sieve-convert	anddraft-ietf-sieve-notify-sip-message
References: <4F43FF5C.6060003@qualcomm.com> <00b201ccf6c2$46a7eb80$4001a8c0@gateway.2wire.net>
In-Reply-To: <00b201ccf6c2$46a7eb80$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 18:03:38 -0000

Good idea. I've added a comment to the tracker in the History section 
for both documents.

pr

On 2/29/12 4:12 AM, t.petch wrote:
> Pete
>
> I agree with what you have done but would like to see it recorded in something
> more accessible than an e-mail archive.  Could it be added to the data tracker,
> under IESG evaluation or IESG writeup or some such?
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "Pete Resnick"<presnick@qualcomm.com>
> To: "IETF-Discussion list"<ietf@ietf.org>
> Sent: Tuesday, February 21, 2012 9:32 PM
>    
>> I wanted to inform the community of the results of the second Last Call
>> issued for draft-ietf-sieve-convert and
>> draft-ietf-sieve-notify-sip-message. To remind you of the circumstances:
>> After these two documents were approved by the IESG and sent on to the
>> RFC Editor, an IPR disclosure was made pertaining to each of them
>> indicating that one of the document editors for both documents was also
>> the listed inventor for the disclosed patent. The disclosures were made
>> by the document editor's employer and indicate that the date of the
>> patent filings was prior to the adoption of these two drafts by the
>> SIEVE working group. The RFC Editor was asked to suspend their work on
>> the documents, and a second Last Call was made.
>>
>> After reviewing discussions in the SIEVE WG and on the IETF mailing
>> list, the chairs have decided (and I support) that, because of the
>> failure to disclose the IPR as required by BCP 79 (RFC 3979), and as per
>> RFC 2418 Section 6.1, the following actions are appropriate and will be
>> taken:
>>
>> - The document editor in question is no longer a document editor for
>> these two documents.
>> - The person's name will be removed from the front page of the documents
>> and from the Authors' Address section.
>> - The person's name will be added to the Acknowledgments section of both
>> documents to identify that he did contribute text to the drafts.
>> - The RFC Editor will be asked to continue processing and publication of
>> these drafts as RFCs.
>>
>> We will be notifying the RFC Editor of this decision presently.
>>
>> Meanwhile, the employer of the document editor in question has made
>> followup disclosures on each of the documents, saying that they
>> "covenant not to assert any such claim against any party for making,
>> using, selling, offering for sale or importing a product that implements
>> the corresponding part of the specification." The full text of the
>> disclosures can be seen here:
>>
>> https://datatracker.ietf.org/ipr/1680/
>> https://datatracker.ietf.org/ipr/1681/
>>
>> pr
>>
>> --
>> Pete Resnick<http://www.qualcomm.com/~presnick/>
>> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
>>
>>      
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>    

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From julian.reschke@gmx.de  Wed Feb 29 13:18:36 2012
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 79F0921E8069 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 13:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.236
X-Spam-Level: 
X-Spam-Status: No, score=-104.236 tagged_above=-999 required=5 tests=[AWL=-1.637, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Jn0FBCljihg for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 13:18:35 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id C204E21E805C for <ietf@ietf.org>; Wed, 29 Feb 2012 13:18:34 -0800 (PST)
Received: (qmail invoked by alias); 29 Feb 2012 21:18:33 -0000
Received: from p3EE26EBB.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.110.187] by mail.gmx.net (mp039) with SMTP; 29 Feb 2012 22:18:33 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/fecUu3G7fQcXhjFeMjzRb+haMN9FqFU+4J2yxtg m1w3KUSD23Ghux
Message-ID: <4F4E961C.7080302@gmx.de>
Date: Wed, 29 Feb 2012 22:18:20 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Vincent Roca <vincent.roca@inria.fr>
Subject: Re: Last Call: <draft-ietf-rmt-flute-revised-13.txt> (FLUTE - File Delivery over Unidirectional Transport) to Proposed Standard
References: <CB72DAA8.19D17%ietfdbh@comcast.net> <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
In-Reply-To: <767A8227-173E-4C87-B597-E93D1882FDEF@inria.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: rmt-chairs@tools.ietf.org, draft-ietf-rmt-flute-revised@tools.ietf.org, ietf@ietf.org, Rod Walsh <roderick.walsh@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Feb 2012 21:18:36 -0000

On 2012-02-29 16:53, Vincent Roca wrote:
> Hello Julian,
>
>
>>> I note that draft-ietf-rmt-flute-revised is on the agenda. Just wanted
>>> to note that I haven't seen any feedback to my LC comments on the
>>> ietf-discuss mailing list...
>
> I didn't see you initial email (I'm not not on the ietf@ietf.org mailing list), which explains
> why you didn't receive any feedback.

Well, you don't need to be on the mailing list, but you certainly should 
scan the mailing list archives. After all, this is the place where the 
Last Call asks for feedback.

> ---
> Co-authors: there are a few comments for which I'd appreciate to have your input.
> They are prefixed with: "=>  Co-authors".
> ---
>
>>> Here are a few comments, mainly of editorial nature:
>>>
>>> Below my review notes; just mechanical checks, and some checks on the
>>> relation to HTTP header fields...:
>>>
>>> Section 3:
>>>
>>> "File name (usually, this can be concluded from the URI). In the above
>>> example: "file.txt"."
>>>
>>> ...or the Content-Disposition header field (RFC 6266).
>
> VR: The sender can freely choose a solution to convey the filename. We
> suggest to use the URI to that purpose. What you suggest (Content-Disposition)
> is an alternative. Current text seems to be appropriate in the sense that:
> 1- it only suggests one solution;
> 2- it does not close the door, and using another solution remains valid;
> I'm also a little bit confused by what RFC6266 / RFC2616 say, namely that
> Content-Disposition is not part of HTTP/1.1.

RFC 6266 has registered Content-Disposition as header field for HTTP. As 
such, it overrides anything that 2616 said about it.

That being said; it's advisory only, but I thought it might be 
worthwhile to mention.

> My feeling is to let the text as it is today. If anybody else has a different opinion...
>
>
>>> "File type, expressed as MIME media type. In the above example:
>>> "text/plain"."
>>>
>>> s/MIME media type/internet media type/
>
> VR: okay, Internet media type is indeed the appropriate term. Corrected.
>
> NEW:
>            File type, expressed as Internet Media Types (often
>            referred to as "MIME Media Types"). In the above example: "text/plain".
>
>
>>> 3.4.2:
>>>
>>> "Where the MD5 message digest is described, the attribute "Content-MD5"
>>> MUST be used for the purpose as defined in [RFC2616]."
>>>
>>> Note that Content-MD5 is gone from HTTPbis.
>
> VR: We are not using MD5 message digest to protect ourselves from
> deliberate attacks, but only as a reasonable way to be confident of the
> decoded object integrity WRT transmission or FLUTE/ALC processing
> errors. The probability of message digest collision is in that case so
> small it makes sense to still use it for that purpose.
>
> Additionally, "Content-MD5" is part of the 3GPP MBMS Rel.6 specifications.
> Removing it altogether from the FLUTE-revised document would be an
> error from a backward compatibility point of view, even if we know that
> this version is not backward compatible.
>
> My feeling is to leave it as it is to minimize differences WRT to RFC3926.
>
>
>>> XML-Schema: I believe the spec should state what to do with invalid
>>> input. Are there extension points (like ignoring unknown elements in
>>> extension namespaces)?
>
> VR: it seems reasonable, indeed. I'd like to hear other opinions.
> What about the following text (last sentence is added)?
>
> NEW:
>           Any valid FDT Instance MUST use the above XML Schema. This way
>            FDT provides extensibility to support private attributes within the
>            file description entries. Those could be, for example, the
>            attributes related to the delivery of the file (timing, packet
>            transmission rate, etc.). Unsupported private attributes SHOULD be
>            silently ignored by a FLUTE receiver.
>
> =>  Co-authors, do you agree?

So any undefined attributes should be ignored. What about undefined 
elements?

>>> "It is RECOMMENDED that the new attributes applied in the FDT are in the
>>> format of MIME fields and are either defined in the HTTP/1.1
>>> specification [RFC2616] or another well-known specification."
>>>
>>> As this is a normative requirement it needs to be clarified what header
>>> fields are used? HTTP? MIME?
>
> VR: Sorry, I don't understand the point (my HTTP/MIME understanding
> is probably too limited).

HTTP header fields and MIME header fields are not the same thing. Pick one.

>>> Also, well-known is irrelevant, we have a registry for header fields.
>
> VR: Right. I've added a pointer to the IANA Internet Media Type registry
> and an informative reference. However I prefer to keep the "or another
> well-known specification" part of the sentence, since removing it might
> create issues.

Such as?

> NEW:
>     It is RECOMMENDED that the new attributes applied in the FDT are in the
>     format of MIME fields and are either defined in the HTTP/1.1
>     specification [RFC2616], or another well-known specification, or in
>     IANA registry [IANAmediatypes].

"MIME fields" isn't a term used in the IETF. (see above).

> NEW reference:
>     [IANAmediatypes]
>                IANA, "IANA Media Types registry",
>                URL: http://www.iana.org/assignments/media-types/.
>
>
>>> 8.1:
>>>
>>> Actually, what's requested is a URN for the XML namespace
>>> ("urn:ietf:params:xml:ns:fdt"). That's fine; I don't think the XML
>>> schema needs to be registered. Otherwise, see
>>> <http://tools.ietf.org/html/rfc3688#section-3.2>.
>
> VR: So we keep it as it is. That's what you mean?

No, you need to rephrase the request. You're asking for a namespace 
name, not a schema URI.

>>> 8.2:
>>>
>>> Has the media type registration been reviewed on ietf-types?
>
> VR: I cannot answer.
> =>  Co-authors, can you say what has been done (or not)?
>
>
>>> 8.3:
>>>
>>> You need to define the IANA procedure (see RFC 5226).
>
> VR: We received several comments from IANA. I'll address them all
> globally.
>
>
>>> Appendix B:
>>>
>>> The example contains a schemaLocation with a relative (URI) reference
>>> ("ietf-flute-fdt.xsd"). That's misleading, right?
>
> VR: I cannot answer (not in my field of expertise).
> =>  Co-authors, what do you suggest to address this comment?
>
>
>>> References:
>>>
>>> Please cite W3C spec with their full details, like this:
>>>
>>> <http://greenbytes.de/tech/webdav/rfc2629xslt/w3c-references.html#ref-REC-
>>> xmlschema-1-20010502>
>>>
>>> Speaking of which; shouldn't you cite the Second Edition?
>
> VR: Done, I've added URL for these two documents, and we now refer to the
> Second Edition. I think FLUTE usage of XML Schema is simple enough not
> to be broken by the Second Edition of these documents.
>
>
>>> [RMT-SIMPLE-AUTH]: this should be cited using the default ID style, in
>>> which case xml2rfc will add the helpful "work-in-progress" label
>
> VR: my Simple-Auth document is already in the RFC Ed Queue, so it will
> soon be assigned an RFC number...
>
>
>>> Should RFC2357 be in the references?
>
> VR: It makes sense since it is referenced. Added as an Informative Reference.
>
>
>>> You may want to cite RFC3986 (URI).
>
> VR: Added as an Informative Reference.
>
>
>>> Formatting: I note that in-document links haven't been generated using
>>> xml2rfc's linking features; this way references to section numbers can
>>> break easily. I did not check those.
>>>
>>> Best regards, Julian
>
> Thanks a lot for your detailed review. That's helpful.
> Cheers,
>
>     Vincent
>
>
> NB: I've added Rod separately to the CC list. Please keep it since his previous
> email address is no longer valid and the draft-ietf-rmt-flute-revised alias will only
> be updated after I've submitted version -14 of this I-D.

Best regards, Julian


From dwing@cisco.com  Wed Feb 29 18:56:33 2012
Return-Path: <dwing@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 31ED821E8080; Wed, 29 Feb 2012 18:56:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.885
X-Spam-Level: 
X-Spam-Status: No, score=-108.885 tagged_above=-999 required=5 tests=[AWL=1.714, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrAUUHj4RaqQ; Wed, 29 Feb 2012 18:56:32 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id E441921E801E; Wed, 29 Feb 2012 18:56:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=3434; q=dns/txt; s=iport; t=1330570586; x=1331780186; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=1LauwGOPKzwS6/4rBFU5vyM6YZxu5x1yVcOAi3w9J7Q=; b=VP+lgIMfcUJG0dhn74wLXDL4uj2Tx/WH+CbBhYdgRd1yMfuuE6b2R4ni BJMxfihB681XwavfCHeiTN/N08S/fnzcTNHluegJ5QJILAhExAgFvmBak sGCCeLs8laRefLCmL4xJeI6CCDkswvOBrJq9cL3aFDXDuvpY5dU2KU4RY Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FACrkTk+rRDoH/2dsb2JhbABDpC2PW4EHggEICgEXED8NBRhQIxwBBBMLF4dmoF8BlyiMfwMBDwsBAQoFAgJBAQEDDAsBAYUChCQEiE+FB5p7
X-IronPort-AV: E=Sophos;i="4.73,507,1325462400"; d="scan'208";a="31213932"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 01 Mar 2012 02:56:26 +0000
Received: from dwingWS ([10.32.240.195]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q212uQ1s008363; Thu, 1 Mar 2012 02:56:26 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'IETF discussion list'" <ietf@ietf.org>
Subject: tsv-dir review of draft-garcia-shim6-applicability-03
Date: Wed, 29 Feb 2012 18:56:26 -0800
Message-ID: <023f01ccf756$e4d4a110$ae7de330$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acz3VuR9N7pidru3QMmf+hQbv6UdHw==
Content-Language: en-us
Cc: 'marcelo bagnulo braun' <marcelo@it.uc3m.es>, joe.abley@icann.org, tsv-area@ietf.org, alberto@it.uc3m.es, 'Transport Directorate' <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2012 02:56:33 -0000

I have 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-dir@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.



Nits:

Section 1:

   Such problems are not specific of Shim6, but
   are suffered by the hosts of any site which is connected to multiple
   transit providers, and which receives an IPv6 prefix from each of the
   providers.

It might be useful to add a non-normative reference to RFC5220 at the end of
that sentence.


Section 3.4:

   The use of HBA is more efficient in the sense that addresses require
   less computation than CGA, involving only hash operations for both
   the generation and the verification of locator sets.  However, the
   locators of an HBA set are determined during the generation process,
   and cannot be subsequently changed; the addition of new locators to
   that initial set is not supported, except by re-generation of the
   entire set which will in turn cause all addresses to change.

I think that paragraph is too harsh, as it implies the old addresses
have to be invalidated immediately.  I expect existing connections 
could continue with the old addresses, and, if the host wanted to, 
could even have new connections use the old addresses.  If that
is not possible, the draft should explain why.  If that is possible,
the draft should probably explain it is possible.


Section 4:

   In order to configure source and destination address selection, tools
   such as DHCPv6 can be used to disseminate a [RFC3484] policy table to
   a host.

It might be useful to add a non-normative reference to
draft-ietf-6man-addr-select-opt.


Section 4:

The sentence ending with "properties exhibited by REAP." needs a reference
to RFC5544, which seems to be the RFC defining REAP.



Section 7.7, "Shim6 and IPv6 NAT", the problem could be overcome by the
Shim6 node knowing its IPv6 address after NPTv6 translation.  Probably not
worth adjusting the document, though, as NPTv6 is experimental.


Section 7.7:

   Note that an Application Level Gateway designed to modify the Shim6
   control packets would not be able to generate a valid signature, in
   case a CGA is being used, or a Parameter Data Structure binding the
   translated locator to the other locators of a node, in case a HBA is
   being used.  Therefore, the same failure cases described before would
   remain.

Applications are layer 7, Shim6 is layer 3, so an "Application Layer
Gateway" that modifies Shim6 control packets seems an abuse of terminology.
Suggest: 

OLD:
   Note that an Application Level Gateway designed to modify the Shim6
   control packets would not be able to generate a valid signature, in   
NEW:
   Note that modification of the Shim6 control packets by the IPv6 NAT 
.............^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   would not be able to generate a valid signature, in

-d










From msk@cloudmark.com  Wed Feb 29 20:43:03 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF71221E8021 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 20:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hh4J3ecY2x2z for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 20:43:03 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id 239EC21E801E for <ietf@ietf.org>; Wed, 29 Feb 2012 20:43:03 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Wed, 29 Feb 2012 20:43:02 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
Thread-Topic: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
Thread-Index: AQHM90Qw9jaKWnzEBEidAEU8BJyAyZZU1DUQ
Date: Thu, 1 Mar 2012 04:43:01 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392806E6F5@exch-mbx901.corp.cloudmark.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>
In-Reply-To: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [67.160.203.60]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "alexey.melnikov@isode.com" <alexey.melnikov@isode.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2012 04:43:03 -0000

I have several comments on this draft.  But first, this is a big improvemen=
t since the last version I reviewed, so kudos to the authors.

A couple of these refer to issues in the document that need to be resolved =
before it can move forward, but you probably already know what they are.  T=
he rest are not showstoppers.  It could also use a quick editorial pass, wh=
ich I'm happy to do for you separately if you like.

- Section 3, bullet 7: LTMP -> LMTP

- Section 4.1 contains a reference to "esmtp-values" which looks like an AB=
NF terminal, but it's not explained.  Did you mean an ABNF terminal, or did=
 you mean something about ESMTP parameters?

- Section 4.2, bullet 2: "Section 6" should probably be in parentheses, pro=
bably preceded by "see"

- There's a bunch of TBDs that still need to be resolved before this docume=
nt moves forward (X.7.TBD3 as an enhanced status code, for example)

- Section 4.2 makes reference to "the Minimize condition" but the document =
doesn't otherwise define it

- Section 4.3 says "For example, once an MTA accepts a message, the MTA MUS=
T NOT change a (syntactically valid) priority value if the MTA doesn't supp=
ort it."  There seems to be a chicken-and-egg going on here: If the MTA doe=
sn't support the extension, how can it know not to change the priority outb=
ound?

- There are lots of SHOULDs in here that might benefit from example situati=
ons in which one might deviate from the normative statement containing the =
SHOULD.

- Section 5 and Section 5.1 use "not required", "should", and "may" where R=
FC2119 is cited earlier.  Should they be in all-caps, or should other langu=
age be selected?

- Section 5: "Irrespectively on" -> "Irrespective of"

- Section 5: "fine grainer control" -> "finer-grained control"

- Section 5.1 makes reference to "the work-in-progress effort extension to =
RSVP that prioritizes reservations."  This should include a citation even i=
f it references an I-D that's not published yet.

- Section 9: "it is advised that all or none of them SHOULD support the PRI=
ORITY extension" sounds awfully mushy.  I suggest dropping the SHOULD, and =
rather say something like "it is advised that either all of them support th=
e PRIORITY extension, or none do".

- Section 10 should be resolved before the document advances.

- Section 11: Why use "PRI" and not "priority"?  The existing set of Receiv=
ed clause names are lowercase words, so it seems strange to deviate.

- Appendix A: Can STANAG 4406 be listed in the Informative References?

- Appendix D: "This appendix and its subsections are informative."  I think=
 that (a) any appendix is informative, because normative text doesn't belon=
g in an appendix; and (b) the normative stuff uses RFC2119 language and thi=
s doesn't.  Thus, I think this sentence should be removed.  (I know I've lo=
st this argument before, but I'll make another stand here anyway.)

-MSK

From sm@resistor.net  Wed Feb 29 22:35:43 2012
Return-Path: <sm@resistor.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 7C17121E8038 for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 22:35:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.648
X-Spam-Level: 
X-Spam-Status: No, score=-102.648 tagged_above=-999 required=5 tests=[AWL=-0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nw9htabgjcQI for <ietf@ietfa.amsl.com>; Wed, 29 Feb 2012 22:35:41 -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 4F6BF21F8554 for <ietf@ietf.org>; Wed, 29 Feb 2012 22:35:41 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q216ZV8f019406 for <ietf@ietf.org>; Wed, 29 Feb 2012 22:35:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330583739; i=@resistor.net; bh=w2CUS8cFmIF+GMDUxX1qdfEvACdK8TldZyPNXWmBvyA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=BnvEz4Zf4mOfjO+7LzZIcTasmo+nxAWJKMXRPozpAaxlNDeboW5Dclby4QpQViaA6 ozBcRUy+0HeDzPGSi7FXTa2WlAi2ajAA/gIv6u/uPNCQA3umBTlh/HyG+iUgnY4eLr 1lY9JX3QxmZctuFAtcXgIZfM78OCJzNRdkyEs8XI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330583739; i=@resistor.net; bh=w2CUS8cFmIF+GMDUxX1qdfEvACdK8TldZyPNXWmBvyA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=xxT9ocCWzm6oGxNLLMPqngbEYoZ7m/q2t8P7cObol982teGDyGMJqjdbO7wMMQOqI uTdXsP1Ypkh6ebZqDIhSwiQDbESpHhJ/dQ3KdC7uwap3+Hv/WbRvDvHNCbRGODV48S dUhDTAftAjw1Wo6nFlzSKToktZ7cXp8C1nx6f2UI=
Message-Id: <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 Feb 2012 22:26:41 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
In-Reply-To: <20120301004643.17274.83943.idtracker@ietfa.amsl.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Mar 2012 06:35:43 -0000

At 16:46 29-02-2012, The IESG wrote:
>The IESG has received a request from the Messaging Abuse Reporting Format
>WG (marf) to consider the following document:
>- 'SPF Authentication Failure Reporting using the Abuse Report Format'
>   <draft-ietf-marf-spf-reporting-08.txt> as a 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 2012-03-14. Exceptionally, comments may be

[snip]

>Note that this document has a downward normative reference: This 
>document makes a normative reference to SPF (RFC4408), which is Experimental.

The MARF charter [1] does not contain any mention of "SPF 
Authentication Failure Reporting using the Abuse Report Format" as a 
deliverable.  There is no mention of SPF in the charter.

According to the Abstract Section of this document:

   "This memo presents extensions to the Abuse Reporting Format (ARF),
    and Sender Policy Framework (SPF) specifications to allow for
    detailed reporting of message authentication failures in an on-demand
    fashion."

This extends a specification on which there hasn't been any 
conclusion yet.  I note that there is a downward normative reference 
to RFC 4408.  During discussions about RFC 4408, on which I don't 
have any opinion up to now, there have been comments about:

  (i)   The specification not being sufficiently clear.

  (ii)  A compelling case that there is, indeed, an error in RFC4408.

  (iii) Interoperability problems in the protocol due to DNS "incompatibility".

I suggest that the IETF waits for a migration or co-existence 
document which discusses about the non-standards track protocol on 
which there is a downward reference.

I'll avoid commenting on the technical angle.  Here are some 
editorial comments:

In Section 3:

   "There exist cases in which a domain name owner employing [SPF] for
    announcing sending practices may want to know when messages are
    received via unauthorized routing."

I suggest not using the term "domain name owner" to side-step the 
question of domain "ownership".

   "particular because a message arrived via an unauthorized route.
    To generate a complete address to which the report is sent, the
    verifier simply appends to this value an "@" followed by the
    SPF domain per paragraph 4.1 of [SPF]."

RFC 4408 uses the term "SPF-compliant domain".

In Section 5.1:

   "New registrations or updates MUST be published in accordance with the
    "Specification Required" guidelines as described in
    [IANA-CONSIDERATIONS].  New registrations and updates MUST contain
    the following information:"

I suggest not using RFC 2119 key words in the IANA Considerations 
section unless there are interoperability issues with IANA.

   "current:  The field is in current use

    deprecated:  The field is in current use but its use is
       discouraged"

The difference in "current use" can end up being problematic for the 
designated expert.

In Section 6:

  "Security issues with respect to these reports are similar to those
   found in [DSN]."

The reference to DSN could be normative.

   "The HELO/EHLO command SHOULD also be selected so that it
    will pass [SPF] HELO checks."

I could not understand what to do about the above 
recommendation.  FWIW, the command is specified in RFC 5321.  That 
specification is not referenced by this draft.

Regards,
-sm

1. https://datatracker.ietf.org/wg/marf/charter/ 

