
From ron.even.tlv@gmail.com  Tue Feb  1 00:28:10 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 595B03A6B58; Tue,  1 Feb 2011 00:28:10 -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.799,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FiRKbXfTwZ24; Tue,  1 Feb 2011 00:28:06 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 59DAB3A6B07; Tue,  1 Feb 2011 00:28:05 -0800 (PST)
Received: by wwa36 with SMTP id 36so7230658wwa.13 for <multiple recipients>; Tue, 01 Feb 2011 00:31:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=rdHpqHA2YZVxRjUpKk39INTaJTzST89lyxxfZB2QAgU=; b=P9jbpV33VhSyT8pp5uXSxXuhTDjgBDYLyJUF2SbY5ePcQURbxqTY7uc1E8a0E/Zpfq FBx5V2P9shEDCFBg4eBOJxJSreReJHcxIWVHhfi4SvPcxIIAbm/Y0LgwNAQiYcibaL4Q 3ruqcmCTepUT01mNjSJeSXUS58mGDyg/DGH7E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=Mu1gZCY5RbhzN17uycX37MUtatbCgNNcxi2WWZ3/FO+lkS8+fnJc3Ana/ZDudW7S0B 2rK24DbUtW05oOjpZd/m4rc8MqLHWocB0tI39RhbLD6jez4AWrA2eFXPtYYrcaB8Ccm+ MZOell52UQSrIHiJwMenKYVRYcrP2VK49EP+Q=
Received: by 10.216.78.146 with SMTP id g18mr7029003wee.1.1296549081093; Tue, 01 Feb 2011 00:31:21 -0800 (PST)
Received: from windows8d787f9 (bzq-79-183-9-180.red.bezeqint.net [79.183.9.180]) by mx.google.com with ESMTPS id r38sm11301527weq.47.2011.02.01.00.31.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 01 Feb 2011 00:31:19 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-shim6-multihome-shim-api.all@tools.ietf.org>, <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-ietf-shim6-multihome-shim-api-15
Date: Tue, 1 Feb 2011 10:27:24 +0200
Message-ID: <4d47c4d7.26ead80a.186e.4528@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0017_01CBC1FA.9FC36A80"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvB6doMMrQL3L4zQvuG+R35xXc7rA==
Content-Language: en-us
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 08:28:10 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01CBC1FA.9FC36A80
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-shim6-multihome-shim-api-15

Reviewer: Roni Even

Review Date:2011-2-1

IETF LC End Date: 2011-2-10

IESG Telechat date:

 

Summary: This draft is almost ready for publication as Informational RFC.

 

Major issues:

 

 

Minor issues:

1.       In section 8.2 the path exploration parameters are different from
RFC 5534, missing keep alive interval. Why the difference.

2.       In section 11.1 you discuss conflict resolution for SHIM6, is this
also relevant for HIP or is it a specific SHIM6 problem. This also relates
to the issue of conflict resolution discussed in the security section.

3.       The last sentence in appendix A "Any solution is needed to overcome
the problem mentioned above" is not clear, does it mean that there is no
solution to the context forking problem.  Section 11.1 claims that using the
procedure described it addresses this issue, am I missing something.

 

 

Nits/editorial comments:

 

1.       In 8.2 for pe_keepaliveto, what are the units, I assume it is
seconds.

2.       In section 7 section paragraph "in which one ore" should be "in
which one or"

 

 


------=_NextPart_000_0017_01CBC1FA.9FC36A80
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;}
/* List Definitions */
@list l0
	{mso-list-id:395208843;
	mso-list-type:hybrid;
	mso-list-template-ids:-1126765420 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1143810922;
	mso-list-type:hybrid;
	mso-list-template-ids:-2041558658 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></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>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-=
shim6-multihome-shim-api-15<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:2011&#8211;2&#8211;1<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: 2011&#8211;2&#8211;10<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 almost ready for publication as Informational =
RFC.<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"'><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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
8.2 the path exploration parameters are different from RFC 5534, missing =
keep alive interval. Why the difference.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
11.1 you discuss conflict resolution for SHIM6, is this also relevant =
for HIP or is it a specific SHIM6 problem. This also relates to the =
issue of conflict resolution discussed in the security =
section.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The last =
sentence in appendix A &#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Any =
solution is needed to overcome the problem mentioned above&#8221; is not =
clear, does it mean that there is no solution to the context forking =
problem.&nbsp; Section 11.1 claims that using the procedure described it =
addresses this issue, am I missing something.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText style=3D'margin-left:.25in'><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"'><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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In 8.2 for =
pe_keepaliveto, what are the units, I assume it is =
seconds.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
7 section paragraph &#8220;in which one ore&#8221; should be &#8220;in =
which one or&#8221;<o:p></o:p></span></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0017_01CBC1FA.9FC36A80--


From magnus.westerlund@ericsson.com  Tue Feb  1 02:10:59 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 298453A6C40; Tue,  1 Feb 2011 02:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.488
X-Spam-Level: 
X-Spam-Status: No, score=-106.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20WysXu9irDd; Tue,  1 Feb 2011 02:10:57 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 79BFD3A6C19; Tue,  1 Feb 2011 02:10:56 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-45-4d47dcf49eb6
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 5B.55.13987.4FCD74D4; Tue,  1 Feb 2011 11:14:12 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.2.234.1; Tue, 1 Feb 2011 11:14:11 +0100
Message-ID: <4D47DCF2.1000200@ericsson.com>
Date: Tue, 1 Feb 2011 11:14:10 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for the	Management	of the	Service	Name and Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>
In-Reply-To: <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 10:11:00 -0000

Cullen Jennings skrev 2011-01-31 18:44:
> 
> Magnus, I agree with what you are saying here but you are avoiding the issue I am concerned with. Is allocating a second port for the secure version of a document a frivolous use case or not? I read this draft as saying it is. Others read the draft as saying it is not and that type of allocation is fine. This seems fairly easy to deal with - first lets agree if particular 2nd port for secure version is a reason to reject requests or not then see if any text needs to be adjusted in the draft to reflect that. 

Well, frankly I don't know. I think it is something that can be avoided
going forward in many use cases, but not all. Simply by thinking of this
issue in the design phase. In addition there is clearly other solutions
there other considerations, like NAT traversal has said, yes
multiplexing is a must, thus live with even higher complexity costs.

The issue I have a problem with is that is we say on general basis that
due to negotiation of security protocols we are allowed to use different
ports for negotiation or simply usage of it. Then why is that different
from different versions of the protocol, or feature support. What is the
difference for a security protocol compared to these other issues?

What I am worried here is that we will see an increased port consumption
rather than a decreased one. At the current run rate I think the
estimate is 50 years+ before run out. That is something that I am
reasonably comfortable, but if the consumption rate increases four
times, then I am suddenly not comfortable. So I am pretty certain that
we need to aim at lowering the consumption rather than raising it.

As I see it there are only one way of doing it.

- State clearly that you really need to do everything reasonable so that
your application is only for one port.
- Be reasonably tough from the expert reviewer to ensure that applicants
has done this.

And from that perspective I don't think security is special in anyway.
It is only one of several things that could potentially require
additional registered ports. Yes security is important, but as
previously discussed it doesn't appear that the actual level of security
provided is different if you are forced to use one port or two. It might
affect the ease of implementation and deployment of security, which is
another aspect of impact.


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From tme@americafree.tv  Tue Feb  1 05:55:21 2011
Return-Path: <tme@americafree.tv>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 874473A6D19 for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 05:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.297
X-Spam-Level: 
X-Spam-Status: No, score=-104.297 tagged_above=-999 required=5 tests=[AWL=2.302, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pqweb4CKeMAI for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 05:55:19 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id AFB7C3A6CDE for <ietf@ietf.org>; Tue,  1 Feb 2011 05:55:19 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 5DD3E9CCD0D3 for <ietf@ietf.org>; Tue,  1 Feb 2011 08:58:36 -0500 (EST)
From: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: APNIC Press release about the Status of the IPv4 Address Pool
Date: Tue, 1 Feb 2011 08:58:32 -0500
Message-Id: <354AD0BE-8EAD-4F6F-8FA8-5AACAED333F0@americafree.tv>
To: The IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 13:55:21 -0000

Seems relevant

=
<http://www.apnic.net/publications/news/2011/leading-global-internet-group=
s-make-significant-announcement-about-the-status-of-the-ipv4-address-pool>=


or=20

http://bit.ly/hPZ40t

Leading Global Internet Groups make Significant Announcement about the =
Status of the IPv4 Address Pool

Published on: Tuesday, 1 February 2011

Much has been written in the international media over the last few weeks =
about the dwindling pool of Internet addresses using the original =
Internet protocol, called IPv4 (Internet Protocol version 4). This week, =
the Internet Assigned Numbers Authority (IANA) allocated two /8 address =
blocks to the Asia Pacific Network Information Centre (APNIC).

As such, the Number Resource Organization (NRO), along with the Internet =
Corporation for Assigned Names and Numbers (ICANN), the Internet Society =
(ISOC), and the Internet Architecture Board (IAB) will be holding a =
press conference to make a significant announcement and to discuss the =
global transition to the next generation of Internet addresses.

When:
Thursday, 3 February 2011 at 09:30 (UTC -5)


Where:
InterContinental Hotel and Resort - Miami
Concourse II
100 Chopin Plaza
Miami, Florida 33131


Who:
	=95 Rod Beckstrom, ICANN President and CEO
	=95 Raul Eceberria, NRO Chair
	=95 Lynn St. Amour, ISOC President and CEO
	=95 Olaf Kolkman, IAB Chair

APNIC invites press in the region to take part in this global event.

APNIC will be issuing a regional level press release to complement the =
information from this media conference. Both the NRO and APNIC press =
releases will be available from the APNIC Press page.

Off site journalists can participate, via live web streaming.=

From fluffy@cisco.com  Tue Feb  1 08:12:42 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A665F3A6C00 for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 08:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.587
X-Spam-Level: 
X-Spam-Status: No, score=-110.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id faqnhZsT3UNZ for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 08:12:42 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id EF4293A6B58 for <ietf@ietf.org>; Tue,  1 Feb 2011 08:12:41 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al4JAAfBR02rRN+K/2dsb2JhbAAipGVzoUObHYVTBIUThxA
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-2.cisco.com with ESMTP; 01 Feb 2011 16:15:52 +0000
Received: from sjc-vpn5-165.cisco.com (sjc-vpn5-165.cisco.com [10.21.88.165]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p11GFp38028302 for <ietf@ietf.org>; Tue, 1 Feb 2011 16:15:52 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Test messages 1
Date: Tue, 1 Feb 2011 11:15:51 -0500
Message-Id: <EEC671B7-D97D-4432-98FB-B37326A4AE01@cisco.com>
To: IETF discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 16:12:42 -0000

Sorry for this - please ignore but some people are having issues with =
this list.=20



From ben@nostrum.com  Mon Jan 31 14:21:38 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F8B33A67F7; Mon, 31 Jan 2011 14:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Level: 
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3iGjFA141CI; Mon, 31 Jan 2011 14:21:36 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 36DC63A688A; Mon, 31 Jan 2011 14:21:35 -0800 (PST)
Received: from dn3-227.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 p0VMOouu069139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 31 Jan 2011 16:24:50 -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 Review of draft-ietf-ccamp-mpls-tp-cp-framework-05
Date: Mon, 31 Jan 2011 16:24:50 -0600
Message-Id: <CFD03B48-6D22-4B6B-A843-B52DF114A101@nostrum.com>
To: draft-ietf-ccamp-mpls-tp-cp-framework.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Tue, 01 Feb 2011 08:18:52 -0800
Cc: The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Jan 2011 22:21:38 -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-ccamp-mpls-tp-cp-framework-05
Reviewer: Ben Campbell
Review Date: 2010-01-31
IETF LC End Date: 2010-01-31
IESG Telechat date: (if known)

Summary:=20

This draft is effectively ready for publication as an informational RFC. =
I have some minor comments, nits. and editorial comments that may be =
worth considering prior to final publication.

Major issues:

None

Minor issues:

-- Section 2 (and subsections)

This section appears to be made up almost entirely of restatements of =
requirements that are normatively stated elsewhere. That takes up about =
16 pages. Is that really necessary, other than to say which requirements =
apply to the control plane? You could do that by merely calling out the =
numbers of the requirements that apply from each document, and making =
notes when more explanation is needed. Since you explicitly state that =
the source documents are authoritative, then a careful reader will need =
to read those documents anyway. OTOH, a not-so-careful reader may not =
read the source documents, and therefore be misinformed if this document =
introduces any discrepancies.

-- Security Considerations:

Are you willing to assert that no new security considerations are =
introduced by the existing mechanism being used in this new context?

Nits/editorial comments:


-- IDNits returns errors and warnings. Please check.

-- The document lists 5 editors on the front page, and 8 authors in the =
author section. That's a bit on the high side. I have no opinion whether =
that is reasonable for this draft--I just call it out so others can =
decide.

-- Please number the tables.

-- The document makes inconsistent use of references. For example, you =
jump between the forms of "... as defined in document[xxx]", "... as =
defined in document, see [xxx]", and "as defined in [xxx]". More =
consistency would make for easier reading. I personally prefer the first =
form, and find the second form disruptive to the flow of reading.

-- Section 1, paragraph 1: "(MPLS-TP) is being defined"

Be careful with time-sensitive statements such as this. An RFC lives =
forever, and this statement may be nonsensical to readers in e future. =
At least qualify it with something like "at the time of this writing..."

-- Section 1, paragraph 2: "as defined by the ITU-T"

Reference?

-- Section 1.2, numbered list:

This is really just normal information, not a sequence. I suggest =
paragraph form, or a bullet list if you really need a list format.

Please put space between the list entries. A long list like this is =
difficult to read without some white space.

Please expand acronyms on first use. There are a number of unexpanded =
acronyms in this section.

-- section 2, first paragraph: "The requirements are summarized in this =
section, but do not replace those documents. If there are differences =
between this section and those documents, those documents shall be =
considered authoritative."

I assume that makes this entire section non-normative, even though it =
uses terms like "must" (albeit non-capitalized). It might be good to say =
that explicitly, as readers may not notice the lack of capitals.

-- section 2.1, req 38:

Do you expect to keep "requirement removed" in the final RFC?

-- ..., req 39:

Which documents are you treating as authoritative for the purpose of =
this document, the ITU or IETF documents?

-- req 52:

The referenced requirement says it MUST be possible to require 100% of =
traffic on the protected path. "Up to 100%" is not the same thing

-- req 95:

Is that a requirement, or an observation?

-- req 100:

Is that a requirement, or an observation?

-- req 101:

Is that a requirement, or an observation?

-- section 4.1.1: "Out-of-band, in-fiber"

You are talking about any scenario using the same physical network, =
right? Is the concept limited to fiber in any way?

-- section 4.1.1, last paragraph: "Some expect the G-ACh to be used =
extensively..."

Who expects it? Can you say something more concrete?

-- 4.1.5, 1st paragraph: "... it is deprecated, and must not be used for =
MPLS-TP."

Do you mean that to be normative?

-- 4.1.9, last paragraph: "Recovery for MPLS-TP LSPs as discussed in =
[TP-SURVIVE], is signaled..."

Missing comma before "as"

-- 4.2.1.1, list:

Please use vertical white space between list entries

-- 4.2.1.2

There are lots of statements of the form "must be possible". Do you mean =
anything in this section to be normative?

-- 4.4.1, last paragraph: "This work will serve as the foundation..."

The referenced work, or this draft? (Similar question for 4.4.5)

Also, there's an odd mid-sentence paragraph break here in the PDF =
version.

-- 4.4.5

This whole paragraph is very time sensitive, and asserts a number of =
things that may no longer be true at some point in the future.

-- 5.3, 2nd paragraph: "See the table in the section above"

Please give a section or table number cross reference.

-- 5.3.2, third paragraph: "it may be required that bidirectional =
traffic follows congruent paths."

"May be required" is pretty vague. Are you talking about requirements on =
the protocol as listed in this document, or something else? (who may =
require it?)=

From ned+ietf@mauve.mrochek.com  Tue Feb  1 08:43:32 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8FCB3A6C0F for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 08:43:31 -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.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUp0drAucxau for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 08:43:30 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id D1B813A6CCE for <ietf@ietf.org>; Tue,  1 Feb 2011 08:43:29 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NXB18GGNGG00K6ZM@mauve.mrochek.com> for ietf@ietf.org; Tue, 1 Feb 2011 08:46:43 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NX5VCDTMLC007FL5@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 1 Feb 2011 08:46:37 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NXB18EJ33U007FL5@mauve.mrochek.com>
Date: Tue, 01 Feb 2011 08:38:25 -0800 (PST)
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for the	Management	of	the	Service	Name and Transport Protocol Port	Number	Registry) to BCP
In-reply-to: "Your message dated Tue, 01 Feb 2011 11:14:10 +0100" <4D47DCF2.1000200@ericsson.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org> <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com> <4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1296575702; i=@mrochek.com; bh=o269w1zTK7aOX9kQ23i/8fAQOQyvZwGvUkNYqm4HA/E=;  h=MIME-version:Content-type:From:Cc:Message-id:Date:Subject: In-reply-to:References:To; b=QJxqCFAJ54tLxhS4/1BT64YwMsRU6C50AmVYjAoW7ZNxksqtf7WjzbBsyTlaOKYTX 7ktnXhKIdRIe6eijrij3lWhgvX+UThZtkfpUMST32T+W/O267GYfNvPlzQ+D7bzmyj Wz6ojvYw06K5VtUrU7or0y7GjRxzWqrCyZD5+G2Q=
Cc: Cullen Jennings <fluffy@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 16:43:32 -0000

+1 to everything Magnus says here. THis is exactly how I view the multiple port
issue.

I will also add that at least part of this fuss seems to be concern about how
"human oversight is needed but what if the overseer misbehaves" issue. Speaking
as someone who has been doing IANA reviews for well over a decade, it is
absolutely the case that a reviwer's actions can screw up a registry. But the
solution to this problem is not to overconstrain the review process - we've
tried that approach and found it causes more problems than it solves - but
rather to have proper checks and balances in the process itself. I believe the
current specified process - once you understand the details, which
unfortunately are a bit difficult to track through all the various
specifications - is sufficient to deal with this.

				Ned

> Cullen Jennings skrev 2011-01-31 18:44:
> >
> > Magnus, I agree with what you are saying here but you are avoiding the issue I am concerned with. Is allocating a second port for the secure version of a document a frivolous use case or not? I read this draft as saying it is. Others read the draft as saying it is not and that type of allocation is fine. This seems fairly easy to deal with - first lets agree if particular 2nd port for secure version is a reason to reject requests or not then see if any text needs to be adjusted in the draft to reflect that.

> Well, frankly I don't know. I think it is something that can be avoided
> going forward in many use cases, but not all. Simply by thinking of this
> issue in the design phase. In addition there is clearly other solutions
> there other considerations, like NAT traversal has said, yes
> multiplexing is a must, thus live with even higher complexity costs.

> The issue I have a problem with is that is we say on general basis that
> due to negotiation of security protocols we are allowed to use different
> ports for negotiation or simply usage of it. Then why is that different
> from different versions of the protocol, or feature support. What is the
> difference for a security protocol compared to these other issues?

> What I am worried here is that we will see an increased port consumption
> rather than a decreased one. At the current run rate I think the
> estimate is 50 years+ before run out. That is something that I am
> reasonably comfortable, but if the consumption rate increases four
> times, then I am suddenly not comfortable. So I am pretty certain that
> we need to aim at lowering the consumption rather than raising it.

> As I see it there are only one way of doing it.

> - State clearly that you really need to do everything reasonable so that
> your application is only for one port.
> - Be reasonably tough from the expert reviewer to ensure that applicants
> has done this.

> And from that perspective I don't think security is special in anyway.
> It is only one of several things that could potentially require
> additional registered ports. Yes security is important, but as
> previously discussed it doesn't appear that the actual level of security
> provided is different if you are forced to use one port or two. It might
> affect the ease of implementation and deployment of security, which is
> another aspect of impact.


> Cheers

> Magnus Westerlund

> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> Färögatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From ekr@rtfm.com  Tue Feb  1 08:53:26 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 997373A6E33; Tue,  1 Feb 2011 08:53:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level: 
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=0.267, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0R8BYMM-PU4v; Tue,  1 Feb 2011 08:53:24 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id D352E3A6BFF; Tue,  1 Feb 2011 08:53:23 -0800 (PST)
Received: by gxk27 with SMTP id 27so2961626gxk.31 for <multiple recipients>; Tue, 01 Feb 2011 08:56:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.52.3 with SMTP id z3mr10888640agz.189.1296579400809; Tue, 01 Feb 2011 08:56:40 -0800 (PST)
Received: by 10.90.116.7 with HTTP; Tue, 1 Feb 2011 08:56:40 -0800 (PST)
In-Reply-To: <01NXB18EJ33U007FL5@mauve.mrochek.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org> <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com> <4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com> <01NXB18EJ33U007FL5@mauve.mrochek.com>
Date: Tue, 1 Feb 2011 08:56:40 -0800
Message-ID: <AANLkTinh4p9z3ahZfUGbUD_Muxor2-75wOsFKof07hMJ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
From: Eric Rescorla <ekr@rtfm.com>
To: ned+ietf@mauve.mrochek.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 16:53:26 -0000

On Tue, Feb 1, 2011 at 8:38 AM,  <ned+ietf@mauve.mrochek.com> wrote:
> +1 to everything Magnus says here. THis is exactly how I view the multipl=
e port
> issue.

I'll respond to this separately.


> I will also add that at least part of this fuss seems to be concern about=
 how
> "human oversight is needed but what if the overseer misbehaves" issue. Sp=
eaking
> as someone who has been doing IANA reviews for well over a decade, it is
> absolutely the case that a reviwer's actions can screw up a registry. But=
 the
> solution to this problem is not to overconstrain the review process - we'=
ve
> tried that approach and found it causes more problems than it solves - bu=
t
> rather to have proper checks and balances in the process itself. I believ=
e the
> current specified process - once you understand the details, which
> unfortunately are a bit difficult to track through all the various
> specifications - is sufficient to deal with this.

Others may have that concern but it's not my concern.

My concern is rather that the reviewer get the correct guidance, and
in this case
that guidance appears to be that he ought to be pushing back on protocols w=
hich
desire to use one port for the insecure version and one port for the
secure version,
and I'm not really that comfortable with that.

-Ekr


> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ned
>
>> Cullen Jennings skrev 2011-01-31 18:44:
>> >
>> > Magnus, I agree with what you are saying here but you are avoiding the=
 issue I am concerned with. Is allocating a second port for the secure vers=
ion of a document a frivolous use case or not? I read this draft as saying =
it is. Others read the draft as saying it is not and that type of allocatio=
n is fine. This seems fairly easy to deal with - first lets agree if partic=
ular 2nd port for secure version is a reason to reject requests or not then=
 see if any text needs to be adjusted in the draft to reflect that.
>
>> Well, frankly I don't know. I think it is something that can be avoided
>> going forward in many use cases, but not all. Simply by thinking of this
>> issue in the design phase. In addition there is clearly other solutions
>> there other considerations, like NAT traversal has said, yes
>> multiplexing is a must, thus live with even higher complexity costs.
>
>> The issue I have a problem with is that is we say on general basis that
>> due to negotiation of security protocols we are allowed to use different
>> ports for negotiation or simply usage of it. Then why is that different
>> from different versions of the protocol, or feature support. What is the
>> difference for a security protocol compared to these other issues?
>
>> What I am worried here is that we will see an increased port consumption
>> rather than a decreased one. At the current run rate I think the
>> estimate is 50 years+ before run out. That is something that I am
>> reasonably comfortable, but if the consumption rate increases four
>> times, then I am suddenly not comfortable. So I am pretty certain that
>> we need to aim at lowering the consumption rather than raising it.
>
>> As I see it there are only one way of doing it.
>
>> - State clearly that you really need to do everything reasonable so that
>> your application is only for one port.
>> - Be reasonably tough from the expert reviewer to ensure that applicants
>> has done this.
>
>> And from that perspective I don't think security is special in anyway.
>> It is only one of several things that could potentially require
>> additional registered ports. Yes security is important, but as
>> previously discussed it doesn't appear that the actual level of security
>> provided is different if you are forced to use one port or two. It might
>> affect the ease of implementation and deployment of security, which is
>> another aspect of impact.
>
>
>> Cheers
>
>> Magnus Westerlund
>
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Phone =A0+46 10 7148287
>> F=E4r=F6gatan 6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>> _______________________________________________
>> 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 paul.hoffman@vpnc.org  Tue Feb  1 08:57:53 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9F0A3A67F9; Tue,  1 Feb 2011 08:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.756
X-Spam-Level: 
X-Spam-Status: No, score=-101.756 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uI7UzscUhO1j; Tue,  1 Feb 2011 08:57:53 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 14C8A3A6E4A; Tue,  1 Feb 2011 08:57:52 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p11H14Zr030532 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 1 Feb 2011 10:01:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D483C4F.3080507@vpnc.org>
Date: Tue, 01 Feb 2011 09:01:03 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for the	Management	of	the	Service	Name and Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com>
In-Reply-To: <4D47DCF2.1000200@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 16:57:53 -0000

On 2/1/11 2:14 AM, Magnus Westerlund wrote:
> Cullen Jennings skrev 2011-01-31 18:44:
>>
>> Magnus, I agree with what you are saying here but you are avoiding the issue I am concerned with. Is allocating a second port for the secure version of a document a frivolous use case or not? I read this draft as saying it is. Others read the draft as saying it is not and that type of allocation is fine. This seems fairly easy to deal with - first lets agree if particular 2nd port for secure version is a reason to reject requests or not then see if any text needs to be adjusted in the draft to reflect that.
>
> Well, frankly I don't know. I think it is something that can be avoided
> going forward in many use cases, but not all. Simply by thinking of this
> issue in the design phase. In addition there is clearly other solutions
> there other considerations, like NAT traversal has said, yes
> multiplexing is a must, thus live with even higher complexity costs.
>
> The issue I have a problem with is that is we say on general basis that
> due to negotiation of security protocols we are allowed to use different
> ports for negotiation or simply usage of it. Then why is that different
> from different versions of the protocol, or feature support. What is the
> difference for a security protocol compared to these other issues?

As has been said many times before: downgrade attacks and essentially 
different transport. Each of those has very serious consequences, the 
first for the security of the communication, the second for the design 
of the underlying protocol.

> What I am worried here is that we will see an increased port consumption
> rather than a decreased one. At the current run rate I think the
> estimate is 50 years+ before run out. That is something that I am
> reasonably comfortable, but if the consumption rate increases four
> times, then I am suddenly not comfortable. So I am pretty certain that
> we need to aim at lowering the consumption rather than raising it.

No one is suggesting raising the consumption rate.

> As I see it there are only one way of doing it.
>
> - State clearly that you really need to do everything reasonable so that
> your application is only for one port.
> - Be reasonably tough from the expert reviewer to ensure that applicants
> has done this.

At least one other way was proposed in the TSVWG, but did not get anywhere.

> And from that perspective I don't think security is special in anyway.
> It is only one of several things that could potentially require
> additional registered ports. Yes security is important, but as
> previously discussed it doesn't appear that the actual level of security
> provided is different if you are forced to use one port or two. It might
> affect the ease of implementation and deployment of security, which is
> another aspect of impact.

Some people say "it doesn't appear that the actual level of security 
provided is different if you are forced to use one port or two" and 
others disagree.

From fluffy@cisco.com  Tue Feb  1 09:15:50 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1BFB3A6DC9; Tue,  1 Feb 2011 09:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.587
X-Spam-Level: 
X-Spam-Status: No, score=-110.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zji+QXaSv6ry; Tue,  1 Feb 2011 09:15:49 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id CF91F3A67F9; Tue,  1 Feb 2011 09:15:49 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFLPR02rRN+J/2dsb2JhbAClB3OhV5shhVMEhROHEA
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-3.cisco.com with ESMTP; 01 Feb 2011 17:19:07 +0000
Received: from sjc-vpn5-165.cisco.com (sjc-vpn5-165.cisco.com [10.21.88.165]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p11HJ6hE004674;  Tue, 1 Feb 2011 17:19:06 GMT
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management	of the Service Name and Transport Protocol Port Number	Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D46B3B9.4050804@ericsson.com>
Date: Tue, 1 Feb 2011 12:19:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1082)
Cc: IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 17:15:50 -0000

So to summarize what you are saying, ports are allocated based on an =
arbitrary view of the expert review. When this person will say yes or no =
too can't be described and will change over time.=20

If that's how it works, there is not even any grounds for appeal of any =
given decision. You can't even use precedence as an argument. My view =
was the IESG has been trying to move to having much more concrete advice =
for registries that required expert review. If you agree that is about =
the right summary, then I'm pretty sure I can find plenty of other =
people that would agree with me that this is not OK. I'm not a fan of =
the WG could not get consensus on if we should allow A or not so we are =
just going to let the expert review do whatever they want. If the IETF =
could not come to consensus on if X  or Y were reasons to deny a =
registration, then I don't think the expert review should be able to =
deny a registration due to X or Y.=20



On Jan 31, 2011, at 8:06 , Magnus Westerlund wrote:

> Cullen Jennings skrev 2011-01-30 05:56:
> >
> > I read the draft to say that there would only be one port allocated =
- I took strive to mean that Joe would deny my port requests for two =
ports. If the intention is actually for the draft to say that it strives =
for one port but allows assignment of two where the that is what the =
protocol design desire, then I have no problem. Perhaps we just need to =
clarify what "strive" means. This definition of "strive" leads into =
exactly my other complain that this draft provides no guidance on what =
the expert will or will not approve.
> >
> > We probably need to adjust text like
> >
> > o  IANA strives to encourage the deployment of secure protocols, and
> >      so strives to avoid separate assignments for non-secure =
variants
> >
> > and
> >
> >  The use of separate
> >   service name or port number assignments for secure and insecure
> >   variants of the same service is to be avoided in order to =
discourage
> >   the deployment of insecure services.
> >
> > and
> >
> >  Services are expected to include support for security, either as
> >   default or dynamically negotiated in-band.
> >
> >
> > In band negotiation of security is applicable for some cases, but it =
adds latency, bandwidth, and complicated multiplexing in non session =
based transports. I think this is a bad idea in many cases. I also view =
separation even for stream based protocols as something that helps =
management and debugging as well as policy.
> >
>=20
> Well, the high level goal is to preserve a limited resource. We can't =
do
> that without making the preference clear. But I think you have =
forgotten
> to consider those statements trying to make clear that this is up to
> review.
>=20
> The review criterias can be expected to change overtime. They are also
> hard to codify. Especially for this case, how do we measure
> architectural uncleanness, implementation issues, and performance =
impact
> to make a rule that judges if one or more port is allowed?





From fluffy@cisco.com  Tue Feb  1 09:16:16 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A33A93A6E7F; Tue,  1 Feb 2011 09:16:16 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkusBUE52NnB; Tue,  1 Feb 2011 09:16:15 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 79EE63A6CC7; Tue,  1 Feb 2011 09:15:59 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANrOR02rRN+J/2dsb2JhbAClB3OhU5shAoVRBIUThxA
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-6.cisco.com with ESMTP; 01 Feb 2011 17:19:16 +0000
Received: from sjc-vpn5-165.cisco.com (sjc-vpn5-165.cisco.com [10.21.88.165]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p11HJ6hF004674;  Tue, 1 Feb 2011 17:19:16 GMT
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for the	Management	of the	Service	Name and Transport Protocol Port	Number	Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D47DCF2.1000200@ericsson.com>
Date: Tue, 1 Feb 2011 12:19:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <11676222-268E-4084-BF81-F49A5C0300D8@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-Mailer: Apple Mail (2.1082)
Cc: IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 17:16:16 -0000

inline=20

On Feb 1, 2011, at 5:14 , Magnus Westerlund wrote:

> Cullen Jennings skrev 2011-01-31 18:44:
> >
> > Magnus, I agree with what you are saying here but you are avoiding =
the issue I am concerned with. Is allocating a second port for the =
secure version of a document a frivolous use case or not? I read this =
draft as saying it is. Others read the draft as saying it is not and =
that type of allocation is fine. This seems fairly easy to deal with - =
first lets agree if particular 2nd port for secure version is a reason =
to reject requests or not then see if any text needs to be adjusted in =
the draft to reflect that.
>=20
> Well, frankly I don't know. I think it is something that can be =
avoided
> going forward in many use cases, but not all. Simply by thinking of =
this
> issue in the design phase. In addition there is clearly other =
solutions
> there other considerations, like NAT traversal has said, yes
> multiplexing is a must, thus live with even higher complexity costs.
>=20
> The issue I have a problem with is that is we say on general basis =
that
> due to negotiation of security protocols we are allowed to use =
different
> ports for negotiation or simply usage of it. Then why is that =
different
> from different versions of the protocol, or feature support. What is =
the
> difference for a security protocol compared to these other issues?

I've provided reason why I think this is needed for security in previous =
email on this thread. I'm not arguing you need more ports for versions =
or feature support - I don't think you do.

> What I am worried here is that we will see an increased port =
consumption
> rather than a decreased one. At the current run rate I think the
> estimate is 50 years+ before run out. That is something that I am
> reasonably comfortable, but if the consumption rate increases four
> times, then I am suddenly not comfortable. So I am pretty certain that
> we need to aim at lowering the consumption rather than raising it.
>=20

I'm far more worried about people just using ports without registering =
them than I am about running out. Keep in mind the allocation policy is =
more or less anyone can get one port for just about anything so if we =
are really worried about running out, we would change that. Most =
protocols will not need or request two ports.

> As I see it there are only one way of doing it.
>=20
> - State clearly that you really need to do everything reasonable so =
that
> your application is only for one port.

"Reasonable" here is the problem. I don't want the expert review to tell =
me a second port for security is not reasonable for cases where latency =
is a relevant.=20

> - Be reasonably tough from the expert reviewer to ensure that =
applicants
> has done this.

Again - I want to be able to register ports for proprietary protocols =
without disclosing the details of the proprietary algorithm

>=20
> And from that perspective I don't think security is special in anyway.

> It is only one of several things that could potentially require
> additional registered ports. Yes security is important, but as
> previously discussed it doesn't appear that the actual level of =
security
> provided is different if you are forced to use one port or two. It =
might
> affect the ease of implementation and deployment of security, which is
> another aspect of impact.

It's not just an "ease" of anything - it's the real time performance of =
the resulting system that is an issue.=20

>=20
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20


Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From touch@isi.edu  Tue Feb  1 09:36:36 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C95CC3A6C00; Tue,  1 Feb 2011 09:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8bMzGPtHlSja; Tue,  1 Feb 2011 09:36:35 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id C066F3A6BFF; Tue,  1 Feb 2011 09:36:35 -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 p11HdFsa011189 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 09:39:17 -0800 (PST)
Message-ID: <4D484543.7010601@isi.edu>
Date: Tue, 01 Feb 2011 09:39:15 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for	the	Management	of	the	Service	Name and Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>	<4D47DCF2.1000200@ericsson.com> <4D483C4F.3080507@vpnc.org>
In-Reply-To: <4D483C4F.3080507@vpnc.org>
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: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF discussion list <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 17:36:37 -0000

To clarify some of this discussion, providing some context that might be 
useful:

1) the current doc already explicitly states the procedures for 
assignment in each range of ports (see Sec 8.1.1).

2) Sec 8.1.1 *already* states that IESG approval through IETF process is 
a valid path for assignment, distinct from Expert Review. Since that 
appears to be a point of confusion, I'll quote it directly:

    o  Ports in the User Ports range (1024-49151) are available for
       assignment through IANA, and MAY be used as service identifiers
       upon successful assignment.  Because assigning a port number for a
       specific application consumes a fraction of the shared resource
       that is the port number registry, IANA will require the requester
       to document the intended use of the port number.  This
       documentation will be input to the "Expert Review" procedure
       [RFC5226], by which IANA will have a technical expert review the
       request to determine whether to grant the assignment.  The
       submitted documentation MUST explain why using a port number in
       the Dynamic Ports range is unsuitable for the given application.
       Ports in the User Ports range may also be assigned under the "IETF
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       Review" or "IESG Approval" procedures [RFC5226], which is how most
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       assignments for IETF protocols are handled.
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

    o  Ports in the System Ports range (0-1023) are also available for
       assignment through IANA.  Because the System Ports range is both
       the smallest and the most densely allocated, the requirements for
       new assignments are more strict than those for the User Ports
       range, and will only be granted under the "IETF Review" or "IESG
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
       Approval" procedures [RFC5226].  A request for a System Port
       ^^^^^^^^^
       number MUST document *both* why using a port number from the
       Dynamic Ports range is unsuitable *and* why using a port number
       from the User Ports range is unsuitable for that application.

3) section 7 has NOTHING TO DO with the procedures this document 
updates. That section has plenty of words to avoid any such impression. 
And no, we don't need to define "strives", IMO - since NOTHING IN THAT 
SECTION IS BINDING.

Again, since this is a persistent cause of confusion, I quote from that 
section:

    This section summarizes the current principles by which IANA handles
    the Service Name and Transport Protocol Port Number Registry and
    attempts to conserve the port number space.  This description is
    intended to inform applicants requesting service names and port
    numbers.  IANA has flexibility beyond these principles when handling
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    assignment requests; other factors may come into play, and exceptions
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                                           **************
    may be made to best serve the needs of the Internet.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ***********

If you need more explicit words, the term "non-binding" can be added.

-------

There's a doc I drafted in TSVWG which is a more appropriate venue to 
discuss this issue (draft-touch-tsvwg-port-use0. I encourage those 
interested in these issues to continue discussion on that list, not on 
this general list.

For this document, if this section is causing confusion, it should be 
removed, since it is already included in this other doc and can be 
vetted there.

Joe

From touch@isi.edu  Tue Feb  1 09:46:23 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C38883A6959; Tue,  1 Feb 2011 09:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.516
X-Spam-Level: 
X-Spam-Status: No, score=-104.516 tagged_above=-999 required=5 tests=[AWL=2.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XzykfvE1q0Xx; Tue,  1 Feb 2011 09:46:22 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 5F17B3A6E88; Tue,  1 Feb 2011 09:46:17 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p11HnGxm001001 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 09:49:16 -0800 (PST)
Message-ID: <4D48479C.3010104@isi.edu>
Date: Tue, 01 Feb 2011 09:49:16 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers Authority (IANA) Procedures for the	Management	of the Service Name and Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>
In-Reply-To: <755A9333-6960-4BCC-B996-3775E76B5D9E@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: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg@ietf.org, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 17:46:23 -0000

On 2/1/2011 9:19 AM, Cullen Jennings wrote:
>
> So to summarize what you are saying, ports are allocated based on an
> arbitrary view of the expert review. When this person will say yes or no
> too can't be described and will change over time.

See my other post. Section 8.1.1 already states that there are other 
means besides expert review.

> If that's how it works, there is not even any grounds for appeal of
> any given decision.

The grounds are "disagree with the advice of the Expert Review". The 
IESG can overturn those decisions on that basis alone. They can - and 
have - held up decisions that have come from community consensus as 
well. I.e., this is no different from other appeals process. It is based 
on the strength of the argument.

 From your earlier post:

> I put in a request for a latency sensitive protocol that uses DTLS
> and request a different port for the secure version. Joe as expert
> review says we should redesign the protocol to use something like
> STARTLS and run on one port. I assert, with very little evidence,
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                          **************************
> that will not meet the latency goals of the protocol. Joe does not
> agree.

The burden of proof, especially when asking for multiple ports, ought to 
be on the applicant. "very little evidence" is the issue, and if that 
didn't convince me, then there's an appeals process listed in RFC 5226 
which you could have used to take that "very little evidence" to 
convince the IESG to overturn the decision.

Joe



From ekr@rtfm.com  Tue Feb  1 09:57:17 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 980BD3A6C95; Tue,  1 Feb 2011 09:57:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.651
X-Spam-Level: 
X-Spam-Status: No, score=-102.651 tagged_above=-999 required=5 tests=[AWL=0.326, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7UpyzkJEFr6r; Tue,  1 Feb 2011 09:57:16 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 51E423A6BFA; Tue,  1 Feb 2011 09:57:16 -0800 (PST)
Received: by gwb20 with SMTP id 20so2997944gwb.31 for <multiple recipients>; Tue, 01 Feb 2011 10:00:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.91.20 with SMTP id o20mr11354328agb.27.1296583233379; Tue, 01 Feb 2011 10:00:33 -0800 (PST)
Received: by 10.90.116.7 with HTTP; Tue, 1 Feb 2011 10:00:33 -0800 (PST)
In-Reply-To: <4D484543.7010601@isi.edu>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org> <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com> <4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com> <4D483C4F.3080507@vpnc.org> <4D484543.7010601@isi.edu>
Date: Tue, 1 Feb 2011 10:00:33 -0800
Message-ID: <AANLkTimifgn=UV53Ndsj3PvjQ54j=awKQbHxx=t9H0CD@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
From: Eric Rescorla <ekr@rtfm.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 17:57:17 -0000

On Tue, Feb 1, 2011 at 9:39 AM, Joe Touch <touch@isi.edu> wrote:
> To clarify some of this discussion, providing some context that might be
> useful:
>
> 1) the current doc already explicitly states the procedures for assignmen=
t
> in each range of ports (see Sec 8.1.1).
>
> 2) Sec 8.1.1 *already* states that IESG approval through IETF process is =
a
> valid path for assignment, distinct from Expert Review. Since that appear=
s
> to be a point of confusion, I'll quote it directly:
>
> =A0 o =A0Ports in the User Ports range (1024-49151) are available for
> =A0 =A0 =A0assignment through IANA, and MAY be used as service identifier=
s
> =A0 =A0 =A0upon successful assignment. =A0Because assigning a port number=
 for a
> =A0 =A0 =A0specific application consumes a fraction of the shared resourc=
e
> =A0 =A0 =A0that is the port number registry, IANA will require the reques=
ter
> =A0 =A0 =A0to document the intended use of the port number. =A0This
> =A0 =A0 =A0documentation will be input to the "Expert Review" procedure
> =A0 =A0 =A0[RFC5226], by which IANA will have a technical expert review t=
he
> =A0 =A0 =A0request to determine whether to grant the assignment. =A0The
> =A0 =A0 =A0submitted documentation MUST explain why using a port number i=
n
> =A0 =A0 =A0the Dynamic Ports range is unsuitable for the given applicatio=
n.
> =A0 =A0 =A0Ports in the User Ports range may also be assigned under the "=
IETF
> =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^
> =A0 =A0 =A0Review" or "IESG Approval" procedures [RFC5226], which is how =
most
> =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^
> =A0 =A0 =A0assignments for IETF protocols are handled.
> =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For the purposes of clarification, then, this document has no impact whatso=
ever
on ports assigned through the IESG process? I.e., if my WG submits a propos=
ed
standard document to the IESG and it asks for two ports, I'm not going to g=
et
pushback based on the claim that this document imposes a presumption that
that's wrong?

-Ekr

From touch@isi.edu  Tue Feb  1 10:24:33 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 271023A6FAC; Tue,  1 Feb 2011 10:24:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.555
X-Spam-Level: 
X-Spam-Status: No, score=-104.555 tagged_above=-999 required=5 tests=[AWL=2.044, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tGLC38yOJpDE; Tue,  1 Feb 2011 10:24:32 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 241723A6FA7; Tue,  1 Feb 2011 10:24:32 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p11IQs2C009133 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 10:26:54 -0800 (PST)
Message-ID: <4D48506E.2020200@isi.edu>
Date: Tue, 01 Feb 2011 10:26:54 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>	<4D47DCF2.1000200@ericsson.com>	<4D483C4F.3080507@vpnc.org>	<4D484543.7010601@isi.edu> <AANLkTimifgn=UV53Ndsj3PvjQ54j=awKQbHxx=t9H0CD@mail.gmail.com>
In-Reply-To: <AANLkTimifgn=UV53Ndsj3PvjQ54j=awKQbHxx=t9H0CD@mail.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: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 18:24:33 -0000

On 2/1/2011 10:00 AM, Eric Rescorla wrote:
> On Tue, Feb 1, 2011 at 9:39 AM, Joe Touch<touch@isi.edu>  wrote:
>> To clarify some of this discussion, providing some context that might be
>> useful:
>>
>> 1) the current doc already explicitly states the procedures for assignment
>> in each range of ports (see Sec 8.1.1).
>>
>> 2) Sec 8.1.1 *already* states that IESG approval through IETF process is a
>> valid path for assignment, distinct from Expert Review. Since that appears
>> to be a point of confusion, I'll quote it directly:
>>
>>    o  Ports in the User Ports range (1024-49151) are available for
>>       assignment through IANA, and MAY be used as service identifiers
>>       upon successful assignment.  Because assigning a port number for a
>>       specific application consumes a fraction of the shared resource
>>       that is the port number registry, IANA will require the requester
>>       to document the intended use of the port number.  This
>>       documentation will be input to the "Expert Review" procedure
>>       [RFC5226], by which IANA will have a technical expert review the
>>       request to determine whether to grant the assignment.  The
>>       submitted documentation MUST explain why using a port number in
>>       the Dynamic Ports range is unsuitable for the given application.
>>       Ports in the User Ports range may also be assigned under the "IETF
>>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>       Review" or "IESG Approval" procedures [RFC5226], which is how most
>>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>       assignments for IETF protocols are handled.
>>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> For the purposes of clarification, then, this document has no impact whatsoever
> on ports assigned through the IESG process? I.e., if my WG submits a proposed
> standard document to the IESG and it asks for two ports, I'm not going to get
> pushback based on the claim that this document imposes a presumption that
> that's wrong?

The ONLY impact is in the format of information required for an assignment.

(i.e., yes, if you're asking that there's no change to the process, 
that's correct)

However, IANA can still pushback, and can use whatever advice it sees 
fit to do so, during IESG review. You can get that pushback now. This 
document doesn't change that AT ALL.

Joe

From ekr@rtfm.com  Tue Feb  1 10:26:22 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6665D3A6844; Tue,  1 Feb 2011 10:26:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.665
X-Spam-Level: 
X-Spam-Status: No, score=-102.665 tagged_above=-999 required=5 tests=[AWL=0.312, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yFUTHsYt320; Tue,  1 Feb 2011 10:26:20 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 546AC3A6FC3; Tue,  1 Feb 2011 10:26:15 -0800 (PST)
Received: by gwb20 with SMTP id 20so3012362gwb.31 for <multiple recipients>; Tue, 01 Feb 2011 10:29:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.96.1 with SMTP id t1mr3929053agb.54.1296584972511; Tue, 01 Feb 2011 10:29:32 -0800 (PST)
Received: by 10.90.116.7 with HTTP; Tue, 1 Feb 2011 10:29:31 -0800 (PST)
In-Reply-To: <4D48506E.2020200@isi.edu>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org> <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com> <4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com> <4D483C4F.3080507@vpnc.org> <4D484543.7010601@isi.edu> <AANLkTimifgn=UV53Ndsj3PvjQ54j=awKQbHxx=t9H0CD@mail.gmail.com> <4D48506E.2020200@isi.edu>
Date: Tue, 1 Feb 2011 10:29:31 -0800
Message-ID: <AANLkTinFLrKMKiEzJOYjZ33KX1D5bunaOctqja5+=8CH@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
From: Eric Rescorla <ekr@rtfm.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 18:26:22 -0000

On Tue, Feb 1, 2011 at 10:26 AM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 2/1/2011 10:00 AM, Eric Rescorla wrote:
>>
>> On Tue, Feb 1, 2011 at 9:39 AM, Joe Touch<touch@isi.edu> =A0wrote:
>>>
>>> To clarify some of this discussion, providing some context that might b=
e
>>> useful:
>>>
>>> 1) the current doc already explicitly states the procedures for
>>> assignment
>>> in each range of ports (see Sec 8.1.1).
>>>
>>> 2) Sec 8.1.1 *already* states that IESG approval through IETF process i=
s
>>> a
>>> valid path for assignment, distinct from Expert Review. Since that
>>> appears
>>> to be a point of confusion, I'll quote it directly:
>>>
>>> =A0 o =A0Ports in the User Ports range (1024-49151) are available for
>>> =A0 =A0 =A0assignment through IANA, and MAY be used as service identifi=
ers
>>> =A0 =A0 =A0upon successful assignment. =A0Because assigning a port numb=
er for a
>>> =A0 =A0 =A0specific application consumes a fraction of the shared resou=
rce
>>> =A0 =A0 =A0that is the port number registry, IANA will require the requ=
ester
>>> =A0 =A0 =A0to document the intended use of the port number. =A0This
>>> =A0 =A0 =A0documentation will be input to the "Expert Review" procedure
>>> =A0 =A0 =A0[RFC5226], by which IANA will have a technical expert review=
 the
>>> =A0 =A0 =A0request to determine whether to grant the assignment. =A0The
>>> =A0 =A0 =A0submitted documentation MUST explain why using a port number=
 in
>>> =A0 =A0 =A0the Dynamic Ports range is unsuitable for the given applicat=
ion.
>>> =A0 =A0 =A0Ports in the User Ports range may also be assigned under the=
 "IETF
>>> =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^
>>> =A0 =A0 =A0Review" or "IESG Approval" procedures [RFC5226], which is ho=
w most
>>> =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^
>>> =A0 =A0 =A0assignments for IETF protocols are handled.
>>> =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> For the purposes of clarification, then, this document has no impact
>> whatsoever
>> on ports assigned through the IESG process? I.e., if my WG submits a
>> proposed
>> standard document to the IESG and it asks for two ports, I'm not going t=
o
>> get
>> pushback based on the claim that this document imposes a presumption tha=
t
>> that's wrong?
>
> The ONLY impact is in the format of information required for an assignmen=
t.
>
> (i.e., yes, if you're asking that there's no change to the process, that'=
s
> correct)
>
> However, IANA can still pushback, and can use whatever advice it sees fit=
 to
> do so, during IESG review. You can get that pushback now. This document
> doesn't change that AT ALL.

I'm sorry, but I'm still not clear.

This document has an affirmative statement against the use of multiple
ports for TLS.

AFAIK that statement is not part of present written policy. Is that correct=
?

-Ekr

From touch@isi.edu  Tue Feb  1 10:35:31 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA6073A6F64; Tue,  1 Feb 2011 10:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.573
X-Spam-Level: 
X-Spam-Status: No, score=-104.573 tagged_above=-999 required=5 tests=[AWL=2.026, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2-1xWR5IDQ9; Tue,  1 Feb 2011 10:35:31 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 02AA23A6844; Tue,  1 Feb 2011 10:35:30 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p11Ib5TE011207 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 10:37:05 -0800 (PST)
Message-ID: <4D4852D1.8060106@isi.edu>
Date: Tue, 01 Feb 2011 10:37:05 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>	<4D47DCF2.1000200@ericsson.com>	<4D483C4F.3080507@vpnc.org>	<4D484543.7010601@isi.edu>	<AANLkTimifgn=UV53Ndsj3PvjQ54j=awKQbHxx=t9H0CD@mail.gmail.com>	<4D48506E.2020200@isi.edu> <AANLkTinFLrKMKiEzJOYjZ33KX1D5bunaOctqja5+=8CH@mail.gmail.com>
In-Reply-To: <AANLkTinFLrKMKiEzJOYjZ33KX1D5bunaOctqja5+=8CH@mail.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: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 18:35:31 -0000

On 2/1/2011 10:29 AM, Eric Rescorla wrote:
...
> I'm sorry, but I'm still not clear.
>
> This document has an affirmative statement against the use of multiple
> ports for TLS.

I'm sorry, but it does not.

I states a goal, and a preference, and has plenty of wiggle room as I've 
repeatedly quoted, and will quote again here:

    This section summarizes the current principles by which IANA handles
    the Service Name and Transport Protocol Port Number Registry and
    attempts to conserve the port number space.  This description is
    intended to inform applicants requesting service names and port
    numbers.  IANA has flexibility beyond these principles when handling
    assignment requests; other factors may come into play, and exceptions
    may be made to best serve the needs of the Internet.

> AFAIK that statement is not part of present written policy. Is that correct?

See the word above "principles". That isn't policy.

IANA isn't bound by it (see the last sentence). The Expert Review team 
is not bound by any written policy - RFC 5226 does not require that we 
have one, and we don't.

Joe

From lear@cisco.com  Tue Feb  1 11:08:06 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52F843A6FC4; Tue,  1 Feb 2011 11:08:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.236
X-Spam-Level: 
X-Spam-Status: No, score=-110.236 tagged_above=-999 required=5 tests=[AWL=0.363, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T-fpngPPzXeL; Tue,  1 Feb 2011 11:08:05 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id F2A663A6E88; Tue,  1 Feb 2011 11:08:04 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJbpR02Q/khMgWdsb2JhbACEF6ByFgEWIiShaYpjkEKBJ4M3dQSMIw
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 01 Feb 2011 19:11:22 +0000
Received: from dhcp-10-61-103-43.cisco.com (dhcp-10-61-103-43.cisco.com [10.61.103.43]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p11JBLms002380; Tue, 1 Feb 2011 19:11:21 GMT
Message-ID: <4D485ACE.4000208@cisco.com>
Date: Tue, 01 Feb 2011 20:11:10 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for	the	Management	of	the	Service	Name and	Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>	<4D47DCF2.1000200@ericsson.com> <01NXB18EJ33U007FL5@mauve.mrochek.com>
In-Reply-To: <01NXB18EJ33U007FL5@mauve.mrochek.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 19:08:06 -0000

I'll add my +1 to Ned's comments in a slightly different way.  As
someone who is a reviewer, I think we all owe a big debt to Joe Touch
and Pearl Liang for guiding applicants and reviewers through the process
(even if the applicants don't know it).

Eliot

On 2/1/11 5:38 PM, Ned Freed wrote:
> +1 to everything Magnus says here. THis is exactly how I view the multiple port
> issue.

From hartmans@mit.edu  Tue Feb  1 11:11:50 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D62B03A700B; Tue,  1 Feb 2011 11:11:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.933
X-Spam-Level: 
X-Spam-Status: No, score=-102.933 tagged_above=-999 required=5 tests=[AWL=-0.668, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYjl9nIl3w1Y; Tue,  1 Feb 2011 11:11:45 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 7EEE33A6FFB; Tue,  1 Feb 2011 11:11:42 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 66EC120289; Tue,  1 Feb 2011 14:12:58 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F0039432C; Tue,  1 Feb 2011 14:14:47 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu>
Date: Tue, 01 Feb 2011 14:14:47 -0500
In-Reply-To: <4D421795.70505@isi.edu> (Joe Touch's message of "Thu, 27 Jan 2011 17:10:45 -0800")
Message-ID: <tslbp2vh8ig.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 19:11:50 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:

    Joe> On 1/27/2011 12:52 AM, Lars Eggert wrote:
    Joe> ...
    >>> Small Issue #3: I object to anonymous review
    >>> 
    >>> The current review is anonymous and this draft does not seem to
    >>> change that. I don't like anonymous review - it's not how we do
    >>> things at IETF and it encourages really bad behavior. I have
    >>> several emails with an expert reviewer relayed via IANA where
    >>> the conversation was going no where - once I knew the name of
    >>> the reviewer, the whole conversation changed and stuff quickly
    >>> came back to the realm of sane. I'm not willing to forward these
    >>> emails to the list as that would just not be kind to anyone but
    >>> I am happy to forward them to the IESG if they think looking at
    >>> them is really critical.
    >> 
    >> I can see your point, and I personally have no problem with
    >> disclosing the reviewer identity. What do others think?

    Joe> AFAICT, the experts team reports to IANA. We make
    Joe> recommendations to them. They are the ones who have the
    Joe> conversation with the applicant. They can take our advice or
    Joe> not - that's their decision.

Joe, the IESG had a fair amount of negative experience with this style
of review just before  I joined; this type of review was just about out
of the process leading to blocking objections when I joined as an AD.

I think that being able to discuss concerns with reviewers and being
able to consider potential conflicts and other issues mean that an open
dialogue with identified reviewers is an important part of our
process. Anonymous contributions may have their place in the WG process,
but I don't think they should have a place in expert review oor blocking
objections to documents.  So, as an individual I strongly support making
expert reviewers identities public.

From touch@isi.edu  Tue Feb  1 11:22:34 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D8E103A6A7A; Tue,  1 Feb 2011 11:22:34 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rDd76EHZeKpF; Tue,  1 Feb 2011 11:22:34 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id F00BD3A6FDF; Tue,  1 Feb 2011 11:22:33 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p11JPWS4003535 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 11:25:33 -0800 (PST)
Message-ID: <4D485E2B.4080201@isi.edu>
Date: Tue, 01 Feb 2011 11:25:31 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu>
In-Reply-To: <tslbp2vh8ig.fsf@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: touch@isi.edu
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 19:22:35 -0000

On 2/1/2011 11:14 AM, Sam Hartman wrote:
...
> Joe, the IESG had a fair amount of negative experience with this style
> of review just before  I joined; this type of review was just about out
> of the process leading to blocking objections when I joined as an AD.
>
> I think that being able to discuss concerns with reviewers and being
> able to consider potential conflicts and other issues mean that an open
> dialogue with identified reviewers is an important part of our
> process. Anonymous contributions may have their place in the WG process,
> but I don't think they should have a place in expert review oor blocking
> objections to documents.  So, as an individual I strongly support making
> expert reviewers identities public.

Such reviews occur elsewhere in the IETF as well; it's not a requirement 
that every review include a list of all consulted parties. This is no 
different. IANA is the one making the decision of how to use the advice 
they receive.

I.e., please explain where in RFC 5226 that the process of Expert Review 
is expected to be a dialogue.

I.e., the dialogue is with IANA, not the reviewer.

The point isn't that reviewers MUST be anonymous; many of them do engage 
in direct conversation with the applicant. However, we try to avoid that 
because we want IANA involved in all conversation, and we want IANA to 
approve that conversation as it goes along. So, ultimately, the 
discussion is really, IMO, with IANA, not the reviewer per se, which is 
why the identity of the reviewer is irrelevant.

Joe

From hartmans@mit.edu  Tue Feb  1 12:08:50 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B14E13A6E78; Tue,  1 Feb 2011 12:08:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.919
X-Spam-Level: 
X-Spam-Status: No, score=-102.919 tagged_above=-999 required=5 tests=[AWL=-0.654, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRT9QzOE690M; Tue,  1 Feb 2011 12:08:50 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id DB3043A6E58; Tue,  1 Feb 2011 12:08:49 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 1C6D72028C; Tue,  1 Feb 2011 15:10:08 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 42B32432C; Tue,  1 Feb 2011 15:12:01 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Joe Touch <touch@isi.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <4D485E2B.4080201@isi.edu>
Date: Tue, 01 Feb 2011 15:12:01 -0500
In-Reply-To: <4D485E2B.4080201@isi.edu> (Joe Touch's message of "Tue, 01 Feb 2011 11:25:31 -0800")
Message-ID: <tslk4hjfram.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, Sam Hartman <hartmans-ietf@MIT.EDU>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 20:08:50 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:

    Joe> On 2/1/2011 11:14 AM, Sam Hartman wrote:
    Joe> ...
    >> Joe, the IESG had a fair amount of negative experience with this
    >> style of review just before I joined; this type of review was
    >> just about out of the process leading to blocking objections when
    >> I joined as an AD.
    >> 
    >> I think that being able to discuss concerns with reviewers and
    >> being able to consider potential conflicts and other issues mean
    >> that an open dialogue with identified reviewers is an important
    >> part of our process. Anonymous contributions may have their place
    >> in the WG process, but I don't think they should have a place in
    >> expert review oor blocking objections to documents.  So, as an
    >> individual I strongly support making expert reviewers identities
    >> public.

    Joe> Such reviews occur elsewhere in the IETF as well; it's not a
    Joe> requirement that every review include a list of all consulted
    Joe> parties. This is no different. IANA is the one making the
    Joe> decision of how to use the advice they receive.

Joe, RFC 5226 disagrees with you fairly significantly.
I draw your attention in particular to section 3.2, and particularly
call our attention to several points made there:

* The designated expert is responsible for initiating and coordinating
  the review.

* Designated experts are expected to be able to defend their *decisions*
  to the IETf community

* The process is not intended to be secretive

* Experts make a single clear recommendation to IANA

* In cases of deadlock IESG may be pulled in to resolve disputes

* When IANA receives conflicting advice, chair of pool of experts  gives
  clear *instructions* to IANA.
On page 10, the expert review criteria  requires approval of a
  designated expert.

I submit based on the above that the experts rather than IANA are making
the decision; the expert has the responsibility of justifying and
defending their decision. Moreover anonymous expert reviews violate two
BCP requirements: they tend to a secretive process and they do not
facilitate the expert defending their decision to the IETF community.

Having read RFc 5226 my objection to anonymous expert reviews is much
stronger than when I first read Cullen's message.

From touch@isi.edu  Tue Feb  1 13:03:42 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 646D73A6C0E; Tue,  1 Feb 2011 13:03:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.609
X-Spam-Level: 
X-Spam-Status: No, score=-104.609 tagged_above=-999 required=5 tests=[AWL=1.990, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9FPqeMp3r-e; Tue,  1 Feb 2011 13:03:41 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 415FF3A6B4F; Tue,  1 Feb 2011 13:03:41 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p11L6PVf014294 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 13:06:25 -0800 (PST)
Message-ID: <4D4875D1.6060106@isi.edu>
Date: Tue, 01 Feb 2011 13:06:25 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service  Name  and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu>	<4D485E2B.4080201@isi.edu> <tslk4hjfram.fsf@mit.edu>
In-Reply-To: <tslk4hjfram.fsf@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: touch@isi.edu
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 21:03:42 -0000

On 2/1/2011 12:12 PM, Sam Hartman wrote:
>>>>>> "Joe" == Joe Touch<touch@isi.edu>  writes:
>
>      Joe>  On 2/1/2011 11:14 AM, Sam Hartman wrote:
>      Joe>  ...
>      >>  Joe, the IESG had a fair amount of negative experience with this
>      >>  style of review just before I joined; this type of review was
>      >>  just about out of the process leading to blocking objections when
>      >>  I joined as an AD.
>      >>
>      >>  I think that being able to discuss concerns with reviewers and
>      >>  being able to consider potential conflicts and other issues mean
>      >>  that an open dialogue with identified reviewers is an important
>      >>  part of our process. Anonymous contributions may have their place
>      >>  in the WG process, but I don't think they should have a place in
>      >>  expert review oor blocking objections to documents.  So, as an
>      >>  individual I strongly support making expert reviewers identities
>      >>  public.
>
>      Joe>  Such reviews occur elsewhere in the IETF as well; it's not a
>      Joe>  requirement that every review include a list of all consulted
>      Joe>  parties. This is no different. IANA is the one making the
>      Joe>  decision of how to use the advice they receive.
>
> Joe, RFC 5226 disagrees with you fairly significantly.
> I draw your attention in particular to section 3.2, and particularly
> call our attention to several points made there:
>
> * The designated expert is responsible for initiating and coordinating
>    the review.
>
> * Designated experts are expected to be able to defend their *decisions*
>    to the IETf community
>
> * The process is not intended to be secretive
>
> * Experts make a single clear recommendation to IANA
>
> * In cases of deadlock IESG may be pulled in to resolve disputes
>
> * When IANA receives conflicting advice, chair of pool of experts  gives
>    clear *instructions* to IANA.
> On page 10, the expert review criteria  requires approval of a
>    designated expert.
>
> I submit based on the above that the experts rather than IANA are making
> the decision; the expert has the responsibility of justifying and
> defending their decision. Moreover anonymous expert reviews violate two
> BCP requirements: they tend to a secretive process and they do not
> facilitate the expert defending their decision to the IETF community.
>
> Having read RFc 5226 my objection to anonymous expert reviews is much
> stronger than when I first read Cullen's message.

Well, based on the above, the Expert Team has a lot more power than I 
originally thought.  I agree that, given that power, making the reviewer 
known makes sense.

I will let you know that I will recommend to IANA that they should 
include a warning that any communication regarding an application made 
outside of the process (e.g., with IANA in the loop) will likely result 
in an application being rejected on a violation of the above "open" 
process. That should avoid my concerns about the team being deluged 
out-of-band ;-)

Joe

From ekr@rtfm.com  Tue Feb  1 13:08:57 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AD753A6C7F; Tue,  1 Feb 2011 13:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.712
X-Spam-Level: 
X-Spam-Status: No, score=-102.712 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9-6ndLx3V91; Tue,  1 Feb 2011 13:08:55 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 2A1D83A6C75; Tue,  1 Feb 2011 13:08:55 -0800 (PST)
Received: by gxk27 with SMTP id 27so3090225gxk.31 for <multiple recipients>; Tue, 01 Feb 2011 13:12:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.52.3 with SMTP id z3mr11221374agz.189.1296594730870; Tue, 01 Feb 2011 13:12:10 -0800 (PST)
Received: by 10.90.116.7 with HTTP; Tue, 1 Feb 2011 13:12:10 -0800 (PST)
In-Reply-To: <4D47DCF2.1000200@ericsson.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org> <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com> <4D46D1D3.10701@vpnc.org> <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com> <4D46E623.3080602@ericsson.com> <9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com> <4D47DCF2.1000200@ericsson.com>
Date: Tue, 1 Feb 2011 13:12:10 -0800
Message-ID: <AANLkTimsf8wH0oYRt74k1jVRsTOJhWK2aLGOMiLR7g70@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
From: Eric Rescorla <ekr@rtfm.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Cullen Jennings <fluffy@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Feb 2011 21:08:57 -0000

On Tue, Feb 1, 2011 at 2:14 AM, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
> Cullen Jennings skrev 2011-01-31 18:44:
>>
>> Magnus, I agree with what you are saying here but you are avoiding the i=
ssue I am concerned with. Is allocating a second port for the secure versio=
n of a document a frivolous use case or not? I read this draft as saying it=
 is. Others read the draft as saying it is not and that type of allocation =
is fine. This seems fairly easy to deal with - first lets agree if particul=
ar 2nd port for secure version is a reason to reject requests or not then s=
ee if any text needs to be adjusted in the draft to reflect that.
>
> Well, frankly I don't know. I think it is something that can be avoided
> going forward in many use cases, but not all. Simply by thinking of this
> issue in the design phase. In addition there is clearly other solutions
> there other considerations, like NAT traversal has said, yes
> multiplexing is a must, thus live with even higher complexity costs.
>
> The issue I have a problem with is that is we say on general basis that
> due to negotiation of security protocols we are allowed to use different
> ports for negotiation or simply usage of it. Then why is that different
> from different versions of the protocol, or feature support. What is the
> difference for a security protocol compared to these other issues?
>
> What I am worried here is that we will see an increased port consumption
> rather than a decreased one. At the current run rate I think the
> estimate is 50 years+ before run out. That is something that I am
> reasonably comfortable, but if the consumption rate increases four
> times, then I am suddenly not comfortable. So I am pretty certain that
> we need to aim at lowering the consumption rather than raising it.
>
> As I see it there are only one way of doing it.
>
> - State clearly that you really need to do everything reasonable so that
> your application is only for one port.
> - Be reasonably tough from the expert reviewer to ensure that applicants
> has done this.
>
> And from that perspective I don't think security is special in anyway.
> It is only one of several things that could potentially require
> additional registered ports. Yes security is important, but as
> previously discussed it doesn't appear that the actual level of security
> provided is different if you are forced to use one port or two. It might
> affect the ease of implementation and deployment of security, which is
> another aspect of impact.
>
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Phone =A0+46 10 7148287
> F=E4r=F6gatan 6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From touch@isi.edu  Tue Feb  1 17:33:09 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66DD93A6B4F; Tue,  1 Feb 2011 17:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.127
X-Spam-Level: 
X-Spam-Status: No, score=-100.127 tagged_above=-999 required=5 tests=[AWL=-2.528, BAYES_00=-2.599, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Remvo5Ii+ZV0; Tue,  1 Feb 2011 17:33:07 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 349EA3A68D8; Tue,  1 Feb 2011 17:33:07 -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 p121ZcWa007512 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 1 Feb 2011 17:35:39 -0800 (PST)
Message-ID: <4D48B4EA.20503@isi.edu>
Date: Tue, 01 Feb 2011 17:35:38 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Subject: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
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.9
Precedence: list
Reply-To: TSV Dir <tsv-dir@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 01:33:09 -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.

The document describes the issues with IP address sharing approaches, 
independent of approach. The document does include a number of 
application issues, many of which originate from transport protocol 
problems, as well as a few specific transport issues.

There are a few missing transport issues that should be addressed prior 
to final publication, as noted below. Overall, the document does discuss 
some such issues in various places, but the table should include these 
issues, and the issue discussion should be expanded to include some 
issues not currently addressed.

Some of these changes are substantive, however, and I recommend that the 
changes be discussed in the transport WG (e.g. TSVWG, tsvwg@ietf.org) 
before proceeding with publication of this document.

The note below includes the significant transport issues, as well as 
additional comments interspersed in a copy of the text as well. Some are 
editorial  ("??") and should not impede doc. progress. There are a few 
issues labeled "?INT?" that are Internet-area (IP), not transport 
issues, but they would be very useful to also treat as substantive 
rather than editorial.

I hope this feedback will be useful to the authors, and will be glad to 
provide further assistance either on- or off-list as useful.

Joe

--------------------------------------------------------------

Transport issues include:

- refers to "Well Known ports"
Throughout this document, this usually refers to the entire Assigned 
range, i.e., Well-known (i.e., System) as well as Registered (i.e., 
User) ports. It would be preferable to refer to them as "Assigned 
ports", and include "(both System and User)". The term "Registered" 
should, FWIW, be avoided as it is ambiguous (since both User and System 
ports are registered with IANA).

- omits numerous transport issues from the table
Such issues include, but may not be limited to:

	- port handoff
		this is included in section 6, but not in the table
		and sec 6 should call out specific protocols
		affected, e.g., FTP, among others)
	- port discovery (using a UDP port to discover a service
		available on a corresponding TCP port, either
		through broadcast, multicast, or unicast)
		this is common, and not discussed anywhere
		see "-disc" in the IANA ports listing (that
		suffix has been in use recently, and helps
		highlight how common the practice is)
	- service discovery through the DNS (e.g., SRV records)
		mentioned in 5.2.2, but not here
	- parallel connections
		i.e., that assume that a single IP address used
		for multiple connections implies a single machine,
		as with striping, multipath, or systems that use
		multiple concurrent connections for different services
		(somewhat related to load balancing in sec 16,	
		but not necessarily)
	- serial connections
		i.e., that assume that returning to a given	
		IP address returns to the same physical host,
		as with stateful transactions; this may also affect
		cookie-based systems, such as TCP-CT, TCP with SYN
		cookies, etc.
	- TCP state mechanisms
		e.g., that might allow a connection that should have
		been in TIME-WAIT (this is discussed in Sec 5, but
		not listed as an issue)
	- address or DNS-name-based signatures
		as in some X.509 signatures

- omits some network issues from the table
This is in Sec 11, but missing from the table. See the NAT discussion in 
draft-ietf-intarea-ipv4-id-update for a related discussion. There appear 
to be more issues here than just the lack of port numbers.

-----------------------------------------------------------

...
>                      Issues with IP Address Sharing
>              draft-ietf-intarea-shared-addressing-issues-02
>
> Abstract
>
>    The completion of IPv4 address allocations from IANA and the RIRs is
>    causing service providers around the world to question how they will
>    continue providing IPv4 connectivity service to their subscribers
>    when there are no longer sufficient IPv4 addresses to allocate them
>    one per subscriber.  Several possible solutions to this problem are
>    now emerging based around the idea of shared IPv4 addressing.  These
>    solutions give rise to a number of issues and this memo identifies
>    those common to all such address sharing approaches.  Solution-
>    specific discussions are out of scope.

?? The abstract is a bit vague. It would be useful to summarize some of 
the issues of note.

...
> 1.  Introduction
...
>
>    Over the long term, deploying IPv6 is the only way to ease pressure
>    on the public IPv4 address pool and thereby mitigate the need for
>    address sharing mechanisms that give rise to the issues identified
>    herein.

?? This sentence is misleading. Clearly address sharing eases pressure 
too, but has caveats. It should be revised to be more clear about the 
options available.

...
> 2.  Shared Addressing Solutions

This section should define address sharing. It's implied, and two 
variants given (1:N NAT, and M:N pooled sharing), but that should be 
made very direct and clear.

...
>    In Figure 1 we have also tried to indicate (with 'xx') where issues
>    are newly created in addition to what could be expected from the
>    introduction of a traditional NAT device.  Issues marked with a
>    single 'x' are already present today in the case of typical CPE NAT,
>    however they can be expected to be more severe and widespread in the
>    case of large-scale address sharing.

?? The notation description could be more clear, e.g. (presuming the 
description is correct):

?? In this figure, "x" indicates issues already present with a NAT, and 
"xx" are for those further issues introduced by pooled sharing.

 >  +------------------------------------------------+--------+---------+
 >  |                   Issue                        |   1st  |   3rd   |
 >  |                                                |  party | parties |
 >  +------------------------------------------------+--------+---------+

This table is useful, but the issue descriptions are subjective in some 
cases, where others are objective. All issues should be objectively 
described.

Further, some issues overlap - "Some applications will fail to operate" 
can be related to other issues, e.g., lack of reverse DNS (for apps 
using DNS names for ACLs), lack of ICMP (for apps using transport 
requiring PMTUD, rather than PLPMTUD), etc.

See the primary note above for items missing from this list.

...
>    | Incoming connections to Well-Known Ports will  |    x   |         |
>    | not work                                       |        |         |

This will affect both Well-Known (i.e., user) and System ports. Use the 
term "Assigned Ports" to refer to the sum of both ranges.

> 5.  Port Allocation
...
>    IANA has classified the whole port space into three categories (as
>    defined in http://www.iana.org/assignments/port-numbers):

Cite RFC 1340 here, rather than the web pages; that's where the ranges 
were defined.

It's useful here to define "Assigned" as including both Well-known and 
Registered ranges as well (to refer to it later, e.g., in Sec 6).

...
> 5.2.1.2.  NAT Port Mapping Protocol (NAT-PMP)
>
>    NAT-PMP already has a better semantic here, enabling the NAT to
>    redirect the application to an available port number.

?? This section is brief; it would be useful to explain what is better. 
Is it better because it can use ANY available port number? What defines 
available?

> 5.2.2.  Connection to a Well-Known Port Number
...
>    For example, the use of DNS SRV records [RFC2782] provides a
>    potential solution for subscribers wishing to host services in the
>    presence of a shared-addressing scheme.  SRV records make it possible
>    to specify a port value related to a service, thereby making services
>    accessible on ports other than the Well-Known ports.  It is worth
>    noting that this mechanism is not applicable to HTTP.

It's not clear why HTTP is singled out here. Few of the commonly used 
services rely on SRV records.

> 6.  Impact on Applications
...
>    o  Applications that use fixed ports (e.g., well-known ports) - see
>       Section 5.2.2 for more discussion of this;

Use the term "Assigned" here".

...
>    o  Applications that do not use any port (e.g., ICMP) - where address
>       sharing solutions map subscribers to (private) IP addresses on a
>       one-to-one basis this will not be an issue, otherwise such
>       applications will require special handling - see Section 9 for
>       more discussion of this;

ICMP does use port information, notably to demux the the signal to the 
appropriate transport connection or association. An alternate example 
might be useful.

...
> 7.  Geo-location and Geo-proximity

?INT? This section is, IMO, odd; IP address never meant physical 
location anyway, and tunnels obviate that meaning regardless of the 
impact of NATs or other sharing techniques.

...
> 9.  ICMP
>
>    ICMP does not carry any port information and is consequently
>    problematic for address sharing mechanisms.

ICMP messages are specifically intended to include enough of the 
transport header to enable port demuxing at the end receiver. When that 
is not available, the demuxing fails. That can impact a number of 
devices, including PMTUD.

> 11.  Fragmentation
>
>    When a packet is fragmented, transport-layer port information (either
>    UDP or TCP) is only present in the first fragment.  Subsequent
>    fragments will not carry the port information and so will require
>    special handling.

?INT? The ID will be incorrect too; it may not be unique as required 
when viewed from the outside.

...
> 13.  Security

This section might also address the impact of sharing on X.509 
authentication, e.g., that signs the name of a host. This can be 
important for some applications.

> 13.4.  Port Randomisation
...
>    It should be noted that guessing the port information may not be
>    sufficient to carry out a successful blind attack.   The exact TCP
>    Sequence Number (SN) should also be known.

There are data injection attacks that are possible even without knowing 
the exact SN.

Further, port randomization is just one way to protect a connection 
(another includes timestamp verification, as noted in RFC4953).

 >    A TCP segment is
>    processed only if all previous segments have been received, except
>    for some Reset Segment implementations which immediately process the
>    Reset as long as it is within the Window.

Processing the reset if in-window is valid according to existing 
standards. See Sec 1.1 of
draft-ietf-tcpm-tcpsecure-13; i.e., it is a MAY except where 
specifically warranted.

?? There's also a proposal for an experimental version of TCP-AO that 
supports NAT traversal, FWIW (draft-touch-tcp-ao-nat).

------

From mrex@sap.com  Tue Feb  1 17:36:33 2011
Return-Path: <mrex@sap.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D28593A6B5C for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 17:36:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.154
X-Spam-Level: 
X-Spam-Status: No, score=-10.154 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lsnIgbcGfKs for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 17:36:33 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id BBAA83A68D8 for <ietf@ietf.org>; Tue,  1 Feb 2011 17:36:32 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p121dlXM012160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Feb 2011 02:39:47 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201102020139.p121dl7E005388@fs4113.wdf.sap.corp>
Subject: Re: prerequisite for change (was Re:
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Wed, 2 Feb 2011 02:39:47 +0100 (MET)
In-Reply-To: <4D44AA6C.8060003@gmail.com> from "Brian E Carpenter" at Jan 30, 11 01:01:48 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: sob@harvard.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 01:36:33 -0000

Brian E Carpenter wrote:
> 
> The bar for PS has crept up, IMHO, precisely because the bar
> for DS/STD has appeared too high to be readily attainable.

Lowering the bar will result in the I-Ds on which the first rush of
implementations are currently being based on becoming the PS document.

But I fail to see how a lowered bar for PS would encourage folks
to tackle DS.  Frankly, I believe just the opposite is going to happen.

For many vendors, the working model is switched from "development mode"
to "maintenance mode" as soon as the product is shipped.  And when that
switch happens, most of the existing resources are reassigned to new
features, rather than improving stuff that is in maintenance mode.

And when DS/STD are collapsed into one and the requirements for the
new STD are at least as high as for the old DS, then the gap between
the new PS and the new STD will be much larger than between old PS
and old DS, resulting in two problems: more resistence from early
implementors to change the document, and less resources from the
vendors to improve a document describing a product that has already
shipped.  The ones who profit most from an improved document would
be those vendors that haven't implemented or shipped yet, and many
of these are not active in the WG or even in the IETF at all.


The reliably predictable outcome of lowering the bar for PS is that
there will be new PS documents with significantly lower quality.

But so far I've not seen any remotely convincing rationale why
the change of PS would improve the likelihood for PS->STD
transitions.  Personally, I believe it will have just the
opposite effect, considering that a non-marginal fraction of
us work for large organizations and how these usually operate.


-Martin

From hallam@gmail.com  Tue Feb  1 19:24:39 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C1983A6A86 for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 19:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.477
X-Spam-Level: 
X-Spam-Status: No, score=-3.477 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17xZLmoFoGEd for <ietf@core3.amsl.com>; Tue,  1 Feb 2011 19:24:37 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 99D593A6916 for <ietf@ietf.org>; Tue,  1 Feb 2011 19:24:37 -0800 (PST)
Received: by yie19 with SMTP id 19so3186664yie.31 for <ietf@ietf.org>; Tue, 01 Feb 2011 19:27:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LuGN3MTf6EOeHDmd4JHcNivLNSfAfUPdk9zHE/n6F6c=; b=UV6r6plaG8hTer1XOynOT918dW/VPQW0CU03Tdx+MSUrkfKnal+5C9/gIvbN2isv7o 2q0C71ctcyvcmXnujUIlu96/IBJiqPj7qRZGISyDKrjKJiP2PoYW7LzhxKn/JTz8DSPP radYq7agQsvC+jY3+12VAE3urV3eMS3nSllSU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=DRzXOwJSJyAU/KbalJeXrC3gahDfnSmegBgfGcOC0kbGIQVRCldiyUxtzIOuVr7tq9 7frESy7auuYFQMDZRx4nzWkQiH0HROkuRhjgVN794m7oEfQtK2HA66/2+64BFWpbwLTZ xSD83PkJVzwiGLkV/GaAYU+rH6iVRnkb8CEP0=
MIME-Version: 1.0
Received: by 10.100.8.9 with SMTP id 9mr5493690anh.120.1296617274128; Tue, 01 Feb 2011 19:27:54 -0800 (PST)
Received: by 10.100.109.16 with HTTP; Tue, 1 Feb 2011 19:27:54 -0800 (PST)
In-Reply-To: <201102020139.p121dl7E005388@fs4113.wdf.sap.corp>
References: <4D44AA6C.8060003@gmail.com> <201102020139.p121dl7E005388@fs4113.wdf.sap.corp>
Date: Tue, 1 Feb 2011 22:27:54 -0500
Message-ID: <AANLkTin-wS02JATw5y=eqc2xRLWbctJ7M4r3iUJUbZdn@mail.gmail.com>
Subject: Re: prerequisite for change (was Re:
From: Phillip Hallam-Baker <hallam@gmail.com>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=0016e6441dd808b81b049b443c00
Cc: ietf@ietf.org, sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 03:24:39 -0000

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

What is wrong with using Informational and Experimental for cases where a
lowered bar is required?

If someone is proposing an entirely new protocol, a low bar is appropriate.
But that is only a very small fraction of the work done in IETF today. Most
of the WG effort goes to incremental refinements to existing specs.

If someone is going to propose an extension to HTTP or PKIX or TLS they had
better have a very good document if it is going to go through.


On Tue, Feb 1, 2011 at 8:39 PM, Martin Rex <mrex@sap.com> wrote:

> Brian E Carpenter wrote:
> >
> > The bar for PS has crept up, IMHO, precisely because the bar
> > for DS/STD has appeared too high to be readily attainable.
>
> Lowering the bar will result in the I-Ds on which the first rush of
> implementations are currently being based on becoming the PS document.
>
> But I fail to see how a lowered bar for PS would encourage folks
> to tackle DS.  Frankly, I believe just the opposite is going to happen.
>
> For many vendors, the working model is switched from "development mode"
> to "maintenance mode" as soon as the product is shipped.  And when that
> switch happens, most of the existing resources are reassigned to new
> features, rather than improving stuff that is in maintenance mode.
>
> And when DS/STD are collapsed into one and the requirements for the
> new STD are at least as high as for the old DS, then the gap between
> the new PS and the new STD will be much larger than between old PS
> and old DS, resulting in two problems: more resistence from early
> implementors to change the document, and less resources from the
> vendors to improve a document describing a product that has already
> shipped.  The ones who profit most from an improved document would
> be those vendors that haven't implemented or shipped yet, and many
> of these are not active in the WG or even in the IETF at all.
>
>
> The reliably predictable outcome of lowering the bar for PS is that
> there will be new PS documents with significantly lower quality.
>
> But so far I've not seen any remotely convincing rationale why
> the change of PS would improve the likelihood for PS->STD
> transitions.  Personally, I believe it will have just the
> opposite effect, considering that a non-marginal fraction of
> us work for large organizations and how these usually operate.
>
>
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Website: http://hallambaker.com/

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

What is wrong with using Informational and Experimental for cases where a l=
owered bar is required?<div><br></div><div>If someone is proposing an entir=
ely new protocol, a low bar is appropriate. But that is only a very small f=
raction of the work done in IETF today. Most of the WG effort goes to incre=
mental refinements to existing specs.</div>
<div><br></div><div>If someone is going to propose an extension to HTTP or =
PKIX or TLS they had better have a very good document if it is going to go =
through.</div><div><br><br><div class=3D"gmail_quote">On Tue, Feb 1, 2011 a=
t 8:39 PM, Martin Rex <span dir=3D"ltr">&lt;<a href=3D"mailto:mrex@sap.com"=
>mrex@sap.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Brian E Carpenter wrote:<br>
&gt;<br>
&gt; The bar for PS has crept up, IMHO, precisely because the bar<br>
&gt; for DS/STD has appeared too high to be readily attainable.<br>
<br>
Lowering the bar will result in the I-Ds on which the first rush of<br>
implementations are currently being based on becoming the PS document.<br>
<br>
But I fail to see how a lowered bar for PS would encourage folks<br>
to tackle DS. =A0Frankly, I believe just the opposite is going to happen.<b=
r>
<br>
For many vendors, the working model is switched from &quot;development mode=
&quot;<br>
to &quot;maintenance mode&quot; as soon as the product is shipped. =A0And w=
hen that<br>
switch happens, most of the existing resources are reassigned to new<br>
features, rather than improving stuff that is in maintenance mode.<br>
<br>
And when DS/STD are collapsed into one and the requirements for the<br>
new STD are at least as high as for the old DS, then the gap between<br>
the new PS and the new STD will be much larger than between old PS<br>
and old DS, resulting in two problems: more resistence from early<br>
implementors to change the document, and less resources from the<br>
vendors to improve a document describing a product that has already<br>
shipped. =A0The ones who profit most from an improved document would<br>
be those vendors that haven&#39;t implemented or shipped yet, and many<br>
of these are not active in the WG or even in the IETF at all.<br>
<br>
<br>
The reliably predictable outcome of lowering the bar for PS is that<br>
there will be new PS documents with significantly lower quality.<br>
<br>
But so far I&#39;ve not seen any remotely convincing rationale why<br>
the change of PS would improve the likelihood for PS-&gt;STD<br>
transitions. =A0Personally, I believe it will have just the<br>
opposite effect, considering that a non-marginal fraction of<br>
us work for large organizations and how these usually operate.<br>
<br>
<br>
-Martin<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a href=3D"htt=
p://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e6441dd808b81b049b443c00--

From fernando.gont.netbook.win@gmail.com  Wed Feb  2 00:00:57 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E3BE83A68F1; Wed,  2 Feb 2011 00:00:57 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghGibR4MEsgM; Wed,  2 Feb 2011 00:00:57 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id D7E6C3A6836; Wed,  2 Feb 2011 00:00:56 -0800 (PST)
Received: by ywk9 with SMTP id 9so3272619ywk.31 for <multiple recipients>; Wed, 02 Feb 2011 00:04:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=nlT960Qf8grhVp39ahxfvuI7Eq0txL59FkVva90vPu0=; b=wQjC6Hw6R/ctlKAhZNIhaHszW+xaYFYAQCpCPn/mE1cpZ+AXtJuJyfrHbY3aS7+JHW bhfD3PhUqjfL974Q0DrW1h9/BDDsTT5+ppb7V02wgHFyprYPbxZeSuscXR6iZo4Ytcmc cwM8LvSnx4xGOLyuLVcUSA9T/6LzpEinCMtOs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=PCNSw0A4WKBV8yElbX7hnwLHTI2BidX/xrr6JOKbfCK6DqTZCUjJDdRZ0F7sj86ftz jHEblFTLlPs7bnuXfs650Uj9O+9qXG4YpnxAcjbJQhIH4Z2dXfpEaD2GsltOmk6IaoX1 B99uBKVU6ENqd5dYV7W3DBwasxfURqCeDs5JY=
Received: by 10.100.164.2 with SMTP id m2mr5726823ane.146.1296633855567; Wed, 02 Feb 2011 00:04:15 -0800 (PST)
Received: from [192.168.2.5] ([190.246.229.147]) by mx.google.com with ESMTPS id t1sm28328657ano.3.2011.02.02.00.04.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 00:04:14 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D490FED.6060303@gont.com.ar>
Date: Wed, 02 Feb 2011 05:03:57 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: TSV Dir <tsv-dir@ietf.org>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu>
In-Reply-To: <4D48B4EA.20503@isi.edu>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 08:00:58 -0000

On 01/02/2011 10:35 p.m., Joe Touch wrote:

>>    Over the long term, deploying IPv6 is the only way to ease pressure
>>    on the public IPv4 address pool and thereby mitigate the need for
>>    address sharing mechanisms that give rise to the issues identified
>>    herein.
> 
> ?? This sentence is misleading. Clearly address sharing eases pressure
> too, but has caveats. It should be revised to be more clear about the
> options available.

+1



> ...
>> 7.  Geo-location and Geo-proximity
> 
> ?INT? This section is, IMO, odd; IP address never meant physical
> location anyway, and tunnels obviate that meaning regardless of the
> impact of NATs or other sharing techniques.

Agreed. But geo-location is nevertheless widely ued for marketing purposes.



>> 13.4.  Port Randomisation
> ...
>>    It should be noted that guessing the port information may not be
>>    sufficient to carry out a successful blind attack.   The exact TCP
>>    Sequence Number (SN) should also be known.
> 
> There are data injection attacks that are possible even without knowing
> the exact SN.

draft-ietf-tcpm-tcp-security may be of use here.



> Further, port randomization is just one way to protect a connection
> (another includes timestamp verification, as noted in RFC4953).

RFC4953 is a little bit vague in this respect. It talks about an
"accepted window". However, as far as the current specs are concerned,
the "accepted window" is half the timestamps space: i.e., you need to
forge, at most, two different timestamps value. It also mentions that
timestamps may be easily predictable. However, this does not need to be
the case (see e.g., draft-gont-timestamps-generation)

Thanks!

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





From magnus.westerlund@ericsson.com  Wed Feb  2 01:13:17 2011
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECA1E3A7125; Wed,  2 Feb 2011 01:13:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.49
X-Spam-Level: 
X-Spam-Status: No, score=-106.49 tagged_above=-999 required=5 tests=[AWL=0.109, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXYijZUVqzqd; Wed,  2 Feb 2011 01:13:15 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id CB4833A6B9C; Wed,  2 Feb 2011 01:13:14 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-ba-4d4920f08b25
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 12.9B.13987.0F0294D4; Wed,  2 Feb 2011 10:16:33 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.2.234.1; Wed, 2 Feb 2011 10:16:32 +0100
Message-ID: <4D4920F0.1070204@ericsson.com>
Date: Wed, 2 Feb 2011 10:16:32 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management	of the Service Name and Transport Protocol Port Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>
In-Reply-To: <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 09:13:17 -0000

Cullen Jennings skrev 2011-02-01 18:19:
> 
> So to summarize what you are saying, ports are allocated based on an arbitrary view of the expert review. When this person will say yes or no too can't be described and will change over time. 
> 
> If that's how it works, there is not even any grounds for appeal of any given decision. You can't even use precedence as an argument. My view was the IESG has been trying to move to having much more concrete advice for registries that required expert review. If you agree that is about the right summary, then I'm pretty sure I can find plenty of other people that would agree with me that this is not OK. I'm not a fan of the WG could not get consensus on if we should allow A or not so we are just going to let the expert review do whatever they want. If the IETF could not come to consensus on if X  or Y were reasons to deny a registration, then I don't think the expert review should be able to deny a registration due to X or Y. 

Cullen,

Apparently you like to twist what I am saying in most negative way and
without considering the checks that are in place.

- I think general guidelines can and should be developed. But other than
high level goals this isn't the document. Here Joe has the start of a
document. But I do think that in long term this guidance may change.

- There is an appeal process where the IESG and then IAB gets to sanity
check the arguments that the reviewer + IANA has given towards the
appealing requestor.

- One can take a assignment request through the IETF process

I hope that we can get consensus on the guidelines, because I think that
would give the reviewers a lot of comfort being able to rely on that
consensus.

Cullen, what are your suggestion for how to improve the document?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From evnikita2@gmail.com  Wed Feb  2 02:48:37 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0CEE3A6CB6 for <ietf@core3.amsl.com>; Wed,  2 Feb 2011 02:48:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.237
X-Spam-Level: 
X-Spam-Status: No, score=-2.237 tagged_above=-999 required=5 tests=[AWL=-0.599, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cF6djS3xyy9D for <ietf@core3.amsl.com>; Wed,  2 Feb 2011 02:48:37 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id B99A63A6BB0 for <ietf@ietf.org>; Wed,  2 Feb 2011 02:48:36 -0800 (PST)
Received: by fxm9 with SMTP id 9so8566989fxm.31 for <ietf@ietf.org>; Wed, 02 Feb 2011 02:51:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:content-type; bh=RU11GXUl/3TD28YVc7yjzkbAdXHabePUdaaXBeQwh2Q=; b=LlqFKpvlBlzx59GYMybXnNvUxymxd7pLZIfiHma5IxHnZGlb/12oepRSHd8dPQprRG HefOCoea20L6rJu3bHhhOqg9hPLML7jLVz7xBTYS3+1yb/ZIhDMYhDwmZmtoc80Np67/ fPJLUwOrAGVUV9OQaF5yCn2xQ91sFiPhgJV9s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; b=VHV6kieP5y3grEqYkdy9HwroojlYbQOmkAGJX/oeSjeGt0lxWXRLZoqJg9D+hqaJkG u//Xswn7D+w19/8h1Jh1uSdUWnEnpH1mc8EZGD1qQHKuU/HwubHQlxMR9WX1bdCRHyrN /V3SwniArI7znXsnwbxCyffyV7Q8OHogKPz7M=
Received: by 10.223.73.206 with SMTP id r14mr8607559faj.126.1296643915526; Wed, 02 Feb 2011 02:51:55 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n2sm8262387fam.4.2011.02.02.02.51.54 (version=SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 02:51:54 -0800 (PST)
Message-ID: <4D493762.7060900@gmail.com>
Date: Wed, 02 Feb 2011 12:52:18 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, rfc-interest@rfc-editor.org
Subject: draft-yevstifeyev-genarea-historic-02
Content-Type: multipart/alternative; boundary="------------000106000001040502040700"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 10:48:37 -0000

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

Hello folks,

A new version of draft-yevstifeyev-genarea-historic is now available and 
can be found here: 
http://tools.ietf.org/html/draft-yevstifeyev-genarea-historic-02

This version is believed to address a number of issues mentioned while 
discussion.

Among other:

    * Added the reason for historicizing document - it is deprecated;
      and mentioned criteria for such 'status'.  See Section 2.1;
    * Clarified the criterion for obsolete documents.
    * Deleted the regulation that Standards Track RFCs may move its
      predecessor to Historic only if it has reached the same status as
      that doc.
    * Clarified the procedures for historicizing Experimental RFCs.
    * Added the regulation for IANA considerations in Historic document.

There are also a number of questions to discuss; they are:

    * Whether historicizing Informational RFCs should be allowed?
    * Whether publication of separate Historic RFCs should be allowed?
      (e.g. RFC 6037)
    * Whether procedures for historicizing Experimental RFCs in the
      current version are acceptable?
    * What are other considerations for Historic docs. that should also
      be discussed?

Any comments are then welcome.

Mykyta Yevstifeyev

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <font size="-1"><big>Hello folks,<br>
        <br>
        A new version of draft-yevstifeyev-genarea-historic is now
        available and can be found here:
        <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-yevstifeyev-genarea-historic-02">http://tools.ietf.org/html/draft-yevstifeyev-genarea-historic-02</a><br>
        <br>
        This version is believed to address a number of issues mentioned
        while discussion.<br>
        <br>
        Among other:<br>
      </big></font>
    <ul>
      <li><font size="-1"><big>Added the reason for historicizing
            document - it is deprecated; and mentioned criteria for such
            'status'.Â  See Section 2.1;</big></font></li>
      <li><font size="-1"><big>Clarified the criterion for obsolete
            documents.</big></font></li>
      <li><font size="-1"><big>Deleted the regulation that Standards
            Track RFCs may move its predecessor to Historic only if it
            has reached the same status as that doc.</big></font></li>
      <li><font size="-1"><big>Clarified the procedures for
            historicizing Experimental RFCs.</big></font></li>
      <li><font size="-1"><big>Added the regulation for IANA
            considerations in Historic document.</big></font></li>
    </ul>
    <font size="-1"><big>There are also a number of questions to
        discuss; they are:<br>
      </big></font>
    <ul>
      <li><font size="-1"><big>Whether historicizing Informational RFCs
            should be allowed?</big></font></li>
      <li><font size="-1"><big>Whether publication of separate Historic
            RFCs should be allowed? (e.g. RFC 6037)</big></font></li>
      <li><font size="-1"><big>Whether procedures for historicizing
            Experimental RFCs in the current version are acceptable?</big></font></li>
      <li><font size="-1"><big>What are other considerations for
            Historic docs. that should also be discussed?</big></font></li>
    </ul>
    <font size="-1"><big>Any comments are then welcome.<br>
        <br>
        Mykyta Yevstifeyev<br>
      </big></font>
  </body>
</html>

--------------000106000001040502040700--

From daedulus@btconnect.com  Wed Feb  2 04:23:55 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2141A3A6C14; Wed,  2 Feb 2011 04:23:55 -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.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIiqJFOUmCcU; Wed,  2 Feb 2011 04:23:54 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by core3.amsl.com (Postfix) with ESMTP id 485413A7154; Wed,  2 Feb 2011 04:23:52 -0800 (PST)
Received: from host81-152-46-124.range81-152.btcentralplus.com (HELO pc6) ([81.152.46.124]) by c2beaomr10.btconnect.com with SMTP id BNW94587; Wed, 02 Feb 2011 12:26:53 +0000 (GMT)
Message-ID: <007101cbc2cb$8ee4cca0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Joe Touch" <touch@isi.edu>, "Paul Hoffman" <paul.hoffman@vpnc.org>
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>	<4D47DCF2.1000200@ericsson.com><4D483C4F.3080507@vpnc.org> <4D484543.7010601@isi.edu>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	AssignedNumbers	Authority (IANA) Proceduresfor	the	Management	of	the	Service	Nameand Transport Protocol Port	Number	Registry) to BCP
Date: Wed, 2 Feb 2011 12:22:57 +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.0A0B0302.4D494D8C.00C8, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4D494D8E.011B,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 12:23:55 -0000

----- Original Message -----
From: "Joe Touch" <touch@isi.edu>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
"IETF discussion list" <ietf@ietf.org>; <tsvwg@ietf.org>; "IESG IESG"
<iesg@ietf.org>
Sent: Tuesday, February 01, 2011 6:39 PM

> To clarify some of this discussion, providing some context that might be
> useful:
>
> 1) the current doc already explicitly states the procedures for
> assignment in each range of ports (see Sec 8.1.1).
>
> 2) Sec 8.1.1 *already* states that IESG approval through IETF process is
> a valid path for assignment, distinct from Expert Review. Since that
> appears to be a point of confusion, I'll quote it directly:
>
>     o  Ports in the User Ports range (1024-49151) are available for
>        assignment through IANA, and MAY be used as service identifiers
>        upon successful assignment.  Because assigning a port number for a
>        specific application consumes a fraction of the shared resource
>        that is the port number registry, IANA will require the requester
>        to document the intended use of the port number.  This
>        documentation will be input to the "Expert Review" procedure
>        [RFC5226], by which IANA will have a technical expert review the
>        request to determine whether to grant the assignment.  The
>        submitted documentation MUST explain why using a port number in
>        the Dynamic Ports range is unsuitable for the given application.
>        Ports in the User Ports range may also be assigned under the "IETF
>        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>        Review" or "IESG Approval" procedures [RFC5226], which is how most
>        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>        assignments for IETF protocols are handled.
>        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Joe

I think that it is a point of confusion because the text is confused
(well, it confuses me:-(.

If you know in advance that there are two independent paths that
can be taken, then you can read that meaning into it.

If you do not know that, then having read
                                                                     "This
        documentation will be input to the "Expert Review" procedure
        [RFC5226], by which IANA will have a technical expert review the
        request to determine whether to grant the assignment"

then it is obvious that Expert Review always happens, even when a later
sentence talks about 'may also be assigned'.

To make the two paths clear, the text should be reordered eg

         Ports in the User Ports range (1024-49151) are available for
        assignment through IANA, and MAY be used as service identifiers
        upon successful assignment.  Because assigning a port number for a
        specific application consumes a fraction of the shared resource
        that is the port number registry, IANA will require the requester
        to document the intended use of the port number.

For most IETF protocols, ports in the User Ports range will be assigned under
the "IETF
Review" or "IESG Approval" procedures [RFC5226] and no further
documentation is required.

Where these procedures do not apply, then the requester must
input the documentation to

                                                            the "Expert Review"
procedure
        [RFC5226], by which IANA will have a technical expert review the
        request to determine whether to grant the assignment.  The
        submitted documentation MUST explain why using a port number in
        the Dynamic Ports range is unsuitable for the given application.

Tom Petch


>
>     o  Ports in the System Ports range (0-1023) are also available for
>        assignment through IANA.  Because the System Ports range is both
>        the smallest and the most densely allocated, the requirements for
>        new assignments are more strict than those for the User Ports
>        range, and will only be granted under the "IETF Review" or "IESG
>                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>        Approval" procedures [RFC5226].  A request for a System Port
>        ^^^^^^^^^
>        number MUST document *both* why using a port number from the
>        Dynamic Ports range is unsuitable *and* why using a port number
>        from the User Ports range is unsuitable for that application.
>
> 3) section 7 has NOTHING TO DO with the procedures this document
> updates. That section has plenty of words to avoid any such impression.
> And no, we don't need to define "strives", IMO - since NOTHING IN THAT
> SECTION IS BINDING.
>
> Again, since this is a persistent cause of confusion, I quote from that
> section:
>
>     This section summarizes the current principles by which IANA handles
>     the Service Name and Transport Protocol Port Number Registry and
>     attempts to conserve the port number space.  This description is
>     intended to inform applicants requesting service names and port
>     numbers.  IANA has flexibility beyond these principles when handling
>               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     assignment requests; other factors may come into play, and exceptions
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>                                                            **************
>     may be made to best serve the needs of the Internet.
>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>     ***********
>
> If you need more explicit words, the term "non-binding" can be added.
>
> -------
>
> There's a doc I drafted in TSVWG which is a more appropriate venue to
> discuss this issue (draft-touch-tsvwg-port-use0. I encourage those
> interested in these issues to continue discussion on that list, not on
> this general list.
>
> For this document, if this section is causing confusion, it should be
> removed, since it is already included in this other doc and can be
> vetted there.
>
> Joe
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From daedulus@btconnect.com  Wed Feb  2 04:28:09 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30F2B3A7142; Wed,  2 Feb 2011 04:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hOd+0RWTH-y9; Wed,  2 Feb 2011 04:28:08 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id CE1963A6CC1; Wed,  2 Feb 2011 04:28:06 -0800 (PST)
Received: from host81-152-46-124.range81-152.btcentralplus.com (HELO pc6) ([81.152.46.124]) by c2beaomr07.btconnect.com with SMTP id BPV12464; Wed, 02 Feb 2011 12:31:20 +0000 (GMT)
Message-ID: <009101cbc2cc$2e43bfe0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>, "Magnus Westerlund" <magnus.westerlund@ericsson.com>
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com><4D47DCF2.1000200@ericsson.com> <4D483C4F.3080507@vpnc.org>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	AssignedNumbers	Authority (IANA) Procedures forthe	Management	of	the	Service	Nameand Transport Protocol Port	Number	Registry) to BCP
Date: Wed, 2 Feb 2011 12:27: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.0A0B0302.4D494E97.01D9, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4D494E9A.02D8,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 12:28:09 -0000

----- Original Message -----
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
Cc: "Cullen Jennings" <fluffy@cisco.com>;  "IESG IESG" <iesg@ietf.org>; "IETF
discussion list" <ietf@ietf.org>
Sent: Tuesday, February 01, 2011 6:01 PM

> On 2/1/11 2:14 AM, Magnus Westerlund wrote:
> > Cullen Jennings skrev 2011-01-31 18:44:
> >>

<snip>.
>
> Some people say "it doesn't appear that the actual level of security
> provided is different if you are forced to use one port or two" and
> others disagree.

This did get a thorough airing on the TLS list
in the second week of November
"[TLS] Security concerns around co-locating TLS and non-secure on same port
(WGLC: draft-ietf-tsvwg-iana-ports-08)"

As Paul said, some say yea and others nay.

Tom Petch

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


From jari.arkko@piuha.net  Wed Feb  2 06:31:34 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B23D3A6CF9; Wed,  2 Feb 2011 06:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.497
X-Spam-Level: 
X-Spam-Status: No, score=-99.497 tagged_above=-999 required=5 tests=[AWL=-2.967, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DT+mRmFYumzG; Wed,  2 Feb 2011 06:31:32 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id DAF693A6C68; Wed,  2 Feb 2011 06:31:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0A09E2CC2D; Wed,  2 Feb 2011 16:34:51 +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 ZSfEHNK2r2Cr; Wed,  2 Feb 2011 16:34:49 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id C37922CC3C; Wed,  2 Feb 2011 16:34:48 +0200 (EET)
Message-ID: <4D48F56B.7080402@piuha.net>
Date: Tue, 01 Feb 2011 22:10:51 -0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: TSV Dir <tsv-dir@ietf.org>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu>
In-Reply-To: <4D48B4EA.20503@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 14:31:34 -0000

Joe,

Thanks for your review. A couple of comments inline:

> Transport issues include:
>
> - refers to "Well Known ports"
> Throughout this document, this usually refers to the entire Assigned 
> range, i.e., Well-known (i.e., System) as well as Registered (i.e., 
> User) ports. It would be preferable to refer to them as "Assigned 
> ports", and include "(both System and User)". The term "Registered" 
> should, FWIW, be avoided as it is ambiguous (since both User and 
> System ports are registered with IANA).

OK

> - omits numerous transport issues from the table
> Such issues include, but may not be limited to:
>
>     - port handoff
>         this is included in section 6, but not in the table
>         and sec 6 should call out specific protocols
>         affected, e.g., FTP, among others)
>     - port discovery (using a UDP port to discover a service
>         available on a corresponding TCP port, either
>         through broadcast, multicast, or unicast)
>         this is common, and not discussed anywhere
>         see "-disc" in the IANA ports listing (that
>         suffix has been in use recently, and helps
>         highlight how common the practice is)
>     - service discovery through the DNS (e.g., SRV records)
>         mentioned in 5.2.2, but not here

OK

>     - parallel connections
>         i.e., that assume that a single IP address used
>         for multiple connections implies a single machine,
>         as with striping, multipath, or systems that use
>         multiple concurrent connections for different services
>         (somewhat related to load balancing in sec 16,   
>         but not necessarily)

Why is this an issue? I thought that many of these mechanisms explicitly 
signal that a new connection is going to be established. Are there 
systems that assume that two independent connections are to the same 
machine, if they come from the same IP address? And isn't that 
assumption already broken by existing NATs?

>     - serial connections
>         i.e., that assume that returning to a given   
>         IP address returns to the same physical host,
>         as with stateful transactions; this may also affect
>         cookie-based systems, such as TCP-CT, TCP with SYN
>         cookies, etc.

OK. Interesting.

>     - TCP state mechanisms
>         e.g., that might allow a connection that should have
>         been in TIME-WAIT (this is discussed in Sec 5, but
>         not listed as an issue)

OK

>     - address or DNS-name-based signatures
>         as in some X.509 signatures

Why would DNS-name based certificates be an issue? You can still have 
multiple names per an IP address.

> - omits some network issues from the table
> This is in Sec 11, but missing from the table. See the NAT discussion 
> in draft-ietf-intarea-ipv4-id-update for a related discussion. There 
> appear to be more issues here than just the lack of port numbers.
>
> -----------------------------------------------------------
>
> ...
>>                      Issues with IP Address Sharing
>>              draft-ietf-intarea-shared-addressing-issues-02
>>
>> Abstract
>>
>>    The completion of IPv4 address allocations from IANA and the RIRs is
>>    causing service providers around the world to question how they will
>>    continue providing IPv4 connectivity service to their subscribers
>>    when there are no longer sufficient IPv4 addresses to allocate them
>>    one per subscriber.  Several possible solutions to this problem are
>>    now emerging based around the idea of shared IPv4 addressing.  These
>>    solutions give rise to a number of issues and this memo identifies
>>    those common to all such address sharing approaches.  Solution-
>>    specific discussions are out of scope.
>
> ?? The abstract is a bit vague. It would be useful to summarize some 
> of the issues of note.
>
> ...
>> 1.  Introduction
> ...
>>
>>    Over the long term, deploying IPv6 is the only way to ease pressure
>>    on the public IPv4 address pool and thereby mitigate the need for
>>    address sharing mechanisms that give rise to the issues identified
>>    herein.
>
> ?? This sentence is misleading. Clearly address sharing eases pressure 
> too, but has caveats. It should be revised to be more clear about the 
> options available.
>
> ...
>> 2.  Shared Addressing Solutions
>
> This section should define address sharing. It's implied, and two 
> variants given (1:N NAT, and M:N pooled sharing), but that should be 
> made very direct and clear.
>
> ...
>>    In Figure 1 we have also tried to indicate (with 'xx') where issues
>>    are newly created in addition to what could be expected from the
>>    introduction of a traditional NAT device.  Issues marked with a
>>    single 'x' are already present today in the case of typical CPE NAT,
>>    however they can be expected to be more severe and widespread in the
>>    case of large-scale address sharing.
>
> ?? The notation description could be more clear, e.g. (presuming the 
> description is correct):
>
> ?? In this figure, "x" indicates issues already present with a NAT, 
> and "xx" are for those further issues introduced by pooled sharing.
>
> >  +------------------------------------------------+--------+---------+
> >  |                   Issue                        |   1st  |   3rd   |
> >  |                                                |  party | parties |
> >  +------------------------------------------------+--------+---------+
>
> This table is useful, but the issue descriptions are subjective in 
> some cases, where others are objective. All issues should be 
> objectively described.
>
> Further, some issues overlap - "Some applications will fail to 
> operate" can be related to other issues, e.g., lack of reverse DNS 
> (for apps using DNS names for ACLs), lack of ICMP (for apps using 
> transport requiring PMTUD, rather than PLPMTUD), etc.
>
> See the primary note above for items missing from this list.
>
> ...
>>    | Incoming connections to Well-Known Ports will  |    x   |         |
>>    | not work                                       |        |         |
>
> This will affect both Well-Known (i.e., user) and System ports. Use 
> the term "Assigned Ports" to refer to the sum of both ranges.
>
>> 5.  Port Allocation
> ...
>>    IANA has classified the whole port space into three categories (as
>>    defined in http://www.iana.org/assignments/port-numbers):
>
> Cite RFC 1340 here, rather than the web pages; that's where the ranges 
> were defined.
>
> It's useful here to define "Assigned" as including both Well-known and 
> Registered ranges as well (to refer to it later, e.g., in Sec 6).
>
> ...
>> 5.2.1.2.  NAT Port Mapping Protocol (NAT-PMP)
>>
>>    NAT-PMP already has a better semantic here, enabling the NAT to
>>    redirect the application to an available port number.
>
> ?? This section is brief; it would be useful to explain what is 
> better. Is it better because it can use ANY available port number? 
> What defines available?
>
>> 5.2.2.  Connection to a Well-Known Port Number
> ...
>>    For example, the use of DNS SRV records [RFC2782] provides a
>>    potential solution for subscribers wishing to host services in the
>>    presence of a shared-addressing scheme.  SRV records make it possible
>>    to specify a port value related to a service, thereby making services
>>    accessible on ports other than the Well-Known ports.  It is worth
>>    noting that this mechanism is not applicable to HTTP.
>
> It's not clear why HTTP is singled out here. Few of the commonly used 
> services rely on SRV records.
>
>> 6.  Impact on Applications
> ...
>>    o  Applications that use fixed ports (e.g., well-known ports) - see
>>       Section 5.2.2 for more discussion of this;
>
> Use the term "Assigned" here".
>
> ...
>>    o  Applications that do not use any port (e.g., ICMP) - where address
>>       sharing solutions map subscribers to (private) IP addresses on a
>>       one-to-one basis this will not be an issue, otherwise such
>>       applications will require special handling - see Section 9 for
>>       more discussion of this;
>
> ICMP does use port information, notably to demux the the signal to the 
> appropriate transport connection or association. An alternate example 
> might be useful.
>
> ...
>> 7.  Geo-location and Geo-proximity
>
> ?INT? This section is, IMO, odd; IP address never meant physical 
> location anyway, and tunnels obviate that meaning regardless of the 
> impact of NATs or other sharing techniques.

Perhaps it is an odd practice, but geo-location by IP is a very 
widespread technique, and address sharing does impact it. I do think it 
should be covered by the document.

>
> ...
>> 9.  ICMP
>>
>>    ICMP does not carry any port information and is consequently
>>    problematic for address sharing mechanisms.
>
> ICMP messages are specifically intended to include enough of the 
> transport header to enable port demuxing at the end receiver. When 
> that is not available, the demuxing fails. That can impact a number of 
> devices, including PMTUD.

Right.

>
>> 11.  Fragmentation
>>
>>    When a packet is fragmented, transport-layer port information (either
>>    UDP or TCP) is only present in the first fragment.  Subsequent
>>    fragments will not carry the port information and so will require
>>    special handling.
>
> ?INT? The ID will be incorrect too; it may not be unique as required 
> when viewed from the outside.

Yes. Though this seems to be an issue in existing NATs already. (But do 
the existing BEHAVE RFCs say something about IPID allocation/change by 
NATs?)

> ...
>> 13.  Security
>
> This section might also address the impact of sharing on X.509 
> authentication, e.g., that signs the name of a host. This can be 
> important for some applications.
>
>> 13.4.  Port Randomisation
> ...
>>    It should be noted that guessing the port information may not be
>>    sufficient to carry out a successful blind attack.   The exact TCP
>>    Sequence Number (SN) should also be known.
>
> There are data injection attacks that are possible even without 
> knowing the exact SN.
>
> Further, port randomization is just one way to protect a connection 
> (another includes timestamp verification, as noted in RFC4953).
>
> >    A TCP segment is
>>    processed only if all previous segments have been received, except
>>    for some Reset Segment implementations which immediately process the
>>    Reset as long as it is within the Window.
>
> Processing the reset if in-window is valid according to existing 
> standards. See Sec 1.1 of
> draft-ietf-tcpm-tcpsecure-13; i.e., it is a MAY except where 
> specifically warranted.
>
> ?? There's also a proposal for an experimental version of TCP-AO that 
> supports NAT traversal, FWIW (draft-touch-tcp-ao-nat).

Jari



From touch@isi.edu  Wed Feb  2 09:36:09 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24CF63A6D67; Wed,  2 Feb 2011 09:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.603
X-Spam-Level: 
X-Spam-Status: No, score=-102.603 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wf2Wx0Yi8ww; Wed,  2 Feb 2011 09:36:08 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 5ECF13A6D44; Wed,  2 Feb 2011 09:36:08 -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 p12HcsJV000763 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 09:38:54 -0800 (PST)
Message-ID: <4D4996AE.8060302@isi.edu>
Date: Wed, 02 Feb 2011 09:38:54 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar>
In-Reply-To: <4D490FED.6060303@gont.com.ar>
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>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 17:36:09 -0000

Hi, Fernando,

On 2/2/2011 12:03 AM, Fernando Gont wrote:
> On 01/02/2011 10:35 p.m., Joe Touch wrote:
...
>> ...
>>> 7.  Geo-location and Geo-proximity
>>
>> ?INT? This section is, IMO, odd; IP address never meant physical
>> location anyway, and tunnels obviate that meaning regardless of the
>> impact of NATs or other sharing techniques.
>
> Agreed. But geo-location is nevertheless widely used for marketing purposes.

Agreed, but whether it works now is arbitrary; it's not a design 
consideration of the protocols.

At the least, it's worth noting that geolocation is already broken by 
tunnels, and that IP addressing does not ensure geographic proximity 
before attributing breakage on NATs or other sharing.

>>> 13.4.  Port Randomisation
>> ...
>>>     It should be noted that guessing the port information may not be
>>>     sufficient to carry out a successful blind attack.   The exact TCP
>>>     Sequence Number (SN) should also be known.
>>
>> There are data injection attacks that are possible even without knowing
>> the exact SN.
>
> draft-ietf-tcpm-tcp-security may be of use here.

rfc5961 is already published and describes the issue in specific, and 
may be more useful as a reference for this.

>> Further, port randomization is just one way to protect a connection
>> (another includes timestamp verification, as noted in RFC4953).
>
> RFC4953 is a little bit vague in this respect.

Yes, but it does refer to the issue. The point is just that the current 
doc focuses on one way, there are others, and that's worth noting IMO.

Joe

From touch@isi.edu  Wed Feb  2 11:36:11 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB1A63A6D51; Wed,  2 Feb 2011 11:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.303
X-Spam-Level: 
X-Spam-Status: No, score=-104.303 tagged_above=-999 required=5 tests=[AWL=1.696, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0R6-fpDtH51i; Wed,  2 Feb 2011 11:36:10 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id B03943A6C41; Wed,  2 Feb 2011 11:36:10 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p12JcaEw028333 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 11:38:36 -0800 (PST)
Message-ID: <4D49B2BC.6050901@isi.edu>
Date: Wed, 02 Feb 2011 11:38:36 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	AssignedNumbers Authority (IANA) Proceduresfor	the	Management	of	the	Service	Nameand Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>	<4D44F85D.5030407@isi.edu>	<4D457FD9.5030905@vpnc.org>	<B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>	<4D46CC62.1040006@vpnc.org>	<3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>	<4D46D1D3.10701@vpnc.org>	<F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>	<4D46E623.3080602@ericsson.com>	<9E89C43A-EB2A-4DAB-9B12-A740612783E8@cisco.com>	<4D47DCF2.1000200@ericsson.com><4D483C4F.3080507@vpnc.org> <4D484543.7010601@isi.edu> <007101cbc2cb$8ee4cca0$4001a8c0@gateway.2wire.net>
In-Reply-To: <007101cbc2cb$8ee4cca0$4001a8c0@gateway.2wire.net>
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: Cullen Jennings <fluffy@cisco.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 19:36:11 -0000

Hi, Tom,

Thanks - yes, I can see where reordering the sentences in that paragraph 
could make the issue much clearer. I'll do that in the pending update ...

Joe

On 2/2/2011 3:22 AM, t.petch wrote:
> ----- Original Message -----
> From: "Joe Touch"<touch@isi.edu>
> To: "Paul Hoffman"<paul.hoffman@vpnc.org>
> "IETF discussion list"<ietf@ietf.org>;<tsvwg@ietf.org>; "IESG IESG"
> <iesg@ietf.org>
> Sent: Tuesday, February 01, 2011 6:39 PM
>
>> To clarify some of this discussion, providing some context that might be
>> useful:
>>
>> 1) the current doc already explicitly states the procedures for
>> assignment in each range of ports (see Sec 8.1.1).
>>
>> 2) Sec 8.1.1 *already* states that IESG approval through IETF process is
>> a valid path for assignment, distinct from Expert Review. Since that
>> appears to be a point of confusion, I'll quote it directly:
>>
>>      o  Ports in the User Ports range (1024-49151) are available for
>>         assignment through IANA, and MAY be used as service identifiers
>>         upon successful assignment.  Because assigning a port number for a
>>         specific application consumes a fraction of the shared resource
>>         that is the port number registry, IANA will require the requester
>>         to document the intended use of the port number.  This
>>         documentation will be input to the "Expert Review" procedure
>>         [RFC5226], by which IANA will have a technical expert review the
>>         request to determine whether to grant the assignment.  The
>>         submitted documentation MUST explain why using a port number in
>>         the Dynamic Ports range is unsuitable for the given application.
>>         Ports in the User Ports range may also be assigned under the "IETF
>>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>         Review" or "IESG Approval" procedures [RFC5226], which is how most
>>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>         assignments for IETF protocols are handled.
>>         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Joe
>
> I think that it is a point of confusion because the text is confused
> (well, it confuses me:-(.
>
> If you know in advance that there are two independent paths that
> can be taken, then you can read that meaning into it.
>
> If you do not know that, then having read
>                                                                       "This
>          documentation will be input to the "Expert Review" procedure
>          [RFC5226], by which IANA will have a technical expert review the
>          request to determine whether to grant the assignment"
>
> then it is obvious that Expert Review always happens, even when a later
> sentence talks about 'may also be assigned'.
>
> To make the two paths clear, the text should be reordered eg
>
>           Ports in the User Ports range (1024-49151) are available for
>          assignment through IANA, and MAY be used as service identifiers
>          upon successful assignment.  Because assigning a port number for a
>          specific application consumes a fraction of the shared resource
>          that is the port number registry, IANA will require the requester
>          to document the intended use of the port number.
>
> For most IETF protocols, ports in the User Ports range will be assigned under
> the "IETF
> Review" or "IESG Approval" procedures [RFC5226] and no further
> documentation is required.
>
> Where these procedures do not apply, then the requester must
> input the documentation to
>
>                                                              the "Expert Review"
> procedure
>          [RFC5226], by which IANA will have a technical expert review the
>          request to determine whether to grant the assignment.  The
>          submitted documentation MUST explain why using a port number in
>          the Dynamic Ports range is unsuitable for the given application.
>
> Tom Petch
>
>
>>
>>      o  Ports in the System Ports range (0-1023) are also available for
>>         assignment through IANA.  Because the System Ports range is both
>>         the smallest and the most densely allocated, the requirements for
>>         new assignments are more strict than those for the User Ports
>>         range, and will only be granted under the "IETF Review" or "IESG
>>                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>         Approval" procedures [RFC5226].  A request for a System Port
>>         ^^^^^^^^^
>>         number MUST document *both* why using a port number from the
>>         Dynamic Ports range is unsuitable *and* why using a port number
>>         from the User Ports range is unsuitable for that application.
>>
>> 3) section 7 has NOTHING TO DO with the procedures this document
>> updates. That section has plenty of words to avoid any such impression.
>> And no, we don't need to define "strives", IMO - since NOTHING IN THAT
>> SECTION IS BINDING.
>>
>> Again, since this is a persistent cause of confusion, I quote from that
>> section:
>>
>>      This section summarizes the current principles by which IANA handles
>>      the Service Name and Transport Protocol Port Number Registry and
>>      attempts to conserve the port number space.  This description is
>>      intended to inform applicants requesting service names and port
>>      numbers.  IANA has flexibility beyond these principles when handling
>>                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>      assignment requests; other factors may come into play, and exceptions
>>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>                                                             **************
>>      may be made to best serve the needs of the Internet.
>>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>      ***********
>>
>> If you need more explicit words, the term "non-binding" can be added.
>>
>> -------
>>
>> There's a doc I drafted in TSVWG which is a more appropriate venue to
>> discuss this issue (draft-touch-tsvwg-port-use0. I encourage those
>> interested in these issues to continue discussion on that list, not on
>> this general list.
>>
>> For this document, if this section is causing confusion, it should be
>> removed, since it is already included in this other doc and can be
>> vetted there.
>>
>> Joe
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf

From mohta@necom830.hpcl.titech.ac.jp  Wed Feb  2 13:52:57 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A39E3A6DCA for <ietf@core3.amsl.com>; Wed,  2 Feb 2011 13:52:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.693
X-Spam-Level: 
X-Spam-Status: No, score=0.693 tagged_above=-999 required=5 tests=[AWL=0.783,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 707tTAOgZZNY for <ietf@core3.amsl.com>; Wed,  2 Feb 2011 13:52:56 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 294E13A6D4D for <ietf@ietf.org>; Wed,  2 Feb 2011 13:52:55 -0800 (PST)
Received: (qmail 76491 invoked from network); 2 Feb 2011 22:02: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; 2 Feb 2011 22:02:18 -0000
Message-ID: <4D49D2C9.50508@necom830.hpcl.titech.ac.jp>
Date: Thu, 03 Feb 2011 06:55:21 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu>
In-Reply-To: <4D48B4EA.20503@isi.edu>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 21:52:57 -0000

Joe Touch wrote:

>> 9. ICMP
>>
>> ICMP does not carry any port information and is consequently
>> problematic for address sharing mechanisms.
> 
> ICMP messages are specifically intended to include enough of the 
> transport header to enable port demuxing at the end receiver.

I think it says ICMP information messages such as echo request
do not have port numbers.

However, ID and sequence number field of echo request can be
used (overridden) as source and destination port numbers,
respectively.

As the fields are copied as is from echo request to echo reply,
ID and sequence number field of echo request must be
used as destination and source (reversed) port numbers,
respectively.

It's implemented for end to end NAT and is working with "ping"
and "traceroute".

>> 11. Fragmentation
>>
>> When a packet is fragmented, transport-layer port information (either
>> UDP or TCP) is only present in the first fragment. Subsequent
>> fragments will not carry the port information and so will require
>> special handling.
> 
> ?INT? The ID will be incorrect too; it may not be unique as required 
> when viewed from the outside.

Port based redirection MUST be done after fragmentation reassembly.

That's all and is no special.

						Masataka Ohta

From touch@isi.edu  Wed Feb  2 14:01:33 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E84633A6E1E; Wed,  2 Feb 2011 14:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wRnvd+zAJ8vx; Wed,  2 Feb 2011 14:01:33 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 01F5C3A6E1A; Wed,  2 Feb 2011 14:01:32 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p12M4LL9006188 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 14:04:21 -0800 (PST)
Message-ID: <4D49D4E5.5020505@isi.edu>
Date: Wed, 02 Feb 2011 14:04:21 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D48F56B.7080402@piuha.net>
In-Reply-To: <4D48F56B.7080402@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p12M4LL9006188
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 22:01:34 -0000

Hi, Jari,

Notes below...

Joe

On 2/1/2011 10:10 PM, Jari Arkko wrote:
...
>> - parallel connections
>> i.e., that assume that a single IP address used
>> for multiple connections implies a single machine,
>> as with striping, multipath, or systems that use
>> multiple concurrent connections for different services
>> (somewhat related to load balancing in sec 16, but not necessarily)
>
> Why is this an issue? I thought that many of these mechanisms explicitly
> signal that a new connection is going to be established. Are there
> systems that assume that two independent connections are to the same
> machine, if they come from the same IP address? And isn't that
> assumption already broken by existing NATs?

Yes, and yes. The doc currently includes other such issues, and this 
seems worth including too.

>> - serial connections
>> i.e., that assume that returning to a given IP address returns to the
>> same physical host,
>> as with stateful transactions; this may also affect
>> cookie-based systems, such as TCP-CT, TCP with SYN
>> cookies, etc.
>
> OK. Interesting.

FWIW, this is like banking or other transaction systems, that use 
back-end data consistency or 'intelligent' routing to try to avoid 
sending series of connections to different places.

...
>> - address or DNS-name-based signatures
>> as in some X.509 signatures
>
> Why would DNS-name based certificates be an issue? You can still have
> multiple names per an IP address.

I might sign something with my hostname which isn't in the list of names 
for the shared address. I.e., this is a case where reverse DNS is the 
issue, but the impact is to a secondary system (X.509).

...
>> ...
>>> 7. Geo-location and Geo-proximity
>>
>> ?INT? This section is, IMO, odd; IP address never meant physical
>> location anyway, and tunnels obviate that meaning regardless of the
>> impact of NATs or other sharing techniques.
>
> Perhaps it is an odd practice, but geo-location by IP is a very
> widespread technique, and address sharing does impact it. I do think it
> should be covered by the document.

It should be, but it might be useful to note that geolocation by IP is a 
hueristic at best, and already challenged by other deployed capabilities 
(e.g., tunnels). The point is that the ability to do geolocation isn't 
part of IP, and isn't something that NAT/sharing breaks more than it's 
basically already broken, IMO.

I.e., it's useful to not imply that this issue will be fixed by avoiding 
NAT/sharing per se.

...
>>> 11. Fragmentation
>>>
>>> When a packet is fragmented, transport-layer port information (either
>>> UDP or TCP) is only present in the first fragment. Subsequent
>>> fragments will not carry the port information and so will require
>>> special handling.
>>
>> ?INT? The ID will be incorrect too; it may not be unique as required
>> when viewed from the outside.
>
> Yes. Though this seems to be an issue in existing NATs already. (But do
> the existing BEHAVE RFCs say something about IPID allocation/change by
> NATs?)

Yes, and not sure. Fragmentation causes multiple issues, not just the 
unknown port one.

---

From touch@isi.edu  Wed Feb  2 14:11:49 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34C9D3A6C3A for <ietf@core3.amsl.com>; Wed,  2 Feb 2011 14:11:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wy6c0+EIDXAo for <ietf@core3.amsl.com>; Wed,  2 Feb 2011 14:11:45 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 116013A6AF5 for <ietf@ietf.org>; Wed,  2 Feb 2011 14:11:44 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p12MEse2008012 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 14:14:54 -0800 (PST)
Message-ID: <4D49D75E.1010808@isi.edu>
Date: Wed, 02 Feb 2011 14:14:54 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D49D2C9.50508@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4D49D2C9.50508@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p12MEse2008012
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Feb 2011 22:11:49 -0000

On 2/2/2011 1:55 PM, Masataka Ohta wrote:
> Joe Touch wrote:
>
>>> 9. ICMP
>>>
>>> ICMP does not carry any port information and is consequently
>>> problematic for address sharing mechanisms.
>>
>> ICMP messages are specifically intended to include enough of the
>> transport header to enable port demuxing at the end receiver.
>
> I think it says ICMP information messages such as echo request
> do not have port numbers.

I quoted the start of the section. The first sentence, without further 
qualification, is inaccurate, IMO.

ICMP messages do not themselves have port numbers, but they are intended 
to *carry* port numbers of the messages that caused their generation (if 
they report errors).

> However, ID and sequence number field of echo request can be
> used (overridden) as source and destination port numbers,
> respectively.

This is relevant to the generation of new ICMPs that are not the result 
of errors - e.g., echo request. The section is written so generally as 
to include ICMPs that are responses to errors too, typically as 
generated by packet arrivals.

> As the fields are copied as is from echo request to echo reply,
> ID and sequence number field of echo request must be
> used as destination and source (reversed) port numbers,
> respectively.
>
> It's implemented for end to end NAT and is working with "ping"
> and "traceroute".
>
>>> 11. Fragmentation
>>>
>>> When a packet is fragmented, transport-layer port information (either
>>> UDP or TCP) is only present in the first fragment. Subsequent
>>> fragments will not carry the port information and so will require
>>> special handling.
>>
>> ?INT? The ID will be incorrect too; it may not be unique as required
>> when viewed from the outside.
>
> Port based redirection MUST be done after fragmentation reassembly.
>
> That's all and is no special.

IMO, any device that initiates packets MUST verify that the IDs emitted 
follow spec. Once a packet's address(es) are rewritten, the NAT is 
responsible for ensuring that the IDs are unique across the 
src/dst/proto triple.

I'm not aware of NATs that do this; they typically copy the ID field, 
and this can easily cause reassembly errors later - even if the packet 
is reassembled at the NAT itself.

See draft-ietf-intarea-ipv4-id-update for more a discussion of this 
issue and the proposed requirements to address it.

Joe

From fernando.gont.netbook.win@gmail.com  Wed Feb  2 17:02:02 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69EFF3A65A6; Wed,  2 Feb 2011 17:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level: 
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYtjwnZxzog8; Wed,  2 Feb 2011 17:01:59 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 295693A65A5; Wed,  2 Feb 2011 17:01:59 -0800 (PST)
Received: by gyd12 with SMTP id 12so287103gyd.31 for <multiple recipients>; Wed, 02 Feb 2011 17:05:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=+VwlH6WJB8cVo20qMv9TQ8jz1ENB3e8Ley1WbLBBRgc=; b=e48AjFCb2gWpHe4GYcQSGXEf/Y13fonUutF6qIvhZnqmP6dP2diYOBoaGIcziQ/Btp owta8zzFe5YnAPZANPLqIBCL7ZCp5ixizbx6Vnb4Da+dgt5UxYSgcKlTii+ds53/pdWe jYv0uEwpsNhs84TAL7rS7S0qV3z7kXaVt3Ngk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=rNBltDIYh0zZRgDN55ZzfJ8Kq1UOq9x13XRY1nPLkufryeAKoJMWLwlk23W6dUn5PL PpiW9igrF1xY5raePbXdmU1Y0R2J9nuN+BI8GHP2qHz85g9mwEM7fiEi6MR4MszLsDL3 csGPrz3kjPvc1gCf3N57mQntzj7tpDmYyyI8U=
Received: by 10.236.95.17 with SMTP id o17mr20544236yhf.10.1296695119842; Wed, 02 Feb 2011 17:05:19 -0800 (PST)
Received: from [192.168.0.123] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id 50sm145353yhl.29.2011.02.02.17.05.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 17:05:18 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D49FF33.7030107@gont.com.ar>
Date: Wed, 02 Feb 2011 22:04:51 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu>
In-Reply-To: <4D4996AE.8060302@isi.edu>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 01:02:02 -0000

On 02/02/2011 02:38 p.m., Joe Touch wrote:

>>> ?INT? This section is, IMO, odd; IP address never meant physical
>>> location anyway, and tunnels obviate that meaning regardless of the
>>> impact of NATs or other sharing techniques.
>>
>> Agreed. But geo-location is nevertheless widely used for marketing
>> purposes.
> 
> Agreed, but whether it works now is arbitrary; it's not a design
> consideration of the protocols.

Well, the protocols were not designed for production networks, either.
FWIW, geo-location is currently used, and it would be affected by
increased used of NATs.


> At the least, it's worth noting that geolocation is already broken by
> tunnels, and that IP addressing does not ensure geographic proximity
> before attributing breakage on NATs or other sharing.

Tunnels need not break geo-location. -- They do not masquerade the
source address. Or am I missing something?

And, FWIW, I agree that usually lots of breakage is attributed to NATs,
where the brokeness is really somewhere else (e.g., app protocols
passing IP addresses).


>>>> 13.4.  Port Randomisation
>>> ...
>>>>     It should be noted that guessing the port information may not be
>>>>     sufficient to carry out a successful blind attack.   The exact TCP
>>>>     Sequence Number (SN) should also be known.
>>>
>>> There are data injection attacks that are possible even without knowing
>>> the exact SN.
>>
>> draft-ietf-tcpm-tcp-security may be of use here.
> 
> rfc5961 is already published and describes the issue in specific, and
> may be more useful as a reference for this.

I disagree. It discusses only TCP-based attacks (there are many other
vectors). If you want an alternative "published" reference, here it is:
http://www.cpni.gov.uk/Docs/tn-03-09-security-assessment-TCP.pdf

However, it's up to the authors to include this or other references -- I
just noted the tcp assessment doc for completeness sake.

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





From touch@isi.edu  Wed Feb  2 17:06:05 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B43713A676A; Wed,  2 Feb 2011 17:06:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.617
X-Spam-Level: 
X-Spam-Status: No, score=-104.617 tagged_above=-999 required=5 tests=[AWL=1.982, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KuUiCIV7NzDp; Wed,  2 Feb 2011 17:06:05 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 033103A63EC; Wed,  2 Feb 2011 17:06:04 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p1318dFc002088 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 17:08:39 -0800 (PST)
Message-ID: <4D4A0017.6050401@isi.edu>
Date: Wed, 02 Feb 2011 17:08:39 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar>
In-Reply-To: <4D49FF33.7030107@gont.com.ar>
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>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 01:06:05 -0000

On 2/2/2011 5:04 PM, Fernando Gont wrote:
...
>> At the least, it's worth noting that geolocation is already broken by
>> tunnels, and that IP addressing does not ensure geographic proximity
>> before attributing breakage on NATs or other sharing.
>
> Tunnels need not break geo-location. -- They do not masquerade the
> source address. Or am I missing something?

When I tunnel using an ISI address, whomever sees my address thinks I'm 
in California.

Except that there's an ISI office in Virginia too.

And if I'm VPN'd in, the tunnel makes me have an ISI IP address 
regardless of where I actually am.

Joe

From fernando.gont.netbook.win@gmail.com  Wed Feb  2 17:21:43 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAC593A6767; Wed,  2 Feb 2011 17:21:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.522
X-Spam-Level: 
X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cniDiljh4ulH; Wed,  2 Feb 2011 17:21:42 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id DB4F23A6407; Wed,  2 Feb 2011 17:21:41 -0800 (PST)
Received: by yxt33 with SMTP id 33so302152yxt.31 for <multiple recipients>; Wed, 02 Feb 2011 17:25:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=4qXSYKTyiE0pwXmWVYivjj+oYFCmgeUQxum+3onWF14=; b=R7/0Kas92B5vItx7hnBKCX8+Ktj/MJ5v8VgHupOcpzYaVXSHcPlboKESBuaUuT11dk urclY6cJ6ug3A/GxxHEHZceFxMIjGyS54TR/rOrPaz4+tBt33QqZMVPvrbGLJTbXdbP4 HhlwvX8Zp/ZVDXdk2iMBpWY8JSkZ/FiLd91Wc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=rEqwqPJkTIoDNY7ukiA7qZs+7FYn4xpln8bthl+urvd9zD8obOI/pJfAW+JDGK/N3F D/ZlCA4S8hVN6o/3zkJ0Ax+rXl2ARFuiqemuixm1rpgTdXFlXDCXbcZstG3DTuN9uAef FTdHRti7XzCLVO023WoKlSJOfTD9NFvT1MMfc=
Received: by 10.150.199.16 with SMTP id w16mr328837ybf.136.1296696302209; Wed, 02 Feb 2011 17:25:02 -0800 (PST)
Received: from [192.168.0.123] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id p32sm57ybk.20.2011.02.02.17.24.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 17:25:01 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D4A03CE.9020105@gont.com.ar>
Date: Wed, 02 Feb 2011 22:24:30 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar> <4D4A0017.6050401@isi.edu>
In-Reply-To: <4D4A0017.6050401@isi.edu>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 01:21:43 -0000

On 02/02/2011 10:08 p.m., Joe Touch wrote:

> On 2/2/2011 5:04 PM, Fernando Gont wrote:
> ...
>>> At the least, it's worth noting that geolocation is already broken by
>>> tunnels, and that IP addressing does not ensure geographic proximity
>>> before attributing breakage on NATs or other sharing.
>>
>> Tunnels need not break geo-location. -- They do not masquerade the
>> source address. Or am I missing something?
> 
> When I tunnel using an ISI address, whomever sees my address thinks I'm
> in California.
[..]

Ok.. I see. I was thinking about tunnels in the infrastructure. -- those
are transparent in this respect.

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





From fernando.gont.netbook.win@gmail.com  Wed Feb  2 17:27:13 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B5983A679C; Wed,  2 Feb 2011 17:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbwBTgXziWP7; Wed,  2 Feb 2011 17:27:12 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 933D23A66B4; Wed,  2 Feb 2011 17:27:12 -0800 (PST)
Received: by gxk27 with SMTP id 27so295334gxk.31 for <multiple recipients>; Wed, 02 Feb 2011 17:30:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=W54nJFMkJ0to/tyrhh8gqTgJIwXiNpqZ/zhq/ZEmN4Q=; b=QXnFsgBN+HNmUtLrJrpFa/cYh9UoJsi2/hzucs8kWIsK8OnrFdlN1B+CFDZiEkYbrq KRIHaHV7iKFHa4N2jpnro+epd2x1+MNGPX5xF6IknPQ+n7iv4lb84hV0gseU6Kkhe3KE bLbLkAaCszEtT1PLcgVOtW4CSULbZJ112t9XU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=UE9vFebyl3YhBBirk34OM0tTgsIOu/6oRbphKDpckZK7mWpzgZzOEmS0uLqmnHRJlK IbEYacRCtulPxhVsqk67U2y0rrd2VG1qmEZMCCKUby0Tx/oYORppYz7iVZAuOZw32avt N6jhgvT3+Mw/p8mkMu/ypZjNfdPCeuivt4vx8=
Received: by 10.100.8.9 with SMTP id 9mr6391208anh.120.1296696633223; Wed, 02 Feb 2011 17:30:33 -0800 (PST)
Received: from [192.168.0.123] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id e24sm289585ana.22.2011.02.02.17.30.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 17:30:32 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D4A051C.1060501@gont.com.ar>
Date: Wed, 02 Feb 2011 22:30:04 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar> <4D4A0017.6050401@isi.edu> <4D4A03CE.9020105@gont.com.ar>
In-Reply-To: <4D4A03CE.9020105@gont.com.ar>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 01:27:13 -0000

On 02/02/2011 10:24 p.m., Fernando Gont wrote:
>> On 2/2/2011 5:04 PM, Fernando Gont wrote:
>> ...
>>>> At the least, it's worth noting that geolocation is already broken by
>>>> tunnels, and that IP addressing does not ensure geographic proximity
>>>> before attributing breakage on NATs or other sharing.
>>>
>>> Tunnels need not break geo-location. -- They do not masquerade the
>>> source address. Or am I missing something?
>>
>> When I tunnel using an ISI address, whomever sees my address thinks I'm
>> in California.
> [..]

And one might argue that, in this type of scenario, this "breakeage" of
geo-location might, in some cases, be desirable.

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





From touch@isi.edu  Wed Feb  2 17:46:15 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A634F3A6452; Wed,  2 Feb 2011 17:46:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.632
X-Spam-Level: 
X-Spam-Status: No, score=-102.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWc77wnNG-vm; Wed,  2 Feb 2011 17:46:14 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 854633A63CB; Wed,  2 Feb 2011 17:46:14 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p131nPQi015959 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 17:49:25 -0800 (PST)
Message-ID: <4D4A09A5.3050306@isi.edu>
Date: Wed, 02 Feb 2011 17:49:25 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar> <4D4A0017.6050401@isi.edu> <4D4A03CE.9020105@gont.com.ar> <4D4A051C.1060501@gont.com.ar>
In-Reply-To: <4D4A051C.1060501@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p131nPQi015959
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 01:46:15 -0000

On 2/2/2011 5:30 PM, Fernando Gont wrote:
> On 02/02/2011 10:24 p.m., Fernando Gont wrote:
>>> On 2/2/2011 5:04 PM, Fernando Gont wrote:
>>> ...
>>>>> At the least, it's worth noting that geolocation is already broken by
>>>>> tunnels, and that IP addressing does not ensure geographic proximity
>>>>> before attributing breakage on NATs or other sharing.
>>>>
>>>> Tunnels need not break geo-location. -- They do not masquerade the
>>>> source address. Or am I missing something?
>>>
>>> When I tunnel using an ISI address, whomever sees my address thinks I'm
>>> in California.
>> [..]
>
> And one might argue that, in this type of scenario, this "breakeage" of
> geo-location might, in some cases, be desirable.

It can't break if it was never intended to work.

Anyone who thinks that IP address = location is as incorrect as those 
who assume area code = location these days.

I.e., the overall assumption was never true. The fact is that it 
*sometimes* works, that's all.

Joe

From touch@isi.edu  Wed Feb  2 17:47:04 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09D5E3A657C; Wed,  2 Feb 2011 17:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.632
X-Spam-Level: 
X-Spam-Status: No, score=-102.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yt5lbB6-SS55; Wed,  2 Feb 2011 17:47:03 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 3A44F3A6452; Wed,  2 Feb 2011 17:47:03 -0800 (PST)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p131nwnc015989 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 2 Feb 2011 17:49:58 -0800 (PST)
Message-ID: <4D4A09C6.7080009@isi.edu>
Date: Wed, 02 Feb 2011 17:49:58 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar> <4D4A0017.6050401@isi.edu> <4D4A03CE.9020105@gont.com.ar>
In-Reply-To: <4D4A03CE.9020105@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p131nwnc015989
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 01:47:04 -0000

On 2/2/2011 5:24 PM, Fernando Gont wrote:
> On 02/02/2011 10:08 p.m., Joe Touch wrote:
>
>> On 2/2/2011 5:04 PM, Fernando Gont wrote:
>> ...
>>>> At the least, it's worth noting that geolocation is already broken by
>>>> tunnels, and that IP addressing does not ensure geographic proximity
>>>> before attributing breakage on NATs or other sharing.
>>>
>>> Tunnels need not break geo-location. -- They do not masquerade the
>>> source address. Or am I missing something?
>>
>> When I tunnel using an ISI address, whomever sees my address thinks I'm
>> in California.
> [..]
>
> Ok.. I see. I was thinking about tunnels in the infrastructure. -- those
> are transparent in this respect.

Yes. It's tunnels at the endpoints I'm using as an example here.

Joe

From fernando.gont.netbook.win@gmail.com  Wed Feb  2 18:41:20 2011
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 773843A67B0; Wed,  2 Feb 2011 18:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.034
X-Spam-Level: 
X-Spam-Status: No, score=-3.034 tagged_above=-999 required=5 tests=[AWL=0.565,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHQbQ9V08hCt; Wed,  2 Feb 2011 18:41:19 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 5B5EE3A6778; Wed,  2 Feb 2011 18:41:19 -0800 (PST)
Received: by gwb20 with SMTP id 20so314280gwb.31 for <multiple recipients>; Wed, 02 Feb 2011 18:44:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=CscBwCFkvU5eFQvbP84UZRTwohHxRwYq03s5S9xMuGY=; b=LmfRR3sOE6GUZpNkFnQp+hUnKWy1OvjW4TBgoOZjSCA8ZDAehq0S8wd70Ekd4FNus0 RhtV8w9ICc5A7H4OmCKwdjg0sPo2QmlOL+qdcVZveO5TR0Xm36S7K14vsbmwI2tMJuc7 GL/LNQYowYOV+Nd6fU+buuJItk8SDC3A4HLSk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=oodnn81BSIvsYqTUFaxB8GI5l2Xg0UhGDxEUex1qKkgPXZHKAxIIOQCUro5Pzrq0MG SNZTU9dvpFaYvsFaxxaoyHu+aI0cRXkTe8FAxs1i/RiB2oqZjKZzBcbpVe10yAf/Q66Q gU4pC+IxwhdAiNen/eWY1+L2OLTpFI1fzjlNA=
Received: by 10.90.89.3 with SMTP id m3mr13188494agb.120.1296701080226; Wed, 02 Feb 2011 18:44:40 -0800 (PST)
Received: from [192.168.123.101] ([190.48.212.16]) by mx.google.com with ESMTPS id b11sm363388ana.18.2011.02.02.18.44.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 18:44:39 -0800 (PST)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4D4A168C.6060100@gont.com.ar>
Date: Wed, 02 Feb 2011 23:44:28 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar> <4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar> <4D4A0017.6050401@isi.edu> <4D4A03CE.9020105@gont.com.ar> <4D4A051C.1060501@gont.com.ar> <4D4A09A5.3050306@isi.edu>
In-Reply-To: <4D4A09A5.3050306@isi.edu>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, draft-ietf-intarea-shared-addressing-issues@tools.ietf.org, IETF discussion list <ietf@ietf.org>, TSV Dir <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 02:41:20 -0000

Joe,

On 02/02/2011 10:49 p.m., Joe Touch wrote:
>>>> When I tunnel using an ISI address, whomever sees my address thinks I'm
>>>> in California.
>>> [..]
>>
>> And one might argue that, in this type of scenario, this "breakeage" of
>> geo-location might, in some cases, be desirable.
> 
> It can't break if it was never intended to work.

I've been attended presentations in which people have argued that this
geo-location thing (i.e., multiple-layers of NATs breaking it) is yet
another motivation for v6. -- I don't buy it (nor do I buy much of the
"NAT is evil" and similar stuff).

But this thing is being used, and if multiple layers of NAT will break
it (or, "will prevent it to work the way it used to", if you prefer), it
should be noted.

The fact that geo-location was not considered in the IP design, is
irrelevant. As noted, IP wasn't meant for production, either.

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





From mohta@necom830.hpcl.titech.ac.jp  Thu Feb  3 01:47:09 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FC733A68D2 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 01:47:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.606
X-Spam-Level: 
X-Spam-Status: No, score=0.606 tagged_above=-999 required=5 tests=[AWL=0.696,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6L+0kZEpPiEM for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 01:47:08 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 6EEE43A68A0 for <ietf@ietf.org>; Thu,  3 Feb 2011 01:47:06 -0800 (PST)
Received: (qmail 92760 invoked from network); 3 Feb 2011 09:56:07 -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; 3 Feb 2011 09:56:07 -0000
Message-ID: <4D4A79ED.1060104@necom830.hpcl.titech.ac.jp>
Date: Thu, 03 Feb 2011 18:48:29 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D49D2C9.50508@necom830.hpcl.titech.ac.jp> <4D49D75E.1010808@isi.edu>
In-Reply-To: <4D49D75E.1010808@isi.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 09:47:09 -0000

Joe Touch wrote:

>>>> 9. ICMP

> I quoted the start of the section. The first sentence, without further 
> qualification, is inaccurate, IMO.

Anyway, most of the discussion in the section is inapplicable to
end to end NAT where public source addresses are used even within
private networks.

> ICMP messages do not themselves have port numbers, but they are intended 
> to *carry* port numbers of the messages that caused their generation (if 
> they report errors).

FYI, traceroute both with UDP or ICMP ECHO is working to/from
/between private network behind end to end gateway is working.

> IMO, any device that initiates packets MUST verify that the IDs emitted 
> follow spec. Once a packet's address(es) are rewritten, the NAT is 
> responsible for ensuring that the IDs are unique across the 
> src/dst/proto triple.
> 
> I'm not aware of NATs that do this; they typically copy the ID field, 
> and this can easily cause reassembly errors later - even if the packet 
> is reassembled at the NAT itself.

IC. We can rely on random id and transport checksum, then.

> See draft-ietf-intarea-ipv4-id-update for more a discussion of this 
> issue and the proposed requirements to address it.

It should be noted that packet smaller than 69B is also atomic.

The problem of the draft (and IPv6) is that it depends on PMTUD.

PMTUD just does not work. Worse, PMTUD is inefficient. That is,
that PMTUD periodically sends oversized packets means PMTUD
overloads routers, just as IPv4 fragmentation overloads routers.

If we write a draft on IPv6 issues, it should contain a lot
more and a lot more serious issues than those of shared
addressing.

						Masataka Ohta

From evnikita2@gmail.com  Thu Feb  3 06:59:49 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 409353A69A7 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 06:59:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.217
X-Spam-Level: 
X-Spam-Status: No, score=-2.217 tagged_above=-999 required=5 tests=[AWL=-0.578, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uimRD+-uGtWL for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 06:59:48 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 065663A69A0 for <ietf@ietf.org>; Thu,  3 Feb 2011 06:59:47 -0800 (PST)
Received: by fxm9 with SMTP id 9so1362259fxm.31 for <ietf@ietf.org>; Thu, 03 Feb 2011 07:03:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yywQBcku1k2gdBGY3Xa+4Z7ePVY+qjWKaTipDdFLkw0=; b=opczWZkkI7IKjo0bec54Ddy1P1EvKO9z3XL50TJUmODEQC6gn7SsTskgjmQ3nH1u79 Mm7MboVjuXzSzCpMOgvhMW5aBUlGI6vrKAKeMRXDaWlW9pEb6eIbK3RAyenNW2HWivDG oYi45XGYkvOC7wh3Z4oJZrB2sYDXKMSZrVxCM=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=dlsmyZlGLUe/EasTVdhKdsWF9El484GHoXU8SpE4IgZy8z8E59Hxhu5D4VkhAxVIaD ActdpGE7ofKzPlvWvXpYblbrR9ZI2L7LlkOZLgwlTQRx4hknDgFokVJm1WCdKRbeokky mEQ6WLaEOPf8jT12lBUOEK19YTMH5eLTOeQCU=
Received: by 10.223.81.76 with SMTP id w12mr2795439fak.26.1296745389993; Thu, 03 Feb 2011 07:03:09 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n7sm318631fam.11.2011.02.03.07.03.08 (version=SSLv3 cipher=RC4-MD5); Thu, 03 Feb 2011 07:03:08 -0800 (PST)
Message-ID: <4D4AC3C3.5020003@gmail.com>
Date: Thu, 03 Feb 2011 17:03:31 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-eggert-tcpm-historicize-00.txt> (Moving the Undeployed TCP Extensions RFC1072, RFC1106, RFC1110, RFC1145, RFC1146, RFC1263,  RFC1379, RFC1644 and RFC1693 to Historic Status) to Informational RFC
References: <20110202215157.24554.29312.idtracker@localhost>
In-Reply-To: <20110202215157.24554.29312.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 14:59:49 -0000

Hello all,

While I fully agree with what this document proposes.  This might be an 
editorial comment but I 've noticed that RFC 1072 is not mentioned to be 
made Historic despite the option specified by it is made obsolete.  What 
is more, referencing all the documents made obsolete normatively is OK?  
Here I suggest only RFC 4614 to be mentioned in this way.

However I'd like to raise some questions not directly connected to this 
document.  I wonder why those who said a few weeks ago that 
historicizing some documents in the similar situation is not appropriate 
do not object now.  The arguments of these folks were that RFC 2026 sets 
the criteria for Historic status as 'replaced by other doc' and did not 
consider 'being deprecated' (what exactly we have in the current case) 
as weighty reason for historicizing document.

Moreover, there are no clear procedures for moving documents to 
Historic.  So everybody who wants to propose to move some RFC to 
Historic must think out what procedures should be used or find them out 
in the most recent documents.

Up to this day there are neither any clear definition of Historic RFC 
status nor procedures for historicizing RFCs.  Should this continue?

Mykyta Yevstifeyev

02.02.2011 23:51, The IESG wrote:
> The IESG has received a request from the TCP Maintenance and Minor
> Extensions WG (tcpm) to consider the following document:
> - 'Moving the Undeployed TCP Extensions RFC1072, RFC1106, RFC1110,
>     RFC1145, RFC1146, RFC1263, RFC1379, RFC1644 and RFC1693 to Historic
>     Status'
>    <draft-eggert-tcpm-historicize-00.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 2011-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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-eggert-tcpm-historicize/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-eggert-tcpm-historicize/
>
>
>
> 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 twalsh@juniper.net  Thu Feb  3 07:43:21 2011
Return-Path: <twalsh@juniper.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A7D93A6984 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 07:43:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.478
X-Spam-Level: 
X-Spam-Status: No, score=-106.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id niXAEhHMhctS for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 07:43:20 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by core3.amsl.com (Postfix) with ESMTP id D06993A69AB for <ietf@ietf.org>; Thu,  3 Feb 2011 07:43:17 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTUrN35WIjcptWobIyRLQMC+ZdWnF64+n@postini.com; Thu, 03 Feb 2011 07:46:40 PST
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 3 Feb 2011 07:38:06 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 3 Feb 2011 10:40:13 -0500
From: Thomas Walsh <twalsh@juniper.net>
To: IETF discussion list <ietf@ietf.org>
Date: Thu, 3 Feb 2011 10:40:12 -0500
Subject: FW: NomCom 2010-2011: IAB Appointments 
Thread-Topic: NomCom 2010-2011: IAB Appointments 
Thread-Index: AcvDuE8BgRZ+2XS1QbCrOGcN6HEdIAAAE7bg
Message-ID: <A4C6A166C36F5F40A5767E6F66358FC092E095CC2C@EMBX01-WF.jnpr.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 15:43:21 -0000

-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org=
] On Behalf Of NomCom Chair
Sent: Thursday, February 03, 2011 7:34 AM
To: IETF Announcement list
Subject: NomCom 2010-2011: IAB Appointments=20

Hi Folks,=20

The 2010-2011 IETF Nominating committee is pleased to announce the=20
selection of the IAB members whose two year terms start in March 2011.

The following, listed alphabetically by last name, have been selected to
serve as members of the IAB by the nominating committee and confirmed=20
by the ISOC Board of Trustees in their role as confirming body:=20

Alissa Cooper=20
Joel Halpern=20
David Kessens=20
Danny McPherson=20
Jon Peterson=20
Dave Thaler

Our thanks to the incumbents who are not returning for their outstanding
service, to the many qualified members of the community who offered to=20
serve, to the community for their assistance in this process, and to the=20
named individuals above for agreeing to serve the community on the IAB.=20

Best Regards,=20

Thomas Walsh=20
nomcom-chair@ietf.org=20
twalsh@juniper.net=20




_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From lars.eggert@nokia.com  Thu Feb  3 09:37:26 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 749AB3A6A45 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 09:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.686
X-Spam-Level: 
X-Spam-Status: No, score=-103.686 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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rjt43c2qW01F for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 09:37:25 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 7B86A3A6A3F for <ietf@ietf.org>; Thu,  3 Feb 2011 09:37:25 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p13Hehiq020393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Feb 2011 19:40:44 +0200
Subject: Re: Last Call: <draft-eggert-tcpm-historicize-00.txt> (Moving the Undeployed TCP Extensions RFC1072, RFC1106, RFC1110, RFC1145, RFC1146, RFC1263, RFC1379, RFC1644 and RFC1693 to Historic Status) to Informational RFC
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-53-620061018; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4D4AC3C3.5020003@gmail.com>
Date: Thu, 3 Feb 2011 19:40:40 +0200
Message-Id: <DE07D0D2-53F6-4C55-9EB4-0CC7348B8DE2@nokia.com>
References: <20110202215157.24554.29312.idtracker@localhost> <4D4AC3C3.5020003@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Thu, 03 Feb 2011 19:40:41 +0200 (EET)
X-Nokia-AV: Clean
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 17:37:26 -0000

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

Hi,

On 2011-2-3, at 17:03, Mykyta Yevstifeyev wrote:
> While I fully agree with what this document proposes.  This might be =
an editorial comment but I 've noticed that RFC 1072 is not mentioned to =
be made Historic despite the option specified by it is made obsolete.

you mean it's missing from Section 2? Good catch. I'll add that in my =
working copy.

>  What is more, referencing all the documents made obsolete normatively =
is OK?  Here I suggest only RFC 4614 to be mentioned in this way.

I guess they could become informative references, but you could also =
argue that they are required background reading and hence should be =
normative.

Lars=

--Apple-Mail-53-620061018
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDIwMzE3NDA0MVowIwYJKoZIhvcNAQkE
MRYEFO9NGf7YIv2pEcFY8R7c+RqB2k3CMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AGrX2UaCqjbKGjYDODbVtsBEiZ2m4/ZootrQoNAQpIaiEXVvV5vw2gdXPflMf8mZtpDePv8Zh/Dy
en6RgpDZ1jYtcqmBExJaka7CHKGScMSfk37kDWzWepRLZiyAdqo31qkoIo9qTX1DoKkx1UTrkBGa
KnllLNILNcHrobjdEsLvGs3ioCcYKjXZxUXliE3MYIR259tmyG7Op6S7VxXr6L3/4ml6H5YPwLtS
Dde56qWhzTa4ReEdRebGmdwlFzhecSDftG03Wl/z3cqrS9PJMOHaonzvNeIT5FsKx0bvXGdQGNZ8
pCGiBYZWaxQ9cQS3rPgYWunANyb4te52w8duCuoAAAAAAAA=

--Apple-Mail-53-620061018--

From touch@isi.edu  Thu Feb  3 10:09:32 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D8203A69A8 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 10:09:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.632
X-Spam-Level: 
X-Spam-Status: No, score=-104.632 tagged_above=-999 required=5 tests=[AWL=1.967, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNUXIoIYnlb3 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 10:09:31 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id CAFB33A69F3 for <ietf@ietf.org>; Thu,  3 Feb 2011 10:09:31 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p13IBItF013866 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 3 Feb 2011 10:12:27 -0800 (PST)
Message-ID: <4D4AEFC6.70901@isi.edu>
Date: Thu, 03 Feb 2011 10:11:18 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D49D2C9.50508@necom830.hpcl.titech.ac.jp> <4D49D75E.1010808@isi.edu> <4D4A79ED.1060104@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4D4A79ED.1060104@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 18:09:32 -0000

On 2/3/2011 1:48 AM, Masataka Ohta wrote:
> Joe Touch wrote:
> 
>>>>> 9. ICMP
> 
>> I quoted the start of the section. The first sentence, without further
>> qualification, is inaccurate, IMO.
...
>> ICMP messages do not themselves have port numbers, but they are intended
>> to *carry* port numbers of the messages that caused their generation (if
>> they report errors).
> 
> FYI, traceroute both with UDP or ICMP ECHO is working to/from
> /between private network behind end to end gateway is working.

Understood, but my issue is that "ICMP" is more than just ICMP echo;
many other messages are the result of sending a regular packet (as with
traceroute), and those are intended to include both the address and port
of the packet that causes the ICMP.

>> IMO, any device that initiates packets MUST verify that the IDs emitted
>> follow spec. Once a packet's address(es) are rewritten, the NAT is
>> responsible for ensuring that the IDs are unique across the
>> src/dst/proto triple.
>>
>> I'm not aware of NATs that do this; they typically copy the ID field,
>> and this can easily cause reassembly errors later - even if the packet
>> is reassembled at the NAT itself.
> 
> IC. We can rely on random id and transport checksum, then.

Transport checksum works only if the entire transport packet is included
in the ICMP response, and should not be relied on because it's only a
SHOULD to include the entire packet (and that entire packet wouldn't fit
if it was already at the path MTU anyway - there wouldn't be room for
the ICMP "IP" header or its additional fields).

>> See draft-ietf-intarea-ipv4-id-update for more a discussion of this
>> issue and the proposed requirements to address it.
> 
> It should be noted that packet smaller than 69B is also atomic.

Packet size is not a consideration in whether a packet is atomic.

Packets under 69B must be able to be carried without fragmentation by a
link as per RFC791, but there's nothing in RFC791 that prohibits such
packets from being fragmented anyway. The only trick would be that the
node that did such fragmentation would need to know when to stop - so
that a packet with a max IP header and at least one 8-octet fragment
could eventually get through. But nothing in RFC791 requires that this
be the original packet.

> The problem of the draft (and IPv6) is that it depends on PMTUD.

Please explain how and where. PMUTD isn't even discussed or cited.

Joe

From chair@ietf.org  Thu Feb  3 11:41:00 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C0AC3A6A07 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 11:41:00 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxJCAGABh5Pk for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 11:40:59 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 332C53A67B0 for <ietf@ietf.org>; Thu,  3 Feb 2011 11:40:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 86493E0801 for <ietf@ietf.org>; Thu,  3 Feb 2011 11:44:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdQKsSgoAddJ for <ietf@ietf.org>; Thu,  3 Feb 2011 11:44:22 -0800 (PST)
Received: from [10.2.2.40] (unknown [12.154.31.2]) by c1a.amsl.com (Postfix) with ESMTPSA id 2A1DBE077B for <ietf@ietf.org>; Thu,  3 Feb 2011 11:44:22 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Final IPv4 Unicast Address Allocations
Date: Thu, 3 Feb 2011 14:44:05 -0500
In-Reply-To: <AE9AF8F6-4D0E-41D6-8CF8-34DA55E6443A@icann.org>
To: IETF <ietf@ietf.org>
Message-Id: <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 19:41:00 -0000

You have probably already heard the news, but just to make sure no one =
is left out of the loop, I am posting this note.

The last five /8 IPv4 address blocks were assigned today.

Two /8s were recently allocated to APNIC, which triggered the =
implementation of the Exhaustion Phase set out in the Global Policy for =
the Allocation of the Remaining IPv4 Address Space.  Today in Miami, =
Florida in a very nice ceremony, this policy was implemented, and each =
RIR received one of the final /8 address blocks.  As of now, there are =
no more unallocated IPv4 unicast /8s in the IANA pool. The current =
status of the IPv4 address space can be seen in the IANA IPv4 Address =
Space Registry at:

   =
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtm=
l

We have all known that this day was coming for a long time.  In =
preparation, the IETF developed IPv6.  IPv6 is ready, and it has been =
ready for a long time.  This milestone simply increases the urgency for =
IPv6 deployment.  The explosive growth of the Internet can only continue =
with the bigger address space offered by IPv6.
=20
The depletion of the IANA IPv4 address pool is not a crisis.  Next week =
the Internet will not be significantly different that it was a week ago. =
 There will not be any notable short-term effects caused by the empty =
IANA IPv4 address pool.
=20
There is no crisis, but there is a need for action so that the Internet =
can continue to grow.  The transition to IPv6 requires the attention of =
many actors.  However, our parents, spouses, and children will be =
largely unaware of the transition.  They will continue to be amazed of =
the endless possibilities offered by the growing Internet.  For them, =
this milestone will remain insignificant.

To the universal deployment of IPv6,
  Russ=

From jnc@mercury.lcs.mit.edu  Thu Feb  3 11:48:34 2011
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0AA813A6A07; Thu,  3 Feb 2011 11:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.307
X-Spam-Level: 
X-Spam-Status: No, score=-5.307 tagged_above=-999 required=5 tests=[AWL=-1.122, BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-xnWz+ig01d; Thu,  3 Feb 2011 11:48:33 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id 4C98D3A695E; Thu,  3 Feb 2011 11:48:33 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 82EAE6BE5DC; Thu,  3 Feb 2011 14:51:55 -0500 (EST)
To: chair@ietf.org, ietf@ietf.org
Subject: Re: Final IPv4 Unicast Address Allocations
Message-Id: <20110203195155.82EAE6BE5DC@mercury.lcs.mit.edu>
Date: Thu,  3 Feb 2011 14:51:55 -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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 19:48:34 -0000

    > From: IETF Chair <chair@ietf.org>

    > there is a need for action so that the Internet can continue to
    > grow. The transition to IPv6 requires the attention of many actors.

I guess we'll see, won't we?

	Noel

From llynch@civil-tongue.net  Thu Feb  3 11:55:48 2011
Return-Path: <llynch@civil-tongue.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AF023A6ACD; Thu,  3 Feb 2011 11:55:48 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vFvj6LIUyW01; Thu,  3 Feb 2011 11:55:47 -0800 (PST)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by core3.amsl.com (Postfix) with ESMTP id CF8BE3A6AC8; Thu,  3 Feb 2011 11:55:46 -0800 (PST)
Received: from hiroshima.bogus.com (localhost [127.0.0.1]) by hiroshima.bogus.com (8.14.3/8.14.3) with ESMTP id p13Jx8NX042760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Feb 2011 11:59:08 -0800 (PST) (envelope-from llynch@civil-tongue.net)
Received: from localhost (llynch@localhost) by hiroshima.bogus.com (8.14.3/8.14.3/Submit) with ESMTP id p13Jx8pb042757; Thu, 3 Feb 2011 11:59:08 -0800 (PST) (envelope-from llynch@civil-tongue.net)
Date: Thu, 3 Feb 2011 11:59:08 -0800 (PST)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: IETF Chair <chair@ietf.org>
Subject: Re: Final IPv4 Unicast Address Allocations
In-Reply-To: <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
Message-ID: <alpine.BSF.2.00.1102031156120.21712@hiroshima.bogus.com>
References: <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 19:55:48 -0000

On Thu, 3 Feb 2011, IETF Chair wrote:

>
> You have probably already heard the news, but just to make sure no one 
> is left out of the loop, I am posting this note.
<snip>
>
> To the universal deployment of IPv6,

Hear Hear. It seems a bit odd to down a shot of single malt at 11:56am PST
but it *is*  special occasion.

A toast to everyone in the IETF who struggled through the long process to 
get us here and to the universal deployment of IPv6...

- Lucy

>  Russ
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From parasane@gmail.com  Thu Feb  3 12:07:48 2011
Return-Path: <parasane@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF02C3A6ACB; Thu,  3 Feb 2011 12:07:48 -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=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m40DW7+hyIbq; Thu,  3 Feb 2011 12:07:47 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id C64B93A6A1D; Thu,  3 Feb 2011 12:07:47 -0800 (PST)
Received: by iwc10 with SMTP id 10so1577227iwc.31 for <multiple recipients>; Thu, 03 Feb 2011 12:11:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=DZGlqbJWGZz/zqCiHn3x4am8gJD5X0ZIbBnLlRD0kXo=; b=sGDZ0qKyWtUHlQwVVt0fwrzqw8w25uoh7YuqpoFN75voE+S9Y5gzSkP+hecakGm/4h dpxJzin44LODtNsEPvy7j1UE7jI2ziDIMMz90pIRPcW5KamdWuojawO7YQGmunHWHT9D c2Cqk4Oa4RduBkbs5hJICtmUGhsdINMQhanug=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=R4Xk38+9dUXY6RX11wZl1ppcVPFxMQJZiStZtx7XsVdRHNHietWGcywpCMGY0shus+ F8sFDbuzPUdi0nqUcQlgYfJ8Y1xVeG4q8CFoHK0vX9Q2LrTZT234JuADWtGI0bAmZWFh E8UWrLWIT90EWz4SCKTYUi0h9ZQz0kG3psUZo=
Received: by 10.42.167.71 with SMTP id r7mr13515118icy.220.1296763870723; Thu, 03 Feb 2011 12:11:10 -0800 (PST)
MIME-Version: 1.0
Sender: parasane@gmail.com
Received: by 10.42.217.136 with HTTP; Thu, 3 Feb 2011 12:10:50 -0800 (PST)
In-Reply-To: <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
References: <AE9AF8F6-4D0E-41D6-8CF8-34DA55E6443A@icann.org> <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
From: Daniel Brown <danbrown@php.net>
Date: Thu, 3 Feb 2011 15:10:50 -0500
X-Google-Sender-Auth: V5_k0D1TF8RN-is2jgRo68vQfqU
Message-ID: <AANLkTikbTy_85CBNoNXQF23zMUDduazROm=-YbtVtgd8@mail.gmail.com>
Subject: Re: Final IPv4 Unicast Address Allocations
To: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 20:07:49 -0000

On Thu, Feb 3, 2011 at 14:44, IETF Chair <chair@ietf.org> wrote:
>
> There is no crisis, but there is a need for action so that the Internet c=
an continue to grow. =A0The transition to IPv6 requires the attention of ma=
ny actors. =A0However, our parents, spouses, and children will be largely u=
naware of the transition. =A0They will continue to be amazed of the endless=
 possibilities offered by the growing Internet. =A0For them, this milestone=
 will remain insignificant.

    Until they see a documentary on newfound evidence recovered from
ancient Internet archives, including your very message, Russ, and a
disaster-science-fiction-movie producer creates a film called "IPv4:
The Unpredicted Eighth Seal."

--=20
</Daniel P. Brown>
Network Infrastructure Manager
http://www.php.net/

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb  3 13:37:13 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A770C3A6A0B for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 13:37:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.479
X-Spam-Level: 
X-Spam-Status: No, score=0.479 tagged_above=-999 required=5 tests=[AWL=0.569,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-MrZVHJRdgU for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 13:37:12 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 620713A69EF for <ietf@ietf.org>; Thu,  3 Feb 2011 13:37:11 -0800 (PST)
Received: (qmail 11316 invoked from network); 3 Feb 2011 21:46:48 -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; 3 Feb 2011 21:46:48 -0000
Message-ID: <4D4B208F.1000101@necom830.hpcl.titech.ac.jp>
Date: Fri, 04 Feb 2011 06:39:27 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D49D2C9.50508@necom830.hpcl.titech.ac.jp> <4D49D75E.1010808@isi.edu> <4D4A79ED.1060104@necom830.hpcl.titech.ac.jp> <4D4AEFC6.70901@isi.edu>
In-Reply-To: <4D4AEFC6.70901@isi.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 21:37:13 -0000

Joe Touch wrote:

>>>>>> 9. ICMP

>> FYI, traceroute both with UDP or ICMP ECHO is working to/from
>> /between private network behind end to end gateway is working.
> 
> Understood, but my issue is that "ICMP" is more than just ICMP echo;
> many other messages are the result of sending a regular packet (as with
> traceroute), and those are intended to include both the address and port
> of the packet that causes the ICMP.

Yes, ICMP time exceeded including UDP can be routed and is actually
working.

>> IC. We can rely on random id and transport checksum, then.

> Transport checksum works only if the entire transport packet is included
> in the ICMP response,

ICMP? I'm afraid the only ICMP possibly affected by reassembly
is port unreachable. Moreover, as long as destination port number
is correct, proper response can be returned. Purely theoretically,
wrong reassembly of IPv6 (or IPv4 with fragmented ICMP error) can
make the destination port number wrong. Still, as the source port
number is assured to be in the same fragment as the destination
port number, the port unreachable message itself is correct.

You should better worry about the theoretical possibility that
port numbers are not included in the first fragment of IPv6
packet (because of lengthy optional headers).

>> It should be noted that packet smaller than 69B is also atomic.
> 
> Packet size is not a consideration in whether a packet is atomic.
> 
> Packets under 69B must be able to be carried without fragmentation by a
> link as per RFC791, but there's nothing in RFC791 that prohibits such
> packets from being fragmented anyway.

RFC791 specifies fragmentation occur only "when necessary":

  The internet modules use fields in the internet header to fragment and
  reassemble internet datagrams when necessary for transmission through
  "small packet" networks.

and "necessary" is defined as:

    Fragmentation of an internet datagram is necessary when it
    originates in a local net that allows a large packet size and must
    traverse a local net that limits packets to a smaller size to reach
    its destination.

NetBSD, for example, assumes so:

	if (m->m_pkthdr.len < IP_MINFRAGSIZE) {
		ip->ip_id = 0;

thanks to IPv6, we can safely assume not only IPv6, but also IPv4,
packets smaller than 1281B is atomic.

BTW, note that atomic packets may be fragmented within a tunnel as
is specified in RFC2473, which is used for IPv6 mobility.

> But nothing in RFC791 requires that this be the original packet.

That a fragment can be 28B long does not mean 68B packet may be
fragmented unnecessarily. Note also a suggestion in RFC791:

      An alternative might produce less
      than the maximum size datagrams.  For example, one could implement
      a fragmentation procedure that repeatly divided large datagrams in
      half until the resulting fragments were less than the maximum
      transmission unit size.

which is seemingly ignored but should be useful today with nested
tunneling.

>> The problem of the draft (and IPv6) is that it depends on PMTUD.
> 
> Please explain how and where. PMUTD isn't even discussed or cited.

You can't safely send an IPv4 (with DF=1) or IPv6 packet larger
than 1280B unless you know path MTU.

It's an issue of IPv6, not specific to the draft.

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb  3 13:53:16 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5747B3A69F7 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 13:53:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.432
X-Spam-Level: 
X-Spam-Status: No, score=0.432 tagged_above=-999 required=5 tests=[AWL=0.522,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmCI77g9nPo5 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 13:53:15 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 675E53A6998 for <ietf@ietf.org>; Thu,  3 Feb 2011 13:53:15 -0800 (PST)
Received: (qmail 11553 invoked from network); 3 Feb 2011 22:02:59 -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; 3 Feb 2011 22:02:59 -0000
Message-ID: <4D4B2459.2030500@necom830.hpcl.titech.ac.jp>
Date: Fri, 04 Feb 2011 06:55:37 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: TSVDIR review of draft-ietf-intarea-shared-addressing-issues-02
References: <4D48B4EA.20503@isi.edu> <4D490FED.6060303@gont.com.ar>	<4D4996AE.8060302@isi.edu> <4D49FF33.7030107@gont.com.ar>	<4D4A0017.6050401@isi.edu> <4D4A03CE.9020105@gont.com.ar>	<4D4A051C.1060501@gont.com.ar> <4D4A09A5.3050306@isi.edu> <4D4A168C.6060100@gont.com.ar>
In-Reply-To: <4D4A168C.6060100@gont.com.ar>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 21:53:16 -0000

Fernando Gont wrote:

> The fact that geo-location was not considered in the IP design, is
> irrelevant. As noted, IP wasn't meant for production, either.

As the address sharing occurs only at the edge, it is quite
unlikely that geo location approximation breaks.

You can assume hosts sharing an address have the same location,
much more safely than assume hosts in a /24 address range have
the same location.

						Masataka Ohta

From ben@niven-jenkins.co.uk  Thu Feb  3 15:57:37 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F4203A6AC3 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 15:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.052
X-Spam-Level: 
X-Spam-Status: No, score=-104.052 tagged_above=-999 required=5 tests=[AWL=-0.453, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFIzBLAmdmfY for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 15:57:36 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 261463A6B40 for <ietf@ietf.org>; Thu,  3 Feb 2011 15:57:35 -0800 (PST)
Received: from cpc22-cmbg15-2-0-cust173.5-4.cable.virginmedia.com ([86.27.176.174] helo=[192.168.0.203]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pl96g-0003nY-3N; Fri, 04 Feb 2011 00:00:58 +0000
References: <20110202215157.24554.29312.idtracker@localhost> <4D4AC3C3.5020003@gmail.com>
In-Reply-To: <4D4AC3C3.5020003@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset=us-ascii
Message-Id: <F1C92CA4-2C16-437C-8626-EAE0F90B8B53@niven-jenkins.co.uk>
Content-Transfer-Encoding: quoted-printable
From: Benjamin Niven-Jenkins <ben@niven-jenkins.co.uk>
Subject: Re: Last Call: <draft-eggert-tcpm-historicize-00.txt> (Moving the Undeployed TCP Extensions RFC1072, RFC1106, RFC1110, RFC1145, RFC1146, RFC1263, RFC1379, RFC1644 and RFC1693 to Historic Status) to Informational RFC
Date: Fri, 4 Feb 2011 00:00:57 +0000
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1078)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2011 23:57:37 -0000

Mykyta,

On 3 Feb 2011, at 15:03, Mykyta Yevstifeyev wrote:
> However I'd like to raise some questions not directly connected to =
this document.  I wonder why those who said a few weeks ago that =
historicizing some documents in the similar situation is not appropriate =
do not object now.  The arguments of these folks were that RFC 2026 sets =
the criteria for Historic status as 'replaced by other doc' and did not =
consider 'being deprecated' (what exactly we have in the current case) =
as weighty reason for historicizing document.

I am not sure which of the many "move to historic" proposals you have =
proposed recently you are referring to but IMO there is a difference =
between your proposals and that of Lars, namely:

Your proposals fell into one of two categories:
1) Protocol X is old so we should make it historic for housekeeping =
reasons
2) URI Y has never been used so we should make it historic

Whereas while Lars' document is doing some housekeeping it is really =
saying "if you implement TCP you don't need to implement these bits =
anymore" so it has a clear value to people writing new TCP stack =
implementations.

In comparison your proposals were housekeeping for the sake of =
housekeeping and provided no value to the wider community.

HTH
Ben


From mail@sabahattin-gucukoglu.com  Thu Feb  3 16:00:35 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5C22E3A6B54 for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 16:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cyha0kauxnQZ for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 16:00:34 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com (Mintaka.sabahattin-gucukoglu.com [IPv6:2002:adcb:c9c7::1]) by core3.amsl.com (Postfix) with ESMTP id C8DA33A6B40 for <ietf@ietf.org>; Thu,  3 Feb 2011 16:00:33 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:37846) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S28608> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Fri, 4 Feb 2011 00:03:55 -0000
Received: from [192.168.1.13] (cpc4-dals7-0-0-cust274.hari.cable.virginmedia.com [62.31.227.19]) (using SMTP over TLS) by Mintaka (tmda-ofmipd) with ESMTP; Fri, 04 Feb 2011 00:03:47 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Final IPv4 Unicast Address Allocations
In-Reply-To: <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
Date: Fri, 4 Feb 2011 00:03:40 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2D93CB4-1BA0-4027-973D-BBDF840E4414@sabahattin-gucukoglu.com>
References: <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1082)
X-Delivery-Agent: TMDA/1.1.12-kg2 (Pluto)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1299369835.f511b5@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 00:00:35 -0000

On 3 Feb 2011, at 19:44, IETF Chair wrote:
> There is no crisis, but there is a need for action so that the =
Internet can continue to grow.  The transition to IPv6 requires the =
attention of many actors.  However, our parents, spouses, and children =
will be largely unaware of the transition.  They will continue to be =
amazed of the endless possibilities offered by the growing Internet.  =
For them, this milestone will remain insignificant.

Putting aside any bumps in the transition itself, and noting that I'm =
quite sure the IETF is capable of sensible decision-making in times of =
crisis and would wish the transition to be as transparent as possible, I =
think it's more often the case that reconciliation to those who do not =
immediately see our passions is sometimes difficult, but ultimately =
possible.

I explained it to my social worker today, and he bookmarked the test =
IPv6 site, while connected to my home network with IPv6 enabled, and =
said he'd try it at work.  I explained it to my brother and =
sister-in-law, and prepared them for IPv6 from their ISP.  I urged every =
person who I was in contact with to give attention to the issues, and to =
be selective about who they did business with, as a precondition of =
acquiring new services and hardware, in order the better to further IPv6 =
wherever possible, and rightly so.  You want to be able to explain why =
this milestone is such a great achievement - maybe not with any =
immediate effect, but an achievement nonetheless - and make your =
unfortunate hearer understand it.  Perhaps then they'll understand what =
all the wasted time in revery of a great community of technical friends =
and colleagues is really all about.  It isn't for nothing that IPv6 is =
such great news; it will mean a better and more fulfilling Internet for =
everybody who it touches, including every member of your circle, and =
will bring them even closer together.  It is even quite surprising how =
many of them, inspired with that urgency, wish to understand it more =
completely than they might have otherwise, or try to imagine how a =
dotted-decimal address can actually be made longer. :-)

Cheers,
Sabahattin

From narten@us.ibm.com  Thu Feb  3 21:49:42 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B696D3A69EC for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 21:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.097
X-Spam-Level: 
X-Spam-Status: No, score=-106.097 tagged_above=-999 required=5 tests=[AWL=0.502, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQMP31dRSqzj for <ietf@core3.amsl.com>; Thu,  3 Feb 2011 21:49:41 -0800 (PST)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by core3.amsl.com (Postfix) with ESMTP id 8EF733A6868 for <ietf@ietf.org>; Thu,  3 Feb 2011 21:49:40 -0800 (PST)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e36.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p145m3Af000652 for <ietf@ietf.org>; Thu, 3 Feb 2011 22:48:03 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p145r3Ps105514 for <ietf@ietf.org>; Thu, 3 Feb 2011 22:53:03 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p145r3h1028086 for <ietf@ietf.org>; Thu, 3 Feb 2011 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p145r2OT028043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 3 Feb 2011 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 p145r2Uk008336 for <ietf@ietf.org>; Fri, 4 Feb 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p145r29I008322 for ietf@ietf.org; Fri, 4 Feb 2011 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201102040553.p145r29I008322@rotala.raleigh.ibm.com>
Date: Fri, 04 Feb 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 05:49:43 -0000

Total of 129 messages in the last 7 days.
 
script run at: Fri Feb  4 00:53:02 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.83% |   23 | 17.18% |   154722 | touch@isi.edu
 10.08% |   13 |  9.26% |    83405 | fluffy@cisco.com
  6.20% |    8 |  8.66% |    78028 | evnikita2@gmail.com
  4.65% |    6 |  5.23% |    47118 | ekr@rtfm.com
  3.88% |    5 |  3.88% |    34922 | magnus.westerlund@ericsson.com
  3.88% |    5 |  3.44% |    31008 | fernando@gont.com.ar
  3.88% |    5 |  3.38% |    30463 | paul.hoffman@vpnc.org
  2.33% |    3 |  3.96% |    35681 | lars.eggert@nokia.com
  3.10% |    4 |  2.61% |    23498 | lear@cisco.com
  3.10% |    4 |  2.37% |    21379 | mohta@necom830.hpcl.titech.ac.jp
  2.33% |    3 |  3.03% |    27282 | hallam@gmail.com
  2.33% |    3 |  2.50% |    22558 | daedulus@btconnect.com
  2.33% |    3 |  2.42% |    21840 | brian.e.carpenter@gmail.com
  2.33% |    3 |  1.88% |    16931 | dhc2@dcrocker.net
  2.33% |    3 |  1.52% |    13676 | ajs@shinkuro.com
  1.55% |    2 |  1.61% |    14492 | michelle.cotton@icann.org
  1.55% |    2 |  1.46% |    13196 | doug@ewellic.org
  0.78% |    1 |  2.22% |    20043 | even.roni@huawei.com
  1.55% |    2 |  1.41% |    12666 | hartmans-ietf@mit.edu
  1.55% |    2 |  1.19% |    10684 | moore@network-heretics.com
  1.55% |    2 |  1.15% |    10366 | twalsh@juniper.net
  0.78% |    1 |  1.90% |    17097 | ron.even.tlv@gmail.com
  1.55% |    2 |  1.08% |     9712 | tena@huawei.com
  0.78% |    1 |  1.64% |    14759 | jari.arkko@piuha.net
  0.78% |    1 |  1.13% |    10214 | adrian.farrel@huawei.com
  0.78% |    1 |  1.01% |     9054 | ben@nostrum.com
  0.78% |    1 |  0.99% |     8933 | ned+ietf@mauve.mrochek.com
  0.78% |    1 |  0.91% |     8229 | sm@resistor.net
  0.78% |    1 |  0.89% |     7990 | narten@us.ibm.com
  0.78% |    1 |  0.71% |     6405 | mra@pobox.com
  0.78% |    1 |  0.70% |     6275 | john@jlc.net
  0.78% |    1 |  0.68% |     6149 | mail@sabahattin-gucukoglu.com
  0.78% |    1 |  0.68% |     6085 | john-ietf@jck.com
  0.78% |    1 |  0.61% |     5508 | chair@ietf.org
  0.78% |    1 |  0.61% |     5453 | drc@virtualized.org
  0.78% |    1 |  0.59% |     5332 | danbrown@php.net
  0.78% |    1 |  0.58% |     5231 | mrex@sap.com
  0.78% |    1 |  0.57% |     5154 | tme@americafree.tv
  0.78% |    1 |  0.57% |     5117 | ben@niven-jenkins.co.uk
  0.78% |    1 |  0.57% |     5094 | rbarnes@bbn.com
  0.78% |    1 |  0.50% |     4469 | gwz@net-zen.net
  0.78% |    1 |  0.49% |     4414 | jabley@hopcount.ca
  0.78% |    1 |  0.48% |     4359 | llynch@civil-tongue.net
  0.78% |    1 |  0.47% |     4259 | sob@harvard.edu
  0.78% |    1 |  0.46% |     4115 | stig@venaas.com
  0.78% |    1 |  0.45% |     4088 | randy@psg.com
  0.78% |    1 |  0.38% |     3398 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |  129 |100.00% |   900851 | Total

From jari.arkko@piuha.net  Fri Feb  4 03:14:15 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8844C3A68E9; Fri,  4 Feb 2011 03:14:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDGJ7YKdHn9U; Fri,  4 Feb 2011 03:14:14 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 8A4273A68E1; Fri,  4 Feb 2011 03:14:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 18F9C2CC3C; Fri,  4 Feb 2011 13:17:33 +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 zdCDisMEg72Q; Fri,  4 Feb 2011 13:17:32 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 65FBF2CC2D; Fri,  4 Feb 2011 13:17:32 +0200 (EET)
Message-ID: <4D4BE04C.50803@piuha.net>
Date: Fri, 04 Feb 2011 13:17:32 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Tina Tsou <tena@huawei.com>
Subject: Re: Review of draft-arkko-dual-stack-extra-lite-03
References: <004401cbbdae$f6bf1c30$e43d5490$@com>
In-Reply-To: <004401cbbdae$f6bf1c30$e43d5490$@com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ops-dir@ietf.org, draft-arkko-dual-stack-extra-lite@tools.ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 11:14:15 -0000

Tina,

Thank you for your review.

> This document proposed using layer 2 identifier to make address translation.
>   

Strictly speaking, we propose linking NAT bindings to an interface. An 
interface may be associated with layer 2 identifiers or it may be a 
tunnel with layer 3 identifiers.

> Is this application scenario compatible with the existing technologies,
> e.g., DS-Lite, GI DS-Lite and 6RD? 
>   

DS-Lite is one application of the general principle outlined in our draft.

> Point-to-point link usually terminates at BRAS. If BRAS and AFTR is not
> co-located, there still needs tunnels in the layer 3 network. 
>   

That's right.

> In this case, if the IP addresses allocated are overlapped, it will need
> some identifiers to identify the host as described in GI DS-Lite document. 
> So another question for clarification: does this document only care about
> the layer 2 network regardless of what happens in layer 3 network?   
>   

The draft talks about the general case of an interface, and it notes 
that interfaces may, for instance, be point-to-point links or tunnels. 
It is not our intent to enumerate all possible identifier types.

Jari


From lear@cisco.com  Fri Feb  4 03:41:27 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A75F3A6BA1; Fri,  4 Feb 2011 03:41:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.241
X-Spam-Level: 
X-Spam-Status: No, score=-110.241 tagged_above=-999 required=5 tests=[AWL=0.358, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ao0vp3z5Q3Pi; Fri,  4 Feb 2011 03:41:26 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 0C51C3A68FC; Fri,  4 Feb 2011 03:41:25 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AusDABN1S02Q/khNgWdsb2JhbACEFqEXFQEBFiIkhn2XeoppkBKBJ4FpgVR2BItn
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 04 Feb 2011 11:44:50 +0000
Received: from dhcp-10-61-111-78.cisco.com (dhcp-10-61-111-78.cisco.com [10.61.111.78]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p14Bino7019428; Fri, 4 Feb 2011 11:44:49 GMT
Message-ID: <4D4BE6A4.9060801@cisco.com>
Date: Fri, 04 Feb 2011 12:44:36 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: draft-ietf-hokey-ldn-discovery@tools.ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "'IESG'" <iesg@ietf.org>, IETF Discussion <ietf@ietf.org>
Subject: apps-team review of draft-ietf-hokey-ldn-discovery-06
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 11:41:27 -0000

I have been selected as the Applications Area Review Team reviewer for
this draft (for background on apps-review, please see
http://www.apps.ietf.org/content/applications-area-review-team).
Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-hokey-ldn-discovery
Title: The Local Domain Name DHCPv6 Option Reviewer: [your name here]
Review Date: February 2, 2011

Summary: This draft is almost ready for publication as proposed standard
and should be revised further.

This draft provides a means for DHCP clients to ascertain a domain name
for use with ERP [RFC5296].

Major Issues:

The option specified in this draft is to be used for the specific
purpose of ERP, and may not be appropriate for other uses, such as use
in a search list.  See Section 2 of RFC 5296.  Both the option name and
the text should make this clear.

While this is an Applications area review, the Security Considerations
section should still conform to the requirements of RFC-3552.


Minor Issues:

According to RFC 4282 it should be possible for an NAI realm to begin
with a digit.  Strictly speaking this is not allowed by RFC 1035, which
RFC 3315 refers to, which this document references.  As a matter of
correctness, I might simply reference RFC 4282 instead of RFC 3315.

This document also specifies a length limitation of 256 octets that does
not take into account issues raised by RFC 4282.  My recommendation
would be to either match or reference the text in RFC 4282.  FWIW, I do
not like the text in 4282 much myself, because it's rather wishy washy. 
Not sure how to fix that...

Nits:

IMHO no TOC required.

Section 5:

 DHPv6 server as a suboption of the Relay-Supplied Options option
 ^^^^^

s/DHPv6/DHCPv6/

From jari.arkko@piuha.net  Fri Feb  4 04:19:45 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2E253A68F5 for <ietf@core3.amsl.com>; Fri,  4 Feb 2011 04:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1EnfC0+ly6nG for <ietf@core3.amsl.com>; Fri,  4 Feb 2011 04:19:45 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 889433A68E1 for <ietf@ietf.org>; Fri,  4 Feb 2011 04:19:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6A76D2CC3C; Fri,  4 Feb 2011 14:23:08 +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 NmuNWdMyFPdy; Fri,  4 Feb 2011 14:23:07 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 982392CC2D; Fri,  4 Feb 2011 14:23:07 +0200 (EET)
Message-ID: <4D4BEFAB.4030309@piuha.net>
Date: Fri, 04 Feb 2011 14:23:07 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: Last Call: <draft-arkko-dual-stack-extra-lite-03.txt> (Scalable Operation of Address Translators with Per-Interface Bindings)	to	Proposed Standard
References: <20110113235830.13395.80271.idtracker@localhost> <4D31F7AE.4050603@viagenie.ca>
In-Reply-To: <4D31F7AE.4050603@viagenie.ca>
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 12:19:45 -0000

Marc,

Thanks for your review.

> I wonder if this document should be instead Informational status. I 
> don't see here a protocol, more an implementation optimisation.

My personal opinion is that proposed standard RFCs are not reserved for 
just protocol definitions -- they can also describe procedures. What is 
described in our draft is a procedure, a variation of the bigger 
procedure involved in address translation.

In any case, I don't have a strong opinion about what document class 
this RFC should have, I'm also fine with Informational if we think its 
better. But I'll note that our procedure is a component in some other 
works that are on the standards track, e.g., dual-stack lite.

Jari


From jari.arkko@piuha.net  Fri Feb  4 04:22:12 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F8E93A6BA7; Fri,  4 Feb 2011 04:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I59WA0utLFu8; Fri,  4 Feb 2011 04:22:11 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 545E23A6956; Fri,  4 Feb 2011 04:22:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9A9B52CC4E; Fri,  4 Feb 2011 14:25:35 +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 zjz+Pqkv55FB; Fri,  4 Feb 2011 14:25:35 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 45ADE2CC2D; Fri,  4 Feb 2011 14:25:35 +0200 (EET)
Message-ID: <4D4BF03E.4080000@piuha.net>
Date: Fri, 04 Feb 2011 14:25:34 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-arkko-dual-stack-extra-lite
References: <4d3d776a.1ebdd80a.50b4.632e@mx.google.com>
In-Reply-To: <4d3d776a.1ebdd80a.50b4.632e@mx.google.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>, draft-arkko-dual-stack-extra-lite.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 12:22:12 -0000

Roni,

Thanks for your review.

Jari


From Rolf.Winter@neclab.eu  Fri Feb  4 04:34:45 2011
Return-Path: <Rolf.Winter@neclab.eu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52CDA3A6956; Fri,  4 Feb 2011 04:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.418
X-Spam-Level: 
X-Spam-Status: No, score=-102.418 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SvarIbkjGMO; Fri,  4 Feb 2011 04:34:44 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 521E33A6941; Fri,  4 Feb 2011 04:34:44 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id F411A2C000409; Fri,  4 Feb 2011 13:39:13 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mAb7NhVFIrUM; Fri,  4 Feb 2011 13:39:13 +0100 (CET)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id C175B2C000406; Fri,  4 Feb 2011 13:38:53 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.15]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Fri, 4 Feb 2011 13:37:48 +0100
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: "tsv-dir@ietf.org" <tsv-dir@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-netconf-4741bis@tools.ietf.org" <draft-ietf-netconf-4741bis@tools.ietf.org>
Subject: tsv-dir review of draft-ietf-netconf-4741bis-07
Thread-Topic: tsv-dir review of draft-ietf-netconf-4741bis-07
Thread-Index: AcvEaFPgjVChlilzTTCe0WJ6/3YvVQ==
Date: Fri, 4 Feb 2011 12:37:48 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D8ED1FC@DAPHNIS.office.hd>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.6.28]
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 12:34:45 -0000

Hi,

I've reviewed this document as part of the transport area directorate's ong=
oing effort to review key IETF documents. These comments were written prima=
rily for the transport area directors, but are copied to the document's aut=
hors for their information and to allow them to address any issues raised. =
The authors should consider this review together with any other last-call c=
omments they receive. Please always CC tsv-dir@ietf.org if you reply to or =
forward this review. =20

This draft is basically ready for publication, but has nits that should be =
fixed before publication. There are no transport-related concerns that I co=
uld spot.

Some nits:

Section 2.1: second paragraph (below), second sentence doesn't parse quite =
right for me. Especially as the following sentence seems to imply the oppos=
ite. I read this as "The client can change things that cannot be changed"

--> "NETCONF connections are long-lived, persisting between protocol
operations.  This allows the client to make changes to the state of
the connection that will persist for the lifetime of the connection.
For example, authentication information specified for a connection
remains in effect until the connection is closed."

You have "Authentication" in titles twice (in 2.2 and 2.3). Can do without =
in 2.2 as you dedicate a whole section on it.

Section 2.2. "NETCONF connections must" is not a "MUST". Is this intentiona=
l (BTW, you don't mention integrity in the security considerations section =
any more).

"NETCONF transport protocols therefore MUST explain how a NETCONF username =
is
derived from the authentication mechanisms supported by the transport
protocol." I read this as every transport protocol that NETCONF can run ove=
r (SSH e.g.) needs to specify this, but I think this is not what you requir=
e or even can ask for. But maybe I misunderstand the sentence.

Regarding this error:
enum operation-failed {
          description
            "Request could not be completed because the requested
             operation failed for some reason not covered by
             any other error condition.";
}
This is send if the XML is not well formed. Maybe you could dedicate a mess=
age to this that makes trouble shooting a little easier such as "XML-format=
-error" or something.

That's about it.

Best,

	Rolf

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014=20



From evnikita2@gmail.com  Fri Feb  4 06:09:37 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C9BE3A6948 for <ietf@core3.amsl.com>; Fri,  4 Feb 2011 06:09:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[AWL=0.412,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zLUD03Y+xM7H for <ietf@core3.amsl.com>; Fri,  4 Feb 2011 06:09:36 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 277883A6925 for <ietf@ietf.org>; Fri,  4 Feb 2011 06:09:35 -0800 (PST)
Received: by fxm9 with SMTP id 9so2585584fxm.31 for <ietf@ietf.org>; Fri, 04 Feb 2011 06:13:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fVBjjAvInQO/XcM7C3XkmvVtHWjfaBk74lBwPR/Pyxw=; b=J+PiNWSCAJdYANVLXuQ3bOdTgmEzCzAHtQ9Lk/irsWSf6etxbDoWDDW7q/zGLP3ZGQ 9kTyy8X9im2w5XMIlyNJ5MrlGwz06oLLRoOwMdT9SW4wcfnmQlBE0MgxwtpafvYdHiGn piZ18zXVrT9xEYprdlT3lO14+jltUDEaWcZA0=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=ZZd2yYEcvnEfPsDCEvVAPACaj5uCoKs5XdU56SqFU0kAOjBUYmLz8Hpgb7+oP2gIAT xao/AvglAgRuHby1kaTmVl7wfpjVNXTvd8Dwb2DfKQZdDc5kqRl/Qqj3gzsheUq0ssd7 7Hn+5PcHgBjMRrbcrCMqeL2aBmrWl2B7KKxh4=
Received: by 10.223.74.200 with SMTP id v8mr11381890faj.144.1296828780514; Fri, 04 Feb 2011 06:13:00 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id k6sm244521faa.6.2011.02.04.06.12.58 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Feb 2011 06:12:59 -0800 (PST)
Message-ID: <4D4C0981.7080607@gmail.com>
Date: Fri, 04 Feb 2011 16:13:21 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Benjamin Niven-Jenkins <ben@niven-jenkins.co.uk>
Subject: Re: Last Call: <draft-eggert-tcpm-historicize-00.txt> (Moving the Undeployed TCP Extensions RFC1072, RFC1106, RFC1110, RFC1145, RFC1146, RFC1263,  RFC1379, RFC1644 and RFC1693 to Historic Status) to Informational RFC
References: <20110202215157.24554.29312.idtracker@localhost> <4D4AC3C3.5020003@gmail.com> <F1C92CA4-2C16-437C-8626-EAE0F90B8B53@niven-jenkins.co.uk>
In-Reply-To: <F1C92CA4-2C16-437C-8626-EAE0F90B8B53@niven-jenkins.co.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 14:09:37 -0000

Benjamin,

RFC 4644, that is a reason to have this document written says:

>   The RFCs listed here define extensions that have thus far failed to
>     arouse substantial interest from implementers, or that were found to
>     be defective for general use.

I. e. these options are out-of-use and did not gain the implementators' 
popularity. Nearly the same is with IRTP, which I referred to.

Nevertheless I agree that this purpose of this draft is to say "if you 
implement TCP you don't need to implement these bits anymore"; the 
purpose of moving i.e. IRTP to Historic is contiguous - "this technology 
was eventually defined but revealed itself unacceptable/uninteresting; 
further implementations are discouraged"

Mykyta Yevstifeyev

04.02.2011 2:00, Benjamin Niven-Jenkins Ð¿Ð¸ÑˆÐµÑ‚:
> Mykyta,
>
> On 3 Feb 2011, at 15:03, Mykyta Yevstifeyev wrote:
>> However I'd like to raise some questions not directly connected to this document.  I wonder why those who said a few weeks ago that historicizing some documents in the similar situation is not appropriate do not object now.  The arguments of these folks were that RFC 2026 sets the criteria for Historic status as 'replaced by other doc' and did not consider 'being deprecated' (what exactly we have in the current case) as weighty reason for historicizing document.
> I am not sure which of the many "move to historic" proposals you have proposed recently you are referring to but IMO there is a difference between your proposals and that of Lars, namely:
>
> Your proposals fell into one of two categories:
> 1) Protocol X is old so we should make it historic for housekeeping reasons
> 2) URI Y has never been used so we should make it historic
>
> Whereas while Lars' document is doing some housekeeping it is really saying "if you implement TCP you don't need to implement these bits anymore" so it has a clear value to people writing new TCP stack implementations.
>
> In comparison your proposals were housekeeping for the sake of housekeeping and provided no value to the wider community.
>
> HTH
> Ben
>
>


From lear@cisco.com  Fri Feb  4 10:09:10 2011
Return-Path: <lear@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 282023A6968; Fri,  4 Feb 2011 10:09:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.245
X-Spam-Level: 
X-Spam-Status: No, score=-110.245 tagged_above=-999 required=5 tests=[AWL=0.354, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qnxxrczHkamo; Fri,  4 Feb 2011 10:09:09 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id CBF9A3A694A; Fri,  4 Feb 2011 10:09:08 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 04 Feb 2011 18:12:33 +0000
Received: from dhcp-10-61-111-78.cisco.com (dhcp-10-61-111-78.cisco.com [10.61.111.78]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p14ICXOQ000413; Fri, 4 Feb 2011 18:12:33 GMT
Message-ID: <4D4C4184.4070108@cisco.com>
Date: Fri, 04 Feb 2011 19:12:20 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: [apps-discuss] apps-team review of draft-ietf-hokey-ldn-discovery-06
References: <4D4BE6A4.9060801@cisco.com>
In-Reply-To: <4D4BE6A4.9060801@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Robert Elz <kre@munnari.OZ.AU>, IETF Discussion <ietf@ietf.org>, 'IESG' <iesg@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, draft-ietf-hokey-ldn-discovery@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 18:09:10 -0000

Correcting something I wrote (thanks to Rob Elz):

On 2/4/11 12:44 PM, Eliot Lear wrote:
> According to RFC 4282 it should be possible for an NAI realm to begin
> with a digit.  Strictly speaking this is not allowed by RFC 1035, which
> RFC 3315 refers to, which this document references.  As a matter of
> correctness, I might simply reference RFC 4282 instead of RFC 3315.

There is confusion here.  1035 has display guidelines relating to the
use of numbers.  RFC 4282 indicates makes the claim that the limitation
is stronger.  RFC 2181 clarifies this in Section 11.  Either reference,
therefore, would work, and the authors should ignore the above quoted
text.  In time it may be worth RFC3315bis referencing 1035 and 2181, and
RFC 4282 doing the same.

Eliot

From dmiloshevic@afilias.info  Fri Feb  4 10:44:59 2011
Return-Path: <dmiloshevic@afilias.info>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98D613A6A3E; Fri,  4 Feb 2011 10:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.265
X-Spam-Level: 
X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6rNeSmIWM37; Fri,  4 Feb 2011 10:44:58 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [69.46.124.26]) by core3.amsl.com (Postfix) with ESMTP id DA2EE3A69CF; Fri,  4 Feb 2011 10:44:58 -0800 (PST)
Message-Id: <989191F7-5318-4025-9B8A-F918298089ED@afilias.info>
From: Desiree Miloshevic <dmiloshevic@afilias.info>
To: Daniel Brown <danbrown@php.net>
In-Reply-To: <AANLkTikbTy_85CBNoNXQF23zMUDduazROm=-YbtVtgd8@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Final IPv4 Unicast Address Allocations
Date: Fri, 4 Feb 2011 18:48:13 +0000
References: <AE9AF8F6-4D0E-41D6-8CF8-34DA55E6443A@icann.org> <51A5A1C8-C6E7-406C-8A10-414FAABFEF0E@ietf.org> <AANLkTikbTy_85CBNoNXQF23zMUDduazROm=-YbtVtgd8@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-Authenticated: True
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 18:44:59 -0000

On 3 Feb 2011, at 20:10, Daniel Brown wrote:

> On Thu, Feb 3, 2011 at 14:44, IETF Chair <chair@ietf.org> wrote:
>>
>> There is no crisis, but there is a need for action so that the  
>> Internet can continue to grow.  The transition to IPv6 requires the  
>> attention of many actors.  However, our parents, spouses, and  
>> children will be largely unaware of the transition.  They will  
>> continue to be amazed of the endless possibilities offered by the  
>> growing Internet.  For them, this milestone will remain  
>> insignificant.
>
>    Until they see a documentary on newfound evidence recovered from
> ancient Internet archives, including your very message, Russ, and a
> disaster-science-fiction-movie producer creates a film called "IPv4:
> The Unpredicted Eighth Seal."
>
According to Dan Brown's books, It's usually all the Illuminates  
fault.  ;-)

Desiree
--


From marka@isc.org  Fri Feb  4 15:52:14 2011
Return-Path: <marka@isc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7E203A6A61; Fri,  4 Feb 2011 15:52:14 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GNA2qogXl8Is; Fri,  4 Feb 2011 15:52:14 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) by core3.amsl.com (Postfix) with ESMTP id C348D3A69F4; Fri,  4 Feb 2011 15:52:13 -0800 (PST)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:ea06:88ff:fef3:4f9c]) (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 10A78216C2B; Fri,  4 Feb 2011 23:55: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 0F9BB9B32D8; Sat,  5 Feb 2011 10:55:36 +1100 (EST)
To: Eliot Lear <lear@cisco.com>
From: Mark Andrews <marka@isc.org>
References: <4D4BE6A4.9060801@cisco.com><4D4C4184.4070108@cisco.com>
Subject: Re: [apps-discuss] apps-team review of draft-ietf-hokey-ldn-discovery-06
In-reply-to: Your message of "Fri, 04 Feb 2011 19:12:20 BST." <4D4C4184.4070108@cisco.com>
Date: Sat, 05 Feb 2011 10:55:36 +1100
Message-Id: <20110204235536.0F9BB9B32D8@drugs.dv.isc.org>
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, draft-ietf-hokey-ldn-discovery@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Robert Elz <kre@munnari.OZ.AU>, 'IESG' <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Feb 2011 23:52:14 -0000

In message <4D4C4184.4070108@cisco.com>, Eliot Lear writes:
> Correcting something I wrote (thanks to Rob Elz):
> 
> On 2/4/11 12:44 PM, Eliot Lear wrote:
> > According to RFC 4282 it should be possible for an NAI realm to begin
> > with a digit.  Strictly speaking this is not allowed by RFC 1035, which
> > RFC 3315 refers to, which this document references.  As a matter of
> > correctness, I might simply reference RFC 4282 instead of RFC 3315.
> 
> There is confusion here.  1035 has display guidelines relating to the
> use of numbers.  RFC 4282 indicates makes the claim that the limitation
> is stronger.  RFC 2181 clarifies this in Section 11.  Either reference,
> therefore, would work, and the authors should ignore the above quoted
> text.  In time it may be worth RFC3315bis referencing 1035 and 2181, and
> RFC 4282 doing the same.

RFC 1035 puts NO, NONE, NADA restrictions on labels other than length.
Hell even 0x00 is allowed as a octet in a label "\000" is how you
enter it.

The restrictions on hostnames comes from RFC 952 as is relaxed by RFC 1123.
The restrictions on mail domains comes from RFC 821 or 822 (I don't care to
look up which).  This may now have been relaxed when these were updated but
RFC 1123 failed to formally do so as it only updates RFC 952.

Mark
> Eliot
> _______________________________________________
> 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 evnikita2@gmail.com  Fri Feb  4 22:49:52 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E0513A6B07; Fri,  4 Feb 2011 22:49:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.192
X-Spam-Level: 
X-Spam-Status: No, score=-3.192 tagged_above=-999 required=5 tests=[AWL=0.407,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stbYGJHm4xw0; Fri,  4 Feb 2011 22:49:50 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id B3D843A6B06; Fri,  4 Feb 2011 22:49:49 -0800 (PST)
Received: by fxm9 with SMTP id 9so3372243fxm.31 for <multiple recipients>; Fri, 04 Feb 2011 22:53:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cA0asgB0A2YgHCH6Lrr4n4izsyKwH166sR4wv2QAIgA=; b=r7B8VEUG1NnSFLKWaTbrSQI0lDtO0HWak+Lvd0sGCFX1NV8pn2odGwxSyvu1kJfKi4 Cmv71EYN7NXfW5UJFrn484qB8cBaLCEubSm1poaqBF4fuuCQu7OVSn9iaHuy4LHRalfP 5DU1AUPxlbG8GsYPe2W2EJQZkFDuUa+aPWi38=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=ZVeymZvkTIU0ETnHeN4VBjpthksBWadOhvKVvS8zEngycCzhYqeY+KZeEVhMAUTXGR CdcOxiLjT3q28T4zrU9ZZMkYa1TF50jBqduovtXs4Z9JgfdsTdNNCPn8RjrVq08WPMYZ gbNvP9EyqLaNMQEnBRS5cNskOKNnPoBzpR8hk=
Received: by 10.223.104.71 with SMTP id n7mr4509109fao.120.1296888794774; Fri, 04 Feb 2011 22:53:14 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n1sm510878fam.16.2011.02.04.22.53.12 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Feb 2011 22:53:13 -0800 (PST)
Message-ID: <4D4CF3F0.1090501@gmail.com>
Date: Sat, 05 Feb 2011 08:53:36 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-geopriv-rfc3825bis-16.txt> (Dynamic Host Configuration Protocol Options for Coordinate-based Location	Configuration Information) to Proposed Standard
References: <20110204221920.8479.11615.idtracker@localhost>
In-Reply-To: <20110204221920.8479.11615.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: geopriv@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2011 06:49:53 -0000

Hello,

I might want to comment the Section 4 of this document.

Firstly, none of the three registries are properly specified, per RFC 
5226.  Among other, there is no clear format of the registries.  
Therefore I propose the following changes.

> 4. IANA Considerations
>
> 4.1. 'Altitude Types' Registry
>
> IANA is asked to create and maintain the registry called 'Altitude 
> Types' following the guidelines below.
>
> The registry consists of 3 values: Altitude Type, Description and 
> Reference.  They are described below.
>
>   Altitude Type - an integer; refers to the value used in DHCP options 
> described in this document.  Values from 0 to 15 are assigned.
>
>   Description - the description of the altitude described by this code.
>
>   Reference - the reference to the document that describes the 
> altitude code.  Such MUST define the way that the 30 bit altitude 
> values and the associated 6 bit uncertainty are interpreted.
>
> Initial values are given below; new assignments are to be made 
> following the 'Standards Action' policies [RFC5226]
>
>   #         Description                 Reference
> +-------+---------------------------+------------+
> | 0     | No known altitude         | RFC xxxx   |
> | 1     | Altitude in meters        | RFC xxxx   |
> | 2     | Altitude in floors        | RFC xxxx   |
> | 3-14  | Unassigned                | RFC xxxx   |
> | 15    | Reserved                  | RFC xxxx   |
> +-------+---------------------------+------------+
> [RFC Editor: Please replace xxxx with RFC number assigned to this 
> document. 

and etc. for each registry and the request to assign the DHCP code number.

Moreover, IMO RFC 5226 should be referenced normatively as it describes 
procedures for assignment of new values to the registry.  Informative is 
not appropriate here.  I'd also like to ask whether the following 
reference is acceptable for normative:

> [EPSG]       European Petroleum Survey Group, http://www.epsg.org/ and
>              http://www.epsg-registry.org/

Normative references are allowed to documents only, but not websites.

Thank you in advance for considering my comments in the next version of 
the draft.

Mykyta Yevstifeyev

05.02.2011 0:19, The IESG wrote:
> The IESG has received a request from the Geographic Location/Privacy WG
> (geopriv) to consider the following document:
> - 'Dynamic Host Configuration Protocol Options for Coordinate-based
>     Location Configuration Information'
>    <draft-ietf-geopriv-rfc3825bis-16.txt>  as a Proposed Standard
>
> This is the 2nd IETF LC for this document focusing on changes resulting from IESG review.
> The first last call was on version -12 of the document.
> IESG review resulted in these substantial changes:
>    - The document will obsolete RFC3825
>    - Option code 123 is defined in this document
>    - The document defines a new option code instead of extending the behavior of code 123
>
> 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 2011-02-18. 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 Dynamic Host Configuration Protocol Options
>     (both DHCPv4 and DHCPv6) for the coordinate-based geographic location
>     of the client.  The Location Configuration Information (LCI) includes
>     Latitude, Longitude, and Altitude, with resolution or uncertainty
>     indicators for each.  Separate parameters indicate the reference
>     datum for each of these values.  This document obsoletes RFC 3825.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-geopriv-rfc3825bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-geopriv-rfc3825bis/
>
>
>
> 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 ron.even.tlv@gmail.com  Sun Feb  6 07:56:04 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 240233A6935; Sun,  6 Feb 2011 07:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJEa8JLD08kJ; Sun,  6 Feb 2011 07:56:03 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 7EC933A6900; Sun,  6 Feb 2011 07:56:02 -0800 (PST)
Received: by wyf23 with SMTP id 23so4012542wyf.31 for <multiple recipients>; Sun, 06 Feb 2011 07:56:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:content-language:thread-index; bh=hC2IjHEJSRKPcn0ZD5e2f+2uQi6Q5YR3Prv1DYCwLEg=; b=JOwOD5ZIklEqv0eYc46UbP8J1naJ+b3NxTuEU8e7/cPcR8bnEzlxzZ5xPCCp97exyz yrHYSr8po2OX06YtQef7OB7+f7NgLhBp6JekAb6SDba6bRqi0Cp/MiH50CJmN1Ngp0xI B711KrnjVCJhmpaIGiMrGTP7F9DOB7vHIWFf4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :content-language:thread-index; b=JHQRcWLb38MqYUqhbmDgYJ6pXOhCT0tdrus8e+Osx5ql96rZKtN3XH3ticYcPqOwXM K+JGSiMHkqhComNcFGpzk6kTOLMD/qtfrC07gIPGDl90S5Zm7TjqDzoPDk1FdkRzBvTq bJIGCGxUKZNULGWzlRCRFhieG4YHymp0uC4TU=
Received: by 10.216.187.82 with SMTP id x60mr1523162wem.9.1297007763565; Sun, 06 Feb 2011 07:56:03 -0800 (PST)
Received: from windows8d787f9 ([109.67.25.69]) by mx.google.com with ESMTPS id u2sm1625560weh.36.2011.02.06.07.55.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 06 Feb 2011 07:56:01 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Shinta Sugimoto'" <shinta@sfc.wide.ad.jp>
References: <4d47c4d7.26ead80a.186e.4528@mx.google.com> <4D4EA234.3070301@sfc.wide.ad.jp>
In-Reply-To: <4D4EA234.3070301@sfc.wide.ad.jp>
Subject: RE: Gen-ART LC review of draft-ietf-shim6-multihome-shim-api-15
Date: Sun, 6 Feb 2011 17:51:51 +0200
Message-ID: <4d4ec491.027bd80a.1292.ffff83b6@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-us
Thread-index: AcvGAeDc3C4absZ0S0C98nYz0OTBMQAE7wBg
Cc: draft-ietf-shim6-multihome-shim-api.all@tools.ietf.org, gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2011 15:56:04 -0000

Hi Shinta,
I am OK with all your proposals
Thanks
Roni

> -----Original Message-----
> From: Shinta Sugimoto [mailto:shinta@sfc.wide.ad.jp]
> Sent: Sunday, February 06, 2011 3:29 PM
> To: Roni Even
> Cc: draft-ietf-shim6-multihome-shim-api.all@tools.ietf.org; gen-
> art@ietf.org; 'IETF-Discussion list'
> Subject: Re: Gen-ART LC review of draft-ietf-shim6-multihome-shim-api-
> 15
> 
> Dear Roni,
> 
> Thank you very much for your review. Please find my answers inline.
> 
> (11/02/01 17:27), Roni Even 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 resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-shim6-multihome-shim-api-15
> >
> > Reviewer: Roni Even
> >
> > Review Date:2011-2-1
> >
> > IETF LC End Date: 2011-2-10
> >
> > IESG Telechat date:
> >
> > Summary: This draft is almost ready for publication as Informational
> RFC.
> >
> > Major issues:
> >
> > Minor issues:
> >
> > 1.In section 8.2 the path exploration parameters are different from
> RFC
> > 5534, missing keep alive interval. Why the difference.
> 
> You are right. Keepalive Interval is missing in the parameter set that
> we defined in our draft. We did not put in the draft as we thought that
> the value will be determined according to the recommendation given in
> RFC5534 (i.e., the interval should be set one-half to one-third of the
> Keepalive Timeout value), but I agreed that we should make it explicit
> in our draft.
> 
> I suggest to make the following changes in Section 8.2:
> 
> 1) change the structure (shim_pathexplore{}) as follows:
> 
> struct shim_pathexplore {
>          uint16_t  pe_probenum;      /* # of initial probes */
>          uint16_t  pe_keepaliveto;   /* Keepalive Timeout */
>          uint16_t  pe_keepaliveint;  /* Keepalive Interval */
>          uint16_t  pe_initprobeto;   /* Initial Probe Timeout */
>          uint32_t  pe_reserved;      /* reserved */
> };
> 
> 2) Add pe_keepaliveint and its description as below.
> 
> pe_keepaliveint
> 	Indicates interval of REAP keepalive messages in seconds to be
> sent by
> the host when there is no outbound traffic to the peer host. The value
> shall be set according to the recommendation given in [RFC5534].
> 
> Does this sound reasonable to you?
> 
> > 2.In section 11.1 you discuss conflict resolution for SHIM6, is this
> > also relevant for HIP or is it a specific SHIM6 problem. This also
> > relates to the issue of conflict resolution discussed in the security
> > section.
> 
> No, the issue addressed in Section 11.1 is not relevant to HIP. It is
> an
> issue specific to SHIM6. Note that the concept of context forking is
> not
> defined in the HIP RFC. As for the texts in Section 14 (Security
> Considerations), the texts in Section 14.1.1 apply to HIP and SHIM6.
> When there is no indication of specific protocol name (i.e., HIP or
> SHIM6), a term shim sub-layer refers to both HIP and SHIM6. This is an
> assumption in this document.
> 
> > 3.The last sentence in appendix A "Any solution is needed to overcome
> > the problem mentioned above" is not clear, does it mean that there is
> no
> > solution to the context forking problem. Section 11.1 claims that
> using
> > the procedure described it addresses this issue, am I missing
> something.
> 
> No, the issue discussed in Appendix A cannot be solved by the solution
> (or I had better say recommendation) explained in section 11.1. They
> are
> simply different issues. With regard to the issue described in Appendix
> A, there is no solution as far as I know. To avoid the confusion, I
> suggest to change the last sentence of Appendix A as follows: "It is
> for
> further study how to solve the issue described above." Does this make
> sense?
> 
> > Nits/editorial comments:
> >
> > 1.In 8.2 for pe_keepaliveto, what are the units, I assume it is
> seconds.
> 
> Yes, you are right. Let us update the text to make it clear.
> 
> > 2.In section 7 section paragraph "in which one ore" should be "in
> which
> > one or"
> 
> OK, thanks. Let us correct the typo.
> 
> Again, thank you very much for your review!
> 
> Regards,
> Shinta


From pasi.sarolahti@iki.fi  Mon Feb  7 06:17:07 2011
Return-Path: <pasi.sarolahti@iki.fi>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 84CFC3A6DE3; Mon,  7 Feb 2011 06:17:07 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMPx2BSIOCzd; Mon,  7 Feb 2011 06:17:06 -0800 (PST)
Received: from smtp-3.hut.fi (smtp-3.hut.fi [130.233.228.93]) by core3.amsl.com (Postfix) with ESMTP id 65D5A3A6DD3; Mon,  7 Feb 2011 06:17:06 -0800 (PST)
Received: from localhost (katosiko.hut.fi [130.233.228.115]) by smtp-3.hut.fi (8.13.6/8.12.10) with ESMTP id p17EH9Wx013538; Mon, 7 Feb 2011 16:17:09 +0200
Received: from smtp-3.hut.fi ([130.233.228.93]) by localhost (katosiko.hut.fi [130.233.228.115]) (amavisd-new, port 10024) with LMTP id 19029-713; Mon,  7 Feb 2011 16:17:08 +0200 (EET)
Received: from smtp.netlab.hut.fi (luuri.netlab.hut.fi [130.233.154.177]) by smtp-3.hut.fi (8.13.6/8.12.10) with ESMTP id p17EGx4f013524; Mon, 7 Feb 2011 16:16:59 +0200
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.netlab.hut.fi (Postfix) with ESMTP id A05881E143; Mon,  7 Feb 2011 16:16:59 +0200 (EET)
X-Virus-Scanned: by amavisd-new at luuri.netlab.hut.fi
Received: from smtp.netlab.hut.fi ([127.0.0.1]) by localhost (luuri.netlab.hut.fi [127.0.0.1]) (amavisd-new, port 10024) with LMTP id e+8FNMjK5a+o; Mon,  7 Feb 2011 16:16:55 +0200 (EET)
Received: from [192.168.0.12] (cs181059059.pp.htv.fi [82.181.59.59]) by smtp.netlab.hut.fi (Postfix) with ESMTPSA id C503F1E11D; Mon,  7 Feb 2011 16:16:55 +0200 (EET)
From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: tsv-dir review of draft-ymbk-aplusp-08
Date: Mon, 7 Feb 2011 16:16:55 +0200
Message-Id: <73767A4C-D4A9-4854-91A6-858D4971C52B@iki.fi>
To: draft-ymbk-aplusp@tools.ietf.org, tsv-dir@ietf.org, ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-TKK-Virus-Scanned: by amavisd-new-2.1.2-hutcc at katosiko.hut.fi
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2011 14:17:07 -0000

Hello,

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.

I found no major issues with the document, and the document is ready for =
publication. Below are some minor nits you might want to consider =
addressing before publishing:

* Section 1.1: You could add reference to UPnP/NAT-PMP.

* Bottom of page 16: you could describe with a few words what "delayed =
translation" is. (is it address translation that doesn't happen at the =
edge of the A+P subsystem?)

* Section 5.2: "There is a general observation that the more demanding =
customer uses around 1024 ports when heavily communicating." -- on what =
is this based on? Do you have some reference or other data to back this =
up?

* The typical initial scenario probably is that an A+P gateway is NATing =
the traffic to a legacy host in private address realm, but I understood =
that if a host/application supports A+P, it could use A+P addressing =
directly without NAT. Have you thought how this would be reflected on =
the socket API? For example, what would be the intended behavior, if an =
application tries to bind a port that was not part of the port range =
assigned for the host? Is there an error, or does that trigger some =
other behavior? You might want to mention something about such API =
interactions in some appropriate place (maybe in 5.3.4?). Apparently it =
is thought that there would be some extended API for an A+P-aware =
application to query which ports are available, right?

- Pasi


From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Feb  5 17:34:26 2011
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 201A93A6C65 for <ietf@core3.amsl.com>; Sat,  5 Feb 2011 17:34:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.704
X-Spam-Level: 
X-Spam-Status: No, score=0.704 tagged_above=-999 required=5 tests=[HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vY+WvGmZA1Ke for <ietf@core3.amsl.com>; Sat,  5 Feb 2011 17:34:25 -0800 (PST)
Received: from smtp2.adam.net.au (smtp2.adam.net.au [202.136.110.251]) by core3.amsl.com (Postfix) with ESMTP id 04C233A6C64 for <ietf@ietf.org>; Sat,  5 Feb 2011 17:34:25 -0800 (PST)
Received: from 182-239-156-97.ip.adam.com.au ([182.239.156.97] helo=opy.nosense.org) by smtp2.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PltW9-00064W-E4; Sun, 06 Feb 2011 12:04:21 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 11D6E3B336; Sun,  6 Feb 2011 12:04:21 +1030 (CST)
Date: Sun, 6 Feb 2011 12:04:20 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: ietf@ietf.org, mrw@painless-security.com, fred@cisco.com
Subject: Last Call: <draft-mrw-nat66-07.txt> (IPv6-to-IPv6 Network Prefix Translation) to Experimental RFC
Message-ID: <20110206120420.43dcfc71@opy.nosense.org>
X-Mailer: Claws Mail 3.7.8 (GTK+ 2.22.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 07 Feb 2011 07:35:23 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2011 01:34:26 -0000

Hi,

I've been aware of this draft for a while, and have begrudgingly felt
that if any form of address translation is going to occur in IPv6 then
the method described in this I-D was a good way to do it, as it avoids
many of the drawbacks of many of the IPv4 NAT and NAPT methods.

One area where I think there could be further discussion is the
consequences of end-nodes not knowing their global address(es). There
is mention about applications having trouble because of not being able
to do referrals, as that is a well known problem in commonly deployed
IPv4 NAPT. One of the high barriers in IPv4 NAPT for this to occur was
the absence of a 1-to-1 mapping between external and internal
addresses, as well as the absence of knowledge of which external ports
are currently mapped to internal ports and vice-versa. This draft
removes both of these significant limitations in IPv6 translation.

I've only recently realised that what is really happening with address
translation is that end-nodes lose their ability to know their global
identity at the network layer (losing their ability to know their
global addresses is the symptom, losing their ability to know their
"global identity" is the consequence). If two end-nodes don't have
global identities, they are forced to communicate, at least initially,
via an intermediary which does have a global identity. End-nodes behind
translators can't have a true peer-to-peer relationship at the network
layer or above it if they don't know their own global identities. Yet my
understanding is that a true peer-to-peer property of the network layer
is one of the fundamental architectural design goals of the Internet's
network layer protocols. While IPv4 NAT/NAPT limited that significantly,
my hope has been that IPv6 restore that the network layer's true
peer-to-peer nature, which requires end-nodes to know their own global
identity.

I think two other cases could be mentioned were trading of
global identities are occurring at the transport layer, rather
than the application layer - SCTP and multipath-TCP - and that their
reliability and performance goals will also be effected by IPv6
prefix translation.

There also might be one possible saving grace worth mentioning. If
protocols and mechanisms to separate the locator and identifier become
wide spread, then I think true end-node peer-to-peer communications
should return to being commonly available.

Apologies for the late comments, I've only recently been thinking a bit
more about "global identities" after seeing SCTP behavior in more
detail as well as a IPv6 sip client incorrectly picking a ULA address
instead of a global address for an incoming media stream.

Best regards,
Mark.

(Please CC me, I'm not subscribed. Thanks.)




From shinta@sfc.wide.ad.jp  Sun Feb  6 05:29:28 2011
Return-Path: <shinta@sfc.wide.ad.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1EF143A6A50; Sun,  6 Feb 2011 05:29:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.504
X-Spam-Level: ***
X-Spam-Status: No, score=3.504 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rom58SoEYkwf; Sun,  6 Feb 2011 05:29:27 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id EFACB3A6778; Sun,  6 Feb 2011 05:29:26 -0800 (PST)
Received: from imac.local (softbank126018084155.bbtec.net [126.18.84.155]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id A0FB727807A; Sun,  6 Feb 2011 22:29:24 +0900 (JST)
Message-ID: <4D4EA234.3070301@sfc.wide.ad.jp>
Date: Sun, 06 Feb 2011 22:29:24 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; ja-JP-mac; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-shim6-multihome-shim-api-15
References: <4d47c4d7.26ead80a.186e.4528@mx.google.com>
In-Reply-To: <4d47c4d7.26ead80a.186e.4528@mx.google.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Mon, 07 Feb 2011 07:35:36 -0800
Cc: draft-ietf-shim6-multihome-shim-api.all@tools.ietf.org, gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2011 13:29:28 -0000

Dear Roni,

Thank you very much for your review. Please find my answers inline.

(11/02/01 17:27), Roni Even 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 resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-shim6-multihome-shim-api-15
>
> Reviewer: Roni Even
>
> Review Date:2011–2–1
>
> IETF LC End Date: 2011–2–10
>
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> 1.In section 8.2 the path exploration parameters are different from RFC
> 5534, missing keep alive interval. Why the difference.

You are right. Keepalive Interval is missing in the parameter set that 
we defined in our draft. We did not put in the draft as we thought that 
the value will be determined according to the recommendation given in 
RFC5534 (i.e., the interval should be set one-half to one-third of the 
Keepalive Timeout value), but I agreed that we should make it explicit 
in our draft.

I suggest to make the following changes in Section 8.2:

1) change the structure (shim_pathexplore{}) as follows:

struct shim_pathexplore {
         uint16_t  pe_probenum;      /* # of initial probes */
         uint16_t  pe_keepaliveto;   /* Keepalive Timeout */
         uint16_t  pe_keepaliveint;  /* Keepalive Interval */
         uint16_t  pe_initprobeto;   /* Initial Probe Timeout */
         uint32_t  pe_reserved;      /* reserved */
};

2) Add pe_keepaliveint and its description as below.

pe_keepaliveint
	Indicates interval of REAP keepalive messages in seconds to be sent by 
the host when there is no outbound traffic to the peer host. The value 
shall be set according to the recommendation given in [RFC5534].

Does this sound reasonable to you?

> 2.In section 11.1 you discuss conflict resolution for SHIM6, is this
> also relevant for HIP or is it a specific SHIM6 problem. This also
> relates to the issue of conflict resolution discussed in the security
> section.

No, the issue addressed in Section 11.1 is not relevant to HIP. It is an 
issue specific to SHIM6. Note that the concept of context forking is not 
defined in the HIP RFC. As for the texts in Section 14 (Security 
Considerations), the texts in Section 14.1.1 apply to HIP and SHIM6. 
When there is no indication of specific protocol name (i.e., HIP or 
SHIM6), a term shim sub-layer refers to both HIP and SHIM6. This is an 
assumption in this document.

> 3.The last sentence in appendix A “Any solution is needed to overcome
> the problem mentioned above” is not clear, does it mean that there is no
> solution to the context forking problem. Section 11.1 claims that using
> the procedure described it addresses this issue, am I missing something.

No, the issue discussed in Appendix A cannot be solved by the solution 
(or I had better say recommendation) explained in section 11.1. They are 
simply different issues. With regard to the issue described in Appendix 
A, there is no solution as far as I know. To avoid the confusion, I 
suggest to change the last sentence of Appendix A as follows: "It is for 
further study how to solve the issue described above." Does this make sense?

> Nits/editorial comments:
>
> 1.In 8.2 for pe_keepaliveto, what are the units, I assume it is seconds.

Yes, you are right. Let us update the text to make it clear.

> 2.In section 7 section paragraph “in which one ore” should be “in which
> one or”

OK, thanks. Let us correct the typo.

Again, thank you very much for your review!

Regards,
Shinta

From fluffy@cisco.com  Mon Feb  7 10:42:43 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83C9E3A6D81; Mon,  7 Feb 2011 10:42:43 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2a+e18M2VGp; Mon,  7 Feb 2011 10:42:42 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 9CFE03A6E80; Mon,  7 Feb 2011 10:42:41 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAPMT02rRN+K/2dsb2JhbAClM3OeRZsPhVoEhHqGbYMu
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-6.cisco.com with ESMTP; 07 Feb 2011 18:42:46 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p17IgiMN028663; Mon, 7 Feb 2011 18:42:44 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated Dialog) to Proposed Standard
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20110207170250.4107.67897.idtracker@localhost>
Date: Mon, 7 Feb 2011 11:44:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com>
References: <20110207170250.4107.67897.idtracker@localhost>
To: IESG IESG <iesg@ietf.org>, "ietf@ietf.org IETF" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2011 18:42:43 -0000

I was somewhat surprised to see this back in LC. I am still not aware of =
any use case where this actually helps. I searched the IETF and WG lists =
for email with the subject draft-ietf-sipcore-199 and I do not see a =
single email that suggests there is support for this draft or the =
changes in it since the previous LC.=20

This draft has no use that I understand how it helps - it is at best a =
very limited optimization. The SIP standards is already too complicated =
with too many extensions. I believe this draft makes SIP worse.Thought =
the draft mandates that systems need to work even when the 199 are lost, =
I do not think that is how the proponents of the work intent to use. I =
could be very wrong but I presume that people intent to use to control =
middle boxes that control media gates. It's broken for that but given =
that is not discussed in the draft, it's hard to discuss how it is =
broken and what would be needed to fix it.=20

I do not support publishing this draft as standards track without actual =
WG discussion on what the problem is this draft solves and if there is =
WG consensus that problem is worth solving. =20


On Feb 7, 2011, at 10:02 AM, The IESG wrote:

> The IESG has received a request from the Session Initiation Protocol =
Core
> WG (sipcore) to consider the following document:
> - 'Session Initiation Protocol (SIP) Response Code for Indication of
>   Terminated Dialog'
>  <draft-ietf-sipcore-199-05.txt> as a Proposed Standard
>=20
> This is the second IETF last call for this document. The previous last =
call was on version -02.
> While resolving review comments, an issue with the interaction of the =
199 response and the
> 100rel extension was identified and addressed by the SIPCORE working =
group. A full summary
> of the changes are available in section 13 of the document.
>=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 2011-02-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 specification defines a new Session Initiation Protocol (SIP)
>   response code, 199 Early Dialog Terminated, that a SIP forking proxy
>   and a User Agent Server (UAS) can use to indicate towards upstream
>   SIP entities (including the User Agent Client (UAC)) that an early
>   dialog has been terminated, before a final response is sent towards
>   the SIP entities.
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-sipcore-199/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-sipcore-199/
>=20
>=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


From adam@nostrum.com  Mon Feb  7 13:01:52 2011
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 443AF3A6E70; Mon,  7 Feb 2011 13:01:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxNJcuZ3MyZG; Mon,  7 Feb 2011 13:01:51 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id D46BB3A6E55; Mon,  7 Feb 2011 13:01:50 -0800 (PST)
Received: from dn3-228.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 p17L1rkS045381 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 7 Feb 2011 15:01:54 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D505DC1.40002@nostrum.com>
Date: Mon, 07 Feb 2011 15:01:53 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
References: <20110207170250.4107.67897.idtracker@localhost> <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com>
In-Reply-To: <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IESG IESG <iesg@ietf.org>, "ietf@ietf.org IETF" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2011 21:01:52 -0000

On 2/7/11 12:44 PM, Cullen Jennings wrote:
> I was somewhat surprised to see this back in LC. I am still not aware of any use case where this actually helps. I searched the IETF and WG lists for email with the subject draft-ietf-sipcore-199 and I do not see a single email that suggests there is support for this draft or the changes in it since the previous LC.
>
> This draft has no use that I understand how it helps - it is at best a very limited optimization. The SIP standards is already too complicated with too many extensions. I believe this draft makes SIP worse.Thought the draft mandates that systems need to work even when the 199 are lost, I do not think that is how the proponents of the work intent to use. I could be very wrong but I presume that people intent to use to control middle boxes that control media gates. It's broken for that but given that is not discussed in the draft, it's hard to discuss how it is broken and what would be needed to fix it.
>
> I do not support publishing this draft as standards track without actual WG discussion on what the problem is this draft solves and if there is WG consensus that problem is worth solving.

Cullen:

Speaking as a chair of SIPCORE, I would like to clarify a minor point. 
Although it may not have been your intention, your message can be read 
as implying that the SIPCORE chairs and/or the RAI area directors have 
decided to move this document forward without community input.

For the benefit of those on this mailing list who were not involved in 
the earlier stages of this document's progress: the initial community 
input on whether to pursue the problem solved by this draft was taken at 
the face-to-face SIPPING meeting during IETF 69. In particular, the 
minutes for that meeting reflect: "Hum... in support of working on this 
problem."

In April of 2008, the requirements document was handed over from SIPPING 
to the SIP working group for working on actual protocol mechanism. (The 
SIP change process at the time limited core protocol changes to the SIP 
working group, requiring a change in venue).

Within the SIP working group, there were at least 316 message in 38 
different threads on the protocol document over the one year period 
spanning April 2008 to April 2009. This period included a two-week long 
Working Group Last Call period in November of 2008.

In April of 2009, the RAI area underwent a reorganization, which 
resulted in the conclusion of the SIP working group. As part of the 
chartering of the SIPCORE working group, this document (and its 
associated milestone) was transferred to the SIPCORE WG.

In January of 2010, the document entered IETF last call for the first 
time. During IETF balloting, certain issues were identified by the IESG, 
and balloted as a "DISCUSS" position. Over the course of 2010, the 
document's author worked with the RAI ADs to address these issues to the 
satisfaction of the currently seated IESG. As a result of these 
conversations, a technical issue involving interaction with another SIP 
extension mechanism was identified, and brought back to the SIPCORE 
working group. A resolution to the issue was identified in early 
December 2010, and a revised version of the document was produced to 
reflect this resolution.

At every step of this process, the IETF, RAI, and SIP community has 
opportunity for involvement. The volume of discussion demonstrates a 
non-trivial interest in this mechanism.

/a

From touch@isi.edu  Mon Feb  7 20:32:11 2011
Return-Path: <touch@isi.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03FA33A6C86; Mon,  7 Feb 2011 20:32: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FYpe0KARzWUU; Mon,  7 Feb 2011 20:32:10 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 39D393A6BDF; Mon,  7 Feb 2011 20:32:10 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id p184VWx2008295 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 7 Feb 2011 20:31:47 -0800 (PST)
Message-ID: <4D50C724.9040402@isi.edu>
Date: Mon, 07 Feb 2011 20:31:32 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Chris Benson <cbenson@adax.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <Pine.LNX.4.64.1102071321290.4671@adax.adax>
In-Reply-To: <Pine.LNX.4.64.1102071321290.4671@adax.adax>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p184VWx2008295
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 04:32:11 -0000

Regardless, we're already moving forward to make the identities public 
(not sure if it's happening, or already happened).

Regardless, though, again, this is out of scope for this doc to address 
in detail, IMO.

Joe

On 2/7/2011 1:24 PM, Chris Benson wrote:
> Hi folks,
>
> Sam Hartman wrote (and others suggest):
>>>
>>>   I think that being able to discuss concerns with reviewers and being
>>>   able to consider potential conflicts and other issues mean that an open
>>>   dialogue with identified reviewers is an important part of our
>>>   process. Anonymous contributions may have their place in the WG process,
>>>   but I don't think they should have a place in expert review oor blocking
>>>   objections to documents.  So, as an individual I strongly support making
>>>   expert reviewers identities public.
>>>
>
> I don't see that "public identity" (of expert reviewers) is
> required for "interactive discussion".  Or would anonymous
> interaction fail a Turing test of some kind?
>
> Chris Benson.

From christer.holmberg@ericsson.com  Mon Feb  7 23:04:52 2011
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B3E43A7032; Mon,  7 Feb 2011 23:04:52 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aPwrHSBAA2dF; Mon,  7 Feb 2011 23:04:51 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 84D3C3A702E; Mon,  7 Feb 2011 23:04:50 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-df-4d50eb1697e4
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 05.70.13987.61BE05D4; Tue,  8 Feb 2011 08:04:55 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.59]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Tue, 8 Feb 2011 08:04:54 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Cullen Jennings <fluffy@cisco.com>, IESG IESG <iesg@ietf.org>, "ietf@ietf.org IETF" <ietf@ietf.org>
Date: Tue, 8 Feb 2011 08:04:53 +0100
Subject: RE: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
Thread-Index: AcvG9tz1YS9Uq3P9T6CzzdeDWD1FnwAZwyqw
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194432B146@ESESSCMS0356.eemea.ericsson.se>
References: <20110207170250.4107.67897.idtracker@localhost> <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com>
In-Reply-To: <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.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: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 07:04:52 -0000

Cullen,

When we last talked, you said that your main is the fact that unreliable re=
sponses might be sent even in the case of Require:100rel. That has now been=
 solved, so I am very surprised by your comments.

Also, the draft WAS back in the WG when the proposed solution was presented=
. Why didn't you say anything then????

Regarding the usage, I have been provided text (mostly by Robert) regarding=
 the usability, limitations etc. Why haven't you said anything before if yo=
u didn't like it????

Regards,

Christer=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On=20
> Behalf Of Cullen Jennings
> Sent: 7. helmikuuta 2011 20:45
> To: IESG IESG; ietf@ietf.org IETF
> Subject: Re: Last Call: <draft-ietf-sipcore-199-05.txt>=20
> (Session Initiation Protocol (SIP) Response Code for=20
> Indication of Terminated Dialog) to Proposed Standard
>=20
>=20
> I was somewhat surprised to see this back in LC. I am still=20
> not aware of any use case where this actually helps. I=20
> searched the IETF and WG lists for email with the subject=20
> draft-ietf-sipcore-199 and I do not see a single email that=20
> suggests there is support for this draft or the changes in it=20
> since the previous LC.=20
>=20
> This draft has no use that I understand how it helps - it is=20
> at best a very limited optimization. The SIP standards is=20
> already too complicated with too many extensions. I believe=20
> this draft makes SIP worse.Thought the draft mandates that=20
> systems need to work even when the 199 are lost, I do not=20
> think that is how the proponents of the work intent to use. I=20
> could be very wrong but I presume that people intent to use=20
> to control middle boxes that control media gates. It's broken=20
> for that but given that is not discussed in the draft, it's=20
> hard to discuss how it is broken and what would be needed to fix it.=20
>=20
> I do not support publishing this draft as standards track=20
> without actual WG discussion on what the problem is this=20
> draft solves and if there is WG consensus that problem is=20
> worth solving. =20
>=20
>=20
> On Feb 7, 2011, at 10:02 AM, The IESG wrote:
>=20
> > The IESG has received a request from the Session Initiation=20
> Protocol=20
> > Core WG (sipcore) to consider the following document:
> > - 'Session Initiation Protocol (SIP) Response Code for Indication of
> >   Terminated Dialog'
> >  <draft-ietf-sipcore-199-05.txt> as a Proposed Standard
> >=20
> > This is the second IETF last call for this document. The=20
> previous last call was on version -02.
> > While resolving review comments, an issue with the=20
> interaction of the=20
> > 199 response and the 100rel extension was identified and=20
> addressed by=20
> > the SIPCORE working group. A full summary of the changes=20
> are available in section 13 of the document.
> >=20
> > The IESG plans to make a decision in the next few weeks,=20
> and solicits=20
> > final comments on this action. Please send substantive=20
> comments to the=20
> > ietf@ietf.org mailing lists by 2011-02-21. Exceptionally,=20
> comments may=20
> > be sent to iesg@ietf.org instead. In either case, please retain the=20
> > beginning of the Subject line to allow automated sorting.
> >=20
> > Abstract
> >=20
> >   This specification defines a new Session Initiation Protocol (SIP)
> >   response code, 199 Early Dialog Terminated, that a SIP=20
> forking proxy
> >   and a User Agent Server (UAS) can use to indicate towards upstream
> >   SIP entities (including the User Agent Client (UAC)) that an early
> >   dialog has been terminated, before a final response is=20
> sent towards
> >   the SIP entities.
> >=20
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-sipcore-199/
> >=20
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-sipcore-199/
> >=20
> >=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
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> =

From mohta@necom830.hpcl.titech.ac.jp  Tue Feb  8 01:16:52 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0F5D3A7086 for <ietf@core3.amsl.com>; Tue,  8 Feb 2011 01:16:52 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Byx6ZYnvPON3 for <ietf@core3.amsl.com>; Tue,  8 Feb 2011 01:16:52 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id BE4DB3A7087 for <ietf@ietf.org>; Tue,  8 Feb 2011 01:16:51 -0800 (PST)
Received: (qmail 56682 invoked from network); 8 Feb 2011 09:24:26 -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; 8 Feb 2011 09:24:26 -0000
Message-ID: <4D5109CA.3040009@necom830.hpcl.titech.ac.jp>
Date: Tue, 08 Feb 2011 18:15:54 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: tsv-dir review of draft-ymbk-aplusp-08
References: <73767A4C-D4A9-4854-91A6-858D4971C52B@iki.fi>
In-Reply-To: <73767A4C-D4A9-4854-91A6-858D4971C52B@iki.fi>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 09:16:52 -0000

Pasi Sarolahti wrote:

My comments are as an implementer of a port restricted IP.

> * The typical initial scenario probably is that an A+P gateway
> is NATing the traffic to a legacy host in private address
> realm, but I understood that if a host/application supports
> A+P, it could use A+P addressing directly without NAT.

That's the proper way to use of port restricted IP with the
end to end transparency not unnecessarily combined with
legacy NAT.

> Have you thought how this would be reflected on the socket API?
> For example, what would be the intended behavior, if an
> application tries to bind a port that was not part of the port
> range assigned for the host?

It's like specifying a source address not belonging to the host.

So, a super user should be allowed to do so with raw IP.

> Apparently it is thought that there would be some extended API
> for an A+P-aware application to query which ports are
> available, right?

My implementation of PRIP has such mechanisms as ioctl.

						Masataka Ohta

From david.black@emc.com  Mon Feb  7 09:49:32 2011
Return-Path: <david.black@emc.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01AB43A6E3E; Mon,  7 Feb 2011 09:49:32 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GGmwc3G6lEcx; Mon,  7 Feb 2011 09:49:30 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 6F1923A6E22; Mon,  7 Feb 2011 09:49:30 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p17HnVfX015672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Feb 2011 12:49:33 -0500
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.253]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Mon, 7 Feb 2011 12:49:23 -0500
Received: from mxhub17.corp.emc.com (mxhub17.corp.emc.com [10.254.93.46]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p17HnKNo003521; Mon, 7 Feb 2011 12:49:20 -0500
Received: from mx14a.corp.emc.com ([169.254.1.70]) by mxhub17.corp.emc.com ([10.254.93.46]) with mapi; Mon, 7 Feb 2011 12:49:20 -0500
From: <david.black@emc.com>
To: <ietf@ietf.org>
Date: Mon, 7 Feb 2011 12:49:19 -0500
Subject: RE: Last Call: <draft-ietf-pwe3-fc-encap-14.txt> (Encapsulation Methods	for Transport of Fibre Channel Traffic over MPLS Networks) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-pwe3-fc-encap-14.txt> (Encapsulation Methods	for Transport of Fibre Channel Traffic over MPLS Networks) to Proposed Standard
Thread-Index: AcvG4hjxH/z3UzYqSGukU9j68wK4OgAC9FSQ
Message-ID: <7C4DFCE962635144B8FAE8CA11D0BF1E03E1FB28B4@MX14A.corp.emc.com>
References: <20110207161310.20916.56573.idtracker@localhost>
In-Reply-To: <20110207161310.20916.56573.idtracker@localhost>
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: Tue, 08 Feb 2011 08:35:17 -0800
Cc: david.black@emc.com, pwe3@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2011 17:49:32 -0000

This IETF draft contains normative references to three Fibre Channel standa=
rds that are developed by INCITS Technical Committee T11 (www.t11.org) - FC=
-BB-6, FC-FS-2 and FC-SP.  FC-BB-6 is under active development at T11, and =
hence its latest working draft (revision 1.02) is publicly available from T=
11's web site.  As the other two references are to published standards, the=
ir availability is restricted.  In both cases, the material relied upon by =
this IETF draft has not been changed by follow-on standards work, so the la=
test drafts of T11's follow-on standards efforts (FC-FS-3 and FC-SP-2) can =
be used for reference.

If anyone needs a copy of FC-FS-2 and/or FC-SP in order to review this IETF=
 draft, please send me an email - I have been authorized by T11 to provide =
copies of these standards for the personal use of IETF participants in IETF=
 activity related to this draft.

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

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.o=
rg] On Behalf Of The IESG
> Sent: Monday, February 07, 2011 11:13 AM
> To: IETF-Announce
> Cc: pwe3@ietf.org
> Subject: Last Call: <draft-ietf-pwe3-fc-encap-14.txt> (Encapsulation Meth=
ods for Transport of Fibre
> Channel Traffic over MPLS Networks) to Proposed Standard
>=20
>=20
> The IESG has received a request from the Pseudowire Emulation Edge to
> Edge WG (pwe3) to consider the following document:
> - 'Encapsulation Methods for Transport of Fibre Channel Traffic over MPLS
>    Networks'
>   <draft-ietf-pwe3-fc-encap-14.txt> as a Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-02-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
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-fc-encap/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-fc-encap/
>=20
>=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


From cbenson@adax.com  Mon Feb  7 13:21:40 2011
Return-Path: <cbenson@adax.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 835BF3A6EFE; Mon,  7 Feb 2011 13:21:40 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEz9xHPKI7II; Mon,  7 Feb 2011 13:21:37 -0800 (PST)
Received: from mail1.adax.com (mail1.adax.com [208.201.231.104]) by core3.amsl.com (Postfix) with ESMTP id 844EE3A6E62; Mon,  7 Feb 2011 13:21:37 -0800 (PST)
Received: from adax (adax [12.0.0.88]) by mail1.adax.com (Postfix) with ESMTP id A92361209B4; Mon,  7 Feb 2011 13:21:42 -0800 (PST)
Received: by adax (Postfix, from userid 243) id DCA758ED57; Mon,  7 Feb 2011 13:24:52 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by adax (Postfix) with ESMTP id D536C8ED52; Mon,  7 Feb 2011 13:24:52 -0800 (PST)
Date: Mon, 7 Feb 2011 13:24:52 -0800 (PST)
From: Chris Benson <cbenson@adax.com>
X-X-Sender: cbenson@adax.adax
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
In-Reply-To: <tslbp2vh8ig.fsf@mit.edu>
Message-ID: <Pine.LNX.4.64.1102071321290.4671@adax.adax>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 08 Feb 2011 08:35:17 -0800
Cc: IESG IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2011 21:21:40 -0000

Hi folks,

Sam Hartman wrote (and others suggest):
>>
>>  I think that being able to discuss concerns with reviewers and being
>>  able to consider potential conflicts and other issues mean that an open
>>  dialogue with identified reviewers is an important part of our
>>  process. Anonymous contributions may have their place in the WG process,
>>  but I don't think they should have a place in expert review oor blocking
>>  objections to documents.  So, as an individual I strongly support making
>>  expert reviewers identities public.
>>  

I don't see that "public identity" (of expert reviewers) is 
required for "interactive discussion".  Or would anonymous
interaction fail a Turing test of some kind?

Chris Benson.

From tena@huawei.com  Mon Feb  7 18:05:02 2011
Return-Path: <tena@huawei.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FD6E3A7008; Mon,  7 Feb 2011 18:05:02 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b6uNdBVg-UJ6; Mon,  7 Feb 2011 18:05:01 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 585FB3A7007; Mon,  7 Feb 2011 18:05:01 -0800 (PST)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LGA009ZM0GHR5@usaga02-in.huawei.com>; Mon, 07 Feb 2011 18:05:06 -0800 (PST)
Received: from TingZousc1 ([10.193.34.106]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGA0082F0GHMN@usaga02-in.huawei.com>; Mon, 07 Feb 2011 18:05:05 -0800 (PST)
Date: Mon, 07 Feb 2011 18:05:05 -0800
From: Tina Tsou <tena@huawei.com>
Subject: Review of draft-ietf-netconf-4741bis-07
To: secdir@ietf.org
Message-id: <00dc01cbc734$9ab8cbe0$d02a63a0$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcvHNJologxQ/mhUTsec0i/teATXiw==
X-Mailman-Approved-At: Tue, 08 Feb 2011 08:35:17 -0800
Cc: ietf@ietf.org, iesg@ietf.org, draft-ietf-netconf-4741bis@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 02:05:02 -0000

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area
directors.  Document editors and WG chairs should treat these comments just
like any other last call comments.

It is well written, so only some editorial comments are below.

#1
"
2.2.  Authentication, Integrity, and Confidentiality
...
2.3.  Authentication
...
"

Perhaps the Titles of 2.2 and 2.3 can harmonize better to explain why there
are two "authentications" here.

#2
"
6.2.  Subtree Filter Components

   A subtree filter is comprised of XML elements and their XML
   attributes.  There are five types of components that may be present
   in a subtree filter:

   o  Namespace Selection

   o  Attribute Match Expressions

   o  Containment Nodes

   o  Selection Nodes

   o  Content Match Nodes
...
"

If a figure could be provided to describe the relationship among these 5
components and when it becomes what, it would be very helpful for readers to
understand more easily.

#3
"
6.2.3.  Containment Nodes

   Nodes that contain child elements within a subtree filter are called
   "containment nodes".  

I would say "Child Elements Nodes" or "Child Nodes" might be a little bit
more of straight forward than "Containment Nodes".


#4
"
7.2.  <edit-config>
...
Parameters:
...
merge:  The configuration data in the <config> parameter is
            merged with the configuration at the corresponding level in
            the target datastore.  This is the default behavior.
...
"
Has the <config> parameter been introduced before?


Best Regards,
Tina TSOU
http://tinatsou.weebly.com/contact.html




From huitema@microsoft.com  Tue Feb  8 12:41:32 2011
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 326673A6859; Tue,  8 Feb 2011 12:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8r6ecTio7+G; Tue,  8 Feb 2011 12:41:31 -0800 (PST)
Received: from smtp.microsoft.com (mail2.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 270773A6835; Tue,  8 Feb 2011 12:41:30 -0800 (PST)
Received: from TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 8 Feb 2011 12:41:37 -0800
Received: from TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com (157.54.71.68) by TK5EX14MLTC101.redmond.corp.microsoft.com (157.54.79.178) with Microsoft SMTP Server (TLS) id 14.1.270.2; Tue, 8 Feb 2011 12:41:37 -0800
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.204]) by TK5EX14MLTW652.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.68]) with mapi; Tue, 8 Feb 2011 12:41:37 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Chris Benson <cbenson@adax.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: RE: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned	Numbers Authority (IANA) Procedures for the Management of the Service	Name and Transport Protocol Port Number Registry) to BCP
Thread-Topic: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned	Numbers Authority (IANA) Procedures for the Management of the Service	Name and Transport Protocol Port Number Registry) to BCP
Thread-Index: AQHLx65uYHyiMSXjuU2y+c+m+OGflZP4EPgQ
Date: Tue, 8 Feb 2011 20:41:36 +0000
Message-ID: <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <Pine.LNX.4.64.1102071321290.4671@adax.adax>
In-Reply-To: <Pine.LNX.4.64.1102071321290.4671@adax.adax>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 20:41:32 -0000

> I don't see that "public identity" (of expert reviewers) is required for =
"interactive discussion". =20
> Or would anonymous interaction fail a Turing test of some kind?

Public identity is required for reviewer accountability. It is easy to imag=
ine how withholding registration of some required numbers may delay a compe=
titor's products. The best protection against shade is sunlight.

-- Christian Huitema



From ekr@rtfm.com  Tue Feb  8 12:58:33 2011
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83CD43A6857; Tue,  8 Feb 2011 12:58:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.677
X-Spam-Level: 
X-Spam-Status: No, score=-102.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwX5-+4TBvBO; Tue,  8 Feb 2011 12:58:32 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 79D503A684C; Tue,  8 Feb 2011 12:58:32 -0800 (PST)
Received: by yie19 with SMTP id 19so2791594yie.31 for <multiple recipients>; Tue, 08 Feb 2011 12:58:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.68.4 with SMTP id q4mr460212aga.54.1297198719438; Tue, 08 Feb 2011 12:58:39 -0800 (PST)
Received: by 10.90.117.9 with HTTP; Tue, 8 Feb 2011 12:58:39 -0800 (PST)
In-Reply-To: <DD68C5E0-BBE9-4F8A-87EA-2192ED24B158@iki.fi>
References: <20101130132359.32419.3777.idtracker@localhost> <alpine.LRH.2.02.1012201513440.26448@netcore.fi> <DD68C5E0-BBE9-4F8A-87EA-2192ED24B158@iki.fi>
Date: Tue, 8 Feb 2011 12:58:39 -0800
Message-ID: <AANLkTimUZ6VavWenYR8Ai2D0it7_jWCLpXdvu20N7jMX@mail.gmail.com>
Subject: Re: [TLS] Last Call: <draft-ietf-tls-rfc4347-bis-04.txt> (Datagram Transport Layer Security version 1.2) to Proposed Standard
From: Eric Rescorla <ekr@rtfm.com>
To: =?ISO-8859-1?Q?Juho_V=E4h=E4=2DHerttua?= <juhovh@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: tls@ietf.org, ietf@ietf.org, Pekka Savola <pekkas@netcore.fi>, tls-chairs@tools.ietf.org, draft-ietf-tls-rfc4347-bis@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 20:58:33 -0000

On Mon, Dec 20, 2010 at 11:01 AM, Juho V=E4h=E4-Herttua <juhovh@iki.fi> wro=
te:
> On 20.12.2010, at 15.15, Pekka Savola wrote:
>> 3.2.3. Message Size
>>
>> =A0 TLS and DTLS handshake messages can be quite large (in theory up to
>> =A0 2^24-1 bytes, in practice many kilobytes). =A0By contrast, UDP
>> =A0 datagrams are often limited to <1500 bytes if fragmentation is not
>> =A0 desired. =A0In order to compensate for this limitation, each DTLS
>> =A0 handshake message may be fragmented over several DTLS records. =A0Ea=
ch
>> =A0 DTLS handshake message contains both a fragment offset and a fragmen=
t
>> =A0 length.
>>
>> 4.1.1. Transport Layer Mapping
>>
>> =A0 Each DTLS record MUST fit within a single datagram. =A0In order to
>> =A0 avoid fragmentation, clients of the DTLS record layer SHOULD attempt
>> =A0 to size records so that they fit within any PMTU estimates obtained
>> =A0 from the record layer.
>>
>> ... these seem somewhat contradictory. =A0Maybe I'm missing something. =
=A0The
>> latter seems to be saying that DTLS implementations should try to avoid =
IP
>> fragmentation, but the former seems to imply that it's de-facto mode of
>> operation.
>
> These are not contradictory. If a handshake message size and record heade=
r don't fit inside single datagram, it should be fragmented into several sm=
all handshake messages and each of these is put into a separate DTLS record=
. The resulting DTLS record after encryption should not exceed the maximum =
UDP (or DCCP or whatever) datagram size and therefore doesn't need IP level=
 fragmentation.
>
> I think what you "missed" was simply the difference of IP level fragmenta=
tion and DTLS handshake protocol level fragmentation.

I think that is a lot of the issue here. We probably don't distinguish
these clearly. Given that I don't want to change terminology now
I suggest we just say "DTLS fragmentation" and "IP fragmentation".
It's clunky but serviceable.

WRT to the ICMP issue, my take on this is that ICMP Isn't reliable
both because of filtering and that it implies connected
sockets. So, the application needs to be able to determine PMTU even
if it never gets any kind of error indication. However,
I agree that if the stack does get an explicit error it MUST adjust.

The rest of Pekka's suggestions make sense and I should be able to
implement them.
-Ekr

From dworley@avaya.com  Tue Feb  8 14:19:04 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 413263A688C; Tue,  8 Feb 2011 14:19: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgNhUQM6s2BI; Tue,  8 Feb 2011 14:19:03 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id 647363A6884; Tue,  8 Feb 2011 14:19:03 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKtPUU3GmAcF/2dsb2JhbAClPHOjdgKZDYVaBIR7ijc
X-IronPort-AV: E=Sophos;i="4.60,444,1291611600"; d="scan'208";a="263840743"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 08 Feb 2011 17:19:10 -0500
X-IronPort-AV: E=Sophos;i="4.60,444,1291611600"; d="scan'208";a="579823777"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 Feb 2011 17:19:10 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 8 Feb 2011 17:19:09 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Cullen Jennings <fluffy@cisco.com>, IESG IESG <iesg@ietf.org>, "ietf@ietf.org IETF" <ietf@ietf.org>
Date: Tue, 8 Feb 2011 17:19:09 -0500
Subject: RE: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
Thread-Index: AcvG9tp8OycZ29IfRDWNxLgLbUB9PwA5d3Cj
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A17685A@DC-US1MBEX4.global.avaya.com>
References: <20110207170250.4107.67897.idtracker@localhost>, <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com>
In-Reply-To: <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 22:19:04 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Cullen Jen=
nings [fluffy@cisco.com]

I am still not aware of any use case where this actually helps. I searched =
the IETF and WG lists for email with the subject draft-ietf-sipcore-199 and=
 I do not see a single email that suggests there is support for this draft =
or the changes in it since the previous LC.
_______________________________________________

I recall discussing the utility of 199 at one of the IETF meetings.  Indeed=
, I pushed Christer rather hard on the subject.  The primary use is situati=
ons where the SIP UAC is a gateway and has to allocate audio processors to =
each early dialog; 199 gives the downstream elements the ability to release=
 the allocated processors when an early dialog ends, even though the UAC wi=
ll not see the failure response for some time.

Since then, the proposal has gone through a number of changes that increase=
 its value.  E.g., clarification of how it interacts with 100rel processing=
, ensuring it works correctly when non-199-aware SIP elements are present, =
providing warnings against likely errors by implementors, and allowing UACs=
 to generate 199s on their own behalf.  (That latter is significant in the =
SIP environments I work with, as we put more responsibility on the UAs and =
make the proxies stateless.)

Dale

From bob.hinden@gmail.com  Tue Feb  8 22:38:41 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB6CF3A6917; Tue,  8 Feb 2011 22:38:40 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlN4hHyiCsXR; Tue,  8 Feb 2011 22:38:39 -0800 (PST)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id A76B53A6900; Tue,  8 Feb 2011 22:38:39 -0800 (PST)
Received: by pzk5 with SMTP id 5so1631163pzk.31 for <multiple recipients>; Tue, 08 Feb 2011 22:38:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=h94Jts137J/3ATEjb2Xg0inTmBUVZwQeIG1S3cFtB/Q=; b=KaSVk8bz2bNVBQRLup2zgw09DjTQj9ZVXu8LfdgMvMSIrUWIuyej7H1U/865/B2N6V 8XY7/AixDhoXQLQk3p7SnU7g8xHzwuZdll71Uyd8wlMj3B96l6euMuR9FPVWbFAgidIF 2gFtokSl/LzyA14aA6PDhcOZmUIoJZ4QVjVXg=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=YqBG1fhzd1vifZjZ6IPP/r3UvkowGcBiYaCunxewKxd91YgBNl2pp7LmOv6tNbtp+G wUj6AMDpBoATrQYWjg8aCl4Dyn7VS7O/vXP0rUUTM+dem+oNxrkmbKMKPkuDb02tSqhA jlXePY9XLAMz02Qr1Vnam7GZWu10ACAnezBIg=
Received: by 10.142.173.8 with SMTP id v8mr17884190wfe.397.1297233526534; Tue, 08 Feb 2011 22:38:46 -0800 (PST)
Received: from [10.104.74.0] ([62.50.232.90]) by mx.google.com with ESMTPS id w42sm1389753wfh.3.2011.02.08.22.38.39 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Feb 2011 22:38:44 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned	Numbers Authority (IANA) Procedures for the Management of the Service	Name and Transport Protocol Port Number Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Date: Wed, 9 Feb 2011 07:38:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F547C5C9-22D8-4794-9EA6-C54E1DCB390C@gmail.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <Pine.LNX.4.64.1102071321290.4671@adax.adax> <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1082)
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Chris Benson <cbenson@adax.com>, IESG IESG <iesg@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2011 06:38:41 -0000

On Feb 8, 2011, at 9:41 PM, Christian Huitema wrote:

>> I don't see that "public identity" (of expert reviewers) is required =
for "interactive discussion". =20
>> Or would anonymous interaction fail a Turing test of some kind?
>=20
> Public identity is required for reviewer accountability. It is easy to =
imagine how withholding registration of some required numbers may delay =
a competitor's products. The best protection against shade is sunlight.

+1

Bob


>=20
> -- Christian Huitema
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From twalsh@juniper.net  Wed Feb  9 09:44:53 2011
Return-Path: <twalsh@juniper.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3BA13A69EA for <ietf@core3.amsl.com>; Wed,  9 Feb 2011 09:44:53 -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=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XPGwoHkefE2p for <ietf@core3.amsl.com>; Wed,  9 Feb 2011 09:44:53 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by core3.amsl.com (Postfix) with ESMTP id 9BDB63A69EC for <ietf@ietf.org>; Wed,  9 Feb 2011 09:44:52 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTVLSnr4IAQB+tG491pbIZhbJHVoyTVUf@postini.com; Wed, 09 Feb 2011 09:45:03 PST
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 9 Feb 2011 09:42:37 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Wed, 9 Feb 2011 12:42:47 -0500
From: Thomas Walsh <twalsh@juniper.net>
To: IETF discussion list <ietf@ietf.org>
Date: Wed, 9 Feb 2011 12:42:46 -0500
Subject: FW: NomCom 2010-2011: IAOC Appointment 
Thread-Topic: NomCom 2010-2011: IAOC Appointment 
Thread-Index: AcvIgIetPaZzpo1xSi64Jz094Bs2GAAADAvg
Message-ID: <A4C6A166C36F5F40A5767E6F66358FC0931D3B5256@EMBX01-WF.jnpr.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Feb 2011 17:44:53 -0000

-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org=
] On Behalf Of NomCom Chair
Sent: Wednesday, February 09, 2011 9:41 AM
To: IETF Announcement list
Subject: NomCom 2010-2011: IAOC Appointment=20

Hi Folks,=20

The 2010-2011 IETF Nominating Committee is pleased to announce the=20
selection of an individual to serve on the IETF Administrative=20
Oversight Committee (IAOC) starting in March 2011 for a two year term.=20

Dave Crocker has been selected as the candidate by the nominating=20
committee and confirmed by the IESG in their role as confirming body.

Our thanks to Dave for agreeing to serve, to all the nominees, and to=20
the community for their assistance in this process.=20

Best Regards,=20

Thomas Walsh=20
nomcom-chair@ietf.org=20
twalsh@juniper.net

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From narten@us.ibm.com  Thu Feb 10 21:53:01 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C56783A688F for <ietf@core3.amsl.com>; Thu, 10 Feb 2011 21:53:01 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wnPzzhouUkb for <ietf@core3.amsl.com>; Thu, 10 Feb 2011 21:52:59 -0800 (PST)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by core3.amsl.com (Postfix) with ESMTP id 807CD3A6884 for <ietf@ietf.org>; Thu, 10 Feb 2011 21:52:58 -0800 (PST)
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by e31.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p1B5cNsj007550 for <ietf@ietf.org>; Thu, 10 Feb 2011 22:38:23 -0700
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p1B5r3DP119294 for <ietf@ietf.org>; Thu, 10 Feb 2011 22:53:03 -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 p1B5r3lu006312 for <ietf@ietf.org>; Thu, 10 Feb 2011 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p1B5r37w006300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 10 Feb 2011 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p1B5r2Df008331 for <ietf@ietf.org>; Fri, 11 Feb 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p1B5r2to008319 for ietf@ietf.org; Fri, 11 Feb 2011 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201102110553.p1B5r2to008319@rotala.raleigh.ibm.com>
Date: Fri, 11 Feb 2011 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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 05:53:01 -0000

Total of 28 messages in the last 7 days.
 
script run at: Fri Feb 11 00:53:02 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.71% |    3 |  7.90% |    13523 | jari.arkko@piuha.net
  7.14% |    2 |  9.26% |    15843 | evnikita2@gmail.com
  7.14% |    2 |  6.09% |    10421 | lear@cisco.com
  3.57% |    1 |  5.71% |     9779 | ron.even.tlv@gmail.com
  3.57% |    1 |  4.90% |     8390 | christer.holmberg@ericsson.com
  3.57% |    1 |  4.36% |     7469 | shinta@sfc.wide.ad.jp
  3.57% |    1 |  4.31% |     7376 | narten@us.ibm.com
  3.57% |    1 |  4.30% |     7364 | adam@nostrum.com
  3.57% |    1 |  4.22% |     7224 | david.black@emc.com
  3.57% |    1 |  3.99% |     6830 | fluffy@cisco.com
  3.57% |    1 |  3.85% |     6597 | rolf.winter@neclab.eu
  3.57% |    1 |  3.80% |     6507 | ipng@69706e6720323030352d30312d31340a.nosense.org
  3.57% |    1 |  3.65% |     6253 | ekr@rtfm.com
  3.57% |    1 |  3.59% |     6148 | pasi.sarolahti@iki.fi
  3.57% |    1 |  3.45% |     5900 | dworley@avaya.com
  3.57% |    1 |  3.43% |     5876 | bob.hinden@gmail.com
  3.57% |    1 |  3.18% |     5442 | tena@huawei.com
  3.57% |    1 |  3.18% |     5438 | marka@isc.org
  3.57% |    1 |  3.01% |     5151 | touch@isi.edu
  3.57% |    1 |  3.01% |     5151 | huitema@microsoft.com
  3.57% |    1 |  2.82% |     4834 | twalsh@juniper.net
  3.57% |    1 |  2.75% |     4713 | cbenson@adax.com
  3.57% |    1 |  2.66% |     4560 | mohta@necom830.hpcl.titech.ac.jp
  3.57% |    1 |  2.54% |     4350 | dmiloshevic@afilias.info
--------+------+--------+----------+------------------------
100.00% |   28 |100.00% |   171139 | Total

From wwwrun@core3.amsl.com  Fri Feb 11 10:08:05 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 8D67C3A6860; Fri, 11 Feb 2011 10:08:05 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: RFP for XML2RFC Tool Development 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110211180805.8D67C3A6860@core3.amsl.com>
Date: Fri, 11 Feb 2011 10:08:05 -0800 (PST)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org, tools-development@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 18:08:05 -0000

The IETF Administrative Oversight Committee (IAOC), on behalf of the IETF,
announces this Request for Proposals to develop the XML2RFC Tool.  The
successful bidder will enter into a contract with the Internet Society.

The xml2rfc tool is used by authors to compose Internet-Drafts, and by
the RFC Production Center to produce RFCs. This development effort is
intended to produce an xml2rfc tool that uses the same input format with a
few enhancements, is easy to install on a personal machine, and is easier
to maintain and enhance in the future.

Bidders may elect to submit one or two bids to reflect the development
approach they follow, that is, whether to develop a single program that
handles the xml2rfc input format and does all of the processing, and/or
develop software that handles the xml2rfc input format and then calls upon
other existing programs as needed to complete the overall task (such as
nroff or gruff).

The python language is preferred for software development. Proposals that
use other languages will be accepted, but the proposal must explain why a
language other than python is desirable for the tasks proposed.

The xml2rfc tool created under this effort shall generate output
comparable to the current version xml2rfc.tcl with the current version of
the DTD, fixes to the various issues that have been filed in and resolved
in the bug tracker, and the enhancements specified below. To the greatest
extent practical, the xml2rfc tools needs to accommodate changes by the
community to the DTD; several potential improvements are under discussion.


During development, the winning bidder may come up with ideas to further
improve the usability or maintainability of the xml2rfc tools.

The Statement of Work includes three sections. The first section
discusses xml2rfc processing. The second section describes required
enhancements to the current xml2rfc tool. The third section describes the
preferred nroff output, which is a bit different than the nroff output
produced by the current xml2rfc tool.

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html 

Proposals must be received via email at rpelletier@isoc.org no later than
February 28, 2011 5:00 P.M. EST.  All questions/inquiries must be
submitted in writing and must be received no later than midnight, EST,
February 18, 2011.  Responses to questions and inquiries shall be posted
online at:  http://iaoc.ietf.org/rfpsrfis.html by midnight, EST, February
22, 1011. 

The point of contact regarding this RFP is the IETF Administrative
Director, Ray Pelletier, iad@ietf.org.

From alexey.melnikov@isode.com  Sat Feb 12 12:01:49 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D6F23A6AEF; Sat, 12 Feb 2011 12:01:49 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sbsjfM17OaBK; Sat, 12 Feb 2011 12:01:48 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id B34DC3A6ADF; Sat, 12 Feb 2011 12:01:47 -0800 (PST)
Received: from [188.28.20.209] (188.28.20.209.threembb.co.uk [188.28.20.209])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TVbnOAADL2Tc@rufus.isode.com>; Sat, 12 Feb 2011 20:02:02 +0000
Message-ID: <4D56E703.7050304@isode.com>
Date: Sat, 12 Feb 2011 20:01:07 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>  (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org>
In-Reply-To: <4D457FD9.5030905@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2011 20:01:49 -0000

Hi Paul (and Cullen),

Paul Hoffman wrote:

> On 1/29/11 9:34 PM, Joe Touch wrote:
>
>> On 1/29/2011 8:54 PM, Cullen Jennings wrote:
>>
>>> On Jan 27, 2011, at 17:10 , Joe Touch wrote:
>>
>> ...
>>
>>>> AFAICT, the experts team reports to IANA. We make recommendations to
>>>> them. They are the ones who have the conversation with the applicant.
>>>> They can take our advice or not - that's their decision.
>>>
>>>
>>> I think you are pretty misrepresenting the situation. My impression
>>> of the reality of the situation is that if the IANA did not like the
>>> advice of the expert reviewer, they might ask the AD to override but
>>> short of that they pretty much do whatever the expert says.
>>
>>
>> As per my other note:
>> RFC2780 specifies Expert Review as *one* of the viable means by which
>> IANA can decide on transport protocol port assignments. The term "Expert
>> Review" is defined in RFC 2434.
>>
>> Neither document binds IANA to use the advice of a reviewer.
>>
>> Further, there is no single reviewer - we have a team, consulting each
>> other on occasion, and all decisions are seen by multiple reviewers.
>> However, none of that is worth codifying. If IANA or the IESG doesn't
>> like how we serve them, they can replace us - at any time, for any
>> reason, and there is an appeals process for decisions of the expert 
>> team:
>>
>> Any decisions made by the designated expert can be appealed using the
>> normal IETF appeals process as outlined in Section 6.5 of [IETF-
>> PROCESS].
>
> Now that this has been made clear to me, I am *much* more worried 
> about the wording in the current draft. The above emphatic statements 
> means that IANA can reject a request for an IETF-approved protocol 
> that needs two ports without recourse. As Cullen and others have 
> pointed out, there are sometimes very good technical reasons for a 
> particular protocol to need to have two ports.
>
> The document should be amended to say that protocols with IETF 
> consensus should get as many ports as it needs, regardless of what 
> IANA or the expert reviewer thinks. This makes it the responsibility 
> of the IETF consensus process to follow the guidelines in this document.

I think the document (-10) was amended as requested, but can you please 
double check?


From alexey.melnikov@isode.com  Sat Feb 12 12:03:15 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F117E3A6A41; Sat, 12 Feb 2011 12:03: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id txdNbcyusqGF; Sat, 12 Feb 2011 12:03:15 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id F3DD83A6AEF; Sat, 12 Feb 2011 12:03:14 -0800 (PST)
Received: from [188.28.20.209] (188.28.20.209.threembb.co.uk [188.28.20.209])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TVbnjwADL4vp@rufus.isode.com>; Sat, 12 Feb 2011 20:03:30 +0000
Message-ID: <4D56E75A.9070903@isode.com>
Date: Sat, 12 Feb 2011 20:02:34 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>  (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu> <4D457FD9.5030905@vpnc.org> <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com> <4D46CC62.1040006@vpnc.org>
In-Reply-To: <4D46CC62.1040006@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, IESG IESG <iesg@ietf.org>, tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2011 20:03:16 -0000

Paul Hoffman wrote:

> On 1/31/11 12:23 AM, Lars Eggert wrote:
>
>> On 2011-1-30, at 17:12, Paul Hoffman wrote:
>>
>>> The above emphatic statements means that IANA can reject a request 
>>> for an IETF-approved protocol that needs two ports without recourse.
>>
>> I don't follow. Assignments through IETF-stream documents do not go
>> through expert review.
>
> Then this should be made *much* clearer in the document.

I believe this was clarified in -10.

> In fact, the document says:
>    A key element of the procedural streamlining specified in this
>    document is to establish identical assignment procedures for all IETF
>    transport protocols.
>
> I assumed that "all" meant "all", not "all except those through 
> IETF-stream documents"; others might have read it the same way I did. 
> Further, the wording throughout the template description in 8.1 makes 
> it sound like that the restrictions in this document apply to 
> everything that needs a template, which clearly includes IETF-stream 
> documents.



From ben@nostrum.com  Fri Feb 11 15:46:24 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C9EF3A69D1; Fri, 11 Feb 2011 15:46:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.3
X-Spam-Level: 
X-Spam-Status: No, score=-100.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hqV8OXq9FgH; Fri, 11 Feb 2011 15:46:22 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 5DB093A6838; Fri, 11 Feb 2011 15:46:21 -0800 (PST)
Received: from dn3-227.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 p1BNkP6W064978 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 11 Feb 2011 17:46:30 -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-bryan-metalinkhttp-19
Date: Fri, 11 Feb 2011 17:46:24 -0600
Message-Id: <19DDC0DF-9ECF-499A-954E-17BABF6410B5@nostrum.com>
To: General Area Review Team <gen-art@ietf.org>, draft-bryan-metalinkhttp.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Mon, 14 Feb 2011 09:49:44 -0800
Cc: The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2011 23:46: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 resolve these comments along with any other Last Call comments =
you may receive.

Document: draft-bryan-metalinkhttp-19
Reviewer: Ben Campbell
Review Date: 2011-02-11
IETF LC End Date: 2011-02-11

Summary:=20

This document is on the right track for a proposed standard, but there =
are open issues and editorial issues that should be addressed prior to =
publication.

--- Major issues:=20

none.

--- Minor issues:

-- Section 1, paragraph 1, first sentence:

Is this really intended as an alternative to Metalink/XML? It seems like =
more of a complementary approach than an alternative one.

-- section 2, third paragraph:

If they must have the same eTag policy, should this document not specify =
at least one mandatory-to-implement policy?

-- section 2, last paragraph: "Metalink clients MAY make use of digital =
signatures if they are offered."

That seems too weak. We usually recommend that people check signatures =
on downloads when available. Wouldn't we want an automated system to =
treat this as at least a SHOULD?

-- section 3, 4th paragraph: "[[Some organizations have many mirrors. =
Only send a few mirrors, or only use the Link header fields if =
Want-Digest is used?]]"

Open issue?

-- section 3.3, 1st paragraph:"([draft-ietf-ftpext2-hash] allows for FTP =
mirrors to be coordinated and provide file hashes)."

Do you mean to allow such FTP servers to be preferred?=20

-- section 4.1 "This is particularly useful for providing metadata such =
as cryptographic hashes of parts of a file, allowing a client to recover =
from partial errors (see Section 7.1.2)."

Seems like this might warrant a SHOULD.

-- section 5, last paragraph: "Metalink clients MAY support the use of =
OpenPGP signatures."

MAY seems weak here. This means that the publisher of a file has no =
reasonable expectation that clients will check the signature.

-- section 6, 3rd paragraph: "Digest: SHA-256=3D..."

Example needs more context


-- section 7, 4th paragraph from end: "Downloads from mirrors that do =
not have the same file size as the Metalink server are considered =
unusable and the client can deal with it as it sees fit."

What if the client sees fit to use it? Is there a normative  "client =
SHOULD NOT" implied here?

-- section 7.1.1, 1st paragraph:"the requirement is that merging of =
ranges from multiple responses must be verified"

The requirement for what? Is this intended to be normative?


-- section 7.1.2, 2nd paragraph:"If no partial cryptographic hashes are =
available, then the client MUST fetch the complete object from other =
mirrors."

Does this imply that the client also MUST fetch from other mirrors if =
the hashed are present but fail verification?

-- section 8, last paragraph: "The size of chunks chosen by the client =
should be sufficiently large that the chunk request header fields and =
reponse header fields represent neglible overhead, and sufficiently =
large that they can be pipelined effectively without needing a very high =
rate of chunk requests."

Can you provide guidance on what "sufficiently large", and  "negligible =
overhead" mean, either in terms of examples or real numbers?

"Note that Range requests impose an overhead on servers and clients need =
to be aware of that and not abuse them."

What constitutes abuse? Can you provide more specific guidance on when =
range should not be used, since all the other guidance seems to suggest =
using it?

-- section 10.2:

What can an implementor do to mitigate spoofing?

-- section 10.4:

This section should include a warning that clients only have a MAY level =
requirement to support signature verification.

"Metalinks should include digital signatures, as described in Section =
5."

Normative?

-- section 11.1, [BITTORRENT]

Is bittorrent.org an acceptable SDO for the purposes of normative =
references? (I'm not saying it's not--just asking)

[draft-ietf-ftpext2-hash]  -- is this a normative downref?







--- Nits/editorial comments:

-- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the same =
ETag policy as the originating Metalink server."

-- section 2, 5th paragraph: "Metalink clients use the mirrors provided =
by a Metalink server with Link header fields [RFC5988]."

Sentence seems ambiguous. Do you mean "_in_ Link header fields."

-- section 3, 2nd paragraph: "A brief Metalink server response with two =
mirrors only:"

Sentence fragment

-- section 3, last paragraph: "fieldss"

Typo. (Note same typo repeats throughout)

"Such a decision could be a hard-coded limit, a random selection, based =
on file size, or based on server load."

I assume this is not meant to be exhaustive?

-- section 3.3, last paragraph:

Paragraph is redundant with similar normative statements in section 2

-- section 4.1: "as shown in Section 4."

.. as shown in the example in section 4.

-- section 6, 1st paragraph: "Metalink servers MUST provide Instance =
Digests in HTTP [RFC3230] for files they describe with mirrors via Link =
header fields."

Redundant with previously mentioned normative requirement.

-- section 7, paragraph starting with: "If no range limit was given in =
the original request then work from the tail of the object (the first =
request is still running and will eventually catch up), otherwise =
continue after the range requested in the first request."

Implied "you". Restate as "the client works from the tail" (Please avoid =
use of 2nd person pronouns in an RFC, implied or otherwise) (Note that =
this usage is sprinkled throughout )

"If no Range was provided,"

... in the original request,...

Also, be careful with the passive voice in this paragraph. Who =
undertakes HEAD requests first? Who undertakes Range-based requests?

-- section 7, paragraph 10: "If-Match conditions based on the ETag =
SHOULD be used..."

Clients should use If-Match conditions...

"If no indication of ETag syncronisation/ knowledge is given then =
If-Match should not be used, and optimally there will be an Instance =
Digest in the mirror response which we can use to detect a mismatch =
early, and if not then a mismatch won=92t be detected until the =
completed object is verified."

Is there any way other than the pref parameter to indicate this? If not, =
it would be better to say "if no pref parameter is present..."

Is this sentence intended to be normative?

Also, "... The client should not use..."

Finally, the sentence is hard to follow--please break it up.

-- section 7.1.1, general:

This whole section switches to an almost stream-of-consciousness style. =
It has very long sentences with many comma separated clauses that are =
hard to follow. It really needs to be rewritten to be more readable and =
precise.

-- section 7.1.1, paragraph 3:

Paragraph seems self contradictory. How is guaranteeing correct content =
different than verifying integrity?

-- paragraph 4: "This guarantees that a mismatch will be detected by =
using only the synchronized ETag from a master server and mirror server, =
even alerted by the mirror servers themselves by responding with an =
error, preventing accidental merges of ranges from different versions of =
files with the same name."

I can't parse this sentence.

"This even includes many malicious attacks where the data on the mirror =
has been replaced by some other file, but not all."

Antecedent of "this" is ambiguous

-- 2nd to last paragraph:

This is the first mention of e idea of slave and master mirror servers. =
Is this the same as preferred and normal mirrors? Please use consistent =
terms.

-- section 7.1.2, 2nd paragraph: "If the object cryptographic hash does =
not match the Instance Digest then fetch the Metalink/XML if available, =
where partial file cryptographic hashes can be found, allowing detection =
of which server returned incorrect data."

I can't parse this sentence.

-- section 8, paragraph after bullet list:

Please avoid first person pronouns in an RFC.

"Based on laboratory experiments,..."

Reference?

"we suggest a good default number of simultaneous connections is =
probably four,"

That's very weak language--can you remove "we suggest" and "probably"?

-- Section 9, 1st paragraph: "registration to the Link Relation Type =
registry"

Can you provide the URL to the registry?

-- section 10.2 "In that case, this could deceive unaware downloaders =
that they are downloading a malicious or worthless file."

Sentence does not make sense. Does the attacker with to deceive them =
into downloading a malicious file, or convince them that they are when =
they are not?




From rbarnes@bbn.com  Tue Feb 15 09:05:17 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F315F3A6CAB for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 09:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=0.157, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJYZYTzmKs8T for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 09:05:16 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id EA98F3A6D26 for <ietf@ietf.org>; Tue, 15 Feb 2011 09:05:15 -0800 (PST)
Received: from [128.89.253.66] (port=56051 helo=[192.168.5.174]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PpOLN-000EwJ-NG for ietf@ietf.org; Tue, 15 Feb 2011 12:05:41 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <20110118150445.13842.1912.idtracker@localhost>
Date: Tue, 15 Feb 2011 12:05:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com>
References: <20110118150445.13842.1912.idtracker@localhost>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 17:05:17 -0000

One late comment on this: Section 7 discusses the impact of address =
sharing on geolocation and geo-proximity use cases.  (Nit: common usage =
is "geolocation", not "geo-location")  This section does a good job of =
describing the impact of address sharing on the common case where an IP =
address is used as a key into a generic "IP geo" database.

However, there are several emerging systems that provide much more than =
these generic databases.  Typically, these systems tap into network =
management infrastructure to map an IP address to the physical resource =
to which it is assigned, using things like RADIUS databases and DHCP =
lease tables. This is an important use case, for example, for ECRIT =
emergency services [draft-ietf-ecrit-framework] using the HELD location =
protocol [RFC5985].  (Also an issue that Law Enforcement agencies have =
been known to care deeply about.)

It would be good for this draft to comment on the impact of address =
sharing for these high-precision IP-geo systems. Suggested text for =
after the first paragraph of Section 7:
"
IP addresses are also used as input to higher-fidelity geolocation =
services that resolve an IP address to a physical location using =
information from the network infrastructure.  Current systems rely on =
resources such as RADIUS databases and DHCP lease tables.  The use of =
address sharing will prevent these systems from resolving the location =
of a host based on IP address alone.  It will be necessary for users of =
such systems to provide more information (e.g., TCP or UDP port numbers =
[I-D.ietf-geopriv-held-identity-extensions]), and for the systems to use =
this information to query additional network resources (e.g., NAT-PT =
binding tables).  Since these new data elements tend to be more =
ephemeral than those currently used for geolocation, their use by =
geolocation systems may require them to be cached  for some period of =
time.
"=20


On Jan 18, 2011, at 10:04 AM, The IESG wrote:

>=20
> The IESG has received a request from the Internet Area Working Group =
WG
> (intarea) to consider the following document:
> - 'Issues with IP Address Sharing'
>  <draft-ietf-intarea-shared-addressing-issues-02.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 2011-02-01. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> The file can be obtained via
> =
http://datatracker.ietf.org/doc/draft-ietf-intarea-shared-addressing-issue=
s/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-intarea-shared-addressing-issue=
s/
>=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


From rbarnes@bbn.com  Tue Feb 15 09:06:00 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 848CE3A6CB9; Tue, 15 Feb 2011 09:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level: 
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyo0UUByKFNA; Tue, 15 Feb 2011 09:05:59 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 974593A6D27; Tue, 15 Feb 2011 09:05:59 -0800 (PST)
Received: from [128.89.253.66] (port=56051 helo=[192.168.5.174]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PpOM5-000EwJ-CK; Tue, 15 Feb 2011 12:06:25 -0500
Subject: Re: Last Call: <draft-ymbk-aplusp-08.txt> (The A+P Approach to the IPv4 Address Shortage) to Experimental RFC
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <20110110160206.9040.18655.idtracker@localhost>
Date: Tue, 15 Feb 2011 12:06:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B799D9BC-50B4-4DFB-9E68-BB62C701BC08@bbn.com>
References: <20110110160206.9040.18655.idtracker@localhost>
To: The IESG <iesg-secretary@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 17:06:00 -0000

One late comment: It would be helpful for this document to have some =
comment on how it impacts systems that provide geolocation information =
based on IP address.

Suggested text (not sure where to put this, maybe Section 1.1?):
"
As with other large-scale NAT systems, A+P will cause problems for =
systems that provide geolocation information based on IP addresses.  If =
these systems are unable to account use port information to identify =
hosts (i.e., if they continue to use IP addresses alone), then their =
precision will be reduced to the scale of the NAT -- potentially a large =
area.  Conversely, if such systems need to continue to be able to =
identify specific hosts, clients of such systems will need to provide =
port information, and servers will need to be able to use this =
information to identify hosts (e.g., by querying A+P binding tables).
"

See also my comments on draft-intarea-shared-addressing-issues:
=
<https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D5549=
5&tid=3D1297789532>




On Jan 10, 2011, at 11:02 AM, The IESG wrote:

>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'The A+P Approach to the IPv4 Address Shortage'
>  <draft-ymbk-aplusp-08.txt> as an Experimental RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-02-07. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ymbk-aplusp/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ymbk-aplusp/
>=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


From anthonybryan@gmail.com  Mon Feb 14 14:43:16 2011
Return-Path: <anthonybryan@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 240753A6C72; Mon, 14 Feb 2011 14:43:16 -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=-1.450, BAYES_00=-2.599, J_CHICKENPOX_39=0.6, MANGLED_LIST=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HA6DOmnmcksG; Mon, 14 Feb 2011 14:43:14 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 911F73A6A3D; Mon, 14 Feb 2011 14:43:13 -0800 (PST)
Received: by eyd10 with SMTP id 10so2871053eyd.31 for <multiple recipients>; Mon, 14 Feb 2011 14:43:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OAEuQ+DkxKpnhgu0ANzChm5qETRbFCjBuFIIdGi8Lyk=; b=H7gt6BpUfpKnQRXbEGLPCtwWp0DRbEZ0gJlyG6BYgRLusLlLCaui2r1Yp0Omsi9TKu BDNou2TlGkvf3HBw7Fd3jApYe4H+KKmkEkLA86O6JfWR0ZLNJvEn3o1+ZP88rXXq/ZAi RDZ9eIOWC0y3B2oFlPCy7a1au6eezrhFZI5p0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Cy+eUkWdYIkrCFInDh5dB5MRQyU0pGZ1r2ULGQVxecFnvteGmo2L4Cj5MoLaYbUrcS cgrNOymkqcs+mWAanzEBqktyauoaIZB/xaTLJLpsFmcc8uZweXnHwYS7ENiP/eCSjMZU SBhJYex/STWQvbOBfDkAGOjFcqLODrfdAqcyc=
MIME-Version: 1.0
Received: by 10.213.29.210 with SMTP id r18mr4627184ebc.62.1297723414743; Mon, 14 Feb 2011 14:43:34 -0800 (PST)
Received: by 10.213.22.11 with HTTP; Mon, 14 Feb 2011 14:43:34 -0800 (PST)
In-Reply-To: <19DDC0DF-9ECF-499A-954E-17BABF6410B5@nostrum.com>
References: <19DDC0DF-9ECF-499A-954E-17BABF6410B5@nostrum.com>
Date: Mon, 14 Feb 2011 17:43:34 -0500
Message-ID: <AANLkTik3VNfsT4fY2wc8HpfidPVCshGSUW1py4Jzf==w@mail.gmail.com>
Subject: Re: Gen-ART LC Review of draft-bryan-metalinkhttp-19
From: Anthony Bryan <anthonybryan@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 15 Feb 2011 09:25:52 -0800
Cc: alexey.melnikov@isode.com, General Area Review Team <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-bryan-metalinkhttp.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Feb 2011 22:43:16 -0000

hi Ben, thanks for taking the time to read & critique this :)
I apologize for it needing this exhaustive review.

the new version can be found at
http://tools.ietf.org/html/draft-bryan-metalinkhttp-20

with diff including your & others suggestions
http://tools.ietf.org/rfcdiff?url2=3Ddraft-bryan-metalinkhttp-20.txt

was there supposed to be a comment along with

-- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the
same ETag policy as the originating Metalink server."
?

On Fri, Feb 11, 2011 at 6:46 PM, 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/G=
enArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you=
 may receive.
>
> Document: draft-bryan-metalinkhttp-19
> Reviewer: Ben Campbell
> Review Date: 2011-02-11
> IETF LC End Date: 2011-02-11
>
> Summary:
>
> This document is on the right track for a proposed standard, but there ar=
e open issues and editorial issues that should be addressed prior to public=
ation.
>
> --- Major issues:
>
> none.
>
> --- Minor issues:
>
> -- Section 1, paragraph 1, first sentence:
>
> Is this really intended as an alternative to Metalink/XML? It seems like =
more of a complementary approach than an alternative one.

well...you could use either, or both :)

"Metalink/HTTP is an alternative and complementary representation of
Metalink information,"...
?

> -- section 2, third paragraph:
>
> If they must have the same eTag policy, should this document not specify =
at least one mandatory-to-implement policy?

SHOULD share the same ETag policy.

I added:

"It is up to the administrator of the Metalink server to communicate
the details of the shared ETag policy to the administrators of the
mirror servers so that the mirror servers can be configured with the
same ETag policy."

> -- section 2, last paragraph: "Metalink clients MAY make use of digital s=
ignatures if they are offered."
>
> That seems too weak. We usually recommend that people check signatures on=
 downloads when available. Wouldn't we want an automated system to treat th=
is as at least a SHOULD?

I think this was written with the idea that most download clients
won't have the capability to check signatures, even if we would like
them to.

"Metalink clients SHOULD support checking digital signatures."

> -- section 3, 4th paragraph: "[[Some organizations have many mirrors. Onl=
y send a few mirrors, or only use the Link header fields if Want-Digest is =
used?]]"
>
> Open issue?

removed...

> -- section 3.3, 1st paragraph:"([draft-ietf-ftpext2-hash] allows for FTP =
mirrors to be coordinated and provide file hashes)."
>
> Do you mean to allow such FTP servers to be preferred?

removed too.

> -- section 4.1 "This is particularly useful for providing metadata such a=
s cryptographic hashes of parts of a file, allowing a client to recover fro=
m partial errors (see Section 7.1.2)."
>
> Seems like this might warrant a SHOULD.

"Metalink servers SHOULD provide Metalink/XML files with partial file
hashes in Link header fields and Metalink clients SHOULD use them for
error recovery."

> -- section 5, last paragraph: "Metalink clients MAY support the use of Op=
enPGP signatures."
>
> MAY seems weak here. This means that the publisher of a file has no reaso=
nable expectation that clients will check the signature.

changed to SHOULD.

> -- section 6, 3rd paragraph: "Digest: SHA-256=3D..."
>
> Example needs more context

added:
Etag: "thvDyvhfIqlvFe+A9MYgxAfm1q5=3D"
Link: &lt;http://www2.example.com/example.ext&gt;; rel=3Dduplicate


> -- section 7, 4th paragraph from end: "Downloads from mirrors that do not=
 have the same file size as the Metalink server are considered unusable and=
 the client can deal with it as it sees fit."
>
> What if the client sees fit to use it? Is there a normative =A0"client SH=
OULD NOT" implied here?

changed to

"Metalink clients SHOULD NOT use downloads from mirrors that do not
have the same file size as the Metalink server. "

> -- section 7.1.1, 1st paragraph:"the requirement is that merging of range=
s from multiple responses must be verified"
>
> The requirement for what? Is this intended to be normative?

changed

> -- section 7.1.2, 2nd paragraph:"If no partial cryptographic hashes are a=
vailable, then the client MUST fetch the complete object from other mirrors=
."
>
> Does this imply that the client also MUST fetch from other mirrors if the=
 hashed are present but fail verification?

no, changed.

> -- section 8, last paragraph: "The size of chunks chosen by the client sh=
ould be sufficiently large that the chunk request header fields and reponse=
 header fields represent negligible overhead, and sufficiently large that t=
hey can be pipelined effectively without needing a very high rate of chunk =
requests."
>
> Can you provide guidance on what "sufficiently large", and =A0"negligible=
 overhead" mean, either in terms of examples or real numbers?
>
> "Note that Range requests impose an overhead on servers and clients need =
to be aware of that and not abuse them."
>
> What constitutes abuse? Can you provide more specific guidance on when ra=
nge should not be used, since all the other guidance seems to suggest using=
 it?

removed section 8 except for this first sentence & added the next

"Note that Range requests impose an overhead on servers and clients
need to be aware of that and not abuse them. Metalink clients SHOULD
NOT make more than one concurrent Range request to each mirror server
that it downloads from."

> -- section 10.2:
>
> What can an implementor do to mitigate spoofing?

nothing, I'm aware of?

added:
As with all downloads, users should only download from trusted sources.

> -- section 10.4:
>
> This section should include a warning that clients only have a MAY level =
requirement to support signature verification.

changed to SHOULD

> "Metalinks should include digital signatures, as described in Section 5."
>
> Normative?

yes, changed to SHOULD.

> -- section 11.1, [BITTORRENT]
>
> Is bittorrent.org an acceptable SDO for the purposes of normative referen=
ces? (I'm not saying it's not--just asking)

it was for RFC 5854.
http://tools.ietf.org/html/rfc5854#section-8.1

> [draft-ietf-ftpext2-hash] =A0-- is this a normative downref?

removed



> --- Nits/editorial comments:
>
> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the same E=
Tag policy as the originating Metalink server."

what's wrong here?

> -- section 2, 5th paragraph: "Metalink clients use the mirrors provided b=
y a Metalink server with Link header fields [RFC5988]."
>
> Sentence seems ambiguous. Do you mean "_in_ Link header fields."

yes, changed.

> -- section 3, 2nd paragraph: "A brief Metalink server response with two m=
irrors only:"
>
> Sentence fragment

fixed

> -- section 3, last paragraph: "fieldss"
>
> Typo. (Note same typo repeats throughout)

fixed

> "Such a decision could be a hard-coded limit, a random selection, based o=
n file size, or based on server load."
>
> I assume this is not meant to be exhaustive?

"As some organizations can have many mirrors, it is up to the
organization to configure the amount of Link header fields the
Metalink server will provide. Such a decision could be a random
selection or a hard-coded limit based on network proximity, file size,
server load, or other factors. "

> -- section 3.3, last paragraph:
>
> Paragraph is redundant with similar normative statements in section 2

removed from 3.3

> -- section 4.1: "as shown in Section 4."
>
> .. as shown in the example in section 4.

fixed

> -- section 6, 1st paragraph: "Metalink servers MUST provide Instance Dige=
sts in HTTP [RFC3230] for files they describe with mirrors via Link header =
fields."
>
> Redundant with previously mentioned normative requirement.

removed

> -- section 7, paragraph starting with: "If no range limit was given in th=
e original request then work from the tail of the object (the first request=
 is still running and will eventually catch up), otherwise continue after t=
he range requested in the first request."
>
> Implied "you". Restate as "the client works from the tail" (Please avoid =
use of 2nd person pronouns in an RFC, implied or otherwise) (Note that this=
 usage is sprinkled throughout )
>
> "If no Range was provided,"
>
> ... in the original request,...
>
> Also, be careful with the passive voice in this paragraph. Who undertakes=
 HEAD requests first? Who undertakes Range-based requests?

rewritten

   If the first request was GET and no Range header field was sent and
   the client determines later that it will issue a Range request, then
   the client SHOULD close the first connection when it catches up with
   the other parallel ranged downloads of the same object.  This means
   the first connection was sacrificed.  Metalink clients can use a HEAD
   request first, if possible, so that the client can find out if there
   are any Link header fields, and then Range-based requests are
   undertaken to the mirror servers without sacrificing a first
   connection.

> -- section 7, paragraph 10: "If-Match conditions based on the ETag SHOULD=
 be used..."
>
> Clients should use If-Match conditions...
>
> "If no indication of ETag syncronisation/ knowledge is given then If-Matc=
h should not be used, and optimally there will be an Instance Digest in the=
 mirror response which we can use to detect a mismatch early, and if not th=
en a mismatch won=92t be detected until the completed object is verified."
>
> Is there any way other than the pref parameter to indicate this? If not, =
it would be better to say "if no pref parameter is present..."
>
> Is this sentence intended to be normative?
>
> Also, "... The client should not use..."
>
> Finally, the sentence is hard to follow--please break it up.

changed:

   Preferred mirrors have coordinated ETags, as described in
   Section 3.3, and Metalink clients SHOULD use If-Match conditions
   based on the ETag to quickly detect out-of-date mirrors by using the
   ETag from the Metalink server response.  Optimally, the mirror server
   will include an Instance Digest in the mirror response to the client
   GET request, which the client can also use to detect a mismatch
   early.  If the mirror did not include the pref parameter or an
   Instance Digest, then a mismatch can not be detected until the
   completed object is verified.

> -- section 7.1.1, general:
>
> This whole section switches to an almost stream-of-consciousness style. I=
t has very long sentences with many comma separated clauses that are hard t=
o follow. It really needs to be rewritten to be more readable and precise.

hahaha :)

this is my fault as a bad editor & a non-native English speaker co-author.

> -- section 7.1.1, paragraph 3:
>
> Paragraph seems self contradictory. How is guaranteeing correct content d=
ifferent than verifying integrity?

the server sends the correct content  but there can be errors during transf=
er.

maybe this is not explicit enough. might need to condense some of this down=
.

earlier we state:
Error detection requires Instance Digests to detect errors in transfer
after the transfers have completed.

> -- paragraph 4: "This guarantees that a mismatch will be detected by usin=
g only the synchronized ETag from a master server and mirror server, even a=
lerted by the mirror servers themselves by responding with an error, preven=
ting accidental merges of ranges from different versions of files with the =
same name."
>
> I can't parse this sentence.

 This guarantees that a mismatch will be detected by using only the
   shared ETag from a Metalink server and mirror server.  Mirror servers
   will respond with an error if ETags do not match, which will prevent
   accidental merges of ranges from different versions of files with the
   same name.

> "This even includes many malicious attacks where the data on the mirror h=
as been replaced by some other file, but not all."
>
> Antecedent of "this" is ambiguous

removed

> -- 2nd to last paragraph:
>
> This is the first mention of e idea of slave and master mirror servers. I=
s this the same as preferred and normal mirrors? Please use consistent term=
s.

ok.

> -- section 7.1.2, 2nd paragraph: "If the object cryptographic hash does n=
ot match the Instance Digest then fetch the Metalink/XML if available, wher=
e partial file cryptographic hashes can be found, allowing detection of whi=
ch server returned incorrect data."
>
> I can't parse this sentence.

   If the cryptographic hash of the object does not match the Instance
   Digest from the Metalink server, then the client SHOULD fetch the
   Metalink/XML (if available) that could contain partial file
   cryptographic hashes which will allow detection of which mirror
   server returned incorrect data.  Metalink clients SHOULD figure out
   what ranges of the downloaded data can be recovered and what needs to
   be fetched again.

> -- section 8, paragraph after bullet list:
>
> Please avoid first person pronouns in an RFC.
>
> "Based on laboratory experiments,..."
>
> Reference?

removed text

> "we suggest a good default number of simultaneous connections is probably=
 four,"
>
> That's very weak language--can you remove "we suggest" and "probably"?

removed

> -- Section 9, 1st paragraph: "registration to the Link Relation Type regi=
stry"
>
> Can you provide the URL to the registry?

added URL to registry

> -- section 10.2 "In that case, this could deceive unaware downloaders tha=
t they are downloading a malicious or worthless file."
>
> Sentence does not make sense. Does the attacker with to deceive them into=
 downloading a malicious file, or convince them that they are when they are=
 not?

"In that case, this could deceive unaware downloaders into downloading
a malicious or worthless file."


--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From mail@sabahattin-gucukoglu.com  Tue Feb 15 09:44:41 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6724F3A6A0F for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 09:44:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qcZkJsHOeIAp for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 09:44:40 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by core3.amsl.com (Postfix) with ESMTP id D71593A69AB for <ietf@ietf.org>; Tue, 15 Feb 2011 09:44:39 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:51595) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S29029> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Tue, 15 Feb 2011 17:45:04 -0000
Received: from [192.168.1.13] (cpc4-dals7-0-0-cust274.hari.cable.virginmedia.com [62.31.227.19]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Tue, 15 Feb 2011 17:45:03 +0000
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: World IPv6 Day and Us
Date: Tue, 15 Feb 2011 17:45:01 +0000
Message-Id: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Delivery-Agent: TMDA/1.1.12-kg2 (Pluto)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 17:44:41 -0000

Noting the increasing length of the list at =
http://isoc.org/wp/worldipv6day/participants/ (now with many former =
staunch nay-sayers on it, pleasingly), and that the ISOC considers =
itself a member, I think it only right to point out that we (IETF, IRTF, =
IESG, IAB, ICANN, IANA, et al) are not listed.

I don't suppose now is the time for an April 1 RFC discussing our =
commitment to the IPv6 protocol, and our intent to be present on World =
IPv6 day ......... is it?

Yes, I think we probably deserve a small slice of that publicity pie, =
too. :-)

Cheers,
Sabahattin

From shuque@isc.upenn.edu  Tue Feb 15 10:56:02 2011
Return-Path: <shuque@isc.upenn.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 708C93A6D52 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 10:56: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]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2Rbq+cymEw2 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 10:55:58 -0800 (PST)
Received: from talkeetna.isc-net.upenn.edu (TALKEETNA.isc-net.upenn.edu [128.91.197.188]) by core3.amsl.com (Postfix) with ESMTP id 1332B3A6AB3 for <ietf@ietf.org>; Tue, 15 Feb 2011 10:55:57 -0800 (PST)
Received: by talkeetna.isc-net.upenn.edu (Postfix, from userid 4127) id 89074235A; Tue, 15 Feb 2011 13:56:23 -0500 (EST)
Date: Tue, 15 Feb 2011 13:56:23 -0500
From: Shumon Huque <shuque@isc.upenn.edu>
To: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>
Subject: Re: World IPv6 Day and Us
Message-ID: <20110215185623.GA29973@isc.upenn.edu>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
User-Agent: Mutt/1.4.2.1i
Organization: University of Pennsylvania
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 18:56:02 -0000

Maybe it's because IETF/IRTF already have their outward facing
services available over IPv6 (Web, Mail, &, DNS at least - I checked 
only for ietf.org and irtf.org).

The stated purpose of IPv6 day seems to be to get folks who don't 
have any IPv6 in production yet to make it available for a 24-hour 
period for a "test drive":

	On 8 June, 2011, Google, Facebook, Yahoo!, Akamai and
	Limelight Networks will be amongst some of the major organisations
	that will offer their content over IPv6 for a 24-hour "test
	flight". The goal of the Test Flight Day is to motivate organizations
	across the industry ? Internet service providers, hardware makers,
	operating system vendors and web companies ? to prepare their services
	for IPv6 to ensure a successful transition as IPv4 addresses run out.

But sure, it sounds fine to me if we are also publicising 
organizations who already have production IPv6 services running long
in advance of "World IPv6 Day".

--Shumon.

On Tue, Feb 15, 2011 at 05:45:01PM +0000, Sabahattin Gucukoglu wrote:
> Noting the increasing length of the list at http://isoc.org/wp/worldipv6day/participants/ (now with many former staunch nay-sayers on it, pleasingly), and that the ISOC considers itself a member, I think it only right to point out that we (IETF, IRTF, IESG, IAB, ICANN, IANA, et al) are not listed.
> 
> I don't suppose now is the time for an April 1 RFC discussing our commitment to the IPv6 protocol, and our intent to be present on World IPv6 day ......... is it?
> 
> Yes, I think we probably deserve a small slice of that publicity pie, too. :-)
> 
> Cheers,
> Sabahattin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

-- 
Shumon Huque
University of Pennsylvania.

From mail@sabahattin-gucukoglu.com  Tue Feb 15 11:50:11 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57B443A6D10 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 11:50:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mChH7tXoUl2W for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 11:50:08 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by core3.amsl.com (Postfix) with ESMTP id 239CF3A6A9E for <ietf@ietf.org>; Tue, 15 Feb 2011 11:50:05 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:58338) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S29040> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Tue, 15 Feb 2011 19:50:30 -0000
Received: from [192.168.1.13] (cpc4-dals7-0-0-cust274.hari.cable.virginmedia.com [62.31.227.19]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Tue, 15 Feb 2011 19:50:29 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: World IPv6 Day and Us
In-Reply-To: <20110215185623.GA29973@isc.upenn.edu>
Date: Tue, 15 Feb 2011 19:50:27 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <C0A4655A-0462-4FFE-B3DF-05FB675BE565@sabahattin-gucukoglu.com>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com> <20110215185623.GA29973@isc.upenn.edu>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1082)
X-Delivery-Agent: TMDA/1.1.12-kg2 (Pluto)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1300391430.49cfb6@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 19:50:11 -0000

On 15 Feb 2011, at 18:56, Shumon Huque wrote:
> Maybe it's because IETF/IRTF already have their outward facing
> services available over IPv6 (Web, Mail, &, DNS at least - I checked=20=

> only for ietf.org and irtf.org).

Perhaps, but the same is true for ISOC.org.  Anyway, I'm not questioning =
ISOC's policy on the event, just making an observation.

Cheers,
Sabahattin

From housley@vigilsec.com  Tue Feb 15 12:13:47 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAAF43A6D7B for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 12:13:47 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bip595SDgxJO for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 12:13:46 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id C184E3A6D52 for <ietf@ietf.org>; Tue, 15 Feb 2011 12:13:46 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 9AF42F24018; Tue, 15 Feb 2011 15:14:14 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 5sVqBoleMK-P; Tue, 15 Feb 2011 15:14:10 -0500 (EST)
Received: from [192.168.2.105] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 50A75F24014; Tue, 15 Feb 2011 15:14:12 -0500 (EST)
Subject: Re: World IPv6 Day and Us
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
Date: Tue, 15 Feb 2011 15:14:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2934B7E1-D1CB-4940-A96B-DE7AC758E768@vigilsec.com>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
To: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>
X-Mailer: Apple Mail (2.1082)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 20:13:47 -0000

I have asked that www.ietf.org be added to the sites that are already =
IPv6 enabled.  I've also nudged the folks associated with these other =
organizations to do the same.

Russ

On Tue, Feb 15, 2011 at 05:45:01PM +0000, Sabahattin Gucukoglu wrote:
> Noting the increasing length of the list at =
http://isoc.org/wp/worldipv6day/participants/ (now with many former =
staunch nay-sayers on it, pleasingly), and that the ISOC considers =
itself a member, I think it only right to point out that we (IETF, IRTF, =
IESG, IAB, ICANN, IANA, et al) are not listed.
>=20
> I don't suppose now is the time for an April 1 RFC discussing our =
commitment to the IPv6 protocol, and our intent to be present on World =
IPv6 day ......... is it?
>=20
> Yes, I think we probably deserve a small slice of that publicity pie, =
too. :-)
>=20
> Cheers,
> Sabahattin

From cheshire@apple.com  Tue Feb 15 12:47:23 2011
Return-Path: <cheshire@apple.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 435E73A6D63 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 12:47:23 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEytrCJ-0mjY for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 12:47:22 -0800 (PST)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 0A2D93A6C74 for <ietf@ietf.org>; Tue, 15 Feb 2011 12:47:21 -0800 (PST)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id 83CAED251618 for <ietf@ietf.org>; Tue, 15 Feb 2011 12:47:48 -0800 (PST)
X-AuditID: 11807136-b7b89ae000000345-e7-4d5ae67488de
Received: from [17.193.13.41] (chesh1.apple.com [17.193.13.41]) by relay15.apple.com (Apple SCV relay) with SMTP id 9E.A9.00837.476EA5D4; Tue, 15 Feb 2011 12:47:48 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Transfer-Encoding: 7bit
Message-Id: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IETF-Discussion list <ietf@ietf.org>
From: Stuart Cheshire <cheshire@apple.com>
Subject: MHonArc mail archive line wrapping
Date: Tue, 15 Feb 2011 12:46:54 -0800
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: AAAAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 20:47:23 -0000

In the MHonArc mail archive there are often super-long lines, which  
would be wrapped to the window width when viewing in most mail  
clients, but when viewed in a web browser they appear as long single  
lines which take a lot of left-to-right scrolling to read them.

For example: <http://www.ietf.org/mail-archive/web/renum/current/ 
msg00060.html>

This appears to be due to MHonArc's use of the PRE tag, which tells  
the web browser to display the literal text exactly as given, in a  
fixed-width font.

The MHonArc FAQ suggests a couple of solutions to this problem:

> Can long lines be wrapped in converted messages?

<http://www.mhonarc.org/MHonArc/doc/faq/mime.html#lineclip>

> Can the <PRE> tags be removed from converted messages?

<http://www.mhonarc.org/MHonArc/doc/faq/mime.html#removepre>

Can we consider using either of these options?

Using "maxwidth=xxx" would solve this problem, though of course it  
opens the debate about what's the right value for "xxx".

Using "nonfixed" has the nice property of letting the web browser  
wrap the text to the window width, but might break ASCII-art  
diagrams. Perhaps that could be fixed by making the default font a  
fixed-width one (e.g. via style sheet) and using the "keepspace"  
option, which would give us monospaced text while still allowing the  
web browser to wrap the text to the current window width.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


From lixia@cs.ucla.edu  Tue Feb 15 12:53:35 2011
Return-Path: <lixia@cs.ucla.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A220F3A6DD9 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 12:53:35 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dr2q7i7Unbwy for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 12:53:34 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 179933A6DB3 for <ietf@ietf.org>; Tue, 15 Feb 2011 12:53:34 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id A9B2539E80DB; Tue, 15 Feb 2011 12:54:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lkdUrra2EeL5; Tue, 15 Feb 2011 12:53:59 -0800 (PST)
Received: from cs-211-36.cs.ucla.edu (Cs-211-36.CS.UCLA.EDU [131.179.211.36]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 7283B39E8083; Tue, 15 Feb 2011 12:53:59 -0800 (PST)
Subject: Re: MHonArc mail archive line wrapping
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>
Date: Tue, 15 Feb 2011 12:53:59 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7546F5DA-8920-4BB6-9B73-23D1628BBEAA@cs.ucla.edu>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>
To: Stuart Cheshire <cheshire@apple.com>
X-Mailer: Apple Mail (2.1082)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 20:53:35 -0000

good catch of the problem.=20
I suffered when I read IETF email on the web.
Would be great to see this fixed.

Lixia

On Feb 15, 2011, at 12:46 PM, Stuart Cheshire wrote:

> In the MHonArc mail archive there are often super-long lines, which =
would be wrapped to the window width when viewing in most mail clients, =
but when viewed in a web browser they appear as long single lines which =
take a lot of left-to-right scrolling to read them.
>=20
> For example: =
<http://www.ietf.org/mail-archive/web/renum/current/msg00060.html>
>=20
> This appears to be due to MHonArc's use of the PRE tag, which tells =
the web browser to display the literal text exactly as given, in a =
fixed-width font.
>=20
> The MHonArc FAQ suggests a couple of solutions to this problem:
>=20
>> Can long lines be wrapped in converted messages?
>=20
> <http://www.mhonarc.org/MHonArc/doc/faq/mime.html#lineclip>
>=20
>> Can the <PRE> tags be removed from converted messages?
>=20
> <http://www.mhonarc.org/MHonArc/doc/faq/mime.html#removepre>
>=20
> Can we consider using either of these options?
>=20
> Using "maxwidth=3Dxxx" would solve this problem, though of course it =
opens the debate about what's the right value for "xxx".
>=20
> Using "nonfixed" has the nice property of letting the web browser wrap =
the text to the window width, but might break ASCII-art diagrams. =
Perhaps that could be fixed by making the default font a fixed-width one =
(e.g. via style sheet) and using the "keepspace" option, which would =
give us monospaced text while still allowing the web browser to wrap the =
text to the current window width.
>=20
> Stuart Cheshire <cheshire@apple.com>
> * Wizard Without Portfolio, Apple Inc.
> * www.stuartcheshire.org
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rja.lists@gmail.com  Tue Feb 15 13:18:30 2011
Return-Path: <rja.lists@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A56A03A6CB9 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 13:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.96
X-Spam-Level: 
X-Spam-Status: No, score=-2.96 tagged_above=-999 required=5 tests=[AWL=-0.361,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3e4-kCXLwXAc for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 13:18:29 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by core3.amsl.com (Postfix) with ESMTP id 812A83A6C4E for <ietf@ietf.org>; Tue, 15 Feb 2011 13:18:29 -0800 (PST)
Received: by vxi40 with SMTP id 40so479226vxi.31 for <ietf@ietf.org>; Tue, 15 Feb 2011 13:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=mlF7k67IjmVZ7us/S7l2tYP6NaO7Whn23dRQsdLhjzU=; b=mib1RFpgQw0vJo9WB92HxyB9LFwJdahr7PFhne79+Fg2T66QNO/6dkuvFiCm+4LUWt a2u+a/iZ8UYlgiMuTg5PwrrvSiKKRhVFouj8wjk8JMTmLnbuaiitnzzY3qOmmItuc28h 3U0Bl/13zW5b+TFFe/mNSQ+vcyyyEocDq821A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=ZJvtnzua1Cj7atf3+u14P0jTIlt/sh/TW/XP+pEYLgPRbER04W+iT2BOrRJyqIuHXe p4mId0nbzJd2kJuYBR6NDDYe4kI9Z0AGaYCdNUzz/xC32xpRrnnBCaPAceomHIle6tBm kzXlDWS9qr9/XSm+IHCLnPYEZjapzx+sbueII=
Received: by 10.220.201.1 with SMTP id ey1mr1595246vcb.61.1297804735669; Tue, 15 Feb 2011 13:18:55 -0800 (PST)
Received: from [10.30.20.7] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id bq5sm1434478vcb.32.2011.02.15.13.18.54 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Feb 2011 13:18:54 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: MHonArc mail archive line wrapping
Date: Tue, 15 Feb 2011 16:18:53 -0500
Message-Id: <D14E788F-0F32-43B2-A52D-596FAA5B8A93@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 21:18:30 -0000

Earlier, Stuart Chesire wrote:
> In the MHonArc mail archive there are often super-long lines, which =
would be wrapped to the window width when viewing in most mail clients, =
but when viewed in a web browser they appear as long singlelines which =
take a lot of left-to-right scrolling to read them.
> For example: <http://www.ietf.org/mail-archive/web/renum/current/ =
msg00060.html>
> This appears to be due to MHonArc's use of the PRE tag, which tells =
the web browser to display the literal text exactly as given, in a =
fixed-width font.
> The MHonArc FAQ suggests a couple of solutions to this problem:
>=20
>=20
> Can long lines be wrapped in converted messages?
>=20
> <http://www.mhonarc.org/MHonArc/doc/faq/mime.html#lineclip
> >
>=20
>=20
> Can the <PRE> tags be removed from converted messages?
>=20
> <http://www.mhonarc.org/MHonArc/doc/faq/mime.html#removepre
> >
>=20
> Can we consider using either of these options?

Yes, please. =20

If either fix could be deployed for web archives of the sundry
mailing lists, both @ietf.org and @irtf.org, that would be VERY kind.

Thanks,

Ran



From derhoermi@gmx.net  Tue Feb 15 13:32:30 2011
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2CCF43A6C51 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 13:32:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.373
X-Spam-Level: 
X-Spam-Status: No, score=-2.373 tagged_above=-999 required=5 tests=[AWL=0.226,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-MEggF3Y0vM for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 13:32:26 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id DCE4D3A6AB9 for <ietf@ietf.org>; Tue, 15 Feb 2011 13:32:25 -0800 (PST)
Received: (qmail invoked by alias); 15 Feb 2011 21:32:50 -0000
Received: from dslb-094-223-179-002.pools.arcor-ip.net (EHLO HIVE) [94.223.179.2] by mail.gmx.net (mp058) with SMTP; 15 Feb 2011 22:32:50 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19IozlrSQZIz9W/kPNTJmGyReaZuWoJaKuC75DOfj hPu+fDCfTWwP8K
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stuart Cheshire <cheshire@apple.com>
Subject: Re: MHonArc mail archive line wrapping
Date: Tue, 15 Feb 2011 22:32:50 +0100
Message-ID: <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>
In-Reply-To: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 21:32:30 -0000

* Stuart Cheshire wrote:
>In the MHonArc mail archive there are often super-long lines, which  
>would be wrapped to the window width when viewing in most mail  
>clients, but when viewed in a web browser they appear as long single  
>lines which take a lot of left-to-right scrolling to read them.

That is the result of some clients and users violating netiquette and
mail standards, for instance, RFC 1855, section 2.1.1:

  - Limit line length to fewer than 65 characters and end a line
    with a carriage return. 

and RFC 2822 (and similarily RFC 5322), section 2.1.1:

  There are two limits that this standard places on the number of
  characters in a line. Each line of characters MUST be no more than
  998 characters, and SHOULD be no more than 78 characters, excluding
  the CRLF. 

And this does not cause problems just with unwrapped lines, it also has
other effects, like people quoting excessively long lines on one line
but then write their own text properly wrapped (that's appropriate be-
havior if long lines are rare and most likely intentional, such as when
including some computer code you don't want wrapped at odd positions.)

I note that one of the main culprits here are Apple Mail users, although
you seem to be using it yet have managed to send properly wrapped lines.
If there is something Apple Mail users can do to stop their netiquette
and standards violations, I would apprciate any pointer you may have.

Obviously the solution is to have those using broken or misconfigured
clients use clients that are not broken or configure them correctly.

As for the list archives, you can make the lines wrap by changing the
style sheet (or use an appropriate user style sheet), for instance,

  pre { white-space: pre-wrap; }

should probably do it in modern clients (for older clients there is
option to use proprietary extensions in some browsers, but that may
not be necessary these days.) This would seem preferable over forcing
line wraps in the archival software as that would break lines that are
meant to be long for very good reasons.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From petithug@acm.org  Tue Feb 15 15:22:10 2011
Return-Path: <petithug@acm.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E56B3A6C4E for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 15:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.705
X-Spam-Level: 
X-Spam-Status: No, score=-101.705 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_46=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sLmCUrix-OH4 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 15:22:09 -0800 (PST)
Received: from server.implementers.org (server.implementers.org [69.55.225.91]) by core3.amsl.com (Postfix) with ESMTP id 9B27B3A6C31 for <ietf@ietf.org>; Tue, 15 Feb 2011 15:22:09 -0800 (PST)
Received: by server.implementers.org (Postfix, from userid 1001) id 51F65EBC4024; Tue, 15 Feb 2011 23:22:35 +0000 (UTC)
Received: from [192.168.2.3] (server.implementers.org [127.0.0.1]) by server.implementers.org (Postfix) with ESMTPA id 4A8BEEBC4024; Tue, 15 Feb 2011 23:22:33 +0000 (UTC)
Message-ID: <4D5B0AB8.90509@acm.org>
Date: Tue, 15 Feb 2011 15:22:32 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101226 Iceowl/1.0b1 Icedove/3.0.11
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: MHonArc mail archive line wrapping
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com> <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
In-Reply-To: <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Stuart Cheshire <cheshire@apple.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Feb 2011 23:22:10 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/15/2011 01:32 PM, Bjoern Hoehrmann wrote:
> * Stuart Cheshire wrote:
>> In the MHonArc mail archive there are often super-long lines, which  
>> would be wrapped to the window width when viewing in most mail  
>> clients, but when viewed in a web browser they appear as long single  
>> lines which take a lot of left-to-right scrolling to read them.
> 
> That is the result of some clients and users violating netiquette and
> mail standards, for instance, RFC 1855, section 2.1.1:
> 
>   - Limit line length to fewer than 65 characters and end a line
>     with a carriage return. 
> 
> and RFC 2822 (and similarily RFC 5322), section 2.1.1:
> 
>   There are two limits that this standard places on the number of
>   characters in a line. Each line of characters MUST be no more than
>   998 characters, and SHOULD be no more than 78 characters, excluding
>   the CRLF. 
> 
> And this does not cause problems just with unwrapped lines, it also has
> other effects, like people quoting excessively long lines on one line
> but then write their own text properly wrapped (that's appropriate be-
> havior if long lines are rare and most likely intentional, such as when
> including some computer code you don't want wrapped at odd positions.)
> 
> I note that one of the main culprits here are Apple Mail users, although
> you seem to be using it yet have managed to send properly wrapped lines.
> If there is something Apple Mail users can do to stop their netiquette
> and standards violations, I would apprciate any pointer you may have.
> 
> Obviously the solution is to have those using broken or misconfigured
> clients use clients that are not broken or configure them correctly.
> 
> As for the list archives, you can make the lines wrap by changing the
> style sheet (or use an appropriate user style sheet), for instance,
> 
>   pre { white-space: pre-wrap; }
> 
> should probably do it in modern clients (for older clients there is
> option to use proprietary extensions in some browsers, but that may
> not be necessary these days.) This would seem preferable over forcing
> line wraps in the archival software as that would break lines that are
> meant to be long for very good reasons.

And for people who do no want to wait for Central Services to fix the problem,
here's a Greasemonkey script:

// ==UserScript==
// @name           Fix wrap
// @namespace      http://shalmaneser.org/fix-wrap
// @include        http://www.ietf.org/mail-archive/*
// ==/UserScript==
var pres = document.getElementsByTagName('pre');
for (var i = pres.length - 1; i >= 0; i--) {
	pres[i].style.whiteSpace = 'pre-wrap';
}

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk1bCrYACgkQ9RoMZyVa61eERgCgotrFrcN+qQsWLNSD7VNt7p6u
ggUAoI690tgUNDdGX+zur2d8W0xJhk3E
=AGIZ
-----END PGP SIGNATURE-----

From fluffy@cisco.com  Tue Feb 15 19:32:00 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D9E43A6C7E; Tue, 15 Feb 2011 19:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.447
X-Spam-Level: 
X-Spam-Status: No, score=-109.447 tagged_above=-999 required=5 tests=[AWL=-1.002, BAYES_00=-2.599, FRT_BELOW2=2.154, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iPI2-vPAyh8S; Tue, 15 Feb 2011 19:31:59 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 065F43A6CAB; Tue, 15 Feb 2011 19:31:59 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMzTWk2rR7Hu/2dsb2JhbAClYnOhY5toAoVcBIUGhwCDNg
X-IronPort-AV: E=Sophos;i="4.60,478,1291593600"; d="scan'208";a="264195625"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2011 03:32:26 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p1G3WO4o005430; Wed, 16 Feb 2011 03:32:25 GMT
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet	Assigned Numbers Authority (IANA) Procedures for the Management	of the Service Name and Transport Protocol Port Number	Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D4920F0.1070204@ericsson.com>
Date: Tue, 15 Feb 2011 20:34:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com> <4D4920F0.1070204@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, IESG IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: IETF discussion list <ietf@ietf.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 03:32:00 -0000

I propose some text for the draft near the bottom of this email....

On Feb 2, 2011, at 2:16 AM, Magnus Westerlund wrote:

> Cullen Jennings skrev 2011-02-01 18:19:
>>=20
>> So to summarize what you are saying, ports are allocated based on an =
arbitrary view of the expert review. When this person will say yes or no =
too can't be described and will change over time.=20
>>=20
>> If that's how it works, there is not even any grounds for appeal of =
any given decision. You can't even use precedence as an argument. My =
view was the IESG has been trying to move to having much more concrete =
advice for registries that required expert review. If you agree that is =
about the right summary, then I'm pretty sure I can find plenty of other =
people that would agree with me that this is not OK. I'm not a fan of =
the WG could not get consensus on if we should allow A or not so we are =
just going to let the expert review do whatever they want. If the IETF =
could not come to consensus on if X  or Y were reasons to deny a =
registration, then I don't think the expert review should be able to =
deny a registration due to X or Y.=20
>=20
> Cullen,
>=20
> Apparently you like to twist what I am saying in most negative way and
> without considering the checks that are in place.

Sorry Magnus ... I really did not mean to twist your words. I know you =
are very straight up about this type of stuff. I suggested some text =
bellow.=20

>=20
> - I think general guidelines can and should be developed. But other =
than
> high level goals this isn't the document. Here Joe has the start of a
> document. But I do think that in long term this guidance may change.
>=20
> - There is an appeal process where the IESG and then IAB gets to =
sanity
> check the arguments that the reviewer + IANA has given towards the
> appealing requestor.

I understand that but we both know appeals are a painful tool to use and =
we would like to avoid it where possible - they waste an incredible =
amount of time for everyone involved and particularly the IESG.=20

>=20
> - One can take a assignment request through the IETF process

I'm not as focused on drafts in IETF process but even in theses cases, =
WGs will look to this BCP for guidance on what would be acceptable =
behavior. So even if this draft might not "legally" block a WG from =
doing something, the WG will still be influenced by the goals this draft =
"strives" for. That is a good thing - BCP advice that applies to non =
IETF work should guide IETF process work too.=20


>=20
> I hope that we can get consensus on the guidelines, because I think =
that
> would give the reviewers a lot of comfort being able to rely on that
> consensus.
>=20
> Cullen, what are your suggestion for how to improve the document?

For the user ports the document should have some text along the lines =
of:

There is not IETF consensus on when it is appropriate to use a second =
port for a secure version of protocol therefor the export reviewer =
should not reject a request for a second port to run a secure variant of =
the protocol over.=20

The reason I think this needs to be in the draft is very simple. In my =
mind there are clear and compelling cases for two ports - many of them =
involving DTLS and real time protocols that actually care about number =
of round trips. Joe Touch has already said he would reject an example =
use case that I think should be accepted. I think this is much easier to =
resolve this issue now than with an appeal.=20

The CORE WG, which I co-chair, needs clear advice now on what direction =
would be acceptable and is not particular interested in waiting for a =
year or two for the drafts to be done, appealed, and then redesigned.=20

>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------


From paul.hoffman@vpnc.org  Tue Feb 15 19:58:59 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1DDF3A6B8E; Tue, 15 Feb 2011 19:58:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.316
X-Spam-Level: 
X-Spam-Status: No, score=-100.316 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_20=-0.74, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1b13ffshfUA5; Tue, 15 Feb 2011 19:58:58 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 425963A6B77; Tue, 15 Feb 2011 19:58:58 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1G3xK66028915 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Feb 2011 20:59:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D5B4B98.4060704@vpnc.org>
Date: Tue, 15 Feb 2011 19:59:20 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers Authority (IANA) Procedures for the	Management	of the Service Name and Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com>	<755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>	<4D4920F0.1070204@ericsson.com> <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>
In-Reply-To: <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg@ietf.org, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 03:58:59 -0000

On 2/15/11 7:34 PM, Cullen Jennings wrote:
> I propose some text for the draft near the bottom of this email....
> For the user ports the document should have some text along the lines
> of:
>
> There is not IETF consensus on when it is appropriate to use a second
> port for a secure version of protocol therefor the export reviewer
> should not reject a request for a second port to run a secure variant
> of the protocol over.

That feels close, but too prescriptive. Also, the requests are usually 
for a protocol with two ports, not a later request for a second port. 
How about:

There is not IETF consensus on when it is appropriate to use a second 
port for a secure version of protocol. Therefore, an expert reviewer 
should not reject a proposal for a protocol that uses a second part to 
run a secure variant for the sole reason that it using two ports.

From fluffy@cisco.com  Tue Feb 15 19:59:52 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7918A3A6CAB; Tue, 15 Feb 2011 19:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.19
X-Spam-Level: 
X-Spam-Status: No, score=-110.19 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABHJb3GhKt86; Tue, 15 Feb 2011 19:59:51 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A8DEC3A6B77; Tue, 15 Feb 2011 19:59:51 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMraWk2rR7Ht/2dsb2JhbAClYnOhWJtkhV4EhQaHAIM2
X-IronPort-AV: E=Sophos;i="4.60,478,1291593600"; d="scan'208";a="260669802"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 16 Feb 2011 04:00:18 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1G40G0G018511; Wed, 16 Feb 2011 04:00:17 GMT
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers Authority (IANA) Procedures for the	Management	of the Service Name and Transport Protocol Port	Number	Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D5B4B98.4060704@vpnc.org>
Date: Tue, 15 Feb 2011 21:02:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com>	<755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>	<4D4920F0.1070204@ericsson.com> <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com> <4D5B4B98.4060704@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1082)
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, tsvwg@ietf.org, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 03:59:52 -0000

Paul's text is much better than mine. That was what I trying to get at.=20=


On Feb 15, 2011, at 8:59 PM, Paul Hoffman wrote:

> On 2/15/11 7:34 PM, Cullen Jennings wrote:
>> I propose some text for the draft near the bottom of this email....
>> For the user ports the document should have some text along the lines
>> of:
>>=20
>> There is not IETF consensus on when it is appropriate to use a second
>> port for a secure version of protocol therefor the export reviewer
>> should not reject a request for a second port to run a secure variant
>> of the protocol over.
>=20
> That feels close, but too prescriptive. Also, the requests are usually =
for a protocol with two ports, not a later request for a second port. =
How about:
>=20
> There is not IETF consensus on when it is appropriate to use a second =
port for a secure version of protocol. Therefore, an expert reviewer =
should not reject a proposal for a protocol that uses a second part to =
run a secure variant for the sole reason that it using two ports.


From stpeter@stpeter.im  Tue Feb 15 20:07:10 2011
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B4543A6CD1; Tue, 15 Feb 2011 20:07:10 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJhvobNzJ75K; Tue, 15 Feb 2011 20:07:09 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id CABAF3A6CB6; Tue, 15 Feb 2011 20:07:09 -0800 (PST)
Received: from squire.local (dsl-251-175.dynamic-dsl.frii.net [216.17.251.175]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 27707400F6; Tue, 15 Feb 2011 21:25:40 -0700 (MST)
Message-ID: <4D5B4D86.3020102@stpeter.im>
Date: Tue, 15 Feb 2011 21:07:34 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call:	<draft-ietf-tsvwg-iana-ports-09.txt>	(Internet	Assigned Numbers	Authority (IANA) Procedures for the	Management	of the Service	Name and Transport Protocol Port	Number	Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost>	<B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<4D413827.7040407@ericsson.com>	<B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>	<4D46B3B9.4050804@ericsson.com>	<755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com>	<4D4920F0.1070204@ericsson.com>	<49CDF352-D900-4883-8D67-19172DBC8474@cisco.com>	<4D5B4B98.4060704@vpnc.org> <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>
In-Reply-To: <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090609060805040009070606"
Cc: IESG IESG <iesg@ietf.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 04:07:10 -0000

This is a cryptographically signed message in MIME format.

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

Agreed, thanks to Paul for the proposed text.

On 2/15/11 9:02 PM, Cullen Jennings wrote:
>=20
> Paul's text is much better than mine. That was what I trying to get
> at.
>=20
> On Feb 15, 2011, at 8:59 PM, Paul Hoffman wrote:
>=20
>> On 2/15/11 7:34 PM, Cullen Jennings wrote:
>>> I propose some text for the draft near the bottom of this
>>> email.... For the user ports the document should have some text
>>> along the lines of:
>>>=20
>>> There is not IETF consensus on when it is appropriate to use a
>>> second port for a secure version of protocol therefor the export
>>> reviewer should not reject a request for a second port to run a
>>> secure variant of the protocol over.
>>=20
>> That feels close, but too prescriptive. Also, the requests are
>> usually for a protocol with two ports, not a later request for a
>> second port. How about:
>>=20
>> There is not IETF consensus on when it is appropriate to use a
>> second port for a secure version of protocol. Therefore, an expert
>> reviewer should not reject a proposal for a protocol that uses a
>> second part to run a secure variant for the sole reason that it
>> using two ports.


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIITzjCC
BjQwggQcoAMCAQICASMwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDMzM1oXDTE3MTAyNDIxMDMzM1owgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALmjSW4SPiDKlAinvVeL
ZOVfItiuP1aRHL530E7QUc9icCwL33+PH+Js1HAh8CgWFl34sOxx1FJyS/C4VLPRsqDfP72j
tzCVUAL0DAxZ7wgzQvFz7x61jGxfhYhqYb1+PPOLkYBbkRIrPMg3dLEdKmXIYJYXDH+mB/V/
jLo73/Kb7h/rNoNg/oHHSv5Jolyvp5IY2btfcTBfW/telEFj5rDTX2juTvZ3Qhf3XQX5ca3Q
7A10zrUV/cWJOJ7F5RltbEIaboZmX5JBUb3FhUiAdBotehAX6DbDOuYoJtVxmGof6GuVGcPo
98K4TJf8FHo+UA9EOVDp/W7fCqKT4sXk/XkCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBR7iZySlyShhEcCy3T8LvSs3DLl8zAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQELBQADggIBAGpd
SbdLFMhirxK37V4gE00+uW74UdAXtDgQI3AsRZWtaRtKHgAxFBSteqz4kDkeAjH/1b+K8tQR
6cxSI2nho7qOaPW/UpzOfSS/MeKK/9vfM2lfs+uItXH7LWtvS9wD1erfH1a+BXHCrCp4LA1l
fADDhRIiGTSS3i0Zu5xV3INNRHrCCCl6patltQ8RZTqzDMri7ombgIxjN51Zo7xV77EZcThV
0GA8iIN+7T53uHhUJpjfLIztHs/69OclRvHux9hCflfOm7GY5Sc4nqjfES+5XPArGGWiQSEk
ez37QfXqsxO3oCHK4b3DFZysG4uyOuC/WL80ab3muQ3tgwjBhq0D3JZN5kvu5gSuNZPa1WrV
hEgXkd6C7s5stqB6/htVpshG08jRz9DEutGM9oKQ1ncTivbfPNx7pILoHWvvT7N5i/puVoNu
bPUmLXh/2wA6wzAzuuoONiIL14Xpw6jLSnqpaLWElo2yTIFZ/CU/nCvvpW1Dj1457P3Ci9bD
0RPkWSR+CuucpgxrEmaw4UOLxflzuYYaq1RJwygOO5K0s2bAWOcXpgteyUOnQ3d/EjJAWRri
2v0ubiq+4H3KUOMlbznlPAY/1T8YyyJPM88+Ueahe/AW1zoUwZayNcTnuM7cq6yBV8Wr3GOI
LFXhtT0UVuJLChPMJKVKVsa7qNorlLkMMIIGxzCCBa+gAwIBAgICAIswDQYJKoZIhvcNAQEF
BQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJT
ZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBD
bGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTAeFw0xMDEwMTQwMTM2MzRa
Fw0xMjEwMTQxMjAxMDdaMIHAMSAwHgYDVQQNExcyNzQ1ODEtOU5YMDRxeExEYjBvNDY5VDEL
MAkGA1UEBhMCVVMxETAPBgNVBAgTCENvbG9yYWRvMQ8wDQYDVQQHEwZEZW52ZXIxLDAqBgNV
BAsTI1N0YXJ0Q29tIFRydXN0ZWQgQ2VydGlmaWNhdGUgTWVtYmVyMRowGAYDVQQDExFQZXRl
ciBTYWludC1BbmRyZTEhMB8GCSqGSIb3DQEJARYSc3RwZXRlckBzdHBldGVyLmltMIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuERvnrkpQTx9wbJfgxbNKEYvt0IilecZRUM6
wrbCzIUPCocuYhaAJcQoqIyHaKybPQ7f+DIGIAolAa3dHnNdlsXP2smTft/ZNpj10PIG5bil
NAqLUYwmLJaEaqY7BMW8423U3blW43/luLJk/Pq4OsWcw7AK3LeVh1U/HOgqhin26N3h72X1
nbLEpZFrgcp8egmWtXLCbLBDMqUK3j6wjLldni79muzYEVqU0A5GqSeb8Wc4kIx8VI5yL24J
KzinG2iVRP5ZDEbOZETzBXJabUsV56XSxqPG9DK6ke+ybCiL/wKV1HFqdtFB1y25lfvHgOP2
gyEApBKEDNjgLmKyyQIDAQABo4IC+zCCAvcwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBS2EW2iNB+g0EibKJLBdv8I
eLovVDAfBgNVHSMEGDAWgBR7iZySlyShhEcCy3T8LvSs3DLl8zAdBgNVHREEFjAUgRJzdHBl
dGVyQHN0cGV0ZXIuaW0wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQICMIIBIDAu
BggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEF
BQcCARYoaHR0cDovL3d3dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYB
BQUHAgIwgaowFBYNU3RhcnRDb20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNl
ZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNz
bC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3Ns
LmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1
My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2NzcC5z
dGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNVHRIE
HDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBADVtbXJG
tKAr55xc/OUM546gXUybI72Bank0w739Mv+9BBNtq9rMEvCnLmSKhBi76c1mdXh6zXs8RQDo
6nR/aPabE3llF2T4z80smi9jfnl3y9dpu9TcgDoqDLZ7a2lBlW656XAAQzHjvLp2MC7/mxlg
PYH2axa+q40mAYM20GbNsAEGbWQT1IqIh0BcLLsgbaMJHbyG/57zd9JLyMX3Vry1L1fJRQr3
GeLxMV5RtxN+mBgxrwFz/cOc09COiFExlsHgekpB5O43gqsAU16MXypyoSt4MrSfKTMHIGx6
2RF/M6vqUlvhi28gk2ZUvQ/+OX5+gjcZyooEzAAn4RuOKNswggbHMIIFr6ADAgECAgIAizAN
BgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4x
KzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBMB4XDTEw
MTAxNDAxMzYzNFoXDTEyMTAxNDEyMDEwN1owgcAxIDAeBgNVBA0TFzI3NDU4MS05TlgwNHF4
TERiMG80NjlUMQswCQYDVQQGEwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRl
bnZlcjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0aWZpY2F0ZSBNZW1iZXIxGjAY
BgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcNAQkBFhJzdHBldGVyQHN0cGV0
ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4RG+euSlBPH3Bsl+DFs0o
Ri+3QiKV5xlFQzrCtsLMhQ8Khy5iFoAlxCiojIdorJs9Dt/4MgYgCiUBrd0ec12Wxc/ayZN+
39k2mPXQ8gbluKU0CotRjCYsloRqpjsExbzjbdTduVbjf+W4smT8+rg6xZzDsArct5WHVT8c
6CqGKfbo3eHvZfWdssSlkWuBynx6CZa1csJssEMypQrePrCMuV2eLv2a7NgRWpTQDkapJ5vx
ZziQjHxUjnIvbgkrOKcbaJVE/lkMRs5kRPMFclptSxXnpdLGo8b0MrqR77JsKIv/ApXUcWp2
0UHXLbmV+8eA4/aDIQCkEoQM2OAuYrLJAgMBAAGjggL7MIIC9zAJBgNVHRMEAjAAMAsGA1Ud
DwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFLYRbaI0
H6DQSJsoksF2/wh4ui9UMB8GA1UdIwQYMBaAFHuJnJKXJKGERwLLdPwu9KzcMuXzMB0GA1Ud
EQQWMBSBEnN0cGV0ZXJAc3RwZXRlci5pbTCCAUIGA1UdIASCATkwggE1MIIBMQYLKwYBBAGB
tTcBAgIwggEgMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3ku
cGRmMDQGCCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUu
cGRmMIG3BggrBgEFBQcCAjCBqjAUFg1TdGFydENvbSBMdGQuMAMCAQEagZFMaW1pdGVkIExp
YWJpbGl0eSwgc2VlIHNlY3Rpb24gKkxlZ2FsIExpbWl0YXRpb25zKiBvZiB0aGUgU3RhcnRD
b20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgUG9saWN5IGF2YWlsYWJsZSBhdCBodHRwOi8v
d3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMGMGA1UdHwRcMFowK6ApoCeGJWh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2NydHUzLWNybC5jcmwwK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUzLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MzL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL3d3dy5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMy5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEANW1tcka0oCvnnFz85QznjqBdTJsjvYFqeTTDvf0y/70EE22r2swS8KcuZIqEGLvp
zWZ1eHrNezxFAOjqdH9o9psTeWUXZPjPzSyaL2N+eXfL12m71NyAOioMtntraUGVbrnpcABD
MeO8unYwLv+bGWA9gfZrFr6rjSYBgzbQZs2wAQZtZBPUioiHQFwsuyBtowkdvIb/nvN30kvI
xfdWvLUvV8lFCvcZ4vExXlG3E36YGDGvAXP9w5zT0I6IUTGWweB6SkHk7jeCqwBTXoxfKnKh
K3gytJ8pMwcgbHrZEX8zq+pSW+GLbyCTZlS9D/45fn6CNxnKigTMACfhG44o2zGCA80wggPJ
AgEBMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMAkGBSsOAwIa
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDIx
NjA0MDczNFowIwYJKoZIhvcNAQkEMRYEFFc6EOxT89Pc6PJRhHl9UhQdSK6gMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQAOSx3bgfp+PX+yFrLcOgO5rTLFrT8FsG0qJuwTFP2Iv78YIYa3AfwrwRG4
U8VtBg9hZStPAJa9szjL9Z3tGm5FOczm39uTt3uvrXQUJdNnCJXx1GiZAnp1X9VksY7E2KGU
TQv+QTRuqj9t8QvxyDRcrOr2qALYeZHh84zNtCU+ktX4KfO1bo3eR+3EPiiNberWvDu+GPXr
HlM24FtFkgz2EsSqIs1ri+mUpbUjPhGPPuj6a9k/yAUAXREANKJlxO+k6OAUt1xTEGO2D7mA
OokLjKUUj+S2qqcHjXVoE7vAjptAMBWUrWNbZw7s3OOp6nKD8GRx2nB3c7+esTkkoAFpAAAA
AAAA
--------------ms090609060805040009070606--

From fluffy@cisco.com  Tue Feb 15 20:28:41 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 186133A6D23; Tue, 15 Feb 2011 20:28:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.562
X-Spam-Level: 
X-Spam-Status: No, score=-110.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NBjJtMER4W2J; Tue, 15 Feb 2011 20:28:39 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id E5E023A6A7B; Tue, 15 Feb 2011 20:28:39 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANLhWk2rRDoJ/2dsb2JhbAClYnOhdZtfhV4EhQaHAIM2
X-IronPort-AV: E=Sophos;i="4.60,478,1291593600"; d="scan'208";a="264218515"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2011 04:29:07 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p1G4T5Ic023583; Wed, 16 Feb 2011 04:29:05 GMT
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> now draft-ietf-tsvwg-iana-ports-10.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20110212011501.19200.14616.idtracker@localhost>
Date: Tue, 15 Feb 2011 21:31:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A909D9B-AEC3-4EB9-A1D1-EB28706CF874@cisco.com>
References: <20110212011501.19200.14616.idtracker@localhost>
To: IESG IESG <iesg@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: Apple Mail (2.1082)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 04:28:41 -0000

It seems like the text in version 10 are changes that would need a LC to =
decide if they had consensus.=20

Consider the change to add the text=20

   Because the port number space is finite (and
   therefore conservation is an important goal) the alternative of using
   service names instead of port numbers is RECOMMENDED whenever
   possible.

I think at least one member of the expert review teams believes that it =
is possible to use SRV for most protocols so does this mean that ports =
will not be assigned for most protocols? Take SIP or XMPP for example, =
they both use SRV - would they get a port? If we were doing a new =
protocol like HTTP that did not define a SRV record but could be =
designed to have one, would the expert reviews approve a port or not? I =
think all these topics need significant discussion before the a LC of =
text like this. Anyone want to elaborate on how "whenever possible" =
would be decided?

I find the the following text a bit outrageous.

   Applicants
   should be aware that IANA decisions are not required to be bound to
   these principles.  These principles and general advice to users on
   port use are expected to change over time and are therefore
   documented separately, please see [I-D.touch-tsvwg-port-use].

The basic complaints about this draft can mostly be summarized as a view =
that everything that the authors of this draft could not get agreement =
on in the WG, they just made the draft silent on and Joe is asserting =
that the expert reviews can do whatever they think was best regardless =
of any IETF consensus and then people can appeal it. So this text would =
have this BCP assert that the place to find out what was OK and not OK =
was in documented in an individual draft written by Joe. This is not OK. =
Consider if I asked that instead, it pointed at I-D.fluffy-port-use. I'm =
sure many people would think that was totally unacceptable. I don't see =
how this is any more acceptable. It  seems like an inappropriate change =
to make without a new LC. I don't think that it is OK for a BCP on how =
to register ports to point people at a spec without consensus approval =
that says what is OK to register and what is not.=20

I am confused by=20
=20
   use of the "Expert Review" helps advise IANA informally in
   cases where "IETF Review" or "IESG Review" is used, as with most IETF
   protocols.

I read this to mean that IANA would also ask for expert review on =
allocations made in IESG reviewed drafts? This seemed to be the opposite =
of what was discussed on list.=20

The draft removed the "and so strives to avoid separate assignments for =
non-secure variants" out of=20
  "IANA strives to encourage the deployment of secure protocols, and so =
strives to avoid separate assignments for non-secure variants"

I suspect this was done to try and address my main complaint but I don't =
see how it helps.=20





On Feb 11, 2011, at 6:15 PM, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the Transport Area Working Group Working =
Group of the IETF.
>=20
>=20
> 	Title           : Internet Assigned Numbers Authority (IANA) =
Procedures for the Management of the Service Name and Transport Protocol =
Port Number Registry
> 	Author(s)       : M. Cotton, et al.
> 	Filename        : draft-ietf-tsvwg-iana-ports-10.txt
> 	Pages           : 32
> 	Date            : 2011-02-11
>=20
> This document defines the procedures that the Internet Assigned
> Numbers Authority (IANA) uses when handling assignment and other
> requests related to the Service Name and Transport Protocol Port
> Number Registry.  It also discusses the rationale and principles
> behind these procedures and how they facilitate the long-term
> sustainability of the registry.
>=20
> This document updates IANA's procedures by obsoleting the previous
> UDP and TCP port assignment procedures defined in Sections 8 and 9.1
> of the IANA allocation guidelines [RFC2780], and it updates the IANA
> Service Name and Port assignment procedures for UDP-Lite [RFC3828],
> DCCP [RFC4340] [RFC5595] and SCTP [RFC4960].  It also updates the DNS
> SRV specification [RFC2782] to clarify what a service name is and how
> it is registered.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-iana-ports-10.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Mail Attachment>_______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From fluffy@cisco.com  Tue Feb 15 20:28:50 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3BD63A6D45; Tue, 15 Feb 2011 20:28:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.946
X-Spam-Level: 
X-Spam-Status: No, score=-109.946 tagged_above=-999 required=5 tests=[AWL=-0.587, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jj2WOVE58oCY; Tue, 15 Feb 2011 20:28:49 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id D039C3A6CDA; Tue, 15 Feb 2011 20:28:49 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANLhWk2rRDoJ/2dsb2JhbAClYnOhdZtfgn6CYASFBocAgzY
X-IronPort-AV: E=Sophos;i="4.60,478,1291593600"; d="scan'208";a="264218599"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by sj-iport-3.cisco.com with ESMTP; 16 Feb 2011 04:29:17 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p1G4T5Id023583; Wed, 16 Feb 2011 04:29:15 GMT
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned	Numbers Authority (IANA) Procedures for the Management of the Service	Name and Transport Protocol Port Number Registry) to BCP
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 15 Feb 2011 21:31:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2803F25F-A2BE-46E3-8284-A256A9B9D415@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <Pine.LNX.4.64.1102071321290.4671@adax.adax> <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1082)
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, Chris Benson <cbenson@adax.com>, IESG IESG <iesg@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 04:28:50 -0000

I've been thinking more about this thread and my concerns about this =
draft. I was originally looking for the draft to have advice for the =
expert review team that gave them guidance on what the IETF thought was =
all right to approve or not approve. It's become clear that this draft =
does not have that advice and is not likely to get it in the very short =
term. This BCP will empower the expert reviewer to reject or approve =
just about any request. Appeals are not the best way to balance putting =
that power because they are incredibly corrosive and time consuming to =
everyone involved. I think this thread somewhat suggests an alternative =
approach for a check and balance.=20

What do people think of the idea of: for all ports requests, the request =
and the expert reviewer reposes including reason for accepting or =
rejecting them need to be posted to a public email list. This seems like =
a simple way to help mitigate this issue and it will help educate people =
writing a port request to know what types of issues they need to address =
and what would be appropriate or not.=20

Pros & cons of this idea?


On Feb 8, 2011, at 1:41 PM, Christian Huitema wrote:

>> I don't see that "public identity" (of expert reviewers) is required =
for "interactive discussion". =20
>> Or would anonymous interaction fail a Turing test of some kind?
>=20
> Public identity is required for reviewer accountability. It is easy to =
imagine how withholding registration of some required numbers may delay =
a competitor's products. The best protection against shade is sunlight.
>=20
> -- Christian Huitema
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From mohta@necom830.hpcl.titech.ac.jp  Tue Feb 15 23:42:15 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CA873A6D23 for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 23:42:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.146
X-Spam-Level: 
X-Spam-Status: No, score=-0.146 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mNno0cJy2rYI for <ietf@core3.amsl.com>; Tue, 15 Feb 2011 23:42:14 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 71B8D3A6DB3 for <ietf@ietf.org>; Tue, 15 Feb 2011 23:42:13 -0800 (PST)
Received: (qmail 35528 invoked from network); 16 Feb 2011 07:52:26 -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 2011 07:52:26 -0000
Message-ID: <4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2011 16:41:33 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
References: <20110118150445.13842.1912.idtracker@localhost> <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com>
In-Reply-To: <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 07:42:15 -0000

Richard L. Barnes wrote:

> However, there are several emerging systems that provide much
> more than these generic databases.  Typically, these systems
> tap into network management infrastructure to map an IP
> address to the physical resource to which it is assigned,
> using things like RADIUS databases and DHCP lease tables.

As you are assuming physical identity of DHCP clients are known
reliably (I don't know how it can be done), it is a lot easier
for DHCP servers to assign static IP addresses to the clients
based on the physical identity information than assigning random
addresses and map them later through complicated database look up.

> This is an important use case, for example, for ECRIT
> emergency services [draft-ietf-ecrit-framework]

Is it a use case in the real world?

> IP addresses are also used as input to higher-fidelity
> geolocation services that resolve an IP address to
> a physical location using information from the network
> infrastructure.

AFAIK, IP addresses can not be used for high fidelity geo-location,
though some copyright-wraiths are hoping so.

						Masataka Ohta

From lars.eggert@nokia.com  Wed Feb 16 01:13:20 2011
Return-Path: <lars.eggert@nokia.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 964293A6DFD for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 01:13:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GW54ysuZi+fU for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 01:13:19 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 9E2A03A6DF7 for <ietf@ietf.org>; Wed, 16 Feb 2011 01:13:19 -0800 (PST)
Received: from mail.fit.nokia.com (esdhcp030222.research.nokia.com [172.21.30.222]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p1G9Diar021524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Feb 2011 11:13:46 +0200
Subject: Re: World IPv6 Day and Us
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.96.5 at fit.nokia.com
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-30--434646293; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
Date: Wed, 16 Feb 2011 11:13:37 +0200
Message-Id: <9ED59100-59BD-44B9-8319-FC66DD86D020@nokia.com>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com>
To: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Wed, 16 Feb 2011 11:13:42 +0200 (EET)
X-Nokia-AV: Clean
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 09:13:20 -0000

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

On 2011-2-15, at 19:45, Sabahattin Gucukoglu wrote:
> Noting the increasing length of the list =
athttp://isoc.org/wp/worldipv6day/participants/

...I mostly note that I see very few eyeball ISPs on that list (with the =
notable exception of two large US cable ISPs - great, guys!)

Turning on IPv6 on the content provider side is great and all, but =
without the eyeballs on IPv6, I wonder a bit about the point of this =
exercise.

Lars=

--Apple-Mail-30--434646293
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMRjCCBVAw
ggQ4oAMCAQICEGxdPUZzCwUJ8KBiJwH+bYgwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMDEwMTUwMDAwMDBaFw0x
MTEwMTUyMzU5NTlaMIIBEzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9r
aWEuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwolKEyOz/NQZJJlw0x9XBS9W
wCmabdY1fXpbWSdcaJiEWhQpRzSIC/pgIwCgaUW9g3JsWioXCawyjUVeg8xR42sR690f4z+OPAUm
3jokZxsuRaGX6fuPkPQomYAGz7htUHws/8FZIU+4dciETQf4vF5ptitJ+QZCVRCTLqisj6mG/kG4
65Op3G5/YZF9F/a390LdhuRP6vdY2Y+dqm8LDa0zmENPpoE98u1pIZGqCcnskN/nNBtEPd+a4lNh
ZSGnPuL4XCUSJYR9NB7FAYBvi5N7LSWHR3fspwa5EgpXynJcsLzaLA0iGfjFOBYFxul/07edmyw4
FIXuCIkaMDUfEwIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcX
ATAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIF
oDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDov
L2luZGMxZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3Js
MA0GCSqGSIb3DQEBBQUAA4IBAQAlSTzUKqa3ZouKWFQfIJ+4l/KsztPnY4Onwzt8lqAmeiFPqOmf
kLTXbXDKtC6caFadNtyHpnsmQFFKXwhe5Z9/AaVSwryu6F9992DzYLp3j8PE0DSU0wmpUXUtp+rz
TFqJRkzB8RCBoq/TPBmkMPr68qB0TkU3dbYiVIvscOt1MRkdHiwG4wKQLyCf8XRRWqmMY6lbun7g
kiEWiris5StGKRvE5+e1SrcdnoZxIKQFF7Etr+4ftClrsDQWX9nRCEjYcmz4y/deq+HU8ylBaKZE
0ZJmcnYlAaD50OYWi0ckGDnKYyeMUEtCZJSV0otm2LqyIUAu9WPv/GNHt2ntjnUaMIIG7jCCBdag
AwIBAgIQcRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAV
BgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTow
OAYDVQQLEzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5
MUUwQwYDVQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24g
QXV0aG9yaXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBO
ZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29t
L3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJp
U2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0B
AQEFAAOCAQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6Zvg
SU6Lb9UB0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHs
EnMhjfXcMM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO
4YM/d/mZ//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSy
riMGZSalJ1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCC
ArUwNAYIKwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20w
EgYDVR0TAQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUH
AgEWHGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWdu
LmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgw
VhYJaW1hZ2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDov
L2xvZ28udmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQ
cml2YXRlTGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYD
VR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4x
HzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlT
aWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENs
YXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaE
VIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlM
JBq6WaSHO3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKv
YLMVirOVnDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDR
yxTWcVibvtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy
+kgOZY5JyNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/
wYIxggSLMIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2Ug
YXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2Ny
aWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJ
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDIxNjA5MTMzN1owIwYJKoZIhvcNAQkE
MRYEFLS6/0qpwN7Vcg4WFBaYw7e+LX7wMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AEt05GZoFJmLISuAqGdAUpHyc8zqU0mCQSejinz9QoMxyoBYOdqgwLVjcLue+bFfReooQXnG2Pln
rHiUl6eUhE/N/K6tVSStu7fHMivgo7ky/cqcmM/rTQgjNC+Xnt1DpA1fs73LgyzAwsYTPCxJAkl/
b80ouW6oG1l6O37hP4w3PWf646ETbTAgqneBqGBi8JtWufjchS0mf5DVX9z7SPiazloxNoOtWxrY
nrQli+2UUWceebyIjuhM+jDakVVxea/73y+qgNBBYb4gYmJF3XVm3qYv6ydROMhaW5IsR8GtfCcV
3EuCBX+GxPkSdsEOhu28+TlcdjYa7HOMmw8L70UAAAAAAAA=

--Apple-Mail-30--434646293--

From alexey.melnikov@isode.com  Wed Feb 16 03:11:48 2011
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 903623A6DF8; Wed, 16 Feb 2011 03:11:48 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BwfkcyQkyw7z; Wed, 16 Feb 2011 03:11:42 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 97F153A6E05; Wed, 16 Feb 2011 03:11:41 -0800 (PST)
Received: from [188.28.83.64] (188.28.83.64.threembb.co.uk [188.28.83.64])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TVuxAwADL2Lh@rufus.isode.com>; Wed, 16 Feb 2011 11:12:06 +0000
Message-ID: <4D5BB0E8.5000503@isode.com>
Date: Wed, 16 Feb 2011 11:11:36 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Peter Saint-Andre <stpeter@stpeter.im>, Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt>  (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@ericsson.com> <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com> <4D46B3B9.4050804@ericsson.com> <755A9333-6960-4BCC-B996-3775E76B5D9E@cisco.com> <4D4920F0.1070204@ericsson.com> <49CDF352-D900-4883-8D67-19172DBC8474@cisco.com> <4D5B4B98.4060704@vpnc.org> <6AA482E6-924C-4981-9E7F-69AD8EE3DD6F@cisco.com> <4D5B4D86.3020102@stpeter.im>
In-Reply-To: <4D5B4D86.3020102@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Paul Hoffman <paul.hoffman@vpnc.org>, IESG IESG <iesg@ietf.org>, tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 11:11:48 -0000

Peter Saint-Andre wrote:

>Agreed, thanks to Paul for the proposed text.
>
>On 2/15/11 9:02 PM, Cullen Jennings wrote:
>  
>
>>Paul's text is much better than mine. That was what I trying to get
>>at.
>>    
>>
Agreed, I will add this as an RFC Editor's note.

>>On Feb 15, 2011, at 8:59 PM, Paul Hoffman wrote:
>>    
>>
>>>On 2/15/11 7:34 PM, Cullen Jennings wrote:
>>>      
>>>
>>>>I propose some text for the draft near the bottom of this
>>>>email.... For the user ports the document should have some text
>>>>along the lines of:
>>>>
>>>>There is not IETF consensus on when it is appropriate to use a
>>>>second port for a secure version of protocol therefor the export
>>>>reviewer should not reject a request for a second port to run a
>>>>secure variant of the protocol over.
>>>>        
>>>>
>>>That feels close, but too prescriptive. Also, the requests are
>>>usually for a protocol with two ports, not a later request for a
>>>second port. How about:
>>>
>>>There is not IETF consensus on when it is appropriate to use a
>>>second port for a secure version of protocol. Therefore, an expert
>>>reviewer should not reject a proposal for a protocol that uses a
>>>second part to run a secure variant for the sole reason that it
>>>is using two ports.
>>>      
>>>


From daedulus@btconnect.com  Wed Feb 16 04:00:59 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 265FF3A6E28 for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 04:00: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rP5q-dylqkzj for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 04:00:58 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id C55B03A6E14 for <ietf@ietf.org>; Wed, 16 Feb 2011 04:00:56 -0800 (PST)
Received: from host86-141-16-12.range86-141.btcentralplus.com (HELO pc6) ([86.141.16.12]) by c2beaomr07.btconnect.com with SMTP id BUF08530; Wed, 16 Feb 2011 12:01:19 +0000 (GMT)
Message-ID: <003101cbcdc8$42dfaf20$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Marc Petit-Huguenin" <petithug@acm.org>, "Bjoern Hoehrmann" <derhoermi@gmx.net>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com><2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de> <4D5B0AB8.90509@acm.org>
Subject: Re: MHonArc mail archive line wrapping
Date: Wed, 16 Feb 2011 11:57:06 +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.0A0B0302.4D5BBC8F.00E6, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4D5BBC90.0231,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: Stuart Cheshire <cheshire@apple.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 12:00:59 -0000

---- Original Message -----
From: "Marc Petit-Huguenin" <petithug@acm.org>
To: "Bjoern Hoehrmann" <derhoermi@gmx.net>
Cc: "Stuart Cheshire" <cheshire@apple.com>; "IETF-Discussion list"
<ietf@ietf.org>
Sent: Wednesday, February 16, 2011 12:22 AM
>
> On 02/15/2011 01:32 PM, Bjoern Hoehrmann wrote:
> > * Stuart Cheshire wrote:
> >> In the MHonArc mail archive there are often super-long lines, which
> >> would be wrapped to the window width when viewing in most mail
> >> clients, but when viewed in a web browser they appear as long single
> >> lines which take a lot of left-to-right scrolling to read them.
> >
> > That is the result of some clients and users violating netiquette and
> > mail standards, for instance, RFC 1855, section 2.1.1:
> >
> >   - Limit line length to fewer than 65 characters and end a line
> >     with a carriage return.
> >
> > and RFC 2822 (and similarily RFC 5322), section 2.1.1:
> >
> >   There are two limits that this standard places on the number of
> >   characters in a line. Each line of characters MUST be no more than
> >   998 characters, and SHOULD be no more than 78 characters, excluding
> >   the CRLF.
> >
> > And this does not cause problems just with unwrapped lines, it also has
> > other effects, like people quoting excessively long lines on one line
> > but then write their own text properly wrapped (that's appropriate be-
> > havior if long lines are rare and most likely intentional, such as when
> > including some computer code you don't want wrapped at odd positions.)
> >
> > I note that one of the main culprits here are Apple Mail users, although
> > you seem to be using it yet have managed to send properly wrapped lines.
> > If there is something Apple Mail users can do to stop their netiquette
> > and standards violations, I would apprciate any pointer you may have.

If only Apple Mail users would stop signing mails it would be a major step
forward.

Depending on the algorithm, I either get a blank pane, and have to
get into properties to see the text, or, with more recent PKIX-based
algorithms, have to wait for a megabyte download of CRL (or, if
I am offline, a two minute lockup of my PC).

Grrr  I don't care what standard signed mails conform to, I just
want them filtered out at source:-)

Tom Petch

<snip>


From hartmans@mit.edu  Wed Feb 16 04:13:43 2011
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC61A3A6E3D; Wed, 16 Feb 2011 04:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.349, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NlAeAmTvmxnl; Wed, 16 Feb 2011 04:13:43 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 3F57D3A6B74; Wed, 16 Feb 2011 04:13:43 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 59812202FB; Wed, 16 Feb 2011 07:11:54 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2410A4307; Wed, 16 Feb 2011 07:13:51 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry) to BCP
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <4D421795.70505@isi.edu> <tslbp2vh8ig.fsf@mit.edu> <Pine.LNX.4.64.1102071321290.4671@adax.adax> <CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <2803F25F-A2BE-46E3-8284-A256A9B9D415@cisco.com>
Date: Wed, 16 Feb 2011 07:13:51 -0500
In-Reply-To: <2803F25F-A2BE-46E3-8284-A256A9B9D415@cisco.com> (Cullen Jennings's message of "Tue, 15 Feb 2011 21:31:29 -0700")
Message-ID: <tslmxlwqirk.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, Chris Benson <cbenson@adax.com>, IESG IESG <iesg@ietf.org>, Christian Huitema <huitema@microsoft.com>, Sam Hartman <hartmans-ietf@mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 12:13:44 -0000

Cullen, there's a lot of history with port registrations.  As you're
probably aware in the past, there was a procedure for experts to sign an
NDA before reviewing port requests.  It's my understanding that is no
longer done.  However, it does suggest there's strong desire for
proprietary protocol support.
So, there's lots of complexity specific to this registry here that I
don't know about.

However, the general idea of having experts reviews on a public list, or
even soliciting comments on a public list is well supported. There's
specific discussion of this in RFC 5226. We've done it successfully in a
number of cases.  So, there's reason to believe that things in this
space could be effective for IANA registries.  I think soliciting public
comments on port requests would be bad; I think your proposal of having
the request/response be published would be as far as we should go for
this registry at this time.

So, I don't have the background to say this would be a good fit for the
port registry, but to the extent that my background supports something
like this I can support your idea. It's worked elsewhere at lesat.

From daedulus@btconnect.com  Wed Feb 16 04:17:28 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2E6C3A6E34; Wed, 16 Feb 2011 04:17:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[AWL=-0.620, BAYES_00=-2.599, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELAynWwZ3qQF; Wed, 16 Feb 2011 04:17:27 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id 2AAB93A6CAA; Wed, 16 Feb 2011 04:17:26 -0800 (PST)
Received: from host86-141-16-12.range86-141.btcentralplus.com (HELO pc6) ([86.141.16.12]) by c2beaomr07.btconnect.com with SMTP id BUF28912; Wed, 16 Feb 2011 12:17:50 +0000 (GMT)
Message-ID: <009301cbcdca$91682300$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Cullen Jennings" <fluffy@cisco.com>, "Christian Huitema" <huitema@microsoft.com>
References: <20110118212603.5733.34489.idtracker@localhost><B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com><ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<4D421795.70505@isi.edu><tslbp2vh8ig.fsf@mit.edu><Pine.LNX.4.64.1102071321290.4671@adax.adax><CEBCE3CF81D2D441B14B84256C3C46810BD95BD8@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com> <2803F25F-A2BE-46E3-8284-A256A9B9D415@cisco.com>
Subject: Re: Last Call: <draft-ietf-tsvwg-iana-ports-09.txt> (InternetAssigned	Numbers Authority (IANA) Procedures for the Managementof the Service	Name and Transport Protocol Port NumberRegistry) to BCP
Date: Wed, 16 Feb 2011 12:13:18 +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.4D5BC06E.0075, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0204.4D5BC06F.0332,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: IETF discussion list <ietf@ietf.org>, tsvwg@ietf.org, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 12:17:28 -0000

---- Original Message -----
From: "Cullen Jennings" <fluffy@cisco.com>
To: "Christian Huitema" <huitema@microsoft.com>
Cc: <tsvwg@ietf.org>; "Paul Hoffman" <paul.hoffman@vpnc.org>; "Chris Benson"
<cbenson@adax.com>; "IESG IESG" <iesg@ietf.org>; "Sam Hartman"
<hartmans-ietf@mit.edu>; "IETF discussion list" <ietf@ietf.org>
Sent: Wednesday, February 16, 2011 5:31 AM
>
> I've been thinking more about this thread and my concerns about this draft. I
was originally looking for the draft to have advice for the expert review team
that gave them guidance on what the IETF thought was all right to approve or not
approve. It's become clear that this draft does not have that advice and is not
likely to get it in the very short term. This BCP will empower the expert
reviewer to reject or approve just about any request. Appeals are not the best
way to balance putting that power because they are incredibly corrosive and time
consuming to everyone involved. I think this thread somewhat suggests an
alternative approach for a check and balance.
>

Cullen

My understanding of this draft is that Expert Review only applies when "IETF
Review" or "IESG Approval" does not apply, so a duly approved Standards
Track RFC trumps all Experts.

I proposed text on 2nd February to make this clearer, and understand that this
change was accepted.

Where the request is not via "IETF Review" or "IESG Approval", then I have
less concern as to what the Expert may or may not allow.

My  text is

"For most IETF protocols, ports in the User Ports range will be assigned under
the "IETF Review" or "IESG Approval" procedures [RFC5226] and no further
documentation is required.

Where these procedures do not apply, then the requester must
input the documentation to  the "Expert Review"
procedure
        [RFC5226], by which IANA will have a technical expert review the
        request to determine whether to grant the assignment.  The
        submitted documentation MUST explain why using a port number in
        the Dynamic Ports range is unsuitable for the given application."

Tom Petch


> What do people think of the idea of: for all ports requests, the request and
the expert reviewer reposes including reason for accepting or rejecting them
need to be posted to a public email list. This seems like a simple way to help
mitigate this issue and it will help educate people writing a port request to
know what types of issues they need to address and what would be appropriate or
not.
>
> Pros & cons of this idea?
>
> On Feb 8, 2011, at 1:41 PM, Christian Huitema wrote:
>
> >> I don't see that "public identity" (of expert reviewers) is required for
"interactive discussion".
> >> Or would anonymous interaction fail a Turing test of some kind?
> >
> > Public identity is required for reviewer accountability. It is easy to
imagine how withholding registration of some required numbers may delay a
competitor's products. The best protection against shade is sunlight.
> >
> > -- Christian Huitema
> >
> >


From rbarnes@bbn.com  Wed Feb 16 05:29:34 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90A203A6CBF for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 05:29:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.489
X-Spam-Level: 
X-Spam-Status: No, score=-102.489 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmt50BRMDDND for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 05:29:30 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id E027F3A6B74 for <ietf@ietf.org>; Wed, 16 Feb 2011 05:29:29 -0800 (PST)
Received: from [128.89.253.107] (port=62031 helo=[192.168.1.10]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PphS8-000Plv-99; Wed, 16 Feb 2011 08:29:56 -0500
Subject: Re: World IPv6 Day and Us
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <9ED59100-59BD-44B9-8319-FC66DD86D020@nokia.com>
Date: Wed, 16 Feb 2011 08:29:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA93C9FD-2E4F-4EC2-93D2-983453E4EB9C@bbn.com>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com> <9ED59100-59BD-44B9-8319-FC66DD86D020@nokia.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.1082)
Cc: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 13:29:37 -0000

Parts of the challenge here is that turning on IPv6 (publishing a AAAA) =
can also cause brokenness for users that have no IPv6 connectivity, =
e.g., those relying on broken 6to4 relays.  This has been documented all =
over the place, for example here:
<http://ripe61.ripe.net/presentations/162-ripe61.pdf>

So even if there are very few IPv6 eyeballs, this event can serve to =
flush out that flavor of brokenness.  As I understand it, part of the =
idea of everyone moving together is to get people to see the brokenness =
across multiple sites, thus to blame the network not the content =
provider, thus to pressure the networks to fix things.

--Richard



On Feb 16, 2011, at 4:13 AM, Lars Eggert wrote:

> On 2011-2-15, at 19:45, Sabahattin Gucukoglu wrote:
>> Noting the increasing length of the list =
athttp://isoc.org/wp/worldipv6day/participants/
>=20
> ...I mostly note that I see very few eyeball ISPs on that list (with =
the notable exception of two large US cable ISPs - great, guys!)
>=20
> Turning on IPv6 on the content provider side is great and all, but =
without the eyeballs on IPv6, I wonder a bit about the point of this =
exercise.
>=20
> Lars_______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rbarnes@bbn.com  Wed Feb 16 05:36:01 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7DA23A6D12 for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 05:36:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iO4UoeFJONbI for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 05:36:00 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 851BA3A6CB8 for <ietf@ietf.org>; Wed, 16 Feb 2011 05:36:00 -0800 (PST)
Received: from [128.89.253.107] (port=62062 helo=[192.168.1.10]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PphYN-000Pqw-JJ; Wed, 16 Feb 2011 08:36:23 -0500
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2011 08:36:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1812B930-6730-4432-814B-740B14C37F1A@bbn.com>
References: <20110118150445.13842.1912.idtracker@localhost> <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com> <4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
X-Mailer: Apple Mail (2.1082)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 13:36:02 -0000

> As you are assuming physical identity of DHCP clients are known
> reliably (I don't know how it can be done), it is a lot easier
> for DHCP servers to assign static IP addresses to the clients
> based on the physical identity information than assigning random
> addresses and map them later through complicated database look up.

As an example, consider a system we built for the IETF meeting network a =
few years ago.  The server queried a series of tables inside of NetDisco =
to map an IP address to the WiFi AP that it was connected to:
IP address --> MAC address --> Connected AP
Since the locations of the APs are known, this gives you the location of =
the endpoint to within a few tens of meters (empirically, within the =
IETF network).


>> This is an important use case, for example, for ECRIT
>> emergency services [draft-ietf-ecrit-framework]
>=20
> Is it a use case in the real world?

The US FCC thinks so:
<http://edocket.access.gpo.gov/2011/pdf/2011-565.pdf>

--Richard=

From tme@americafree.tv  Wed Feb 16 05:58:34 2011
Return-Path: <tme@americafree.tv>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 87AC43A6B6B for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 05:58:34 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zA7a41s5YvNY for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 05:58:33 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 7C5F53A6956 for <ietf@ietf.org>; Wed, 16 Feb 2011 05:58:33 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 81F219F3C7E0; Wed, 16 Feb 2011 08:59:01 -0500 (EST)
Subject: Re: World IPv6 Day and Us
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <9ED59100-59BD-44B9-8319-FC66DD86D020@nokia.com>
Date: Wed, 16 Feb 2011 08:58:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D64480CC-ED35-415B-BC06-D4C7A141D4A9@americafree.tv>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com> <9ED59100-59BD-44B9-8319-FC66DD86D020@nokia.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.1081)
Cc: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 13:58:34 -0000

On Feb 16, 2011, at 4:13 AM, Lars Eggert wrote:

> On 2011-2-15, at 19:45, Sabahattin Gucukoglu wrote:
>> Noting the increasing length of the list =
athttp://isoc.org/wp/worldipv6day/participants/
>=20
> ...I mostly note that I see very few eyeball ISPs on that list (with =
the notable exception of two large US cable ISPs - great, guys!)
>=20
> Turning on IPv6 on the content provider side is great and all, but =
without the eyeballs on IPv6, I wonder a bit about the point of this =
exercise.
>=20

You have to start somewhere...

And, this has been good at getting some publicity for IPv6, which is not =
negligible.=20

Marshall

> Lars_______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From mohta@necom830.hpcl.titech.ac.jp  Wed Feb 16 06:23:09 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30D023A6E62 for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.114
X-Spam-Level: 
X-Spam-Status: No, score=-0.114 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q7fpPocNHUtw for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:23:08 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id E02193A6E49 for <ietf@ietf.org>; Wed, 16 Feb 2011 06:23:07 -0800 (PST)
Received: (qmail 49776 invoked from network); 16 Feb 2011 14:33:44 -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 2011 14:33:44 -0000
Message-ID: <4D5BDDBA.9090109@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2011 23:22:50 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
References: <20110118150445.13842.1912.idtracker@localhost> <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com> <4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp> <1812B930-6730-4432-814B-740B14C37F1A@bbn.com>
In-Reply-To: <1812B930-6730-4432-814B-740B14C37F1A@bbn.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:23:09 -0000

Richard L. Barnes wrote:

>> As you are assuming physical identity of DHCP clients are known
>> reliably (I don't know how it can be done), it is a lot easier
>> for DHCP servers to assign static IP addresses to the clients
>> based on the physical identity information than assigning random
>> addresses and map them later through complicated database look up.
> 
> As an example, consider a system we built for the IETF meeting
> network a few years ago.  The server queried a series of
> tables inside of NetDisco to map an IP address to the WiFi AP
> that it was connected to:
> IP address -->  MAC address -->  Connected AP

As the MAC addresses are NOT reliable, it is a lot more straight
forward to directly map between IP addresses and APs.

> Since the locations of the APs are known, this gives you the
> location of the endpoint to within a few tens of meters
> (empirically, within the IETF network).

Directional antenna makes it imprecise.

>> Is it a use case in the real world?
> 
> The US FCC thinks so:
> <http://edocket.access.gpo.gov/2011/pdf/2011-565.pdf>

Could you quote the relevant part of the lengthy document?

						Masataka Ohta

From scott.brim@gmail.com  Wed Feb 16 06:27:35 2011
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 415F93A6E41 for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0L6TsEAtqIPH for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:27:34 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 381EB3A6CCD for <ietf@ietf.org>; Wed, 16 Feb 2011 06:27:34 -0800 (PST)
Received: by gxk27 with SMTP id 27so674138gxk.31 for <ietf@ietf.org>; Wed, 16 Feb 2011 06:28:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Uj8mo3ZHwJBzxxvHLzf1cYW4F4QtrUW21vxIBznd/Do=; b=w8KOW4f9GMUfTfBGB7q5C+lKqJCMY8Sz6G0dhxoC5FYkvKL0tDdssFPg+ECZrJ5h4P ymhTEDQ98L04gidDLMFUyrik+SvxNzoPAjxdtseadU4++r7DTM1wHB+WHcRYTdJUY04H lPKPjsoCAH0D71edOEf9M8MrtyqK+dK6aNK84=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=aKenclil5bchUnZH2MdGUCdMaOZHhabrI/yUKEzxMCsvn0ZuMMfWFAIsLAZrPqpZm/ VpcyMtEjILy59v1YfP04J4QAi0kqjLrBDqmYP0jjOBIqwpxczbcZ+awV+WSd5/zJVgVo GMx1SRW9UNAQArEIpnZY3QaCy697/7iEgZ7FM=
MIME-Version: 1.0
Received: by 10.90.116.6 with SMTP id o6mr854151agc.78.1297866482264; Wed, 16 Feb 2011 06:28:02 -0800 (PST)
Received: by 10.91.180.19 with HTTP; Wed, 16 Feb 2011 06:28:02 -0800 (PST)
In-Reply-To: <4D5BDDBA.9090109@necom830.hpcl.titech.ac.jp>
References: <20110118150445.13842.1912.idtracker@localhost> <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com> <4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp> <1812B930-6730-4432-814B-740B14C37F1A@bbn.com> <4D5BDDBA.9090109@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Feb 2011 09:28:02 -0500
Message-ID: <AANLkTikHqVC1_Rnm3H8GUVVwtteiMgj3ZNsMt9dZs+T8@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
From: Scott W Brim <scott.brim@gmail.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Content-Type: multipart/alternative; boundary=001636164691a42b93049c67166d
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:27:35 -0000

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

On Wed, Feb 16, 2011 at 09:22, Masataka Ohta <
mohta@necom830.hpcl.titech.ac.jp> wrote:

> Richard L. Barnes wrote:
>
> > As an example, consider a system we built for the IETF meeting
> > network a few years ago.  The server queried a series of
> > tables inside of NetDisco to map an IP address to the WiFi AP
> > that it was connected to:
> > IP address -->  MAC address -->  Connected AP
>
> As the MAC addresses are NOT reliable, it is a lot more straight
> forward to directly map between IP addresses and APs.
>

In the (excellent!) experiment, you associated yourself with one or more MAC
addresses.  Your IP address is more likely to change than your MAC.


> > Since the locations of the APs are known, this gives you the
> > location of the endpoint to within a few tens of meters
> > (empirically, within the IETF network).
>
> Directional antenna makes it imprecise.
>

In the (truly excellent) experiment, the goal was to find out which room
someone was in so you could find them.

swb

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

On Wed, Feb 16, 2011 at 09:22, Masataka Ohta <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mohta@necom830.hpcl.titech.ac.jp">mohta@necom830.hpcl.titech.ac.=
jp</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rg=
b(204, 204, 204); padding-left: 1ex;">
Richard L. Barnes wrote:<br>
<br>
&gt; As an example, consider a system we built for the IETF meeting<br>
&gt; network a few years ago. =A0The server queried a series of<br>
&gt; tables inside of NetDisco to map an IP address to the WiFi AP<br>
&gt; that it was connected to:<br>
&gt; IP address --&gt; =A0MAC address --&gt; =A0Connected AP<br>
<br>
As the MAC addresses are NOT reliable, it is a lot more straight<br>
forward to directly map between IP addresses and APs.<br></blockquote><div>=
<br>In the (excellent!) experiment, you associated yourself with one or mor=
e MAC addresses.=A0 Your IP address is more likely to change than your MAC.=
<br>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8=
ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
&gt; Since the locations of the APs are known, this gives you the<br>
&gt; location of the endpoint to within a few tens of meters<br>
&gt; (empirically, within the IETF network).<br>
<br>
Directional antenna makes it imprecise.<br></blockquote><div><br>In the (tr=
uly excellent) experiment, the goal was to find out which room someone was =
in so you could find them.=A0=A0 <br><br>swb<br><br></div></div>

--001636164691a42b93049c67166d--

From dworley@avaya.com  Wed Feb 16 06:46:16 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EFC403A6E3C for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:46:16 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-1Rk03mJEoq for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:46:16 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id A32EF3A6E14 for <ietf@ietf.org>; Wed, 16 Feb 2011 06:46:15 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAH9xW03GmAcF/2dsb2JhbAClYHOjGgKZKIVeBIUIilQ
X-IronPort-AV: E=Sophos;i="4.60,480,1291611600"; d="scan'208";a="232691381"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Feb 2011 09:46:42 -0500
X-IronPort-AV: E=Sophos;i="4.60,480,1291611600"; d="scan'208";a="583089806"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 16 Feb 2011 09:46:41 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.215]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Wed, 16 Feb 2011 09:46:41 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Marshall Eubanks <tme@americafree.tv>, Lars Eggert <lars.eggert@nokia.com>
Date: Wed, 16 Feb 2011 09:43:11 -0500
Subject: RE: World IPv6 Day and Us
Thread-Topic: World IPv6 Day and Us
Thread-Index: AcvN4bJhLNdOpw25SquKjRbxLNqvBQABiMNg
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A176886@DC-US1MBEX4.global.avaya.com>
References: <14C63D7E-0E2C-46EB-8C52-B61C45F0CABF@sabahattin-gucukoglu.com> <9ED59100-59BD-44B9-8319-FC66DD86D020@nokia.com>, <D64480CC-ED35-415B-BC06-D4C7A141D4A9@americafree.tv>
In-Reply-To: <D64480CC-ED35-415B-BC06-D4C7A141D4A9@americafree.tv>
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: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:46:17 -0000

> On 2011-2-15, at 19:45, Sabahattin Gucukoglu wrote:
>> Noting the increasing length of the list athttp://isoc.org/wp/worldipv6d=
ay/participants/
>
> ...I mostly note that I see very few eyeball ISPs on that list (with the =
notable exception of two large US cable ISPs - great, guys!)
>
> Turning on IPv6 on the content provider side is great and all, but withou=
t the eyeballs on IPv6, I wonder a bit about the point of this exercise.

The point is that eventually, someone will notice that the IETF is lobbying=
 hard for IPv6 as the necessary next step for the Internet, but that the IE=
TF doesn't actually use IPv6 in its own infrastructure, and we are greatly =
embarrassed.

It would be like lobbying regarding global warming while owning 500 coal-fi=
red power plants.  It doesn't make what you *say* wrong, but it looks very,=
 very bad.  It suggests that despite our advocacy of IPv6 there is some gre=
at difficulty to going to IPv6 that we are not admitting.

Dale

From jason_livingood@cable.comcast.com  Wed Feb 16 06:48:24 2011
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28B2A3A6CBF for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.977
X-Spam-Level: 
X-Spam-Status: No, score=-103.977 tagged_above=-999 required=5 tests=[AWL=-2.242, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ss-D1qhyY7o for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 06:48:23 -0800 (PST)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by core3.amsl.com (Postfix) with ESMTP id 5D57A3A6C9F for <ietf@ietf.org>; Wed, 16 Feb 2011 06:48:20 -0800 (PST)
Received: from ([24.40.55.41]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.26044284; Wed, 16 Feb 2011 07:59:13 -0700
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0270.001; Wed, 16 Feb 2011 09:47:43 -0500
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>, Lars Eggert <lars.eggert@nokia.com>
Subject: Re: World IPv6 Day and Us
Thread-Topic: World IPv6 Day and Us
Thread-Index: AQHLzTgcJYB3k/56vUuyFPaQVbIk9pQELPeAgABHlYD//8H5gA==
Date: Wed, 16 Feb 2011 14:47:42 +0000
Message-ID: <C9814D43.18C04%jason_livingood@cable.comcast.com>
In-Reply-To: <FA93C9FD-2E4F-4EC2-93D2-983453E4EB9C@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [10.36.144.238]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3DEE707040DAAE408AF29DA49F8E4E7C@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 14:48:24 -0000

>Parts of the challenge here is that turning on IPv6 (publishing a AAAA)
>can also cause brokenness for users that have no IPv6 connectivity, e.g.,
>those relying on broken 6to4 relays.  This has been documented all over
>the place, for example here:
><http://ripe61.ripe.net/presentations/162-ripe61.pdf>
>
>So even if there are very few IPv6 eyeballs, this event can serve to
>flush out that flavor of brokenness.  As I understand it, part of the
>idea of everyone moving together is to get people to see the brokenness
>across multiple sites, thus to blame the network not the content
>provider, thus to pressure the networks to fix things.

Richard is exactly right on where a lot of value is. This is an
opportunity to find and fix the ~0.05% level of brokenness. Even
"non-participating" ISPs will need to take steps to prepare, and this is
of course a great forcing function within companies to ask what their IPv6
plans and to begin/continue IPv6 technical training, etc.

Jason


From brian.e.carpenter@gmail.com  Wed Feb 16 11:19:27 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAC8E3A6D33 for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 11:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.173
X-Spam-Level: 
X-Spam-Status: No, score=-103.173 tagged_above=-999 required=5 tests=[AWL=-0.174, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x3WHu-0rFFGq for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 11:19:26 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 93E2F3A69A6 for <ietf@ietf.org>; Wed, 16 Feb 2011 11:19:26 -0800 (PST)
Received: by fxm9 with SMTP id 9so1865422fxm.31 for <ietf@ietf.org>; Wed, 16 Feb 2011 11:19:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2aRss2qnK8bg1mLqp1dEgyH3CcLf+zHwt0y+2JDBXdo=; b=xmMZnHcBaQNkKdpvEGEn1ONxwpeaNVjCL5WYPJPoC/XA9h7iaqf9TsiI350netdolf OWapD6CcsjsrCfg6dyDiVM2RVMdmv4YccDyiwuIaJuZ7e00eA7uXLbISZkd8S0XHCMMH HN/g+qnKPWeirc21kLgppdcBOkk78cVfYir/4=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=Jc0GZZW7rfxyPezZt/ZYLStfherWKbG9pTiZW4p5eIFVoS700b4BnqTffMquiOJ/MI nS4G/dyoSJ4NIwiQw0AZVE/tRNwnFCOEgbZFopmDHSr02gi1Lv2Vc/Tejanzwql0vdsb n5GEuYcebwLaeYmglmE5n9tN3UEHDCtiu0uCA=
Received: by 10.223.74.15 with SMTP id s15mr1211018faj.28.1297883994907; Wed, 16 Feb 2011 11:19:54 -0800 (PST)
Received: from [10.1.1.5] ([121.98.190.33]) by mx.google.com with ESMTPS id a2sm49291faw.46.2011.02.16.11.19.49 (version=SSLv3 cipher=OTHER); Wed, 16 Feb 2011 11:19:53 -0800 (PST)
Message-ID: <4D5C234A.6090903@gmail.com>
Date: Thu, 17 Feb 2011 08:19:38 +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: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Subject: Re: World IPv6 Day and Us
References: <C9814D43.18C04%jason_livingood@cable.comcast.com>
In-Reply-To: <C9814D43.18C04%jason_livingood@cable.comcast.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, Sabahattin Gucukoglu <mail-dated-1300383904.c57e10@sabahattin-gucukoglu.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 19:19:27 -0000

On 2011-02-17 03:47, Livingood, Jason wrote:
>> Parts of the challenge here is that turning on IPv6 (publishing a AAAA)
>> can also cause brokenness for users that have no IPv6 connectivity, e.g.,
>> those relying on broken 6to4 relays.  This has been documented all over
>> the place, for example here:
>> <http://ripe61.ripe.net/presentations/162-ripe61.pdf>
>>
>> So even if there are very few IPv6 eyeballs, this event can serve to
>> flush out that flavor of brokenness.  As I understand it, part of the
>> idea of everyone moving together is to get people to see the brokenness
>> across multiple sites, thus to blame the network not the content
>> provider, thus to pressure the networks to fix things.
> 
> Richard is exactly right on where a lot of value is. This is an
> opportunity to find and fix the ~0.05% level of brokenness. Even
> "non-participating" ISPs will need to take steps to prepare, and this is
> of course a great forcing function within companies to ask what their IPv6
> plans and to begin/continue IPv6 technical training, etc.

Over in v6ops, we have had some vigorous discussion about the anycast 6to4
brokenness and there is a draft:
   draft-carpenter-v6ops-6to4-teredo-advisory
My hope is that this will be in good enough shape prior to June 8th
that it can contribute to the day. Discussion welcome on the v6ops list.

    Brian


From mohta@necom830.hpcl.titech.ac.jp  Wed Feb 16 12:41:57 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4D753A6D4F for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 12:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.111
X-Spam-Level: 
X-Spam-Status: No, score=-0.111 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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MlnD5dR9r9nW for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 12:41:57 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id BDC9C3A6D6C for <ietf@ietf.org>; Wed, 16 Feb 2011 12:41:55 -0800 (PST)
Received: (qmail 63476 invoked from network); 16 Feb 2011 20:52: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; 16 Feb 2011 20:52:24 -0000
Message-ID: <4D5C3669.6060907@necom830.hpcl.titech.ac.jp>
Date: Thu, 17 Feb 2011 05:41:13 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Scott W Brim <scott.brim@gmail.com>
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
References: <20110118150445.13842.1912.idtracker@localhost>	<9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com>	<4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp>	<1812B930-6730-4432-814B-740B14C37F1A@bbn.com>	<4D5BDDBA.9090109@necom830.hpcl.titech.ac.jp> <AANLkTikHqVC1_Rnm3H8GUVVwtteiMgj3ZNsMt9dZs+T8@mail.gmail.com>
In-Reply-To: <AANLkTikHqVC1_Rnm3H8GUVVwtteiMgj3ZNsMt9dZs+T8@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 20:41:57 -0000

Scott W Brim wrote:

>>> IP address -->   MAC address -->   Connected AP

>> As the MAC addresses are NOT reliable, it is a lot more straight
>> forward to directly map between IP addresses and APs.

> In the (excellent!) experiment, you associated yourself with one or more MAC
> addresses.  Your IP address is more likely to change than your MAC.

I can't see the point of insisting on MAC. If MAC is so good, use it,
not IP, for geo-location.

> In the (truly excellent) experiment, the goal was to find out which room
> someone was in so you could find them.

Are there any other hidden assumptions of the experiment?

							Masataka Ohta

PS

I acknowledge there is no real world use cases.

From chair@ietf.org  Wed Feb 16 13:31:29 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD7803A6CB0; Wed, 16 Feb 2011 13:31:29 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yyhe7tX8XiSd; Wed, 16 Feb 2011 13:31:29 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 058AA3A6D58; Wed, 16 Feb 2011 13:31:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 77FC1E08C3; Wed, 16 Feb 2011 13:31:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqlXsKMR3BZW; Wed, 16 Feb 2011 13:31:58 -0800 (PST)
Received: from [192.168.2.105] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) by c1a.amsl.com (Postfix) with ESMTPSA id 0C597E0611; Wed, 16 Feb 2011 13:31:57 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Prague IETF Codesprint
Mime-Version: 1.0 (Apple Message framework v1082)
From: IETF Chair <chair@ietf.org>
Date: Wed, 16 Feb 2011 16:31:56 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <49A6CCB2-B484-4F0E-B489-F1D1DAEBAEE8@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: 80all@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: IETF <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 21:31:29 -0000

Prague IETF Codesprint

When:  26 March 2011, starting at 9:30 AM

Where: IETF Hotel

What:  A bunch of hackers get together to work on code for the IETF.
      All code will become part of the open source IETF tools.

Who:   Hopefully you can help

Many of the results of previous codesprint activities are being
used every day by the IETF community.  Work to polish or
improve existing tools will be most welcome.  Work on something
completely new is also welcome.

Steve Conte will be helping with advance planning.  Henrik Levkowetz
will be coordinating the event in Prague.  More information is available at:

http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF80Sprint

If you are able to participate, please sign up on the wiki at:

http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF80SprintSignUp

Please support the tools development effort,
 Russ


From rbarnes@bbn.com  Wed Feb 16 14:24:45 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B73F23A6AFD for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 14:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGMVemoAETys for <ietf@core3.amsl.com>; Wed, 16 Feb 2011 14:24:44 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 64DA03A6AA6 for <ietf@ietf.org>; Wed, 16 Feb 2011 14:24:44 -0800 (PST)
Received: from [128.89.253.126] (port=64631 helo=[10.45.1.166]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Pppo9-0007iV-67; Wed, 16 Feb 2011 17:25:13 -0500
Subject: Re: Last Call: <draft-ietf-intarea-shared-addressing-issues-02.txt> (Issues with IP Address Sharing) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <AANLkTikHqVC1_Rnm3H8GUVVwtteiMgj3ZNsMt9dZs+T8@mail.gmail.com>
Date: Wed, 16 Feb 2011 17:25:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F245CA3A-7F9C-4B6D-BA20-387C7E81DAAE@bbn.com>
References: <20110118150445.13842.1912.idtracker@localhost> <9E2CF70F-F7DD-409C-A5FE-E946BCD32C1F@bbn.com> <4D5B7FAD.8090400@necom830.hpcl.titech.ac.jp> <1812B930-6730-4432-814B-740B14C37F1A@bbn.com> <4D5BDDBA.9090109@necom830.hpcl.titech.ac.jp> <AANLkTikHqVC1_Rnm3H8GUVVwtteiMgj3ZNsMt9dZs+T8@mail.gmail.com>
To: Scott W Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 22:24:45 -0000

Hey Scott,

Thanks for all the "excellent"s.  Hopefully some of them are deserved :)

Couple of clarifications:

> > IP address -->  MAC address -->  Connected AP
>=20
> As the MAC addresses are NOT reliable, it is a lot more straight
> forward to directly map between IP addresses and APs.
>=20
> In the (excellent!) experiment, you associated yourself with one or =
more MAC addresses.  Your IP address is more likely to change than your =
MAC.

You're actually both right, but neither fact really matters to the =
experiment.  The goal was to locate "the thing with that IP", and the =
network is authoritative for which MAC address goes with that IP -- even =
if the MAC address is bogus and even if the MAC address changes.  In the =
end, all you really care about is that the thing that is assigned a =
given IP address is connected to a given access point, which bounds its =
location.  =20


> Directional antenna makes it imprecise.
>=20
> In the (truly excellent) experiment, the goal was to find out which =
room someone was in so you could find them.  =20

Even with a directional antenna that's throwing WiFi out for a couple of =
kilometers, you're still doing a lot better than the generic IP-geo =
service mentioned in the draft.  And part of the point of discussing =
ISP-based systems is that the ISP knows how the APs are laid out and =
configured -- so even if there were directional antennas, the location =
system could account for them.

In reality, we just did the easy thing.  If we had gotten into signal =
measurements, we probably could have done much better.  I understand =
that there are even companies that make products for these sorts of =
things :)
=
<http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6386/=
prod_qas0900aecd8029371a.html>

In any case, the broad point is that if you know something about the =
infrastructure, you can create a better location service, and that such =
services are being created.  I was just suggesting that it could be =
helpful for the shared-addressing-issues draft to mention the impact on =
these systems.=20

--Richard


From ben@nostrum.com  Wed Feb 16 15:16:14 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 620543A6CE4; Wed, 16 Feb 2011 15:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqGyrm5us1CG; Wed, 16 Feb 2011 15:16:13 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id 3B52B3A6AD5; Wed, 16 Feb 2011 15:16:13 -0800 (PST)
Received: from [10.0.1.6] (cpe-76-183-178-106.tx.res.rr.com [76.183.178.106]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p1GNFNio011109 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Feb 2011 17:15:24 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC Review of draft-bryan-metalinkhttp-19
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <AANLkTik3VNfsT4fY2wc8HpfidPVCshGSUW1py4Jzf==w@mail.gmail.com>
Date: Wed, 16 Feb 2011 17:15:23 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3E2F61E-A91C-4665-8DF4-42B58C4C0580@nostrum.com>
References: <19DDC0DF-9ECF-499A-954E-17BABF6410B5@nostrum.com> <AANLkTik3VNfsT4fY2wc8HpfidPVCshGSUW1py4Jzf==w@mail.gmail.com>
To: Anthony Bryan <anthonybryan@gmail.com>
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 76.183.178.106 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Thu, 17 Feb 2011 08:05:57 -0800
Cc: alexey.melnikov@isode.com, General Area Review Team <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-bryan-metalinkhttp.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2011 23:16:14 -0000

Thanks for the quick response. I haven't had a chance to look at the new =
version yet, but here are my responses to your email comments. I removed =
sections where I had no further (non-trivial) comment. Please consider =
any removed parts to be the same as an "Okay" response.

Thanks!

Ben.

On Feb 14, 2011, at 4:43 PM, Anthony Bryan wrote:

[...]

> was there supposed to be a comment along with
>=20
> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the
> same ETag policy as the originating Metalink server."
> ?

I responded to this one below.

>=20
> On Fri, Feb 11, 2011 at 6:46 PM, Ben Campbell <ben@nostrum.com> wrote:

[...]

>>=20
>> -- Section 1, paragraph 1, first sentence:
>>=20
>> Is this really intended as an alternative to Metalink/XML? It seems =
like more of a complementary approach than an alternative one.
>=20
> well...you could use either, or both :)
>=20
> "Metalink/HTTP is an alternative and complementary representation of
> Metalink information,"...
> ?

WFM

>=20
>> -- section 2, third paragraph:
>>=20
>> If they must have the same eTag policy, should this document not =
specify at least one mandatory-to-implement policy?
>=20
> SHOULD share the same ETag policy.
>=20
> I added:
>=20
> "It is up to the administrator of the Metalink server to communicate
> the details of the shared ETag policy to the administrators of the
> mirror servers so that the mirror servers can be configured with the
> same ETag policy."

My comment was about policy implementation, not policy configuration.=20

Do you expect the method to generate ETags to be configurable in most =
implementations? Is that the case among common HTTP servers today? =
(That's not rhetorical--I don't know the answer.) And even if it is, is =
there a risk that there won't be a common selection between =
implementations? It doesn't help to tell an administrator to select a =
certain policy unless his software can actually do it. If there was a =
mandatory-to-implement policy, then that shouldn't happen.

=20
[...]

>=20
>> -- section 10.2:
>>=20
>> What can an implementor do to mitigate spoofing?
>=20
> nothing, I'm aware of?
>=20
> added:
> As with all downloads, users should only download from trusted =
sources.

Hmm. What does "trusted" mean in context? Does that have implications on =
authentication of the source and integrity protection of the download =
session? (i.e. TLS)?

[...]

>> --- Nits/editorial comments:
>>=20
>> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the =
same ETag policy as the originating Metalink server."
>=20
> what's wrong here?

Oops, sorry, cut-and-paste error. My comment was "This seems redundant =
with a similar statement in the previous paragraph"

[...]


>> -- section 7.1.1, general:
>>=20
>> This whole section switches to an almost stream-of-consciousness =
style. It has very long sentences with many comma separated clauses that =
are hard to follow. It really needs to be rewritten to be more readable =
and precise.
>=20
> hahaha :)
>=20
> this is my fault as a bad editor & a non-native English speaker =
co-author.
>=20

On reflection, I think my comment was a little harsh. But another pass =
with some attention to style in the section would help.


>> -- section 7.1.1, paragraph 3:
>>=20
>> Paragraph seems self contradictory. How is guaranteeing correct =
content different than verifying integrity?
>=20
> the server sends the correct content  but there can be errors during =
transfer.
>=20
> maybe this is not explicit enough. might need to condense some of this =
down.

> earlier we state:
> Error detection requires Instance Digests to detect errors in transfer
> after the transfers have completed.
>=20

I think a rewording would help, as I took "guaranteeing correct content" =
to mean "guaranteeing the client receives correct content" rather than =
"guaranteeing the server sends correct content".

[...]

>=20
>> -- section 7.1.2, 2nd paragraph: "If the object cryptographic hash =
does not match the Instance Digest then fetch the Metalink/XML if =
available, where partial file cryptographic hashes can be found, =
allowing detection of which server returned incorrect data."
>>=20
>> I can't parse this sentence.
>=20
>   If the cryptographic hash of the object does not match the Instance
>   Digest from the Metalink server, then the client SHOULD fetch the
>   Metalink/XML (if available) that could contain partial file
>   cryptographic hashes which will allow detection of which mirror
>   server returned incorrect data.  Metalink clients SHOULD figure out
>   what ranges of the downloaded data can be recovered and what needs =
to
>   be fetched again.

That's better, but how about breaking it up a bit more, as in the =
following:

"  If the cryptographic hash of the object does not match the Instance =
Digest from the Metalink server, then the client SHOULD fetch the =
Metalink/XML (if available). This may contain partial file cryptographic =
hashes which will allow detection of which mirror server returned =
incorrect data.  Metalink clients SHOULD use the Metalink/XML data to =
figure out what ranges of the downloaded data can be recovered and what =
needs to be fetched again. "

[...]

>=20
>> -- section 10.2 "In that case, this could deceive unaware downloaders =
that they are downloading a malicious or worthless file."
>>=20
>> Sentence does not make sense. Does the attacker with to deceive them =
into downloading a malicious file, or convince them that they are when =
they are not?
>=20
> "In that case, this could deceive unaware downloaders into downloading
> a malicious or worthless file."
>=20

WFM=

From cheshire@apple.com  Thu Feb 17 12:35:08 2011
Return-Path: <cheshire@apple.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CE5E3A6EC2 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 12:35:08 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id La8VD3CjqS14 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 12:35:06 -0800 (PST)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id C1B973A6E55 for <ietf@ietf.org>; Thu, 17 Feb 2011 12:35:06 -0800 (PST)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out4.apple.com (Postfix) with ESMTP id BBAF8D2C1F22; Thu, 17 Feb 2011 12:35:38 -0800 (PST)
X-AuditID: 1180711d-b7c12ae00000228a-d9-4d5d869abe41
Received: from [17.193.13.41] (chesh1.apple.com [17.193.13.41]) by relay13.apple.com (Apple SCV relay) with SMTP id 8F.7A.08842.A968D5D4; Thu, 17 Feb 2011 12:35:38 -0800 (PST)
In-Reply-To: <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com> <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
Mime-Version: 1.0 (Apple Message framework v753.1)
Content-Type: multipart/mixed; boundary=Apple-Mail-6--307386066
Message-Id: <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
From: Stuart Cheshire <cheshire@apple.com>
Subject: Re: MHonArc mail archive line wrapping
Date: Thu, 17 Feb 2011 12:34:37 -0800
To: Bjoern Hoehrmann <derhoermi@gmx.net>
X-Mailer: Apple Mail (2.753.1)
X-Brightmail-Tracker: AAAAAA==
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 20:35:08 -0000

--Apple-Mail-6--307386066
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed

On 15 Feb, 2011, at 13:32, Bjoern Hoehrmann wrote:

> As for the list archives, you can make the lines wrap by changing  
> the style sheet (or use an appropriate user style sheet), for  
> instance,
>
>   pre { white-space: pre-wrap; }

Thanks, this worked like a charm.

<sarcasm>
And of course the great advantage of having every user do this  
individually, instead of just changing the web site, is that only the  
inner circle of those "in the know" get the benefit of a readable  
mail archive.
</sarcasm>

> That is the result of some clients and users violating netiquette  
> and mail standards, for instance, RFC 1855, section 2.1.1:
>
>   - Limit line length to fewer than 65 characters and end a line
>     with a carriage return.

I'm sure that was all wonderful back in the century of teletypes and  
(if you were very lucky) a 80-column VT100 terminal, but these days I  
read email on devices ranging from my phone at one end of the  
spectrum to my desktop computer with dual 30-inch displays at the other.

On my 30-inch displays your hard-wrapped text appears as a thin  
narrow ribbon of text no matter how wide the window is, and on my  
phone your hard-wrapped lines are too long to fit so they get re- 
wrapped to that charming long/short/long/short pattern so  
characteristic of hard-wrapped text displayed on any device other  
than the one it was created on.

Stuart Cheshire <cheshire@apple.com>
* Wizard Without Portfolio, Apple Inc.
* www.stuartcheshire.org


--Apple-Mail-6--307386066
Content-Transfer-Encoding: base64
Content-Type: image/png;
	x-unix-mode=0644;
	name=photo.PNG
Content-Disposition: inline;
	filename=photo.PNG

iVBORw0KGgoAAAANSUhEUgAAAUAAAAHgCAYAAADUjLREAAAgAElEQVR4AexdB2AVxdY+gZDQQggk
9NB7R3qTKiJNQVGx++y9PX3Pjs/+7D7RH3tDRbAriqCCIEjvhF4DhBJSSUII7H++czPL3s3u3r3J
DSFkD+Tu7vQ5M3Nm5szMN2G33n6HdtOtt1P1mBhyQ2FhYW6cUYm4s0ibZWpPgTsrJpVUWgrEa5F/
y/SWkDurtGiaZmVcwCzU7sgUr2UqTG6QqFPirkDuEXHBmAuanBp35uSFumyKEl56WhpNfvMNCluT
sFmr17CBOa3et8cBjwMeB85oDuzdlUhhBzOyLDuIMzrnXuY8DpRxDsz47lsaNmIkhVeoUKY5EX7i
+IkyzQAv86WHA6mpqaSdOFlfIyIjqUqVKn4ZOHLkCOUePSpmlStXpsiKFXX71JQUniH6+vvo6tWp
XLlyul1JvhznNnj82AmKqBh+ypKxMWEdHTqwny4YfylVjYo6ZfGebhGFnzhx/HRLU4mlZ93uwzR3
9SHasCWH9hwMo8QDvqQ0qEXUoJZGrZpVpAEdY6ldfA06dvw4VShfvsTSWpwRf/DuO/TyC8/TG5Pf
oQEDB+lRfT3tS/rw/fdo29YtFB/fkG645VYad9F43d78AndPPPoIrV65kiqzoDr3vBF037/+rQut
tatX05OPP0oJ69dTuw4daOToMTT+0kspMvKk0DKGOahvT9q7Z49uBAHWo1dv8Xft9TdQeS6Pf917
F02b+oW4uZHT98TTz8o7dD5tmjWmE/kCdMW6DVSnbl09rJJ4geBbPDWRFn+5h+74uhenzb4tQnCv
SVhPCZs3UeK+fZLcBpz+1i1aUsc2bV3r3FU+oRfeuyeRPn53Mp0//mKqW6++sjqtnhP/8wqtXbup
yGlq374lTXzsngLhhB/nhnyq6cnHHqF5c+dQ1+7d6dkXX5Hox40c7piMr3/6hVYuX0bPPvkEpRw+
TLFxcdyYHpIw3Ph1CnzL/lR68/tdNGcp0YFylSimbjWq3KAiHesQKd52phylhH3Z9OXaozT5m500
sNtOuu38RtSsVrRTsKXKDoLhyy8+p80bN9Bnn3xMGRkZPCrJJVU/5vz+G91+841UnUdOo0aNonnz
5tNtN15PGenpdMXV1xTIa05ODl0w4jw6fDiZzjvvPAnvrTdepzWrV9EXX31DSdyIx48dI0Lr4vHj
aemyZXT/PXfR8qVL6YVXXysQHgzK54/Yrr76aqrLjT85OZm+/+EHevTBf1F6ehrdde8/KTy/U6rI
I7+li/7W079k8SIRfjBH2jSNR10lUPdVxv7+YjcteHU/5eyMoPGT23DewijPJj0QfvM4Lxu2bqaa
zP8OrVtJMKnM+78W/03J3B7O5o7AaeFxx7atMtKLjePePJ/69+9PGzdupC8+/oiGc+fTsnUbZWX5
HDFkoKX5jN/miPmXn02h6V9+QdnZ2dStew/pIOvVP7m+MPHhh+iH776hIecM43b/spT9xg0JBPPP
uU5Y0aZN2+nS96rR1uzVVtaWZs0rd6Tf784fveS7QDhW5R1ux3TLkENgmJGRziOCFRTDq84bExJo
//79VDM2lnr17q2HvoHNQa3bnCwQpPPVF/9LjRs3prfe+j9677136cXnnqZPvvzKlV89cNPLr6v3
0uTph2lZZlXqOq4ODWlSiQbUjqRu1SOoeZRvSrItM48Wp+TS3P1HadN2FoQzkmjrjh1000U1aFjH
eqYQS+fnsWPH6MVnn+FGRIR3EBqeqh+zZ/4i3199/bWMuv5e8BcNHTKEpn3xGV16xZUiVKZ89CGF
sZD6xw030tLFi+ngwQN066230osvvyJ+mzZuRPP/nEu7d++iZUsWUw43lEceeYTuvOc+2rF9K3Vs
356WLlmkx2nHyes4/I6du4jQ6HLWWXTrLbfQfO5Qb7sLPbxvitulSxdasmQJpbMgx1R4KQvAOO40
IcA3b95Mx1ngq7zZxVMc5sum7aG/Jx2gsMQoiq3QhKq0q0Bnja9FKVmZttGtWr+ONm3bQs0bNtTd
XDl2LH3yzTcUU60abWbeVa1alTq1bafbG1/y8vLor7l/yMDhvDFjqVHTpmIdW7s2DRl6Dr315iSa
+eMPFMffUdXsO/WxHKeRfuDOB2GDj99On0YfvvcOjR4zhtpwu530xhv0+ssv0lP/fUm8gP/LuGzX
cdseOngwLfhrPvXu24+msPC9mcvPriwqVoykrrV6UeMTdYxRO77XLNeY/q48289NNkVaxsE6wFM7
AvyTRxKg2++4g15/7TWaM3sWjeUh+JNPP6Mn+NLxF8m70Sw5LUN6dwzdY2rV4YocIyOCPG6sRnd2
fvXA81/QW1aMqEBTZ2XS1tjadNW1tem82hVoXINKlJbJeqS8DEpN9vGmVnh5GlcjnK5tGE1f1Y2g
X5pV5pHHfvabQqPPKk+5x/KkQZnjKE3fGDklJiZKkseOvYBQubUTGqn6MWHCBBozaiQ1ataCDhxO
pXUbNorbOtxo4CYrM1Oms5iWXvOP66gJC7uvWVg2atqMkpJTCPq7NJ6GRkREULWoanQxl/mtN1xP
qRlHaNfeffTGpDclvHOHDdPjNPNPrdZlZmXT4bR0sd7DfkGVeGSn0orv7jwCWbhwIa1ctpR69ekr
ArBnz560YcMGWJPG00+jezEsxp9V3+6jpf/Hgi8pihpUbUbRUKNk8xT+EaI0Fn5Oadm5ayfV5UEC
RlZGUt+wg5sOrVobrfV3jJxvu+12msYqjB+/mU59BwwSu927dtPcOXMom/WmN3BZRFSNthQSKiCM
sBVN5dkC6PGJEyXtM2f8SB1YjXHfA/+iY3nH6cKLLuKO9Dgdyi+nAzzib9SoMWXmHONBTBPC916u
b+vXrJH2e5TbkBVVqlSRoiIqcwfqXk9ZLawyRZn0mllaBXrpxbc5DfVp3LiTs83w45zYU0kzZ/xE
zZo1o4FDhtEvP/9Ms36ZQWPGXkgHklP1ZECXAzKa4fu+f95Pj7FO6bYbr6ODBw7Q3ffcI43U6M7O
L/ybqTwr0X9+pgfd8ushuqt5JMVRLk1dsIF+mnuIVq7I4YbpS0fDesepc5eKNHJALJ3Trj61j4qk
Cn1j6K1hLSg1nYVlrm/EZA6/tH1v35MkSYZuCoRpsaofbTt04ilLOcrKPkrJBw7SG6+9Km5Gjzlf
3ECAjuHeHwIQfmrXqUvxPGLJzc3jBpFHr/z3eRkljhgxgjANTWPBh7/jbNe+hW9EUo1HMzfcfIse
p0Rg8TP5rTepRs2atG/vXsLUHNS9R0/xl7/GQe07dKQKvMK5fOkSOuusbrScp9gPsP5RCUBMh1Te
LKIImdG6n/bTqvcPUrlDValRLAu+9jWocsUqpB0rT9lhadRwaCQdSs91jC85+RBFmxo0PGDBR1Ea
VBYObTmJ29dF3OnMjf2d/vjDxzOMyqKjo+kWHoGdKB9BOUcDpCPV1+ns2L6NPnj/Pbr00gnUu98A
OpKdQ/uTkqhr1650/3330SZWozRn3eQ1191AagpcmztKzPbSWSDu3beXGjSoT19Pm0qXXX651CmV
D/OzEo8A9+TuoP0nfB2u2d7qu3a54zLDNNqlcxt99KHb6P4Hn6Pzx5yjW53SKfCe3btFcIFxqRmZ
NJCHwu9MnsyVMkEYplKFRgQyDouTDx2kd955R/QGhw4e5MIczz3ZYMo4kqW8ydPKr58Dw0cyF0YY
617eGFKD5qzfR+8u3ENfz8imxPCqFNGuDuWd51th3LYjkzYuh75lPy0ZkUYjejdgP3V5pJhFCONM
Iy1/GnnCMAXGqAu0gadjd9xyIyVyWV588cU0gnVHR3JyKbJSZZry+Rfic8/+Q1J22dygsrKO0L/v
u5dmzfyZe/7G9Ozz/5URs+IZRnV33XUXzZo1i9bzYshDDz5IL772hrL2f+YPAb/75mvdHA3rcm5E
t/KMIusoRhE+R2EsrDENxlS8Z+++nI4s6tTlLPqU9Zug4p4Cb5l1kJa/xYJvXxWqFduYYurHUHTN
qlS5ViSFVypHaTuyqdP1FVj4pfnVc0mc6acaT29VW7j/5pt1W2UGA6Mb3YHpJZHLpVff/twp5dJf
f/0lndXlV1xBR0+Uo6NH/UeXJq9+n19+PoXKhYXR6AvGymwJlmh3v86cSVdcdTX179eP3mcV1euv
8BT4ed8UuHPXbtSpcycaOWwwjTn/fGrVph09+9STNGXqdHrmyYn0688z6GxecHt44pPSxlWElStX
ohU7ltGmDPc6wJbVMqlGje4qCHkeZNXbux9NZ32pP7/D80wrT70f3k/lIsvTiaPHaeHTtf0CKerH
n3N+9/XKK5bT0hUr6NjRHAoPD6e//pxDjXlUqEgXYoa0vfPWJBae++mpp5+mpawo//6776hp67b0
8nPP0EDWY1x82RXi3cqvCtfqmZR8mKfCEdS5YTW677VEyh7QmC7tGEUX8DS3b51I8TJ/Xw59ty2b
fl2dQb8tTqKHLqnGK8SHKIcr0plMJ3ihwFg/oL+7747bKItHHv/85z/poUcfo72HDot+j+dBtGPf
fj92oKO69fprKWHdOurVqxd9/sUXlBsWzgLwGKXwlpSsI5kUGxtHjz7xH7r+hhvoLBZYs36dSYdT
DlM1HpkUJJ9we/PNN6lVq1aiz+vQsSNlZuXQPl4QOcFTdjUChIDr1r07ffLxxzz6WyKNqoVBp3yc
02vMW8G4imbSZkQdGnB5a4qqUlkP6FiGRovuz6EqrGPOScum2AHhtO9Q4DoENcNuHu2CrmW+K2pt
aDP12Y2b/PzOU97FCxZIEBjhf/rppzR05BgbfquYTj4Td+2iVdx+BwwcSBqPsNXCAtpdD1YxjLv4
Epk5HOC2+vVXX+lpymN58h9ekX/5lVekvCax3nEUd55LeWFzFf+tWLmKRvBi2RJe1OnWs5ceIUaA
2w/spvWHdutmgV4qxMZQn9jzfPUy33El1t9//8NsOrtfdz1NsArPMw2bKzSoThENalBu4mFWcIZu
eoz9W0sXLZSVqoXc+0DBDj0cBOAy7qXHXXIZVWBBBFKrWcb4d/KwG5W+XuNmNIF7j0MHD9Hz/5lI
DeLjaeTIUXparfxKoA4/mXnZPC2JpJXv9qSJ3HM/NiiG9h9OoTTuMUF9oirTWDb7j3acJt7Tkw6m
pHEhuu8xHaI+La2UEIFAUWWAin/PbbfwAEsT3R70SDv3nVxpQ3liqwkIe+zwDWEJ4XfjjTfSf198
kTuNwzwdzhE30z//TJTkjzzxJF14yQQKC/ft6YOuMDUllbfNVBV3Vj8NWQ/ZsEVrGcWt27rT5MQn
JJF2jPjenDSJpvLqZEcWlMe1MN0tpvkqb7phCF8yuE5lHPGvI3mZrFLIrU4njmjU7PJwSjqU4ioN
tWvVpj08xQS1bdHCMpVw45QfaX8L/6KN69fSOeecw6v486hdu3aUwDrRn76eRgPOGU61WG0RiDbx
VhwIuw4dO/Go8aTqp169ehx/Hh1k/TAIgwPoe41p2sODBhD0nTN/+pEm/d/bko6mLMj3paRT4yaN
KZk7TaMf6AAP7DtG6YnWOkIJ0PSTzh0sFrtAkAeoi5UqHabpn/+PMnm6np1zVPcRfsIk5E6UC6cT
rBuTp8lO91WIlzWrVlAmK8qHDB3Ko4f79RCe45XHuXPnSi9wVrceYq6EmDFt7XiFcC0rTD//5BOZ
ti7hVcRITmcm6z4yWJdUIdLX01r51SNzeEk6kCyK8X+fHU3v/7yafl98iOb/5Svgfn0r0OAesfTv
oW3oAFfa/azUP7PJJ0TQaFQZTOfVXqzaYiX1hRdfkqkseIDFqOdeepWFVgoN6d9LGseS1Qm0lre7
QP+G8ljHU9tzeOuDogceepQGDxokAvDFZ5+W6fSuHdtloQSK9IbcqWFhyY6yuRKnp2daWnNdF8IC
TlvWA4K2bd3KQvgmyjPoanEAQOVNHJ2CHzR8jRufdrQcVepajpKTTjZEp+gb1WtA4ayqWcr134q6
Mc/q16lP6aySsaP5f8zmRYdddNVVV1Fc3foieOrzXs7hPOpCJ/HbjB9o1LiLqUpV58WGHcxLlGks
C1wj/6BfnPTG/+gr7tgwep/N0+Gu3br5uVFpm88zPqgn0Gahwkhi4Z4B3SDv8WxQv4GfH6wCx0RF
U0wNqxmBCtH/GcMr2dGV/N0jnP0HD/s75C/eB+hf0bK5UI4ePUwnUrJ4eFuezn0yGWJUev6Zj9YM
+lvFuHDeXNle0blLV1q3eZsypi6sG5g9ezYtWjBPemxYYJ8WyJi2226/g1575WX65afvxe4cXi3s
zVtnXnzhBXrlhefovgcf5pWfapZ+xYOLn72s3E/n6d3onvH04tRMSurp6xGXb0+hV+6Ip8SkA5Rp
0jm6CLbUOoEAVGWwdtVKycdB7qHxpwj78eAmLCxf8rAFvtetWSVO0Pv+NX++ci7PnOwsaseN4/nn
n5dtMB+++7aYY0TywYcfcQ/tK38/T4YPbBhW6TIY57/mC2+evkfxKKBOnTrSwDp27uzn5wSn0T6M
gqGGwgTTxazdR6nFjdG0Z/9ejt/dDCuFhUPD+vFUPbo67eIFhP35/K/NnVGjuvUoioXWofyRl106
e/bsTvHjLqAsPnGSmK+qSOJFiUWLFsliypVXXknHy0eKesIuDJjv3r1T2jEEpZF/3Xv3oRHbtslg
JjU1hfr07UvX8iJIDo8KzfTNtC9oIo/8c1gF1p5Hkm15I/elY0fT6NGjqR2P1I0jtKaNG1BkwniK
p/HmYOy/Wc4tpE1+9gjHmF5lGfb3itUnay6btmraWNnRxm07ivytAmtYr44oanfu2cdTgyPKmM2q
UMN6dcUMdqD2LZvLc+2mLfLET4UK4dSwbh05ClWRh8XpmUcog/8a1Kktq4zb+GAzlMJWfvVAXL7U
r12LasfWpC63+hr9ijc70/5DyVxpT075XAZVKp21bNpI9peh/FPTMyQP7Vo0o6oGfZbKGPR5OFUB
VUbX9r59m4tWrqG6cbHcaH0diHKrnus2b5WOpG6tOKpdM0ZWZrECXItHA1t37bEVgF3ataYI1juh
XhyxUUE0axhPsTV4r9+OXXQ4NY3OatdG6s7WXbtFSHRq05Iq8swBaUbaTyXlHTlBma9GUsdJNXmH
gW9KG0z81atFSXupzPUflIWRMLcBVUZOYcVEV+OBDS9K5XcuP0yfKoOFajxauu66f9ARXq2HoA1E
zRvFC/82bt/BgtBfuNWrHSdtHDsC0MYxoDC7QfgIA4OJnPwji/HcrqOjqvLCaIYunFU6YmOqS3zq
u7BPxHWIVStmCpu/dIWfADQ7ON2+sacJCu7ipuaNGlLNGN8wOpl1flt27iruKMtk+JhOVeZtMViU
CLQNo7QzCAKw3rG6dDiWV8lDqF4qDF9+5v2AtWrVkm0ou/cfFGFamHBKu5+wuYuXlSoBWNoZ7qW/
bHMAIxqrkcip5krynl00cNBg2rh95ykfCZ/qvDrF56HBOHHHs/M4EGIOHOBtQ6cDdeezw2s2bCbs
9SzLxGgwxT+dLMsM9vLuceB05MCmbebtQ6djKos/TeEf8aqbRx4HPA54HCiLHAhbtm572R4Dl8VS
9/LsccDjgHAgfPe+00Mn4ZWHxwGPAx4HTjUHwtXh8VMdsRefxwGPAx4HSpoD4WV9FaikC8CL3+OA
x4GS4wCvAnsqwJJjvxezxwGPAyXJAW8EWJLc9+L2OOBxoEQ5EI7D6h55HPA44HGgLHKgSFNgQHL/
Pe932ro5gS9cYdQYjzwOMAdwvrdx0xbUf9AwqssoJh6550Diru20YvE8yuQb32RwwuMTQejOf/rM
fIMWvPvGL3j6zKDSYgQ8wcX22fvM4VC50bh8wvLdixu4ZsAnnycAP+X7YYQf9QozOMEP3nNzjzIw
BQMG8zfKG37hC+/4FGL8RbHDB8zwJ1GdNFdpUe5wqZbExYEAdVpIwvS9+9z54lB+ECHefc75iX8M
H1aZkbS79OhHDRv7wFV8gfn/hk35YUF+bv0tAn2hoH78dirVa9iC6sU3o6jomEBePPsywgHAaO3b
s502r11BXXv2pq49+pSRnBctm8v+nscAssv5esoOgsuHhgySho4GLh9i5GvwMJH/xqfPnWrUPsEg
PsWjLjRUuL7gEEl+bGJh/Q63+e6SGBmpDiMxQUJKXEpSshNdgJrf4T+AO+XXJwThHv/lR55Ge19w
Pjv9XaKAD00QxzclrGb4/c7UtXd/Trrvqg24VVSoo3B79+6iGT98Qz0HnE8xcbX5RvtKDDnOO2o8
8jiQz4Eq1WOpdoNmtPjPGRTHt/g1aNjY440DB/Yyzt7uHZtp2OjxfDVldb97MXzeTgoxfPtGO/Lm
s4aZ/qbsjSYGS9OrUSiKlQtvR4+HUf1GTf2EnSlY3yfLJzMpIWY2N3+b3fkH5fsyyNN87yddAW+x
MSOHz581g2rXa0D1GzYxR0G8CBLcWeAMvsRl5g/fUveBo6lmrfqCAIyFZCM6bIFYPIMyx4Gw8hUo
KqYWdew5hG/YW8qzhIZljgfBZHj50vnUre9gvu0uNPfwnBQDgVNRQIi48Aw4r+PHXTi0jN6FhIW/
k1JeQrHyZXLiF1s5RrePqVGLuvcfSsuXzKe68Y387PERfjyIbTBHGUzx6y8/o9ZdB1H1GvVwDw7/
BSdAC6TAMzijORAdU4e2cz0Jpp6d0QyxyVxExcoUw8Ivr5S0J9+teqWj7dfge78jeZZqVQeDWgSZ
/fP3fClRe4qt06jUFJRNffOMTxkHwvjuhyi5sc1tlJj65ORkUS53uJX4cqSICN/tfG79F9bd/r27
+Y6ZNEZOPkoNm7SgqnzFQiAKVVqjoviyJB5QaSUMlBoov8q+uC+VUvGE6in8tRjsudYBbkxYw7DZ
GrVo3o5v19Is8fVDlVgvnDOLA+UjKspViW5ylbhzGyWsWUaVK0USIOD38+1/4RGVqF2n7lST9c3F
Rcv+nkv14qKpeYO6VK1aVTqQnhcwzaFMa3iFijKoKKCPK2KGVy+eSx17DChiKAW9iwAsJaNVpB78
tYL+czUCxP2tC/+aT10HjGPhV56O88UqHnkccMsBtBM3J44OJu2hqIg8mvzasxRT/eStXpu3bqf3
P5kqC23VqtdwG61rd1lHMuiyccPp7L69dD/TfvqTDmf633mhW/JLqNMqU0oe/YVSAG5NWEFjzhtM
M+csomZtuhiTX+T3oowAj+XmUPKBvYVOQ81a9fgKXd+9KG4DAX+t6qArHeDsn3+gJm16cqQ8jy4l
Q3S3jDnV7o7n+S7iKR9e4VRHbRnfqUgPVuOs9C/mBIUdS+crU28zG1OLZk3oiYfvo2dfeYeqVAv9
dqsK5cN04Ycp7cHDGVQ+ojKnOa1AWpRBqNOKxgn9X6gEYC7fuNauZUMaMWwgJe7dR4ezsigiMjih
ofJq9SyKDhAXYPXp2tYqWFdmazcn8qVLzjcHmgMCf63qYMAp8Po1Kyj7eDg1qdWIcm2E39GcI7Ry
/o8SZ1zdxtS0XU9537t9Pe3e6rvLtG23wXQkPYV2blpBzdg+lt2B0pKTaMMKnn40bk3xzTuJWVF/
1i2exRtJD1Ot+k1ZcHcvanAh9Z+wdDZv8CxPrboOod1bVtPeHQnUsfd5rOsKrG8qTELAh4Qlv1GD
5h2pbqNWBYIwpqeAZYgM0LCtph/G4I/xxtp/XOm7+hBXj/69ehvfxJdOnVvHU7sW8XIb3LCBvWnZ
Zt/l2ka/du+7t28m6PXSud5hb2JV3l5SM64ONW3ZTnYvwN+OLQkUW913pzS+f5u7kL75metjfBOK
jqkJowJUHGnFpVC41TBUAjCJ295N//Z1JuMvGEFPPDeJ6rUITfsCQ3xTYHfXepoZmJJ+hMs2leJq
nhzlm93YfR9MTiP4D5bAX6s66CgAMzPSadmSpdSuz0ie+nKUNnP+qCoVafHsqZKmn2bNpx8X+678
O29AJ7p+8iNi/sSkb6hBbBO67s1/0+sfzaCERN8lzq2b1qOPX5hK0378k35fVfRrJ49mZ9LrT99H
7ds0p29++o1+WX6IK3v5YPlVbO4//b/neBd9Hj37wRyacP4gumT0RPrXS9MpPad41AoN6sTQ5J8+
pk++/YOWbi547aExPcWVafS8VpXPGF8EX3tal68jBW3ZuZ/Wb9kj73MWrSPUkfJ81WLD+Pq0ZGPg
OoILyFfxtpIu7ZrTReddQk0aN5RrO3fw1amr16ynX+fOok7d+snKYIeW8dSscX2JCz/x9WvTkL6d
ac+hLNs0hzKtKmJsKQnVCDCLBf6Avl11NQLUCYP6d6clCfuocohG0HncoRRlxXpr4kHW8Vax2O+o
OFLwiZkE/BUmXvDXqg7yPsCCESmT2TO+p/otu1O58Ep89659A+X704VwrWHblk1o2twdrHSMoBaN
68lVhxUjI2TPkBqCYuuMCk8346kHzDAl2715BaUfhhANo+iavIm2eRcqz/fOHkzcQocP7KK4+s3p
wO5NfNylHNVq0JJiajVQSaaw3DQRfjAY2Lc7TZ31EVWN8SnP9+/aSKkHE6lOoza0b8c6atKuN4cb
QYlbVlJm6kGKrFSVw+J7Zes11cNTL1kZKZKuGrUaStow6q0d30rSkLQzgcrxRvBGrbpSparVJQ+J
W1ZRRsp+Dp/3w1WvRXWbtJc8fPb1r1wQyGuYfiENelPTFasS7aG92+jgni0SXpVqNalWfEueAtag
YPJx4kR5XkWtwNuVjtP6pX9QTlY6RcfWpwbNOnGay5MxPSqvoX7KCNChniG+Cnzf709zV0nUBw6n
Uxpfrn0kM4OSk3ZS+SuGi/neg6myUiofDj+JO7fS9VeMpb69/Ef/nTu0Jfz16NaZJn/yDTVq0ZGG
DupP9evE6qG14vuP8ffd7MW0fW+Kbm58CWVaVbiYUqIehGIEmJO6l6e+l6qg5Tl86ACat/BliqwS
/KjLL6D8D5lS2gyIrNybzbKyc/mS92RqXJvybboAACAASURBVD/ObGX7vTvpMF/fmWtr72QhOkCL
Omg7Aly7ahkdKx9FUbH1ZGjuFHge7woHbdmxh/UOjel4DrYSRFD71s3YbC+1b8VmXMBqZ3cqC7ct
a3xT4yptGotf4BJiCpC0bSXdec1I6tezK1f2E1xoS+ntz3+l2k270JA+7ah/t7H05be/0tP3PExH
c7Jpyte/0AEWmuqYS4+2vt58wcot1Kdzc2oYF0EHjvqG6iMHdqY+Z11C73z6NT3x0oP0f18tpi3r
ltEdV4+gnl07087de2jm7/NpxfZdIiQkYfk/9WtVo/uvvot++e0vOrvPKKpTK4Y++vw76Y1eeOA/
XDBZ9N9Jn1NepShK3b+Nbr7sHOrT4yy5wPvvpStp2szlFFOvBXXmkemxvDxau3eHzg+fPsW/dCCo
zmoeTRP+9ThV40ujV/DI5fNvZnF80RRMPmKrNpIcRITl0stP3MmXldei3/9cRF/MXEnRrNYwpseY
31C+S+Xj8nei7JxcvqLxpGI8MzmRoipXoCtvvlK8oe5s3nXIshc3hnuCpzqtG8fpwi89M5vWbNot
9a9ts/oUGxNFrVs2p+EDetBSHk2u2LCbdu45oOukEjZtp72Hs+hweo5tXKFKq3+6IQCLPgVO4wHC
pecPp0gedBgJ3+PZ/Isf5nC5NzRaFeodHSrSWxTaufcQ1a4RVSCtVmHiUvcdew5KJ2FlH8gMoz/r
EaDFEDAtLYWWL1tGrXuOZk8Qbv6N0xyZqttbdyZRy6YNqEFcFTqQmk01a1SnuYsTRABqmAZxJQZd
OGIAV7h28l4j//JxWOWwovafN15IQwf0ooTt+ym8fDkaO3IoRUZE0CeztlJtFsZdOrShNlyBE7Yf
oI5tW9ADdWvTLU9+xiOvGPafQYP7DqPklHT65o8EEYB9urSkafP2iM6nVmwN6tiuJT376F0yLdZO
LOH4LqLBZ/ek5QmJ1KxpE3qsawf6z/+m0eYk32KFJJJ/InlEi7jbtWrOw/DD1KRhHD1y302iF913
KIM6tKlPd153Ib0+fRVdNHIgXTi6Py1ctZ2XP4/RFeNHUS4Pk/9Yk0ItmzfizuEYHZ+9nfVSvtDR
kZp31dfihvrY/ZdxoR+ipesTWfh3o+aN4+mJ9+ZTMPnIPOrj+RXjR9OqTXt5xBpOl4wdTrsPHKFV
u476pUflNdTPEzL98KXDbdjXXHYhl3MT3fn0b2fQvL/XUrNWHXQzq5dsBui46dpRutW0mYspJc2n
M1qRsJNuvmQw16cKNGzI2bR8w2e0Yds+iq4UpgvAnYn7aO2OVN2/m5fCptUYNmZCMhvyjSWMVkG9
x1WLoJ7dO1v6gflvcxdQlkWbt/TgYJiHAUsRw8njzmrTroPUrvlJFYRdlHB39FjhBS54i1GrmXgV
uGDPPGfmT6ww7UE4zoRRWSDKEyFJfMFyHm3mXrx5w1iqFJlKB5NT6QArLUG+UYAvAS2a8UJJk0Zi
zjJOSGNpEFn+uAi/leu20vOfLBDzx28YSMOH9KMpv67XBej/pvxOyzcdoLH9GtPFo/pTg9rVaX/6
capc7gi1btGEvv91Aa1asYx2JnanQf260/s/LKMq0bV5xOXL6x+LN9FXv62nvKPpIvwWrdhAr05d
QnExVemKkV0prk59Stiz1Zew/N/j+X6/+mUhfb9gJ00Y0oLGnNOLnn33Z9qwK43+e8cwahRfl/m1
nHYnpdGzr39CX333Ew3o14N6d7mX6tWpSXkrWYEvLPCNdlWHgJ7UrNcIj6hCr7//Nf30y2zCKmXn
lo+zfqqOlEcw+Ujbtkty8NeyBHrr6+XUpE4VeubucTKCXbad9WyG9PhlOIQfKHureuYUxTEKp6Os
K42M8J0xHz92JKtTjtKOZOfVzIoRYRTFKCCg/QeT+RLyDD2a40dP0Jbtu7kTaypTzdjqVekw615P
aPmVkF2iIz5VadUThnjRQNETOp3tMnqweE/Zs4muvuVyC5uTRuPHjqCX35pCMfVbnjQsxJuGTq0I
U2AV5b4DKVQ/rhpF895LO0pLzyS4Kwr5VoELyrpwVDIzVYuLp+wTkXQiPdtsZfmt5fmUgMd4lXj9
1r2stG4gvew6Xq7OyQ8/MytXKjQCeP7t72hhgu8ypjbxVeiVBy9n4XmCqlf3rYQuXb2RV3p8cS/n
99bN4nlzajU6lt8DrNy4h1Iy8vTKDeEB96O6NZT0HT+WQ/061KWU1DRq1KAONYqrSJsPZYuOEQ6+
mrWKklJyqFl935aKhC27xf+hw2l018QlFFG5Go8o/febxVX1dc37ZRUqW497e2Iy+z1GmUeyefNu
RQln2ZIN9MCtE+j+2y4nTJdAGOEhjZjKQfDhHfwCZRw5yt/+5ZC4bT31u2ooTf/gJdkUnJNzVBqH
z5+vIN3ko3WTuhLHmo07Jc6IsPx4uKGb0yMOi+EnM+uoXvZ2wWdlplMGK+9B1WvE0bezl8l7o3o1
6ZLhPahixUi6bPz5NPHVT0kLswfeiI/zlSk8r1m/uUC86zZsFQEI+1pxNWnf1kOUF3FykQzTJKs2
AfeKQpVWFR6eR7h807kOFVYAasePUZf2TXnLUGNjsAXeYQ93q3amywCngAOXBkeyc3zpdeneydmK
jbupd6fmtk5gL7yxdRHYAvy1KtdyaJDmvxHDh/Ah4XSW8HnSU0Ix6/znSwBExKbdKTzNbEGd2jSl
jTsP6ggVvo5Nje8N4RnSfiTXZ1+Pe4S0A9spNWkr1a/tq9DchnRCLy3K4vzeEu+52ek0fFBPcTN2
5GCePt5Endv7tn0M6d3eN/rLjz4nFzrDMEpiXQ9GuJUqaHQkdT/lpuykoV0bUNsmtQvkV88Iv0jc
+anBu/oGBA/en3nwJp6+NaX7XviKLr39WT3dyh2nXvcDS/Yi3yosPC8//2waN2oITfnhbxpx40u0
YfN2CUfCCDIf8IgpgNEvIpVvX6jyDh7uXv+n8B12udkZpm9/e7hx84e4zHXM/F2tSgTVqRYmf7lH
UnX3UAGsXJMgqcRKcP26tXQ7cxj4zjOM5uJqRFMe64eN7qKrVpSw8JObp+q+biQDYqN7q/dQpdUY
NnOyaP8y9xG2u7ghuAtj90WMMWT+U9OyZIRnlR6M/GBvZResmZHf6t1SAB7mCIed3ZWyU/dJ5XHD
VOVm694MnoJUoQ6sn9uyxzf9VXaBnnsPptPOvck0oE9XOq9nYxrTvyUvTnSgLbsO0IEUnx7HLoza
USeoeZN4WrhiM9301HT9LyUtk4b070HHMgsCtmblHKO1m/fQuYN6U+vaGt08YTA9+eCtFFe7jl00
rsyjonCEK5kWz/mBJrAuEHSCe+hgqHqMb2Xyd4byia92jM7q2AZyhM/HFuRDqPLRuF4NmvrWRLp0
ZG9JaqO6MX7fjeup717BZEXcqgpn96xXty49+sCd8oeROUZZx3mxaO+uLaT0xBJQWAU/gWYOD6Na
RW3btOC9lusIm4KP5ebSzi3rqVP71sqaMnj6K/59egDd3Bym+TtUaTWGyy0c/WKh/o4f5Tp+dnd9
24ueEZsXbIs5Z2BPgr/Cxhlqfxt2JMlgxBguBicwN5oV5d3Ib/VuKQARcS5P2c7u0Zqy0pKk4aHx
2f1ViKwkrK5ULZaSePMqdmljzr01MYUqR/sackVefq/MWzlAlaJq6GFV5G0joMrsF/TSJ39SZnae
jOAeuuc6OpyWTS9/Ok/cq7AiOD6kRYUXyVPWC0YOE//zVu1mHRxvWcn/W5rAx6uqVpZ9UJWjfPEj
vSov02avlS0777zyGE0Ydx79/FcCL4js0e2VO6QfhDh9cfvSG1GxinxH8BaacrylBnbfzllPDflM
6YKfP6L4Rk0IU8DWrXnLDNuFc9xA/vALg/3i2/j3x7IdlJx6hL587wWa+K9bZQEjgreKYEofTD4i
K0f5pRvpBVXKz4cxPdVr1JQtRE2aNZe0xNQ0fdeIFXugPRvTGvCd41MVzu6ZuD/F1wDY7ajhgyhx
83JaxB1Ii/rRvFDTBEnmlfYcOsg6PbswYH4k+yhhug+qwFunxp3Xj9Yu+Z1W/PULT7OaUp3acWK3
78Bh2s3bMFRYYsg/6tvpGaq0GuPg4i902650IpW3vQxSWXD1xLYY+CtsvIiksH6t/GFhEKu8RsIq
Mcyt3BfGzMhv9R726GvTeUJpTdFRlQjbArYlZVHFKj5BZe0y9KZ1YqO4MrIiO/mkEjv0sfhCxGoz
DsIfTs8SYRWKeCpVrMCLF+VYd2GYuwcZMARLHCvqD6RwT+2CiiMfLqIN6CQ5cQOdOzgwKvSYwWdR
t/ZN9PCwXQhCTNG3vy2j5et2qE/bZw3m2S2X+lZ7lSNUcjQaEDrnT76fT1t5ZgGKjQqnO689X95/
+HUeLdkQeLN1qNIqkfLP2lVLqUGTNr5eUBm6eOamJ9G1F51ju/LrFMSiJSvpg+mzKKJa8DOepD27
qE59n87dKY5g7Mpzezm7a0vR90Ln/eeyTYXe9mKON3E770bp2NVsTI6XIqWyQOjQphkdOLSMFzNy
BJWjQAjFZJB0SDV6VW2LKSIONo9Hu7uS1NaH0MSXnZNHvslY4cNDB+Cb+rsLozjyERqu+3SAgcL6
ngUc9LO9WCEOYa6EXzbvAZvBm6RX8jYWN5TMo8RJn82mi4f3pAZ1fItZioM4RjXt50U8Q/AtwiG8
ylG+0T3eo3kBRtP249WRQpXWk5EghervpGmgt1ZtOhZK+CFcbItZsG4/bTeNvALF6bMPPq2BwsVC
4cYd+6lT64by9G0NUyUXyHcge+s6GPbQK1/ajgARJJTcNapVoh9nLaKKMfV5H9nJFbNAUXr2HgfA
AYwAhwzwLVC54Ug5vtCmVo1qFMNHpQ7zHr7k1AzupApuYXATFo5p1uIzpxiNJ/EKfhp36o4V3k2g
BjehSusGvj+lMCNAQ1JO6WtxjABVBnD0ccO2veozJE+MAFu3K7g/0nEEiJgxV07LzKFBfTrSrAVr
KaomNi2GSiqHJG9eIKWAA6hHbgk9/z4+9oa/ohJOguCvuCiUaS2uNJa2cEMt/FT+reogC0Blbf/M
5f13FRigskubeFq9+QAvbPgUyfY+PBuPA/4ccFPP/H14Xx4HQssBqzoYcASokpCZlUMN6tWR6UhS
ajph5dUjjwOBOKDxcSeAYVj1voH8liX7cIZIA2RXGO919Ci0HABfhb8WEtC1AESScKyoW4dW9Ptf
y3lXdYVTuigSWpZ4oZ0qDhzLzaY41ud5AtCZ41UY8CL32FE+DlrZ2aFnGzQHcnkBtwrvTbaqg7wP
EHo+93/7eJ/f2b060omsQwyNX/gtHkHnwvNQ6jiACnc0PVlQgYKpY2XRbcPGjQQ+TUfIKHWlfZom
mCtTekoSxTMmpFW9YjxAF0pAY97Y/SHenHzeoB40e/5yPusaSREMAXW6QLwbk+q9lwwHcIQyj89j
52QkU49OzegYg2UEXc9KJuklFuuJsEgGu2jA0Fy7KCq6ZoH25Ft25F+/9UccBsungi8+O2wmtSWf
naMT8WsdBkA5rMWHs0w56cfBHTvyt83/0h8GW/3V3w+wRTNSk/nwQDzzLYLrYEEswbD7np+ie7fl
k4VFhfDyVDe2Gq3buIO27dpHGZk+hGcLp55RGeNAJQYuqBVbnQ/dtyDWaslWljLGgkJltyZv4C6n
HaPtO3fztaBYufY1TU2DAOJ3eeQ3cv7EWxie+RLF9/C5U2bwxv/hSNzjVUjC9IWhS1EJAPvldEfq
RfwjAcoKxxTDWQZwCsSN75dt/aRpvp08TtqF5cft8+gLURfl7F+c5/9IcPnu8Y5teSAYiUt5sgHM
JSg2BVPYNpLvQGmKkV+5CgyRl6mnHf4Vhd37XOEEIALAHijod6pV4eNdFTzlrWJqWX9iz14Wo+Ac
4suFsInZI3ccQNOuXCmCYqKrMkL2yRMwIuRE1MCFj/LlgPrUBYNuwC8n3Zz0B/uT5kbX1u+6YDJZ
h4eXk1MaJ4XlSQf+47CT5nZv/mH4BCLc+pv7fOuCPT8woxvpEFjwKfmKk0QpfJw0i49Hngw132P+
I6hFEH+vPoinJN6rhT+PPA54HCgaB9BIcW4cfx6dGg642gd4apLixeJxwOOAx4FTy4HwYIerpzZ5
XmweBzwOeBwoPg4UaQpcfMnyQvY44HHA40DxcyDcVjtY/HF7MXgc8DjgcaBEOcBTYI88Dngc8DhQ
NjkQ1qHHYE8Gls2y93LtcaDMcyCM99V4ArDMVwOPAR4HyiYHTl6IWjbz7+Xa44DHgTLMAU8AluHC
97LucaCsc8ATgGW9Bnj59zhQhjngCcAyXPhe1j0OlHUOeAKwrNcAL/8eB8owBzwBWIYL38u6x4Gy
zoGgBOCuXbvoq6++orS0tELzLY8haqZMmUJ4uqGffvqJEhMTLZ0mJCTQokWLLO2CNfzjjz9o27Zt
wXrz3JcgB5YsWUIrV660TEFWVpbU1ZLa5ZWRkUHffPONZdpOteHs2bNpz549BaJds2YN/fXXXwXM
y5JBUALwP//5D1100UX08ccfF5pH2dnZdMUVV9DRo/aQP5dddhlt3LhR4vjXv/5FS5cutYwPFez1
11+3tAvW8L///S/NnTs3WG8l4n7SpEn0/vvvl0jcp1OkH374IX355ZeWSdq/f7/U1RN8IU5JEDrt
Sy+9tEhRh6qc0YbUQMHYttB+3nzzzSKlsbR7di0A0aOisl1wwQX0ySefFGu+f/nlF0pJSQkYx0MP
PSSjyYAOzzAHq1evprVr155huTqzstOmTRvHTt5NbkNVzsuWLaNx48ZJlG7blpv0nQluXAvAr7/+
muLj4wkjJUw91AgNTHjnnXcIo8P77ruPGjVqRF26dKHff/9d588rr7xCHTp0oF69etEXX3yhm1u9
jB07ltLT0+maa67RR2SY6p577rlUp04dGjNmDKWm+gBYP/jgA3r00UclmCNHjkj8zZo1o6ZNm9KT
Tz6pQ4VbxYMeceDAgdSqVSu69957KTf3JHIxKkzfvn0pKiqKOnbsSN9++60exLFjx+jhhx+mFi1a
ULt27eipp57S4wkmDdu3b6chQ4bINK1z587UuHFjevzxx/V47NKAUQHKAmoElXfdk+EF+evRowfF
xMRIpzV//nyxRRpvuOEG4RHifeCBB3RfCBt5U4Qy7t+/v+4P5WvFXyeeqLDUc8WKFXTJJZfIyL1t
27bCx7ffflus9+7dS/369SOoPTp16kTr168XdQvqQlxcHDVo0ID+/e9/+wmWgwcPSv5q1qxJffr0
sZ0t/PDDD8IPhDFhwgTCCBGEcoA/1MuzzjqLunXrJvE//fTTOo/+/PNPcRtM+e7YsYMGDBgg/pz4
CgcYyYLPtWrVEkF14MABclPO//jHP+ijjz6SOA4dOkRdu3al77//Xv9G+WPGdeWVVxJUPFZtCzOx
W2+9Vdo26oPKqwRSFn5wFM4NDR48WHv22WfFKTNa44aie3viiSe08PBw7YUXXtA2b96s8TBbY8Ei
9t99953GlVd79913tTlz5mjdu3fH0TstMzNT92982b17t1atWjWNdY0aVziNhYzGQlXj4bq2cOFC
jQWpxoJCvCDe8ePHy/v//vc/jQtY4wah8VRWY4Ei8RnDVu85OTkSxz333KMtX75cu/nmmyVNPK0U
/9HR0dp7772nsSDWuEJpVatW1Vjoi/e77rpL44qlse5EYx2KxsJeT08waeDGrZUrV04bOXKktmnT
Jm3y5MnCQ+71HdNw+PBhjadW2nXXXadxQ1FZ8nvCnIW39tprr2k8FdMeeeQRjRuXdvz4ce3VV1/V
LrzwQo0bvsYCTuPOQmMBL/55RC1lpwIDb5B3kFPenHiiwlJPboiSb26UGgsJDfUjMjJS4w5TYx2s
8ICFkNQX1qNpPOOQMkaewCfw+8EHH5TguOFKWMjTunXrNFataHXr1pW6hbBQz1jXrM2bN0/KmwWN
xnps7e6775Z6xdNjDeXA90xI3eFOR7vtttu08uXLS5ysX9RuueUWjQWjxOfEA5U/9US4FSpUkE8n
vqJ8ateurW3YsEHbunWrxp2Dhny5KWfuACXdiATtBW3w+uuvlzh5tqZxJy7vaEP4NrcttB/UQbRr
pBd1ikeu4qes/GD0EpBQUVEpwEAQBB0EDCoQCIzknlve8QNmwj2PqoSpPMLS7dDYnAQgHPKoRYQd
3lF4L7/8Ml6FHnvsMWnA+DAKQFQyNA40BBCPJqQSyYfph6cBGo9mdVPuBbUqVapoEIA8WtV4dKfb
4YWnDxoaOfemUqlZqazbT58+XYQIDIJJA3gEPuzbt08PC3nlkYhjGuD4xhtv1CC87Qj8at++vW7N
IzTtmWee0VitoLE+VePRj9glJSVpZ599tsajKvl2aqh2eQvEEz0R+S8QgMg3j+J1q2uvvVbjUakI
QNgtWLBA7CAc8A1BpOjzzz/X6tWrJ58QFDyrUFYaBCaEwK+//qqHBQGIjhE8U4QOsFKlShoEnioH
XiQQa/AHccIc9Pfff4tbvNvxAHZmgn83AhBpQAeAjgDtBXnYuXOnBBeonDEgiI2NlXZ4xx13CA+b
N28ufm+66SaNR7HyrgQgPoxtC+2nd+/e4gY/rFbR261ueIa/uJoCY9GDewoaMWKETAmhOMUQn3tW
ris+wtRCEY8a+MKU4zKthM5BTQVgj6llsMQjQN0LCyqCPtJMUPRC74IpDKbq3OD5VqhIszP5Nqcp
IiJCpkew3LJlS4E0cqUiTEuwSozpHhTJmI7jj0ePur4ymDQgLu4kJAy8g8A35M0pDT6Xzr9IJwtA
3RELBeJRE1WvXl1W37lhEaaMQ4cOJRbAujvzi3Gl3i5vgXhiDhPfPEojHmXrVlBZsDDWvzF1A4EP
4AnUJ4qgesB0Ty1u8MxEWYlbqDSSk5N1M7zwyFGmuKrMUJ9Qn9U0GOXAQlX8oM7gG3UJBN6hzEF2
PBDLIH6MfMW0m0dgdPvtt4u64vLLL9frU6AgwSeWT6IqwAIed4riFyu+v/32m7TXQGE0bNhQd4K2
pdqtbniGvwQUgGAwdBQ88pKVR6w+YjEE+rNPP/1UZw8qlBVBuPB0S7eCPi9YsgvbGA70gkgbFk94
+io6D6VbMrrDOyo5Gq6RVLogJIzphRssOCC/NWrUEC+oXGiw+ONRsb4VI5g0ICC7fDmlQRIQ4Af6
M6RLESo1eAEdFvRB0BVB8GEbBDoMRbhyUAkWmO3gTk6RXd4C8UT5Nz6h40W9UsRTbdEdq2/1BB+Q
Zgg8RSgL6MsU74yCE/osnkYSj2qVc3kijTzt1csMfnimQEp4qrD8PBk+VFrteGBwavnqxFee6tLV
V19N2GLGo00RgtDJuSGkG7pxrOYiHAjtQYMGyS4NdKTQ6QUiCPuyTNZSy8ARjPKgnOYhtjQWNBj8
XXXVVTRt2jQ/hbTBm/6KUeNnn30mDZKnHiKcdEubF/S6rCO0sbU2vv/++4l1XgSBO2zYMFmIwV4s
KzrvvPNkIQeKYRD2NqqGhArFUwt9fxQECU/JpDfFCAI9NuvrJN9onBgBIm5QMGkQDzY/TmmAF/AH
cdsRVuohVNTCBzoEdFZoyNieMXz4cOETRkazZs3ShREWOLD4gvLGqIf1tnoUdnkLxBM9AMML0q4W
wyDQUA4YjZoJDRqjeWx1wiIVhPPUqVOJ9aa6UyxuoIwg5N944w1q3bq1PppTjlAHWVUh+QIP0IFj
cQthBkN2PAgUhhNfsViIxQnwBKN21s+SqreByhnxIm+sA9VnWVhYe/HFF21Hf4VpW4HyV6rtuUI4
EvQzaqHB6BD6JBY2GgtB0cVh4UMRFM3MFFFG83RE41U2ccuNReOVRNHT2C2CIAzoL6DEnzlzpugA
sQCi6Pnnn9dYgMmnUQcIXQ30G9BNQv8F3ZbdIgE8YxEHaeQpgCi5zznnHNEBwm7ixImiHIbuBAsi
vMINYyEsfEDPAsU1Fmu4xxV9IyyDSYNRR+QLWdN69uzpKg1YmEHc0PvY0XPPPSf6HFZNaDwSkEUb
uMUCEvjEAkD0P8grFqmgd8MCEvIM/ViTJk00XiHWF0Gc8ubEE3P6oAPk6beUD/iIRRbUCRCPyqVM
oLdThAUtLOBA74eyAr9Rp0DQAWKRBAsf+OMRo8ajc7EzhgWdH+owdHKoH+DJjBkzxJ25HJAXHhWJ
HX6gE1TfTjzQPeS/GMN14iv0fjygEB00yp9XxmXhDcG4KWeEzSNBWTSCHywUoV7zTgF8Chl1gMa2
hfZjbLc889HbrfJ7pj/R+xc7YbEEFYJHWa7jgoDlXt21eziEAhmrtU6CzxggFiB46qsv5hjt0MhQ
+fnUi9FY3tFA0VCwcmemYNNg9m/8dkoDT3E0/DkROhksJJgJK4w8atKNsSiChRJFUMIbhZAyd8qb
E0+UfzwhAOvXry9GaHBOHaHyBwGGhRBjmpUdnogbZQFh4kTwjzLFwk1hyYkHxjCNAlCZ2/EV9Rzu
1QKeco+nm3I2unfzXpi25Sbc0ujGQ4Qu1eP30pd43golJ4EwFT9TCfo43ikh03yzPvlMzXNpzVdA
HWBpzZiX7tOTA1h9VosPp2cKi54q6FCxawB6R49Obw54I8DTu3y81Hkc8DhQjBzwRoDFyFwvaI8D
HgdObw54AvD0Lh8vdR4HPA4UIwc8AWjDXF6tLLBZWjnFJlPsHeRVL8IGagU1pOxP5ZNXJSUtRY3T
mKeihqX8Y8MzH11Tn97T48BpxwFPANoUiRM+II5QARcRG3OxCz9UmIQ2SXE0xrEnHJ8CrVq1ioAQ
Uhgy5qkw/q38IG045eCRx4HTlQPhp2vCSku6+IB8iSYVJx9wwgbEm2LlZEeJJsiL3ONAKeJAwBEg
jkvxDnW/LOGoFY6HYY+THaYdpj44d6qIoXbozjvvVJ+Eb96NL3hmfDpBcOgUaAKmlMD9w6F5HJEC
/p0iHIPCsS5spYA9w//ox+ac7ODfRoJMSwAAIABJREFUDhMOdk74gLC3ow8MmISBcBFx3hPHnngj
sBxdAlS5IitMOGXn9MR5XQBMoJwYukkO+AN30Y6ceGv0Y5ceXIdwjQM+nzEM9Q7MOpxLBQgBcCMV
OaUFuIFAVAYOIM4uQyXhkceBkHMg0O5t7MBXsD7KLY4w/fzzz7J7HcdwrDDtgGsHf3zGUQPcFI62
4QgWdr1jJ37FihU1QBDhaBvsgFGnYKZwdA7YazgJAZwzHJ0CNh8Ix7b4bKVAGWHnPLDagNkWyM4J
Ew4nDXC0zAofUAI2/RiPWRmP4+Gdz1pa4iIiDhwvY9QPjVFOJF+IE/zFaQ0rTDhTtJafOEHAlUJ4
zEjdGo4b4oSFHdnx1pgnp/Q44fOZ41Rp485MyosFofAHsEsgu7TADkcZGcBBYyAE7a233pJ8BXsy
COF45HHAiQMBj8IFEoBofDhSpgjnDoFpBwLmHs5mQvjwiE1w87hnF0GH86kgCEC4w3E5EI5k8QF9
eccRJ4By4swxcNNAClxVPvgHghhnQEFOdk6YcE74gBKw6ccoLMwC0A4XETh2ONNqPK518cUXawyx
JHmzw4QzRV3gUwkZWIBvOOdqR068NebJDqMOghHljTqhCPlS+HzKTD1V2uBPEQMcSP1wSgvqQsuW
LQWDUZ37BXir8bieCs97ehwoCgcKpQNkwaSPRAGnA0QQRQrTDt9AXQHENhAoANMD1A4chcIueaBY
KAK6DCCDQHDLjVHQXLjhCDS6cqee0HspApYcYIqUHszODlNEwFgx8KTyqmPCMYCmjqYBSyDKKEw6
3bHLFztcRMDLI51AN1EE+Cagfxgx4XCMCmoFTBWNWG3KT1GebniL8O3Sg/Q74fNZwUqhfmDKr0jh
OTqlBXUBqgWgrwAmHlcsACKKhaIKxnt6HAgJBwLqABELVjsVcS/sd02lVaVXbiHkANSIPwhANGwI
QEAAGQWgEn7wB90PdIXAr4NSnxFhRDga3aAhKgJ8E08fiafUYmRn54QJ54QPqOJx+7TjB+IHLBJg
t9QfXx8gd6xA6BUWE85tuuDODW/hzi49bvD54N9IdvxwSgs6BnQUuLIRuIW4w4Sh6v3wCY1xeO8e
BwrLgYACkPVWIgCxYAECRpxxBOgUMQQeKjq2Z2BEhYULCEOM8OwU9RipYcQAxbeKDw2Ch7l6VAA+
xTeEHdCqEY8iOzsIXDtMOCd8QBVuUZ8Mt0UQeMDfA4EHfD+KdAZOmHAQlsgT9ukFIta5yiU4xg7L
6McNb+HeLj1u8PmM8Tm9O6UFnSxAXTFqxiIIELgx8mTdsVOQnp3HgaA5EFAAsqJeph9YYcX0DgIM
ldMNodJieospDBon318gK4FY2cXUyIqwwoxpD+O2EaDoAZgJAcW4hLpzCGCMEDD9BXAqgFAV2dkB
Lpz1kxIu/OGGM4By8gKMTH9xOxoENFYqAacPgRVKwtSclfmyuo18IS24HQ37Cc8//3wRcBjJomPA
zWe4lQyEjdZYMTeObO3Shakr8mM3dXbDW4Rtlx6oBnAlKla70THiD6qHwuz1c0oL6g3KC7fGoZPA
CjLukoYA9sjjQEg54FaBCGU0cMROFeGGLGCvgaAUxyVHICx0ALyTBYLc8CWG+T9OdsqdEyacEz6g
8l/UJ1azgVkIDD4jOWHC4dY6FuxG57bv4BVPYW3tYWHHW6Mnp/RgRRsLIXb4fMZwAr07pQW7BBYv
Xiwr3IHC8ew9DhSGA6UODQajQyxk8G1WBToCJ7sCjkuJAUaAgLaHHswjjwMeB0LLgUKtAoc2CcGF
hukz7ye09ORkZ+mhFBhi2udN/UpBQXlJLJUcKHUjwFLJZS/RHgc8DpyWHAi4CHJaptpLlMcBjwMe
B0LAAU8AhoCJXhAeBzwOlE4OhFQA8k1p+n26p5od2P7y448/ymXfiJtXrWXPIvYQliQZcfaM2IG4
mBv7I0sjYQ8fXxF52iY9VBiJp20GHRIGgA3AkBWWjPU1mDAK6y+YOIrDbZEFIDapYsMqCNh4b775
ZnGkM2CY48aNI0BTAa0Ef9hM/dNPP/mdYgkYiMmBMW8mK9efRpw9I3YgLos3XjzuOsDTwOG3334r
t56dBknRk2DEQoQAUBiJuoMy8sJny4sE0Gusr8GwrLD+gomjONwWWQAykADx/sDiSFtQYWL0+eyz
zxKDEciJC2y0hsDhS76DCsfoONR5g4CeMmWKMQrvPUQcMGIhGjESQxR8qQkGR0MxGPDIHQdcCUAw
FZhzOGXQsWNHwggABGw7wJ5fw/hwOCECwpQTB9dxUgM7+AGGoMgODw/XCEJwYcSGUyaMIqK8+D3t
/F911VVyZhSnOd577z05OYF0IM04KYKjVQ8//DC1aNFCTmA89dRTfkfrXn75ZTnVgBMUSDvOwprz
xrBecnoE53lxkuTJJ5/0C8MvoTYfRuxAoxOEjRMhL730khjb5dPoR73jqCFOlACVGicnkEeco1bk
FJYTth/SgrttcQIHo+n+/fsTQ5ypYP2eTjiLfg7zP3hzs+zjBC8BeMAQYYLViKm1HfYkvNqlF/6M
WIgKIxF+tjtgVhrDxOkc8BG8mzhxIqwsyY6fDN9Gw4cPl/oPjzgxM2rUKP3bqo7BnV14sEPZWmEi
OtVFYHACOxGYmTjRY6R7771XPzUVqMzQrnF81Vjm33//vZxkMoZp9/7GG29IXYyOjhY+4OgnKNTl
YRe/a/NAu6e5Z9U4ExoLFsHkYyZofFRJTjPgJAAw7YDZB9w/QEPx4XeNR2KCFchHuDTewyZROOHh
MXMEJ46PzWk8LdRPgBjT5uQfcEvcSDWeVgqGII/8BHsQ4eJEw1133aVxYWp8uF7jkaLGR/M0BmGV
4PkssZwuWbhwoaSZQVk1nLww5w34hIDUAj9Y2Gt8VE9jYAdjEi3fkQYuDDnJYYTO4tGgYAPitAsg
tPg4maTVKZ9WEXBlF55zxde44Wu8SVwDtBaf59UCheWE7ccdgZQJA6MKL7jxCGwZ63oEwoxHGZIc
J5xFq/QC3w915pFHHhFcxAcffFDSz+ed5XSJHfYkwrJLL3d2mhELUcFwwQ/eUSetMCthP3r0aA14
hTyF1iZNmiRpQzlbkRM/UY7Ae+SOVvAd0WZQD0F2dcwpPPizw0R0qouAo/vyyy+lLjCAiMZ6ZwSl
8UBAq1y5srZ06VKBp0MZoGxZAGt33323Bn84RWSsr7yvVkP5KAJf/vnPf6pPv6fRH89ypK4Ayg7l
jbrDnbOc6AllefgloJAfGMU40iuvvKLxqMLPDSo/hAoIIKcQHiA0cD6hIe/4AfAlT0UFA88JD08x
D0fc7MjJP/zwGV4NwgCE41N87ljeAb6KRqXAVmHIoAiCTYh3pBfpVgQBCSEMMuYNAguCEyCsIBzN
C3TkDO5U3nCUzSwAeeQqoKDABYSgBgXKpzgy/CDPELA4GqiIR20anxxxDCsQth8E4LnnnquClPSh
0TB0mJ8ARKO48cYbdXdo1Kx20PEbdYv8Fz63XQCzkE/waIEEYKD0GrEQzQIQ/LHCrFRhqmOWSCKP
xKWjM6cb34HKhmc7gl2JzpbvZtGDsKtjTuFBGNlhIjrVRSUAEfnAgQM1nqlIOhBX+/bt5d2pzIz1
FQISaQBBwKNcjViQYpH/Y/SH/KIjUIQ6wfBnGp9okg4pVOWhwi/KM+AUmNGLZSrJidYJ0wVg+lmR
8SA+sN+4YRODgMpCCQ70Y2oM/ED8AYePewg9GAy57ciIp2fn38ovF4xMgbGgofzxCE/XW8KeK4bu
Fe8AHzATlMs4kQFwB+QBgAmA0SoKYZqE6TZWhLGKDSpMPnE1AKYaijBFB4qMU1goV4AOdOjQQXmT
KQvKgxufmLVq1Uq3A6wVACoQrpEw/QSohOItd0Q6zqLRnXoHIg6PbNSnPJ1w/hRf3KTXL1DDB/TB
SJ8i5Burlih7qHXAP0VQxdiREz/hB2oCnEaCykiBWcDcro45hQf4N6hM+Ny4gIMAFALwYMBRdFsX
oRrC7YUglJECFHFbZtAl8kxIpsFQT0Fl4QYIBWXFaN8SL37QTtBmlMwIVXnoERThJeBROGDAAZHF
SPg26xeUPTJnRQoPj3tn3RqNDQ0Lup1A5OTfyS/8gQCGqgQd90h6YaBAUciKUHgQSOb8QXgDlgp/
0HdCnwJ9EU8flNegn4iDe2YRQhCo0D0VJp/Q13AvqIPK8tRDUG2cwkKeoUtCGeAMNQjlikaMMgEh
z4ogMDZs2CBCEBh9ihAHQF15dKuMaOfOnX4CR7fgFwhqCAQjGbdtKOELeyP2pBGL0C69xjCN7yo/
RjO840gldMRomCpMY10wu3fiJ9zyTEjqBhZhAGirdkTY1TGn8KDDhtCA0MMCDxb0gIkIXE3kx01d
hF4Z+lUIZGyPmTx5smTJqcygj1eEzgF1FDByaLfGO36UG6sn+ApdnyJsS+LRttQt5CVU5aHCL8oz
4AiQp0FSsCgIECoILkRSgKbokVCJApETHl4gv7AvrH/0/ICJQuGjUqHRYwQI5TsIjRe9Ixo17Hlq
rwtEY97gHrBbgIQaNmyYQHyhYEHY0gKhGSwBXgxArmgoWMFGGIXJJ/KEPIAgxHhaLCMRp7AwmkUD
w+IJRugQPFOnTiXAninCKjgaBIQrhD1PgQuMAJxwFlU4xicgx1hvSIwCI8bAR2Tdpbw7YU8GSm8g
LERjGtQ7Rp4oAyjsIWzR+WFUbkdO/EQZYMSFlX6UBQQUwHxBdnXMKTwnTESnumhMOwQYT3flqlRg
ZgJuDRRMmQGGDJ008uJ2axFkBtqEEqask5SZE+DwnCjY8nAKy7Wdm/kzj0xEkQz9ApS73Lvp3m66
6Sa51IgZJDounmrqdtwLiH4KClgQ48jJZUg8lJYn7sMA8YhAXygQA5sfO/9wzlMvDfowkFEHiG/o
9XjaLhcPQY/FvagOr8WjT40roug3cLcFlOJQ9IOMeeONv6IT5Gmg6FKgoOaRg7iDvvHVV1+Vd/OP
MW9mHSAuSFLEq30ar4CKrs0pn8q9eiLPuDQK6UEesUDFWIfK2pbncIDFHOjfkG9WXQhf1B0c0AEi
TCwugbew543mEi7ucVGLINDvjB8/XvSs4A0LFI3Bc/X4rV6gw4I+iUdKGu6G4am26ADhlkc5UhcQ
L6/Kajx6kntfYOeUXsCMIX74M+sAzQsr4DMLKAQpiwJYXEEZQteNxSiUhR3ZlQ0u5uIdEvqdL9C9
IS3QEzvVMbvwED/aGY+WNCwOos3g0i6QU1006gDhFu2ShYHGNyviU8ipzIz1FY5ZEAtveIXb59nm
1+gPdQiLiViMA09YxSALL/CKsglledgkx7VxwEUQFRIyhRUkFKaZgBOolPhmO/M3KqoVHp7Znd13
Yf1jEQKCkKdxlkEDew5hm8mYNyiCkXYl+JRbrLzytgL1GZKn23xCAKKhgdDhqM7GmAinsNAYrLD9
IADR4NAAwDMo5Z2IZwZSP7Do5IZ46i2rwAiXtyvpAgl+UdfssCft0gt/CMvNwhTcguAeecNFVVhJ
BjEYrb5wIAYWP078tHCuG9nVMafw4McKE9GuLuqRuXhxW2ZYPFEr2i6CFSfgLbAeeUbi+jKrwpaH
2zRZuXMtAK08e2Y+DmDFi6dAJcIOowAMZQKUAAxlmHZhmQWgnbviMGe0cdkGwgsSMnLF9aQYYXnk
G61hyw1GxhhAnAo61eURUAfoei5dhh1iYzXvsSoRDvD0V6D8Qx05T6VOGQ4hb5sQfWSo8+AmPKX/
wyZo6ImhuzNvxnYTzpnoBno/LKDw9Nn2CotQ5/tUl4eHBxjqEvTC8zjgcaDUcMAbAZaaovIS6nHA
40CoOeAJwFBz1AvP44DHgVLDgYACEBtgsZucFaByReOiRYtKTeZKIqEev0qC616cHgcKx4GAAtCI
84Xd6Ng465E9Bzx+2fPGs/E4cLpxIOAiyHY+0oKzpTiTaXfM7XTLVEmmx+NXSXLfi9vjQHAcCDgC
NAaHw9mPPvqoGPEOdjnvyKcO5NwpI6UQQzDpzp1wzhhlQs4F4vwlDlyrQ9K6Z8OLHRYhBA2O92B6
DtxBPgVADHFl8FnwtbBh4VgS7/WzxRMsGJPPJFT8sgvfM/c44HGgiBwItLnReMTFeJQL74C4YdBM
jRE+NByBw5EmEHbrAxsNR734fKXgBeIIGk4cAIIIm02xAx87xXHcCZturcgJixBHanBMyA7nzRxe
UcJywhM0xxNqfpnD9749DngcCB0HAp4EcWrQAPJUBIHEU+SA2H88CpMzgjg+hiNIONLD6CEqGL+n
ExahOu9phfPmF0j+R2HDCoQnaI4r1Pwyh+99exzwOBA6DgSEw3IaYAJJQxEw1qyw/5Q9kFaAigFk
FiCfAKYHWHiYxgI6yIgjqPwAnQOw9kYCFqGCLLLDFTO6V++FDYsFmo4nCIw2EPKJv2CpMPwKNg7P
vccBjwPuOVAkAWiH6+WEcwahx4gbxAftBbrpxRdflHs4FNyWMemBsAjt4jeGod4LGxbyArLDE1Th
u3napdeJX27C9dx4HPA4UDgOBLUI4jYKJ5wzLJQAowz4aQAoxahQ4eqZww+ERWh27/Rd2LAC4Qk6
xenWzolfbsPw3Hkc8DgQPAeKRQACEfett96SG6QwZcXBehw2B0ItEGaxWRjgjL169SKGH/KDDzdm
AejEAJgEhDqEJeDbgcRsnEoa3Tu9FyWsjz76iAAOyrh4xNh5cpMX4/85RReUnRO/ggrIc+xxwONA
UBwIuA8wqNBMjjGyw70H0O8pyHE4YdwvMWdVplzlaPJW4BPTZmx7wZWPQCUuChU2LOj8+IYtAvKw
8a6MoqTF7NeOX2Z33rfHAY8DoeFAsQrA0CTRC8XjgMcBjwPFw4FimQIXT1K9UD0OeBzwOBBaDngC
MLT89ELzOOBxoBRxwBOApaiwvKR6HPA4EFoOeAIwtPz0QvM44HGgFHEgoAAEUMH3339/SrKE2+dx
gfLpSlgFLg48xMLmG6vGAIPw6PTjAPa7ns51OdQcwz3PfEFXqIMt9vACCkA+cyt77wqTkkmTJskl
M05+GURBtsTADd8TTHz1ppPzErUz4iG6yZtTYkORb74y0fVl1U5pKU47Yz4LG09ReV3YeIvi74EH
HqD58+cXJYhS5ZfvbCYGRilVaUZiAwrAouRo9erVctzNKQxsMOY7YJ2cnDZ22JQ9ZcoUSY+bvDkl
PBT5xgZqRt5xiqbE7UKRz6LyusSZ4CXgtOWAKwGIDcsALIiPjye+oZ5wdR1o06ZNBa4QvOCCC2jB
ggWEXhvX6UFgKAxBMxdwJI4vhaZrrrmG0IOAMM3EsTUcQRszZgylpqbq3vjycerRo4ecBJkwYQIB
fRkULDbgP/7xD8LpDhBf0E1du3bVp/n4RhyMAkNXXnklTZ06VU6vPPPMM6Tw/azy5oR/KBEZfkKV
7x07duhgEcgP8BCBWzhgwABDbP6vdpiIbnly8cUX07Rp02j48OFUt25dGjVqlIBa+Mfi+zLn0w5X
EZvMgQsJHitCnXjuuecC1qMVK1bIKSMglbdt21Y2y7/99tsSzN69e4kRiwgqhk6dOhFmM2lpaVLf
4uLipB7hJBKAOkAvvfSSjGKuvfZa4svmBbMSwleRXRlbxaP8MOoR8V236lOed9xxhyWyutsyMNdL
BPrmm29KW8ShA7QNtAmQU56ceAe/duUFO/DxqquuEnmAdgqwkVJJgYBlcPE2Z0zjiq9xZdBee+01
rVKlShr37ILvxycj/ILgo2/azz//rPGJC+3SSy/VrrvuOo31iH5u1AdupgdOIOux5GJxPjKn8XEz
uYV+4cKFGh9907hRi/N58+aJWwZT1bgiymXWcI/b5AGNFQw2IAtkjRunhIu4gWt4/fXXy/eXX36p
4aJuEAtGjRuChovPgV2o8BDNeXPCP5SATD+hzDfKBvT8889rUVFRGp+t1mbPnm2K0ffphInolifg
OTcybdasWRrKBBiQ8GtF5nw64SqyzkxDXWIViMZ382rcAWpIr5nX5nhQP1H2LBQ07hA0wKxFRkZq
CA/QZCjbbt26ae+++65Ar3EHrY0fP17qJHfgGgP5ag8++KAEC1xKuEcdQ9r52KXGnb7GRzcdMS6t
4kHd+fzzzyUehMnCRuJgva1WsWJFbfHixeasCB8LUy8BJwf8TR5ESHyoy8DnBDnlyYl38OtUXldc
cYUGODzEyeDIWnR0tIZLzUsbBcQDVAIQQkfR6NGjRWAA4NROAMLtjTfeqDHqi/Jm+YyJidEg7EBo
XC+//LLu7rHHHpMGDQNUDISnCEIHghj4gsFiAyK+2NhYEZ7cG2s33HCDBsENuummm7Snn35a3lGJ
jelXAhCWxryhovNRP8E3FI/8gw6DdZrqs8AzlPlG4BCAaKzoEOzICRPRLU9QRjza0qMAT3j0pn+b
X1Q+3eAqosHxKE5j5B5txowZelBGXuuG+S+qfvJMQbfiEZyUqcJm5BmJ2AGMFx0G6q0ilB2f75ZP
CAuefSgrjUem0un++uuvIszsytgcDwJQAhDvAO1FJwpCfC1btpR384/bMjDXSwhrDE5ADDKiMdyc
xjM1+XbKkxPvnMqLr8fQVLlKJPwDgVsaBaCrKTAADTD9VcQ9qu20B3eHFIUAOKCoSpUqApyAb0y3
v/jiC5kaY3oMd4CXUtPgYLABMcXlMpMpEabegOaCHhKLCoC9GjFihEqCTIf1D5sXnHfGVB08Qtrw
x41Gptc2XgoYFzbfxoBQLgqz0Giu3u0wEbHSHwxPMD1UBBxIqAsCEQsJHVdR8ejmm2/20/9iCo80
YrpqnjY6hY+pOI9AdCe4wyYpKUn/Rt5ACBvpBaiGIpwvh9oD59NBxnPeqF+4agFhuSljFY8KWz15
tETTp0+XT6gPLr/8cmXl9wymDIxx8YiSeNQqU3rohaEqMpJdnuDGjndO5cWjV1EbdO/eXY8GqobS
SK7wAM13dqxbt04QWpBhVXHwDp1BUZf+UemsCJh5gM7iEYduzUN/ETYoLDt/umPDC9xCz4hVXYAj
tGnThgYNGkQff/yxCFzcMRIMhQLPzy79gfJtTKeT8IM7J0zEYHhil1ZjWszvyAfICVeRR97EoyPZ
aoRtJIMHDzYHY/kNPTI6NJX/5cuXSwdpdoz8A4YNAk+Bc6xdu1Z0fSpPRp0zUIv46gYRgjCH/ht6
REUIB/6gD3Mi6Mh4lkF///23oAoBA9OKgikDo3+eNQnPeGRLPLORen3//ffrTuzyBN2rHe+cyotV
E9JOMPgAOhLIyBc94lLwYi1tTAkHkyAcQEuWLJHLj3hYT6x3EAHI0xWxYz2L3B4nH/zDug+pcOrb
6gk3mZmZVlZ+ZhiVoReFwhmVnXV11LFjR2JYfT93bj8QHiCt1IIBkKlRMY2jP6ewjHkrDJ5fSeQ7
ECZiUXlixS+VT4z6gAY+efJkGT1AEGEEqBrqn3/+KQseGOU/8sgjhIUIJViMvLaKA2HBHwgCjad2
NHTo0AJO0dFhlI4FE9QbdN5Y5EJdVoRVa1XHsJgC9CGMSAtTxirMypUryyIPq1eEB2g3dlSYMsDs
qHfv3iL8sKDz3nvvSRtRcdjlCfZ2vHMqL0DTgY+8HiBliYEIFppKJbEwcSToCaCzYEw+0TFxL6Xx
Hifdz2233SZ6FSwW4IIjriyyCAIHvIFadCjQs9kRdG5Q3s+cOVN0gDwq051Cr6X0CtD5QXkNnSNP
SzTGBNT1RNABmnWRPXv2FGW6HpjpBQp25AXKcRAU4lyAGq9c6y6NehwYGnWA5rxBEQzlNnQveDrp
/xBWqPKNNIPAKyddnDjin4kTJ0q+ocuD4ppX95WVLDoE4gn8GcuIVxn1MtIDMrwY87lmzRrRteJS
LCx+8ahbY2EjixNQ4kPnC+KZhMbCUmPkcPk281oM839QP2vWrCn1E3pcnuJqfFOh2CrdHHRWiqC0
hy4Pej8s5iANycnJYg19Geo56jKrJMT+xx9/VF5F2W9VxlbxmOsO9IgoKyzwOFFh6iUWo3gqK4uG
SDfvUhAdN+qrU56ceIc02pUX7OCXR4lywRmeuABNtVXYlxbytR6XqcUqG1blzIQKxDo0s7F8YwUN
f04Ev1A4uyEofLFSCCVtSZM5bzxS1niErPHUwFXSSirfKC/wkEdYrtJZVEfGfEIYoWHhVsBgyMxr
5RcNEQILxFs/NJ5NKCvbJzpTLISgLhkJwgKLXhDASJ/VglKwZazC5+1d0uHwiEsZhfQJviLNqh2B
Dzz1FQFolyc3vHMqL5QJ+BiofYc0oyEOzJUOUA1tuXdRr35PpS/wM8z/4JVaK2M/M+hm3BLQoAuD
CO02/GDcmfPGI1nCQoRbKql8o7ycysxt+t26M+YTi1WYQgVLZl5b+ceChRvibTIyrbVziym3ceHA
6C7YMoZfTO8xXcQUGNPh4iDw1ZhmLCAaySlPcGfHO6fyQplAPVCaKSgBWJoz6qX9zOQAT39dL5YE
4gBP7wXxO5C7YO2xSMFTYrr77ruD9Vpk9055CiXvipzQEgrAQ4QuIcZ70Xoc8DhQ8hxwtQpc8sn0
UuBxwOOAx4HQc8ATgKHnqReixwGPA6WEA64FoHG/kDFvvKJHVpeaG924fQe2HeI5k6m4MAWNPDuV
GI7GeL13jwOljQOuBSDQYNSmYyPGG05TAImiMGTGeQPKBTZdn8kEfmEjbiBatWoVAR2kMIRd+bg/
2SOPAx4HnDngSgACdglnGCH4QKHAeEM4Zpw37Lo3numEmzONjJiCTnnDcSNGXHFy4tl5HPA4UEQO
uBKAOBIEbDfsJcITo7RrDBh+OH7Dm0jleAzO0WLfkyJAyOMsJA5d43gSMAJBVph6WJbHPinglDGU
FgGzDdsHeMOmCq7A0y78QFhnOP706aefyhYKpI0hhPQjeVbYenY4eoHiMWO3ffDBB374iFY4bjja
dMsttwjQQ69evSTPOGcNrD/9T5LLAAAgAElEQVQc3sfWhqeeesrvuJOZMbxf1BLDEe7scO3MYXjf
HgfOeA642VjN4JdyDAhusXveiOGH4zY4PgUIHhxJA/4fn7nUg+3Tp4/2v//9T44bAXsPx5awm94K
5w1YbiAcR2Khq/Fhc+2tt94SbDi1w10POP/FLnzscke6rHDi4JWFqxxbA5wWgzvI0SsWOhKqGVsP
x5NwbIzPWEracTQLR65w6iNQPDgShZMKZkxBRGSH48YdivbJJ59IvnG6AeSEzSYODD9IE1dcSwzH
YLELDcF6rx4HzjgOuDoKhwaMRqXIiAUGAcgHsZWVxofRNd49Lth4OFIE4EwQjtQwSocWEREhGH4w
s8J5w/EjnD1Gg1dnNBmKSI4nwY+RnMJXQgDHgRQpnDh8QwCqc8D4Bogrn1jAawFsPSccvUDxQADa
YQo64biBbzjvDHLCZhMHph+VJisMx0DYhfv27dN4VC1/wR5XMyXD+/Q4cNpzIOBJEEx3gZNnxAM0
D4sBw60IR3AAs4MFE7wDqopRdwUmy82xGUAaYZoIlBBAFsEvpteASTITpuRO4VthnQHLTBGw0xQB
Qw6wQTxCEiMjtp4djh4LMHEbKB4jdpuKD0+F4wZEEh6t2vIYecQUGDpYBfkEHuPPjqwwHLGwYsS1
U36hwgDUGIgFpEy18Q6EHDO2HMw98jhwpnAgoABklBXJKyCCgIdmRTgvaEXQj915553EaBUE8EQ0
WAhF1Yit/KAxQthiaw0WArBqyogzgtdnPq8YKHwIb+6C9PjMOHFGnDTo+BilRIQS0mVMI86yAmbJ
SPg+//zzxShQPEZ/xvdAOG7KrTq364Slp9yqpx2GIwStHa4d/AIcFn8eeRwoCxwIuAiCA8+4bAYj
B0UYebnB8IMyn6fPspABv8ALhICDUAIhHPO+P4x0MFJEfFgEwajHDnU4UPjGvYtWOHEMTSRpgSAE
3iFGPFYUCEcvUDxWYcIM6bfDcUPHA6RlYNY5YbPZhQ2hbIXhWBRcO7u4PHOPA6WVAwEFIDIGtGSj
AMQNXvgD7LsT4YY4TGMxcsOUDEIIUOcAuwThZjEAWWKUqAjCDiMQCF2MGrGqDEhxgFmaKVD4WFX+
v//7P1k5haDhBRp91IawWC8po01MfyHQgdhhRf379ydsX+HFGUEyAaQ69tkpVJpA8ViFCTMcjset
eQB2BZIHwDAhuLDnEuChQB5R6gWsTGP7ERB5gMKLlVwAutoRVAYAxoR/rCRjTyHKANN+XliSlXl8
Y0WZcRzpoosusgvKM/c4cOZywI2WkqeaclmN0a0R481obvWOG9VwGxYIixwAwVRkh/PGeke5OQsr
ooHIKnwsBDjhxGERBJflYJHEuFjgFJcVjl6geJzCg50djhvswCsj/qITNhvcW5EdhiML2qCwC63C
9sw8DpR2DrhGg8G+P9wJ6xYyvqS7jDlz5sjI0e6OEoxMcWcrRoZFoUDxFCVsz6/HAY8DxcsBV1Ng
JAH3ZeAca2khTEudLtXBpmzezlPk7ASKp8gReAF4HPA4UGwccD0CLLYUeAF7HPA44HGghDjgegRY
QunzovU44HHA40CxccATgMXGWi9gjwMeB053DgQUgNiWgdMBoaRQYuLx6jIBR1ARr9Tq+w2VmXry
irO45ZUrZVTsT2Ococx3sSf8DI6Adw04AmyUdNbt6gyfWSec5gmWcMm83WJgsGGdae4DCkAcg+P7
WUOab7eYeG4iRfouv/xycYqLtLHxGpc0YwOxmXCTPfa7WdmZ3Ybq2xhnKPMdqvSVxXD4bmB64YUX
SizrZhxMc0Ls6sxnn30mnbvZfaBvvseb5s+fH8hZmbQPeBSuOLiCTcWhImzsVed3N2/eTDiWB0Fz
OlIo83065s9LkzsOAAfTfG2lnU+vzthxJjTmAUeAKhqcRMCpDJxEwEkFRXZ4fMDaU2dllVucnsBp
CzMm3htvvCGnNQCGOmrUKAE4gB+cP+7Xr5+M6HA8DkjHZgJYa9++feVkBE564Kgdvt0c1bOLlyGo
5FgcptbIM06yPP7443rUGGliXyROUuAUBfASJ06cqNvbvRjz/c477wgf77vvPuEpQB8wVVHkhNn3
4YcfEk6nYC8jTuSYz/2qMPC0Kx8r3uIYolvMQSv/dnEhHWZcRJgBaAFAEThRM2HCBME/hLkd2YXv
pryuuuoqOQMNbEqAW9gRwmKINTmhhNM4AMXAjOLpp58mnBgy413a1SGEb1VOVjiYdmmBubHOGN3h
+CVmMy+99JIYO9UX5Q/7XnESy0h33HGHK4Ryo58z6j3QTm5g/HGGNa44AmPFglDjM7wCewW/dnh8
OIHAgAIa670kCtxUz2Cn2tKlSzVAaI0fP17M+SiYxuAHApUF/D8WknLqBCdAGAVF4uJKKNBV6jSJ
eMz/Uelj9BmNR34aoLrgj4EXjM7kHebIC05UOMWLMIElyKCpGp/X1SZPnizp4J5bwhk9erTwg/Ux
GldowUdkoNgC8cHAGKcx33gHH3kqpvHIVeMzzxofh5MwnDD7WJejMWiDBqgqnIBhAawxWo5l3DC0
Kx8r3gaDOWjl3y4upMOMi8gAGcI3FhJyEoePBWp8LE9Ov8C9FdmFH6i8+Cilxh2pxlNfwbUEtiML
AqsoBNMS9RblCaxIBuIQeDfU15UrV2rAjGTBKH6d6pBdOVnhYJoTYldneDSo3X777XKqCvlh1ZTU
c6f6grDBe8CgcUcpdQ4nu0BoT4xIJCeuxKAM/gTEA1QCBgWqCICnfIZXMPqc8P4GDhyoPfnkk+IN
BdC+fXt5NwoCYAkCLFQRChOCgXUWuvDAkTU7UumDPUNdaf/P3pnA/TuU+39EpBTty0lpOYp/RIgW
/AgR2mRfoiylUlnCOZIiRLJlLW2USFIq2SLhJ0vi6KRFSWVN5Zz2U83/8764bvPcv/ue+/5+n++z
z/V6Pc/3Xmaumblm5rpnrpnrM0960pPaglb8UIC5dJ0n2HhOdE7KjBxQoqk7n77E1mE8bPrb1piR
AY3YiTQdRxFZaXRnmIr+Xl44cd9997VOudhii0XAY1H6NGKAVZsoh5fo+XLZDoo5WI+fS4u81XER
UTDgQTpR7wLeqLAi/bn/5vjn6ou6TvEr4cfHJqcAqV9cMSE+2NyTBnTNNddYPrnOtSGUZ1s9NeFg
ws/JZUve076CAtRI1j5qtAf/yOfaCzxdAXLNR937G/HA3pzL1GsKjF2NxQUn7BesVIHmosoyzD4Q
S8DwS4lph6/QAnrgIAhpGKYj+rJXj9RoDKAgnda14elVkYa46EqXMlMmJ0AaKDPlBaQADEAnpunD
kIMpEBf+wIWBo5hi9pEH/gCe0AjZQBKEvh00EjBPFhaA5JfdmHxX/RDJZUu5mAKDvuNpvu1tb2vl
7Ql6/EHSIi5IOLQJTwvTClBdLAA0URf/tvoC/xGzCMAaTl31BS8AJyDaI/cOxkE+kBOUa0NMn/vW
kzHr+U9I4UGjyMCKsBSkxcq1lzpbgEXOOecce8w5P76AWA83V+57KUAaZhM5Hh82MLD7LrzwQsPR
cyw9bBQ0dLD2LrnkkkZh446G3cWJbS0aZZmNy59NxG9Xum1lJh72xVRBOzDqoPlsSwP8PzD77r77
7uqPBZ4jjjjCGr+mPmbz1GjElCCAsU3UVT9pnBRz0NOlXJr2pcFarwdJCyakBxqOp8UvnbrNfbGL
f5sshUBuH65UsWo011oOXrTx8kgaMdllrg2hpPrWk/Pt84tdHVmg1A899FCLkmsvdZ7YQNk5QdsB
XQjb7FymZs3WUyIotxzeHyMlDlECigmsPQBH6wTWHsv7GNWhs88+2wzPmsrWg470fth0gZli5Ibx
m5EAowC+yqOkHGYfCyXIFCO4TAqG5MxHo4m66ieNw0iMUYvsnda54M8IsD6qT+Ok14OkRTxANRiJ
UO8oFOodWDBGwE00KH/ngYwA2GXxDaUhc4Etavj78fzm2lCunhhFIt9hiLYHkjiHaTHC5KORay/1
NDh0jIWz3Xbbzer7Oc95Tj3InLoflwLswuNDkkyDWfbfUaumTcTqKeCfrLCx0vv+97/fRjpNYUf5
bNh0GVGwzYYD4Zkm0ZFZWWOqNCrKYfYxAmAqzscEnL/99tvPViib0u5TP2m8QTEH07iDpgXmI1iE
rLBT96yGMyXmo9lEg/J3HtQLwLCA8TLNRslzIuAoKNeGcvXUhIM5aH5Qeigydj7wUR4E45FpMH1y
2HOnB83rdA4/EjAE7EdsycCOxdec6UxqI+sSAHGYBoOADDAoX8jJoGHSJQ6jETot1yjE/fff3/Z1
HXDAASPNNiM77DuAmiJfJzZy85z0AY7tokHqBzskHit8lKiLQWmQtOCNuYPpKcqQkU0XDcrf+dG2
qDeUBSjno6JcG8rVE/mBRpmXtvZSL6t2ENjHk9E3I8K5TCNRgHNNgIz6UA6c3YtbFYs77LFaffXV
55ooSnlnmAQ4sxtzAHtYdfzrDMv96LNbFOAQMmUUwoFGHNzEtErbGmYMUOwQxS1RZpEEMCVoW4wt
QLWZG2ZRcTuLUhRgp4hKgCKBIoHZKoFxLYLMVqGUchUJFAnMDQkUBTg36rmUskigSKBBAp0KkJUl
9+ZoiD/hjyYDQ2+q8NImAmtxlBUCCACrtIWKBGarBDoVYIq31yUE3KjYnjFeSvlMBobeVOGlIVu8
BaYryfc4yBd2umav5KtIYNwS6FSAKd5eV2q41rT5pXbFTd+nfMBDE+pG+rpcFwkUCRQJjEQCnQrw
9ofw9kgth2GHexZTOjw+QNyF2vDeBuHz6U9/2rxDjKH+teGv5XgStw1Lzvn2/W3CeCMu5b9cZxE7
gfuW4iaybQa3IzY147uLr6hTG9aiv09/c+Voy1san2s8AEgTAmCBbRFf+9rXqnsADnyjLiYIXL5w
lcOPVAfJWzjcANuwA7vqwhiUf0UC00EC2smeJYcaIlAOw06O84bvJnthlJ9jzOG9DcInhQPK4a/l
eJL3Niw53qVwQdy3EVBYbVh8//7v/254hB5X3iFRG6TtVq5Y8clPfnKcP3++wSqtvfbaUX62dq02
0Iq16LzS37Zy5PKWxuda7oYVfBf1Jc+buPPOO1sw+eRGAcraNRBg2udo5SLvK6ywQhQwrL3LYQd2
1YUxKP+KBKaBBHCnylJdAbZh2MFE6BjWybnWiKgV740O0pdPqgBz+Gs5nhqtxBxuYV8FmMN4yylA
8k3+nORHbACvLluUl5NjLfp9+psrRy5vKQ+uUWbgJspVKwoROO6yyy5RngEWTE7yUejHdo0C1MjV
rvl34IEHxs022yxqdBjlKheF8FO9E7BBlHug3efqoopQLooEpoEEOqfA9VFqG4ZdPRx+lzm8t758
Ur45/DXCtfHEtxjvDWDnmcr1RThJ0+Z6EIw3x2ojHmmDSuLENU7sEFhzTViLHjb9zZVjkLwxxVXb
syMGMFcATIDtlkWZSy+9dIxXC54uTo4DSXmYAuewA9vqwnmV3yKB6SCBgRVgF1aaF6oL760vH+fH
bw5/jfdtPLuw5Ijbh3IYb2AgpqfNpRiHoNykmIEocnyHobY8N+UnV45c3uq8SBO7HivsxAPsc511
1jHUFJBmOPfCqSl/fbADm+I5z/JbJDBdJDCwAsxlnBGKH0Y0KN5byjflkz7P4a+l4erXg2DJgU0I
xloT5TDeQIcBEJaREeClAMA6adpoo2FB7BsmnexnYxSih+v6zZUjl7cmvtTPMcccE2SPtNfgNX70
ox8dM/prisez8WIHtvEtz4sEJlsCI1WA4JPxB3z7oHhvacFTPunzHP5aGq5+PQiWHMopVV4prxzG
G+jGAKMCA8ZJcTo4qYq61VZbGc4dKM8oSqa9PgWuAvW4yJUjl7cm1nxMmPYy8oNQgIwGUYx9aDzY
gX34lzBFApMhgZGDIbBN4nGPe1w1tcOTYBC8Ny90nY8/x3Y1LHYgtqsu3EK2gzB943jOJsphvIFm
zNEAqU0v5QH+Gggc40XhaCtHLm9pPkZ1PV7swFHlo/ApEhhWAiNXgMNmZLrEA9SUzddzHShyutRH
yUeRwERKoCjAiZRu4V0kUCQwrSUwUhvgtC5pyVyRQJFAkUBNAkUB1gRSbosEigTmjgSKApw7dV1K
WiRQJFCTQKcCHAUe4LB4e3hTgATD72TgAtZkU25niATSdjJDshwuu+wy8xAaT37x3KFvFRpeAp0K
cBA8wLZsDIu3ByIJZ5hyoPVk4AK25b88f1gCKVbjw0+n9iptJ1Obk/6pH3HEERVqUv9YY0P+4Ac/
CPLPtodTWS833XTTjD1juFMBDoIHOLZ6RntXcAFHK89huaVYjcPyKPFGIwH22y655JLGbCrrhb2v
AhsZTaEmmUunAuyLB0i+warD0R6fXbwWrrzyygWK04Wbd/TRRwfBLtnBzYApOKW4gF14c9ddd525
eHHYNph1IBsz5WijNhy9Bx54wPANBWVlQAv77befjUbhQx44EB2PF3D+wMrDhQ63t2c84xnmCdIH
O68pT21yHFV+Nt5443DGGWeEdddd1zxXBIVVuTCCY4jMnED4XnPNNe22jvmI218bJiCeIoLOsvfu
buc8099hykr8tnbCuzYcSt7V6Z3vfGc46qijqse4ctKGMbnk5J2TU8UsuaCc8+bNs/Ok99xzz8Cm
eSch+QRBkNkG+RVXXDGcd955/ipsscUW4Utf+lLYcMMNra7YoI/HDoQC5K9eL1Xkhy764j8Kxi4I
Gci8lfAHZ+bm1JYP3DM5HxtnhzXWWMODz5zfLkQah2wiHDBH8tONRx55ZJS/a9SwO+qAcGNx7733
Rnk4RB26HIF30obiKK+LKG+BMXh7OdgoAQQYbt4nP/nJKHDRuNpqq0VJMqpRWtqbb765pdWVDzWK
qEYdNUWIqvwooIJ45plnWtz6vxyOnpR4JE3KpoqOQpOJ4PxBngdNZaJg46MaTJSLWzz++OPjzTff
HIG1OuywwyxsDjvPAiT/cnIcVX7AJpRbXgRCS0o7CkkmqhFbLjTStnr1LH3/+9+PSyyxhN3WMR9z
5dKh29YegM9KYbOcL7/DljXXTnI4lGnafn3qqadWUGA8o50ss8wyBhWWk3dOTs7bf//6178aVqY+
lhF5ggVJu/7Upz4VNXqKGsXF0047LQpQOMoTyeStj7hFB5JMILoG50bZ6G/gOUL6wFo/qdeLvUz+
9cV/lG+4wZ3J0yrqw2fwZlLGxqktHzJPRbmARvmHR+LNNBoZHiC4cYJ5qsoPdt2hhx4a5W/aWwHK
Pzbq61jxQPhtCrANT1AjgwrQE0ZCN4mPetSjokAOKr7pRRuOHoqRtFGiTnQOje7sFgUIOKmTRplj
yr/XXnvFHXbYoRM7z+P7b5scUVSjyA/poAD5yDhdcMEFcamllrLbro7tmI9dmIAowKWXXtoUiadT
/x22rLl2ksOhrKfPvUZTcdFFF63qWX7oUaNa+4jn5N0lpzQtTU9NFv4MpSFoMVOAtFcGBSmRBz4u
EIrnuOOOq17T7nhfJ6+X+nPu++I/8iHXSM5Y3H333XGttdaKmvXYfS4fYG0K/szCzbR/i6iSB6I2
nLc65h2ILkwRuyjFzcOOceKJJ1ZRmBa0US4f+kpW0RZffHGDfK8e1C5SHD2mFoACAGXP9FUjH5uO
exQ1VIOQd9gr4O2d1InGYP5RfqaIKXYekFkQPrT8NVGbHMHtG0V+PE1su04ANFBejVT8UfWb1k/1
UBd9yrXqqqsGL3Ma16+HLWuunTAlA9PQ4cZIC99upmhNhLkGk4AAXYNAYYM+BkGAsAHIsi55p/za
5EQY8puaAWgrTLMh0qm3c/KRwqelvuXkiUWfQaiO/4hp6dxzz63wH5liQ5Rh1113DRppmhmHxceU
xpuPlNd0ue60AdYz2obzVse8o4NrehHAl0sph5tHwwDowAk7TBu15YMGTcdK6Y477khvx1yj9DiZ
jTDXXHON2S85s0MjooBNhDMznG655Razh3na/uvv0199Ce22D3ZeGq9NjosttthI8uNpuX2Se2xQ
gvoPGimbwnIFzztswE3Up1w55QfPYcuaayddOJRNZWGnAQrw61//etBIJ/Bx6Kr/ejtukxPpUXf1
Nultm3TSNk942hn2QqdcO/MwuV/id+E/0l633357GywA2ybU8sAHLKXx5iPlNV2uB1aAbRln0UP2
jWrhQzYNM7TXQQVyuHlAMYHHx9eP0Qg8BiUM+xry2x9x4ZF+Tev82nD0AAnVFC5o+mEGa5TCWWed
ZaOFOo/c/aDYeW1yZKQ6ivx4XmV/MlRoFKHOLLGRL++A7EIhglzDCFZTZY9iv47VOGi5xjB56GbY
subaCe9QZuSfTq0zTgILC+miQz0vjAA15Qsy2ZgS4H1X/XfJKU1jo402CizM+UIc52yTHoRior1e
ddVVdk9bvfrqq3vDklkk/fN68fv6L3LJ4T/ysQe5icUWPjCMpFnZ9Q95nV96r+MRbFSafjjT99P5
emQKUGdM2KofXy466kknnRQOP/zwBcqew81j6klFMgVgZRWe3A9CTDWYRsvQbNBXrAiyosXopona
cPRoBOD7sdpLXvhDKQ9zju8g2HltchxlfpAD0x3qiQ8SK59avDLxgGNIWtQBpoQUHZoAKVbjIOUy
5rV/w5Y1106GwaFkhKbFLjvTetttt7Vcdsm7S05pUWmTrKjyceaIARTt+uuvb0FYYZc9McjeZiYU
dkCwSpyaeFJebddpvTSF6cJ/ZGpNHgnHyHxHne7ICjkfShR0jvg4A/GWmoRy4afVO2n4kRIrtiwg
5AgjcFsYfUXstDSMsMOQti5ETUcsKulArHiyqtVGrFSz2s1CQ51YwWMhRF/m+quB7qVwIoch3Xrr
rb3itclxFPlhEUSjDFtF1NS/MT+//OUvI3luIha2kBk0aLma+A1T1q52Qn1h1Gexpg+xuMCuhjp1
yTsnpzovTS2jpr6NC0P333+/5Zf2Oyyl9TIsDxaF0rbOoggLml1EfRB3ptGsg8PC2I0d5+STT7ZD
jJhSM5LD5jIbbRjDfE0BhWWRQKfVDRN9VsXBxovpRkeYmkzqdq9ZVdhSmAUkMLIp8AKcp+gBxnw2
NmP7YVMyxmfsfEX5PVwh6623ni32PPxk7l5hK2RTNfaxovzmXjuYdSPAuVeFpcRFAkUCw0pg1o0A
hxVEiVckUCQw9yRQFODcq/NS4iKBIoGHJDCrFeBtt91W7b2ayhpn/1d9I6znZ7LzyGIQjvlNxHGg
wJ9NBoHzyD7DQkUCUymBWa0AcR8TcMNQ8h0lvloO+208eRymYCmuYh3HDdScNuU4TFq5OHL8t4PY
c2HKuyKBiZbAYLuMJzo304g//pt77LHHNMrRaLLCplunOo4bHiCTRUA0LbvssrbhlsPkCxUJTIUE
OkeAfbHE8CPEVQzPCna6Q3hkrL766rZDfOutt658HsFfY2TG3iscrNkNLwgpi3PjjTeGLbfc0lzQ
ll9++QAAAT7FTkyb2jDowG8TAou5c4HPh6N5jhjtEI4OyNYQHMShLnw1wqAs2jDccthvg+SxSxa5
PBB3q622CmAZrrLKKpUpwHEVm3DcqEN31yKfeAMQH6+EFAuxDRsOueBSJSQcqwO8TA4++OBGdyq8
L5A5njaFigSmTAJdO7f7Yompk0UpM4MSkl0rskNe7mNRUzzDfRPoZrXTXmADhiuo/Xq26xwILLll
GXSVOmDUnr2ozmgeHWC/qbNE7eWzrOYw6OTUHoHJIk11LMNZkx9maxGBswK/j1348s+MT3ziEw2T
jZ3wYAryTB16gfg5DDc8B4jbhP0Go0HymJNFLg+kA5QRWHfa6Bvllmh4bXhv4PEAxiFeMnUcNyCP
tH+S6DGHhUe4Now65AkkFfmjHsDWu1zYjk0ErqSQSppelWdFApMiAb7OWeqLJYYCpNM7oUQABoVQ
IoCD4pIGoQDlc2jX/KNjojQuuuiiSKfX18DctDyARopRSLVZbD1csuqYaLg2tSlA3HvAMYOIC1Cl
/D8NJJRndV48c8phuGnq3Ir9Nmgec7LI5QG3JE0vDVMO5Q7hCkiZXQHyrI7j5gqwCwuRcG0YdeDk
ARzrboXaaNzqIgX4Jx+3QkUCUyWBzilwHUsMZ3P5HFZYYqBMODnGGfeAD+CRwfQJeCFACVJKMfvw
0tBIoULIYErqZx0Qh6kU6BmspDIFZoECNBL+AD0gP9dee63B1QtFukpGo8Hqun4ByAL81FmNzz77
7FMP0nrfhuEmhOMs9tugeSQDbbLI5QGoJqa6IJDg9oZMQBvpCywB7y4svDZsOBZSQFLBqwKwBcwh
THebCIAJMOc0am56XZ4VCUy4BDoVIMoJhAhWD8HOo3Gvs846BqEE1l8dLcRzLLRfW1Hk5Cqw9vbe
e29/Zb8pHh18BBJgSpCXrBDqi1CFx1cTFI0cBh3oHfBJgS8FcFDxqF9gI2ORA/siiwEXXnihYeF1
YdjBJ4fhRmevb3lx7LdB80habbLI5QGlgvJB6YHtxjkP73jHO8LtLdh+pJNSFxYeYdtcC6lXEET4
KAFFplHsGBtumg51xQeyDaknDVuuiwQmQgKdCpBEu7DEmjKGkR1neyCP6JB0hlSpscrqmG0oIU2B
DYYHXhjS/UAkwCHpRBjMcxh0guO3Tg+sE+nJBhm+8Y1vNGXNnpE/RjEsEEDg3hHP88hoCZioJuKD
0IbhlsN+GzSPpN0mi1weGCUDacSBRixiMGJuQhJuw3HrwsJrkok/YyRNHaDsN9hgAxthc7Y0xCKZ
psYe1BapwOorVCQwZRLoM/fGoM3ChJSEBZfyMDudVk2r6NgAOTPDiQNcNH2LwjeLGr1FnaIVpQzN
BoUNECM9iya8w6AuNF6Lit2LxQjeC5PODojhfA0nIKV4LtADsxtqNBqxM0HE1SjR3vErPLNWGyCL
FTrFyux12CY9rDqk8V4LuJ8AACAASURBVNptt93sUB+NDO2+/u+ggw4ymWAP41AbYdRVQThTQhVq
5eLAIWG/2fkPBBgkj4TNySKXB/JDnWkqarZXt8+mNkAO4ZHpweqBvLkNkGsWMDjUijNQqB/k7PZE
wmlGQDAjDqByW6tQtc1+Cl/OiKEeOfwI0mgvcvCOE/XqZ074s/JbJDCZEuhcBBlPZjD6g3/n2HHg
vmmKZIsgdEiM8rzHaO9Ep0cxQr/QKVPEqRN827D1NA02/D5++xAr1hqhWFDy4cqUB134ajkMtxz2
W9889pFFLg/y6oiyO9qKb5sscjhuXVh4bTyRJ6eaueJrCke6HAYEDmOhIoGpksCUoMFgj8JWhp2w
TtoyETijAXjuuU6zWRbsueQAorIPcK638qkt/5R4gmgKFbA/NZGmfAYd3vRurj2bzbLQudKNRybM
tTou5Z1aCUzJCHBqi1xSLxIoEigSeFACvVaBi7CKBIoEigRmowSKApyNtVrKVCRQJNBLAkUB9hJT
CVQkUCQwGyVQFOBsrNVSpiKBIoFeEigKsJeYSqAigSKB2SiBogBnY62WMhUJFAn0kkBRgL3EVAIV
CRQJzEYJFAU4G2u1lKlIoEiglwSKAuwlphKoSKBIYDZKoCjA2VirpUxFAkUCvSRQFGAvMZVARQJF
ArNRAkUBzsZaLWUqEigS6CWBogB7iakEKhIoEpiNEigKcDbWailTkUCRQC8JFAXYS0wlUJFAkcBs
lEBRgLOxVkuZigSKBHpJoCjAXmIqgYoEigRmowSKApyNtVrKVCRQJNBLAr0U4JVXXhl0ClsvhlMV
iDOAZ/NBSjoJL+jo0F71MB1lwdnAX/7ylye1eXD2s47pHDjNUeWVQ+11VOzA6c+kCHfccYfV6wMP
PDCSbOvEROOnU+JGwq+TSZ/j6HTAddxzzz37BB0ozMc//vGoA9MHipMG3nrrre1YTZ7Vz6pNw3Vd
p3y6wk7V+0033dTOWOa85SZKyzAeWTTxHsWzH/3oR1EnAY6CVW8eH/nIR+Ib3/jG3uE9YD2vqWw9
TJ9fjvzU4V99gs7YMG9961vtDOzjjjtuJGX4+c9/bvw4+nYyqNcIsFOLDhng5ptvDrfccsuQsUP4
1re+FXR279DxPeKo+Di/ifhlBH7YYYeFV77ylY3sp3sZXvjCFwadM9yY9+n2sJ7X6S7bqZIfo7Wz
zz47vP71rw+nn376VGVjXOmOWwHq8PLwqle9yoatK620UlhmmWXCBz7wgSpTN9xwQ3jFK14RHvvY
x4YVV1wxnHfeefbuhBNOCJwN+/nPfz68//3vt2cMp9/whjcEHYwe1l577XDJJZdUfOoXhGOKseOO
O4bvfOc79lpf7vDqV786PO1pTwuvfe1rgw5hr6KdeOKJYfXVVw/Petazgr7ogXxDTXyqSA9dtJWh
q+w6+D3853/+Z9AB4IGjQA855BAOoq+zr+7b0tlhhx2CDloP73vf+8LXvva1KrxfNJUhJ4vzzz8/
vPSlLw3PfOYzTRb33HOPs1rglzK+/OUvD1/84hfDS17ykrDqqqsGptgf/vCHw3Of+9xAnV9xxRVV
vDY533777dYOCMhZwB/60IfCXnvtFZ797GeHlVdeOXz729+ueDRdfO9737M8P/7xj7cOh1kGouyc
n+xEu4J3nTbeeONwxhln2JGrT3/608POO+8c/vjHP1qwz372s9ZmqSvaXZrXumz/9Kc/Wb6f97zn
WfkPPvjgbJ2SAPyRE2VN85Zr79tvv30466yzwute97pw6KGHWj4HqTciIDP6AeVdb731rL/x/M47
77QPKfX44he/OGikGgZtq/Ch/y699NLhiCOOCNddd1348Y9/zGOjo446Khx55JFhp512sv685ppr
BgY8UO6dBUj+5WSUBBv+ss8wMzcFZpj/iEc8IqqBRdlc4imnnBIXWWSRqMLG++67Ly655JI2zZWy
iuq8cYkllogSVvzd734Xt9pqq8gQ+t57740aHcTnPOc58Z3vfGf82c9+FmUvio973OPiD37wg8Ys
/upXv7L3hFOjtCmwGlj8yle+EufPn2/TRSlii/vLX/7SeEtRWlpq/HGbbbaxd3U+9cRyZciVHT7v
fve7oxRNvOqqq6JGcFEdPXqeBklHts2oj0L8whe+EJFjneplYArcJgum0Mj1M5/5TFTjiu95z3tM
dv/617/qbO2eMi600EJRiiBKQUcdah8XXnjhuPnmm1vdvP3tb49SjBY2J2f4qJVauA9+8IPWRtRB
os4Htrp4wQte0Jg+D2kf+oDGY489NiKLAw44ID7lKU+J//znP6M+LlbnHnn//feP6nR2m06Bn/zk
J0cpLSvDD3/4Q8szeYcIB//NNtss6qMb07zWZXv88cebLGgXtCd98KMUsPGp/3M+UkKWrhShlVuz
ns72vsoqq1idSynH2267LQ5ab+RFH65Ifu+//37rTzpn2toP00z6qD5m8ZOf/GSUzXOgturlXHfd
daNmJXZLfsmr0+67725p0M6QISY0KcuoUWPMvUunwIPqBE97kN8HW2RHjC4FSMPWCKXiQgfUiCEe
ffTR1kCrF7rAJoNigHbdddf43ve+165lLLZG/fe//93u+bfFFlvEfffdt7qvX2g0YMqO56T5sY99
rApy4IEHWoPmARWAQoZQllQancEp5ePP/DdXBm/gTWX/y1/+YvYfOpTTOeecEzVq8tsxv7l0CIhC
u+yyy8bESW/SMuRkgSJD7k40ssUXX9w6qD9Lf72Mv/nNb+zx9ddfb4qM55AWGSw+1zk5Ox/CoQA1
lefSiHco1bTu/R2/1OuLXvSi6pFGK1Gjoijzx0AKkM7udMEFF8SlllrKblGAdE7/CKR5JUAq2//4
j/+wDxlKFNJoyj7mdlP753xQ2k7LLbec9Y2u9o5C8b5B3EHrDRldfPHFliz2tO9///tx0UUXtXp2
JXP11Vfb+0HbKpE0SrY6o84hPmZ8DFyGKDnNxuwd//hY8eG96KKLTAG2vfO8kecuGVXMx3GxyPBj
x4djqvHatNOfaJQXsA9oJFdNe/zd85///CCh+W31y/CZKStDaqe//e1vQV9lv+38lZKowjzmMY+x
PPDgUY96VNCXyKYUGq2OSaOK0HLRVYa2sqsibVqhkWbQCMq4qxEE/pqoK52mOLlnbbJgZfTSSy8N
X/3qV6voyCQ3DaaMz3jGMyy8FjIC9+rIdq+RhJWTm0HkzPTbifaCXKQAgxYN/HH1iyylAKt70tRI
r7pPL1gtbyNse05M32lvbpdkau/15GGafvVBtiky4TWisum4FGhTUHuGrDDpOHm7ZGrX1d4xUzgN
Wm/ICLlhXmB3BFPdOjn/QdsqfD73uc8F2s1rXvMaY4s5QUoxaKQa1lprLXumUb398o+wUpDh7rvv
zr5DPziNQic4r7bfkShACtdE+sIusMjBogd2jTo94QlPCNhV9NWsXv32t781wVUPOi7a8qERhNlD
NJ0OT3rSk4KmyWGfffbp4Pbg664ytKVJeSCUjXdeOpumcw8yrv3vSqcWvPM2ly8+KhqFVTw0dR3z
AatePHTRxsvD6QNsl4PIuYun8+aXzssHzAllqd0DYbvttjOlpVGHvzLbLvbmJkptwthbn/rUp5rS
Jmwf5Uc4eHzqU5+yP2zPmtqFU089NciUwOsFqK2cg7Z3wg9SbzfeeGPYY489TCGtttpq9oFB+TaV
c9C2Sn1TH5plhQ033LAqM30KO6srwFTeDIhuvfVWU4JsTWp7VzHTxaAySuP2vW7WXH1jd4RjQUL2
uCAbmIVk5Kdhd/XV4CuFURlaf/31g+xBQcN2u+erRMXljOPEd0O2RWr5x9fzZS97mSk/RpV0Hu+0
RMnx6SpDS5KmUFg0kE00kCblfNvb3taqeIdNx9PPlcHD8MsXW1NxM4QjA1bxWJxi9DVe6pLzsPxZ
ZdQULvjCB/VHR3v0ox9tCxEXXnihjUJpP7mFMxQXZabzMYJh8a4PpbKlk8sWGTSdDDIN2QiLfYOD
0qDtfdB6oy4YeWoqbVnT9N/aYdruPc8sGg7SVhnlsZDyrne9yxbFGA3zx2Ldl770JUsH3qyeE440
+UhoClyNRHPvPF+DysjjDfI7oQqQlR/ZTOyLwChohRVWsC+mT3/4erC6yJeK6clJJ51kq1YMg2XH
CltuuWV405ve1Foe2RMDf7IrtIbhBV9nVpvp6AzLaUysIPuKXI5PVxlyCbP6R0UzHWUKybTnmGOO
aYwynnRgmCtDmqDsSiZbpiNMA1mJpQ7aRk1p3K7rLjl3xW97z6hdi0dh3rx5Zr6gnRx++OEWnDTZ
gsFKJ+1F+yXb2ASmx5hYKDcfThRZH0ply4iPtOFBe6ZO+bANSoO290HrjY+GFopsxEV/Yua10UYb
2apsU14HaauM/pCzFjjHsGLFnJEeq9UQZWSarcXNIBu3jRpRgl3vLMBD8QfVCR6396+084QTq1AY
z7VbfIG0WBXiz4lVTlaJZZPyR9lfDOGaEmXD8BKjqobgVVh1gKiRQBWvi0+uDBWThgvSZQWYtPvQ
sOnAu6sMafoYr6kTDOCjpC45jyct6ixdUHBeGmE3Pvf3/LIKjNGfOmf1e1BKZcuqKW2U1enx0qDt
fdB6YwWZ/EIsULBo00aDttU2PjxnEYRFHBZjaPu+ONL1ronnoDJq4tH2bCFe9NaWJWCRwAyVAKMh
Fn4whRSaeAlou1RgwQy7cJ1y7+phJ/p+JIsgE53Jwr9IYLwSYCOwtrOMl02J31MCmLCaVvSJnnvX
k/3IgpUR4MhEWRgVCRQJzDQJTOgiyEwTRslvkUCRwNySQFGAc6u+S2mLBIoEEgl0KkA2nYLj1ra/
Cuf8b37zmwnL5kv2SjkeHHuUhsFpa+Y8fZ6yBYAyNq0rgebi+yEnK8fTERdwsspe0ikS6CWBtuVh
f47vrBiZXysABimxvYN32uOWPm68TjHWUif1xsAz9KE2b5s82E4ApThy+L86AMNkFQ+fYMAhChUJ
FAk0S6BzBOhalF3lwN+khBdB6nOavqtfsynS/S7r72brfcGRm601W8o1WyTQWwHihwg+WUoowLqn
Rh88uJRH/ZrpMbh9KbGrHRc6iF3oeE2wr4sd+qlvbRteGrvc8SRwvLcuPpZQ5l8bzloahV3xeJvs
mOAV4hKnDaLmjVDH0RM6tuEGsrt+k002MUd2+HXJAyhy0mC3P54QuBwddNBBVVZyuIBVoHJRJDBX
JdA8MHz4qU+BBXoZhfZR7X4Hp0/O5DbF8ilwXzy43BQYvnUYcXXuCHwRXgCkyc5ydrirw9uOc3Kb
w0sjvRTvLcfn4ZK3X+Vw1tSOzOuEHfvA/zheIVNgOcYbFBcwSeAgAo0EyU3P4JiALBIAhGGnLb/8
8hEPh5w8iAtUPnhzN910UxQYqKUJdBLEFFgj9EaMRAtQ/hUJzHEJ9N4IDfQPaLkY+fF9ZPTHqBC4
HyeQL9htj48kCwKgu+CEPSoCsglHdmBy8GuEt+ySxp4d5wJYDW9+85vtHn9NgAhAxYBAW8FRGzQM
HOvb+FjgzD/Z9wxJhY21LBDh58gCD4746UZb/J0dRgqnfYiR7X777WfX+HYymgWJl9EfjuRAF0Eg
AOuMBUPZBSqqjYTRZ36XOJzjC4uvszADx0BuCXvRIJvgwah0PEcQtOWjPC8SmKkS6D0FpoBMsXwa
jALkPiXHg6PzY/Nzp+g0zDDXKB0IxArOxRBqtCmbbbfdtjoThKkiTv0gW/CHbRKF7Dh3Kd5bjk9X
/kAGAakGZUU6fWG14AscvxPQRChQUFjAAgR23gkXIpz20+m9v+PX5UE+ADFA+TnVzwxJbbSORedh
y2+RwFyXwEAKkBEE9i+2vTDCq3e2FA8OlIy99957KPmm+G6MkAB0hBjtMcKDN9toGHFhU4PADgMZ
BMBF/xNqr50BwfsUBy3Hh7A5cpw1bG2CRQ9AMcE75d8WPx0tp2EoB2dvODGipMzYOqE2eRAPVJNU
UQI5llIbHl0aplwXCcxVCQykAJlGgqEmSHVb/Kh3LkZhOdy9PkJmSkmH972FTHN9xAM2IEoYbD3g
tZiCoyygQfDScnxQnuDGoeCbiDL2xVlLceSaePkzsAB13odhp/GM0TUjVmCgcvJYdtll7WAjptB8
KBhJztTTuVwW5bdIYDIlMJACJGNMe7E96byOBfI5Cjw48MIY1XGKF1NpUHcdzhskaRQTSL5rrLGG
2dM4nQwaBC8tx4dVUy1QjEGsTQs6CM5aiiOX8qhfs2qL4zgYc5SVU/I4aQvKyQNQTtCt2WQN3iAf
AWyjTKELFQkUCXRLYORgCNi1GIlwFCQjREZrjODq4IldWWOaSnxGnSkxOmQRRItXQSul6Su7ZuqI
3Q/ECWySbZTjo9PCbGGibcoKT+xvbMVhkYK8MHJMbXGeLostKLH6aNnf+y88mAYLn89AWxk9ptQk
D+IwIkVxco1C5KwMbH06OS2NXq6LBIoEGiQwcgXYkMaMesQIEOj1XXbZZUbkm1EfKNcobW0NMsRf
VuLreylnRGFKJosEJlkCRQFOssBHnRwjURaf8DNmxRf7LEqxUJFAkUC3BIoC7JZRCVEkUCQwSyUw
8CLILJVDKVaRQJHAHJRAUYBzsNJLkYsEigQelEBRgCNuCWxKBiNxKomFHDasj5pSTMdR8+7LD4CJ
M888s2/wEq5DAuzQ4MhY32vbEXzavR5v/osCbKlSYffZdpuW162PBXRgZx+3BpiEF+wNxJd41MT+
T9wPIYEvhLe85S2jTqKTL3lwf++RJz4HGbLtarvttqsOM28SwbB9oYnXqJ/1yX8uzaIAW6Qzk7H8
OIyer/qoKcV0xA3w4osvHnUS5l44EXxHntE5xHAm94WuaupUgAAPHHXUURUffE857Z1plmPR6dBp
89oA6QTMO0jQTIa/5xHZvOy+rf4s/W3D+cPFCxw/NlazufmQQw4ZAznfhgH4iU98wjYF4yGCO5kg
owK+wbjP4TXByfZsUm4i3O1SLL9cOZvisyn5Qx/6kAEagIiDq5oTfszwx50OdJ22owYIzybn+n6+
PtiIn/70p82bBB547ICCs+GGG9pGbbAG2VTtxEgRuZIXwCRwdUx9jz0cv7fffnt4xSteYfli3yEb
zvHIaaJcu2mrU8rbxdfTAuMRTEW2/iBrpzasxjPOOCPgAZTSnnvuGY499lh71NaO0vB+zYZ1wCuQ
F8AauC1y/ABeSWxKr2M9tmFkwgd5g7BEnGWWWcZwKz2dtrLw3ttkGw5krjxHH320ITZRd5QhR+Pt
C8P0a/oudbrXXntZ/QI8gvuq0yD59zitv+qsWZLTfwSPz0n2l6iKspPe1Rnj5ptvbhiBarxRGY3y
RLCgGoWMgYAH605eE85mzG8On09wTlEKN2qfWwSCnzQEbmrxcxiA4O/JmyLKpSxef/31UQ0syrMj
Hn/88fHmm282LD4hy4zJh9/Usfxy5fQ4/is4KoPFl+KxdNTB4uKLLx71FY1CxI5SxlHKIcpbxrAC
wQwE86+JcliAOZlRduoFAhNQKDRRoyrDTNSm6ShXO3v3uc99zvAVpYTtvTrzGEh/C5T8A8dQDclw
CuVzHIWGE9WJkxAPX+baTVudgn/YxdfzAAbiDTfcEKUIrZ4F82WJt2E1SnlHAVZEfbgtnD7kUTBl
1jZy7ejhEj18RR7gJeVgedBB39a2kDl1JiUekSXUhZEpD6Eot89I/xF8m5WF9gm1lYV3ORzIXHm0
ST5qwBLlYx8vv/zyuNpqq1mdIo8mGk9fyLXRtjZAHrzvHnnkkVEwc6ZHaLfQoPm3SJl/jKaypNFC
lItV1Unl3xo1IjNwUjpD2nlRjg6OOogCpCHLf9UKJ3ioKGO7NRzN7w0clQ7qdM4550R9Ze2WBqiN
v/7KFAzKBn4IkQbktO+++0YBKPht1NclCoOvuq9fCGklzp8/v7Oc9XiuADXSq17RWHfeeeeIfOQ+
FymjE4qSvDVRTgG2yQw+dQWoUV7FnnfUISTginjMMcdU7wR11ksBEgGFKl/tKm79oq3ddNVpF19X
gHQuJ4BlNZKJGllavngu43jko0vbRVbQvHnz4sEHH2zX1IW3h1w7ssC1f54H2SPtDR9Y+gLPISEV
2UePaxSIKzTAhfnoalbAKwtPvLvuusvu+ccHq6sslJ14woGs4gmZ3RQyD3LlAYhXI98q3nnnnZdV
gAQcti+0tdGuNkAbFdJUlUfkyuCFfjNM/itGDRdjHU4l1ToBuQQwgRSPwa4LmdmG+vj74gcL+KkT
01QhGjdOoXKrTCk+H9MzpgUMgZluM13CCOtwU/ga8wcxZbr00ksNhNXzgM+tYwCm+Hv4yYIg44Sv
Lby7qKucTT6+TEvA83NiisSiAWYApt3pO0wGTMv7ksuxTWZpmZ0n020n6gzDMcQUDLueUx3ezJ8P
89vWbvBcydVpn7Tw0U7L5DiH1Cn8mTJJSVQgGs4T0Fmm/PhJM/Xbaaed7FVXO/L46S95wJQCAT7B
vRSx3adtyzEywdGkraR1T2DigSvpRP0A+JErC2VswoEEOATKlQd7HlNyJ0wafWnQvtDWRrv6NfkB
CMUJmTh25njy7/zS304bIIFZJUIBfv3rXzd7EZ0GkAKADlB4TqANY+ejolFYqS0J+1EbofRY2avj
/IHxB6HkHOMPvDuNjOx5FwZgk3KyiPqnj4FfZn+7ytkUOcXn4z22x7XWWsswC7EJeln4BUnakV+a
eKUyRHHQsaE2mTXxaJMDZcN/2AnZjpKa2k1XnfZJv608XViNnF+DctDIxGyvvqLd1Y6a8tSWBw/r
7asLI7ONT64sfFxQImk7S+suVx4GAnz4nLDl96VB+0JbG+3TBtrkMp78N5WzlwJkBEhnBap9++23
Nz587fia8UXV0NSUHV85wkJ0dBoacO10XHD92qgNn48vI18RoO0ZKaFwgeN3FOZBMADb0m57zheY
RtZVzqb4LKDIvmavrrvuOjPgIpf111/fFJ6vcvIllw1mjIE35ZfDAmyTWRq/65qRNqvF1C0n9oG2
3ZeA72IkmSroetymdtNVp3341tPxe5RbDquRUZOmh7Z9h7IDqwZNZDsiT8NgZObK0oUDmSsP78Ce
RGFS56eddpqLr/V32L7Q1ka72kBrRh6qq0Hzn+PXaQP0abPQUcxOx6E9Thpym00Lux+G9nXWWSfe
f//99lrbJMyegU0Ow//73ve+1kUQ5vaaJkZNZaJWPSMHAmkzsfFh4YNFGA5DYsGANNz2waIChmcO
UWJhBpuUgFQtHnaE9BxeDP86M8Szbvnh3N422m233ewgJSE+x1w56/GxAaqBRo347KAjfcksLQ+n
FS47XAo7EIdMtdn/PDwGdlVgVMe2Q6CEF2gHROVkVrcBpmcDa0U/CjPQ2P/+9783Wyi81SijPiwm
Syk1T37Mr9u+eCglbzInbo6a2k2uTrv4kgfqOyXajkBszQaslU2TO/JlsYmy6qyUKjj1iTx1xGv1
LNeOqkDJRT0PlEdT2SoENkG/Z0FCMGlRpqKoFWs7uEpAt2anrfOBAe2/T1lIg8U5eMn0FDWDqtp3
rjz0T2zj2Eapc2zhUnBRH/sq//WLYftCro3m2kC972JPp87I4zD5r5cnve+tAOuZciYIG2O9vij+
aMwvq2AYpLtIc3wzCmu6uEBQ4iMwToNrItKmQWBcHSWhIMgX1FXOpnRZedQ0YIFXdHKNDKNslQu8
a3pApZOXOuVkVg/bdI8xHd40VJQeiwapsmiKkz4jTlP50jBt7SZXp334pmnUrzkxkIU0CF7+wayH
q99PVDuirLRdb0t0ZNmC68k33jeVhTLBj3pj5RzSFrRqgccZtZWH+Chfjfw9aOfvsH0h10ZzbSCX
oWHy38avUwEykuOrySiPTlto9kiAkQZbjFjt5lhNTQutI42ihKXdjEKK7TwY2QqBPWphzWY9zJBY
fS40mAQ64bC0hB80TTO7iaab2el0eTmzJKAvqdn9LrroIlsUwkbJpvM2A/QgpSvtZhBpDR4W+3HB
gRxcbvUYnQqwHqHcFwkUCRQJzBYJ9FoFni2FLeUoEigSKBJIJVAUYCqNcl0kUCQwpyQwYxUge4x8
U/BcqDE2LGuLTWNR8RzAoV7mXwOpmAgswMaEy8MigRkugRmrALWv0E5vm+Hy75193JzkHN4YHtc/
vBxY1JgoLMDGhMvDIoEZLoFOX+AZXr45l32wAAsVCRQJ9JNA5wgQn8Qtt9zSXN44iBzAA0EdGXfc
3HCgBwtNHgpBmysrnLImjEBwBRnF4ISOyxJ+w2yXcGrDymtKx+NwBq72RPmt/b7rXe9qREQGwRgc
OQgf5lVWWaWCr+cenEPcu3D3w60P/Djc/6A2TLdcmXKygycugm1Yh+C94byPSyFYhjii96FPJ1iA
XbhqbfImnTYctz55KGGKBGaMBLq2DeLahTuXlELEswE8LqCrZIOL2otkbjS4IoEvxu77HHbe7rvv
buHVucxzBFge+RNH2bCyWHlN6Uh5GbyUHMKNp5SNFYU84GJ27bXXLlA03OGACoJkM7N4wFRBZ599
dhQyhl3DGxcvYL/YiZ/DdMuVKSc7EsphoglIwCCBcMPDfW7JJZesXNgsk8k/5KMGZx43qRsc17g5
NeGq4dnShk2Ihwgba/E2oPz6AEbKWahIYLZJoNMThE5M50pddzSCi/h4ese7+uqrTS50HMK2YQTS
iV796ldXMsRNBv9ebcTNYuXV04GBK0Cu5XRvyoprcN7wxW0iPB7wncSVRqNEK4ODveLvKERfiwZv
IUlXLHApasN0y5UpJzvc9vBpbcI6xEXIMdg8E/g1uw+vP/Nflw/x6gqwDVcth03YhuPm6ZXfIoHZ
IoHOKTBDWTlzB41AuDQC9hsEESemjlAXXhhhhOzKjxEeBwIxMF4pVh5oEfzhoZDCbXk6Ht9/HXaJ
e+DfHebI3/svGLveQwAAIABJREFU8VVxNlVnUQG4fPk4Bg7aAXILpAynNC3HdAOjDCgw4MZTaisT
YdpkJ6VV4eJ5eUG6IT8avRr6DUgxTsNi9bXhquXkneK4Ab2EPMlXoSKB2SaBXgoQeCcUh5Oc5g2r
3+/9tw9eWHoOB9s3NM0yJQhGGPYuFKv/dWHlebrYyFBi8oUMACY6ZJe/918UrkagtlIKVhlQV0KX
Megq8sK5DE3UhenWViZ4tckuh4kG5hn5cWBX+GBfHYba3Npy8m7DcRsm/RKnSGA6S6CXAgSHzw9P
AfRUU7uw3nrrLVCuPth5KCgWNVCoLKZoCmwLKINi5aWJ62yHIJj3oGms4QeCo9dGjPIEA2+HABEG
XLiPfvSjY0Z/9bhdmG5tZYJPm+wY9bVhHYJcDdYiB/aAgygbpC001fM1nvucvNtw3EiP0+AEomAK
ejzpl7hFAtNCAl1zeexYT3ziEw3fDnuZ4KkNQ4x4qe3J+eSw87CXgZPHAgPYaGAICmXao5qxnwWM
OlZeUzqpDRAG2BElUMNSqxg2XIBSwqIOizaQlJvFS/Hh6rxzmG65MuVkR9o5TDTiapRmixH8OrYd
8eqUyqduA0wxEVNcNXi0YRPmcNywoyJnPw+jnpdyXyQwkyTQaxHEQS9/oRPAcsCJXvA27DyUBYsL
2v5hK4wsRtRpUKw8j89pX6yUasTlj0b624bplisTSqxLdjlMNFbHWVDid6KoTd45HLeJykvhWyQw
2RIYaCM0CxZ9iENi2BfYRkBspwsHaThgyzlEaBC64oorbLrIFJjp8EQQh9ekeeYgnpRyZSJcm+zg
mx7WlPIUmnZWjmnYYa/b5I3tEJNGoSKB2SyBTgWo6W9Yd911RyIDDuDmzIdRE4sUmrYGAUSOmnUn
v1yZRim7zoyUAEUCRQIDS6DgAQ4sshKhSKBIYLZIoNcq8GwpbClHkUCRQJFAKoGiAFNplOsigSKB
OSWBXgrwyiuvDNqyUQmGvYDALvUhgBKmArdPPsGGkdcnj9M5TE5+cqOzDeATlX/AEsAZBJhhFMTm
bsctHJSfVqUtLmVuIh2jGnQkatOrMc/SdsH+TjbPF2qXgHYyBLyWZi31WXbeYIMNIsAFkA78jvL4
MAf7trict4sjPaRFgpieS9sWZ9TP2RYDaMNMI7a94GvtlJOfNlIbqIOHHfXvW9/6Vtvzd9xxx42E
dbpfcVCGbG9SJzT/6fpRnOyn5B0nF3ZR2i4+8pGPRG2g74oyp99vuOGGnXtr2wSU6oG2MFP9vNcI
MNX+jASBidp7773Tx2Ou8YyYat9RfHa1H3FMvmbCDZ4WF198ca+sCrTAPGB6BR4wEKM1IeQEofuE
008/fcDYExdc+yqDNq2PSYB8amP9mGdtNzO1XbSVZzo/nw56oEs+AylAMOI+//nPm78tQAJNJLgp
83/dcccdA4ADkL665oOL+xd+u6nvLMACAA/gtK8vRuX/2oQBmMPPq+dF0F1B8Fb2GHe0vfbay3yN
AXI4+OCDx/g21+O2YeExFaRcTViHYO/tv//+BrCAKx7l1CHvYbPNNgsamYRNN920KndbOZiSvf3t
bzcZrLHGGlW22uSHzzNTFGiLLbYwIAh9sQ2AYZNNNgn49DppFBfYsrP22mubWyMugCBItxFKBne8
I444Iug86AB4glMOAzH3zuP7bw6P0MPUf5EnWI0poQBBxE6pDb8xbRdp+Po1dbH66quPeczHQMhH
9qytjfCyrU2DRfmBD3zAMCCpByjHxwIk/zjqgL4CQAV5wTQF0b6FzhRo2/izg5bu1IUJ6eH8lzTm
zZtne1416wvyCvJXgQ8ufYq9oyuuuGI477zzqnf1i7oeyPWdetxJve8zBPUpsEZ1BiEFVt1dd93V
GBXoKCCuwNtj2sIUDrc3psG4Ua2wwgpRjcDi4mJGWDWCiJsWBz0THg8Rpktg2aVYgzn8vHpmBB5g
0yKeH3/88YYDiBscrnralBwvv/zyehS7z2Hh5bAOHXtPCiNef/31UQ0xapOzpQ2UljYVx8MOO8zS
aCuH/H6jRltRH4qI1w2Ukx/vwDH0cLgWavQYkas2bUfwDyHMFuD7Ab3Fe6bOamSGH2gBGv5p72eV
X1wDwUZ0wvuFuqHeqO8U1zH3Lp0C5/AIPZ3016fA2vRueI/gQEKYDCgb7cunwDn8xrRd5KbA8AWu
LCVcQS+44IKYayO5Nk16Uh5RStzqIscnTZdryktc+Ydb+gcccEB8ylOeEvHYkW+78aTNcFC6FGGU
cjIW3i6bMCHraVAn9Ee8tQR4EoVOZO1Evt+RvoOn1WmnnRbxHpLN1dxi9XGss7H7uh7I9Z1GBpP0
sNMVjny4AuRaU9+oUQqXrZRi2dFJtVG5CnvggQdaZfEAcNJdd921ekcFyPshgkfnncWxBnP4eRWD
5CJt6IKJjyuvvHLUiMxCaHQZ63Ykj9qGhUdjRWnQMZzA1PNOR0N7+ctf7q+iDpOP8vCo7jUCjUJ4
jl3lQEFpNFzFy8mvrgBTWx35cfvWy172MuskzlQjqKwCBPgW5U0jhug8fDTcdREl14brmHvndYr7
Xw6P0POZ/roCpA5J+6STTrLX1C1p0iG9Lsh3G35j2i6GVYBtbYQM5do06QEA7HLM8UnLzjV9KG1P
uJMKrTwyKOGDK+QgiyIkJfO332+//eyedtCGCWkBkn+aslr+/BEfZHk8mQ3w6KOPjkKD91f2S/vi
Y95Grge6+k5b/Ml4PtAUeNihqUaAVVRcyLAvQUwzQJlxPDzC4YKVwkA5Lp86Tyt+XsW85ULKyNy6
cLFjWgfMPe56TdSGhdcH61AjsIolkFapixuuckx9hylHm/yqxB66wD7mJNAKg/fnXiMDwzH0d13Y
ghoxWj2AnMNUh+kkU0eNbpzFGLdA6gxXP8eITF0G6++cQQ6P0MO0/XJEg0+Dmf5yn1IXfmMadpBr
KW4L3tZGeNnVpmmDCy20UCcfC5D8o93U2xMmFyDoyJcGEgHPI1CaNDtLYgYzL/kD2gUr6unU1t9h
s/OpOc9ow97/aP9uUvLwGhEHjUz9tvW3T99pjTzBLyZFAdIJmghMOtzXHP+PX+xmTa53hIUALvXw
+tIHjciaWI95hs0RCCcWZjSEN7uZn2syJqBu2rDw+mAdtpWTNPQ1s6SGKUeOrzF96F9bOPLOsZpO
yK2NyCd2KY3UTWbIDSUzT3ahM844o4qW2nH5oDmuIwFy75wBchgW/xH7ErYqtr2Qdl2hd+E3eh66
fjVSq4Lw8dJIxu7b2ggvu9q0Kz/C5vjwPiV869N6Q4nRhrH/YQvGFRTFxyJl3Ze+rV2k/LlmUICi
TQn7M0Qb4kOaEtvhaBdd1KfvdPGYqPfNmmmcqTHaEWpMJxdGGOecc06FD0hHY8TR9HXK4ed1JbTP
PvsYWAJfNE3ng6bDgf1gTdSGhdcH67CJX/1ZVznwleZgprTz1XkMes+CB4tXfDhYGZctspUFozwW
oDhYio7kfxzQBNo2+IQQo4UmXMeudxZZ/3J4hB6m7ZcORZkY9bD4Ue/gjMI07Q86/sDyy0fPP0Bt
POvPWciiDnxvoeDTbKRFuLY2wrtB2nSOD7xSYtEDIGJf+KBMfJAoF4qZxS/aN2VnF8Gg5SUtDhdj
wcsX1tizSZuBABKWDT9cddVVdo8yZkGI8raR64FR9Z22dMbzvBMMYRjmgJPyh3LLESvJVCrTJ6Zv
DOWZErPKlELhOw9W0fj60xFREnz16NhdxGoWlSu7UWAKwFeaUUITscVHtpogw7pNOVCUhx9+uDUu
toNsvvnmgZPXqFxGMG9+85ub2GSf5crB9IryM532EUeWWY+XhxxySOAPZcbIgREDirauOGDF6I8V
6/QIBJ4jdyD7/TgAtpMwPUIOPmoE3BZqe3f//ffbew9DfbBaTt2D6C170gKruVWE2gXTXmFJ2up3
7ZXNKlgVv/DCC21HAquijBg/9KEPWf3VwzfdUxbZFoPOm7H8Mcp0hKO2NgKfXJuup5PjUw+LMmcF
mREXxyxwf8IJJ1h7pnwoKMw7mJiEHWnv4D8IMf2FFzMw2h9p8KGCOMGRI1eF52nmJNomOyvSIxfq
aaV6YFR9p57GuO/VeCeEMM6yQtWH9DUxQy4LBF2EAZ2Nr77Ruiu8v5cii6xY+eqhP2/6Jd8Yy33R
JA3DQg0LIeR5PJQrB0bytkWaYdJUY41SPhGgU3izwqeR9jCsLA6LDqwUYoinHuDplHvnYdLfNjzC
NMww18iXvHkbBMdSU/OBWSE32nKdcm2EsH3bdBeferqUg/qsE+0lbZMsilA/wxA7PNgwntar80Ee
LLpoW4s/yv6memBUfSeb4IAvCxrMuD8h058BI9aTTz7ZzADgJTIi5sCl3FQ4V6p3vOMdZi9qGkXn
3uV4lndFAlMhgQmZAk9FQUqa7RJgmo69jtVwfSBtWsOB7MOStt+04jrm3g2bXolXJDBREigjwImS
bOFbJFAkMO0lMCGrwNO+1CWDRQJFAkUCkkBRgKUZFAkUCcxZCcwIBZjDxMvVXIr9lgs36ndTle6o
y1H4FQnMdgmMSwGyDwlPgYkgnWdbIZBgvNfS+8DJsLds2223HTjeMBFSWUxGuml65DeV1zD5L3GK
BOaiBMalAOVwHnCHmQgaBZbYZGK/pbKYjHTT9JD/KOQ1EfVYeBYJTGsJ9Nk3qH1khighHDxDu2CT
5cc//vGoneIGyQM0D8QGSRBR5G1hsFcpErRcZgzqaZ111jG4J9CG2ZzcREDngEYCpNPlgq0C9QTk
C1BpgD6Sp8KYzakggWhfmx1CvtVWW0W57xhb+S5WCC3ycIgg0YAeot3sTckaAg0wUPJgidr1HwVC
YHE8MDBL5A3UEXiA3ALVZZGmy3uQPIBSEr6cQVMBRyUfVoMukjcFQSrS7v0odyO7Z+My+SXu8ssv
H4VjaJtT6+nV5UXkNplUCZWLIoEigci+sCyx6xylw656OdRHuSAZ/BA7z1E2KDK8K7rwwlCech0z
qCs8LFACbbBa7GgHl2y8mIJ16KMUi62p0ISXe1iU+1OUT2U85ZRTDPcOaCV2scs/NMrNKArdwvJG
HvEKqcsiTVeueqbw5b4XNVq2D4m+iJEd/cRtw5wjf224gfX06vLKYdI1lbs8KxKYqxLoVIA5zDKw
/HCJgrrwwlCAciiv5AywpJzaq/v6hWOJ8ZwRIKMop76YgqkiqmOxOa/018PjCuRE2vJP7sSvS2Xh
fOABFpvLiHsAWfsowC7cwDQ9+KbyymHSEbZQkUCRwIMS6PQESbHPNPIwFA6cylPsO+b4bXhhGp3w
2gjbmBPw3cAmgU4CflsXaTpaBaljCgKR9dWvfrV6j5M/mIKALKQEGEAKR5S+82tNvQ2f0O8BTwBy
Cfh28ovDuRPIKEC05+inP/3pmPNTll122VzwCnEkxQ30PMtv1MAMsgz0EkSQNpl0xS3viwTmkgQ6
F0FQerhSoQA4QlAjDUPJqAupD15YihOnkaUhrvRRfqTVhFzC8y78NcI4uSLx+6bfXDrD4NeBqgIO
oRMoGinJ4by6TTHnKBc0DP7hIDKpEi8XRQJzUAKdCjCHWQYUEoCMUB+8MLbMaOBpIylQh8F0ayN4
jxpTsC2tPs+78OtSWaT8tOhjp6oxeoM4pMYphznXhRtYTy+V1yCYdJ6X8lskMCcl0GULYCVSU0c7
G4BVTFYjWWGE+GUhQOCZdn/QQQfZIgJ2Mw5Q0VTZnvMPG6Cw32ylFnsVtjEWTtpot912s0NghOlm
NsB0RRl7nvD9LCqLE8Los8UETXntPA2BWNq71BZHHM4wyBHh64sSlFmK26JJedmBPCzmaORq5344
v1QWabrCNYyCErfyc9YHeVVDs0UQ4go9xe6FiWcLTKw+Yx+FgP1iBZhFKOTMCjrnmUBpetyn8srJ
hLCFigSKBB6UQC8wBKZpnOGgKEEKcMyHAmBSSIcZ2S9TZm0DCTpAJajT2jP+6QQrs9MRXxhwY2xp
VaDaBVNmeLRNS9PgTC2x+0n59rIppnEHucbLA1lgA6VMKdVlkb4Dkp7pMGjXAIAyusWWCSEzyogZ
oU6MHIElB8A0PWuDcPX06vKaLJnU81zuiwRmigR6KcBRFMYVIFDlc5mApaorwLksj1L2IoGplECn
DXBUmeO0KhZQ5jqx6IONjtXmQkUCRQJTK4FJGwFObTFL6kUCRQJFAgtKYNJGgAsmXZ4UCRQJFAlM
rQSKApxa+ZfUiwSKBKZQApOqAFkJ9TNHp7DMVdKjzM8oeXkGL7nkEjsu0u/bftmrWd9g3RY2fd6X
fxpnlNeccctB3lNBeMuwsb+JOJ6V41b5nY401fU2HWUybJ4mVQHKDzYceeSRA+e1jn03MIOWCMPm
p4ndKHk5f3AQOc+2izjL1Q/MzoW96aabwlve8pYqSF/+VYQRXwjdxs4hHjHbXuzOO++81rbI9qLt
ttuuOgS+F8NJDNS33iaq30xiUSc8qU5f4AnPQY8EwL7zPXM9gs+aILgLjpK08TwIwqtiOWr+FeNy
MaES6Ftvc7XfDCL8XiNARiHy4rAT6dnOcu6551oabHjGnU2wVWGllVYy8AFOr3fS4clhhx12CPjQ
Eh/AhBwJs89OoGfPIKfKC2bLTrgnPaYk73//+y16W354ucUWWwRBT4UNN9zQ8rvJJpvYRmPedeXn
xBNPDPL8sE3OW2+9tW3oJh579+S5EoDml6dGkKdHlteNN94YBBUW5P0SVlllley0f8cddwzC9yMZ
I4AXyANpbL/99lVc8k5YeMqjJOy3336NIxRcE3fZZZcA2AR1wugQYson+DHbLL7GGmvYs5Q/nUoe
K0GQYUGHpgdGSE45mZLeXnvtZXVMmozq2DA/XmKk+tnPftbYyJvG5Cjvl+peOIq2ETwnF6HiBOFJ
VllhRASQRxMJzSissMIKAdkI/acpSPWsrf1R74KLC8cdd5w5DOAMcOqpp1bxBLMWzjjjjCDMSWub
O++8c+XuSVnpOxxXuvbaa1sc0qGcbB8T5mM1yk/rra2+KWu93+DPj0zYh0oaTKVz1FbOXL8HlERe
WmPYylPMZDLm4XS56eMSA8jp8ccfHzkVHoy+Jz7xiVHeHBGXL3kwNOLnwVfTCHN5AwIKNzLc49yF
rZ6ubFi9cAeJ15Yf3uGGJy8NAysFFw9QVSlOXmXzA9gpeH/kFXxDNc4omHmLJ2QWwwXEJRBIL4Bc
c2UDLFUNP+IGd9JJJxkeoDw6jFf930c/+lEDj/XnZ511VpQiMeBTynL22WfbK0BPcaMjb2AVrrzy
ynH//fe3d1KyBtfFzTHHHBOFUBPVSA1wFV5SZlHINQZIKx9je0dY59+F5ZiTKe0C+C14IDvcEQGx
7UMA3OqQ9sag1Bl8IdqcfJ2tTrhHJrgXQjm5SAHF1IUSee20004WL3WNVKc1V0XqlrwDrqv+Wbkr
WoTkX1v7k33b+oMUVLz99tsjfBdbbLEoG63Fxh0UN0p9bGIdE5P8pHiV1DP3xx57bKRvADqsgUGk
HXm9wbStvuVdNAavM4dnmRRtzGVbOXP9nnxTV/oYGC/6Cm6j11577Rje0+WGr3WWhFBSIR/LKBy/
//3vx0UXXdQqEUHQUJrw8wiLz+/8+fMr/iiUNgVIo6Cx0GjwP0ZwKCUoxb7L5YewNA59gbk0+uAH
P2g+wF35AVQU4FNIX9V42GGHWWPlHgVIOa+++mpuY46X3AajIK8MzJQPBiTXuUi+mwjZgX5NGAh/
ZfIMeUOnA5A+AKpOZ555piFTc58qQFC5QeyGQMZGGWu0aPcgWOOP7OT8u7Ac22QKHxCrUcZ0aAhf
ZTpfH8opQNoNiOPIE19zjWrNLxq++D1/+MMfNsWQk0tfBQiob6qI+WDAF9DaOuXaHwqQeHJJrKKh
cMk7hAJsw8REAQpqzcpLWPAvX/SiF3FpRLqgogtZqGoXvMjVd9pvaC8oUPqWk0b2Y/zZ/Tm/uXLm
+j1xARTWSJZL+zDTH6YrdU6BQRkBm06N3HDy9tlnH9Xxw9SGnyeNb1M0fU2rwEwj2yjFHWTIz2FG
KYyUx+vKD+EY4juB54dRuys/eGgwBWd6CW7h+eef7yyqX6YjUI4XkFs6QiBcd9115itM+QVxH8h3
E4H6IkUQBMMf8DPmbA/gx1LCdEA5mKI5Mb1iapjCafFOyjmo4QeN0gPmCilYj9L624blqK95FadJ
przEIL/ccssFsBbBSlQnDfqQVfGGvUDW6jRmCmCBSaCy1h44cAqIMLxpBpEL+UA2TYTMfdrJe0wB
bdTV/p7+9Kebz7fHxyygD5HfWtvyG97hvw0mJpTiVdLnpAA9qLUfjWAX8BfvW9/4r5MWdUSb4++i
iy6yNlQlklx0lbOt38OCBSTaM4Q5arIOJrMEB/zXqQCxa+yxxx5my8CILnQWAxV1bL02oAKNEg1I
FIACJ305/HKBXwAB6PhduINd+YFxU5668qMvrq24apRledh7770XyKM/yPECJJVGhtJD+WCPE+JL
0JTIoy/wi52UBoPdDRtUCv5KYEASsPWg8Jw4jGrNNdccU1YUBvYh7I6kzRYTOlUX9cFybJIpfOlU
wJzxsTrttNPMZpnavbrSbntPekCsaQprNlyULNBiwKhhJ8W+2SUX2mj6gZBZoDE56jN9B/hEG3W1
P4A+qAcnzZjG1CfycsLuKqSfCrzD+xTvsTWnYMKAYiBXyu40SH2DEYktHmXsf4D1HnHEEc5uzG9X
OdvaA0yw9/OhYpsRHxfa5HSlTgWI8ZyvP50K0hDeRnZpJTcVjq8XikA2DAuv6awtIjSF5Vlf3MGJ
yg98AWrQtMvyS2duK2OubJo6WOPli8uCBcdV+ii0rewYuPniyx4YNGVaIBidH1liXAdNhk4tW2HA
qJ4SSpL9gCwA0akpE6u+Xg4QZRgNp0qB+H2wHNN00mtmBNQx6TGSZabASBb6whe+EDQ1ToMPdM0o
TzauanTGghsy4jnUJRdGWHywqRM6e5vRH37kFYXDaIy6b6Ou9kcd+CIKHylNi20k7vz6YmLSJlCe
vr2JPLGA8uhHP9pZ2UcxV9+M4sgP1IVnWTF96KKrnPXw6T15ZBFTporAzA7cy2lL6hxZwniqUYnZ
JzDgcigQdjytFNoiSA4/D5uIvjy2uMGvx21KENsEiwza7mKnp7XhDubyA1/sVanh+6ijjqrsjrn8
sGCi6YstSGgEFrWKZjYo7HFuA8T255TjBQ6ivpBWHmSWngni8eu/LLqA+acGW71yGx0PWGDAhsOJ
dCzygA3oNsbUBqiVRLO9Uj9S6BGMRmxP2C9ZuGKRQh80SyPlTzjyzLM6lmNOpvrKW3rwxWaFzRFD
OIQNDyN9G+VsgMRhYYU8ud1MndJsbFrdrFjm5KLRRxRMmy3aYadkcaJpEQQ5YvCXErcFK61qmyG/
yQaYa3+0CRYIkQE4jvrwRXg5UQ9tmJjpooyHP/zww80+jN1WI97qtMC03nL1XceMzOFZepr+mysn
NsBcv4eHptdWV46l6Xyn2y+jg14kT4fqGEuNICpgzq7IGrKb8Z7fLmKFC+G6QT0NT/yUx0TkBwXH
6Xe+YksH0JQlzcaY61zZNAWwlS9WX0dFNEoWQliwyRGLEGkYFkUwakPUXdsiBYoAo7q2luTYL/CO
BSvZPCvF5wFY0JIt1W8n7DcnF+TPIlIXIRfaHgtHfaip/aEA/eOiKfUCiyj+IaJNydTTJxnj0ZX/
XH3X+w0fQerKF8q6MtFUzq44vJcZwT6k6Qe9T7zJDlPQYKbt2HzmZ0xbN4JWicdM22Z+qdpLcLn2
HLIAwLS0idjfqo+CmVqa3s+WZ1dccYWZRTQKDhrZTutiNS9NTussl8zNFAkccsghMyWrI8knK+9s
cm6juYKJyYIiawbvec972kQxbZ6XEeC0qYqSkSKBIoHJlkDnKvBkZ6ikVyRQJFAkMFkSKApwsiRd
0ikSKBKYdhKYUAVYcMtGV99ssJU70+gYFk5FAkUCYUIVYMEtG10LY2d93UVudNwLpyKBuSmBCV0F
xtWnDxXcsj5SKmGKBIoERi2BzhEgPoE5jDOUXBuOHD6A2hxqeW7DlBsUtwyeuIG97nWvM8f7ukDk
bRLk/VE95gByHOvx78xhx5EPsNiccGXD17aJtMk1yHPAXJ5w9cHfFqxAIZRUOHzshXJqwxnM5dXj
1n/BjcMPFn/hFNuuDbsN9ylklZKQT2yfFs8AfUA+gECAgZj6bqdxynWRwKyUQNfOa3a3446EG1Ed
46wPjpzj2eG+04TTxy52gYdGIIlwoWJXP7h8uM0J7cOw4HARcygo3L7YbQ/cDrvU6wQOH25ITsAA
4abFTv8cdhywTo7/R1xgv3BlaiI8BuS4bnh1wHgJ7MBclsDrI58CHo1SjBY1hzOYy2s9XdJUAzRX
KtKUIjR3LfmbWtA27DbqjLyyMx/Cu0W+mubxgfsfshUKjnkmaN+WucIhq0JFAnNBAp2ucChAOl7q
EuYYZ31w5FIF2ITTh5AHwS1DAeZ8a1Go+HS6wgRfD2WJOxHl8Oeki3LEtxYaVAHCC3c3CPcx7lFS
EP6x+KBCuKS14Qy25dUi1v65AkzdogQGEOV4n8Vug828efOikJqNI2XGZxcCcBTZO/HxId8o2EJF
AnNBAp1TYHVsg++WgzyXRo5x1gdHzuPwC6qMUxtCSh/cMsflc17pL1iCoKQALwUSxgUXXGDuSaPC
jvO0wEOT8rRb8O+4B50EAoUDBBIohzPYlleL2PCPNFIZck6KfD0tPdBk2jAbgdvi2AIIpBJHnAHx
g3vHh2NardF+mQY3yL48mp0S6LUI4hhnjlfmGGcoRSB/UuK+bnPy93SuLnLcMo14qqDg4PWJ6xHw
x8SeB2yVpt4GQglOHwoRXvhkQuTVMfUom6Z+ziJo6lhdN1105UdfT4uW4gwCtQW+XQoq25TXpvR4
1pamY7f/C28SAAAgAElEQVRpShsAYAU7DuXo9fWmN70pYG/EXsvWpFNOOcWSQNaCzw9CvKmSBLYM
hVioSGAuSKBbI0kKKI4mjLPx4Milwh0PblnKx68ZAQL6CDoxiyZQF3YcYJEoCA5AYvQG7uEoiFFW
DmewKa+DptuF3cZBRxyGw0FDYOoBwgmBg8dImTKjsGWusAORwByEWGwaD56fMSn/igSmsQR6KUCc
vE8++eQADDudWQsWNspj9ATah/DPbLQFZDsrjKwoDkIAeKJgQZ4Gjl4HCRmqLGgSjOBYhWYU05eY
kmpBIjCddjhuADtPP/30IEw0A2gEpFE2r2pv3aabbmqgnqSpg5RspbVverlwOIRzoh0nrcEXpcOI
2ldwm/Ka49f0DvBMRrVa7Ankn5EtJ3P5VJc4TIPZbrSjTpZzAmYe+RIPswanu1EPKEwIVOw2EFHn
UX6LBGayBDrBEFKIH6aFoBzXz+iVMd8gxVGQWlUcSh4gFUMywtsvqMIoMK0cV1NWe9HzHwqG+Cif
lJgKC/PPzsxoUtRA8mNnw942KmJKig0S+TCNZUTNWQ5uV23L66DpYwdEEWJfZUTHKJgzKroI+Ca2
v6AMsVkWKhKYKxIYSAHOBKFg48NGyegH7LU+Z2JMVblmUl6nSkYl3SKBiZRA5xS4C+NsIjM3DG/s
WRxyzVkS01n5UbaZlNdh6qLEKRKY7hLoHAFO9wKU/BUJFAkUCQwrgc4R4LCMS7wigSKBIoHpLoGi
AKd7DZX8FQkUCUyYBIoCnDDRFsZFAkUC010CRQFO9xoq+SsSKBKYMAkUBThhoi2MiwSKBKa7BIoC
nO41VPJXJFAkMGESKApwwkRbGBcJFAlMdwkUBTjda6jkr0igSGDCJFAU4ISJtjAuEigSmO4SKApw
utdQyV+RQJHAhEmgKMAJE21hXCRQJDDdJVAU4HSvoZK/IoEigQmTQFGAEybawrhIoEhgukugKMDp
XkMlf0UCRQITJoGiACdMtIVxkUCRwHSXQFGA072GSv6KBIoEJkwCRQFOmGgL4yKBIoHpLoGiAKd7
DZX8FQkUCUyYBHorQM7KvfTSS8Phhx8eDj744PC1r30tcHKb07333mvP/L7v749+9KPwve99r2/w
gcNxZu4111wzcLx6hG984xuB09OmkoYtC0db/uY3vxlp1qn7L3/5yyPl2cWM40TPPPPMrmCT+n46
tIthCjzR/W6YPE1FnF4K8A9/+EPgEPStttoq3HTTTYHjFznvdpVVVrEzaMn4f//3f9uZwIMW4itf
+Uo47rjjBo3WO/x5550XjjzyyN7h04DbbLONHa3Js3333Tdcf/316etJv+5bFuqIQ9CdyPuoPzIo
VD9z2dPp+5vKtW8cwpHmm9/85kGiTEjYNP/ToV0MU8iJ7nfD5Gkq4izSJ1EqnLNsUXKcCwxxqPj2
229vB3Dfdtttfdg0huFg9elK3/rWt+yw9umav7Z83XfffeHiiy+uXt9www3V9aguOMCeNjAMzVS5
ellnev4px3Tudy7nyfjtHAHecsst4YILLggnnnhipfzIGAdo8+z+++8P5557ruWVw7g55HvppZcO
z3ve88LHP/5xe37GGWeE173udXbt//bcc89w7LHHhk9/+tPh/e9/vz+2OBwgzqHhm2yyiY02eXnC
CSeE//zP/6zCcej5mmuuWd1/5jOfsXsOBn/jG98YmJKnxBnBG220UfoovOtd72odfb7hDW8ITLl2
3HHH8J3vfMfiMW1gJPy0pz0tvPa1rw2MjJ3OP//88NKXvjRw2PrWW29tB437u6bftvw+8MADliYf
Gnjtt99+gcPc60T+OLTeCfkge6bJb3/72y39NdZYw17zobrsssvsOsd/iy22CF/60pfChhtuaAeq
I38OvW+i22+/PbziFa+wV3wc99prL6vz5z73uWYioS00UV2uufw0xefZZz/72bDSSiuFZz/72VZm
D8col3rhMPj11luvape59kfcQequnn/i59oFfaCpPROvrQ1gbqKtE4/D6g855BA76J44daK+V199
9TGPX//614err77anrWlkfa7rnpnhkY+1l577fDFL34xvOpVrwr/+te/xqQ5Y2/UULMkAcbHPe5x
rWE0DY5SYFEdjBYfJcx48803Rym3uPjii0d9LaM6S1xooYWiGorx+eMf/xgf/ehHR00p4wc/+MG4
+eab2/PPf/7zUcoz6mDzqEPDo5RkXH755aMUQNQXK2okWuWDMEsssYTdyzYXn/rUp8Zbb701ajQa
t9xyy7j77rvbu4985CNRCjFKIcZFFlkk3njjjfZcNqwoJR6vvfbaimd68atf/crKLTtXVAePagBR
HS5q6hDnz58fV1hhhfiBD3zAonz3u9+1sMjqjjvuiDIPWHg1kpRldZ3LrxqvyYP8qnHHlVdeOe6/
//4W18vCjTqH5cWZEkaHwZusTj/99CglHX/xi1/Ya/J+9tln23WOP+Ge9axnRY0eI2V6wQteYHXr
aaS/mg1YffPs+OOPj1IMUSPPqI9FXGaZZaKUcxq8uq7LNZefKtJDF56mlFzUqDZKEVqd6iNtIV7+
8pdbXvRRjtSbzrSO+ohl29+gdVfPf65d5Npzrg28+93vjvqYxquuuir+13/9l7UBb2t1mfzgBz+I
j3zkI8c8fv7znx81aIm5NNJ+l6v3z33uc9a3ZEe2dvGSl7zE6v0f//jHmDRn6g1flizJfmYNui0Q
FaWvf6UAUQBOm266adx5553tdt68eVGLJ3YtQ3Z80YteZNdpRbzsZS+L+vJ59KgpljXwK6+8MqsA
6QyLLbZY1Cgv/v3vf48ot1/+8pfGJ1UaG2+8ccWfPCy77LJVWk0Xj3/8403Z8Y5G8rGPfawKduCB
B8bNNtvM7un8u+66a/WOfKP8yVcTteWXBstHhEbtRD6f8Yxn2G1aljYFSEAUmEaPzsLyjgLs4k8Z
9bWv4lE3fDyayJUR7/g4oah/+MMfWlAd+B41cmyKZs9crl35qTPwNInntNxyy0WNSqJGTVZuntM5
+UAuuuiiVR20tb9B6w7+nn+uc+0i157b2sBf/vIXU2goHKdzzjknamTtt2N+cwqwLQ0YpP0uV++U
4ZhjjqnSPOuss2aVAuycAmvUE5ju8FcnpoASsk19eKcvj01/Pdyqq65aTaF22GGHatWQYbRGKx6s
+v3Zz34W9BWv7qXUjF99OksANfIqnL5K4bDDDgvvfOc7gxqnGed///vfV+/9YrvttgtqTHbLVG9Q
Iz6ycHrMYx4T/vznP9st0xDKxNSYP8I94hGPaJ0Gt+WX8mtUGzS69GRsGqTRcOeUI5VHFbl20Yf/
v/3bv1WxyIs6ZHXfdsFCgBRRoL4xfxx66KGBuuuiPvmp81h44YVDmkevB43uzVwiRWx1sM8++4yJ
2tb+Bq27MUwfumlrF7n23NYGWGBkCozd3dvT2972ttDUnpvywjNvC21pNMVLZZrWu2YRAXuv0ytf
+Uq/nBW/nQoQO5KG2OHrX//6AgX+9re/HTS1DRtssIG9qysqjQjCWmutZe/e9KY3mX0Khcm2jCbl
g/JC4E5stdDX3mx7pJPaHVKFjJ2K1UGNPm3LC3w0BXY21S/2IVYS2RaDIRvb2CCEUmuiJzzhCbYq
fvfddwf/o+zrrrtuU3D7KDTld6mllrLFJhSeEzZYbJ31tOvySOXmceu/ffjX06nzaLrnQ/ipT33K
Oulpp51m9sZTTz21KeiYZ33yMyaCbtryJ9OGLViRLotAF154obVN5AS1tb9B686Y1f615SnXntva
LPmB2HLmbUnT7qCRXi3Vh2/TfoHypM9AbWk8HPPhq7YyUEfpIid5mU3U3KOTEvJF5wv04Q9/2CrF
hY0iYysMioYFD4hFA9kM7Pq6664LKEhNO+3+sY99bMCAzPYMjKiy2dnz9B8LDF/4wheCplD2WNM2
G1U86UlPsjRIk3dU8ic/+ckqKunAG2O8ptZBU9MxexQ9oOyOtkCy2267Bb6Oz3nOc/xV4y+jCtkr
G9+lD1/zmtfYyJK8aa4QyPeKK64YNB1Pg1XXbfllFIW8MToTF1lrylHJsGKgCxYb6OTI4qc//al9
VPw9HyxGbl5X/nwQ/h6nzy+jLRa0NOW0jyGjMD5ebeRyHWV+GMkximFrFkT7YPGI+oDa2t+gdQcv
zz/XOcq157Y2wKiPtnnKKadY/mnT9L/6iNbTpQ1Tz9/85jftEeX2EWBbGh63zy99VbZMU8as+jPT
mlVUTe4zFxKoGfyxqbB4oS+b/WLTk/AtJosg2NQ04rOFDH1R4vve974xXNVhzX6gVePqeWqLwHit
lSaz50mBRK3mmTGewBjYsVVgW1OlG29fBMHup+lX1HQoakXMFk60UdvSSO1mPLjooossDxqx2Pvc
PynKqI4TyTdpswDiBF+tKtstNj8WcjBGswCA/U0N0oMu8JvLL4sIWsk2ux8LEuuss05ELlBaFhaX
kAWGfuxvGs3aIgjhMPyTDykEbisbINc5/vUyHnXUUVUZiZuS2+N4phG1tQnSxLZLG2ARp41Sueby
U49PmnWDP/VOXVIHmq1Y29MHOcocYnmnHTk1tb9B6w5eaf7rMkvbRa4959oACx8sZLCwxwIkbQC7
ahu94x3vsDZNfbMA+OIXv9gWQXJppP2uXoa03jX1Nhs/vKWcoxSx1YH3+7Y8zZTnC5HRvhqd0QZL
/thhsAvw20RagAiqOLPHNb3PPSM7TOcYwWgV0r62aXimuXzp62nzFWRrDPG1cpxGGXOtleLAtJ7R
GiPCLmJ6R1napghpfKYe99xzj20ZYJtQjnL5ZeRCPqXcbCtMGx81cJvuIY86IQfyzjSsTn351+Pl
7hkpk2fsYb5XNBc+leso84MNja1Q2LGQAdNItsV00SB1B680/zneufacawP//Oc/ra8xmqcfdBHT
XdooU9aUcmmk4dquMRnpQ2sjaEa+TMV31NYwNtvPBhpIAc70Al9xxRU2VWOxRl/qmV6ckv8igQmX
APsFTz75ZOs3DBjYv7vaaqvNmqnwnFKAbBDFRoTtEptQoSKBIoG8BBhBYveT6chG1Ouvv75t0u4z
I8pznh5v55QCnB4iL7koEigSmC4S6FwFni4ZLfkoEigSKBIYtQSKAhy1RAu/IoEigRkjgU4FyOZm
sP9GQWwOni2rR8iDFfFRw0z1lTN7vdicri0TU5oPzy/5Yb+Y70Hz5+W3SGA6S6BTAWrv1VA4f02F
ZpNzuoG5KcxMejaVmGog3gBpBJrKVObD64ttS7gasqWlUJHATJFALzzAmVKYyc7nVGKqMfIDagnf
zNnmnznZ9VjSm7sS6BwBIho2czbh/LGZmM4HLLh2nxtgal98N1x88M/UrnOTPhuccWdjUy+4Y/gL
O3XhlXk4/8VlDqw6trrgkgaSMtSUX4/jv2zCBpABcANcknDwp3y4AuJ+Bg4d+wkh9kg5liHlacPE
Y5oMViCbktmKI3QbT64V//ATn/iEyRyebC7GvQzXJgjH/rvuuivI08bME2k+eN+G35bDVGySDRvf
c7h0Rx99tAE3sLEceRUqEphxEpByy1IO50+77g2uCnckTW0NhiqH7wZsEi5KwFVJcUYBAkTteDc3
JtzbeCcEDcNywwXIYaFw1emLU4fLnMBUo5zyzSUMlzhc5uSbHJvyWy887lZyoDd8OynSiJuRvE7M
1Y38CGw0SjFatNSdqA0TD5cw3OnAR5S3QTzggAPM1Y1y5/Di4K2d9xE4Mvn6GhYi+HwQfHBNkknB
ypjmI4ffhvzbMBWbZJPDpQN6TB4fVu9g/2lzrLljgfVYqEhgpkiA0V2WXAE24fzRaaTxo9BnjQcd
k3tXXDxM8ezogBq9RIArAU5FCXgY/F/xXXTivWCW7BYF2BenTqMSAwt1PvyCaUdnruc3DePX7uMq
FyB7BGgrZeI5hN8rPrhQqngoGz65dUw8MAQd+5A4GlVFwUVFfCxzeHHw5iPhRPooYpeRRoWRuoHS
fOTw27oUYFqXsullcene+ta3GmCtZUD/NMouCtCFUX5njAR62QCbcP7S1Vymd1AffDehFZtvI1Nl
VgxBEMGHF99KkFCcMKaD6uKU+rumeGX+3n/Jg0O1+zPyn8L4eH79ff0XP2OBkNpjcO24B7kEwh+S
qWGdwMQDoospMz68THVxt5PSNYQaD098oTfbLXnViNBfGYYeMnBYMSDxnSgz/qH4/+If2kZM4fvi
tzWt2LpsyDflBJfOIaVInz8IODGORHCqy9yfl98igeksgV42QO+QXpAU58+f8dsH342zQcBuQ8EB
nAmBgQakluOf8QvE0xFHHGHv+dfX9YY8oARSAlNv3rx56aPsdVda+rwtEB8F3oSJh200Vb4oEDDr
AFPN4cWRQFc+FsiEHuTw2+oYgimmYp1XFy4dH65UzmwJKlQkMNMk0EsB5nD+0gL3wXdjVOMHKuFj
iDLFvxCF5yeZMfrA4dqN/mkaXddgsOnMjqDzFCwoyocDYsB9m0hqw8RjJCh49mrhA8BQDunBsTyH
FzdsXnP4bXxk2jAV6+l14dIhT7Y1IV9w4ihXoSKBmSaBXgpQOH/WwLUQYVBSgJoyrawTowKmuKxg
AtTIH51Dix31oKb02MsmW1KA/0knnWQnesFXNr8gXDNbJV4gYscD0JNl6zIkasBRgZcHwSKdTnaw
GOo1aXBoPCvFpMmqNkCWgLnqQBsbgTK9pZyEgw466CCbzhKHkSIryumod5iMcIKY7IA2FUf+yJYp
M6NJndFiJgdkDMQSK9o54vQ1prqsQmMSoEw6H8KisCuA6Ty8SIdycl+oSGAmSWAgMIS+OH/D4ruB
Iow9EEULptt4CHw0pmgcLQie32RQDhOPbTJMk1NbJnliOk0+2/APB813H/w2FBn5wLbZRUzZmd42
4dKRdzAAmS43IXx38S7viwSmWgIDKcCpzmxJv1sCsx2/rVsCJUSRQH8JFAXYX1YzIuRsx2+bEZVQ
MjljJFAU4IypqpLRIoEigVFLoNciyKgTLfyKBIoEigSmgwSKApwOtVDyUCRQJDAlEhiXAmSfHqdp
QYAXsAI5F2m6ygEQB6+fuVgv9TIXbMu6RIa713Gf1bnLM73fj0sBgkbiyCa4go0XHBT3OvYYzjSa
TnLAdY2tRBB1Il/mocSZ8hmKwRREAu0Gb5w2kj91wbZsE07P57iwsoWKjysLbqPo9z2TnpBgI9u5
iofBeElILpU3yHh5TVX8qZYDG5f32GOPcRd/VHzGnZEBGNx8883hMY95zAAxStBBJYDHFvtHAeGF
RtHeB83DKMP3GgHm8Ow8M9tvv30QOondstF2UGy/n/zkJ0FQU3awOPhyED7DW221lR20zXGWzt9e
Jv+Iu/rqqydPgoER4AIHfeYznwl4iLC5Gu+T1Lf5/PPPN6w+PEW23nprS38Mo+RmussBmeO2uKMO
rv7Od75jOWcTMy53uLa99rWvtc3YXiTADJAbG88pu/v2NvHxOP6LLODHoePrrbdeOPfcc+3VMLiC
zpNf8oA735e//GXzVFlmmWXMk8bD0OGasB4Z/ZEHYPkdo9HjpL9s3p4r2JaUu63N5nA727Ao6dd4
buHoQB2w8T/t984T7yA8ufB5x9sJymFR4nGEtxTYk2CBQjkdYgFG9U8NIktSFq14dlJKBncFAyCr
zj777KGx/STUKDe6qI4a1QksT2uttVaUEONvf/vbKBcyeyfPBHuX/gN+S54K6aOoSogXXHCBYefJ
SyHKYyHedtttURUTd999dwv73e9+N4I7KAUZJfCo84KtHBraj+HFzUyQg/xyrTxSHlGeJ1YWYLP0
tY7yj45y0YtqaFY2efVEubBFKUor284771xhBdb5WITaPyDNwECUPcjwG4WAY9iEQI7JJS6mGJE5
XMEaW4Mdk9te3HjjjaM+bPGUU04xfhrdxRzWozx/oj6WEZgu6qqJgA9TvzEoNviB0Qi0mUa7jViR
Mx3bMtdmc2UDXo06rGNRAsVGWxKIh8mLvuj9HnnL1TLqoxhlyopSeNYW9TG1qshBsQk1yXSM0J+i
bIqdOqSpbod91okHmMOza1KA4P8Ni+0nMISokZiVBSUkP1bD8aOTQbJtGZ6e3ST/cgpQI4YoSKsI
gCcVCBgrnR+icnbdddeKk/yWrUMQp04zQQ7kmcaJsoNonOTb6cADD4w0MgglhxKAUJYCpogCS7B7
/qV8qocPXYBpSF1BgtSKAnuI8gOPyA0FiJJxjMguXMGHWFY/jscoxOvqGeUQ4nTMYT0SmLp873vf
W8WrX7gC5GPnRKdF+dfzPRuwLdvaLJiV1FEbbmcOi/Laa6+N8vt28VUK0OWlGUD1Tojv1sd40KUA
5ScffeDRpUOqBEZw0TkFBpkFUAEnHN7BswN2qYlSbD+mXfxxqrxGcVXw1B+2DdsP6CbcuoTkbFNX
0GFAeOnrcO9Yd8DagzojtGmDn9p2222DwEgtL0ydgXL3fOL0D2jAPffcU+XVL2aqHCiTE/YxYLgg
EHkwDTD1Bz8QU0Bfog6QBzD9yA4knDo14Qq6nAGJ8Dqox+MeGxNhnWgj5LsN61EjHQ/a+cv0LMWd
BL8Rv3Enz3dfbEvigmjk7W1U7Z/89Cmv59fzn/62tVls7cgU0A4nfObpoyxsQCl4SIpF6eHrv6TF
ERSYRJxyZ9W4vDws9eC4k31k6PHG+9upAHN4dk2JjwrbDzsDDRWlx/kXu+yySxA8vYGONqXrFcc7
gDx9+wcNFDQabApCczYlqCmwsSCvmvaOwSGkMa+77roLJDFT5FDPeBumoEYHZh/SKMBks/fee9ej
tt5jm2WhBRsPnenCCy+0xusNOI3YhSuYhvXrtjyPAuuxriypb5laPOnql7QAsEg/3OBKYkv2/E13
bMu2NgvIb1fZvIyVQDouwLbEJpjKF6g0J9pG2kfrWJRp2+mjQ5zveH87FWAOz64p8fFg+4E4AioK
gkKJUYF8DXT2hCETt40WgWMizje/+U3LEkdv+heGPXoY9alwRrKgTIM6A4Fpd84559hhSRpNB9kw
7RAlUJfrNBPkQJ4ZndEQu4jRL7BZwFjxsQHPDxk45fgQl1E8C1MQ8oZHGt/5MJJjFC5bnoWhHhgB
No0aPU7bbxfWI3mGf47mErZlW5ulPhhccHgWbZ2+c9ZZZwXZXXOiy74Ddo1RIycV0ncZvQKN5zQI
FuV4dIin1/e3UwHm8OyaEmE6NSy2HxXDMJpVSZSd7Dlh+eWXN3BUsOs4d9ah6dO0gbtiVEcFUgms
gKI8Ib7STJ+Aa2J1eb/99rMT3ngHf9mXAiuNYPJxAhtTYvJQp5kgB/LMKjd/mB1yxMiXFVNOzQMb
kI8ByoEVUijHh47FijpyY0rJyGijjTYKO+20U2OSOVzBxggtD7uwHjfccEOrv9w2IDoqyn4uYFu2
tdlBcDtbqmKBx/BkawzHtYIdSXuiTTDahAbBohyPDlkgY10P+toRNaqwFdW+4dWZ7CQ22dP6RrFw
+hpFVvScOJwIwyurxF3EYgmHDdWJ1SqM6xh/m4gFAQ4/wmDfRTNBDsigabW8XjaNkm113MNSNmEW
VsG6+LCqzqISRL2lBvCKyUMXpKXOYenV3w16Tz1TX9p2sUBUfewif12kKdiYdtYWnoUxFgtoI4PQ
sO2/KY1ceZvC15+1tdlhy1bnzz31z04LFhq9r2qwEQ8++OAxwVmApC30oVHKsC29ggbT9YUo74sE
igR6SYBRH7MJ9vPq42gzAu2+WGCPbi9mkxSoKMBJEnRJpkhgtkuAlWAW11i4ZPeBtiVN+Fk845Xp
QiustOrDlu/xcivxiwSKBIoEZpAEFrr153cWBTiDKqxktUigSGB0Eljk1p/fNTpuhVORQJFAkcAM
ksAiMZQB4Ayqr5LVIoEigRFKYBGtXo+QXWFVJFAkUCQwcySwiPbHzJzclpwWCRQJFAmMUAKLCPhp
hOwKqyKBIoEigZkjAU2BH0R/mDlZLjktEigSKBIYjQSKDXA0cixcigSKBGagBCZEAf7+978T7NQT
ZqA4SpaLBIoE5pIEZAMc/RR4/ncvDc941nPDii9eeS7JspS1SKBIYIZJYEJGgJ847tBw4ifPCN84
/7ywzqs2EPrw4jNMLCW7EyEBoc6E237yw3DPnb8O//znP8YkAQr0k5/6jPDvy60gROiRHVY4Jo1y
UyRQl8CEKMBHL7542Ptdu4Qrrr42fOzET4eXrrF2eLowwmY73SPk6t/c+avwW6Ekb7Dh8OCSs1VO
v/rFT8O6L185vGKNncOjHsKJ87L+/e//F6694aZwyZU3hGc/bzl/XH6LBCZUAgt94kuXjWsfzD/+
7x/hjl/+QqjKvwr33XtP+J8H/hC+e8FZVabvvue+cNDhx4ZHPOpxYaWVV63gxKsAM/ziv266Mdyl
Ec1dd/0mvOD5y4RVV1ohvODfnx9uu+cvY0p2/2/vE/T+neHeu++Sgrw3bL71DmPez4WbpR+/cHj1
q9bMFvWy714j2f01G2Y2v/z1r38pUN9nz+YiNpbtx7f+MFx3zdXhr38d228aAzc8ZNbwxi22CUsu
2XxWUUMUe7TQqWd9e2gF+Otf3xF+cduPw9JPe0JYRR1/+RfqwJlnPF2HUz96THpMfU47/ezwrcvm
h7Xmra/3S4x5P5Nv/vy728PKK/6/8BL9LbHEg4dy/+lPfw6HnXCmzsu4J9x7z93299xlnhle/KLl
wgrLvyC8cNnnhYvm/2QmF3uovG/+6lXCUks+Lnz9Mn007vvDGB5Pf/JSYZN1VhZE+/+F0865vPfh
V2OYzOAb+sgN188Piy/8r7DCqgueUTKDi9Yr67+/+2dhlx22CI9fasle4euB/vGPf4azLpgvVOpz
w3333BXmrbNBeOazlqkHW+B+kX8M6Qr3i9t+Eh7xzz+FHbfcJKy71ssXYJw+wL6z645bh9VWeXH4
+oPelQ4AAA0lSURBVLdvCIst/qCiSMPM1Ot3v+1hGPg//O+fwxKLLxoWesRC4W//e29YY6VlpfA2
CSv8vxeGxQQZntI/rvpxejtrr+/69e3h5z/97yDI4LDtpi+zcp75hYfPikgLjgJcdNFHhhvmXxb+
pnMlnv+CFcJTnv7MNMisvH7gD78PV11xSdjyda8O2235+nDSF789K8vZVqj/+7+/j0v5/eLX94Xv
3XybDuf6VnjvrtuEF2mQccKnzgp9dNtCH//8xQOPAO/8zR1hiUX+EbZ640bhOc9euq1cCzz/m77u
V1z/4/CT2+9e4N1MffCObdbTQU5/DWd+89rwl7/9Pez4upcvMAJ+QIrx1/f8Pvzmnt+FOzXy2Wqj
NcJpX/5O+Muf/6RTtO4K99x1Z1h51TXCIx85VknOVJmk+X7swn8M27xp07CIPoKDECPBz5311fC3
hQeb0gySxnQI++Mf3RLuu/P28MH93x2Wff5zLEsnfOGS6ZC1SctD1ILYO7ff0NL78kXXhbt/+8BA
af9VB6n94Ibvhfe9661hheUelOGPf/GbcMn8H3XyGXgbDKetPWrhscrvD//7x3D7b+4Pd9x1f7j3
/v8JO79p3gIJ3/KzX4f5N/40/FUNe7YR3jR/+uuDdqtFdLIdCu9XUna/vvt3mur9Pvzxz3+zIv/l
L3+24fnhGhFdNf+a8MiFF7Jp8SavWiPc9T8hTMSWpKmW9VZv3GRg5UeeGQluqbifOe+KqS7ChKRP
p/3eVd8JL13pBeGIAz4yZlFoNraDvBAfHoPdqf4yCP1N/e76+ZeHbTZ7Tfj4KZ8M22y9dVhp+eeF
6265/f+3d6XBURxX+FtpMUiYQ9ciIYQ4hSgLMEQmIAqRELAVDLgMict27Cqc/LIduxJfoUzFBhMq
DpRjCldISKqCg8slQnwEl4I4BYEAQoBAWCDQgSR0oVvoRBJa8t4sM9vyjlY7gjg7Q3fVbvf0Nf2+
mXnz+vV7PT49T3Znj/vkvpyYTRgenZegSX6l5dW4UFCJq2X6H6dmbp6ReRG1Da5PUfpyDjPWUXHc
sfs42jvcDK+OJTxa+LheVa4xPP4S3QtPL0VsTLRG6pa/7YHah5ZpgcQfUw/hlecWK4tfW0my6SZd
DW/AoX4HVk2rMUuKL/9kkfKpxr+SlGzFUEULhpdzs/HaS6uQnDTbg0Qr3gceRAoZ9F0O7cgI7Z2d
Lub3m7dfVaTnlB8sQGraCRSV16OlzbeFNMObIYwOH67p/OobbyAnvwJFOsyvjaSe4+fycbGwQiPO
ygl1U4nLl/OI4VUqtm6D7C4Jb/niuZjzyEzEREf1CQG3t+rejOpHtln6P591lJihDdMT52vphFlJ
yDl9jJhiAB6e7VoA4DYqpn2CZrICJy105JzPwsghAfjz5vVwhIfpUpC6YxsGk+1scPBQjBgZiuiY
WESOjrHswlAvBigwQ11w7mR2d3WS5HcY761+RVMd1DW1oK2zG51dvW1MvfVDdoBOb+UeZXGx7of4
Yn4pCko99XlnLxYrzK+7u8ejvVUzVBwHox1PEMObTQs+ooTH0+KT565g7swpuhBw+9s2m26ZVTJ7
SH2yce3rCjmffHVSSB/H5g2rFemQ89WgYqoemzluaW5C1okjeO5HS/Hsj5d7JSXz4Beob2hEbV0D
CotLcezEaRxI+wzjJk3FhLgpGGS3lq7YJnij+XLNXczvCFjyY4sKDqxf35l2HAgwpmu29xhcBZ48
wb3oUVbTDL32hzIveb3AVixUcVjz2oseiyBM77Zdh8EXui8G2EPvods291TAihix5BfpCFdIE9OD
Sd8XFhqi5au0q5iqx2aNrxbkoam2HFt+uwaTJsT6RAbjwT9+wJc+thCNTTewY+cXOHAonaTneRgZ
oi89+tS5n1USb/v+rjkzv3M0i1i3+uca8yujtYc/fZqGC2ePY/6iJwxRZ9gTJJrs/NRQSVzXeTtA
PfQad5KBY/ruVKVOoH0Qlq183mt9sxX2t7M2l/ODzroJlpprqsqQIhgF36Zyp3gnmA0AH8YrYmQ0
7UP3flvle0mz8GTKqx6mUEYGzPZxbHK1YlkKfr3hQ3SNmYLwiFFGuvDbugHCtFe8L7454Fu3XCqU
d994EQ/FT1aKSypq8dn+M2isKsJfNm/Ax1+d+mYzr8d2Nk0xEsRJWh15NwQP823Xl/a2ZrBoz6G9
vQObtu81clq/r9sfjlzOv99/nI7Swly8v+alXjSx3ZsTvr1MejU00UEneQ2pQUx39ZHfH6ZqX/4e
24cMo4Uf8ckZ+IhZj7z1g3V4652NaCRBInjosIF35ictSdurjcTbNb+ccwrM/KY95FIj8cJr6p5M
sBH0RxvfJR/yQOUZ0zrzIWF4S/zrtQ2YEOtavRwRHIgugXt7Ox/XVQP3YaWt+HniqtIjTmI/370X
je1OOAOHaOVtrS1Y8N0ETwW4hRdB1OtOIGhJX9Iqpu5G5kzl5pehgkyinlyciLFRdz91ZV/79Wt+
gTfXfoigSdPNCUqvUbvvi76ueTXNmH758iqN+fEsalf6KUVvzF0x8+PQV3ulUOfPMAPk+bbKACeP
jURG1pV+rfVryARk4Wy38p/7MDpQnbH7VZYePT98dAHWvb8FZbVttMvJDGW8TTUlePb1tz3GbqML
ePuW+03oUcECGSJGvdLClwl75YsM0+T0N9xoxXYy61kweyqSH4lHgJcFr21/z1CoHTZ0CPgXNPgB
RI8KxdjRYRgaNFgp4ykxm1LtTD+N0HCHqdERrR/E668S5XT2IDTIiX37D6CtoxtjoiKQ+q+TtKOQ
5/Oi117tRy8mBqiX3XdeVX2rVpiclIiL+UW4TraBfbksMfOLDLGTvVOi1o77MHperbGfJvTo4Tf1
79b9SvGD/nLvEUSNGYdVTz1OHh+DelHB5iHKIojBa9GrExMciBgZTZuAvH6H2ENEZ9ACYdG1Gqwg
aTBkhL5LaAV5DekFZppx4yMxb1YcYkeH0646iUg7eML0z5KoHRDvCxUDdqdc/8ZPMcoRho8+2Y+j
Zwt1mR/X12uv9qMXG5YA80uqkZ1biFkJk2hA4Vj5+CLs/HIP8r4+Q0rZKAwnuyUOzU0NtOtJFeJi
HUodrsuB23IfRjm10tiP/7zR87Pnn0L85AlIP/hv5aYVybhJ7nP/PJSt6DHEfCumbWTbpwYxHRDo
fiEE2t17AXrDVO3HjDEr7remHsTyhbMwLc5tVaHS0hfdzEDziiqV38PxsVi2cCZSFs7B3hOFsJvY
jVJ87+vRvmTxAtTd6MCufftR19iiwqQb67XXrXgn07AhNCuvc/IrERkRgtGjwpQ5uSMiDIePnUTm
mfPIOZWtdM3L9ytTkvD9+XMVRsmZldX1SltRAX5nHKaP2Gi35UajstKrRwy/rfnHgb0hWIF7pbgK
uQXlJNa7PEf02lkpjw1UK2pc0k0X2Yiq6Vaiv76pVXGTbL/ZpZFsNUNojTBKMJ07SYHP98Ay2gSC
LQTU4Avd2XklaGptxzNL5igv0GD73esW1fN/27FNUIHU1lQijAQpMeSX1uDspWtiVq90Y32tduwL
dlplShiWALkxKyCDhzyA5O/YEEW6CZbunl65TPmJnYvpKjKZOXa2QNdwWqxnxnQ3reCeOpqOKEeI
x/RWpYd3irlEXjGMXeG16j5FeLW+FeOuznb84dMDGmli+oPte5R8NpdSg9G3udrOTHH2pRIUk0T4
zJK5GEPbynHwle4iuo8yMnMR7QhFQ7soR5kJAWJCAvN/oLsRh9KOGCJgRkK8Vt9X7NQGhnWAasPz
l68pkktiwnhMnzJWzdaNL1y5hjO5xfTwV+uWmznzJrnesEJ666Z3MHG8GwfO5216mOHx7jcs4dyv
obWtAw8ODVJstcorPT2HRFyiHBHKYXNLm2F9jtiPmdINTW1gn+lFSQm0SBJviO7TuaWYHONA/VV9
X3wz4NBxsxvNJM0OfzAYW8icZaChjlxz/+c6QHFw/GDz24uncRNjRilvsPAQ12andY2tym4oRWXV
yLtaCau6xf1jXxYemzdNsfAvpmntVWJ6/GYuqagTobqv02XX6zF14hgyVH3PZxzYtcno29znzv2w
Iuv39v3nAgpKqgzRzXZzlXUthtr4Ifm0ddUlLEmeQbviuFUBRsbJKoWjZwoM42B7a1OqeWVnIwjJ
uv83BMZFR+CFFck+39zM/D4n636OZegfAXYr9OZB0X8P928N25sbJQO8fy+/pNwKCLB5jFHlvxXo
vhc0GF4FvhcnlX1IBCQC9w4ByfwGjiUZXckZ8MDhky0lAhIBMyMw4FVgMxMtxy4RkAhIBBiBAdkB
SugkAhIBiYAVEJASoBWuoqRBIiARGBACdnEnhgH1IBtJBCQCEgGTIiCnwCa9cHLYEgGJwN0jYJeL
wHcPouxBIiARMCcC9vqaCoQ63N+nNScZctQSAYmARMAYAg3E+wJtsK0dPjIMQRb4toAx8mVtiYBE
4H5FgJnf11kZ+C9kCsC7F1WtuQAAAABJRU5ErkJggg==

--Apple-Mail-6--307386066--

From mohta@necom830.hpcl.titech.ac.jp  Thu Feb 17 14:14:29 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F6CC3A6E7D for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 14:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.105
X-Spam-Level: 
X-Spam-Status: No, score=-0.105 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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XztEXUHpnLy for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 14:14:28 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by core3.amsl.com (Postfix) with SMTP id 43C7D3A6CDD for <ietf@ietf.org>; Thu, 17 Feb 2011 14:14:27 -0800 (PST)
Received: (qmail 948 invoked from network); 17 Feb 2011 22:25:16 -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 2011 22:25:16 -0000
Message-ID: <4D5D9DAF.50501@necom830.hpcl.titech.ac.jp>
Date: Fri, 18 Feb 2011 07:14:07 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: MHonArc mail archive line wrapping
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>	<2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de> <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
In-Reply-To: <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 22:14:29 -0000

Stuart Cheshire wrote:

>> - Limit line length to fewer than 65 characters and end a line
>> with a carriage return.
> 
> I'm sure that was all wonderful back in the century of teletypes and (if 
> you were very lucky) a 80-column VT100 terminal, but these days I read 
> email on devices ranging from my phone at one end of the spectrum to my 
> desktop computer with dual 30-inch displays at the other.

The assumption on line length is necessary to have multilevel
quotation ("> ", ">> ", etc., see above) with plain text.

> On my 30-inch displays your hard-wrapped text appears as a thin narrow 
> ribbon of text no matter how wide the window is, and on my phone your 
> hard-wrapped lines are too long to fit so they get re-wrapped to that 
> charming long/short/long/short pattern so characteristic of hard-wrapped 
> text displayed on any device other than the one it was created on.

We know that we can use directives of structured text such as:

	.in +3
	...
	.in -3

when necessary.

But, when plain text is good enough, we use plain text.

Assuming you have ASCII key board, 80-column assumption is
reasonable.

						Masataka Ohta

From randy_presuhn@mindspring.com  Thu Feb 17 15:00:06 2011
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00AF23A6F48 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 15:00:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFlhMkKl8NeV for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 15:00:05 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by core3.amsl.com (Postfix) with ESMTP id 2D1263A6F45 for <ietf@ietf.org>; Thu, 17 Feb 2011 15:00:05 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=suWrMT2PVfXxcPGYvjoZYcFipvUAospt0vBlAkMVK6sYDUR8z37uLZ51w7kdbXXH; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.30.226.148] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1PqCpw-0003GA-K8 for ietf@ietf.org; Thu, 17 Feb 2011 18:00:37 -0500
Message-ID: <000801cbcef6$f8c926c0$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com>	<2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de><D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com> <4D5D9DAF.50501@necom830.hpcl.titech.ac.jp>
Subject: Re: MHonArc mail archive line wrapping
Date: Thu, 17 Feb 2011 15:04:02 -0800
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.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888d26d9b9edb73dbfb255f85a160c830e4f01869ebd91f7ec1350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.30.226.148
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 23:00:06 -0000

Hi -

> From: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
> To: <ietf@ietf.org>
> Sent: Thursday, February 17, 2011 2:14 PM
> Subject: Re: MHonArc mail archive line wrapping
...
> But, when plain text is good enough, we use plain text.
> 
> Assuming you have ASCII key board, 80-column assumption is
> reasonable.

For reasonable devices, I would agree.  But the use case cited
is for  people are using devices with display capabilities
which are in some respects much more limited than those of
the teletypes and CRTs in common use in the 1970s.  The
question is whether to change email practice in order to better
support these limited devices.  (My answer would be "no".)

Randy


From cyrus@daboo.name  Thu Feb 17 17:04:55 2011
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 108543A6C72 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 17:04:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.255
X-Spam-Level: 
X-Spam-Status: No, score=-101.255 tagged_above=-999 required=5 tests=[AWL=1.344, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ubmVLW+lQMwa for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 17:04:54 -0800 (PST)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 0B6F63A6D23 for <ietf@ietf.org>; Thu, 17 Feb 2011 17:04:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id F22151BCC8097; Thu, 17 Feb 2011 20:05:25 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zrOdgsy+UIIE; Thu, 17 Feb 2011 20:05:21 -0500 (EST)
Received: from [10.0.1.7] (unknown [151.201.22.177]) by daboo.name (Postfix) with ESMTPSA id 5DE441BCC808C; Thu, 17 Feb 2011 20:05:20 -0500 (EST)
Date: Thu, 17 Feb 2011 20:05:19 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Randy Presuhn <randy_presuhn@mindspring.com>, ietf@ietf.org
Subject: Re: MHonArc mail archive line wrapping
Message-ID: <D8511239647756B5AAC6AE18@cyrus.local>
In-Reply-To: <16610_1297983678_p1HN1HvW025865_000801cbcef6$f8c926c0$6801a8c0@oemcomputer>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com> <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de> <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com> <4D5D9DAF.50501@necom830.hpcl.titech.ac.jp> <16610_1297983678_p1HN1HvW025865_000801cbcef6$f8c926c0$6801a8c0@oemcomputer>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=811
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 01:04:55 -0000

Hi Randy,

--On February 17, 2011 3:04:02 PM -0800 Randy Presuhn 
<randy_presuhn@mindspring.com> wrote:

>> Assuming you have ASCII key board, 80-column assumption is
>> reasonable.
>
> For reasonable devices, I would agree.  But the use case cited
> is for  people are using devices with display capabilities
> which are in some respects much more limited than those of
> the teletypes and CRTs in common use in the 1970s.  The
> question is whether to change email practice in order to better
> support these limited devices.  (My answer would be "no".)

All we have to do is make sure the tools we use actually make use of IETF 
standards (that have been around for a while) such as 
<https://datatracker.ietf.org/doc/rfc2646/> which would go a long way to 
solving this particular problem.

-- 
Cyrus Daboo


From mail@sabahattin-gucukoglu.com  Thu Feb 17 21:07:45 2011
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C5063A6A9D for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 21:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HOST_MISMATCH_COM=0.311, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1bNfw19sBwu for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 21:07:44 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com (sgucukoglu-2-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:7ef::2]) by core3.amsl.com (Postfix) with ESMTP id 4C5943A6C75 for <ietf@ietf.org>; Thu, 17 Feb 2011 21:07:43 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:55693) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S29314> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Fri, 18 Feb 2011 05:08:15 -0000
Received: from [192.168.1.13] (cpc4-dals7-0-0-cust274.hari.cable.virginmedia.com [62.31.227.19]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Fri, 18 Feb 2011 05:08:14 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: MHonArc mail archive line wrapping
In-Reply-To: <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
Date: Fri, 18 Feb 2011 05:08:12 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8C9F3FA-B888-4950-9058-1B36E0701B99@sabahattin-gucukoglu.com>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com> <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de> <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1082)
X-Delivery-Agent: TMDA/1.1.12-kg2 (Pluto)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1300597695.1f7968@sabahattin-gucukoglu.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 05:07:45 -0000

On 17 Feb 2011, at 20:34, Stuart Cheshire wrote:
> On 15 Feb, 2011, at 13:32, Bjoern Hoehrmann wrote:
>> That is the result of some clients and users violating netiquette and =
mail standards, for instance, RFC 1855, section 2.1.1:
>>=20
>>  - Limit line length to fewer than 65 characters and end a line
>>    with a carriage return.
>=20
> I'm sure that was all wonderful back in the century of teletypes and =
(if you were very lucky) a 80-column VT100 terminal, but these days I =
read email on devices ranging from my phone at one end of the spectrum =
to my desktop computer with dual 30-inch displays at the other.
>=20
> On my 30-inch displays your hard-wrapped text appears as a thin narrow =
ribbon of text no matter how wide the window is, and on my phone your =
hard-wrapped lines are too long to fit so they get re-wrapped to that =
charming long/short/long/short pattern so characteristic of hard-wrapped =
text displayed on any device other than the one it was created on.

Yes.  So the people who send you messages without information in their =
messages for helping you to reflow the lines, in a way that does not =
interfere with email clients and netnews reading clients which do not =
support those notions, should be enticed to do so.  And since you're =
sending such an email message, and using the same platform as I am, and =
since you are using all the right standards while I regularly get flamed =
to volcanic ash every time I dare to post to Usenet through a =
netnews-by-mail gateway, I wonder if perhaps you could help?

Cheers,
Sabahattin

From narten@us.ibm.com  Thu Feb 17 21:52:38 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B54C73A6862 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 21:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.449
X-Spam-Level: 
X-Spam-Status: No, score=-105.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15+zegvicxFQ for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 21:52:37 -0800 (PST)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141]) by core3.amsl.com (Postfix) with ESMTP id A57603A69D0 for <ietf@ietf.org>; Thu, 17 Feb 2011 21:52:37 -0800 (PST)
Received: from d01dlp01.pok.ibm.com (d01dlp01.pok.ibm.com [9.56.224.56]) by e1.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p1I5hXD6004134 for <ietf@ietf.org>; Fri, 18 Feb 2011 00:43:34 -0500
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 0E46F38C803D for <ietf@ietf.org>; Fri, 18 Feb 2011 00:53:04 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p1I5r3Yx208194 for <ietf@ietf.org>; Fri, 18 Feb 2011 00:53:03 -0500
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p1I5r3Dv022806 for <ietf@ietf.org>; Fri, 18 Feb 2011 03:53:03 -0200
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p1I5r3IK022788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 18 Feb 2011 03:53:03 -0200
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p1I5r2Se018559 for <ietf@ietf.org>; Fri, 18 Feb 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p1I5r1Qc018547 for ietf@ietf.org; Fri, 18 Feb 2011 00:53:01 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201102180553.p1I5r1Qc018547@rotala.raleigh.ibm.com>
Date: Fri, 18 Feb 2011 00:53:01 -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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 05:52:38 -0000

Total of 45 messages in the last 7 days.
 
script run at: Fri Feb 18 00:53:01 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.44% |    2 | 24.91% |    93172 | cheshire@apple.com
 11.11% |    5 |  7.41% |    27732 | rbarnes@bbn.com
  8.89% |    4 |  7.77% |    29047 | fluffy@cisco.com
  8.89% |    4 |  5.17% |    19326 | mohta@necom830.hpcl.titech.ac.jp
  6.67% |    3 |  4.51% |    16886 | alexey.melnikov@isode.com
  4.44% |    2 |  5.82% |    21774 | ben@nostrum.com
  4.44% |    2 |  3.69% |    13803 | daedulus@btconnect.com
  2.22% |    1 |  4.96% |    18557 | anthonybryan@gmail.com
  4.44% |    2 |  2.40% |     8984 | mail@sabahattin-gucukoglu.com
  2.22% |    1 |  3.89% |    14536 | stpeter@stpeter.im
  2.22% |    1 |  2.90% |    10856 | lars.eggert@nokia.com
  2.22% |    1 |  2.07% |     7737 | scott.brim@gmail.com
  2.22% |    1 |  1.84% |     6875 | petithug@acm.org
  2.22% |    1 |  1.63% |     6115 | brian.e.carpenter@gmail.com
  2.22% |    1 |  1.63% |     6101 | narten@us.ibm.com
  2.22% |    1 |  1.61% |     6014 | derhoermi@gmx.net
  2.22% |    1 |  1.53% |     5712 | lixia@cs.ucla.edu
  2.22% |    1 |  1.51% |     5660 | hartmans-ietf@mit.edu
  2.22% |    1 |  1.47% |     5494 | dworley@avaya.com
  2.22% |    1 |  1.46% |     5445 | rja.lists@gmail.com
  2.22% |    1 |  1.41% |     5285 | shuque@isc.upenn.edu
  2.22% |    1 |  1.38% |     5166 | iad@ietf.org
  2.22% |    1 |  1.36% |     5083 | paul.hoffman@vpnc.org
  2.22% |    1 |  1.36% |     5070 | jason_livingood@cable.comcast.com
  2.22% |    1 |  1.32% |     4925 | randy_presuhn@mindspring.com
  2.22% |    1 |  1.32% |     4922 | cyrus@daboo.name
  2.22% |    1 |  1.30% |     4870 | housley@vigilsec.com
  2.22% |    1 |  1.21% |     4535 | chair@ietf.org
  2.22% |    1 |  1.17% |     4389 | tme@americafree.tv
--------+------+--------+----------+------------------------
100.00% |   45 |100.00% |   374071 | Total

From cabo@tzi.org  Thu Feb 17 23:02:32 2011
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C45F53A6D34 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 23:02:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTKS44tyoBoy for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 23:02:32 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by core3.amsl.com (Postfix) with ESMTP id 7A0103A68DD for <ietf@ietf.org>; Thu, 17 Feb 2011 23:02:30 -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 p1I72qNc017463; Fri, 18 Feb 2011 08:02:52 +0100 (CET)
Received: from [192.168.217.101] (p5489FE35.dip.t-dialin.net [84.137.254.53]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 1FC27560; Fri, 18 Feb 2011 08:02:52 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: MHonArc mail archive line wrapping
From: Carsten Bormann <cabo@tzi.org>
Date: Fri, 18 Feb 2011 08:03:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <705FECE4-4D29-48A9-9F0F-7CF1571FBD50@tzi.org>
To: Stuart Cheshire <cheshire@apple.com>
X-Mailer: Apple Mail (2.1082)
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 07:02:32 -0000

On Feb 15, 2011, at 21:46, Stuart Cheshire wrote:

(readable E-Mail)

How did you manage to get Apple Mail to properly use RFC 3676, i.e.

	; Format=3D"flowed"; DelSp=3D"yes"

on the Content-Type?  Apple broke that in 10.6, IIRC.

(Not that solving this problem on the sender side would solve it for all =
other senders on the reader side, but I'd like to solve both.)

Gruesse, Carsten


From dougb@dougbarton.us  Thu Feb 17 23:32:52 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0758A3A6D6A for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 23:32:52 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xQOygBhSw-QS for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 23:32:51 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id B54D93A6D4F for <ietf@ietf.org>; Thu, 17 Feb 2011 23:32:50 -0800 (PST)
Received: (qmail 16776 invoked by uid 399); 18 Feb 2011 07:33:20 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 18 Feb 2011 07:33:20 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D5E20BF.4050604@dougbarton.us>
Date: Thu, 17 Feb 2011 23:33:19 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110129 Thunderbird/3.1.7
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: MHonArc mail archive line wrapping
References: <705FECE4-4D29-48A9-9F0F-7CF1571FBD50@tzi.org>
In-Reply-To: <705FECE4-4D29-48A9-9F0F-7CF1571FBD50@tzi.org>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Stuart Cheshire <cheshire@apple.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 07:32:52 -0000

On 02/17/2011 23:03, Carsten Bormann wrote:
> On Feb 15, 2011, at 21:46, Stuart Cheshire wrote:
>
> (readable E-Mail)
>
> How did you manage to get Apple Mail to properly use RFC 3676, i.e.
>
> 	; Format="flowed"; DelSp="yes"
>
> on the Content-Type?  Apple broke that in 10.6, IIRC.
>
> (Not that solving this problem on the sender side would solve it for all other senders on the reader side, but I'd like to solve both.)

Combining format=flowed with wrapping at around 70 columns gives you the 
best of both worlds. Unfortunately you run into complications when you 
add PGP to the mix, but otherwise it's a good combination.

Pine (now Alpine) has been doing this (or capable of it) for years. For 
Thunderbird wrapping is the default, and you can toggle the 
mailnews.send_plaintext_flowed option to true in the config editor.

The historical reasons that wrapping is useful are still (to some 
extent) relevant; but we aren't doing anyone any favors by ignoring the 
new reality that messages are read on a wide variety of devices here in 
the 21st Century.


hth,

Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

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


From derhoermi@gmx.net  Fri Feb 18 01:47:51 2011
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 238FF3A6D48 for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 01:47:51 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LSVTpRpk90ex for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 01:47:50 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 8D8153A68A3 for <ietf@ietf.org>; Fri, 18 Feb 2011 01:47:48 -0800 (PST)
Received: (qmail invoked by alias); 18 Feb 2011 09:48:20 -0000
Received: from dslb-094-223-179-002.pools.arcor-ip.net (EHLO HIVE) [94.223.179.2] by mail.gmx.net (mp009) with SMTP; 18 Feb 2011 10:48:20 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/FIoYhkx7FAsyMEVzUbtjANtP2xtXxhJcDa4FzGP wxaD0Fh5G4TA7+
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stuart Cheshire <cheshire@apple.com>
Subject: Re: MHonArc mail archive line wrapping
Date: Fri, 18 Feb 2011 10:48:23 +0100
Message-ID: <l1bsl6ptndd1t0g8omlpbke7kqr0mjpeb8@hive.bjoern.hoehrmann.de>
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com> <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de> <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
In-Reply-To: <D856495F-F22E-4E2E-AB05-AC4BA9B72B0D@apple.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 09:47:51 -0000

* Stuart Cheshire wrote:
>On my 30-inch displays your hard-wrapped text appears as a thin  
>narrow ribbon of text no matter how wide the window is, and on my  
>phone your hard-wrapped lines are too long to fit so they get re- 
>wrapped to that charming long/short/long/short pattern so  
>characteristic of hard-wrapped text displayed on any device other  
>than the one it was created on.

The developer of your mail client is welcome to develop an algorithm
that recognizes which wraps are intentional and which can safely be
removed, and which parts are quotations and which parts are not. With
that information mails can easily be reformatted as you'd like them
to be. To a point anyway, and developing the algorithm for it won't
be that easy, much as putting mails into the right context is not all
that simple when clients don't send References or In-Reply-To headers,
or, worse, people decide to reply to dozens of mails in one mail; but
something good enough, compared to weird zig zag, certainly seems
feasible.

The need for this exists no matter what other remedy one might have
in mind, short of having everyone upgrade all their software at once
and living with issues with older mails, if you don't want to see (or
in some cases generate yourself) poorly formatted mails, by someone's
standard. As you've noticed, simply sending out very very long lines
breaks deployed software that expects standards compliant e-mails, for
instance. Such is life when trying to use machines to understand some
format that wasn't exactly designed for machine readability.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From wwwrun@core3.amsl.com  Fri Feb 18 02:26:46 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 8A5B33A6DEB; Fri, 18 Feb 2011 02:26:46 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: RFP for Legal Services Provider 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110218102646.8A5B33A6DEB@core3.amsl.com>
Date: Fri, 18 Feb 2011 02:26:46 -0800 (PST)
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 10:26:46 -0000

The Internet Society, on behalf of the IETF Administrative Oversight
Committee (IAOC), announces this Request for Proposals for a legal service
provider.  The successful bidder will enter into a contract with the
Internet Society.

The legal services provider (Provider) will provide advice to the IETF
Engineering Steering Group, IAOC, Internet Architecture Board, Internet
Research Task Force, RFC Series Editor, Independent Submissions Editor,
and the IETF Trust as requested, and will report to the IETF
Administrative Director.

The IAOC desires a long-term relationship commencing on 1 May 2011 of up
to four (4) years with a successful Provider.  Accordingly, it is looking
to structure a four (4) year term with contract review points at the
one-year and three-year marks to evaluate the success of the service
provider. The contract may be extended twice of one year’s duration each
for a possible contract term of six (6).  

The Internet Engineering Task Force (IETF) is a community of volunteers
interested in contributing to the long-term vitality of the Internet.  The
Internet Society is the organizational home of the IETF and is itself a
non-profit organization.  Pro bono bids are welcomed, however, where that
is not possible a fixed price would be desirable. It is understood that
for certain services additional costs may apply.  

Traditionally, the legal services that IETF has required have included
the following:

a)	Advice regarding the conduct of standard-setting activities,
particularly antitrust and intellectual property implications of IETF
policies and activities

b)	Development, drafting and interpretation of IETF policies relating to
intellectual property, namely copyright and patent policies

c)	Advice regarding the acquisition and licensing of intellectual
property held by the IETF Trust

d)	Maintenance and oversight of IETF’s global trademark portfolio

e)	Advice with drafting and negotiation of contracts with vendors and
service providers

f)	Response to third party subpoenas served on IETF by litigants in
cases, typically patent infringement suits, in which IETF standards or
activities are implicated

g)	Governance and procedural issues relating to the IETF Trust and IETF
in general

h)	Analysis and advice relating to relationships with other standards
development organizations, governmental entities, and the like

i)	Training sessions for the IETF Trust, as well as the IETF and WG
leadership on the above topics 

The RFP can be found at: http://iaoc.ietf.org/rfpsrfis.html 

Proposals must be received via email at rpelletier@isoc.org no later than
March 21, 2011 5:00 P.M. EST.  All questions/inquiries must be submitted
in writing and must be received no later than midnight, EST, March 1,
2011.  Responses to questions and inquiries shall be posted online at: 
http://iaoc.ietf.org/rfpsrfis.html by midnight, EST, March 7, 2011. 

The point of contact regarding this RFP is the IETF Administrative
Director, Ray Pelletier.

Ray Pelletier
IETF Administrative Director

From hallam@gmail.com  Fri Feb 18 10:02:10 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09A003A6D71 for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 10:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bnTL6ZK6MdTu for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 10:02:08 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 782893A6CF3 for <ietf@ietf.org>; Fri, 18 Feb 2011 10:02:08 -0800 (PST)
Received: by ywi6 with SMTP id 6so324103ywi.31 for <ietf@ietf.org>; Fri, 18 Feb 2011 10:02:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:references:from :content-transfer-encoding:content-type:in-reply-to:message-id:date :cc:to:mime-version:x-mailer; bh=zVEDFfERKi6AjV3SrW2O5slJlGgFOecI66IzJ7qfaXU=; b=RUgzOayWsvu+6p8a+G2aPofuO88PhjQD9jOX0TLnEsw9oaSqoGXcRR+fYkf2oRSQx6 I3GbmZtzqttqOS29C2IHvp93hOYE7du8CstoHm4T6k/DbPTAhJ1oHHaf4UnOk1J0Gr53 6rrt1lcenn3g6WLwBEecFVw7gvvp+U39e9/vg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:references:from:content-transfer-encoding:content-type :in-reply-to:message-id:date:cc:to:mime-version:x-mailer; b=GajPAVjU1Ye2DshcLmW2w10pi3PXhiJXFnYh05S7TjdF5Lj9xsEAbTM3h/A8/nxLv+ RafX0KqwIBOYOMKWNxvZ7CG6TLRoTwhIGifgmfqA3qWUmPMiDoKB6JMCD7WPuKAgk5j1 RE9Q9N4N4JZwjOnQEdMoN88AmSmD1zjEDcbZU=
Received: by 10.100.40.13 with SMTP id n13mr466030ann.169.1298052162256; Fri, 18 Feb 2011 10:02:42 -0800 (PST)
Received: from [10.34.214.59] ([166.205.137.167]) by mx.google.com with ESMTPS id w4sm2845972anw.36.2011.02.18.10.02.36 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Feb 2011 10:02:40 -0800 (PST)
Subject: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt
References: <BF118113-AF47-4250-A24F-81E6217FCA3E@gmail.com> <4CE9F51C.2010201@dougbarton.us> <alpine.LSU.2.00.1011221451450.4075@hermes-2.csi.cam.ac.uk> <4CEC2A46.8040300@dougbarton.us> <p06240848c911df19b671@[10.20.30.150]> <4CEC32DF.203@dougbarton.us>
From: Phillip Hallam-Baker <hallam@gmail.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4CEC32DF.203@dougbarton.us>
Message-Id: <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com>
Date: Fri, 18 Feb 2011 09:46:52 -0800
To: Doug Barton <dougb@dougbarton.us>
Mime-Version: 1.0 (iPad Mail 8C148)
X-Mailer: iPad Mail (8C148)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 18:02:10 -0000

This protocol has established a legacy base, as in it is going to be a part o=
f the infrastructure we have to work round for decades even if Apple abandon=
 it tomorrow.

It is now futile to attempt modification of the protocol except in limited w=
ays that do not impact the legacy base.


Therefore we need to have a description of the protocol as a standard used o=
n the Internet.

If people here want to be jerks and make that process painful, they can. But=
 they are damaging the organization in ways tbat they either do not understa=
nd or do not care about.

If IETF wants to be relevant, it has to give a timely response. Endless fill=
ibustering with nits has to stop.

People have a choice in standards organizations. The IETF has no special pos=
ition of control. If Stuart had waited for the IANA to issue his DNS codes, b=
onjour would never have deployed and he would be out of a job. And the only p=
eople who benefitted would be the process trolls.


I have a proposal in at the moment, CAA. I have a party that is going to rel=
ease code before Prague. The expert review should take six weeks, it has tak=
en twice that.

Now i am willing to solicit advice, but at some point the other party is goi=
ng to release their code and tell me the RR they have decided to assign.=20

If this organization wants to be involved in the development of the Internet=
 the advice has to be timely. As it is the process trolls have reduced the r=
ole of the IETF to documenting what others do and grumbing about why the dev=
elopers did not complete the correct obessiances in the correct order.


Ship it. Ship it now.


Sent from my iPad

On Nov 23, 2010, at 13:32, Doug Barton <dougb@dougbarton.us> wrote:

> On 11/23/2010 13:17, Paul Hoffman wrote:
>> At 12:55 PM -0800 11/23/10, Doug Barton wrote:
>>> In the theoretical perfect world the reason for producing a spec is so t=
hat vendors can _create_ interoperable versions of the service. That motivat=
ion doesn't apply here, so one wonders what the time pressure is.
>>=20
>> That is "a" reason, not "the" reason. Another is so that vendors can assu=
re interoperability of their systems after they are deployed. Saying "you ha=
ve to figure out how to interoperate with all other implementations" does no=
t lead to that interoperability. A stable RFC can help greatly, as has been s=
hown repeatedly in the IETF.
>=20
> That's a motivation for creating the draft, yes. It's not a motivation for=
 publishing the RFC before it's ready.
>=20
> Please understand, I'm not saying "don't publish," I'm not even saying "fi=
x _all_ the problems." I'm saying, "Fix the obvious, glaring protocol error t=
hat has potential to do more damage down the road, and while you're at it he=
re are some other minor suggestions to improve the quality of the document i=
f you choose to accept them. THEN publish the RFC."
>=20
> And now I've repeated myself sufficiently so I will spare the list members=
 any more responses to ad absurdum replies.
>=20
>=20
> Doug
>=20
> --=20
>=20
>    Nothin' ever doesn't change, but nothin' changes much.
>            -- OK Go
>=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 hallam@gmail.com  Fri Feb 18 10:06:01 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ADAD3A6D71 for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 10:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M+41Sy2HsYzu for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 10:06:00 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 2C9CE3A6D48 for <ietf@ietf.org>; Fri, 18 Feb 2011 10:06:00 -0800 (PST)
Received: by iym1 with SMTP id 1so4037376iym.31 for <ietf@ietf.org>; Fri, 18 Feb 2011 10:06:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=pp91HEaC0wyvvXk/s+J2bp8Erai7gQcQqbqWJYrROME=; b=e3T2TPrloybRi2pNfePkf0I3CWarhCH1BSHCAJBSlNfdyWeWPesFyMGoONxCyi3J8x uoASMHL+3tBV7dePlE/yZ40qxMTcfZ6GXTOtM7UdIZLoxOx9gB12EpoxGxqULbgLnGD9 lPPlo5Im+HzwT1KBGOd05ziddAEjvBiCmZrIo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; b=bpKZ7z0c+84rjLgpbkYUMxbLc4eq4k+8cjHvYTxa+Rf9GXe1zu27XFX52c+VOfvD80 IT5rY0Z/t9AsIWeEzPgOWd+RZbrCl0uB1FTUTMJCcV86NOF7KvZ1yMu6KO7fZUh8vBZ3 modvfh+4c84Im+TuZfLZgwTakEyLQ0qQoe350=
Received: by 10.231.36.10 with SMTP id r10mr713530ibd.137.1298052394143; Fri, 18 Feb 2011 10:06:34 -0800 (PST)
Received: from [10.34.214.59] ([166.205.137.167]) by mx.google.com with ESMTPS id z4sm1963221ibg.1.2011.02.18.10.06.30 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Feb 2011 10:06:33 -0800 (PST)
References: <BF1B4928-ABEE-4EC0-9BE5-DDD3C6FAB9C3@apple.com> <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
In-Reply-To: <2vqll6ts0l0hjuic0t3p60sp679nh87920@hive.bjoern.hoehrmann.de>
Mime-Version: 1.0 (iPad Mail 8C148)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <10075264-431E-4EC8-9272-9C8B144A8748@gmail.com>
X-Mailer: iPad Mail (8C148)
From: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: MHonArc mail archive line wrapping
Date: Fri, 18 Feb 2011 10:06:24 -0800
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Cc: Stuart Cheshire <cheshire@apple.com>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 18:06:01 -0000

IETF standards should never attempt to solve a technical issue by changing h=
uman behavior.

It is futile. And it suggests that the dvelopers are more important than use=
rs.


This is a bug in the technology. Fix it.


Sent from my iPad

On Feb 15, 2011, at 13:32, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> * Stuart Cheshire wrote:
>> In the MHonArc mail archive there are often super-long lines, which =20
>> would be wrapped to the window width when viewing in most mail =20
>> clients, but when viewed in a web browser they appear as long single =20
>> lines which take a lot of left-to-right scrolling to read them.
>=20
> That is the result of some clients and users violating netiquette and
> mail standards, for instance, RFC 1855, section 2.1.1:
>=20
>  - Limit line length to fewer than 65 characters and end a line
>    with a carriage return.=20
>=20
> and RFC 2822 (and similarily RFC 5322), section 2.1.1:
>=20
>  There are two limits that this standard places on the number of
>  characters in a line. Each line of characters MUST be no more than
>  998 characters, and SHOULD be no more than 78 characters, excluding
>  the CRLF.=20
>=20
> And this does not cause problems just with unwrapped lines, it also has
> other effects, like people quoting excessively long lines on one line
> but then write their own text properly wrapped (that's appropriate be-
> havior if long lines are rare and most likely intentional, such as when
> including some computer code you don't want wrapped at odd positions.)
>=20
> I note that one of the main culprits here are Apple Mail users, although
> you seem to be using it yet have managed to send properly wrapped lines.
> If there is something Apple Mail users can do to stop their netiquette
> and standards violations, I would apprciate any pointer you may have.
>=20
> Obviously the solution is to have those using broken or misconfigured
> clients use clients that are not broken or configure them correctly.
>=20
> As for the list archives, you can make the lines wrap by changing the
> style sheet (or use an appropriate user style sheet), for instance,
>=20
>  pre { white-space: pre-wrap; }
>=20
> should probably do it in modern clients (for older clients there is
> option to use proprietary extensions in some browsers, but that may
> not be necessary these days.) This would seem preferable over forcing
> line wraps in the archival software as that would break lines that are
> meant to be long for very good reasons.
> --=20
> Bj=C3=B6rn H=C3=B6hrmann =C2=B7 mailto:bjoern@hoehrmann.de =C2=B7 http://b=
joern.hoehrmann.de
> Am Badedeich 7 =C2=B7 Telefon: +49(0)160/4415681 =C2=B7 http://www.bjoerns=
world.de
> 25899 Dageb=C3=BCll =C2=B7 PGP Pub. KeyID: 0xA4357E78 =C2=B7 http://www.we=
bsitedev.de/=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From moore@network-heretics.com  Fri Feb 18 10:10:02 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 298AD3A6E1E for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 10:10:02 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DJuKUilOsfIE for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 10:10:01 -0800 (PST)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 1F46C3A6D6A for <ietf@ietf.org>; Fri, 18 Feb 2011 10:10:01 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 18DA1207F5; Fri, 18 Feb 2011 13:10:35 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 18 Feb 2011 13:10:35 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=smtpout; bh=Ztmvs79xt1OrN83jAwSt0/Q+IC8=; b=S8EMW7M18E5fpgnC1yz0ayRAytpqfJRwoHGaET2uoSrxAw4oEg8EzPBjk5ekowzvn+5rD9klr9bLDlGc8oUNG2uud5WKzUrY2iKryHn4cwuA4c3deFy4LtZGlm6GI+/ddxTl9HJKrfxJUjsgeBtmXu29Hp35oHbIQshRweBBl+c=
X-Sasl-enc: UCNGvjqvR8NZBa7qqdeaV6yYeKy24kBCHd5KfkL7k2nP 1298052634
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 561F0446371; Fri, 18 Feb 2011 13:10:34 -0500 (EST)
Subject: Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com>
Date: Fri, 18 Feb 2011 13:10:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC4CE4EE-9238-46A2-9F69-73FF40103CBA@network-heretics.com>
References: <BF118113-AF47-4250-A24F-81E6217FCA3E@gmail.com> <4CE9F51C.2010201@dougbarton.us> <alpine.LSU.2.00.1011221451450.4075@hermes-2.csi.cam.ac.uk> <4CEC2A46.8040300@dougbarton.us> <p06240848c911df19b671@[10.20.30.150]> <4CEC32DF.203@dougbarton.us> <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "ietf@ietf.org" <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 18:10:02 -0000

On Feb 18, 2011, at 12:46 PM, Phillip Hallam-Baker wrote:

> This protocol has established a legacy base, as in it is going to be a =
part of the infrastructure we have to work round for decades even if =
Apple abandon it tomorrow.
>=20
> It is now futile to attempt modification of the protocol except in =
limited ways that do not impact the legacy base.
>=20
> Therefore we need to have a description of the protocol as a standard =
used on the Internet.

Does not follow.   Having a description of the protocol, as it was =
deployed, documented is usually a good idea.   Having it as standard, =
not necessarily so.  There are a great many protocols which have =
"established a legacy base" which are not suitable for standardization.

> If people here want to be jerks and make that process painful, they =
can. But they are damaging the organization in ways tbat they either do =
not understand or do not care about.

The most effective way to damage the IETF, is to insist that the IETF =
endorse technically flawed protocols as standards.

> If IETF wants to be relevant, it has to give a timely response. =
Endless fillibustering with nits has to stop.
>=20
> People have a choice in standards organizations. The IETF has no =
special position of control. If Stuart had waited for the IANA to issue =
his DNS codes, bonjour would never have deployed and he would be out of =
a job. And the only people who benefitted would be the process trolls.

If the IETF has no special position of control, then it doesn't matter =
if IETF declines to standardize something.

Anytime I see someone making these kinds of arguments to support =
standardization of something, it tells me that there is very probably =
something seriously wrong with the proposal, and that at the very least =
it needs further scrutiny.

Keith


From nazare@isoc.org  Thu Feb 17 10:45:42 2011
Return-Path: <nazare@isoc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CA463A6E19 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 10:45:42 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZdBloZl9YB1 for <ietf@core3.amsl.com>; Thu, 17 Feb 2011 10:45:41 -0800 (PST)
Received: from smtp127.iad.emailsrvr.com (smtp127.iad.emailsrvr.com [207.97.245.127]) by core3.amsl.com (Postfix) with ESMTP id 79D5B3A6D6C for <ietf@ietf.org>; Thu, 17 Feb 2011 10:45:41 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp52.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id DB334240FAB for <ietf@ietf.org>; Thu, 17 Feb 2011 13:46:12 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp52.relay.iad1a.emailsrvr.com (Authenticated sender: nazare-AT-isoc.org) with ESMTPSA id C36C2240DDE for <ietf@ietf.org>; Thu, 17 Feb 2011 13:46:12 -0500 (EST)
From: "Leni Nazare" <nazare@isoc.org>
To: "'IETF'" <ietf@ietf.org>
References: <49A6CCB2-B484-4F0E-B489-F1D1DAEBAEE8@ietf.org>
Subject: RE: [80all] Prague IETF Codesprint
Date: Thu, 17 Feb 2011 13:49:11 -0500
Message-ID: <18CD74B68A4A4628AA10F2EDC75E2A7C@ISOC.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcvOIPQcYO7Ntet0QBa/rlidt1SrRQAsmE+A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
In-Reply-To: <49A6CCB2-B484-4F0E-B489-F1D1DAEBAEE8@ietf.org>
X-Mailman-Approved-At: Fri, 18 Feb 2011 11:28:47 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 18:45:42 -0000

Steve,

By what time will this sprint be over do you think?


> -----Original Message-----
> From: 80all-bounces@ietf.org [mailto:80all-bounces@ietf.org] On Behalf Of
> IETF Chair
> Sent: Wednesday, February 16, 2011 4:32 PM
> To: IETF Announcement list
> Cc: 80all@ietf.org; IETF
> Subject: [80all] Prague IETF Codesprint
> 
> Prague IETF Codesprint
> 
> When:  26 March 2011, starting at 9:30 AM
> 
> Where: IETF Hotel
> 
> What:  A bunch of hackers get together to work on code for the IETF.
>       All code will become part of the open source IETF tools.
> 
> Who:   Hopefully you can help
> 
> Many of the results of previous codesprint activities are being
> used every day by the IETF community.  Work to polish or
> improve existing tools will be most welcome.  Work on something
> completely new is also welcome.
> 
> Steve Conte will be helping with advance planning.  Henrik Levkowetz
> will be coordinating the event in Prague.  More information is available
> at:
> 
> http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF80Sprint
> 
> If you are able to participate, please sign up on the wiki at:
> 
> http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF80SprintSignUp
> 
> Please support the tools development effort,
>  Russ
> 
> _______________________________________________
> 80all mailing list
> 80all@ietf.org
> https://www.ietf.org/mailman/listinfo/80all


From ben@nostrum.com  Thu Feb 17 12:24:58 2011
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D1F03A6AAE; Thu, 17 Feb 2011 12:24:58 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8qsGsL23Ke1b; Thu, 17 Feb 2011 12:24:57 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id E2B083A6A00; Thu, 17 Feb 2011 12:24:56 -0800 (PST)
Received: from [10.0.1.6] (cpe-76-183-178-106.tx.res.rr.com [76.183.178.106]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p1HKOA4M005339 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Feb 2011 14:24:11 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC Review of draft-bryan-metalinkhttp-19
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <C3E2F61E-A91C-4665-8DF4-42B58C4C0580@nostrum.com>
Date: Thu, 17 Feb 2011 14:24:11 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDE8D629-46FB-4BBC-AB66-CDCE053158A5@nostrum.com>
References: <19DDC0DF-9ECF-499A-954E-17BABF6410B5@nostrum.com> <AANLkTik3VNfsT4fY2wc8HpfidPVCshGSUW1py4Jzf==w@mail.gmail.com> <C3E2F61E-A91C-4665-8DF4-42B58C4C0580@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 76.183.178.106 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Fri, 18 Feb 2011 11:28:47 -0800
Cc: alexey.melnikov@isode.com, General Area Review Team <gen-art@ietf.org>, Anthony Bryan <anthonybryan@gmail.com>, The IETF <ietf@ietf.org>, draft-bryan-metalinkhttp.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Feb 2011 20:24:58 -0000

Update: I looked at the diffs for version 20, and I think the discussion =
below accurately reflect the changes--so please consider this a followup =
review of version 20.

Thanks!

Ben.

On Feb 16, 2011, at 5:15 PM, Ben Campbell wrote:

> Thanks for the quick response. I haven't had a chance to look at the =
new version yet, but here are my responses to your email comments. I =
removed sections where I had no further (non-trivial) comment. Please =
consider any removed parts to be the same as an "Okay" response.
>=20
> Thanks!
>=20
> Ben.
>=20
> On Feb 14, 2011, at 4:43 PM, Anthony Bryan wrote:
>=20
> [...]
>=20
>> was there supposed to be a comment along with
>>=20
>> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the
>> same ETag policy as the originating Metalink server."
>> ?
>=20
> I responded to this one below.
>=20
>>=20
>> On Fri, Feb 11, 2011 at 6:46 PM, Ben Campbell <ben@nostrum.com> =
wrote:
>=20
> [...]
>=20
>>>=20
>>> -- Section 1, paragraph 1, first sentence:
>>>=20
>>> Is this really intended as an alternative to Metalink/XML? It seems =
like more of a complementary approach than an alternative one.
>>=20
>> well...you could use either, or both :)
>>=20
>> "Metalink/HTTP is an alternative and complementary representation of
>> Metalink information,"...
>> ?
>=20
> WFM
>=20
>>=20
>>> -- section 2, third paragraph:
>>>=20
>>> If they must have the same eTag policy, should this document not =
specify at least one mandatory-to-implement policy?
>>=20
>> SHOULD share the same ETag policy.
>>=20
>> I added:
>>=20
>> "It is up to the administrator of the Metalink server to communicate
>> the details of the shared ETag policy to the administrators of the
>> mirror servers so that the mirror servers can be configured with the
>> same ETag policy."
>=20
> My comment was about policy implementation, not policy configuration.=20=

>=20
> Do you expect the method to generate ETags to be configurable in most =
implementations? Is that the case among common HTTP servers today? =
(That's not rhetorical--I don't know the answer.) And even if it is, is =
there a risk that there won't be a common selection between =
implementations? It doesn't help to tell an administrator to select a =
certain policy unless his software can actually do it. If there was a =
mandatory-to-implement policy, then that shouldn't happen.
>=20
>=20
> [...]
>=20
>>=20
>>> -- section 10.2:
>>>=20
>>> What can an implementor do to mitigate spoofing?
>>=20
>> nothing, I'm aware of?
>>=20
>> added:
>> As with all downloads, users should only download from trusted =
sources.
>=20
> Hmm. What does "trusted" mean in context? Does that have implications =
on authentication of the source and integrity protection of the download =
session? (i.e. TLS)?
>=20
> [...]
>=20
>>> --- Nits/editorial comments:
>>>=20
>>> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the =
same ETag policy as the originating Metalink server."
>>=20
>> what's wrong here?
>=20
> Oops, sorry, cut-and-paste error. My comment was "This seems redundant =
with a similar statement in the previous paragraph"
>=20
> [...]
>=20
>=20
>>> -- section 7.1.1, general:
>>>=20
>>> This whole section switches to an almost stream-of-consciousness =
style. It has very long sentences with many comma separated clauses that =
are hard to follow. It really needs to be rewritten to be more readable =
and precise.
>>=20
>> hahaha :)
>>=20
>> this is my fault as a bad editor & a non-native English speaker =
co-author.
>>=20
>=20
> On reflection, I think my comment was a little harsh. But another pass =
with some attention to style in the section would help.
>=20
>=20
>>> -- section 7.1.1, paragraph 3:
>>>=20
>>> Paragraph seems self contradictory. How is guaranteeing correct =
content different than verifying integrity?
>>=20
>> the server sends the correct content  but there can be errors during =
transfer.
>>=20
>> maybe this is not explicit enough. might need to condense some of =
this down.
>=20
>> earlier we state:
>> Error detection requires Instance Digests to detect errors in =
transfer
>> after the transfers have completed.
>>=20
>=20
> I think a rewording would help, as I took "guaranteeing correct =
content" to mean "guaranteeing the client receives correct content" =
rather than "guaranteeing the server sends correct content".
>=20
> [...]
>=20
>>=20
>>> -- section 7.1.2, 2nd paragraph: "If the object cryptographic hash =
does not match the Instance Digest then fetch the Metalink/XML if =
available, where partial file cryptographic hashes can be found, =
allowing detection of which server returned incorrect data."
>>>=20
>>> I can't parse this sentence.
>>=20
>>  If the cryptographic hash of the object does not match the Instance
>>  Digest from the Metalink server, then the client SHOULD fetch the
>>  Metalink/XML (if available) that could contain partial file
>>  cryptographic hashes which will allow detection of which mirror
>>  server returned incorrect data.  Metalink clients SHOULD figure out
>>  what ranges of the downloaded data can be recovered and what needs =
to
>>  be fetched again.
>=20
> That's better, but how about breaking it up a bit more, as in the =
following:
>=20
> "  If the cryptographic hash of the object does not match the Instance =
Digest from the Metalink server, then the client SHOULD fetch the =
Metalink/XML (if available). This may contain partial file cryptographic =
hashes which will allow detection of which mirror server returned =
incorrect data.  Metalink clients SHOULD use the Metalink/XML data to =
figure out what ranges of the downloaded data can be recovered and what =
needs to be fetched again. "
>=20
> [...]
>=20
>>=20
>>> -- section 10.2 "In that case, this could deceive unaware =
downloaders that they are downloading a malicious or worthless file."
>>>=20
>>> Sentence does not make sense. Does the attacker with to deceive them =
into downloading a malicious file, or convince them that they are when =
they are not?
>>=20
>> "In that case, this could deceive unaware downloaders into =
downloading
>> a malicious or worthless file."
>>=20
>=20
> WFM


From ajs@shinkuro.com  Fri Feb 18 12:08:24 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC64E3A6E4D for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 12:08:24 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhakGn9YCpW9 for <ietf@core3.amsl.com>; Fri, 18 Feb 2011 12:08:24 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id A04FD3A6DF1 for <ietf@ietf.org>; Fri, 18 Feb 2011 12:08:22 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 2E1141ECB420 for <ietf@ietf.org>; Fri, 18 Feb 2011 20:08:56 +0000 (UTC)
Date: Fri, 18 Feb 2011 15:08:54 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: On DNS Expert failure (was: Stop the process trolls !)
Message-ID: <20110218200854.GQ66684@shinkuro.com>
References: <BF118113-AF47-4250-A24F-81E6217FCA3E@gmail.com> <4CE9F51C.2010201@dougbarton.us> <alpine.LSU.2.00.1011221451450.4075@hermes-2.csi.cam.ac.uk> <4CEC2A46.8040300@dougbarton.us> <p06240848c911df19b671@[10.20.30.150]> <4CEC32DF.203@dougbarton.us> <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2011 20:08:25 -0000

Hi,

On Fri, Feb 18, 2011 at 09:46:52AM -0800, Phillip Hallam-Baker wrote:
> 
> I have a proposal in at the moment, CAA. I have a party that is going to release code before Prague. The expert review should take six weeks, it has taken twice that.

I want to apologize here, publicly to Phillip and those who are
waiting on this assignment.  I'm the chair who is supposed to be
managing that expert review, and ensuring that the expert returns in a
timely fashion.  I have obviously failed.

This is just a bureaucratic foul-up on my part, and I'm sorry for it.
I'm doing everything I can to get the review completed reasonably
quickly now.

Best regards,

Andrew

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From evnikita2@gmail.com  Fri Feb 18 21:34:31 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFA133A6FAD; Fri, 18 Feb 2011 21:34:31 -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.004,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id unoxgju12NNY; Fri, 18 Feb 2011 21:34:29 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 3B3A63A6DE5; Fri, 18 Feb 2011 21:34:28 -0800 (PST)
Received: by bwz13 with SMTP id 13so966334bwz.31 for <multiple recipients>; Fri, 18 Feb 2011 21:35:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=dYaPcW8NmL198UK0EAWm/a5T1ozZL7GKYUL/czt6w0w=; b=KhvmjcUN3Kr2dZdsHegFNZ1Cb8Rlilq5tajjKuuyzvhupT0EQ096n+t0AiHGGlyy9/ JCFR84cDPff4uxdE1ZuTIGYDUYbIAo6zdE0oabReB4TDmlaWtItvalmwCEpEpnMa3WSW ipCqqyyXwk4R+DZlh3FBDE2/x9DHZeQlEZKyU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=med/pBwaNYwQDibobYNmigDmkMKXRktURSS1zHRx2+cyj+XV9LZMACF1AsnKyLzdwc b8IJoobIvFY55WlwqVh0tgxL9x88b1DATkCsWtx9BGrwT8thhYDnpqyODvcWIESgq15/ y2nB+QA+TE7rdWqS5LcnY/ZG1g4NTAt4EsmK8=
Received: by 10.204.46.134 with SMTP id j6mr1403531bkf.112.1298093701128; Fri, 18 Feb 2011 21:35:01 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id u23sm1966231bkw.21.2011.02.18.21.34.58 (version=SSLv3 cipher=OTHER); Fri, 18 Feb 2011 21:34:59 -0800 (PST)
Message-ID: <4D5F569F.3010305@gmail.com>
Date: Sat, 19 Feb 2011 07:35:27 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-xcon-common-data-model-23.txt> (Conference Information Data Model for Centralized Conferencing (XCON)) to	Proposed Standard
References: <20110218223448.15711.10845.idtracker@localhost>
In-Reply-To: <20110218223448.15711.10845.idtracker@localhost>
Content-Type: multipart/alternative; boundary="------------050209060402000602020706"
Cc: xcon@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2011 05:34:32 -0000

This is a multi-part message in MIME format.
--------------050209060402000602020706
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

As far as I know there was a request to review URI schemes defined in 
this document on uri-review list on 1 March 2010.  There were a few 
responses on it, but I'd like to comment these schemes' registration 
now, during the Last Call.

See my comments in-line.

>
>       9.3. Conference Object Identifier Registration
>
>
>
>
>
>   The IANA is requested to register the following URI scheme
>   under the Permanent URI Schemes registry.
Here the informative reference to RFC 4395 might be appropriate.
>   XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx]
>
>    conf-object-id = 1*( unreserved / "+" / "=" / "/" )
You should have the normative reference to RFC 5234 here.  Moreover, 
here [RFC xxxx] may be treated as part of scheme definition.  I'd like 
to propose to remove it at all.
>
>     host, port, and unreserved are defined inRFC3986  <http://tools.ietf.org/html/rfc3986>[RFC3986  <http://tools.ietf.org/html/rfc3986>]
I wonder why you have informative reference to RFC 3986.  If you import 
these rules, informative reading the document that defines them won't be 
enough.
>     [Note to the RFC Editor: replace xxxx with the number this RFC gets
>     assigned.]
>
>
>      Subject: Request for XCON-URI Registration
>      Person&  email address to contact for further information:
>           Oscar Novo<oscar novo_at_ericsson.com>
>      Specification: RFC XXXX
>      Author/Change Controller: IESG
>      Comments:
>          Identifies the Conference
As I know, RFC 4395 requires full registration template for Permanent 
registrations.  See here: http://tools.ietf.org/html/rfc4395#section-5.4
>
>
>       9.4. Conference User Identifier Registration
>
>
>
Just the same comments - references to RFC 5234 and 4395, full template.
>
>     The IANA is requested to register the following URI scheme
>      under the Permanent URI Schemes registry.
>
>      XCON-USERID = "xcon-userid" ":" conf-user-id  [ RFC xxxx ]
>
>      conf-user-id = 1*(unreserved)
Here '/conf-user-id = 1*unreserved/' would be better, IMO.
>
>     unreserved is defined inRFC3986  <http://tools.ietf.org/html/rfc3986>[RFC3986  <http://tools.ietf.org/html/rfc3986>]
>
>     [Note to the RFC Editor: replace xxxx with the number this RFC gets
>     assigned.]
>
>
>
>      Subject: Request for XCON-USERID Registration
>      Person&  email address to contact for further information:
>           Oscar Novo<oscar novo_at_ericsson.com>
>      Specification: RFC XXXX
>      Author/Change Controller: IESG
>      Comments:
>          Identifies the User in the conference
Thank you in advance for considering my comments.

All the best,
Mykyta Yevstifeyev

19.02.2011 0:34, The IESG wrote:
> The IESG has received a request from the Centralized Conferencing WG
> (xcon) to consider the following document:
> - 'Conference Information Data Model for Centralized Conferencing (XCON)'
>    <draft-ietf-xcon-common-data-model-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 2011-03-04. 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/
>
>
>
> 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
>


--------------050209060402000602020706
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hello,<br>
    <br>
    As far as I know there was a request to review URI schemes defined
    in this document on uri-review list on 1 March 2010.&nbsp; There were a
    few responses on it, but I'd like to comment these schemes'
    registration now, during the Last Call.<br>
    <br>
    See my comments in-line.<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage"><span class="h3"><h3><a name="section-9.3">9.3</a>.  Conference Object Identifier Registration</h3></span>



 The IANA is requested to register the following URI scheme
 under the Permanent URI Schemes registry.
</pre>
    </blockquote>
    Here the informative reference to RFC 4395 might be appropriate.<br>
    <blockquote type="cite">
      <pre class="newpage">
 XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx]

  conf-object-id = 1*( unreserved / "+" / "=" / "/" )
</pre>
    </blockquote>
    You should have the normative reference to RFC 5234 here.&nbsp; Moreover,
    here [RFC xxxx] may be treated as part of scheme definition.&nbsp; I'd
    like to propose to remove it at all.<br>
    <blockquote type="cite">
      <pre class="newpage">

   host, port, and unreserved are defined in <a href="http://tools.ietf.org/html/rfc3986">RFC3986</a>[<a href="http://tools.ietf.org/html/rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]
</pre>
    </blockquote>
    I wonder why you have informative reference to RFC 3986.&nbsp; If you
    import these rules, informative reading the document that defines
    them won't be enough.<br>
    <blockquote type="cite">
      <pre class="newpage">
   [Note to the RFC Editor: replace xxxx with the number this RFC gets
   assigned.]


</pre>
      <pre class="newpage">    Subject: Request for XCON-URI Registration
    Person &amp; email address to contact for further information:
         Oscar Novo &lt;oscar novo_at_ericsson.com&gt;
    Specification: RFC XXXX
    Author/Change Controller: IESG
    Comments:
        Identifies the Conference
</pre>
    </blockquote>
    As I know, RFC 4395 requires full registration template for
    Permanent registrations.&nbsp; See here:
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc4395#section-5.4">http://tools.ietf.org/html/rfc4395#section-5.4</a><br>
    <blockquote type="cite">
      <pre class="newpage">
<span class="h3"><h3><a name="section-9.4">9.4</a>.  Conference User Identifier Registration</h3></span>

</pre>
    </blockquote>
    Just the same comments - references to RFC 5234 and 4395, full
    template.<br>
    <blockquote type="cite">
      <pre class="newpage">

   The IANA is requested to register the following URI scheme
    under the Permanent URI Schemes registry.

    XCON-USERID = "xcon-userid" ":" conf-user-id  [ RFC xxxx ]

    conf-user-id = 1*(unreserved)
</pre>
    </blockquote>
    Here '<i>conf-user-id = 1*unreserved</i>' would be better, IMO.<br>
    <blockquote type="cite">
      <pre class="newpage">

   unreserved is defined in <a href="http://tools.ietf.org/html/rfc3986">RFC3986</a>[<a href="http://tools.ietf.org/html/rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]

   [Note to the RFC Editor: replace xxxx with the number this RFC gets
   assigned.]



    Subject: Request for XCON-USERID Registration
    Person &amp; email address to contact for further information:
         Oscar Novo &lt;oscar novo_at_ericsson.com&gt;
    Specification: RFC XXXX
    Author/Change Controller: IESG
    Comments:
        Identifies the User in the conference
</pre>
    </blockquote>
    Thank you in advance for considering my comments.<br>
    <br>
    All the best,<br>
    Mykyta Yevstifeyev<br>
    <br>
    19.02.2011 0:34, The IESG wrote:
    <blockquote
      cite="mid:20110218223448.15711.10845.idtracker@localhost"
      type="cite">
      <pre wrap="">
The IESG has received a request from the Centralized Conferencing WG
(xcon) to consider the following document:
- 'Conference Information Data Model for Centralized Conferencing (XCON)'
  &lt;draft-ietf-xcon-common-data-model-23.txt&gt; 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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2011-03-04. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/">http://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/">http://datatracker.ietf.org/doc/draft-ietf-xcon-common-data-model/</a>



No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a>

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050209060402000602020706--

From evnikita2@gmail.com  Fri Feb 18 21:44:27 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1C943A6E0D; Fri, 18 Feb 2011 21:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.295
X-Spam-Level: 
X-Spam-Status: No, score=-3.295 tagged_above=-999 required=5 tests=[AWL=0.303,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5jkHkwdoDFa6; Fri, 18 Feb 2011 21:44:26 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 69D643A6FA5; Fri, 18 Feb 2011 21:44:25 -0800 (PST)
Received: by bwz13 with SMTP id 13so969988bwz.31 for <multiple recipients>; Fri, 18 Feb 2011 21:45:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type; bh=HVUAhhnw8hgSZJq8cSOXb+n+8VTlA16/tVHtPlpm5sE=; b=MKlIQbT/cDbPAYzxlGtbWPq/ntL+YIUU7Ky0HIORjxOhdfug9x35ZviwVtaauAFns2 ghhY86JKmCmQG7URSUE0Wbnhz97rF4AwQwiU4F4CqZ5oF5fhTcZIJtNfm3f3CGnzCb2K EX2NsgWOPALzegkIHyYhik7/50qaKKADZ4WHA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=VMgfdUMRaqkpfwLYE8hmovm4ky9CwY+jRVI4H8hxIKMXY7fkD1jDA/oPVN/fvbeN0n ZhguZDj29RJdIxr+aoH7w8lo74NKpR8mYGOceYYGJKxdmHvgLDY3CEZVxOnBS2TN5MrP jfiTP6I7aQqvkJGIWMFcn1V8wMhOZhmyqeCB0=
Received: by 10.204.61.10 with SMTP id r10mr1427802bkh.195.1298094299145; Fri, 18 Feb 2011 21:44:59 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id w3sm1975208bkt.5.2011.02.18.21.44.57 (version=SSLv3 cipher=OTHER); Fri, 18 Feb 2011 21:44:58 -0800 (PST)
Message-ID: <4D5F58F6.4090206@gmail.com>
Date: Sat, 19 Feb 2011 07:45:26 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-xcon-ccmp-12.txt> (Centralized Conferencing Manipulation Protocol) to Proposed Standard
References: <20110218223622.15783.95652.idtracker@localhost>
In-Reply-To: <20110218223622.15783.95652.idtracker@localhost>
Content-Type: multipart/alternative; boundary="------------000404030008070201020007"
Cc: xcon@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2011 05:44:28 -0000

This is a multi-part message in MIME format.
--------------000404030008070201020007
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

Let me briefly comment IANA considerations sub-sections, that define two 
registries.

See my comments in-line.

>
>       12.5. CCMP Protocol Registry
>
>
>
>     This document requests that the IANA create a new registry for the
>     CCMP protocol including an initial registry for operation types and
>     response codes.
>
>
>
>         12.5.1. CCMP Message Types
>
>
>
>     The CCMP messages are described inSection 4.1  <http://tools.ietf.org/html/draft-ietf-xcon-ccmp-12#section-4.1>  and defined in the XML
>     schema inSection 11  <http://tools.ietf.org/html/draft-ietf-xcon-ccmp-12#section-11>.  The following summarizes the requested
>    registry:
>
>     Related Registry:   CCMP Message Types Registry
>
>     Defining RFC:  RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
>        with the RFC number for this specification.]
>
>     Registration/Assignment Procedures:  New CCMP message types are
>        allocated on a specification required basis.
Here you should have the normative reference to RFC 5226.
>     Registrant Contact:  IETF, XCON working group, (xcon@ietf.org), Mary
>        Barnes (mary.ietf.barnes@gmail.com).
As far as I may see, this registry definition does not conform to that 
described by RFC 5226.  Particularly, there are no description of the 
format of the registry and its entries as well as some other 
information, required by that document.  See here:  
http://tools.ietf.org/html/rfc5226#section-4.2
>     This section pre-registers the following initial CCMP message types:
>    [ ... ]
>
>
>
>         12.5.2. CCMP Response Codes
>
>
Here the same as above apply.
>     The following summarizes the requested registry for CCMP Response
>     codes:
>
>     Related Registry:   CCMP Response Code Registry
>
>     Defining RFC:  RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
>        with the RFC number for this specification.]
>
>     Registration/Assignment Procedures:  New response codes are allocated
>        on a first-come/first-serve basis with specification required.
>
>     Registrant Contact:  IETF, XCON working group, (xcon@ietf.org), Mary
>        Barnes (mary.ietf.barnes@gmail.com).
>
>     This section pre-registers the following thirteen initial response
>     codes as described above inSection 4.1  <http://tools.ietf.org/html/draft-ietf-xcon-ccmp-12#section-4.1>:
>     [ ... ]

Thank you for considering my comments.

Mykyta Yevstifeyev

19.02.2011 0:36, The IESG wrote:
> The IESG has received a request from the Centralized Conferencing WG
> (xcon) to consider the following document:
> - 'Centralized Conferencing Manipulation Protocol'
>    <draft-ietf-xcon-ccmp-12.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 2011-03-04. 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-xcon-ccmp/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-xcon-ccmp/
>
>
>
> The following IPR Declarations may be related to this I-D:
>
> /ipr/472/
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


--------------000404030008070201020007
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">
    Hello,<br>
    <br>
    Let me briefly comment IANA considerations sub-sections, that define
    two registries.<br>
    <br>
    See my comments in-line.<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage"><span class="h3"><h3><a name="section-12.5">12.5</a>.  CCMP Protocol Registry</h3></span>

   This document requests that the IANA create a new registry for the
   CCMP protocol including an initial registry for operation types and
   response codes.

<span class="h4"><h4><a name="section-12.5.1">12.5.1</a>.  CCMP Message Types</h4></span>

   The CCMP messages are described in <a href="http://tools.ietf.org/html/draft-ietf-xcon-ccmp-12#section-4.1">Section 4.1</a> and defined in the XML
   schema in <a href="http://tools.ietf.org/html/draft-ietf-xcon-ccmp-12#section-11">Section 11</a>.  The following summarizes the requested
</pre>
      <pre class="newpage">  registry:

   Related Registry:   CCMP Message Types Registry

   Defining RFC:  RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
      with the RFC number for this specification.]

   Registration/Assignment Procedures:  New CCMP message types are
      allocated on a specification required basis.
</pre>
    </blockquote>
    Here you should have the normative reference to RFC 5226.<br>
    <blockquote type="cite">
      <pre class="newpage">
   Registrant Contact:  IETF, XCON working group, (<a class="moz-txt-link-abbreviated" href="mailto:xcon@ietf.org">xcon@ietf.org</a>), Mary
      Barnes (<a class="moz-txt-link-abbreviated" href="mailto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>).
</pre>
    </blockquote>
    As far as I may see, this registry definition does not conform to
    that described by RFC 5226.&nbsp; Particularly, there are no description
    of the format of the registry and its entries as well as some other
    information, required by that document.&nbsp; See here:&nbsp;
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc5226#section-4.2">http://tools.ietf.org/html/rfc5226#section-4.2</a><br>
    <blockquote type="cite">
      <pre class="newpage">
   This section pre-registers the following initial CCMP message types:
  [ ... ]

<span class="h4"><h4><a name="section-12.5.2">12.5.2</a>.  CCMP Response Codes</h4></span>
</pre>
    </blockquote>
    Here the same as above apply.<br>
    <blockquote type="cite">
      <pre class="newpage">
   The following summarizes the requested registry for CCMP Response
   codes:

   Related Registry:   CCMP Response Code Registry

   Defining RFC:  RFC XXXX [NOTE TO IANA/RFC-EDITOR: Please replace XXXX
      with the RFC number for this specification.]

   Registration/Assignment Procedures:  New response codes are allocated
      on a first-come/first-serve basis with specification required.

   Registrant Contact:  IETF, XCON working group, (<a class="moz-txt-link-abbreviated" href="mailto:xcon@ietf.org">xcon@ietf.org</a>), Mary
      Barnes (<a class="moz-txt-link-abbreviated" href="mailto:mary.ietf.barnes@gmail.com">mary.ietf.barnes@gmail.com</a>).

   This section pre-registers the following thirteen initial response
   codes as described above in <a href="http://tools.ietf.org/html/draft-ietf-xcon-ccmp-12#section-4.1">Section 4.1</a>:
   [ ... ]</pre>
    </blockquote>
    <br>
    Thank you for considering my comments.<br>
    <br>
    Mykyta Yevstifeyev<br>
    <br>
    19.02.2011 0:36, The IESG wrote:
    <blockquote
      cite="mid:20110218223622.15783.95652.idtracker@localhost"
      type="cite">
      <pre wrap="">
The IESG has received a request from the Centralized Conferencing WG
(xcon) to consider the following document:
- 'Centralized Conferencing Manipulation Protocol'
  &lt;draft-ietf-xcon-ccmp-12.txt&gt; 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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2011-03-04. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-xcon-ccmp/">http://datatracker.ietf.org/doc/draft-ietf-xcon-ccmp/</a>



The following IPR Declarations may be related to this I-D:

/ipr/472/
_______________________________________________
IETF-Announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a>

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000404030008070201020007--

From hallam@gmail.com  Sat Feb 19 08:29:54 2011
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 870A23A6F56 for <ietf@core3.amsl.com>; Sat, 19 Feb 2011 08:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.489
X-Spam-Level: 
X-Spam-Status: No, score=-3.489 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIaTA18mc9EU for <ietf@core3.amsl.com>; Sat, 19 Feb 2011 08:29:53 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 3C2753A6F64 for <ietf@ietf.org>; Sat, 19 Feb 2011 08:29:53 -0800 (PST)
Received: by iwl42 with SMTP id 42so1463498iwl.31 for <ietf@ietf.org>; Sat, 19 Feb 2011 08:30:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=b5QL/hXuy2nXsUMK5+vIi1RJdo8ak/xDmpj1vuYupuc=; b=s0FvaypzPsaV7Qs2WqxOTuGnl00TPzeqmg9DckgJ/8zLmwbg4itp3nEQlOcTJ85jlZ qZv6LzOwWBVYGO0NBjxA/y1lO4W7GphD9105Y86XH8jB2IbfEFDi9yMIMqYKwKnDrgdf RtfRDBnd3U79dI/eONiUUtuqcoSibajNO78Cs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=M7rH6RWEti9D9qqdIChKWqr96X2tNJ+G8XteyvedTMPimYcDRMZUJksU0vF1dO6CCa Wl9BNmCdzk/ycCpnv3Vz3jKybAqFD3U3Fqe9GSbtB/DSmVai2Xwhk5ytU1urtLEpeU67 IsDlgyb2R6Y+NiRbMBbOC88K4R4jV+5F9F+nQ=
MIME-Version: 1.0
Received: by 10.42.222.202 with SMTP id ih10mr2540078icb.236.1298133029748; Sat, 19 Feb 2011 08:30:29 -0800 (PST)
Received: by 10.42.215.140 with HTTP; Sat, 19 Feb 2011 08:30:29 -0800 (PST)
In-Reply-To: <DC4CE4EE-9238-46A2-9F69-73FF40103CBA@network-heretics.com>
References: <BF118113-AF47-4250-A24F-81E6217FCA3E@gmail.com> <4CE9F51C.2010201@dougbarton.us> <alpine.LSU.2.00.1011221451450.4075@hermes-2.csi.cam.ac.uk> <4CEC2A46.8040300@dougbarton.us> <p06240848c911df19b671@10.20.30.150> <4CEC32DF.203@dougbarton.us> <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com> <DC4CE4EE-9238-46A2-9F69-73FF40103CBA@network-heretics.com>
Date: Sat, 19 Feb 2011 08:30:29 -0800
Message-ID: <AANLkTimQPYc06a=ziJj=bs2YUdKOQYb4tT6gJSZNNdGN@mail.gmail.com>
Subject: Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=20cf3054ab2b1c0136049ca526b8
Cc: "ietf@ietf.org" <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2011 16:29:54 -0000

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

On Fri, Feb 18, 2011 at 10:10 AM, Keith Moore <moore@network-heretics.com>wrote:

> On Feb 18, 2011, at 12:46 PM, Phillip Hallam-Baker wrote:
>
> > This protocol has established a legacy base, as in it is going to be a
> part of the infrastructure we have to work round for decades even if Apple
> abandon it tomorrow.
> >
> > It is now futile to attempt modification of the protocol except in
> limited ways that do not impact the legacy base.
> >
> > Therefore we need to have a description of the protocol as a standard
> used on the Internet.
>
> Does not follow.   Having a description of the protocol, as it was
> deployed, documented is usually a good idea.   Having it as standard, not
> necessarily so.  There are a great many protocols which have "established a
> legacy base" which are not suitable for standardization.


Internet Standards are what run on the Internet.

The reason that I keep proposing process and document changes is because I
would like the IETF to be more effective in playing a leadership role in
Internet Standards making.


But take a look at the events in Egypt and Tunisia. The events that are
beginning in Lybia and Bahrain. The Web was originally designed and deployed
in the aftermath of the year of miracles, 1989, the year the Berlin Wall and
the iron curtain fell.

The Web is bigger than one person or one organization.

So expecting to control its growth or development is as futile for us as for
anyone else.

Which if people think about it, is rather a good thing. If the IETF had the
ability to control the development of the Web, the tyrants and the dictators
who are murdering their own people as I write would be attacking the IETF as
well.


-- 
Website: http://hallambaker.com/

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

<br><br><div class=3D"gmail_quote">On Fri, Feb 18, 2011 at 10:10 AM, Keith =
Moore <span dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com">m=
oore@network-heretics.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex;">
<div class=3D"im">On Feb 18, 2011, at 12:46 PM, Phillip Hallam-Baker wrote:=
<br>
<br>
&gt; This protocol has established a legacy base, as in it is going to be a=
 part of the infrastructure we have to work round for decades even if Apple=
 abandon it tomorrow.<br>
&gt;<br>
&gt; It is now futile to attempt modification of the protocol except in lim=
ited ways that do not impact the legacy base.<br>
&gt;<br>
&gt; Therefore we need to have a description of the protocol as a standard =
used on the Internet.<br>
<br>
</div>Does not follow. =A0 Having a description of the protocol, as it was =
deployed, documented is usually a good idea. =A0 Having it as standard, not=
 necessarily so. =A0There are a great many protocols which have &quot;estab=
lished a legacy base&quot; which are not suitable for standardization.</blo=
ckquote>
<div><br></div><div>Internet Standards are what run on the Internet.</div><=
div><br></div><div>The reason that I keep proposing process and document ch=
anges is because I would like the IETF to be more effective in playing a le=
adership role in Internet Standards making.</div>
<div><br></div><div><br></div><div>But take a look at the events in Egypt a=
nd Tunisia. The events that are beginning in Lybia and Bahrain. The Web was=
 originally designed and deployed in the aftermath of the year of miracles,=
 1989, the year the Berlin Wall and the iron curtain fell.</div>
<div><br></div><div>The Web is bigger than one person or one organization.=
=A0</div><div><br></div><div>So expecting to control its growth or developm=
ent is as futile for us as for anyone else.</div><div><br></div><div>Which =
if people think about it, is rather a good thing. If the IETF had the abili=
ty to control the development of the Web, the tyrants and the dictators who=
 are murdering their own people as I write would be attacking the IETF as w=
ell.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br><br>

--20cf3054ab2b1c0136049ca526b8--

From john-ietf@jck.com  Sat Feb 19 08:48:27 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3EE0E3A6F53; Sat, 19 Feb 2011 08:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.237
X-Spam-Level: 
X-Spam-Status: No, score=-102.237 tagged_above=-999 required=5 tests=[AWL=0.362, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXAqdQXaSyNl; Sat, 19 Feb 2011 08:48:26 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id EB3A93A6DF6; Sat, 19 Feb 2011 08:48:25 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PqpzS-0003lM-90; Sat, 19 Feb 2011 11:49:02 -0500
Date: Sat, 19 Feb 2011 11:49:01 -0500
From: John C Klensin <john-ietf@jck.com>
To: iaoc@ietf.org
Subject: xml2rfc and legal services RFPs
Message-ID: <E23665735D529B2C8CC3A393@PST.JCK.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2011 16:48:27 -0000

Hi.

This is not an attempt to derail either of these RFPs, nor is it
a formal appeal (request for review).  However, these two RFPs
raise an issue that may be worth some consideration.

The clear intent of the discussions leading up to RFC 4071/ BCP
101, and some of text in that document, was that the IASA was to
act with maximum transparency to the community and openness to
community comment.   It is especially important that substantive
decisions be open for community review and discussion before
they are made because, especially for those that are eventually
represented by contracts, there is no mechanism for review later.

IASA has recently issued two RFPs -- for legal services and for
a reprogrammed version of xml2rfc -- with no advance indication
to the community (at least that I can find) that they were
coming or opportunity for the community to review draft
provisions.  The clear expectation is that proposals will be
submitted (on a fairly short timeframe) and that the IAD and
IAOC will do whatever they do to evaluate the proposals and
establish contracts.   I don't know whether that is harmful in
these particular cases, but I don't believe it is how the
community had intended that things be done.

FWIW, community discussion might have improved at least the
XML2RFC one -- either the details of the RFP or community
confidence that it addresses/includes the right specifications.
For example, of the very large number of extensions or additions
that have bee requested over the years, the RFP selects two
(explicit line breaks in titles) and alternate anchors for
citations/references) but ignores the others.   I know that the
ability to easily index and cross-reference items in bulleted
lists, to easily generate numbers for ABNF productions (rules)
and build an index of productions, to have indexing reflect
section (and other subdivision) numbers rather than page numbers
(as various RFC style guides have required for years and that
becomes particularly important as people contemplate
non-paginated output formats), the ability to properly reference
books and journal articles without resorting to odd tricks
involving seriesInfo, and better handling of widows and orphans
(especially with regard to section title-text and lists with
undented headings top my personal list, but there are certainly
others.   

In addition, one of the two extensions that was specified
involves the addition of a new format-specific directive that is
exclusive to xml2rfc, not the DTD/Schema, thereby making
equivalent processing by other, XML-standard, processors
problematic and violating the fundamental principle that generic
markup does not specify formatting.   Perhaps community members
might have been able to propose design models that are more
friendly to XML principles and other tools (even I can think of
one or two).

The two extensions that were chosen may be the most important
ones, and there may be a reason why two extensions were chosen
rather than one or five.  But it seems to me that the community,
and perhaps even the text of the RFP and the proposals that will
arrive in response, would have benefited from some opportunity
for review and discussion.

Can we at least agree to more openness about draft RFP contents
in the future?  Or get an explanation from the IAOC as to why
the procedural model now seems to include issuance of RFPs
without any opportunity for community review of their
substantive provisions?

thanks,
   john






From moore@network-heretics.com  Sat Feb 19 09:42:40 2011
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 962F63A6F62 for <ietf@core3.amsl.com>; Sat, 19 Feb 2011 09:42:40 -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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4IQlImQY6QB for <ietf@core3.amsl.com>; Sat, 19 Feb 2011 09:42:39 -0800 (PST)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 415723A6EE0 for <ietf@ietf.org>; Sat, 19 Feb 2011 09:42:39 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.messagingengine.com (Postfix) with ESMTP id 789B020B93; Sat, 19 Feb 2011 12:43:15 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 19 Feb 2011 12:43:15 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=subject:mime-version:content-type:from:in-reply-to:date:cc:message-id:references:to; s=smtpout; bh=Mf9SxG+u3iGvQkFLOTIJyStCTpg=; b=cBnIL6/Dt3XFOzS8xFuVkvEI4sqAhXspX7ccTfJ3+OS1O+mMDMXAFj5pCdufVn4psiG1GlDlgvkyHX0ZVfXNqaxXxYsKi5ycGEugLSmAwV/enD8Qnq3T6noFUl5RrkdVArbIwC/+UM7GQz7T4WCO+wDgO14VwKaNV/x6lcVGvdw=
X-Sasl-enc: ZZOK3CbwTIq7jDTJTloqwr2vYrAK+gXyupO7vWxfuqfe 1298137395
Received: from host65-16-145-177.birch.net (host65-16-145-177.birch.net [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AEDB0446393; Sat, 19 Feb 2011 12:43:14 -0500 (EST)
Subject: Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-122--144869504
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <AANLkTimQPYc06a=ziJj=bs2YUdKOQYb4tT6gJSZNNdGN@mail.gmail.com>
Date: Sat, 19 Feb 2011 12:43:13 -0500
Message-Id: <717556C4-46A3-46ED-892D-4BE843AD0639@network-heretics.com>
References: <BF118113-AF47-4250-A24F-81E6217FCA3E@gmail.com> <4CE9F51C.2010201@dougbarton.us> <alpine.LSU.2.00.1011221451450.4075@hermes-2.csi.cam.ac.uk> <4CEC2A46.8040300@dougbarton.us> <p06240848c911df19b671@10.20.30.150> <4CEC32DF.203@dougbarton.us> <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com> <DC4CE4EE-9238-46A2-9F69-73FF40103CBA@network-heretics.com> <AANLkTimQPYc06a=ziJj=bs2YUdKOQYb4tT6gJSZNNdGN@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "ietf@ietf.org" <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2011 17:42:40 -0000

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

On Feb 19, 2011, at 11:30 AM, Phillip Hallam-Baker wrote:

> On Fri, Feb 18, 2011 at 10:10 AM, Keith Moore =
<moore@network-heretics.com> wrote:
> On Feb 18, 2011, at 12:46 PM, Phillip Hallam-Baker wrote:
>=20
> > This protocol has established a legacy base, as in it is going to be =
a part of the infrastructure we have to work round for decades even if =
Apple abandon it tomorrow.
> >
> > It is now futile to attempt modification of the protocol except in =
limited ways that do not impact the legacy base.
> >
> > Therefore we need to have a description of the protocol as a =
standard used on the Internet.
>=20
> Does not follow.   Having a description of the protocol, as it was =
deployed, documented is usually a good idea.   Having it as standard, =
not necessarily so.  There are a great many protocols which have =
"established a legacy base" which are not suitable for standardization.
>=20
> Internet Standards are what run on the Internet.

Lots of things run on the Internet that are not standard.

> The reason that I keep proposing process and document changes is =
because I would like the IETF to be more effective in playing a =
leadership role in Internet Standards making.

Ideally, IETF's role is to provide advice that helps the Internet and =
Internet-based protocols work well.   Merely blessing things that do not =
work well is not playing a leadership role.

> The Web is bigger than one person or one organization.=20
>=20
> So expecting to control its growth or development is as futile for us =
as for anyone else.

Control has nothing to do with it.   But if IETF doesn't fairly reliably =
give good advice, its reputation will decline and IETF will become less =
relevant.

Keith


--Apple-Mail-122--144869504
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><div>On Feb 19, 2011, at 11:30 AM, Phillip Hallam-Baker wrote:</div><br><blockquote type="cite"><div class="gmail_quote">On Fri, Feb 18, 2011 at 10:10 AM, Keith Moore <span dir="ltr">&lt;<a href="mailto:moore@network-heretics.com">moore@network-heretics.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
<div class="im">On Feb 18, 2011, at 12:46 PM, Phillip Hallam-Baker wrote:<br>
<br>
&gt; This protocol has established a legacy base, as in it is going to be a part of the infrastructure we have to work round for decades even if Apple abandon it tomorrow.<br>
&gt;<br>
&gt; It is now futile to attempt modification of the protocol except in limited ways that do not impact the legacy base.<br>
&gt;<br>
&gt; Therefore we need to have a description of the protocol as a standard used on the Internet.<br>
<br>
</div>Does not follow. &nbsp; Having a description of the protocol, as it was deployed, documented is usually a good idea. &nbsp; Having it as standard, not necessarily so. &nbsp;There are a great many protocols which have "established a legacy base" which are not suitable for standardization.</blockquote>
<div><br></div><div>Internet Standards are what run on the Internet.</div></div></blockquote><div><br></div>Lots of things run on the Internet that are not standard.</div><div><br><blockquote type="cite"><div class="gmail_quote"><div>The reason that I keep proposing process and document changes is because I would like the IETF to be more effective in playing a leadership role in Internet Standards making.</div></div></blockquote><div><br></div><div>Ideally, IETF's role is to provide advice that helps the Internet and Internet-based protocols work well. &nbsp; Merely blessing things that do not work well is not playing a leadership role.</div><br><blockquote type="cite"><div class="gmail_quote">
<div>The Web is bigger than one person or one organization.&nbsp;</div><div><br></div><div>So expecting to control its growth or development is as futile for us as for anyone else.</div></div></blockquote><div><br></div>Control has nothing to do with it. &nbsp; But if IETF doesn't fairly reliably give good advice, its reputation will decline and IETF will become less relevant.</div><div><br></div><div>Keith</div><div><br></div></body></html>
--Apple-Mail-122--144869504--

From ron.even.tlv@gmail.com  Sun Feb 20 05:49:45 2011
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10C893A6C82; Sun, 20 Feb 2011 05:49:45 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eS2TdtYfn1yE; Sun, 20 Feb 2011 05:49:42 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id B97EC3A6FD8; Sun, 20 Feb 2011 05:49:41 -0800 (PST)
Received: by fxm15 with SMTP id 15so1639503fxm.31 for <multiple recipients>; Sun, 20 Feb 2011 05:50:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=MzYfImwhLYlj0N2ONnrAiixL1ZPpBEKT1W+I8VF20d0=; b=RdE6aq6GWfIoEuLb1keuV0l/hquK1LfS1rzNx3D1A6qPPhLniZAOHywV6cLG/WdLQJ 95JtgJ/2Iwj4jTbpaPPE8rZF6UmM2sNOXLmcrBlikwwEuJWiRkxTN0UXajQ06FE+Ze51 BLIqUZoQ6ozKVvh7gvhtL5H93+TJY4HNbZnHU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; b=G1303bYl61kRbysHt6vzmRE4OWCSufD+/h2SxZ8XjnssWsZ+KTON1bB+oizR0+HUsI rrPY+Ak9y4zKjwTSbAJxe/rbW4GYKCskvOVUrKfUQyZ8ysE59ObLqYEuW8wJzFuWpLK4 RqI9EvLhHRQkkfB50wCLoP8CfeYEu4mBsxbvE=
Received: by 10.223.54.132 with SMTP id q4mr480108fag.117.1298209819143; Sun, 20 Feb 2011 05:50:19 -0800 (PST)
Received: from windows8d787f9 (bzq-79-178-22-235.red.bezeqint.net [79.178.22.235]) by mx.google.com with ESMTPS id c11sm1965499fav.2.2011.02.20.05.50.14 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 20 Feb 2011 05:50:17 -0800 (PST)
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>, <draft-ietf-morg-multimailbox-search.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-morg-multimailbox-search-06
Date: Sun, 20 Feb 2011 15:45:31 +0200
Message-ID: <4d611c19.4b91df0a.4e61.ffffc2c5@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00D7_01CBD115.395BD870"
X-Mailer: Microsoft Office Outlook 12.0
Thread-index: AcvRBFqeCy3nGtCiSFqsEK2apBti3Q==
Content-Language: en-us
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Feb 2011 13:49:45 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00D7_01CBD115.395BD870
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-morg-multimailbox-search-06

Reviewer: Roni Even

Review Date:2011-2-20

IETF LC End Date: 2011-2-28

IESG Telechat date:

 

Summary: This draft is ready for publication as Experimental  RFC.

 

Major issues:

None

 

Minor issues:

None

 

Nits/editorial comments:

None

 


------=_NextPart_000_00D7_01CBD115.395BD870
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:"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.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
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: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=3DMsoNormal><o:p>&nbsp;</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: =
draft-ietf-morg-multimailbox-search-06<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:2011&#8211;2&#8211;20<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: 2011&#8211;2&#8211;28<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 Experimental&nbsp; =
RFC.<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"'>None<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"'>None<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"'>None<o:p></=
o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00D7_01CBD115.395BD870--


From bertietf@bwijnen.net  Mon Feb 21 00:20:31 2011
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 30CCE3A6FBE; Mon, 21 Feb 2011 00:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0hwjDhXErqVf; Mon, 21 Feb 2011 00:20:30 -0800 (PST)
Received: from postlady.ripe.net (postlady.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1341]) by core3.amsl.com (Postfix) with ESMTP id 534FF3A6F84; Mon, 21 Feb 2011 00:20:29 -0800 (PST)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postlady.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1PrR0u-0006lp-NX; Mon, 21 Feb 2011 09:21:02 +0100
Received: from dog.ripe.net ([193.0.1.217] helo=guest184.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1PrR0u-0006Mv-Km; Mon, 21 Feb 2011 09:21:00 +0100
Message-ID: <4D62206E.2030909@bwijnen.net>
Date: Mon, 21 Feb 2011 09:21:02 +0100
From: "Bert (IETF) Wijnen" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Tina Tsou <tena@huawei.com>
Subject: Re: Review of draft-ietf-netconf-4741bis-07
References: <00dc01cbc734$9ab8cbe0$d02a63a0$@com>
In-Reply-To: <00dc01cbc734$9ab8cbe0$d02a63a0$@com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd4071e60cfdd6c027100037708add5603a
Cc: iesg@ietf.org, "Ersue, Mehmet \(NSN - DE/Munich\)" <mehmet.ersue@nsn.com>, draft-ietf-netconf-4741bis@tools.ietf.org, ietf@ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 08:20:31 -0000

Revision 9 is out and tried to address IETF LC comments

Here is the diff between the rev you reviewed and the latest one:
    http://tools.ietf.org/rfcdiff?url1=draft-ietf-netconf-4741bis-07&url2=draft-ietf-netconf-4741bis-09
Bert
document shepherd

On 2/8/11 3:05 AM, Tina Tsou wrote:
> I have reviewed this document as part of the security directorate's ongoing
> effort to review all IETF documents being processed by the IESG.  These
> comments were written primarily for the benefit of the security area
> directors.  Document editors and WG chairs should treat these comments just
> like any other last call comments.
>
> It is well written, so only some editorial comments are below.
>
> #1
> "
> 2.2.  Authentication, Integrity, and Confidentiality
> ...
> 2.3.  Authentication
> ...
> "
>
> Perhaps the Titles of 2.2 and 2.3 can harmonize better to explain why there
> are two "authentications" here.
>
> #2
> "
> 6.2.  Subtree Filter Components
>
>     A subtree filter is comprised of XML elements and their XML
>     attributes.  There are five types of components that may be present
>     in a subtree filter:
>
>     o  Namespace Selection
>
>     o  Attribute Match Expressions
>
>     o  Containment Nodes
>
>     o  Selection Nodes
>
>     o  Content Match Nodes
> ...
> "
>
> If a figure could be provided to describe the relationship among these 5
> components and when it becomes what, it would be very helpful for readers to
> understand more easily.
>
> #3
> "
> 6.2.3.  Containment Nodes
>
>     Nodes that contain child elements within a subtree filter are called
>     "containment nodes".
>
> I would say "Child Elements Nodes" or "Child Nodes" might be a little bit
> more of straight forward than "Containment Nodes".
>
>
> #4
> "
> 7.2.<edit-config>
> ...
> Parameters:
> ...
> merge:  The configuration data in the<config>  parameter is
>              merged with the configuration at the corresponding level in
>              the target datastore.  This is the default behavior.
> ...
> "
> Has the<config>  parameter been introduced before?
>
>
> Best Regards,
> Tina TSOU
> http://tinatsou.weebly.com/contact.html
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From ajs@shinkuro.com  Mon Feb 21 05:03:06 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEE693A70FA for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 05:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwX2peJSz5BZ for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 05:03:06 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id EA7853A70F6 for <ietf@ietf.org>; Mon, 21 Feb 2011 05:03:05 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id A4C481ECB408 for <ietf@ietf.org>; Mon, 21 Feb 2011 13:03:46 +0000 (UTC)
Date: Mon, 21 Feb 2011 08:03:45 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: Re: Stop the process trolls ! Re: Last Call: draft-cheshire-dnsext-dns-sd-07.txt
Message-ID: <20110221130344.GE32224@shinkuro.com>
References: <BF118113-AF47-4250-A24F-81E6217FCA3E@gmail.com> <4CE9F51C.2010201@dougbarton.us> <alpine.LSU.2.00.1011221451450.4075@hermes-2.csi.cam.ac.uk> <4CEC2A46.8040300@dougbarton.us> <p06240848c911df19b671@10.20.30.150> <4CEC32DF.203@dougbarton.us> <0AE5282C-3630-46F7-9FEE-51C83FAA37E9@gmail.com> <DC4CE4EE-9238-46A2-9F69-73FF40103CBA@network-heretics.com> <AANLkTimQPYc06a=ziJj=bs2YUdKOQYb4tT6gJSZNNdGN@mail.gmail.com> <717556C4-46A3-46ED-892D-4BE843AD0639@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <717556C4-46A3-46ED-892D-4BE843AD0639@network-heretics.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 13:03:07 -0000

On Sat, Feb 19, 2011 at 12:43:13PM -0500, Keith Moore wrote:
> 
> Ideally, IETF's role is to provide advice that helps the Internet and Internet-based protocols work well.   Merely blessing things that do not work well is not playing a leadership role.
> 

Let us look at the case of mDNS.  Apple has actively listened to the
advice it has been given and worked within the limits of its deployed
base to make alterations.  If the IETF had been a little more
responsive, actually, the deployed-base problems might not have been
so bad (this is not to say that the IETF bears all the responsibility
for how this document has languished, note: the authors have not
always been quick to respond either).  What else do we want from our
standards procedure?

It seems to me that the documents should therefore be published.  It
is IMO better that they be published on the standards track, but who
cares?  The distinction between Informational and Standards Track when
a document actually is a protocol is one that IETF arcana fans and
nobody else in the universe cares about.  

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From chair@ietf.org  Mon Feb 21 07:47:30 2011
Return-Path: <chair@ietf.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 042953A711F; Mon, 21 Feb 2011 07:47:30 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J7ExS1En68w6; Mon, 21 Feb 2011 07:47:29 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 552A33A7108; Mon, 21 Feb 2011 07:47:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 8ABE1E08AF; Mon, 21 Feb 2011 07:48:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VaNpoO1Ujwca; Mon, 21 Feb 2011 07:48:11 -0800 (PST)
Received: from [192.168.2.105] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) by c1a.amsl.com (Postfix) with ESMTPSA id 31DEAE0827; Mon, 21 Feb 2011 07:48:11 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Datatracker Wiki Pages
Date: Mon, 21 Feb 2011 10:48:09 -0500
Message-Id: <D80AE554-4563-4C6C-929E-78DE5BD9F211@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 15:47:30 -0000

The IAOC has been developing specifications for the enhancement and =
improvement of the Datatracker.  To facilitate review and make it easier =
for people to track the progress of the specification developments, we =
are putting pointers to these documents on a wiki page:

   http://trac.tools.ietf.org/tools/ietfdb/wiki/DatatrackerDrafts

Right now, four Internet-Drafts are listed.  Three are complete, and one =
are in active review:

  draft-ietf-proto-wgdocument-states, approved, RFC Editor queue
  draft-juskevicius-datatracker-wgdocstate-reqts, approved, RFC Editor =
queue
  draft-hoffman-alt-streams-tracker, finished, what stream to publish?
  draft-ietf-genarea-datatracker-community, near IETF Last Call

Thanks,
Russ=

From daedulus@btconnect.com  Mon Feb 21 09:27:43 2011
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 18C1E3A6DDB; Mon, 21 Feb 2011 09:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.283
X-Spam-Level: 
X-Spam-Status: No, score=-1.283 tagged_above=-999 required=5 tests=[AWL=-0.696, BAYES_00=-2.599, FAKE_REPLY_C=2.012]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqfXgFAWlKUN; Mon, 21 Feb 2011 09:27:42 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by core3.amsl.com (Postfix) with ESMTP id 912B73A6E10; Mon, 21 Feb 2011 09:27:41 -0800 (PST)
Received: from host86-141-16-12.range86-141.btcentralplus.com (HELO pc6) ([86.141.16.12]) by c2beaomr10.btconnect.com with SMTP id BTW31338; Mon, 21 Feb 2011 17:28:19 +0000 (GMT)
Message-ID: <000c01cbd1e3$c1036e40$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "ietf" <ietf@ietf.org>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructure to 
Date: Mon, 21 Feb 2011 17:23:40 +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.0A0B0302.4D62A0B3.0065, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4D62A0B6.0104,ss=1,fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=single engine
X-Junkmail-IWF: false
Cc: iesg <iesg@ietf.org>, sidr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 17:27:43 -0000

I find this I-D problematic.  The subject matter is of crucial importance,
comparable to, or perhaps more important than, IPv6, yet this I-D is not
an easy read and there should be one such somewhere.

sidr has produced an awesome collection of I-Ds (some now obsolete) but it is
not obvious, short of spending a few months in the archives, how they fit
together.  Other major projects - snmp for example - produced an Introduction,
acting as a starting point and a road map to the other I-Ds and I think that
that should be a prerequisite for sidr.  This I-D is not it (even if it could
be); its Normative
References include a further 80 pages of sidr I-Ds!

One small example.  The I-Ds have several references to RPKI and indeed, that
appears in -arch; but it first appears on page 8 and is not even expanded, let
alone explained.  Of course you can turn to Wikipedia and you find a clear
explanation of what RPKI is but you should not need Wikipedia to understand
something as important as sidr.  This I-D seems to be written to be understood
by those who understand it:-(

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary at ietf.org>
To: "IETF-Announce" <ietf-announce at ietf.org>
Cc: <sidr@ietf.org>
Sent: Monday, February 07, 2011 5:14 PM
Subject: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructure to


>
> The IESG has received a request from the Secure Inter-Domain Routing WG
> (sidr) to consider the following document:
> - 'An Infrastructure to Support Secure Internet Routing'
>   <draft-ietf-sidr-arch-11.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 at ietf.org mailing lists by 2011-02-21. Exceptionally, comments may be
> sent to iesg at ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>
>
>
> The following IPR Declarations may be related to this I-D:
>
> /ipr/1204/
>


From bob.hinden@gmail.com  Mon Feb 21 11:22:51 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 922A93A7156; Mon, 21 Feb 2011 11:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.571
X-Spam-Level: 
X-Spam-Status: No, score=-103.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0mGnk9TgJSJ; Mon, 21 Feb 2011 11:22:50 -0800 (PST)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by core3.amsl.com (Postfix) with ESMTP id 32B173A714D; Mon, 21 Feb 2011 11:22:50 -0800 (PST)
Received: by vws16 with SMTP id 16so1280887vws.27 for <multiple recipients>; Mon, 21 Feb 2011 11:23:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=rB9g4QkPsfG8p2hCqT84dpB82sFW5+eDGebibN5K0wY=; b=vHHN+aSwpvvTU9Wlw6jt9no1ackNam1fuKUxWl9BC103lxD8BT0lNFtlidfIH9BSP1 cMu85lxBG2pRK+6FXZQxb7Toe2fN2/xFF1pKYxvSDA+/stfl0a3b5CTMO1DlN6t5XJev kcEeeI+u803dcnVtL2G5FCityyfYGeiEt72SE=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=qjLZ88zD8/XfEf3zdNn06MlQCAamyAzDsD/APEz8y7BGzGgo4zuwlHywy2oXp7rPq8 liQoAedVAxDBRaeFxd27czx/mtmF0RVxge+D5TId406CiecTrxKkYsI/HQ4yJVaA1jwe IAynWByB8P9DNa/UalX6/6S+NpTfRbgRyxH9g=
Received: by 10.52.157.74 with SMTP id wk10mr2587793vdb.114.1298316212296; Mon, 21 Feb 2011 11:23:32 -0800 (PST)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id i14sm2480630vcr.11.2011.02.21.11.23.29 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Feb 2011 11:23:30 -0800 (PST)
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <E23665735D529B2C8CC3A393@PST.JCK.COM>
Date: Mon, 21 Feb 2011 11:23:28 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <54C48986-B211-462C-B942-247886122AF2@gmail.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1082)
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 19:22:51 -0000

John,

Support for the xml2rfc tool was discussed on the IETF mail list when =
Marshall Rose indicated he could no longer support the tool.  Several =
people volunteered to maintain the tool, and they recommended the it be =
rewritten.  That recommendation plus the realization that this tool had =
become critical to IETF operations resulted in the IAOC deciding to =
issue a public RFP for a rewrite.

The Statement of Work in the xml2rfc RFP was reviewed and modified by =
the people on the tool-development list.  You can read the discussion =
at:

  =
http://www.ietf.org/mail-archive/web/tools-development/current/maillist.ht=
ml

There was an active discussion that resulted in many changes from what =
was first proposed.  While this wasn't the whole community I think it a =
good representation of the people who are interested in the xml2rfc =
tool.  I will send you the list members off line.  Also, we will use a =
subset of this group to review the bids.

The legal services RFP was developed inside the IAOC/Trust.  To be =
honest, I didn't see very much value in doing a community review for =
this.  We will consider it in the future.  I do note that this work was =
previously done without a public RFP (dating back to when Wilmer-Hale =
was providing the service) so I think this is a better process than what =
was used earlier.

In the future, we will strive to give more notice to the community on =
planned RFPs.

Bob

p.s. I will forward your specific comments to tools-discuss.


On Feb 19, 2011, at 8:49 AM, John C Klensin wrote:

> Hi.
>=20
> This is not an attempt to derail either of these RFPs, nor is it
> a formal appeal (request for review).  However, these two RFPs
> raise an issue that may be worth some consideration.
>=20
> The clear intent of the discussions leading up to RFC 4071/ BCP
> 101, and some of text in that document, was that the IASA was to
> act with maximum transparency to the community and openness to
> community comment.   It is especially important that substantive
> decisions be open for community review and discussion before
> they are made because, especially for those that are eventually
> represented by contracts, there is no mechanism for review later.
>=20
> IASA has recently issued two RFPs -- for legal services and for
> a reprogrammed version of xml2rfc -- with no advance indication
> to the community (at least that I can find) that they were
> coming or opportunity for the community to review draft
> provisions.  The clear expectation is that proposals will be
> submitted (on a fairly short timeframe) and that the IAD and
> IAOC will do whatever they do to evaluate the proposals and
> establish contracts.   I don't know whether that is harmful in
> these particular cases, but I don't believe it is how the
> community had intended that things be done.
>=20
> FWIW, community discussion might have improved at least the
> XML2RFC one -- either the details of the RFP or community
> confidence that it addresses/includes the right specifications.
> For example, of the very large number of extensions or additions
> that have bee requested over the years, the RFP selects two
> (explicit line breaks in titles) and alternate anchors for
> citations/references) but ignores the others.   I know that the
> ability to easily index and cross-reference items in bulleted
> lists, to easily generate numbers for ABNF productions (rules)
> and build an index of productions, to have indexing reflect
> section (and other subdivision) numbers rather than page numbers
> (as various RFC style guides have required for years and that
> becomes particularly important as people contemplate
> non-paginated output formats), the ability to properly reference
> books and journal articles without resorting to odd tricks
> involving seriesInfo, and better handling of widows and orphans
> (especially with regard to section title-text and lists with
> undented headings top my personal list, but there are certainly
> others.  =20
>=20
> In addition, one of the two extensions that was specified
> involves the addition of a new format-specific directive that is
> exclusive to xml2rfc, not the DTD/Schema, thereby making
> equivalent processing by other, XML-standard, processors
> problematic and violating the fundamental principle that generic
> markup does not specify formatting.   Perhaps community members
> might have been able to propose design models that are more
> friendly to XML principles and other tools (even I can think of
> one or two).
>=20
> The two extensions that were chosen may be the most important
> ones, and there may be a reason why two extensions were chosen
> rather than one or five.  But it seems to me that the community,
> and perhaps even the text of the RFP and the proposals that will
> arrive in response, would have benefited from some opportunity
> for review and discussion.
>=20
> Can we at least agree to more openness about draft RFP contents
> in the future?  Or get an explanation from the IAOC as to why
> the procedural model now seems to include issuance of RFPs
> without any opportunity for community review of their
> substantive provisions?
>=20
> thanks,
>   john
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> IAOC mailing list
> IAOC@ietf.org
> https://www.ietf.org/mailman/listinfo/iaoc


From turners@ieca.com  Mon Feb 21 11:58:54 2011
Return-Path: <turners@ieca.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10DE23A717B for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 11:58:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.455
X-Spam-Level: 
X-Spam-Status: No, score=-101.455 tagged_above=-999 required=5 tests=[AWL=-0.852, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rx77nzR5ds+a for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 11:58:53 -0800 (PST)
Received: from nm21-vm0.bullet.mail.sp2.yahoo.com (nm21-vm0.bullet.mail.sp2.yahoo.com [98.139.91.220]) by core3.amsl.com (Postfix) with SMTP id 2C14D3A714D for <ietf@ietf.org>; Mon, 21 Feb 2011 11:58:53 -0800 (PST)
Received: from [98.139.91.67] by nm21.bullet.mail.sp2.yahoo.com with NNFMP; 21 Feb 2011 19:59:33 -0000
Received: from [98.139.91.14] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 21 Feb 2011 19:59:33 -0000
Received: from [127.0.0.1] by omp1014.mail.sp2.yahoo.com with NNFMP; 21 Feb 2011 19:59:33 -0000
X-Yahoo-Newman-Id: 185710.94515.bm@omp1014.mail.sp2.yahoo.com
Received: (qmail 79666 invoked from network); 21 Feb 2011 19:59:32 -0000
Received: from [10.13.53.182] (turners@166.137.15.89 with plain) by smtp115.biz.mail.mud.yahoo.com with SMTP; 21 Feb 2011 11:59:31 -0800 PST
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: G5X4e8kVM1m0fmZDyFlLJLqd0HTxOepSJvYQRoZCfEa2SDk 2hR3WKwP2bg5rcwmwVyUFFAJWokLZDpWbUyT3qmgAF.TGqqG_Gw2iGUF6hKT UxNGyp73NCcTJI2KsMEAdimTq3TGiUP0YR9Cro5.oxp3z1SqI_ptTHbrlqii rg7_S45tNtw4YloaifzDLNLP6N45ZTjSI5okU5F9bOUo_hl4s07wjNWtt4Av WrEC5Mxlzee5dNp9DTNfzKAw4Bhpppytapn0nf9WTmxJoRsUQANFfp2udizp mcRJHBS3E3wczbK3WQELt1pfKHxxach0nxEjqCkS.
X-Yahoo-Newman-Property: ymail-3
References: <000c01cbd1e3$c1036e40$4001a8c0@gateway.2wire.net> <AANLkTin36cA5r-Jr-j7-YqMrOR4_cDEystZFV7Eq-USf@mail.gmail.com>
In-Reply-To: <AANLkTin36cA5r-Jr-j7-YqMrOR4_cDEystZFV7Eq-USf@mail.gmail.com>
Mime-Version: 1.0 (iPhone Mail 8C148)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <975F6DE4-FF8F-4F6A-B9D2-38884E219BFF@ieca.com>
X-Mailer: iPhone Mail (8C148)
From: Sean Turner <turners@ieca.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructure to
Date: Mon, 21 Feb 2011 13:58:00 -0600
To: Christopher Morrow <morrowc.lists@gmail.com>
Cc: iesg <iesg@ietf.org>, ietf <ietf@ietf.org>, "sidr@ietf.org" <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 19:58:54 -0000

On Feb 21, 2011, at 1:15 PM, Christopher Morrow <morrowc.lists@gmail.com> wr=
ote:

> (not speaking for the authors, just observing some... also not
> speaking as a co-chair)
>=20
> On Mon, Feb 21, 2011 at 11:23 AM, t.petch <daedulus@btconnect.com> wrote:
>> I find this I-D problematic.  The subject matter is of crucial importance=
,
>> comparable to, or perhaps more important than, IPv6, yet this I-D is not
>> an easy read and there should be one such somewhere.
>>=20
>=20
> I thought there was to be an overview doc as well produced, with the
> goal being to lay out the basic parts referring to the other drafts
> for further info/expansion.
>=20
>> sidr has produced an awesome collection of I-Ds (some now obsolete) but i=
t is
>> not obvious, short of spending a few months in the archives, how they fit=

>> together.  Other major projects - snmp for example - produced an Introduc=
tion,
>> acting as a starting point and a road map to the other I-Ds and I think t=
hat
>> that should be a prerequisite for sidr.  This I-D is not it (even if it c=
ould
>> be); its Normative
>> References include a further 80 pages of sidr I-Ds!
>>=20
>> One small example.  The I-Ds have several references to RPKI and indeed, t=
hat
>> appears in -arch; but it first appears on page 8 and is not even expanded=
, let
>=20
> eh.. that's a nit that someone should file... "hey, you can't use an
> acronym for the first time without actually expanding it properly!"
>=20
> Can you cite the proper para/page/section on this so the authors can fix i=
t?
>=20

Maybe if we tweaked the last sentence in section 2:

Such a PKI, which is henceforth referred to as the Resource Public Key Infra=
structure (RPKI), is a central component of this architecture.

Spt

> -Chris
>=20
>> alone explained.  Of course you can turn to Wikipedia and you find a clea=
r
>> explanation of what RPKI is but you should not need Wikipedia to understa=
nd
>> something as important as sidr.  This I-D seems to be written to be under=
stood
>> by those who understand it:-(
>>=20
>> Tom Petch
>>=20
>>=20
>> ----- Original Message -----
>> From: "The IESG" <iesg-secretary at ietf.org>
>> To: "IETF-Announce" <ietf-announce at ietf.org>
>> Cc: <sidr@ietf.org>
>> Sent: Monday, February 07, 2011 5:14 PM
>> Subject: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructu=
re to
>>=20
>>=20
>>>=20
>>> The IESG has received a request from the Secure Inter-Domain Routing WG
>>> (sidr) to consider the following document:
>>> - 'An Infrastructure to Support Secure Internet Routing'
>>> <draft-ietf-sidr-arch-11.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 at ietf.org mailing lists by 2011-02-21. Exceptionally, comments ma=
y be
>>> sent to iesg at ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>>>=20
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>>>=20
>>>=20
>>>=20
>>> The following IPR Declarations may be related to this I-D:
>>>=20
>>> /ipr/1204/
>>>=20
>>=20
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>>=20
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr


From john-ietf@jck.com  Mon Feb 21 12:19:32 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED5003A6E38; Mon, 21 Feb 2011 12:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.309
X-Spam-Level: 
X-Spam-Status: No, score=-102.309 tagged_above=-999 required=5 tests=[AWL=0.290, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eipEnnqBG2pd; Mon, 21 Feb 2011 12:19:32 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 9D1763A6CCB; Mon, 21 Feb 2011 12:19:31 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PrcEv-000OLN-Af; Mon, 21 Feb 2011 15:20:13 -0500
Date: Mon, 21 Feb 2011 15:20:12 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Message-ID: <DFA887BC0886F81AADFA0390@PST.JCK.COM>
In-Reply-To: <54C48986-B211-462C-B942-247886122AF2@gmail.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM> <54C48986-B211-462C-B942-247886122AF2@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: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 20:19:33 -0000

--On Monday, February 21, 2011 11:23 -0800 Bob Hinden
<bob.hinden@gmail.com> wrote:

> John,
> 
> Support for the xml2rfc tool was discussed on the IETF mail
> list when Marshall Rose indicated he could no longer support
> the tool.  Several people volunteered to maintain the tool,
> and they recommended the it be rewritten.  That recommendation
> plus the realization that this tool had become critical to
> IETF operations resulted in the IAOC deciding to issue a
> public RFP for a rewrite.
>...

Bob,

Thanks for the reply.  Let me stress again that, even where I
might have a different opinion on some matters, I do not
question the IAOC's right to consult whomever (or whatever
lists) it thinks appropriate in  the process of developing draft
RFPs or draft SOWs.

I have opinions about the process used too, but they aren't very
significant.  For example, I note, in conjunction with your
comment...
 
> There was an active discussion that resulted in many changes
> from what was first proposed.  While this wasn't the whole
> community I think it a good representation of the people who
> are interested in the xml2rfc tool.  I will send you the list
> members off line.  Also, we will use a subset of this group to
> review the bids.

that there are 18 people on that list.  Unless I'm miscounted,
of the 18, 7 are AMSL or IETF professional staff, two more are
ISOC professional staff, and 5 (not counting overlaps) are IAOC
and/or IESG members.  This isn't quite the composition I would
have chosen for a group I expected to be representative of
either the broader IETF community or the community of active
writers of I-Ds.  But, again, that isn't the point, IMO.

>...
> In the future, we will strive to give more notice to the
> community on planned RFPs.

Perhaps I'm the only member of the community who cares any more.
If I am, maybe you should just ignore this.  But I believe that
the intent of the community at the time BCP 101 was written was
that the IAOC should not just be providing "notice" (although
that is desirable), or the opportunity to participate in the
specification-development process or watch it unfold (although I
think that would be desirable too), but that you post the text
of proposed RFPs for community comment.   Most of the time,
those comments won't yield anything.  But, just like Last Call
on standards track documents, exposure of a draft that is
believed to be finished to the community might turn something up
that the development process (no matter how good) didn't catch.
That "something" might be substantive; it might even be a detail
of specification style that was somehow overlooked.  As we all
known, this is a rather diverse community with a broad
collection of skills and experience that will never be
completely reflected in a small draft development or review
group, no matter how carefully chosen.  When it occurs, that is
valuable.  Even when it does not occur, it helps us all
understand that the IASA is operating as openly and
transparently as I think we all desire.

 best,
   john


From sob@harvard.edu  Mon Feb 21 12:33:47 2011
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2F1A3A6F5C for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 12:33:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.44
X-Spam-Level: 
X-Spam-Status: No, score=-102.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sh5atceleumi for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 12:33:47 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 16BA23A6E38 for <ietf@ietf.org>; Mon, 21 Feb 2011 12:33:46 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 9EBE988C654; Mon, 21 Feb 2011 15:34:28 -0500 (EST)
To: ietf@ietf.org
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Message-Id: <20110221203428.9EBE988C654@newdev.eecs.harvard.edu>
Date: Mon, 21 Feb 2011 15:34:28 -0500 (EST)
From: sob@harvard.edu (Scott O. Bradner)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 20:33:48 -0000

jck sed:
> Perhaps I'm the only member of the community who cares any more.

he is not alone

quite a few of us were quite worried when the IAOC was formed that
it would tend to evolve into a management group that thought
it knew best for the the IETF without getting around to asking.

announcing RFPs without any chance for the IETF community to 
comment is just the sort of the thing that I, for one, was
worried about.

I have an easy time understanding that the IAOC migt find it
a pain to consult with the community, and as John mentioned,
many times there will be little or no comment, but please
rethink your processes 

you may "not see very much value in doing a community review for this"
but, I do not think that should be your call. Always consult is
a better plan to ensure that the IAOC is not getting out of step
with the part of teh community that does care.

Scott


ps - long before Wilmer-Hale it was Hale and Dorr & I was involved
in the first pick so might have an opinion on future ones


From brian.e.carpenter@gmail.com  Mon Feb 21 12:41:08 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D48A3A6E38; Mon, 21 Feb 2011 12:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.423
X-Spam-Level: 
X-Spam-Status: No, score=-103.423 tagged_above=-999 required=5 tests=[AWL=0.176, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QnCmAhhLHSUl; Mon, 21 Feb 2011 12:41:07 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 974273A6FF7; Mon, 21 Feb 2011 12:41:06 -0800 (PST)
Received: by fxm15 with SMTP id 15so2909342fxm.31 for <multiple recipients>; Mon, 21 Feb 2011 12:41:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9zt9xdbrw4Sbm6Hw6mYYbunMRreLgPrXyHYCb4eX6LE=; b=ZWSy0AZrHUjfh/ZS/YHIBMsbZ48ADYTz4L0xbDGrnlqVHqtJ6LD3AzmfDcVAsnJw6N I4dMUz8XB9mjoxB8Yvs0qTwqFpxQXIWxb9tQhOkxmN+YXqAjMK3L2yuowhJpxu1Isd7F 3VbmmWENUme9ay2+dLsdBBtLeFMuiQ9FL2XuI=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=mXztqDTo83dBFxPRZ4C9tcCgkFmivhCinRRnEIZqXzi4WepZxTBEgBOIr10BCtZfne 4AzY2EOeXCbgqQZTzumtm+2RIfmOCZpj+1IObNHmatOjJBhrXvwephyLwrjFI14H2zz4 W/NmbgFy0utaVXRM5apYdzaJsYnqzbt/PQRfU=
Received: by 10.223.100.16 with SMTP id w16mr2385640fan.85.1298320821804; Mon, 21 Feb 2011 12:40:21 -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 n2sm2679475fam.4.2011.02.21.12.40.17 (version=SSLv3 cipher=OTHER); Mon, 21 Feb 2011 12:40:20 -0800 (PST)
Message-ID: <4D62CDAE.7070006@gmail.com>
Date: Tue, 22 Feb 2011 09:40:14 +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: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM> <54C48986-B211-462C-B942-247886122AF2@gmail.com>
In-Reply-To: <54C48986-B211-462C-B942-247886122AF2@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 20:41:08 -0000

Bob,

On 2011-02-22 08:23, Bob Hinden wrote:
> John,
> 
> Support for the xml2rfc tool was discussed on the IETF mail
> list when Marshall Rose indicated he could no longer support
> the tool.  Several people volunteered to maintain the tool,
> and they recommended the it be rewritten.  That
> recommendation plus the realization that this tool had become
> critical to IETF operations resulted in the IAOC deciding to
> issue a public RFP for a rewrite.
> 
> The Statement of Work in the xml2rfc RFP was reviewed and
> modified by the people on the tool-development list.  You can
> read the discussion at:
> 
> http://www.ietf.org/mail-archive/web/tools-development/current/maillist.html
>
> There was an active discussion that resulted in many changes
> from what was first proposed.  While this wasn't the whole
> community I think it a good representation of the people who
> are interested in the xml2rfc tool.  I will send you the list
> members off line.  Also, we will use a subset of this group
> to review the bids.

I think the tools development list was a good venue for the
detailed discussion. Was the process mentioned on tools-discuss
too? (I dropped off that one a while back, due to lack of
cycles, but it does seems the obvious place, not to mention the
xml2rfc list, where I don't recall it being mentioned).

> 
> The legal services RFP was developed inside the IAOC/Trust.
> To be honest, I didn't see very much value in doing a
> community review for this.  We will consider it in the
> future.  I do note that this work was previously done without
> a public RFP (dating back to when Wilmer-Hale was providing
> the service) so I think this is a better process than what
> was used earlier.
> 
> In the future, we will strive to give more notice to the
> community on planned RFPs.

I think that is appropriate, given the comments in BCP 101
about transparency. But I agree that for legal services, our
community doesn't particularly have the skills to wordsmith
an RFP.

   Brian


> 
> Bob
> 
> p.s. I will forward your specific comments to tools-discuss.
> 
> 
> On Feb 19, 2011, at 8:49 AM, John C Klensin wrote:
> 
>> Hi.
>> 
>> This is not an attempt to derail either of these RFPs, nor
>> is it a formal appeal (request for review).  However, these
>> two RFPs raise an issue that may be worth some
>> consideration.
>> 
>> The clear intent of the discussions leading up to RFC 4071/
>> BCP 101, and some of text in that document, was that the
>> IASA was to act with maximum transparency to the community
>> and openness to community comment.   It is especially
>> important that substantive decisions be open for community
>> review and discussion before they are made because,
>> especially for those that are eventually represented by
>> contracts, there is no mechanism for review later.
>> 
>> IASA has recently issued two RFPs -- for legal services and
>> for a reprogrammed version of xml2rfc -- with no advance
>> indication to the community (at least that I can find) that
>> they were coming or opportunity for the community to review
>> draft provisions.  The clear expectation is that proposals
>> will be submitted (on a fairly short timeframe) and that
>> the IAD and IAOC will do whatever they do to evaluate the
>> proposals and establish contracts.   I don't know whether
>> that is harmful in these particular cases, but I don't
>> believe it is how the community had intended that things be
>> done.
>> 
>> FWIW, community discussion might have improved at least the
>>  XML2RFC one -- either the details of the RFP or community 
>> confidence that it addresses/includes the right
>> specifications. For example, of the very large number of
>> extensions or additions that have bee requested over the
>> years, the RFP selects two (explicit line breaks in titles)
>> and alternate anchors for citations/references) but ignores
>> the others.   I know that the ability to easily index and
>> cross-reference items in bulleted lists, to easily generate
>> numbers for ABNF productions (rules) and build an index of
>> productions, to have indexing reflect section (and other
>> subdivision) numbers rather than page numbers (as various
>> RFC style guides have required for years and that becomes
>> particularly important as people contemplate non-paginated
>> output formats), the ability to properly reference books
>> and journal articles without resorting to odd tricks 
>> involving seriesInfo, and better handling of widows and
>> orphans (especially with regard to section title-text and
>> lists with undented headings top my personal list, but
>> there are certainly others.
>> 
>> In addition, one of the two extensions that was specified 
>> involves the addition of a new format-specific directive
>> that is exclusive to xml2rfc, not the DTD/Schema, thereby
>> making equivalent processing by other, XML-standard,
>> processors problematic and violating the fundamental
>> principle that generic markup does not specify formatting.
>> Perhaps community members might have been able to propose
>> design models that are more friendly to XML principles and
>> other tools (even I can think of one or two).
>> 
>> The two extensions that were chosen may be the most
>> important ones, and there may be a reason why two
>> extensions were chosen rather than one or five.  But it
>> seems to me that the community, and perhaps even the text
>> of the RFP and the proposals that will arrive in response,
>> would have benefited from some opportunity for review and
>> discussion.
>> 
>> Can we at least agree to more openness about draft RFP
>> contents in the future?  Or get an explanation from the
>> IAOC as to why the procedural model now seems to include
>> issuance of RFPs without any opportunity for community
>> review of their substantive provisions?
>> 
>> thanks, john
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________ IAOC
>> mailing list IAOC@ietf.org 
>> https://www.ietf.org/mailman/listinfo/iaoc
> 
> _______________________________________________ Ietf mailing
> list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From spencer@wonderhamster.org  Mon Feb 21 13:18:30 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 744AC3A7159; Mon, 21 Feb 2011 13:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.237
X-Spam-Level: 
X-Spam-Status: No, score=-102.237 tagged_above=-999 required=5 tests=[AWL=0.361, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvyQtUfX3lUG; Mon, 21 Feb 2011 13:18:29 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 4564C3A712A; Mon, 21 Feb 2011 13:18:29 -0800 (PST)
Received: from S73602b ([12.172.14.11]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0Lh8ff-1QN7y93sGN-00oHC0; Mon, 21 Feb 2011 16:19:04 -0500
Message-ID: <622C74FA4B4D440C8F6D28CB6B3E0372@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Bob Hinden" <bob.hinden@gmail.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM><54C48986-B211-462C-B942-247886122AF2@gmail.com> <4D62CDAE.7070006@gmail.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Date: Mon, 21 Feb 2011 15:18:54 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
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.5994
X-Provags-ID: V02:K0:mPtLpqyYcsCParV8FjOvSNYqOE0V3J6PhshuUJ9VIn3 v9vs87PibpJjCIvNTDavBW23XcWsm5e+8yFzb6VfhDBp+GjPDC S9O9yewTYO7YRnrP4ZY228/0wLki0jAEuK/6/I+QuWYLJbtAmu RKSIdC+inr4g6/v0XsJrZ/sgzcDaXcMXD4D6E3QmH/Kk2qSA/o ueLDBW9aVt4ObmjkhPRMac/cO3OG8zYfWaT/wxMur0=
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 21:18:30 -0000

For what it's worth,

I agree that when you're talking to the community about RFPs, it's great if 
that doesn't turn into a wordsmithing exercise on the ietf mailing list,

And I agree that providing a list of things that lawyers have already done 
for us is a very reasonable basis for an RFP about what we expect lawyers to 
do for us,

But I do think posting draft text does allow you to say "and the community 
saw this" if you guys get any pushback at all...

Thanks,

Spencer

> Bob,
>
> On 2011-02-22 08:23, Bob Hinden wrote:
>> John,
>>
>> Support for the xml2rfc tool was discussed on the IETF mail
>> list when Marshall Rose indicated he could no longer support
>> the tool.  Several people volunteered to maintain the tool,
>> and they recommended the it be rewritten.  That
>> recommendation plus the realization that this tool had become
>> critical to IETF operations resulted in the IAOC deciding to
>> issue a public RFP for a rewrite.
>>
>> The Statement of Work in the xml2rfc RFP was reviewed and
>> modified by the people on the tool-development list.  You can
>> read the discussion at:
>>
>> http://www.ietf.org/mail-archive/web/tools-development/current/maillist.html
>>
>> There was an active discussion that resulted in many changes
>> from what was first proposed.  While this wasn't the whole
>> community I think it a good representation of the people who
>> are interested in the xml2rfc tool.  I will send you the list
>> members off line.  Also, we will use a subset of this group
>> to review the bids.
>
> I think the tools development list was a good venue for the
> detailed discussion. Was the process mentioned on tools-discuss
> too? (I dropped off that one a while back, due to lack of
> cycles, but it does seems the obvious place, not to mention the
> xml2rfc list, where I don't recall it being mentioned).
>
>>
>> The legal services RFP was developed inside the IAOC/Trust.
>> To be honest, I didn't see very much value in doing a
>> community review for this.  We will consider it in the
>> future.  I do note that this work was previously done without
>> a public RFP (dating back to when Wilmer-Hale was providing
>> the service) so I think this is a better process than what
>> was used earlier.
>>
>> In the future, we will strive to give more notice to the
>> community on planned RFPs.
>
> I think that is appropriate, given the comments in BCP 101
> about transparency. But I agree that for legal services, our
> community doesn't particularly have the skills to wordsmith
> an RFP.
>
>   Brian
>
>
>>
>> Bob
>>
>> p.s. I will forward your specific comments to tools-discuss.
>>
>>
>> On Feb 19, 2011, at 8:49 AM, John C Klensin wrote:
>>
>>> Hi.
>>>
>>> This is not an attempt to derail either of these RFPs, nor
>>> is it a formal appeal (request for review).  However, these
>>> two RFPs raise an issue that may be worth some
>>> consideration.
>>>
>>> The clear intent of the discussions leading up to RFC 4071/
>>> BCP 101, and some of text in that document, was that the
>>> IASA was to act with maximum transparency to the community
>>> and openness to community comment.   It is especially
>>> important that substantive decisions be open for community
>>> review and discussion before they are made because,
>>> especially for those that are eventually represented by
>>> contracts, there is no mechanism for review later.
>>>
>>> IASA has recently issued two RFPs -- for legal services and
>>> for a reprogrammed version of xml2rfc -- with no advance
>>> indication to the community (at least that I can find) that
>>> they were coming or opportunity for the community to review
>>> draft provisions.  The clear expectation is that proposals
>>> will be submitted (on a fairly short timeframe) and that
>>> the IAD and IAOC will do whatever they do to evaluate the
>>> proposals and establish contracts.   I don't know whether
>>> that is harmful in these particular cases, but I don't
>>> believe it is how the community had intended that things be
>>> done.
>>>
>>> FWIW, community discussion might have improved at least the
>>>  XML2RFC one -- either the details of the RFP or community
>>> confidence that it addresses/includes the right
>>> specifications. For example, of the very large number of
>>> extensions or additions that have bee requested over the
>>> years, the RFP selects two (explicit line breaks in titles)
>>> and alternate anchors for citations/references) but ignores
>>> the others.   I know that the ability to easily index and
>>> cross-reference items in bulleted lists, to easily generate
>>> numbers for ABNF productions (rules) and build an index of
>>> productions, to have indexing reflect section (and other
>>> subdivision) numbers rather than page numbers (as various
>>> RFC style guides have required for years and that becomes
>>> particularly important as people contemplate non-paginated
>>> output formats), the ability to properly reference books
>>> and journal articles without resorting to odd tricks
>>> involving seriesInfo, and better handling of widows and
>>> orphans (especially with regard to section title-text and
>>> lists with undented headings top my personal list, but
>>> there are certainly others.
>>>
>>> In addition, one of the two extensions that was specified
>>> involves the addition of a new format-specific directive
>>> that is exclusive to xml2rfc, not the DTD/Schema, thereby
>>> making equivalent processing by other, XML-standard,
>>> processors problematic and violating the fundamental
>>> principle that generic markup does not specify formatting.
>>> Perhaps community members might have been able to propose
>>> design models that are more friendly to XML principles and
>>> other tools (even I can think of one or two).
>>>
>>> The two extensions that were chosen may be the most
>>> important ones, and there may be a reason why two
>>> extensions were chosen rather than one or five.  But it
>>> seems to me that the community, and perhaps even the text
>>> of the RFP and the proposals that will arrive in response,
>>> would have benefited from some opportunity for review and
>>> discussion.
>>>
>>> Can we at least agree to more openness about draft RFP
>>> contents in the future?  Or get an explanation from the
>>> IAOC as to why the procedural model now seems to include
>>> issuance of RFPs without any opportunity for community
>>> review of their substantive provisions?
>>>
>>> thanks, john
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________ IAOC
>>> mailing list IAOC@ietf.org
>>> https://www.ietf.org/mailman/listinfo/iaoc
>>
>> _______________________________________________ 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  Mon Feb 21 13:29:35 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAAB43A7161 for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 13:29:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id voQx8L3HyYFU for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 13:29:31 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id E865B3A7180 for <ietf@ietf.org>; Mon, 21 Feb 2011 13:29:30 -0800 (PST)
Received: (qmail 17735 invoked by uid 399); 21 Feb 2011 21:30:09 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 21 Feb 2011 21:30:09 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D62D960.3040406@dougbarton.us>
Date: Mon, 21 Feb 2011 13:30:08 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110129 Thunderbird/3.1.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>	<54C48986-B211-462C-B942-247886122AF2@gmail.com> <DFA887BC0886F81AADFA0390@PST.JCK.COM>
In-Reply-To: <DFA887BC0886F81AADFA0390@PST.JCK.COM>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 21:29:35 -0000

On 02/21/2011 12:20, John C Klensin wrote:
> Perhaps I'm the only member of the community who cares any more.

Nope, I'll give a +1 to that as well.

I don't have anything intelligent to say about either RFP, but I'm more 
concerned about the fact that the IAOC thought that releasing them 
without wider community review was something that the community would 
accept and/or tolerate. I first grew concerned about this with the 
"network registration" donnybrook at the China IETF. I didn't speak up 
then because I wasn't there, didn't know the details, and figured that 
based on the response from both the community and the IAOC that it was a 
lesson learned.

For future reference, erring on the side of more communication with the 
community is probably the right way to go, regardless of how 
inconvenient it may be.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	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  Mon Feb 21 16:42:58 2011
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AB283A67AE for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 16:42:58 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TXFxYHLYEx2S for <ietf@core3.amsl.com>; Mon, 21 Feb 2011 16:42:57 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 69FA33A67AA for <ietf@ietf.org>; Mon, 21 Feb 2011 16:42:57 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NY3FPO2BN400MIUA@mauve.mrochek.com> for ietf@ietf.org; Mon, 21 Feb 2011 16:43:37 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NY0802NCW000H4Y3@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 21 Feb 2011 16:43:33 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NY3FPMHG2C00H4Y3@mauve.mrochek.com>
Date: Mon, 21 Feb 2011 16:43:21 -0800 (PST)
Subject: Re: [IAOC] xml2rfc and legal services RFPs
In-reply-to: "Your message dated Mon, 21 Feb 2011 13:30:08 -0800" <4D62D960.3040406@dougbarton.us>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <E23665735D529B2C8CC3A393@PST.JCK.COM> <54C48986-B211-462C-B942-247886122AF2@gmail.com> <DFA887BC0886F81AADFA0390@PST.JCK.COM> <4D62D960.3040406@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1298331760; i=@mrochek.com; bh=KBzo0/l3rN+u7QXcYSMvgsfRMCe76AnexfVrMl+9mn0=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=FMAubvls9Hyb8lKtppIAmL3kekA7l21d2qvdgaVHep7WE/9BhC8JJZ5kJrJWm4C01 XftxY8N+f62cr7ZIMLkA5XHMt08ZcsfJDbz0GJMUL+s+7QZSOcoar0Yjb7ff4fQIjW W/XAlPUD8qo/olpMMG/7/Fouppc9rQ+YZDRXrWzk=
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 00:42:58 -0000

> On 02/21/2011 12:20, John C Klensin wrote:
> > Perhaps I'm the only member of the community who cares any more.

> Nope, I'll give a +1 to that as well.

> I don't have anything intelligent to say about either RFP, but I'm more
> concerned about the fact that the IAOC thought that releasing them
> without wider community review was something that the community would
> accept and/or tolerate. I first grew concerned about this with the
> "network registration" donnybrook at the China IETF. I didn't speak up
> then because I wasn't there, didn't know the details, and figured that
> based on the response from both the community and the IAOC that it was a
> lesson learned.

> For future reference, erring on the side of more communication with the
> community is probably the right way to go, regardless of how
> inconvenient it may be.

+1

				Ned

From dworley@avaya.com  Tue Feb 22 07:29:05 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A965F3A690D; Tue, 22 Feb 2011 07:29: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6X0oLhnOowk8; Tue, 22 Feb 2011 07:29:03 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id B5D973A68F8; Tue, 22 Feb 2011 07:29:02 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAM5kY02HCzI1/2dsb2JhbACmRHOkTQKZIYVeBIUNiluCdg
X-IronPort-AV: E=Sophos;i="4.62,206,1297054800"; d="scan'208";a="60232557"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 22 Feb 2011 10:29:22 -0500
X-IronPort-AV: E=Sophos;i="4.62,206,1297054800"; d="scan'208";a="603642523"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 22 Feb 2011 10:28:46 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 22 Feb 2011 10:28:45 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Bob Hinden <bob.hinden@gmail.com>, John C Klensin <john-ietf@jck.com>
Date: Tue, 22 Feb 2011 10:25:11 -0500
Subject: RE: [IAOC] xml2rfc and legal services RFPs
Thread-Topic: [IAOC] xml2rfc and legal services RFPs
Thread-Index: AcvR/N3M7MWLIwFJQBWIndlqeHZYOQAp9Rut
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com>
In-Reply-To: <54C48986-B211-462C-B942-247886122AF2@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: "iaoc@ietf.org" <iaoc@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 15:29:05 -0000

> From: ietf-bounces@ietf.org On Behalf Of Bob Hinden [bob.hinden@gmail.com=
]
>=20
> The Statement of Work in the xml2rfc RFP was reviewed and modified
> by the people on the tool-development list.  [...]
>=20
> There was an active discussion that resulted in many changes from
> what was first proposed.  While this wasn't the whole community I
> think it a good representation of the people who are interested in
> the xml2rfc tool.

Yeah, and the features list for the next version of MS Word will be
decided by polling the MS Word developers.

You need to poll the *users* of the tool, not the *developers* of the
tool, to find out what is needed.

Dale

From julian.reschke@gmx.de  Tue Feb 22 07:42:12 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B39603A6915 for <ietf@core3.amsl.com>; Tue, 22 Feb 2011 07:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.938
X-Spam-Level: 
X-Spam-Status: No, score=-103.938 tagged_above=-999 required=5 tests=[AWL=-1.339, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJ9-NoJKtGOy for <ietf@core3.amsl.com>; Tue, 22 Feb 2011 07:42:11 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 659153A68F8 for <ietf@ietf.org>; Tue, 22 Feb 2011 07:42:11 -0800 (PST)
Received: (qmail invoked by alias); 22 Feb 2011 15:42:55 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.134]) [217.91.35.233] by mail.gmx.net (mp022) with SMTP; 22 Feb 2011 16:42:55 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19ZESxwqjJZZRhCheJXSXwxw3cK2ETSp4bgs3vcmf C+Ejdh3fU7XlCN
Message-ID: <4D63D978.4050808@gmx.de>
Date: Tue, 22 Feb 2011 16:42:48 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: John C Klensin <john-ietf@jck.com>, "iaoc@ietf.org" <iaoc@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 15:42:12 -0000

On 22.02.2011 16:25, Worley, Dale R (Dale) wrote:
>> From: ietf-bounces@ietf.org On Behalf Of Bob Hinden [bob.hinden@gmail.com]
>>
>> The Statement of Work in the xml2rfc RFP was reviewed and modified
>> by the people on the tool-development list.  [...]
>>
>> There was an active discussion that resulted in many changes from
>> what was first proposed.  While this wasn't the whole community I
>> think it a good representation of the people who are interested in
>> the xml2rfc tool.
>
> Yeah, and the features list for the next version of MS Word will be
> decided by polling the MS Word developers.
>
> You need to poll the *users* of the tool, not the *developers* of the
> tool, to find out what is needed.
> ...

Both, actually.

That being said: do you have specific suggestions? How about posting 
them to the xml2rfc mailing list?

Best regards, Julian

From sambasiva.manchili@nexustelecom.com  Sat Feb 19 09:14:39 2011
Return-Path: <sambasiva.manchili@nexustelecom.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 321533A6F83 for <ietf@core3.amsl.com>; Sat, 19 Feb 2011 09:14:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_42=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgftALZSjAnJ for <ietf@core3.amsl.com>; Sat, 19 Feb 2011 09:14:38 -0800 (PST)
Received: from typhon.nexustelecom.com (typhon.nexustelecom.com [212.203.104.229]) by core3.amsl.com (Postfix) with ESMTP id 334B73A6F7A for <ietf@ietf.org>; Sat, 19 Feb 2011 09:14:38 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.62,192,1297033200";  d="scan'208";a="2344879"
Received: from unknown (HELO hermes.nexustelecom.com) ([172.29.1.4]) by typhon.nexustelecom.com with ESMTP; 19 Feb 2011 18:15:14 +0100
Received: from hermes.nexustelecom.com (localhost [127.0.0.1]) by hermes.nexustelecom.com (Postfix) with ESMTP id 6BC5E159F64 for <ietf@ietf.org>; Sat, 19 Feb 2011 18:15:14 +0100 (CET)
Received: from poseidon.nexus-ag.com (poseidon.nexus-ag.com [172.29.2.111]) by hermes.nexustelecom.com (Postfix) with ESMTP id 6DB03159F63 for <ietf@ietf.org>; Sat, 19 Feb 2011 18:14:58 +0100 (CET)
Received: from poseidon.nexus-ag.com ([172.29.2.111]) by poseidon.nexus-ag.com ([172.29.2.111]) with mapi; Sat, 19 Feb 2011 18:14:58 +0100
From: Sambasiva Rao Manchili <sambasiva.manchili@nexustelecom.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 19 Feb 2011 18:13:10 +0100
Subject: FW: RTP Timestamping in Control messages of IuCS interface.
Thread-Topic: RTP Timestamping in Control messages of IuCS interface.
Thread-Index: AQHL0FeK//SQUrZ5dEaOQI5XewDSTpQJD+JQ
Message-ID: <509DA52866E38F47878413CF102D751F7099C582BE@poseidon.nexus-ag.com>
References: <509DA52866E38F47878413CF102D751F7099C582BD@poseidon.nexus-ag.com>
In-Reply-To: <509DA52866E38F47878413CF102D751F7099C582BD@poseidon.nexus-ag.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TBoneOriginalFrom: Sambasiva Rao Manchili <sambasiva.manchili@nexustelecom.com>
X-TBoneOriginalTo: "ietf@ietf.org" <ietf@ietf.org>
X-TBoneDomainSigned: false
X-Mailman-Approved-At: Tue, 22 Feb 2011 07:42:33 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2011 17:14:39 -0000

I am forwarding this mail as the mail that I sent previously are on hold fo=
r its approval from different groups. Please do the needful.
Thank you.
________________________________________
From: Sambasiva Rao Manchili
Sent: Saturday, February 19, 2011 6:07 PM
To: tsvwg@ietf.org; payload@ietf.org; avtcore@ietf.org; codec@ietf.org
Cc: Antonio Gambin; Markus Locher; Ralf K=FChl
Subject: RTP Timestamping in Control messages of IuCS interface.

Hallo,

Can some one in IETF list, please help me to clarify the point w.r.t the Ti=
me stamping in RTP header for Audio Stream AMR 5.9.
I hope I am addressing to right group.

Our implementation of RTP is not accepting the two control messages belongi=
ng to the UPP(User plane protocol above RTP) if the two consecutive control=
 packets arrived has same time stamp with different sequence numbers.
The two control messages are UPP_INIT_ACK and Rate Control Message which be=
longs to UPP layer on IuCS user plane stack.
Our implementation expects the time stamp of second packet to be 320ms grea=
ter than the time stamp arrived in 1st Control message of RTP header.

Our counter part RTP stack says their implementation is right and can have =
the same time stamp in the RTP header of these control messages.

 RFC 3350 tells about equal timestamps for Video stream belonging to same f=
rame, but does not specifically tell about the control messages of its uppe=
r layer.
We have read the RFC 3550 , section 5.1 does NOT prevent RTP packets
from having equal timestamps but rather explicitly allows for it:

      Several consecutive RTP packets will have equal timestamps if
      they are (logically) generated at once, e.g., belong to the same
      video frame.  Consecutive RTP packets MAY contain timestamps that
      are not monotonic if the data is not transmitted in the order it
      was sampled, as in the case of MPEG interpolated video frames.
      (The sequence numbers of the packets as transmitted will still be
      monotonic.)

May I kindly ask the RTP experts in Audio Stream area(or specific to IuCS )=
 can please clarify me.

Thank you very much for your time.

Best Regads,
Samba.

This email and any attachment may contain confidential information which is=
 intended for use only by the addressee(s) named above. If you received thi=
s email by mistake, please notify the sender immediately, and delete the em=
ail from your system. You are prohibited from copying, disseminating or oth=
erwise using the email or any attachment.


From Even.roni@huawei.com  Sun Feb 20 05:49:15 2011
Return-Path: <Even.roni@huawei.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A5753A6DD8; Sun, 20 Feb 2011 05:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.428
X-Spam-Level: 
X-Spam-Status: No, score=-103.428 tagged_above=-999 required=5 tests=[AWL=1.066, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5IK0DreG4D8I; Sun, 20 Feb 2011 05:49:13 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 7D7553A6C82; Sun, 20 Feb 2011 05:49:13 -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 <0LGX00H5V52TO7@szxga03-in.huawei.com>; Sun, 20 Feb 2011 21:49:41 +0800 (CST)
Received: from 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 <0LGX00B5652TUH@szxga03-in.huawei.com>; Sun, 20 Feb 2011 21:49:41 +0800 (CST)
Received: from windows8d787f9 (bzq-79-178-22-235.red.bezeqint.net [79.178.22.235]) by szxml12-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LGX0057L52MT8@szxml12-in.huawei.com>; Sun, 20 Feb 2011 21:49:41 +0800 (CST)
Date: Sun, 20 Feb 2011 15:44:55 +0200
From: Roni Even <Even.roni@huawei.com>
Subject: Gen-ART LC review of draft-ietf-morg-multimailbox-search-06
To: gen-art@ietf.org, draft-ietf-morg-multimailbox-search.all@tools.ietf.org
Message-id: <00d101cbd104$6069c550$213d4ff0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_aAKQzN3uL9P/w7sARYRvFg)"
Content-language: en-us
Thread-index: AcvRBFqeCy3nGtCiSFqsEK2apBti3Q==
X-Mailman-Approved-At: Tue, 22 Feb 2011 07:42:33 -0800
Cc: 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Feb 2011 13:49:15 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_aAKQzN3uL9P/w7sARYRvFg)
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-morg-multimailbox-search-06

Reviewer: Roni Even

Review Date:2011-2-20

IETF LC End Date: 2011-2-28

IESG Telechat date:

 

Summary: This draft is ready for publication as Experimental  RFC.

 

Major issues:

None

 

Minor issues:

None

 

Nits/editorial comments:

None

 


--Boundary_(ID_aAKQzN3uL9P/w7sARYRvFg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at &lt;<a href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Please resolve these comments along with any other Last Call comments you may receive.<o:p></o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-morg-multimailbox-search-06<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;fo
 nt-famil
>Reviewer: Roni Even<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review Date:2011&#8211;2&#8211;20<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC End Date: 2011&#8211;2&#8211;28<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG Telechat date:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This draft is ready for publication as Experimental&nbsp; RFC.<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major issues:<o:p></o:p></
 span></p
pan style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>None<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>None<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Nits/editorial comments:<o:p></o:p></span></p><p class=MsoPlainText><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>None<o:p></o:p></span></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--Boundary_(ID_aAKQzN3uL9P/w7sARYRvFg)--

From christopher.morrow@gmail.com  Mon Feb 21 11:14:41 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6F403A6F5C; Mon, 21 Feb 2011 11:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.179
X-Spam-Level: 
X-Spam-Status: No, score=-103.179 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCRSFuJdeXGB; Mon, 21 Feb 2011 11:14:41 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 7A5F23A6F42; Mon, 21 Feb 2011 11:14:40 -0800 (PST)
Received: by wwa36 with SMTP id 36so6590282wwa.13 for <multiple recipients>; Mon, 21 Feb 2011 11:15:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=5MuhdJ+F83ngQ7OV8qVoKLa/utNDp/w9ujRT8No1UUs=; b=YrxmoTM3JH12WxhoA7OFr/fDkXMiwhh6z0iLWKVmi0lI9v4y5FatTXzpMtiXTO7QTc dePh98C5ntuentKx223rmIYvzkgd2mv5UM68PUu611p2oJf4cYNhg8xLEdSDPnpUiJ/u LqDRuYE49tnqrGMLvUAyyOClxiAxIBdAV+KGE=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=T/9hBKs2SScAjuuZUCcLtLpQYdKjzpA/let5kfErtSAFmy4696/hAFf6E9kBK4uE7g MI5vgHlfbUFGpf3RlAwiMtRM7kfkFd7Y2E2Xvru20gsRSQIN9w+j8X5lyRs3t6t5oawI H+XUNDKzoGthmYpCG36Sxyf1l0tUkqCwowGW8=
MIME-Version: 1.0
Received: by 10.216.18.204 with SMTP id l54mr1487836wel.99.1298315720728; Mon, 21 Feb 2011 11:15:20 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.216.1.197 with HTTP; Mon, 21 Feb 2011 11:15:20 -0800 (PST)
In-Reply-To: <000c01cbd1e3$c1036e40$4001a8c0@gateway.2wire.net>
References: <000c01cbd1e3$c1036e40$4001a8c0@gateway.2wire.net>
Date: Mon, 21 Feb 2011 14:15:20 -0500
X-Google-Sender-Auth: RIInaIxgoLZeRM5VT2KMSPiwODM
Message-ID: <AANLkTin36cA5r-Jr-j7-YqMrOR4_cDEystZFV7Eq-USf@mail.gmail.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructure to
From: Christopher Morrow <morrowc.lists@gmail.com>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 22 Feb 2011 07:42:33 -0800
Cc: sidr@ietf.org, ietf <ietf@ietf.org>, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 19:14:42 -0000

(not speaking for the authors, just observing some... also not
speaking as a co-chair)

On Mon, Feb 21, 2011 at 11:23 AM, t.petch <daedulus@btconnect.com> wrote:
> I find this I-D problematic. =A0The subject matter is of crucial importan=
ce,
> comparable to, or perhaps more important than, IPv6, yet this I-D is not
> an easy read and there should be one such somewhere.
>

I thought there was to be an overview doc as well produced, with the
goal being to lay out the basic parts referring to the other drafts
for further info/expansion.

> sidr has produced an awesome collection of I-Ds (some now obsolete) but i=
t is
> not obvious, short of spending a few months in the archives, how they fit
> together. =A0Other major projects - snmp for example - produced an Introd=
uction,
> acting as a starting point and a road map to the other I-Ds and I think t=
hat
> that should be a prerequisite for sidr. =A0This I-D is not it (even if it=
 could
> be); its Normative
> References include a further 80 pages of sidr I-Ds!
>
> One small example. =A0The I-Ds have several references to RPKI and indeed=
, that
> appears in -arch; but it first appears on page 8 and is not even expanded=
, let

eh.. that's a nit that someone should file... "hey, you can't use an
acronym for the first time without actually expanding it properly!"

Can you cite the proper para/page/section on this so the authors can fix it=
?

-Chris

> alone explained. =A0Of course you can turn to Wikipedia and you find a cl=
ear
> explanation of what RPKI is but you should not need Wikipedia to understa=
nd
> something as important as sidr. =A0This I-D seems to be written to be und=
erstood
> by those who understand it:-(
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "The IESG" <iesg-secretary at ietf.org>
> To: "IETF-Announce" <ietf-announce at ietf.org>
> Cc: <sidr@ietf.org>
> Sent: Monday, February 07, 2011 5:14 PM
> Subject: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructu=
re to
>
>
>>
>> The IESG has received a request from the Secure Inter-Domain Routing WG
>> (sidr) to consider the following document:
>> - 'An Infrastructure to Support Secure Internet Routing'
>> =A0 <draft-ietf-sidr-arch-11.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 at ietf.org mailing lists by 2011-02-21. Exceptionally, comments ma=
y be
>> sent to iesg at ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>>
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>> /ipr/1204/
>>
>
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>

From christopher.morrow@gmail.com  Mon Feb 21 11:17:03 2011
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A310B3A7138; Mon, 21 Feb 2011 11:17:03 -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=-0.165, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42u4d1yJvDzF; Mon, 21 Feb 2011 11:17:02 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 1B97F3A6F5C; Mon, 21 Feb 2011 11:17:01 -0800 (PST)
Received: by wwa36 with SMTP id 36so6592731wwa.13 for <multiple recipients>; Mon, 21 Feb 2011 11:17:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=HIo8r3Yct3p7v3LMpDGXv1xOpty0XLnx/+h6PU6odW8=; b=hcT0RPc6inhq4gxlu2kMIa/Tr2h+sgZWJ9DW/XH0YljaDiv3nIypR0Yoyz4b4VR9jH NqGKNRdnrpzU1N9PMNNYkybppNS0c+WoDyOaAGewrzP1n8lm5EFEOj92Lhd6sHs/NIJD AqVl6Lk09tABw1jhGGJZj6D71z0O2INQ7CV9s=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=bnKge6oXCO06Annka6o8LWv/o9ba/g7CMD2CUCRWml8/IPhYVw30jWzRlbydRJsqLm oLMqL2d/Plpfs9e56DxM3y4FgRI8s32LjCaT3YUZwc7HqqHaldcgg38WhSoOPBHLXdwt hOQHqKnSlGgNMMxD5jFcBt/CbiAVesE0geYr4=
MIME-Version: 1.0
Received: by 10.216.155.1 with SMTP id i1mr2534051wek.0.1298315862791; Mon, 21 Feb 2011 11:17:42 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.216.1.197 with HTTP; Mon, 21 Feb 2011 11:17:42 -0800 (PST)
In-Reply-To: <AANLkTin36cA5r-Jr-j7-YqMrOR4_cDEystZFV7Eq-USf@mail.gmail.com>
References: <000c01cbd1e3$c1036e40$4001a8c0@gateway.2wire.net> <AANLkTin36cA5r-Jr-j7-YqMrOR4_cDEystZFV7Eq-USf@mail.gmail.com>
Date: Mon, 21 Feb 2011 14:17:42 -0500
X-Google-Sender-Auth: efSXlYI4g-EtuSlEptcSwLJT8Qs
Message-ID: <AANLkTintL=cMHkJ9saujy8FmaheNqonPERfJdhqJeiGZ@mail.gmail.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastructure to
From: Christopher Morrow <morrowc.lists@gmail.com>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 22 Feb 2011 07:42:33 -0800
Cc: sidr@ietf.org, ietf <ietf@ietf.org>, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2011 19:17:03 -0000

On Mon, Feb 21, 2011 at 2:15 PM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
> (not speaking for the authors, just observing some... also not
> speaking as a co-chair)
>
> On Mon, Feb 21, 2011 at 11:23 AM, t.petch <daedulus@btconnect.com> wrote:
>> I find this I-D problematic. =A0The subject matter is of crucial importa=
nce,
>> comparable to, or perhaps more important than, IPv6, yet this I-D is not
>> an easy read and there should be one such somewhere.
>>
>
> I thought there was to be an overview doc as well produced, with the
> goal being to lay out the basic parts referring to the other drafts
> for further info/expansion.

oh, I mentioned the overview in the note about rechartering:

"The SIDR working group is charged with the following goals and
milestones:
ID Date      Pub Date
Mar 2011   Jan 2012  An overview of the RPKI and BGP Protocol changes
required for origin and path validation"

-chris

>> sidr has produced an awesome collection of I-Ds (some now obsolete) but =
it is
>> not obvious, short of spending a few months in the archives, how they fi=
t
>> together. =A0Other major projects - snmp for example - produced an Intro=
duction,
>> acting as a starting point and a road map to the other I-Ds and I think =
that
>> that should be a prerequisite for sidr. =A0This I-D is not it (even if i=
t could
>> be); its Normative
>> References include a further 80 pages of sidr I-Ds!
>>
>> One small example. =A0The I-Ds have several references to RPKI and indee=
d, that
>> appears in -arch; but it first appears on page 8 and is not even expande=
d, let
>
> eh.. that's a nit that someone should file... "hey, you can't use an
> acronym for the first time without actually expanding it properly!"
>
> Can you cite the proper para/page/section on this so the authors can fix =
it?
>
> -Chris
>
>> alone explained. =A0Of course you can turn to Wikipedia and you find a c=
lear
>> explanation of what RPKI is but you should not need Wikipedia to underst=
and
>> something as important as sidr. =A0This I-D seems to be written to be un=
derstood
>> by those who understand it:-(
>>
>> Tom Petch
>>
>>
>> ----- Original Message -----
>> From: "The IESG" <iesg-secretary at ietf.org>
>> To: "IETF-Announce" <ietf-announce at ietf.org>
>> Cc: <sidr@ietf.org>
>> Sent: Monday, February 07, 2011 5:14 PM
>> Subject: [sidr] Last Call: <draft-ietf-sidr-arch-11.txt> (An Infrastruct=
ure to
>>
>>
>>>
>>> The IESG has received a request from the Secure Inter-Domain Routing WG
>>> (sidr) to consider the following document:
>>> - 'An Infrastructure to Support Secure Internet Routing'
>>> =A0 <draft-ietf-sidr-arch-11.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 at ietf.org mailing lists by 2011-02-21. Exceptionally, comments m=
ay be
>>> sent to iesg at ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-sidr-arch/
>>>
>>>
>>>
>>> The following IPR Declarations may be related to this I-D:
>>>
>>> /ipr/1204/
>>>
>>
>> _______________________________________________
>> sidr mailing list
>> sidr@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidr
>>
>

From housley@vigilsec.com  Tue Feb 22 07:53:17 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8DE83A692B; Tue, 22 Feb 2011 07:53:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xF9Q5ECZuYKG; Tue, 22 Feb 2011 07:53:16 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id C528A3A692C; Tue, 22 Feb 2011 07:53:16 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 1DF9A9A473A; Tue, 22 Feb 2011 10:54:24 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 2d4vkmUHqAXN; Tue, 22 Feb 2011 10:53:31 -0500 (EST)
Received: from [192.168.2.105] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 8F8549A4725; Tue, 22 Feb 2011 10:54:23 -0500 (EST)
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>
Date: Tue, 22 Feb 2011 10:54:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1082)
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 15:53:17 -0000

>> The Statement of Work in the xml2rfc RFP was reviewed and modified
>> by the people on the tool-development list.  [...]
>>=20
>> There was an active discussion that resulted in many changes from
>> what was first proposed.  While this wasn't the whole community I
>> think it a good representation of the people who are interested in
>> the xml2rfc tool.
>=20
> Yeah, and the features list for the next version of MS Word will be
> decided by polling the MS Word developers.
>=20
> You need to poll the *users* of the tool, not the *developers* of the
> tool, to find out what is needed.

The xml2rfc tool was declared critical to the IETF because of the use by =
the RFC Production Center.  The volunteers that stepped forward to =
maintain the code when Marshall Rose declared that he was finished =
recommended the rewrite.  Therefore, the things that the enhancements =
proposed by the RFC Production Center have priority, but the entire =
community will benefit from a tools that is easier to maintain and =
enhance.

Russ=

From dworley@avaya.com  Tue Feb 22 07:56:06 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C8BB3A68FA; Tue, 22 Feb 2011 07:56:06 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4QdKiOVt1Q7; Tue, 22 Feb 2011 07:56:04 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 24D4E3A6892; Tue, 22 Feb 2011 07:56:02 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANdrY03GmAcF/2dsb2JhbACmHnOkSgKZJoVeBIUNils
X-IronPort-AV: E=Sophos;i="4.62,207,1297054800"; d="scan'208";a="60237681"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 22 Feb 2011 10:56:13 -0500
X-IronPort-AV: E=Sophos;i="4.62,207,1297054800"; d="scan'208";a="585222981"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 22 Feb 2011 10:56:13 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Tue, 22 Feb 2011 10:56:12 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Russ Housley <housley@vigilsec.com>
Date: Tue, 22 Feb 2011 10:55:41 -0500
Subject: RE: [IAOC] xml2rfc and legal services RFPs
Thread-Topic: [IAOC] xml2rfc and legal services RFPs
Thread-Index: AcvSqM7WlgdOGwykTrSryGHI4lA7RQAACXVF
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>
In-Reply-To: <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.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: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 15:56:06 -0000

________________________________________
From: Russ Housley [housley@vigilsec.com]

The xml2rfc tool was declared critical to the IETF because of the use by th=
e RFC Production Center.
________________________________________

Not because a large fraction of the draft authors use it?

Dale

From housley@vigilsec.com  Tue Feb 22 08:05:15 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 134743A691D; Tue, 22 Feb 2011 08:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2+bQxDraSZW; Tue, 22 Feb 2011 08:05:14 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 327783A689B; Tue, 22 Feb 2011 08:05:14 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id EA2FBF24022; Tue, 22 Feb 2011 11:06:27 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id m553sS0XeR9d; Tue, 22 Feb 2011 11:05:18 -0500 (EST)
Received: from [192.168.2.105] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5BC13F2401D; Tue, 22 Feb 2011 11:06:27 -0500 (EST)
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com>
Date: Tue, 22 Feb 2011 11:05:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1082)
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 16:05:15 -0000

Dale:

> The xml2rfc tool was declared critical to the IETF because of the use =
by the RFC Production Center.
> ________________________________________
>=20
> Not because a large fraction of the draft authors use it?

Yes and no.  If so many authors we not using it, then xml2rfc would not =
be important to the RFC Production Center.  There are many tools used by =
I-D authors, including nroff/troff/groff, NroffEdit, MS Word templates, =
LaTex, and a plethora of editors.  The IETF cannot take on every tool =
that seems popular.  In this case, the RFC Production Center will become =
more effective, and that represents a return on the investment, and it =
will also help many I-D authors.

Russ=

From dhc@dcrocker.net  Tue Feb 22 08:15:19 2011
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B3563A690F; Tue, 22 Feb 2011 08:15:19 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEQO3XimHj1L; Tue, 22 Feb 2011 08:15:18 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 30E3C3A68E6; Tue, 22 Feb 2011 08:15:18 -0800 (PST)
Received: from [172.16.1.101] (ip-207-190-24-002.ithink.com [207.190.24.2] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p1MGFqcw013775 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2011 08:15:58 -0800
Message-ID: <4D63E136.5070805@dcrocker.net>
Date: Tue, 22 Feb 2011 11:15:50 -0500
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com> <708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.com>
In-Reply-To: <708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.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, 22 Feb 2011 08:15:59 -0800 (PST)
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 16:15:19 -0000

On 2/22/2011 11:05 AM, Russ Housley wrote:
>  There are many tools used by I-D
> authors, including nroff/troff/groff, NroffEdit, MS Word templates, LaTex,
> and a plethora of editors.  The IETF cannot take on every tool that seems
> popular.


Isn't the statistic of xml2rfc use somewhere around 50-60%?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From housley@vigilsec.com  Tue Feb 22 08:17:21 2011
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CBE43A6924; Tue, 22 Feb 2011 08:17:21 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVpokS8OJUb9; Tue, 22 Feb 2011 08:17:20 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id 85B8D3A68EE; Tue, 22 Feb 2011 08:17:20 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 88E979A4726; Tue, 22 Feb 2011 11:18:09 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id QanifDldRAok; Tue, 22 Feb 2011 11:17:58 -0500 (EST)
Received: from [192.168.2.105] (pool-71-178-218-117.washdc.fios.verizon.net [71.178.218.117]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id F077C9A4725; Tue, 22 Feb 2011 11:18:08 -0500 (EST)
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4D63E136.5070805@dcrocker.net>
Date: Tue, 22 Feb 2011 11:18:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <95586EBA-DB21-4D1F-A271-776C6FE4D27B@vigilsec.com>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com> <708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.com> <4D63E136.5070805@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1082)
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 16:17:21 -0000

>> There are many tools used by I-D
>> authors, including nroff/troff/groff, NroffEdit, MS Word templates, =
LaTex,
>> and a plethora of editors.  The IETF cannot take on every tool that =
seems
>> popular.
>=20
>=20
> Isn't the statistic of xml2rfc use somewhere around 50-60%?

Roughly half.  Again, that is why there is a value to the RFC Production =
Center.

Russ


From ole@cisco.com  Tue Feb 22 09:32:55 2011
Return-Path: <ole@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A5E73A6940; Tue, 22 Feb 2011 09:32:55 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtBqavU-oFyb; Tue, 22 Feb 2011 09:32:54 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 0A5A63A694D; Tue, 22 Feb 2011 09:32:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1173; q=dns/txt; s=iport; t=1298396019; x=1299605619; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=qbxOalT2M6suEYj+Y6Q7i0lnxJuIwUIz+MCvY6QwexQ=; b=CVc0+eS55AdN4dC7T3hl3vwJ/co8/oq5nchZIDQhoNMFEMuWGBCfOTxB PrrPfDZpIDrlbPRfWBpPl3zl6Vr+Wl+GJMku3Y3RAuT7c+M+GLLO/bmka sTJjgmQ5Do+70UWiYWem/uqLMfRIzVjESH9zhGYLkBS7rBh72VtnZXkw4 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGGCY02rR7Ht/2dsb2JhbACmF3OiVYJiDgGYZoMXgkcEhQ2HBoM7
X-IronPort-AV: E=Sophos;i="4.62,207,1297036800"; d="scan'208";a="333547229"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 22 Feb 2011 17:33:34 +0000
Received: from [10.24.17.59] ([10.24.17.59]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1MHXYar024786; Tue, 22 Feb 2011 17:33:34 GMT
Date: Tue, 22 Feb 2011 09:33:33 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
In-Reply-To: <4D62D960.3040406@dougbarton.us>
Message-ID: <alpine.OSX.2.01.1102220928500.33818@macpro.local>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM> <54C48986-B211-462C-B942-247886122AF2@gmail.com> <DFA887BC0886F81AADFA0390@PST.JCK.COM> <4D62D960.3040406@dougbarton.us>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 17:32:55 -0000

On Mon, 21 Feb 2011, Doug Barton wrote:

> I don't have anything intelligent to say about either RFP, but I'm 
> more concerned about the fact that the IAOC thought that releasing 
> them without wider community review was something that the community 
> would accept and/or tolerate. I first grew concerned about this with 
> the "network registration" donnybrook at the China IETF. I didn't 
> speak up then because I wasn't there, didn't know the details, and 
> figured that based on the response from both the community and the 
> IAOC that it was a lesson learned.

For the record: THe network registration was announced BEFORE 
Maastricht and tested there, not in China. So, your statemenet is 
highly misleading. There were plenty of comments etc one whole meeting 
cycle ahead of time.

If you are talking about the badge checking in Beijing, that's another 
matter, but also not an IAOC policy matter that was "planned".

> 
> 
> Doug
> 
> -- 


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



From dougb@dougbarton.us  Tue Feb 22 10:42:41 2011
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9D043A6939 for <ietf@core3.amsl.com>; Tue, 22 Feb 2011 10:42:41 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38Pk1mjSE116 for <ietf@core3.amsl.com>; Tue, 22 Feb 2011 10:42:39 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id 29B283A6916 for <ietf@ietf.org>; Tue, 22 Feb 2011 10:42:39 -0800 (PST)
Received: (qmail 21564 invoked by uid 399); 22 Feb 2011 18:43:20 -0000
Received: from router.ka9q.net (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@75.60.237.91) by mail2.fluidhosting.com with ESMTPAM; 22 Feb 2011 18:43:20 -0000
X-Originating-IP: 75.60.237.91
X-Sender: dougb@dougbarton.us
Message-ID: <4D6403C7.1090503@dougbarton.us>
Date: Tue, 22 Feb 2011 10:43:19 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110129 Thunderbird/3.1.7
MIME-Version: 1.0
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM> <54C48986-B211-462C-B942-247886122AF2@gmail.com> <DFA887BC0886F81AADFA0390@PST.JCK.COM> <4D62D960.3040406@dougbarton.us> <alpine.OSX.2.01.1102220928500.33818@macpro.local>
In-Reply-To: <alpine.OSX.2.01.1102220928500.33818@macpro.local>
X-Enigmail-Version: 1.1.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 18:42:42 -0000

On 02/22/2011 09:33, Ole Jacobsen wrote:

> If you are talking about the badge checking in Beijing, that's another
> matter, but also not an IAOC policy matter that was "planned".

That is what I was talking about, yes. Sorry the 2 things got conflated 
in my mind. And in fairness to the IAOC, as I pointed out previously 
without knowing all the details of that incident I didn't feel 
comfortable speaking out about my concerns at the time. Looking back now 
it _seems_ to have been a step on the slippery slope.

... but even if I'm still totally wrong about that, the current 
situation (publishing the RFPs without wider community input) is 
definitely in the category of "needs feedback."


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

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


From jdfalk-lists@cybernothing.org  Tue Feb 22 10:43:51 2011
Return-Path: <jdfalk-lists@cybernothing.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 438853A6945; Tue, 22 Feb 2011 10:43:51 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qgezKiUpa+Sm; Tue, 22 Feb 2011 10:43:50 -0800 (PST)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by core3.amsl.com (Postfix) with ESMTP id E7A303A692B; Tue, 22 Feb 2011 10:43:49 -0800 (PST)
Received: from [192.168.11.33] (c-76-126-154-212.hsd1.ca.comcast.net [76.126.154.212]) (authenticated bits=0) by ocelope.disgruntled.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p1MIiVMn005004 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 22 Feb 2011 10:44:33 -0800
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
X-Priority: 3
In-Reply-To: <622C74FA4B4D440C8F6D28CB6B3E0372@china.huawei.com>
Date: Tue, 22 Feb 2011 10:44:31 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B520B71D-D6A8-441F-9FB4-53418B50ECB3@cybernothing.org>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM><54C48986-B211-462C-B942-247886122AF2@gmail.com> <4D62CDAE.7070006@gmail.com> <622C74FA4B4D440C8F6D28CB6B3E0372@china.huawei.com>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 18:43:51 -0000

On Feb 21, 2011, at 1:18 PM, Spencer Dawkins wrote:

> For what it's worth,
>=20
> I agree that when you're talking to the community about RFPs, it's =
great if that doesn't turn into a wordsmithing exercise on the ietf =
mailing list,
>=20
> And I agree that providing a list of things that lawyers have already =
done for us is a very reasonable basis for an RFP about what we expect =
lawyers to do for us,
>=20
> But I do think posting draft text does allow you to say "and the =
community saw this" if you guys get any pushback at all...

+1

The same process internet-drafts go through, right?  Or as close as =
makes sense.

--
J.D. Falk
the leading purveyor of industry counter-rhetoric solutions


From spencer@wonderhamster.org  Tue Feb 22 10:55:15 2011
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A46DF3A695F; Tue, 22 Feb 2011 10:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.328
X-Spam-Level: 
X-Spam-Status: No, score=-102.328 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58OuLM2YrteY; Tue, 22 Feb 2011 10:55:14 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id BA2D33A695D; Tue, 22 Feb 2011 10:55:14 -0800 (PST)
Received: from S73602b ([12.172.14.11]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0Lb5Wr-1QL0kM0djd-00l3XU; Tue, 22 Feb 2011 13:55:58 -0500
Message-ID: <521BD6534FA84D32908C3BE978D300E3@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "J.D. Falk" <jdfalk-lists@cybernothing.org>, "IETF list" <ietf@ietf.org>
References: <E23665735D529B2C8CC3A393@PST.JCK.COM><54C48986-B211-462C-B942-247886122AF2@gmail.com><4D62CDAE.7070006@gmail.com><622C74FA4B4D440C8F6D28CB6B3E0372@china.huawei.com> <B520B71D-D6A8-441F-9FB4-53418B50ECB3@cybernothing.org>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
Date: Tue, 22 Feb 2011 12:55:49 -0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
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.5994
X-Provags-ID: V02:K0:nW6Xob+JW7st6UtyICE48juPic1TSmrgMzWq2agBdF+ /rzJbl5DWyNLN4XIYqQneDqpaOvBtSMgQD2xVEmQWYrUWNiO0i x7GxWvbtztz3i/+qYM67rFCKtYlwPTY3fCN1eOqMKJJZP64qmc 4K/1IXShA11bFPes0tVCv/nALlnf/bc546pqbOTY1xbCleo3bJ BLWkVD25Qc9TZyS6tBOMr0wJQSoUGhAWiVdN3BSSl0=
Cc: iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2011 18:55:15 -0000

Hi, J.D.,

>> But I do think posting draft text does allow you to say "and the 
>> community saw this" if you guys get any pushback at all...
>
> +1
>
> The same process internet-drafts go through, right?  Or as close as makes 
> sense.

If "process" means "a chance for the community to look and comment before 
it's too late", yes, exactly.

That's what we do for Internet Drafts, and it's almost certainly easier to 
make a contract that's in effect go away, than to make an RFC go away :D

My sense is that the community is trained to back off (not completely, but 
at least significantly) when told "yeah, and the working group considered 
that", "yeah, and the NomCom considered that", or even "yeah, that came up 
in IETF Last Call", and the IAOC might benefit if they could make the same 
point about RFPs.

Thanks,

Spencer 


From bob.hinden@gmail.com  Tue Feb 22 18:31:10 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F22643A67D0; Tue, 22 Feb 2011 18:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.574
X-Spam-Level: 
X-Spam-Status: No, score=-103.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIEtimhCOoD2; Tue, 22 Feb 2011 18:31:09 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 12D353A67B8; Tue, 22 Feb 2011 18:31:09 -0800 (PST)
Received: by iwl42 with SMTP id 42so4891994iwl.31 for <multiple recipients>; Tue, 22 Feb 2011 18:31:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:cc:to:mime-version:x-mailer; bh=+7qLQXi1nDDSi8TcmPPAOHoW+dmPcXSqkDLg96Spsw8=; b=dBkbaslJnDEvAw2K4KsRrxZ1Gy7fyb+tjO45v7djMhuNeFgERGocANrM/7kEctiE7P jETstIMY/4UKMTsmgQxa8U1hmss209cog+9zsi6Z7qlgL53/SrqfFcIuKAOYWheGK9dt xFcsGSp1aLzkUuhwLUZuhw736XAzLG40XuoEw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; b=dbzSwQb4WGotJFL3/M3lOy8JUOnMWlmKJCydbP8vKMs6HOaO9ZsOZ7S68rrGI12J+3 eZF5jpw/ZvNaEm+Sm+ZjnE5Nr0iqlUZKJDynFK5mHO8arHFsI+Mi6RHS/IonAvLeTvos Zh0+R89VVne0bTq74rsGKXc899xLvrb2gJ60g=
Received: by 10.42.225.4 with SMTP id iq4mr4512501icb.110.1298428314815; Tue, 22 Feb 2011 18:31:54 -0800 (PST)
Received: from [10.0.0.37] (c-24-130-226-27.hsd1.ca.comcast.net [24.130.226.27]) by mx.google.com with ESMTPS id ve9sm765357icb.6.2011.02.22.18.31.48 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Feb 2011 18:31:50 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: xml2rfc RFP
Date: Tue, 22 Feb 2011 18:31:47 -0800
Message-Id: <D2C9BE7C-BC3F-42B8-B602-4EBC5C3CCADD@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Cc: iaoc@ietf.org, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 02:31:10 -0000

Based on the discussion, the IAOC has decided to put the XML2RFC RFP on =
hold, notify potential bidders of this, and have a community comment =
period on the tools-discuss@ietf.org list.  Subscription information can =
be found at:

  https://www.ietf.org/mailman/listinfo/tools-discuss

The RFP is located at: =20

  http://iaoc.ietf.org/rfpsrfis.html=20

The comment period will end on March 9. =20

Please note that the main goal is to have a supportable xml2rfc tool =
this year that works for the current users and provides the =
functionality of the current tool with some incremental improvements.  =
There will be an opportunity in the future for changes that can not be =
accommodated in this phase. =20

Bob





From julian.reschke@gmx.de  Wed Feb 23 01:46:26 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C260B3A67A5 for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 01:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.099
X-Spam-Level: 
X-Spam-Status: No, score=-104.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shkX8bsHSgpD for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 01:46:26 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 8C5F03A6407 for <ietf@ietf.org>; Wed, 23 Feb 2011 01:46:25 -0800 (PST)
Received: (qmail invoked by alias); 23 Feb 2011 09:47:10 -0000
Received: from p508FB4B4.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.180.180] by mail.gmx.net (mp016) with SMTP; 23 Feb 2011 10:47:10 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/OpWd9laLOtXvzyiq42f2Gaj8a2OcPR0sM51QASQ 92IxgCTnkatygT
Message-ID: <4D64D78C.5080500@gmx.de>
Date: Wed, 23 Feb 2011 10:46:52 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com>	<708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.com>	<4D63E136.5070805@dcrocker.net> <95586EBA-DB21-4D1F-A271-776C6FE4D27B@vigilsec.com>
In-Reply-To: <95586EBA-DB21-4D1F-A271-776C6FE4D27B@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IAOC <iaoc@ietf.org>, dcrocker@bbiw.net, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 09:46:26 -0000

On 22.02.2011 17:18, Russ Housley wrote:
>
>>> There are many tools used by I-D
>>> authors, including nroff/troff/groff, NroffEdit, MS Word templates, LaTex,
>>> and a plethora of editors.  The IETF cannot take on every tool that seems
>>> popular.
>>
>>
>> Isn't the statistic of xml2rfc use somewhere around 50-60%?
>
> Roughly half.  Again, that is why there is a value to the RFC Production Center.
> ...

Can the RFC Production Center remind us about what the actual numbers 
are, and also whether they ever generate an XML version if the authors 
didn't supply one?

Best regards, Julian

From julian.reschke@gmx.de  Wed Feb 23 02:09:19 2011
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 510923A6836 for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 02:09:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.08
X-Spam-Level: 
X-Spam-Status: No, score=-104.08 tagged_above=-999 required=5 tests=[AWL=-1.481, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxx0JKi2mMpC for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 02:09:18 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 31E043A67CF for <ietf@ietf.org>; Wed, 23 Feb 2011 02:09:17 -0800 (PST)
Received: (qmail invoked by alias); 23 Feb 2011 10:10:03 -0000
Received: from p508FB4B4.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.180.180] by mail.gmx.net (mp046) with SMTP; 23 Feb 2011 11:10:03 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18r/I9GVrkr2C0cfJDIID9JcIQ7MMHRUPanUCuFm3 3++7XbJRSI7XYG
Message-ID: <4D64DCF2.3060004@gmx.de>
Date: Wed, 23 Feb 2011 11:09:54 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
References: <E23665735D529B2C8CC3A393@PST.JCK.COM>, <54C48986-B211-462C-B942-247886122AF2@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DA@DC-US1MBEX4.global.avaya.com>, <69EC0EF3-E8CB-473C-9F43-B29CD1C5F800@vigilsec.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14DD@DC-US1MBEX4.global.avaya.com>	<708DE35B-FCE3-4D64-B780-48C8820D5360@vigilsec.com>	<4D63E136.5070805@dcrocker.net> <95586EBA-DB21-4D1F-A271-776C6FE4D27B@vigilsec.com> <4D64D78C.5080500@gmx.de>
In-Reply-To: <4D64D78C.5080500@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IAOC <iaoc@ietf.org>, dcrocker@bbiw.net, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 10:09:19 -0000

On 23.02.2011 10:46, Julian Reschke wrote:
> On 22.02.2011 17:18, Russ Housley wrote:
>>
>>>> There are many tools used by I-D
>>>> authors, including nroff/troff/groff, NroffEdit, MS Word templates,
>>>> LaTex,
>>>> and a plethora of editors. The IETF cannot take on every tool that
>>>> seems
>>>> popular.
>>>
>>>
>>> Isn't the statistic of xml2rfc use somewhere around 50-60%?
>>
>> Roughly half. Again, that is why there is a value to the RFC
>> Production Center.
>> ...
>
> Can the RFC Production Center remind us about what the actual numbers
> are, and also whether they ever generate an XML version if the authors
> didn't supply one?
> ...

I just realized that I have an archive of XML versions of RFCs in AUTH48 
state; so I *can* report the percentage of XML versions since ~RFC5000.

Note that these may be inaccurate (for instance, not all RFC numbers get 
assigned, right?); it just observes how much XML files ended up in AUTH48.

Here are the numbers:

RFC5000 - RFC5099: 41
RFC5100 - RFC5199: 44
RFC5200 - RFC5299: 47
RFC5300 - RFC5399: 48
RFC5400 - RFC5499: 64
RFC5500 - RFC5599: 59
RFC5600 - RFC5699: 58
RFC5700 - RFC5799: 64
RFC5800 - RFC5899: 63
RFC5900 - RFC5999: 68
RFC6000 - RFC6099: 69

Best regards, Julian

From sginoza@amsl.com  Wed Feb 23 07:45:10 2011
Return-Path: <sginoza@amsl.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B632D3A68F3 for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 07:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.226
X-Spam-Level: 
X-Spam-Status: No, score=-0.226 tagged_above=-999 required=5 tests=[AWL=2.372,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOSkWwjoC6dJ for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 07:45:07 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id D1C4E3A6845 for <ietf@ietf.org>; Wed, 23 Feb 2011 07:45:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 6AE91E08C5 for <ietf@ietf.org>; Wed, 23 Feb 2011 07:45:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c1a.amsl.com ([127.0.0.1]) by localhost (c1a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUeTp-OOtFVQ for <ietf@ietf.org>; Wed, 23 Feb 2011 07:45:54 -0800 (PST)
Received: from [192.168.1.64] (99-17-217-159.lightspeed.snvaca.sbcglobal.net [99.17.217.159]) by c1a.amsl.com (Postfix) with ESMTPA id 1DBD3E08C0 for <ietf@ietf.org>; Wed, 23 Feb 2011 07:45:54 -0800 (PST)
From: Sandy Ginoza <sginoza@amsl.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-2-193690276
Subject: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
Date: Wed, 23 Feb 2011 07:45:53 -0800
Message-Id: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com>
To: The IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Mailman-Approved-At: Wed, 23 Feb 2011 09:25:22 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 15:45:10 -0000

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

>> Can the RFC Production Center remind us about what the actual numbers
>> are, and also whether they ever generate an XML version if the =
authors
>> didn't supply one?


Julian's numbers are good approximations; 50-60% of docs have XML source =
files. =20

The Production Center does not create XML files.  We process XML files =
when XML source files are provided to us. =20

Thanks,
Sandy
for the RFC Production Center


> From: Julian Reschke <julian.reschke@gmx.de>
> Date: February 23, 2011 5:09:54 AM EST
> To: Russ Housley <housley@vigilsec.com>
> Cc: dcrocker@bbiw.net, IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
> Subject: RFC production center XML format usage, was: [IAOC] xml2rfc =
and legal services RFPs
>=20
> On 23.02.2011 10:46, Julian Reschke wrote:
>> On 22.02.2011 17:18, Russ Housley wrote:
>>>=20
>>>>> There are many tools used by I-D
>>>>> authors, including nroff/troff/groff, NroffEdit, MS Word =
templates,
>>>>> LaTex,
>>>>> and a plethora of editors. The IETF cannot take on every tool that
>>>>> seems
>>>>> popular.
>>>>=20
>>>>=20
>>>> Isn't the statistic of xml2rfc use somewhere around 50-60%?
>>>=20
>>> Roughly half. Again, that is why there is a value to the RFC
>>> Production Center.
>>> ...
>>=20
>> Can the RFC Production Center remind us about what the actual numbers
>> are, and also whether they ever generate an XML version if the =
authors
>> didn't supply one?
>> ...
>=20
> I just realized that I have an archive of XML versions of RFCs in =
AUTH48 state; so I *can* report the percentage of XML versions since =
~RFC5000.
>=20
> Note that these may be inaccurate (for instance, not all RFC numbers =
get assigned, right?); it just observes how much XML files ended up in =
AUTH48.
>=20
> Here are the numbers:
>=20
> RFC5000 - RFC5099: 41
> RFC5100 - RFC5199: 44
> RFC5200 - RFC5299: 47
> RFC5300 - RFC5399: 48
> RFC5400 - RFC5499: 64
> RFC5500 - RFC5599: 59
> RFC5600 - RFC5699: 58
> RFC5700 - RFC5799: 64
> RFC5800 - RFC5899: 63
> RFC5900 - RFC5999: 68
> RFC6000 - RFC6099: 69
>=20
> Best regards, Julian


--Apple-Mail-2-193690276
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; =
"><div><blockquote type=3D"cite"><blockquote type=3D"cite">Can the RFC =
Production Center remind us about what the actual =
numbers<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">are, and also whether they ever generate an XML version =
if the authors<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">didn't supply =
one?</blockquote></blockquote></div><div><br></div><div>Julian's numbers =
are good approximations; 50-60% of docs have XML source files. =
&nbsp;</div><div><br></div><div>The Production Center does not create =
XML files. &nbsp;We process XML files when XML source files are provided =
to us. =
&nbsp;</div><div><br></div><div>Thanks,</div><div>Sandy</div><div>for =
the RFC Production Center</div><div><br></div><div><br></div><blockquote =
type=3D"cite">From: Julian Reschke &lt;<a =
href=3D"mailto:julian.reschke@gmx.de">julian.reschke@gmx.de</a>&gt;<br></b=
lockquote><blockquote type=3D"cite">Date: February 23, 2011 5:09:54 AM =
EST<br></blockquote><blockquote type=3D"cite">To: Russ Housley &lt;<a =
href=3D"mailto:housley@vigilsec.com">housley@vigilsec.com</a>&gt;<br></blo=
ckquote><blockquote type=3D"cite">Cc:&nbsp;<a =
href=3D"mailto:dcrocker@bbiw.net">dcrocker@bbiw.net</a>, IAOC &lt;<a =
href=3D"mailto:iaoc@ietf.org">iaoc@ietf.org</a>&gt;, IETF &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br></blockquote><block=
quote type=3D"cite">Subject: RFC production center XML format usage, =
was: [IAOC] xml2rfc and legal services RFPs<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On 23.02.2011 =
10:46, Julian Reschke wrote:<br></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">On 22.02.2011 17:18, Russ =
Housley wrote:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">There =
are many tools used by =
I-D<br></blockquote></blockquote></blockquote></blockquote></blockquote><b=
lockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">authors,=
 including nroff/troff/groff, NroffEdit, MS Word =
templates,<br></blockquote></blockquote></blockquote></blockquote></blockq=
uote><blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">LaTex,<br></blockquote></blockquote></blockquote></blockquot=
e></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">and a plethora of editors. The =
IETF cannot take on every tool =
that<br></blockquote></blockquote></blockquote></blockquote></blockquote><=
blockquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">seems<br></blockquote></blockquote></blockquote></blockquote=
></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">popular.<br></blockquote></blockquote></blockquote></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">Isn't the statistic of xml2rfc =
use somewhere around =
50-60%?<br></blockquote></blockquote></blockquote></blockquote><blockquote=
 type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">Roughly =
half. Again, that is why there is a value to the =
RFC<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">Production =
Center.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">...<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Can the RFC Production Center =
remind us about what the actual =
numbers<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">are, and also whether they ever generate an XML version =
if the authors<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">didn't supply =
one?<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">...<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I just realized =
that I have an archive of XML versions of RFCs in AUTH48 state; so I =
*can* report the percentage of XML versions since =
~RFC5000.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Note that these =
may be inaccurate (for instance, not all RFC numbers get assigned, =
right?); it just observes how much XML files ended up in =
AUTH48.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Here are the =
numbers:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">RFC5000 - =
RFC5099: 41<br></blockquote><blockquote type=3D"cite">RFC5100 - RFC5199: =
44<br></blockquote><blockquote type=3D"cite">RFC5200 - RFC5299: =
47<br></blockquote><blockquote type=3D"cite">RFC5300 - RFC5399: =
48<br></blockquote><blockquote type=3D"cite">RFC5400 - RFC5499: =
64<br></blockquote><blockquote type=3D"cite">RFC5500 - RFC5599: =
59<br></blockquote><blockquote type=3D"cite">RFC5600 - RFC5699: =
58<br></blockquote><blockquote type=3D"cite">RFC5700 - RFC5799: =
64<br></blockquote><blockquote type=3D"cite">RFC5800 - RFC5899: =
63<br></blockquote><blockquote type=3D"cite">RFC5900 - RFC5999: =
68<br></blockquote><blockquote type=3D"cite">RFC6000 - RFC6099: =
69<br></blockquote><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Best regards, =
Julian<br></blockquote><div><br></div></body></html>=

--Apple-Mail-2-193690276--

From dworley@avaya.com  Wed Feb 23 09:29:43 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 678B83A692F for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 09:29:43 -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.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdULXRW8xBcD for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 09:29:42 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id AAD173A6840 for <ietf@ietf.org>; Wed, 23 Feb 2011 09:29:41 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKvSZE3GmAcF/2dsb2JhbACmGXOiSAKZRoVeBIUNil4
X-IronPort-AV: E=Sophos;i="4.62,213,1297054800"; d="scan'208";a="60460629"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 23 Feb 2011 12:30:28 -0500
X-IronPort-AV: E=Sophos;i="4.62,213,1297054800"; d="scan'208";a="585649714"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 Feb 2011 12:30:28 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Wed, 23 Feb 2011 12:30:27 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Sandy Ginoza <sginoza@amsl.com>, The IETF <ietf@ietf.org>
Date: Wed, 23 Feb 2011 12:29:33 -0500
Subject: RE: RFC production center XML format usage,	was: [IAOC] xml2rfc and legal services RFPs
Thread-Topic: RFC production center XML format usage,	was: [IAOC] xml2rfc and legal services RFPs
Thread-Index: AcvTfsiQeP+Gf91TSx2mrcMSclSfLgAAHOVy
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com>
In-Reply-To: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 17:29:43 -0000

> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Sandy Gi=
noza [sginoza@amsl.com]
>=20
> Julian's numbers are good approximations; 50-60% of docs have XML source =
files.

Rising fairly steadily, and approaching 70% in the most recent RFCs.

Dale

From n.mavrogiannopoulos@gmail.com  Wed Feb 23 10:00:02 2011
Return-Path: <n.mavrogiannopoulos@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC41D3A694A; Wed, 23 Feb 2011 10:00:02 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kq0STlbzADa6; Wed, 23 Feb 2011 10:00:01 -0800 (PST)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 59A2F3A693B; Wed, 23 Feb 2011 10:00:01 -0800 (PST)
Received: by ewy9 with SMTP id 9so1177442ewy.31 for <multiple recipients>; Wed, 23 Feb 2011 10:00:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=Fabv+Doqq+jfz4Nxz9+IJ93rcYwngIy9hD20ebs+EVg=; b=XA4yZb3lz5zVThrjmT7UVSlP6tMugG0DHBWUJu2RXnb4zrueD2YYjvenyipnoBoJmt mT5XlOO/BUo3X+W7zGkQwFnxVEwypg0S8IAsR5nHXAM2Xhcg3c+yZ7T08EDCPFFUCoB9 VJruSv1aheNeQ75A3jsYXy6P6mE4fxJ5k2aFk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=EekMRM3j9ewSe27ovJUy3GlN1Nf3NBGcbM0ZJUOUk9+0V5ndHC7VucT9xppZk+0lOc bm3fqyTlgQqd1xf1TeLfa9VoxRkuK3hCLEsCOg1L+fcF3SUxhf/AboGaxsVG5pUFZr+L heB/+j6Jv75R7AiKGUbdmO5veAfIH/ASX+HYQ=
Received: by 10.14.119.16 with SMTP id m16mr4476540eeh.8.1298484047906; Wed, 23 Feb 2011 10:00:47 -0800 (PST)
Received: from [10.100.2.14] (78-23-65-69.access.telenet.be [78.23.65.69]) by mx.google.com with ESMTPS id x54sm7303066eeh.23.2011.02.23.10.00.46 (version=SSLv3 cipher=OTHER); Wed, 23 Feb 2011 10:00:46 -0800 (PST)
Sender: Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com>
Message-ID: <4D654B4D.8020800@gnutls.org>
Date: Wed, 23 Feb 2011 19:00:45 +0100
From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [TLS] Last Call: <draft-kanno-tls-camellia-00.txt> (Addition of the	Camellia Cipher Suites to Transport Layer Security (TLS)) to	Informational RFC
References: <20110223172955.27054.7913.idtracker@localhost>
In-Reply-To: <20110223172955.27054.7913.idtracker@localhost>
X-Enigmail-Version: 1.1.2
OpenPGP: id=96865171
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 18:00:03 -0000

On 02/23/2011 06:29 PM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to
> consider the following document: - 'Addition of the Camellia Cipher
> Suites to Transport Layer Security (TLS)' 
> <draft-kanno-tls-camellia-00.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 2011-03-23.
> 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.
> 
> The file can be obtained via 
> http://datatracker.ietf.org/doc/draft-kanno-tls-camellia/

I see that this document defines ciphersuites with a PRF based on
SHA384... However it does not specify the verify_data_length, thus
the default value of 12 applies, and the SHA384 PRF is being truncated
to 96 bits. Is this intentional? If yes, then what is the purpose to
use the SHA384 as PRF?

regards,
Nikos



From evnikita2@gmail.com  Wed Feb 23 10:19:11 2011
Return-Path: <evnikita2@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E8EC63A676A; Wed, 23 Feb 2011 10:19:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.356
X-Spam-Level: 
X-Spam-Status: No, score=-3.356 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VdRXjqvmOLsr; Wed, 23 Feb 2011 10:19:11 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 4F4673A6935; Wed, 23 Feb 2011 10:19:10 -0800 (PST)
Received: by bwz13 with SMTP id 13so443251bwz.31 for <multiple recipients>; Wed, 23 Feb 2011 10:19:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oKhnS1RKRkOhc9AbKkcb9HSV5GlAGPQhhreK7yvipeM=; b=HkLMaygx4+hrrkxiCLxt8HJMgWrMwkzR3BBEEtib/lWwTvH7QkzR3D3JAGG6peynkA vJX31kx/hYu3u2a33IbMdimsfue01eADV0fcN9+6P/2z3iq2isyG3NcXsKtVR0njMq/h TKtSG7Jq9nQUGV0JqipFiFttCnrQehQmxCe/k=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=sV1q6Eh+6pEzek221qvfa2k8999iVwucgqdw3cAcMk5kftfY8+FpqHIR3Jc/W7PMZb +Fq3EcFPehfXA9UZFeRoZfe/BM9xbszJI/Inao2W5paKkfuGq3FHVl0yEyqR0o8sOpOJ 7f36tR8O0RcOfqP7g8nB+qhwmKWqzXFDL8y8c=
Received: by 10.204.136.15 with SMTP id p15mr2969359bkt.77.1298485191430; Wed, 23 Feb 2011 10:19:51 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id j11sm5514522bka.0.2011.02.23.10.19.49 (version=SSLv3 cipher=OTHER); Wed, 23 Feb 2011 10:19:50 -0800 (PST)
Message-ID: <4D654FE3.8080001@gmail.com>
Date: Wed, 23 Feb 2011 20:20:19 +0200
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-ancp-protocol-15.txt> (Protocol for Access Node Control Mechanism in Broadband Networks) to Proposed Standard
References: <20110223165725.17207.94768.idtracker@localhost>
In-Reply-To: <20110223165725.17207.94768.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ancp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 18:19:12 -0000

Hello,

Let me comment the IANA consideration section of this document.

>    IANA is requested to implement the following modification to the
>     General Switch Management Protocol version 3 (GSMPv3) Result Type
>     Name Space registry:
>
>             +--------------+-----------------------+-----------+
>             | Result Value | Result Type Name      | Reference |
>             +--------------+-----------------------+-----------+
>             | 0            | Ignore (was Reserved) | RFCXXXX   |
>             +--------------+-----------------------+-----------+
In the registry you are modifying the value 0 is now Reserved.  RFC 5226 
says:

>        Reserved:  Not to be assigned.  Reserved values are held for
>              special uses, such as to extend the namespace when it become
>              exhausted.  Reserved values are not available for general
>              assignment.
Therefore it is not permitted to register reserved values.  Moreover, 
this document says that you shouldn't have mentioned exact values you 
want to register - see Section 5.1 of RFC 5226 (the same applies to 
another registry modifications, as one might notice).

Next,

>     IANA is requested to create a new ANCP Port Management Function Name
>     registry, with the following initial entries.  Additions to this
>     registry will be by IETF Consensus.
You should have here the reference to RFC 5226, shouldn't you? (This 
also applies to other registry descriptions)
>    Values may range from 0 to 255.
>
>       [ . . . ]

What is more,

> IANA is requested to create a new ANCP Version registry, with
>     additions by IETF consensus.  The initial entries are as follows:
>
>             +---------+-------------+--------------+-----------+
>             | Version | Sub-Version | Name         | Reference |
>             +---------+-------------+--------------+-----------+
>             | 3       | 1           | Pre-standard |           |
>             | 3       | 2           | ANCPv1       | RFCXXXX   |
>             +---------+-------------+--------------+-----------+
This description is obviously missing the definition of values' format, 
or at least key values.

Moreover,

> IANA is requested to create a new ANCP Command Code registry, with
>     additions by IETF Consensus.  The initial entry is as follows:
>
>       +--------------------+-----------------------------+-----------+
>       | Command Code Value | Command Code Directive Name | Reference |
>       +--------------------+-----------------------------+-----------+
>       | 0                  | Reserved                    | RFCXXXX   |
>       +--------------------+-----------------------------+-----------+
The same as above applies.  Moreover, does this registry consists of 
only one values, that is reserved and therefore cannot be assigned, per 
RFC 5226?  This is at least impossible.

Finally,
> IANA is requested to create a new ANCP TLV Type registry, with
>     additions by IETF Consensus.  Values may range from 0x0000 to 0xFFFF.
>     New assignments should be in the range of values from 0x0100 upwards.
>     The initial entries are as follows:
Here you should have mentioned that values are hexadecimal, for clarity.

Thank you for considering my comments in advance.

All the best,
Mykyta Yevstifeyev


23.02.2011 18:57, The IESG wrote:
> The IESG has received a request from the Access Node Control Protocol WG
> (ancp) to consider the following document:
> - 'Protocol for Access Node Control Mechanism in Broadband Networks'
>    <draft-ietf-ancp-protocol-15.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 2011-03-09. 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.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ancp-protocol/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ancp-protocol/
>
>
>
> The following IPR Declarations may be related to this I-D:
>
> /ipr/1124/
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


From dhc2@dcrocker.net  Wed Feb 23 10:58:59 2011
Return-Path: <dhc2@dcrocker.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BE953A6929 for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 10:58: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5IJFuhQ6jxH for <ietf@core3.amsl.com>; Wed, 23 Feb 2011 10:58:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 8A3F43A6915 for <ietf@ietf.org>; Wed, 23 Feb 2011 10:58:58 -0800 (PST)
Received: from [172.16.1.101] (ip-207-190-24-002.ithink.com [207.190.24.2] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p1NIxOHi005706 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 23 Feb 2011 10:59:32 -0800
Message-ID: <4D65590B.8000808@dcrocker.net>
Date: Wed, 23 Feb 2011 13:59:23 -0500
From: Dave CROCKER <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: RFC production center XML format usage,	was: [IAOC] xml2rfc and legal services RFPs
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.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, 23 Feb 2011 10:59:32 -0800 (PST)
Cc: Sandy Ginoza <sginoza@amsl.com>, The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 18:58:59 -0000

On 2/23/2011 12:29 PM, Worley, Dale R (Dale) wrote:
> Rising fairly steadily, and approaching 70% in the most recent RFCs.


Exactly.

I was impressed with just how steady that increase appears to be over a 
reasonably extended period of time, as well as its seeming to be around 70%, not 
50%, now.

Pretty serious 'market' domination...

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ajs@shinkuro.com  Thu Feb 24 06:41:35 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D7BD3A6B39 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 06:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yo1Cp+2qk8xL for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 06:41:34 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 41A263A6B38 for <ietf@ietf.org>; Thu, 24 Feb 2011 06:41:34 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 1924C1ECB408 for <ietf@ietf.org>; Thu, 24 Feb 2011 14:42:23 +0000 (UTC)
Date: Thu, 24 Feb 2011 09:42:21 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
Message-ID: <20110224144221.GD74938@shinkuro.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <4D65590B.8000808@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D65590B.8000808@dcrocker.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 14:41:35 -0000

On Wed, Feb 23, 2011 at 01:59:23PM -0500, Dave CROCKER wrote:
>
> I was impressed with just how steady that increase appears to be over a  
> reasonably extended period of time, as well as its seeming to be around 
> 70%, not 50%, now.
>
> Pretty serious 'market' domination...

I submit that this is a consequence of the submission process.  The
idnits tool is now an effective gatekeeper against people who are
preparing documents with something other than xml2rfc and, maybe, the
*roff gui that's available.  As a WG chair of a WG with a lot of
participants who have older toolchains, I field regular complaints
about how difficult it is to get things by idnits.  My stock advice is
to use xml2rfc, which is always being updated exactly so that it
conforms to the latest physical layout rules.

I personally think this is sort of a shame, because it reminds me of
other (near) monocultures based on tools that are considerably worse
than the state of the art (Word is my favourite example).

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From dworley@avaya.com  Thu Feb 24 07:18:21 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5AB933A6A18 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 07:18:21 -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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H2PochtMftYA for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 07:18:20 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 5C8AE3A6A02 for <ietf@ietf.org>; Thu, 24 Feb 2011 07:18:20 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADsFZk3GmAcF/2dsb2JhbACmKHOkNgKZO4VgBIUQimM
X-IronPort-AV: E=Sophos;i="4.62,218,1297054800"; d="scan'208";a="233987657"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 24 Feb 2011 10:19:08 -0500
X-IronPort-AV: E=Sophos;i="4.62,218,1297054800"; d="scan'208";a="586108705"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 24 Feb 2011 10:19:08 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 24 Feb 2011 10:19:07 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Andrew Sullivan <ajs@shinkuro.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 24 Feb 2011 10:18:10 -0500
Subject: RE: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
Thread-Topic: RFC production center XML format usage, was: [IAOC] xml2rfc and	legal services RFPs
Thread-Index: AcvUMRnws6bKpGMmTGi4qKcNVRJHngABPIKf
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <4D65590B.8000808@dcrocker.net>,<20110224144221.GD74938@shinkuro.com>
In-Reply-To: <20110224144221.GD74938@shinkuro.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 15:18:21 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Andrew Sul=
livan [ajs@shinkuro.com]

how difficult it is to get things by idnits.
_______________________________________________

I would expect that the idnits rules change only very slowly.  What is the =
real story on that?

Dale

From ajs@shinkuro.com  Thu Feb 24 07:27:41 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CC063A6A13 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 07:27:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mzHQE9uS4Xt for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 07:27:40 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 5C8623A68E3 for <ietf@ietf.org>; Thu, 24 Feb 2011 07:27:40 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id E83F51ECB408 for <ietf@ietf.org>; Thu, 24 Feb 2011 15:28:29 +0000 (UTC)
Date: Thu, 24 Feb 2011 10:28:28 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
Message-ID: <20110224152827.GE74938@shinkuro.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 15:27:41 -0000

On Thu, Feb 24, 2011 at 10:18:10AM -0500, Worley, Dale R (Dale) wrote:
> 
> I would expect that the idnits rules change only very slowly.  What is the real story on that?

They seem to change more quickly than people realise.  Also, of
course, a whole bunch of changes can go by between a given
contributor's last I-D, and a current one.  Not all the changes are
intentional; they're often pretty clearly based on heuristics that as
often as not look to me like they're derived from what certain tools
do.  So then if someone submits something that doesn't do exactly what
those tools do, they get a false failure.

Note that none of this is to attack the tools developers.  I've ranted
before about the absurdity of checking the formatting of early drafts
for perfection, so I won't bother again.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From henrik@levkowetz.com  Thu Feb 24 08:10:58 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED73B3A672E for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S4t6GQjgG8Nw for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:10:56 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 365683A676A for <ietf@ietf.org>; Thu, 24 Feb 2011 08:10:55 -0800 (PST)
Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:52101 helo=dyn-fg117.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PsdmP-0006FV-AB; Thu, 24 Feb 2011 17:11:16 +0100
Message-ID: <4D668314.8060502@levkowetz.com>
Date: Thu, 24 Feb 2011 17:11:00 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Andrew Sullivan <ajs@shinkuro.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com>
In-Reply-To: <20110224152827.GE74938@shinkuro.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e
X-SA-Exim-Rcpt-To: ajs@shinkuro.com, ietf@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 16:10:59 -0000

Hi Andrew,

On 2011-02-24 16:28 Andrew Sullivan said:
> On Thu, Feb 24, 2011 at 10:18:10AM -0500, Worley, Dale R (Dale) wrote:
>>
>> I would expect that the idnits rules change only very slowly.  What is the real story on that?
> 
> They seem to change more quickly than people realise.  Also, of
> course, a whole bunch of changes can go by between a given
> contributor's last I-D, and a current one.  Not all the changes are
> intentional; they're often pretty clearly based on heuristics that as
> often as not look to me like they're derived from what certain tools
> do.  So then if someone submits something that doesn't do exactly what
> those tools do, they get a false failure.
> 
> Note that none of this is to attack the tools developers.  I've ranted
> before about the absurdity of checking the formatting of early drafts
> for perfection, so I won't bother again.

Still, I feel that the characterization above is less than spot-on.  Idnits
in submission-checking mode only returns errors for a few selected things
out of the myriad of things it is able to check, and those things are
clearly required by http://www.ietf.org/id-info/1id-guidelines.txt .

Only errors will prevent an automatic draft submission from going through;
ignore the warnings and comments to your heart's content for that purpose.

If you have examples of drafts which conform to the submission requirements
of 1id-guidelines.txt, but don't pass the submission check mode of idnits,
*please* tell me about them so I can fix things.

The ratio of gripes against idnits to actual bug reports is getting to
be a bit annoying; and I'd like to suggest that people either submit
bug reports, or direct the complaints against the requirements of
1id-guidelines.txt rather than against the tool which checks the
requirements if the problem is that the requirements are too strict.


	Henrik

From dworley@avaya.com  Thu Feb 24 08:24:48 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B6B93A66B4 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:24:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XubKZdoefZBJ for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:24:47 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id A50523A63CB for <ietf@ietf.org>; Thu, 24 Feb 2011 08:24:47 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKMVZk2HCzI1/2dsb2JhbACmKnOkVwKZQYVgBIUQimM
X-IronPort-AV: E=Sophos;i="4.62,219,1297054800"; d="scan'208";a="266510778"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 24 Feb 2011 11:25:36 -0500
X-IronPort-AV: E=Sophos;i="4.62,219,1297054800"; d="scan'208";a="604846929"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 24 Feb 2011 11:25:36 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 24 Feb 2011 11:25:36 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, Andrew Sullivan <ajs@shinkuro.com>
Date: Thu, 24 Feb 2011 11:25:34 -0500
Subject: RE: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
Thread-Topic: RFC production center XML format usage, was: [IAOC] xml2rfc and	legal services RFPs
Thread-Index: AcvUPZcT8cj9nQ+gQvyFGCpqijrSwAAAQShe
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14EF@DC-US1MBEX4.global.avaya.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com>, <4D668314.8060502@levkowetz.com>
In-Reply-To: <4D668314.8060502@levkowetz.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 16:24:48 -0000

> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Henrik L=
evkowetz [henrik@levkowetz.com]
>=20
> Only errors will prevent an automatic draft submission from going through=
;
> ignore the warnings and comments to your heart's content for that purpose=
.

Are you saying that one can order the draft submission process to
continue even if the submission tool considers the draft to violate
idnits?  I had no idea that was possible; I believe (from memory) that
that is not clear from the error output.

> The ratio of gripes against idnits to actual bug reports is getting to
> be a bit annoying; and I'd like to suggest that people either submit
> bug reports, or direct the complaints against the requirements of
> 1id-guidelines.txt rather than against the tool which checks the
> requirements if the problem is that the requirements are too strict.

Based on the user interface principle that each error message should
make it clear what possible next steps are, perhaps your advice
"either submit a bug report about the tool or direct a complaint
against the requirements of 1id-guidelines.txt [give link]" should be
provided in any message that the idnits-checker has rejected a draft.
It would probably reduce the number of non-useful gripes.

"There is a Toyota in the driveway.  I am holding the keys in my hand.
What do I do next?"

Dale

From ben@niven-jenkins.co.uk  Thu Feb 24 08:31:30 2011
Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FF623A6774 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:31:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.299
X-Spam-Level: 
X-Spam-Status: No, score=-104.299 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UZa3Dpqo1OQw for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:31:29 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.61]) by core3.amsl.com (Postfix) with ESMTP id 876683A67B3 for <ietf@ietf.org>; Thu, 24 Feb 2011 08:31:29 -0800 (PST)
Received: from host1.cachelogic.com ([212.44.43.80] helo=[172.16.18.188]) by mail11.atlas.pipex.net with esmtpa (Exim 4.71) (envelope-from <ben@niven-jenkins.co.uk>) id 1Pse6z-0002FP-Pa; Thu, 24 Feb 2011 16:32:18 +0000
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14EF@DC-US1MBEX4.global.avaya.com>
Date: Thu, 24 Feb 2011 16:32:14 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <C571E2FC-2553-47AD-8572-694ABB72E4DA@niven-jenkins.co.uk>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com>, <4D668314.8060502@levkowetz.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EF@DC-US1MBEX4.global.avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
X-Mailer: Apple Mail (2.1082)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
Cc: Henrik Levkowetz <henrik@levkowetz.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 16:31:30 -0000

On 24 Feb 2011, at 16:25, Worley, Dale R (Dale) wrote:

>> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of =
Henrik Levkowetz [henrik@levkowetz.com]
>>=20
>> Only errors will prevent an automatic draft submission from going =
through;
>> ignore the warnings and comments to your heart's content for that =
purpose.
>=20
> Are you saying that one can order the draft submission process to
> continue even if the submission tool considers the draft to violate
> idnits?  I had no idea that was possible; I believe (from memory) that
> that is not clear from the error output.
>=20

idnits reports 3 categories of nits: errors, warnings & comments.

Only errors prevent automatic submission AFAIK.

HTH
Ben


From ajs@shinkuro.com  Thu Feb 24 08:37:51 2011
Return-Path: <ajs@shinkuro.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E8B33A65A5 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:37:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cHFS-duoYYQj for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:37:49 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id BFADC3A66B4 for <ietf@ietf.org>; Thu, 24 Feb 2011 08:37:49 -0800 (PST)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id B96221ECB408; Thu, 24 Feb 2011 16:38:38 +0000 (UTC)
Date: Thu, 24 Feb 2011 11:38:37 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, ietf@ietf.org
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
Message-ID: <20110224163836.GN74938@shinkuro.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com> <4D668314.8060502@levkowetz.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D668314.8060502@levkowetz.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 16:37:51 -0000

On Thu, Feb 24, 2011 at 05:11:00PM +0100, Henrik Levkowetz wrote:
> The ratio of gripes against idnits to actual bug reports is getting to
> be a bit annoying; and I'd like to suggest that people either submit
> bug reports, or direct the complaints against the requirements of
> 1id-guidelines.txt rather than against the tool which checks the
> requirements if the problem is that the requirements are too strict.

You're quite right that I'm using "idnits" as a portmanteau for the
whole "1id-guidelines checking at submission" bundle.  My apologies
for being imprecise.  I am indeed complaining about the latter and not
about the former.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From henrik@levkowetz.com  Thu Feb 24 08:48:26 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2DB53A677E for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:48:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.69
X-Spam-Level: 
X-Spam-Status: No, score=-102.69 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49OlNtgWr3lN for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:48:14 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id BC3B13A63CB for <ietf@ietf.org>; Thu, 24 Feb 2011 08:48:13 -0800 (PST)
Received: from dyn-fg117.sth.netnod.se ([77.72.226.117]:52392) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PseMu-0001Hj-JE; Thu, 24 Feb 2011 17:48:46 +0100
Message-ID: <4D668BEC.9040501@levkowetz.com>
Date: Thu, 24 Feb 2011 17:48:44 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com>	<20110224152827.GE74938@shinkuro.com>, <4D668314.8060502@levkowetz.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EF@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C14EF@DC-US1MBEX4.global.avaya.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 77.72.226.117
X-SA-Exim-Rcpt-To: dworley@avaya.com, ajs@shinkuro.com, ietf@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 16:48:26 -0000

On 2011-02-24 17:25 Worley, Dale R (Dale) said:
>> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Henrik Levkowetz [henrik@levkowetz.com]
>>
>> Only errors will prevent an automatic draft submission from going through;
>> ignore the warnings and comments to your heart's content for that purpose.
> 
> Are you saying that one can order the draft submission process to
> continue even if the submission tool considers the draft to violate
> idnits?  I had no idea that was possible; I believe (from memory) that
> that is not clear from the error output.

This is at the top of the idnits output in submission checking mode:

  "Showing Errors (**), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission."

>> The ratio of gripes against idnits to actual bug reports is getting to
>> be a bit annoying; and I'd like to suggest that people either submit
>> bug reports, or direct the complaints against the requirements of
>> 1id-guidelines.txt rather than against the tool which checks the
>> requirements if the problem is that the requirements are too strict.
> 
> Based on the user interface principle that each error message should
> make it clear what possible next steps are, perhaps your advice
> "either submit a bug report about the tool or direct a complaint
> against the requirements of 1id-guidelines.txt [give link]" should be
> provided in any message that the idnits-checker has rejected a draft.
> It would probably reduce the number of non-useful gripes.

It would also add noise (i.e., text which to most people most of the
time would carry no relevant information, and would just have to be
ignored) to each and every idnits report.

If you google for 'idnits', go to the first hit and click on 'feedback'
you'll be able to send feedback to the right place.  Or go to
tools.ietf.org and click on idnits, and do the same.  I think that
should be easy enough, without adding more noise to the world.


	Henrik

From henrik@levkowetz.com  Thu Feb 24 08:58:24 2011
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 193B13A67D3 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:58:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.683
X-Spam-Level: 
X-Spam-Status: No, score=-102.683 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xsb1UGMs1VC7 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 08:58:23 -0800 (PST)
Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 214D53A65A5 for <ietf@ietf.org>; Thu, 24 Feb 2011 08:58:23 -0800 (PST)
Received: from dyn-fg117.sth.netnod.se ([77.72.226.117]:52445) by merlot.tools.ietf.org with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <henrik@levkowetz.com>) id 1PseWs-00035e-O9; Thu, 24 Feb 2011 17:59:03 +0100
Message-ID: <4D668E56.6000004@levkowetz.com>
Date: Thu, 24 Feb 2011 17:59:02 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Andrew Sullivan <ajs@shinkuro.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com> <4D668314.8060502@levkowetz.com> <20110224163836.GN74938@shinkuro.com>
In-Reply-To: <20110224163836.GN74938@shinkuro.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 77.72.226.117
X-SA-Exim-Rcpt-To: ajs@shinkuro.com, ietf@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 16:58:24 -0000

Hi Andrew,

On 2011-02-24 17:38 Andrew Sullivan said:
> On Thu, Feb 24, 2011 at 05:11:00PM +0100, Henrik Levkowetz wrote:
>> The ratio of gripes against idnits to actual bug reports is getting to
>> be a bit annoying; and I'd like to suggest that people either submit
>> bug reports, or direct the complaints against the requirements of
>> 1id-guidelines.txt rather than against the tool which checks the
>> requirements if the problem is that the requirements are too strict.
> 
> You're quite right that I'm using "idnits" as a portmanteau for the
> whole "1id-guidelines checking at submission" bundle.  My apologies
> for being imprecise.  I am indeed complaining about the latter and not
> about the former.

Ah.  Ok.  I'll go tweak some code, then :-)


Best,

	Henrik


From dworley@avaya.com  Thu Feb 24 09:01:20 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE9053A677E for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 09:01:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyObP9lVmyCA for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 09:01:16 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 495313A67D1 for <ietf@ietf.org>; Thu, 24 Feb 2011 09:01:13 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAE4eZk3GmAcF/2dsb2JhbACmKnOkQQKZQ4VgBIUQimM
X-IronPort-AV: E=Sophos;i="4.62,219,1297054800"; d="scan'208";a="60659063"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 24 Feb 2011 12:01:30 -0500
X-IronPort-AV: E=Sophos;i="4.62,219,1297054800"; d="scan'208";a="586157733"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 24 Feb 2011 12:01:30 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 24 Feb 2011 12:01:29 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
Date: Thu, 24 Feb 2011 11:58:56 -0500
Subject: RE: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
Thread-Topic: RFC production center XML format usage, was: [IAOC] xml2rfc and legal services RFPs
Thread-Index: AcvUQsORp2DWDatbT0mwbrsP+W1R1wAAVya4
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14F2@DC-US1MBEX4.global.avaya.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com>, <4D668314.8060502@levkowetz.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EF@DC-US1MBEX4.global.avaya.com>, <4D668BEC.9040501@levkowetz.com>
In-Reply-To: <4D668BEC.9040501@levkowetz.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 17:01:20 -0000

> From: Henrik Levkowetz [henrik@levkowetz.com]
>=20
> This is at the top of the idnits output in submission checking mode:
>=20
>   "Showing Errors (**), Warnings (=3D=3D), and Comments (--).
>   Errors MUST be fixed before draft submission."

Are people complaining about the errors or the warnings?

> It would also add noise (i.e., text which to most people most of the
> time would carry no relevant information, and would just have to be
> ignored) to each and every idnits report.
>=20
> If you google for 'idnits', go to the first hit and click on 'feedback'
> you'll be able to send feedback to the right place.  Or go to
> tools.ietf.org and click on idnits, and do the same.  I think that
> should be easy enough, without adding more noise to the world.

Hey, man, you're the one who doesn't like getting pointless
complaints.  I'm just suggesting ways you might be able to reduce
them.

Dale

From john-ietf@jck.com  Thu Feb 24 10:21:18 2011
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 693A93A67B1 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 10:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.357
X-Spam-Level: 
X-Spam-Status: No, score=-102.357 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZUGzsyRjV5M3 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 10:21:09 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id DBE943A6784 for <ietf@ietf.org>; Thu, 24 Feb 2011 10:21:07 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Psfp7-0003Xj-0E; Thu, 24 Feb 2011 13:21:57 -0500
Date: Thu, 24 Feb 2011 13:21:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, ietf@ietf.org
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc and	legal services RFPs
Message-ID: <FAFDC74874FD9BA2A6732D21@PST.JCK.COM>
In-Reply-To: <20110224144221.GD74938@shinkuro.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <4D65590B.8000808@dcrocker.net> <20110224144221.GD74938@shinkuro.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 18:21:18 -0000

--On Thursday, February 24, 2011 09:42 -0500 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> On Wed, Feb 23, 2011 at 01:59:23PM -0500, Dave CROCKER wrote:
>> 
>> I was impressed with just how steady that increase appears to
>> be over a   reasonably extended period of time, as well as
>> its seeming to be around  70%, not 50%, now.
>> 
>> Pretty serious 'market' domination...

Dave,

Sure.   But, having started this thread, let me point out that I
don't think anyone has made a serious claim that xml2rfc is
unimportant to the community, that it should not work well, or
even that putting resources into making it more stable, more
maintainable, or better behaved is a bad idea.  Those figures
are interesting but they would be relevant only if one of those
"don't do this at all" arguments were being made.  They haven't
been.

I raised two issues and two issues only:

(i) That the "tell the community work is going to be started by
issuing an RFP" model was suboptimal and maybe inappropriate.  I
think the discussions and conclusions of the last two weeks
indicate that the community agrees with that position and that
the IAOC has recognized that agreement.

(ii) That perhaps the priorities about extensions in the draft
RFP were inappropriate.  I want to stress "perhaps" because,
while I have a view on that subject, I think the correct
priorities can emerge only from community discussion (which
takes us back to (i) above).  Interestingly, while the numbers
you and others cite can be used to argue that improving RFC
Editor Production Center Staff efficiency in dealing with
documents arriving in xml2rfc format, they can equally well be
used to argue that, if the community is producing that much text
in that format, it is at least equally (if not more) important
to improve the efficiency and capabilities of the tool (and
DTD/Schema) for those who are originating/writing the documents.


> I submit that this is a consequence of the submission process.
> The idnits tool is now an effective gatekeeper against people
> who are preparing documents with something other than xml2rfc
> and, maybe, the *roff gui that's available.  As a WG chair of
> a WG with a lot of participants who have older toolchains, I
> field regular complaints about how difficult it is to get
> things by idnits.  My stock advice is to use xml2rfc, which is
> always being updated exactly so that it conforms to the latest
> physical layout rules.
> 
> I personally think this is sort of a shame, because it reminds
> me of other (near) monocultures based on tools that are
> considerably worse than the state of the art (Word is my
> favourite example).

I agree, especially with regard to having the tools
over-constrain early drafts and sometimes thereby making it
harder to expose ideas and get work done.  I think the community
should be pushing back, very hard, on submission tools that
enforce rules that have never been formally announced by the
IESG and/or approved by the community.  But I think it is (or
should be) a separate issue from whether and how we improve the
behavior or robustness of xml2rfc.

   john




From brian.e.carpenter@gmail.com  Thu Feb 24 11:47:47 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED8C43A6802 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 11:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.48
X-Spam-Level: 
X-Spam-Status: No, score=-103.48 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9gpM4Jg36bN for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 11:47:47 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id B3B153A659B for <ietf@ietf.org>; Thu, 24 Feb 2011 11:47:46 -0800 (PST)
Received: by fxm15 with SMTP id 15so924298fxm.31 for <ietf@ietf.org>; Thu, 24 Feb 2011 11:48:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NdMOjdSZPWdvyc09QzVJZ41mPDFpbbNngykCtfvXtVQ=; b=oT77GVe6UuO4tw6DQvHG8cXlVsttKf1YZ8mZ4iXG9UBCmxyHWNaE6q4ItK/V5M2Cae 8u6fADiznHG9khdq+d+91QaHNr85UoxbJnKsjbiu0sNBPmpWf9e45QHFPMhwMnl9Jf4t yMHxBHipLJSETxNao/rn3uuw+zMD75m1J48IM=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=dY2+tE/ClrLGhZlUPJO6y/pvCsxhQlyIr9JjcoVohyA59Jp2uux6bvk2NKcp6stFCB Hxp/CDlK7KnL0rO5abPs88q7VhwuL/6Gkq5sygE89ZU6oLwWjcOuzvt0uFCtpMO8Kt1J SbSh3EH6CQ6Qv8MqpXnwj72smp1S1tjff2F5Q=
Received: by 10.223.79.11 with SMTP id n11mr1555111fak.69.1298576849171; Thu, 24 Feb 2011 11:47:29 -0800 (PST)
Received: from [10.1.1.5] ([121.98.190.33]) by mx.google.com with ESMTPS id e17sm1923213fak.34.2011.02.24.11.47.24 (version=SSLv3 cipher=OTHER); Thu, 24 Feb 2011 11:47:27 -0800 (PST)
Message-ID: <4D66B5C7.6010800@gmail.com>
Date: Fri, 25 Feb 2011 08:47:19 +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: Andrew Sullivan <ajs@shinkuro.com>
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com>	<20110224152827.GE74938@shinkuro.com>	<4D668314.8060502@levkowetz.com> <20110224163836.GN74938@shinkuro.com>
In-Reply-To: <20110224163836.GN74938@shinkuro.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Henrik Levkowetz <henrik@levkowetz.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 19:47:48 -0000

On 2011-02-25 05:38, Andrew Sullivan wrote:
> On Thu, Feb 24, 2011 at 05:11:00PM +0100, Henrik Levkowetz wrote:
>> The ratio of gripes against idnits to actual bug reports is getting to
>> be a bit annoying; and I'd like to suggest that people either submit
>> bug reports, or direct the complaints against the requirements of
>> 1id-guidelines.txt rather than against the tool which checks the
>> requirements if the problem is that the requirements are too strict.
> 
> You're quite right that I'm using "idnits" as a portmanteau for the
> whole "1id-guidelines checking at submission" bundle.  My apologies
> for being imprecise.  I am indeed complaining about the latter and not
> about the former.

For the record, I positively like the facts that the submission tool
carries out basic conformance checks and that 1id-guidelines is
picky.

1. I like this as an author, because it avoids me having to check things
   as a separate step (until the draft is ready for AD review).

2. I like this as a reader and reviewer of drafts, because it leads
   to a very useful degree of uniformity in the way drafts are
   laid out.

And while I'm at it, I like the fact that xml2rfc does a lot of
fiddly stuff for me that I always found a pain in the neck with
other methods.

Yours,
  A Satisfied Customer

From paul.hoffman@vpnc.org  Thu Feb 24 13:14:22 2011
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3F463A684B for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 13:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.464
X-Spam-Level: 
X-Spam-Status: No, score=-101.464 tagged_above=-999 required=5 tests=[AWL=0.582, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t+9DlhO8lcoB for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 13:14:21 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id DB3973A683F for <ietf@ietf.org>; Thu, 24 Feb 2011 13:14:21 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1OLFBKh002204 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 24 Feb 2011 14:15:12 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D66CA5F.8020407@vpnc.org>
Date: Thu, 24 Feb 2011 13:15:11 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com>	<CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com>
In-Reply-To: <20110224152827.GE74938@shinkuro.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 21:14:22 -0000

On 2/24/11 7:28 AM, Andrew Sullivan wrote:
> On Thu, Feb 24, 2011 at 10:18:10AM -0500, Worley, Dale R (Dale) wrote:
>>
>> I would expect that the idnits rules change only very slowly.  What is the real story on that?
>
> They seem to change more quickly than people realise.  Also, of
> course, a whole bunch of changes can go by between a given
> contributor's last I-D, and a current one.  Not all the changes are
> intentional; they're often pretty clearly based on heuristics that as
> often as not look to me like they're derived from what certain tools
> do.  So then if someone submits something that doesn't do exactly what
> those tools do, they get a false failure.
>
> Note that none of this is to attack the tools developers.  I've ranted
> before about the absurdity of checking the formatting of early drafts
> for perfection, so I won't bother again.

Off-list, I asked Henrik which errors the idnits step finds. A summary 
of his answer is "only two non-boilerplate errors (non-ascii characters, 
and lacking an Abstract), and many boilerplate errors (mostly bad IETF 
Trust text, some about the boring first-page boilerplate)". So, I 
suspect that the large percentage of the non-00 drafts getting kicked 
back are due to the IETF Trust requirements changing over time. We can 
argue (and have argued!) about all that, but I think saying "idnits" is 
likely just shooting the messenger.

--Paul Hoffman

From dworley@avaya.com  Thu Feb 24 14:13:09 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31AD63A683F for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 14:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GiCft2Wk0VoY for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 14:13:08 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id 67DEC3A6826 for <ietf@ietf.org>; Thu, 24 Feb 2011 14:13:08 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPdmZk3GmAcF/2dsb2JhbACmM3OkNAKZQ4VgBIUQimM
X-IronPort-AV: E=Sophos;i="4.62,220,1297054800"; d="scan'208";a="60710463"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 24 Feb 2011 17:13:58 -0500
X-IronPort-AV: E=Sophos;i="4.62,220,1297054800"; d="scan'208";a="586290896"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 24 Feb 2011 17:13:57 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 24 Feb 2011 17:13:57 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 24 Feb 2011 17:09:54 -0500
Subject: RE: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
Thread-Topic: RFC production center XML format usage, was: [IAOC] xml2rfc and	legal services RFPs
Thread-Index: AcvUZ//llqmgc0UyQWO3CjZ8eVJgxQAB5Cws
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C14FC@DC-US1MBEX4.global.avaya.com>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com>,<4D66CA5F.8020407@vpnc.org>
In-Reply-To: <4D66CA5F.8020407@vpnc.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 22:13:09 -0000

> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Paul Hof=
fman [paul.hoffman@vpnc.org]
>=20
> So, I suspect that the large percentage of the non-00 drafts getting
> kicked back are due to the IETF Trust requirements changing over
> time. We can argue (and have argued!) about all that, but I think
> saying "idnits" is likely just shooting the messenger.

I wouldn't be surprised.  And although "idnits" catches the bullets
that should be aimed elsewhere, it is where the problem is discovered.
In a perfect world, we would ensure that the users are educated enough
that they can discern the correct entity to blame and file their
reports correctly.  But in the real world, the target audience turns
over fast enough that (collectively) it cannot learn.  So would be
more effective if the necessary information is presented to the user
at the moment the problem becomes evident.

Dale

From narten@us.ibm.com  Thu Feb 24 16:36:58 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 728F73A67FA for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 16:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.024
X-Spam-Level: 
X-Spam-Status: No, score=-106.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YtCz-2BZ42Wv for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 16:36:57 -0800 (PST)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by core3.amsl.com (Postfix) with ESMTP id A411F3A63D3 for <ietf@ietf.org>; Thu, 24 Feb 2011 16:36:57 -0800 (PST)
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by e39.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p1P0P8xv016230 for <ietf@ietf.org>; Thu, 24 Feb 2011 17:25:08 -0700
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 p1P0blwZ085454 for <ietf@ietf.org>; Thu, 24 Feb 2011 17:37:47 -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 p1P0blmE008850 for <ietf@ietf.org>; Thu, 24 Feb 2011 17:37:47 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p1P0bkX8008835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 24 Feb 2011 17:37:47 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p1P0bkjC022196 for <ietf@ietf.org>; Thu, 24 Feb 2011 19:37:46 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p1P0bjsr022152 for ietf@ietf.org; Thu, 24 Feb 2011 19:37:45 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201102250037.p1P0bjsr022152@rotala.raleigh.ibm.com>
Date: Thu, 24 Feb 2011 19:37:45 -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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 00:36:58 -0000

Total of messages in the last 7 days.
 
script run at: Thu Feb 24 19:37:45 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
--------+------+--------+----------+------------------------


From clint.chaplin@gmail.com  Thu Feb 24 16:39:11 2011
Return-Path: <clint.chaplin@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63B3B3A68B9 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 16:39:11 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3HSsImHpsQC for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 16:39:10 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 4D13B3A63D3 for <ietf@ietf.org>; Thu, 24 Feb 2011 16:39:10 -0800 (PST)
Received: by eye13 with SMTP id 13so481184eye.31 for <ietf@ietf.org>; Thu, 24 Feb 2011 16:40:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PTcfLiw9BYz8tDZ9yiI1k6N3aom+xm8GPGFYcE0kask=; b=pHPxnPG6EtOtlUMPKiBCzdyiEtS9Kj6OaBb83DgzuflCRkVQMmRnkEOHn2G2TdE46O VmBl8ff0/aTpn3C9wjrWi7JNN5azUSikJ4lVrQA2RetVwD3XzC8TJFOySPRLPXhER/mt Cc5PVm7FMnOXwJaPPpTXdz1O4/t+4gYjii3PE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=H9rHmSJ19NrgbyIu8+YAp1TbafLWRQpnRhy0Oi1fUX5QAxzx/tY7Ym78IopfDMMk6U DbsAhalcL5rztUe8KexPsF8+1R1PP8DL2Nr2ceoVwj4VSrfLXfuEXEg1IlyH0fuHsNPx ij3arF3LX5P9OXRprTuO3kPgIWW/ENQyyeoqI=
MIME-Version: 1.0
Received: by 10.213.104.136 with SMTP id p8mr1827034ebo.59.1298594399905; Thu, 24 Feb 2011 16:39:59 -0800 (PST)
Received: by 10.213.113.212 with HTTP; Thu, 24 Feb 2011 16:39:59 -0800 (PST)
In-Reply-To: <201102250037.p1P0bjsr022152@rotala.raleigh.ibm.com>
References: <201102250037.p1P0bjsr022152@rotala.raleigh.ibm.com>
Date: Thu, 24 Feb 2011 16:39:59 -0800
Message-ID: <AANLkTi=v7g9x6DJ4Mqo0CKF6QVsD9fwoS0yxR+GEm8gZ@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Clint Chaplin <clint.chaplin@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary=000e0cd1e544e9e808049d1091eb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 00:39:11 -0000

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

Wow; I don't remember us being that quiet....

On Thu, Feb 24, 2011 at 4:37 PM, Thomas Narten <narten@us.ibm.com> wrote:

> Total of messages in the last 7 days.
>
> script run at: Thu Feb 24 19:37:45 EST 2011
>
>    Messages   |      Bytes        | Who
> --------+------+--------+----------+------------------------
> --------+------+--------+----------+------------------------
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



-- 
Clint (JOATMON) Chaplin
Principal Engineer
Corporate Standardization (US)
SISA

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

Wow; I don&#39;t remember us being that quiet....<br><br><div class=3D"gmai=
l_quote">On Thu, Feb 24, 2011 at 4:37 PM, Thomas Narten <span dir=3D"ltr">&=
lt;<a href=3D"mailto:narten@us.ibm.com">narten@us.ibm.com</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Total of messages in the last 7 days.<br>
<br>
script run at: Thu Feb 24 19:37:45 EST 2011<br>
<br>
 =A0 =A0Messages =A0 | =A0 =A0 =A0Bytes =A0 =A0 =A0 =A0| Who<br>
--------+------+--------+----------+------------------------<br>
--------+------+--------+----------+------------------------<br>
<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Clint (JOATMON) Chaplin=
<br>Principal Engineer<br>Corporate Standardization (US)<br>SISA<br>

--000e0cd1e544e9e808049d1091eb--

From narten@us.ibm.com  Thu Feb 24 21:52:13 2011
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A85FE3A692F for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 21:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.216
X-Spam-Level: 
X-Spam-Status: No, score=-106.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id khgjcnuD6-Qe for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 21:52:12 -0800 (PST)
Received: from e4.ny.us.ibm.com (e4.ny.us.ibm.com [32.97.182.144]) by core3.amsl.com (Postfix) with ESMTP id 8FF6D3A67DA for <ietf@ietf.org>; Thu, 24 Feb 2011 21:52:12 -0800 (PST)
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by e4.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p1P5Y66w023047 for <ietf@ietf.org>; Fri, 25 Feb 2011 00:34:06 -0500
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p1P5r3vF2572430 for <ietf@ietf.org>; Fri, 25 Feb 2011 00:53:03 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p1P5r3oR001665 for <ietf@ietf.org>; Fri, 25 Feb 2011 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p1P5r26d001654 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 25 Feb 2011 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id p1P5r22U024401 for <ietf@ietf.org>; Fri, 25 Feb 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p1P5r1Lh024389 for ietf@ietf.org; Fri, 25 Feb 2011 00:53:01 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201102250553.p1P5r1Lh024389@rotala.raleigh.ibm.com>
Date: Fri, 25 Feb 2011 00:53:01 -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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 05:52:13 -0000

Total of 70 messages in the last 7 days.
 
script run at: Fri Feb 25 00:53:01 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.00% |    7 |  7.88% |    36422 | dworley@avaya.com
  4.29% |    3 |  8.17% |    37796 | evnikita2@gmail.com
  7.14% |    5 |  5.13% |    23712 | ajs@shinkuro.com
  4.29% |    3 |  5.43% |    25112 | hallam@gmail.com
  4.29% |    3 |  4.30% |    19899 | john-ietf@jck.com
  2.86% |    2 |  5.70% |    26370 | sginoza@amsl.com
  4.29% |    3 |  3.79% |    17503 | henrik@levkowetz.com
  4.29% |    3 |  3.24% |    14985 | julian.reschke@gmx.de
  4.29% |    3 |  3.19% |    14764 | dougb@dougbarton.us
  4.29% |    3 |  3.16% |    14600 | housley@vigilsec.com
  2.86% |    2 |  3.70% |    17099 | brian.e.carpenter@gmail.com
  2.86% |    2 |  3.50% |    16168 | moore@network-heretics.com
  2.86% |    2 |  3.44% |    15903 | morrowc.lists@gmail.com
  2.86% |    2 |  3.37% |    15582 | spencer@wonderhamster.org
  2.86% |    2 |  3.23% |    14947 | bob.hinden@gmail.com
  2.86% |    2 |  2.46% |    11354 | narten@us.ibm.com
  1.43% |    1 |  2.31% |    10685 | ron.even.tlv@gmail.com
  1.43% |    1 |  2.18% |    10101 | even.roni@huawei.com
  1.43% |    1 |  2.15% |     9921 | ben@nostrum.com
  1.43% |    1 |  1.75% |     8086 | turners@ieca.com
  1.43% |    1 |  1.54% |     7117 | sambasiva.manchili@nexustelecom.com
  1.43% |    1 |  1.42% |     6578 | bertietf@bwijnen.net
  1.43% |    1 |  1.42% |     6557 | clint.chaplin@gmail.com
  1.43% |    1 |  1.30% |     6020 | daedulus@btconnect.com
  1.43% |    1 |  1.26% |     5808 | iad@ietf.org
  1.43% |    1 |  1.25% |     5783 | nmav@gnutls.org
  1.43% |    1 |  1.24% |     5716 | mail@sabahattin-gucukoglu.com
  1.43% |    1 |  1.22% |     5629 | derhoermi@gmx.net
  1.43% |    1 |  1.20% |     5531 | ole@cisco.com
  1.43% |    1 |  1.16% |     5362 | paul.hoffman@vpnc.org
  1.43% |    1 |  1.13% |     5216 | nazare@isoc.org
  1.43% |    1 |  1.12% |     5160 | ned+ietf@mauve.mrochek.com
  1.43% |    1 |  1.04% |     4800 | ben@niven-jenkins.co.uk
  1.43% |    1 |  0.97% |     4469 | dhc2@dcrocker.net
  1.43% |    1 |  0.96% |     4461 | dhc@dcrocker.net
  1.43% |    1 |  0.95% |     4373 | jdfalk-lists@cybernothing.org
  1.43% |    1 |  0.94% |     4346 | chair@ietf.org
  1.43% |    1 |  0.92% |     4251 | sob@harvard.edu
  1.43% |    1 |  0.91% |     4216 | cabo@tzi.org
--------+------+--------+----------+------------------------
100.00% |   70 |100.00% |   462402 | Total

From marc@let.de  Thu Feb 24 22:27:53 2011
Return-Path: <marc@let.de>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7656E3A6935 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 22:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oizjzL8p0A0x for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 22:27:48 -0800 (PST)
Received: from mail.speedpartner.de (mail.speedpartner.de [91.184.32.3]) by core3.amsl.com (Postfix) with ESMTP id 82C5F3A6939 for <ietf@ietf.org>; Thu, 24 Feb 2011 22:27:48 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.speedpartner.de (Postfix) with ESMTP id D05A3B3CAA for <ietf@ietf.org>; Fri, 25 Feb 2011 07:28:37 +0100 (CET)
Received: from mail.speedpartner.de ([127.0.0.1]) by localhost (mail.speedpartner.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDsP9cdudgwF for <ietf@ietf.org>; Fri, 25 Feb 2011 07:28:37 +0100 (CET)
Received: from [192.168.1.83] (f048197124.adsl.alicedsl.de [78.48.197.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.speedpartner.de (Postfix) with ESMTP id B451DB3AD9 for <ietf@ietf.org>; Fri, 25 Feb 2011 07:28:36 +0100 (CET)
Message-Id: <EFF606D8-32F6-4BEA-A338-F905F8677042@let.de>
From: Marc Manthey <marc@let.de>
To: ietf@ietf.org
In-Reply-To: <201102250553.p1P5r1Lh024389@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Subject: Re: Weekly posting summary for ietf@ietf.org
Date: Fri, 25 Feb 2011 07:28:35 +0100
References: <201102250553.p1P5r1Lh024389@rotala.raleigh.ibm.com>
X-Mailer: Apple Mail (2.936)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 06:27:53 -0000

>  4.29% |    3 |  8.17% |    37796 | evnikita2@gmail.com
>  4.29% |    3 |  5.43% |    25112 | hallam@gmail.com
>   2.86% |    2 |  3.70% |    17099 | brian.e.carpenter@gmail.com
>   2.86% |    2 |  3.44% |    15903 | morrowc.lists@gmail.com
>  2.86% |    2 |  3.23% |    14947 | bob.hinden@gmail.com
>  1.43% |    1 |  2.31% |    10685 | ron.even.tlv@gmail.com
>  1.43% |    1 |  1.42% |     6557 | clint.chaplin@gmail.com


http://www.youtube.com/watch?v=3DQOEMv0S8AcA   < ......spying for =20
free :-)))

*SCNR*

have a nice weekend all


Marc


-- =20
Les enfants teribbles - research / deployment
Marc Manthey- Vogelsangerstrasse 97
50823 K=F6ln - Germany
Tel.:0049-221-29891489
Mobil:0049-1577-3329231
blog: http://let.de
project : http://opencu.org
twitter: http://twitter.com/macbroadcast/
facebook : http://opencu.tk


Opinions expressed may not even be mine by the time you read them, and =20=

certainly don't reflect those of any other entity (legal or otherwise).


From fluffy@cisco.com  Fri Feb 25 09:34:17 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 307843A6968 for <ietf@core3.amsl.com>; Fri, 25 Feb 2011 09:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.515
X-Spam-Level: 
X-Spam-Status: No, score=-110.515 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cw4x3zB0pPzB for <ietf@core3.amsl.com>; Fri, 25 Feb 2011 09:34:16 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by core3.amsl.com (Postfix) with ESMTP id 046423A67AE for <ietf@ietf.org>; Fri, 25 Feb 2011 09:34:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=2653; q=dns/txt; s=iport; t=1298655309; x=1299864909; h=mime-version:subject:from:in-reply-to:date: content-transfer-encoding:message-id:references:to; bh=7O73mOzvK+kb87Col4x++ysfTNUJkmve0sz5O8VqXrk=; b=HS77jxHhtr7xVzJw5SqrvHeEJcdHrXvB6sMAh9IYHMsdXPVE7zi3eBi0 XzvPLcpXMBU2FLucTt8LDzkeOon/9XiUPzf8MB4QhrafzjBBEBhdGE668 BjlLjnjZGQU4rTJm+rqrznhIf/6qLQ7a+i2P/gZ1p4qR98gDsdBMad38T g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAF92Z02rRN+K/2dsb2JhbACmPHShPZtign6CYgSFEIcNgz4
X-IronPort-AV: E=Sophos;i="4.62,226,1297036800"; d="scan'208";a="315243147"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-2.cisco.com with ESMTP; 25 Feb 2011 17:35:08 +0000
Received: from [192.168.4.2] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p1PHZ8U1007086 for <ietf@ietf.org>; Fri, 25 Feb 2011 17:35:08 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Last Call: <draft-ietf-intarea-server-logging-recommendations-02.txt> (Logging recommendations for Internet facing servers) to BCP
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <20110225150413.12795.84573.idtracker@localhost>
Date: Fri, 25 Feb 2011 10:37:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5245CFB-CD52-4850-B542-4BCE1456ABFE@cisco.com>
References: <20110225150413.12795.84573.idtracker@localhost>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 17:34:17 -0000

I'd like to see a bit of text about privacy considerations added to =
this. For some servers, the advice in draft is fine but for many =
servers, I think logging this sort of information is an awful idea. It =
makes the owner of the server a subpoena target, possibly violates laws =
in some countries around personal identifying information, and will have =
no benefit for the operator of the server business or ability to debug, =
improve, or provide service.=20

The draft should also point out that the source port, ip, and time does =
not uniquely identify a host behind the nat. Some NATs are designed so =
that two devices inside the NAT, call them A and B, are talking to =
different external servers, call them C and D. The NAT may use the same =
external IP and port on the NAT for the flow from A to C as it uses from =
the flow from B to D. The nat can different them looking at the 5 tuple. =
So if an email server sees a packet form a given IP port at the same =
time that a bittorent server sees packet from same IP and port, there is =
no guarantees that they came from the same host.=20

This recommendation fails to say anything about what protocol one might =
use to log this information - given the rates of information from CGN =
the existing IETF logging protocols may not be appropriate.=20

It seem to me that an BCP about what web, email, sip, and xmpp servers =
should do should probably be run by theses areas.


On Feb 25, 2011, at 8:04 AM, The IESG wrote:

>=20
> The IESG has received a request from the Internet Area Working Group =
WG
> (intarea) to consider the following document:
> - 'Logging recommendations for Internet facing servers'
>  <draft-ietf-intarea-server-logging-recommendations-02.txt> as a BCP
>=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 2011-03-11. 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
> The file can be obtained via
> =
http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommen=
dations/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommen=
dations/
>=20
>=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


From woolf@isc.org  Thu Feb 24 10:38:48 2011
Return-Path: <woolf@isc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE6323A67F7 for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 10:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.725
X-Spam-Level: 
X-Spam-Status: No, score=-2.725 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JDfAZsRUbGK for <ietf@core3.amsl.com>; Thu, 24 Feb 2011 10:38:44 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id 06EC03A67C3 for <ietf@ietf.org>; Thu, 24 Feb 2011 10:38:44 -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 4181B5F98ED; Thu, 24 Feb 2011 18:39:24 +0000 (UTC) (envelope-from woolf@isc.org)
Received: by bikeshed.isc.org (Postfix, from userid 10265) id 60D4B216C22; Thu, 24 Feb 2011 18:39:22 +0000 (UTC)
Date: Thu, 24 Feb 2011 18:39:22 +0000
From: Suzanne Woolf <woolf@isc.org>
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: RFC production center XML format usage, was: [IAOC] xml2rfc	and legal services RFPs
Message-ID: <20110224183922.GA52073@bikeshed.isc.org>
References: <79FAC1BC-BCBB-45A2-AD7A-74D494D5BC89@amsl.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14EB@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C14ED@DC-US1MBEX4.global.avaya.com> <20110224152827.GE74938@shinkuro.com> <4D668314.8060502@levkowetz.com> <20110224163836.GN74938@shinkuro.com> <4D668E56.6000004@levkowetz.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D668E56.6000004@levkowetz.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Fri, 25 Feb 2011 09:59:25 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Feb 2011 18:38:48 -0000

Colleagues,

With respectful apologies to both the posters I'm quoting, I'm going
to reframe this conversation slightly, in hopes of pointing out what I
think we're really talking about, or should be.

On Thu, Feb 24, 2011 at 05:59:02PM +0100, Henrik Levkowetz wrote:
> On 2011-02-24 17:38 Andrew Sullivan said:
> > On Thu, Feb 24, 2011 at 05:11:00PM +0100, Henrik Levkowetz wrote:
> >> The ratio of gripes against idnits to actual bug reports is getting to
> >> be a bit annoying; and I'd like to suggest that people either submit
> >> bug reports, or direct the complaints against the requirements of
> >> 1id-guidelines.txt rather than against the tool which checks the
> >> requirements if the problem is that the requirements are too strict.
> > 
> > You're quite right that I'm using "idnits" as a portmanteau for the
> > whole "1id-guidelines checking at submission" bundle.  My apologies
> > for being imprecise.  I am indeed complaining about the latter and not
> > about the former.
> 
> Ah.  Ok.  I'll go tweak some code, then :-)

The whole process needs work. Focusing on a specific piece is useful
on the merits, but also misses an important point.

I'm a long-time IETF participant who's currently editor on a WG draft
for the first time in several years.

The process of submitting the -00 of the WG draft I'm responsible for
was an eye-opener, and not a happy one.

I knew to use xml2rfc, and I'm familiar with the relevant XML, and I
took a lot of the formatting of meta-boilerplate from a previous
generation of the document. However, the document was still rejected
for automatic submission as a -00 for no reason I could immediately
understand.

A big deal? No, it took two people half an hour to muddle through, and
the obvious backup (email submission) was available, and there were
no deadlines immediately at hand.

Harder than it needed to be? I venture to say yes. The mechanics of
submitting the draft, as opposed to the substance of writing it or the
process of getting WG chair pre-approval, was simply opaque even to an
experienced participant who just hadn't attempted this specific task
before.

I can't tell how much of the wrestling with the tools occurred because
it's been a few years and the process had changed so much, how much
that I had to be reminded to use idnits separately (having looked,
perhaps in the wrong places, for a simple "how to"), how much that the
guidelines document is overly-particular, and how much the submission
tool itself. (The problem was a missing version number in the internal
"filename" parameter, which led to a failed match for the pre-approved
name. The submission tool error was "no previous version found". The
idnits error was that the internal filename didn't have a version
number. Putting those together was harder than it had to be,
especially as I was fooled by the fact I was submitting a file named
exactly what we'd agreed it should be.)

As someone trying to make a contribution as editor of a document
needed by a WG to do its work, I don't care exactly where the problem
lies. I don't even care to characterize it as a documentation error, a
tools error, or a UI (confusing output) error. 

I know that the details of making something like this work can be
arcane, particularly as it evolves. My appreciation for Henrik,
Andrew, and everybody else who makes the whole infrastructure function
is sincere.

But wouldn't it be easier for them, and everyone else, as well as for
me and others who don't write several RFCs a year, if the whole
document submission pipeline could be reviewed and perhaps made easier
to work with?


Suzanne





From bernard_aboba@hotmail.com  Sat Feb 26 17:44:46 2011
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C9B5C3A696D; Sat, 26 Feb 2011 17:44:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level: 
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-8BwJE5MBtJ; Sat, 26 Feb 2011 17:44:44 -0800 (PST)
Received: from blu0-omc3-s29.blu0.hotmail.com (blu0-omc3-s29.blu0.hotmail.com [65.55.116.104]) by core3.amsl.com (Postfix) with ESMTP id 96E583A6968; Sat, 26 Feb 2011 17:44:44 -0800 (PST)
Received: from BLU152-W63 ([65.55.116.74]) by blu0-omc3-s29.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 26 Feb 2011 17:45:40 -0800
Message-ID: <BLU152-w632AA289B4BB351AE9FEDC93DF0@phx.gbl>
Content-Type: multipart/alternative; boundary="_897e5e99-8915-492e-a9f1-6e56696e9640_"
X-Originating-IP: [64.122.3.235]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "dromasca@avaya.com" <dromasca@avaya.com>, <tena@huawei.com>, <ops-dir@ietf.org>, <ietf@ietf.org>
Subject: RE: Request for Operations Directorate Review of draft-ietf-payload-rfc4695-bis-01 by 2011-02-23
Date: Sat, 26 Feb 2011 17:45:40 -0800
Importance: Normal
In-Reply-To: <EDC652A26FB23C4EB6384A4584434A0402C29012@307622ANEX5.global.avaya.com>
References: <000d01cbd0bd$3ae1bd20$b0a53760$@com>, <EDC652A26FB23C4EB6384A4584434A0402C29012@307622ANEX5.global.avaya.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Feb 2011 01:45:40.0406 (UTC) FILETIME=[09EDAD60:01CBD620]
Cc: lazzaro@cs.berkeley.edu, johnw@cs.berkeley.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2011 01:44:46 -0000

--_897e5e99-8915-492e-a9f1-6e56696e9640_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


I reviewed the document draft-ietf-payload-rfc4695-bis in general
and for its operational impact.
=20
Operations directorate reviews are solicited primarily to help the area
directors improve their efficiency=2C particularly when preparing for IESG
telechats=2C and allowing them to focus on documents requiring their attent=
ion
and spend less time on the trouble-free ones.

Improving the documents is important=2C but clearly a secondary purpose.
A third purpose is to broaden the OpsDir reviewers' exposure to work going
on in other parts of the IETF.
=20
Reviews from OpsDir members do not in and of themselves cause the IESG to
raise issue with a document. The reviews may=2C however=2C convince individ=
ual
IESG members to raise concern over a particular document requiring further
discussion. The reviews=2C particularly those conducted in last call and
earlier=2C may also help the document editors improve their documents.
=20
--
=20
Review Summary:=20
Intended status:  Standards Track
=20
   The document provides an updated specification for the RTP=20
   payload format for MIDI=2C suitable for applications such as
   musical performances.  The primary reason for the update was
   to address errors found in RFC 4695 by reviewers. =20

Is the document readable?

Yes.=20
=20
Does it contain nits?

Possibly:

idnits 2.12.07:

tmp/draft-ietf-payload-rfc4695-bis-01.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  -------------------------------------------------------------------------=
---

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt=
:
  -------------------------------------------------------------------------=
---

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/checklist :
  -------------------------------------------------------------------------=
---

  -- The draft header indicates that this document obsoletes RFC4695=2C but=
 the
     abstract doesn't seem to mention this=2C which it should.


  Miscellaneous warnings:
  -------------------------------------------------------------------------=
---

  -- The document date (February 8=2C 2011) is 19 days in the past.  Is thi=
s
     intentional?


  Checking references for intended status: Proposed Standard
  -------------------------------------------------------------------------=
---

     (See RFCs 3967 and 4897 for information about using normative referenc=
es
     to lower-maturity documents in RFCs)

  =3D=3D Unused Reference: 'RFC3986' is defined on line 7122=2C but no expl=
icit
     reference was found in the text
     '[RFC3986]   Berners-Lee=2C T.=2C Fielding=2C R.=2C and L. Masinter=2C=
 "Uniform...'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'MIDI'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'MPEGSA'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'MPEGAUDIO'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'DLS2'

  -- Possible downref: Non-RFC (?) normative reference: ref. 'RP015'


     Summary: 0 errors (**)=2C 1 warning (=3D=3D)=2C 7 comments (--).
---------------------------------------------------------------------------=
-----
=20
Is the document class appropriate?

Yes.

Is the problem well stated?

Yes.

Is the problem really a problem?

Yes.

Does the document consider existing solutions?

Yes. The document addresses issues found in RFC 4695.  The differences are =
detailed in Appendix F=2C and there are
no operational issues raised there (it's mostly ABNF corrections for SDP se=
ssion management parameters).
=20
Does the solution break existing technology?

No.  This update is backward compatible with RFC 4695=2C other than the err=
ors that were corrected.
=20
Does the solution preclude future activity?
=20
No.=20
=20
Is the solution sufficiently configurable?

Yes. Negotiation is taken care of by SDP. =20
=20
Can performance be measured? How?
=20
Yes=2C using RTCP reporting.=20
=20
Does the solution scale well?

Yes. The document defines both multicast and unicast transport. =20
=20
Is Security Management discussed?=20

Security considerations are addressed in Section 9.=20
=20
------------------------------------------------
Hello=2C
As a member of the Operations Directorate you are being asked to review
the following draft which is in IETF last call for it's operational
impact.
=20
IETF Last Call:
The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
=20
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
=20
Please provide comments and review to the Ops-dir mailing list
(ops-dir@ietf.org) before 2011-02-23=2C and include the authors of the
draft as well.
=20
A Check-list of possible questions/topics to address in an OPS-DIR=20
review may be found in Appendix A of RFC 5706.
Only include the questions that apply to your review.
=20
The status of Operations Directorate Review could be found
http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates
or
http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=3D4904/welcome
You could update the wiki page when you finish the review.
=20
=20
Thank you=2C
Tina
http://tinatsou.weebly.com



> > -----Original Message-----
> > From: Tina Tsou [mailto:tena@huawei.com]=20
> > Sent: Sunday=2C February 20=2C 2011 7:16 AM
> > To: Bernard_Aboba@hotmail.com
> > Cc: Romascanu=2C Dan (Dan)=3B rbonica@juniper.net
> > Subject: Request for Operations Directorate Review of=20
> > draft-ietf-payload-rfc4695-bis-01 by 2011-02-23
> >=20
> > Hello=2C
> > As a member of the Operations Directorate you are being asked=20
> > to review the following draft which is in IETF last call for=20
> > it's operational impact.
> >=20
> > IETF Last Call:
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
> >=20
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/
> >=20
> >=20
> > Please provide comments and review to the Ops-dir mailing list
> > (ops-dir@ietf.org) before 2011-02-23=2C and include the authors=20
> > of the draft as well.
> >=20
> > A Check-list of possible questions/topics to address in an=20
> > OPS-DIR review may be found in Appendix A of RFC 5706.
> > Only include the questions that apply to your review.
> >=20
> > The status of Operations Directorate Review could be found=20
> > http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates
> > or
> > http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=3D4904/welcom=
e
> > You could update the wiki page when you finish the review.
> >=20
> >=20
> > Thank you=2C
> > Tina
> > http://tinatsou.weebly.com
> >=20
> >=20
> >=20
 		 	   		  =

--_897e5e99-8915-492e-a9f1-6e56696e9640_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style>
</head>
<body class=3D'hmmessage'>
I reviewed the document draft-ietf-payload-rfc4695-bis in general<br>and fo=
r its operational impact.<br>&nbsp=3B<br>Operations directorate reviews are=
 solicited primarily to help the area<br>directors improve their efficiency=
=2C particularly when preparing for IESG<br>telechats=2C and allowing them =
to focus on documents requiring their attention<br>and spend less time on t=
he trouble-free ones.<br><br>Improving the documents is important=2C but cl=
early a secondary purpose.<br>A third purpose is to broaden the OpsDir revi=
ewers' exposure to work going<br>on in other parts of the IETF.<br>&nbsp=3B=
<br>Reviews from OpsDir members do not in and of themselves cause the IESG =
to<br>raise issue with a document. The reviews may=2C however=2C convince i=
ndividual<br>IESG members to raise concern over a particular document requi=
ring further<br>discussion. The reviews=2C particularly those conducted in =
last call and<br>earlier=2C may also help the document editors improve thei=
r documents.<br>&nbsp=3B<br>--<br>&nbsp=3B<br>Review Summary: <br>Intended =
status:&nbsp=3B Standards Track<br>&nbsp=3B<br>&nbsp=3B&nbsp=3B The documen=
t provides an updated specification for the RTP <br>&nbsp=3B&nbsp=3B payloa=
d format for MIDI=2C suitable for applications such as<br>&nbsp=3B&nbsp=3B =
musical performances.&nbsp=3B The primary reason for the update was<br>&nbs=
p=3B&nbsp=3B to address errors found in RFC 4695 by reviewers.&nbsp=3B <br>=
<br>Is the document readable?<br><br>Yes. <br>&nbsp=3B<br>Does it contain n=
its?<br><br>Possibly:<br><br>idnits 2.12.07:<br><br>tmp/draft-ietf-payload-=
rfc4695-bis-01.txt:<br><br>&nbsp=3B Checking boilerplate required by RFC 53=
78 and the IETF Trust (see<br>&nbsp=3B http://trustee.ietf.org/license-info=
):<br>&nbsp=3B ------------------------------------------------------------=
----------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B No issues found he=
re.<br><br>&nbsp=3B Checking nits according to http://www.ietf.org/id-info/=
1id-guidelines.txt:<br>&nbsp=3B -------------------------------------------=
---------------------------------<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B N=
o issues found here.<br><br>&nbsp=3B Checking nits according to http://www.=
ietf.org/id-info/checklist :<br>&nbsp=3B ----------------------------------=
------------------------------------------<br><br>&nbsp=3B -- The draft hea=
der indicates that this document obsoletes RFC4695=2C but the<br>&nbsp=3B&n=
bsp=3B&nbsp=3B&nbsp=3B abstract doesn't seem to mention this=2C which it sh=
ould.<br><br><br>&nbsp=3B Miscellaneous warnings:<br>&nbsp=3B -------------=
---------------------------------------------------------------<br><br>&nbs=
p=3B -- The document date (February 8=2C 2011) is 19 days in the past.&nbsp=
=3B Is this<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B intentional?<br><br><br>&nb=
sp=3B Checking references for intended status: Proposed Standard<br>&nbsp=
=3B -----------------------------------------------------------------------=
-----<br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B (See RFCs 3967 and 4897 for i=
nformation about using normative references<br>&nbsp=3B&nbsp=3B&nbsp=3B&nbs=
p=3B to lower-maturity documents in RFCs)<br><br>&nbsp=3B =3D=3D Unused Ref=
erence: 'RFC3986' is defined on line 7122=2C but no explicit<br>&nbsp=3B&nb=
sp=3B&nbsp=3B&nbsp=3B reference was found in the text<br>&nbsp=3B&nbsp=3B&n=
bsp=3B&nbsp=3B '[RFC3986]&nbsp=3B&nbsp=3B Berners-Lee=2C T.=2C Fielding=2C =
R.=2C and L. Masinter=2C "Uniform...'<br><br>&nbsp=3B -- Possible downref: =
Non-RFC (?) normative reference: ref. 'MIDI'<br><br>&nbsp=3B -- Possible do=
wnref: Non-RFC (?) normative reference: ref. 'MPEGSA'<br><br>&nbsp=3B -- Po=
ssible downref: Non-RFC (?) normative reference: ref. 'MPEGAUDIO'<br><br>&n=
bsp=3B -- Possible downref: Non-RFC (?) normative reference: ref. 'DLS2'<br=
><br>&nbsp=3B -- Possible downref: Non-RFC (?) normative reference: ref. 'R=
P015'<br><br><br>&nbsp=3B&nbsp=3B&nbsp=3B&nbsp=3B Summary: 0 errors (**)=2C=
 1 warning (=3D=3D)=2C 7 comments (--).<br>--------------------------------=
------------------------------------------------<br>&nbsp=3B<br>Is the docu=
ment class appropriate?<br><br>Yes.<br><br>Is the problem well stated?<br><=
br>Yes.<br><br>Is the problem really a problem?<br><br>Yes.<br><br>Does the=
 document consider existing solutions?<br><br>Yes. The document addresses i=
ssues found in RFC 4695.&nbsp=3B The differences are detailed in Appendix F=
=2C and there are<br>no operational issues raised there (it's mostly ABNF c=
orrections for SDP session management parameters).<br>&nbsp=3B<br>Does the =
solution break existing technology?<br><br>No.&nbsp=3B This update is backw=
ard compatible with RFC 4695=2C other than the errors that were corrected.<=
br>&nbsp=3B<br>Does the solution preclude future activity?<br>&nbsp=3B<br>N=
o. <br>&nbsp=3B<br>Is the solution sufficiently configurable?<br><br>Yes. N=
egotiation is taken care of by SDP.&nbsp=3B <br>&nbsp=3B<br>Can performance=
 be measured? How?<br>&nbsp=3B<br>Yes=2C using RTCP reporting. <br>&nbsp=3B=
<br>Does the solution scale well?<br><br>Yes. The document defines both mul=
ticast and unicast transport.&nbsp=3B <br>&nbsp=3B<br>Is Security Managemen=
t discussed? <br><br>Security considerations are addressed in Section 9. <b=
r>&nbsp=3B<br>------------------------------------------------<br>Hello=2C<=
br>As a member of the Operations Directorate you are being asked to review<=
br>the following draft which is in IETF last call for it's operational<br>i=
mpact.<br>&nbsp=3B<br>IETF Last Call:<br>The file can be obtained via<br>ht=
tp://datatracker.ietf.org/doc/draft-ietf-payload-rfc4695-bis/<br>&nbsp=3B<b=
r>IESG discussion can be tracked via<br>http://datatracker.ietf.org/doc/dra=
ft-ietf-payload-rfc4695-bis/<br>&nbsp=3B<br>Please provide comments and rev=
iew to the Ops-dir mailing list<br>(ops-dir@ietf.org) before 2011-02-23=2C =
and include the authors of the<br>draft as well.<br>&nbsp=3B<br>A Check-lis=
t of possible questions/topics to address in an OPS-DIR <br>review may be f=
ound in Appendix A of RFC 5706.<br>Only include the questions that apply to=
 your review.<br>&nbsp=3B<br>The status of Operations Directorate Review co=
uld be found<br>http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates<=
br>or<br>http://merlot.tools.ietf.org/tools/art/opsdir/index.cgi/t=3D4904/w=
elcome<br>You could update the wiki page when you finish the review.<br>&nb=
sp=3B<br>&nbsp=3B<br>Thank you=2C<br>Tina<br>http://tinatsou.weebly.com<br>=
<br><br><br>&gt=3B &gt=3B -----Original Message-----<br>&gt=3B &gt=3B From:=
 Tina Tsou [mailto:tena@huawei.com] <br>&gt=3B &gt=3B Sent: Sunday=2C Febru=
ary 20=2C 2011 7:16 AM<br>&gt=3B &gt=3B To: Bernard_Aboba@hotmail.com<br>&g=
t=3B &gt=3B Cc: Romascanu=2C Dan (Dan)=3B rbonica@juniper.net<br>&gt=3B &gt=
=3B Subject: Request for Operations Directorate Review of <br>&gt=3B &gt=3B=
 draft-ietf-payload-rfc4695-bis-01 by 2011-02-23<br>&gt=3B &gt=3B <br>&gt=
=3B &gt=3B Hello=2C<br>&gt=3B &gt=3B As a member of the Operations Director=
ate you are being asked <br>&gt=3B &gt=3B to review the following draft whi=
ch is in IETF last call for <br>&gt=3B &gt=3B it's operational impact.<br>&=
gt=3B &gt=3B <br>&gt=3B &gt=3B IETF Last Call:<br>&gt=3B &gt=3B The file ca=
n be obtained via<br>&gt=3B &gt=3B http://datatracker.ietf.org/doc/draft-ie=
tf-payload-rfc4695-bis/<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B IESG discussion =
can be tracked via<br>&gt=3B &gt=3B http://datatracker.ietf.org/doc/draft-i=
etf-payload-rfc4695-bis/<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br>&gt=3B &gt=
=3B Please provide comments and review to the Ops-dir mailing list<br>&gt=
=3B &gt=3B (ops-dir@ietf.org) before 2011-02-23=2C and include the authors =
<br>&gt=3B &gt=3B of the draft as well.<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B =
A Check-list of possible questions/topics to address in an <br>&gt=3B &gt=
=3B OPS-DIR review may be found in Appendix A of RFC 5706.<br>&gt=3B &gt=3B=
 Only include the questions that apply to your review.<br>&gt=3B &gt=3B <br=
>&gt=3B &gt=3B The status of Operations Directorate Review could be found <=
br>&gt=3B &gt=3B http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates=
<br>&gt=3B &gt=3B or<br>&gt=3B &gt=3B http://merlot.tools.ietf.org/tools/ar=
t/opsdir/index.cgi/t=3D4904/welcome<br>&gt=3B &gt=3B You could update the w=
iki page when you finish the review.<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br=
>&gt=3B &gt=3B Thank you=2C<br>&gt=3B &gt=3B Tina<br>&gt=3B &gt=3B http://t=
inatsou.weebly.com<br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br>&gt=3B &gt=3B <br=
> 		 	   		  </body>
</html>=

--_897e5e99-8915-492e-a9f1-6e56696e9640_--

From kanno.satoru@po.ntts.co.jp  Sun Feb 27 22:36:05 2011
Return-Path: <kanno.satoru@po.ntts.co.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D160E3A6AB3; Sun, 27 Feb 2011 22:36:05 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QO4MOE09TqRy; Sun, 27 Feb 2011 22:36:05 -0800 (PST)
Received: from mail12.ics.ntts.co.jp (mail12.ics.ntts.co.jp [210.232.35.65]) by core3.amsl.com (Postfix) with ESMTP id A83143A6A96; Sun, 27 Feb 2011 22:36:04 -0800 (PST)
Received: from sadoku33.silk.ntts.co.jp (sadoku33 [10.7.18.33]) by mail12.ics.ntts.co.jp (8.14.4/8.13.4/NTTSOFT) with ESMTP id p1S6aNkk000760; Mon, 28 Feb 2011 15:36:23 +0900 (JST)
Received: (from root@localhost) by sadoku33.silk.ntts.co.jp (8.13.8/NTTSOFT) id p1S6aNC3020307; Mon, 28 Feb 2011 15:36:23 +0900 (JST)
Received: from ccmds32.silk.ntts.co.jp [10.107.0.32]  by sadoku33.silk.ntts.co.jp with SMTP id RAA20306; Mon, 28 Feb 2011 15:36:23 +0900
Received: from mail137.silk.ntts.co.jp (ccmds32.silk.ntts.co.jp [127.0.0.1]) by ccmds32.silk.ntts.co.jp (8.14.3/8.14.3) with ESMTP id p1S6aM0M028057; Mon, 28 Feb 2011 15:36:22 +0900
Received: from mail137.silk.ntts.co.jp (localhost [127.0.0.1]) by mail137.silk.ntts.co.jp (8.14.4/NTTSOFT) with ESMTP id p1S6aM3A027672; Mon, 28 Feb 2011 15:36:22 +0900 (JST)
Received: from ccmds32 (ccmds32.silk.ntts.co.jp [10.107.0.32]) by mail137.silk.ntts.co.jp (8.14.4/NTTSOFT) with SMTP id p1S6aMxe027669; Mon, 28 Feb 2011 15:36:22 +0900 (JST)
Message-ID: <4D6B423D.1010402@po.ntts.co.jp>
Date: Mon, 28 Feb 2011 15:35:41 +0900
From: Satoru Kanno <kanno.satoru@po.ntts.co.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Subject: Re: [TLS] Last Call: <draft-kanno-tls-camellia-00.txt> (Addition of the	Camellia Cipher Suites to Transport Layer Security (TLS)) to	Informational RFC
References: <20110223172955.27054.7913.idtracker@localhost> <4D654B4D.8020800@gnutls.org>
In-Reply-To: <4D654B4D.8020800@gnutls.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-CC-Mail-RelayStamp: CC-Mail-V4.3-Client
X-CC-Mail-RelayStamp: CC-Mail-V4.3-Server
Cc: ietf@ietf.org, tls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 06:36:06 -0000

(2011/02/24 3:00), Nikos Mavrogiannopoulos wrote:
> On 02/23/2011 06:29 PM, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to
>> consider the following document: - 'Addition of the Camellia Cipher
>> Suites to Transport Layer Security (TLS)'
>> <draft-kanno-tls-camellia-00.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 2011-03-23.
>> 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.
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-kanno-tls-camellia/
>
> I see that this document defines ciphersuites with a PRF based on
> SHA384... However it does not specify the verify_data_length, thus
> the default value of 12 applies, and the SHA384 PRF is being truncated
> to 96 bits. Is this intentional? If yes, then what is the purpose to
> use the SHA384 as PRF?
>

Hi Nikos,

Thank you for your comment.

I think that the verify_data_length with a PRF based on
SHA384 is specified in RFC5246.
As a result, I refer to RFC5246 as well as other documents( e.g., 
RFC5289, RFC5487, and draft-nsri-tls-aria etc.,) in our document.

I think that your comment is not only our draft but all documents 
specifying the PRF base on SHA384 for TLS.

What do you think?

Regards,
Satoru



> regards,
> Nikos
>
>
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>


-- 
Satoru Kanno

Security Business Unit
Mobile and Security Solution Business Group
NTT Software Corporation

e-mail: kanno.satoru@po.ntts.co.jp


From presnick@qualcomm.com  Sun Feb 27 23:31:34 2011
Return-Path: <presnick@qualcomm.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C592D3A6AC3 for <ietf@core3.amsl.com>; Sun, 27 Feb 2011 23:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.531
X-Spam-Level: 
X-Spam-Status: No, score=-106.531 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oZgAfrgpwwMI for <ietf@core3.amsl.com>; Sun, 27 Feb 2011 23:31:33 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id D7FC53A68F2 for <ietf@ietf.org>; Sun, 27 Feb 2011 23:31:33 -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=1298878353; x=1330414353; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4D6B4F86.8080007@qualcomm.com>|Date:=20Mo n,=2028=20Feb=202011=2001:32:22=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>|Subject:=20XKC D=20-=20Nanobots|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=G7Qv3sadzlqM8+c6pZgzEViMbTcxWfiGdKUOgSLK+WA=; b=N/NoWyrkjltfq/aTSv3HziIIAeExxk5bQYmfk81RuvQzbFb3afjBOTdf xssFOwJ8MNddzxaaQ8hQtPx2qPWHIh4wpypievXekvI4Z54QA7BLM0pJL k9al/Ihy4qN7xOTXsth2UaMKuf2z3nUWFyXIzkFnAA6UciqigE0Af8Xzi E=;
X-IronPort-AV: E=McAfee;i="5400,1158,6270"; a="77015740"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 27 Feb 2011 23:32:33 -0800
X-IronPort-AV: E=Sophos;i="4.62,237,1297065600"; d="scan'208";a="54856774"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 27 Feb 2011 23:32: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.270.1; Sun, 27 Feb 2011 23:32:33 -0800
Message-ID: <4D6B4F86.8080007@qualcomm.com>
Date: Mon, 28 Feb 2011 01:32:22 -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: XKCD - Nanobots
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 07:31:34 -0000

I'm sorry, but how could this *not* be posted to the IETF list?

<http://xkcd.com/865/>

pr

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


From bob.hinden@gmail.com  Mon Feb 28 00:39:27 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D4FC3A6AD9 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 00:39:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.531
X-Spam-Level: 
X-Spam-Status: No, score=-103.531 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqniiA4GnyYv for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 00:39:26 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 1CFF03A6ACA for <ietf@ietf.org>; Mon, 28 Feb 2011 00:39:25 -0800 (PST)
Received: by bwz13 with SMTP id 13so4047593bwz.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 00:40:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=JMhCUyreJd7kdb4s4zhf7XDIfKEIrQjUa+ZanFqYFxc=; b=hhD2goLGStBd+vDP3tHHAW88mc56psLzPOnNLhMIi8Pj6xNvArRdQqU6ZBHR4ztN5a 8SlCx5X1+IfkoIarSE2jQK41F3Xk2wEonAR+4pSg47EJyTacexUNR7jvSbEk6uAwEWZr kiexqHnK/CrlG1GtRd3fVQ1BelNxdCpyVxyPE=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=uLfBTwma3FRxwTHS/w8arm6ajEey9zFjfeU5V6kOy3kIz17caupnloBIr4l9X/lt9A TSJvO3fWg3bw7EnOG09dPCCzMTrgj20XCuT/y4OCfJAE9hRYELExaam8yKwxoltCf0PO TFbqZXDj1TudlNt6Ac5HiQVp3BgUzw4SgG0uo=
Received: by 10.204.157.21 with SMTP id z21mr1414676bkw.5.1298882425267; Mon, 28 Feb 2011 00:40:25 -0800 (PST)
Received: from [172.24.249.63] (dyn32-131.checkpoint.com [194.29.32.131]) by mx.google.com with ESMTPS id u23sm2337635bkw.21.2011.02.28.00.40.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Feb 2011 00:40:24 -0800 (PST)
Subject: Re: XKCD - Nanobots
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4D6B4F86.8080007@qualcomm.com>
Date: Mon, 28 Feb 2011 00:40:18 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com>
References: <4D6B4F86.8080007@qualcomm.com>
To: Pete Resnick <presnick@qualcomm.com>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 08:39:27 -0000

Pete,

On Feb 27, 2011, at 11:32 PM, Pete Resnick wrote:

> I'm sorry, but how could this *not* be posted to the IETF list?
>=20
> <http://xkcd.com/865/>

I did a rough calculation and think they would have not run out of IPv6 =
addresses :-)

I assumed a nanobot was 1 x 10^-6 M^2 and the surface of the earth was =
5.1 x 10^11 M^2 (from Wikipedia).  This means it would take 5.1 x 10^17 =
nanobots to cover the earth.  The IPv6 address space is 3.4 x 10^38.  Of =
course, I assumed only one layer deep.=20

Bob



From n.mavrogiannopoulos@gmail.com  Mon Feb 28 00:44:19 2011
Return-Path: <n.mavrogiannopoulos@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A6B63A6AE1; Mon, 28 Feb 2011 00:44:19 -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=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id quNVPkKBLtTV; Mon, 28 Feb 2011 00:44:18 -0800 (PST)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 9660F3A6ADE; Mon, 28 Feb 2011 00:44:18 -0800 (PST)
Received: by qyk7 with SMTP id 7so2818200qyk.10 for <multiple recipients>; Mon, 28 Feb 2011 00:45:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UymXaXJnuCC627tlVYXTVhz3lxQeur095B1ozZsU4bg=; b=B7NLYoWtFZmYX4IE1+vbGMD6haaWoO5TrTkHAFlSFg6cn5mSXiNKKTea7GrLANWXEj Izu/IigAaXWB7GnHDaGmEfccjNRw3SeqOux3zBtwX8xU8BqQDQjix0aITo5/k1qvdofV 6dcW10tY/9eyqOJeNFWPjTAr31/O6qIQwjjHM=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=EFcPw+k0vgzTcaGDHTNBmVx2z8ha1pp2Ps5suOjE1I0WlD0NzqjPAqOrwIZ4eUxuI+ 3uagM4LA4iDglCZDtt2Fz3FQ+eZrXg662gQUwYeaXIXh2l65VcIni7dL3xhQOmtd4PdT 4KF6C99x+R4UxUiWY7jU8FTnEb2VPm0Qf6/TI=
MIME-Version: 1.0
Received: by 10.229.192.149 with SMTP id dq21mr4003295qcb.57.1298882717179; Mon, 28 Feb 2011 00:45:17 -0800 (PST)
Sender: n.mavrogiannopoulos@gmail.com
Received: by 10.229.20.71 with HTTP; Mon, 28 Feb 2011 00:45:17 -0800 (PST)
In-Reply-To: <4D6B423D.1010402@po.ntts.co.jp>
References: <20110223172955.27054.7913.idtracker@localhost> <4D654B4D.8020800@gnutls.org> <4D6B423D.1010402@po.ntts.co.jp>
Date: Mon, 28 Feb 2011 09:45:17 +0100
X-Google-Sender-Auth: D_Tw3CaUBrjRgfMaDfjpEitKzHA
Message-ID: <AANLkTikAu_yzjzH92Fx89EheEvU1zKjTyNi7=NwG1raY@mail.gmail.com>
Subject: Re: [TLS] Last Call: <draft-kanno-tls-camellia-00.txt> (Addition of the Camellia Cipher Suites to Transport Layer Security (TLS)) to Informational RFC
From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: Satoru Kanno <kanno.satoru@po.ntts.co.jp>
Content-Type: text/plain; charset=UTF-8
Cc: ietf@ietf.org, tls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 08:44:19 -0000

On Mon, Feb 28, 2011 at 7:35 AM, Satoru Kanno
<kanno.satoru@po.ntts.co.jp> wrote:

>> I see that this document defines ciphersuites with a PRF based on
>> SHA384... However it does not specify the verify_data_length, thus
>> the default value of 12 applies, and the SHA384 PRF is being truncated
>> to 96 bits. Is this intentional? If yes, then what is the purpose to
>> use the SHA384 as PRF?
> Hi Nikos,
> Thank you for your comment.
> I think that the verify_data_length with a PRF based on
> SHA384 is specified in RFC5246.
> As a result, I refer to RFC5246 as well as other documents( e.g., RFC5289,
> RFC5487, and draft-nsri-tls-aria etc.,) in our document.
> I think that your comment is not only our draft but all documents specifying
> the PRF base on SHA384 for TLS.

Yours was the first document I noticed to use SHA384 as PRF. If there
are other documents that specify that, and don't set the verify_data_length
size then it applies to those as well. (just noticed that applies to RFC5288
as well).

regards,
Nikos

From ynir@checkpoint.com  Mon Feb 28 00:57:07 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C48FF3A6AE2 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 00:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.502
X-Spam-Level: 
X-Spam-Status: No, score=-10.502 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_OTHER=0.135]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zinRf4h0dCy6 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 00:57:06 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 70D293A6ADE for <ietf@ietf.org>; Mon, 28 Feb 2011 00:57:06 -0800 (PST)
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 p1S8w2Dd032310;  Mon, 28 Feb 2011 10:58:02 +0200
X-CheckPoint: {4D6B63B3-8-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 28 Feb 2011 10:58:02 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Bob Hinden <bob.hinden@gmail.com>
Date: Mon, 28 Feb 2011 10:58:05 +0200
Subject: Re: XKCD - Nanobots
Thread-Topic: XKCD - Nanobots
Thread-Index: AcvXJZrk2ZbqIBjnQT+BWP/9Z4tv7A==
Message-ID: <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com>
In-Reply-To: <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@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: Pete Resnick <presnick@qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 08:57:07 -0000

On Feb 28, 2011, at 10:40 AM, Bob Hinden wrote:

> Pete,
>=20
> On Feb 27, 2011, at 11:32 PM, Pete Resnick wrote:
>=20
>> I'm sorry, but how could this *not* be posted to the IETF list?
>>=20
>> <http://xkcd.com/865/>
>=20
> I did a rough calculation and think they would have not run out of IPv6 a=
ddresses :-)
>=20
> I assumed a nanobot was 1 x 10^-6 M^2 and the surface of the earth was 5.=
1 x 10^11 M^2 (from Wikipedia).  This means it would take 5.1 x 10^17 nanob=
ots to cover the earth.  The IPv6 address space is 3.4 x 10^38.  Of course,=
 I assumed only one layer deep.=20
>=20
> Bob

Yes, but I think the nanobots are supposed to devour the entire earth, so i=
t's volume that counts. The volume is about 1x10^21 m^3. So 40% is 4 x 10^2=
0 m^3. =20

3.4 x 10^38 nanobots comes to 8.5 x 10^17 nanobots per m^3, or about 1.17 m=
icrons^3 per nanobot.

Sounds about right.



From joao@bondis.org  Mon Feb 28 01:15:33 2011
Return-Path: <joao@bondis.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D1AA3A6908 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.242
X-Spam-Level: 
X-Spam-Status: No, score=-1.242 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, SARE_SUB_OBFU_OTHER=0.135]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 83AsOXQ2T4TP for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:15:32 -0800 (PST)
Received: from smtp1.bondis.org (voyager.c-l-i.net [194.176.119.229]) by core3.amsl.com (Postfix) with ESMTP id 2A79B3A68C6 for <ietf@ietf.org>; Mon, 28 Feb 2011 01:15:31 -0800 (PST)
Received: from core.c-l-i.net (178.89.217.87.dynamic.jazztel.es [87.217.89.178]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp1.bondis.org (Postfix) with ESMTPSA id C53AE1AB303; Mon, 28 Feb 2011 09:16:29 +0000 (UTC)
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com>
In-Reply-To: <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
Message-Id: <649C3D95-274D-40C8-A5F2-58C3CF5A6F30@bondis.org>
Content-Transfer-Encoding: quoted-printable
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
Subject: Re: XKCD - Nanobots
Date: Mon, 28 Feb 2011 10:16:28 +0100
To: Bob Hinden <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 09:15:33 -0000

On 28 Feb 2011, at 09:40, Bob Hinden wrote:

> Pete,
>=20
> On Feb 27, 2011, at 11:32 PM, Pete Resnick wrote:
>=20
>> I'm sorry, but how could this *not* be posted to the IETF list?
>>=20
>> <http://xkcd.com/865/>
>=20
> I did a rough calculation and think they would have not run out of =
IPv6 addresses :-)
>=20
> I assumed a nanobot was 1 x 10^-6 M^2 and the surface of the earth was =
5.1 x 10^11 M^2 (from Wikipedia).  This means it would take 5.1 x 10^17 =
nanobots to cover the earth.  The IPv6 address space is 3.4 x 10^38.  Of =
course, I assumed only one layer deep.=20

is that with a /48 or a /64 per bot?=

From shane@isc.org  Mon Feb 28 01:44:26 2011
Return-Path: <shane@isc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE4753A6AF0 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:44:26 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8MLM31Ku5Qa for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:44:26 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id 12C6C3A69C8 for <ietf@ietf.org>; Mon, 28 Feb 2011 01:44:26 -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 878F75F985D for <ietf@ietf.org>; Mon, 28 Feb 2011 09:45:11 +0000 (UTC) (envelope-from shane@isc.org)
Received: from [IPv6:2001:610:719:1:20c:76ff:fe4e:e048] (unknown [IPv6:2001:610:719:1:20c:76ff:fe4e:e048]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 4EC88216C1E for <ietf@ietf.org>; Mon, 28 Feb 2011 09:45:09 +0000 (UTC) (envelope-from shane@isc.org)
Subject: Where to find IETF recommendations?
From: Shane Kerr <shane@isc.org>
To: ietf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Organization: ISC
Date: Mon, 28 Feb 2011 10:44:57 +0100
Message-ID: <1298886297.2266.2.camel@shane-desktop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 (2.32.1-1.fc14) 
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 09:44:27 -0000

All,

I just happened to notice this document on ietf-announce today:

http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommendations/

It seems quite reasonable.

My question is... how is this advice expected to trickle out into actual
use? There are more than 6000 RFCs, and they don't seem to be organized
in a useful way that I can find.

I ask because I was going to forward this to an IPv6 operations list,
and thought "hm... what about the rest?" and I realized I did not know,
and did not even know how to find out.

Any advice would be appreciated. Thanks!

--
Shane


From bob.hinden@gmail.com  Mon Feb 28 01:47:58 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6E983A69C1 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:47:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.348
X-Spam-Level: 
X-Spam-Status: No, score=-103.348 tagged_above=-999 required=5 tests=[AWL=-0.184, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iIC3mKbjx63b for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:47:57 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 85E223A6907 for <ietf@ietf.org>; Mon, 28 Feb 2011 01:47:57 -0800 (PST)
Received: by bwz13 with SMTP id 13so4086813bwz.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 01:48:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=9vML6p+6gcXDoh9qnRgikZ/POjTQYF0RfGvZ1sbtfU4=; b=uFe9+SPnVtD6vuud2iqsSzmHu4w9rb75g3Kywbt/Qvxck4SlpzBOWVKDkM463oB5N/ gCBAyA0zcMw/UqU4P0ANUbF0VTRejwS70v5oEsnbCxYT4/G3paCKWVi/3dlrtymE3mBG AFaeb6IyREYfZO+Sbq/ZwK5m+qLbdFxj3l56U=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=eWs3Dv7HdbjCAYSCdUtjHfj1illo6vCWH0La9dRY/49kc8msYFIVO03drJ/vwVIhkj VIL45nQKfPgzIfDK6AvLOLkY+4jOoVR4BDz3FAoE7SpaQHIS6Ece0tOy3Ek0QMtjZ8/9 7zP96q9iOXPe3VvSyOBLlK5M1wU5tBdldwOUI=
Received: by 10.204.26.214 with SMTP id f22mr4513706bkc.100.1298886536302; Mon, 28 Feb 2011 01:48:56 -0800 (PST)
Received: from [172.24.249.63] (dyn32-131.checkpoint.com [194.29.32.131]) by mx.google.com with ESMTPS id a17sm2382791bku.23.2011.02.28.01.48.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Feb 2011 01:48:54 -0800 (PST)
Subject: Re: XKCD - Nanobots
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <649C3D95-274D-40C8-A5F2-58C3CF5A6F30@bondis.org>
Date: Mon, 28 Feb 2011 11:41:39 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <99CE4ABD-B181-440E-A468-488B6C794B0C@gmail.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com> <649C3D95-274D-40C8-A5F2-58C3CF5A6F30@bondis.org>
To: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
X-Mailer: Apple Mail (2.1082)
Cc: Pete Resnick <presnick@qualcomm.com>, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 09:47:58 -0000

On Feb 28, 2011, at 11:16 AM, Jo=E3o Damas wrote:

>=20
> On 28 Feb 2011, at 09:40, Bob Hinden wrote:
>=20
>> Pete,
>>=20
>> On Feb 27, 2011, at 11:32 PM, Pete Resnick wrote:
>>=20
>>> I'm sorry, but how could this *not* be posted to the IETF list?
>>>=20
>>> <http://xkcd.com/865/>
>>=20
>> I did a rough calculation and think they would have not run out of =
IPv6 addresses :-)
>>=20
>> I assumed a nanobot was 1 x 10^-6 M^2 and the surface of the earth =
was 5.1 x 10^11 M^2 (from Wikipedia).  This means it would take 5.1 x =
10^17 nanobots to cover the earth.  The IPv6 address space is 3.4 x =
10^38.  Of course, I assumed only one layer deep.=20
>=20
> is that with a /48 or a /64 per bot?

A /128, of course.  I assume nanobots have very efficient ways to use =
subnets.

Bob



From bob.hinden@gmail.com  Mon Feb 28 01:48:00 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 654E43A6B06 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:48:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.436
X-Spam-Level: 
X-Spam-Status: No, score=-103.436 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r22rfrhiWRi9 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 01:47:59 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 1EA3E3A69C1 for <ietf@ietf.org>; Mon, 28 Feb 2011 01:47:58 -0800 (PST)
Received: by mail-bw0-f44.google.com with SMTP id 13so4086813bwz.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 01:48:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=XrvZqKqUa+JslS6scQqzMJ/yvZcc6NQ68RINXXovBak=; b=fhHQF+J399SkBi1ob+jKc6WJeAzLFhIfMETXeArGuKECS7RcrTBY71c3eO4iCGU4Cn 9kZc8tWuJp3LGOlQUnmoeaYULthHKyF9we5BRABBwQFAVBt7Wg4wPoE8bULTN95Flu+t Ye7Kl5Ch3PfklrZlijuUTzRUbG24y8Yc/9WG0=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=ihbeD0g97IDDyhXKth7WKYj7oc+xvqWyYsDeZiqsm342iA7p0ZcBPYqj0QG7iJGtRN JJyzixx59HeISn0NvEOAvn1H42wat6nTmws+R3cZmFKWVGi/JR/zzm0QPNGcnOckr123 jugK1DpoA54wzhsP+iZ7R+7B9JDaFruSJLqoY=
Received: by 10.204.10.141 with SMTP id p13mr4569069bkp.106.1298886539059; Mon, 28 Feb 2011 01:48:59 -0800 (PST)
Received: from [172.24.249.63] (dyn32-131.checkpoint.com [194.29.32.131]) by mx.google.com with ESMTPS id a17sm2382791bku.23.2011.02.28.01.48.57 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Feb 2011 01:48:58 -0800 (PST)
Subject: Re: XKCD - Nanobots
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com>
Date: Mon, 28 Feb 2011 11:45:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com> <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1082)
Cc: Pete Resnick <presnick@qualcomm.com>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 09:48:00 -0000

Yoav,

> Yes, but I think the nanobots are supposed to devour the entire earth, =
so it's volume that counts. The volume is about 1x10^21 m^3. So 40% is 4 =
x 10^20 m^3. =20

But they start from the outside and eat down.  This causes the surface =
area to decrease and less nonobots are required.  Or to put it another =
way, the don't have to replace the earth with nonbots :-)

>=20
> 3.4 x 10^38 nanobots comes to 8.5 x 10^17 nanobots per m^3, or about =
1.17 microns^3 per nanobot.
>=20
> Sounds about right.

This must have been one of the design goals :-)

Bob


From bob.hinden@gmail.com  Mon Feb 28 02:09:20 2011
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3977B3A6AF2 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 02:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.511
X-Spam-Level: 
X-Spam-Status: No, score=-103.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ecq4CRS2MgrI for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 02:09:19 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 239373A684F for <ietf@ietf.org>; Mon, 28 Feb 2011 02:09:18 -0800 (PST)
Received: by bwz13 with SMTP id 13so4100019bwz.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 02:10:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=Jia5TVVloz0ZyrRWm/3pnVyS2qfl9RKk2wmbEKI1C7k=; b=fBQvBEWb25yYh9nKxPRph5R8apkRCKNOiVwgb1oy1Qstztr4/D+Cwehkz+qks3/s0F HNAiWnyaukRYaShqtVPLFWJ1m0HLEA/Ll4XD+wc6plHrhDfVtilgSHUkYT5BJorU+49w y+SJQ6OPoi1PxB/rFicMelaxNqI9poQ4y7S0Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=BB6DsKW+/neA9/bdfPOZwnCXfq2l+dR2uRNVkX4BdhHMiNMzA3L/6YpgFJNndxwwg+ DDBNzE/p0IgayFvqdoi/U4rtaYr4wssR8AMXFe0jY0ozlDEJSKn96VcBKbzpcAiiLkxd VOBHd5W85Pxen+cV095Qyh2yT8+uh3A8BWxAI=
Received: by 10.204.4.212 with SMTP id 20mr4522276bks.172.1298887818215; Mon, 28 Feb 2011 02:10:18 -0800 (PST)
Received: from [172.24.249.63] (dyn32-131.checkpoint.com [194.29.32.131]) by mx.google.com with ESMTPS id b16sm2391246bkw.14.2011.02.28.02.10.16 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Feb 2011 02:10:17 -0800 (PST)
Subject: Re: Where to find IETF recommendations?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <1298886297.2266.2.camel@shane-desktop>
Date: Mon, 28 Feb 2011 12:10:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB46718F-2DC8-4658-A668-61EE0BF11F08@gmail.com>
References: <1298886297.2266.2.camel@shane-desktop>
To: Shane Kerr <shane@isc.org>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 10:09:20 -0000

Shane,

Like this one, aren't recommendations usually published as BCPs?

Bob


On Feb 28, 2011, at 11:44 AM, Shane Kerr wrote:

> All,
>=20
> I just happened to notice this document on ietf-announce today:
>=20
> =
http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommen=
dations/
>=20
> It seems quite reasonable.
>=20
> My question is... how is this advice expected to trickle out into =
actual
> use? There are more than 6000 RFCs, and they don't seem to be =
organized
> in a useful way that I can find.
>=20
> I ask because I was going to forward this to an IPv6 operations list,
> and thought "hm... what about the rest?" and I realized I did not =
know,
> and did not even know how to find out.
>=20
> Any advice would be appreciated. Thanks!
>=20
> --
> Shane
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From shane@isc.org  Mon Feb 28 02:34:38 2011
Return-Path: <shane@isc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E4113A6B0F for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 02:34:38 -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_33=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0GHwCpJE50C for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 02:34:37 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by core3.amsl.com (Postfix) with ESMTP id 2B6AD3A6B10 for <ietf@ietf.org>; Mon, 28 Feb 2011 02:34: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.ams1.isc.org (Postfix) with ESMTPS id 1CCB65F983B; Mon, 28 Feb 2011 10:35:23 +0000 (UTC) (envelope-from shane@isc.org)
Received: from [IPv6:2001:610:719:1:20c:76ff:fe4e:e048] (unknown [IPv6:2001:610:719:1:20c:76ff:fe4e:e048]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id B3F3B216C31; Mon, 28 Feb 2011 10:35:20 +0000 (UTC) (envelope-from shane@isc.org)
Subject: Re: Where to find IETF recommendations?
From: Shane Kerr <shane@isc.org>
To: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <FB46718F-2DC8-4658-A668-61EE0BF11F08@gmail.com>
References: <1298886297.2266.2.camel@shane-desktop> <FB46718F-2DC8-4658-A668-61EE0BF11F08@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Organization: ISC
Date: Mon, 28 Feb 2011 11:35:12 +0100
Message-ID: <1298889312.4217.5.camel@shane-desktop>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 (2.32.1-1.fc14) 
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 10:34:38 -0000

Bob,

Are recommendations actually published as BCP?

I only see one BCP with "IPv6" in the title, published back in 2004.
Compared to this, the ipv6ops working group alone has produced dozens of
informational RFCs:

https://datatracker.ietf.org/wg/v6ops/

At least one of these are even explicitly recommendations:

https://datatracker.ietf.org/doc/rfc4890/

Some are targeted at protocol developers, some at vendors, some at
operators. It's quite a mixed bag. :)

I'm not complaining, I just want to know if I am missing an obvious
place.

--
Shane

On Mon, 2011-02-28 at 12:10 +0200, Bob Hinden wrote:
> Shane,
> 
> Like this one, aren't recommendations usually published as BCPs?
> 
> Bob
> 
> 
> On Feb 28, 2011, at 11:44 AM, Shane Kerr wrote:
> 
> > All,
> > 
> > I just happened to notice this document on ietf-announce today:
> > 
> > http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommendations/
> > 
> > It seems quite reasonable.
> > 
> > My question is... how is this advice expected to trickle out into actual
> > use? There are more than 6000 RFCs, and they don't seem to be organized
> > in a useful way that I can find.
> > 
> > I ask because I was going to forward this to an IPv6 operations list,
> > and thought "hm... what about the rest?" and I realized I did not know,
> > and did not even know how to find out.
> > 
> > Any advice would be appreciated. Thanks!
> > 
> > --
> > Shane
> > 
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> 



From chelliot@gmail.com  Mon Feb 28 02:40:36 2011
Return-Path: <chelliot@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 800133A6A07 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 02:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.068
X-Spam-Level: 
X-Spam-Status: No, score=-2.068 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1,  SARE_SUB_OBFU_OTHER=0.135]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eNI+niQJ2xyw for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 02:40:35 -0800 (PST)
Received: from mail-yi0-f44.google.com (mail-yi0-f44.google.com [209.85.218.44]) by core3.amsl.com (Postfix) with ESMTP id 75C2E3A69E3 for <ietf@ietf.org>; Mon, 28 Feb 2011 02:40:35 -0800 (PST)
Received: by yib18 with SMTP id 18so587237yib.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 02:41:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=9+eerNh7QQ1EfG1di8TMnJ+rL6rhDQE1hQRPdCm4xCQ=; b=xtxF5ZH0fSzZTem9DGZXgFlxRn0xPv65W69ifBjcyZgAYSw8bhkj3o3RT6MVa7tS1o jlkjWQLCsWvN02Un2fxU/ioqcPHUR94Ei0MI/UdLDoMq5rVsuIWoQHfas1pPh3jHjwOS ziG7nqNhXmiprc4uZ5xR24O+axEMLIdmZ8YOg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; b=qTYhAevZXv9DM4qw+suvBQnmRnK7mz17EWyZyBX0jhUw5bcY2HrRMASJEtihKyvqDc z2gbKco0h4WQpBEyZ6mgnf4Jjm5kpNeDEGxJJt7i5FXaXHbmK1uggJVVaCcqCUkBJyUH GgCquSi3qVbpoIe8CBEDAKKAKuaAwfCgs8JSw=
Received: by 10.236.108.41 with SMTP id p29mr9363818yhg.21.1298889693512; Mon, 28 Feb 2011 02:41:33 -0800 (PST)
Received: from [10.0.1.103] (cpe-098-026-014-181.nc.res.rr.com [98.26.14.181]) by mx.google.com with ESMTPS id g27sm2073212yhc.8.2011.02.28.02.41.31 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 28 Feb 2011 02:41:32 -0800 (PST)
Sender: Chris Elliott <chelliot@gmail.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com> <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com> <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com>
In-Reply-To: <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com>
Mime-Version: 1.0 (iPhone Mail 8C148)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <338AB689-3B1E-4849-BB43-649CC584850D@pobox.com>
X-Mailer: iPhone Mail (8C148)
From: Chris Elliott <chelliot@pobox.com>
Subject: Re: XKCD - Nanobots
Date: Mon, 28 Feb 2011 05:39:48 -0500
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Pete Resnick <presnick@qualcomm.com>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 10:40:36 -0000

Bob, et al.:

I took the liberty of informing Randall that he hit the IETF list on his for=
um here:

http://forums.xkcd.com/viewtopic.php?f=3D7&t=3D68893

May take a bit for my post to get approved.

And, yes, I did point out that you commented...and were involved with the de=
velopment of IPv6... ;-)

Enjoy, and see you all in Prague!
Chris.


--
Chris Elliott


From chelliot@gmail.com  Mon Feb 28 03:16:18 2011
Return-Path: <chelliot@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B89983A69E7 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 03:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.842
X-Spam-Level: 
X-Spam-Status: No, score=-2.842 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_OTHER=0.135]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHefiRw5XG5j for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 03:16:17 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 4CBF43A69DF for <ietf@ietf.org>; Mon, 28 Feb 2011 03:16:17 -0800 (PST)
Received: by eye13 with SMTP id 13so1481741eye.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 03:17:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=yZhJbhnS4OIwi36i7iJtmDIq7KZUR/o+ysCizMnY97M=; b=pfKytV87JNL1gT0TVwhbii0rKex8OPbetSYuH84v5LKyw0FCFGIm1+xGUmFnhDqfBA Fj7ATnNFSXxUJGHs1DC/xhcQWE6mCCWi6PdWvmkTO6oJ0JZi8E07PN9sFVKLQEIcUv5U uSTK7QTgCTbcQyWVoH3PokEaQ5EsnBAtm2nYs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=brv819XofIQTZkn9+D2ZVJGIyt5pu/NE7UwEsXs7F5eikcTFq6NG6B1LEhWOuRKuNV AmvDP10gP4z23UmmbPocNtnmJJX0l+V/emBTLQ+gmojFjlz7avkGbvRYDCMDZ1Ifz/9x Tgo6kMFE8ymIE9BxlmL+sOMi8r0wfqWax/vYk=
MIME-Version: 1.0
Received: by 10.213.19.6 with SMTP id y6mr4186733eba.86.1298891836555; Mon, 28 Feb 2011 03:17:16 -0800 (PST)
Sender: chelliot@gmail.com
Received: by 10.213.22.7 with HTTP; Mon, 28 Feb 2011 03:17:16 -0800 (PST)
In-Reply-To: <338AB689-3B1E-4849-BB43-649CC584850D@pobox.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com> <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com> <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com> <338AB689-3B1E-4849-BB43-649CC584850D@pobox.com>
Date: Mon, 28 Feb 2011 06:17:16 -0500
X-Google-Sender-Auth: MV02fZfQqHCHSF_SdKOhIcrZhI0
Message-ID: <AANLkTin3o2vy2_oYuYMtNnw5_e_L7DYiTryzv3osJGtX@mail.gmail.com>
Subject: Re: XKCD - Nanobots
From: Chris Elliott <chelliot@pobox.com>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: chelliot@pobox.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 11:16:18 -0000

And I'll point out that this is not the first xkcd cartoon to be
referenced by IETF'ers:

http://www.ipv6now.com.au/news/TheStandardAug09.pdf

The referenced comic is # 195, "Map of the Internet,

http://www.xkcd.com/195/

And, as always with xkcd comics, check out the tool tip!

Enjoy again!
Chris.

On Mon, Feb 28, 2011 at 5:39 AM, Chris Elliott <chelliot@pobox.com> wrote:
> Bob, et al.:
>
> I took the liberty of informing Randall that he hit the IETF list on his forum here:
>
> http://forums.xkcd.com/viewtopic.php?f=7&t=68893
>
> May take a bit for my post to get approved.
>
> And, yes, I did point out that you commented...and were involved with the development of IPv6... ;-)
>
> Enjoy, and see you all in Prague!
> Chris.
>
>
> --
> Chris Elliott
>
>



-- 
Chris Elliott
chelliot@pobox.com

From ynir@checkpoint.com  Mon Feb 28 03:17:16 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AF283A69E9 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 03:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.501
X-Spam-Level: 
X-Spam-Status: No, score=-10.501 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_OTHER=0.135]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHxaWONIlPQW for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 03:17:15 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 0ED733A6907 for <ietf@ietf.org>; Mon, 28 Feb 2011 03:17:14 -0800 (PST)
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 p1SBICut028297;  Mon, 28 Feb 2011 13:18:12 +0200
X-CheckPoint: {4D6B848D-2C-1B221DC2-FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 28 Feb 2011 13:18:12 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Chris Elliott <chelliot@pobox.com>
Date: Mon, 28 Feb 2011 13:18:15 +0200
Subject: Re: XKCD - Nanobots
Thread-Topic: XKCD - Nanobots
Thread-Index: AcvXOS+tAkyn4xTJS3qgVifNdOhnyw==
Message-ID: <803A9336-A7C6-4688-AC23-A330D1C21EFC@checkpoint.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com> <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com> <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com> <338AB689-3B1E-4849-BB43-649CC584850D@pobox.com>
In-Reply-To: <338AB689-3B1E-4849-BB43-649CC584850D@pobox.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: Pete Resnick <presnick@qualcomm.com>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 11:17:16 -0000

Yup. It's posted (right after mine)

On Feb 28, 2011, at 12:39 PM, Chris Elliott wrote:

> Bob, et al.:
>=20
> I took the liberty of informing Randall that he hit the IETF list on his =
forum here:
>=20
> http://forums.xkcd.com/viewtopic.php?f=3D7&t=3D68893
>=20
> May take a bit for my post to get approved.
>=20
> And, yes, I did point out that you commented...and were involved with the=
 development of IPv6... ;-)
>=20
> Enjoy, and see you all in Prague!
> Chris.
>=20
>=20
> --
> Chris Elliott
>=20
>=20
> Scanned by Check Point Total Security Gateway.


From anthonybryan@gmail.com  Sat Feb 26 21:38:38 2011
Return-Path: <anthonybryan@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A3F53A69B6; Sat, 26 Feb 2011 21:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.516
X-Spam-Level: 
X-Spam-Status: No, score=-3.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvJ8BiotPVBn; Sat, 26 Feb 2011 21:38:35 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id E03D13A68DB; Sat, 26 Feb 2011 21:38:34 -0800 (PST)
Received: by eye13 with SMTP id 13so1150270eye.31 for <multiple recipients>; Sat, 26 Feb 2011 21:39:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NbFf3NDpX9bZ17Ki+ibeRF93/R9cAG3VRKKfsbxd8No=; b=REfL2exfcr2RhejpScEY47qdOnefJRJxqzTZIffzr71pK1i7Njn7fRchHrf2NnnKUO EvjOKd36SmqA4qL/pPbpQlYIMDSJLETERbDoONf1dJn5JWsQJSgI3UpkIzls2QYdhI2k hbVdxqcImVv6AyMCY7uOayrsc5/XASg2C01ys=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=oaUtzEShuVP5wTiAOuW3aKpv3i6vEqrO5nH787IkXnBHz6ZVs/qKn3bjmyY/w4wlYu 2seQPrAjVmCnRkYcx53x50MmaF8USrfwCd9ZzclWGewbIH2Gwf8BgJrhwe+L47gNQAHm vkPNvRn5TnimVdACSlJEjqoRNo5757KL6RRuo=
MIME-Version: 1.0
Received: by 10.213.34.131 with SMTP id l3mr3407461ebd.8.1298785170198; Sat, 26 Feb 2011 21:39:30 -0800 (PST)
Received: by 10.213.17.148 with HTTP; Sat, 26 Feb 2011 21:39:30 -0800 (PST)
In-Reply-To: <C3E2F61E-A91C-4665-8DF4-42B58C4C0580@nostrum.com>
References: <19DDC0DF-9ECF-499A-954E-17BABF6410B5@nostrum.com> <AANLkTik3VNfsT4fY2wc8HpfidPVCshGSUW1py4Jzf==w@mail.gmail.com> <C3E2F61E-A91C-4665-8DF4-42B58C4C0580@nostrum.com>
Date: Sun, 27 Feb 2011 00:39:30 -0500
Message-ID: <AANLkTimbO9v2HWVrwiaeuaSvWvkrznxgmk6dP7fobz64@mail.gmail.com>
Subject: Re: [Gen-art] Gen-ART LC Review of draft-bryan-metalinkhttp-19
From: Anthony Bryan <anthonybryan@gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Mon, 28 Feb 2011 07:43:11 -0800
Cc: alexey.melnikov@isode.com, General Area Review Team <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-bryan-metalinkhttp.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2011 05:38:39 -0000

On Wed, Feb 16, 2011 at 6:15 PM, Ben Campbell <ben@nostrum.com> wrote:
> Thanks for the quick response. I haven't had a chance to look at the new =
version yet, but here are my responses to your email comments. I removed se=
ctions where I had no further (non-trivial) comment. Please consider any re=
moved parts to be the same as an "Okay" response.
>
> Thanks!
>
> Ben.
>
> On Feb 14, 2011, at 4:43 PM, Anthony Bryan wrote:
>
> [...]
>
>> was there supposed to be a comment along with
>>
>> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the
>> same ETag policy as the originating Metalink server."
>> ?
>
> I responded to this one below.
>
>>
>> On Fri, Feb 11, 2011 at 6:46 PM, Ben Campbell <ben@nostrum.com> wrote:
>
> [...]
>
>>>
>>> -- Section 1, paragraph 1, first sentence:
>>>
>>> Is this really intended as an alternative to Metalink/XML? It seems lik=
e more of a complementary approach than an alternative one.
>>
>> well...you could use either, or both :)
>>
>> "Metalink/HTTP is an alternative and complementary representation of
>> Metalink information,"...
>> ?
>
> WFM
>
>>
>>> -- section 2, third paragraph:
>>>
>>> If they must have the same eTag policy, should this document not specif=
y at least one mandatory-to-implement policy?
>>
>> SHOULD share the same ETag policy.
>>
>> I added:
>>
>> "It is up to the administrator of the Metalink server to communicate
>> the details of the shared ETag policy to the administrators of the
>> mirror servers so that the mirror servers can be configured with the
>> same ETag policy."
>
> My comment was about policy implementation, not policy configuration.
>
> Do you expect the method to generate ETags to be configurable in most imp=
lementations? Is that the case among common HTTP servers today? (That's not=
 rhetorical--I don't know the answer.) And even if it is, is there a risk t=
hat there won't be a common selection between implementations? It doesn't h=
elp to tell an administrator to select a certain policy unless his software=
 can actually do it. If there was a mandatory-to-implement policy, then tha=
t shouldn't happen.

Apache has an option that fits. I don't know about other server
software. obviously, this would need to be added for them to be able
to be Metalink servers if they don't have it. but, at least initially,
I don't expect every web server to easily be able to also be a
Metalink server without changes.

>
> [...]
>
>>
>>> -- section 10.2:
>>>
>>> What can an implementor do to mitigate spoofing?
>>
>> nothing, I'm aware of?
>>
>> added:
>> As with all downloads, users should only download from trusted sources.
>
> Hmm. What does "trusted" mean in context? Does that have implications on =
authentication of the source and integrity protection of the download sessi=
on? (i.e. TLS)?

I'm not sure how to word this. a non-TLS source like download.com
could be more trusted than a TLS one from denialofserviceRus.com

> [...]
>
>>> --- Nits/editorial comments:
>>>
>>> -- section 2, 4th paragraph: "HTTP mirror servers SHOULD share the same=
 ETag policy as the originating Metalink server."
>>
>> what's wrong here?
>
> Oops, sorry, cut-and-paste error. My comment was "This seems redundant wi=
th a similar statement in the previous paragraph"

there is a paragraph on the Metalink server, mirror server, and
client. I think it's ok to reiterate.

paragraph 3 on Metalink servers:
Metalink servers and their associated mirror servers SHOULD all share
the same ETag policy.

paragraph 4 on Mirror servers:
HTTP mirror servers SHOULD share the same ETag policy as the
originating Metalink server.

>
> [...]
>
>
>>> -- section 7.1.1, general:
>>>
>>> This whole section switches to an almost stream-of-consciousness style.=
 It has very long sentences with many comma separated clauses that are hard=
 to follow. It really needs to be rewritten to be more readable and precise=
.
>>
>> hahaha :)
>>
>> this is my fault as a bad editor & a non-native English speaker co-autho=
r.
>>
>
> On reflection, I think my comment was a little harsh. But another pass wi=
th some attention to style in the section would help.

no, it needed work.

here's our next pass
http://tools.ietf.org//rfcdiff?url1=3Dhttp://tools.ietf.org/id/draft-bryan-=
metalinkhttp-20.txt&url2=3Dhttp://www.metalinker.org/test/mh/draft-bryan-me=
talinkhttp-21.txt

>>> -- section 7.1.1, paragraph 3:
>>>
>>> Paragraph seems self contradictory. How is guaranteeing correct content=
 different than verifying integrity?
>>
>> the server sends the correct content =A0but there can be errors during t=
ransfer.
>>
>> maybe this is not explicit enough. might need to condense some of this d=
own.
>
>> earlier we state:
>> Error detection requires Instance Digests to detect errors in transfer
>> after the transfers have completed.
>>
>
> I think a rewording would help, as I took "guaranteeing correct content" =
to mean "guaranteeing the client receives correct content" rather than "gua=
ranteeing the server sends correct content".

"ETags can not be used for verifying the integrity of the received
content. If the ETag given by the mirror server matches the ETag given
by the Metalink server, then the Metalink client assumes the responses
are valid for that object. "


>>> -- section 7.1.2, 2nd paragraph: "If the object cryptographic hash does=
 not match the Instance Digest then fetch the Metalink/XML if available, wh=
ere partial file cryptographic hashes can be found, allowing detection of w=
hich server returned incorrect data."
>>>
>>> I can't parse this sentence.
>>
>> =A0 If the cryptographic hash of the object does not match the Instance
>> =A0 Digest from the Metalink server, then the client SHOULD fetch the
>> =A0 Metalink/XML (if available) that could contain partial file
>> =A0 cryptographic hashes which will allow detection of which mirror
>> =A0 server returned incorrect data. =A0Metalink clients SHOULD figure ou=
t
>> =A0 what ranges of the downloaded data can be recovered and what needs t=
o
>> =A0 be fetched again.
>
> That's better, but how about breaking it up a bit more, as in the followi=
ng:
>
> " =A0If the cryptographic hash of the object does not match the Instance =
Digest from the Metalink server, then the client SHOULD fetch the Metalink/=
XML (if available). This may contain partial file cryptographic hashes whic=
h will allow detection of which mirror server returned incorrect data. =A0M=
etalink clients SHOULD use the Metalink/XML data to figure out what ranges =
of the downloaded data can be recovered and what needs to be fetched again.=
 "
>

perfect, thanks!




--=20
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
=A0 )) Easier, More Reliable, Self Healing Downloads

From bmanning@sfc.keio.ac.jp  Fri Feb 25 13:33:46 2011
Return-Path: <bmanning@sfc.keio.ac.jp>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE8453A6A48 for <ietf@core3.amsl.com>; Fri, 25 Feb 2011 13:33:46 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z4onA2EATGOr for <ietf@core3.amsl.com>; Fri, 25 Feb 2011 13:33:45 -0800 (PST)
Received: from mail-gw2.sfc.keio.ac.jp (mail-gw2.sfc.keio.ac.jp [133.27.4.128]) by core3.amsl.com (Postfix) with ESMTP id A02EA3A6A44 for <ietf@ietf.org>; Fri, 25 Feb 2011 13:33:45 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAI6vZ02FGwXL/2dsb2JhbACmPHS9GYVgBIUQiks
X-IronPort-AV: E=Sophos;i="4.62,227,1297004400"; d="scan'208";a="10256721"
Received: from imap03.sfc.keio.ac.jp ([133.27.5.203]) by mail-gw2.sfc.keio.ac.jp with ESMTP; 26 Feb 2011 06:34:37 +0900
Received: from [198.32.6.183] by imap03.sfc.keio.ac.jp with esmtpsa (Exim 4.69 #1 (Debian-submission)) id 1Pt5J7-0000qv-6s; Sat, 26 Feb 2011 06:34:37 +0900
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: What If....
From: bill manning <bmanning@sfc.keio.ac.jp>
Date: Fri, 25 Feb 2011 13:34:29 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <2A4D7751-CAD5-4B40-B827-94E8BCD296F6@sfc.keio.ac.jp>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Mailman-Approved-At: Mon, 28 Feb 2011 07:43:26 -0800
Cc: arin-discuss@arin.net, nanog@nanog.org, bill manning <bmanning@sfc.keio.ac.jp>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2011 21:37:16 -0000

The IANA function was split?

http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf


--bill

From mstjohns@comcast.net  Mon Feb 28 08:07:45 2011
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A63583A6C2A for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 08:07:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level: 
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qd6wT6YOnauH for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 08:07:45 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by core3.amsl.com (Postfix) with ESMTP id C906E3A6A96 for <ietf@ietf.org>; Mon, 28 Feb 2011 08:07:44 -0800 (PST)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta09.westchester.pa.mail.comcast.net with comcast id DU5A1g0061wpRvQ59U8m8p; Mon, 28 Feb 2011 16:08:46 +0000
Received: from Mike-PC3.comcast.net ([208.54.35.58]) by omta18.westchester.pa.mail.comcast.net with comcast id DU8S1g00b1FFgeg3eU8Wp0; Mon, 28 Feb 2011 16:08:44 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 28 Feb 2011 11:08:23 -0500
To: Bob Hinden <bob.hinden@gmail.com>,Yoav Nir <ynir@checkpoint.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: XKCD - Nanobots
In-Reply-To: <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com>
References: <4D6B4F86.8080007@qualcomm.com> <99EEB83B-7A1E-4E7B-BDC7-AAC15B1D40FE@gmail.com> <E6BE1FB3-66FD-4F33-B64C-0AB6DF75759B@checkpoint.com> <0E5A493F-C8DC-43C3-884E-4F816C1DFDE0@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110228160744.C906E3A6A96@core3.amsl.com>
Cc: Pete Resnick <presnick@qualcomm.com>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 16:07:45 -0000

At 04:45 AM 2/28/2011, Bob Hinden wrote:
>Yoav,
>
>> Yes, but I think the nanobots are supposed to devour the entire earth, so it's volume that counts. The volume is about 1x10^21 m^3. So 40% is 4 x 10^20 m^3.  
>
>But they start from the outside and eat down.  This causes the surface area to decrease and less nonobots are required.  Or to put it another way, the don't have to replace the earth with nonbots :-)

Umm... are you ignoring conservation of mass?  Or are you assuming perfect conversion to energy?  If the latter, I would expect the nanobots to melt - actually vaporize or turn into plasma.  If the former, I'd expect replacing the earth with nanobots.  Or at least something with some mass and volume. 



>> 
>> 3.4 x 10^38 nanobots comes to 8.5 x 10^17 nanobots per m^3, or about 1.17 microns^3 per nanobot.
>> 
>> Sounds about right.
>
>This must have been one of the design goals :-)
>
>Bob
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf



From dworley@avaya.com  Mon Feb 28 08:20:28 2011
Return-Path: <dworley@avaya.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 771103A6A04 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 08:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVwRADVT5NSL for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 08:20:25 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (p-us1-iereast-outbound-tmp.us1.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id CACF53A6A08 for <ietf@ietf.org>; Mon, 28 Feb 2011 08:20:19 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMJZa02HCzI1/2dsb2JhbACmR3SjZAKYc4VhBIUQimU
X-IronPort-AV: E=Sophos;i="4.62,240,1297054800"; d="scan'208";a="61143732"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 28 Feb 2011 11:21:11 -0500
X-IronPort-AV: E=Sophos;i="4.62,240,1297054800"; d="scan'208";a="607293411"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 28 Feb 2011 11:21:10 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.187]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 28 Feb 2011 11:21:10 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Shane Kerr <shane@isc.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 28 Feb 2011 11:19:35 -0500
Subject: RE: Where to find IETF recommendations?
Thread-Topic: Where to find IETF recommendations?
Thread-Index: AcvXLEEOjmzSn0iJTZyjZx7rhVDoBwANwkyr
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220B5C150C@DC-US1MBEX4.global.avaya.com>
References: <1298886297.2266.2.camel@shane-desktop>
In-Reply-To: <1298886297.2266.2.camel@shane-desktop>
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 16:20:28 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Shane Kerr=
 [shane@isc.org]

My question is... how is this advice expected to trickle out into actual
use? There are more than 6000 RFCs, and they don't seem to be organized
in a useful way that I can find.
_______________________________________________

In practice, you have to be "up on the field", to be part of the ongoing di=
scussions.  Other standards organizations are better organized about publis=
hing their recommendations, but always, in practice, you have to be aware o=
f what is being done by the systems you need to interoperate with.

Dale

From tglassey@earthlink.net  Mon Feb 28 08:36:18 2011
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 900BC3A69F9 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 08:36:18 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwMqFjQyfAGH for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 08:36:17 -0800 (PST)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 842B03A687C for <ietf@ietf.org>; Mon, 28 Feb 2011 08:36:17 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=dcslZrExCD0CLRv/MJiDYAXM189L9zFeRl27ZdeemLYh0tSdXii+dz6XZJ5noZKM; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Opacus-Archived:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.100]) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Pu662-0003GW-3L for ietf@ietf.org; Mon, 28 Feb 2011 11:37:18 -0500
Message-ID: <4D6BCF3F.2040800@earthlink.net>
Date: Mon, 28 Feb 2011 08:37:19 -0800
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: What If....
References: <2A4D7751-CAD5-4B40-B827-94E8BCD296F6@sfc.keio.ac.jp>
In-Reply-To: <2A4D7751-CAD5-4B40-B827-94E8BCD296F6@sfc.keio.ac.jp>
X-Opacus-Archived: none
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec797d050a09f6a3a6a6fac7651f7752f624350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 207.111.209.5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 16:36:18 -0000

On 2/25/2011 1:34 PM, bill manning wrote:
> The IANA function was split?
>
> http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf
>
Then the IETF will find its world more tightly constrained (as it should 
be...).

Todd

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


From fluffy@cisco.com  Mon Feb 28 09:23:42 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0DD63A6A1A; Mon, 28 Feb 2011 09:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.541
X-Spam-Level: 
X-Spam-Status: No, score=-110.541 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nVizgF5aX7Ml; Mon, 28 Feb 2011 09:23:41 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 167FF3A6957; Mon, 28 Feb 2011 09:23:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=13384; q=dns/txt; s=iport; t=1298913882; x=1300123482; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=JEq0T1pMrBJcpOptWMXc2TDcjNRAIssqFyxYpPnUQ3o=; b=kY47AiuUDP0xF02Sq88xbNEWLsbjT6zHmb72ZweoiERJHl7ADHXXBvfh d4I1OoMcfxocv4HHe5ApN/fygCOvmS+W6h28JO/INGKKAAMLDVqyjPBhT FaBeSBY1MIcvkfijB8vFN+w41jCUO/zHOobQwwZ4wuF0KxCMayMoJYOhe 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMRoa02rRN+K/2dsb2JhbACmR3ShAps5hWEEhQ+HDYM+
X-IronPort-AV: E=Sophos;i="4.62,241,1297036800";  d="scan'208,217";a="411258799"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 28 Feb 2011 17:24:41 +0000
Received: from [192.168.4.100] (rcdn-fluffy-8712.cisco.com [10.99.9.19]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p1SHOedb014373; Mon, 28 Feb 2011 17:24:40 GMT
Subject: Re: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-631767159
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D505DC1.40002@nostrum.com>
Date: Mon, 28 Feb 2011 10:27:10 -0700
Message-Id: <3F6F6B2C-E28F-4865-9CE7-19479ADCE59E@cisco.com>
References: <20110207170250.4107.67897.idtracker@localhost> <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com> <4D505DC1.40002@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.1082)
Cc: IESG IESG <iesg@ietf.org>, "ietf@ietf.org IETF" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 17:23:43 -0000

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


On Feb 7, 2011, at 2:01 PM, Adam Roach wrote:

> On 2/7/11 12:44 PM, Cullen Jennings wrote:
>> I was somewhat surprised to see this back in LC. I am still not aware =
of any use case where this actually helps. I searched the IETF and WG =
lists for email with the subject draft-ietf-sipcore-199 and I do not see =
a single email that suggests there is support for this draft or the =
changes in it since the previous LC.
>>=20
>> This draft has no use that I understand how it helps - it is at best =
a very limited optimization. The SIP standards is already too =
complicated with too many extensions. I believe this draft makes SIP =
worse.Thought the draft mandates that systems need to work even when the =
199 are lost, I do not think that is how the proponents of the work =
intent to use. I could be very wrong but I presume that people intent to =
use to control middle boxes that control media gates. It's broken for =
that but given that is not discussed in the draft, it's hard to discuss =
how it is broken and what would be needed to fix it.
>>=20
>> I do not support publishing this draft as standards track without =
actual WG discussion on what the problem is this draft solves and if =
there is WG consensus that problem is worth solving.
>=20
> Cullen:
>=20
> Speaking as a chair of SIPCORE, I would like to clarify a minor point. =
Although it may not have been your intention, your message can be read =
as implying that the SIPCORE chairs and/or the RAI area directors have =
decided to move this document forward without community input.

It was really just sloppy overly fast writing on my part - I did not =
mean to imply that. The total time I'm willing to spend on this draft is =
pretty minimal.

>=20
> For the benefit of those on this mailing list who were not involved in =
the earlier stages of this document's progress: the initial community =
input on whether to pursue the problem solved by this draft was taken at =
the face-to-face SIPPING meeting during IETF 69. In particular, the =
minutes for that meeting reflect: "Hum... in support of working on this =
problem."
>=20
> In April of 2008, the requirements document was handed over from =
SIPPING to the SIP working group for working on actual protocol =
mechanism. (The SIP change process at the time limited core protocol =
changes to the SIP working group, requiring a change in venue).
>=20
> Within the SIP working group, there were at least 316 message in 38 =
different threads on the protocol document over the one year period =
spanning April 2008 to April 2009. This period included a two-week long =
Working Group Last Call period in November of 2008.
>=20
> In April of 2009, the RAI area underwent a reorganization, which =
resulted in the conclusion of the SIP working group. As part of the =
chartering of the SIPCORE working group, this document (and its =
associated milestone) was transferred to the SIPCORE WG.
>=20
> In January of 2010, the document entered IETF last call for the first =
time. During IETF balloting, certain issues were identified by the IESG, =
and balloted as a "DISCUSS" position. Over the course of 2010, the =
document's author worked with the RAI ADs to address these issues to the =
satisfaction of the currently seated IESG.

 I thought we were still in middle on conversation about what to do =
about any this stuff - thus my surprise it was in LC again. Last email I =
had was you in May of asking Christer if he was going to reply. He =
eventual did but it did resolve what this was use for. It did point out =
that no one was complaining about it. That caused me to send an email in =
June that said=20

"Silence is not consent - the WG does not care about this and there is =
not consensus that it is useful, what it is useful for, or that it =
should be published. I'd be happy to shown to be wrong as I, like I =
suspect many others, don't care too much one way or the other. "

After that, other than people saying the IETF had to do this because =
3GPP had already made it mandatory, I had not heard any more about it.=20=



> As a result of these conversations, a technical issue involving =
interaction with another SIP extension mechanism was identified, and =
brought back to the SIPCORE working group. A resolution to the issue was =
identified in early December 2010, and a revised version of the document =
was produced to reflect this resolution.

Uh, you mean the one where the total traffic seems to be=20

Chair (Paul) proposed the WG should see if the WG was OK with it
Christer (Author) said he was OK with even though he did not really like =
it
Keith proposed some text without saying if he actually liked any of it =
or not=20
Christer (Author) said he was OK with it=20

And no one else said anything. Hopefully I failed to find the email, or =
lost it, or am just confused, but I have a hard time imaging how that =
looks like consensus in one of the largest WG in the IETF.=20


>=20
> At every step of this process, the IETF, RAI, and SIP community has =
opportunity for involvement. The volume of discussion demonstrates a =
non-trivial interest in this mechanism.

Hmm ... I 100% agree there has been opportunity for involvement. I am =
talking about the actually involvement since the previous LC over a year =
ago. In that year, there looks to be mostly silence about any of the =
issues or changes to the draft. I did not go do a good search but when I =
searched for the draft name, I'm not seeing much discussion. If you tell =
me 10 people were actively engaged in the last year and support these =
changes, I'm happy to agree I am in the rough in the consensus and =
ignore the whole thing. But if you are telling me that no one objected, =
then I do not believe silence is the same as consensus.=20

>=20
> /a

Anyways - I this is very much on my low priority list - I have not gone =
back and looked carefully at the previous discussions.=20


--Apple-Mail-1-631767159
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; =
"><br><div><div>On Feb 7, 2011, at 2:01 PM, Adam Roach wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
2/7/11 12:44 PM, Cullen Jennings wrote:<br><blockquote type=3D"cite">I =
was somewhat surprised to see this back in LC. I am still not aware of =
any use case where this actually helps. I searched the IETF and WG lists =
for email with the subject draft-ietf-sipcore-199 and I do not see a =
single email that suggests there is support for this draft or the =
changes in it since the previous LC.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">This draft has =
no use that I understand how it helps - it is at best a very limited =
optimization. The SIP standards is already too complicated with too many =
extensions. I believe this draft makes SIP worse.Thought the draft =
mandates that systems need to work even when the 199 are lost, I do not =
think that is how the proponents of the work intent to use. I could be =
very wrong but I presume that people intent to use to control middle =
boxes that control media gates. It's broken for that but given that is =
not discussed in the draft, it's hard to discuss how it is broken and =
what would be needed to fix it.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I do not =
support publishing this draft as standards track without actual WG =
discussion on what the problem is this draft solves and if there is WG =
consensus that problem is worth =
solving.<br></blockquote><br>Cullen:<br><br>Speaking as a chair of =
SIPCORE, I would like to clarify a minor point. Although it may not have =
been your intention, your message can be read as implying that the =
SIPCORE chairs and/or the RAI area directors have decided to move this =
document forward without community =
input.<br></div></blockquote><div><br></div>It was really just sloppy =
overly fast writing on my part - I did not mean to imply that. The total =
time I'm willing to spend on this draft is pretty =
minimal.</div><div><br><blockquote type=3D"cite"><div><br>For the =
benefit of those on this mailing list who were not involved in the =
earlier stages of this document's progress: the initial community input =
on whether to pursue the problem solved by this draft was taken at the =
face-to-face SIPPING meeting during IETF 69. In particular, the minutes =
for that meeting reflect: "Hum... in support of working on this =
problem."<br><br>In April of 2008, the requirements document was handed =
over from SIPPING to the SIP working group for working on actual =
protocol mechanism. (The SIP change process at the time limited core =
protocol changes to the SIP working group, requiring a change in =
venue).<br><br>Within the SIP working group, there were at least 316 =
message in 38 different threads on the protocol document over the one =
year period spanning April 2008 to April 2009. This period included a =
two-week long Working Group Last Call period in November of =
2008.<br><br>In April of 2009, the RAI area underwent a reorganization, =
which resulted in the conclusion of the SIP working group. As part of =
the chartering of the SIPCORE working group, this document (and its =
associated milestone) was transferred to the SIPCORE WG.<br><br>In =
January of 2010, the document entered IETF last call for the first time. =
During IETF balloting, certain issues were identified by the IESG, and =
balloted as a "DISCUSS" position. Over the course of 2010, the =
document's author worked with the RAI ADs to address these issues to the =
satisfaction of the currently seated IESG. =
</div></blockquote><div><br></div><div>&nbsp;I thought we were still in =
middle on conversation about what to do about any this stuff - thus my =
surprise it was in LC again. Last email I had was you in May =
of&nbsp;asking Christer if he was going to reply. He eventual did but it =
did resolve what this was use for. It did point out that no one was =
complaining about it. That caused me to send an email in June that =
said&nbsp;</div><div><br></div><div>"Silence is not consent - the WG =
does not care about this and there is not consensus that it is useful, =
what it is useful for, or that it should be published. I'd be&nbsp;happy =
to shown to be wrong as I, like I suspect many others, don't care too =
much one way or the other. <b>"</b></div><div><b><br></b></div>After =
that, other than people saying the IETF had to do this because 3GPP had =
already made it mandatory, I had not heard any more about =
it.&nbsp;</div><div><br></div><div><br><blockquote type=3D"cite"><div>As =
a result of these conversations, a technical issue involving interaction =
with another SIP extension mechanism was identified, and brought back to =
the SIPCORE working group. A resolution to the issue was identified in =
early December 2010, and a revised version of the document was produced =
to reflect this resolution.<br></div></blockquote><div><br></div>Uh, you =
mean the one where the total traffic seems to =
be&nbsp;</div><div><br></div><div>Chair (Paul) proposed the WG should =
see if the WG was OK with it</div><div>Christer (Author) said he was OK =
with even though he did not really like it</div><div>Keith proposed some =
text without saying if he actually liked any of it or =
not&nbsp;</div><div>Christer (Author) said he was OK with =
it&nbsp;</div><div><br></div><div>And no one else said anything. =
Hopefully I failed to find the email, or lost it, or am just confused, =
but I have a hard time imaging how that looks like consensus in one of =
the largest WG in the =
IETF.&nbsp;</div><div><br></div><div><br><blockquote =
type=3D"cite"><div><br>At every step of this process, the IETF, RAI, and =
SIP community has opportunity for involvement. The volume of discussion =
demonstrates a non-trivial interest in this =
mechanism.<br></div></blockquote><div><br></div>Hmm ... I 100% agree =
there has been opportunity for involvement. I am talking about the =
actually involvement since the previous LC over a year ago. In that =
year, there looks to be mostly silence about any of the issues or =
changes to the draft. I did not go do a good search but when I searched =
for the draft name, I'm not seeing much discussion. If you tell me 10 =
people were actively engaged in the last year and support these changes, =
I'm happy to agree I am in the rough in the consensus and ignore the =
whole thing. But if you are telling me that no one objected, then I do =
not believe silence is the same as =
consensus.&nbsp;</div><div><br><blockquote =
type=3D"cite"><div><br>/a<br></div></blockquote><br></div><div>Anyways - =
I this is very much on my low priority list - I have not gone back and =
looked carefully at the previous =
discussions.&nbsp;</div><br></body></html>=

--Apple-Mail-1-631767159--

From rbarnes@bbn.com  Mon Feb 28 10:29:50 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0C6A3A6C2F for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 10:29:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7VYiBUxTUZaU for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 10:29:50 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id 1FB413A6C49 for <ietf@ietf.org>; Mon, 28 Feb 2011 10:29:50 -0800 (PST)
Received: from ros-dhcp192-1-51-78.bbn.com ([192.1.51.78]:58102) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Pu7ru-000N9K-2O; Mon, 28 Feb 2011 13:30:50 -0500
Subject: Re: Where to find IETF recommendations?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <1298889312.4217.5.camel@shane-desktop>
Date: Mon, 28 Feb 2011 13:30:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7086EA0D-1C1E-491C-AE5E-3543E7906BDD@bbn.com>
References: <1298886297.2266.2.camel@shane-desktop> <FB46718F-2DC8-4658-A668-61EE0BF11F08@gmail.com> <1298889312.4217.5.camel@shane-desktop>
To: Shane Kerr <shane@isc.org>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 18:29:51 -0000

As far as I know, what you're looking for doesn't exist, although it =
would probably be good if it did!

One thing that does crop up here and there are "hitchhiker's guide" =
RFCs, such as this one:
<http://tools.ietf.org/html/rfc5411>

Beyond that, the best way I know of to look for IETF recommendations on =
a subject is using the search feature on the tools pages:
<http://tools.ietf.org/html/>




On Feb 28, 2011, at 5:35 AM, Shane Kerr wrote:

> Bob,
>=20
> Are recommendations actually published as BCP?
>=20
> I only see one BCP with "IPv6" in the title, published back in 2004.
> Compared to this, the ipv6ops working group alone has produced dozens =
of
> informational RFCs:
>=20
> https://datatracker.ietf.org/wg/v6ops/
>=20
> At least one of these are even explicitly recommendations:
>=20
> https://datatracker.ietf.org/doc/rfc4890/
>=20
> Some are targeted at protocol developers, some at vendors, some at
> operators. It's quite a mixed bag. :)
>=20
> I'm not complaining, I just want to know if I am missing an obvious
> place.
>=20
> --
> Shane
>=20
> On Mon, 2011-02-28 at 12:10 +0200, Bob Hinden wrote:
>> Shane,
>>=20
>> Like this one, aren't recommendations usually published as BCPs?
>>=20
>> Bob
>>=20
>>=20
>> On Feb 28, 2011, at 11:44 AM, Shane Kerr wrote:
>>=20
>>> All,
>>>=20
>>> I just happened to notice this document on ietf-announce today:
>>>=20
>>> =
http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommen=
dations/
>>>=20
>>> It seems quite reasonable.
>>>=20
>>> My question is... how is this advice expected to trickle out into =
actual
>>> use? There are more than 6000 RFCs, and they don't seem to be =
organized
>>> in a useful way that I can find.
>>>=20
>>> I ask because I was going to forward this to an IPv6 operations =
list,
>>> and thought "hm... what about the rest?" and I realized I did not =
know,
>>> and did not even know how to find out.
>>>=20
>>> Any advice would be appreciated. Thanks!
>>>=20
>>> --
>>> Shane
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From dwing@cisco.com  Mon Feb 28 10:46:26 2011
Return-Path: <dwing@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB1183A6C68 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 10:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.502
X-Spam-Level: 
X-Spam-Status: No, score=-110.502 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9iCgxqeUAVB for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 10:46:25 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A8CFF3A6C49 for <ietf@ietf.org>; Mon, 28 Feb 2011 10:46:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=167; q=dns/txt; s=iport; t=1298918847; x=1300128447; h=from:to:references:in-reply-to:subject:date:message-id: mime-version:content-transfer-encoding; bh=m1lLWjrO1Q53yeJS3BKhvqJd51DviWLt+qDEKfRH4mE=; b=Q6zeYp+o4SN3p8qInu1TvA2pMDmQCv+aGGbhjkoKbRVpuezCBhOD0tF0 7L+MNw1PRKbS8/nTCoZoA8VegfNseJ50dEmLNsllGnn8ibNUht66cvzUQ yIf4kIlOPMHw80ALOkyD2u92rGApnNcCRtLuOOH95Yfn8UOjBXYw62+o1 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOt8a02rR7Ht/2dsb2JhbACZWYxvdKA9m0qFYQSFDw
X-IronPort-AV: E=Sophos;i="4.62,241,1297036800"; d="scan'208";a="266581389"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 28 Feb 2011 18:47:26 +0000
Received: from dwingWS ([10.32.240.194]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p1SIlQE5025561; Mon, 28 Feb 2011 18:47:26 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Pete Resnick'" <presnick@qualcomm.com>, <ietf@ietf.org>
References: <4D6B4F86.8080007@qualcomm.com>
In-Reply-To: <4D6B4F86.8080007@qualcomm.com>
Subject: RE: XKCD - Nanobots
Date: Mon, 28 Feb 2011 10:47:26 -0800
Message-ID: <00fd01cbd777$f1b370a0$d51a51e0$@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: AcvXGbWJbPGvdPgxQz+2CwpYWfXfcgAXhjRQ
Content-Language: en-us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 18:46:27 -0000

> I'm sorry, but how could this *not* be posted to the IETF list?
> 
> <http://xkcd.com/865/>

It appears www.xkcd.com added its AAAA on the same day, too.

-d



From llynch@civil-tongue.net  Mon Feb 28 11:31:58 2011
Return-Path: <llynch@civil-tongue.net>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 976A83A6C5D for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 11:31:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.304
X-Spam-Level: 
X-Spam-Status: No, score=-101.304 tagged_above=-999 required=5 tests=[AWL=0.695, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lr65BNS0BAh3 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 11:31:57 -0800 (PST)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) by core3.amsl.com (Postfix) with ESMTP id 4DD063A6A1E for <ietf@ietf.org>; Mon, 28 Feb 2011 11:31:57 -0800 (PST)
Received: from hiroshima.bogus.com (localhost [127.0.0.1]) by hiroshima.bogus.com (8.14.3/8.14.3) with ESMTP id p1SJWeQY087868 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 28 Feb 2011 11:32:40 -0800 (PST) (envelope-from llynch@civil-tongue.net)
Received: from localhost (llynch@localhost) by hiroshima.bogus.com (8.14.3/8.14.3/Submit) with ESMTP id p1SJWeUu087865; Mon, 28 Feb 2011 11:32:40 -0800 (PST) (envelope-from llynch@civil-tongue.net)
Date: Mon, 28 Feb 2011 11:32:40 -0800 (PST)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: Where to find IETF recommendations?
In-Reply-To: <7086EA0D-1C1E-491C-AE5E-3543E7906BDD@bbn.com>
Message-ID: <alpine.BSF.2.00.1102281126060.63461@hiroshima.bogus.com>
References: <1298886297.2266.2.camel@shane-desktop> <FB46718F-2DC8-4658-A668-61EE0BF11F08@gmail.com> <1298889312.4217.5.camel@shane-desktop> <7086EA0D-1C1E-491C-AE5E-3543E7906BDD@bbn.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 19:31:58 -0000

On Mon, 28 Feb 2011, Richard L. Barnes wrote:

> As far as I know, what you're looking for doesn't exist, although it would probably be good if it did!
>
> One thing that does crop up here and there are "hitchhiker's guide" RFCs, such as this one:
> <http://tools.ietf.org/html/rfc5411>
>
> Beyond that, the best way I know of to look for IETF recommendations on a subject is using the search feature on the tools pages:
> <http://tools.ietf.org/html/>
>

Although they can quite intimidating, I'm fond the the dependency
graphs the accompany the WG pages on tools.ietf.org The link is
at the very bottom of the page - http://tools.ietf.org/wg/v6ops/

Take a look at:
http://www.fenron.net/~fenner/ietf/deps/viz/v6ops.pdf

kind of makes your head hurt.

- Lucy

>
>
> On Feb 28, 2011, at 5:35 AM, Shane Kerr wrote:
>
>> Bob,
>>
>> Are recommendations actually published as BCP?
>>
>> I only see one BCP with "IPv6" in the title, published back in 2004.
>> Compared to this, the ipv6ops working group alone has produced dozens of
>> informational RFCs:
>>
>> https://datatracker.ietf.org/wg/v6ops/
>>
>> At least one of these are even explicitly recommendations:
>>
>> https://datatracker.ietf.org/doc/rfc4890/
>>
>> Some are targeted at protocol developers, some at vendors, some at
>> operators. It's quite a mixed bag. :)
>>
>> I'm not complaining, I just want to know if I am missing an obvious
>> place.
>>
>> --
>> Shane
>>
>> On Mon, 2011-02-28 at 12:10 +0200, Bob Hinden wrote:
>>> Shane,
>>>
>>> Like this one, aren't recommendations usually published as BCPs?
>>>
>>> Bob
>>>
>>>
>>> On Feb 28, 2011, at 11:44 AM, Shane Kerr wrote:
>>>
>>>> All,
>>>>
>>>> I just happened to notice this document on ietf-announce today:
>>>>
>>>> http://datatracker.ietf.org/doc/draft-ietf-intarea-server-logging-recommendations/
>>>>
>>>> It seems quite reasonable.
>>>>
>>>> My question is... how is this advice expected to trickle out into actual
>>>> use? There are more than 6000 RFCs, and they don't seem to be organized
>>>> in a useful way that I can find.
>>>>
>>>> I ask because I was going to forward this to an IPv6 operations list,
>>>> and thought "hm... what about the rest?" and I realized I did not know,
>>>> and did not even know how to find out.
>>>>
>>>> Any advice would be appreciated. Thanks!
>>>>
>>>> --
>>>> Shane
>>>>
>>>> _______________________________________________
>>>> 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 adam@nostrum.com  Mon Feb 28 11:33:31 2011
Return-Path: <adam@nostrum.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 051BA3A6C57; Mon, 28 Feb 2011 11:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-rxvKqnaVx5; Mon, 28 Feb 2011 11:33:30 -0800 (PST)
Received: from nostrum.com (shaman.nostrum.com [72.232.179.90]) by core3.amsl.com (Postfix) with ESMTP id DEBA03A6A14; Mon, 28 Feb 2011 11:33:29 -0800 (PST)
Received: from dn3-228.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 p1SJWiMh053794 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 28 Feb 2011 13:32:44 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D6BF85B.2040108@nostrum.com>
Date: Mon, 28 Feb 2011 13:32:43 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Last Call: <draft-ietf-sipcore-199-05.txt> (Session Initiation Protocol (SIP) Response Code for Indication of Terminated	Dialog) to Proposed Standard
References: <20110207170250.4107.67897.idtracker@localhost> <3A723B49-1CCB-4E55-8122-FBF58F30D6AF@cisco.com> <4D505DC1.40002@nostrum.com> <3F6F6B2C-E28F-4865-9CE7-19479ADCE59E@cisco.com>
In-Reply-To: <3F6F6B2C-E28F-4865-9CE7-19479ADCE59E@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: IESG IESG <iesg@ietf.org>, "ietf@ietf.org IETF" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 19:33:31 -0000

On 2/28/11 11:27 AM, Cullen Jennings wrote:
>
> On Feb 7, 2011, at 2:01 PM, Adam Roach wrote:
>
>>
>> At every step of this process, the IETF, RAI, and SIP community has 
>> opportunity for involvement. The volume of discussion demonstrates a 
>> non-trivial interest in this mechanism.
>
> Hmm ... I 100% agree there has been opportunity for involvement. I am 
> talking about the actually involvement since the previous LC over a 
> year ago.

I would imagine that actual working group involvement on any draft after 
IETF last call generally approaches zero. I believe this document is 
rather average in that regard.

> In that year, there looks to be mostly silence about any of the issues 
> or changes to the draft. I did not go do a good search but when I 
> searched for the draft name, I'm not seeing much discussion. If you 
> tell me 10 people were actively engaged in the last year and support 
> these changes, I'm happy to agree I am in the rough in the consensus 
> and ignore the whole thing. But if you are telling me that no one 
> objected, then I do not believe silence is the same as consensus.
>

I'm not trying to tell you that silence is consensus. In this case, 
silence simply indicates that the working group thinks it is finished, 
and hasn't elected to spend additional work on a completed item.

It's my experience that working groups do not generally work on 
documents after they have been passed off to the IESG for publication. 
This document has been in front of the IESG for the past year that you 
reference. The only mailing list traffic that the working group could 
have generated after publication was requested would have been cheering 
from the sidelines, which isn't part of the publication process as I 
understand it.

So, while your request for 10 people who have expressed interest on the 
list list after IETF last call makes no sense, I *can* offer you the 
following list of 35 people who participated in mailing list discussions 
while the draft was still in a working group:

Adam Roach <adam@nostrum.com>
Anders Kristensen <andersk@cisco.com>
Ashish Hsaxena <ashish.hsaxena@wipro.com>
Attila Sipos <attila.sipos@vegastream.com>
Avasarala Ranjit <ranjit@motorola.com>
Bob Penfield <BPenfield@acmepacket.com>
Brett Tate <brett@broadsoft.com>
Christer Holmberg <christer.holmberg@ericsson.com>
Cullen Jennings <fluffy@cisco.com>
Dale Worley <dworley@nortel.com>
Dean Willis <dean.willis@softarmor.com>
Eric Rescorla <ekr@networkresonance.com>
Eric Wang <eric.wangxr@gmail.com>
Francois Audet <audet@nortel.com>
Hadriel Kaplan <HKaplan@acmepacket.com>
Hans Erik van Elburg <ietf.hanserik@gmail.com>
Ian Elz <ian.elz@ericsson.com>
Jeroen van Bemmel <jbemmel@zonnet.nl>
John Elwell <john.elwell@siemens.com>
Juha Heinanen <jh@tutpro.com>
Keith Drage <drage@alcatel-lucent.com>
Martin Dolly <mdolly@att.com>
Paul Kyzivat <pkyzivat@cisco.com>
Robert Sparks <rjsparks@nostrum.com>
Rockson Li <zhengyli@cisco.com>
Sanjay Sinha <sanjsinh@cisco.com>
Serhad Doken <sdoken@qualcomm.com>
Spencer Dawkins <spencer@wonderhamster.org>
Sreeram Kanumuri <sreeramk@qualcomm.com>
Sreerekha Shenoy <sreerekha.shenoy@wipro.com>
Timothy M Dwight <timothy.dwight@verizonbusiness.com>
Tom Taylor <tom.taylor@rogers.com>
Vijay K. Gurbani <vkg@alcatel-lucent.com>
Vikram Chhibber <vikram.chhibber@gmail.com>
Ya Ching Tan <ya-ching.tan@nsn.com>

/a

From brian.e.carpenter@gmail.com  Mon Feb 28 12:35:35 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A1B003A67E2 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 12:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.459
X-Spam-Level: 
X-Spam-Status: No, score=-103.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T849-eW4x5l6 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 12:35:34 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 5F2203A67D6 for <ietf@ietf.org>; Mon, 28 Feb 2011 12:35:34 -0800 (PST)
Received: by fxm15 with SMTP id 15so4205426fxm.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 12:36:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jHjdkj632oVv9T2p4/7pmlJhnIxVOmnKxzLUjPpuKRk=; b=IjLYVbRszRayWIHj/9Nnpa04ZZLhYBCqbJ5g0ZIV+Q++FFeRmb0PX1Hbuql1o6vbZV 6A3Ob2HdwU62ggpXuRvIJbEw+qdhtqb9p33eV3J8nlJgnVnfF6MvCQ+E0nI2HL1VV1vB eMefdHkVJ2yYquOdY0nNdhY7vKrah6r8FX0as=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=WAjBRUxHjM5UN8fRz/cekpcwETerZ9jwH4/XmPi3jDvVrRe2JEGT60NnkrS66OOl3B sdVToJbZONpETDkNbnLWcEyt7M18yqOIOh5qrMKQhaCw07g9K0xAzBVhcM2QtJymB2ne GjL8ejI+unoqum6+acJtPibCdsh+POZRPJMns=
Received: by 10.223.83.142 with SMTP id f14mr2775643fal.0.1298925357233; Mon, 28 Feb 2011 12:35:57 -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 a2sm1786170faw.46.2011.02.28.12.35.53 (version=SSLv3 cipher=OTHER); Mon, 28 Feb 2011 12:35:56 -0800 (PST)
Message-ID: <4D6C0725.3010005@gmail.com>
Date: Tue, 01 Mar 2011 09:35: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: bill manning <bmanning@sfc.keio.ac.jp>
Subject: Re: What If....
References: <2A4D7751-CAD5-4B40-B827-94E8BCD296F6@sfc.keio.ac.jp>
In-Reply-To: <2A4D7751-CAD5-4B40-B827-94E8BCD296F6@sfc.keio.ac.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: arin-discuss@arin.net, nanog@nanog.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 20:35:35 -0000

On 2011-02-26 10:34, bill manning wrote:
> The IANA function was split?

RFC 2860 already did that. It seems to work well.

> http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf

I'm glad to see they are up to date:
"Paper submissions should
include a three and one-half inch
computer diskette in HTML, ASCII,
Word or WordPerfect format (please
specify version)."

   Brian

From drc@virtualized.org  Mon Feb 28 12:54:20 2011
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59A553A6C93 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 12:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.604,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agNoUOzgL+lv for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 12:54:18 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 14C0D3A6C58 for <ietf@ietf.org>; Mon, 28 Feb 2011 12:54:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 6842D1129F36; Mon, 28 Feb 2011 12:55:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS-asMFAF2oM; Mon, 28 Feb 2011 12:55:17 -0800 (PST)
Received: from [10.0.1.2] (cpe-66-91-109-17.hawaii.res.rr.com [66.91.109.17]) by virtualized.org (Postfix) with ESMTP id 5963B1129F28; Mon, 28 Feb 2011 12:55:17 -0800 (PST)
Subject: Re: What If....
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <4D6C0725.3010005@gmail.com>
Date: Mon, 28 Feb 2011 10:55:15 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <72975549-66E4-48BC-AC72-EBB34B1C8C60@virtualized.org>
References: <2A4D7751-CAD5-4B40-B827-94E8BCD296F6@sfc.keio.ac.jp> <4D6C0725.3010005@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 20:54:20 -0000

[cross-posting greatly reduced]

Brian,

On Feb 28, 2011, at 10:35 AM, Brian E Carpenter wrote:
> On 2011-02-26 10:34, bill manning wrote:
>> The IANA function was split?
> RFC 2860 already did that.=20

I believe Bill was suggesting having multiple organizations perform the =
different "IANA functions".

In any event, it would probably be useful if folks who have opinions on =
how the U.S. Department of Commerce, NTIA administers the "IANA =
functions" contract, which (regardless of what RFC 2860 might suggest) =
currently designates who is to "coordinate the assignment of technical =
protocol parameters" (see section 2.2.1.1 of =
http://www.ntia.doc.gov/ntiahome/domainname/iana/ianacontract_081406.pdf) =
make those opinions known via a response to the NoI that Bill mentioned =
(http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf).=


Regards,
-drc


From barryleiba.mailing.lists@gmail.com  Mon Feb 28 15:32:38 2011
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80DD83A6CB4 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 15:32:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.051
X-Spam-Level: 
X-Spam-Status: No, score=-103.051 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEIOh8kG2k3g for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 15:32:37 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id B15D33A6A21 for <ietf@ietf.org>; Mon, 28 Feb 2011 15:32:37 -0800 (PST)
Received: by iwl42 with SMTP id 42so4027982iwl.31 for <ietf@ietf.org>; Mon, 28 Feb 2011 15:33:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=P0KU/30E40U7oZ6UdlDnLaahrTiQPEHThFicfJKhhJQ=; b=cEuvssKtX8QLxBcqVJd/SS08L7mrQpiKC+njdn7v+PuFJPWDPjd902oBFjIqYvN0No o+aflDAvb0ZOkhktH9PTZyj3EbpOdW4LoD/N8V60gnI8OhAGCEdHV0V33dDjQ9wdzNe/ zaIjmYJKc19A63r/ZMmergQ0H0mLgEnduCr6c=
DomainKey-Signature: a=rsa-sha1; c=nofws; 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; b=SQGMP+qduhisWz9UP+lt6u7x6SA6REDVDzXbL6ZzdqMVChZ7HX1af1SYzOncvSNR3j 03Bks5CRijomWTjYHZjnW08u5151rnUvrk6BQXt32DnrTYzaFhkyBPrK2pUNGZQz3cOU 1fgq7fZ+Z1T8XoTXAcGrsitlA2sxaQFT4ZY4Y=
MIME-Version: 1.0
Received: by 10.42.209.78 with SMTP id gf14mr5724140icb.451.1298936019033; Mon, 28 Feb 2011 15:33:39 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.42.229.67 with HTTP; Mon, 28 Feb 2011 15:33:39 -0800 (PST)
In-Reply-To: <20110228224358.16998.39621.idtracker@localhost>
References: <20110228224358.16998.39621.idtracker@localhost>
Date: Mon, 28 Feb 2011 18:33:39 -0500
X-Google-Sender-Auth: WlmuDohYdw8NgFO9dz_9CpOJBhw
Message-ID: <AANLkTimK6bwAsOitt4saPZwwWVDJ0ViSMPDJhnTYvDhS@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-httpbis-content-disp-06.txt> (Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2011 23:32:38 -0000

I'm sorry not to have posted this during WGLC, but I didn't notice it until now:

The document uses the phrase "are advised [to do something]" in two
places (the penultimate paragraph in Section 4.3, and the beginning of
Appendix D).  I suggest that we either switch to 2119 language
("SHOULD [do something]") or insert a sentence into section 2 that
explains the normative meaning of "ADVISED" that we intend (as being
softer than SHOULD).  Even if we want to leave it fluffy, we should
probably make it clear that we're intentionally leaving it fluffy.[1]

Barry

[1] Apologies to Cullen, in case he has trademarked "fluffy".

From johnl@iecc.com  Mon Feb 28 18:59:45 2011
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF9163A6D01 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 18:59:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.825
X-Spam-Level: 
X-Spam-Status: No, score=-110.825 tagged_above=-999 required=5 tests=[AWL=0.374, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyHPDrrJQGCx for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 18:59:45 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id BC9983A6CB0 for <ietf@ietf.org>; Mon, 28 Feb 2011 18:59:44 -0800 (PST)
Received: (qmail 67037 invoked from network); 1 Mar 2011 03:00:46 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 1 Mar 2011 03:00:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=10be2.4d6c615e.k1102; i=johnl@user.iecc.com; bh=CEz7+zEaoxnkiZ4KSjSz9g0cQMUrY7N3cB6dE7BM59E=; b=Vkql3xZE+lHj4QLjje/9Ra6MzdbveZ10ZOCZgat1shBJCwGUT+TlL+spnkpNrx1RkIeIRPBRRW5CLr1xl+MuMWA2RyHnFDcEo4C800F1Liv/Xk6ehIMIdVEW43MB4Sq6xtVdayaC8XqCaumZUV58V372IlrvvHWGlLgVzlH7LdI=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 1 Mar 2011 03:00:45 -0000
Message-ID: <20110301030045.68577.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: What If....
In-Reply-To: <4D6C0725.3010005@gmail.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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 02:59:46 -0000

>> http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf
>
>I'm glad to see they are up to date:

>"Paper submissions should include a three and one-half inch computer
>diskette in HTML, ASCII, Word or WordPerfect format (please specify
>version)."

I think this is their subtle way of telling us that they would greatly
prefer that we submit comments by e-mail.

R's,
John

From ynir@checkpoint.com  Mon Feb 28 22:52:16 2011
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 70DE53A6CEF for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 22:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.567
X-Spam-Level: 
X-Spam-Status: No, score=-10.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mB1kpIXQq5F for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 22:52:15 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id BAFEA3A6A20 for <ietf@ietf.org>; Mon, 28 Feb 2011 22:52:14 -0800 (PST)
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 p216rCDR016447 for <ietf@ietf.org>; Tue, 1 Mar 2011 08:53:16 +0200
X-CheckPoint: {4D6C97ED-0-1B221DC2-FFFF}
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.2.255.0; Tue, 1 Mar 2011 08:53:12 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 1 Mar 2011 08:53:12 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
Date: Tue, 1 Mar 2011 08:53:09 +0200
Subject: Re: What If....
Thread-Topic: What If....
Thread-Index: AcvX3VRv/O6/LUp+S5eHxrXdflYgxw==
Message-ID: <3032415F-D6FA-4743-AE34-98E9D2BC43CB@checkpoint.com>
References: <20110301030045.68577.qmail@joyce.lan>
In-Reply-To: <20110301030045.68577.qmail@joyce.lan>
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.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 06:52:16 -0000

On Mar 1, 2011, at 5:00 AM, John Levine wrote:

>>> http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf
>>=20
>> I'm glad to see they are up to date:
>=20
>> "Paper submissions should include a three and one-half inch computer
>> diskette in HTML, ASCII, Word or WordPerfect format (please specify
>> version)."
>=20
> I think this is their subtle way of telling us that they would greatly
> prefer that we submit comments by e-mail.

Then they should have mandated 7-3/8 by 3-1/4 inch punch-cards and EBCDIC, =
with proper sequence numbers in columns 73-80.



From bachebazy@gmail.com  Mon Feb 28 23:50:26 2011
Return-Path: <bachebazy@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 057D53A6AF9 for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 23:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.837
X-Spam-Level: 
X-Spam-Status: No, score=-1.837 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_SUBJECT=1.762, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAO63PtPFmsP for <ietf@core3.amsl.com>; Mon, 28 Feb 2011 23:50:25 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id 4F05C3A6AC6 for <Ietf@ietf.org>; Mon, 28 Feb 2011 23:50:22 -0800 (PST)
Received: by iyj8 with SMTP id 8so4123841iyj.31 for <Ietf@ietf.org>; Mon, 28 Feb 2011 23:51:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=2zUJKltCjAxtfYoEsRqAjNhqLpisEsS+3pEhfytzW+E=; b=HkHjsFT0s4P49jtesTJErfNYt8T7s3LM0Y+T6W5ShZiBA3bkk+E8BAOE1WCticiL/k 9IfLe2QeP8aFXVfrldSnrvy4wKK/KyFa1bRxfm6iHIej8Tuf7+q1vSbvQifwhs75KZ2A XEgUJS/GC1sAb8R4wI8k27icHD7Tg8Dd12cLE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=S9vUYpG3LYSf6028B3QNczLqv/9B03zre/0AIUiABg7GnIXWV+izq2AaeqrZao46IP edgPSgrysxnjBorzZtkgMluggzK/0+x4hG+Fgl7XacOYdirC4dxJtWCvENaqpogrD7hb Eob09kdJtbGG6WpW1Fp2/tOkBm/pyL4Ok22wo=
MIME-Version: 1.0
Received: by 10.231.30.70 with SMTP id t6mr6133436ibc.165.1298965884661; Mon, 28 Feb 2011 23:51:24 -0800 (PST)
Received: by 10.231.207.65 with HTTP; Mon, 28 Feb 2011 23:51:24 -0800 (PST)
Date: Mon, 28 Feb 2011 23:51:24 -0800
Message-ID: <AANLkTik+Y21SPhq_O=aH0MBOqCf=XOD+RVNbo_Qp3VbB@mail.gmail.com>
Subject: 
From: dirt boy <bachebazy@gmail.com>
To: Ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2011 07:50:26 -0000

I don't want to be a member
thanks
