
From christer.holmberg@ericsson.com  Sat Jan  1 02:17:33 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 0BF3C3A6953; Sat,  1 Jan 2011 02:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.429
X-Spam-Level: 
X-Spam-Status: No, score=-6.429 tagged_above=-999 required=5 tests=[AWL=0.170,  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 HUIT9g1k12tk; Sat,  1 Jan 2011 02:17:32 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id BD5EA3A68CB; Sat,  1 Jan 2011 02:17:31 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-79-4d1effb80e18
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 58.E9.13987.9BFFE1D4; Sat,  1 Jan 2011 11:19:37 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.237]) by esessmw0191.eemea.ericsson.se ([153.88.115.84]) with mapi; Sat, 1 Jan 2011 11:19:36 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>,  "draft-ietf-sipcore-keep.all@tools.ietf.org" <draft-ietf-sipcore-keep.all@tools.ietf.org>
Date: Sat, 1 Jan 2011 11:19:36 +0100
Subject: RE: Gen-ART LC review of draft-ietf-sipcore-keep-10
Thread-Topic: Gen-ART LC review of draft-ietf-sipcore-keep-10
Thread-Index: AcumvqsCWJU+PYLPQjiNraTwI5wq+QC2Ow3j
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05850482F0CD@ESESSCMS0356.eemea.ericsson.se>
References: <4d1a2fda.8a1ce30a.5ad7.58db@mx.google.com>
In-Reply-To: <4d1a2fda.8a1ce30a.5ad7.58db@mx.google.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="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sat, 01 Jan 2011 10:17:33 -0000

Hi Roni,

>Summary: This draft is almost ready for publication as a Standard track RF=
C.
>
>Major issues:
>
>
>Minor issues:
>
>1.  In the document you mention that the keep alive can be negotiated in e=
ach direction. I understand the dialog case, is this true=20
>for the case of registration, if yes how is it done from the registrar. If=
 not true maybe add some text in 4.2.2.

Good point. It is NOT true for the case of registration, when sending of ke=
ep-alives can only be negotiated from the registering party to the registra=
r.

I suggest adding the following text to the end of section 4.2.2:

"NOTE: Sending of keep-alives associated with a registration can only be ne=
gotiated in the direction from the registering SIP entity towards the regis=
trar."

-----

>Nits/editorial comments:
>
>1.  In section 4.1 in the first note =93If a SIP entity has indicated will=
ingness to receive keep-alives from an adjacent SIP entity,=20
>sending of keep-alives towards the same SIP entity needs to be separately =
negotiated=94.=20
>
>Who is the same SIP entity mentioned in the end of the sentence. I assume =
you meant =93towards the adjacent SIP entity=94.

(I assume you mean "Why" instead of "Who")

You are correct. I propose to change to:

"towards that adjacent SIP entity", to make sure that the text is referring=
 to the entity that indicated willingness to send keep-alives, and not some=
 other adjacent SIP entity.

----

>2.  In the first paragraph of 4.3 and 4.4 you use =93must=94 should it be =
=93MUST=94

As far as I know it shall be "must" when referring to something defined in =
another specifiction.

----

>3.  In 4.3 in the third paragraph =93it MUST start to send keep-alives=94 =
change to =93it MUST start sending keep-alives=94

I'll change as suggested.

----

>4.  In figure 2 in the 200 OK response to Alice the VIA is missing.

Correct.

I'll change "Alice: UAC;keep=3D30" to "Via: Alice;keep=3D30".

----

>5.  In section 7.4 third paragraph =93 When Alice receives the response, s=
he determines from her Via header=20
>field that P1 is willing to receive keep-alives associated with the dialog=
.=94 Should be Bob and not P1.

Correct.=20

I'll change as suggested.

----

Thanks for your comments!

Regards,

Christer=

From daedulus@btconnect.com  Sat Jan  1 04:05:07 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 638AE3A6970 for <ietf@core3.amsl.com>; Sat,  1 Jan 2011 04:05:07 -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 9tiv1eX7DRG1 for <ietf@core3.amsl.com>; Sat,  1 Jan 2011 04:05:06 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id CBA1F3A696E for <ietf@ietf.org>; Sat,  1 Jan 2011 04:05:05 -0800 (PST)
Received: from host217-35-228-90.range217-35.btcentralplus.com (HELO pc6) ([217.35.228.90]) by c2beaomr08.btconnect.com with SMTP id BEH67904; Sat, 01 Jan 2011 12:06:15 +0000 (GMT)
Message-ID: <002c01cba9a3$7af60ce0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "John Leslie" <john@jlc.net>, "Richard L. Barnes" <rbarnes@bbn.com>
References: <4D1DEF2E.2070506@dcrocker.net><B69CDF93-5889-4715-BF9D-95D4D4FC47FF@bbn.com> <20101231183843.GB19900@verdi>
Subject: Re: New Year's Exploration:  Changing the Internet's Infrastructure
Date: Sat, 1 Jan 2011 12:03: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.0A0B0301.4D1F18B6.007A, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0208.4D1F18B7.01DE,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 <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, 01 Jan 2011 12:05:07 -0000

----- Original Message ----- 
From: "John Leslie" <john@jlc.net>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Friday, December 31, 2010 7:38 PM
> Richard L. Barnes <rbarnes@bbn.com> wrote:
> > 
> > ISTM that the success of changes to the infrastructure depends on the
> > value those changes deliver to participants in the Internet economy...
> > So the question is rather how many problems there are in the current
> > infrastructure that cause people enough pain to do something.
> 
>    Indeed -- _an_ interesting question... but perhaps not phrased quite
> right: in truth, there are an arbitrarily large number of problems that
> cause _somebody_ enough pain to do something.
> 
> > I think there are at least a couple (improving BGP security, for
> > example), and the number will probably slowly shrink over time,
> > but in the long run, I expect there will ultimately always be a few
> > big things that need to be done that can't be done in end systems.
> 
>    Start from the end: there _will_ be a number of things that shouldn't
> be done in end systems. End systems _really_don't_ want to worry about
> the route packets follow -- at most they want to worry about delay,
> jitter, and order of delivery. But they _will_ work with whatever tools
> are available to ameliorate such worries.
> 
>    The number of problems will most surely _increase_ over time, not
> shrink.
> 
>    BGP security is a _dreadful_ example. It conflates weaknesses of the
> original design with issues entirely out-of-scope of the original design.
> And the original design was seriously flawed by defining algorithms
> instead of meanings.
> 
>    Nonetheless, the example does serve to illustrate a weakness of IETF
> process -- that it's much easier to get traction on small fixes to
> parts of the problem than on migration to a design which avoids the
> problems.
> 
>    BTW, I find it interesting to see how little of the work originating
> in the Security area has gained traction. I wonder to what extent this
> results from:
> 
> - cycles being expended on cross-area reviews;
> 
> - recommending IPsec whether or not it could be deployed for the use;
> 
> - the inherent complexity of key infrastructure?

Security is different in kind from a functional enhancement, of the sort
one sees in successive generations of mobile, in successive versions
of Windows etc.  With these, you pay, you get.

Security you pay for what you don't get, fraud and crime.  Long
experience teaches me that noone will pay until after the security
breach has cost them; only when a bank loses billions to fraud
will a few millions preventing it seem like a good investment.  All
we can do is have the solutions ready in advance of the attacks,
so that when the latter happen, we can say, what a coincidence,
we just happen to have the solution ready and waiting.

Tom Petch
> --
> John Leslie <john@jlc.net>

From hallam@gmail.com  Sat Jan  1 04:41:59 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 BBBEF3A6903 for <ietf@core3.amsl.com>; Sat,  1 Jan 2011 04:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.887
X-Spam-Level: 
X-Spam-Status: No, score=-2.887 tagged_above=-999 required=5 tests=[AWL=-0.289, 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 SjR3ZobjpeTI for <ietf@core3.amsl.com>; Sat,  1 Jan 2011 04:41:58 -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 8EB6C3A6784 for <ietf@ietf.org>; Sat,  1 Jan 2011 04:41:58 -0800 (PST)
Received: by yie19 with SMTP id 19so3267514yie.31 for <ietf@ietf.org>; Sat, 01 Jan 2011 04:44:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=m9FiwdnYYEmC/786bVRikGGyrUls/BJfMv2odQt5r6k=; b=daYBgtg9pCu4I3pX4qQyjmzPpPttmlaq4E6nJ7rZ1jASpKkTwE1UrbfBWI+J6WH9lG cdPYGJZWJJZAOXm3woEsPIXqZo6UMs26InFosZUY5ySJa0wdcMLcx1X8PyCyTBKlQ8uu LJYX+QEoOIgfg333Fk8lZoD15NJbinPpyQ/Iw=
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=hUjErp4r+NxGbq+a5YyNmhIF+Go+S7cqMQaeCbaJFPbGGQ3hgNY2x+CngJDUts5L6P OOsWz4ZwlT2zTDqV2zrt+q3fUApCF+IT20dpqMrlTzTvDWIILtsXGIfGT99D3ITbb0fi Jt+Za0817EERB/JVREa1EGnpNi73QYP+Ky2a8=
MIME-Version: 1.0
Received: by 10.100.96.1 with SMTP id t1mr10963997anb.137.1293885844849; Sat, 01 Jan 2011 04:44:04 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Sat, 1 Jan 2011 04:44:04 -0800 (PST)
In-Reply-To: <4D1DEF2E.2070506@dcrocker.net>
References: <4D1DEF2E.2070506@dcrocker.net>
Date: Sat, 1 Jan 2011 12:44:04 +0000
Message-ID: <AANLkTik8pnTDna=YxxxJdscyuZtRGz-a5BFw_-PWhNT+@mail.gmail.com>
Subject: Re: New Year's Exploration: Changing the Internet's Infrastructure
From: Phillip Hallam-Baker <hallam@gmail.com>
To: dcrocker@bbiw.net
Content-Type: multipart/alternative; boundary=0016e644caf02985460498c84672
Cc: IETF Discussion <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, 01 Jan 2011 12:41:59 -0000

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

The fundamental problems that infrastructure changes face are cases where

1) Costs are borne by party X, benefits accrue to party Y

2) Costs pers user are independent of number of adopters, benefits are
proportional to the number of adopters.


The network effect is only a virtuous circle once costs exceed benefits.
Until that point is reached it is a chicken and egg problem.

One of the interesting features of this analysis is that every time I give
it people:

1) Insist that the analysis is not novel, is obvious and unimaginative.

2) Continue to attempt the approach they admit is obviously going to fail.


One of the problems with modern academia is that novelty and cleverness are
far more likely to advance a career than building stuff that actually works.
So when we have a problem there is a bias in the academy towards an approach
that is novel and allows the designer to demonstrate their cleverness rather
than an approach that was proposed twenty years ago, before the problem was
recognized as important.

Take the problem of BGP security. People seem to be attempting to
authenticate the routes so as to protect the integrity of messages (assuming
DNSSEC deployment). That seems to be a rather unlikely objective to achieve
given the number of backbone providers, the number of packets and the fact
that packets can be dropped. Trying to achieve anything more than preventing
against Denial of Service attacks at the BGP layer is probably futile.

There are two issues, the binding of IP address range claims to AS numbers
and the interchange of routing metrics. We could solve the first problem
pretty easily using a straightforward approach. Each 24 hours the NICs all
sign a list of the IP address assignments to public key holders they have
granted.This can then be used to verify signatures. Quick, simple and does
not require exploration in untested parts of the X.509 stack.

Instead we get a science project.

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

The fundamental problems that infrastructure changes face are cases where<d=
iv><br></div><div>1) Costs are borne by party X, benefits accrue to party Y=
</div><div><br></div><div>2) Costs pers user are independent of number of a=
dopters, benefits are proportional to the number of adopters.</div>
<div><br></div><div><br></div><div>The network effect is only a virtuous ci=
rcle once costs exceed benefits. Until that point is reached it is a chicke=
n and egg problem.</div><div><br></div><div>One of the interesting features=
 of this analysis is that every time I give it people:</div>
<div><br></div><div>1) Insist that the analysis is not novel, is obvious an=
d unimaginative.</div><div><br></div><div>2) Continue to attempt the approa=
ch they admit is obviously going to fail.</div><div><br></div><div><br>
</div><div>One of the problems with modern academia is that novelty and cle=
verness are far more likely to advance a career than building stuff that ac=
tually works. So when we have a problem there is a bias in the academy towa=
rds an approach that is novel and allows the designer to demonstrate their =
cleverness rather than an approach that was proposed twenty years ago, befo=
re the problem was recognized as important.</div>
<div><br></div><div>Take the problem of BGP security. People seem to be att=
empting to authenticate the routes so as to protect the integrity of messag=
es (assuming DNSSEC deployment). That seems to be a rather unlikely objecti=
ve to achieve given the number of backbone providers, the number of packets=
 and the fact that packets can be dropped. Trying to achieve anything more =
than preventing against Denial of Service attacks at the BGP layer is proba=
bly futile.</div>
<div><br></div><div>There are two issues, the binding of IP address range c=
laims to AS numbers and the interchange of routing metrics. We could solve =
the first problem pretty easily using a straightforward approach. Each 24 h=
ours the NICs all sign a list of the IP address assignments to public key h=
olders they have granted.This can then be used to verify signatures. Quick,=
 simple and does not require exploration in untested parts of the X.509 sta=
ck.</div>
<div><br></div><div>Instead we get a science project.</div>

--0016e644caf02985460498c84672--

From mansaxel@besserwisser.org  Sat Jan  1 05:59:44 2011
Return-Path: <mansaxel@besserwisser.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 0DE1C3A6914 for <ietf@core3.amsl.com>; Sat,  1 Jan 2011 05:59:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uxgCqGYoyUnc for <ietf@core3.amsl.com>; Sat,  1 Jan 2011 05:59:42 -0800 (PST)
Received: from paka.besserwisser.org (paka.besserwisser.org [IPv6:2a01:298:4::43]) by core3.amsl.com (Postfix) with ESMTP id 135AC3A67A3 for <ietf@ietf.org>; Sat,  1 Jan 2011 05:59:41 -0800 (PST)
Received: from paka.besserwisser.org (localhost [127.0.0.1]) by paka.besserwisser.org (8.13.8+Sun/8.13.7) with ESMTP id p01E1Mbb017050; Sat, 1 Jan 2011 15:01:22 +0100 (CET)
Received: (from mansaxel@localhost) by paka.besserwisser.org (8.13.8+Sun/8.13.7/Submit) id p01E1KoY017049;  Sat, 1 Jan 2011 15:01:20 +0100 (CET)
Date: Sat, 1 Jan 2011 15:01:20 +0100
From: Mans Nilsson <mansaxel@besserwisser.org>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Question about Prague
Message-ID: <20110101140120.GA9769@besserwisser.org>
References: <AFAF1BC9D6724B7D8D11AF8BCC7F2186@XeonAL> <8D7FD970-B4E1-41B1-8E50-69406AE54FD9@cisco.com> <70FF1D95-D56C-4F16-8FE6-3E80D914AD36@americafree.tv> <1293820656.17554.6074.camel@mightyatom.folly.org.uk> <4D1E3D4F.7000905@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs"
Content-Disposition: inline
In-Reply-To: <4D1E3D4F.7000905@gmail.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>, 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, 01 Jan 2011 13:59:44 -0000

--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Question about Prague Date: Fri, Dec 31, 2010 at 03:30:07PM -0=
500 Quoting Scott Brim (scott.brim@gmail.com):
> On 12/31/2010 13:37 EST, Elwyn Davies wrote:
> > Driving into the Czech Republic shouldn't be a problem BUT you do have
> > to tell the rental agency in advance and they will make a supplementary
> > charge per day for the whole contract (not just the days you are out of
> > Germany) if my recent experience is anything to go by (hire in Austria,
> > drive to Slovenia).  Its not particularly cheap either.
>=20
> I've learned that in general it costs too much to rent a car for
> international driving in Europe.

The airport is reasonably close to the city, and (as just one sample)
Lufthansa LAX-MUC-PRG and PRG-FRA-LAX costs about 670EUR return flight
in cattle class. Prague has this quaint thing called Public Transport
-- apparently unknown in USA? -- that allows for efficient tram rides
downtown. My experience from a RIPE meeting couple years ago was of a
quite convenient travel experience.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Youth of today!  Join me in a mass rally for traditional mental
attitudes!

--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (SunOS)

iEYEARECAAYFAk0fM68ACgkQ02/pMZDM1cVd5wCfVbLR43rsj92N+ulwwGmtEsHn
gMkAoKk+wgUvUb6vgQHVGgiRICElpst/
=slRF
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--

From ron.even.tlv@gmail.com  Sat Jan  1 14:32:24 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 5248E3A6938; Sat,  1 Jan 2011 14:32:24 -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 rM2DxA3dmWUS; Sat,  1 Jan 2011 14:32:22 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id 136A63A6936; Sat,  1 Jan 2011 14:32:21 -0800 (PST)
Received: by wwi17 with SMTP id 17so12913562wwi.1 for <multiple recipients>; Sat, 01 Jan 2011 14:34:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=28TXdbpfizB5fwEx+bwm5hXymPpjSmfjWJW1Dclfwho=; b=X7GJsuXjFr2V2/BbQWS7M8SLQXleigNlauYH3hh3yhlFJZ1QaU8eWGIkwz15OJKU7o 9IJJOfJMWbTOYaYixHDXs4kCF/fA/67c0CiFCQvQUkhbro9umCON3bJsZlwzZcmnYPi3 ueH3qI5nVMIZTqkBLvWOsSTJR2hRFIi/PaDZM=
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 :thread-index:content-language; b=DLL2rSWGivpoMpg0RDEvisCn6GoIwJCHbUul3OhFs6b/TZzCkDIq59vEIUZ3sSCUdA PiPhMOrP4BpwZi9W48wYQM9NALyfxU4/dcoeKHuZetzTVPDzQ2qIIEeJPpcNiF/1/HjD e/EXaG7VYb/y/fNzADt5VjO08iI7zRa4dTTlA=
Received: by 10.216.14.147 with SMTP id d19mr21845685wed.84.1293921267764; Sat, 01 Jan 2011 14:34:27 -0800 (PST)
Received: from windows8d787f9 ([109.65.44.68]) by mx.google.com with ESMTPS id c54sm3974480wer.6.2011.01.01.14.34.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 01 Jan 2011 14:34:26 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Christer Holmberg'" <christer.holmberg@ericsson.com>, <gen-art@ietf.org>, <draft-ietf-sipcore-keep.all@tools.ietf.org>
References: <4d1a2fda.8a1ce30a.5ad7.58db@mx.google.com> <7F2072F1E0DE894DA4B517B93C6A05850482F0CD@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05850482F0CD@ESESSCMS0356.eemea.ericsson.se>
Subject: RE: Gen-ART LC review of draft-ietf-sipcore-keep-10
Date: Sun, 2 Jan 2011 00:30:58 +0200
Message-ID: <4d1fabf2.ccefd80a.4e12.4381@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
Thread-Index: AcumvqsCWJU+PYLPQjiNraTwI5wq+QC2Ow3jABrnacA=
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: Sat, 01 Jan 2011 22:32:24 -0000

Hi Christer,
I am OK with all your responses
regards
Roni

> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
> Sent: Saturday, January 01, 2011 12:20 PM
> To: Roni Even; gen-art@ietf.org; draft-ietf-sipcore-
> keep.all@tools.ietf.org
> Cc: 'IETF-Discussion list'
> Subject: RE: Gen-ART LC review of draft-ietf-sipcore-keep-10
> 
> Hi Roni,
> 
> >Summary: This draft is almost ready for publication as a Standard
> track RFC.
> >
> >Major issues:
> >
> >
> >Minor issues:
> >
> >1.  In the document you mention that the keep alive can be negotiated
> in each direction. I understand the dialog case, is this true
> >for the case of registration, if yes how is it done from the
> registrar. If not true maybe add some text in 4.2.2.
> 
> Good point. It is NOT true for the case of registration, when sending
> of keep-alives can only be negotiated from the registering party to the
> registrar.
> 
> I suggest adding the following text to the end of section 4.2.2:
> 
> "NOTE: Sending of keep-alives associated with a registration can only
> be negotiated in the direction from the registering SIP entity towards
> the registrar."
> 
> -----
> 
> >Nits/editorial comments:
> >
> >1.  In section 4.1 in the first note "If a SIP entity has indicated
> willingness to receive keep-alives from an adjacent SIP entity,
> >sending of keep-alives towards the same SIP entity needs to be
> separately negotiated".
> >
> >Who is the same SIP entity mentioned in the end of the sentence. I
> assume you meant "towards the adjacent SIP entity".
> 
> (I assume you mean "Why" instead of "Who")
> 
> You are correct. I propose to change to:
> 
> "towards that adjacent SIP entity", to make sure that the text is
> referring to the entity that indicated willingness to send keep-alives,
> and not some other adjacent SIP entity.
> 
> ----
> 
> >2.  In the first paragraph of 4.3 and 4.4 you use "must" should it be
> "MUST"
> 
> As far as I know it shall be "must" when referring to something defined
> in another specifiction.
> 
> ----
> 
> >3.  In 4.3 in the third paragraph "it MUST start to send keep-alives"
> change to "it MUST start sending keep-alives"
> 
> I'll change as suggested.
> 
> ----
> 
> >4.  In figure 2 in the 200 OK response to Alice the VIA is missing.
> 
> Correct.
> 
> I'll change "Alice: UAC;keep=30" to "Via: Alice;keep=30".
> 
> ----
> 
> >5.  In section 7.4 third paragraph " When Alice receives the response,
> she determines from her Via header
> >field that P1 is willing to receive keep-alives associated with the
> dialog." Should be Bob and not P1.
> 
> Correct.
> 
> I'll change as suggested.
> 
> ----
> 
> Thanks for your comments!
> 
> Regards,
> 
> Christer=


From smb@cs.columbia.edu  Sun Jan  2 14:34:48 2011
Return-Path: <smb@cs.columbia.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 75CB228C0ED for <ietf@core3.amsl.com>; Sun,  2 Jan 2011 14:34:48 -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 JW5vkmkUF-02 for <ietf@core3.amsl.com>; Sun,  2 Jan 2011 14:34:46 -0800 (PST)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id 8DB5E28C0EB for <ietf@ietf.org>; Sun,  2 Jan 2011 14:34:46 -0800 (PST)
Received: from [192.168.2.166] (74-92-112-54-Philadelphia.hfc.comcastbusiness.net [74.92.112.54]) (user=smb2132 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p02MajZn015796 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 2 Jan 2011 17:36:48 -0500 (EST)
Subject: Re: Question about Prague
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <20110101140120.GA9769@besserwisser.org>
Date: Sun, 2 Jan 2011 17:36:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B00D0ED-0689-4FF4-8FB2-1B55CD8A8CB8@cs.columbia.edu>
References: <AFAF1BC9D6724B7D8D11AF8BCC7F2186@XeonAL> <8D7FD970-B4E1-41B1-8E50-69406AE54FD9@cisco.com> <70FF1D95-D56C-4F16-8FE6-3E80D914AD36@americafree.tv> <1293820656.17554.6074.camel@mightyatom.folly.org.uk> <4D1E3D4F.7000905@gmail.com> <20110101140120.GA9769@besserwisser.org>
To: Mans Nilsson <mansaxel@besserwisser.org>
X-Mailer: Apple Mail (2.1082)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.8
Cc: Robin Uyeshiro <uyeshiro@ifa.hawaii.edu>, Scott Brim <scott.brim@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: Sun, 02 Jan 2011 22:34:48 -0000

On Jan 1, 2011, at 9:01 20AM, Mans Nilsson wrote:

> Subject: Re: Question about Prague Date: Fri, Dec 31, 2010 at =
03:30:07PM -0500 Quoting Scott Brim (scott.brim@gmail.com):
>> On 12/31/2010 13:37 EST, Elwyn Davies wrote:
>>> Driving into the Czech Republic shouldn't be a problem BUT you do =
have
>>> to tell the rental agency in advance and they will make a =
supplementary
>>> charge per day for the whole contract (not just the days you are out =
of
>>> Germany) if my recent experience is anything to go by (hire in =
Austria,
>>> drive to Slovenia).  Its not particularly cheap either.
>>=20
>> I've learned that in general it costs too much to rent a car for
>> international driving in Europe.
>=20
> The airport is reasonably close to the city, and (as just one sample)
> Lufthansa LAX-MUC-PRG and PRG-FRA-LAX costs about 670EUR return flight
> in cattle class. Prague has this quaint thing called Public Transport
> -- apparently unknown in USA? -- that allows for efficient tram rides
> downtown. My experience from a RIPE meeting couple years ago was of a
> quite convenient travel experience.

But -- beware of the taxis, especially from the train station.  In =
theory,
all taxi rides are metered.  In practice -- well, you know the =
difference
between theory and practice...  The guidebooks warn of this; in our =
experience
(we were there shortly after Maastricht), the warnings are quite =
correct.
The taxi arranged by our hotel to take us back to station was honest.
There are even "honest taxi stands" in some major tourist areas, =
operated
by a consortium of companies that are willing to play by the rules.

Public transit?  We arrived and left by train, so I don't know what =
airport
access is like there.  A couple of years ago, I tallied up how many =
cities
I'd taken trains or trams from the airport.  While most were outside the =
US,
there are a fair number of American airports where it's feasible, =
including
San Francisco, Boston, Atlanta, New York (two of the three airports), =
Chicago,
Washington, Baltimore, Seattle, Portland, Philadelphia, and probably =
more I
can't think of right now.  To be sure, when the rail link to EWR opened, =
a
news story noted that most of the customers were European, since =
Americans
aren't used to thinking that way...


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






From johnl@iecc.com  Sun Jan  2 15:00:52 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 97CE128C0EE for <ietf@core3.amsl.com>; Sun,  2 Jan 2011 15:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.45
X-Spam-Level: 
X-Spam-Status: No, score=-109.45 tagged_above=-999 required=5 tests=[AWL=-0.665, BAYES_40=-0.185, 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 6Y6v1p8yec0K for <ietf@core3.amsl.com>; Sun,  2 Jan 2011 15:00:51 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 3DCC33A6927 for <ietf@ietf.org>; Sun,  2 Jan 2011 15:00:50 -0800 (PST)
Received: (qmail 23786 invoked from network); 2 Jan 2011 23:02:56 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 2 Jan 2011 23:02:56 -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=6dda.4d210420.k1101; i=johnl@user.iecc.com; bh=7sLIwEkrXCvprsIFVRcm64Jdfa9H2hysjs5CD6SdOIs=; b=PeWPGoFthCUtuUVroOvjJqDMuAu7BeILXU6k5BVuoTrJNI30MJXBxwJ4Ya1I8PFhCHd99FsWcDZeBAQjK4NyG5VPg+I53SSqC43WB+YcQtEEppCuwfIn9i4SVvY8AsG/16zo7zbKsXKS/X+Ng4BQjzVcH8gDmiX21l/s6uYVJ+8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Jan 2011 23:02:56 -0000
Message-ID: <20110102230256.28121.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Question about Prague
In-Reply-To: <6B00D0ED-0689-4FF4-8FB2-1B55CD8A8CB8@cs.columbia.edu>
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: Sun, 02 Jan 2011 23:00:52 -0000

>Public transit?  We arrived and left by train, so I don't know what airport
>access is like there.

There's an airport express bus to the downtown train station, and city
buses to the metro.  Details here:

http://www.myczechrepublic.com/prague/prague-airport-bus.html

R's,
John

From ron.even.tlv@gmail.com  Sun Jan  2 23:18:36 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 3EDA33A697D; Sun,  2 Jan 2011 23:18:36 -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 ZG4+oI5Uf9PE; Sun,  2 Jan 2011 23:18:34 -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 3D09F3A694D; Sun,  2 Jan 2011 23:18:33 -0800 (PST)
Received: by wwa36 with SMTP id 36so13140079wwa.13 for <multiple recipients>; Sun, 02 Jan 2011 23:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references :in-reply-to:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=goi6NDTwf3e+QgabkHRPVv+4kkFUupkTBACmMzkvWv4=; b=N5zzWAXmAx0A+cirZIgOxV8EBJqQvdeGKZkJBIeorWeO30iDc7s7EfSouKL1QEV1Xw es3hr2rAWopHYdymSmoh8ie2zAxgcAZVN9m9L9fydafBS8FvgYoukQQUq8kfvvy7h8iI JQn2adIfolfKF9tIcC4n3vtjoKC3ctVjM0knA=
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:x-mailer:thread-index:content-language; b=MkkdL+0zCTSSdFy9qoyyStaD+RwtcBxc4y0rrzojAXyphUuULMp959Q6sa25bQqkh1 T0HWr/Mxq2ND9boVNg2Jp7xmfoe3ao4JA0+rejyVVqdOBm//PxGfgBKlZCvw3+k4cspC DorCJzUtm+zFQ96NEKXsN9ivdktlGY/+EcvuE=
Received: by 10.216.239.9 with SMTP id b9mr3319699wer.24.1294039240162; Sun, 02 Jan 2011 23:20:40 -0800 (PST)
Received: from windows8d787f9 ([109.65.44.68]) by mx.google.com with ESMTPS id t5sm9647954wes.9.2011.01.02.23.20.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Jan 2011 23:20:36 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Karl Heinz Wolf'" <karlheinz.wolf@nic.at>, "'General Area Review Team'" <gen-art@ietf.org>, <draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org>
References: <4cfa61a4.eaecd80a.64b7.ffff8243@mx.google.com> <8BC845943058D844ABFC73D2220D466506876FA7@nics-mail.sbg.nic.at>
In-Reply-To: <8BC845943058D844ABFC73D2220D466506876FA7@nics-mail.sbg.nic.at>
Subject: RE: Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary
Date: Mon, 3 Jan 2011 09:17:14 +0200
Message-ID: <4d2178c4.0504d90a.5952.fffff508@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0057_01CBAB27.0423A430"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuTybiC/+hqNiudRUOFZK+8ttfUZgJ+qg7kA1RwsFA=
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: Mon, 03 Jan 2011 07:18:36 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0057_01CBAB27.0423A430
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Karl,

I looked at the 05 version and it does not look like you fixed the nits

Roni

=20

From: Karl Heinz Wolf [mailto:karlheinz.wolf@nic.at]=20
Sent: Friday, December 17, 2010 10:28 AM
To: Roni Even; General Area Review Team;
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org
Cc: IETF-Discussion list
Subject: AW: Gen-ART IETF LC review of
draft-ietf-ecrit-lost-servicelistboundary

=20

Roni,

thank you for your review and please apologize my delayed response.
I agree to your comments, the 2. one is really a good catch!

Thank you,
Karl



-----Urspr=FCngliche Nachricht-----
Von: ietf-bounces@ietf.org im Auftrag von Roni Even
Gesendet: Sa 12/4/2010 4:41
An: 'General Area Review Team';
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org
Cc: 'IETF-Discussion list'
Betreff: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary

Hi,



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-ecrit-lost-servicelistboundary-04

Reviewer: Roni Even

Review Date: 2010-12-04

IETF LC End Date: 2010-12-14

IESG Telechat date: (if known)



Summary: This draft is ready for publication as an Experimental RFC. =
There
are some nits



Major issues:



Minor issues:



Nits/editorial comments:

1.      In the abstract the document starts with LoST,  Please expand to
Location-to-Service Translation

2.      At the end of section 3.2  in the note, I think that the first
"getServiceListBoundary" should be " getServiceBoundary"







Roni Even




------=_NextPart_000_0057_01CBAB27.0423A430
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<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 name=3DGenerator =
content=3D"Microsoft Word 12 (filtered medium)"><title>AW: Gen-ART IETF =
LC review of =
draft-ietf-ecrit-lost-servicelistboundary</title><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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Karl,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I looked at the 05 version and it does not look like you fixed the =
nits<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Karl Heinz Wolf [mailto:karlheinz.wolf@nic.at] <br><b>Sent:</b> Friday, =
December 17, 2010 10:28 AM<br><b>To:</b> Roni Even; General Area Review =
Team; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org<br><b>Cc:</b=
> IETF-Discussion list<br><b>Subject:</b> AW: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary<o:p></o:p></span></p></div></di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
style=3D'margin-bottom:12.0pt'><span =
style=3D'font-size:10.0pt'>Roni,<br><br>thank you for your review and =
please apologize my delayed response.<br>I agree to your comments, the =
2. one is really a good catch!<br><br>Thank =
you,<br>Karl<br><br><br><br>-----Urspr=FCngliche Nachricht-----<br>Von: =
ietf-bounces@ietf.org im Auftrag von Roni Even<br>Gesendet: Sa 12/4/2010 =
4:41<br>An: 'General Area Review Team'; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org<br>Cc: =
'IETF-Discussion list'<br>Betreff: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary<br><br>Hi,<br><br><br><br>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">http://w=
iki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br><br><br>P=
lease resolve these comments along with any other Last Call comments you =
may receive.<br><br><br><br>Document: =
draft-ietf-ecrit-lost-servicelistboundary-04<br><br>Reviewer: Roni =
Even<br><br>Review Date: 2010-12-04<br><br>IETF LC End Date: =
2010-12-14<br><br>IESG Telechat date: (if known)<br><br><br><br>Summary: =
This draft is ready for publication as an Experimental RFC. There are =
some nits<br><br><br><br>Major issues:<br><br><br><br>Minor =
issues:<br><br><br><br>Nits/editorial =
comments:<br><br>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the abstract the =
document starts with LoST,&nbsp; Please expand to Location-to-Service =
Translation<br><br>2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; At the end of =
section 3.2&nbsp; in the note, I think that the first =
&quot;getServiceListBoundary&quot; should be &quot; =
getServiceBoundary&quot;<br><br><br><br><br><br><br><br>Roni =
Even<br><br></span><o:p></o:p></p></div></div></body></html>
------=_NextPart_000_0057_01CBAB27.0423A430--


From Rolf.Winter@neclab.eu  Mon Jan  3 05:55:18 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 78CC828C11D; Mon,  3 Jan 2011 05:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.186, 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 2f+yjPalllKE; Mon,  3 Jan 2011 05:55:15 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 782D928C103; Mon,  3 Jan 2011 05:55:15 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 327642C0003F9; Mon,  3 Jan 2011 14:59:47 +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 oH8imdxQTDiq; Mon,  3 Jan 2011 14:59:47 +0100 (CET)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id 17A362C0001CE; Mon,  3 Jan 2011 14:59:32 +0100 (CET)
Received: from PALLENE.office.hd ([169.254.1.232]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Mon, 3 Jan 2011 14:57:07 +0100
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: "ietf@ietf.org" <ietf@ietf.org>, "draft-baker-ietf-core@tools.ietf.org" <draft-baker-ietf-core@tools.ietf.org>
Subject: tsv-dir review of draft-baker-ietf-core-11
Thread-Topic: tsv-dir review of draft-baker-ietf-core-11
Thread-Index: AcurThpy7oTTULyoRvKiuMCAjmyPUw==
Date: Mon, 3 Jan 2011 13:57:11 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D88B22A@PALLENE.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
Cc: "tsv-dir@ietf.org" <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: Mon, 03 Jan 2011 13:55:18 -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.

Generally, the document is well written and the following are suggestions t=
o improve the document. There is no show stopper in the document itself but=
 I feel it is sometimes a bit unbalanced regarding detail, explanation and =
recommendation of the various protocols presented. I hope these comments ar=
e helpful.

General observations:

You lack a definition of what the Smart Grid is. You clearly write the docu=
ment for Smart Grid folks (they should know what Smart Grid is) but is ther=
e a generally accepted definition of what the Smart Grid consists of, what =
the requirements are, what the technological assumptions are etc? If there =
is such a document then you should reference it, otherwise you should state=
 in the document what you think the Smart Grid is and why these Smart Grid =
folks need this document.=20
This would also explain why you have included certain things and left other=
 things out (which is something I couldn't tell from the document). As an e=
xample, in Section 2.3 you write "While the following protocols are not cri=
tical to the design of a specific system, they are important to running a n=
etwork, and as such are surveyed here." What is the relevance to Smart Grid=
? Why is only DNS and Network Management mentioned? Having text that explai=
ns what the Smart Grid is makes it much easier to understand why you includ=
ed these specific things in the document.=20


Section 2.2.:

I am not a security expert but I find either the title of the section wrong=
 or the list not quite right. So the section is about authentication and a =
requirement is the "protection of the channel against DoS". I believe that =
is not part of authentication. The same applies to integrity. Maybe you jus=
t want to refer to some of the RFC 4949 definitions here? Generally, I find=
 the security section less coherent than the preceding sections.=20

Section 2.3:

I think you conflate confidentiality and privacy here (but again, please ch=
eck with a sec person). I am also not sure what you want to express with th=
e last sentence. (Or how it would work in practice).

Section 4:

I don't see much value in this section. At least, it is not well titled as =
is mainly talks about firewalls and NATs. Also, if you decide to keep the s=
ection, you might want to change the examples to something less real by usi=
ng RFC 5737 IP addresses.

Other technologies: could delay tolerant networking be of interest. After a=
ll, the Core charter says that devices may be off at any time.

Nits:

Section 2.1: s/While Internet architecture/While the Internet architecture/
Section 2.1: move "(ISO-OSI)" to come right after "Interconnect"
Section 2.1: s/"host /"host"/
Section 2.1: s/"internet gateway"/"Internet gateway"/
Caption figure 1: s/ISO OSI/ISO-OSI/ (at least the rest of the text uses th=
at spelling)
Figure 2: You use slighlty different terminology from RFC 1122 and RFC 1812=
. Is that intentional?
Section 2.1.2: s/to large extent/to a large extent/
Section 2.1.2: The session identification in an IP datagram is often called=
 the "five-tuple" (I personally would use flow instead of session)
Section 2.1.3: s/is the network that/is the network protocol that/
Section 2.1.3.1: s/network abstraction network/network abstraction/
Section 2.1.3.1: s/those protocol/those protocols/=20
Section 2.1.4: s/IPv4 and IPv6 various media types/IPv4 and IPv6 over vario=
us media types/
Section 3.1.2: s/Header (AH) [RFC4302]/Header (AH) [RFC4302],/
Section 3.2: s/since IPv4 free pool/since the IPv4 free pool/
Section 3.2.1.3: s/some networks site networks/some site networks/=20
Section 3.2.2: s/dropped../dropped./
Section 3.2.2.1: s/using Address Resolution Protocol/using the Address Reso=
lution Protocol/
Section 2.2.2.2: You write: "Active research exists in mobile ad hoc routin=
g and other routing paradigms; these result in new protocols and modified f=
orwarding paradigms." This (or a similar) statement applies to all other pr=
otocols that you mention in the document but you do not mention ongoing res=
earch. Why is this statement more relevant to routing v4?
Section 3.2.4.3: expand CLNS
Section 3.2.4.6: s/between device/between devices/
Section 3.2.5.1: s/A the highest/At the highest/
Section 3.2.5.1: s/SSM has inherent/SSM has an inherent/
Section 3.3: s/that built for/that were built for/
Section 3.3.1: s/properly not/probably not/
Section 3.4.3: s/The current versions of the time protocol are/The current =
version of the time protocol is/
Section 3.7.2: s/Representation [I-D.daboo-et-al-icalendar-in-xml]/Represen=
tation [I-D.daboo-et-al-icalendar-in-xml]./
Section 4: s/address/aport tuples/address/port tuples/
Section 4: s/the internet backbone/the Internet backbone/

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


From dworley@avaya.com  Mon Jan  3 07:49:14 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 2B7193A69CA for <ietf@core3.amsl.com>; Mon,  3 Jan 2011 07:49:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, 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 qXWuVzjo9WnG for <ietf@core3.amsl.com>; Mon,  3 Jan 2011 07:49:13 -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 D04D63A69B5 for <ietf@ietf.org>; Mon,  3 Jan 2011 07:49:12 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALp+IU3GmAcF/2dsb2JhbACkNHOlEAKWO4VKBIRliVY
X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="225792313"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 Jan 2011 10:51:18 -0500
X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="565619537"
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; 03 Jan 2011 10:51:17 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Mon, 3 Jan 2011 10:51:09 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Chris Elliott <chelliot@pobox.com>, Joel Jaeggli <joelja@bogus.com>
Date: Mon, 3 Jan 2011 10:49:24 -0500
Subject: RE: BCP request: WiFi at High-Tech Meetings
Thread-Topic: BCP request: WiFi at High-Tech Meetings
Thread-Index: AcuneUVuAtwctOD5Qwq2RKRut0y/4AD5IYN0
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com>, <1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com>
In-Reply-To: <1126A907-D244-4C0C-B640-B356A1D1A48C@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: 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, 03 Jan 2011 15:49:14 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Chris Elli=
ott [chelliot@pobox.com]

I strongly agree here. Encourage .11a (5ghz) usage, disable .11n for the .1=
1b/g 2.4ghz spectrum. We also have the luxury of a large number of repeat a=
ttendees, and many of you have learned the benefits of using .11a and will =
go out of your way to use it. We facilitate that through advertising .11a-o=
nly SSID's.
_______________________________________________

Whereas the NYT article seems to be describing large rooms full of journali=
sts and other technology illiterates, many of whom are trying to send or re=
ceive streaming video, sometimes the video of the presenter they are sittin=
g in front of!

Dale

From john-ietf@jck.com  Mon Jan  3 08:39:19 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 2109C3A6A21 for <ietf@core3.amsl.com>; Mon,  3 Jan 2011 08:39:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.09
X-Spam-Level: 
X-Spam-Status: No, score=-103.09 tagged_above=-999 required=5 tests=[AWL=-0.491, 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 EuD94mXf2hVE for <ietf@core3.amsl.com>; Mon,  3 Jan 2011 08:39:17 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id A32B93A6A30 for <ietf@ietf.org>; Mon,  3 Jan 2011 08:39:16 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PZnTG-000PSn-Fd; Mon, 03 Jan 2011 11:41:22 -0500
Date: Mon, 03 Jan 2011 11:41:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: RE: BCP request: WiFi at High-Tech Meetings
Message-ID: <F6E9A6165321B79A3F3A1FF0@PST.JCK.COM>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com> ,	<1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.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: 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, 03 Jan 2011 16:39:19 -0000

--On Monday, January 03, 2011 10:49 -0500 "Worley, Dale R
(Dale)" <dworley@avaya.com> wrote:

>...
> Whereas the NYT article seems to be describing large rooms
> full of journalists and other technology illiterates, many of
> whom are trying to send or receive streaming video, sometimes
> the video of the presenter they are sitting in front of!

And it seems to me that summarizes a small disconnect we've
developed from the problem that caused the article.  

It seems to me that the Times article claims that 802.11 (all
flavors, but especially b/g/n) are designed exclusively for home
use.  I believe that is just false.  They also suggest that
meetings full of "technology illiterates", implicitly using
hotel setups with maybe one higher-powered beacon per room,
don't work very well.

Judging from the discussion on this list, our reaction to the
above is "well duh" and "we (one of the most
technically-sophisticated communities around) know how to solve
these problems and the solutions start with showing up with our
equipment and configuring the network our way and move on to
specialized laptop configurations".

That is very interesting.  It is probably also very irrelevant.

Getting what we do written down and more widely available --as a
BCP or otherwise-- would be, IMO, a good idea, but it would not
help one bit with the problems that, it seems to me, inspired
the NYT article.

It seems to me that the NYT article is something that the WiFi
Forum ought to be addressing, especially if their vendor-members
want to continue to sell products into conference markets.  We
could offer to supply them our notes if they would be helpful
and I'm certain that there are people in our community who could
alert them to the article in the unlikely event that they aren't
thinking about it already.

But, if this discussion is any indication, I don't think there
is much of a role for the IETF itself in the issues and for the
audience to which the NYT article is addressed.

just my opinion,
     john



From paf@cisco.com  Mon Jan  3 08:57:37 2011
Return-Path: <paf@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 79C093A6994 for <ietf@core3.amsl.com>; Mon,  3 Jan 2011 08:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.193
X-Spam-Level: 
X-Spam-Status: No, score=-11.193 tagged_above=-999 required=5 tests=[AWL=1.106, BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, 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 PtNCnMNQhVBO for <ietf@core3.amsl.com>; Mon,  3 Jan 2011 08:57:36 -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 81E4D3A67C0 for <ietf@ietf.org>; Mon,  3 Jan 2011 08:57:36 -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: AvYEAKqOIU2Q/khMgWdsb2JhbACkNBUBARYiJKMGmGKFSgSLBA
X-IronPort-AV: E=Sophos;i="4.60,267,1291593600"; d="scan'208";a="16216198"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 03 Jan 2011 16:59:43 +0000
Received: from dhcp-10-61-97-5.cisco.com (dhcp-10-61-97-5.cisco.com [10.61.97.5]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p03GxgsT030913; Mon, 3 Jan 2011 16:59:42 GMT
Subject: Re: BCP request: WiFi at High-Tech Meetings
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@cisco.com>
In-Reply-To: <F6E9A6165321B79A3F3A1FF0@PST.JCK.COM>
Date: Mon, 3 Jan 2011 17:59:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <18609486-BAE4-46D8-B057-9C49261A04B7@cisco.com>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com> , <1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com> <F6E9A6165321B79A3F3A1FF0@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1082)
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, 03 Jan 2011 16:57:37 -0000

On 3 jan 2011, at 17.41, John C Klensin wrote:

> It seems to me that the Times article claims that 802.11 (all
> flavors, but especially b/g/n) are designed exclusively for home
> use.  I believe that is just false.

I have definitely not been running wifi networks like the core IETF =
team, but I have run a few conferences with more than 1500 participants =
the last ten years. And specifically, I did run a conference (the =
Internet Governance Forum) in Vilnius in Nov 2010 with 2000+ people and =
do have "some" experience.

Basically my summary is like this:

1- Anyone that "just" mention the letters instead of the frequency bands =
and channel allocation when talking about how good and bad things work =
has not really dived into the issues enough (and does not provide enough =
information that really helps).

2- 2.4GHz is indeed not usable at large conferences (if you do not have =
really skilled people like we have at the IETF), but 5GHz works just =
fine.

   Patrik


From stpeter@stpeter.im  Mon Jan  3 15:12:19 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 508ED3A6ABA; Mon,  3 Jan 2011 15:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.488
X-Spam-Level: 
X-Spam-Status: No, score=-102.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5EA2ZpA7FYeu; Mon,  3 Jan 2011 15:12:17 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id ED1863A6A7E; Mon,  3 Jan 2011 15:12:13 -0800 (PST)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 693BD4009B; Mon,  3 Jan 2011 16:28:32 -0700 (MST)
Message-ID: <4D22584A.2070307@stpeter.im>
Date: Mon, 03 Jan 2011 16:14:18 -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: [certid] Review of draft-saintandre-tls-server-id-check-12
References: <58FE898B-BD2A-4C6E-B769-256008D8A58B@cisco.com> <4D0A2EA8.6080709@stpeter.im>
In-Reply-To: <4D0A2EA8.6080709@stpeter.im>
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="------------ms070903070809060907030503"
Cc: IETF cert-based identity <certid@ietf.org>, IESG IESG <iesg@ietf.org>, 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, 03 Jan 2011 23:12:19 -0000

This is a cryptographically signed message in MIME format.

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

I just realized that we never replied publicly. Jeff and I had a phone
chat with Cullen (and Alexey) about this before the holidays, and we
plan to submit a revised I-D this week. Cullen raised some very good
points, which we've attempted to address in the forthcoming version.

On 12/16/10 8:22 AM, Peter Saint-Andre wrote:
> Thanks for your comments. My co-author and I will need to confer before=

> replying, and that might take a few days given the length of your revie=
w.
>=20
> Peter
>=20
> On 12/16/10 12:17 AM, Cullen Jennings wrote:
>>
>> So let me start with I think there is great information in here and I
>> think it should be published as a standards track RFC however I do
>> think there are some issues with the relation with this draft and the
>> realities of what would help improve security in deployment of SIP,
>> HTTP, IMAP, XMPP etc.
>>
>> There are many places where this draft makes choices to improve the
>> security from many current practices. At face value this seems like a
>> good thing but it's not always. The thing reducing the overall
>> security available to users of TLS is not if certs use CN-ID or
>> DNS-ID, it is that it's such a PITA to deploy a TLS  server that
>> people choose to not use TLS at all. Everywhere there is a trade off
>> between making things marginally more secure, or making things
>> cheaper and easer to deploy, I think we need to seriously consider
>> the cheaper and easier approach. Yes, some things are just broken
>> even if they are easy and obviously we can't do those. Let me give an
>> example of this. I looked at the cert for the domains for the authors
>> of this draft. www.cisco.com has 3 DNS names even though as fas as I
>> can tell one of these are for something that would typically be used
>> in a ftp URI and the other HTTP URI. This is because it makes it
>> easier and cheaper for them to use TLS yet seems to go against the
>> recommendation of this "BCP". Then I went over the www.paypal.com
>> domain which uses, gasp, a CN-ID. Do we really believe that paypal is
>> seriously compromising their security by using a CN instead of
>> URI-ID? If so, how? I'm pretty sure the paypal guys know how to run a
>> secure web server. With the exception of Microsoft small business
>> server certificates (which are outrageously expensive by the way) it
>> pretty hard to get SRV name certs. In making these recommendations,
>> did the TLS WG consider the relative prices of various types of
>> certificates? Lets say I had a certificate for the domain example.org
>> because I was using it for email and it has a CN because I got it
>> years ago. Now lets say I am going to go deploy a SIP service on
>> example.org. My position is that best way to encourage the use of
>> security on the internet is to just reuse the certificate I have. It
>> cheap, it's easy, it secure enough even if it does make you feel a
>> bit dirty. I think Jeff disagrees w ith me, we argued for years about
>> this topic and my understanding is his position is that it would be
>> better to say that all new deployments MUST not use a CN name because
>> it's less secure. Give the prevalence of CN on the internet today, I
>> think it is fine to tell people how DNS-ID is better but I don't
>> think it's OK to tell them they should not use CN-ID and I definitely
>> don't think it is OK to tell implementors they don't need to
>> implement CN-ID.
>>
>> I encouraged Chris to write this draft long ago and what we had
>> discussed at the time was forming a RFC with one or more boiler plate
>> pieces of text that could be used in creation of the name matching
>> section of new protocols that got developed. I was thinking of
>> something similar to the way we use rfc 5226 for writing IANA
>> consideration section. Instead we have a document that is creating a
>> very complex situations about whats normative. This draft is a BCP
>> level, and it says you have to do everything in PKIX and PKIX takes
>> precedence. That is basically elevating PKIX to a BCP without
>> appropriate process review. Next this draft contradicts the
>> procedures in existing protocols and says that it does not apply to
>> the existing protocols but that it would take precedence over any
>> future updates of existing protocols that use TLS within the scope
>> specified here. I do not believe you have the consensus of the people
>> woking on SIP that the next time some specification is marked as an=20
>> UPDATE to 3261, that implementations need to implement the procedures
>> in this draft. Furthermore, I think that would be counter productive.
>> I think you should make it clear this guidelines for designers of new
>> protocol and people updating existing protocol and that these
>> protocols could make their own choices but would want to take into
>> account the information in this draft. When I read the sentence,=20
>> "However, the best current practices described here can be referenced
>> by future specifications, including updates to specifications for
>> existing application protocols if the relevant technology communities
>> agree to do so." I think that is exactly the right solution to the
>> problem. However, that not a BCP, thats a standards track spec.
>> Furthermore, I think this draft is going to have all the normal bugs
>> etc of any other spec that defines algorithms and such it should
>> proceed through the standards track process. If this draft is going
>> to go as a BCP, that text contradicts what a BCP is and needs to come
>> out and the rest of the draft be adjusted appropriately. My
>> preference would be that this draft be standards track. Its writing
>> exactly the same sort of normative algorithm text that we put in all
>> kinds of other thing like SIP, HTTP, and even TLS. They are all
>> standards track. This should be the same.
>>
>> Most RFCs today that use TLS have a page plus or minus that tells an
>> implementer what they need to know about matching names in certs.
>> This draft move that to 30 to 50 pages depending on how you count.
>> Most implementers are just going to ignore this thus worsening the
>> security situation. Think about why is the part implementers need to
>> read 10x longer than existing deceptions - this just seems wrong. Now
>> it's easy to blow off this type concern and say get over it, it's the
>> same number of lines of code they need to write. But the problem is
>> when an implementors goes to start doing this and encounters
>> something that is 50 pages long, they instantly decide this is a big
>> task and down it goes on the priority list of actually happening. The
>> other problem is that even thous it is long, it is still very
>> confusing on how to do things (such at URI). I'll provide more
>> detailed examples of this later in this email. If the document was
>> restructured to have all the normative text in one s hort simple
>> description and the rest moved to an appendix, it would be much
>> easier to get people to take this seriously and easier to review that
>> it was correct.
>>
>> My final big issue is the use of normative language. Lets say there
>> are two procedures A and B and we 100% consensus that B is better
>> than A but we still have to support A for existing deployment
>> reasons. To describe this, the text this draft would use is is MUST
>> do A and SHOULD NOT do B. Now reading 2119 it is pretty clear that
>> SHOULD NOT means you don't implement it unless there are real good
>> reasons to implement it. So on the things were we agree A is
>> preferred to B but you need both for backwards compatibility, this
>> draft needs to say MUST implement A and MUST implement B but
>> deployments are encouraged to use B as we are trying to move away
>> from A. I think the whole document needs a careful read checking for
>> this issue. You can insert the usual rant here about why SHOULD is a
>> awful word in specs 90% of the time it used because implementer
>> thinks it means "ignore rest of sentence". For example,  section 5.4
>> discusses they this spec continues to mandate protocols MUST suppo rt
>> CN yet this draft continually use "SHOULD NOT" when what it really
>> means is MUST implement. This is going to confuse implementors of
>> IETF specification and be ignored by operators. Given the goals of
>> this spec it would be much better if it was clearly defining what
>> IETF required implementers of protocols to do instead of confusing
>> that with how we wish security was deployed.
>>
>>
>> On to the nits.
>>
>> Take an applications like a web server. Is the preferred thing in a
>> cert a DNS-ID or a URI-ID. My reading of the 3.3 is that URI-ID is
>> preferred over DNS-ID yet the examples don't match that. I think
>> point 3 in section 3.1 tries to explain this away but I don't
>> understand that - clearly web browsers use a URI.
>>
>> The rules in section 3.1 don't make sense for a CA. How will the CA
>> know if the cert I want is going to be used for a protocol that uses
>> SRV?
>>
>> In section 3.2, in the imap example, you are saying that if I
>> configure my imap server to mail.example.com and it presents a
>> certificate with a DNS-ID of example.com that this is OK. That does
>> not sound OK to me but I don't know how IMAP works. In the SIP
>> example, the cert should have a SRV and DNS name too. As well as a CN
>> if you actually want it to work in the real world.
>>
>> In section 4.2.1 you have a long discussion on how the information
>> used must come from a way that can't be tampered with over the
>> internet. I generally agree with this but would like to point out
>> that protocols like LOST (see section 18 of rfc5222) specially do the
>> opposite of this and actually match the cert agains the output of
>> NAPTR process not the input to the NAPTR process.
>>
>> The example just seem plain wrong in some cases. Take for example
>> section 4.2.2 where the SIP example has only a URI reference
>> identifiers and no DNS yet the section right before this has said the
>> list MUST include a DNS-ID. This text has been through how many
>> reviews and Last Calls? The problem here is that this draft is too
>> long to review for stuff like this. Even after the IESG is done
>> reviewing it, statistics suggest it will still be littered with bugs
>> like this and implementors will use the examples to guide them. If
>> someone implements what is in the example, it will break in lots of
>> sip deployments.
>>
>> There is a whole algorithm about matching various ID types, but the
>> note about you ignore CN if you have other things is off in "Security
>> Warning" very much out of any flow of the algorithm description then
>> pointed out again in some other section. It's not wrong, but it's a
>> bit weird from an implementer point of view.
>>
>> Many applications do need to deal with IP matching as well as domain
>> names. The way this text is written here makes it harder to figure
>> out how and where to mix that in. I'd rather see it just dealt with
>> than instead of making it out of scope. Obviously it's not common on
>> internet but it is common on private networks and walled gardens
>> where many of the protocols were are talking about are deployed. Many
>> of the "internet of things" people I work with have no intention of
>> using DNS at all. I scoffed at multiple large service providers 10
>> years ago when they said they were not using DNS with SIP but many
>> still use IPs. This sounds less insane when you consider the major OS
>> don't ship with an asynchronous DNS library.
>>
>> I'm baffled on why checking the service name in a SRV record is a
>> SHOULD not a MUST. Could you add text explain why and when one would
>> not check it. If you were in a really good mood you could do that for
>> all the SHOULDs. Actually, when I read section 4.5 carefully, I think
>> it literally says that when using a URI, checking the domain name is
>> a SHOULD not a MUST. Surely check the domain name matches is not a
>> SHOULD level sort of thing.
>>
>> Section 5.4. I have no idea why it matters that some major OS does
>> not support SNI. Even if that OS did support SNI, many many
>> applications running on that OS and the others would not support SNI.
>> It seems like it is the applications acting as TLS servers and
>> clients that are the important thing, not the OS.
>>
>> How you process URI-ID needs work. I could not figure out how to
>> implement given the text in the draft as is. Even ignoring the
>> special tar pit the SIP guys dug for themselves with tel URL
>> processing, just the normal sip, sips issues seems unclear.
>>
>> This seems like a long list of complaints delivered fairly late but,
>> once again, I really do like much of the information in here and
>> think it should be published as PS - it just would be significantly
>> improved with a bit of a re-factored and clean up. If this had been
>> run through the TLS working group, I would have caught all of this in
>> the WG LC. This is a draft that, as a BCP,  profoundly effects many
>> of the protocols I work on including SIP but as far as I can tell has
>> not done much to gather the consensus of the people working on
>> protocol that this draft changes - I don't recall hearing about it
>> until after it went to the IESG so I'm pretty un apologetic about
>> providing these comments during IETF LC.
>>
>> In summary, I like the information in this but I think it still has
>> many small things that need fixing and needs to be changed to get
>> crisp about what implementors need to do and drop the confusing stuff
>> about how we wish operators and CA might use certificates. I also
>> feel strongly that the right way to look at this draft is, as that
>> draft says "practices described here can be referenced by future
>> specifications, including updates to specifications for existing
>> application protocols if the relevant technology communities agree to
>> do so" and that for that reason it has to be standards track not BCP.
>> If it was not being written and pushed by two IESG members, I don't
>> think we would even be discussing if it should be a BCP.
>>


--------------ms070903070809060907030503
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
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEw
MzIzMTQxOFowIwYJKoZIhvcNAQkEMRYEFPGXCljOGIHx2gXzqC5vrZjqhRegMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQBgRfgYeYfHWdtfwrkhocs5b/qEZ4riNPLsFCOj9f+0tp+x/SbhVRsQ9A7h
SREcgUyz+iQCjl9Jza8wPJmysVaFsN5gxiy4G01G0n2g7VaMYi14w4nVh5YQGc/qNbTLqnyC
xdO2dstxV7z8DxKOyIn+5EFazK87lyWx6OauzdRS3jK9RbJs09R7b62CFEpn1fcQq/lMJ7yq
V3X8M5+9cZT1UjkoB1EgG/yoAcVgt8lxvEr9CZldPAkLVemseB8njb5AekfxGswd0cCXNSem
9KfTsv/PUoolY66z5Frw5PZDzMKTOzOlnjNLFpqpXgxNEN8vkbnq0L4PHF1xk7RHef4nAAAA
AAAA
--------------ms070903070809060907030503--

From hallam@gmail.com  Tue Jan  4 07:53:41 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 2FBA63A6CB7 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 07:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.884
X-Spam-Level: 
X-Spam-Status: No, score=-2.884 tagged_above=-999 required=5 tests=[AWL=-0.286, 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 snRfe7NIOLl3 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 07:53:40 -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 C7A9C3A6CB5 for <ietf@ietf.org>; Tue,  4 Jan 2011 07:53:39 -0800 (PST)
Received: by yie19 with SMTP id 19so4145803yie.31 for <ietf@ietf.org>; Tue, 04 Jan 2011 07:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=LRcP6082MIwjhfbeHPhKpCI5CphF0dTzdo5SI2aqMTM=; b=d1331tAhU9xbQLTf+c/mpMeuBRExgnGIPDIGUtr6zmTwMrF0zC+pxmJO+akZ6LM71w uoqzBtPLlyhrW7UhC0BzxvLyg80pDhWQDkN/Bd+UNyUL/raVcikPo6M7hvtT/gTIYTQc QnV97jOkuFrs8T2wp2FixYSPBrvwm6GAgmf+Q=
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=pVbxP3N9mDrHuCSr6759lZzHdmp3K/dYOom+4gf+9r2C7Desph5TOp+inOB/6M8cUr nkISfKmRXL466HUc7cj9sApL4EgV9G9uvVDbNv69wvVaxEYF0quAY5ICeJIdGodfOSF/ UN66Ns3slXDye/lNb3PzC5mDovid9JScN8LFY=
MIME-Version: 1.0
Received: by 10.100.231.20 with SMTP id d20mr2190039anh.35.1294156546198; Tue, 04 Jan 2011 07:55:46 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Tue, 4 Jan 2011 07:55:46 -0800 (PST)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com> <1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com>
Date: Tue, 4 Jan 2011 15:55:46 +0000
Message-ID: <AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com>
Subject: Re: BCP request: WiFi at High-Tech Meetings
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: multipart/alternative; boundary=0016368e2050384c4a0499074d68
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: Tue, 04 Jan 2011 15:53:41 -0000

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

It could be the 11a support.

Or it might well be the vendor that supplies the 11a equipment.

At home I have a box with 7 defunct WiFi routers that I discarded after they
started to fail. Specifically the wireless side of the router would stop
functioning or require rebooting every 24 hours or so to keep functioning.

Then three years ago I mentioned the problem on this list and bought an
AirPort Extreme on the advice of several people.

It has now been running for three years without issue.


I do notice that a significant proportion of laptops used at IETFs are
produced by one specific vendor. And lets face it, we are the type of
audience that is quite willing to pay two to three times the minimum for a
laptop.


On Mon, Jan 3, 2011 at 3:49 PM, Worley, Dale R (Dale) <dworley@avaya.com>wrote:

> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Chris
> Elliott [chelliot@pobox.com]
>
> I strongly agree here. Encourage .11a (5ghz) usage, disable .11n for the
> .11b/g 2.4ghz spectrum. We also have the luxury of a large number of repeat
> attendees, and many of you have learned the benefits of using .11a and will
> go out of your way to use it. We facilitate that through advertising
> .11a-only SSID's.
> _______________________________________________
>
> Whereas the NYT article seems to be describing large rooms full of
> journalists and other technology illiterates, many of whom are trying to
> send or receive streaming video, sometimes the video of the presenter they
> are sitting in front of!
>
> Dale
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

It could be the 11a support.<div><br></div><div>Or it might well be the ven=
dor that supplies the 11a equipment.</div><div><br></div><div>At home I hav=
e a box with 7 defunct WiFi routers that I discarded after they started to =
fail. Specifically the wireless side of the router would stop functioning o=
r require rebooting every 24 hours or so to keep functioning.</div>
<div><br></div><div>Then three years ago I mentioned the problem on this li=
st and bought an AirPort Extreme on the advice of several people.</div><div=
><br></div><div>It has now been running for three years without issue.</div=
>
<div><br></div><div><br></div><div>I do notice that a significant proportio=
n of laptops used at IETFs are produced by one specific vendor. And lets fa=
ce it, we are the type of audience that is quite willing to pay two to thre=
e times the minimum for a laptop.</div>
<div><br><br><div class=3D"gmail_quote">On Mon, Jan 3, 2011 at 3:49 PM, Wor=
ley, Dale R (Dale) <span dir=3D"ltr">&lt;<a href=3D"mailto:dworley@avaya.co=
m">dworley@avaya.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
;">
________________________________________<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [<=
a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] On Behal=
f Of Chris Elliott [<a href=3D"mailto:chelliot@pobox.com">chelliot@pobox.co=
m</a>]<br>

<div class=3D"im"><br>
I strongly agree here. Encourage .11a (5ghz) usage, disable .11n for the .1=
1b/g 2.4ghz spectrum. We also have the luxury of a large number of repeat a=
ttendees, and many of you have learned the benefits of using .11a and will =
go out of your way to use it. We facilitate that through advertising .11a-o=
nly SSID&#39;s.<br>

</div>_______________________________________________<br>
<br>
Whereas the NYT article seems to be describing large rooms full of journali=
sts and other technology illiterates, many of whom are trying to send or re=
ceive streaming video, sometimes the video of the presenter they are sittin=
g in front of!<br>

<br>
Dale<br>
_______________________________________________<br>
<div><div></div><div class=3D"h5">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>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016368e2050384c4a0499074d68--

From ynir@checkpoint.com  Tue Jan  4 08:05:11 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 CBFF93A6CE6 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 08:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.893
X-Spam-Level: 
X-Spam-Status: No, score=-9.893 tagged_above=-999 required=5 tests=[AWL=0.706,  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 qha72ChiUcop for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 08:05:11 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 340613A6CE5 for <ietf@ietf.org>; Tue,  4 Jan 2011 08:05:09 -0800 (PST)
X-CheckPoint: {4D2345B4-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p04G7CCt018304;  Tue, 4 Jan 2011 18:07:12 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Tue, 4 Jan 2011 18:07:12 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Date: Tue, 4 Jan 2011 18:07:13 +0200
Subject: Re: BCP request: WiFi at High-Tech Meetings
Thread-Topic: BCP request: WiFi at High-Tech Meetings
Thread-Index: AcusKXHHf6Jt2vNRR96+4sBzb3Be0A==
Message-ID: <84AFE0E6-D1E7-4606-A620-341457E1B1E5@checkpoint.com>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com> <1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com> <AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com>
In-Reply-To: <AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 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: Tue, 04 Jan 2011 16:05:11 -0000

On Jan 4, 2011, at 5:55 PM, Phillip Hallam-Baker wrote:

> It could be the 11a support.
>=20
> Or it might well be the vendor that supplies the 11a equipment.
>=20
> At home I have a box with 7 defunct WiFi routers that I discarded after t=
hey started to fail. Specifically the wireless side of the router would sto=
p functioning or require rebooting every 24 hours or so to keep functioning=
.
>=20
> Then three years ago I mentioned the problem on this list and bought an A=
irPort Extreme on the advice of several people.
>=20
> It has now been running for three years without issue.
>=20
>=20
> I do notice that a significant proportion of laptops used at IETFs are pr=
oduced by one specific vendor. And lets face it, we are the type of audienc=
e that is quite willing to pay two to three times the minimum for a laptop.

Wouldn't the same be true for media events staged by that same specific ven=
dor?  That was the event the NYT article described.=

From rbarnes@bbn.com  Tue Jan  4 09:40:03 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 D07BE3A6C4C for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 09:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.963
X-Spam-Level: 
X-Spam-Status: No, score=-102.963 tagged_above=-999 required=5 tests=[AWL=-0.364, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWGQBkmE7OSE for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 09:40:02 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id CAD303A699F for <ietf@ietf.org>; Tue,  4 Jan 2011 09:40:02 -0800 (PST)
Received: from [192.1.255.181] (port=54051 helo=col-raltmann-l1.nira.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PaAtd-0005PR-K9; Tue, 04 Jan 2011 12:42:09 -0500
Subject: Re: Question about Prague
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: <20110102230256.28121.qmail@joyce.lan>
Date: Tue, 4 Jan 2011 12:42:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C772989-BA06-4E1C-BE04-65AE11BFFDAA@bbn.com>
References: <20110102230256.28121.qmail@joyce.lan>
To: John Levine <johnl@iecc.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, 04 Jan 2011 17:40:03 -0000

I have also had good luck with the CEDAZ minibus to Namesti Republiky
<http://www.cedaz.cz/>

According to Google Maps, their stop is around a 12 minute walk to the =
IETF hotel, and marginally closer than the main train station.
<http://goo.gl/sib5S>

--Richard




On Jan 2, 2011, at 6:02 PM, John Levine wrote:

>> Public transit?  We arrived and left by train, so I don't know what =
airport
>> access is like there.
>=20
> There's an airport express bus to the downtown train station, and city
> buses to the metro.  Details here:
>=20
> http://www.myczechrepublic.com/prague/prague-airport-bus.html
>=20
> R's,
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From hartmans@painless-security.com  Tue Dec 28 15:35:28 2010
Return-Path: <hartmans@painless-security.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 ED0153A6966; Tue, 28 Dec 2010 15:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 GFwLZEJyiMQG; Tue, 28 Dec 2010 15:35:28 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id 19A7F3A68F3; Tue, 28 Dec 2010 15:35:27 -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 6F88B20B4D; Tue, 28 Dec 2010 18:36:13 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 0A2EB41F6; Tue, 28 Dec 2010 18:36:55 -0500 (EST)
From: Sam Hartman <hartmans@painless-security.com>
To: mrex@sap.com
Subject: Re: Last Call: <draft-turner-md5-seccon-update-07.txt> (Updated
References: <201012281617.oBSGH8HN000052@fs4113.wdf.sap.corp>
Date: Tue, 28 Dec 2010 18:36:55 -0500
In-Reply-To: <201012281617.oBSGH8HN000052@fs4113.wdf.sap.corp> (Martin Rex's message of "Tue, 28 Dec 2010 17:17:08 +0100 (MET)")
Message-ID: <tslr5d1v59k.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
X-Mailman-Approved-At: Tue, 04 Jan 2011 09:58:57 -0800
Cc: Francis.Dupont@fdupont.fr, ietf@ietf.org, L.Wood@surrey.ac.uk, wes@mti-systems.com, 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, 28 Dec 2010 23:35:29 -0000

>>>>> "Martin" == Martin Rex <mrex@sap.com> writes:

    Martin> Sam Hartman wrote:
    >> 
> I'm OK with this text.  I tried to come up with a way to briefly
    >> discuss how error detection is very related to things like
    >> protecting against substitution of content (the internet mirror
    >> case) but failed to come up with something brief.  So, I'm fine
    >> with what you have.

    Martin> The use of MD5 _is_ a security problem in integrity
    Martin> protection scenarios.

Agreed.  My point was close but not identical to yours.  My point was
that even when you think you're just talking about error detection, it
takes effort to tell whether you are really talking about error
detection (OK) or integrity protection (not OK).


    Martin> When used for checksums when mirroring sites, a
    Martin> "contributor" could precompute a collision for a file he
    Martin> contributed in order to perform an MITM attack on specific
    Martin> downloads (substituting a trojaned package with the same
    Martin> md5sum into the download while leaving the file on the
    Martin> Download servers clean.

An excellent point!  In my original long message on this topic I pointed
out that if the checksums are ever separated from the file then you're
talking about integrity protection not error detection in most threat
models. I was thinking of the case where you have a mastersite listing
checksums and a bunch of mirror sites. (That is, the checksums in
something like a Debian Packages file are very much integrity checksums
not just error detection checksums; there's a reason we no longer rely
on MD5.)

However you point out that even if there is only one site, when there
can be separation--even after the fact--then MD5 may be problematic.
Some threat models may reject the case where the original distributor
performs a precomputation attack, but for other threat models, this is a
realistic attack.

After this discussion, I continue to believe that determining whether a
particular use of MD5 is safe is quite tricky. Therefore, it is very
reasonable to ask that the security assumptions be described and
analyzed.

From mohamed.boucadair@orange-ftgroup.com  Wed Dec 29 06:22:38 2010
Return-Path: <mohamed.boucadair@orange-ftgroup.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 C416E3A688A for <ietf@core3.amsl.com>; Wed, 29 Dec 2010 06:22:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.897
X-Spam-Level: 
X-Spam-Status: No, score=-2.897 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, DC_PNG_UNO_LARGO=0.558, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 l+AyTo-+FB3V for <ietf@core3.amsl.com>; Wed, 29 Dec 2010 06:22:37 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by core3.amsl.com (Postfix) with ESMTP id 455D73A687A for <ietf@ietf.org>; Wed, 29 Dec 2010 06:22:36 -0800 (PST)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id B67E43B43F1; Wed, 29 Dec 2010 15:24:40 +0100 (CET)
Received: from PUEXCH61.nanterre.francetelecom.fr (unknown [10.101.44.32]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 9AD1F238059; Wed, 29 Dec 2010 15:24:40 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH61.nanterre.francetelecom.fr ([10.101.44.32]) with mapi; Wed, 29 Dec 2010 15:24:40 +0100
From: <mohamed.boucadair@orange-ftgroup.com>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Wed, 29 Dec 2010 15:24:39 +0100
Subject: RE: Last Call: <draft-arkko-ipv6-transition-guidelines-08.txt> (Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment) to Informational RFC
Thread-Topic: Last Call: <draft-arkko-ipv6-transition-guidelines-08.txt> (Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment) to Informational RFC
Thread-Index: AcumIwpXHc+y5C8CQgakjrwz0yCWsAAPoLTQ
Message-ID: <19137_1293632680_4D1B44A8_19137_59718_1_94C682931C08B048B7A8645303FDC9F33C3E619A91@PUEXCB1B.nanterre.francetelecom.fr>
References: <19776_1293460120_4D18A298_19776_757068_1_94C682931C08B048B7A8645303FDC9F33C3E619705@PUEXCB1B.nanterre.francetelecom.fr> <4D1929EE.6070509@piuha.net>
In-Reply-To: <4D1929EE.6070509@piuha.net>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/mixed; boundary="_002_94C682931C08B048B7A8645303FDC9F33C3E619A91PUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.12.29.131219
X-Mailman-Approved-At: Tue, 04 Jan 2011 09:58:57 -0800
Cc: "draft-arkko-ipv6-transition-guidelines@tools.ietf.org" <draft-arkko-ipv6-transition-guidelines@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Lindqvist Kurt Erik <kurtis@kurtis.pp.se>
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, 29 Dec 2010 14:22:38 -0000

--_002_94C682931C08B048B7A8645303FDC9F33C3E619A91PUEXCB1Bnante_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Dear Jari,

Thank you for your answers.

Please see inline.

Cheers,
Med

-----Message d'origine-----
De : Jari Arkko [mailto:jari.arkko@piuha.net]
Envoy=E9 : mardi 28 d=E9cembre 2010 01:06
=C0 : BOUCADAIR Mohamed NCPI/NAD/TIP
Cc : ietf@ietf.org; rbonica@juniper.net; Lindqvist Kurt Erik; draft-arkko-i=
pv6-transition-guidelines@tools.ietf.org
Objet : Re: Last Call: <draft-arkko-ipv6-transition-guidelines-08.txt> (Gui=
delines for Using IPv6 Transition Mechanisms during IPv6 Deployment) to Inf=
ormational RFC

Mohamed,

Thank you for your in-depth review and comments. I have tried to take
your comments into account in the -14 version that got just posted.

> (1)
>
> * Precise in the introduction section the type of networks which are
> concerned with the IPv6 deployment models listed in the I-D; in
> particular mention that both corporate networks and providers networks
> are concerned.
>
> * Fixed and mobile networks may adopt distinct IPv6 deployment
> strategies because of the differences between the two networks (e.g.,
> controlled CPE vs. non controlled handsets).
>
> * It seems services infrastructures (e.g., VoIP, IP TV) are out of
> scope. This should be mentioned. Note that some service-related
> discussed is covered in Section 4.4.

We certainly did not plan on providing specific guidance to each and
every different networking situation. Draft -14 tries to make this
clearer. But by the same token, I'm not sure I want to single out the
above cases in any particular way either. FWIW I do agree with many of
your arguments above. Who controls what is one of the key factors in any
deployment decision.

Med: The sentence you added is fine.

> (2)
>
> Page 5/6, the I-D says:
>
>
>   " o  The ability to offer a valuable service.  In the case of the
>       Internet, connectivity has been this service.
>
>    o  The ability to deploy the solution in an incremental fashion.
>
>    o  Simplicity.  This has been a key factor in making it possible for
>       all types of devices to support the Internet protocols.
>
>    o  Openly available implementations.  These make it easier for
>       researchers, start-ups and others to build on or improve existing
>       components.
>
>    o  The ability to scale.  The IPv4 Internet grew far larger than its
>       original designers had anticipated, and scaling limits only became
>       apparent 20-30 years later.
>
>    o  The design supports robust interoperability rather than mere
>       correctness.  This is important in order to ensure that the
>       solution works in different circumstances and in an imperfectly
>       controlled world."
>
> and in Page 6: "These factors are also important when choosing IPv6
> migration tools.", but:
>
> * The I-D does not show how these factors are applied for the tools
> listed in the I-D; a table with a set of criteria would be useful;
>
> * The first criterion is IMHO meaningless for IPv6 deployment because
> IPv6 does not offer a new service compared to IPv4.
>
> * I'm not sure that having an open source for a given tool can be an
> argument to RECOMMEND or NOT a given tool;

Well, the document only says "these factors are important". I would
argue that they are. Of course, as you point out, situations differ and
maybe in some case you decide to deploy something regardless of what
some of the factors indicate -- for good reasons.

Med: I would personally remove the list of the bullets provided in the I-D;=
 since no definition is provided to what is meant by "simplicity", "scalabi=
lity", etc. BTW, I would maintain only the new sentence starting from "Succ=
ess factors...". But, this is up to you of course.

> * How "scalability" is defined (5th bullet)?? All the solutions listed
> in the I-D need a NAT (l2-nat, ds-lite nat44, nat44, nat64), to what
> extent a CGN is considered as a scalable solution?

I have added a little bit text to make this part of the document
clearer. In general, the document does not attempt to provide a matrix
of various factors and benefits. We're listing a certain set of tools
mostly because real world networks have used them or are at least giving
serious consideration to them.

Med: Please see my previous answer. Unless you define what you mean by "sca=
lability", "simplicity", etc. this list is not useful.

>
> * The last bullet is not clear: Do you consider that DS-Lite satisfies
> this factor? FWIW, DS-Lite has been rejected by the 3GPP because it
> requires specific functions on the UE.

DS-Lite has been rejected in that particular use case because, well, its
not needed :-)

Med: Oh?! I'm puzzled now with why gi-ds-lite was claimed to be needed ;-).

That's fine. 3GPP networks have native ipv6 to 5 billion
cellphones literally at the flick of a switch. I don't want to say that
its all easy, because there are of course serious problems on many
levels, but one thing that 3GPP networks don't need is more tunnels
because they already have that covered.

Med: FWIW, having an extra tunnel supported at IP level by UEs would be an =
alternative to optimise PDP context/bearers licensing costs and not wait fo=
r v4v6 pdp type (otherwise licensing cost will be doubled), other drawbacks=
 of an extra tunnelling level should be considered also. I agree, this is n=
ot the purpose of this I-D; skip it then.

Lets have them solve their other
problems, like having more terminals that actually support any of this
stuff, ensure that user's eyeballs are happy and not stuck in some
issue, set up the core networks with proper IPv6 routing, figure out in
which situations they can go IPv6-only, etc.

Med: Fully agree.

But back to this document. The factors that we list are really examples
from past Internet deployment, not necessarily something that should be
taken into account verbatim. Version -14 makes this clearer.

Med: The new sentence is fine with me.

> (3)
>
> From the perspective of transitioning networks to IPv6, I don't see
> the rationale behind including techniques such as those listed in
> "4.2. Crossing IPv4 Islands" as a candidate solutions for IPv6
> deployment. This section can be removed to an appendix.

Well, we could argue the philosophy behind this. Is tunneling something
that moves things forward, or are we confessing our inability to change
the part in between?

But again we've chosen to include techniques that have seen world-wide
deployment, and most things in Section 4.2 certainly fall in that
category. If I talk to someone about their IPv6 deployment plans,
techniques in this section are often needed. I think we need to keep the
section, even if I agree with you that the ultimate goal should be
native deployment.

Med: Please keep in mind that in all our internal organisations you will fi=
nd someone who will refer to this section of your document, and we have to =
argue again, again and again why native deployment is preferable, etc. In g=
eneral, people do not care about the RFC track (informational or standard).=
 If you don't agree to move this text to an appendix can you please add a s=
tatement about the ultimate goal, etc, so that to make things clearer? This=
 would be helpful.

>
> (4)
>
> (a) I have an issue with the following statements in the I-D:
>
> On page 6, the ID states:  "The third scenario is more advanced and
> looks at a service provider network that runs only on IPv6 but which
> is still capable of providing both IPv6 and IPv4 services."
>
> and in page 11, the ID mentions:
>
> "   The recommended tool for this model is Dual Stack Lite
>    [I-D.ietf-softwire-dual-stack-lite
> <http://tools.ietf.org/html/draft-arkko-ipv6-transition-guidelines-13#ref=
-I-D.ietf-softwire-dual-stack-lite>].
> Dual Stack Lite provides both
>    relief for IPv4 address shortage and makes forward progress on IPv6
>    deployment, by moving service provider networks and IPv4 traffic over
>    IPv6.  Given this IPv6 connectivity, as a side-effect it becomes easy
>    to provide IPv6 connectivity all the way to the end users."
>
> Taking into account the current DS-Lite specification, this
> recommendation is not justified for the following reasons:
>
> * For Ds-Lite technique to be deployed in a IPv6-only realm, and as
> currently specified in DS-Lite specification, this would mean that
> DS-Lite AFTR(s) are to be located at the boundaries of the IPv6-only
> domain.
>
> * This design choice would lead to non optimal intra-domain paths to
> place communications between two DS-Lite serviced customers.
>
> * This centralised model is not suitable for service providers who
> want to deploy DS-Lite AFTRs closer to the customers.

You may be right, but I don't we're trying to provide perfectly
optimized solution. These are transition tools. Also, DS-Lite is one of
the tools in the small set of IETF-developed transition tools. We've had
fairly large set of people interested in it. Not everyone, of course,
and we already talked about the cellular case above. But I'm trying to
convey the IETF and industry opinion about the transition tools. I don't
think I can suggest other types of solutions.

Med: FYI, DS-Lite is our recommendation to rationale the use of IPv4 addres=
s for our fixed networks. That's said, my concern is more about the technic=
al accuracy of what is stated in that section and not against ds-lite. Depl=
oying DS-Lite AFTR in a IPv6 core domain has several implications and drawb=
acks (see the list above); IMHO this should be mentioned in the text for fa=
irness.

>
> (b) The I-D states in page 11: "Given this IPv6 connectivity, as a
> side-effect it becomes easy to provide IPv6 connectivity all the way
> to the end users."
>
> This wording is not accurate; IPv6 connectivity is not a side-effect
> of DS-lite but rather a pre-requisite for DS-Lite (e.g., DHCPv6 is
> required to configure for instance the AFTR NAME option, dual-stack
> CPE, etc.).

Right. Thanks for the report. I have fixed this in -14.

Med: Thanks, the new text is better.

>
> (5)
>
> * In Section "4.4. IPv6-only Deployment", add a sentence
> to precise that the issues listed
> in [I-D.ietf-intarea-shared-addressing-issues
> <http://tools.ietf.org/html/draft-arkko-ipv6-transition-guidelines-13#ref=
-I-D.ietf-intarea-shared-addressing-issues>]
> are still valid when NAT64 is deployed.

OK

>
> * Page 13, change "SIP (Session Identity Protocol)" to "SIP (Session
> Initiation Protocol)";

Right. I don't know what I was thinking :-)

Med: :-)

>
> * Page 13: "One might position a web proxy, a
>    mail server, or a SIP (Session Identity Protocol) back-to-back user
>    agent across the boundary between IPv4 and IPv6 domains, so that the
>    application terminates IPv4 sessions on one side and IPv6 sessions on
>    the other.  Doing this preserves the end-to-end nature of
>    communications between gateways.  For obvious reasons, this solution
>    is preferable to the implementation of Application Layer Gateways in
>    network layer translators.
> "
>
> (a) Why only listing the back-to-back user agent option (this option
> is valid)? Why not deploying means for NAT traversal is not listed as
> an alternative?

In this part of the text we are talking about deploying a proxy of some
sort. Later in the same section we talk about network address
translators. The latter obviously may benefit from a NAT traversal
solution. But I'm not sure I understand why NAT traversal alone would be
a solution. You have something that converts packets in the network. The
document talks about L3 version of that, as well as L4-L7 gateways.

Med: I'm not suggesting to list only nat traversal techniques but my questi=
on is why listing the b2bua approach only? Several solutions can be envisag=
ed at the application level. Having this discussion in this section is unba=
lanced compared to other section anyway.

>
> (b) "Doing this preserves the end-to-end nature of communications
> between gateways": Which gateways?

Imprecise text. The idea is that the communication from the gateway to
the peer (which might be another gateway) is end-to-end.

I have changed the text.

Med: Thanks

>
> (c) For the SIP case, still there is a need for a translator for media
> flows;

Yes.

>
> (d) Service-related discussions are not elaborated in other sections:
> I would prefer to have a similar discussion for the DS model, in
> particular issues in SIP environments to signal both IPv4 and IPv6
> addresses in the SDP offers; means to prioritise the use of IPv6; how
> the SIP Proxy Server can determine whether there is a need to invoke a
> SIP ALG/NAT64/NAT46 (e.g.., translator should be avoided when a DS UA
> calls a IPvx-only/DS UA. ALG/NAT46/NAT64 should be invoked only for
> IPvx-IPvy sessions), etc.

These would be useful. If you have text, please submit it.

Med: below a text proposal:

"   The IPv4-IPv6 co-existence introduces heterogeneous scenarios with
   combinations of IPv4 and IPv6 nodes some of which are capable of
   supporting both IPv4 and IPv6, and dual-stack.  Some of user agents
   are capable of supporting only IPv4 or only IPv6. moreover, some
   dual-stack UAs are unable to use both interfaces natively at the
   same time which can mean for example that if a UA has to use IPv6 for
   signaling it cannot use IPv4 for media even though the UA supports an
   IPv4 stack (e.g., mobile context).  In order to encourage the use of nat=
ive IPv6 and avoid
   invoking SIP ALG/IPv4-IPv6 NAT, SIP Proxy Servers should be aware of
   the type of the involved user agents before forwarding session
   establishment requests.  Otherwise, SIP Proxy Servers have no way to
   optimise the invocation of IPv4-IPv6 adaptation functions (e.g.  SIP
   ALG and IPv4-IPv6 NAT) and therefore to encourage the use of IPv6 to
   place SIP communications.  In addition, dual-stack UAs should be able
   to include both IPv4 and IPv6 addresses in their SDP offers; with a
   higher priority assigned to the enclosed IPv6 address."


>
> * Add a reference to
> http://tools.ietf.org/html/draft-ietf-v6ops-v6-in-mobile-networks-02
>
Ack

> (6)
>
> It would be valuable if the I-D describes some migration paths and
> examples about the use of the tools listed in the I-D; e.g.,:
>
> * How DS-Lite CGN devices can be removed from the network since it is
> supposed to be a transition solution. This would be a good example to
> apply what is stated in the I-D in page 5: "The end goal is
> network-wide native IPv6 deployment, resulting in the
>    obsolescence of transitional mechanisms based on encapsulation,
>    tunnels, or translation, and also resulting in the obsolescence of
>    IPv4."

We don't have a lot of running code about that yet. Again, do you have
suggested words?

Med: what about something like:

"  Service providers need to investigate appropriate means to remove CGN
   (NAT44) devices from their networks and to extend the scope of IPv6-
   enabled portion of the network.  Various IPv4 address sharing schemes
   may be activated in the network (e.g.  DS-Lite NAT44 and NAT64);
   means and triggers to offload NAT44 to NAT64 may be considered whenever =
appropriate to
   help for reducing maintaining several IPv4 address sharing tools."

FWIW, I attach a figure showing an example of the removal of the CGN.

>
> * How to encourage the use of native IPv6 transfer capabilities:
> address selection issues, application considerations, etc.

This too would be useful. (Text?) FWIW I think we might need another
document or even a set of documents for this particular issue. Some of
this is in the happy eyeballs doc though.

Jari

>
> Cheers,
> Med
> *********************************
> This message and any attachments (the "message") are confidential and int=
ended solely for the addressees.
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.
> France Telecom Group shall not be liable for the message if altered, chan=
ged or falsified.
> If you are not the intended addressee of this message, please cancel it i=
mmediately and inform the sender.
> ********************************
>


*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


--_002_94C682931C08B048B7A8645303FDC9F33C3E619A91PUEXCB1Bnante_
Content-Type: image/png; name="DS_lite-migration paths.png"
Content-Description: DS_lite-migration paths.png
Content-Disposition: attachment; filename="DS_lite-migration paths.png";
	size=39193; creation-date="Tue, 14 Dec 2010 09:57:30 GMT";
	modification-date="Tue, 14 Dec 2010 09:57:45 GMT"
Content-Transfer-Encoding: base64

iVBORw0KGgoAAAANSUhEUgAAA7IAAAF6CAYAAAAkpGQEAAAABGdBTUEAALGPC/xhBQAAAAlwSFlz
AAAOwwAADsMBx2+oZAAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAAJiWSURB
VHhe7b1tbBRXlv/ffwmGQPDDADYGu23jp9jY7TXYOAEDWRyTwQ6PGXA2a2ySAZyBACYQYpLxD5PV
YCJhjBSekkwmaIfEzGRnx0pWIRn9NPKbKH4xq0EaaRRFisRKvxe85GVenn+fYpuUm+quW11P9976
tmTNhK66dev099w6nzrn3vv/UfITwwcWgAVgAVgAFoAFYAFYABaABWABWAAWUMUCDLL4wAKwACwA
C8ACsAAsAAvAArAALAALwAKqWCCmSkfRT1gAFoAFYAFYABaABWABWAAWgAVgAViALQCQhQ5gAVgA
FoAFYAFYABaABWABWAAWgAWUsgBAVqmfC52FBWABWAAWgAVgAVgAFoAFYAFYABYAyEIDsAAsAAvA
ArAALAALwAKwACwAC8ACSlkAIKvUz4XOwgKwACwAC8ACsAAsAAvAArAALAALAGShAVgAFoAFYAFY
ABaABWABWAAWgAVgAaUsAJBN+7lmZmZoenpa+E+pXxudhQV8tgD8x2cDo3mlLQD/UPrnQ+ddWgD6
d2lAnC61BaDvcH6eyIDsDz/8YMDprVu3aHR0lE6dGqbW1rXGX3LP34d/JSX1tHx5QvjPfG5j42qj
vcOHjxrXuHHjhnHN+/fvh/Pr4qqwgEcWSPef4dOnaf3Gjcaf2QcSrW3Uuq5D+M98blt7u9HesaEh
+I9HvxuaCcYC8I9g7IyryGkB6F/O3wW98sYCj+h7+HVau6HF+DPHMPUthZRoF/8zn7t6Tb3R3tGh
Q4h/HP5sWoJsSnTnz5+nbduep3i8mubO/YkBp/H4Olq2bCuVlu6iurqTxl9r6/ue/NXXDxvtxeO9
xjXi8Y3GNefPX0jFxaXU1dVjCBRw61ClODxQC5j9Z3dvL9XU1dG8eY8ZcNq1Yyf1H3+N9g+fpvHf
f2r8/d//+X+e/L079ZnR3qEzo8Y1enpfMK6ZX1BA8fIK2rp9O/wnUCXgYlYWgH9AF1G2APQf5V9f
/3s36/v5PT1UXbucfjJvjgGo67rzaetgjHYdidHJ9x/8vf/f3vwN33jQXu+JmHGNjTsWGtdcmD+P
SsuXUM+2TYh/MshPG5DllD5nWc3QWlraTStWHKDGxrc9AVU3wJtIjFF19SEDcM1w+9JLB2hqaorY
efCBBcKyAPsPZ1nN0Pri4VfprctX6aO/THsCqm6A9+OvZ+jsBx8agGuG28FXXoH/hCWaCF0X/hGh
Hxu3+ogFoH+IQmcLGPpOZlnN0Nr98hw6MBajt//oDai6Ad6xz2N0aPwB4Jrh9sDgAOKfpDCVBVku
1+XSXc64LliQR1wSzFlWGaBVFHgZbsvL+6isrN24B87YXr9+ne7evavzmIF7k8ACKf/hjCtnPLkk
mLOsMkCrKPAy3A6dG6Ont3Qb98AZW/iPBOLSoAvwDw1+RNxCzhaA/nM2HU5UwAIpfXPGNa9gPnFJ
MGdZZYBWUeBluO17M0btzxRQXv5jRsY2qvGPUiDLWUuG146OTqNcl0t3OePa0nIp9IyrKLxmOm7V
qitGxjYe76TCwhKqqVlpiPLevXsKDAvoogoWSPlP17PPGuDHpbuccZ36+z9Cz7iKwmum47747nsj
Y7ujfyBZhlNOTc3N8B8VRClRH+EfEv0Y6ErgFoD+Azc5LhigBVL67tz8lFGuy6W7nHG9NB1+xlUU
XjMdd+WbBxnbzj0LqKRsIa1MrIhU/KMEyH755ZfU29tnZC0ZXmtrjykPrnbg29AwYkBtXt4iI+vM
i1ThAwvkYgH2n/6BgYfwOvbvN5UHVzvwfe/2VwbULikuJs46w39yUU40zoF/wD+ioXTru4T+oX+d
9c/67hvYbWQtGV6Pvas+uNqB78jkA6hdVLSAOOuse/wjLchy6v/NN0eS2cklyZLh1VRZuY84a2kH
gDp+z1lnXqSKQf6XvzyCLK3Oo65H98b+83/OnKGipUtp7aZOOjU+QZy1tANAHb/nrDMvUsVZ6KPJ
FZFR5eCRyBRuBv7x4wJt8A+FhZxj16F/6D9H6ShxGut75Mxw8kV2Pq3eUEj7RmPEWUs7ANTxe846
8yJVXEJ95NhBLeMf6UCWg0yGtfz8xUl43UHNzRciCa9WQM4l1JWVLxhZWs5QYy6tEmNqoJ1k/2FY
KypeSvteO0F/+OvfIgmvVkDOJdSHz5w1srScoYb/BCpNKS4G/8i8wjj8QwqJ+toJ6B/691VgITfO
+mZYW1z0OO145TG68OdowqsVkHMJ9QuvzzGytJyh1in+kQZk2agMZwxpDGtRzb6KZpQ5Q81zaXmB
qDt37oQ8fODyYVuA/YfhjCGNYS2q2VfRjDJnqHkuLS8QBf8JW73+Xx/+4WyLLPiH/5oM8grQP/Qf
pN6Cvhbrm+GMIY1hLarZV9GMMmeoeS4tLxClQ/wTOsjyG5T+/v0GlDGciYIcjnuw9y0vEFVcXG0A
rU5vWIIeCFW9HvvPgcFBA8o4+BQFORz3ILDhBaKeaGoygBb+o6oXZO43/MNZAJ8+LsA/1PYJ6B/6
V1vB2XvP+t4/2GdAGcOZKMjhuAe24gWiqhuSC38mgVbl+Cc0kOUVxM6e/TUtXVpJVVV7AbBJKHUD
5wy0RUUVNDR0knh+AD56W4D959zYGFXV1tHxc+cBsEkodQPnHLBX1dbSqeFh+I8GrgP/cOcPVkAL
/1DHMaB/6F8dtTrvKev71+dGqbJmMe19ay4ANgmlbuCcgbaiupBOvnFUyfgnFJDlVcSqqhqSW+ds
02LrHDcA6uW5XI5dVbWbli2r1H6VMudDnz5nsP80JreX6Xv1iBZb57gBUC/P5XLsg6ffpOq6OviP
wu4C//A2iE/5GPxDDaeA/qF/NZSaWy9Z3w1N5bTtF49rsXWOGwD18lwux9597LHky4Ei5eKfQEGW
ywB4D1hehbix8W1XGUgvAVC3tniBLF7luLFxNX377be5jRY4SzoLsP/wHrC8CvFHf5l2lYH0EgB1
a4sXyOJVjtva2+E/0nlB9jJi+Ic/QbzZx+EfcjoFng/+a5/9APoPR/+sb94DllchfvuP7jKQXgKg
bm3xAlm8yvHqNfXKxD+BgSy/ReEy4ijsASsLGNfXD1NJSQ1dunQ5nJEHV/XMAkYVQ7KMOAp7wMoC
xu9OfUb1TQm6eu2aZ78jGvLHAvCPYIJ4s2/CP/zRci6tQv/Qfy66UeUc1jeXEUdhD1hZwHj4Roxq
Vi6iy1cnpJeJ7yDLtex9fS8bWVjePkYWyItKPx6UG282MuHYP1N6f3ykg+w/vJgTZ2F5ewxZIC8q
/eByyl39+4xMOPxHPv+BfwQfwJt9H/4Rrk9A/9B/uAr09+qs75cP/ouRheXtY2SBvKj0g8uNN/cW
GplwmeMfX0GWl3XmubB1dQMAWJeLObkFb86Ex+N1xG+28FHDAuw/PBf2tbF3ALAuF3NyC96cCV+Z
SMB/JHId+Ee4QbzZp+AfwTsG9A/9B6+64K7I+ua5sAO/mg+AdbmYk1vw5kx4XWOJtPGPbyB78+Yn
ySxsA+bChgywZgDmubOcGT9y5ERwoxGulJMFJicnqbmtDXNhQwbY9LmBnBl//Y03cvpNcZJ3FoB/
yBPEp3yE5w7CP7zTeLaWoH/oPxilhXOVTyZ/Rw2rFmMubMgAawZgnjvLmfETpw6FI4osV/UFZBmU
Kio6iMta3WYScb67bXms7Fdb20vPPbeLuGwDH/kswKC0ObnYEJftuc0k4nzvA57B02/R7t5e+E9I
rgP/8F7TXo4T8A9/HQP6h/79VVi4rTModfT8lLis1W0mEed7b8PeoTzatednUsU/noIsg1FnZ3dy
QadeAKxEmVhrmB1Mzll+Ssk9o8IdZv27OvvPc9u3EweCXgaWaMv7wGfk8lVat2Ej/Mc/d3ikZfiH
9zr2a2yAf3jvGNA/9O+9quRpkfXdvW0jMSgBQL0HUC9tOnh+Lj21vkma+MczkOWJwA0NLfTEE68C
YiWH2BTY8qrGFRXqLLEtz5DrfU/Yf1qT27382wcfAmIlKifOFujzqq0rE83KLFHvvWqDaxH+oU4Q
n/IZ+Id3/gH9Q//eqUm+lljfLW219OrFuYBYicqJs8Evr2pc31QqRfzjCcjevXuXqqsTSZAdAcQq
ArEpmE0kxpKLQDUST6zHJxwLsP+sWrOG3rv9FSBWEYhNBesffz1D/5Scywz/8c934B/qBfHwD+/8
AfqH/r1Tk3wtsb4TreU0Mil3FtLLjKYubY19HqPGVUtDj39cgyyLsK6ulRiIMJ/V+/msQdiUt0Wq
rGwJXYzyDbH+94j958n164mByK8yP7TrbyDE2yKt6VgP//HBXeAf/mo3iLEB/pG7Y0D/0H/u6pH/
TNZ369pKYiDSBe6idh+8LVLLUyWhxj+uQPb+/ftJgG1HJlaxLKwVHPOLCH4hwQMLPsFYgP1n7YYN
yMQqloW1Cv75RQS/kID/eOc78A/1g3hzZhb+4cw3oH/o35li1Dqa9d3eUY9MrCKlxNkAnV9E8AuJ
sOKfnEEWEKtm9jVbhhcwG9yDAEGKPkEKgnXv/Qb+Af/wXlXqtAj9Q//qqNV5TwGx+mWgw4TZnECW
VxfjhZ0wJ1ZPmOX5zjz5Hh9/LMD+wws7YU6snsEKz3eG/+TuO/AP/fzC/LIH/pHdN6B/6D/30VP+
M1nfvLAT5sTqCbM83zno+CcnkOUtdrA6sX4Qa17NmLfmwT6z/jwUeIsdrE6sb7DCq7Xy1jzwn9z8
B/6hr28w0MI/svsF9A/95zZyqnEWb7GD1Yn1g9hU6TGvZsxb8wQZ/zgG2XfeGaeqqm4s7KTBvNhs
ZcY1NS/SwYOH1RgZFerlxYkJ6j1wEAs7aTAvNttCOa+OnqUjx44ppEw5ugr/0DuIT/kM/MPa36B/
6F+OkdifXoxfHKPu/nws7KTBvNhsc2ZffH0+HT76C39EZNGqI5Cdnp6m5csTgFjNITYFuBUVHXTz
5ieBiVH3C7H/tK7rAMRqDrGpYH3zjp00OTmpu6w9uz/4RzSCePiHtctA/9C/Z4OphA2xvhPthYBY
zSE2BbgdPT+lTyZ/F4gShUGWa57j8Tpqbr4AkI0IyK5adYVKSmqk2PA4EG/w8SLsPysTCfrDX/8G
kI0IyH7x3ffJDcMT8B8Bv4J/RCuIZ5iFf/zoGNA/9C8wTCp7COu7rrGELvxZ35LaqG27Y3e/V76J
Uc3KRYHEP8Ig29i4murrhwGxEYHYVFaWVzIuLV0RaL27sqN1lo63JRd34rlhQezbiGvIExTxtjw1
dXXwHxunhn/Io9kgxw/4xwPHgP6hfx3jntQ9rV5TTzx30g5+8L1eNuKVjFfUlvge/wiB7OXLV6mi
ogsQGzGITcFsVdVuGho6qfM46+u9Xbt2jXb2DwBiI5KJTQeBg6ffpFPDw75qTOXG4R/RDOJTfhJ1
/whK/7FYjNL/vHppwe06bSuXc8zXEDk/0zHmfxdpx+m9OTled/1fvfYudfXmAWIjUlKc/jJi97HH
6OQbR30NUWxBFiXF+q5OnG2xJ/N3XGJcWtpAd+7c8VWMOjaOkrFoB+mpEsrmtjb4j4WDwz/gH1xi
HFX/CFL/VsDmFcTl0k4u53gFsk7bcQKmTo/VWf8oKdYrw5pLxpxLjBtWLfY1/rEF2f7+/clVivci
GxvRbKx5Sx4uL8fHmQUODA7S8XPnHb+tdvowxPFyAwGXlXP5ID6zLQD/kFu3QY0rUfWPIPWfS3Yy
/RxzRlcUBq3OEf231DVSx2e7phNQTx3rtB9++YOu+t8/2Ed735qLbGxEs7HmLXm4vNyvT1aQnZmZ
SS72Uw+IjTjE/riKcRdxmTk+YhZg/0m0tgFiI1pSnB70cHk5lxHi88AC8A9ArNlHouYfQevfLcha
Qa0ZNK0gT/ScXI4TKQ92es/Z+uEXxKba1U3/rO/6FqxSnEsWU8dzuLycy8z9+GQF2ZqaldTQMAKQ
BcgaGuAVq4uKlvs+cdsPoYfRZlNzM713+yuALEDW0ACvWF1WXg7/+V9nhH8AZM1wEDX/CFr/TqGO
f5ts5b9uQNLLtkX7mCmbm+0+3JY/O4Ff3fS/MrGCRiZRWqsjlOZyT7xi9fL4Il/in4wgOzU1RWVl
7YBYQOwsDVRUbKHx8YthcKFS12T/eXpLNyAWEDtLA3sOHKSJiQmltOxHZ+EfgFirID8q/hGG/r0A
WXMprhUAOinVzVa2LArJViXHIiXPmdpPv78gQZb7rYv+Wd/tzxSgpDjiJcXpwLtl7+N0ceKC5yFF
RpBFNhaLPFktBoWsrJgPBv223cmbXxwbHkTo9tZdzBsePQr+EZ4GZfb/qPhHGPp3C7Ki5b/Z9JUN
IEUypm6OETk3aHBNt5Uu+kc2Fploq6ytX1lZS5Dl1WmLi6uRjUU21lID8XgnXb9+PdcYVvvz2H+e
aGpCNhbZWEsN7EjOlY2y/8A/ALHZYEd3/whL/yKLIYnCanomVASS08uJ7bKiVvNvRUHYydxdWUqL
U31WXf+s7+oGZGNzKb+NwjmdexZ4Hv9YgmxXVw9VVx8CyAJkLTXA86Y5Y4+PtQW2bt9OZz/4ECAL
kLXUAM+b5oxMVD/wD4BsNpDV3T/C0r9o2Wym8uEUiKbAT6T813xOplJiM3RatZ1+3UyQmgnUre47
ve9W/x1WdlZ1/fds20SHxpGRjAKU5nKPPG+aM/Zefh4BWWRjUVIssr8sz5/meRD4zLZAWG/bZS4X
RN8eBReePx1F/4F/AGJFxgNd/QP6h/511j+ysQB4Ebjl+dNexj+PgOyJE6eovPznyMYiG5tVAytW
HKBt254Hx6ZZ4I3hYTow/CayscjGZtXAW8ltrHb39kbOf+AfCORFAnld/QP6h/511v+p4eP086Nz
sMgTFnnKqoEDYzF6fk+PZ/HPIyBbXFxKicQYQBYgm1UDq1ZdoQUL8nxZStszdYfQULy8gj7+egYg
C5DNqoEvvvue8gsKIuc/8A8E8iKBvK7+Af1D/zrrv7R8CY19jqykSFYyysdc+SZGefmPeRb/zAJZ
3sC4pKQeEAuIFdJAPL6Obt26FQIuynnJoDe4F3kg4hh5A6euHTsj5T/wD3m1KOM4oZt/QP/QvxM/
U03/rO/6lkJkY5GNFdLAuu58z+KfWSCLsmLMjxWZH5s6BuXFs4EaZWMIVJwEKrqWT2Z6zQT/gH9E
2T+gf+hfZ/2jrBiZaCdZZi/Li2eBLMqKAbJOQBblxbNDdpSNIVBxEqjoWj6ZCWThH/CPKPtHGPrP
tAqw3fY0dr9TLiv6ZloZOH0rH5FrOz3Hrk3z99nuLZf7dnJt87GqPR9QVgyQdQKyXpYXPwTZu3fv
UmFhiVBJqRPYwbF6w/Hy5Qmanp6Ws9Y3wF6x/5SWl2NuLObGOtJA67qOSPgP/AMQm0tAr4t/hKH/
bFvMZNrSRvQ3ygXo7LbrEWkz2z63on23O86uH3bf27Xv5HtV9M/6LilbKFRS6gR2cKzecJxoL/Qk
/nkIsrwUMm+pAvDUGzy9/n3Lyp6lS5cuBYiMcl6K/Ye3jHDykMKxCO537z8YCf+Bf0DruYx3uvhH
GPrPBWTNe66m/17mLGimPWFFs5mZ9nzNlCm2yyxn0lam+zG3lwmORf89F12LnqOK/lnfvKUKwFNv
8PT69322b54n8c9DkB0ZOZME2e0AWSz05EgDlZX7qLe3T066DLBXZ0ZHaeD4CYAsMrKONHBqfIL6
BwYCVGo4l4J/AGRFg3fzcbr4R9D6t4MwKzDMlu3MBsWiWVInGVmR/ttlRu3uJ1N/MkGzXf9z0bfd
Oaro/8yZX9H2V7Dtjtegp3t7+0Zj1Dew23VQ8hBku7p6qLr6kCOI8Tq7h/bUywY3NIxQTc1K10JU
vYGt27fT2Q8+dAQxdg8xfK9/8P/e7a+oqblZdfnb9h/+ob+W/RivdPGPoPUvAoKp8mK7LGj6cU7O
yzT31JwpNWd6rY53AtHZ5rpmA1E3UOuH7lNtqqL/nm2b6NA4spG6g6fX9zcyGaOViRW28YPdAQ9B
Fgs9qQeRMoA/Fnx64GJhLOTh5wMUbQcDHqot6GH3QMFCT8HoJir+qYt/BP18CBpk08HUSp9OM5pO
ssZWJcR2GdlskJ0O96JZZ6/9UhX9Y6EnQHwukOvVgk8GyN6/f5/mz1+IbCzKinPSQHFxNd25cyfX
GFf589h/8gsKkI1FWXFOGniiqUlr/4F/AG7dBPiq+0cY+g8aZEV+Xz9B1g6cnWSRrfoZFshyv2XX
P+t7Yf48zI/F/rE5aaC6ocB1/GOArA4rFvN9pDKUVmTkJHtpbsvJeXbH+tWu3XX9/j7qKxeHsSKl
SOBgd4xIeZddG5m+t5u/JBJ4OL12Ltd0eg0/jldlZcpc3zjJ4h9R1Hsmn3AKFX7oXrRN1f0jDP2L
ZiNzKbd1AoUiWc9sOrADyGxjvqgNcrmfIJ81sutf5RWL+XdMZRKtng8iWUbzeSLHOz3G3Een56pw
vBcrFxsgOzMzQyUl9Tll4/yGJNH200E2/TxRiEwFa6LXdXKcaB+ctCnDsfH4Orp161auca4S5/Fg
nenD/pNobcspGycazPlxnNXD2KsHdC7t5HJOtjlRftjMjza7duxU3n9U8I8o6l3Ep0SO8UP3om2q
4B8y6j8TpNrBayowT/990gP99LE303npZbrp4OgEZFPn2l3LfE2rY3OFXCd9F9W33XEy6N9O3/Ut
hTll48IGrXSQTe+PHUSmf293fC7360ebufTDr3PWdee7jn8MkOV9QDmrJgMU5doHUZBNh0mr/xYB
TjPUmPucOtcKiM3fWZ2T672HfV48vpFu3LihBJDm2snR5KrElZWVlvfJ/sNvTe0eSLJ9n0u2xioA
EAkU7IIec5BkF4SYg5lsICt7gJ7qe0/vC8r7jwr+EUW9292zU78LYwxTwT9k1L8q418YmnJyzWzQ
66SdXI+VQf92+uasml+g42e7oiCbCVidQqZ5vDXfV6qd1PeZvrP6dz/tE0TbG3csdB3/GCDL2TTO
qoUNRG6u7wXIZgJNu+xu+rUz9UVXkC0t7abz58/nyohKnMcDeWqQSQda9h9+a5rrgyqs8+yCXKu3
z3Zv863evovCZi5tZzpHpSDuxcOvKu8/KvhHFPXu9J7DDtqtxkIV/ENW/as0Dob1HHSSEQ7DnjLo
307fnFULAnq8voZXIGsFoHbZ3fRrZ+qLGXJ1BNnul+e4jn8MkOVsGmfV3IBk2OdawaRI1jRTNjXb
/WTL6op+JwrNYdtV5PrLlm0lHuh0/pgH8nSgZf/ht6YyPoidPKRFSsCyPcizgagd4NqVbDlpO4xg
w81v33/8NeX9RwX/cAp1XmrSSh9e+ZJoO5leKIm+QHKjcTfnquAfKujfzW+Ac8NbsE0G/dvpm7Nq
XkNmEO1ZwaRI1jR9Xq35vzP1O1NWl48X/S4T1AZhK7+usXUw5jr+MUD2+vXrSZDt1ApkRUDULnPK
bVjBsCisps43L0KV/v/T2xIBR9mOYZDlLKV5AIjS/1+8eDFt3vV8JEE2/XdOB1bz93Ylw1bZoEzn
ZwKD1PEqBV4cqOjsP7L4hxcgq5rend6z1bgdti+p7h+y6D/s3xHXzw2GZdc/63tdz3wtQDYbrFlB
ZCYAtYJhUVhNB1urTG16W35BZhDtegayOmZkcwHZ9IxipjYAsrP33I1qRpYHk5deeokuXLgQyYys
FXiKZF7dZoacBueyB1AyvHF3W01h9cZeNv/IRTei2cpsWdEw9e70nkXvI0ifUsE/VNB/kL8ZrpUb
tFrZTQb92+lbl4ysVyBr1Q5A1nqvXc9ANgqLPdnNc3Wy+JIXIJuerZUty+qkP1FZ7Mn8lo0BNrWS
n06LPWWD0/RSy/QgP1vQnwlwM50j2rbI+bIHVTIs5uE1yMroH1aQprve3YKsDGCrgn+kB/oy6l/2
cRD9s4ZfGfRvp29dF3tyMs/VqkQ425xWq0yrVYlyNgAOImPq9zU8W+wJIDs7wyhS7ms3/zZbObHV
d07AUbZjowSy5gAlpQGVQTZTqWR6Fsl8nNV32SA3PUARaSvVXiqQtgIOJxAic5AkQ6DiFcjK7B/p
Ws8GeSIaFXlxY9axnYZT10z3pXRfEHkpZFXGn8nXzdfN1t+wfEgF/0gF+jLrP6zfD9d1l52VQf92
+o4qyKbgNTWG2kGfeQz2AnLtrqfC956BLGeWCgtLlJ4jKxvcifRHBJhF2gn7GN66iWFO5w/fX6a9
1MLY8B7BgbvgQCb7yb7hvYhfwz/00aNMvsF9UcE/oH93+pch8y+b7lP9kUH/dvouKVNzsScVQM8u
K6ziPZj7zC9B3PKDsdgTQHZ2RjYIMNQFYtlWJSX1NDMzIxLvankMQNZdECNrABFUvxKtbVr7D/wD
/uHGl1T3D+jfXv8A2cw2kl3/rG+ArPX8T68hM73M2Ov2w2ivvqXQdfxjgCx/FizIo5aWS8jKJsEs
CJDV6Rrz5y+k+/fvawmpojeVX1BAU3//h3IrF7sJMHGufYAmYiPWju7+A//wRisietLtGB38A/q3
1r9oub9umnZyPyroP69gPl2aDgbmwoAtXNO/33Zh/jzX8c9DkG1tXUt1dScBcQBZRxpIJMaouLhU
lPe0PW79xo00/vtPAbLJUkAnD+moH/vx1zMUL6/Q1i9SNwb/gF/k4uu6+Af0n13/yMha20cV/a/d
0EIn3/cPdgCSetp27PMYlZYvcR3/PATZw4ePJveS7XUEMTplFXEvuWWiq6sPUVdXj2shqt7AsaEh
OnRmFBAHkHWkgbMffEhbt29XXf62/Yd/AGRzAVld/AP6B8jqrP+jQ4eo94SesAWI9u93PTQeo55t
m2zjB7sDHoKsDnvJAkZzg1E3disr204jI2fsdKb99+w/vLpgLg8rnBPdIH/g+Ak6MzoK/8ALEIwd
FhrQxT/wfIjuGO/m+a6K/lnfqu4lC1D1D1TtbLv9lTl05syvXMc/D0H2zp07yRLRamRkUVrsSANl
Ze00NTXlWoiqN8D+80RTE4JRAIkjDTy9pTsS/gP/QCCfS0Cvi39A/9C/zvpnfVc3FJAduOD78KBR
Rtu3P5NcW8YDfngIsljwKfhspptMqCznYqGnHxEcC3ogWHEarKiwkIdXL5ngH/CPKPsH9A/966x/
LPgESHUKy14s9MTxySyQ7e3to8rKfY4ycrIAFfoRPIg/WBxsrVdxrvLt9A8M0KnxCUcZOacPNhyv
TzDEi4PxIjBR+cA/9NFuEOOQbv4B/UP/TvxGNf33DeymfaOAOacwF9XjeXEwXiTMi88skP3yyy+p
tHQ1QBblxUIaiMc76fr1617oUIs22H/WbuoEyKK8WEgDO/oHIuU/8A8E8k4Ced38A/qH/nXWP+t7
9YZClBf/N2BeBM479yzwLP6ZBbI//PADFRQsxn6yAFkhkM3LW0T37t3TAkK9uAn2n6KlS7GfLEBW
CGSXFBdHyn/gHwjknQTyuvkH9A/966x/1vfi4jzsJwuQFXqZsahogWfxzyyQ5WAe5cXBl+iqWBaN
smJr9EX5GIIVkWBFtbIxL170cBvwD/hHlP0D+of+ddY/youRjRXJxnpZVvzIHFn+B5QXA2RFwBpl
xdahPcrHEKiIBCq6lU2Kgi78A/4RZf+A/qF/nfWP8mKArAjIellWbAmy/I81NSupoWFEqLxUBHpw
jF5w3NJyyShB51ISfB61QFNzM713+yuh8lKRhxqO0Sv4mfr7P4wS9Kj6D/xDLz17PT7p7h+66z8W
iz3y7ON/S/2Z9WJ1LH+f+nfzeVbne609GdpTXf8rEytoZBJAJwJ0UTzm0nTMKEH3Mv55pLSYw/Jb
t25RPL4OIIu5spYaqKx8gX75yyNg2AwWYP/p2rETIIu5spYaOHzmLB0dGoqs/8A/ALLZgEF3/9Bd
/+lw6ua/M4GuDMDpVx9U1z/re113vtA8ySiCXNTv+YXX59CRYwc9jX8sQdZYlKBoOTU3XwDMAmZn
aWDVqiu0aNEyzyZpe6pmSRpj/ykrL6c//PVvgFnA7CwNfPHd91Sa1EaUF0mDfwBkM0FAFPxDd/2b
4dMu42rOvqY0IXK+XxAZdrs66J/1vTy+iC78GVnZqENr+v1f+SZGy8ryPY9/LEGWeWB8/CJVVGwB
yAJkZ2kA2VgxWp6YmKA9Bw4CZAGyszSg+tt2MfXbHwX/AMxaQUNU/ENn/ecCouZSYpHS47CB06/r
66L/ixMXaMvex5GVxQrGszTgRzY24xxZ/gJZWb3mtXo1T7m4uJru3LljH6lG/Ajd37r79SDXvd0n
mprgP//7fEHVAmA23d+j4h86Px9yAVmrzGzq3zLNr9XxWaGL/pGVRTbaKhtd3VDgS/yTMSPLHHL5
8tVkVrYLWVlkZQ0NVFXtpf7+/RFHVPHbv3btGu3sH0BWFllZQwPHz52nA4OD4gLS/Ej4B0DWDCNR
8w9d9Z8LyCIjq9/z4eq1d6mrNw9ZWWRlDQ3sfWsu7R/s8yWqyQqyfMXGxtVUXz8MmI04zPJ86WXL
Kun+/fu+CFHXRtva2+ndqc8AsxGHWZ4vXV1XB/9Jc3T4B2CWYTaq/qGj/kVANtsxIufrlo3VVf+r
19TT8A1kJ6M+V5bnS1fWFPkW/9iCLJeRcjmpV6WpaEfNkuWKig66efMTXXnTt/ti/+FyId0evLgf
ZwCyObmK9eTkpG86U7Vh+IczHenqd1H1Dx3172aV4vQS46isWqyr/lnfXE4adZCL+v139PyUPpn8
nW9hii3I8pV5qxVe5AcQqiaEuv3dqqsPUVdXj28i1L1h3mqFF3HQNQjFfWWHkbMffEhbt2/XXeY5
3x/8I9owG3X/0E3/Xu8jq/vzRXf981YrvMhP1GEuqvd/aDxGPds25RwfiJwoBLJY+CmaAMsAjO12
RNwo+zE6L+yhe5Dh9v502E7BvQfAP9zqSNfz4R8PFtbEwmfRfJkTBf1j4afollb7td1OekQhBLJ8
0szMDMXjzQbYuM3w4Xx1wLi8/En6j//4T79jWe3bZ/9p6+ggfnDpGpTivh4Nxp7e0k1/+tOftNe3
2xuEf0QzkId/PPAc6B/6dzuGynw+67v5ySXEYBPVzGQU7/vJZxbRf/7pU9+lKQyy3JN33hlPrlzb
DZCNyMJPNTUv0sGDh30XYVQucDG5t2wv9paNDMi/OnqWjhw7FhV5u75P+Ee0gnn4x2yXgf6hf9eD
qMQNjF8co+7+fIBsRFYxfvH1+XT46C8CUaQjkOUePffcLqqtHQTMag6zdXUnk7/x2kBEGKWL7O7t
pZHktlbIXuodtIz//lNav3FjlKTtyb3CP/T2i9S4B/+wdhfoH/r3ZCCVtJFde35Gg+fnAmY1h9mT
78do7YaWwFToGGS53r2qqiG5Lc/bgFlNYZa32onH6+jevXuBCTEqF2L/aWxupo/+Mg2Y1XRLHt5K
YWUiAf/JwanhH/oH8vCPzI4B/UP/OQybypzC+m5oKqe3/4gSY11LjXmrnbrGkkDjH8cgyx5z9+5d
Ki2tpZaWS4BZzWCW50DzXGie04CPPxZg/2lIgs7U3/8BmNUMZnkONM+Fhv/k7jvwD32DefiHvV9A
/9C/vUrUPYL1XdtYRJemAbO6wSzPgea50EHHPzmBLLsQ7w9VWdkCmNUIZBliq6rW0n/91xfqjpKK
9Jz9Z03HesCsRiDLQfqm7h66ffu2IiqUt5vwD/2CefiHuL9B/9C/uFrUO5L13fJUCWBWoxJjhti1
m5fSF7c/C1yQOYMsYFadlYdFVokGxAbue8bLIMCsHgELgnTv/Qf+oYdv8LxY+Idz/4D+oX/nqlHn
DMCsPhnpMCGWFe8KZLmB6elpqqhoxbY8imdmKyo66ObNT9QZBTXpKfvPus5ObMujeGZ2846dNDk5
qYkq5bkN+IcewTz8Izefgv6h/9yUo8ZZrO/WjdiWR/US446en9Ink78LTXSuQZZ7zqWoDLOYM6te
lvZBJnYTXb/+m9BEGPULcykqwyzmzKoXtHCm6bkXXqDffvRR1GXs2/3DP9Tzi9TqxPAP924B/UP/
7lUkbwtcisowizmz6mVoORO7adci+s1vr4YqME9ANpWZjccbKZEYwwJQimRn+cUDv4AAxIbqg8bF
+c3kP7W10cdfz2ABKEWys/zigV9AAGL99x/4h3rBPPzDO7+A/qF/79QkX0us78ZVS2nsc/VgTvVs
aq795xcP/AIibIj1pLTY7BLffvttEozqqb5+GDArOczyCwd+8cADCD5yWID9Z2Wimd6d+gwwKznM
8gsHfvEA/wnOd+Af6gTz8A/v/QL6h/69V5U8LbK+65tKafgGYDZXuAzqPH7hwC8eZIl/PMvIptzh
/v37yRLjp6i2dhAwKynM8osGfuHAAwc+clmA/Wfdho00cvkqYFZSmOUXDfzCAf4TvO/AP+QP5uEf
/vkF9A/9+6eu8FtmfT+1vokGz8+loKAM13H24oBfNPALB5niH89Bll2BNz1+7rldtGLFNiwCJRnM
1tS8bLxo4AEDHzktwP6zu7eX+l49gkWgJIPZN8YnjBcN8J/wfAf+IW8wD//w3y+gf+jff5WFdwXW
9649P6Ntv3iceA4mQFMeG7x8dq7xokG2+McXkE25wNmzv06WrzZTY+PbyM6GDLTNzReotHQ17d79
r8aLBnzkt8C5sTFq6+igj/4yjexsyED7h7/+jdZu6qS9AwPwH0lcB/4hT0AP/wjeKaB/6D941QV3
xV+fG6XmJ5fQ23+UB+SiCtUX/hyj1RsK6V/7d0kZ//gKsiz5mZmZ5Kq4DVRXNwCYDQlma2uP0bJl
lfTll18GNwrhSp5YgP2nsbmZXht7BzAbEsyO/ftNqq6rg/94omhvG4F/hB/Mwz+81bST1qB/6N+J
XlQ7lvXd0FROA7+aj8zsf4cD9MfejVFlTZHU8Y/vIJsqNe7re9nICHJmsDUkoIvadR+sSvzP1NHR
KV0pgGoDapj95Qz6gcFBIyPImY/U1hb4X3+DGF519bneF6jr2WfhP2E6gM214R/++kGmcQb+IYdT
QP/QvxxK9KcXrO+XD/6LkRHkzGBUs6JB3zevSvzPOwuoc7P8UxEDAdmUvDkjyJnBqqrdmDvrM8xX
Ve2lpUsr6Te/+a0/owtaDdwC7D+cGTx4+k3MnfU5O3v83Hmqqq2jj7A/bOA6z/WC8I/gAnr4R64q
9e886B/6909d4bfM+ubM4O5jj2HurM/Z2b1vzU3aenFya8EPwv/hBXoQKMhyf3iS8NDQSSopqUmu
bHwM2VmPgZZXJC4pqaf+/v107949AQngEJUswP5zang4uWpcgrikD1lZb4MXXnE10dpmZMDhPyp5
xoO+wj+89Yf08QX+IbdPQP/Qv9wKddc71vfJN45SzcpFxCWvQWcpdb+esSJxSyHtH+xTKv4JHGRT
Mualm7nklcuNsRjU+66Bnku24/F1SVuuNuYl46O3Bdh/uOSVy42xGJT74IVLtrt27KS29nb4jwau
A/9w7xNmiIV/qOUU0D/0r5ZinfWW9c0lr1xujMWg3AM9l2yv686n1WvqlYx/QgPZlGy5XCAer07+
baREYsw10EVtHiwDbEXFFioqWk63bt1yNhrgaOUtwP5Tkyw37knO5fz46xlkaB2WHHOAvufAQSor
L4f/KO8Nj94A/MNdQA//UNspoH/oX20FZ++9UU5fu5w27lhIY5+7BzrdM67p98cAu2Xv47Q8vkjp
+Cd0kE3J9MaNG1RcXGpkFRsaRgC0NiXHDP0M/wyw4+MXpVwSW+cBVLZ7Y/+Jl1cYWcX3bn8FoLUB
WoZ+hn8G2ImJCfiPbIL2uD/wD2cBPfzDYwGG3Bz0D/2HLEFfL8/6Li1fYmQVRyYBtHZAztDP8M8A
e3HigvLxjzQgm1I5ZxVralYaJcd1dScBtGlAy5DPsM/Qz86LPWF9HR+Va5z9pym5XQ+XHI///lMA
bRrQMuQz7DP0w3+Uk7frDsM/sgf08A/XEpO6Aegf+pdaoC47x/pemVhhlByffB9Amw60DPkM+wz9
OsU/0oGsueS4tXUtLV4cp/Lyn0d62x7eRqe8vC8Jr9UG5KOE2OVoF4HTueRm/caNtKK2lg4Mvxnp
bXt4m5Chc2P0RFOTAfnwnwg4gM0twj9+DOjhH9HzB+gf+tdZ9azvtRtaKF6dTz8/OifS2/bwNjp9
b8aouqHAgHwd4x9pQTblZDyp+8SJU1RYuMTI0q5YcSAyW/fwqs6cfS0oWEwvvXSA7ty5o/PYg3vz
wQLsP28kVzkuWrrUyNK+dflqZLbu4VWdOfvK9z74yivwHx/0pXqT8A/4h+oadtN/6B/6d6Mf2c9l
fZ8aPk5LipMLGSWztAfGYpHZuodXdebs6+LivOQuDANaxz/Sg6zZUfgty7Ztz1N+/mJjfihDLWcr
dVngadWqK1RdfSh5b51JcC8xVnXmtycoH5Z9uFSjf+w/u3t7qah4qTE/lKGWszG6bOHzxXff09kP
PqQd/QPJ0plyY1Vn+I8a2pShl/APGX4F9CEsC0D/YVke1w3CAqzv5/f00OKix435oQy1nK20m0+q
yvdXvonRofEYde5ZQCVlC41VnaMS/ygFsimx815SXN/NULtgQZ6xb2pp6S4lF4nirYfi8V4j2zx3
7k+oq6uHrl+/Tnfv3g3Ct3GNCFog5T8MtfkFBca+qfuHTyu5SBRvPXTozKiRbZ732GO0dft2+E8E
Ne3lLcM/vLQm2lLNAtC/ar8Y+uvEAil9M9TmFcw39k3ddSSm5CJRvPVQ74mYkW3+ybw51LNtUyTj
HyVBNl20vG/qqVPDxvzRvLxFBhQuW7aVuDSXt6eRJWPL2WNewIr7VlbWbmRdeeuhw4ePEr8twgcW
CMMC7D/Dp08b80eXFBcbUNh//DXi0lzefkOWjC1nj3kBK+7b01u6jawrbz10bGgI/hOGcCJyTfhH
RH5o3KalBaB/CENnCxj6Hn7dmD+6qGiBAYVbB2PEpbm8PY0sGVnOHvMCVty39mcKjKwrbz10dOhQ
5OMfLUDW7GT37t0zftTR0VGjNJfn1prhlhdNYpisrx/2DXB5ZWG+RmXlvlnQytljXsCK+zY1NYWs
q86jo6L3ZvYfLs3l+aVmuOVFkxgm3536zDfA5ZVT+RqnxidmQStnj3kBK/iPouLSoNvwDw1+RNxC
zhaA/nM2HU5UwAJmfXNpLs+tNcMtL5rEMDl8wz/A5ZWF+Rr7RmdDK2ePeQErxD+PCkk7kLXyFbM4
edEkhsnGxtUUi8WMv+XLEw//Sku7DfgU/TOfy6XB3B5nhvkavb19EJ0Cgxe6mN0CZv/hRZMYJtva
2x/6T+u6Dkr9vXj4VQM+Rf/M586b95jRJmeG+Rr9AwPwH4hTegvAP6T/idBBHy0A/ftoXDQdugXM
+uZFkxgmV6+pfxj/JNoLKfXX/fIcI2Mq+mc+l0uDOf7hzDBfo29gN+IfwV8/EiBrZ4vp6WlK/Z0/
f94Qj+if+VwsymRnaXyvowXgPzr+qrgnrywA//DKkmhHRQtA/yr+auizqAWgb1FL+XccQNY/26Jl
WAAWgAVgAVgAFoAFYAFYABaABWABHywAkPXBqGgSFoAFYAFYABaABWABWAAWgAVgAVjAPwsAZP2z
LVqGBWABWAAWgAVgAVgAFoAFYAFYABbwwQIAWR+MiiZhAVgAFoAFYAFYABaABWABWAAWgAX8swBA
1j/bomVYABaABWABWAAWgAVgAVgAFoAFYAEfLACQ9cGoaBIWgAVgAVgAFoAFYAFYABaABWABWMA/
CwBk/bMtWoYFYAFYABaABWABWAAWgAVgAVgAFvDBAgBZH4yKJmEBWAAWgAVgAVgAFoAFYAFYABaA
BfyzAEDWP9uiZVgAFoAFYAFYABaABWABWAAWgAVgAR8sAJD1wahoEhaABWABWAAWgAVgAVgAFoAF
YAFYwD8LAGT9sy1ahgVgAVgAFoAFYAFYABaABWABWAAW8MECAFkfjIomYQFYABaABWABWAAWgAVg
AVgAFoAF/LMAQNY/26JlWAAWgAVgAVgAFoAFYAFYABaABWABHywAkPXBqGgSFoAFYAFYABaABWAB
WAAWgAVgAVjAPwsAZNNsOzMzQ9PT08J//v00aBkWgAVgAVhAJwvg+aLTr4l7cWoB6N+pxXC8ShaA
vsP5tSIDsj/88IMBp7du3aLR0VE6dWqYWlvXGn+xWOzhX0lJPS1fnhD+M5/b2LjaaO/w4aPGNW7c
uGFc8/79++H8urgqLAALwAKwgO8WSH++DJ8+Tes3bjT+zM+IRGsbta7rEP4zn9vW3m60d2xoCM8X
339RXMCJBaB/J9bCsapZ4BF9D79Oaze0GH/mMbq+pZAS7eJ/5nNXr6k32js6dAjju0OBaAmyKdGd
P3+etm17nuLxapo79ycGnMbj62jZsq1UWrqL6upOGn+tre978ldfP2y0F4/3GteIxzca15w/fyEV
F5dSV1ePIVDArUOV4nBYABaABSSxgPn5sru3l2rq6mjevMcMOO3asZP6j79G+4dP0/jvPzX+/u//
/D9P/t6d+sxo79CZUeMaPb0vGNfMLyigeHkFbd2+Hc8XSTSiczegf51/XdybWd/P7+mh6trl9JN5
cwxAXdedT1sHY7TrSIxOvv/g7/3/9uZv+MaD9npPxIxrbNyx0Ljmwvx5VFq+hHq2bcL4nkGe2oAs
p/Q5y2qG1tLSblqx4gA1Nr7tCai6Ad5EYoyqqw8ZgGuG25deOkBTU1PEzoMPLAALwAKwgHwW4OcL
Z1nN0Pri4VfprctX6aO/THsCqm6A9+OvZ+jsBx8agGuG28FXXsHzRT45Kdcj6F+5nwwddmABQ9/J
LKsZWrtfnkMHxmL09h+9AVU3wDv2eYwOjT8AXDPcHhgcwPie/J2VBVku1+XSXc64LliQR1wSzFlW
GaBVFHgZbsvL+6isrN24B87YXr9+ne7evevABXEoLAALwAKwgJcWSD1fOOPKGU8uCeYsqwzQKgq8
DLdD58bo6S3dxj1wxhbPFy9Vom9b0L++vy3ujIzpfswPnHHNK5hPXBLMWVYZoFUUeBlu+96MUfsz
BZSX/5iRsY3q+K4UyHLWksXX0dFplOty6S5nXFtaLoWecRWF10zHrVp1xcjYxuOdVFhYQjU1Kw1R
3rt3D+MOLAALwAKwgM8WSD1fup591gA/Lt3ljOvU3/8ResZVFF4zHffFd98bGdsd/QPJMrVyampu
xvPFZz2p1jz0r9ovhv46sUBK352bnzLKdbl0lzOul6bDz7iKwmum46588yBj27lnAZWULaSViRWR
Gt+VANkvv/ySenv7jKwlw2tt7THlwdUOfBsaRgyozctbZGSdeZEqfGABWAAWgAW8tQA/X/oHBh7C
69i/31QeXO3A973bXxlQu6S4mDjrjOeLt5pSqTXoH/pXSa9O+8r67hvYbWQtGV6Pvas+uNqB78jk
A6hdVLTAyDrrPr5LC7Kc+n/zzZFkdnJJsmR4NVVW7iPOWtoBoI7fc9aZF6likP/lL48gS+t0JMPx
sAAsAAuYLMDPl/9z5gwVLV1Kazd10qnxCeKspR0A6vg9Z515kSrOQh9NroiMKiD9XQX6/3EBNuhf
P72zvkfODCdf1OXT6g2FtG80Rpy1tANAHb/nrDMvUsUl1EeOHdRyfJcOZPkhyrCWn784Ca87qLn5
QiTh1QrIuYS6svIFI0vLGWrMpdVvAMYdwQKwgH8W4OcLw1pR8VLa99oJ+sNf/xZJeLUCci6hPnzm
rJGl5Qw1ni/+6TCslqH/zCuIQ/9hqdK767K+GdYWFz1OO155jC78OZrwagXkXEL9wutzjCwtZ6h1
Gt+lAVk2KsMZQxrDWlSzr6IZZc5Q81xaXiDqzp073o0EaAkWgAVgAc0swM8XhjOGNIa1qGZfRTPK
nKHmubS8QBSeL+o7A/TvbAss6F8tzbO+Gc4Y0hjWopp9Fc0oc4aa59LyAlE6jO+hgyy/Qenv329A
GcOZKMjhuAd73/ICUcXF1QbQ6vSGRa1hFL2FBWABGS3Az5cDg4MGlHFwKgpyOO5B4M8LRD3R1GQA
LZ4vMio8e5+gf2cAm+730L/cmmd97x/sM6CM4UwU5HDcA1vxAlHVDcmFDZNAq/L4HhrI8gpiZ8/+
mpYuraSqqr0A2CSUuoFzBtqiogoaGjppLC2ODywAC8ACUbUAP1/OjY1RVW0dHT93HgCbhFI3cM4B
fVVtLZ0aHsbzRQGngv7d6d0KaKF/eYTP+v71uVGqrFlMe9+aC4BNQqkbOGegragupJNvHFVyfA8F
ZHkVsaqqhuTWOdu02DrHDYB6eS6XY1dV7aZlyyq1X6VMniEVPYEFYAGZLMDPl8bk9jJ9rx7RYusc
NwDq5blcjn3w9JtUXVeH54tMgk/rC/TvLcSmfAj6l0P0rO+GpnLa9ovHtdg6xw2Aenkul2PvPvZY
8uVAkXLje6Agy2UAvAcsr0Lc2Pi2qwyklwCoW1u8QBavctzYuJq+/fZbOUYf9AIWgAVgAR8twM8X
3gOWVyH+6C/TrjKQXgKgbm3xAlm8ynFbezueLz7q2WnT0L8/AJvuv9C/U2V6czzrm/eA5VWI3/6j
uwyklwCoW1u8QBavcrx6Tb0y43tgIMtvUbiMOAp7wMoCxvX1w1RSUkOXLl32ZiRBK7AALAALSGgB
o8onWUYchT1gZQHjd6c+o/qmBF29dk1CRUSrS9B/MBBr9j3oPzgfY31zGXEU9oCVBYyHb8SoZuUi
unx1IrgfOscr+Q6yXMve1/eykYXl7WNkgbyo9ONBufFmIxOO/QFz9BKcBgvAAlJagJ8vvJgTZ2F5
+wxZIC8q/eByy139+4xMOJ4vwbsI9B88wJp9G/r3V/Os75cP/ouRheXtY2SBvKj0g8uNN/cWGplw
mcd3X0GWl3XmubB1dQMAWJeLObkFb86Ex+N1xG+28IEFYAFYQHUL8POF58K+NvYOANblYk5uwZsz
4SsTCTxfAnQq6D9ciDX7DPTvvfBZ3zwXduBX8wGwLhdzcgvenAmvayyRdnz3DWRv3vwkmYVtwFzY
kAHWDMA8d5Yz40eOnPB+1EGLsAAsAAsEZIHJyUlqbmvDXNiQAdYczPPcQc6Mv/7GGwGpILqXgf7l
gdiUD0D/3vnjJ5O/o4ZVizEXNmSANQMwz53lzPiJU4e8+6E9askXkGVQqqjoIC5rdZtJxPnutuWx
sl9tbS8999wu4rINfGABWAAWUMkCDEqbk4sNcVmf20wizvceCAZPv0W7e3vxfPHJqaB/7zXr5TgA
/bsTPoNSR89Picta3WYScb73NuwdyqNde34m1fjuKcgyGHV2dicXdOoFwEqUibWG2cHknOWnlNwz
yt0wibNhAVhARQvw8+W57duJA0UvA0+05T0YjFy+Sus2bMTzxUNHg/6916lfvg/9Oxc+67t720Zi
UAKAeg+gXtp08Pxcemp9kzTju2cgyxOBGxpa6IknXgXESg6xKbDlVY0rKtRZYtv50IgzYAFYQAcL
8POlNbndy7998CEgVqJy4mwgwKu6rkw0K7OFg8x+Av2rA7Epn4D+xT2K9d3SVkuvXpwLiJWonDgb
/PKqxvVNpVKM756A7N27d6m6OpEE2RFArCIQm4LZRGIsuQhUI/HEenxgAVgAFpDNAvx8WbVmDb13
+ytArCIQmwrmP/56hv4pOZcZz5fcvQr6Vw9ioX9xvbO+E63lNDIpdxbSy4ymLm2NfR6jxlVLQx/f
XYMsi7CurpUYiDCf1fv5rEHYlLdFqqxsCV2M4kMfjoQFYIEoWICfL0+uX08MRH6VAaJdf0GBt0Va
07Eez5ccHBb691ebQfg+9J9Z+Kzv1rWVxECkC9xF7T54W6SWp0pCHd9dgez9+/eTANuOTKxiWVgr
OOYXEfxCggcWfGABWAAWCNsC/HxZu2EDMrGKZWGt4IBfRPALCTxfxL0K+lcfYs2ZWeh/tvZZ3+0d
9cjEKlJKnA3Q+UUEv5AIa3zPGWQBsWpmX7NleAGz4kEGjoQFYAH/LIAgXp8gHsG8cz+B/qF/56pR
5wxArH4Z6DBhNieQ5dXFeGEnzInVE2Z5vjNPvscHFoAFYIGgLcDPF17YCXNi9Qzmeb4zni+ZvQr6
10/35pc5Udc/65sXdsKcWD1hluc7Bz2+5wSyvMUOVifWD2LNqxnz1jzYZzboEB7XgwVgAd5iB6sT
6xvM82quvDUPni/Wvg7966t9Btqo65+32MHqxPpBbKr0mFcz5q15ghzfHYPsO++MU1VVNxZ20mBe
bLYy45qaF+ngwcOIqmEBWAAWCMwCFycmqPfAQSzspMG82GwL6bw6epaOHDsWmK5UuRD0rzfEpnwi
qvofvzhG3f35WNhJg3mx2ebMvvj6fDp89BeBDbuOQHZ6epqWL08AYjWH2BTgVlR00M2bnwQmRlwI
FoAFomsBfr60rusAxGoOsalgfvOOnTQ5ORldwafdOfQfDYiNqv5Z34n2QkCs5hCbAtyOnp/SJ5O/
C2R8FwZZrnmOx+uoufkCQDYiILtq1RUqKamRYsPjQLwBF4EFYIFQLMDPl5WJBP3hr38DyEYEZL/4
7nuqb0rg+ZL0OOg/WhDLMBsl/bO+6xpL6MKf9S2pjdq2O3b3e+WbGNWsXBTI+C4Mso2Nq6m+fhgQ
GxGITWVleSXj0tIVgda7hxJJ46KwACwQmgXakos78dyxIPZ1xDXkgQbelqemri7yzxfoXx5NBjk+
REX/q9fUE8+dtIMffK+XjXgl4xW1Jb6P70Ige/nyVaqo6ALERgxiUzBbVbWbhoZOhhbk4sKwACyg
rwWuXbtGO/sHALERycSmg8LB02/SqeFhfQVuc2dB6T8Wi1H6n1fQxu06bSuXc8zXEDk/0zHmfxdp
x+m9OTled/1fvfYudfXmAWIjUlKc/jJi97HH6OQbR30d321BFiXF+q5OnG2xJ/N3XGJcWtpAd+7c
8VWMaBwWgAWiZQGUVEYzE2UO9LnEsrmtLZLPlyD1bwVsXkFcLu3kco5XIOu0HSdg6vRYnfWPkmK9
Mqy5ZMy5xLhh1WJfx3dbkO3v359cpXgvsrERzcaat+Th8nJ8YAFYABbwygIHBgfp+LnzjrM5ToNF
HC83MHNZOZfXRu0TpP5zyU6mn2PO6IrCoNU5ov+Wukbq+GzXdALqqWOd9sOvcURX/e8f7KO9b81F
Njai2VjzljxcXu7XJyvIzszMJBf7qQfERhxif1zFuIu4zBwfWAAWgAXcWoCfL4nWNkBsREuK06GA
y8u5zDYqn6D17xZkraDWDJpWkCd6Ti7HiZQHO73nbP3wC2JT7eqmf9Z3fQtWKc4li6njOVxezmXm
fnyygmxNzUpqaBgByAJkDQ3witVFRct9n7jth9DRJiwAC8hlgabmZnrv9lcAWYCsoQFesbqsvDwy
z5eg9e8U6vg3yVb+6wYkvWxbtI+ZsrnZ7sNt+bMT+NVN/ysTK2hkEqW1OkJpLvfEK1Yvjy/yZXzP
CLJTU1NUVtYOiAXEztJARcUWGh+/KFdEjN7AArCAUhbg58vTW7oBsYDYWRrYc+AgTUxMKKXlXDob
hv69AFlzKa4VADop1c1WtiwKyVYlxyIlz5naT7+/IEGW+62L/lnf7c8UoKQ44iXF6cC7Ze/jdHHi
Qi5DZtZzMoIssrFY5MlqMShkZT33QTQIC0TOAkFno5xkRnBsePNpdctKZXLsMPTvFmRFy3+z+U82
gBTJmLo5RuTcoME13Va66B/ZWGSirbK2fmVlLUGWV6ctLq5GNhbZWEsNxOOddP369cgF37hhWAAW
cG8Bfr480dSEbCyysZYa2JGcK6vz8yUs/YsshiQKq+mZUBFITi8ntsuKWs2/FQVhJ3N3ZSktTvVZ
df2zvqsbkI3Npfw2Cud07lng+fhuCbJdXT1UXX0IIAuQtdQAz5vmjD0+sAAsAAs4tcDW7dvp7Acf
AmQBspYa4HnTnLHU9ROW/kXLZjOVD6dANAV+IuW/5nMylRJbrUxsd6zVHNtMoG513+l9t/rvsLKz
quu/Z9smOjSOjGQUoDSXe+R505yx9/LzCMgiG4uSYpH9ZXn+NM+DwAcWgAVgAVELhJWNQrlweOXC
udie50/r+HyB/tXSYS7a9eIcVfWPbCwAXgRuef60l+P7IyB74sQpKi//ObKxyMZm1cCKFQdo27bn
ReNXHAcLwAKwAL0xPEwHht9ENhbZ2KwaeCu5zdvu3l7tPAb6B8iKgK6q+j81fJx+fnQOFnnCIk9Z
NXBgLEbP7+nxbHx/BGSLi0spkRgDyAJks2pg1aortGBBni9LaXumbjQEC8ACUlkgXl5BH389A5AF
yGbVwBfffU/5BQXaPV+gf4CsCMiqqv/S8iU09jmykiJZySgfc+WbGOXlP+bZ+D4LZHkD45KSekAs
IFZIA/H4Orp165ZUgTI6AwvAAnJagJ8vidY2QCwgVkgDXTt2avV8gf4BsSIQmzpGNf2zvutbCpGN
RTZWSAPruvM9G99ngSzKijE/VmR+bOoYlBfLCQzoFSwgowVQVolA3kkgr2p5ZSbfg/6hf531j7Ji
ZKKdZJm9LC+eBbIoKwbIOgFZlBfLiAvoEywgpwVQVolA3kkgr2p5ZSbvC0P/VisMZ9pP1clvk8uK
vplWBk7fyseuH+ZViO2OzeX7bPeWy33n0gc+RzX9o6wYIOsEZL0sL34Isnfv3qXCwhKhklInsINj
9Ybj5csTND09LWfkjF7BArCAFBbg50tpeblQSWmugR/O0w+UW9d1aPF8CUP/2baYSd9Kx6nv5AJ0
dtv1iLSZbZ9bp/eQ6Xi7fth971U/uB1V9M/6LilbKFRS6gR2cKzecJxoL/RkfH8IsrwUMm+pAvDU
Gzy9/n3Lyp6lS5cuSREsoxOwACwgpwX4+cJbSngZ5KEt/cA1/Tfdvf+gFs+XMPSfC8hmy3aaM6eZ
9nkVzWZm2vPVvKesVebYKURmuh9zpjoTHIv+u5/jkCr6Z33zlioAT73B0+vf99m+eZ6M7w9BdmTk
TBJktwNksdCTIw1UVu6j3t4+OaNn9AoWgAWksMCZ0VEaOH4CIIuFnhxp4NT4BPUPDEihYTedCFr/
dhBmVXKcLduZDYpFs6ROMrIi/beDWrv7ydQfK9ukMtiZQNsvmFVF/2fO/Iq2v4Jtd7wGPd3b2zca
o76B3W6GVuPchyDb1dVD1dWHHEGM19k9tKdeNrihYYRqala6FiIagAVgAX0tsHX7djr7wYeOIMav
4BDtqpPJfe/2V9TU3Ky8YwStfxEQtIOzbOAp+l2m+bjmTKk502uXhU0/VjQDnOu9ikCtn+OJKvrv
2baJDo0jG6k7eHp9fyOTMVqZWOF6fH8IsljoST2IlAH8seCTax9EA7CA9hYIY6EbPwNMtB0MDKu2
4E0mRw5a/0GDbDqYWvmHXUY2/RwnWWOrEmK7jGw2yE7PvIpmnb0eF1TRPxZ6AsTnArleLfhkgOz9
+/dp/vyFyMairDgnDRQXV9OdO3e0D8Zxg7AALODcAvx8yS8oQDYWZcU5aeCJpialny9h6D9okBUB
OD9B1g6cVc3Icr9l1z/re2H+PMyPxf6xOWmguqHA9fhugKwOKxbzfaQylFahlpPspbktJ+fZHetX
u3bX9ft7rFzsPLjHGbBAVCwQxoqtmQJbkcyRSFCeKXvk5Fy7OX52bYmcn+kYp1Bh1xc/v1dl5dZM
/hyG/kWzkaIlwqLtpQOjSNYzm3bsMqF+lxZnuh8R3/PKJ2TXv8orFvPvmMokWpW7i2QZzeeJHO/0
GHMfnZ6rwvFerFxsgOzMzAyVlNTnlI3zG5JE208H2fTzRCEy9TASva6T40T74KRNGY6Nx9fRrVu3
ohKX4z5hAVggzQIczGT68PMl0dqWUzbOq2DQ74A0l8A2l3MygUEmO4lcQ+QYL38Hp2117dgp/fNF
Rv1nglQ7eE0F5lYva6xKeFO+lem89DLdbLAr8oIoUx/sXl5l8x07mzj1O6caz3a8DPq303d9S2FO
2biwQSsdZNP7YweR6d/bHZ/L/frRZi798Oucdd35rsd3A2R5H1DOqskARbn2QRRk02HS6r9FgNMc
tJn7nDrXCojN31mdk+u9h31ePL6Rbty4geAeFoAFImqB0eSqxJWVlZbjAD9fOKvgZXCXS1u5ZCet
MkJWAbtdZij9HKtgPFuALnJNqz7Y3bPTfuRid7fn9PS+IP3zRUb9y/6Cwq0ugjrfagwI6tp8HRn0
b6dvzqr5BTp+tisKspmA1Slkmsdb832l2kl9n+k7q3/30z5BtL1xx0LX47sBspxN46xa2EDk5vpe
gGwm0LTL7qZfO1NfdAXZ0tJuOn/+fERDeNw2LAALcKCTeginAy0/XzirEGTwlyk7Y/fv2YJWJ99Z
ZaHSM1GiWaBMx2U7P9P17bJjYQftVr/Pi4dflf75Iqv+AbPuFiWTwR9k0L+dvjmrFgT0eH0Nr0DW
CkDtsrvp187UFzPk6giy3S/PcT2+GyDL2TTOqrkBybDPtYJJkaxppmxqtvvJltUV/U4UmsO2q8j1
ly3bSjzQ4QMLwALRtIA50EkHWn6+cFZBdZDNVvZol/m0A2g3bdtlg+2uLQrUYf1+/cdfk/75ooL+
w/r9cF13MC2D/u30zVk1ryEziPasYFIka5o+r9b835n6nSmry8eLfpcJaoOwlV/X2DoYcz2+GyB7
/fr1JMh2agWyIiBqlznlNqxgWBRWU+ebF6FK///pbYmAo2zHMMhyFsY8AOD/Pxic8AcbRF0Dixcv
ps27ntcCZNN/y/QMp/l783epf7ebp5fpfCfz/0Tm82XL8ma6x7CAhAN5lZ8vsug/rN8P13UPsjLr
n/W9rme+FiCbDdasIDITgFrBsCispoOtVaY2vS2/IDOIdj0DWR0zsrmAbHouJVMbANnZe+4iIxvN
LBzuGhZIWcDqjT0/bF966SW6cOGCFhnZ9MxntkxmpuA9G0BmAlCRbK/IMSLtZ8vuhgUkMmSk7Dxd
Bf2H9fvhuu5BNuyKNzt965KR9QpkrdoByFrvtesZyEZhsSe7ea5OFl/yAmTTs7WyZVmd9AeLPdmF
OfgeFtDbAumBDgNsaqVLmRd7ygandnNaRUBWFH7T2xIB3lyur+IcWRkWu7HzXhX0D6B0B5Rh2U8G
/dvpW9fFnpzMc7UqEc42p9Uq02pVopwNgIPImPp9Dc8WewLIzs4wipT72s2/zVZObPWdE3CU7ViA
rF2Yg+9hAb0tkAp0zACbumOZQFakbDbbMeYSYRGQTMFwptLiTABrBcBOoNuqrDnTfaX3zXxcWMG7
+boyBPJ23quC/mX4LdEH5zAtg/7t9B1VkE3Ba2rMtIM+q5JjJ3Nk7WDZ7voyfu8ZyPKb88LCEqXn
yMoGdyL9EQFmkXbCPoa3buJgFR9YABaIpgXY/zPtNcj/XlpeHvocWQTRzoNoGWzGWzfJ/nyB/nPT
loyl7DJo3twHGfRvp++SMjUXe5IR7Oz6pNP8WL5Xfgnidnw3FnsCyM7OyAYBhrpALNuqpKSeZmZm
ohnB465hAVggqwUAsrkF+bIF1GH1J9HapvTzBfrPrH+ArP3YILv+Wd8AWev5n3ZQ6vR73SCW77++
pdD1+G6ALH8WLMijlpZLyMomwSwIkNXpGvPnL6T79+8jnIcFYAFYwNIC+QUFNPX3fyAr+z/2gWtY
wCjrdVk7qj9foP/Zuk8vcwfQZh4XVNB/XsF8ujQdDMw5hT8cL/fvsjB/nuvx/SHItraupbq6k4A4
gKwjDSQSY1RcXIrwHRaABWCBjBZYv3Ejjf/+U4AsQNaRBj7+eobi5RXKexb0bw1qANjsL7ZU0f/a
DS108n25gQlAK9/vM/Z5LDntaInr8f0hyB4+fDS5l2yvI4jRKauIe8ktE11dfYi6unpcCxENwAKw
gL4WODY0RIfOjDqCGFkzhOhXcFnlsx98SFu3b1feMaB/gGwu44Yq+j86dIh6T8gHSoBXuX+TQ+Mx
6tm2yfX4/hBkddhLFjCaG4y6sVtZ2XYaGTnjWohoABaABfS1AD9fePXNXII5nBMcOMpm64HjJ+jM
6KjyjgH9R1fDbnxKFf2zvlXdSxawGx7sbn9lDp058yvX4/tDkL1z506yRLQaGVmUFjvSQFlZO01N
TbkWIhqABWABfS3Az5cnmpoAsigtdqSBp7d0a/F8gf4BsrkArSr6Z31XNxQQoDA8KFTR9u3PJNfO
8IAfHoIsh1BY8Cn4jKabbKgM52KhJ33hA3cGC3hpASx4g2DeaTCvwkI3oj4C/UP/OusfCz4BYp3C
tBcLPfH4Owtke3v7qLJyn6OMnAwwhT6EA+APFgdbK/ocx3GwACwQYQv0DwzQqfEJRxk5p4EfjtcH
FnhxMF4kSZcP9K+PNoMYZ1TTf9/Abto3CphzCnNRPZ4XB+NFwrz4zALZL7/8kkpLVwNkUV4spIF4
vJOuX7/uhQ7RBiwAC2huAX6+rN3UCZBFebGQBnb0D2j1fIH+AbJOAFg1/bO+V28oRHlxcm/UqMKp
k/vu3LPAs/F9Fsj+8MMPVFCwGPvJAmSFQDYvbxHdu3dP8/AbtwcLwAJeWICfL0VLl2I/WYCsEMgu
KS7W6vkC/QNknYCsavpnfS8uzsN+sgBZIZBfVLTAs/F9FshysILy4nDKdFUrj0ZZsRehPdqABaJl
AZRXIpgXCeZVK6sU9WLoH/rXWf8oL0Y2ViQr62VZ8SNzZPkfUF4MkBWBapQVi4YuOA4WgAVSFkB5
JQJ5kUBetbJKUQ+H/qF/nfWP8mKArAjIellWbAmy/I81NSupoWFEqLxUBHpwjF5w3NJyyShB51IS
fGABWAAWcGKBpuZmeu/2V0LlpSJBH47RCw6m/v4PowRd1+eL7vqPxWKP+Db/W+rP7K9Wx/L3qX83
n2d1vo6+r7r+VyZW0MgkgE4E6KJ4zKXpmFGC7uX4/khpMQckt27donh8HUAWc2UtNVBZ+QL98pdH
nMSuOBYWgAVgAcMC/Hzp2rETIIu5spYaOHzmLB0dGtLWW3TXfzqcuvnvTKCrI8Cm7kl1/bO+13Xn
C82TjCLIRf2eX3h9Dh05dtDT8d0SZI1FCYqWU3PzBcAsYHaWBlatukKLFi3zbJK2p2pGY7AALCC9
Bfj5UlZeTn/4698As4DZWRr44rvvqTSpDZ0XEdRd/2b4tMu4mrOvKZATOV9XkNVB/6zv5fFFdOHP
yMpGHVrT7//KNzFaVpbv+fhuCbIcCY2PX6SKii0AWYDsLA0gGys9J6CDsID0FpiYmKA9Bw4CZAGy
szSgejZK1PF01n8uIGouJRYpPdYVZHXR/8WJC7Rl7+PIymIF41ka8CMby2NuRpBFVlavea1ezVMu
Lq6mO3fuiD6vcRwsAAvAAo9YQPeslK6Btt/39URTUySeLzrrPxeQtcrMpv4t0/xav7UYRvu66B9Z
WWSjrbLR1Q0FvozvGUGWI4/Ll68ms7JdyMoiK2tooKpqL/X370dYDgvAArCAawtcu3aNdvYPICuL
rKyhgePnztOBwUHXulKlAV31nwvIIiOrn/6vXnuXunrzkJVFVtbQwN635tL+wT5fhuesIMtXbGxc
TfX1w4DZiMMsz5detqyS7t+/74sQ0SgsAAtEzwJt7e307tRngNmIwyzPl66uq4vc80VH/YuAbLZj
RM4PI1vq5zV11f/qNfU0fAPZyajPleX50pU1Rb6N77Ygy2WkXE7qVWkq2lGzZLmiooNu3vwkepE2
7hgWgAV8swA/X7iczs8gEW3Lvz3P5uQq1pOTk77pTNaGddS/m1WK00uMo7Jqsa76Z31zOWnUQS7q
99/R81P6ZPJ3vg3DtiDLV+atVniRH0ComhDq9nerrj5EXV09vokQDcMCsEB0LcBbrfAiJwBO+YHT
j9/o7Acf0tbt2yPrALrp3+t9ZP3QnExt6q5/3mqFF/mJOsxF9f4PjceoZ9smX8d3IZDFwk/RBFgG
YGy346v/oXFYIPIW0HnhG5kCZhn7osN2I24dGPqP5gsc9sco6B8LP0W3tNqv7XbSx1whkOWTZmZm
KB5vNsDGbYYP56sDxuXlT9J//Md/un1W43xYABaABTJagJ8vbR0dRmAnI3ChT/7AxtNbuulPf/pT
5D0D+vdHX7L7bVT0z/pufnIJMdhENTMZxft+8plF9J9/+tT38V0YZLkn77wznly5thsgG5GFn2pq
XqSDBw/7LkJcABaABWCBi8m9ZXuxt2xkQP7V0bN05NgxCP9/LQD9Rwtmo6b/8Ytj1N2fD5CNyCrG
L74+nw4f/UUg47sjkOUePffcLqqtHQTMag6zdXUnk7/x2kBEiIvAArAALMAW2N3bSyPJbd9kz6Sg
f+6gY/z3n9L6jRsh+jQLQP/udKWKX0ZV/7v2/IwGz88FzGoOsyffj9HaDS2Bje+OQZbr3auqGpLb
8rwNmNUUZnmrnXi8ju7duxeYEHEhWAAWgAX4+dLY3Ewf/WUaMKvpljy81cjKRALPFwt3h/71B9ko
65/13dBUTm//ESXGupYa81Y7dY0lgY7vjkGWx967d+9SaWkttbRcAsxqBrM8B5rnQvOcBnxgAVgA
FgjaAvx8aUiCztTf/wGY1QxmeQ40z4XG8yWzV0H/+sIs9P+AH2obi+jSNGBWN5jlOdA8Fzro8T0n
kOUhmPeHqqxsAcxqBLIMsVVVa+m//uuLoGNXXA8WgAVggYcW4OfLmo71gFmNQJaD+E3dPXT79m0o
3cYC0L9+MAv9/yh61nfLUyWAWY1KjBli125eSl/c/izw8T1nkAXMqrPysMgq0YDYwH0PF4QFYIEs
FkAwr08wjyDeuatD/9C/c9WocwZgVp+MdJgQy4p3BbLcwPT0NFVUtGJbHsUzsxUVHXTz5ifqjILo
KSwAC2hvAX6+rOvsxLY8imdmN+/YSZOTk9rr1esbhP71gFno39ozWN+tG7Etj+olxh09P6VPJn/n
9fAn3J5rkOUrcSkqwyzmzKqXpX2Qid1E16//Rlg0OBAWgAVggaAswKWoDLOYM6teUM+Z2OdeeIF+
+9FHQclFu+tA/+rpPrV6MvRv745cisowizmz6mVoORO7adci+s1vr9r/0D4e4QnIpjKz8XgjJRJj
WABKkewsv3jgFxCAWB89DE3DArCAawvwm/t/amujj7+ewQJQimRn+cUDv4AAxLqWv1H5Bv2rBbTQ
v7juWd+Nq5bS2OfqwZzq2dRc+88vHvgFRNgQyyrzDGS5sW+//TYJRvVUXz8MmJUcZvmFA7944AEE
H1gAFoAFZLcAP19WJprp3anPALOSwyy/cGDwwvPFO6+C/tUBWejfue5Z3/VNpTR8AzCbK1wGdR6/
cOAXD7KM756CLEv3/v37yRLjp6i2dhAwKynM8osGfuHAAwc+sAAsAAuoYgF+vqzbsJFGLl8FzEoK
s/yigV844PnivVdB//LDLPSfu+5Z30+tb6LB83MpKCjDdZy9OOAXDfzCQabx3XOQZQnzpsfPPbeL
VqzYhkWgJIPZmpqXjRcNPGDgAwvAArCAahbg58vu3l7qe/UIFoGSDGbfGJ8wXjTg+eKfV0H/8sIs
9O9e96zvXXt+Rtt+8TjxHEyApjw2ePnsXONFg2zjuy8gm5Ly2bO/TpavNlNj49vIzoYMtM3NF6i0
dDXt3v2vxosGfGABWAAWUNkC58bGqK2jgz76yzSysyED7R/++jdau6mT9g4M4PkSkFNB//IALfTv
veh/fW6Ump9cQm//UR6QiypUX/hzjFZvKKR/7d8l5fjuK8iytGdmZpKr4jZQXd0AYDYkmK2tPUbL
llXSl19+6f1ogxZhAVgAFgjJAvx8aWxuptfG3gHMhgSzY/9+k6rr6vB8CcEHoP/wYRb690/4rO+G
pnIa+NV8ZGb/OxygP/ZujCpriqQe330H2VSpcV/fy0ZGkDODrSEBXdSu+2BV4n+mjo5O6UoB/Bv6
0DIsAAtEyQJcYXJgcNDICHJmJLX1Bf7X3yCfV2V9rvcF6nr2WTxfQnQ46N9fnWcaR6D/YETP+n75
4L8YGUHODEY1Kxr0ffOqxP+8s4A6N8s/FTEQkE3JnTOCnBmsqtqNubM+w3xV1V5aurSSfvOb3wYz
2uAqsAAsAAuEaAF+vnBm8ODpNzF31ufs7PFz56mqto4+wv6wISp+9qWh/+CAFvoPXvasb84M7j72
GObO+pyd3fvW3KStFye3Tvsg+B86hysGCrLcP54kPDR0kkpKapIrGx9DdtZjoOUViUtK6qm/fz/d
u3cvB0ngFFgAFoAF1LQAP19ODQ8nV1VMEJf8ISvrbXDPK7ImWtuMDDieL/L5CPTvrd7Txw/oP1zN
s75PvnGUalYuIi55DTpLqfv1jBWJWwpp/2CfUuN74CCbcgNeuplLXrncGItBve8a6LlkOx5fl7Tl
amNeMj6wACwAC0TVAvx84ZJXLjfGYlDug3su2e7asZPa2tvxfFHAqaB/95o3Qyz0L5foWd9c8srl
xlgMyj3Qc8n2uu58Wr2mXsnxPTSQNZcbx+PVSQjbSInEmGugi9o8WAbYiootVFS0nG7duiXXaIPe
wAKwACwQogW4HK0mWW7ck5zL+fHXM8jQOiw55gB+z4GDVFZejudLiDrO9dLQvzughf5zVV4w5xnl
9LXLaeOOhTT2uXug0z3jmn5/DLBb9j5Oy+OLlB7fQwfZlNxv3LhBxcWlRlaxoWEEQGtTcszQz/DP
ADs+flHKJbGDGcpwFVgAFoAFsluAny/x8gojq/je7a8AtDZAy9DP8M8AOzExgeeL4g4G/TsDWuhf
LcGzvkvLlxhZxZFJAK0dkDP0M/wzwF6cuKD8+C4NyKbchrOKNTUrjZLjurqTANo0oGXIZ9hn6Gfn
xZ6wag246C0sAAuEZwF+vjQlt+vhkuPx338KoE0DWoZ8hn2GfjxfwtOpX1eG/rMDLfTvl/KCaZf1
vTKxwig5Pvk+gDYdaBnyGfYZ+nUa36UDWXPJcWvrWlq8OE7l5T+P9LY9vI1OeXlfEl6rDchHCXEw
gyKuAgvAAnpagEvS1m/cSCtqa+nA8JuR3raHtxEZOjdGTzQ1GZCP54uemjffFfT/I9BC//rpnfW9
dkMLxavz6edH50R62x7eRqfvzRhVNxQYkK/j+C4tyKZciyd1nzhxigoLlxhZ2hUrDkRm6x5e1Zmz
rwUFi+mllw7QnTt39BtxcEewACwAC4RkAX6+vJFc5bho6VIjS/vW5auR2bqHV3Xm7Cvf++Arr+D5
EpIGw7ws9A/9h6k/v6/N+j41fJyWFCcXMkpmaQ+MxSKzdQ+v6szZ18XFeclV5ge0Ht+lB9n0t4jb
tj1P+fmLjfmhDLWcrdRlgadVq65QdfWh5L11JsG9xFjVmd+eoHzY7+EO7cMCsEDULcBv8Xf39lJR
8VJjfihDLWdrdNnC54vvvqezH3xIO/oHkqVl5caqzni+RF31P94/9A8t6GwB1vfze3pocdHjxvxQ
hlrOVtrNJ1Xl+yvfxOjQeIw69yygkrKFxqrOURnflQLZlJPxXlJc381Qu2BBnrFvamnpLiUXieKt
h+LxXiPbPHfuT6irq4euX79Od+/e1XlMwb3BArAALCClBVLPF4ba/IICY9/U/cOnlVwkirceOnRm
1Mg2z3vsMdq6fTueL1KqTp5OQf/y/BboifcWSOmboTavYL6xb+quIzElF4nirYd6T8SMbPNP5s2h
nm2bIjm+Kwmy6dLmfVNPnRo25o/m5S0yoHDZsq3Epbm8PY0sGVvOHvMCVty3srJ2I+vKWw8dPnyU
+G0RPrAALAALwAJyWYCfL8OnTxvzR5cUFxtQ2H/8NeLSXN6eQ5aMLWePeQEr7tvTW7qNrCtvPXRs
aAjPF7kkpVRvoH+lfi501qEFDH0Pv27MH11UtMCAwq2DMeLSXN6eRpaMLGePeQEr7lv7MwVG1pW3
Hjo6dCjy47sWIGvW7b1794wfdXR01CjN5bm1ZrjlRZMYJuvrh30DXF5ZmK9RWblvFrRy9pgXsOK+
TU1NIevqcMDB4bAALAALhGkB8/OFS3N5fqkZbnnRJIbJd6c+8w1weWVVvsap8YlZ0MrZY17ACs+X
MBWi97Whf71/36jfnVnfXJrLc2vNcMuLJjFMDt/wD3B5ZWG+xr7R2dDK2WNewArj+6Mq1Q5krRzR
LE5eNIlhsrFxNcViMeNv+fLEw7/S0m4DPkX/zOdyaTC3x5lhvkZvbx9EF/WREfcPC8ACWlvA/Hzh
RZMYJtva2x8+X1rXdVDq78XDrxrwKfpnPnfevMeMNjkzzNfoHxjA80VrZalxc9C/Gr8TepmbBcz6
5kWTGCZXr6l/OL4n2gsp9df98hwjYyr6Zz6XS4N5fOfMMF+jb2A3xnfBnywSIGtni+npaUr9nT9/
3hCP6J/5XCzKZGdpfA8LwAKwQLQsgOdLtH5v3O1sC0D/UITOFoC+w/91AbLh/wboASwAC8ACsAAs
AAvAArAALAALwAKwgAMLAGQdGAuHwgKwACwAC8ACsAAsAAvAArAALAALhG8BgGz4vwF6AAvAArAA
LAALwAKwACwAC8ACsAAs4MACAFkHxsKhsAAsAAvAArAALAALwAKwACwAC8AC4VsAIBv+b4AewAKw
ACwAC8ACsAAsAAvAArAALAALOLAAQNaBsXAoLAALwAKwACwAC8ACsAAsAAvAArBA+BYAyKb9BjMz
Mw+34jEvq53p/4f/E6IHsIA8FoD/yPNboCfqWQD+o95vhh6LWwD6FrcVjlTPAtB3OL9ZZECW93hl
GL1165axR+ypU8PU2rrW+ONNiFN/JSX1tHx5QvjPfG5j42qjvcOHjxrXuHHjhnHN+/fvh/Pr4qqw
gEcWSPef4dOnaf3Gjcaf2QcSrW3Uuq5D+M98blt7u9HesaEh+I9HvxuakcMC8B85fgf0wh8LQN/+
2BWtymGBR/Q9/Dqt3dBi/JljmPqWQkq0i/+Zz129pt5o7+jQIcQ/Dn92LUE2Jbrz58/Ttm3PUzxe
TXPn/sSA03h8HS1btpVKS3dRXd1J46+19X1P/urrh4324vFe4xrx+EbjmvPnL6Ti4lLq6uoxBAq4
dahSHB6oBcz+s7u3l2rq6mjevMcMOO3asZP6j79G+4dP0/jvPzX+/u///D9P/t6d+sxo79CZUeMa
Pb0vGNfMLyigeHkFbd2+Hf4TqBJwsVwsAP/JxWo4RxULQN+q/FLoZy4WMOv7+T09VF27nH4yb44B
qOu682nrYIx2HYnRyfcf/L3/3978Dd940F7viZhxjY07FhrXXJg/j0rLl1DPtk2IfzL8oNqALKf0
OctqhtbS0m5aseIANTa+7QmougHeRGKMqqsPGYBrhtuXXjpAU1NTxM6DDywQlgXYfzjLaobWFw+/
Sm9dvkof/WXaE1B1A7wffz1DZz/40ABcM9wOvvIK/Ccs0eC6Dy0A/4EYdLYA9K3zr4t7M/SdzLKa
obX75Tl0YCxGb//RG1B1A7xjn8fo0PgDwDXD7YHBAcQ/SfkqC7Jcrsulu5xxXbAgj7gkmLOsMkCr
KPAy3JaX91FZWbtxD5yxvX79Ot29excjCyzgqwVS/sMZV854ckkwZ1llgFZR4GW4HTo3Rk9v6Tbu
gTO28B9fZYPG/9cC8B9IQWcLQN86/7q4t5S+OeOaVzCfuCSYs6wyQKso8DLc9r0Zo/ZnCigv/zEj
YxvV+EcpkOWsJcNrR0enUa7LpbuccW1puRR6xlUUXjMdt2rVFSNjG493UmFhCdXUrDREee/ePYw6
sIAnFkj5T9ezzxrgx6W7nHGd+vs/Qs+4isJrpuO++O57I2O7o38gWYZTTk3NzfAfT1SDRlIWgP9A
CzpbAPrW+dfFvaX03bn5KaNcl0t3OeN6aTr8jKsovGY67so3DzK2nXsWUEnZQlqZWBGp+EcJkP3y
yy+pt7fPyFoyvNbWHlMeXO3At6FhxIDavLxFRtaZF6nCBxbIxQLsP/0DAw/hdezfbyoPrnbg+97t
rwyoXVJcTJx1hv/kohycwxaA/8B/dPYE6Bv61l3ffQO7jawlw+uxd9UHVzvwHZl8ALWLihYQZ511
j3+kBVlO/b/55kgyO7kkWTK8mior9xFnLe0AUMfvOevMi1QxyP/yl0eQpdV51PXo3th//s+ZM1S0
dCmt3dRJp8YniLOWdgCo4/ecdeZFqjgLfTS5IjKqHDwSmcbNwH9+XMAN/qOf0KFv6Fs/Vf94R6zv
kTPDyRfZ+bR6QyHtG40RZy3tAFDH7znrzItUcQn1kWMHtYx/pANZDjIZ1vLzFyfhdQc1N1+IJLxa
ATmXUFdWvmBkaTlDjbm0Og/Fud0b+w/DWlHxUtr32gn6w1//Fkl4tQJyLqE+fOaskaXlDDX8JzeN
6XwW/CfzCuTwH/WVD31D3+qrOPMdsL4Z1hYXPU47XnmMLvw5mvBqBeRcQv3C63OMLC1nqHWKf6QB
WTYqwxlDGsNaVLOvohllzlDzXFpeIOrOnTs6j024NwELsP8wnDGkMaxFNfsqmlHmDDXPpeUFouA/
AgLT/BD4j7MttOA/ajkE9A19q6VYZ71lfTOcMaQxrEU1+yqaUeYMNc+l5QWidIh/QgdZfoPS37/f
gDKGM1GQw3EP9r7lBaKKi6sNoNXpDYuzYSy6R7P/HBgcNKCMg0tRkMNxDwIbXiDqiaYmA2jhP9Hz
I/iPswA/fdyA/8jtM9A39C23Qt31jvW9f7DPgDKGM1GQw3EPbMULRFU3JBf+TAKtyvFPaCDLK4id
PftrWrq0kqqq9gJgk1DqBs4ZaIuKKmho6CTx/AB89LYA+8+5sTGqqq2j4+fOA2CTUOoGzjkgr6qt
pVPDw/AfvV3HuDv4jzt/sQJa+I88jgN9Q9/yqNH7nrC+f31ulCprFtPet+YCYJNQ6gbOGWgrqgvp
5BtHlYx/QgFZXiWvqqohuXXONi22znEDoF6ey+XYVVW7admySu1XKfN+aFSnRfafxuT2Mn2vHtFi
6xw3AOrluVyOffD0m1RdVwf/UccdHPcU/uNtkJ/yQfiPYyn6cgL0DX37IixJGmV9NzSV07ZfPK7F
1jluANTLc7kce/exx5IvB4qUi38CBVkuA+A9YHkV4sbGt11lIL0EQN3a4gWyeJXjxsbV9O2330oy
/KAbbi3A/sN7wPIqxB/9ZdpVBtJLANStLV4gi1c5bmtvh/+4Fa1E58N//Anw0/0f/hOO6KFv6Dsc
5QVzVdY37wHLqxC//Ud3GUgvAVC3tniBLF7lePWaemXin8BAlt+icBlxFPaAlQWM6+uHqaSkhi5d
uhzMSIOr+GYBo4ohWUYchT1gZQHjd6c+o/qmBF29ds233xUNB2MB+E8wQb7Zd+E/wWibrwJ9Q9/B
qS34K7G+uYw4CnvAygLGwzdiVLNyEV2+OhH8D+7wir6DLNey9/W9bGRhefsYWSAvKv14UG682ciE
Y/9Mh94hweHsP7yYE2dhefsLWSAvKv3gcsld/fuMTDj8RwKHcNgF+E/wAb55bID/OBSsw8Ohb+jb
oWSUOpz1/fLBfzGysLx9jCyQF5V+cLnx5t5CIxMuc/zjK8jyss48F7aubgAA63IxJ7fgzZnweLzO
eHOLjxoWYP/hubCvjb0DgHW5mJNb8OZM+MpEAv6jhusYvYT/hBvkm30O/uO940Df0Lf3qpKnRdY3
z4Ud+NV8AKzLxZzcgjdnwusaS6SNf3wD2Zs3P0lmYRswFzZkgDUDMM+d5cz4kSMn5Bmt0BNLC0xO
TlJzWxvmwoYMsOZgnOf+cWb89TfegGoltwD8R54gP+VD8B/vnAb6hr69U5N8LX0y+TtqWLUYc2FD
BlgzAPPcWc6Mnzh1SDrB+AKyDEoVFR3EZa1uM4k43922PFb2q63tpeee22VsQYGPfBZgUNqcXGyI
y/LcZhJxvvcBz+Dpt2h3by/8Rz7XMXoE//Fe816OI/Afd44DfUPf7hQk99kMSh09PyUua3WbScT5
3tuwdyiPdu35mVTxj6cgy2DU2dmdXNCpFwArUSbWGmYHk3OWn1Jyzyi5h+Hce8f+89z27cSBnpeB
I9ryPvAZuXyV1m3YCP/JXe6enwn/8V7nfo0d8B/n8oe+oW/nqlHnDNZ397aNxKAEAPUeQL206eD5
ufTU+iZp4h/PQJYnAjc0tNATT7wKiJUcYlNgy6saV1Sos8S2OkOy856y/7Qmt3v5tw8+BMRKVE6c
LZDnVVlXJpqVWaLeuSrVOQP+o06Qn/Ip+I+4f0Hf0Le4WtQ7kvXd0lZLr16cC4iVqJw4G/zyqsb1
TaVSxD+egOzdu3epujqRBNkRQKwiEJuC2URiLLkIVKOxMAo+4ViA/WfVmjX03u2vALGKQGwqGP/4
6xn6p+RcZvhPOL7DV4X/qBfkw3/E/QX6hr7F1aLekazvRGs5jUzKnYX0MqOpS1tjn8eocdXS0OMf
1yDLIqyrayUGIsxn9X4+axA25W2RKitbQhejekOw+x6z/zy5fj0xEPlVxod2/Q2EeFukNR3r4T/u
3cFxC/Aff7UdxNgB/8kse+gb+nY8KCp0Auu7dW0lMRDpAndRuw/eFqnlqZJQ4x9XIHv//v0kwLYj
E6tYFtYKjvlFBL+Q4IEFn2AswP6zdsMGZGIVy8JaBff8IoJfSMB/gvEdvgr8R/0g35yZhf/M9h3o
G/oObjQN/kqs7/aOemRiFSklzgbo/CKCX0iEFf/kDLKAWDWzr9kyvIDZ4AZzBCn6BCkIxoPzm9SV
4D/wn+BVF9wVoW/oOzi1BX8lQKx+GegwYTYnkOXVxXhhJ8yJ1RNmeb4zT77Hxx8LsP/wwk6YE6tn
sMLzneE//vgOtwr/0c9vzC+Dou4/0Df07d/oGX7LrG9e2AlzYvWEWZ7vHHT8kxPI8hY7WJ1YP4g1
r2bMW/Ngn1l/Bn3eYgerE+sbrPBqrLw1D/wH/hPEHFPdrhF1/8HzQd9nA/tq1PXNW+xgdWL9IDZV
esyrGfPWPEHGP45B9p13xqmqqhsLO2kwLzZbmXFNzYt08OBhfyLRCLd6cWKCeg8cxMJOGsyLzQYQ
r46epSPHjkVY6f7cOvxH7yA/5VNR9R/oG/r2Z+SUo9Xxi2PU3Z+PhZ00mBebbc7si6/Pp8NHfxGY
6ByB7PT0NC1fngDEag6xKcCtqOigmzc/CUyMul+I/ad1XQcgVnOITQXjm3fspMnJSd1lHdj9wX+i
EeRH1X+gb+g7sME0hAuxvhPthYBYzSE2BbgdPT+lTyZ/F4jShEGWa57j8Tpqbr4AkI0IyK5adYVK
Smqk2PA4EG/w8SLsPysTCfrDX/8GkI0IyH7x3ffJDcMT8B8P/Ar+E60gn2E2Sv4DfUPfHgyT0jbB
+q5rLKELf9a3pDZq2+7Y3e+Vb2JUs3JRIPGPMMg2Nq6m+vphQGxEIDaVleWVjEtLVwRa7y7taOyi
Y23JxZ14boxu89lwP9kDMN6Wp6auDv7jwnf4VPhP9AJ9Hlui4j/QN/TtcoiU+vTVa+qJ507awQ++
18tGvJLxitoS3+MfIZC9fPkqVVR0AWIjBrEpmK2q2k1DQyelHihl7ty1a9doZ/8AIDYimdh0uD94
+k06NTwss0Sl7hv8J5pBfsqPdPcf6Bv61vn5cPXau9TVmweIjUhJcfrLiN3HHqOTbxz1NcawBVmU
FOu7OnG2xZ7M33GJcWlpA925c8dXMerYOErGoh2kpEokm9va4D85ODj8B/7DJca6+g/0DX3rrm+U
FOuVZXWaNecS44ZVi32Nf2xBtr9/f3KV4r3IxkY0G2vekofLy/FxZoEDg4N0/Nx5ZGMjmo1NZZW4
rJzLB/FxZgH4DwL91JYlOvoP9A1966zv/YN9tPetucjGRjQba96Sh8vL/fpkBdmZmZnkYj/1gNiI
Q+yPqxh3EZeZ4yNmAfafRGsbIDbiEJuCWS4v5zJCfMQsAP9BkG8u09fNf6Bv6Ft3fde3YJVipxlM
XY/n8nIuM/fjkxVka2pWUkPDCEAWIGtogFesLipa7vvEbT+EHkabTc3N9N7trwCyAFlDA7xidVl5
OfxH0BnhPwj0zYG+bv4DfUPfOut7ZWIFjUxGu6xWVyjN5b54xerl8UW+xD8ZQXZqaorKytoBsYDY
WRqoqNhC4+MXBUPR6B7G/vP0lm5ALCB2lgb2HDhIExMT0XUMwTuH/yDIt1oRXRf/gb6hb9313f5M
AUqKI15SnA68W/Y+ThcnLghGAeKHZQRZZGOxyJPVYlDIyoo5F962I1CxClR0yyqJeYPzo+A/8B+d
/Qf6hr511jeyschEW2Vt/crKWoIsr05bXFyNbCyysZYaiMc76fr1686j04icwf7zRFMTsrHIxlpq
YEdyriz8J/NgEJb/xGIxSv/zap9kbtdpW7mcY76GyPmZjjH/u0g7Tu/NzfGq+09Y+nZjc5wbHHjr
oO/qBmRjcym/jcI5nXsWeB7/WIJsV1cPVVcfAsgCZC01wPOmOWOPj7UFtm7fTmc/+NBx4IpgIbhg
IUxb87xpzsjgI5f/WAGbVxCXSzu5nOMVyDptJ0h/Ut1/8HyIxjifq0+oru+ebZvo0DgyklGA0lzu
kedNc8bey88jIItsLEqKRfaX5fnTPM8Hn9kWwNt2BCkiAQzPn4b/PDp6hOk/uWQn088xZ3RFYdDq
HNF/S10jdXy2azoB9dSxTvshon0vjlHVf8LUtxd2RxvBPN9U1jeysYB4O8Dl+dNexj+PgOyJE6eo
vPznyMYiG5tVAytWHKBt254Hx6ZZ4I3hYTow/CaysSgrzqqBt5LbWO3u7YX/SOQ/bkHWCmrNoGkF
AaLn5HKcSHmw03vO1o8gIUdV/8HzIRgQDFKLflxLVX2fGj5OPz86B4s8YZGnrBo4MBaj5/f0eBb/
PAKyxcWllEiMAWQBslk1sGrVFVqwIM+XpbQ9U3cIDcXLK+jjr2cAsgDZrBr44rvvKb+gAP6T5qNh
+o9TqOMANlv5rxuQ9LJt0T5myuZmuw+35c+5QoCq/hOmvnO1Nc4LHr5V1Xdp+RIa+xwZSbuMZNS/
v/JNjPLyH/Ms/pkFsrxBd0lJPSAWECukgXh8Hd26dSsEXJTzktjgPvgHvspBVteOnfAfkyuH7T9e
gKy5FNcKAJ2U6mYrWxaFZKuSY5GS50ztp99fWCDL96Ca/4Stb5XHyij2XUV917cUIhuLbKyQBtZ1
53sW/8wCWZQVY36syPzY1DEoL54N1CgbA8g6CbhULR/z6zVS2P7jFmRFy3+zaSQbQIpkTN0cI3Ju
mOCabjfV/CdsfTsZm3Bs+M8y1fSNsmJkop1kmr0sL54FsigrBsg6AVmUF88O6VE2Fv7DX6UATNXy
Mb9ANmz/EVkMSRRW0zOhIpCcXk5slxW1mn8rCsJO5u7KWFrM/VfNf0T17fRlgdMsefrvmamKwG4s
taousDtHpe9FfgeRyohc71k1faOsGCDrBGS9LC9+CLJ3796lwsISoZJSJ7CDY/WG4+XLEzQ9Pe1X
bKtMu+w/peXlmBuLubGONNC6rgP+k/RyGfxHFAiyBf5mgBUNcjMBgRUMp9rMVHacrWw4E6hb3bcV
7JjhN71vuQbrbs9TxX9E9Z3p9xXN4tu9oMj2skTk3EzHiECf29866PNF7knkGDf9VknfJWULhUpK
ncAOjtUbjhPthZ7EPw9BlpdC5i1VAJ56g6fXv29Z2bN06dIlZYDTr46y//CS+W4eWjg3ehnd3fsP
wn+STgn/iZ72vRjvVPEfUX3bgaxI1UA6rKbb2e4Fi0gG3gnAZXtRk+prtpcsVv23epFitl2mFz1W
/y5aUp/pxZLdy6VM1xR5GaSSvnlLFYCn3uDp9e/7bN88T+KfhyA7MnImCbLbAbJY6MmRBior91Fv
b59ffKhMu2dGR2ng+AmALDKyjjRwanyC+gcGlNG5Xx2F/wBkcwFbVfxHVN+qgawdjGUDRyswdFIu
b5VdtoJwuz7Ygazo+SIvAKzAPdtLAWX0feZXtP0VbLvjNejp3t6+0Rj1Dex2HVY8BNmurh6qrj7k
CGK8zu6hPfWywQ0NI1RTs9K1EFVvYOv27XT2gw8dQUwugRvO0Svgf+/2V9TU3Ky6/F33H/6jl66D
GqdU8R8RfdsBU3oJuFWptx1YZoK/TFlT8/HpoGaX2bXKDDuBPRENibSXDRTtbG7Vh0zXFOmLnU3S
r6eKvnu2baJD48hG6g6eXt/fyGSMViZWuI4fHoIsFnpSDyJlAH8s+PTAB0UX8hB5OOOY6AT1qi3o
4fqJk6EB+E90NO/l+KaK/4joOx1UM5XbZisVFrGtCIBaZSlFQS393GwAbpcNzQSSVuBtB6VWkG93
TqaXBW4zx5nuO/1+VdE3FnoCxOcCuV4t+GSA7P3792n+/IXIxqKsOCcNFBdX0507d/yKcaVvl/0n
v6AA2ViUFeekgSeamuA/8J+ctCMCLrofI7v/iD4fskGVFThl+7dsv3nQIJupL6IQmQ36coXrTLZz
U5os2heR39l8zyroe2H+PMyPxf6xOWmguqHAdfxjgKwOKxbzfaQylFbk4yR7aW7LyXl2x/rVrt11
/f4+6isXi65I6XdAKfJGP9c+ZCvPEg1UnF5b5JqZjnEarDntm5fHq7IypV9vlGTxHy9/U7QVXIZZ
dv8R0bfIOObVOJvL2GgHX6L9zwX2spXypn/nBkTZvnbnp2d1s/VNNNts95xTQd+qrljMtk9lEq3i
J5Eso/k8keOdHmPuo9NzVTjei5WLDZCdmZmhkpL6nLJxfkOSaPvpIJt+nihEpoI10es6OU60D07a
lOHYeHwd3bp1y684V4p2ORjJ9GH/SbS2hZ5RsXog2j0kRQPuXNrJ5RzRkisn2Qi3/RC1Ua7Hde3Y
Cf+RwH9y/f1wXnDQamVrGfzH7fNBFASt7t/p+OYFyKagLx3sMvXP6jgROM70TEv9eybwtGo7U1/T
Acbq2WI+NxM8i17T7r7TbaiCvutbCnPKxoUNWukgm94fO4hM/97u+Fzu1482c+mHX+es6853Hf8Y
IMv7gHJWTQYoyrUPoiCbDpNW/y0CnGaoMfc5da4VEJu/szon13sP+7x4fCPduHFDCuD0qxOjyVWJ
KysrLe+T/YffmoYd0IoEQ3YPUfNDXRQqrc4R/Tdz0CDSt3Qb292z036E8Rv29L4A/5HAf8L47UWv
6RRWRNvV4TgZ/EeF54MOv3W2e9DVR1TQN2fV/AIdP9sVBdlMwOoUMs3xiPm+Uu2kvs/0ndW/+2mf
INreuGOh6/jHAFnOpnFWLWwgcnN9L0A2E2jaZXfTr52pL7qCbGlpN50/f94vhpSiXQ5UUoNMOtCy
//Bb07ADBTuoSy+dylRKlemNtEg2wOoNuZPrip5vl5EVbUeG4OfFw6/CfyTwn7D9N4pBuhc2l8F/
VHg+eGFrmduQYSz3wz4q6JuzakFAj9fX8ApkrQDULrubfu1MfTFDro4g2/3yHNfxjwGynE3jrJob
kAz7XCuYFMmaZsqmZrufbFld0e9EoTlsu4pcf9myrcQPcp0/5kAlHWjZf/itqR8PMSdtugXZbNlO
kbZFs6V2AJ0OqdkCFJF+ZYJaK8B2Ym+vju0//hr8RwL/8er39LId8xv81P/3sn0d2pLBf1R4Pujw
W0fxHlTQN2fVvIbMINqzgkmRrGn6vFrzf2fqd6asLh8v+l0mqA3CVn5dY+tgzHX8Y4Ds9evXkyDb
qRXIioCoXeaU27CCYVFYTZ1vXoQq/f+ntyUCjrIdwyDLWUqroCsK/7Z48WLavOt5LUA2/feygsr0
gNp8jjnQSIdMu7atQNgueM8FZDP1I6wgiQOVqPvPtr7+0P0nrN9f5Lq6ZptE7t3uGNn9R5bng50d
8X24c70z2V8Ffa/rma8FyGaDNSuIzASgVjAsCqvpYGuVqU1vyy/IDKJdz0BWx4xsLiCbnlHM1AZA
dvaeu1HNyPJg8tJLL9GFCxe0yMhagWc6yNoFO5myn7m0nS2Tatcv0X7Y3U8Q38vwxt3vagqrjJVs
/hPEb53rNQCymSFDBv+Bvv2HwKj6gAr61iUj6xXIWrUDkLXea9czkI3CYk9281ydLL7kBcimZ2tl
y7I66U9UFnsyv2VjgE2tVCnzYk/ZADJbia9V1tUqCBcF1HSwFAHNIEBWhuBIhsU8ggZZGf0nV8jE
ef5DTDYby+A/6SALfXurCatxWnTsFj1OVj9WQd+6LvbkZJ6rVYlwtjmtVplWqxLlbAAcRMbU72t4
ttgTQHZ2hlGk3Ndu/m22cmKr75yAo2zHRglkzQFKSgMygaxI2Wy2Y8wAKwKSKRhOB1/zv5uzp6k2
rQDYCXSnt5l+T3bgbNXfsAIZGQKVoEBWZv8J6/fHdd1Bjwz+kwJZ6Nvdb+nEF0QBVfQ4J9cO8lgV
9B1VkE3BayqesIM+c5ziBeTaXU+F7z0DWc4sFRaWKD1HVja4E+mPCDCLtBP2Mbx1E8Oczh++v0x7
BYpseB/kgw/XCi6Y8sLWsm9474Vfw3/U0qQXug6qDRn8Jyr6Ngfi6b+v1XfmF5eZXl7agWamdq2q
hkT+LShdenUdFfRdUqbmYk8qgJ5dVljFezD3mV+CuOUHY7EngOzsjGwQYKgLxLKtSkrqaWZmxot4
V8k2ALII0t0ELYnWNvhPeTkWe/of+FEufiS7/+jyfMhWMZPpOyuwTJ/SYvXf5oobsyYyVQk56Vsu
GgvzHBX0DZC1nv/pNWSmlxl73X4Y7dW3FLqOfwyQ5c+CBXnU0nIJWdkkmAUBsjpdY/78hXT//n0l
IdSrTucXFNDU3/+BYBzBuGMNsHbgP/CfMINlla+tgv/o8Hywy5xaAWc2wBXRXK6AKjotRqQPYR+j
gr7zCubTpelgYC4M2MI1/fttF+bPcx3/PATZ1ta1VFd3EhAHkHWkgURijIqLS73iQWXbWb9xI43/
/lPHEBP2QxLXDzcL9vHXMxQvr1BW9151HP4Trg5VHQdU8R9d9C1aWpxtLQSr9Q0y6c9u7YN0eM5W
3qyixlXR99oNLXTyff9gByCpp23HPo9RafkS12HEQ5A9fPhoci/ZXkcQo1NWEfeSWya6uvoQdXX1
uBai6g0cGxqiQ2dGAbLIyDrSwNkPPqSt27erLn/X/Yf/AGRzAQ1V/EdHfWfLeoqAbKaSYZF/Ty9H
zjVzm4vmgjxHFX0fHTpEvSf0hC1AtH+/66HxGPVs2+Q6fngIsjrsJQsYzQ1G3ditrGw7jYyccS1E
1Rtg/+HVBYN8yOFa6gf/A8dP0JnRUdXl77r/8B/1tRzGeKSK/+igb1FYNM+LFS0tzlS27OSa6Zne
TPNsw9BprtdUSd+q7iULUPUPVO1su/2VOXTmzK9cxw8PQfbOnTvJEtFqZGRRWuxIA2Vl7TQ1NeVa
iKo3wP7zRFMTQBYZWUcaeHpLN/wn6fxR8h+roD1TyaZdgJ+t9DLX4Fml81TxH130LVJabM6W2oFo
+mJQVtrL5hvpWWGrTLDINWTVvEr6rm4oIDtwwffhQaOMtm9/Jrk2hgf88BBkseBT8NlMN5lQWc7F
Qk8/IrgOC3rI+kDXtV8qLOQR1EumqPhPtuA+vWTS7r+dLMCjow+p5D9R0beOOgvrnlTSNxZ8AqQ6
hWUvFnri+GQWyPb29lFl5T5HGTlZgAr9CB7EHywOtjaoOFf66/QPDNCp8QlHGbmwHpC4bvilnLw4
GC8Cg88DC0TFf0RWVBWZf2gFuVHya9X8Jyr6jpIG/bxX1fTdN7Cb9o0C5pzCXFSP58XBeJEwLz6z
QPbLL7+k0tLVAFmUFwtpIB7vpOvXr3uhQy3aYP9Zu6kTIIvyYiEN7OgfgP+YPD8q/iMCsukBstPF
c/wMsGVpWzX/iYq+ZdGH6v1QUd+rNxSivPi/AfMicN65Z4Fn8c8skP3hhx+ooGAx9pMFyAqBbF7e
Irp3754WEOrFTbD/FC1div1kAbJCILukuBj+Y3K8qPhPLiCbKfuaPkdW9eDdSf9V85+o6NvJb4hj
M1cGqajvxcV52E8WICv0MmNR0QLP4p9ZIMsxBcqLgy/RVbEsGmXF1uiL8rHwS3ZVCI5UKxvz4kWP
SBtR8J9cQBYZ2dnjiqr+EwV9qzD+yt5HVfWN8mJkY0WysV6WFT8yR5b/AeXFAFkRsEZZsXVYjvIx
gKxIkKRa2ZgIhHpxTBT8RwRkMUc2+ziiqv9EQd8i4x+O0VffKC8GzNrBrJdlxZYgy/9YU7OSGhpG
hMpLRaAHx+gFxy0tl4wSdC6VwudRCzQ1N9N7t78SKi/FAz164Dv1938YJejwH+vRQ3f/warF7nxe
df/RXd94pkVb3ysTK2hkEjBnB3NR/f7SdIy4BN3L+OeR0mIOLW7dukXx+DqALObKWmqgsvIF+uUv
j4BhM1iA/adrx06ALObKWmrg8JmzdHRoCP4TUf/xeh/ZqIGD6v6D54M70NNd7zroe113vtA8yajC
XJTv+4XX59CRYwc9jX8sQdZYlKBoOTU3XwDMAmZnaWDVqiu0aNEyzyZpe6pmSRpj/ykrL6c//PVv
gFnA7CwNfPHd91Sa1AYWScvsrPAfBPqZYEUH/4G+oW/d9b08vogu/BlZ2SgDq9W9X/kmRsvK8j2P
fyxBlkOM8fGLVFGxBSALkJ2lAWRjxWh5YmKC9hw4CJAFyM7SgOpv28XU7/4o+A+CfatgXxf/gb6h
b531fXHiAm3Z+ziysljBeJYG/MjGZpwjy18gK6vXvFav5ikXF1fTnTt33EeqmreAt+4IVKwClSea
muA/Ar4P/4H/6Ow/0Df0rbu+kZVFRjo9K1vdUOBL/JMxI8uxxuXLV5NZ2S5kZZGVNTRQVbWX+vv3
C4ShOIQtcO3aNdrZP4CsLLKyhgaOnztPBwYH4RyCFoD/INg3B/u6+Q/0DX3rrO+r196lrt48ZGWR
lTU0sPetubR/sE/w6e/ssKwgy001Nq6m+vphwGzEYZbnSy9bVkn37993prCIH93W3k7vTn0GmI04
zPJ86eq6OviPw/EA/oNgn4N9Xf0H+oa+ddb36jX1NHwDmcmoz5Xl+dKVNUW+xT+2IMtlpFxO6lVp
KtpRs2S5oqKDbt78xGEYisPZf7icVPeVFnF/2QOyzclVrCcnJ+EQDi0A/0Ggz2OLrv4DfUPfuuub
y0mjDnJRv/+Onp/SJ5O/c/j0Fz/cFmS5Kd5qhRf5AYSqCaFuf7fq6kPU1dUjriocOcsCvNUKL1IC
2Itm0HL2gw9p6/bt8IocLQD/iabfpMZL3f0H+oa+dX4+8FYrvMhP1GEuqvd/aDxGPds25fj0FztN
CGSx8FM0AZYBGNvtiDlStqOwsEd0AxUdtgtx7wHuWoD/wH903q4K+oa+ddc3Fn6KZnm1X9vtpEcU
QiDLJ83MzFA83myAjdsMH85XB4zLy5+k//iP/3QXieJsw3/aOjqIwQaZ2egELk9v6aY//elP8ACX
FoD/RMdnzONjVPwH+oa+XQ6RUp/O+m5+cgkx2EQ1MxnF+37ymUX0n3/61HdtCoMs9+Sdd8aTK9d2
A2QjsvBTTc2LdPDgYd9FGJULXEzuLduLvWUjA/Kvjp6lI8eORUXevt8n/CdawX7U/Af6hr59H0RD
vMD4xTHq7s8HyEZkFeMXX59Ph4/+IhDFOQJZ7tFzz+2i2tpBwKzmMFtXdzL5G68NRIRRusju3l4a
SW5rhays3kHL+O8/pfUbN0ZJ2oHcK/xHb79JjYtR9R/oG/oOZCAN6SK79vyMBs/PBcxqDrMn34/R
2g0tganMMcjyfI6qqobktjxvA2Y1hVneaiceryOd520E5mFpF2L/aWxupo/+Mg2Y1XRLHt4qZGUi
Af/xwcngP/oH+lH2H+gb+vZh2JSmSdZ3Q1M5vf1HlBjrWmrMW+3UNZYEGv84Bln2iLt371JpaS21
tFwCzGoGszwHmudC85wGfPyxAPtPQxJ0pv7+D8CsZjDLc6B5LjT8xx/fST1/4D96BvzwnwfxFfQN
ffs3gobbMuu7trGILk0DZnWDWZ4DzXOhg45/cgJZdgPe/6yysgUwqxHIMsRWVa2l//qvL8Id6SJw
dfafNR3rAbMagSwH4Zu6e+j27dsRUHC4twj/0S/Qh//86FPQN/Qd7gjr79VZ3y1PlQBmNSoxZohd
u3kpfXH7M3/FY9F6ziALmFVn5WGRVaIBsYH7nvEyCDCrR8CCIBz+g3nvufsy/OdR/8HzIXc9yeaL
0Le1vgGzemSlw4RYVpYrkOUGpqenqaKiFdvyKJ6ZrajooJs3Pwk+Go34Fdl/1nV2YlsexTOzm3fs
pMnJyYirOfjbh//oEezDf6x9B/qGvoMfVYO7Iuu7dSO25VG9xLij56f0yeTvghNO2pVcgyy3x6Wo
DLOYM6telvZBJnYTXb/+m9BEGPULcykqwyzmzKoXtPCb9udeeIF++9FHUZdxaPcP/1HPb1IZM/iP
vdtA39C3vUrUPYJLURlmMWdWvewsZ2I37VpEv/nt1VAF6AnIpjKz8XgjJRJjWABKkewsv3jgFxCA
2FB90Lg4v5n8p7Y2+vjrGSwApUh2ll888AsIQCz8R7ZSRhX6A/8R9xs8H9SDWejbmb4bVy2lsc/V
gznVs6m59p9fPPALiLAh1pPSYrNUv/322yQY1VN9/TBgVnKY5RcO/OKBH5D4yGEB9p+ViWZ6d+oz
wKzkMMsvHPjFA/xHDt/hXsB/1An24T/O/Qb6hr6dq0adM1jf9U2lNHwDMJsrXAZ1Hr9w4BcPssQ/
nmVkU+5y//79ZInxU1RbOwiYlRRm+UUDv3DggQMfuSzA/rNuw0YauXwVMCspzPKLBn7hAP+Ry3e4
N/Af+YN9+E/ufgN9Q9+5q0f+M1nfT61vosHzcykoKMN1nL044BcN/MJBpvjHc5BlV+FNj597bhet
WLENi0BJBrM1NS8bLxp4wMBHTguw/+zu7aW+V49gESjJYPaN8QnjRQP8R07fST1/4D9yBvzwH/d+
g+eDnNrmcn7o2xt979rzM9r2i8eJ52ACNOWxwctn5xovGmSLf3wB2ZSUz579dbJ8tZkaG99GdjZk
oG1uvkClpatp9+5/NV404CO/Bc6NjVFbRwd99JdpZGdDBto//PVvtHZTJ+0dGID/yO86Rg/hP/IE
/PAf750G+oa+vVeVPC3++twoNT+5hN7+ozwgF1WovvDnGK3eUEj/2r9LyvjHV5Bll5iZmUmuittA
dXUDgNmQYLa29hgtW1ZJX375pTyjFHoiZAH2n8bmZnpt7B3AbEgwO/bvN6m6rg7+I6RYuQ6C/4Qf
7MN//PMJ6Bv69k9d4bfM+m5oKqeBX81HZva/wwH6Y+/GqLKmSOr4x3eQTZV69fW9bGQEOTPYGhLQ
Re26D1Yl/mfq6OiUrhQg/CFSnR5wBv3A4KCREeTMhgorkurQR1518rneF6jr2WfhP+q4yyM9hf+E
E+zDf4JxGugb+g5GaeFchfX98sF/MTKCnBmMalY06PvmVYn/eWcBdW6WfypiICCbkj9nBDkzWFW1
G3NnfYb5qqq9tHRpJf3mN78NZ/TBVT23APsPZwYPnn4Tc2d9zs4eP3eeqmrr6CPsD+u5jsNqEP4T
XMAP/wle5dA39B286oK7IuubM4O7jz2GubM+Z2f3vjU3aevFya0FPwjuB3ZxpUBBlvvJk4SHhk5S
SUlNcmXjY8jOegy0vCJxSUk99ffvp3v37rmQBk6V0QLsP6eGh5OrxiWIS/Z0yHzKdA+8omqitc3I
gMN/ZPQAd32C//gb7MN/3OnT7dnQN/TtVkMyn8/6PvnGUapZuYi45DXoLKXu1zNWJG4ppP2DfUrF
P4GDbMpJeOlmLnnlcmMsBvW+a6Dnku14fF3SlquNecn46G0B9h8ueeVyYywG5T544ZLtrh07qa29
Hf6jt+sYdwf/ce8z5hdQ8B+5nAb6hr7lUqS3vWF9c8krlxtjMSj3QM8l2+u682n1mnol45/QQDYl
ay4XiMerk38bKZEYcw10UZsHywBbUbGFioqW061bt7wdLdCa9BZg/6lJlhv3JOdyfvz1DDK0DkuO
OQDfc+AglZWXw3+kV7v3HYT/uAv44T/ea9LLFqFv6NtLPcnWllFOX7ucNu5YSGOfuwc63TOu6ffH
ALtl7+O0PL5I6fgndJBNOcaNGzeouLjUyCo2NIwAaG1Kjhn6Gf4ZYMfHL0q5JLZsg57O/WH/iZdX
GFnF925/BaC1AVqGfoZ/BtiJiQn4j87OIXBv8B9nAT/8R0BUEh0CfUPfEsnR866wvkvLlxhZxZFJ
AK0dkDP0M/wzwF6cuKB8/CMNyKaUzVnFmpqVRslxXd1JAG0a0DLkM+wz9LPzYk9Yz8dEpRtk/2lK
btfDJcfjv/8UQJsGtAz5DPsM/fAfpaXuS+fhP9kDfviPL7ILrFHoG/oOTGwhXIj1vTKxwig5Pvk+
gDYdaBnyGfYZ+nWKf6QDWXPJcWvrWlq8OE7l5T+P9LY9vI1OeXlfEl6rDchHCXEII6Ril+SSm/Ub
N9KK2lo6MPxmpLft4W1Ahs6N0RNNTQbkw38UE3MI3YX//Bjww39CEKDPl4S+oW+fJRZq86zvtRta
KF6dTz8/OifS2/bwNjp9b8aouqHAgHwd4x9pQTblBTyp+8SJU1RYuMTI0q5YcSAyW/fwqs6cfS0o
WEwvvXSA7ty5E+rggIurZwH2nzeSqxwXLV1qZGnfunw1Mlv38KrOnH3lex985RX4j3ryDb3H8B/4
T+gi9LED0Df07aO8Qm+a9X1q+DgtKU4uZJTM0h4Yi0Vm6x5e1Zmzr4uL85K7MAxoHf9ID7JmT+C3
LNu2PU/5+YuN+aEMtZyt1GWBp1WrrlB19aHkvXUmwb3EWNWZ356gfDj08VCLDrD/7O7tpaLipcb8
UIZazrbItP2Nm7588d33dPaDD2lH/0CydKbcWNUZ/qOFdKW4CfiPFD8DOuGTBaBvnwyLZqWwAOv7
+T09tLjocWN+KEMtZyvt5pOq8v2Vb2J0aDxGnXsWUEnZQmNV56jEP0qBbMobeC8pru9mqF2wIM/Y
N7W0dJeSi0Tx1kPxeK+RbZ479yfU1dVD169fp7t370rh/OiEfhZI+Q9DbX5BgbFv6v7h00ouEsVb
Dx06M2pkm+c99hht3b4d/qOfZKW6I/iPVD8HOuOxBaBvjw2K5qSyQErfDLV5BfONfVN3HYkpuUgU
bz3UeyJmZJt/Mm8O9WzbFMn4R0mQTfcK3jf11KlhY/5oXt4iAwqXLdtKXJrL29PIkrHl7DEvYMV9
KytrN7KuvPXQ4cNHid8W4QMLhGEB9p/h06eN+aNLiosNKOw//hpxaS5vr+EmS+rluZw95gWsuG9P
b+k2sq689dCxoSH4TxjCwTUNC8B/IASdLQB96/zr4t4MfQ+/bswfXVS0wIDCrYMx4tJc3p5Glows
Z495ASvuW/szBUbWlbceOjp0KPLxjxYga3bFe/fuGT/q6OioUZrLc2vNcMuLJjFM1tcP+wa4vLIw
X6Oyct8saOXsMS9gxX2bmppC1hVjqHQWMPsPl+by/FIz3PKiSQyT70595hvg8sqofI1T4xOzoJWz
x7yAFfxHOtmgQ/9rAfgPpKCzBaBvnX9d3JtZ31yay3NrzXDLiyYxTA7f8A9weWVhvsa+0dnQytlj
XsAK8c+jOtUOZK1c0SxOXjSJYbKxcTXFYjHjb/nyxMO/0tJuAz5F/8zncmkwt8eZYb5Gb28fRIex
UXkLmP2HF01imGxrb3/oP63rOij19+LhVw34FP0znztv3mNGm5wZ5mv0DwzAf5RXD24A/gMN6GwB
6FvnXxf3ZtY3L5rEMLl6Tf3D+CfRXkipv+6X5xgZU9E/87lcGszxD2eG+Rp9A7sR/wjKLxIga2eL
6elpSv2dP3/eEI/on/lcLMpkZ2l8r6MF4D86/qq4p6AsAP8JytK4ThgWgL7DsDquGZQFoO+gLJ35
OgDZ8H8D9AAWgAVgAVgAFoAFYAFYABaABWABWMCBBQCyDoyFQ2EBWAAWgAVgAVgAFoAFYAFYABaA
BcK3AEA2/N8APYAFYAFYABaABWABWAAWgAVgAVgAFnBgAYCsA2PhUFgAFoAFYAFYABaABWABWAAW
gAVggfAtAJAN/zdAD2ABWAAWgAVgAVgAFoAFYAFYABaABRxYACDrwFg4FBaABWABWAAWgAVgAVgA
FoAFYAFYIHwLAGTD/w3QA1gAFoAFYAFYABaABWABWAAWgAVgAQcWAMg6MBYOhQVgAVgAFoAFYAFY
ABaABWABWAAWCN8C/z/tSI7rlIR2WQAAAABJRU5ErkJggg==

--_002_94C682931C08B048B7A8645303FDC9F33C3E619A91PUEXCB1Bnante_--

From karlheinz.wolf@nic.at  Mon Jan  3 00:52:07 2011
Return-Path: <karlheinz.wolf@nic.at>
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 2AF383A6989; Mon,  3 Jan 2011 00:52:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.429
X-Spam-Level: 
X-Spam-Status: No, score=-9.429 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_MESSAGE=0.001, 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 I4T2yNNTAn49; Mon,  3 Jan 2011 00:52:02 -0800 (PST)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) by core3.amsl.com (Postfix) with ESMTP id 4642728C0E7; Mon,  3 Jan 2011 00:52:00 -0800 (PST)
Received: from nics-exch.sbg.nic.at ([10.17.175.3]) by mail.sbg.nic.at over TLS secured channel with XWall v3.46 ; Mon, 3 Jan 2011 09:54:06 +0100
Received: from nics-mail.sbg.nic.at (10.17.175.2) by NICS-EXCH.sbg.nic.at (10.17.175.3) with Microsoft SMTP Server id 14.0.722.0; Mon, 3 Jan 2011 09:53:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBAB23.C28D17B8"
Subject: AW: Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary
Date: Mon, 3 Jan 2011 09:53:57 +0100
Message-ID: <8BC845943058D844ABFC73D2220D466509CFB2C7@nics-mail.sbg.nic.at>
In-Reply-To: <4d2178c4.0504d90a.5952.fffff508@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Gen-ART IETF LC review of draft-ietf-ecrit-lost-servicelistboundary
Thread-Index: AcuTybiC/+hqNiudRUOFZK+8ttfUZgJ+qg7kA1RwsFAAAw+/sA==
References: <4cfa61a4.eaecd80a.64b7.ffff8243@mx.google.com> <8BC845943058D844ABFC73D2220D466506876FA7@nics-mail.sbg.nic.at> <4d2178c4.0504d90a.5952.fffff508@mx.google.com>
From: Karl Heinz Wolf <karlheinz.wolf@nic.at>
To: Roni Even <ron.even.tlv@gmail.com>, General Area Review Team <gen-art@ietf.org>, <draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org>
X-XWALL-BCKS: auto
X-Mailman-Approved-At: Tue, 04 Jan 2011 09:58:57 -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: Mon, 03 Jan 2011 08:52:07 -0000

------_=_NextPart_001_01CBAB23.C28D17B8
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Roni,

I issued the 05 version before I was aware of your review (since your =
mail got somehow lost in a spam filter). Robert pointed out your review =
to me and instructed me to note it to the RFC editor. I won't forget it. =


Thanks again for your review,

Karl

=20

Von: Roni Even [mailto:ron.even.tlv@gmail.com]=20
Gesendet: Montag, 03. J=E4nner 2011 08:17
An: Karl Heinz Wolf; 'General Area Review Team'; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org
Cc: 'IETF-Discussion list'
Betreff: RE: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary

=20

Hi Karl,

I looked at the 05 version and it does not look like you fixed the nits

Roni

=20

From: Karl Heinz Wolf [mailto:karlheinz.wolf@nic.at]=20
Sent: Friday, December 17, 2010 10:28 AM
To: Roni Even; General Area Review Team; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org
Cc: IETF-Discussion list
Subject: AW: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary

=20

Roni,

thank you for your review and please apologize my delayed response.
I agree to your comments, the 2. one is really a good catch!

Thank you,
Karl



-----Urspr=FCngliche Nachricht-----
Von: ietf-bounces@ietf.org im Auftrag von Roni Even
Gesendet: Sa 12/4/2010 4:41
An: 'General Area Review Team'; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org
Cc: 'IETF-Discussion list'
Betreff: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary

Hi,



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-ecrit-lost-servicelistboundary-04

Reviewer: Roni Even

Review Date: 2010-12-04

IETF LC End Date: 2010-12-14

IESG Telechat date: (if known)



Summary: This draft is ready for publication as an Experimental RFC. =
There are some nits



Major issues:



Minor issues:



Nits/editorial comments:

1.      In the abstract the document starts with LoST,  Please expand to =
Location-to-Service Translation

2.      At the end of section 3.2  in the note, I think that the first =
"getServiceListBoundary" should be " getServiceBoundary"







Roni Even


------_=_NextPart_001_01CBAB23.C28D17B8
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><title>AW: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary</title><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Sprechblasentext Zchn";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.E-MailFormatvorlage18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.E-MailFormatvorlage19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.SprechblasentextZchn
	{mso-style-name:"Sprechblasentext Zchn";
	mso-style-priority:99;
	mso-style-link:Sprechblasentext;
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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=3DDE-AT link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Roni,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I issued the 05 version before I was aware of your review (since your =
mail got somehow lost in a spam filter). Robert pointed out your review =
to me and instructed me to note it to the RFC editor. I won&#8217;t =
forget it. <o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks again for your review,<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Karl<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-GB =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span><=
/b><span lang=3DDE =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[mailto:ron.even.tlv@gmail.com] <br><b>Gesendet:</b> Montag, 03. =
J=E4nner 2011 08:17<br><b>An:</b> Karl Heinz Wolf; 'General Area Review =
Team'; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org<br><b>Cc:</b=
> 'IETF-Discussion list'<br><b>Betreff:</b> RE: Gen-ART IETF LC review =
of =
draft-ietf-ecrit-lost-servicelistboundary<o:p></o:p></span></p></div></di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Karl,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I looked at the 05 version and it does not look like you fixed the =
nits<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Karl Heinz =
Wolf [mailto:karlheinz.wolf@nic.at] <br><b>Sent:</b> Friday, December =
17, 2010 10:28 AM<br><b>To:</b> Roni Even; General Area Review Team; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org<br><b>Cc:</b=
> IETF-Discussion list<br><b>Subject:</b> AW: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary<o:p></o:p></span></p></div></di=
v><p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
style=3D'margin-bottom:12.0pt'><span lang=3DEN-US =
style=3D'font-size:10.0pt'>Roni,<br><br>thank you for your review and =
please apologize my delayed response.<br>I agree to your comments, the =
2. one is really a good catch!<br><br>Thank =
you,<br>Karl<br><br><br><br>-----Urspr=FCngliche Nachricht-----<br>Von: =
ietf-bounces@ietf.org im Auftrag von Roni Even<br>Gesendet: Sa 12/4/2010 =
4:41<br>An: 'General Area Review Team'; =
draft-ietf-ecrit-lost-servicelistboundary.all@tools.ietf.org<br>Cc: =
'IETF-Discussion list'<br>Betreff: Gen-ART IETF LC review of =
draft-ietf-ecrit-lost-servicelistboundary<br><br>Hi,<br><br><br><br>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">http://w=
iki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br><br><br>P=
lease resolve these comments along with any other Last Call comments you =
may receive.<br><br><br><br>Document: =
draft-ietf-ecrit-lost-servicelistboundary-04<br><br>Reviewer: Roni =
Even<br><br>Review Date: 2010-12-04<br><br>IETF LC End Date: =
2010-12-14<br><br>IESG Telechat date: (if known)<br><br><br><br>Summary: =
This draft is ready for publication as an Experimental RFC. There are =
some nits<br><br><br><br>Major issues:<br><br><br><br>Minor =
issues:<br><br><br><br>Nits/editorial =
comments:<br><br>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In the abstract the =
document starts with LoST,&nbsp; Please expand to Location-to-Service =
Translation<br><br>2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; At the end of =
section 3.2&nbsp; in the note, I think that the first =
&quot;getServiceListBoundary&quot; should be &quot; =
getServiceBoundary&quot;<br><br><br><br><br><br><br><br>Roni =
Even</span><span =
lang=3DEN-US><o:p></o:p></span></p></div></div></div></body></html>
------_=_NextPart_001_01CBAB23.C28D17B8--

From hallam@gmail.com  Tue Jan  4 10:10:37 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 2808F3A6B83 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 10:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.381
X-Spam-Level: 
X-Spam-Status: No, score=-3.381 tagged_above=-999 required=5 tests=[AWL=0.217,  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 F8KQZ5fg5Fzw for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 10:10:35 -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 72D083A6B73 for <ietf@ietf.org>; Tue,  4 Jan 2011 10:10:34 -0800 (PST)
Received: by gxk28 with SMTP id 28so6827442gxk.31 for <ietf@ietf.org>; Tue, 04 Jan 2011 10:12:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=fnZeiN+FVIz/JgoyjeYbvI4frYEkosngamiGmVoSPXQ=; b=lW1XOAUVE8QF/Pi1GGCBjSsQFmXYbTExRp5/yi+TJbVZw38BRNWt0bo8oOnVpQ0ls6 5njCDbInuTfAV5uMK7/YcEVKWnN16sMw9QtPakpQvCMmD8EBRT3dVC5AuSbZxbsbLP/I A7uegVQ19t8ASEvae5IWLPnPcVQfETduscFQ4=
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=qADxtDq7cRr8ARU6SqfmJOzbolmI0yUmELWzPj5Fu8Q05ZT2jxq0f+rFVS0ukyBxMd 1q7FABBMGcDYpItVZPOiMbnPCMcSNWxh12VfzD3eBA0ubEN8NEwljEz31UDyPLZiYF84 J1KkSvMblbXMWbgRliqqVkTDxONSvySYlf0EA=
MIME-Version: 1.0
Received: by 10.100.231.20 with SMTP id d20mr2281546anh.35.1294164761101; Tue, 04 Jan 2011 10:12:41 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Tue, 4 Jan 2011 10:12:41 -0800 (PST)
In-Reply-To: <84AFE0E6-D1E7-4606-A620-341457E1B1E5@checkpoint.com>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com> <1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com> <AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com> <84AFE0E6-D1E7-4606-A620-341457E1B1E5@checkpoint.com>
Date: Tue, 4 Jan 2011 18:12:41 +0000
Message-ID: <AANLkTinbn0pjixGakae+7uwOyX6KjDsRj_gE5rvtENMZ@mail.gmail.com>
Subject: Re: BCP request: WiFi at High-Tech Meetings
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=0016368e2050ddc45f04990936b5
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: Tue, 04 Jan 2011 18:10:38 -0000

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

The problem there appears to have been the density of MiFi boxes all
offering access and a WiFi stack that crashed in the presence of 500+ access
points.

I am not sure that we have experience operating in that zone either.

Of course, had said vendor been more willing to allow tethering on their
phone the MiFi boxes might not have become so popular/necessary.


On Tue, Jan 4, 2011 at 4:07 PM, Yoav Nir <ynir@checkpoint.com> wrote:

>
> On Jan 4, 2011, at 5:55 PM, Phillip Hallam-Baker wrote:
>
> > It could be the 11a support.
> >
> > Or it might well be the vendor that supplies the 11a equipment.
> >
> > At home I have a box with 7 defunct WiFi routers that I discarded after
> they started to fail. Specifically the wireless side of the router would
> stop functioning or require rebooting every 24 hours or so to keep
> functioning.
> >
> > Then three years ago I mentioned the problem on this list and bought an
> AirPort Extreme on the advice of several people.
> >
> > It has now been running for three years without issue.
> >
> >
> > I do notice that a significant proportion of laptops used at IETFs are
> produced by one specific vendor. And lets face it, we are the type of
> audience that is quite willing to pay two to three times the minimum for a
> laptop.
>
> Wouldn't the same be true for media events staged by that same specific
> vendor?  That was the event the NYT article described.




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

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

The problem there appears to have been the density of MiFi boxes all offeri=
ng access and a WiFi stack that crashed in the presence of 500+ access poin=
ts.=A0<div><div><br></div><div>I am not sure that we have experience operat=
ing in that zone either.=A0<br>
<br></div><div>Of course, had said vendor been more willing to allow tether=
ing on their phone the MiFi boxes might not have become so popular/necessar=
y.</div><div><br></div><div><br><div class=3D"gmail_quote">On Tue, Jan 4, 2=
011 at 4:07 PM, Yoav Nir <span dir=3D"ltr">&lt;<a href=3D"mailto:ynir@check=
point.com">ynir@checkpoint.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;"><div class=3D"im"><br>
On Jan 4, 2011, at 5:55 PM, Phillip Hallam-Baker wrote:<br>
<br>
&gt; It could be the 11a support.<br>
&gt;<br>
&gt; Or it might well be the vendor that supplies the 11a equipment.<br>
&gt;<br>
&gt; At home I have a box with 7 defunct WiFi routers that I discarded afte=
r they started to fail. Specifically the wireless side of the router would =
stop functioning or require rebooting every 24 hours or so to keep function=
ing.<br>

&gt;<br>
&gt; Then three years ago I mentioned the problem on this list and bought a=
n AirPort Extreme on the advice of several people.<br>
&gt;<br>
&gt; It has now been running for three years without issue.<br>
&gt;<br>
&gt;<br>
&gt; I do notice that a significant proportion of laptops used at IETFs are=
 produced by one specific vendor. And lets face it, we are the type of audi=
ence that is quite willing to pay two to three times the minimum for a lapt=
op.<br>

<br>
</div>Wouldn&#39;t the same be true for media events staged by that same sp=
ecific vendor? =A0That was the event the NYT article described.</blockquote=
></div><br><br clear=3D"all"><br>-- <br>Website: <a href=3D"http://hallamba=
ker.com/">http://hallambaker.com/</a><br>
<br>
</div></div>

--0016368e2050ddc45f04990936b5--

From jmpolk@cisco.com  Tue Jan  4 12:14:41 2011
Return-Path: <jmpolk@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 420EF3A6B39 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 12:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.516
X-Spam-Level: 
X-Spam-Status: No, score=-110.516 tagged_above=-999 required=5 tests=[AWL=0.083, 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 NLdswiMEmBlh for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 12:14:40 -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 34ECD3A6AE1 for <ietf@ietf.org>; Tue,  4 Jan 2011 12:14:40 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAM4OI02rR7H+/2dsb2JhbACkK3OjVJhshUoEhGg
X-IronPort-AV: E=Sophos;i="4.60,274,1291593600"; d="scan'208";a="310182393"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 04 Jan 2011 20:16:47 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8716.cisco.com [10.99.80.23]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p04KGko4023451; Tue, 4 Jan 2011 20:16:47 GMT
Message-Id: <201101042016.p04KGko4023451@sj-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 04 Jan 2011 14:16:45 -0600
To: Phillip Hallam-Baker <hallam@gmail.com>, "Worley, Dale R (Dale)" <dworley@avaya.com>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: BCP request: WiFi at High-Tech Meetings
In-Reply-To: <AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.c om>
References: <4D1B5053.6000005@dcrocker.net> <Pine.GSO.4.63.1012290751380.5366@pita.cisco.com> <72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu> <4D1B6415.4040502@bogus.com> <1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com> <CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com> <AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Tue, 04 Jan 2011 20:14:41 -0000

At 09:55 AM 1/4/2011, Phillip Hallam-Baker wrote:
>It could be the 11a support.
>
>Or it might well be the vendor that supplies the 11a equipment.
>
>At home I have a box with 7 defunct WiFi routers that I discarded 
>after they started to fail. Specifically the wireless side of the 
>router would stop functioning or require rebooting every 24 hours or 
>so to keep functioning.
>
>Then three years ago I mentioned the problem on this list and bought 
>an AirPort Extreme on the advice of several people.
>
>It has now been running for three years without issue.
>
>
>I do notice that a significant proportion of laptops used at IETFs 
>are produced by one specific vendor.

Phillip - I bet you there are more Thinkpads than laptops from your 
unnamed vendor at any given IETF over the last 5-8 years.

Don't take this as an attack on your laptop's vendor, I happening to 
be in transition to that very same vendor from a Thinkpad.

James

>And lets face it, we are the type of audience that is quite willing 
>to pay two to three times the minimum for a laptop.
>
>
>On Mon, Jan 3, 2011 at 3:49 PM, Worley, Dale R (Dale) 
><<mailto:dworley@avaya.com>dworley@avaya.com> wrote:
>________________________________________
>From: <mailto:ietf-bounces@ietf.org>ietf-bounces@ietf.org 
>[<mailto:ietf-bounces@ietf.org>ietf-bounces@ietf.org] On Behalf Of 
>Chris Elliott [<mailto:chelliot@pobox.com>chelliot@pobox.com]
>
>I strongly agree here. Encourage .11a (5ghz) usage, disable .11n for 
>the .11b/g 2.4ghz spectrum. We also have the luxury of a large 
>number of repeat attendees, and many of you have learned the 
>benefits of using .11a and will go out of your way to use it. We 
>facilitate that through advertising .11a-only SSID's.
>_______________________________________________
>
>Whereas the NYT article seems to be describing large rooms full of 
>journalists and other technology illiterates, many of whom are 
>trying to send or receive streaming video, sometimes the video of 
>the presenter they are sitting in front of!
>
>Dale
>_______________________________________________
>Ietf mailing list
><mailto:Ietf@ietf.org>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf
>
>
>
>
>--
>Website: <http://hallambaker.com/>http://hallambaker.com/
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From A.Kral@bobek.cz  Tue Jan  4 12:16:25 2011
Return-Path: <A.Kral@bobek.cz>
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 C39913A6CE6 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 12:16:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.25
X-Spam-Level: 
X-Spam-Status: No, score=-1.25 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
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 teVoDwGtQn2E for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 12:16:24 -0800 (PST)
Received: from srv1.trusted.cz (srv1.trusted.cz [81.2.209.38]) by core3.amsl.com (Postfix) with ESMTP id AFD923A6BA7 for <ietf@ietf.org>; Tue,  4 Jan 2011 12:16:23 -0800 (PST)
Received: from bobek-a0.bobek.cz (unknown [109.80.14.240]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by srv1.trusted.cz (Postfix) with ESMTPSA id E55BE138E0A7; Tue,  4 Jan 2011 21:18:28 +0100 (CET)
Received: from bobek by bobek-a0.bobek.cz with local (Exim 4.72) (envelope-from <A.Kral@bobek.cz>) id 1PaDKu-0007tS-3B; Tue, 04 Jan 2011 21:18:28 +0100
Date: Tue, 4 Jan 2011 21:18:27 +0100
From: Antonin Kral <A.Kral@sh.cvut.cz>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Subject: Re: Question about Prague
Message-ID: <20110104201827.GD25922@bobek.cz>
References: <20110102230256.28121.qmail@joyce.lan> <2C772989-BA06-4E1C-BE04-65AE11BFFDAA@bbn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2C772989-BA06-4E1C-BE04-65AE11BFFDAA@bbn.com>
X-URL: http://www.bobek.cz
Organization: Trusted Solutions s.r.o. <http://www.trusted.cz>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: John Levine <johnl@iecc.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, 04 Jan 2011 21:22:38 -0000

* Richard L. Barnes <rbarnes@bbn.com> [2011-01-04 18:45] wrote:
> According to Google Maps, their stop is around a 12 minute walk to the IETF hotel, and marginally closer than the main train station.
> <http://goo.gl/sib5S>

You can take bus 100 from Airport to Zlicin and then change to Metro
line B (yellow). The station Florenc near the hotel is on the same line,
so you just need to sit and enjoy the tunnels ;)

  Antonin

From rbarnes@bbn.com  Tue Jan  4 13:32:52 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 ADE9E3A6D38 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 13:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.907
X-Spam-Level: 
X-Spam-Status: No, score=-102.907 tagged_above=-999 required=5 tests=[AWL=-0.308, 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 fClHVBX+GtMe for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 13:32:51 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id AAEC43A6D39 for <ietf@ietf.org>; Tue,  4 Jan 2011 13:32:51 -0800 (PST)
Received: from [192.1.255.181] (port=56500 helo=col-raltmann-l1.nira.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PaEWt-000ABE-Rq; Tue, 04 Jan 2011 16:34:55 -0500
Subject: Re: Question about Prague
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: <2C772989-BA06-4E1C-BE04-65AE11BFFDAA@bbn.com>
Date: Tue, 4 Jan 2011 16:34:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8545A74-1D71-4598-B6BD-156E423DAC27@bbn.com>
References: <20110102230256.28121.qmail@joyce.lan> <2C772989-BA06-4E1C-BE04-65AE11BFFDAA@bbn.com>
To: Richard L. Barnes <rbarnes@bbn.com>
X-Mailer: Apple Mail (2.1082)
Cc: John Levine <johnl@iecc.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, 04 Jan 2011 21:32:52 -0000

Correction:=20
s/the IETF hotel/the hotel where the IETF was *last* time/

--Richard



On Jan 4, 2011, at 12:42 PM, Richard L. Barnes wrote:

> I have also had good luck with the CEDAZ minibus to Namesti Republiky
> <http://www.cedaz.cz/>
>=20
> According to Google Maps, their stop is around a 12 minute walk to the =
IETF hotel, and marginally closer than the main train station.
> <http://goo.gl/sib5S>
>=20
> --Richard
>=20
>=20
>=20
>=20
> On Jan 2, 2011, at 6:02 PM, John Levine wrote:
>=20
>>> Public transit?  We arrived and left by train, so I don't know what =
airport
>>> access is like there.
>>=20
>> There's an airport express bus to the downtown train station, and =
city
>> buses to the metro.  Details here:
>>=20
>> http://www.myczechrepublic.com/prague/prague-airport-bus.html
>>=20
>> R's,
>> John
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From rbarnes@bbn.com  Tue Jan  4 13:53:25 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 0FC6D3A6AB4; Tue,  4 Jan 2011 13:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.885
X-Spam-Level: 
X-Spam-Status: No, score=-102.885 tagged_above=-999 required=5 tests=[AWL=-0.286, 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 fVfLNTk2ToHv; Tue,  4 Jan 2011 13:53:23 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id C6D0E3A6C34; Tue,  4 Jan 2011 13:53:23 -0800 (PST)
Received: from [192.1.255.181] (port=56713 helo=col-raltmann-l1.nira.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PaEqo-000AQe-BS; Tue, 04 Jan 2011 16:55:30 -0500
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART review of draft-groves-sakke-00
Date: Tue, 4 Jan 2011 16:55:29 -0500
Message-Id: <6E2836A2-3C56-46E3-BABB-8CDA2BD85030@bbn.com>
To: gen-art@ietf.org, IETF Discussion <ietf@ietf.org>, IESG <iesg@ietf.org>, draft-groves-sakke@tools.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, 04 Jan 2011 21:53:25 -0000

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

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

Document: draft-groves-sakke-00
Reviewer: Richard Barnes
Review Date: 04 Jan 2010
IETF LC End Date: 18 Jan 2010
IESG Telechat date: (if known)

Summary: It's not clear to me why this draft is necessary, given that =
there is already a published specification for the algorithm.  Putting =
that aside, the draft is not ready for publication. =20

Major issues:

-- When I read this document, it's not clear to me what I would need to =
do to integrate this into a protocol.  In particular, it would be =
helpful to have a list of parameters according to:
(a) Which ones are constant for the whole algorithm
(b) Which ones are expected to be set out of band for a given =
implementation
(c) Which ones must be negotiated in the protocol
For example, the algorithm makes use of a hash function and an elliptic =
curve, but it's not clear how the communicating parties agree on what =
hash function or curves to use.

-- =46rom a security perspective, the choice of a single static curve =
makes me uncomfortable.  This is not typical of other EC-based =
algorithms.  For example, RFC 4754, RFC 5091, and ECDSA (ANSI X9.62) all =
allow choices of curves, even if that choice is restricted to an =
enumerated set or a class.

-- If this document is extending RFC 5091, then it should formally =
extend it (as in, with a line at the top), and explain in more detail =
its relation to RFC 5091.


Minor issues:

-- The notation lg(x) for logarithms is not defined.  Suggest adding to =
the Notation section.

-- The normative references [MIKEY-SAKKE], [P1363], [P1363a] should be =
made informative.

-- The informative references [S-K], [SK-KEM] should be made normative

-- I have not checked whether the algorithm in this draft is the same as =
that described in references [S-K] [SK-KEM]


Nits/editorial comments:

-- Section 2.2 seems to have additional spaces at the beginning of each =
line.



From ole@cisco.com  Tue Jan  4 18:33:54 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 D6AD43A67E5 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 18:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.557
X-Spam-Level: 
X-Spam-Status: No, score=-110.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 xX708W81n6Hq for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 18:33:53 -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 3640C3A67D8 for <ietf@ietf.org>; Tue,  4 Jan 2011 18:33:53 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoKAFxOI02rR7Hu/2dsb2JhbACWA44qc6QKgk8OAZYMhUoEhGiGHw
X-IronPort-AV: E=Sophos;i="4.60,275,1291593600"; d="scan'208";a="310350750"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 05 Jan 2011 02:36:00 +0000
Received: from pita.cisco.com (pita.cisco.com [171.71.177.199]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p052a0eD003856 for <ietf@ietf.org>; Wed, 5 Jan 2011 02:36:00 GMT
Date: Tue, 4 Jan 2011 18:35:08 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: Off Topic: On the way to Prague
Message-ID: <Pine.GSO.4.63.1101041816310.28063@pita.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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: Wed, 05 Jan 2011 02:33:55 -0000

Hello,

If you have some extra time before the IETF, may I cordially invite 
you to a very special evening in the Thomaskirche in Leipzig, Germany 
on Thursday, March 24th, at 18:30 for a pipe organ demonstration and 
concert. This is the church where Johann Sebastian Bach spent the last 
part of his life as organist and cantor (1723 - 1750). You'll hear 
music by Bach (obviously), Mendelssohn and others, performed by two 
organists on the famous Wilhelm Sauer organ (1889) and Gerald Woehl 
"Bach" organ (2000).

Details of the event can be found here: 

http://www.yikes.com/~ole/store/LEIPZIG/Social_Event.html

(Sponsorship details available upon request).

Leipzig is about 4 hours by train from Frankfurt. Prague is another 
3.5 hours (via Dresden). (There is an airport in Leipzig too if you
prefer to fly).

Ole J. Jacobsen
Principal without Chorus
http://organdemo.info
ole@organdemo.info





From tme@americafree.tv  Tue Jan  4 18:36:51 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 2F7D83A67E5 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 18:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.187
X-Spam-Level: 
X-Spam-Status: No, score=-102.187 tagged_above=-999 required=5 tests=[AWL=0.412, 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 A1qmV6iB0lS2 for <ietf@core3.amsl.com>; Tue,  4 Jan 2011 18:36:50 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 225B93A67D8 for <ietf@ietf.org>; Tue,  4 Jan 2011 18:36:50 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id A92239938AE3; Tue,  4 Jan 2011 21:38:51 -0500 (EST)
Subject: Re: Question about Prague
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <C8545A74-1D71-4598-B6BD-156E423DAC27@bbn.com>
Date: Tue, 4 Jan 2011 21:38:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B823A10D-C10F-4029-AEA1-57B1232F4AC4@americafree.tv>
References: <20110102230256.28121.qmail@joyce.lan> <2C772989-BA06-4E1C-BE04-65AE11BFFDAA@bbn.com> <C8545A74-1D71-4598-B6BD-156E423DAC27@bbn.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
X-Mailer: Apple Mail (2.1081)
Cc: John Levine <johnl@iecc.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, 05 Jan 2011 02:36:51 -0000

On Jan 4, 2011, at 4:34 PM, Richard L. Barnes wrote:

> Correction:=20
> s/the IETF hotel/the hotel where the IETF was *last* time/

Which is the same location this time (as revealed by the announcement =
just made by the Secretariat).

Regards
Marshall

>=20
> --Richard
>=20
>=20
>=20
> On Jan 4, 2011, at 12:42 PM, Richard L. Barnes wrote:
>=20
>> I have also had good luck with the CEDAZ minibus to Namesti Republiky
>> <http://www.cedaz.cz/>
>>=20
>> According to Google Maps, their stop is around a 12 minute walk to =
the IETF hotel, and marginally closer than the main train station.
>> <http://goo.gl/sib5S>
>>=20
>> --Richard
>>=20
>>=20
>>=20
>>=20
>> On Jan 2, 2011, at 6:02 PM, John Levine wrote:
>>=20
>>>> Public transit?  We arrived and left by train, so I don't know what =
airport
>>>> access is like there.
>>>=20
>>> There's an airport express bus to the downtown train station, and =
city
>>> buses to the metro.  Details here:
>>>=20
>>> http://www.myczechrepublic.com/prague/prague-airport-bus.html
>>>=20
>>> R's,
>>> John
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From evnikita2@gmail.com  Tue Jan  4 21:18:38 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 5EC4D3A6805; Tue,  4 Jan 2011 21:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.245
X-Spam-Level: 
X-Spam-Status: No, score=-2.245 tagged_above=-999 required=5 tests=[AWL=-0.607, 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 J1mpI9Aq-AAg; Tue,  4 Jan 2011 21:18:37 -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 0C5EC3A67A2; Tue,  4 Jan 2011 21:18:36 -0800 (PST)
Received: by bwz12 with SMTP id 12so15062538bwz.31 for <multiple recipients>; Tue, 04 Jan 2011 21:20:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type; bh=ryLZVXbvQ3CdwMcEmjA4+jmSF1f24hWaQbUJw3fEbxI=; b=lH5sVrxasLA/ZsHIf7nOdsQOqrEJzCCanHG2+WNnM0ToigPY0YKt1vnpTzjpy7xXzf IcoCuwZgWGFoyjaZCq5/PkwSu3sMGO52Q6UtninZAJGJLpy04wM17RKi+ihjb/+abrg/ L5pvwKKotFmKRWFtVKw5KLMHbHIZro1P1HV+8=
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=xJeOLRJxtcUu77SgmoxMUkbzL5MqblGeIlGD2qxfqiU5t9Qi4UoaCstn0rCTEnu58k z2HdgdeZi1EYpfnytpJkuadP7+IItSZGoqFzXboob3Fc5kIdMx7pw41MyMkWVzPIpizU yr7D0Ec9RO78ojPEHTYXWiP/KKVXMb0QRVuEA=
Received: by 10.204.122.65 with SMTP id k1mr16707856bkr.80.1294204842045; Tue, 04 Jan 2011 21:20:42 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id a17sm12657626bku.23.2011.01.04.21.20.40 (version=SSLv3 cipher=RC4-MD5); Tue, 04 Jan 2011 21:20:41 -0800 (PST)
Message-ID: <4D23FFBA.5030804@gmail.com>
Date: Wed, 05 Jan 2011 07:20:58 +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>, uri-review@ietf.org,  URI <uri@w3.org>
Subject: FYI: Last Call On draft-yevstifeyev-tn3270-uri-12
Content-Type: multipart/alternative; boundary="------------090707080206010907030200"
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, 05 Jan 2011 05:18:38 -0000

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

That is FYI. Any comments are welcome. Excuses if you receive multiple 
copies of this. Mykyta.
> Date: Tue, 04 Jan 2011 09:52:23 -0800
> From: The IESG<iesg-secretary@ietf.org>
> Subject: Last Call:<draft-yevstifeyev-tn3270-uri-12.txt>  (The tn3270
> 	Uniform	Resource Identifier Scheme) to Informational RFC
> To: IETF-Announce<ietf-announce@ietf.org>
> Message-ID:<20110104175223.26076.55590.idtracker@localhost>
> Content-Type: text/plain; charset="us-ascii"
>
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'The tn3270 Uniform Resource Identifier Scheme'
>    <draft-yevstifeyev-tn3270-uri-12.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-01. Exceptionally, comments may be
> sent toiesg@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-yevstifeyev-tn3270-uri/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yevstifeyev-tn3270-uri/
>
>
> No IPR declarations have been submitted directly on this I-D.


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

<!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>That is FYI. Any comments are welcome. Excuses
        if you receive multiple copies of this. Mykyta.</big><br>
      <blockquote type="cite"><font><font size="-1">
            <pre wrap=""><big>Date: Tue, 04 Jan 2011 09:52:23 -0800
From: The IESG <a class="moz-txt-link-rfc2396E" href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a>
Subject: Last Call: &lt;draft-yevstifeyev-tn3270-uri-12.txt&gt; (The tn3270
	Uniform	Resource Identifier Scheme) to Informational RFC
To: IETF-Announce <a class="moz-txt-link-rfc2396E" href="mailto:ietf-announce@ietf.org">&lt;ietf-announce@ietf.org&gt;</a>
Message-ID: &lt;20110104175223.26076.55590.idtracker@localhost&gt;
Content-Type: text/plain; charset="us-ascii"


The IESG has received a request from an individual submitter to consider
the following document:
- 'The tn3270 Uniform Resource Identifier Scheme'
  &lt;draft-yevstifeyev-tn3270-uri-12.txt&gt; 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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2011-02-01. 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-yevstifeyev-tn3270-uri/">http://datatracker.ietf.org/doc/draft-yevstifeyev-tn3270-uri/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-yevstifeyev-tn3270-uri/">http://datatracker.ietf.org/doc/draft-yevstifeyev-tn3270-uri/</a>


No IPR declarations have been submitted directly on this I-D.</big></pre>
          </font></font></blockquote>
      <br>
    </font>
  </body>
</html>

--------------090707080206010907030200--

From stpeter@stpeter.im  Wed Jan  5 10:03:07 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 4B4923A6CE5; Wed,  5 Jan 2011 10:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level: 
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 F2a2Nzpzju01; Wed,  5 Jan 2011 10:03:05 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 45D8B3A6C9F; Wed,  5 Jan 2011 10:03:05 -0800 (PST)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A68244009B; Wed,  5 Jan 2011 11:19:32 -0700 (MST)
Message-ID: <4D24B2D5.6060709@stpeter.im>
Date: Wed, 05 Jan 2011 11:05:09 -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: [certid] Review of draft-saintandre-tls-server-id-check-12
References: <58FE898B-BD2A-4C6E-B769-256008D8A58B@cisco.com>	<4D0A2EA8.6080709@stpeter.im> <4D22584A.2070307@stpeter.im>
In-Reply-To: <4D22584A.2070307@stpeter.im>
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="------------ms070509000902060800050103"
Cc: IETF cert-based identity <certid@ietf.org>, IESG IESG <iesg@ietf.org>, 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: Wed, 05 Jan 2011 18:03:07 -0000

This is a cryptographically signed message in MIME format.

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

Done:

http://www.ietf.org/id/draft-saintandre-tls-server-id-check-13.txt

The diff from -12 is here:

http://tools.ietf.org/rfcdiff?url2=3Ddraft-saintandre-tls-server-id-check=
-13

Peter

On 1/3/11 4:14 PM, Peter Saint-Andre wrote:
> I just realized that we never replied publicly. Jeff and I had a phone
> chat with Cullen (and Alexey) about this before the holidays, and we
> plan to submit a revised I-D this week. Cullen raised some very good
> points, which we've attempted to address in the forthcoming version.
>=20
> On 12/16/10 8:22 AM, Peter Saint-Andre wrote:
>> Thanks for your comments. My co-author and I will need to confer befor=
e
>> replying, and that might take a few days given the length of your revi=
ew.
>>
>> Peter
>>
>> On 12/16/10 12:17 AM, Cullen Jennings wrote:
>>>
>>> So let me start with I think there is great information in here and I=

>>> think it should be published as a standards track RFC however I do
>>> think there are some issues with the relation with this draft and the=

>>> realities of what would help improve security in deployment of SIP,
>>> HTTP, IMAP, XMPP etc.
>>>
>>> There are many places where this draft makes choices to improve the
>>> security from many current practices. At face value this seems like a=

>>> good thing but it's not always. The thing reducing the overall
>>> security available to users of TLS is not if certs use CN-ID or
>>> DNS-ID, it is that it's such a PITA to deploy a TLS  server that
>>> people choose to not use TLS at all. Everywhere there is a trade off
>>> between making things marginally more secure, or making things
>>> cheaper and easer to deploy, I think we need to seriously consider
>>> the cheaper and easier approach. Yes, some things are just broken
>>> even if they are easy and obviously we can't do those. Let me give an=

>>> example of this. I looked at the cert for the domains for the authors=

>>> of this draft. www.cisco.com has 3 DNS names even though as fas as I
>>> can tell one of these are for something that would typically be used
>>> in a ftp URI and the other HTTP URI. This is because it makes it
>>> easier and cheaper for them to use TLS yet seems to go against the
>>> recommendation of this "BCP". Then I went over the www.paypal.com
>>> domain which uses, gasp, a CN-ID. Do we really believe that paypal is=

>>> seriously compromising their security by using a CN instead of
>>> URI-ID? If so, how? I'm pretty sure the paypal guys know how to run a=

>>> secure web server. With the exception of Microsoft small business
>>> server certificates (which are outrageously expensive by the way) it
>>> pretty hard to get SRV name certs. In making these recommendations,
>>> did the TLS WG consider the relative prices of various types of
>>> certificates? Lets say I had a certificate for the domain example.org=

>>> because I was using it for email and it has a CN because I got it
>>> years ago. Now lets say I am going to go deploy a SIP service on
>>> example.org. My position is that best way to encourage the use of
>>> security on the internet is to just reuse the certificate I have. It
>>> cheap, it's easy, it secure enough even if it does make you feel a
>>> bit dirty. I think Jeff disagrees w ith me, we argued for years about=

>>> this topic and my understanding is his position is that it would be
>>> better to say that all new deployments MUST not use a CN name because=

>>> it's less secure. Give the prevalence of CN on the internet today, I
>>> think it is fine to tell people how DNS-ID is better but I don't
>>> think it's OK to tell them they should not use CN-ID and I definitely=

>>> don't think it is OK to tell implementors they don't need to
>>> implement CN-ID.
>>>
>>> I encouraged Chris to write this draft long ago and what we had
>>> discussed at the time was forming a RFC with one or more boiler plate=

>>> pieces of text that could be used in creation of the name matching
>>> section of new protocols that got developed. I was thinking of
>>> something similar to the way we use rfc 5226 for writing IANA
>>> consideration section. Instead we have a document that is creating a
>>> very complex situations about whats normative. This draft is a BCP
>>> level, and it says you have to do everything in PKIX and PKIX takes
>>> precedence. That is basically elevating PKIX to a BCP without
>>> appropriate process review. Next this draft contradicts the
>>> procedures in existing protocols and says that it does not apply to
>>> the existing protocols but that it would take precedence over any
>>> future updates of existing protocols that use TLS within the scope
>>> specified here. I do not believe you have the consensus of the people=

>>> woking on SIP that the next time some specification is marked as an=20
>>> UPDATE to 3261, that implementations need to implement the procedures=

>>> in this draft. Furthermore, I think that would be counter productive.=

>>> I think you should make it clear this guidelines for designers of new=

>>> protocol and people updating existing protocol and that these
>>> protocols could make their own choices but would want to take into
>>> account the information in this draft. When I read the sentence,=20
>>> "However, the best current practices described here can be referenced=

>>> by future specifications, including updates to specifications for
>>> existing application protocols if the relevant technology communities=

>>> agree to do so." I think that is exactly the right solution to the
>>> problem. However, that not a BCP, thats a standards track spec.
>>> Furthermore, I think this draft is going to have all the normal bugs
>>> etc of any other spec that defines algorithms and such it should
>>> proceed through the standards track process. If this draft is going
>>> to go as a BCP, that text contradicts what a BCP is and needs to come=

>>> out and the rest of the draft be adjusted appropriately. My
>>> preference would be that this draft be standards track. Its writing
>>> exactly the same sort of normative algorithm text that we put in all
>>> kinds of other thing like SIP, HTTP, and even TLS. They are all
>>> standards track. This should be the same.
>>>
>>> Most RFCs today that use TLS have a page plus or minus that tells an
>>> implementer what they need to know about matching names in certs.
>>> This draft move that to 30 to 50 pages depending on how you count.
>>> Most implementers are just going to ignore this thus worsening the
>>> security situation. Think about why is the part implementers need to
>>> read 10x longer than existing deceptions - this just seems wrong. Now=

>>> it's easy to blow off this type concern and say get over it, it's the=

>>> same number of lines of code they need to write. But the problem is
>>> when an implementors goes to start doing this and encounters
>>> something that is 50 pages long, they instantly decide this is a big
>>> task and down it goes on the priority list of actually happening. The=

>>> other problem is that even thous it is long, it is still very
>>> confusing on how to do things (such at URI). I'll provide more
>>> detailed examples of this later in this email. If the document was
>>> restructured to have all the normative text in one s hort simple
>>> description and the rest moved to an appendix, it would be much
>>> easier to get people to take this seriously and easier to review that=

>>> it was correct.
>>>
>>> My final big issue is the use of normative language. Lets say there
>>> are two procedures A and B and we 100% consensus that B is better
>>> than A but we still have to support A for existing deployment
>>> reasons. To describe this, the text this draft would use is is MUST
>>> do A and SHOULD NOT do B. Now reading 2119 it is pretty clear that
>>> SHOULD NOT means you don't implement it unless there are real good
>>> reasons to implement it. So on the things were we agree A is
>>> preferred to B but you need both for backwards compatibility, this
>>> draft needs to say MUST implement A and MUST implement B but
>>> deployments are encouraged to use B as we are trying to move away
>>> from A. I think the whole document needs a careful read checking for
>>> this issue. You can insert the usual rant here about why SHOULD is a
>>> awful word in specs 90% of the time it used because implementer
>>> thinks it means "ignore rest of sentence". For example,  section 5.4
>>> discusses they this spec continues to mandate protocols MUST suppo rt=

>>> CN yet this draft continually use "SHOULD NOT" when what it really
>>> means is MUST implement. This is going to confuse implementors of
>>> IETF specification and be ignored by operators. Given the goals of
>>> this spec it would be much better if it was clearly defining what
>>> IETF required implementers of protocols to do instead of confusing
>>> that with how we wish security was deployed.
>>>
>>>
>>> On to the nits.
>>>
>>> Take an applications like a web server. Is the preferred thing in a
>>> cert a DNS-ID or a URI-ID. My reading of the 3.3 is that URI-ID is
>>> preferred over DNS-ID yet the examples don't match that. I think
>>> point 3 in section 3.1 tries to explain this away but I don't
>>> understand that - clearly web browsers use a URI.
>>>
>>> The rules in section 3.1 don't make sense for a CA. How will the CA
>>> know if the cert I want is going to be used for a protocol that uses
>>> SRV?
>>>
>>> In section 3.2, in the imap example, you are saying that if I
>>> configure my imap server to mail.example.com and it presents a
>>> certificate with a DNS-ID of example.com that this is OK. That does
>>> not sound OK to me but I don't know how IMAP works. In the SIP
>>> example, the cert should have a SRV and DNS name too. As well as a CN=

>>> if you actually want it to work in the real world.
>>>
>>> In section 4.2.1 you have a long discussion on how the information
>>> used must come from a way that can't be tampered with over the
>>> internet. I generally agree with this but would like to point out
>>> that protocols like LOST (see section 18 of rfc5222) specially do the=

>>> opposite of this and actually match the cert agains the output of
>>> NAPTR process not the input to the NAPTR process.
>>>
>>> The example just seem plain wrong in some cases. Take for example
>>> section 4.2.2 where the SIP example has only a URI reference
>>> identifiers and no DNS yet the section right before this has said the=

>>> list MUST include a DNS-ID. This text has been through how many
>>> reviews and Last Calls? The problem here is that this draft is too
>>> long to review for stuff like this. Even after the IESG is done
>>> reviewing it, statistics suggest it will still be littered with bugs
>>> like this and implementors will use the examples to guide them. If
>>> someone implements what is in the example, it will break in lots of
>>> sip deployments.
>>>
>>> There is a whole algorithm about matching various ID types, but the
>>> note about you ignore CN if you have other things is off in "Security=

>>> Warning" very much out of any flow of the algorithm description then
>>> pointed out again in some other section. It's not wrong, but it's a
>>> bit weird from an implementer point of view.
>>>
>>> Many applications do need to deal with IP matching as well as domain
>>> names. The way this text is written here makes it harder to figure
>>> out how and where to mix that in. I'd rather see it just dealt with
>>> than instead of making it out of scope. Obviously it's not common on
>>> internet but it is common on private networks and walled gardens
>>> where many of the protocols were are talking about are deployed. Many=

>>> of the "internet of things" people I work with have no intention of
>>> using DNS at all. I scoffed at multiple large service providers 10
>>> years ago when they said they were not using DNS with SIP but many
>>> still use IPs. This sounds less insane when you consider the major OS=

>>> don't ship with an asynchronous DNS library.
>>>
>>> I'm baffled on why checking the service name in a SRV record is a
>>> SHOULD not a MUST. Could you add text explain why and when one would
>>> not check it. If you were in a really good mood you could do that for=

>>> all the SHOULDs. Actually, when I read section 4.5 carefully, I think=

>>> it literally says that when using a URI, checking the domain name is
>>> a SHOULD not a MUST. Surely check the domain name matches is not a
>>> SHOULD level sort of thing.
>>>
>>> Section 5.4. I have no idea why it matters that some major OS does
>>> not support SNI. Even if that OS did support SNI, many many
>>> applications running on that OS and the others would not support SNI.=

>>> It seems like it is the applications acting as TLS servers and
>>> clients that are the important thing, not the OS.
>>>
>>> How you process URI-ID needs work. I could not figure out how to
>>> implement given the text in the draft as is. Even ignoring the
>>> special tar pit the SIP guys dug for themselves with tel URL
>>> processing, just the normal sip, sips issues seems unclear.
>>>
>>> This seems like a long list of complaints delivered fairly late but,
>>> once again, I really do like much of the information in here and
>>> think it should be published as PS - it just would be significantly
>>> improved with a bit of a re-factored and clean up. If this had been
>>> run through the TLS working group, I would have caught all of this in=

>>> the WG LC. This is a draft that, as a BCP,  profoundly effects many
>>> of the protocols I work on including SIP but as far as I can tell has=

>>> not done much to gather the consensus of the people working on
>>> protocol that this draft changes - I don't recall hearing about it
>>> until after it went to the IESG so I'm pretty un apologetic about
>>> providing these comments during IETF LC.
>>>
>>> In summary, I like the information in this but I think it still has
>>> many small things that need fixing and needs to be changed to get
>>> crisp about what implementors need to do and drop the confusing stuff=

>>> about how we wish operators and CA might use certificates. I also
>>> feel strongly that the right way to look at this draft is, as that
>>> draft says "practices described here can be referenced by future
>>> specifications, including updates to specifications for existing
>>> application protocols if the relevant technology communities agree to=

>>> do so" and that for that reason it has to be standards track not BCP.=

>>> If it was not being written and pushed by two IESG members, I don't
>>> think we would even be discussing if it should be a BCP.
>>>


--------------ms070509000902060800050103
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
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEw
NTE4MDUwOVowIwYJKoZIhvcNAQkEMRYEFL5lyBis3AiteY0AR3CWP99gQGKEMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQBlegfgmwP+IaLrJYtzBKnXi1GkE0x7Jm4K/BsYEkoOulgTZI37t4ySox1X
pxWpow6KzxMVsJs8V4zv3zXTkK1+32llW7IUFyrJTmYGO0SGtVyqesJb6EISFzN3ZiCeLwHv
/A2r2LNY5PJh/ZWwAFMBK8CZGJZ89NlQ+qu/PLZugknHRCDZkkqz5FR4xuVxv7u7OJb1N6cX
O0NncTbD/nuotDIYMS0DbAe0BWtfWyC2BXp1BdBJyv170jmvn0JUt44X5+GPJ/RbDO3mz43L
YtcYT6YAwk+IgAJSaKnojgZs/ZUs218zDUGj3wis8ba61nBOoQ3yG7JERS6hitz0Qn7YAAAA
AAAA
--------------ms070509000902060800050103--

From jari.arkko@piuha.net  Wed Jan  5 13:27:30 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 B386B3A6B8E; Wed,  5 Jan 2011 13:27:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oJ8oYNGEEpa; Wed,  5 Jan 2011 13:27:29 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 79D9B3A6B87; Wed,  5 Jan 2011 13:27:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E98CF2CC45; Wed,  5 Jan 2011 23:29: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 Q3r1HQWHVx3y; Wed,  5 Jan 2011 23:29:35 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 1950F2CC2F; Wed,  5 Jan 2011 23:29:34 +0200 (EET)
Message-ID: <4D24E2BE.6010207@piuha.net>
Date: Wed, 05 Jan 2011 22:29:34 +0100
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
Subject: time to act on IETF-80 BOFs
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: Wed, 05 Jan 2011 21:27:30 -0000

Just as a reminder, if any of you are thinking of proposing new IETF
work: the deadline for BOF proposals for the next meeting is January
31st. But if you have something in mind, please talk to your ADs as soon
as possible. More information at
http://www.ietf.org/meeting/cutoff-dates-2011.html#IETF80

Jari


From rbarnes@bbn.com  Wed Jan  5 13:54:36 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 193FF3A6BA8 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 13:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.479
X-Spam-Level: 
X-Spam-Status: No, score=-101.479 tagged_above=-999 required=5 tests=[AWL=-1.541, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_GIF_ATTACH=1.42, 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 PDPXXym9nVy4 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 13:54:34 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 5D1193A67D6 for <ietf@ietf.org>; Wed,  5 Jan 2011 13:54:34 -0800 (PST)
Received: from [192.1.255.181] (port=60164 helo=col-raltmann-l1.nira.bbn.com) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1PabLV-0001b8-2G for ietf@ietf.org; Wed, 05 Jan 2011 16:56:41 -0500
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-1-277304384
Subject: Fwd: FCC IPv6 Working Paper Released
Date: Wed, 5 Jan 2011 16:56:40 -0500
References: <90ADAFB59248FE4380AF87D28B231FEB53F5A4@P2PXMB02S1.fccnet.win.fcc.gov>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
Message-Id: <60EBF00D-95B0-474F-9FF3-73B6DD0F514A@bbn.com>
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: Wed, 05 Jan 2011 21:54:36 -0000

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

This seems like a document that might interest some on this list...

> From: "Robert Cannon" <Robert.Cannon@fcc.gov>
> Date: January 5, 2011 11:24:51 AM EST
> Subject: FCC IPv6 Working Paper Released
>=20
> Last week the FCC released a new working paper Potential Impacts on =
Communications =46rom IPv4 Exhaustion & IPv6 Transition.
> =20
> http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303870A1.pdf
> =20
> Abstract
> =20
> The Internet is in transition.  The original address space, IPv4, is =
nearly exhausted; the Internet is in the progress of migrating to the =
new IPv6 address space.=20
>=20
> The Internet Protocol version 4 (IPv4) developed in the late 1970s has =
the capacity for about 4 billion unique addresses.  It would have been =
hard to imagine in the 1970s that 4 billion addresses were not going to =
be enough.  But by the early 1990s, Internet engineers recognized that =
the supply of addresses was relatively limited compared to likely =
demand, and they set to work designing a successor to IPv4.  They =
developed a new Internet Protocol, IPv6, with a vastly increased address =
space: 340 trillion trillion trillion addresses.
>=20
> Broadband Internet access has become essential to the United States =
and the rest of the world. The exhaustion of IPv4 addresses and the =
transition to IPv6 could result in significant, but not insurmountable, =
problems for broadband Internet services.  In the short term, to permit =
the network to continue to grow, engineers have developed a series of =
kludges. These kludges include more efficient use of the IPv4 address =
resource, conservation, and the sharing of IPv4 addresses through the =
use of Network Address Translation (NAT).  While these provide partial =
mitigation for IPv4 exhaustion, they are not a long-term solution, =
increase network costs, and merely postpone some of the consequences of =
address exhaustion without solving the underlying problem. Some of these =
fixes break end-to-end connectivity, impairing innovation and hampering =
applications, degrading network performance, and resulting in an =
inferior version of the Internet.  These kludges require capital =
investment and ongoing operational costs by network service providers, =
diverting investment from other business objectives. Network operators =
will be confronted with increased costs to offer potentially inferior =
service.
>=20
> The short term solutions are necessary because there is not enough =
time to completely migrate the entire public Internet to "native IPv6" =
where end users can communicate entirely via IPv6.  Network protocol =
transitions require significant work and investment, and with the =
exhaustion of IPv4 addresses looming, there is insufficient time to =
complete the full IPv6 transition.
>=20
> But the short-term solutions are problematic. The "solution to the =
solution" is to complete the transition to a native IPv6 network.  A =
native IPv6 network will restore end-to-end connectivity with a vastly =
expanded address space, will improve network performance, and should =
decrease costs.  Completing the transition of the public Internet to =
IPv6 will take time.
> =20
> FCC Staff Working Papers are intended to stimulate discussion and =
critical comment within the FCC, as well as outside the agency, on =
issues that may affect communications policy.  The analyses and =
conclusions set forth are those of the authors and do not necessarily =
reflect the view of the FCC, other Commission staff members, or any =
Commissioner.
> =20
> Initial feedback on the paper has been positive. If you have any =
question, please feel free to contact me.
> =20
> Robert
> =20
> ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
> Robert Cannon
> Senior Counsel for Internet Law
> Office of Strategic Planning and Policy Analysis
> Federal Communications Commission
> 202 418 2421
> =20
> ** Non Public :: For Internal Use Only **=20
>=20
> =20


--Apple-Mail-1-277304384
Content-Type: multipart/related;
	type="text/html";
	boundary=Apple-Mail-2-277304384


--Apple-Mail-2-277304384
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; ">This =
seems like a document that might interest some on this =
list...<br><div><br><blockquote type=3D"cite"><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>From: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">"Robert Cannon" &lt;<a =
href=3D"mailto:Robert.Cannon@fcc.gov">Robert.Cannon@fcc.gov</a>&gt;<br></s=
pan></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">January 5, 2011 11:24:51 AM EST<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>FCC IPv6 Working =
Paper Released</b></span></div><br><o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"country-region">
<o:smarttagtype =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Chiller;
	panose-1:4 2 4 4 3 16 7 2 6 2;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:.5in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>



<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div class=3D"Section1"><p class=3D"MsoNormal"><font size=3D"4" =
face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial">Last week the FCC released a new working paper =
<i><span style=3D"font-style:italic">Potential Impacts on Communications =
=46rom IPv4 Exhaustion
&amp; IPv6 Transition</span></i>.<o:p></o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;
font-family:Arial"><a =
href=3D"http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303870A1.pdf=
">http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303870A1.pdf</a><o=
:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"4" =
face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal" align=3D"center" =
style=3D"margin-left:.5in;text-align:center"><b><font size=3D"5" =
face=3D"Times New Roman"><span =
style=3D"font-size:16.0pt;font-weight:bold">Abstract<o:p></o:p></span></fo=
nt></b></p><p class=3D"MsoNormal" align=3D"center" =
style=3D"margin-left:.5in;text-align:center"><b><u><font size=3D"3" =
face=3D"Times New Roman"><span =
style=3D"font-size:12.0pt;font-weight:bold"><o:p><span =
style=3D"text-decoration:none">&nbsp;</span></o:p></span></font></u></b></=
p><p class=3D"MsoBodyText" style=3D"margin-left:.5in"><font size=3D"3" =
face=3D"Times New Roman"><span style=3D"font-size:12.0pt">The Internet =
is in
transition.&nbsp; The original address space, IPv4, is nearly exhausted; =
the
Internet is in the progress of migrating to the new IPv6 address =
space.&nbsp; <o:p></o:p></span></font></p><p class=3D"MsoBodyText" =
style=3D"margin-left:.5in"><font size=3D"3" face=3D"Times New =
Roman"><span style=3D"font-size:12.0pt">The Internet Protocol
version 4 (IPv4) developed in the late 1970s has the capacity for about =
4
billion unique addresses.&nbsp; It would have been hard to imagine in =
the 1970s that
4 billion addresses were not going to be enough.&nbsp; But by the early =
1990s,
Internet engineers recognized that the supply of addresses was =
relatively
limited compared to likely demand, and they set to work designing a =
successor
to IPv4.&nbsp; They developed a new Internet Protocol, IPv6, with a =
vastly increased
address space: 340 trillion trillion trillion =
addresses.<o:p></o:p></span></font></p><p class=3D"MsoBodyText" =
style=3D"margin-left:.5in"><font size=3D"3" face=3D"Times New =
Roman"><span style=3D"font-size:12.0pt">Broadband Internet access
has become essential to the <st1:country-region w:st=3D"on"><st1:place =
w:st=3D"on">United
  States</st1:place></st1:country-region> and the rest of the world. The
exhaustion of IPv4 addresses and the transition to IPv6 could result in
significant, but not insurmountable, problems for broadband Internet =
services.&nbsp;
In the short term, to permit the network to continue to grow, engineers =
have
developed a series of kludges. These kludges include more efficient use =
of the
IPv4 address resource, conservation, and the sharing of IPv4 addresses =
through
the use of Network Address Translation (NAT).&nbsp; While these provide =
partial
mitigation for IPv4 exhaustion, they are not a long-term solution, =
increase
network costs, and merely postpone some of the consequences of address
exhaustion without solving the underlying problem. Some of these fixes =
break
end-to-end connectivity, impairing innovation and hampering =
applications,
degrading network performance, and resulting in an inferior version of =
the
Internet.&nbsp; These kludges require capital investment and ongoing =
operational
costs by network service providers, diverting investment from other =
business
objectives. Network operators will be confronted with increased costs to =
offer
potentially inferior service. <o:p></o:p></span></font></p><p =
class=3D"MsoBodyText" style=3D"margin-left:.5in"><font size=3D"3" =
face=3D"Times New Roman"><span style=3D"font-size:12.0pt">The short term =
solutions
are necessary because there is not enough time to completely migrate the =
entire
public Internet to "native IPv6" where end users can communicate
entirely via IPv6.&nbsp; Network protocol transitions require =
significant work and
investment, and with the exhaustion of IPv4 addresses looming, there is
insufficient time to complete the full IPv6 =
transition.<o:p></o:p></span></font></p><p class=3D"MsoNormal" =
style=3D"margin-left:.5in;text-indent:.5in"><font size=3D"3" face=3D"Times=
 New Roman"><span style=3D"font-size:12.0pt">But the short-term
solutions are problematic. The "solution to the solution" is to
complete the transition to a native IPv6 network.&nbsp; A native IPv6 =
network will
restore end-to-end connectivity with a vastly expanded address space, =
will
improve network performance, and should decrease costs.&nbsp; Completing =
the
transition of the public Internet to IPv6 will take =
time.</span></font><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;font-family:Arial"><o:p></o:p></span></font></p>=
<p class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;
font-family:Arial">FCC Staff Working Papers are intended to stimulate
discussion and critical comment within the FCC, as well as outside the =
agency,
on issues that may affect communications policy. &nbsp;The analyses and
conclusions set forth are those of the authors and do not necessarily =
reflect
the view of the FCC, other Commission staff members, or any =
Commissioner.<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;
font-family:Arial">Initial feedback on the paper has been positive. If =
you have
any question, please feel free to contact =
me.<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"4" =
face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span =
style=3D"font-size:14.0pt;
font-family:Arial">Robert</span></font><font size=3D"4" =
face=3D"Arial"><span =
style=3D"font-size:14.0pt;font-family:Arial"><o:p></o:p></span></font></p>=
<p class=3D"MsoNormal"><font size=3D"2" color=3D"gray" =
face=3D"Arial"><span style=3D"font-size:
=
10.0pt;font-family:Arial;color:gray"><o:p>&nbsp;</o:p></span></font></p><p=
 class=3D"MsoNormal"><font size=3D"2" color=3D"gray" face=3D"Arial"><span =
style=3D"font-size:
=
10.0pt;font-family:Arial;color:gray">~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~=
-~-~-~-~-~-~-</span></font><font color=3D"gray"><span =
style=3D"color:gray"><o:p></o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"2" color=3D"gray" face=3D"Calibri"><span=
 style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">Robert =
Cannon<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"2"=
 color=3D"gray" face=3D"Calibri"><span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">Senior Counsel for Internet =
Law<br>
Office of Strategic Planning and Policy =
Analysis<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"2" color=3D"gray" face=3D"Calibri"><span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">Federal Communications =
Commission<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"2" color=3D"gray" face=3D"Calibri"><span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">202 418 =
2421</span></font><o:p></o:p></p><p class=3D"MsoNormal"><font size=3D"3" =
face=3D"Times New Roman"><span style=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"3" color=3D"gray" face=3D"Chiller"><span style=3D"font-size:
12.0pt;font-family:Chiller;color:gray">** Non Public :: For Internal Use =
Only
**&nbsp;<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font =
size=3D"3" color=3D"gray" face=3D"Chiller"><span style=3D"font-size:
12.0pt;font-family:Chiller;color:gray"><img border=3D"0" width=3D"487" =
height=3D"36" id=3D"_x0000_i1025" apple-width=3D"yes" apple-height=3D"yes"=
 =
src=3D"cid:image001.gif@01CBACCB.2B753030"><o:p></o:p></span></font></p><p=
 class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span =
style=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>


</o:smarttagtype></o:smarttagtype></blockquote></div><br></body></html>=

--Apple-Mail-2-277304384
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename=image001.gif
Content-Type: image/gif;
	name="image001.gif"
Content-Id: <image001.gif@01CBACCB.2B753030>

R0lGODlh5wEkAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAX
AAAAC21zT1BNU09GRklDRTkuMEI8pPUALAAAAADnASQAhwCAAP///wECAwECAwAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAj/AAMIHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePAwEAAEmypMmTKFOqXMmy
pcuSIkW+nEmzps2bOHPqzBlz5M6fQIMKHUq0aMeeMo0qXcq0qdOnH5HGhEq1qtWrWIf2zMq1q9ev
YC1KTRq2rNmzaJ2OnUpQatq3cOPKNUn2YFK3AfDmbbu2oEyfbKcK/jtW4Fq2eZEmHtnXcF/Fh+sG
JjyZ8ePCjgcfzpz5ruLFlitrjkyZM+DLkMnqXczZcMjVc7X6ROg5MV/Xth3vvXubcG7ef3X7/m0b
OGPhlnHr3n169uniz2szX068dvDX0F0HH84dMPbk1r2D/8++97f4492L3y6PPbd78rFtbgUdef1w
4a+f41+P3PR739b1115/133nX4EARtfcdO5dJxh1343XYHLkFaheeg9SV5p+BqlG4X0G+sUhYiDG
N5OHpEk2n4rGtTffgBXupiF4zdUoIl+jiQjcdM6F1mN1MiIYmIzvdWYkaxWSiBiSL27HnodBQsjf
Z9LlN1tI6jEIn4kn1mXXZ1KqWN6L2V3534dImpfkmBRCmCB7+4WWZZkKarfdcXEyaSadbEYooIVQ
BqikgZOBNmB6bqLXoo0CctnlZjrytxya0cXooqV3EqgfjZK+CeeOavoZHm6Z/khklaKe5+eaT/4Y
4IQhSrQn5p+K2udXlpui6WhLKXbYI4q9ugWbkguWRp9oqTE6WpOXzbhVZaYNBl1hlF2ZLGZ6+kil
ZsdKa6iwv1rLbX1WilmtttjuqlKvN6rr7rvwXkVupPHWa++9QTX25Z749uvvv3SR6euSABds8MEI
J6zwwgw37PDDEEcs8cQUV2zxxRhnrPHGHHfs8ccghyzyyCSXbPLJKKes8sost+zyyzDHLPPMNNds
880456zzzjz37DPCAQEAOw==

--Apple-Mail-2-277304384--

--Apple-Mail-1-277304384--

From ynir@checkpoint.com  Wed Jan  5 15:13:27 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 875F93A6E29 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 15:13:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.847
X-Spam-Level: 
X-Spam-Status: No, score=-8.847 tagged_above=-999 required=5 tests=[AWL=-0.373, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 nOKQ0H3wpMh3 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 15:13:26 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id D811F3A6CD9 for <ietf@ietf.org>; Wed,  5 Jan 2011 15:13:24 -0800 (PST)
X-CheckPoint: {4D24FB92-2-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p05NFTa4026338 for <ietf@ietf.org>; Thu, 6 Jan 2011 01:15:30 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 6 Jan 2011 01:15:29 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
Date: Thu, 6 Jan 2011 01:15:27 +0200
Subject: Re: FCC IPv6 Working Paper Released
Thread-Topic: FCC IPv6 Working Paper Released
Thread-Index: AcutLnF4Ex+aULBORI+Vq1YaXIDcXw==
Message-ID: <8CC05F99-5896-4FDA-A8C4-F4F281C927DC@checkpoint.com>
References: <90ADAFB59248FE4380AF87D28B231FEB53F5A4@P2PXMB02S1.fccnet.win.fcc.gov> <60EBF00D-95B0-474F-9FF3-73B6DD0F514A@bbn.com>
In-Reply-To: <60EBF00D-95B0-474F-9FF3-73B6DD0F514A@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8CC05F9958964FDAA8C4F4F281C927DCcheckpointcom_"
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, 05 Jan 2011 23:13:27 -0000

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

Sigh.

You'd think they would have learned by now.

"A native IPv6 network will restore end-to-end connectivity with a vastly e=
xpanded address space..."

On Jan 5, 2011, at 11:56 PM, Richard L. Barnes wrote:

This seems like a document that might interest some on this list...

From: "Robert Cannon" <Robert.Cannon@fcc.gov<mailto:Robert.Cannon@fcc.gov>>
Date: January 5, 2011 11:24:51 AM EST
Subject: FCC IPv6 Working Paper Released

Last week the FCC released a new working paper Potential Impacts on Communi=
cations From IPv4 Exhaustion & IPv6 Transition.

http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303870A1.pdf

Abstract


The Internet is in transition.  The original address space, IPv4, is nearly=
 exhausted; the Internet is in the progress of migrating to the new IPv6 ad=
dress space.

The Internet Protocol version 4 (IPv4) developed in the late 1970s has the =
capacity for about 4 billion unique addresses.  It would have been hard to =
imagine in the 1970s that 4 billion addresses were not going to be enough. =
 But by the early 1990s, Internet engineers recognized that the supply of a=
ddresses was relatively limited compared to likely demand, and they set to =
work designing a successor to IPv4.  They developed a new Internet Protocol=
, IPv6, with a vastly increased address space: 340 trillion trillion trilli=
on addresses.

Broadband Internet access has become essential to the United States and the=
 rest of the world. The exhaustion of IPv4 addresses and the transition to =
IPv6 could result in significant, but not insurmountable, problems for broa=
dband Internet services.  In the short term, to permit the network to conti=
nue to grow, engineers have developed a series of kludges. These kludges in=
clude more efficient use of the IPv4 address resource, conservation, and th=
e sharing of IPv4 addresses through the use of Network Address Translation =
(NAT).  While these provide partial mitigation for IPv4 exhaustion, they ar=
e not a long-term solution, increase network costs, and merely postpone som=
e of the consequences of address exhaustion without solving the underlying =
problem. Some of these fixes break end-to-end connectivity, impairing innov=
ation and hampering applications, degrading network performance, and result=
ing in an inferior version of the Internet.  These kludges require capital =
investment and ongoing operational costs by network service providers, dive=
rting investment from other business objectives. Network operators will be =
confronted with increased costs to offer potentially inferior service.

The short term solutions are necessary because there is not enough time to =
completely migrate the entire public Internet to "native IPv6" where end us=
ers can communicate entirely via IPv6.  Network protocol transitions requir=
e significant work and investment, and with the exhaustion of IPv4 addresse=
s looming, there is insufficient time to complete the full IPv6 transition.
But the short-term solutions are problematic. The "solution to the solution=
" is to complete the transition to a native IPv6 network.  A native IPv6 ne=
twork will restore end-to-end connectivity with a vastly expanded address s=
pace, will improve network performance, and should decrease costs.  Complet=
ing the transition of the public Internet to IPv6 will take time.

FCC Staff Working Papers are intended to stimulate discussion and critical =
comment within the FCC, as well as outside the agency, on issues that may a=
ffect communications policy.  The analyses and conclusions set forth are th=
ose of the authors and do not necessarily reflect the view of the FCC, othe=
r Commission staff members, or any Commissioner.

Initial feedback on the paper has been positive. If you have any question, =
please feel free to contact me.

Robert

~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Robert Cannon
Senior Counsel for Internet Law
Office of Strategic Planning and Policy Analysis
Federal Communications Commission
202 418 2421

** Non Public :: For Internal Use Only **
<image001.gif>


<ATT00001..txt>


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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; ">Sigh.<div><br></div><div>Y=
ou'd think they would have learned by now.</div><div><br></div><div>"<span =
class=3D"Apple-style-span" style=3D"font-family: 'Times New Roman'; font-si=
ze: 12px; ">A native IPv6 network will restore end-to-end connectivity with=
 a vastly expanded address space..."</span></div><div><font class=3D"Apple-=
style-span" face=3D"'Times New Roman'"><br></font><div><div>On Jan 5, 2011,=
 at 11:56 PM, Richard L. Barnes wrote:</div><br class=3D"Apple-interchange-=
newline"><blockquote type=3D"cite"><div style=3D"word-wrap: break-word; -we=
bkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This seems =
like a document that might interest some on this list...<br><div><br><block=
quote type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; margi=
n-bottom: 0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; f=
ont-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span style=
=3D"font-family:'Helvetica'; font-size:medium;">"Robert Cannon" &lt;<a href=
=3D"mailto:Robert.Cannon@fcc.gov">Robert.Cannon@fcc.gov</a>&gt;<br></span><=
/div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; font-size:medium=
; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span style=3D"font-family:'=
Helvetica'; font-size:medium;">January 5, 2011 11:24:51 AM EST<br></span></=
div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; m=
argin-left: 0px;"><span style=3D"font-family:'Helvetica'; font-size:medium;=
 color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span style=3D"font-family=
:'Helvetica'; font-size:medium;"><b>FCC IPv6 Working Paper Released</b></sp=
an></div><br><o:smarttagtype namespaceuri=3D"urn:schemas-microsoft-com:offi=
ce:smarttags" name=3D"country-region">
<o:smarttagtype namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"=
 name=3D"place">
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Chiller;
	panose-1:4 2 4 4 3 16 7 2 6 2;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:12.0pt;
	margin-left:0in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:.5in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>



<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div class=3D"Section1"><p class=3D"MsoNormal"><font size=3D"4" face=3D"Ari=
al"><span style=3D"font-size:14.0pt;
font-family:Arial">Last week the FCC released a new working paper <i><span =
style=3D"font-style:italic">Potential Impacts on Communications From IPv4 E=
xhaustion
&amp; IPv6 Transition</span></i>.<o:p></o:p></span></font></p><p class=3D"M=
soNormal"><font size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal=
"><font size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><a href=3D"http://hraunfoss.fcc.gov/edocs_public/attachm=
atch/DOC-303870A1.pdf">http://hraunfoss.fcc.gov/edocs_public/attachmatch/DO=
C-303870A1.pdf</a><o:p></o:p></span></font></p><p class=3D"MsoNormal"><font=
 size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal=
" align=3D"center" style=3D"margin-left:.5in;text-align:center"><b><font si=
ze=3D"5" face=3D"Times New Roman"><span style=3D"font-size:16.0pt;font-weig=
ht:bold">Abstract<o:p></o:p></span></font></b></p><p class=3D"MsoNormal" al=
ign=3D"center" style=3D"margin-left:.5in;text-align:center"><b><u><font siz=
e=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt;font-weigh=
t:bold"><o:p><span style=3D"text-decoration:none">&nbsp;</span></o:p></span=
></font></u></b></p><p class=3D"MsoBodyText" style=3D"margin-left:.5in"><fo=
nt size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">The=
 Internet is in
transition.&nbsp; The original address space, IPv4, is nearly exhausted; th=
e
Internet is in the progress of migrating to the new IPv6 address space.&nbs=
p; <o:p></o:p></span></font></p><p class=3D"MsoBodyText" style=3D"margin-le=
ft:.5in"><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size=
:12.0pt">The Internet Protocol
version 4 (IPv4) developed in the late 1970s has the capacity for about 4
billion unique addresses.&nbsp; It would have been hard to imagine in the 1=
970s that
4 billion addresses were not going to be enough.&nbsp; But by the early 199=
0s,
Internet engineers recognized that the supply of addresses was relatively
limited compared to likely demand, and they set to work designing a success=
or
to IPv4.&nbsp; They developed a new Internet Protocol, IPv6, with a vastly =
increased
address space: 340 trillion trillion trillion addresses.<o:p></o:p></span><=
/font></p><p class=3D"MsoBodyText" style=3D"margin-left:.5in"><font size=3D=
"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt">Broadband Int=
ernet access
has become essential to the <st1:country-region w:st=3D"on"><st1:place w:st=
=3D"on">United
  States</st1:place></st1:country-region> and the rest of the world. The
exhaustion of IPv4 addresses and the transition to IPv6 could result in
significant, but not insurmountable, problems for broadband Internet servic=
es.&nbsp;
In the short term, to permit the network to continue to grow, engineers hav=
e
developed a series of kludges. These kludges include more efficient use of =
the
IPv4 address resource, conservation, and the sharing of IPv4 addresses thro=
ugh
the use of Network Address Translation (NAT).&nbsp; While these provide par=
tial
mitigation for IPv4 exhaustion, they are not a long-term solution, increase
network costs, and merely postpone some of the consequences of address
exhaustion without solving the underlying problem. Some of these fixes brea=
k
end-to-end connectivity, impairing innovation and hampering applications,
degrading network performance, and resulting in an inferior version of the
Internet.&nbsp; These kludges require capital investment and ongoing operat=
ional
costs by network service providers, diverting investment from other busines=
s
objectives. Network operators will be confronted with increased costs to of=
fer
potentially inferior service. <o:p></o:p></span></font></p><p class=3D"MsoB=
odyText" style=3D"margin-left:.5in"><font size=3D"3" face=3D"Times New Roma=
n"><span style=3D"font-size:12.0pt">The short term solutions
are necessary because there is not enough time to completely migrate the en=
tire
public Internet to "native IPv6" where end users can communicate
entirely via IPv6.&nbsp; Network protocol transitions require significant w=
ork and
investment, and with the exhaustion of IPv4 addresses looming, there is
insufficient time to complete the full IPv6 transition.<o:p></o:p></span></=
font></p><p class=3D"MsoNormal" style=3D"margin-left:.5in;text-indent:.5in"=
><font size=3D"3" face=3D"Times New Roman"><span style=3D"font-size:12.0pt"=
>But the short-term
solutions are problematic. The "solution to the solution" is to
complete the transition to a native IPv6 network.&nbsp; A native IPv6 netwo=
rk will
restore end-to-end connectivity with a vastly expanded address space, will
improve network performance, and should decrease costs.&nbsp; Completing th=
e
transition of the public Internet to IPv6 will take time.</span></font><fon=
t size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;font-family:Ari=
al"><o:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"4" fa=
ce=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal=
"><font size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial">FCC Staff Working Papers are intended to stimulate
discussion and critical comment within the FCC, as well as outside the agen=
cy,
on issues that may affect communications policy. &nbsp;The analyses and
conclusions set forth are those of the authors and do not necessarily refle=
ct
the view of the FCC, other Commission staff members, or any Commissioner.<o=
:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"4" face=3D"=
Arial"><span style=3D"font-size:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal=
"><font size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial">Initial feedback on the paper has been positive. If you =
have
any question, please feel free to contact me.<o:p></o:p></span></font></p><=
p class=3D"MsoNormal"><font size=3D"4" face=3D"Arial"><span style=3D"font-s=
ize:14.0pt;
font-family:Arial"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal=
"><font size=3D"4" face=3D"Arial"><span style=3D"font-size:14.0pt;
font-family:Arial">Robert</span></font><font size=3D"4" face=3D"Arial"><spa=
n style=3D"font-size:14.0pt;font-family:Arial"><o:p></o:p></span></font></p=
><p class=3D"MsoNormal"><font size=3D"2" color=3D"gray" face=3D"Arial"><spa=
n style=3D"font-size:
10.0pt;font-family:Arial;color:gray"><o:p>&nbsp;</o:p></span></font></p><p =
class=3D"MsoNormal"><font size=3D"2" color=3D"gray" face=3D"Arial"><span st=
yle=3D"font-size:
10.0pt;font-family:Arial;color:gray">~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-=
~-~-~-~-~-~-</span></font><font color=3D"gray"><span style=3D"color:gray"><=
o:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"2" color=
=3D"gray" face=3D"Calibri"><span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">Robert Cannon<o:p></o:p></span></fon=
t></p><p class=3D"MsoNormal"><font size=3D"2" color=3D"gray" face=3D"Calibr=
i"><span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">Senior Counsel for Internet Law<br>
Office of Strategic Planning and Policy Analysis<o:p></o:p></span></font></=
p><p class=3D"MsoNormal"><font size=3D"2" color=3D"gray" face=3D"Calibri"><=
span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">Federal Communications Commission<o:=
p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"2" color=3D"=
gray" face=3D"Calibri"><span style=3D"font-size:
10.0pt;font-family:Calibri;color:gray">202 418 2421</span></font><o:p></o:p=
></p><p class=3D"MsoNormal"><font size=3D"3" face=3D"Times New Roman"><span=
 style=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p><p class=3D"MsoNormal"><font siz=
e=3D"3" color=3D"gray" face=3D"Chiller"><span style=3D"font-size:
12.0pt;font-family:Chiller;color:gray">** Non Public :: For Internal Use On=
ly
**&nbsp;<o:p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"3=
" color=3D"gray" face=3D"Chiller"><span style=3D"font-size:
12.0pt;font-family:Chiller;color:gray"><span>&lt;image001.gif&gt;</span><o:=
p></o:p></span></font></p><p class=3D"MsoNormal"><font size=3D"3" face=3D"T=
imes New Roman"><span style=3D"font-size:
12.0pt"><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>


</o:smarttagtype></o:smarttagtype></blockquote></div><br></div><span>&lt;AT=
T00001..txt&gt;</span></blockquote></div><br></div></body></html>=

--_000_8CC05F9958964FDAA8C4F4F281C927DCcheckpointcom_--

From johnl@iecc.com  Wed Jan  5 15:21:10 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 34DE83A6DD4 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 15:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.677
X-Spam-Level: 
X-Spam-Status: No, score=-110.677 tagged_above=-999 required=5 tests=[AWL=0.522, 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 mOS4uP2TLb-i for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 15:21:08 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id CDFD03A6CD9 for <ietf@ietf.org>; Wed,  5 Jan 2011 15:21:07 -0800 (PST)
Received: (qmail 27767 invoked from network); 5 Jan 2011 23:23:14 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 5 Jan 2011 23:23:14 -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=8215.4d24fd62.k1101; i=johnl@user.iecc.com; bh=Tfanz81gviTLG4plKlNRtkUCBYGPTZbsfGsiF3VCmVM=; b=qE/tcFqyLAtSuspATxMlMBd/NHUd+Z8cD9L1TcaHYN0pivxq9QpvU8bQWbinHr/feSCwy4dE5QAhjdGZv0zQBgT1KGZk/+87qpNn3/YBGRipTjmWiLgtrZjSozURmD9HbHXI8aCiqWrm/ZIUofmnjrFu6/LwCxtc2olP0HllJ90=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Jan 2011 23:23:14 -0000
Message-ID: <20110105232314.33300.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Fwd: FCC IPv6 Working Paper Released
In-Reply-To: <60EBF00D-95B0-474F-9FF3-73B6DD0F514A@bbn.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: Wed, 05 Jan 2011 23:21:10 -0000

>This seems like a document that might interest some on this list...

It's not bad, but it's basically a well written summary of the
conventional wisdom about IPv6.  As we all know, some of the
conventional wisdom is more grounded in reality, some less.

>> Last week the FCC released a new working paper Potential Impacts on Communications From IPv4 Exhaustion & IPv6 Transition.
>>  
>> http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-303870A1.pdf

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From mohta@necom830.hpcl.titech.ac.jp  Wed Jan  5 15:41: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 01C223A6E23 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 15:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.204
X-Spam-Level: *
X-Spam-Status: No, score=1.204 tagged_above=-999 required=5 tests=[AWL=0.694,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_74=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 qunTeJsrSV9o for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 15:41: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 827033A6D0E for <ietf@ietf.org>; Wed,  5 Jan 2011 15:41:07 -0800 (PST)
Received: (qmail 84123 invoked from network); 6 Jan 2011 00:31:50 -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; 6 Jan 2011 00:31:50 -0000
Message-ID: <4D2501C5.9090801@necom830.hpcl.titech.ac.jp>
Date: Thu, 06 Jan 2011 08:41:57 +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: FCC IPv6 Working Paper Released
References: <90ADAFB59248FE4380AF87D28B231FEB53F5A4@P2PXMB02S1.fccnet.win.fcc.gov>	<60EBF00D-95B0-474F-9FF3-73B6DD0F514A@bbn.com> <8CC05F99-5896-4FDA-A8C4-F4F281C927DC@checkpoint.com>
In-Reply-To: <8CC05F99-5896-4FDA-A8C4-F4F281C927DC@checkpoint.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, 05 Jan 2011 23:41:09 -0000

Yoav Nir wrote:

> You'd think they would have learned by now.
> 
> "A native IPv6 network will restore end-to-end connectivity
> with a vastly expanded address space..."

That's true but the problem is that the end to end connectivity
is utterly lost during the transition from IPv4 to IPv6 network
(dual stacking was abandoned).

On the other hand, IPv4 address space extended by PR-IP (port
restricted IP such as Address+Port, end to end NAT and port
enhanced ARP) is large enough and the end to end connectivity
is always kept.

						Masataka Ohta

From adam@nostrum.com  Wed Jan  5 16:56:38 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 1BE653A6E44 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 16:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.068, 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 zZkb5d2Fy7Ls for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 16:56:35 -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 C59553A6DD2 for <ietf@ietf.org>; Wed,  5 Jan 2011 16:56:34 -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 p060wenS081392 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 5 Jan 2011 18:58:40 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <4D2513C0.6050400@nostrum.com>
Date: Wed, 05 Jan 2011 18:58:40 -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: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: Question about Prague
References: <CBD2BFC0-4954-4B55-8534-8B9E9F1A1D7E@checkpoint.com> <5D41E230-D3BC-45BF-B228-AB28359954DE@isoc.org>
In-Reply-To: <5D41E230-D3BC-45BF-B228-AB28359954DE@isoc.org>
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: "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, 06 Jan 2011 00:56:38 -0000

On 12/30/10 6:15 AM, Ray Pelletier wrote:
>
> Registration will open the beginning of next week with the usual hotel details, etc.
>
> Ray

Wow. Less than a week, and the special rate for the block is already 
unavailable. I've reserved a room at 5600 CZK per night (about $300US), 
but I don't think I can keep that reservation (I'd have a hard time 
getting it reimbursed).

Is something completely botched in Hilton's system, or is the block 
actually sold out already? If it's the latter, is the secretariat 
working to expand the block?

/a

From johnl@iecc.com  Wed Jan  5 17:10:39 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 11AFA3A6E2C for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 17:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.688
X-Spam-Level: 
X-Spam-Status: No, score=-110.688 tagged_above=-999 required=5 tests=[AWL=0.511, 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 w1YYqtrS6ui0 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 17:10:37 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 097453A6DDA for <ietf@ietf.org>; Wed,  5 Jan 2011 17:10:36 -0800 (PST)
Received: (qmail 44837 invoked from network); 6 Jan 2011 01:12:43 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 6 Jan 2011 01:12:43 -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=ee36.4d25170b.k1101; i=johnl@user.iecc.com; bh=6ziJ5twmnj7XlFnkaVM1i0ROdcNRSBl4/M6RPzOJAfI=; b=JSGOSJyVBf8l1T2kxvoJeGswXtYITlEXwcxAAqqmsXQ4Y+DmdVo1ncBehpiNhiLYuf8kheGJJN6ler1KeREhOGTPbS6ASA4XzIz0ldNEKuScZyYhJu3TX6TcZv1C961uq0faPDjZtMsAssttqFzkUueCszljpuv54lDrISa5HjE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 6 Jan 2011 01:12:43 -0000
Message-ID: <20110106011243.60981.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Question about Prague
In-Reply-To: <4D2513C0.6050400@nostrum.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: Thu, 06 Jan 2011 01:10:39 -0000

>Wow. Less than a week, and the special rate for the block is already 
>unavailable. I've reserved a room at 5600 CZK per night (about $300US), 
>but I don't think I can keep that reservation (I'd have a hard time 
>getting it reimbursed).

I just followed the link from the IETF web site and it offered
me a room at the 3700 conference rate.

R's,
John

From jnc@mercury.lcs.mit.edu  Wed Jan  5 17:46:30 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 B90C33A6E4B for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 17:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.49
X-Spam-Level: 
X-Spam-Status: No, score=-6.49 tagged_above=-999 required=5 tests=[AWL=0.109,  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 QCgny0Z3rPvL for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 17:46:29 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by core3.amsl.com (Postfix) with ESMTP id D60993A6BB4 for <ietf@ietf.org>; Wed,  5 Jan 2011 17:46:29 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id DE0C16BE59F; Wed,  5 Jan 2011 20:48:35 -0500 (EST)
To: ietf@ietf.org, ynir@checkpoint.com
Subject: Re: FCC IPv6 Working Paper Released
Message-Id: <20110106014835.DE0C16BE59F@mercury.lcs.mit.edu>
Date: Wed,  5 Jan 2011 20:48:35 -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, 06 Jan 2011 01:46:31 -0000

    > From: Yoav Nir <ynir@checkpoint.com>

    > Sigh.
    > You'd think they would have learned by now.

"Experience is a dear master, but fools will learn at no other."

 -- Benjamin Franklin, 'Poor Richard's Almanac'

	Noel

From jsalowey@cisco.com  Wed Jan  5 21:02:25 2011
Return-Path: <jsalowey@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 3E5D93A6B4F for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 21:02:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 9rD06FUEYtdx for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 21:02:23 -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 D54C33A68DA for <ietf@ietf.org>; Wed,  5 Jan 2011 21:02:23 -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: AvsEAA/cJE2rR7Hu/2dsb2JhbACkHnOmBpg2gnQggjgEhGeGIoMd
X-IronPort-AV: E=Sophos;i="4.60,281,1291593600"; d="scan'208";a="241185440"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 06 Jan 2011 05:04:30 +0000
Received: from [10.33.249.181] ([10.33.249.181]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0654Rhn022826; Thu, 6 Jan 2011 05:04:28 GMT
Subject: Re: Review of draft-zorn-radius-keywrap
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Joe Salowey <jsalowey@cisco.com>
In-Reply-To: <BLU152-ds13BCD67AB7B04DAECDB74693140@phx.gbl>
Date: Wed, 5 Jan 2011 21:05:09 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C3CE48A-DC53-422B-844F-2EA89EE40A3A@cisco.com>
References: <BLU152-ds13BCD67AB7B04DAECDB74693140@phx.gbl>
To: Bernard Aboba <bernard_aboba@hotmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "'Romascanu, Dan \(Dan\)'" <dromasca@avaya.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, 06 Jan 2011 05:02:25 -0000

Hi Bernard,

Thank for the review. Comments in line below:


On Dec 15, 2010, at 12:14 PM, Bernard Aboba wrote:

> There are two major issues remaining in this document.
>=20
> One issue is that in a number of places, the document appears to=20
> contradict IETF standards track documents.=20
>=20
> Examples:
>=20
> Section 3.1
>=20
>       If the client requires the use of the Keying-Material Attribute
>       for keying material delivery and it is not present in the =
Access-
>       Accept or Access-Challenge message, the client MAY ignore the
>       message in question and end the user session.
>=20
> [BA] Presumbly the MAY is included here for security reasons, such as =
preventing
> the client from accepting a downlevel key from a server from which it =
has
> previously received keying material described in this document, thus =
preventing
> spoofing in the event that the RADIUS shared secret (or MD5) is =
compromised.
> However, in such a situation the key material itself would be =
compromised,
> so that some sort of warning should probably be raised.=20
>=20

[Joe]  How about the following:

"In environments where the the Keying-Material attribute is known to be =
supported or in cases where the client wants to avoid roll-back attacks =
the client MAY be configured to require the use of the Keying-Material =
Attribute.  If the client requires the use of the Keying-Material =
Attribute for keying material delivery and it is not present in the =
Access-Accept or Access-Challenge message, the client MAY ignore the =
message in question and end the user session."

> My recommendation is that this be rewritten to state the =
considerations=20
> underlying the MAY, as well as recommended behavior in line with RFC =
2865
> Section 5.26, which states:
>=20
>       Clients which do not receive desired vendor-specific information
>       SHOULD make an attempt to operate without it, although they may =
do
>       so (and report they are doing so) in a degraded mode.
>=20
> RFC 2865 is written this way to prevent the creation of proprietary =
RADIUS
> implementations that require the presence of vendor-specific =
information.=20
>=20
> Section 3.3
>=20
>       Any packet that contains an instance of the Message-
>       Authentication-Code Attribute SHOULD NOT contain an instance of
>       the Message-Authenticator Attribute [RFC3579].
>=20
> [BA] Since the Message-Authenticator Attribute is mandated by RFC =
3579,
> this represents a contradiction.  My recommendation would be to remove
> this sentence, and require that the key used in computing the=20
> Message-Authentication-Code be cryptographically independent of the
> RADIUS shared secret.  That way both attributes can be included =
without
> damage.
>=20

[Joe] I think we can remove the sentence.  The section states that if =
both are present the Message-Authenticaiton-Code attribute is computed =
first, but there may be ambiguity as to whether the =
message-authenticator attribute is included in the calculation or not.   =
 I would think it would be, I'd like to try to get some verification =
from implementers on this. =20

> Section 5
>=20
>    It is RECOMMENDED in this memo that two new keys, a key encrypting
>    key and a message authentication key, be shared by the RADIUS =
client
>    and server.  If implemented, these two keys MUST be different from
>    each other and SHOULD NOT be based on a password.  These two keys
>    SHOULD be cryptographically independent of the RADIUS shared secret
>    used in calculating the Response Authenticator [RFC2865], Request
>    Authenticator [RFC2866] [RFC5176] and Message-Authenticator =
Attribute
>    [RFC3579]; otherwise if the shared secret is broken, all is lost.
>=20
> [BA] I believe that cryptgraphic independence of the RADIUS shared =
secret
> needs to be a MUST, since the goal of this document is to provide =
security
> even in a situation where the RADIUS shared secret could be =
compromised.=20
>=20

[Joe] I think we can make the cryptographic separation from the RADIUS =
shared secret a MUST.=20

> Another issue is that there are a number of fields for which "the =
content=20
> of this field is outside the scope of this document." The document
> needs to provide enough information on these fields to enable
> interoperability.  Currently it is not clear if this is the case.=20
>=20
> Fields which are not adequately explained include the following:
>=20
> Section 3.1 Keying-Material
>=20
>       KEK ID
>=20
>          The KEK ID field is 16 octets in length and contains an
>          identifier for the KEK.  The KEK ID MUST refer to an =
encryption
>          key of a type and length appropriate for use with the =
algorithm
>          specified by the Enc Type field (see above).  This key is =
used
>          to protect the contents of the Data field (below).  Further
>          specification of the content of this field is outside the =
scope
>          of this document.
>=20

[Joe]  Replace first sentence with:

"The KEK ID field is 16 octets in length.  The combination of the KEK ID =
and the client and server IP addresses together uniquely identify a key =
shared between the RADIUS client and server.  As a result, the KEK ID =
need not be globally unique."

Replace last sentence with:

"The KEK ID is a constant that is configured through an out-of-band =
mechanism.  The same value is configured on both the RADIUS client and =
server.  If no KEK ID is configured then the field is set to 0.  If  =
only a single KEK is configured for use between a given RADIUS client =
and server, then 0 can be used as the default value.=20

>       KM ID
>=20
>          The KM ID field is 16 octets in length and contains an
>          identifier for the contents of the Data field.  The KM ID MAY
>          be used by communicating parties to identify the material =
being
>          transmitted.  The combination of App ID and KM ID MUST =
uniquely
>          identify the keying material between the parties utilizing =
it.
>          The KM ID is assumed to be known to the parties that derived
>          the keying material.  If the KM ID is not used it is set to =
0.
>          Further specification of the content of this field is outside
>          the scope of this document.
>=20

[Joe] Remove "further specification... " and replace with:

"The KM ID for the EAP-MSK application is set to 0.   Another =
application can be defined in the future which uses the KM ID field. "


> Section 3.3  Message-Authentication-Code
>=20
>       MAC Key ID
>=20
>          The MAC Key ID field is 16 octets in length and contains an
>          identifier for the key.  The MAC Key ID MUST refer to a key =
of
>          a type and length appropriate for use with the algorithm
>          specified by the MAC Type field (see above).  Further
>          specification of the content of this field is outside the =
scope
>          of this document.
>=20

[Joe]  Replace first sentence with:

"The MAC Key ID field is 16 octets in length.  The combination of the =
MAC Key ID and the client and server IP addresses together uniquely =
identify a key shared between the RADIUS client and server.  As a =
result, the MAC Key ID need not be globally unique."

Replace last sentence with:

"The MAC Key ID is a constant that is configured through an out-of-band =
mechanism.  The same value is configured on both the RADIUS client and =
server.  If no MAC Key ID is configured, then the field is set to 0.  If =
 only a single MAC Key ID is configured for use between a given RADIUS =
client and server, then 0 can be used as the default value.=20

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


From evnikita2@gmail.com  Wed Jan  5 21:42:20 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 44FE53A6ED7 for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 21:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.195
X-Spam-Level: 
X-Spam-Status: No, score=-2.195 tagged_above=-999 required=5 tests=[AWL=-0.557, 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 h1sVD1Q-NaRG for <ietf@core3.amsl.com>; Wed,  5 Jan 2011 21:42: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 03A513A6ED3 for <ietf@ietf.org>; Wed,  5 Jan 2011 21:42:18 -0800 (PST)
Received: by bwz12 with SMTP id 12so16028912bwz.31 for <ietf@ietf.org>; Wed, 05 Jan 2011 21:44:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:content-type; bh=s0JrQ5JcklPrgYQNYz7G7w8SnyUWgDA8PnMmfv9vok8=; b=vhbY6duXq0IhQ25OD4QzSFA+zc/yUWsCTyZlGxMgAtmYZoeMGy3EGOMYLD2FuNLFsB cHtd9kDz5yR6N3Nufy1qXRHFawP+ryVM+Od4gtCFHRwJKY4PdkoevwGXV+uJr08jlywp 6/75ZvgV6GeRKC8EqTulSuYlb4duxdkJ2bDv4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type; b=L9UCzKt//bLCHmRU1hMXk3kmP1/njro+Fb7sXKSUF+5U9YK74yMklZE2OjfCfQSDlT 6RbrK0eIsAzTQju3ju7+IsAak427SGuU67c9tO1gJM1tHYfjxcIBkWA8Zqqk5gLTu08k RSQ8QkYtqMCg6O/wHt6aL7Ae+68QpfdwvGjJ8=
Received: by 10.204.98.201 with SMTP id r9mr6751097bkn.37.1294292664535; Wed, 05 Jan 2011 21:44:24 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id p22sm13339246bkp.21.2011.01.05.21.44.23 (version=SSLv3 cipher=RC4-MD5); Wed, 05 Jan 2011 21:44:23 -0800 (PST)
Message-ID: <4D2556C9.9020901@gmail.com>
Date: Thu, 06 Jan 2011 07:44:41 +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>
Subject: Old transport-layer protocols to Historic?
Content-Type: multipart/alternative; boundary="------------000601000407040208030701"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: tsvwg@ietf.org, IETF Discussion <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: Thu, 06 Jan 2011 05:42:20 -0000

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

Hello all,

There have been a discussion on tsvwg mailing list about old transport 
layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT 
(RFC998). Initially there have been proposed to define IANA 
considerations for them. But after a discussion it was found out that it 
would be better to move them to Historic. I am writing to request more 
wider discussion on this topic.

There is quite strong consensus that IRTP should be Historic. There is a 
registered draft on this topic:

https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/

But as for others it should be discussed. Moreover, maybe anyone knows 
some other old transport-layer protocols that are no longer in use?

Please copy tour answer to tsvwg@ietf.org

All the best,
Mykyta Yevstifeyev

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

<!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 all,<br>
        <br>
        There have been a discussion on tsvwg mailing list about old
        transport layer protocols - exactly IRTP (RFC938), RDP
        (RFC908,1151) and NETBLT (RFC998). Initially there have been
        proposed to define IANA considerations for them. But after a
        discussion it was found out that it would be better to move them
        to Historic. I am writing to request more wider discussion on
        this topic. <br>
        <br>
        There is quite strong consensus that IRTP should be Historic.
        There is a registered draft on this topic:<br>
        <br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/">https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/</a><br>
        <br>
        But as for others it should be discussed. Moreover, maybe anyone
        knows some other old transport-layer protocols that are no
        longer in use?<br>
        <br>
        Please copy tour answer to <a class="moz-txt-link-abbreviated" href="mailto:tsvwg@ietf.org">tsvwg@ietf.org</a> <br>
        <br>
        All the best,<br>
        Mykyta Yevstifeyev<br>
      </big></font>
  </body>
</html>

--------------000601000407040208030701--

From vesely@tana.it  Thu Jan  6 01:24:27 2011
Return-Path: <vesely@tana.it>
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 534C53A6C19 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 01:24:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 r0cqBDMGqmrs for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 01:24:23 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 165E73A6C33 for <ietf@ietf.org>; Thu,  6 Jan 2011 01:24:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1294305984; bh=syuH9fd+0bcguCJ9hTmvBq+7Qt/KFAq0DYG558SkEuM=; l=1625; h=Message-ID:Date:From:MIME-Version:To:Content-Transfer-Encoding; b=N0RPL7sQAgn5/AUbZwWfZ1NAmAIJxBvlJvhncFJohdCXhBlispO7cMCtDZendJDHW JIGrH4OZLJnsulf7Z9GLPBpODMvHkiinvjSpUMd9nyiH+CEAFdF5yKRVxwNCujygZK /NvC8dJGa21n9+TwINqwzOAx55Qr5IEIgWnCLKSI=
Received: from [109.115.137.61] ([109.115.137.61]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Thu, 06 Jan 2011 10:26:23 +0100 id 00000000005DC039.000000004D258AC0.00001BD0
Message-ID: <4D258AB3.9010903@tana.it>
Date: Thu, 06 Jan 2011 10:26:11 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Poster sessions
Content-Type: text/plain; charset=ISO-8859-1
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, 06 Jan 2011 09:24:27 -0000

I've never attended an IETF meeting.  Why?  Because it seems to me quite
unlikely to have a chance to say something useful by going there.  I mean
useful with respect to a problem that I consider important.  That is, not
just a minimal contribution to an already scheduled session that I may happen
to attend.  Perhaps, I should request a session...

Problems are often expressed in the form of tentative solutions.  Such
solutions may occasionally happen to be discussed, refined, and agreed upon
by a group of individuals.  Implementation, standardization, and adoption may
eventually follow  --not necessarily in this order.  Isn't this how the IRTF
and the IETF should work?

A poster session would be a sort of plenary, lasting a couple of hours or so,
with posters hanged on numbered hardboard panels arranged along a walkway.  A
poster may be sized A0, or ~50 in, or consist of an equivalent number of
smaller sheets.  Posters may stay exposed for a few hours before/after the
scheduled time period.  During the session time, however, authors should
stand beside their posters and thus have their chance to talk to any
interested ietfers, one by one or in small knots, informally.  A few dozens
of posters per session may provide for adequate gathering.

IME, this way of participating is easier and less binding for both authors
and attendees.  A poster would suit subjects for which it's difficult to
carve a niche within a hosting WG's session, but it may also work as a means
to achieve consensus on a given topic before raising it in a more official
discussion.

Opinions/suggestions?

From ynir@checkpoint.com  Thu Jan  6 02:14: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 3A6E63A6D14 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 02:14:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.901
X-Spam-Level: 
X-Spam-Status: No, score=-9.901 tagged_above=-999 required=5 tests=[AWL=0.698,  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 wT1sVCE32tev for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 02:14:15 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 81E113A6CC8 for <ietf@ietf.org>; Thu,  6 Jan 2011 02:14:14 -0800 (PST)
X-CheckPoint: {4D259674-1-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p06AGJaj010594;  Thu, 6 Jan 2011 12:16:19 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 6 Jan 2011 12:16:19 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Alessandro Vesely <vesely@tana.it>
Date: Thu, 6 Jan 2011 12:16:16 +0200
Subject: Re: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: AcutisKdivyS/x7MRrmXvt90zuVoTw==
Message-ID: <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
References: <4D258AB3.9010903@tana.it>
In-Reply-To: <4D258AB3.9010903@tana.it>
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 Discussion <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, 06 Jan 2011 10:14:16 -0000

On Jan 6, 2011, at 11:26 AM, Alessandro Vesely wrote:

> I've never attended an IETF meeting.  Why?  Because it seems to me quite
> unlikely to have a chance to say something useful by going there.  I mean
> useful with respect to a problem that I consider important.  That is, not
> just a minimal contribution to an already scheduled session that I may ha=
ppen
> to attend.  Perhaps, I should request a session...
>=20
> Problems are often expressed in the form of tentative solutions.  Such
> solutions may occasionally happen to be discussed, refined, and agreed up=
on
> by a group of individuals.  Implementation, standardization, and adoption=
 may
> eventually follow  --not necessarily in this order.  Isn't this how the I=
RTF
> and the IETF should work?
>=20
> A poster session would be a sort of plenary, lasting a couple of hours or=
 so,
> with posters hanged on numbered hardboard panels arranged along a walkway=
.  A
> poster may be sized A0, or ~50 in, or consist of an equivalent number of
> smaller sheets.  Posters may stay exposed for a few hours before/after th=
e
> scheduled time period.  During the session time, however, authors should
> stand beside their posters and thus have their chance to talk to any
> interested ietfers, one by one or in small knots, informally.  A few doze=
ns
> of posters per session may provide for adequate gathering.
>=20
> IME, this way of participating is easier and less binding for both author=
s
> and attendees.  A poster would suit subjects for which it's difficult to
> carve a niche within a hosting WG's session, but it may also work as a me=
ans
> to achieve consensus on a given topic before raising it in a more officia=
l
> discussion.
>=20
> Opinions/suggestions?

Hi Alessandro.=20

Following the Maastricht meeting, there was a lively discussion of a simila=
r issue. The way things are, you need a lot of support to present an idea a=
t a BoF, so the usual way to present new things has become to publish a "ba=
r BoF" and present there. Despite the name, the modern bar BoF is not held =
in a bar, but rather in the empty conference rooms during lunch time and la=
te in the evening.  Understandably, people don't like this much.

There have been a few suggestions for alternate ways of presenting and gath=
ering supporters. One such suggestion is in this draft: http://tools.ietf.o=
rg/html/draft-nir-non-wg-presentations-01

A poster session sounds cool, but it works well when the presenters are com=
panies, rather than individuals. To get a good A0 poster, you need access t=
o printing services (which are not cheap, but doable) and graphic design ta=
lent, which is neither cheap nor common in IETF attendees.  To get such a p=
oster up, I would need either my company's sponsorship, or else use my own =
talents in graphic design: Hmm, #12FF12. Now there's a nice shade of green =
for a background. As for fonts, let's go with Mistral, because http://www.c=
racked.com/funny-5647-fonts .

Seriously, though, most of the presentation slides you see in an IETF meeti=
ng are either black-on-white with way too much text, sometimes adding some =
default design from the software, or else they're extremely well designed, =
where you know there's been some company sponsorship.  Some of the Internet=
-of-Things presentations in recent IETF meetings are examples of the latter=
. I think that's too high a bar to set for new ideas that still don't have =
much traction.

It could be done with some booths instead of the posters - maybe some desks=
 arranged around a room.

Yoav


From tme@americafree.tv  Thu Jan  6 04:30:14 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 544453A6EFF for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 04:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.193
X-Spam-Level: 
X-Spam-Status: No, score=-102.193 tagged_above=-999 required=5 tests=[AWL=0.406, 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 zvbRUYGEbi+Q for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 04:30:13 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id C65CD3A6EFE for <ietf@ietf.org>; Thu,  6 Jan 2011 04:30:12 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 6ED85996743D; Thu,  6 Jan 2011 07:32:18 -0500 (EST)
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
Date: Thu, 6 Jan 2011 07:32:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1552B4CF-059E-4EE3-ADE0-48F191D66041@americafree.tv>
References: <4D258AB3.9010903@tana.it> <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
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, 06 Jan 2011 12:30:14 -0000

On Jan 6, 2011, at 5:16 AM, Yoav Nir wrote:

>=20
> On Jan 6, 2011, at 11:26 AM, Alessandro Vesely wrote:
>=20
>> I've never attended an IETF meeting.  Why?  Because it seems to me =
quite
>> unlikely to have a chance to say something useful by going there.  I =
mean
>> useful with respect to a problem that I consider important.  That is, =
not
>> just a minimal contribution to an already scheduled session that I =
may happen
>> to attend.  Perhaps, I should request a session...
>>=20
>> Problems are often expressed in the form of tentative solutions.  =
Such
>> solutions may occasionally happen to be discussed, refined, and =
agreed upon
>> by a group of individuals.  Implementation, standardization, and =
adoption may
>> eventually follow  --not necessarily in this order.  Isn't this how =
the IRTF
>> and the IETF should work?
>>=20
>> A poster session would be a sort of plenary, lasting a couple of =
hours or so,
>> with posters hanged on numbered hardboard panels arranged along a =
walkway.  A
>> poster may be sized A0, or ~50 in, or consist of an equivalent number =
of
>> smaller sheets.  Posters may stay exposed for a few hours =
before/after the
>> scheduled time period.  During the session time, however, authors =
should
>> stand beside their posters and thus have their chance to talk to any
>> interested ietfers, one by one or in small knots, informally.  A few =
dozens
>> of posters per session may provide for adequate gathering.
>>=20
>> IME, this way of participating is easier and less binding for both =
authors
>> and attendees.  A poster would suit subjects for which it's difficult =
to
>> carve a niche within a hosting WG's session, but it may also work as =
a means
>> to achieve consensus on a given topic before raising it in a more =
official
>> discussion.
>>=20
>> Opinions/suggestions?
>=20
> Hi Alessandro.=20
>=20
> Following the Maastricht meeting, there was a lively discussion of a =
similar issue. The way things are, you need a lot of support to present =
an idea at a BoF, so the usual way to present new things has become to =
publish a "bar BoF" and present there. Despite the name, the modern bar =
BoF is not held in a bar, but rather in the empty conference rooms =
during lunch time and late in the evening.  Understandably, people don't =
like this much.
>=20
> There have been a few suggestions for alternate ways of presenting and =
gathering supporters. One such suggestion is in this draft: =
http://tools.ietf.org/html/draft-nir-non-wg-presentations-01
>=20
> A poster session sounds cool, but it works well when the presenters =
are companies, rather than individuals. To get a good A0 poster, you =
need access to printing services (which are not cheap, but doable) and =
graphic design talent, which is neither cheap nor common in IETF =
attendees.  To get such a poster up, I would need either my company's =
sponsorship, or else use my own talents in graphic design: Hmm, #12FF12. =
Now there's a nice shade of green for a background. As for fonts, let's =
go with Mistral, because http://www.cracked.com/funny-5647-fonts .

I am neutral on the overall idea, but in many (most?) academic =
conferences in a poster session you get a pin board (hopefully with a =
bunch of pins), which lends itself well to pinning up a set of printed =
out slides. I have seen many fine poster session presentations from =
people with very little money, so
I don't agree it unduly favors the well sponsored. And it has one great =
advantage...


>=20
> Seriously, though, most of the presentation slides you see in an IETF =
meeting are either black-on-white with way too much text,

... in that you can read the slides with too much text at your leisure =
if you want to, rather than having them flash by unread.

I am not sure it would fit well with the "IETF ecosystem," as it takes =
time to scan through a bunch of posters, and it takes time to stand
by your poster and answer any questions, and time is always short at an =
IETF. Maybe we could just have them in the halls and call them a =
"hall-BOF."

Regards
Marshall=20


> sometimes adding some default design from the software, or else =
they're extremely well designed, where you know there's been some =
company sponsorship.  Some of the Internet-of-Things presentations in =
recent IETF meetings are examples of the latter. I think that's too high =
a bar to set for new ideas that still don't have much traction.
>=20
> It could be done with some booths instead of the posters - maybe some =
desks arranged around a room.
>=20
> Yoav
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From hgs@cs.columbia.edu  Thu Jan  6 05:54:05 2011
Return-Path: <hgs@cs.columbia.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 840A23A6E38 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 05:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, GB_I_LETTER=-2]
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 bvRn-FN2zmgl for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 05:54:02 -0800 (PST)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by core3.amsl.com (Postfix) with ESMTP id D27FC3A6E28 for <ietf@ietf.org>; Thu,  6 Jan 2011 05:54:01 -0800 (PST)
Received: from [192.168.1.15] (pool-71-191-235-184.washdc.east.verizon.net [71.191.235.184]) (user=hgs10 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id p06Du2j8016640 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 6 Jan 2011 08:56:03 -0500 (EST)
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
Date: Thu, 6 Jan 2011 08:56:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DAE1D7B-4DE8-4EAE-80FC-FFF6B16C0B92@cs.columbia.edu>
References: <4D258AB3.9010903@tana.it> <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1082)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: IETF Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
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, 06 Jan 2011 13:54:05 -0000

>=20
> A poster session sounds cool, but it works well when the presenters =
are companies, rather than individuals. To get a good A0 poster, you =
need access to printing services (which are not cheap, but doable) and =
graphic design talent, which is neither cheap nor common in IETF =
attendees.  To get such a poster up, I would need either my company's =
sponsorship, or else use my own talents in graphic design: Hmm, #12FF12. =
Now there's a nice shade of green for a background. As for fonts, let's =
go with Mistral, because http://www.cracked.com/funny-5647-fonts .

Conferences (IEEE, ACM, ...) routinely have poster sessions, with mostly =
academic participation. Well-funded universities spend $50 at the local =
print shop or have an in-house large-size printer; not-so-well-funded =
universities simply print a dozen letter-size sheets and attach them to =
the board.

Henning=

From edj.etc@gmail.com  Thu Jan  6 06:08:46 2011
Return-Path: <edj.etc@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 57B8A3A6F13 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 06:08:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.384
X-Spam-Level: 
X-Spam-Status: No, score=-103.384 tagged_above=-999 required=5 tests=[AWL=0.215, 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 LB0C4hfac5FF for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 06:08:45 -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 9E3033A6E28 for <ietf@ietf.org>; Thu,  6 Jan 2011 06:08:44 -0800 (PST)
Received: by bwz12 with SMTP id 12so16311241bwz.31 for <ietf@ietf.org>; Thu, 06 Jan 2011 06:10:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=vl0XcOfdlCUXaVbbIwPNOmpgioAZbJQGHTviti/3M/4=; b=bl84iUYDAd9SVrIy7RhHAgwhQZJVqovsDqJFBKUK/U4lyZuAlwbj1ABbBSahPHskXB wJWT9hPrwyFpSAqZFtsxEAgmmFlVSVcEOvVRHKrw65xg9sg/PNRMJbmVGx7qbiylEsZo ouOPnlzUmws3idorl6xB1z9ZfROkDzMBBD0rM=
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 :content-type; b=wsY8hWtWQbODeObrpDoJBNSzvLHOR8+x9oikSfVUpb7cpOhmRqbHqIz31+fJdji2n0 iMypqDAq3Vi1r9pncTEXnbkyW9/51LQsSIMROAdAjABvPMg7sI0qiCFlTTz0Axa1MqXK gDW6lBKtiZTYaSrIx7VnGL0jPnMzJtbXrybFU=
MIME-Version: 1.0
Received: by 10.204.114.148 with SMTP id e20mr11696bkq.168.1294323049737; Thu, 06 Jan 2011 06:10:49 -0800 (PST)
Received: by 10.204.119.211 with HTTP; Thu, 6 Jan 2011 06:10:49 -0800 (PST)
In-Reply-To: <1552B4CF-059E-4EE3-ADE0-48F191D66041@americafree.tv>
References: <4D258AB3.9010903@tana.it> <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com> <1552B4CF-059E-4EE3-ADE0-48F191D66041@americafree.tv>
Date: Thu, 6 Jan 2011 09:10:49 -0500
Message-ID: <AANLkTi=G06XYCCw9Jz05n0b4kZbH_6JPPomtq6bCKX21@mail.gmail.com>
Subject: Re: Poster sessions
From: Ed Juskevicius <edj.etc@gmail.com>
To: Marshall Eubanks <tme@americafree.tv>, Yoav Nir <ynir@checkpoint.com>,  IETF Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
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: Thu, 06 Jan 2011 14:08:46 -0000

+1

Regards,

Ed  J



On 1/6/11, Marshall Eubanks <tme@americafree.tv> wrote:
>
> On Jan 6, 2011, at 5:16 AM, Yoav Nir wrote:
>
>>
>> On Jan 6, 2011, at 11:26 AM, Alessandro Vesely wrote:
>>
>>> I've never attended an IETF meeting.  Why?  Because it seems to me quite
>>> unlikely to have a chance to say something useful by going there.  I mean
>>> useful with respect to a problem that I consider important.  That is, not
>>> just a minimal contribution to an already scheduled session that I may
>>> happen
>>> to attend.  Perhaps, I should request a session...
>>>
>>> Problems are often expressed in the form of tentative solutions.  Such
>>> solutions may occasionally happen to be discussed, refined, and agreed
>>> upon
>>> by a group of individuals.  Implementation, standardization, and adoption
>>> may
>>> eventually follow  --not necessarily in this order.  Isn't this how the
>>> IRTF
>>> and the IETF should work?
>>>
>>> A poster session would be a sort of plenary, lasting a couple of hours or
>>> so,
>>> with posters hanged on numbered hardboard panels arranged along a
>>> walkway.  A
>>> poster may be sized A0, or ~50 in, or consist of an equivalent number of
>>> smaller sheets.  Posters may stay exposed for a few hours before/after
>>> the
>>> scheduled time period.  During the session time, however, authors should
>>> stand beside their posters and thus have their chance to talk to any
>>> interested ietfers, one by one or in small knots, informally.  A few
>>> dozens
>>> of posters per session may provide for adequate gathering.
>>>
>>> IME, this way of participating is easier and less binding for both
>>> authors
>>> and attendees.  A poster would suit subjects for which it's difficult to
>>> carve a niche within a hosting WG's session, but it may also work as a
>>> means
>>> to achieve consensus on a given topic before raising it in a more
>>> official
>>> discussion.
>>>
>>> Opinions/suggestions?
>>
>> Hi Alessandro.
>>
>> Following the Maastricht meeting, there was a lively discussion of a
>> similar issue. The way things are, you need a lot of support to present an
>> idea at a BoF, so the usual way to present new things has become to
>> publish a "bar BoF" and present there. Despite the name, the modern bar
>> BoF is not held in a bar, but rather in the empty conference rooms during
>> lunch time and late in the evening.  Understandably, people don't like
>> this much.
>>
>> There have been a few suggestions for alternate ways of presenting and
>> gathering supporters. One such suggestion is in this draft:
>> http://tools.ietf.org/html/draft-nir-non-wg-presentations-01
>>
>> A poster session sounds cool, but it works well when the presenters are
>> companies, rather than individuals. To get a good A0 poster, you need
>> access to printing services (which are not cheap, but doable) and graphic
>> design talent, which is neither cheap nor common in IETF attendees.  To
>> get such a poster up, I would need either my company's sponsorship, or
>> else use my own talents in graphic design: Hmm, #12FF12. Now there's a
>> nice shade of green for a background. As for fonts, let's go with Mistral,
>> because http://www.cracked.com/funny-5647-fonts .
>
> I am neutral on the overall idea, but in many (most?) academic conferences
> in a poster session you get a pin board (hopefully with a bunch of pins),
> which lends itself well to pinning up a set of printed out slides. I have
> seen many fine poster session presentations from people with very little
> money, so
> I don't agree it unduly favors the well sponsored. And it has one great
> advantage...
>
>
>>
>> Seriously, though, most of the presentation slides you see in an IETF
>> meeting are either black-on-white with way too much text,
>
> ... in that you can read the slides with too much text at your leisure if
> you want to, rather than having them flash by unread.
>
> I am not sure it would fit well with the "IETF ecosystem," as it takes time
> to scan through a bunch of posters, and it takes time to stand
> by your poster and answer any questions, and time is always short at an
> IETF. Maybe we could just have them in the halls and call them a "hall-BOF."
>
> Regards
> Marshall
>
>
>> sometimes adding some default design from the software, or else they're
>> extremely well designed, where you know there's been some company
>> sponsorship.  Some of the Internet-of-Things presentations in recent IETF
>> meetings are examples of the latter. I think that's too high a bar to set
>> for new ideas that still don't have much traction.
>>
>> It could be done with some booths instead of the posters - maybe some
>> desks arranged around a room.
>>
>> Yoav
>>
>> _______________________________________________
>> 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 dwm@xpasc.com  Thu Jan  6 07:10:15 2011
Return-Path: <dwm@xpasc.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 2F0B83A6E35 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 07:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 fTDfTed8sc5t for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 07:10:14 -0800 (PST)
Received: from mail.xpasc.com (mail.xpasc.com [68.164.244.189]) by core3.amsl.com (Postfix) with ESMTP id 331523A6E31 for <ietf@ietf.org>; Thu,  6 Jan 2011 07:10:14 -0800 (PST)
Received: from bslepgate.xpasc.com (localhost.localdomain [127.0.0.1]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 5061D100586 for <ietf@ietf.org>; Thu,  6 Jan 2011 07:12:20 -0800 (PST)
X-Propel-Return-Path: <dwm@xpasc.com>
Received: from mail.xpasc.com ([10.1.2.88]) by [127.0.0.1] ([127.0.0.1]) (port 7027) (Abaca EPG outproxy filter 3.1.2.exported $Rev: 9262 $) id iz6Urb16fck0; Thu, 06 Jan 2011 07:12:20 -0800
Received: from xpasc.com (egate.xpasc.com [10.1.2.49]) by bslepgate.xpasc.com (Postfix-out) with ESMTP id 24259100585 for <ietf@ietf.org>; Thu,  6 Jan 2011 07:12:20 -0800 (PST)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id p06FCGJc016973 for <ietf@ietf.org>; Thu, 6 Jan 2011 07:12:18 -0800
Date: Thu, 6 Jan 2011 07:12:16 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: Poster sessions
In-Reply-To: <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
Message-ID: <Pine.LNX.4.64.1101060659460.6107@egate.xpasc.com>
References: <4D258AB3.9010903@tana.it> <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Propel-ID: iz6Urb16fck0
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, 06 Jan 2011 15:10:15 -0000

On Thu, 6 Jan 2011, Yoav Nir wrote:

> A poster session sounds cool, but it works well when the presenters are
> companies, rather than individuals. To get a good A0 poster, you need
> access to printing services (which are not cheap, but doable) and
> graphic design talent, which is neither cheap nor common in IETF
> attendees.  To get such a poster up, I would need either my company's
> sponsorship, or else use my own talents in graphic design: Hmm, #12FF12.
> Now there's a nice shade of green for a background. As for fonts, let's
> go with Mistral, because http://www.cracked.com/funny-5647-fonts.

My just completed her MS in Nutrition and Food Science. As part of her
program she had to produce two posters. It turns out to be quite easy
to use PowerPoint to create poster sized slides ... in one case a single
very large slide and in the other, 3 slides, one per tri-fold panel. I 
forget what FedEx Office (aka Kinko's) would have charged, and our local
large format print ship would have been less as the company I was working
for allowed me to use their large format HP printer, but it was in the
order of $200. Quite reasonable for someone to spend to put forth an 
idea they are passionate about with or without sponsorship. And as
others have noted, printed pages fastened to a board is much cheaper.

Seems like a few tables at one end of the break area could be setup
if there are just a few such presentations at a meeting, or if this
becomes popular, reserve a meeting room near the break area. Schedule
a couple specific breaks/lunch times as Poster BOFs when the presenters
would be there and include a list of topics, etc. in the meeting
materials.

Probably require an ID to backup the material.

Dave Morris 

From dworley@avaya.com  Thu Jan  6 08:54:30 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 5A4BA3A6C24 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 08:54:30 -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 cEAv05fKyqKy for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 08:54:29 -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 2C86F3A6B8F for <ietf@ietf.org>; Thu,  6 Jan 2011 08:54:29 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHaCJU2HCzI1/2dsb2JhbACkHnOoEgKVbIVMBIRniVk
X-IronPort-AV: E=Sophos;i="4.60,284,1291611600"; d="scan'208";a="53161610"
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; 06 Jan 2011 11:56:35 -0500
X-IronPort-AV: E=Sophos;i="4.60,284,1291611600"; d="scan'208";a="578447052"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 06 Jan 2011 11:55:55 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 6 Jan 2011 11:55:54 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Alessandro Vesely <vesely@tana.it>, IETF Discussion <ietf@ietf.org>
Date: Thu, 6 Jan 2011 11:54:53 -0500
Subject: RE: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: Acutg+wXOlVR0zuuTgGJQvy3ZhRoVgAPoRbh
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>
References: <4D258AB3.9010903@tana.it>
In-Reply-To: <4D258AB3.9010903@tana.it>
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, 06 Jan 2011 16:54:30 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Alessandro=
 Vesely [vesely@tana.it]

I've never attended an IETF meeting.  Why?  Because it seems to me quite
unlikely to have a chance to say something useful by going there.  I mean
useful with respect to a problem that I consider important.  That is, not
just a minimal contribution to an already scheduled session that I may happ=
en
to attend.  Perhaps, I should request a session...

Problems are often expressed in the form of tentative solutions.  Such
solutions may occasionally happen to be discussed, refined, and agreed upon
by a group of individuals.  Implementation, standardization, and adoption m=
ay
eventually follow  --not necessarily in this order.  Isn't this how the IRT=
F
and the IETF should work?
_______________________________________________

If one has a tentative solution that one wants discussed, the usual
technique is to submit an Internet-Draft discussing it and post an
explanatory e-mail in a proper working group list.  Consider it a 24x7
poster session!

Dale

From dworley@avaya.com  Thu Jan  6 09:06: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 70E673A6C9E for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:06:06 -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 Ee91XjwviHMw for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:06:05 -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 7B9F63A6C9B for <ietf@ietf.org>; Thu,  6 Jan 2011 09:06:05 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPqFJU3GmAcF/2dsb2JhbACkHnOoDgKVcIVMBIRniVk
X-IronPort-AV: E=Sophos;i="4.60,284,1291611600"; d="scan'208";a="53163735"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 06 Jan 2011 12:08:05 -0500
X-IronPort-AV: E=Sophos;i="4.60,284,1291611600"; d="scan'208";a="567191801"
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; 06 Jan 2011 12:08:04 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Thu, 6 Jan 2011 12:08:03 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: John Levine <johnl@iecc.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 6 Jan 2011 12:07:08 -0500
Subject: RE: Fwd: FCC IPv6 Working Paper Released
Thread-Topic: Fwd: FCC IPv6 Working Paper Released
Thread-Index: AcutL4wBe92PaTKaTRGigTnkdeEr9gAlJrWN
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B56@DC-US1MBEX4.global.avaya.com>
References: <60EBF00D-95B0-474F-9FF3-73B6DD0F514A@bbn.com>, <20110105232314.33300.qmail@joyce.lan>
In-Reply-To: <20110105232314.33300.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: Thu, 06 Jan 2011 17:06:06 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of John Levin=
e [johnl@iecc.com]

>This seems like a document that might interest some on this list...

It's not bad, but it's basically a well written summary of the
conventional wisdom about IPv6.  As we all know, some of the
conventional wisdom is more grounded in reality, some less.
_______________________________________________

Nonetheless, it's better than nothing -- the "conventional" wisdom is known=
 by only a small subset of the people who ought to know it (and considerabl=
y more wisdom as well).

Dale

From hartmans@mit.edu  Thu Jan  6 09:29:49 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 97BA33A6C21 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:29:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.946
X-Spam-Level: 
X-Spam-Status: No, score=-102.946 tagged_above=-999 required=5 tests=[AWL=-0.681, 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 TMGgqn541rpB for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:29:48 -0800 (PST)
Received: from mail.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by core3.amsl.com (Postfix) with ESMTP id D1F6C3A6B89 for <ietf@ietf.org>; Thu,  6 Jan 2011 09:29:48 -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 23D072028C; Thu,  6 Jan 2011 12:30:24 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C6015432D; Thu,  6 Jan 2011 12:30:57 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Worley\, Dale R \(Dale\)" <dworley@avaya.com>
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>
Date: Thu, 06 Jan 2011 12:30:57 -0500
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> (Dale R. Worley's message of "Thu, 6 Jan 2011 11:54:53 -0500")
Message-ID: <tslipy2ndm6.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: IETF Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
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, 06 Jan 2011 17:29:49 -0000

Dale, I agree!  I think the bar of producing an internet draft is low
enough.  Regardless of what mechanisms we adopt to give people a chance
to try and sell their drafts, I think it is critical that we require the
drafts to be written.  I'm not really interested in lowering the bar too
much for someone to put together an idea for consideration.  I think we
gain a fair bit by asking people to refine their idea a fair bit before
the initial presentation. Writing a draft is one way of making sure that
happens.

Above, I'm commenting on the general problem of presenting an idea, not
the more complicated question of what the bar should be for BOFs.  I'm
not surewhether that bar is in the right place. I'd need to think
somewhat more about that.

From salvatore.loreto@ericsson.com  Thu Jan  6 09:32:11 2011
Return-Path: <salvatore.loreto@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 D2F773A6D01 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:32:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level: 
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 QN3KFBesV2Bg for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:32:11 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id A37533A6B89 for <ietf@ietf.org>; Thu,  6 Jan 2011 09:32:10 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-ef-4d25fd188699
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id D9.B6.23694.81DF52D4; Thu,  6 Jan 2011 18:34:16 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.2.234.1; Thu, 6 Jan 2011 18:34:16 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 0798F255D	for <ietf@ietf.org>; Thu,  6 Jan 2011 19:34:16 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id C549450529	for <ietf@ietf.org>; Thu,  6 Jan 2011 19:34:15 +0200 (EET)
Received: from Salvatore-Loretos-MacBook-Pro.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 52B154FD42	for <ietf@ietf.org>; Thu,  6 Jan 2011 19:34:15 +0200 (EET)
Message-ID: <4D25FD16.5030009@ericsson.com>
Date: Thu, 6 Jan 2011 18:34:14 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.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: ietf@ietf.org
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu>
In-Reply-To: <tslipy2ndm6.fsf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
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: Thu, 06 Jan 2011 17:32:12 -0000

On 1/6/11 6:30 PM, Sam Hartman wrote:
> Dale, I agree!  I think the bar of producing an internet draft is low
> enough.  Regardless of what mechanisms we adopt to give people a chance
> to try and sell their drafts, I think it is critical that we require the
> drafts to be written.  I'm not really interested in lowering the bar too
> much for someone to put together an idea for consideration.  I think we
> gain a fair bit by asking people to refine their idea a fair bit before
> the initial presentation. Writing a draft is one way of making sure that
> happens.
>
> Above, I'm commenting on the general problem of presenting an idea, not
> the more complicated question of what the bar should be for BOFs.  I'm
> not surewhether that bar is in the right place. I'd need to think
> somewhat more about that.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

Couldn't agree more.

/Sal

From jdfalk-lists@cybernothing.org  Thu Jan  6 09:54:48 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 BF1473A6CC0 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:54:48 -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 afTbdc9QgYlt for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 09:54:47 -0800 (PST)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by core3.amsl.com (Postfix) with ESMTP id 8BED63A68D5 for <ietf@ietf.org>; Thu,  6 Jan 2011 09:54:47 -0800 (PST)
Received: from [192.168.11.32] (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 p06HupZj028558 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 6 Jan 2011 09:56:53 -0800
X-DKIM: Sendmail DKIM Filter v2.6.0 ocelope.disgruntled.net p06HupZj028558
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybernothing.org; s=triac; t=1294336613; bh=8OCBuyMFFPC/vCf92UFalkELpo6ZZNCK1C2ecJPX/ fU=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=WcMKHoGQrPSa S+BFnW5lIBDlTdPgs6P0Rzo23x7UAX4ZUVSX7nS7U5XMBDldJSQ+kaKzrVLFlZYYt5S FpvB7nStbnRXN4dnVTrKBDXFE+z9RJaOKE9gn01l2PvKBE4yMVXwcdAXOWMcLBlhdzR WveN19g9EvRbGPFC/5ZAAXi6M=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Poster sessions
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
In-Reply-To: <1552B4CF-059E-4EE3-ADE0-48F191D66041@americafree.tv>
Date: Thu, 6 Jan 2011 09:56:50 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F06C000A-C0F0-4A0D-80F4-9DBDD7CF199C@cybernothing.org>
References: <4D258AB3.9010903@tana.it> <CE2BDE43-23BA-41B5-9C36-C5C17AFBF8A6@checkpoint.com> <1552B4CF-059E-4EE3-ADE0-48F191D66041@americafree.tv>
To: IETF Discussion <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: Thu, 06 Jan 2011 17:54:48 -0000

On Jan 6, 2011, at 4:32 AM, Marshall Eubanks wrote:

> I am not sure it would fit well with the "IETF ecosystem," as it takes =
time to scan through a bunch of posters, and it takes time to stand
> by your poster and answer any questions, and time is always short at =
an IETF. Maybe we could just have them in the halls and call them a =
"hall-BOF."

I like this idea.  A few ideas for requirements:

Slides MUST include the name of the draft so we can go read it in =
detail, and mention which WG or pre-WG mailing list the discussion is =
taking place on.

If anyone puts an obvious product pitch on a poster, attendees SHOULD =
deface it with snarky post-it notes and smeared food.



From touch@isi.edu  Thu Jan  6 10:06:00 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 81AA53A6E28 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 10:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.473
X-Spam-Level: 
X-Spam-Status: No, score=-102.473 tagged_above=-999 required=5 tests=[AWL=0.126, 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 BmafhYk19OLK for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 10:05:59 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id B590D3A6C9B for <ietf@ietf.org>; Thu,  6 Jan 2011 10:05:59 -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 p06I7f53026327 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 6 Jan 2011 10:07:41 -0800 (PST)
Message-ID: <4D2604ED.8080709@isi.edu>
Date: Thu, 06 Jan 2011 10:07:41 -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: John Kristoff <jtk@cymru.com>
Subject: Re: NAT behavior for IP ID field
References: <20100831150444.22bd579e@t61p>
In-Reply-To: <20100831150444.22bd579e@t61p>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@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, 06 Jan 2011 18:06:00 -0000

Although this is a fairly old thread, I didn't see mention of the IPv4 
ID draft we've been working on in INTAREA that addresses this:

https://datatracker.ietf.org/doc/draft-ietf-intarea-ipv4-id-update/

It was updated last Oct.

See esp. Sec 9.

Joe

On 8/31/2010 1:04 PM, John Kristoff wrote:
> I'm trying to locate an RFC that spells out the behavioral
> requirements, expectations or guidelines for NAT handling of the IP ID
> field, particularly for UDP messages.  Section 3.2.5 in RFC 3235
> briefly mentions issues surrounding IP fragmentation and reassembly,
> but  it doesn't specifically say if NATs should re-write IDs as a
> general rule.
>
> RFC 4787 doesn't seem to address this either.
>
> If this is not written down anywhere, do NATs generally rewrite the ID
> field with or without the MF bit set?
>
> For background and reference, I refer you to Steve Bellovin's 'A
> Technique for Counting NATted Hosts', particularly section IV.
>
> Thanks for any pointers,
>
> John
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From richard@shockey.us  Thu Jan  6 11:07:55 2011
Return-Path: <richard@shockey.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 0ED953A6F4D for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 11:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.693
X-Spam-Level: 
X-Spam-Status: No, score=-100.693 tagged_above=-999 required=5 tests=[AWL=-0.695, BAYES_50=0.001, 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 EDUVozISG6Ql for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 11:07:54 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by core3.amsl.com (Postfix) with SMTP id DFC983A6F3D for <ietf@ietf.org>; Thu,  6 Jan 2011 11:07:53 -0800 (PST)
Received: (qmail 25511 invoked by uid 0); 6 Jan 2011 19:10:00 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy1.bluehost.com.bluehost.com with SMTP; 6 Jan 2011 19:10:00 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:thread-index:Content-Language:X-Identified-User; b=Gs7GP7Md8FoIWJ03on8NUAx27oqooYYUO/pTJv20MKIIZCabtwFtIkv1mYhpyRa9caQcdyMUvARqK42mVuxlf2vi/4Mr2Itwhql6XfpnceVPqF36bSvV3/2o/aBd3s+c;
Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1PavDk-0003vt-23 for ietf@ietf.org; Thu, 06 Jan 2011 12:10:00 -0700
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
Subject: Win a free trip to Washington DC and the FCC.
Date: Thu, 6 Jan 2011 14:09:59 -0500
Message-ID: <002101cbadd5$50d162d0$f2742870$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01CBADAB.67FB5AD0"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Acut1U9iCM5r+qDrSK6eaWTTJNdFzg==
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.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: Thu, 06 Jan 2011 19:07:55 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0022_01CBADAB.67FB5AD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The FCC challenges researchers and software developers to engage in research
and create apps that help consumers foster, measure, and protect Internet
openness.

 

http://challenge.gov/FCC/114-fcc-open-internet-apps-challenge

 

 

Richard Shockey
Shockey Consulting
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
< <mailto:richard(at)shockey.us> mailto:richard(at)shockey.us>
skype-linkedin-facebook: rshockey101
http//www.sipforum.org

 


------=_NextPart_000_0022_01CBADAB.67FB5AD0
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:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</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=3DSection1>

<p class=3DMsoNormal>The FCC challenges researchers and software =
developers to
engage in research and create apps that help consumers foster, measure, =
and
protect Internet openness.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><a
href=3D"http://challenge.gov/FCC/114-fcc-open-internet-apps-challenge">ht=
tp://challenge.gov/FCC/114-fcc-open-internet-apps-challenge</a><o:p></o:p=
></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>Richard =
Shockey<br>
Shockey Consulting<br>
Chairman of the Board of Directors SIP Forum<br>
PSTN Mobile: +1 703.593.2683<br>
&lt;<a href=3D"mailto:richard(at)shockey.us"><span =
style=3D'color:blue'>mailto:richard(at)shockey.us</span></a>&gt;<br>
skype-linkedin-facebook: rshockey101<br>
http//www.sipforum.org</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0022_01CBADAB.67FB5AD0--


From dworley@avaya.com  Thu Jan  6 12:18: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 4681A3A6F46 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 12:18:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 lFhgTDq8UEVg for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 12:18:04 -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 6B4B83A6F31 for <ietf@ietf.org>; Thu,  6 Jan 2011 12:18:04 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIOyJU2HCzI1/2dsb2JhbACkH3OndQKWBYVMBIRniVmHdg
X-IronPort-AV: E=Sophos;i="4.60,285,1291611600"; d="scan'208";a="258376971"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 06 Jan 2011 15:20:10 -0500
X-IronPort-AV: E=Sophos;i="4.60,285,1291611600"; d="scan'208";a="578572555"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 06 Jan 2011 15:20:10 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 6 Jan 2011 15:20:10 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 6 Jan 2011 15:16:42 -0500
Subject: RE: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: Acutx6GT36DQ2wFqQqWuiGw3WRxyhgAFwCuV
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>, <tslipy2ndm6.fsf@mit.edu>
In-Reply-To: <tslipy2ndm6.fsf@mit.edu>
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 Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
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, 06 Jan 2011 20:18:05 -0000

________________________________________
From: Sam Hartman [hartmans-ietf@mit.edu]

I think the bar of producing an internet draft is low
enough.  Regardless of what mechanisms we adopt to give people a chance
to try and sell their drafts, I think it is critical that we require the
drafts to be written.
________________________________________

Actually, the bar for writing an I-D is near zero, so it should not be a ba=
rrier to presenting
any idea, no matter how half-baked.  A more significant effect is that an I=
-D is in text form
rather than poster form so it tends to direct the writer to a more thought-=
through presentation.

But most importantly, an I-D is globally available and globally announced, =
whereas a poster
session at an IETF meeting would be inherently limited to those physically =
present, which is biased
toward frequent attendees, those with sponsorship from large organizations,=
 and those from the
developed world.  Historically, the IETF has tried to limit biases in favor=
 of those groups.

Dale

From braden@isi.edu  Thu Jan  6 12:32:17 2011
Return-Path: <braden@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 259D93A6CF5 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 12:32:17 -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.111, 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 9rmT1Pq1tF5p for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 12:32:15 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id CE3833A6CBB for <ietf@ietf.org>; Thu,  6 Jan 2011 12:32:15 -0800 (PST)
Received: from [128.9.168.81] (rtb.isi.edu [128.9.168.81]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p06KXoQY016264; Thu, 6 Jan 2011 12:33:50 -0800 (PST)
Message-ID: <4D2628AB.3080003@isi.edu>
Date: Thu, 06 Jan 2011 12:40:11 -0800
From: Bob Braden <braden@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com>
In-Reply-To: <4D2556C9.9020901@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 06 Jan 2011 20:32:17 -0000

Historic might imply that they were once in service, but have later been 
replaced/deprecated. In fact, these protocols were always, and are 
still, *experimental*.  It would seem logical to assign them the 
Experimental category and be done with it.

Bob Braden


On 1/5/2011 9:44 PM, Mykyta Yevstifeyev wrote:
> Hello all,
>
> There have been a discussion on tsvwg mailing list about old transport
> layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT
> (RFC998). Initially there have been proposed to define IANA
> considerations for them. But after a discussion it was found out that it
> would be better to move them to Historic. I am writing to request more
> wider discussion on this topic.
>
> There is quite strong consensus that IRTP should be Historic. There is a
> registered draft on this topic:
>
> https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/
>
> But as for others it should be discussed. Moreover, maybe anyone knows
> some other old transport-layer protocols that are no longer in use?
>
> Please copy tour answer to tsvwg@ietf.org
>
> All the best,
> Mykyta Yevstifeyev
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From scott.brim@gmail.com  Thu Jan  6 12:58:59 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 275283A6CF5 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 12:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level: 
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[AWL=0.429, 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 TP3icG3P23CX for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 12:58:58 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 050793A6C9F for <ietf@ietf.org>; Thu,  6 Jan 2011 12:58:57 -0800 (PST)
Received: by qyk34 with SMTP id 34so19027644qyk.10 for <ietf@ietf.org>; Thu, 06 Jan 2011 13:01:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=pB/dqrTwoS6YJp81PgnkOAeIQg2bhiDf4VsVTjiWpgc=; b=u8AaHLLmSeA4ZcaV1gXyY62Er7rR8KboRUDbvKHp2kuzIMQ7WU8UCONqrda0FyYt0d grGGu2EF3mrghnkMWRft26pbS74wdZhKfEK44dKyI3CxnBFQDo9dzvExzZnTG2RUXZQz uoIDHUXx7qfJ/LNolQPWnuP6oRtbF0I70EYJg=
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=p+WLowjhVIUxWDHxgqCbjVZEe6jlKke0Jc9Tu+mNcwhhB/vCT/nc4BrhuUtSxpF1C8 4gc8x/XqHGGdjkL8vbO+D0E2YBsjMoLqL+J8yKfpecpQWSMdjcCn+I912tg8ANSC971z A+Q4yn6p+LhZ7kO1jQd9TGkAhIo68HPYzi8Z8=
Received: by 10.224.20.5 with SMTP id d5mr23331142qab.187.1294347663515; Thu, 06 Jan 2011 13:01:03 -0800 (PST)
Received: from bxb-vpn3-60.cisco.com (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id g32sm14629029qck.34.2011.01.06.13.01.01 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 13:01:02 -0800 (PST)
Message-ID: <4D262D8B.207@gmail.com>
Date: Thu, 06 Jan 2011 16:00:59 -0500
From: Scott Brim <scott.brim@gmail.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: Bob Braden <braden@isi.edu>
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com> <4D2628AB.3080003@isi.edu>
In-Reply-To: <4D2628AB.3080003@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 06 Jan 2011 20:58:59 -0000

On 01/06/2011 15:40 EST, Bob Braden wrote:
> 
> Historic might imply that they were once in service, but have later been
> replaced/deprecated. In fact, these protocols were always, and are
> still, *experimental*.  It would seem logical to assign them the
> Experimental category and be done with it.
> 
> Bob Braden

Yup.

> 
> 
> On 1/5/2011 9:44 PM, Mykyta Yevstifeyev wrote:
>> Hello all,
>>
>> There have been a discussion on tsvwg mailing list about old transport
>> layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT
>> (RFC998). Initially there have been proposed to define IANA
>> considerations for them. But after a discussion it was found out that it
>> would be better to move them to Historic. I am writing to request more
>> wider discussion on this topic.
>>
>> There is quite strong consensus that IRTP should be Historic. There is a
>> registered draft on this topic:
>>
>> https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/
>>
>>
>> But as for others it should be discussed. Moreover, maybe anyone knows
>> some other old transport-layer protocols that are no longer in use?
>>
>> Please copy tour answer to tsvwg@ietf.org
>>
>> All the best,
>> Mykyta Yevstifeyev
>>
>>
>>
>> _______________________________________________
>> 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 lixia@cs.ucla.edu  Thu Jan  6 13:06:23 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 D2C533A6CFF for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 13:06:23 -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 Ig-DOPTg1FuY for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 13:06:23 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 065B73A6CEC for <ietf@ietf.org>; Thu,  6 Jan 2011 13:06:23 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 5CE1B39E8083; Thu,  6 Jan 2011 13:08:29 -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 RiBmH0oMgFgk; Thu,  6 Jan 2011 13:08:27 -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 4C57239E80E0; Thu,  6 Jan 2011 13:08:27 -0800 (PST)
Subject: Re: Old transport-layer protocols to Historic?
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: <4D2628AB.3080003@isi.edu>
Date: Thu, 6 Jan 2011 13:08:26 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <59CD4CD4-9E0B-4B78-BB60-249DE018F7F1@cs.ucla.edu>
References: <4D2556C9.9020901@gmail.com> <4D2628AB.3080003@isi.edu>
To: Bob Braden <braden@isi.edu>
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: Thu, 06 Jan 2011 21:06:23 -0000

On Jan 6, 2011, at 12:40 PM, Bob Braden wrote:

>=20
> Historic might imply that they were once in service, but have later =
been replaced/deprecated. In fact, these protocols were always, and are =
still, *experimental*.  It would seem logical to assign them the =
Experimental category and be done with it.
>=20
> Bob Braden

I would like to second Bob's position here.

as a co-author for  NETBLT (RFC998): NETBLT was out of a research effort =
to answer the question: can we *fully* utilize long delay, high =
bandwidth (and potentially error prone) networks?  NETBLT says and here =
is one way to do it.=20
Over the years (it's published in 1987) I have received comments from =
many people saying that they learned something interesting or even =
useful from NETBLT. The NETBLT paper (SIGCOMM 1987) got cited over 200 =
times.

As RFC998 stated clearly:

   This document is published for discussion and comment, and does not
   constitute a standard.  The proposal may change and certain parts of
   the protocol have not yet been specified; implementation of this
   document is therefore not advised.

I don't see any harm to keep it as is.

Lixia
PS: on the other hand, what would a "historical status" imply?  the =
ideas obsolete?


> On 1/5/2011 9:44 PM, Mykyta Yevstifeyev wrote:
>> Hello all,
>>=20
>> There have been a discussion on tsvwg mailing list about old =
transport
>> layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT
>> (RFC998). Initially there have been proposed to define IANA
>> considerations for them. But after a discussion it was found out that =
it
>> would be better to move them to Historic. I am writing to request =
more
>> wider discussion on this topic.
>>=20
>> There is quite strong consensus that IRTP should be Historic. There =
is a
>> registered draft on this topic:
>>=20
>> =
https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/=

>>=20
>> But as for others it should be discussed. Moreover, maybe anyone =
knows
>> some other old transport-layer protocols that are no longer in use?
>>=20
>> Please copy tour answer to tsvwg@ietf.org
>>=20
>> All the best,
>> Mykyta Yevstifeyev
>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From doug@ewellic.org  Thu Jan  6 13:43:29 2011
Return-Path: <doug@ewellic.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 3E6D43A6D03 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 13:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 VsOnnOtmXCYb for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 13:43:28 -0800 (PST)
Received: from smtpoutwbe01.prod.mesa1.secureserver.net (smtpoutwbe01.prod.mesa1.secureserver.net [208.109.78.112]) by core3.amsl.com (Postfix) with SMTP id AAEAB3A6CFB for <ietf@ietf.org>; Thu,  6 Jan 2011 13:43:27 -0800 (PST)
Received: (qmail 32720 invoked from network); 6 Jan 2011 21:45:33 -0000
Received: from unknown (HELO localhost) (72.167.218.130) by smtpoutwbe01.prod.mesa1.secureserver.net with SMTP; 6 Jan 2011 21:45:33 -0000
Received: (qmail 31272 invoked by uid 99); 6 Jan 2011 21:45:33 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.190
User-Agent: Web-Based Email 5.3.03
Message-Id: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net>
From: "Doug Ewell" <doug@ewellic.org>
To: "Lixia Zhang" <lixia@cs.ucla.edu>
Subject: RE: Old transport-layer protocols to =?UTF-8?Q?Historic=3F?=
Date: Thu, 06 Jan 2011 14:45:31 -0700
Mime-Version: 1.0
Cc: Bob Braden <braden@isi.edu>, 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, 06 Jan 2011 21:43:29 -0000

Lixia Zhang <lixia at cs dot ucla dot edu> wrote:

> PS: on the other hand, what would a "historical status" imply?  the ideas=
 obsolete?

Every now and then, someone proposes to move a given RFC to Historic,
not merely to reflect an observation that a process or protocol is
obsolete, but as an active attempt to deprecate it, regardless of its
currency or relevance.

I remember a few months ago, it was proposed (evidently not for the
first time) to move FTP to Historic, on the basis of its lack of
airtight 21st-century security features, with no consideration for the
innumerable existing systems and processes that have no need for
top-notch security, and rely daily on FTP.

I often see comments on this list about whether the "outside world"
views the IETF as irrelevant.  Declaring a commonly used, core process
or protocol as Historic because something better exists might be a
perfect example of this.

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =C2=AD



From Kurt.Zeilenga@Isode.COM  Thu Jan  6 13:57:23 2011
Return-Path: <Kurt.Zeilenga@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 2284D3A6D03; Thu,  6 Jan 2011 13:57:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.416
X-Spam-Level: 
X-Spam-Status: No, score=-102.416 tagged_above=-999 required=5 tests=[AWL=0.183, 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 wFBmcJmeqn4u; Thu,  6 Jan 2011 13:57:21 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id CB72F3A6CFB; Thu,  6 Jan 2011 13:57:20 -0800 (PST)
Received: from [192.168.42.5] (75-141-240-242.dhcp.reno.nv.charter.com [75.141.240.242])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <TSY7PQB0K1Nw@rufus.isode.com>; Thu, 6 Jan 2011 21:59:26 +0000
Subject: Re: Gen-ART LC Review of draft-zeilenga-ldap-dontusecopy-08
From: Kurt Zeilenga <Kurt.Zeilenga@Isode.COM>
In-Reply-To: <624858D5-76CC-4245-A58A-B3C72279324F@estacado.net>
Date: Thu, 6 Jan 2011 13:59:23 -0800
Message-Id: <9EBA7A03-C4F1-440B-9F03-0E84945F1DD7@Isode.COM>
References: <624858D5-76CC-4245-A58A-B3C72279324F@estacado.net>
To: Ben Campbell <ben@estacado.net>
X-Mailer: Apple Mail (2.1082)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: General Area Review Team <gen-art@ietf.org>, draft-zeilenga-ldap-dontusecopy.all@tools.ietf.org, 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: Thu, 06 Jan 2011 21:57:23 -0000

Ben,

Thank you for your comments.  They have lead to a number of improvements =
in the I-D (new revision to be published shortly).  A few notes below.

-- Kurt

On Oct 11, 2010, at 2:39 PM, Ben Campbell wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-zeilenga-ldap-dontusecopy-08
> Reviewer: Ben Campbell
> Review Date: 2010-10-11
> IETF LC End Date: 2010-10-11
> IESG Telechat date: (if known)
>=20
> Summary:
>=20
> This draft is almost ready to be published as a proposed standard, but =
I have some comments that should be considered first.
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> -- General:=20
>=20
> (Let me preface my general comments with the admission that I am not =
an LDAP expert. Since this is a Gen-ART review, I'm approaching this as =
a generalist. If the answer is something like "Ben, if you new anything =
about LDAP this would all be obvious to you", that will not offend me in =
any way.)
>=20
> I'd like to see more explanation of the problem this needs to be =
solved.

The short explanation is that acting upon slate data can introduce =
security vulnerabilities in directory applications.

Exactly how a directory application might be vulnerable depends a great =
deal on the particulars of the directory application.

The intent of this specification is merely to provide a tool, long =
present in X.500 directory applications, to LDAP directory applications.

> I assume that there is concern that copied or cached data may not be =
up to date, or otherwise not be authoritative. Some comments to that =
effect, along with reasoning for why this may happen in the first place =
would be helpful. A quick scan of 4511 and 4512 didn't turn up much =
about this, other than some passing references that some servers may =
shadow or cache dats from other servers., and not to accept modification =
requests against cached or shadowed data. Is there any other =
specification about LDAP cacheing, maintaining cache freshness, etc?

The reference, I guess, would be X.500 series of documents.  LDAP is =
specified as alternative access protocol to an X.500 directory service.

While this document only has an informative reference to its X.500 =
counterpart, I note that this document does contain a normative =
reference to the LDAP technical specification [RFC4510] which does =
include normative references to relevant X.500 specifications.   I do =
not reference X.500 normatively here as I believe a developer can well =
implement this control, by itself, without ever having read a X.500 =
specification.

> I get a gut feeling that this extension effectively patches a hole in =
an implied delegation model for LDAP, but I don't find much in the way =
of explicit specification for that in the referenced docs (Maybe I =
should be looking at X.500 specs?). I'm not saying that this document =
should be burdened with a formal specification of the LDAP delegation =
model. But I think a little more context would be helpful.

I really don't think it necessary to understand the particulars the =
X.500/LDAP delegation model to understand when and how this control =
ought to be used.  Basically, some knowledge a server might rely on in =
answering a question can be stale.  Use of stale data can be =
problematic.  This control says "don't use stale data".

> I'd also like to see some more guidance on when it's reasonable to use =
this extension. For example, wouldn't a client always want an =
authoritative answer to an interrogation?

Generally, clients should only use this control when there is a =
directory application need for it to be used.

> Why wouldn't it use this extension all the time?

Because that would eliminate all the benefits of caching and shadowing =
of data.

> Does it hurt anything if it does?

It can "break" the application.  In general, applications ought to be =
designed to well use copied information.

Anyways, I'll make some minor tweaks here to address these points.

>=20
> -- section 3, 2nd paragraph:
>=20
> I think this paragraph might be better restated normatively.

I'm not sure what you mean by "normatively" as I feel it obvious that =
whole section a normative part of the specification.   I guess what you =
might mean is use RFC 2119 keywords here.  I rather not.  Aside from RFC =
2119 saying keywords ought to be sparingly, to me, MUST and SHOULDs are =
best used to impart implementation requirements and recommendations, =
especially those which if not followed will result in some significant =
peculiar behavior.

>=20
> -- section 4:
>=20
> The security consideration comments seem to be about caching in =
general. Does this extension make things any better or worse?

The extension is a tool which, if used well, can be used to mitigate =
certain threats.

I'll be replacing the security considerations text with the text =
provided by Phillip Hallam-Baker plus some, which should better cover =
this.

> RFC4510 has nothing to say about security beyond referring the reader =
to the security considerations in the technical specs.
>=20
> Nits/editorial comments:
>=20
> -- General
>=20
> There seems to be inconsistent use of the terms "copy", "shadow", =
"cache",  "original" , and "master" between this draft and RFC 4510 and =
4512.

I've tried to avoid some of the pitfalls of inconsistent LDAP/X.500 =
terminology in this document by trying not rely on any particular =
external use of the term, though I've added comments such as "original =
(master)" for clarification.

> Maybe adding these terms to the terminology sections would help.

Frankly, I would be hard pressed to clearly define these terms as =
LDAP/X.500 is a terminology mess.  The best I can do is make it clear to =
the read of this document the intended semantics of this control:  with =
control you get authoritative data or an error, without this control you =
may get non-authoritative data.

>=20
> -- Section 1, paragraph 3:
>=20
> Please expand DN on first use.
>=20
>=20


From brian.e.carpenter@gmail.com  Thu Jan  6 20:16: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 B88F73A6F21 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 20:16:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.43
X-Spam-Level: 
X-Spam-Status: No, score=-103.43 tagged_above=-999 required=5 tests=[AWL=0.169, 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 TKdh-e6AqUnY for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 20:16:26 -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 BED923A6E50 for <ietf@ietf.org>; Thu,  6 Jan 2011 20:16:26 -0800 (PST)
Received: by gxk28 with SMTP id 28so7897485gxk.31 for <ietf@ietf.org>; Thu, 06 Jan 2011 20:18:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Wal3VjQ5UZzAib5ihvrm++MO+idkMhvI6uyF+DqgkK8=; b=LnLJKWm8HjGpuwF9tGQabv7Tn0QH171XNqYm1FYm7WMZK3Ev66/q0wDrbzwuAF35nS Lsq6isDRGKqqcmrZRACHZWF15G3Uh5gx+ZlzAU6gRK0/9z7UlIjpCUvT5JOrDkWoBmOw t2Gzab9Ne8+TpkyPoNC8SyMu4IYKTiXw5Q+R8=
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=mLe5rrbLI9/cz+sA5NOjUm3hOl3aq1GxntM5q0LIq05xdn521rzwwazqAaMrXGjn67 ptV0LqoMJvMN3QJaspv1Ebmv4iQeLsU1CM5tmN5n0ftdAVjMC7mu+JRxYmDDFaUbK4hs MD0udCmQNcW7QrkoKDtDukoUB70pwMDG5Lnus=
Received: by 10.90.70.2 with SMTP id s2mr2792141aga.184.1294373911509; Thu, 06 Jan 2011 20:18:31 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id f10sm33038013anh.5.2011.01.06.20.18.27 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 20:18:30 -0800 (PST)
Message-ID: <4D26940F.3020404@gmail.com>
Date: Fri, 07 Jan 2011 17:18:23 +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: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>, <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF Discussion <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
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, 07 Jan 2011 04:16:27 -0000

Firstly, I agree: as a general rule, to get official floor space of
any kind at the IETF venue, you SHOULD have posted a draft. If there
is no draft, that is exactly when you need a bar BOF. (Complicated joke
about the height of the bar for a bar BOF, and the drafts to be drunk,
goes here.)

Second, a number of operators' meetings have a session for "lightning
talks" with minimal formality. But in practice, we have that at most
Area Meetings - post a relevant draft, ask the ADs for a 5 minute slot,
and you usually get it.

So I'm not sure that we have a gap in our options. I'm more likely
to read a draft with an interesting title than to walk around
reading hard-copy posters.

Regards
   Brian Carpenter




On 2011-01-07 09:16, Worley, Dale R (Dale) wrote:
> ________________________________________
> From: Sam Hartman [hartmans-ietf@mit.edu]
> 
> I think the bar of producing an internet draft is low
> enough.  Regardless of what mechanisms we adopt to give people a chance
> to try and sell their drafts, I think it is critical that we require the
> drafts to be written.
> ________________________________________
> 
> Actually, the bar for writing an I-D is near zero, so it should not be a barrier to presenting
> any idea, no matter how half-baked.  A more significant effect is that an I-D is in text form
> rather than poster form so it tends to direct the writer to a more thought-through presentation.
> 
> But most importantly, an I-D is globally available and globally announced, whereas a poster
> session at an IETF meeting would be inherently limited to those physically present, which is biased
> toward frequent attendees, those with sponsorship from large organizations, and those from the
> developed world.  Historically, the IETF has tried to limit biases in favor of those groups.
> 
> Dale
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From narten@us.ibm.com  Thu Jan  6 21:51:08 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 37FC23A67A1 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 21:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.001
X-Spam-Level: 
X-Spam-Status: No, score=-106.001 tagged_above=-999 required=5 tests=[AWL=0.598, 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 CUInragwWwGZ for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 21:51:06 -0800 (PST)
Received: from e5.ny.us.ibm.com (e5.ny.us.ibm.com [32.97.182.145]) by core3.amsl.com (Postfix) with ESMTP id 4B8D03A6403 for <ietf@ietf.org>; Thu,  6 Jan 2011 21:51:06 -0800 (PST)
Received: from d01dlp01.pok.ibm.com (d01dlp01.pok.ibm.com [9.56.224.56]) by e5.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p075U2wq019757 for <ietf@ietf.org>; Fri, 7 Jan 2011 00:30:02 -0500
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 177A8728042 for <ietf@ietf.org>; Fri,  7 Jan 2011 00:53:05 -0500 (EST)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p075r4lH476824 for <ietf@ietf.org>; Fri, 7 Jan 2011 00:53:04 -0500
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 p075r4bK007305 for <ietf@ietf.org>; Thu, 6 Jan 2011 22:53:04 -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 p075r3mZ007255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 6 Jan 2011 22:53:04 -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 p075r4iB023539 for <ietf@ietf.org>; Fri, 7 Jan 2011 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p075r22q023418 for ietf@ietf.org; Fri, 7 Jan 2011 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201101070553.p075r22q023418@rotala.raleigh.ibm.com>
Date: Fri, 07 Jan 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-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, 07 Jan 2011 05:51:08 -0000

Total of 66 messages in the last 7 days.
 
script run at: Fri Jan  7 00:53:02 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.58% |    5 |  8.21% |    45451 | rbarnes@bbn.com
  1.52% |    1 | 13.58% |    75158 | mohamed.boucadair@orange-ftgroup.com
  3.03% |    2 |  9.82% |    54374 | stpeter@stpeter.im
  4.55% |    3 |  6.14% |    33997 | ynir@checkpoint.com
  6.06% |    4 |  3.76% |    20841 | dworley@avaya.com
  4.55% |    3 |  4.91% |    27197 | hallam@gmail.com
  4.55% |    3 |  3.22% |    17841 | tme@americafree.tv
  4.55% |    3 |  2.32% |    12830 | johnl@iecc.com
  3.03% |    2 |  3.61% |    20010 | ron.even.tlv@gmail.com
  3.03% |    2 |  2.08% |    11512 | scott.brim@gmail.com
  3.03% |    2 |  1.52% |     8403 | mohta@necom830.hpcl.titech.ac.jp
  1.52% |    1 |  2.64% |    14630 | karlheinz.wolf@nic.at
  1.52% |    1 |  2.08% |    11521 | jsalowey@cisco.com
  1.52% |    1 |  1.74% |     9620 | kurt.zeilenga@isode.com
  1.52% |    1 |  1.71% |     9479 | edj.etc@gmail.com
  1.52% |    1 |  1.69% |     9361 | rolf.winter@neclab.eu
  1.52% |    1 |  1.44% |     7961 | richard@shockey.us
  1.52% |    1 |  1.30% |     7184 | dhc2@dcrocker.net
  1.52% |    1 |  1.27% |     7009 | smb@cs.columbia.edu
  1.52% |    1 |  1.26% |     6948 | daedulus@btconnect.com
  1.52% |    1 |  1.24% |     6876 | brian.e.carpenter@gmail.com
  1.52% |    1 |  1.21% |     6717 | jmpolk@cisco.com
  1.52% |    1 |  1.16% |     6398 | narten@us.ibm.com
  1.52% |    1 |  1.15% |     6367 | christer.holmberg@ericsson.com
  1.52% |    1 |  1.13% |     6237 | lixia@cs.ucla.edu
  1.52% |    1 |  1.09% |     6026 | hartmans@painless-security.com
  1.52% |    1 |  1.06% |     5887 | mansaxel@besserwisser.org
  1.52% |    1 |  1.04% |     5753 | dwm@xpasc.com
  1.52% |    1 |  1.04% |     5739 | john-ietf@jck.com
  1.52% |    1 |  0.99% |     5482 | john@jlc.net
  1.52% |    1 |  0.99% |     5468 | salvatore.loreto@ericsson.com
  1.52% |    1 |  0.98% |     5443 | hartmans-ietf@mit.edu
  1.52% |    1 |  0.97% |     5397 | elwynd@dial.pipex.com
  1.52% |    1 |  0.97% |     5390 | vesely@tana.it
  1.52% |    1 |  0.94% |     5227 | paf@cisco.com
  1.52% |    1 |  0.94% |     5207 | tobias.gondrom@gondrom.org
  1.52% |    1 |  0.88% |     4884 | jdfalk-lists@cybernothing.org
  1.52% |    1 |  0.86% |     4783 | braden@isi.edu
  1.52% |    1 |  0.85% |     4723 | doug@ewellic.org
  1.52% |    1 |  0.85% |     4715 | touch@isi.edu
  1.52% |    1 |  0.84% |     4642 | ole@cisco.com
  1.52% |    1 |  0.83% |     4605 | hgs@cs.columbia.edu
  1.52% |    1 |  0.79% |     4389 | adam@nostrum.com
  1.52% |    1 |  0.77% |     4272 | fred@cisco.com
  1.52% |    1 |  0.77% |     4241 | a.kral@sh.cvut.cz
  1.52% |    1 |  0.72% |     3961 | jari.arkko@piuha.net
  1.52% |    1 |  0.63% |     3467 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |   66 |100.00% |   553623 | Total

From evnikita2@gmail.com  Thu Jan  6 21:59:03 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 5DCE93A67A6 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 21:59:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.858
X-Spam-Level: 
X-Spam-Status: No, score=-2.858 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_55=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 k+D0zVzK91qA for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 21:59:01 -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 54DEE3A67A7 for <ietf@ietf.org>; Thu,  6 Jan 2011 21:59:01 -0800 (PST)
Received: by bwz12 with SMTP id 12so16947620bwz.31 for <ietf@ietf.org>; Thu, 06 Jan 2011 22:01:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=6rUqI+KN5KdKknJDUD/g9sWFrSJKyvs/yqUJeIn/WBo=; b=JmXKutm/6rKG5vUjGDk/l3jM1q6zJnPqx+TZ8t4TzgOcXCp2AMi8mIyTmAp85ZCnya p3oIDmHnzaK1uKOFBO9hpeioVejjXSiFcN+bAvLzQDrEPwca8icobmszg7az7TIpN7P1 eG8RPfJOOMlQDYh28Q4JwptudlAfq1dpG5G+M=
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=Uip9aKjOU/uDy7S4nG8WkwWM8FvBRjbXr2MEyrHMu6aVajhJFI+z/J1DgI6ha+U62D lzL2CzLT+UJtU28npMQiwXHUJ9ks5PnSH0cVvj0YyGTtpBnOAZC0l2WZirlz5BuwJN1b /DTIA3EGHEq4JpzGnGn5KpRcrrvNtFQKh5tHc=
Received: by 10.204.56.194 with SMTP id z2mr9282317bkg.81.1294380067079; Thu, 06 Jan 2011 22:01:07 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v25sm13966314bkt.18.2011.01.06.22.01.05 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 22:01:06 -0800 (PST)
Message-ID: <4D26AC33.5090207@gmail.com>
Date: Fri, 07 Jan 2011 08:01:23 +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: Doug Ewell <doug@ewellic.org>
Subject: Re: Old transport-layer protocols to Historic?
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net>
In-Reply-To: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net>
Content-Type: multipart/alternative; boundary="------------080702050100070409060405"
Cc: Bob Braden <braden@isi.edu>, ietf@ietf.org, Lixia Zhang <lixia@cs.ucla.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: Fri, 07 Jan 2011 05:59:03 -0000

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

06.01.2011 23:45, Doug Ewell wrote:
> Lixia Zhang<lixia at cs dot ucla dot edu>  wrote:
>
>> PS: on the other hand, what would a "historical status" imply?  the ideas obsolete?
> Every now and then, someone proposes to move a given RFC to Historic,
> not merely to reflect an observation that a process or protocol is
> obsolete, but as an active attempt to deprecate it, regardless of its
> currency or relevance.
>
> I remember a few months ago, it was proposed (evidently not for the
> first time) to move FTP to Historic, on the basis of its lack of
> airtight 21st-century security features, with no consideration for the
> innumerable existing systems and processes that have no need for
> top-notch security, and rely daily on FTP.
>
> I often see comments on this list about whether the "outside world"
> views the IETF as irrelevant.  Declaring a commonly used, core process
> or protocol as Historic because something better exists might be a
> perfect example of this.
I think that the author of RFC2026 was wrong while writing the 
definition of Historic status. This document says that Historic should 
be assigned only to that documents that were standards and now are 
obsolete. But why do we need such narrow definition? Non-standards RFCs 
are not made Historic while obsoleting, according to 2026. Moreover, 
such status will just duplicate the obsoleted-by one. When there will be 
the attempt to revise RFC 2026, we should put there that Historic status 
is to be assigned to that documents that are considered to be 
/deprecated/. I fully share the opinion of Doug here.

As for NETBLT, I am strongly against moving it to Historic, rather than 
specifying by Standards Track Document. There has been one attempt to do 
that by John White in 1995 (see draft-white-protocol-stack), but IMO 
(that likes strange, but...) we can align this document with the most 
current needs of Internet and publish.

Mykyta
> --
> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    06.01.2011 23:45, Doug Ewell wrote:
    <blockquote
cite="mid:20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net"
      type="cite">
      <pre wrap="">Lixia Zhang &lt;lixia at cs dot ucla dot edu&gt; wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">PS: on the other hand, what would a "historical status" imply?  the ideas obsolete?
</pre>
      </blockquote>
      <pre wrap="">
Every now and then, someone proposes to move a given RFC to Historic,
not merely to reflect an observation that a process or protocol is
obsolete, but as an active attempt to deprecate it, regardless of its
currency or relevance.

I remember a few months ago, it was proposed (evidently not for the
first time) to move FTP to Historic, on the basis of its lack of
airtight 21st-century security features, with no consideration for the
innumerable existing systems and processes that have no need for
top-notch security, and rely daily on FTP.

I often see comments on this list about whether the "outside world"
views the IETF as irrelevant.  Declaring a commonly used, core process
or protocol as Historic because something better exists might be a
perfect example of this.
</pre>
    </blockquote>
    I think that the author of RFC2026 was wrong while writing the
    definition of Historic status. This document says that Historic
    should be assigned only to that documents that were standards and
    now are obsolete. But why do we need such narrow definition?
    Non-standards RFCs are not made Historic while obsoleting, according
    to 2026. Moreover, such status will just duplicate the obsoleted-by
    one. When there will be the attempt to revise RFC 2026, we should
    put there that Historic status is to be assigned to that documents
    that are considered to be <i>deprecated</i>. I fully share the
    opinion of Doug here.<br>
    <br>
    As for NETBLT, I am strongly against moving it to Historic, rather
    than specifying by Standards Track Document. There has been one
    attempt to do that by John White in 1995 (see
    draft-white-protocol-stack), but IMO (that likes strange, but...) we
    can align this document with the most current needs of Internet and
    publish.<br>
    <br>
    Mykyta<br>
    <blockquote
cite="mid:20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net"
      type="cite">
      <pre wrap="">
--
Doug Ewell | Thornton, Colorado, USA | <a class="moz-txt-link-freetext" href="http://www.ewellic.org">http://www.ewellic.org</a>
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­


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

--------------080702050100070409060405--

From d3e3e3@gmail.com  Thu Jan  6 22:29:02 2011
Return-Path: <d3e3e3@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 76DD73A67AA for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 22:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.29
X-Spam-Level: 
X-Spam-Status: No, score=-103.29 tagged_above=-999 required=5 tests=[AWL=0.309, 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 NYU31bxeJNZx for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 22:29:00 -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 401403A67B4 for <ietf@ietf.org>; Thu,  6 Jan 2011 22:29:00 -0800 (PST)
Received: by wyf23 with SMTP id 23so17982851wyf.31 for <ietf@ietf.org>; Thu, 06 Jan 2011 22:31:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=nP6tmQrHE6A7P7Lt3ercWJPVXyY8fWL8JVEEsu8xQIM=; b=CSZtVLvUc0QfFoNhBx2iXX0gPP2tZBLygp1Jerl9pJokFC02I3o8RjCrzrk1lFcRJN MjKcC1uPJZpe6+m9rOwBD726FeKWbFKWtvRmvloKl3Qptx4ksZVMNMCqtZyPlLmJ+8d2 6W5JvzH2NrxFUbEQn8vq87p+Lh6GtUQpDxf9g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=coFtQRRmLSmN9xvxqZDY1pBJ0N/QwhXonxanI2fMlh4/HIson+MCwyxA3NlFzgrlIG Y/m7xE1s3wgB36IIZGr/rPZLAf/OwIdvVM7jlmEf4x9jDm8yaEsFnw0UV7aY8wzdrFVI 3xKkOUWzT1jAuV+HGwaVpy0bsobUwxa5fZE8g=
Received: by 10.227.141.138 with SMTP id m10mr155573wbu.66.1294381866500; Thu, 06 Jan 2011 22:31:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 6 Jan 2011 22:30:46 -0800 (PST)
In-Reply-To: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net>
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 7 Jan 2011 01:30:46 -0500
Message-ID: <AANLkTinUhozsniX1OOKyRhSmNy=HzEMJF6Bu=ZmHc1_J@mail.gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
To: Doug Ewell <doug@ewellic.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Bob Braden <braden@isi.edu>, ietf@ietf.org, Lixia Zhang <lixia@cs.ucla.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: Fri, 07 Jan 2011 06:29:02 -0000

I have also seen attempts to make a standard Historic with the
supposed reason being to "clear things out" for the introduction of
some better replacement. That seems like just nonsense to me. If it is
so obvious that a replacement is superior, the replacement document
can do the move of earlier document to Historic...

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA=A0=A0 +1-508-634-2066 (home)
=A0d3e3e3@gmail.com



On Thu, Jan 6, 2011 at 4:45 PM, Doug Ewell <doug@ewellic.org> wrote:
> Lixia Zhang <lixia at cs dot ucla dot edu> wrote:
>
>> PS: on the other hand, what would a "historical status" imply? =A0the id=
eas obsolete?
>
> Every now and then, someone proposes to move a given RFC to Historic,
> not merely to reflect an observation that a process or protocol is
> obsolete, but as an active attempt to deprecate it, regardless of its
> currency or relevance.
>
> I remember a few months ago, it was proposed (evidently not for the
> first time) to move FTP to Historic, on the basis of its lack of
> airtight 21st-century security features, with no consideration for the
> innumerable existing systems and processes that have no need for
> top-notch security, and rely daily on FTP.
>
> I often see comments on this list about whether the "outside world"
> views the IETF as irrelevant. =A0Declaring a commonly used, core process
> or protocol as Historic because something better exists might be a
> perfect example of this.
>
> --
> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From evnikita2@gmail.com  Thu Jan  6 22:37:21 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 93B473A67D3 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 22:37:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.865
X-Spam-Level: 
X-Spam-Status: No, score=-2.865 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599, J_CHICKENPOX_55=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 WZWPoaN+vAe9 for <ietf@core3.amsl.com>; Thu,  6 Jan 2011 22:37:17 -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 50B6C3A67B2 for <ietf@ietf.org>; Thu,  6 Jan 2011 22:37:15 -0800 (PST)
Received: by bwz12 with SMTP id 12so16962335bwz.31 for <ietf@ietf.org>; Thu, 06 Jan 2011 22:39:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=f9LwDDP5HasJW7Q3t5sI+L375i7U/giI6vtjkfktrv4=; b=PAd+uRboRSp/w31jtQFJvMncZgXMX1+fxqPrRMaoYFBORoFWv8fHtpysphLku8GfO4 EilZwJVPL94Jyt2jm1uIvMz3YxLQD2jqzRAzOwS9FQds1Z20fYhImn6kwbX1KhIuXM9Q QNHf0cOCG38wihcsTSjeg0UOOOkgOat/VxaCc=
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=lWulu31UYMWSNUF/5K9wdQA0fGBaYNT9Y7DNlpb7oHt7J4b4nMU8jAfyEQ3GRUfe3o 3o+Z1mQm7NdJpqu46KPxkWw9qt9YVDjTpTs2UMLsbgWVb3r4qgST71+SdjjV2CSZtHTf cxTQ26gh7hQahn8MBKLuBHiPHQeL7FuEkk86Y=
Received: by 10.204.60.195 with SMTP id q3mr5857363bkh.188.1294382360846; Thu, 06 Jan 2011 22:39:20 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id x38sm12614563bkj.13.2011.01.06.22.39.19 (version=SSLv3 cipher=RC4-MD5); Thu, 06 Jan 2011 22:39:20 -0800 (PST)
Message-ID: <4D26B529.8070303@gmail.com>
Date: Fri, 07 Jan 2011 08:39:37 +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: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <AANLkTinUhozsniX1OOKyRhSmNy=HzEMJF6Bu=ZmHc1_J@mail.gmail.com>
In-Reply-To: <AANLkTinUhozsniX1OOKyRhSmNy=HzEMJF6Bu=ZmHc1_J@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Bob Braden <braden@isi.edu>, ietf@ietf.org, Lixia Zhang <lixia@cs.ucla.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: Fri, 07 Jan 2011 06:37:21 -0000

07.01.2011 8:30, Donald Eastlake wrote:
> I have also seen attempts to make a standard Historic with the
> supposed reason being to "clear things out" for the introduction of
> some better replacement. That seems like just nonsense to me. If it is
> so obvious that a replacement is superior, the replacement document
> can do the move of earlier document to Historic...
As I've mentioned before, I think that the problem is the definition of 
Historic status. It is not correct. It duplicates the obsoleted-by 
status (if that can be called like this). It is really inappropriate for 
its real reason - indicating the deprecated (but not obsoleted) docs. 
Moreover, 'obsoleted' means the same as 'deprecated' or 'non-current' 
(see http://www.synonym.com/synonyms/obsolete/ or 
http://dictionary.sensagent.com/obsolete/en-en/#synonyms). So it is a 
problem in RFC2026.

All the best,
Mykyta Yevstifeyev
> Thanks,
> Donald
> =============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street
>   Milford, MA 01757 USA   +1-508-634-2066 (home)
>   d3e3e3@gmail.com
>
>
>
> On Thu, Jan 6, 2011 at 4:45 PM, Doug Ewell<doug@ewellic.org>  wrote:
>> Lixia Zhang<lixia at cs dot ucla dot edu>  wrote:
>>
>>> PS: on the other hand, what would a "historical status" imply?  the ideas obsolete?
>> Every now and then, someone proposes to move a given RFC to Historic,
>> not merely to reflect an observation that a process or protocol is
>> obsolete, but as an active attempt to deprecate it, regardless of its
>> currency or relevance.
>>
>> I remember a few months ago, it was proposed (evidently not for the
>> first time) to move FTP to Historic, on the basis of its lack of
>> airtight 21st-century security features, with no consideration for the
>> innumerable existing systems and processes that have no need for
>> top-notch security, and rely daily on FTP.
>>
>> I often see comments on this list about whether the "outside world"
>> views the IETF as irrelevant.  Declaring a commonly used, core process
>> or protocol as Historic because something better exists might be a
>> perfect example of this.
>>
>> --
>> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
>> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­
>>
>>
>> _______________________________________________
>> 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 pekkas@netcore.fi  Fri Jan  7 05:09:23 2011
Return-Path: <pekkas@netcore.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 007DC3A68BA; Fri,  7 Jan 2011 05:09:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.078
X-Spam-Level: 
X-Spam-Status: No, score=-102.078 tagged_above=-999 required=5 tests=[AWL=-0.479, BAYES_00=-2.599, J_BACKHAIR_34=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 dejIqVvB9AOL; Fri,  7 Jan 2011 05:09:21 -0800 (PST)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id B701A3A68B9; Fri,  7 Jan 2011 05:09:20 -0800 (PST)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id p07DBGFH020761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Jan 2011 15:11:17 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id p07DBEut020758; Fri, 7 Jan 2011 15:11:16 +0200
Date: Fri, 7 Jan 2011 15:11:14 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: ietf@ietf.org
Subject: Re: Last Call: draft-ietf-isis-ieee-aq (IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging) to Proposed Standard
In-Reply-To: <20110104153454.23796.26316.idtracker@localhost>
Message-ID: <alpine.LRH.2.02.1101071509060.20267@netcore.fi>
References: <20110104153454.23796.26316.idtracker@localhost>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: clamav-milter 0.96.5 at otso.netcore.fi
X-Virus-Status: Clean
Cc: isis-chairs@tools.ietf.org, isis-wg@ietf.org, draft-ietf-isis-ieee-aq@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, 07 Jan 2011 13:09:23 -0000

On Tue, 4 Jan 2011, The IESG wrote:
> - 'IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging '
>   <draft-ietf-isis-ieee-aq-03.txt> as a Proposed Standard
...
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-isis-ieee-aq-03.txt

This is an ops-dir review of draft-ietf-isis-ieee-aq-03.

The document provides an overview of IEEE 802.1aq (shortest path Ethernet
bridging using IS-IS) and specifically defines IS-IS codepoints for use.
802.1aq is orthogonal with TRILL wg solutions but both solve somewhat
similar issues, i.e. Ethernet network scaling and load balancing
optimizations.

Secure use of 802.1aq will probably require manual configuration of IS-IS
authentication in each device or IS-IS filtering in client ports.
The draft does not discuss interoperability with traditional Ethernet, i.e.,
how will this work in an environment where all the equipment does not
support it.

I find the document close to ready to publish after minor text improvements
and e.g. definiting how a newly allocated IANA codepoint TLV subspace is to
be managed by IANA.

Some more detailed comments below.

substantial
-----------

17. Security Considerations

    This document adds no additional security risks to IS-IS, nor does
    it provide any additional security for IS-IS.

.. while true, this is probably a bit weak. Given that the document included
a quite detailed description of 802.1aq (not just IS-IS extensions), some
brief summary would have been nice.

Some notes about this:
  - This protocol is apparently intended to be used in a zero-conf
    environment.  IS-IS authentication cannot be used without manual
    configuration. Hence a warning label would likely be useful.  For
    example, I suppose there is nothing to prevent a UNI port from
    participating in IS-IS and 802.1aq.

  - The increase of state due to broadcast/multicast is a new potential
    concern, but really not that much different from the current MAC address
    flooding issues.

  - One particular thing that comes to mind is intentional clash of SPVID
    values described in S 14.1. By claiming the highest Bridge Identifier, a
    bridge could deny all other bridges all service, right?


semi-editorial
--------------

    FDB            Filtering Information Base: {DA/VID}->{next hops}
...
4. 802.1aq Overview

    802.1aq utilizes 802.1Q based Ethernet bridging. The filtering
    database (FDB) is populated as a consequence of the forwarding
    computed from the IS-IS database.

.. is this a typo?  The established spell-out form of FDB is Forwarding
Database (storing MAC<->port mappings).  Is overloading it intentional?

4.7. Data Path SPBV Multicast


    C-DA multicast addresses may be advertised from SPBV UNI ports.
    These may be configured or learned through MMRP. The MMRP protocol

... there is no reference or spell-out in abbreviations for "MMRP". I
suppose youre referring to Multiple MAC registration protocol defined in
IEEE 802.1ak-2007.

18. IANA Considerations


    Note that the NLPID value 0xC1 [NLPID] used in the IIH PDUs has
    already been assigned by IANA for the purpose of 802.1aq therefore
    no further action is required for this code point.

.. true but I suppose it wouldn't hurt to add a reference to this RFC there,
given that the defining RFC-to-be does not include any other reference other
than "802.1aq".

       The MT-Capability TLV is the only TLV requiring a new sub-registry.
    Type value 144 is requested with a starting sub-tlv value of 1.

.. as you're creating a new registry, I suppose you should also define the
registration policy for it?  Most IS-IS TLV codepoints appear to have
"Expert review", so maybe that would be appropriate here as well.

editorial
---------

Traditionally [references] are not appropriate in Abstract.

It is a bit strange to see an empty Introduction section :-). Most of
Introduction is provided in Overview (S 4) though.



From lear@cisco.com  Fri Jan  7 06:11:16 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 91FCD3A68D2 for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 06:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.191
X-Spam-Level: 
X-Spam-Status: No, score=-110.191 tagged_above=-999 required=5 tests=[AWL=0.408, 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 CKGXCu330npq for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 06:11: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 035333A68CD for <ietf@ietf.org>; Fri,  7 Jan 2011 06:11:06 -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: Av0EADuuJk2Q/khNgWdsb2JhbACDd6AwFgEWIiSjZ4pTjWWBIYM3dASLCQ
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 07 Jan 2011 14:13:13 +0000
Received: from ams3-vpn-dhcp4836.cisco.com (ams3-vpn-dhcp4836.cisco.com [10.61.82.227]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p07EDCJ8029125; Fri, 7 Jan 2011 14:13:12 GMT
Message-ID: <4D271F81.2060302@cisco.com>
Date: Fri, 07 Jan 2011 15:13:21 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net>	<AANLkTinUhozsniX1OOKyRhSmNy=HzEMJF6Bu=ZmHc1_J@mail.gmail.com> <4D26B529.8070303@gmail.com>
In-Reply-To: <4D26B529.8070303@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bob Braden <braden@isi.edu>, ietf@ietf.org, Lixia Zhang <lixia@cs.ucla.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: Fri, 07 Jan 2011 14:11:16 -0000

On 1/7/11 7:39 AM, Mykyta Yevstifeyev wrote:
> 07.01.2011 8:30, Donald Eastlake wrote:
>> I have also seen attempts to make a standard Historic with the
>> supposed reason being to "clear things out" for the introduction of
>> some better replacement. That seems like just nonsense to me. If it is
>> so obvious that a replacement is superior, the replacement document
>> can do the move of earlier document to Historic...
> As I've mentioned before, I think that the problem is the definition
> of Historic status. It is not correct. It duplicates the obsoleted-by
> status (if that can be called like this). It is really inappropriate
> for its real reason - indicating the deprecated (but not obsoleted)
> docs. Moreover, 'obsoleted' means the same as 'deprecated' or
> 'non-current' (see http://www.synonym.com/synonyms/obsolete/ or
> http://dictionary.sensagent.com/obsolete/en-en/#synonyms). So it is a
> problem in RFC2026.

As an exercise some time ago, we looked at the 2000 RFCs to determine
which of the Proposed Standards could be deprecated.  We found 61 out of
125 such memos could be marked as Historic, the point being that we
wanted to the RFC Editor series to reflect the fact that in the IETF's
opinion, nobody was using the work.  Not that the work was bad or
broken.  In this case, it would have been impractical to list 61
documents as "Obsoletes/Obsoleted-by".  See RFC-4450 for a more complete
description of what happened.

Eliot

From ajs@shinkuro.com  Fri Jan  7 06:13:42 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 AB8D63A68CB for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 06:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.98
X-Spam-Level: 
X-Spam-Status: No, score=-99.98 tagged_above=-999 required=5 tests=[AWL=-0.380, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_INFO=1.448, 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 6PShDRI7KtiQ for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 06:13:41 -0800 (PST)
Received: from mail.yitter.info (unknown [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id C2D5A3A68BE for <ietf@ietf.org>; Fri,  7 Jan 2011 06:13:41 -0800 (PST)
Received: from crankycanuck.ca (unknown [74.198.87.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id D4A741ECB408 for <ietf@ietf.org>; Fri,  7 Jan 2011 14:15:46 +0000 (UTC)
Date: Fri, 7 Jan 2011 09:15:43 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: Re: Old transport-layer protocols to Historic?
Message-ID: <20110107141542.GB34186@shinkuro.com>
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <AANLkTinUhozsniX1OOKyRhSmNy=HzEMJF6Bu=ZmHc1_J@mail.gmail.com> <4D26B529.8070303@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D26B529.8070303@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, 07 Jan 2011 14:13:42 -0000

I'm not keen to start a language war, but. . .

On Fri, Jan 07, 2011 at 08:39:37AM +0200, Mykyta Yevstifeyev wrote:

> Moreover, 'obsoleted' means the same as 'deprecated' or 'non-current'  
> (see http://www.synonym.com/synonyms/obsolete/ or  
> http://dictionary.sensagent.com/obsolete/en-en/#synonyms). So it is a  
> problem in RFC2026.

. . .I fully disagree with that, regardless of what those claims of
synonymy say.  To deprecate something is to express disapproval.  To
mark something as obsolete doesn't do that; it merely says that the
marked thing is outdated.  There is a useful distinction here worth
maintaining.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From ben@nostrum.com  Thu Jan  6 15:30:06 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 6CFBC3A6D23; Thu,  6 Jan 2011 15:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.98
X-Spam-Level: 
X-Spam-Status: No, score=-100.98 tagged_above=-999 required=5 tests=[AWL=-0.680, 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 p2gPQrHyXGej; Thu,  6 Jan 2011 15:30:02 -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 EE0543A6F35; Thu,  6 Jan 2011 15:30:01 -0800 (PST)
Received: from [10.0.1.22] (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 p06NW7CF088397 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jan 2011 17:32:07 -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-ltans-xmlers-08
Date: Thu, 6 Jan 2011 17:32:03 -0600
Message-Id: <9D732565-9596-4451-BF74-DE4CA0FC9B27@nostrum.com>
To: General Area Review Team <gen-art@ietf.org>, draft-ietf-ltans-xmlers.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1082)
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, 07 Jan 2011 08:03:42 -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: Thu, 06 Jan 2011 23:30:07 -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-ltans-xmlers-08
Reviewer: Ben Campbell
Review Date: 11-01-06
IETF LC End Date: 11-01-11

Summary:

This draft is on the right track for proposed standard, but I think it =
needs more editing prior to publication.

Note that I have not attempted to verify the XML schema or examples. =
These should be mechanically verified prior to publication, if they have =
not already been done so.

-Major issues:

None

-Minor issues:

-- General: I'd like to see some more architectural background. Who are =
the actors? What are their roles? You mention the time stamp =
authorities, but not much else. Who are the verifiers? How to =
Certificate Authorities fit in?

-- general: I'd like to see at least one complete example.

-- 3.1.2, 1st paragraph: "exact time (obtained from trusted time source) =
of Time-Stamping."

How exact?

-- 3.1.2, paragraph before example: "The Attribute type must be used"

Normative?

-- 3.1.3, 1st paragraph:

Is that a normative SHOULD? Can you offer examples or an explanation of =
when thus might not be possible?

-- 3.1.3, 2nd paragraph: "Following values SHOULD be used as identifiers =
for the Type attribute"

Just should? Don't you mean to say the type MUST be something in the =
IANA registry?

-- 4.1, last paragraph "must be valid at the present time"

Normative?

-- 4.1.1, general:

(comments also apply to the Canonicalization method URL)

What does the URI represent? Does that point to the actual definition of =
the algorithm? Can I make up arbitrary ones? Is there a registry? What =
schemes are allowed and/or reasonable?

Are there any required-to-support algorithms?

-- 4.1.1, 2nd paragraph: "those must be used as defined in [RFC3275] and =
[RFC4051]"

Normative?

-- 4.1.1, last paragraph:

What do you mean by equal? The same algorithm? One of equal strength? =
How do you determine relative strength?

-- 4.2.1, last paragraph: "The new ATS and its hash tree MUST use the =
same digest algorithm as the preceding one"

Does this imply they can't change to a new algorithm? What if an =
algorithm becomes deprecated over time?

-- 7, 1st paragraph: "have to be considered by verifying components"

Normative?

-- 7, 4th paragraph:

should "recommended" and "must" be normative?

Why different TSAs? Wouldn't different algorithms be good enough? Are =
you assuming a given TSA is limited to a single algorithm at a time?

-- 7, last paragraph: "Time-Stamps should have the same or higher =
quality"

Normative?








-Nits/editorial comments:

-- General: The draft could really use another editing pass to check for =
punctuation errors and awkward style. There's lots of missing or misused =
commas, missing articles, passive voice that obscures actors, etc. It =
looks like sections were edited in isolation from each other, with =
redundant assertions (how many times do you need to open with "time =
stamps prove the existence of data at a particular time"), inconsistent =
use of acronyms, etc.  I will highlight some examples, but they are by =
no means exhaustive.

Much of this could be handled by the RFC editor, but its best to =
minimize their work load, and better to minimize the opportunity for =
outside editors to misconstrue your meaning.

-- General: The pagination and vertical spacing seem strange.

-- Abstract : "This document specifies XML syntax and processing rules =
for creating evidence for long-term non- repudiation of existence of =
data."

I assume this is for non-repudiation of more than just the "existence" =
of the data, right? Also, please expand the acronyms in the abstract.

-- section 1: "define XML Schema and processing rules for Evidence =
Record Syntax in XML format. The document is related to initial ASN.1 =
syntax"

Missing articles. Also, since you use an acronym for this later, why not =
declare it here?

-- 1.1, first paragraph: "Such data and non-repudiable proof of =
existence must endure for long periods of time, even when information to =
prove data existence and integrity weakens or ceases to exist."

That seems to say the proof must continue to exist past it's own =
existence. I assume that is not the intent.

-- "digital signatures defined in [RFC5652] for example do not provide =
absolute reliability"

Missing commas around "for example"

-- 2nd paragraph: "All integrity and authenticity related techniques =
used today suffer from the same problem of time related reliability =
degradation including techniques for Time-Stamping, which are generally =
recognized as data existence and integrity proof mechanisms."

I find it hard to parse that sentence.=20

-- "Some of the problems might not even be technically related like a =
decomposing Time-Stamping authority."

Technically related to what? Do you mean to say "might not even be of a =
technical nature..."? Also, I'm not sure I understand "decomposing" in =
this context.

-- 3rd paragraph: " introduced for example by"

Missing commas

-- "long term signature syntaxes like [RFC5126]"

Missing words? (i.e. .... syntaxes like those defined in...)

-- "Long term signature syntaxes and processing rules address mostly the =
long term endurance of digital signatures..."

Seems self-redundant

-- 4th paragraph:

Please expand XMLERS on first mention. Also, this is not consistent with =
the acronym used in the abstract.

-- 6th paragraph: "support for example import"

commas

-- section 1.2, first paragraph

Multiple missing articles

-- 3rd paragraph: "Evidence Record maintains a close relationship to =
Time-Stamping techniques"

I doubt it "maintains" anything. It think you mean to say "is closely =
related to..."

-- 1.2, 4th paragraph: "packed into a structure called a "hash tree""

The text appears to be trying to introduce the concept of a "hash tree", =
but that's already been mentioned several times.

-- 1.2, 5th paragraph: "collected evidence data must be monitored and =
renewed before such events occur"

monitored by whom?

-- 1.3, 2nd paragraph:

"multitude" connotes a large number. I think you just mean "set". Also, =
why the parentheses?

-- 1.3, definition of "canonicalization"

This seems like a definition of "canonicalization rules". Wouldn't =
"canonicalization" refer to the act of following the rules, rather than =
the rules themselves?

Also, the draft needs a definition for "canonical form"

-- section 2, first paragraph:

It would be nice to have definitions of integrity and non-reputability =
in the terminology section. Maybe even "existence" as used in the =
context.

-- section 2, first paragraph: "unit of data, which is to be used"

I think you mean "unit of data that is to be used"

-- section 2, 1st paragraph: "Time-Stamp Tokens obtained from the =
Time-Stamping Authority (TSA)"

Obtained by whom?

-- section 2, 2nd paragraph "number of reasons"

More than one example would be nice.

-- 2.1, 1st paragraph: "CRLs or OCSP"

Expand on first mention

-- 2.1, paragraph made up of "<CanonicalizationMethod> is a required =
element that specifies the canonicalization algorithm applied over the =
archive data in case of XML data objects, <ArchiveTimeStampSequence> or =
<TimeStamp> element prior to performing digest value calculations."

Sentence does not make sense. Are therre missing words?

-- 2.2, 3rd paragraph after numbered list: "the application not defined =
in this draft"

I'm not sure what you mean. Is there a specific application defined =
elsewhere, or are you just trying to say it is out of scope?

-- 2.2, 2nd to last paragraph:

I'm not sure what this is an example of. It just looks like a =
continuation of the section text.

-- "provide also evidence"

also provide evidence

-- 3.1.1, third to last paragraph "When a single Time-Stamp is obtained =
for a set of archive objects, a hash tree MUST be constructed to =
generate a single hash value to bind all archive objects from that group =
and then a reduced hash tree MUST be extracted from the hash tree for =
each archive object respectively (see Section 3.2.1)."

Meaning obscured by passive voice. Who or what MUST generate and/or =
extract hash trees?

-- 3.1.1, 2nd to last paragraph: "For example, the text value"

Is this a second example, or a continuation of the previous one?

-- 3.1.2, 1st paragraph "Since at the time being there is no standard"

Won't is statement become false when this draft is published as an RFC?

-- 3.1.2, paragraph before example: "in particular, e.g."

"in particular" or "e.g", not both.

-- 3.2.1, 2nd paragraph: "This is the case:"

Confusing. Do you mean to say "The values are unequal when either of the =
following are true:"?

-- 3.2.1, 1st bullet list entry "is having"

has

-- 3.2.1, paragraph before 2nd numbered list: "is built from bottom to =
the root."

Leaves to the root, or bottom to top. Also, who builds it?

-- "The leaves represent the digest values of the archive objects:"

It looks like you mean this sentence to introduce the following list, =
but it doesn't seem to do so.

-- List entry 3: Need to define N. Is this the order of the tree?

-- 3.3, list item 2: "If an additional proof is necessary that the =
Archive Time-Stamp relates to a data object group (e.g. a document and =
all its digital signatures), it can also be verified that only the hash =
values of the given data objects are in the first hash value list."

I don't understand this sentence

-- 3.3, numbered list:

Is there a need to distinguish between kinds of negative results?

-- 4.1.2, last paragraph: "it is recommended to use c14n- 20010315."

Reference?

-- 4.2 "Archive Time-Stamps have to be renewed "

by whom?

-- section 7, "Secure Algorithms", etc

Should these be numbered subsections?

-- 7, 1st paragraph: "have to be considered by verifying components"

They need to be considered by people, not components, right? Also, is =
this a verification issue or a generation issue?

-- section 8, 1st paragraph: "namespace has been registered in the IANA =
XML Registry."

It's already been registered, or are you instrucing IANA to register it? =
(repeats several times in section)

-- Appendix A, general:

Why is this in an appendix? It seems central to the draft. lots of =
readers will stop reading when they get to the references sections.





From ben@nostrum.com  Thu Jan  6 16:13:32 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 6D0DA3A6F41; Thu,  6 Jan 2011 16:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.962
X-Spam-Level: 
X-Spam-Status: No, score=-100.962 tagged_above=-999 required=5 tests=[AWL=-0.662, 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 gUp+vT4nUJgi; Thu,  6 Jan 2011 16:13:30 -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 F102B3A6F3E; Thu,  6 Jan 2011 16:13:29 -0800 (PST)
Received: from [10.0.1.22] (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 p070FX1j091564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Jan 2011 18:15:34 -0600 (CST) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-ltans-xmlers-08
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <9D732565-9596-4451-BF74-DE4CA0FC9B27@nostrum.com>
Date: Thu, 6 Jan 2011 18:15:33 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA41737E-E376-476E-8044-BF872A7135D5@nostrum.com>
References: <9D732565-9596-4451-BF74-DE4CA0FC9B27@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, 07 Jan 2011 08:03:42 -0800
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-ltans-xmlers.all@tools.ietf.org, 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, 07 Jan 2011 00:13:32 -0000

Also note that sending to draft-ietf-ltans-xmlers.all@tools.ietf.org =
resulted in a "user unknown" delivery failure report for =
tobias.gondrom@opentext.com . That's not the address listed for him in =
the draft, either the address in the draft forwards to a dead address, =
or the tools alias for the draft is incorrect. In either case, something =
is broken somewhere.

Thanks!

Ben.

On Jan 6, 2011, at 5:32 PM, Ben Campbell wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> Document: draft-ietf-ltans-xmlers-08
> Reviewer: Ben Campbell
> Review Date: 11-01-06
> IETF LC End Date: 11-01-11
>=20
> Summary:
>=20
> This draft is on the right track for proposed standard, but I think it =
needs more editing prior to publication.
>=20
> Note that I have not attempted to verify the XML schema or examples. =
These should be mechanically verified prior to publication, if they have =
not already been done so.
>=20
> -Major issues:
>=20
> None
>=20
> -Minor issues:
>=20
> -- General: I'd like to see some more architectural background. Who =
are the actors? What are their roles? You mention the time stamp =
authorities, but not much else. Who are the verifiers? How to =
Certificate Authorities fit in?
>=20
> -- general: I'd like to see at least one complete example.
>=20
> -- 3.1.2, 1st paragraph: "exact time (obtained from trusted time =
source) of Time-Stamping."
>=20
> How exact?
>=20
> -- 3.1.2, paragraph before example: "The Attribute type must be used"
>=20
> Normative?
>=20
> -- 3.1.3, 1st paragraph:
>=20
> Is that a normative SHOULD? Can you offer examples or an explanation =
of when thus might not be possible?
>=20
> -- 3.1.3, 2nd paragraph: "Following values SHOULD be used as =
identifiers for the Type attribute"
>=20
> Just should? Don't you mean to say the type MUST be something in the =
IANA registry?
>=20
> -- 4.1, last paragraph "must be valid at the present time"
>=20
> Normative?
>=20
> -- 4.1.1, general:
>=20
> (comments also apply to the Canonicalization method URL)
>=20
> What does the URI represent? Does that point to the actual definition =
of the algorithm? Can I make up arbitrary ones? Is there a registry? =
What schemes are allowed and/or reasonable?
>=20
> Are there any required-to-support algorithms?
>=20
> -- 4.1.1, 2nd paragraph: "those must be used as defined in [RFC3275] =
and [RFC4051]"
>=20
> Normative?
>=20
> -- 4.1.1, last paragraph:
>=20
> What do you mean by equal? The same algorithm? One of equal strength? =
How do you determine relative strength?
>=20
> -- 4.2.1, last paragraph: "The new ATS and its hash tree MUST use the =
same digest algorithm as the preceding one"
>=20
> Does this imply they can't change to a new algorithm? What if an =
algorithm becomes deprecated over time?
>=20
> -- 7, 1st paragraph: "have to be considered by verifying components"
>=20
> Normative?
>=20
> -- 7, 4th paragraph:
>=20
> should "recommended" and "must" be normative?
>=20
> Why different TSAs? Wouldn't different algorithms be good enough? Are =
you assuming a given TSA is limited to a single algorithm at a time?
>=20
> -- 7, last paragraph: "Time-Stamps should have the same or higher =
quality"
>=20
> Normative?
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> -Nits/editorial comments:
>=20
> -- General: The draft could really use another editing pass to check =
for punctuation errors and awkward style. There's lots of missing or =
misused commas, missing articles, passive voice that obscures actors, =
etc. It looks like sections were edited in isolation from each other, =
with redundant assertions (how many times do you need to open with "time =
stamps prove the existence of data at a particular time"), inconsistent =
use of acronyms, etc.  I will highlight some examples, but they are by =
no means exhaustive.
>=20
> Much of this could be handled by the RFC editor, but its best to =
minimize their work load, and better to minimize the opportunity for =
outside editors to misconstrue your meaning.
>=20
> -- General: The pagination and vertical spacing seem strange.
>=20
> -- Abstract : "This document specifies XML syntax and processing rules =
for creating evidence for long-term non- repudiation of existence of =
data."
>=20
> I assume this is for non-repudiation of more than just the "existence" =
of the data, right? Also, please expand the acronyms in the abstract.
>=20
> -- section 1: "define XML Schema and processing rules for Evidence =
Record Syntax in XML format. The document is related to initial ASN.1 =
syntax"
>=20
> Missing articles. Also, since you use an acronym for this later, why =
not declare it here?
>=20
> -- 1.1, first paragraph: "Such data and non-repudiable proof of =
existence must endure for long periods of time, even when information to =
prove data existence and integrity weakens or ceases to exist."
>=20
> That seems to say the proof must continue to exist past it's own =
existence. I assume that is not the intent.
>=20
> -- "digital signatures defined in [RFC5652] for example do not provide =
absolute reliability"
>=20
> Missing commas around "for example"
>=20
> -- 2nd paragraph: "All integrity and authenticity related techniques =
used today suffer from the same problem of time related reliability =
degradation including techniques for Time-Stamping, which are generally =
recognized as data existence and integrity proof mechanisms."
>=20
> I find it hard to parse that sentence.=20
>=20
> -- "Some of the problems might not even be technically related like a =
decomposing Time-Stamping authority."
>=20
> Technically related to what? Do you mean to say "might not even be of =
a technical nature..."? Also, I'm not sure I understand "decomposing" in =
this context.
>=20
> -- 3rd paragraph: " introduced for example by"
>=20
> Missing commas
>=20
> -- "long term signature syntaxes like [RFC5126]"
>=20
> Missing words? (i.e. .... syntaxes like those defined in...)
>=20
> -- "Long term signature syntaxes and processing rules address mostly =
the long term endurance of digital signatures..."
>=20
> Seems self-redundant
>=20
> -- 4th paragraph:
>=20
> Please expand XMLERS on first mention. Also, this is not consistent =
with the acronym used in the abstract.
>=20
> -- 6th paragraph: "support for example import"
>=20
> commas
>=20
> -- section 1.2, first paragraph
>=20
> Multiple missing articles
>=20
> -- 3rd paragraph: "Evidence Record maintains a close relationship to =
Time-Stamping techniques"
>=20
> I doubt it "maintains" anything. It think you mean to say "is closely =
related to..."
>=20
> -- 1.2, 4th paragraph: "packed into a structure called a "hash tree""
>=20
> The text appears to be trying to introduce the concept of a "hash =
tree", but that's already been mentioned several times.
>=20
> -- 1.2, 5th paragraph: "collected evidence data must be monitored and =
renewed before such events occur"
>=20
> monitored by whom?
>=20
> -- 1.3, 2nd paragraph:
>=20
> "multitude" connotes a large number. I think you just mean "set". =
Also, why the parentheses?
>=20
> -- 1.3, definition of "canonicalization"
>=20
> This seems like a definition of "canonicalization rules". Wouldn't =
"canonicalization" refer to the act of following the rules, rather than =
the rules themselves?
>=20
> Also, the draft needs a definition for "canonical form"
>=20
> -- section 2, first paragraph:
>=20
> It would be nice to have definitions of integrity and non-reputability =
in the terminology section. Maybe even "existence" as used in the =
context.
>=20
> -- section 2, first paragraph: "unit of data, which is to be used"
>=20
> I think you mean "unit of data that is to be used"
>=20
> -- section 2, 1st paragraph: "Time-Stamp Tokens obtained from the =
Time-Stamping Authority (TSA)"
>=20
> Obtained by whom?
>=20
> -- section 2, 2nd paragraph "number of reasons"
>=20
> More than one example would be nice.
>=20
> -- 2.1, 1st paragraph: "CRLs or OCSP"
>=20
> Expand on first mention
>=20
> -- 2.1, paragraph made up of "<CanonicalizationMethod> is a required =
element that specifies the canonicalization algorithm applied over the =
archive data in case of XML data objects, <ArchiveTimeStampSequence> or =
<TimeStamp> element prior to performing digest value calculations."
>=20
> Sentence does not make sense. Are therre missing words?
>=20
> -- 2.2, 3rd paragraph after numbered list: "the application not =
defined in this draft"
>=20
> I'm not sure what you mean. Is there a specific application defined =
elsewhere, or are you just trying to say it is out of scope?
>=20
> -- 2.2, 2nd to last paragraph:
>=20
> I'm not sure what this is an example of. It just looks like a =
continuation of the section text.
>=20
> -- "provide also evidence"
>=20
> also provide evidence
>=20
> -- 3.1.1, third to last paragraph "When a single Time-Stamp is =
obtained for a set of archive objects, a hash tree MUST be constructed =
to generate a single hash value to bind all archive objects from that =
group and then a reduced hash tree MUST be extracted from the hash tree =
for each archive object respectively (see Section 3.2.1)."
>=20
> Meaning obscured by passive voice. Who or what MUST generate and/or =
extract hash trees?
>=20
> -- 3.1.1, 2nd to last paragraph: "For example, the text value"
>=20
> Is this a second example, or a continuation of the previous one?
>=20
> -- 3.1.2, 1st paragraph "Since at the time being there is no standard"
>=20
> Won't is statement become false when this draft is published as an =
RFC?
>=20
> -- 3.1.2, paragraph before example: "in particular, e.g."
>=20
> "in particular" or "e.g", not both.
>=20
> -- 3.2.1, 2nd paragraph: "This is the case:"
>=20
> Confusing. Do you mean to say "The values are unequal when either of =
the following are true:"?
>=20
> -- 3.2.1, 1st bullet list entry "is having"
>=20
> has
>=20
> -- 3.2.1, paragraph before 2nd numbered list: "is built from bottom to =
the root."
>=20
> Leaves to the root, or bottom to top. Also, who builds it?
>=20
> -- "The leaves represent the digest values of the archive objects:"
>=20
> It looks like you mean this sentence to introduce the following list, =
but it doesn't seem to do so.
>=20
> -- List entry 3: Need to define N. Is this the order of the tree?
>=20
> -- 3.3, list item 2: "If an additional proof is necessary that the =
Archive Time-Stamp relates to a data object group (e.g. a document and =
all its digital signatures), it can also be verified that only the hash =
values of the given data objects are in the first hash value list."
>=20
> I don't understand this sentence
>=20
> -- 3.3, numbered list:
>=20
> Is there a need to distinguish between kinds of negative results?
>=20
> -- 4.1.2, last paragraph: "it is recommended to use c14n- 20010315."
>=20
> Reference?
>=20
> -- 4.2 "Archive Time-Stamps have to be renewed "
>=20
> by whom?
>=20
> -- section 7, "Secure Algorithms", etc
>=20
> Should these be numbered subsections?
>=20
> -- 7, 1st paragraph: "have to be considered by verifying components"
>=20
> They need to be considered by people, not components, right? Also, is =
this a verification issue or a generation issue?
>=20
> -- section 8, 1st paragraph: "namespace has been registered in the =
IANA XML Registry."
>=20
> It's already been registered, or are you instrucing IANA to register =
it? (repeats several times in section)
>=20
> -- Appendix A, general:
>=20
> Why is this in an appendix? It seems central to the draft. lots of =
readers will stop reading when they get to the references sections.
>=20
>=20
>=20
>=20


From daedulus@btconnect.com  Fri Jan  7 10:21:20 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 17E823A67AF for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 10:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  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 NSNqwWyeQjqu for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 10:21:18 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by core3.amsl.com (Postfix) with ESMTP id D83503A67A1 for <ietf@ietf.org>; Fri,  7 Jan 2011 10:21:17 -0800 (PST)
Received: from host81-156-207-254.range81-156.btcentralplus.com (HELO pc6) ([81.156.207.254]) by c2beaomr06.btconnect.com with SMTP id BMU69153; Fri, 07 Jan 2011 18:23:05 +0000 (GMT)
Message-ID: <019701cbae8f$18b284a0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Lixia Zhang" <lixia@cs.ucla.edu>, "Bob Braden" <braden@isi.edu>
References: <4D2556C9.9020901@gmail.com> <4D2628AB.3080003@isi.edu> <59CD4CD4-9E0B-4B78-BB60-249DE018F7F1@cs.ucla.edu>
Subject: Re: Old transport-layer protocols to Historic?
Date: Fri, 7 Jan 2011 18:04:46 +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.4D275A08.0125, actions=TAG
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020A.4D275A09.020E,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@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, 07 Jan 2011 18:21:20 -0000

----- Original Message -----
From: "Lixia Zhang" <lixia@cs.ucla.edu>
To: "Bob Braden" <braden@isi.edu>
Cc: <ietf@ietf.org>
Sent: Thursday, January 06, 2011 10:08 PM
>
> On Jan 6, 2011, at 12:40 PM, Bob Braden wrote:
> >
> > Historic might imply that they were once in service, but have later been
replaced/deprecated. In fact, these protocols were always, and are still,
*experimental*.  It would seem logical to assign them the Experimental category
and be done with it.
> >
> > Bob Braden
>
> I would like to second Bob's position here.
>
> as a co-author for  NETBLT (RFC998): NETBLT was out of a research effort to
answer the question: can we *fully* utilize long delay, high bandwidth (and
potentially error prone) networks?  NETBLT says and here is one way to do it.
> Over the years (it's published in 1987) I have received comments from many
people saying that they learned something interesting or even useful from
NETBLT. The NETBLT paper (SIGCOMM 1987) got cited over 200 times.
>
> As RFC998 stated clearly:
>
>    This document is published for discussion and comment, and does not
>    constitute a standard.  The proposal may change and certain parts of
>    the protocol have not yet been specified; implementation of this
>    document is therefore not advised.
>
> I don't see any harm to keep it as is.

Which is more or less the opinion I see expressed on the tsvwg list.

Perhaps it needs raising it on yet other lists in order to get
different answers:-)

Tom Petch

>
> Lixia
> PS: on the other hand, what would a "historical status" imply?  the ideas
obsolete?
>
>
> > On 1/5/2011 9:44 PM, Mykyta Yevstifeyev wrote:
> >> Hello all,
> >>
> >> There have been a discussion on tsvwg mailing list about old transport
> >> layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT
> >> (RFC998). Initially there have been proposed to define IANA
> >> considerations for them. But after a discussion it was found out that it
> >> would be better to move them to Historic. I am writing to request more
> >> wider discussion on this topic.
> >>
> >> There is quite strong consensus that IRTP should be Historic. There is a
> >> registered draft on this topic:
> >>
> >> https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/
> >>
> >> But as for others it should be discussed. Moreover, maybe anyone knows
> >> some other old transport-layer protocols that are no longer in use?
> >>
> >> Please copy tour answer to tsvwg@ietf.org
> >>
> >> All the best,
> >> Mykyta Yevstifeyev
> >>


From rja.lists@gmail.com  Fri Jan  7 11:22:02 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 0C19C3A6927 for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 11:22:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.412
X-Spam-Level: 
X-Spam-Status: No, score=-3.412 tagged_above=-999 required=5 tests=[AWL=0.188,  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 VAzhC0CM2ZHx for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 11:22:01 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 0805F3A68EA for <ietf@ietf.org>; Fri,  7 Jan 2011 11:22:00 -0800 (PST)
Received: by vws7 with SMTP id 7so7049646vws.31 for <ietf@ietf.org>; Fri, 07 Jan 2011 11:24:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=tBx/h6svusIl7A7bVw+ezX4q8HReb3NPHUy8tJVy+Ko=; b=fLpG7iMU5NTadgC9mY6FWyIMPQ04xTlhqyFPg+32RoOSpEtCraF30KxlxsqVHlns/Y gFp72wjc9PscM1hKDurrH3eT05bTKlYHl1SiYX6u0Ks8LlrNnnj1LWMwPxqIaoG6SQ2X 6QBrxK7Lzs+5JvwLd2WdncVqh8iTzVaxFoTBw=
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=kpuER9GKp4dzeM6CJCYhhkJCBbUJ8l+LpwOpM5l4aAoUyVFRwsAAONpi8z626TX0i4 1JZ6yvBdQomJNbJBjjUjk7yllHUc9dGw8kzYY6eY3jYLh+YqX3CcSpVKrfo3GGTXdOwe PKu69ilrQhNKDYzQhU7xeOb5ybDtOuohrVvCI=
Received: by 10.220.74.73 with SMTP id t9mr6267866vcj.186.1294428246171; Fri, 07 Jan 2011 11:24:06 -0800 (PST)
Received: from vi-mhowell55.leclairryan.com ([38.103.42.150]) by mx.google.com with ESMTPS id c15sm5791138vcs.31.2011.01.07.11.24.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 07 Jan 2011 11:24:04 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Old transport-layer protocols to Historic?
Date: Fri, 7 Jan 2011 14:24:01 -0500
Message-Id: <29CD5F7B-306F-4D49-B2FF-43F8F71422D3@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: Fri, 07 Jan 2011 19:22:02 -0000

Before today, Bob Braden wrote:
> Historic might imply that they were once in service, 
> but have later been replaced/deprecated. In fact, these 
> protocols were always, and are still, *experimental*. 
> It would seem logical to assign them the Experimental 
> category and be done with it.

+1


Subsequently, Mykyta Yevstifeyev wrote:
> As I've mentioned before, I think that the problem is the 
> definition of Historic status. It is not correct.

I disagree that the definition of Historic status is incorrect.
Separately, I think there is an underlying procedural confusion 
lurking here.  

First, it is important to recall that not all RFCs are 
IETF RFCs.

Second, many RFCs (both long ago and continuing now) were 
published as Individual Submissions to the RFC-Editor, 
or by the IAB, or by the IRTF.  Such RFCs are not IETF RFCs.

Meanwhile, moving a document from some status to Historic 
is most frequently an IETF/IESG process (and having the IESG
make the reclassification seems to be what was suggested 
for these ancient RFCs).  However, the IESG lacks authority 
to change unilaterally the status of a non-IETF-track 
RFC.

This is why, for example, it is important that the recent 
I-Ds about deprecating RFC-1320 and RFC-1321, the 
Informational status Individual Submission track RFCs 
that specify MD4 and MD5 respectively, already specifically 
note that the author(s) of the original RFCs agree(s) 
to the reclassification from Informational status to 
Historic status. [1]

As an earlier note from Bob Braden to this list observed, 
<http://www.ietf.org/mail-archive/web/ietf/current/msg65034.html>
the 3 ancient RFCs being discussed are experimental 
(i.e. not on the IETF standards-track). 

So far as I know (NB: I wasn't involved with the 4 RFCs 
being discussed in this thread :-) none of the 4 RFCs being 
discussed in this thread was published on the IETF track.

Yours,

Ran


[1] An Aside: 
I agree that the reclassification is sensible technically, 
and am very happy that the author of the I-Ds proposing 
reclassification has obtained consent from the original 
author(s), and am also very happy that the original authors
agreed to the reclassification of their non-IETF RFCs.
Following the correct process is important.



From bob.hinden@gmail.com  Fri Jan  7 11:51:07 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 3CB6C3A6953; Fri,  7 Jan 2011 11:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.282
X-Spam-Level: 
X-Spam-Status: No, score=-103.282 tagged_above=-999 required=5 tests=[AWL=0.317, 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 0Uj1kxq-BK4T; Fri,  7 Jan 2011 11:51:06 -0800 (PST)
Received: from mail-pw0-f66.google.com (mail-pw0-f66.google.com [209.85.160.66]) by core3.amsl.com (Postfix) with ESMTP id 146B63A6940; Fri,  7 Jan 2011 11:51:06 -0800 (PST)
Received: by pwj5 with SMTP id 5so1754009pwj.1 for <multiple recipients>; Fri, 07 Jan 2011 11:53:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=5S1GhfYEzDXMe6dXR1JYHCOV0sWUmtDkYkxUTQhlExU=; b=cypgrnEfhwkD9O4geC2FNFYuLxAmjWI+fx7J3nilODl/WcSCmSSkSP6mrC3W+BXk/u VZB4PmpiLK54QOrJf492zZGTSILArobH6jub9EHdQE/PD/SDZ7/7krmoeCgkOtAYcnmN iEYoFdVKGm2Y1lWKvOD2JTGSmBSRQva9uE3Sc=
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=c+anb/Xp9LenzxlzPq4MIe2E3n2tPaW9M97whfanzO9cGeKubM/7qrMZaF/ItZrH7T kmzulyKfeBmfP42U2mo3Qfv5FCbSmPnnsSWJ6Bbxr0k8Uy43RsoHyAGVyFEw1l5QVlk2 IhvJDKg3Fbf4fpBeQZ13FViSDwvEMlC+OHFYY=
Received: by 10.142.188.17 with SMTP id l17mr2036706wff.35.1294429992397; Fri, 07 Jan 2011 11:53:12 -0800 (PST)
Received: from [172.16.224.217] ([209.97.127.34]) by mx.google.com with ESMTPS id y42sm3072119wfd.10.2011.01.07.11.53.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 07 Jan 2011 11:53:10 -0800 (PST)
Subject: Re: Old transport-layer protocols to Historic?
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: <4D2556C9.9020901@gmail.com>
Date: Fri, 7 Jan 2011 11:53:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com>
References: <4D2556C9.9020901@gmail.com>
To: tsvwg@ietf.org, IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: 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: Fri, 07 Jan 2011 19:51:07 -0000

Mykyta,


On Jan 5, 2011, at 9:44 PM, Mykyta Yevstifeyev wrote:

> Hello all,
>=20
> There have been a discussion on tsvwg mailing list about old transport =
layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT =
(RFC998). Initially there have been proposed to define IANA =
considerations for them. But after a discussion it was found out that it =
would be better to move them to Historic. I am writing to request more =
wider discussion on this topic.=20

I see little value even thinking about this.  It's looks like a "make =
work" project to me.  Just because something is "old", doesn't mean it =
is "historic" in the sense the label is used in the IETF.

Regarding RDP (RFC908, RFC1151), of which I am one of the authors, both =
are currently labeled as Experimental.  I do not see any reason to =
change that.=20

Bob


> There is quite strong consensus that IRTP should be Historic. There is =
a registered draft on this topic:
>=20
> =
https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/=

>=20
> But as for others it should be discussed. Moreover, maybe anyone knows =
some other old transport-layer protocols that are no longer in use?
>=20
> Please copy tour answer to tsvwg@ietf.org=20
>=20
> All the best,
> Mykyta Yevstifeyev
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From evnikita2@gmail.com  Fri Jan  7 21:11:16 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 074913A6987; Fri,  7 Jan 2011 21:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.166
X-Spam-Level: 
X-Spam-Status: No, score=-3.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 pZGV3PBuWUWk; Fri,  7 Jan 2011 21:11:14 -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 6D3A33A6985; Fri,  7 Jan 2011 21:11:14 -0800 (PST)
Received: by bwz12 with SMTP id 12so17774343bwz.31 for <multiple recipients>; Fri, 07 Jan 2011 21:13:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=H1kv7eQomc9b6qILxdKMukAyEmCca6ZROH56uVGY5SM=; b=bdQRGddlERweisGS0RR9ZRevs347kBJztGeDF0vzhF02P8FhPMJLe5tOBnXozemFs1 wQfnxTod0Qf46S66pOr2hjmZCPQEuWbWIS4jGC9wiXkv/ZVIHeGvomitYXQa7z5Dns9a WrZxpYkZVNNmN+UAovT7KCPPnfdM/Ae6APA4k=
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=n9vSPUhtRibA9qZWR2g0iYyBfkGPuvrYGiN5j7VNBhN3OGr8tOyEjl1lgqx4ylxTp6 PQYPg9nw1Boz2oy7JTbD7LcoQ/PX6JsyphnTwU5DuWIK5aGXxxkD55l59365ulAFhMR8 Tk8ilA/N6yjcSpfoyhxDnXuWV3AFEe3SffXtM=
Received: by 10.204.102.206 with SMTP id h14mr1301520bko.45.1294463599690; Fri, 07 Jan 2011 21:13:19 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id p22sm14414731bkp.9.2011.01.07.21.13.17 (version=SSLv3 cipher=RC4-MD5); Fri, 07 Jan 2011 21:13:18 -0800 (PST)
Message-ID: <4D27F280.1020205@gmail.com>
Date: Sat, 08 Jan 2011 07:13: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: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com> <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com>
In-Reply-To: <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: tsvwg@ietf.org, IETF Discussion <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, 08 Jan 2011 05:11:16 -0000

07.01.2011 21:53, Bob Hinden wrote:
> Mykyta,
>
>
> On Jan 5, 2011, at 9:44 PM, Mykyta Yevstifeyev wrote:
>
>> Hello all,
>>
>> There have been a discussion on tsvwg mailing list about old transport layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT (RFC998). Initially there have been proposed to define IANA considerations for them. But after a discussion it was found out that it would be better to move them to Historic. I am writing to request more wider discussion on this topic.
> I see little value even thinking about this.  It's looks like a "make work" project to me.  Just because something is "old", doesn't mean it is "historic" in the sense the label is used in the IETF.
>
> Regarding RDP (RFC908, RFC1151), of which I am one of the authors, both are currently labeled as Experimental.  I do not see any reason to change that.
>
> Bob
>
>
Dear all,

RFC2026 mentions:

>   A specification that has been superseded by a more recent
>     specification or is for any other reason considered to be obsolete is
>     assigned to the "Historic" level.
and gives 2 reasons for making the RFC Historic: 1) RFC is obsoleted 
(superseded) or 2) obsolete.

Obsoleted = made obsolete. This is obvious. When one RFC replaces 
another, it obsoletes it, and second becomes obsolete.

What is obsolete (adj.)? Obsolete = deprecated, outdated, out of use, 
non-current, etc.

Moreover, RFC2026 does not set any other guidelines for setting the 
Historic status. That is why if the protocol is out of use, even 
specified by Experimental RFC, it is a reason to move its spec. to 
Historic, in accordance with RFC2026.

All the best,
Mykyta Yevstifeyev

>> There is quite strong consensus that IRTP should be Historic. There is a registered draft on this topic:
>>
>> https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/
>>
>> But as for others it should be discussed. Moreover, maybe anyone knows some other old transport-layer protocols that are no longer in use?
>>
>> Please copy tour answer to tsvwg@ietf.org
>>
>> All the best,
>> Mykyta Yevstifeyev
>> _______________________________________________
>> 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 dhc2@dcrocker.net  Fri Jan  7 21:24:03 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 3A9ED3A6985 for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 21:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.576
X-Spam-Level: 
X-Spam-Status: No, score=-6.576 tagged_above=-999 required=5 tests=[AWL=0.023,  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 aDqbDQHxazca for <ietf@core3.amsl.com>; Fri,  7 Jan 2011 21:24:02 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 2130D3A697C for <ietf@ietf.org>; Fri,  7 Jan 2011 21:24:02 -0800 (PST)
Received: from [192.168.1.117] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p085Q4PS020248 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 7 Jan 2011 21:26:09 -0800
Message-ID: <4D27F56A.8040605@dcrocker.net>
Date: Fri, 07 Jan 2011 21:26:02 -0800
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: ietf@ietf.org
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com> <4D2628AB.3080003@isi.edu>
In-Reply-To: <4D2628AB.3080003@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 07 Jan 2011 21:26:09 -0800 (PST)
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: Sat, 08 Jan 2011 05:24:03 -0000

On 1/6/2011 12:40 PM, Bob Braden wrote:
> Historic might imply that they were once in service, but have later been
> replaced/deprecated.


We assign labels to indicate the status of the specification, not the status of 
a service that might use it.

We say 'experimental' to mean that we thinks it's ok to play around with the 
spec and maybe that we are hoping to get further information about it.  But it 
also means that we very much caution about use.  It's our "caveat emptor" label.

We say 'historic' when we frankly think the spec should now not be used, for 
whatever reason and no matter its prior status.

These both are affirmative labels.  I too do not think we should use them for 
"housekeeping" and the mere fact that a specification is not used does not mean 
that it shouldn't be used.

To the extent that having a spec around -- especially one on standards track -- 
might seem to conflict with another, preferred spec, then it's worth considering 
making the one that is out of favor become historic.  The same holds for 
specifications that are now deemed problematic.

But none of this is about propriety or neatness or a community OCD neurosis.  It 
needs to be about pragmatic guidance to the community.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From evnikita2@gmail.com  Fri Jan  7 21:33:38 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 319EF3A6992; Fri,  7 Jan 2011 21:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.171
X-Spam-Level: 
X-Spam-Status: No, score=-3.171 tagged_above=-999 required=5 tests=[AWL=0.428,  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 NQCj+FAdBmZz; Fri,  7 Jan 2011 21:33:36 -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 D0A383A697A; Fri,  7 Jan 2011 21:33:35 -0800 (PST)
Received: by bwz12 with SMTP id 12so17780410bwz.31 for <multiple recipients>; Fri, 07 Jan 2011 21:35:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=pDtC64Ekig9iTZc7ahH4rA3NTOcuFP9xdZmggC6Fm9s=; b=kHwWEOU1fx5gpfXaqFTOuHtjnAEIhH9cPSWhBhwlKiIIqwc3aOH028q8FYjYdct5Uf t0K7BjbCAeL7iFkSofV2VHwbuWtYXUsTvAmR1Uaq4J1XyTOSoGTDgq9M5ZvGCYgGMjSc +oyn6eCVAiSNe3YynnbQENSb4dIKYHS0eWK98=
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=jH472DprZmCRtTI0318mvgrAljASZ2NZqM1sWKXSWezdTALym+NILo+vH636Va9s7q 6eVC3YM5WLTxTcDBQHKTZQBM8dJrU3he5tK3t0p2Py5Sscop/0sDQFucBkaN+RIaYTIR DF4bRgngJqt+hX4hRkTatfl9crRBe5KpzaDvw=
Received: by 10.204.121.138 with SMTP id h10mr4700734bkr.40.1294464941985; Fri, 07 Jan 2011 21:35:41 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id j11sm14416180bka.0.2011.01.07.21.35.40 (version=SSLv3 cipher=RC4-MD5); Fri, 07 Jan 2011 21:35:41 -0800 (PST)
Message-ID: <4D27F7BE.3040800@gmail.com>
Date: Sat, 08 Jan 2011 07:35:58 +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: dcrocker@bbiw.net
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com> <4D2628AB.3080003@isi.edu> <4D27F56A.8040605@dcrocker.net>
In-Reply-To: <4D27F56A.8040605@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Dave CROCKER <dhc2@dcrocker.net>, 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: Sat, 08 Jan 2011 05:33:38 -0000

08.01.2011 7:26, Dave CROCKER wrote:
>
>
> On 1/6/2011 12:40 PM, Bob Braden wrote:
>> Historic might imply that they were once in service, but have later been
>> replaced/deprecated.
>
>
> We assign labels to indicate the status of the specification, not the 
> status of a service that might use it.
But the specification without service is nothing. We should look at the 
service using it, first of all.
>
> We say 'experimental' to mean that we thinks it's ok to play around 
> with the spec and maybe that we are hoping to get further information 
> about it.  But it also means that we very much caution about use.  
> It's our "caveat emptor" label.
>
> We say 'historic' when we frankly think the spec should now not be 
> used, for whatever reason and no matter its prior status.
>
> These both are affirmative labels.  I too do not think we should use 
> them for "housekeeping" and the mere fact that a specification is not 
> used does not mean that it shouldn't be used.
>
> To the extent that having a spec around -- especially one on standards 
> track -- might seem to conflict with another, preferred spec, then 
> it's worth considering making the one that is out of favor become 
> historic.  The same holds for specifications that are now deemed 
> problematic.
But it is the same what is with IRTP. RFC938 is obviously not acceptable 
to be used in the current Internet. In order it remains useful, it's 
needed to be rewritten or moved to Historic. And I really do not 
understand how did it become Experimental. The first notices of current 
classification system appeared in RFC1370, while this spec is RFC938.

Mykyta Yevstifeyev
>
> But none of this is about propriety or neatness or a community OCD 
> neurosis.  It needs to be about pragmatic guidance to the community.
>
> d/
>


From evnikita2@gmail.com  Fri Jan  7 23:21:13 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 D505928C0CF; Fri,  7 Jan 2011 23:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.217
X-Spam-Level: 
X-Spam-Status: No, score=-3.217 tagged_above=-999 required=5 tests=[AWL=0.381,  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 2ksmS9v7E75V; Fri,  7 Jan 2011 23:21: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 6DE903A698E; Fri,  7 Jan 2011 23:21:07 -0800 (PST)
Received: by bwz12 with SMTP id 12so17809882bwz.31 for <multiple recipients>; Fri, 07 Jan 2011 23:23:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:content-type; bh=+/oqtcoMqAV5vpXjVuK4MaXp6DJyCRd4E17Sr7MD+Tg=; b=L1FrxuBm6XN0Zb1HmxWRlUZRWIlPDCRj/ithdV1vK6IeJ1o/oiX104xNf/GaEPjZZi 8G/KA2Q5BEosWCU6I6DhmLKtRIfuO7VzFB0S34oiTg4j+aB0ZftlkB5IVcx1hY1bx85c dvjzpy8IDSSfubWpbWwADdk5grHH6O/xUtSD0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type; b=P9vcS6a4ObmVLuxK7NyxDUCU09gAlG1MmouPZKci8UIw2SyLr/LaqIvBGGQHRZvusV MNemiYk2W1tid2COdkq5VefN5JDYXx6JF1gNG4KAfJvd+gVKDdiyQnTpvbHfr+4ArT9u aoemqHBUW6G295V8CU2VH+OZzMr+9xiMCcDAI=
Received: by 10.204.67.140 with SMTP id r12mr3954806bki.147.1294467682093; Fri, 07 Jan 2011 22:21:22 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id a17sm14563747bku.23.2011.01.07.22.21.20 (version=SSLv3 cipher=RC4-MD5); Fri, 07 Jan 2011 22:21:21 -0800 (PST)
Message-ID: <4D280272.6090402@gmail.com>
Date: Sat, 08 Jan 2011 08:21:38 +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>, httpbis Group <ietf-http-wg@w3.org>,  ietf-message-headers@ietf.org, iesg@ietf.org
Subject: Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
Content-Type: multipart/alternative; boundary="------------020108020706000600080603"
Cc: Alexey Melnikov <alexey.melnikov@isode.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: Sat, 08 Jan 2011 07:21:14 -0000

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

Hello all,

This document summarizes the Last Call for 
draft-yevstifeyev-http-headers-not-recognized.

The Last Call was requested on 11 December, 2010 by Alexey Melnikov and 
was announced on 13 November, 2010. The period of 32 days has been 
assigned for this Last Call, that ends on 14 January, 2011.

The Last call has been requested for version -08. However during the 
Last Call 3 new versions appeared. The latest one is -11, submitted on 8 
January, 2011

This message contains the exhaustive analysis of changes made during the 
Last Call.

    * The intended status: Did not change; Experimental.
    * The name of the document: Changed. Was *'Headers-Not-Recognized'
      HTTP Header Field* and now is *HTTP 'Headers-Not-Recognized'
      Header Field. *I ask Alexey to change the Writeup of the document
      in accordance with the current version.
    * Abstract: Changed. Replaced *headers* with *header fields* and
      some other minor changes.
    * Introduction: Changed. Replaced *headers* with *header fields;
      *and*servers *with *hosts; *other minor changes.
    * Conventions: Changed. Added the definition of term host, gateway,
      proxy, tunnel.
    * Model of Work: Changed. Added more detailed description of action
      of different HTTP nodes.
    * Syntax: Changed. Now is not /token**/but /1*VCAHR /for definition
      of the name of the header.
    * IANA Considerations: Added the reference to RFC 3864.

You may also obtain this information from:

https://tools.ietf.org/rfcdiff?url1=draft-yevstifeyev-http-headers-not-recognized-11&difftype=--html&submit=Go!&url2=draft-yevstifeyev-http-headers-not-recognized-08

During the last call the following note from IANA was received:

> IESG:
>
> IANA has reviewed draft-yevstifeyev-http-headers-not-recognized-08.txt,
> which is currently in Last Call, and has the following comments:
>
> IANA understands that, upon approval of this document, there is a single
> IANA Action that needs to be completed.
>
> In the Permanent Message Header Field Names registry located at:
>
> http://www.iana.org/assignments/message-headers/perm-headers.html
>
> a single, new registration is to be added as follows:
>
> Header field name: Headers-Not-Recognized
> Applicable protocol: http
> Status: experimental
> Specification document: [RFC-to-be]
>
> IANA understands that this is the only IANA Action that needs to be
> completed upon approval of this document.
>
> Thanks,
>
> Amanda Baber
> IANA

No changes are intended to be made to the draft during the period up to 
14 January in order to allow IESG to review the document.

Looking forward to the opinion of IESG,
Mykyta Yevstifeyev

P.S. Apologizing if you receive multiple copies of the message. Mykyta.

--------------020108020706000600080603
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 all,<br>
        <br>
        This document summarizes the Last Call for
        draft-yevstifeyev-http-headers-not-recognized.<br>
        <br>
        The Last Call was requested on 11 December, 2010 by Alexey
        Melnikov and was announced on 13 November, 2010. The period of
        32 days has been assigned for this Last Call, that ends on 14
        January, 2011.<br>
        <br>
        The Last call has been requested for version -08. However during
        the Last Call 3 new versions appeared. The latest one is -11,
        submitted on 8 January, 2011<br>
        <br>
        This message contains the exhaustive analysis of changes made
        during the Last Call.<br>
        <br>
      </big></font>
    <ul>
      <li>The intended status: Did not change; Experimental.</li>
      <li>The name of the document: Changed. Was <b>'Headers-Not-Recognized'

          HTTP Header Field</b> and now is <b>HTTP <span
            class="insert">'Headers-Not-Recognized'</span> Header Field.
        </b>I ask Alexey to change the Writeup of the document in
        accordance with the current version.</li>
      <li>Abstract: Changed. Replaced <b>headers</b> with <b>header
          fields</b> and some other minor changes.</li>
      <li>Introduction: Changed. Replaced <b>headers</b> with <b>header
          fields; </b>and<b> servers </b>with <b>hosts; </b>other
        minor changes.</li>
      <li>Conventions: Changed. Added the definition of term host,
        gateway, proxy, tunnel.</li>
      <li>Model of Work: Changed. Added more detailed description of
        action of different HTTP nodes.</li>
      <li>Syntax: Changed. Now is not <i>token<b> </b></i>but <i>1*VCAHR 
        </i>for definition of the name of the header.</li>
      <li>IANA Considerations: Added the reference to RFC 3864.</li>
    </ul>
    You may also obtain this information from:<br>
    <br>
    <a class="moz-txt-link-freetext"
href="https://tools.ietf.org/rfcdiff?url1=draft-yevstifeyev-http-headers-not-recognized-10&amp;difftype=--html&amp;submit=Go%21&amp;url2=draft-yevstifeyev-http-headers-not-recognized-08">https://tools.ietf.org/rfcdiff?url1=draft-yevstifeyev-http-headers-not-recognized-11&amp;difftype=--html&amp;submit=Go!&amp;url2=draft-yevstifeyev-http-headers-not-recognized-08</a><br>
    <br>
    During the last call the following note from IANA was received:<br>
    <br>
    <blockquote type="cite">
      <pre wrap="">IESG:

IANA has reviewed draft-yevstifeyev-http-headers-not-recognized-08.txt,
which is currently in Last Call, and has the following comments:

IANA understands that, upon approval of this document, there is a single
IANA Action that needs to be completed.

In the Permanent Message Header Field Names registry located at:

<a class="moz-txt-link-freetext" href="http://www.iana.org/assignments/message-headers/perm-headers.html">http://www.iana.org/assignments/message-headers/perm-headers.html</a>

a single, new registration is to be added as follows:

Header field name: Headers-Not-Recognized
Applicable protocol: http
Status: experimental
Specification document: [RFC-to-be]

IANA understands that this is the only IANA Action that needs to be
completed upon approval of this document.

Thanks,

Amanda Baber
IANA
</pre>
    </blockquote>
    <br>
    No changes are intended to be made to the draft during the period up
    to 14 January in order to allow IESG to review the document.<br>
    <br>
    Looking forward to the opinion of IESG,<br>
    Mykyta Yevstifeyev<br>
    <br>
    P.S. Apologizing if you receive multiple copies of the message.
    Mykyta.<br>
  </body>
</html>

--------------020108020706000600080603--

From julian.reschke@gmx.de  Sat Jan  8 00:32: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 D2EFB28C108 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 00:32:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.178
X-Spam-Level: 
X-Spam-Status: No, score=-104.178 tagged_above=-999 required=5 tests=[AWL=-2.179, BAYES_00=-2.599, J_CHICKENPOX_42=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 hhB3v5cYDPBI for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 00:32:26 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id B03BB28C0FA for <ietf@ietf.org>; Sat,  8 Jan 2011 00:32:25 -0800 (PST)
Received: (qmail invoked by alias); 08 Jan 2011 08:34:31 -0000
Received: from p508FD294.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.210.148] by mail.gmx.net (mp049) with SMTP; 08 Jan 2011 09:34:31 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/JU8RhosvJkz8wecMebLmfNl1PNwEif5xkfrQRMT 3Udu9E0+AzGRFf
Message-ID: <4D28218A.2020406@gmx.de>
Date: Sat, 08 Jan 2011 09:34:18 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: [Ietf-message-headers] Last Call Summary on	draft-yevstifeyev-http-headers-not-recognized
References: <4D280272.6090402@gmail.com>
In-Reply-To: <4D280272.6090402@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: iesg@ietf.org, ietf-message-headers@ietf.org, IETF Discussion <ietf@ietf.org>, httpbis Group <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: Sat, 08 Jan 2011 08:32:27 -0000

On 08.01.2011 07:21, Mykyta Yevstifeyev wrote:
> Hello all,
>
> This document summarizes the Last Call for
> draft-yevstifeyev-http-headers-not-recognized.
>
> The Last Call was requested on 11 December, 2010 by Alexey Melnikov and
> was announced on 13 November, 2010. The period of 32 days has been
> assigned for this Last Call, that ends on 14 January, 2011.
>
> The Last call has been requested for version -08. However during the
> Last Call 3 new versions appeared. The latest one is -11, submitted on 8
> January, 2011

If a draft changes three times during LC, there may be a problem. I 
encourage you to go back to the drawing board, and think hard(er about 
the feedback you got, in particular 
<http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html>.

I also mentioned at least once that in many frameworks this is 
essentially un-implementable, as different types of header fields are 
processed by different, independent layers in the code, and thus there's 
no way some part of the code will ever *know* which headers have been 
"processed". Do you think that this is not a problem?

> ...
>     * Syntax: Changed. Now is not /token**/but /1*VCAHR /for definition
>       of the name of the header.
> ...

Why?

Best regards, Julian

From evnikita2@gmail.com  Sat Jan  8 02:17:24 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 5FB013A69BE; Sat,  8 Jan 2011 02:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.921
X-Spam-Level: 
X-Spam-Status: No, score=-2.921 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, J_CHICKENPOX_42=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 PqqunfUeRTVs; Sat,  8 Jan 2011 02:17:23 -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 ADFBF3A6964; Sat,  8 Jan 2011 02:17:22 -0800 (PST)
Received: by bwz12 with SMTP id 12so17859142bwz.31 for <multiple recipients>; Sat, 08 Jan 2011 02:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=NSy4Q4ss+NNXUW8WSDrqnjgs3IfA4rGWOPSKVhtyTWg=; b=ntTafH6oixFJe5XABb6uNffF874DxxxwGmTjugfGv9LMzAFVZBbUV5Xnj+3j6O2PE/ PhSKV5jSntMDrIp/IMhgXeh3flDhPdbW612XtTag5LIk+DnaS39DXtzk9yRBMK5aJb/N vaC7EGS6x0SUx/EOLx8ey4vFLS6viM5DbznZ0=
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=ba8eBGlj83qOYoMz3peCPPL41u8LXyzPtFIradfkEfkh9Qu/J64UwlZ52cHqgTudJy 5aADjv8/9ltuFUKO2RxhQ9QeajXZB6vWQvcELxz8sl7ymSR5Yn4PKCntFvm/ftQUMEt/ EWinbKMtKmyHLX8uxSmNnxC/2vqxmDMWF6vEk=
Received: by 10.204.52.134 with SMTP id i6mr19900903bkg.36.1294481969175; Sat, 08 Jan 2011 02:19:29 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id j11sm14640528bka.12.2011.01.08.02.19.27 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 02:19:28 -0800 (PST)
Message-ID: <4D283A42.3080303@gmail.com>
Date: Sat, 08 Jan 2011 12:19:46 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [Ietf-message-headers] Last Call Summary on	draft-yevstifeyev-http-headers-not-recognized
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de>
In-Reply-To: <4D28218A.2020406@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, ietf-message-headers@ietf.org, IETF Discussion <ietf@ietf.org>, httpbis Group <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: Sat, 08 Jan 2011 10:17:24 -0000

08.01.2011 10:34, Julian Reschke wrote:
> On 08.01.2011 07:21, Mykyta Yevstifeyev wrote:
>> Hello all,
>>
>> This document summarizes the Last Call for
>> draft-yevstifeyev-http-headers-not-recognized.
>>
>> The Last Call was requested on 11 December, 2010 by Alexey Melnikov and
>> was announced on 13 November, 2010. The period of 32 days has been
>> assigned for this Last Call, that ends on 14 January, 2011.
>>
>> The Last call has been requested for version -08. However during the
>> Last Call 3 new versions appeared. The latest one is -11, submitted on 8
>> January, 2011
>
> If a draft changes three times during LC, there may be a problem. I 
> encourage you to go back to the drawing board, and think hard(er about 
> the feedback you got, in particular 
> <http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html>.
Why do you think that the draft shouldn't be changed during LC? 
Moreover, I had some reasons for doing that. firstly, version -09 added 
the section that was not present in -08 and if I added it now, there 
would not be a  possibility to discuss it. Version -10 presented the 
most stable one to reflect all the comments I received during the LC. 
And -11 was prepared as final for IESG review.

I have fully answered all the question form the message you refer to.
>
> I also mentioned at least once that in many frameworks this is 
> essentially un-implementable, as different types of header fields are 
> processed by different, independent layers in the code, and thus 
> there's no way some part of the code will ever *know* which headers 
> have been "processed". Do you think that this is not a problem?
That is the issues that would be decided by the implementators.  
Moreover, one code layer may support this technology while others may not.
>
>> ...
>>     * Syntax: Changed. Now is not /token**/but /1*VCAHR /for definition
>>       of the name of the header.
>> ...
>
> Why?
RFC2616 gives the following definition of token:

token          = 1*<any CHAR except CTLs or separators>
separators     = "(" | ")" | "<" |">" | "@"
                 | "," | ";" | ":" | "\" |<">
                 | "/" | "[" | "]" | "?" | "="
                 | "{" | "}" | SP | HT



And non-visible chars are not allowed in headers. So only VCHARs.
>
> Best regards, Julian
>


From julian.reschke@gmx.de  Sat Jan  8 03:16:05 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 7556728B797 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 03:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.155
X-Spam-Level: 
X-Spam-Status: No, score=-104.155 tagged_above=-999 required=5 tests=[AWL=-2.156, BAYES_00=-2.599, J_CHICKENPOX_42=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 ZaTU3RhZHuAE for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 03:16:04 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 380533A69D2 for <ietf@ietf.org>; Sat,  8 Jan 2011 03:16:03 -0800 (PST)
Received: (qmail invoked by alias); 08 Jan 2011 11:18:08 -0000
Received: from p508FD294.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.210.148] by mail.gmx.net (mp005) with SMTP; 08 Jan 2011 12:18:08 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+DHRo7j0SD6a8ivqtXRklqaF/7wzorxLC/8GaLXi ecmc82BxbUUBAI
Message-ID: <4D2847E1.9090004@gmx.de>
Date: Sat, 08 Jan 2011 12:17:53 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: [Ietf-message-headers] Last Call Summary on	draft-yevstifeyev-http-headers-not-recognized
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de> <4D283A42.3080303@gmail.com>
In-Reply-To: <4D283A42.3080303@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: iesg@ietf.org, ietf-message-headers@ietf.org, IETF Discussion <ietf@ietf.org>, httpbis Group <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: Sat, 08 Jan 2011 11:16:05 -0000

On 08.01.2011 11:19, Mykyta Yevstifeyev wrote:
>> If a draft changes three times during LC, there may be a problem. I
>> encourage you to go back to the drawing board, and think hard(er about
>> the feedback you got, in particular
>> <http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html>.
> Why do you think that the draft shouldn't be changed during LC?

Because people assume stability during LC, and are unlikely to review 
the spec multiple times during the same LC.

Of course that does not mean that you can't start addressing issues 
during LC. Just do so in a way that it doesn't change what's being 
last-called. For instance, by publishing the current edits on a private 
web page.

If you have non-editorial changes, the AD will have to decide whether 
they require a new LC.

> Moreover, I had some reasons for doing that. firstly, version -09 added
> the section that was not present in -08 and if I added it now, there
> would not be a possibility to discuss it. Version -10 presented the most

There was no stability *because* of these updates.

> stable one to reflect all the comments I received during the LC. And -11
> was prepared as final for IESG review.

My recommendation to the IESG is to wait for a stable spec, and then 
restart the LC.

> I have fully answered all the question form the message you refer to.
>>
>> I also mentioned at least once that in many frameworks this is
>> essentially un-implementable, as different types of header fields are
>> processed by different, independent layers in the code, and thus
>> there's no way some part of the code will ever *know* which headers
>> have been "processed". Do you think that this is not a problem?
> That is the issues that would be decided by the implementators.
> Moreover, one code layer may support this technology while others may not.

How so? If a servlet does support it, but the servlet container does 
not, there's no way to generate a correct header field value.

>>> ...
>>> * Syntax: Changed. Now is not /token**/but /1*VCAHR /for definition
>>> of the name of the header.
>>> ...
>>
>> Why?
> RFC2616 gives the following definition of token:
>
> token = 1*<any CHAR except CTLs or separators>
> separators = "(" | ")" | "<" |">" | "@"
> | "," | ";" | ":" | "\" |<">
> | "/" | "[" | "]" | "?" | "="
> | "{" | "}" | SP | HT
>
>
>
> And non-visible chars are not allowed in headers. So only VCHARs.

That didn't answer my question. Why did you change something that was 
ok? It also shows why you'll need a new LC.

In this particular case the change wasn't only not necessary, but also 
changes the syntax significantly. VCHAR allows significantly more 
characters than HTTP's token, namely the comma that you already need as 
delimiter.

Well, assuming you mean the VCHAR definition from RFC 5234, because your 
spec doesn't clearly say where it comes from (you could import specific 
productions or all of them from 5234, but you should say that).

Speaking of which: you can't have a "_" character in a rule name.

Best regards, Julian



From daedulus@btconnect.com  Sat Jan  8 04:05:10 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 0B5F93A69CA; Sat,  8 Jan 2011 04:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_42=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 EtJyEJO-p0fm; Sat,  8 Jan 2011 04:05:09 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by core3.amsl.com (Postfix) with ESMTP id 191813A69C3; Sat,  8 Jan 2011 04:05:07 -0800 (PST)
Received: from host81-152-224-74.range81-152.btcentralplus.com (HELO pc6) ([81.152.224.74]) by c2beaomr10.btconnect.com with SMTP id BGD22905; Sat, 08 Jan 2011 12:07:13 +0000 (GMT)
Message-ID: <002301cbaf23$c0907580$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Julian Reschke" <julian.reschke@gmx.de>
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de><4D283A42.3080303@gmail.com> <4D2847E1.9090004@gmx.de>
Subject: LC changes was Last Call Summaryondraft-yevstifeyev-http-headers-not-recognized
Date: Sat, 8 Jan 2011 12:03:53 +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.4D285371.00C1, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4D285372.00A2,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@ietf.org, IETF Discussion <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, 08 Jan 2011 12:05:10 -0000

----- Original Message -----
From: "Julian Reschke" <julian.reschke@gmx.de>
To: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
Cc: <iesg@ietf.org>; <ietf-message-headers@ietf.org>; "IETF Discussion"
<ietf@ietf.org>; "httpbis Group" <ietf-http-wg@w3.org>
Sent: Saturday, January 08, 2011 12:17 PM
 On 08.01.2011 11:19, Mykyta Yevstifeyev wrote:
> >> If a draft changes three times during LC, there may be a problem. I
> >> encourage you to go back to the drawing board, and think hard(er about
> >> the feedback you got, in particular
> >> <http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html>.
> > Why do you think that the draft shouldn't be changed during LC?
>
> Because people assume stability during LC, and are unlikely to review
> the spec multiple times during the same LC.
>
> Of course that does not mean that you can't start addressing issues
> during LC. Just do so in a way that it doesn't change what's being
> last-called. For instance, by publishing the current edits on a private
> web page.

That's a relief; I agree absolutely with you, but am very aware that
the last statement on this, from Jari Arkko in August on this list,
explained why he encouraged 'his' editors to keep producing
new versions while the Last Call was in progress, an action that
switches me off completely

Tom Petch

>
> If you have non-editorial changes, the AD will have to decide whether
> they require a new LC.
>
> > Moreover, I had some reasons for doing that. firstly, version -09 added
> > the section that was not present in -08 and if I added it now, there
> > would not be a possibility to discuss it. Version -10 presented the most
>
> There was no stability *because* of these updates.
>
> > stable one to reflect all the comments I received during the LC. And -11
> > was prepared as final for IESG review.
>
> My recommendation to the IESG is to wait for a stable spec, and then
> restart the LC.
>

<snip/>

> Best regards, Julian
>
>


From lixia@cs.ucla.edu  Sat Jan  8 07:35:00 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 59C6B3A695F for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 07:35: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 dcU1oityE95F for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 07:34:59 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 9C3CB3A693A for <ietf@ietf.org>; Sat,  8 Jan 2011 07:34:59 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id BA95E39E80F5 for <ietf@ietf.org>; Sat,  8 Jan 2011 07:37:07 -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 I-eNbde0jztw for <ietf@ietf.org>; Sat,  8 Jan 2011 07:37:07 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-174-94-219.socal.res.rr.com [76.174.94.219]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id DCFF339E8083 for <ietf@ietf.org>; Sat,  8 Jan 2011 07:37:06 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: I-D Action:draft-white-tsvwg-netblt-00.txt
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <20110108110002.19936.59779.idtracker@localhost>
Date: Sat, 8 Jan 2011 07:37:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E426D9B-104E-4579-9BAD-63B2FD0AF90C@cs.ucla.edu>
References: <20110108110002.19936.59779.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: Sat, 08 Jan 2011 15:35:00 -0000

I am not sure why this rush to get a new internet draft out, without =
consultation to any of its original authors, and given the rough =
consensus on ietf mailing list discussion is to keep NETBLT RFC as is =
(experimental). =20

Lixia

On Jan 8, 2011, at 3:00 AM, Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>=20
> 	Title           : Network Block Transfer Protocol (NETBLT)
> 	Author(s)       : J. White, M. Yevstifeyev
> 	Filename        : draft-white-tsvwg-netblt-00.txt
> 	Pages           : 34
> 	Date            : 2011-01-08
>=20
> This document is a specification of version 5 of Network Block
> Transfer Protocol (NETBLT). This protocol was firstly specified in
> RFC 969, that has been made obsolete by RFC 998. Nevertheless, none
> of these documents match current Internet Standards and are
> deprecated. This document aligns the NETBLT specification with the
> most current Internet Standards and obsoletes RFC 998.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.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 evnikita2@gmail.com  Sat Jan  8 07:44:02 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 E221D3A6984 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 07:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.263
X-Spam-Level: 
X-Spam-Status: No, score=-3.263 tagged_above=-999 required=5 tests=[AWL=0.336,  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 MleCmywJdPY1 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 07:44:01 -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 94BF43A6954 for <ietf@ietf.org>; Sat,  8 Jan 2011 07:44:01 -0800 (PST)
Received: by bwz12 with SMTP id 12so17981273bwz.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 07:46:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=txQKKkp/zCKv7b+9h5K6OGJmS4QDYjEMeJqRpZiVNds=; b=Nomj4CRbV0Uaf9luGgvzMy3Z46hDlH7Ypu4Ipe9T0xiTMZLT0OcJsTtewhqpP0amA4 v6kuD91IaN/ki2MRBQOmVX1yYHhsLNYPlAyReOIS3L82R2sK8kmJ/1prwpopdjGzQedE EiPz6wzJYZvzaBkL9EO3NV7HNAkrTgT6lak9U=
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=SqtrHwZpp/pbUK1/4JO99L6SI0Xum370ZMdgJKuMBMgQZ4uc5TNkM7p60BeT0xmWXg jMK/GnkmQxDBlCWCMfSOYvx2KRnSKW8x12YGDS+eDfJ8Y1DP3R6aa4Rh2QX/RNYE5h3j tV7Yr9mBQKfp6OB3QQYTkXvrXeyZt64PMpUgY=
Received: by 10.204.76.131 with SMTP id c3mr1226292bkk.110.1294501567129; Sat, 08 Jan 2011 07:46:07 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v1sm14765271bkt.17.2011.01.08.07.46.05 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 07:46:06 -0800 (PST)
Message-ID: <4D2886CF.5020205@gmail.com>
Date: Sat, 08 Jan 2011 17:46:23 +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: I-D Action:draft-white-tsvwg-netblt-00.txt
References: <20110108110002.19936.59779.idtracker@localhost> <6E426D9B-104E-4579-9BAD-63B2FD0AF90C@cs.ucla.edu>
In-Reply-To: <6E426D9B-104E-4579-9BAD-63B2FD0AF90C@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John White <jccw@jccw.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, 08 Jan 2011 15:44:03 -0000

08.01.2011 17:37, Lixia Zhang wrote:
> I am not sure why this rush to get a new internet draft out, without consultation to any of its original authors, and given the rough consensus on ietf mailing list discussion is to keep NETBLT RFC as is (experimental).
First of all, I've consulted the initial author of it, John White, and 
some other people off-list.  The NETBLT spec found in RFC998 *as is* 
could not be appropriate for current Internet, so there is a need for 
another one.  In the next 3 months, I think, we will be a work on it.  
Moreover, we plan to submit it as Independent Submission as Experimental 
RFC, despites it mentions the Standards Track one.

Mykyta
> Lixia
>
> On Jan 8, 2011, at 3:00 AM, Internet-Drafts@ietf.org wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>> 	Title           : Network Block Transfer Protocol (NETBLT)
>> 	Author(s)       : J. White, M. Yevstifeyev
>> 	Filename        : draft-white-tsvwg-netblt-00.txt
>> 	Pages           : 34
>> 	Date            : 2011-01-08
>>
>> This document is a specification of version 5 of Network Block
>> Transfer Protocol (NETBLT). This protocol was firstly specified in
>> RFC 969, that has been made obsolete by RFC 998. Nevertheless, none
>> of these documents match current Internet Standards and are
>> deprecated. This document aligns the NETBLT specification with the
>> most current Internet Standards and obsoletes RFC 998.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> 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
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From evnikita2@gmail.com  Sat Jan  8 07:55:56 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 8059228C104; Sat,  8 Jan 2011 07:55:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.966
X-Spam-Level: 
X-Spam-Status: No, score=-2.966 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=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 NOyLv07la4OR; Sat,  8 Jan 2011 07:55:55 -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 7E2F628C102; Sat,  8 Jan 2011 07:55:53 -0800 (PST)
Received: by bwz12 with SMTP id 12so17986280bwz.31 for <multiple recipients>; Sat, 08 Jan 2011 07:58:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=WW6Tf2aYO2x0f2qWEQ+6gJf79zetI1SlR3nIaUY8zno=; b=NmH9kLy/y+LoKv1mq3a3zFq0kOeiFU0S76yK1c4fd4BxDOSXlv5H3l2GXJor/0si3F NDy4iAvc5swJ+wx2JLIQ/Yw2aV5rKV/SEdCpdqmYYVXDtMSvEetVfA+3DPVlB8gB2zJB uZCEIpUjnr29rxk2yDnkUHWf5DKDeOUTvQ6eY=
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=Pr4h537uu0hyKc5Qys62PBA4GwoVaCtKNVxRhDF7bMwmE7nDdGScztfguZPj/WJDaT uqkFILCOElc//pT+hggX3qfoQSY0O8UTtOm6RN3RLKMqXgx+sdvYgE/OPMLy0+jfVmgi r4CVr6gNKmyAOKS+isiIIctsu905I/ow1p7FA=
Received: by 10.204.73.9 with SMTP id o9mr9257287bkj.191.1294502280380; Sat, 08 Jan 2011 07:58:00 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v25sm14773122bkt.18.2011.01.08.07.57.58 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 07:57:59 -0800 (PST)
Message-ID: <4D288998.9020001@gmail.com>
Date: Sat, 08 Jan 2011 17:58:16 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [Ietf-message-headers] Last Call Summary on	draft-yevstifeyev-http-headers-not-recognized
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de> <4D283A42.3080303@gmail.com> <4D2847E1.9090004@gmx.de>
In-Reply-To: <4D2847E1.9090004@gmx.de>
Content-Type: multipart/alternative; boundary="------------070004030808040705020602"
Cc: iesg@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, ietf-message-headers@ietf.org, IETF Discussion <ietf@ietf.org>, httpbis Group <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: Sat, 08 Jan 2011 15:55:56 -0000

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

Hello all,

I have revised all the comments I received now and during the Last 
Call.  My previous message was just formal stating statistical data on 
LC.  Here I'd like to mention what I really think of the document and 
its further destiny.

Many LC comments referred to that it would be uninteresting and useless 
to implement this.  Maybe one of them seems the most interesting for me 
- it said about the 'Warning' headers that should be used in this 
occasion.  This, IMO, is one of the most suitable for me and this 
technology.  But if we implement this now using Warning, one problem is 
absence of IANA registry for Warning codes, such as for Status codes.  
As this message is now sent to httpbis WG mailing list, I ask you if 
there is a sense in creating such registry?

As for the initial draft, I think I'm about to withdraw /it /(but not my 
idea).  So result of Last Call seems to be the following: the idea in 
the current implementation as Internet-Draft does not seem to be 
appropriate.  So I'll raise this topic later.

All the best,
Mykyta Yevstifeyev

08.01.2011 13:17, Julian Reschke wrote:
> On 08.01.2011 11:19, Mykyta Yevstifeyev wrote:
>>> If a draft changes three times during LC, there may be a problem. I
>>> encourage you to go back to the drawing board, and think hard(er about
>>> the feedback you got, in particular
>>> <http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html>. 
>>>
>> Why do you think that the draft shouldn't be changed during LC?
>
> Because people assume stability during LC, and are unlikely to review 
> the spec multiple times during the same LC.
>
> Of course that does not mean that you can't start addressing issues 
> during LC. Just do so in a way that it doesn't change what's being 
> last-called. For instance, by publishing the current edits on a 
> private web page.
>
> If you have non-editorial changes, the AD will have to decide whether 
> they require a new LC.
>
>> Moreover, I had some reasons for doing that. firstly, version -09 added
>> the section that was not present in -08 and if I added it now, there
>> would not be a possibility to discuss it. Version -10 presented the most
>
> There was no stability *because* of these updates.
>
>> stable one to reflect all the comments I received during the LC. And -11
>> was prepared as final for IESG review.
>
> My recommendation to the IESG is to wait for a stable spec, and then 
> restart the LC.
>
>> I have fully answered all the question form the message you refer to.
>>>
>>> I also mentioned at least once that in many frameworks this is
>>> essentially un-implementable, as different types of header fields are
>>> processed by different, independent layers in the code, and thus
>>> there's no way some part of the code will ever *know* which headers
>>> have been "processed". Do you think that this is not a problem?
>> That is the issues that would be decided by the implementators.
>> Moreover, one code layer may support this technology while others may 
>> not.
>
> How so? If a servlet does support it, but the servlet container does 
> not, there's no way to generate a correct header field value.
>
>>>> ...
>>>> * Syntax: Changed. Now is not /token**/but /1*VCAHR /for definition
>>>> of the name of the header.
>>>> ...
>>>
>>> Why?
>> RFC2616 gives the following definition of token:
>>
>> token = 1*<any CHAR except CTLs or separators>
>> separators = "(" | ")" | "<" |">" | "@"
>> | "," | ";" | ":" | "\" |<">
>> | "/" | "[" | "]" | "?" | "="
>> | "{" | "}" | SP | HT
>>
>>
>>
>> And non-visible chars are not allowed in headers. So only VCHARs.
>
> That didn't answer my question. Why did you change something that was 
> ok? It also shows why you'll need a new LC.
>
> In this particular case the change wasn't only not necessary, but also 
> changes the syntax significantly. VCHAR allows significantly more 
> characters than HTTP's token, namely the comma that you already need 
> as delimiter.
>
> Well, assuming you mean the VCHAR definition from RFC 5234, because 
> your spec doesn't clearly say where it comes from (you could import 
> specific productions or all of them from 5234, but you should say that).
>
> Speaking of which: you can't have a "_" character in a rule name.
>
> Best regards, Julian
>
>
>


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Hello all,<br>
    <br>
    I have revised all the comments I received now and during the Last
    Call.  My previous message was just formal stating statistical data
    on LC.  Here I'd like to mention what I really think of the document
    and its further destiny.<br>
    <br>
    Many LC comments referred to that it would be uninteresting and
    useless to implement this.  Maybe one of them seems the most
    interesting for me - it said about the 'Warning' headers that should
    be used in this occasion.  This, IMO, is one of the most suitable
    for me and this technology.  But if we implement this now using
    Warning, one problem is absence of IANA registry for Warning codes,
    such as for Status codes.  As this message is now sent to httpbis WG
    mailing list, I ask you if there is a sense in creating such
    registry?<br>
    <br>
    As for the initial draft, I think I'm about to withdraw <i>it </i>(but
    not my idea).  So result of Last Call seems to be the following: the
    idea in the current implementation as Internet-Draft does not seem
    to be appropriate.  So I'll raise this topic later.<br>
    <br>
    All the best,<br>
    Mykyta Yevstifeyev<br>
     <br>
    08.01.2011 13:17, Julian Reschke wrote:
    <blockquote cite="mid:4D2847E1.9090004@gmx.de" type="cite">On
      08.01.2011 11:19, Mykyta Yevstifeyev wrote:
      <br>
      <blockquote type="cite">
        <blockquote type="cite">If a draft changes three times during
          LC, there may be a problem. I
          <br>
          encourage you to go back to the drawing board, and think
          hard(er about
          <br>
          the feedback you got, in particular
          <br>
<a class="moz-txt-link-rfc2396E" href="http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html">&lt;http://lists.w3.org/Archives/Public/ietf-http-wg/2010OctDec/0645.html&gt;</a>.
          <br>
        </blockquote>
        Why do you think that the draft shouldn't be changed during LC?
        <br>
      </blockquote>
      <br>
      Because people assume stability during LC, and are unlikely to
      review the spec multiple times during the same LC.
      <br>
      <br>
      Of course that does not mean that you can't start addressing
      issues during LC. Just do so in a way that it doesn't change
      what's being last-called. For instance, by publishing the current
      edits on a private web page.
      <br>
      <br>
      If you have non-editorial changes, the AD will have to decide
      whether they require a new LC.
      <br>
      <br>
      <blockquote type="cite">Moreover, I had some reasons for doing
        that. firstly, version -09 added
        <br>
        the section that was not present in -08 and if I added it now,
        there
        <br>
        would not be a possibility to discuss it. Version -10 presented
        the most
        <br>
      </blockquote>
      <br>
      There was no stability *because* of these updates.
      <br>
      <br>
      <blockquote type="cite">stable one to reflect all the comments I
        received during the LC. And -11
        <br>
        was prepared as final for IESG review.
        <br>
      </blockquote>
      <br>
      My recommendation to the IESG is to wait for a stable spec, and
      then restart the LC.
      <br>
      <br>
      <blockquote type="cite">I have fully answered all the question
        form the message you refer to.
        <br>
        <blockquote type="cite">
          <br>
          I also mentioned at least once that in many frameworks this is
          <br>
          essentially un-implementable, as different types of header
          fields are
          <br>
          processed by different, independent layers in the code, and
          thus
          <br>
          there's no way some part of the code will ever *know* which
          headers
          <br>
          have been "processed". Do you think that this is not a
          problem?
          <br>
        </blockquote>
        That is the issues that would be decided by the implementators.
        <br>
        Moreover, one code layer may support this technology while
        others may not.
        <br>
      </blockquote>
      <br>
      How so? If a servlet does support it, but the servlet container
      does not, there's no way to generate a correct header field value.
      <br>
      <br>
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">...
            <br>
            * Syntax: Changed. Now is not /token**/but /1*VCAHR /for
            definition
            <br>
            of the name of the header.
            <br>
            ...
            <br>
          </blockquote>
          <br>
          Why?
          <br>
        </blockquote>
        RFC2616 gives the following definition of token:
        <br>
        <br>
        token = 1*&lt;any CHAR except CTLs or separators&gt;
        <br>
        separators = "(" | ")" | "&lt;" |"&gt;" | "@"
        <br>
        | "," | ";" | ":" | "\" |&lt;"&gt;
        <br>
        | "/" | "[" | "]" | "?" | "="
        <br>
        | "{" | "}" | SP | HT
        <br>
        <br>
        <br>
        <br>
        And non-visible chars are not allowed in headers. So only
        VCHARs.
        <br>
      </blockquote>
      <br>
      That didn't answer my question. Why did you change something that
      was ok? It also shows why you'll need a new LC.
      <br>
      <br>
      In this particular case the change wasn't only not necessary, but
      also changes the syntax significantly. VCHAR allows significantly
      more characters than HTTP's token, namely the comma that you
      already need as delimiter.
      <br>
      <br>
      Well, assuming you mean the VCHAR definition from RFC 5234,
      because your spec doesn't clearly say where it comes from (you
      could import specific productions or all of them from 5234, but
      you should say that).
      <br>
      <br>
      Speaking of which: you can't have a "_" character in a rule name.
      <br>
      <br>
      Best regards, Julian
      <br>
      <br>
      <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------070004030808040705020602--

From lixia@cs.ucla.edu  Sat Jan  8 08:00:42 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 304E628C10C for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:00:42 -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.001, 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 qmDAhKhQqA6w for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:00:41 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 034E828C10F for <ietf@ietf.org>; Sat,  8 Jan 2011 08:00:41 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 16BCA39E80F0; Sat,  8 Jan 2011 08:02:49 -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 u4eBQkS5khtA; Sat,  8 Jan 2011 08:02:47 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-174-94-219.socal.res.rr.com [76.174.94.219]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 763E939E8083; Sat,  8 Jan 2011 08:02:47 -0800 (PST)
Subject: Re: Old transport-layer protocols to Historic?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-4-515270047
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <4D26AC33.5090207@gmail.com>
Date: Sat, 8 Jan 2011 08:02:46 -0800
Message-Id: <EF470BEE-FC1E-4AA9-9DB3-C31BEDEB8DAE@cs.ucla.edu>
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <4D26AC33.5090207@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Braden <braden@isi.edu>, 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, 08 Jan 2011 16:00:42 -0000

--Apple-Mail-4-515270047
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jan 6, 2011, at 10:01 PM, Mykyta Yevstifeyev wrote:

> 06.01.2011 23:45, Doug Ewell wrote:
>>=20
>> Lixia Zhang <lixia at cs dot ucla dot edu> wrote:
>>=20
>>> PS: on the other hand, what would a "historical status" imply?  the =
ideas obsolete?
>> Every now and then, someone proposes to move a given RFC to Historic,
>> not merely to reflect an observation that a process or protocol is
>> obsolete, but as an active attempt to deprecate it, regardless of its
>> currency or relevance.
>>=20
>> I remember a few months ago, it was proposed (evidently not for the
>> first time) to move FTP to Historic, on the basis of its lack of
>> airtight 21st-century security features, with no consideration for =
the
>> innumerable existing systems and processes that have no need for
>> top-notch security, and rely daily on FTP.
>>=20
>> I often see comments on this list about whether the "outside world"
>> views the IETF as irrelevant.  Declaring a commonly used, core =
process
>> or protocol as Historic because something better exists might be a
>> perfect example of this.
> I think that the author of RFC2026 was wrong while writing the =
definition of Historic status. This document says that Historic should =
be assigned only to that documents that were standards and now are =
obsolete. But why do we need such narrow definition?

My understanding is that we want a well defined set of Internet standard =
protocols, with minimal ambiguity.

> Non-standards RFCs are not made Historic while obsoleting, according =
to 2026.

that is correct.
and I do not see anything wrong with it.

> Moreover, such status will just duplicate the obsoleted-by one. When =
there will be the attempt to revise RFC 2026, we should put there that =
Historic status is to be assigned to that documents that are considered =
to be deprecated. I fully share the opinion of Doug here.
>=20
> As for NETBLT, I am strongly against moving it to Historic, rather =
than specifying by Standards Track Document.

unless there is clearly identified need for a protocol like NETBLT (as =
its name suggested, it is a specialized protocol for bulk data transfer =
only), I do not see the need to move NETBLT to standard.

In case such a need is identified, personally I think we need a clear =
problem statement first, so that we better understand the context the =
protocol will be applied to.  We (the MIT crew at the time) did various =
trials of NETBLT after the RFC998's publication, and collected a list of =
issues for further investigation (of course we did not do it, as =
everyone moved on to other burning fires, and NETBLT served its purpose =
of proof-of-concept).

> There has been one attempt to do that by John White in 1995 (see =
draft-white-protocol-stack), but IMO (that likes strange, but...) we can =
align this document with the most current needs of Internet and publish.
>=20
> Mykyta
>> --
>> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
>> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20


--Apple-Mail-4-515270047
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jan 6, 2011, at 10:01 PM, Mykyta Yevstifeyev =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
<div bgcolor=3D"#ffffff" text=3D"#000000">
    06.01.2011 23:45, Doug Ewell wrote:
    <blockquote =
cite=3D"mid:20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe=
@email03.secureserver.net" type=3D"cite">
      <pre wrap=3D"">Lixia Zhang &lt;lixia at cs dot ucla dot edu&gt; =
wrote:

</pre>
      <blockquote type=3D"cite">
        <pre wrap=3D"">PS: on the other hand, what would a "historical =
status" imply?  the ideas obsolete?
</pre>
      </blockquote>
      <pre wrap=3D"">Every now and then, someone proposes to move a =
given RFC to Historic,
not merely to reflect an observation that a process or protocol is
obsolete, but as an active attempt to deprecate it, regardless of its
currency or relevance.

I remember a few months ago, it was proposed (evidently not for the
first time) to move FTP to Historic, on the basis of its lack of
airtight 21st-century security features, with no consideration for the
innumerable existing systems and processes that have no need for
top-notch security, and rely daily on FTP.

I often see comments on this list about whether the "outside world"
views the IETF as irrelevant.  Declaring a commonly used, core process
or protocol as Historic because something better exists might be a
perfect example of this.
</pre>
    </blockquote>
    I think that the author of RFC2026 was wrong while writing the
    definition of Historic status. This document says that Historic
    should be assigned only to that documents that were standards and
    now are obsolete. But why do we need such narrow =
definition?</div></blockquote><div><br></div>My understanding is that we =
want a well defined set of Internet standard protocols, with minimal =
ambiguity.</div><div><br><blockquote type=3D"cite"><div =
bgcolor=3D"#ffffff" text=3D"#000000">
    Non-standards RFCs are not made Historic while obsoleting, according
    to 2026.</div></blockquote><div><br></div>that is =
correct.</div><div>and I do not see anything wrong with =
it.</div><div><br><blockquote type=3D"cite"><div bgcolor=3D"#ffffff" =
text=3D"#000000"> Moreover, such status will just duplicate the =
obsoleted-by
    one. When there will be the attempt to revise RFC 2026, we should
    put there that Historic status is to be assigned to that documents
    that are considered to be <i>deprecated</i>. I fully share the
    opinion of Doug here.<br>
    <br>
    As for NETBLT, I am strongly against moving it to Historic, rather
    than specifying by Standards Track =
Document.</div></blockquote><div><br></div>unless there is clearly =
identified need for a protocol like NETBLT (as its name suggested, it is =
a specialized protocol for bulk data transfer only), I do not see the =
need to move NETBLT to standard.</div><div><br></div><div>In case such a =
need is identified, personally I think we need a clear problem statement =
first, so that we better understand the context the protocol will be =
applied to. &nbsp;We (the MIT crew at the time) did various trials of =
NETBLT after the RFC998's publication, and collected a list of issues =
for further investigation (of course we did not do it, as everyone moved =
on to other burning fires, and NETBLT served its purpose of =
proof-of-concept).</div><div><br><blockquote type=3D"cite"><div =
bgcolor=3D"#ffffff" text=3D"#000000"> There has been one
    attempt to do that by John White in 1995 (see
    draft-white-protocol-stack), but IMO (that likes strange, but...) we
    can align this document with the most current needs of Internet and
    publish.<br>
    <br>
    Mykyta<br>
    <blockquote =
cite=3D"mid:20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe=
@email03.secureserver.net" type=3D"cite">
      <pre wrap=3D"">--
Doug Ewell | Thornton, Colorado, USA | <a class=3D"moz-txt-link-freetext" =
href=3D"http://www.ewellic.org/">http://www.ewellic.org</a>
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD


_______________________________________________
Ietf mailing list
<a class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a class=3D"moz-txt-link-freetext" =
href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/m=
ailman/listinfo/ietf</a>
</pre>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></body></html>=

--Apple-Mail-4-515270047--

From lixia@cs.ucla.edu  Sat Jan  8 08:10:49 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 6A38828C120; Sat,  8 Jan 2011 08:10: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=[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 KC1vGZNqb6O0; Sat,  8 Jan 2011 08:10:48 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 5469128C11D; Sat,  8 Jan 2011 08:10:42 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 32CF939E80F0; Sat,  8 Jan 2011 08:12:50 -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 3F2mAThflSfq; Sat,  8 Jan 2011 08:12:49 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-174-94-219.socal.res.rr.com [76.174.94.219]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 4870F39E8083; Sat,  8 Jan 2011 08:12:49 -0800 (PST)
Subject: Re: Old transport-layer protocols to Historic?
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: <4D27F280.1020205@gmail.com>
Date: Sat, 8 Jan 2011 08:12:48 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AE9FE30-47F2-4966-BDAF-B27B6437906F@cs.ucla.edu>
References: <4D2556C9.9020901@gmail.com> <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com> <4D27F280.1020205@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, tsvwg@ietf.org, IETF Discussion <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, 08 Jan 2011 16:10:50 -0000

On Jan 7, 2011, at 9:13 PM, Mykyta Yevstifeyev wrote:

> 07.01.2011 21:53, Bob Hinden wrote:
>> Mykyta,
>>=20
>>=20
>> On Jan 5, 2011, at 9:44 PM, Mykyta Yevstifeyev wrote:
>>=20
>>> Hello all,
>>>=20
>>> There have been a discussion on tsvwg mailing list about old =
transport layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and =
NETBLT (RFC998). Initially there have been proposed to define IANA =
considerations for them. But after a discussion it was found out that it =
would be better to move them to Historic. I am writing to request more =
wider discussion on this topic.
>> I see little value even thinking about this.  It's looks like a "make =
work" project to me.  Just because something is "old", doesn't mean it =
is "historic" in the sense the label is used in the IETF.
>>=20
>> Regarding RDP (RFC908, RFC1151), of which I am one of the authors, =
both are currently labeled as Experimental.  I do not see any reason to =
change that.
>>=20
>> Bob
>>=20
>>=20
> Dear all,
>=20
> RFC2026 mentions:
>=20
>>  A specification that has been superseded by a more recent
>>    specification or is for any other reason considered to be obsolete =
is
>>    assigned to the "Historic" level.
> and gives 2 reasons for making the RFC Historic: 1) RFC is obsoleted =
(superseded) or 2) obsolete.
>=20
> Obsoleted =3D made obsolete. This is obvious. When one RFC replaces =
another, it obsoletes it, and second becomes obsolete.
>=20
> What is obsolete (adj.)? Obsolete =3D deprecated, outdated, out of =
use, non-current, etc.
>=20
> Moreover, RFC2026 does not set any other guidelines for setting the =
Historic status.

that is because only standard track protocols need such guidelines

> That is why if the protocol is out of use, even specified by =
Experimental RFC, it is a reason to move its spec. to Historic, in =
accordance with RFC2026.

First, you said RFC2026 did *not* say anything on moving non-standard =
protocols to Historic status.

Then you said Experimental RFCs need to move to Historic, in accordance =
with RFC2026.

Doesn't this sound self-conflicting to you?

Lixia


From evnikita2@gmail.com  Sat Jan  8 08:13:43 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 0016B28C118 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.004
X-Spam-Level: 
X-Spam-Status: No, score=-3.004 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_55=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 DRTPLbcT2WPc for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:13:41 -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 8CA6828C115 for <ietf@ietf.org>; Sat,  8 Jan 2011 08:13:40 -0800 (PST)
Received: by bwz12 with SMTP id 12so17994435bwz.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 08:15:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=OwxOgn6ZCCkbQNCyCfKitck6BBF/aMDaYnpcirX+s18=; b=NMB64jBI7VGSTgSCr2eXAPPflNcz12+w9IpVJYCd2KOsYXZzSbLbq6LTeJQ4c9tkdI hdJtRYadNKNopA6kdhLr+iVV8DrRBAVj2LauYebwUsMWSpNaSXUuX60IRnaSvuGgiWtb M/mU2iUMgctENJX4UVvpTp6pd3eOSLYbobbJ0=
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=mTTu3FS/UGabr08kH9U9OfmCqzXTOT75/3NRPm1fG4ZN0w6FIwTOvxPfjgPj+n2ZDb bNGmntC5JXEQxcb39RHRn/fBTMpEhdur/Aj4pK8SB0zu5Saqw0E7ETzzIKbNu+l/M/F8 lrYLBtQDUiCQIJdtYoTU5F9rNBVI4uIykra6M=
Received: by 10.204.59.16 with SMTP id j16mr10551833bkh.138.1294503346362; Sat, 08 Jan 2011 08:15:46 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id d27sm14653805bkw.2.2011.01.08.08.15.44 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 08:15:45 -0800 (PST)
Message-ID: <4D288DC2.3060507@gmail.com>
Date: Sat, 08 Jan 2011 18:16:02 +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: Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: Old transport-layer protocols to Historic?
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <4D26AC33.5090207@gmail.com> <EF470BEE-FC1E-4AA9-9DB3-C31BEDEB8DAE@cs.ucla.edu>
In-Reply-To: <EF470BEE-FC1E-4AA9-9DB3-C31BEDEB8DAE@cs.ucla.edu>
Content-Type: multipart/alternative; boundary="------------030001040303060302040205"
Cc: Bob Braden <braden@isi.edu>, 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, 08 Jan 2011 16:13:43 -0000

This is a multi-part message in MIME format.
--------------030001040303060302040205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

08.01.2011 18:02, Lixia Zhang wrote:
>
> On Jan 6, 2011, at 10:01 PM, Mykyta Yevstifeyev wrote:
>
>> 06.01.2011 23:45, Doug Ewell wrote:
>>> Lixia Zhang<lixia at cs dot ucla dot edu>  wrote:
>>>
>>>> PS: on the other hand, what would a "historical status" imply?  the ideas obsolete?
>>> Every now and then, someone proposes to move a given RFC to Historic,
>>> not merely to reflect an observation that a process or protocol is
>>> obsolete, but as an active attempt to deprecate it, regardless of its
>>> currency or relevance.
>>>
>>> I remember a few months ago, it was proposed (evidently not for the
>>> first time) to move FTP to Historic, on the basis of its lack of
>>> airtight 21st-century security features, with no consideration for the
>>> innumerable existing systems and processes that have no need for
>>> top-notch security, and rely daily on FTP.
>>>
>>> I often see comments on this list about whether the "outside world"
>>> views the IETF as irrelevant.  Declaring a commonly used, core process
>>> or protocol as Historic because something better exists might be a
>>> perfect example of this.
>> I think that the author of RFC2026 was wrong while writing the 
>> definition of Historic status. This document says that Historic 
>> should be assigned only to that documents that were standards and now 
>> are obsolete. But why do we need such narrow definition?
>
> My understanding is that we want a well defined set of Internet 
> standard protocols, with minimal ambiguity.
>
>> Non-standards RFCs are not made Historic while obsoleting, according 
>> to 2026.
>
> that is correct.
> and I do not see anything wrong with it.
Where do we have it in RFC2026?  Also see 
http://www.ietf.org/mail-archive/web/ietf/current/msg65052.html for some 
thoughts on 'obsolete' and 'obsoleted' terms.
>
>> Moreover, such status will just duplicate the obsoleted-by one. When 
>> there will be the attempt to revise RFC 2026, we should put there 
>> that Historic status is to be assigned to that documents that are 
>> considered to be /deprecated/. I fully share the opinion of Doug here.
>>
>> As for NETBLT, I am strongly against moving it to Historic, rather 
>> than specifying by Standards Track Document.
>
> unless there is clearly identified need for a protocol like NETBLT (as 
> its name suggested, it is a specialized protocol for bulk data 
> transfer only), I do not see the need to move NETBLT to standard.
Nobody currently wants that.  We want to publish it as Experimental (if 
you refer to draft-white-tsvwg-netblt) but updated.
>
> In case such a need is identified, personally I think we need a clear 
> problem statement first, so that we better understand the context the 
> protocol will be applied to.  We (the MIT crew at the time) did 
> various trials of NETBLT after the RFC998's publication, and collected 
> a list of issues for further investigation (of course we did not do 
> it, as everyone moved on to other burning fires, and NETBLT served its 
> purpose of proof-of-concept).
>
>> There has been one attempt to do that by John White in 1995 (see 
>> draft-white-protocol-stack), but IMO (that likes strange, but...) we 
>> can align this document with the most current needs of Internet and 
>> publish.
>>
>> Mykyta
>>> --
>>> Doug Ewell | Thornton, Colorado, USA |http://www.ewellic.org
>>> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­
>>>
>>>
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>
>


--------------030001040303060302040205
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">
    08.01.2011 18:02, Lixia Zhang wrote:
    <blockquote
      cite="mid:EF470BEE-FC1E-4AA9-9DB3-C31BEDEB8DAE@cs.ucla.edu"
      type="cite"><br>
      <div>
        <div>On Jan 6, 2011, at 10:01 PM, Mykyta Yevstifeyev wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">
          <div bgcolor="#ffffff" text="#000000"> 06.01.2011 23:45, Doug
            Ewell wrote:
            <blockquote
cite="mid:20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net"
              type="cite">
              <pre wrap="">Lixia Zhang &lt;lixia at cs dot ucla dot edu&gt; wrote:

</pre>
              <blockquote type="cite">
                <pre wrap="">PS: on the other hand, what would a "historical status" imply?  the ideas obsolete?
</pre>
              </blockquote>
              <pre wrap="">Every now and then, someone proposes to move a given RFC to Historic,
not merely to reflect an observation that a process or protocol is
obsolete, but as an active attempt to deprecate it, regardless of its
currency or relevance.

I remember a few months ago, it was proposed (evidently not for the
first time) to move FTP to Historic, on the basis of its lack of
airtight 21st-century security features, with no consideration for the
innumerable existing systems and processes that have no need for
top-notch security, and rely daily on FTP.

I often see comments on this list about whether the "outside world"
views the IETF as irrelevant.  Declaring a commonly used, core process
or protocol as Historic because something better exists might be a
perfect example of this.
</pre>
            </blockquote>
            I think that the author of RFC2026 was wrong while writing
            the definition of Historic status. This document says that
            Historic should be assigned only to that documents that were
            standards and now are obsolete. But why do we need such
            narrow definition?</div>
        </blockquote>
        <div><br>
        </div>
        My understanding is that we want a well defined set of Internet
        standard protocols, with minimal ambiguity.</div>
      <div><br>
        <blockquote type="cite">
          <div bgcolor="#ffffff" text="#000000"> Non-standards RFCs are
            not made Historic while obsoleting, according to 2026.</div>
        </blockquote>
        <div><br>
        </div>
        that is correct.</div>
      <div>and I do not see anything wrong with it.</div>
    </blockquote>
    Where do we have it in RFC2026?&nbsp; Also see
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/mail-archive/web/ietf/current/msg65052.html">http://www.ietf.org/mail-archive/web/ietf/current/msg65052.html</a> for
    some thoughts on 'obsolete' and 'obsoleted' terms.<br>
    <blockquote
      cite="mid:EF470BEE-FC1E-4AA9-9DB3-C31BEDEB8DAE@cs.ucla.edu"
      type="cite">
      <div><br>
        <blockquote type="cite">
          <div bgcolor="#ffffff" text="#000000"> Moreover, such status
            will just duplicate the obsoleted-by one. When there will be
            the attempt to revise RFC 2026, we should put there that
            Historic status is to be assigned to that documents that are
            considered to be <i>deprecated</i>. I fully share the
            opinion of Doug here.<br>
            <br>
            As for NETBLT, I am strongly against moving it to Historic,
            rather than specifying by Standards Track Document.</div>
        </blockquote>
        <div><br>
        </div>
        unless there is clearly identified need for a protocol like
        NETBLT (as its name suggested, it is a specialized protocol for
        bulk data transfer only), I do not see the need to move NETBLT
        to standard.</div>
    </blockquote>
    Nobody currently wants that.&nbsp; We want to publish it as Experimental
    (if you refer to draft-white-tsvwg-netblt) but updated.<br>
    <blockquote
      cite="mid:EF470BEE-FC1E-4AA9-9DB3-C31BEDEB8DAE@cs.ucla.edu"
      type="cite">
      <div><br>
      </div>
      <div>In case such a need is identified, personally I think we need
        a clear problem statement first, so that we better understand
        the context the protocol will be applied to. &nbsp;We (the MIT crew
        at the time) did various trials of NETBLT after the RFC998's
        publication, and collected a list of issues for further
        investigation (of course we did not do it, as everyone moved on
        to other burning fires, and NETBLT served its purpose of
        proof-of-concept).</div>
      <div><br>
        <blockquote type="cite">
          <div bgcolor="#ffffff" text="#000000"> There has been one
            attempt to do that by John White in 1995 (see
            draft-white-protocol-stack), but IMO (that likes strange,
            but...) we can align this document with the most current
            needs of Internet and publish.<br>
            <br>
            Mykyta<br>
            <blockquote
cite="mid:20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net"
              type="cite">
              <pre wrap="">--
Doug Ewell | Thornton, Colorado, USA | <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.ewellic.org/">http://www.ewellic.org</a>
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s &shy;


_______________________________________________
Ietf mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
            </blockquote>
            <br>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------030001040303060302040205--

From evnikita2@gmail.com  Sat Jan  8 08:17:10 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 0F97028C156; Sat,  8 Jan 2011 08:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.304
X-Spam-Level: 
X-Spam-Status: No, score=-3.304 tagged_above=-999 required=5 tests=[AWL=0.295,  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 zfVBVLaUK3kJ; Sat,  8 Jan 2011 08:17:09 -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 706813A6975; Sat,  8 Jan 2011 08:17:05 -0800 (PST)
Received: by bwz12 with SMTP id 12so17996019bwz.31 for <multiple recipients>; Sat, 08 Jan 2011 08:19:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ogI3KzOanR4HQyhzcI6VdG7VVFhx59oeatkozyWRe8Q=; b=tUbmTqdJ7ut2odyCIh6NPgaPvL7Zlkzw2YUZ7AMUDJODmB9gdTXJMpzZvEZRhCa/JH w7VaCI8o4JjVj7CgDaXI672P8nqdxnnWfdGomcofdBU9vbStauI1ydvmmczQ6qnlNv4J kC5uPsZeuhgiAVVQ/4oQapaXS1rhdq6mf5ohM=
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=ZS6OFCrZYJuiEE4fBpV+LqmatzJAUvBC9I4U9a1JxUoWB+u+XcGfk09+DgxzDnl1HB zfjLtu995EwR1FU5rXTov+eTL3u2gvb881SDmW5LAQnNco+i3PQHgJkj7hxsIAqmo29E 1TTVnIVkioO/MCEzeHKByUh3PJ8S59yhGW7+k=
Received: by 10.204.59.72 with SMTP id k8mr489424bkh.84.1294503553112; Sat, 08 Jan 2011 08:19:13 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id d27sm14778534bkw.14.2011.01.08.08.19.11 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 08:19:12 -0800 (PST)
Message-ID: <4D288E91.9040700@gmail.com>
Date: Sat, 08 Jan 2011 18:19:29 +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: Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com> <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com> <4D27F280.1020205@gmail.com> <4AE9FE30-47F2-4966-BDAF-B27B6437906F@cs.ucla.edu>
In-Reply-To: <4AE9FE30-47F2-4966-BDAF-B27B6437906F@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, tsvwg@ietf.org, IETF Discussion <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, 08 Jan 2011 16:17:10 -0000

08.01.2011 18:12, Lixia Zhang wrote:
> On Jan 7, 2011, at 9:13 PM, Mykyta Yevstifeyev wrote:
>
>> 07.01.2011 21:53, Bob Hinden wrote:
>>> Mykyta,
>>>
>>>
>>> On Jan 5, 2011, at 9:44 PM, Mykyta Yevstifeyev wrote:
>>>
>>>> Hello all,
>>>>
>>>> There have been a discussion on tsvwg mailing list about old transport layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT (RFC998). Initially there have been proposed to define IANA considerations for them. But after a discussion it was found out that it would be better to move them to Historic. I am writing to request more wider discussion on this topic.
>>> I see little value even thinking about this.  It's looks like a "make work" project to me.  Just because something is "old", doesn't mean it is "historic" in the sense the label is used in the IETF.
>>>
>>> Regarding RDP (RFC908, RFC1151), of which I am one of the authors, both are currently labeled as Experimental.  I do not see any reason to change that.
>>>
>>> Bob
>>>
>>>
>> Dear all,
>>
>> RFC2026 mentions:
>>
>>>   A specification that has been superseded by a more recent
>>>     specification or is for any other reason considered to be obsolete is
>>>     assigned to the "Historic" level.
>> and gives 2 reasons for making the RFC Historic: 1) RFC is obsoleted (superseded) or 2) obsolete.
>>
>> Obsoleted = made obsolete. This is obvious. When one RFC replaces another, it obsoletes it, and second becomes obsolete.
>>
>> What is obsolete (adj.)? Obsolete = deprecated, outdated, out of use, non-current, etc.
>>
>> Moreover, RFC2026 does not set any other guidelines for setting the Historic status.
> that is because only standard track protocols need such guidelines
Where is that, once more?
>> That is why if the protocol is out of use, even specified by Experimental RFC, it is a reason to move its spec. to Historic, in accordance with RFC2026.
> First, you said RFC2026 did *not* say anything on moving non-standard protocols to Historic status.
>
> Then you said Experimental RFCs need to move to Historic, in accordance with RFC2026.
RFC2026 in Section 4.2.4. says nothing about this.  It is indefinite, 
per this section.  What you said 'first' was what do all think.  And the 
second what I do.  And maybe not need to move but may be moved.

Mykyta Yevstifeyev
> Doesn't this sound self-conflicting to you?
>
> Lixia
>
>


From lixia@cs.ucla.edu  Sat Jan  8 08:22:09 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 4DC7428C127 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 3Wn583uPnG2S for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:22:07 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id 12A2228C140 for <ietf@ietf.org>; Sat,  8 Jan 2011 08:22:06 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 83EF639E80F0; Sat,  8 Jan 2011 08:24:14 -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 5nUmImMcRm0x; Sat,  8 Jan 2011 08:24:13 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-174-94-219.socal.res.rr.com [76.174.94.219]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 79BDF39E8083; Sat,  8 Jan 2011 08:24:13 -0800 (PST)
Subject: Re: I-D Action:draft-white-tsvwg-netblt-00.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-5-516556845
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <4D2886CF.5020205@gmail.com>
Date: Sat, 8 Jan 2011 08:24:12 -0800
Message-Id: <138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu>
References: <20110108110002.19936.59779.idtracker@localhost> <6E426D9B-104E-4579-9BAD-63B2FD0AF90C@cs.ucla.edu> <4D2886CF.5020205@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: John White <jccw@jccw.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: Sat, 08 Jan 2011 16:22:09 -0000

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


On Jan 8, 2011, at 7:46 AM, Mykyta Yevstifeyev wrote:

> 08.01.2011 17:37, Lixia Zhang wrote:
>> I am not sure why this rush to get a new internet draft out, without =
consultation to any of its original authors, and given the rough =
consensus on ietf mailing list discussion is to keep NETBLT RFC as is =
(experimental).
>=20
> First of all, I've consulted the initial author of it, John White, and =
some other people off-list.

With all the respect to John, he is not among the original authors of =
NETBLT RFC.
Wonder if you can tell me who are the other people that you contacted?


>  The NETBLT spec found in RFC998 *as is* could not be appropriate for =
current Internet,

It was not meant to. It's for discussion and comment.

As I already quoted this in my earlier msg: RFC998 stated clearly that=20=


   This document is published for discussion and comment, and does not
   constitute a standard.  The proposal may change and certain parts of
   the protocol have not yet been specified; implementation of this
   document is therefore not advised.


> so there is a need for another one.  In the next 3 months, I think, we =
will be a work on it.  Moreover, we plan to submit it as Independent =
Submission as Experimental RFC, despites it mentions the Standards Track =
one.
>=20
> Mykyta

I am confused here:
in your message posted on Jan 7 (2 days ago),=20
http://www.ietf.org/mail-archive/web/ietf/current/msg65041.html
you said

As for NETBLT, I am strongly against moving it to Historic, rather than =
specifying by Standards Track Document. There has been one attempt to do =
that by John White in 1995 (see draft-white-protocol-stack), but IMO =
(that likes strange, but...) we can align this document with the most =
current needs of Internet and publish.

Mykyta

but now you changed your mind?

Lixia

>> Lixia
>>=20
>> On Jan 8, 2011, at 3:00 AM, Internet-Drafts@ietf.org wrote:
>>=20
>>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>>>=20
>>> 	Title           : Network Block Transfer Protocol (NETBLT)
>>> 	Author(s)       : J. White, M. Yevstifeyev
>>> 	Filename        : draft-white-tsvwg-netblt-00.txt
>>> 	Pages           : 34
>>> 	Date            : 2011-01-08
>>>=20
>>> This document is a specification of version 5 of Network Block
>>> Transfer Protocol (NETBLT). This protocol was firstly specified in
>>> RFC 969, that has been made obsolete by RFC 998. Nevertheless, none
>>> of these documents match current Internet Standards and are
>>> deprecated. This document aligns the NETBLT specification with the
>>> most current Internet Standards and obsoletes RFC 998.
>>>=20
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.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
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-5-516556845
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 Jan 8, 2011, at 7:46 AM, Mykyta Yevstifeyev =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>08.01.2011 17:37, Lixia Zhang wrote:<br><blockquote =
type=3D"cite">I am not sure why this rush to get a new internet draft =
out, without consultation to any of its original authors, and given the =
rough consensus on ietf mailing list discussion is to keep NETBLT RFC as =
is (experimental).<br></blockquote></div></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><div>First of =
all, I've consulted the initial author of it, John White, and some other =
people off-list. </div></blockquote><div><br></div>With all the respect =
to John, he is not among the original authors of NETBLT =
RFC.</div><div>Wonder if you can tell me who are the other people that =
you contacted?</div><div><br></div><div><br><blockquote =
type=3D"cite"><div>&nbsp;The NETBLT spec found in RFC998 *as is* could =
not be appropriate for current =
Internet,</div></blockquote><div><br></div>It was not meant to. It's for =
discussion and comment.</div><div><br></div><div>As I already quoted =
this in my earlier msg: RFC998 stated clearly =
that&nbsp;</div><div><br></div><div><div>&nbsp;&nbsp; This document is =
published for discussion and comment, and does =
not</div><div>&nbsp;&nbsp; constitute a standard. &nbsp;The proposal may =
change and certain parts of</div><div>&nbsp;&nbsp; the protocol have not =
yet been specified; implementation of this</div><div>&nbsp;&nbsp; =
document is therefore not =
advised.</div><div><br></div></div><div><br><blockquote =
type=3D"cite"><div> so there is a need for another one. &nbsp;In the =
next 3 months, I think, we will be a work on it. &nbsp;Moreover, we plan =
to submit it as Independent Submission as Experimental RFC, despites it =
mentions the Standards Track =
one.<br><br>Mykyta<br></div></blockquote><div><br></div>I am confused =
here:</div><div>in your message posted on Jan 7 (2 days =
ago),&nbsp;</div><div><a =
href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg65041.html">h=
ttp://www.ietf.org/mail-archive/web/ietf/current/msg65041.html</a></div><d=
iv>you said</div><div><br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;"><div>As for NETBLT, I am strongly against moving it =
to Historic, rather than specifying by Standards Track&nbsp;Document. =
There has been one attempt to do that by John White in 1995 (see =
draft-white-protocol-stack), but&nbsp;IMO (that likes strange, but...) =
we can align this document with the most current needs of Internet =
and&nbsp;publish.</div><div><br></div><div>Mykyta</div></blockquote><div><=
br></div><div>but now you changed your =
mind?</div><div><br></div><div>Lixia</div><div><br><blockquote =
type=3D"cite"><div><blockquote =
type=3D"cite">Lixia<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Jan 8, 2011, =
at 3:00 AM, <a =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> =
wrote:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">A New Internet-Draft is available from the on-line =
Internet-Drafts directories.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Network =
Block Transfer Protocol =
(NETBLT)<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: J. White, M. =
Yevstifeyev<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-white-tsvwg-netblt-00.txt<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
34<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2011-01-08<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">This document is a specification =
of version 5 of Network Block<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Transfer Protocol (NETBLT). This =
protocol was firstly specified =
in<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">RFC 969, that has been made obsolete by RFC 998. =
Nevertheless, none<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">of these documents match current =
Internet Standards and are<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">deprecated. This document aligns =
the NETBLT specification with =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">most current Internet Standards and obsoletes RFC =
998.<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">A URL for this Internet-Draft =
is:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.tx=
t">http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.txt</a>=
<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Internet-Drafts are also =
available by anonymous FTP at:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-d=
rafts/</a><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Below is the data which will =
enable a MIME compliant mail =
reader<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">implementation to automatically retrieve the ASCII version =
of the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Internet-Draft.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">&lt;Mail =
Attachment&gt;_______________________________________________<br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">I-D-Announce mailing =
list<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><a =
href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br></block=
quote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.ie=
tf.org/mailman/listinfo/i-d-announce</a><br></blockquote></blockquote><blo=
ckquote type=3D"cite"><blockquote type=3D"cite">Internet-Draft =
directories: <a =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
a><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">or <a =
href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf=
/1shadow-sites.txt</a><br></blockquote></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">Ietf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br></blockquote><blockquot=
e type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/m=
ailman/listinfo/ietf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>_______________________________________=
________<br>Ietf mailing list<br><a =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>https://www.ietf.org/ma=
ilman/listinfo/ietf<br></div></blockquote></div><br></body></html>=

--Apple-Mail-5-516556845--

From evnikita2@gmail.com  Sat Jan  8 08:31:16 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 00E8B28C11D for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:31:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.307
X-Spam-Level: 
X-Spam-Status: No, score=-3.307 tagged_above=-999 required=5 tests=[AWL=0.291,  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 Qsg3i0pmoCeo for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:31:14 -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 04C0228C116 for <ietf@ietf.org>; Sat,  8 Jan 2011 08:31:13 -0800 (PST)
Received: by bwz12 with SMTP id 12so18001445bwz.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 08:33:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=9AD1TD9FkGWN6ueCr6XB59WhjyD6E8EIEGoDhyTYdIo=; b=MWXfgw0fgjj7qUelKlLKBqNAnMn+nBOqHNpVd/qR429JRCfrHsAaRlgC7juZRozcc5 ++y2voOm10Kjcg7d3Eqo62vb7NcNLsncB4GPE0sobJ4fkdfNut41ZGzs0xOxf+ShNpCc 5kg51llyGIxSQSKF+yafRQTHFRTBuS0pUMNE8=
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=H69w3dypkKCjYDshanToqIlr4lF/i482Rw7i5jUNNCghTGC9Cnyyjz5Y0hfwU/Cg5z 7tvYFn0p1RwbDFJAHzEwOR5Yt66S5acWISvHRMRu7Q376fdi/9XlV9R1D7b/rMot9Yvl 1epAxdPz5euX+DPLA7LjGePuo7o6Mfl8ER5wc=
Received: by 10.204.66.79 with SMTP id m15mr3973950bki.124.1294504399712; Sat, 08 Jan 2011 08:33:19 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id f20sm12254045bkf.16.2011.01.08.08.33.16 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 08:33:18 -0800 (PST)
Message-ID: <4D2891DD.5050108@gmail.com>
Date: Sat, 08 Jan 2011 18:33:33 +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: Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: I-D Action:draft-white-tsvwg-netblt-00.txt
References: <20110108110002.19936.59779.idtracker@localhost> <6E426D9B-104E-4579-9BAD-63B2FD0AF90C@cs.ucla.edu> <4D2886CF.5020205@gmail.com> <138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu>
In-Reply-To: <138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu>
Content-Type: multipart/alternative; boundary="------------080704050101030800080501"
Cc: John White <jccw@jccw.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: Sat, 08 Jan 2011 16:31:16 -0000

This is a multi-part message in MIME format.
--------------080704050101030800080501
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

08.01.2011 18:24, Lixia Zhang wrote:
>
> On Jan 8, 2011, at 7:46 AM, Mykyta Yevstifeyev wrote:
>
>> 08.01.2011 17:37, Lixia Zhang wrote:
>>> I am not sure why this rush to get a new internet draft out, without 
>>> consultation to any of its original authors, and given the rough 
>>> consensus on ietf mailing list discussion is to keep NETBLT RFC as 
>>> is (experimental).
>>
>> First of all, I've consulted the initial author of it, John White, 
>> and some other people off-list.
>
> With all the respect to John, he is not among the original authors of 
> NETBLT RFC.
I thought you meant the draft.  How can we contact them if we do not 
have any point of contact in the RFC?
> Wonder if you can tell me who are the other people that you contacted?
Why are you so interested in it?  What benefit would you have if you get 
known that?
>
>
>>  The NETBLT spec found in RFC998 *as is* could not be appropriate for 
>> current Internet,
>
> It was not meant to. It's for discussion and comment.
And what you cited is a comment.
>
> As I already quoted this in my earlier msg: RFC998 stated clearly that
>
>    This document is published for discussion and comment, and does not
>    constitute a standard.  The proposal may change and certain parts of
>    the protocol have not yet been specified; implementation of this
>    document is therefore not advised.
>
>
>> so there is a need for another one.  In the next 3 months, I think, 
>> we will be a work on it.  Moreover, we plan to submit it as 
>> Independent Submission as Experimental RFC, despites it mentions the 
>> Standards Track one.
>>
>> Mykyta
>
> I am confused here:
> in your message posted on Jan 7 (2 days ago),
> http://www.ietf.org/mail-archive/web/ietf/current/msg65041.html
> you said
>
>     As for NETBLT, I am strongly against moving it to Historic, rather
>     than specifying by Standards Track Document. There has been one
>     attempt to do that by John White in 1995 (see
>     draft-white-protocol-stack), but IMO (that likes strange, but...)
>     we can align this document with the most current needs of Internet
>     and publish.
>
>     Mykyta
>
>
> but now you changed your mind?
Not, I have not.  If that was, I wouldn't publish the 
draft-white-tsvwg-netblt.  I desired to move the IRTP to Historic only 
rather that other protocols I mentioned.
>
> Lixia
>
>>> Lixia
>>>
>>> On Jan 8, 2011, at 3:00 AM, Internet-Drafts@ietf.org 
>>> <mailto:Internet-Drafts@ietf.org> wrote:
>>>
>>>> A New Internet-Draft is available from the on-line Internet-Drafts 
>>>> directories.
>>>>
>>>> Title           : Network Block Transfer Protocol (NETBLT)
>>>> Author(s)       : J. White, M. Yevstifeyev
>>>> Filename        : draft-white-tsvwg-netblt-00.txt
>>>> Pages           : 34
>>>> Date            : 2011-01-08
>>>>
>>>> This document is a specification of version 5 of Network Block
>>>> Transfer Protocol (NETBLT). This protocol was firstly specified in
>>>> RFC 969, that has been made obsolete by RFC 998. Nevertheless, none
>>>> of these documents match current Internet Standards and are
>>>> deprecated. This document aligns the NETBLT specification with the
>>>> most current Internet Standards and obsoletes RFC 998.
>>>>
>>>> A URL for this Internet-Draft is:
>>>> http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.txt
>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> 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 <mailto: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
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org <mailto:Ietf@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org <mailto:Ietf@ietf.org>
>> https://www.ietf.org/mailman/listinfo/ietf
>


--------------080704050101030800080501
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">
    08.01.2011 18:24, Lixia Zhang wrote:
    <blockquote
      cite="mid:138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu"
      type="cite"><br>
      <div>
        <div>On Jan 8, 2011, at 7:46 AM, Mykyta Yevstifeyev wrote:</div>
        <br class="Apple-interchange-newline">
        <blockquote type="cite">
          <div>08.01.2011 17:37, Lixia Zhang wrote:<br>
            <blockquote type="cite">I am not sure why this rush to get a
              new internet draft out, without consultation to any of its
              original authors, and given the rough consensus on ietf
              mailing list discussion is to keep NETBLT RFC as is
              (experimental).<br>
            </blockquote>
          </div>
        </blockquote>
        <blockquote type="cite"><br>
        </blockquote>
        <blockquote type="cite">
          <div>First of all, I've consulted the initial author of it,
            John White, and some other people off-list. </div>
        </blockquote>
        <div><br>
        </div>
        With all the respect to John, he is not among the original
        authors of NETBLT RFC.</div>
    </blockquote>
    I thought you meant the draft.&nbsp; How can we contact them if we do not
    have any point of contact in the RFC?<br>
    <blockquote
      cite="mid:138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu"
      type="cite">
      <div>Wonder if you can tell me who are the other people that you
        contacted?</div>
    </blockquote>
    Why are you so interested in it?&nbsp; What benefit would you have if you
    get known that?<br>
    <blockquote
      cite="mid:138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu"
      type="cite">
      <div><br>
      </div>
      <div><br>
        <blockquote type="cite">
          <div>&nbsp;The NETBLT spec found in RFC998 *as is* could not be
            appropriate for current Internet,</div>
        </blockquote>
        <div><br>
        </div>
        It was not meant to. It's for discussion and comment.</div>
    </blockquote>
    And what you cited is a comment.<br>
    <blockquote
      cite="mid:138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu"
      type="cite">
      <div><br>
      </div>
      <div>As I already quoted this in my earlier msg: RFC998 stated
        clearly that&nbsp;</div>
      <div><br>
      </div>
      <div>
        <div>&nbsp;&nbsp; This document is published for discussion and comment,
          and does not</div>
        <div>&nbsp;&nbsp; constitute a standard. &nbsp;The proposal may change and
          certain parts of</div>
        <div>&nbsp;&nbsp; the protocol have not yet been specified; implementation
          of this</div>
        <div>&nbsp;&nbsp; document is therefore not advised.</div>
        <div><br>
        </div>
      </div>
      <div><br>
        <blockquote type="cite">
          <div> so there is a need for another one. &nbsp;In the next 3
            months, I think, we will be a work on it. &nbsp;Moreover, we plan
            to submit it as Independent Submission as Experimental RFC,
            despites it mentions the Standards Track one.<br>
            <br>
            Mykyta<br>
          </div>
        </blockquote>
        <div><br>
        </div>
        I am confused here:</div>
      <div>in your message posted on Jan 7 (2 days ago),&nbsp;</div>
      <div><a moz-do-not-send="true"
          href="http://www.ietf.org/mail-archive/web/ietf/current/msg65041.html">http://www.ietf.org/mail-archive/web/ietf/current/msg65041.html</a></div>
      <div>you said</div>
      <div><br>
      </div>
      <blockquote class="webkit-indent-blockquote" style="margin: 0pt
        0pt 0pt 40px; border: medium none; padding: 0px;">
        <div>As for NETBLT, I am strongly against moving it to Historic,
          rather than specifying by Standards Track&nbsp;Document. There has
          been one attempt to do that by John White in 1995 (see
          draft-white-protocol-stack), but&nbsp;IMO (that likes strange,
          but...) we can align this document with the most current needs
          of Internet and&nbsp;publish.</div>
        <div><br>
        </div>
        <div>Mykyta</div>
      </blockquote>
      <div><br>
      </div>
      <div>but now you changed your mind?</div>
    </blockquote>
    Not, I have not.&nbsp; If that was, I wouldn't publish the
    draft-white-tsvwg-netblt.&nbsp; I desired to move the IRTP to Historic
    only rather that other protocols I mentioned.<br>
    <blockquote
      cite="mid:138221C5-3D47-40E5-8317-F404CAFA86DB@cs.ucla.edu"
      type="cite">
      <div><br>
      </div>
      <div>Lixia</div>
      <div><br>
        <blockquote type="cite">
          <div>
            <blockquote type="cite">Lixia<br>
            </blockquote>
            <blockquote type="cite"><br>
            </blockquote>
            <blockquote type="cite">On Jan 8, 2011, at 3:00 AM, <a
                moz-do-not-send="true"
                href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a>
              wrote:<br>
            </blockquote>
            <blockquote type="cite"><br>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">A New Internet-Draft is available
                from the on-line Internet-Drafts directories.<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span class="Apple-tab-span"
                  style="white-space: pre;"> </span>Title &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:
                Network Block Transfer Protocol (NETBLT)<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span class="Apple-tab-span"
                  style="white-space: pre;"> </span>Author(s) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:
                J. White, M. Yevstifeyev<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span class="Apple-tab-span"
                  style="white-space: pre;"> </span>Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:
                draft-white-tsvwg-netblt-00.txt<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span class="Apple-tab-span"
                  style="white-space: pre;"> </span>Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:
                34<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><span class="Apple-tab-span"
                  style="white-space: pre;"> </span>Date &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;:
                2011-01-08<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">This document is a specification
                of version 5 of Network Block<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">Transfer Protocol (NETBLT). This
                protocol was firstly specified in<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">RFC 969, that has been made
                obsolete by RFC 998. Nevertheless, none<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">of these documents match current
                Internet Standards and are<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">deprecated. This document aligns
                the NETBLT specification with the<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">most current Internet Standards
                and obsoletes RFC 998.<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">A URL for this Internet-Draft is:<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><a moz-do-not-send="true"
href="http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.txt">http://www.ietf.org/internet-drafts/draft-white-tsvwg-netblt-00.txt</a><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">Internet-Drafts are also available
                by anonymous FTP at:<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><a moz-do-not-send="true"
                  href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">Below is the data which will
                enable a MIME compliant mail reader<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">implementation to automatically
                retrieve the ASCII version of the<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">Internet-Draft.<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">&lt;Mail
                Attachment&gt;_______________________________________________<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">I-D-Announce mailing list<br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><a moz-do-not-send="true"
                  href="mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite"><a moz-do-not-send="true"
                  href="https://www.ietf.org/mailman/listinfo/i-d-announce">https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">Internet-Draft directories: <a
                  moz-do-not-send="true"
                  href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">
              <blockquote type="cite">or <a moz-do-not-send="true"
                  href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
              </blockquote>
            </blockquote>
            <blockquote type="cite">_______________________________________________<br>
            </blockquote>
            <blockquote type="cite">Ietf mailing list<br>
            </blockquote>
            <blockquote type="cite"><a moz-do-not-send="true"
                href="mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
            </blockquote>
            <blockquote type="cite"><a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br>
            </blockquote>
            <blockquote type="cite"><br>
            </blockquote>
            <br>
            _______________________________________________<br>
            Ietf mailing list<br>
            <a moz-do-not-send="true" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
            <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a><br>
          </div>
        </blockquote>
      </div>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------080704050101030800080501--

From john-ietf@jck.com  Sat Jan  8 08:55:11 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 843793A679F for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.061
X-Spam-Level: 
X-Spam-Status: No, score=-104.061 tagged_above=-999 required=5 tests=[AWL=0.538, BAYES_00=-2.599, GB_I_INVITATION=-2, 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 BYhwrR5jTe6b for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 08:55:10 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 31F983A635F for <ietf@ietf.org>; Sat,  8 Jan 2011 08:55:07 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pbc6N-000PA4-0G; Sat, 08 Jan 2011 11:57:15 -0500
Date: Sat, 08 Jan 2011 11:57:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: Old transport-layer protocols to Historic?
Message-ID: <5C6FF1BF65F4E4DE2D092AA0@PST.JCK.COM>
In-Reply-To: <4D27F56A.8040605@dcrocker.net>
References: <4D2556C9.9020901@gmail.com> <4D2628AB.3080003@isi.edu> <4D27F56A.8040605@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-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, 08 Jan 2011 16:55:11 -0000

--On Friday, January 07, 2011 21:26 -0800 Dave CROCKER
<dhc2@dcrocker.net> wrote:

> 
> 
> On 1/6/2011 12:40 PM, Bob Braden wrote:
>> Historic might imply that they were once in service, but have
>> later been replaced/deprecated.
> 
> 
> We assign labels to indicate the status of the specification,
> not the status of a service that might use it.
> 
> We say 'experimental' to mean that we thinks it's ok to play
> around with the spec and maybe that we are hoping to get
> further information about it.  But it also means that we very
> much caution about use.  It's our "caveat emptor" label.
> 
> We say 'historic' when we frankly think the spec should now
> not be used, for whatever reason and no matter its prior
> status.
> 
> These both are affirmative labels.  I too do not think we
> should use them for "housekeeping" and the mere fact that a
> specification is not used does not mean that it shouldn't be
> used.

Dave (and Bob),

I'm clearly on record as believing that it is time we do
something about the category labels we have, either to improve
clarity and distinctions or to supplement or replace the
categories with narrative.  I've also got doubts as to whether
this sort of reclassification effort is worth the energy it
takes (an opinion I think I expressed privately to Mykyta very
early in the process).  To some extent, if someone cannot figure
out that they should at least ask a lot of questions about a
protocol that was identified 20+ years ago as Experimental and
that has not been followed up on since, maybe they deserve
whatever happens to them.

But, in a context in which we have stretched "best current
practice" to including both IETF procedures and ideas about how
things should be operated and other statements that have not
been tested in practice a all, we disagree a bit about the
meaning of terms.   I think "experimental" isn't just a warning
label, it is also an implicit invitation to experiment.   Here,
if the experiments were performed (and some were) and the
results written up, recommendations with those results might
well have said "don't use this in this form".  That would have
met most criteria for reclassification to Historic.


It has long been my personal view that, while the automatic
timeout provisions of RFC 2026 have never been successfully
applied to standards-track protocols, a somewhat similar rule
should apply to Experimental work: either some progress --a
report on the experiment, an update to the protocol spec
(possibly including a move to Standards Track but not
necessarily), or something equivalent occurs in some reasonable
period of time, the spec automatically moves to Historic
(because it is the only nearly-appropriate category we have) as
no longer of interest.

Interestingly, NETBLT seems to be a special case of just that
situation: it was implemented, small problems with it were
discovered in a different environment, changes were made, and a
revised spec was published outside the IETF under another name
(there was also an I-D within the IETF pointing to that spec,
but it was allowed to expire without any action).  If Mykyta (or
someone else) is willing to do the work, and an appropriate AD
is willing to sponsor it or assign review to a WG, then I see
considerable advantage in publishing that newer spec or a
pointer to it, preferably with an analysis of limitations, as
either an Informational or Historic record for the community and
using that document to obsolete the original experimental spec.
Documenting ideas that didn't quite work, or that work only in
specialized environments with a good description of those
environments, is the only way we can make progress rather than
repeating ideas that are known to be failures or limited in
scope.

As far as the others are concerned, the procedures don't work
the way I've described above.  While I wouldn't personally want
to invest significant effort in reclassification (and didn't put
significant effort into the successful "de-crufting" effort of
several years ago), I also don't see any harm in it if Mykyta
(or someone else) wants to invest the energy and can find
appropriate AD sponsorship.   I only wish that we had not made
reclassification to Historic, even of experimental specs to
which no one has paid attention for years, into a painful
process that requires nearly as much work as getting a
standards-track specification approved.  There is actually
nothing in RFC 2026 or related documents that requires that much
effort.

    john




From julian.reschke@gmx.de  Sat Jan  8 09:22:34 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 244C53A67B5 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 09:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.433
X-Spam-Level: 
X-Spam-Status: No, score=-104.433 tagged_above=-999 required=5 tests=[AWL=-1.834, 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 SERN+g0grZHD for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 09:22:32 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id F129F3A67AD for <ietf@ietf.org>; Sat,  8 Jan 2011 09:22:31 -0800 (PST)
Received: (qmail invoked by alias); 08 Jan 2011 17:24:38 -0000
Received: from p508FA2EB.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.162.235] by mail.gmx.net (mp013) with SMTP; 08 Jan 2011 18:24:38 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18ijmc+LegiGv5KI+eQCUTEorMi+I3mKW5T9I2Ss6 Nsufxqq4niug4g
Message-ID: <4D289DC9.70208@gmx.de>
Date: Sat, 08 Jan 2011 18:24:25 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: [Ietf-message-headers] Last Call Summary on	draft-yevstifeyev-http-headers-not-recognized
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de> <4D283A42.3080303@gmail.com> <4D2847E1.9090004@gmx.de> <4D288998.9020001@gmail.com>
In-Reply-To: <4D288998.9020001@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: iesg@ietf.org, Alexey Melnikov <alexey.melnikov@isode.com>, ietf-message-headers@ietf.org, IETF Discussion <ietf@ietf.org>, httpbis Group <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: Sat, 08 Jan 2011 17:22:34 -0000

On 08.01.2011 16:58, Mykyta Yevstifeyev wrote:
> ...
> Many LC comments referred to that it would be uninteresting and useless
> to implement this.  Maybe one of them seems the most interesting for me
> - it said about the 'Warning' headers that should be used in this
> occasion.  This, IMO, is one of the most suitable for me and this
> technology.  But if we implement this now using Warning, one problem is
 > ...

I don't see how (a) using HTTP warnings would resolve the problems other 
people see, (b) how the use of warnings makes this proposal any better, 
nor (c) that warnings are actually applicable here (see 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p6-cache-12.html#rfc.section.3.6>).

> absence of IANA registry for Warning codes, such as for Status codes.
> As this message is now sent to httpbis WG mailing list, I ask you if
> there is a sense in creating such registry?

We might create a registry when/if when there are actually requests for 
new Warning values.

> ...

Best regards, Julian

From framefritti@gmail.com  Sat Jan  8 09:39:37 2011
Return-Path: <framefritti@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 A47363A67AD for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 09:39:37 -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 84rtmrE1rHnq for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 09:39: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 51E043A677C for <ietf@ietf.org>; Sat,  8 Jan 2011 09:39:36 -0800 (PST)
Received: by fxm9 with SMTP id 9so18047053fxm.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 09:41:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=1ki0Mn+SUAT0nvZj1JTKeFrBkOUL7lu2JRW4vFcT6+Q=; b=qdXya1Sf3P/QcActvi4K1HJE0HoftEyDfwyV+KX26HHww1/aS6SrEpyZVRbL43oJOW eAi3zU4izXmk1zfPxOOkGuPs/4/T6QA6Fy13kT4DgZoLsnfw2SbdySm/h2zoO32D0Wb9 uIczQCoeG0zovg0ORvRotw17GX8vadJW826+Y=
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 :content-type; b=YThJne9LptdcmrL3g5LL86BKJOIFA4pgGj6ZFVlv+SPUL3PE9LoGEhf8dZOAzsZDsr PCeGIc4kqGDLdAuTVZfCHsxr2qAYM5xhxvneGqttGyJ/I8kyxQ5EmpKMZ5bjINL8w2ck hd1FDJ9pd2b64h950uJ30qBG2e9iaFnOqXGxI=
MIME-Version: 1.0
Received: by 10.223.78.138 with SMTP id l10mr1381335fak.17.1294508502044; Sat, 08 Jan 2011 09:41:42 -0800 (PST)
Received: by 10.223.101.204 with HTTP; Sat, 8 Jan 2011 09:41:41 -0800 (PST)
In-Reply-To: <4D26940F.3020404@gmail.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com>
Date: Sat, 8 Jan 2011 18:41:41 +0100
Message-ID: <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>
Subject: Re: Poster sessions
From: "R. B." <framefritti@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3054a37d6c53a60499593fa4
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, 08 Jan 2011 17:39:37 -0000

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

2011/1/7 Brian E Carpenter <brian.e.carpenter@gmail.com>

> Firstly, I agree: as a general rule, to get official floor space of
> any kind at the IETF venue, you SHOULD have posted a draft. If there
> is no draft, that is exactly when you need a bar BOF. (Complicated joke
> about the height of the bar for a bar BOF, and the drafts to be drunk,
> goes here.)


I'm really in a rush, but I want to send my 0.02 too.  I like the idea of a
poster session, since a single I-D could go unobserved in the churn of other
 I-Ds.  Maybe a poster session with mandatory I-D (to be specified when
requesting the space for the poster) could be a nice solution.


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

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

<br><br><div class=3D"gmail_quote">2011/1/7 Brian E Carpenter <span dir=3D"=
ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@g=
mail.com</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Firstly, I agree: as a general rule, to get official floor space of<br>
any kind at the IETF venue, you SHOULD have posted a draft. If there<br>
is no draft, that is exactly when you need a bar BOF. (Complicated joke<br>
about the height of the bar for a bar BOF, and the drafts to be drunk,<br>
goes here.)</blockquote><div><br></div><div>I&#39;m really in a rush, but I=
 want to send my 0.02 too. =A0I like the idea of a poster session, since a =
single I-D could go unobserved in the churn of other =A0I-Ds. =A0Maybe a po=
ster session with mandatory I-D (to be specified when requesting the space =
for the poster) could be a nice solution.</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div cla=
ss=3D"h5">
_______________________________________________<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>
</div></div></blockquote></div><br>

--20cf3054a37d6c53a60499593fa4--

From bob.hinden@gmail.com  Sat Jan  8 13:42:55 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 E619828C133 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 13:42:55 -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 2gtKHYkAKu1U for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 13:42:55 -0800 (PST)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 4053528C116 for <ietf@ietf.org>; Sat,  8 Jan 2011 13:42:55 -0800 (PST)
Received: by pxi6 with SMTP id 6so4227472pxi.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 13:45:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=Cp5FBGL6QYe3DhPWcAajabYqyp0fKiaLGpWXqiNKcJU=; b=KqipO4+/tE7N2Rp1PvJNAXUjBXjcrcYhRo1P9LgAz0pf+KU0k7YqgCqMPlt691cW0g ztxLyltwp53luTUvYMJgg4h2T+lBXlgpyxjVDvSq7bMeuovOUJq0nitbaWUDsEARPIsC bAZ6VwPw49En6eVN5vwrv95/4ojuChW0i8BqE=
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=REdYDqnKk7SQadEYcXBq560L0ELuzxZDuM5cGkiC2cMOY25C6B1O6aoqSzAgBu+1VB 5G+V6RPpC0MS8Zk3uRiNrccy/oWVG1//agrzwpPLAH3tPFK14NGbO9rLdRXArohoSkDK 64pJnCc8kIoQDpPh6ziuopc8IewnGSrz8M+24=
Received: by 10.142.187.14 with SMTP id k14mr2844035wff.431.1294523104056; Sat, 08 Jan 2011 13:45:04 -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 w42sm4881926wfh.15.2011.01.08.13.45.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 13:45:02 -0800 (PST)
Subject: Re: Old transport-layer protocols to Historic?
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: <4D26AC33.5090207@gmail.com>
Date: Sat, 8 Jan 2011 13:45:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B613C7AC-65A8-40FB-BD38-71810F2D3194@gmail.com>
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <4D26AC33.5090207@gmail.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Braden <braden@isi.edu>, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org, Lixia Zhang <lixia@cs.ucla.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: Sat, 08 Jan 2011 21:42:56 -0000

Hi,

> I think that the author of RFC2026 was wrong while writing the =
definition of Historic status. This document says that Historic should =
be assigned only to that documents that were standards and now are =
obsolete. But why do we need such narrow definition? Non-standards RFCs =
are not made Historic while obsoleting, according to 2026. Moreover, =
such status will just duplicate the obsoleted-by one. When there will be =
the attempt to revise RFC 2026, we should put there that Historic status =
is to be assigned to that documents that are considered to be =
deprecated. I fully share the opinion of Doug here.

If you think RFC20206 is wrong, then propose changes to it and see if =
people agree with the changes.  Until it is changed, IMHO you should not =
propose actions based on what you as an individual think is incorrect.  =
There needs to be a community consensus that RFC2026 is wrong before any =
action should be taken.

Bob




From doug@ewellic.org  Sat Jan  8 18:31:15 2011
Return-Path: <doug@ewellic.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 7005F28C163 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 18:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.554
X-Spam-Level: 
X-Spam-Status: No, score=-0.554 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_05=-1.11, STOX_REPLY_TYPE=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 tPgaGCGj+GsZ for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 18:31:13 -0800 (PST)
Received: from p3plsmtpa01-07.prod.phx3.secureserver.net (p3plsmtpa01-07.prod.phx3.secureserver.net [72.167.82.87]) by core3.amsl.com (Postfix) with SMTP id AA57228C162 for <ietf@ietf.org>; Sat,  8 Jan 2011 18:31:13 -0800 (PST)
Received: (qmail 13239 invoked from network); 9 Jan 2011 02:33:21 -0000
Received: from unknown (24.8.55.39) by p3plsmtpa01-07.prod.phx3.secureserver.net (72.167.82.87) with ESMTP; 09 Jan 2011 02:33:21 -0000
Message-ID: <2358882A1C66475B85B4A8D411AAC3B0@DougEwell>
From: "Doug Ewell" <doug@ewellic.org>
To: <ietf@ietf.org>
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <4D26AC33.5090207@gmail.com> <B613C7AC-65A8-40FB-BD38-71810F2D3194@gmail.com>
In-Reply-To: <B613C7AC-65A8-40FB-BD38-71810F2D3194@gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
Date: Sat, 8 Jan 2011 19:33:51 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
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, 09 Jan 2011 02:31:15 -0000

Bob Hinden replied to Mykyta:

> If you think RFC20206 is wrong, then propose changes to it and see if 
> people agree with the changes.  Until it is changed, IMHO you should 
> not propose actions based on what you as an individual think is 
> incorrect.  There needs to be a community consensus that RFC2026 is 
> wrong before any action should be taken.

RFC 2026 says: "A specification that has been superseded by a more 
recent specification or is for any other reason considered to be 
obsolete is assigned to the 'Historic' level."

My concern (which may not be quite the same as Mykyta's) is how 
aggressive some people might be in declaring a specification like FTP to 
be superseded or obsolete.  "Inappropriate for high-security uses" does 
not by any means imply "inappropriate for all uses."

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­ 


From evnikita2@gmail.com  Sat Jan  8 22:16:39 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 1B97C3A692D for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 22:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.33
X-Spam-Level: 
X-Spam-Status: No, score=-3.33 tagged_above=-999 required=5 tests=[AWL=0.309,  BAYES_00=-2.599, GB_I_INVITATION=-2, 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 P7xRZCkHZX-1 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 22:16:37 -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 9D7663A681E for <ietf@ietf.org>; Sat,  8 Jan 2011 22:16:36 -0800 (PST)
Received: by bwz12 with SMTP id 12so18266773bwz.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 22:18:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=XU55dX6t1MKgye35QPuj5RGF9w0TVkL88nYHHag3Khc=; b=sAx0mY5jZi5nVCaPcTNLDWcAKgAa5PkWYIqgyTb0VHGzBtUDQmc6psFCc3d4I4bvcs c1/w1hGUHOIKCf1YRdDMOOPvaqMm1kMPKqDphXlCSVLlU+DrzjNg5nLj4Y6zZ6GFoih1 u2sQLXS9QJyDLD06Kv0lhPzlEFct0kg9L6OAc=
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=Ekv+NPruwF4EhyGjbJxaIju4SqVmuvYNuZ0qYRYDUZWO3Ng/hdbfBBts/rsARfBSfS 6oUgrDd3SJ5yiMxDVOdNazsGschJ/trak9qNNVicOz75K8h7Q8hy8qaMigLe4sT2g/3c CWMLSjZJJ5nRXOhtaV9/l/GmunKSobsWFCkn4=
Received: by 10.204.138.81 with SMTP id z17mr15557087bkt.162.1294553924312; Sat, 08 Jan 2011 22:18:44 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id p22sm15051359bkp.21.2011.01.08.22.18.42 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 22:18:42 -0800 (PST)
Message-ID: <4D295354.5070805@gmail.com>
Date: Sun, 09 Jan 2011 08:19:00 +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: John C Klensin <john-ietf@jck.com>
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com>	<4D2628AB.3080003@isi.edu> <4D27F56A.8040605@dcrocker.net> <5C6FF1BF65F4E4DE2D092AA0@PST.JCK.COM>
In-Reply-To: <5C6FF1BF65F4E4DE2D092AA0@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dcrocker@bbiw.net, 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, 09 Jan 2011 06:16:39 -0000

08.01.2011 18:57, John C Klensin wrote:
>
> --On Friday, January 07, 2011 21:26 -0800 Dave CROCKER
> <dhc2@dcrocker.net>  wrote:
>
>>
>> On 1/6/2011 12:40 PM, Bob Braden wrote:
>>> Historic might imply that they were once in service, but have
>>> later been replaced/deprecated.
>>
>> We assign labels to indicate the status of the specification,
>> not the status of a service that might use it.
>>
>> We say 'experimental' to mean that we thinks it's ok to play
>> around with the spec and maybe that we are hoping to get
>> further information about it.  But it also means that we very
>> much caution about use.  It's our "caveat emptor" label.
>>
>> We say 'historic' when we frankly think the spec should now
>> not be used, for whatever reason and no matter its prior
>> status.
>>
>> These both are affirmative labels.  I too do not think we
>> should use them for "housekeeping" and the mere fact that a
>> specification is not used does not mean that it shouldn't be
>> used.
> Dave (and Bob),
>
> I'm clearly on record as believing that it is time we do
> something about the category labels we have, either to improve
> clarity and distinctions or to supplement or replace the
> categories with narrative.
Here I agree with you.  At least as for Historic one.
>    I've also got doubts as to whether
> this sort of reclassification effort is worth the energy it
> takes (an opinion I think I expressed privately to Mykyta very
> early in the process).  To some extent, if someone cannot figure
> out that they should at least ask a lot of questions about a
> protocol that was identified 20+ years ago as Experimental and
> that has not been followed up on since, maybe they deserve
> whatever happens to them.
>
> But, in a context in which we have stretched "best current
> practice" to including both IETF procedures and ideas about how
> things should be operated and other statements that have not
> been tested in practice a all, we disagree a bit about the
> meaning of terms.   I think "experimental" isn't just a warning
> label, it is also an implicit invitation to experiment.   Here,
> if the experiments were performed (and some were) and the
> results written up, recommendations with those results might
> well have said "don't use this in this form".  That would have
> met most criteria for reclassification to Historic.
>
> It has long been my personal view that, while the automatic
> timeout provisions of RFC 2026 have never been successfully
> applied to standards-track protocols, a somewhat similar rule
> should apply to Experimental work: either some progress --a
> report on the experiment, an update to the protocol spec
> (possibly including a move to Standards Track but not
> necessarily), or something equivalent occurs in some reasonable
> period of time, the spec automatically moves to Historic
> (because it is the only nearly-appropriate category we have) as
> no longer of interest.
I also agree here.  Experiment has been conducting and some improvements 
should be made or we should claim that during the experiment no one 
found it useful etc
> Interestingly, NETBLT seems to be a special case of just that
> situation: it was implemented, small problems with it were
> discovered in a different environment, changes were made, and a
> revised spec was published outside the IETF under another name
> (there was also an I-D within the IETF pointing to that spec,
> but it was allowed to expire without any action).  If Mykyta (or
> someone else) is willing to do the work, and an appropriate AD
> is willing to sponsor it or assign review to a WG, then I see
> considerable advantage in publishing that newer spec or a
> pointer to it, preferably with an analysis of limitations, as
> either an Informational or Historic record for the community and
> using that document to obsolete the original experimental spec.
> Documenting ideas that didn't quite work, or that work only in
> specialized environments with a good description of those
> environments, is the only way we can make progress rather than
> repeating ideas that are known to be failures or limited in
> scope.
>
> As far as the others are concerned, the procedures don't work
> the way I've described above.  While I wouldn't personally want
> to invest significant effort in reclassification (and didn't put
> significant effort into the successful "de-crufting" effort of
> several years ago), I also don't see any harm in it if Mykyta
> (or someone else) wants to invest the energy and can find
> appropriate AD sponsorship.   I only wish that we had not made
> reclassification to Historic, even of experimental specs to
> which no one has paid attention for years, into a painful
> process that requires nearly as much work as getting a
> standards-track specification approved.  There is actually
> nothing in RFC 2026 or related documents that requires that much
> effort.
IMO old, outdated, out-of-use specification wither they are Standards 
Track or Experimental should be moved to Historic.  It is clearly stated 
in RFC2026 - is considered to be obsolete (i.e. outdated).  I don't find 
anything harmful in identifying, e.g. IRTP as 'Not Recommended For Use' 
via Historic status.

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


From evnikita2@gmail.com  Sat Jan  8 22:20:36 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 E5EA23A6935 for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 22:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level: 
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[AWL=-0.694, 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 rdIWYtXb7fAm for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 22:20: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 F0FA63A6930 for <ietf@ietf.org>; Sat,  8 Jan 2011 22:20:28 -0800 (PST)
Received: by bwz12 with SMTP id 12so18267827bwz.31 for <ietf@ietf.org>; Sat, 08 Jan 2011 22:22:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Drx1E/Wt/qQ0d6aLU/5Qeu/80CuRG0nUP3iTnKv9Ql0=; b=hPhBdMTT1gziA+r0tR1zGmO5fKWAZiu0uBZvL/VDRMmAhtGczD4+ao5sJDpjNYv/C9 aTALLd/8olPrVZm39wKrQcjNvP8luXGZbvAXH4ArgHX6zxsLCk4TXZLGJ8Po1ZYmJE83 8SMIX0TXUJqIw9NAFLt6EBONZg0EvE0rVWQdU=
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=I+UgCwgxrMdAx5Vbe6LP9LJNVddMw1k225bo0N8kpWwB4hU+5FIGhpUyd6ij65W6To +oYYWPDZYJVajYNifrt0V32Dai7qw7r12hfvwA1cWD7dgOuBrq4ITQMcagc5mHFlrT0n PFeoTreOUq0qQRDhaaChkF/KA4XAEOYcOBPko=
Received: by 10.204.64.208 with SMTP id f16mr3918556bki.61.1294554156736; Sat, 08 Jan 2011 22:22:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id a17sm15057447bku.23.2011.01.08.22.22.35 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 22:22:35 -0800 (PST)
Message-ID: <4D29543D.5060503@gmail.com>
Date: Sun, 09 Jan 2011 08:22:53 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [Ietf-message-headers] Last Call Summary on	draft-yevstifeyev-http-headers-not-recognized
References: <4D280272.6090402@gmail.com> <4D28218A.2020406@gmx.de> <4D283A42.3080303@gmail.com> <4D2847E1.9090004@gmx.de> <4D288998.9020001@gmail.com> <4D289DC9.70208@gmx.de>
In-Reply-To: <4D289DC9.70208@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, httpbis Group <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: Sun, 09 Jan 2011 06:20:37 -0000

08.01.2011 19:24, Julian Reschke wrote:
> On 08.01.2011 16:58, Mykyta Yevstifeyev wrote:
>> ...
>> Many LC comments referred to that it would be uninteresting and useless
>> to implement this.  Maybe one of them seems the most interesting for me
>> - it said about the 'Warning' headers that should be used in this
>> occasion.  This, IMO, is one of the most suitable for me and this
>> technology.  But if we implement this now using Warning, one problem is
> > ...
>
> I don't see how (a) using HTTP warnings would resolve the problems 
> other people see, (b) how the use of warnings makes this proposal any 
> better, nor (c) that warnings are actually applicable here (see 
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p6-cache-12.html#rfc.section.3.6>).
At the moment no any, and I want to define a new one.  In spite of this 
there is no any registry (see below).  I ask the WG for opinion on 
should we create it or not?
>
>> absence of IANA registry for Warning codes, such as for Status codes.
>> As this message is now sent to httpbis WG mailing list, I ask you if
>> there is a sense in creating such registry?
>
> We might create a registry when/if when there are actually requests 
> for new Warning values.
However no one can actually do this since there is no such registry.  So 
I think there should be the appropriate registry.  Will the WG agree 
with me?
>
>> ...
>
> Best regards, Julian
>


From evnikita2@gmail.com  Sat Jan  8 22:25: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 04D3D3A6931; Sat,  8 Jan 2011 22:25:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.352
X-Spam-Level: 
X-Spam-Status: No, score=-2.352 tagged_above=-999 required=5 tests=[AWL=-0.714, 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 RbZtrRl7Q4Dk; Sat,  8 Jan 2011 22:25:31 -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 536AD3A6930; Sat,  8 Jan 2011 22:25:30 -0800 (PST)
Received: by bwz12 with SMTP id 12so18269244bwz.31 for <multiple recipients>; Sat, 08 Jan 2011 22:27:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=nPaYKDFudcUAte1fKjw9HUqBtT3+L0gNnd4LmvkEAWQ=; b=vIGV+ygifG67hlg4mXJSeLL5le5IBcYAzhumDjnnYj01OCwbVpWmvgW2skyCK2wOfN uCBuM98G7xhyRBKh4hxZ4EuNbDy93afm4c2vUhcbK2boZt5+AVRz7dGdDrP+tyoArowl Ga/mme0FW2dLzapfDLk1pNofai86qe7QsIpSA=
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=bf+VmxiJVGwObfrv9SZrMnoUy6z5EwBh99lQzRFTL9qTQaxKnbAzpjS2WjvI/TBtwN +u5XJSVBFl/i4Ibls9gbzV9qBGDBBs1LBV1Hzcx86+7LTb+/x35uMDF+gxKgdZuaTKP5 8YgYbwwWARf9mlUCNf2YlBZs/swPQGHq5Lacg=
Received: by 10.204.114.81 with SMTP id d17mr13813030bkq.135.1294554458007; Sat, 08 Jan 2011 22:27:38 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v25sm15051990bkt.18.2011.01.08.22.27.36 (version=SSLv3 cipher=RC4-MD5); Sat, 08 Jan 2011 22:27:37 -0800 (PST)
Message-ID: <4D29556A.6060902@gmail.com>
Date: Sun, 09 Jan 2011 08:27:54 +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: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com> <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com> <4D2842B8.7090100@gmail.com>
In-Reply-To: <4D2842B8.7090100@gmail.com>
Content-Type: multipart/alternative; boundary="------------080703050203060404030302"
Cc: tsvwg@ietf.org, IETF Discussion <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, 09 Jan 2011 06:25:37 -0000

This is a multi-part message in MIME format.
--------------080703050203060404030302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

08.01.2011 12:55, Mykyta Yevstifeyev ?????:
> 07.01.2011 21:53, Bob Hinden wrote:
>> Mykyta,
>>
>>
>> On Jan 5, 2011, at 9:44 PM, Mykyta Yevstifeyev wrote:
>>
>>> Hello all,
>>>
>>> There have been a discussion on tsvwg mailing list about old transport layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT (RFC998). Initially there have been proposed to define IANA considerations for them. But after a discussion it was found out that it would be better to move them to Historic. I am writing to request more wider discussion on this topic.
>> I see little value even thinking about this.  It's looks like a "make work" project to me.  Just because something is "old", doesn't mean it is "historic" in the sense the label is used in the IETF.
>>
>> Regarding RDP (RFC908, RFC1151), of which I am one of the authors, both are currently labeled as Experimental.  I do not see any reason to change that.
>
Bob, all,

Personally I don't support the idea to move the RDP to Historic. The 
initial idea was to defined IANA procedures for assignment RDP ports, 
that remains undefined. But when I presented the corresponding draft to 
tsvwg, many claimed that it would be better to move it ti Historic 
rather than specify IANA procedures for it. Currently, there is a draft 
on this topic:

http://tools.ietf.org/html/draft-yevstifeyev-rdp-ports-registry-02

My initial idea was just that.  And you, Bob, do you find this topic 
interesting (RDP ports assignment) as the developer of RDP?

Mykyta Yevstifeyev


>> Bob
>>
>>
>>> There is quite strong consensus that IRTP should be Historic. There is a registered draft on this topic:
>>>
>>> https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/
>>>
>>> But as for others it should be discussed. Moreover, maybe anyone knows some other old transport-layer protocols that are no longer in use?
>>>
>>> Please copy tour answer totsvwg@ietf.org
>>>
>>> All the best,
>>> Mykyta Yevstifeyev
>>> _______________________________________________
>>> 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
>>
>


--------------080703050203060404030302
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">
    08.01.2011 12:55, Mykyta Yevstifeyev &#1087;&#1080;&#1096;&#1077;&#1090;:
    <blockquote cite="mid:4D2842B8.7090100@gmail.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      07.01.2011 21:53, Bob Hinden wrote:
      <blockquote
        cite="mid:AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com"
        type="cite">
        <pre wrap="">Mykyta,


On Jan 5, 2011, at 9:44 PM, Mykyta Yevstifeyev wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">Hello all,

There have been a discussion on tsvwg mailing list about old transport layer protocols - exactly IRTP (RFC938), RDP (RFC908,1151) and NETBLT (RFC998). Initially there have been proposed to define IANA considerations for them. But after a discussion it was found out that it would be better to move them to Historic. I am writing to request more wider discussion on this topic. 
</pre>
        </blockquote>
        <pre wrap="">I see little value even thinking about this.  It's looks like a "make work" project to me.  Just because something is "old", doesn't mean it is "historic" in the sense the label is used in the IETF.

Regarding RDP (RFC908, RFC1151), of which I am one of the authors, both are currently labeled as Experimental.  I do not see any reason to change that. 
</pre>
      </blockquote>
      <br>
    </blockquote>
    Bob, all,<br>
    <br>
    Personally I don't support the idea to move the RDP to Historic. The
    initial idea was to defined IANA procedures for assignment RDP
    ports, that remains undefined. But when I presented the
    corresponding draft to tsvwg, many claimed that it would be better
    to move it ti Historic rather than specify IANA procedures for it.
    Currently, there is a draft on this topic:<br>
    <br>
    <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-yevstifeyev-rdp-ports-registry-02">http://tools.ietf.org/html/draft-yevstifeyev-rdp-ports-registry-02</a><br>
    <br>
    My initial idea was just that.&nbsp; And you, Bob, do you find this topic
    interesting (RDP ports assignment) as the developer of RDP?<br>
    <br>
    Mykyta Yevstifeyev<br>
    <br>
    <br>
    <blockquote cite="mid:4D2842B8.7090100@gmail.com" type="cite">
      <blockquote
        cite="mid:AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com"
        type="cite">
        <pre wrap="">Bob


</pre>
        <blockquote type="cite">
          <pre wrap="">There is quite strong consensus that IRTP should be Historic. There is a registered draft on this topic:

<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/">https://datatracker.ietf.org/doc/draft-yevstifeyev-tsvwg-irtp-to-historic/</a>

But as for others it should be discussed. Moreover, maybe anyone knows some other old transport-layer protocols that are no longer in use?

Please copy tour answer to <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:tsvwg@ietf.org">tsvwg@ietf.org</a> 

All the best,
Mykyta Yevstifeyev
_______________________________________________
Ietf mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
        </blockquote>
        <pre wrap="">_______________________________________________
Ietf mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>

</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------080703050203060404030302--

From joelja@bogus.com  Sun Jan  9 08:42:29 2011
Return-Path: <joelja@bogus.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 7E9893A681E for <ietf@core3.amsl.com>; Sun,  9 Jan 2011 08:42:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.103
X-Spam-Level: 
X-Spam-Status: No, score=-102.103 tagged_above=-999 required=5 tests=[AWL=0.496, 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 Nb7z7meJWpBl for <ietf@core3.amsl.com>; Sun,  9 Jan 2011 08:42:28 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 329243A681B for <ietf@ietf.org>; Sun,  9 Jan 2011 08:42:28 -0800 (PST)
Received: from 58b035843c84.netpoint.com ([213.221.117.228]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p09GiSsM057681 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 9 Jan 2011 16:44:30 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D29D6BE.6030407@bogus.com>
Date: Sun, 09 Jan 2011 07:39:42 -0800
From: Joel Jaeggli <joelja@bogus.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: Yoav Nir <ynir@checkpoint.com>
Subject: Re: BCP request: WiFi at High-Tech Meetings
References: <4D1B5053.6000005@dcrocker.net>	<Pine.GSO.4.63.1012290751380.5366@pita.cisco.com>	<72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu>	<4D1B6415.4040502@bogus.com>	<1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com>	<CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com>	<AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com> <84AFE0E6-D1E7-4606-A620-341457E1B1E5@checkpoint.com>
In-Reply-To: <84AFE0E6-D1E7-4606-A620-341457E1B1E5@checkpoint.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Phillip Hallam-Baker <hallam@gmail.com>, 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: Sun, 09 Jan 2011 16:42:29 -0000

On 1/4/11 8:07 AM, Yoav Nir wrote:
> 
> On Jan 4, 2011, at 5:55 PM, Phillip Hallam-Baker wrote:
> 
>> It could be the 11a support.
>> 
>> Or it might well be the vendor that supplies the 11a equipment.
>> 
>> At home I have a box with 7 defunct WiFi routers that I discarded
>> after they started to fail. Specifically the wireless side of the
>> router would stop functioning or require rebooting every 24 hours
>> or so to keep functioning.
>> 
>> Then three years ago I mentioned the problem on this list and
>> bought an AirPort Extreme on the advice of several people.
>> 
>> It has now been running for three years without issue.
>> 
>> 
>> I do notice that a significant proportion of laptops used at IETFs
>> are produced by one specific vendor. And lets face it, we are the
>> type of audience that is quite willing to pay two to three times
>> the minimum for a laptop.

There's also sorts of interesting ways to calculate net-present value,
of a given business tool. Someone who uses a given computer 16 hours a
day may have slightly different priorities than someone who uses it for
2 or 4.

in the specific case of wireless 802.11a just isn't very common in $300
laptops and netbooks, yet it's invaluable in an environment that we're
in at least three times a year so it's trivial to justify the $20-50
retail hit associated with a high-end wireless chipset.

> Wouldn't the same be true for media events staged by that same
> specific vendor?  That was the event the NYT article described. 
> _______________________________________________ Ietf mailing list 
> Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
> 


From joelja@bogus.com  Sun Jan  9 08:42:42 2011
Return-Path: <joelja@bogus.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 8373B3A6828 for <ietf@core3.amsl.com>; Sun,  9 Jan 2011 08:42:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.268
X-Spam-Level: 
X-Spam-Status: No, score=-102.268 tagged_above=-999 required=5 tests=[AWL=0.331, 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 lS18vZ1C9qSp for <ietf@core3.amsl.com>; Sun,  9 Jan 2011 08:42:41 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 2CA993A6823 for <ietf@ietf.org>; Sun,  9 Jan 2011 08:42:37 -0800 (PST)
Received: from 58b035843c84.netpoint.com ([213.221.117.228]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p09GifpY057691 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 9 Jan 2011 16:44:43 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D29D836.1060508@bogus.com>
Date: Sun, 09 Jan 2011 07:45:58 -0800
From: Joel Jaeggli <joelja@bogus.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: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: BCP request: WiFi at High-Tech Meetings
References: <4D1B5053.6000005@dcrocker.net>	<Pine.GSO.4.63.1012290751380.5366@pita.cisco.com>	<72511209-CA49-438F-B415-48CD77D7F572@cs.columbia.edu>	<4D1B6415.4040502@bogus.com>	<1126A907-D244-4C0C-B640-B356A1D1A48C@pobox.com>	<CD5674C3CD99574EBA7432465FC13C1B2202288B2B@DC-US1MBEX4.global.avaya.com>	<AANLkTi=LaEnEV55YeLmx+YokZfD6p-wLuhmUrTx5=4Xd@mail.gmail.com>	<84AFE0E6-D1E7-4606-A620-341457E1B1E5@checkpoint.com> <AANLkTinbn0pjixGakae+7uwOyX6KjDsRj_gE5rvtENMZ@mail.gmail.com>
In-Reply-To: <AANLkTinbn0pjixGakae+7uwOyX6KjDsRj_gE5rvtENMZ@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Sun, 09 Jan 2011 16:42:42 -0000

On 1/4/11 10:12 AM, Phillip Hallam-Baker wrote:
> The problem there appears to have been the density of MiFi boxes all
> offering access and a WiFi stack that crashed in the presence of 500+
> access points. 
> 
> I am not sure that we have experience operating in that zone either. 
> 
> Of course, had said vendor been more willing to allow tethering on their
> phone the MiFi boxes might not have become so popular/necessary.

wifi tethering from a non-dedicated device such a phone has about the
same implications...

being willing to burn more power and do 802.11a would substantially
reduce contention...

The number of cellpohones support 802.11a is quit small, thought with
the ipad doing it probably a number of other vendors with take the hint
on larger devices.

> 
> On Tue, Jan 4, 2011 at 4:07 PM, Yoav Nir <ynir@checkpoint.com
> <mailto:ynir@checkpoint.com>> wrote:
> 
> 
>     On Jan 4, 2011, at 5:55 PM, Phillip Hallam-Baker wrote:
> 
>     > It could be the 11a support.
>     >
>     > Or it might well be the vendor that supplies the 11a equipment.
>     >
>     > At home I have a box with 7 defunct WiFi routers that I discarded
>     after they started to fail. Specifically the wireless side of the
>     router would stop functioning or require rebooting every 24 hours or
>     so to keep functioning.
>     >
>     > Then three years ago I mentioned the problem on this list and
>     bought an AirPort Extreme on the advice of several people.
>     >
>     > It has now been running for three years without issue.
>     >
>     >
>     > I do notice that a significant proportion of laptops used at IETFs
>     are produced by one specific vendor. And lets face it, we are the
>     type of audience that is quite willing to pay two to three times the
>     minimum for a laptop.
> 
>     Wouldn't the same be true for media events staged by that same
>     specific vendor?  That was the event the NYT article described.
> 
> 
> 
> 
> -- 
> Website: http://hallambaker.com/
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From msrajesha@gmail.com  Sun Jan  9 23:43:41 2011
Return-Path: <msrajesha@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 98CB23A6A64 for <ietf@core3.amsl.com>; Sun,  9 Jan 2011 23:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stFFAXH7GFgc for <ietf@core3.amsl.com>; Sun,  9 Jan 2011 23:43:40 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 484D428C0CF for <ietf@ietf.org>; Sun,  9 Jan 2011 23:43:40 -0800 (PST)
Received: by qyk34 with SMTP id 34so1197855qyk.10 for <ietf@ietf.org>; Sun, 09 Jan 2011 23:45:53 -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:content-type; bh=AJZDuJV7Eirh6TPh9VraOXDWBynNR/uEyBYH0LcYlI4=; b=m9bSXVgvsc667c92wYPhlkfdVLqOBE20uA+6eUsuctG9w+Yy3N04L4q0iE+iRxhd81 V2sEwRJR+uG5PGfytAo4rdv8DectlaUsxM4UZ8E+zuOWd3CoR9Cp1zxn0ExqWhhZRqBB pk1cDDbzXum/vyX6m2A7OtXNVRlpQEoh+Dzfo=
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 :content-type; b=WuBfckeLkQrPPgm1qn4LoL5kLJ4i/0NZtAXQgPJXd3ICFbXXjtEDlT30XQv7HDJibT Rle2VWrsTlJaIzNJF8Fwme6y4WvqZsRW6hQLcrIPK+r+T5Ko5Kimh4gtoioKq3MdlNPg hGk5lwTyU++3d2cujxn5S3+/sxVBiu8cnUfPM=
MIME-Version: 1.0
Received: by 10.229.84.137 with SMTP id j9mr24864697qcl.214.1294645553076; Sun, 09 Jan 2011 23:45:53 -0800 (PST)
Received: by 10.229.34.17 with HTTP; Sun, 9 Jan 2011 23:45:52 -0800 (PST)
In-Reply-To: <4D286E51.5060004@tana.it>
References: <4D258AB3.9010903@tana.it> <AANLkTikw3KMsKq5epkEDGtzb_mMMMOqs7PvidvyksVNj@mail.gmail.com> <4D286E51.5060004@tana.it>
Date: Mon, 10 Jan 2011 13:15:52 +0530
Message-ID: <AANLkTimto68ckSqvJGhmmQbUXutWthOoQZUQJUYBQCEP@mail.gmail.com>
Subject: Fwd: Poster sessions
From: rajesh rajesh <msrajesha@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=0016364ee2f44d1c3d049979287b
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, 10 Jan 2011 07:43:41 -0000

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

On 07/Jan/11 05:26, rajesh rajesh wrote:
> Poster sessions at IETF meeting sounds quite meaningful considering
> fact that thoughts are written and author available for discussion and
> will give way for fresh subject.
>
> Rajesh
>
> On Thu, Jan 6, 2011 at 2:56 PM, Alessandro Vesely <vesely@tana.it
> <mailto:vesely@tana.it>> wrote:
>
>     I've never attended an IETF meeting.  Why?  Because it seems to me
>     quite
>     unlikely to have a chance to say something useful by going there.
>      I mean
>     useful with respect to a problem that I consider important.  That
>     is, not
>     just a minimal contribution to an already scheduled session that I
>     may happen
>     to attend.  Perhaps, I should request a session...
>
>     Problems are often expressed in the form of tentative solutions.  Such
>     solutions may occasionally happen to be discussed, refined, and
>     agreed upon
>     by a group of individuals.  Implementation, standardization, and
>     adoption may
>     eventually follow  --not necessarily in this order.  Isn't this
>     how the IRTF
>     and the IETF should work?
>
>     A poster session would be a sort of plenary, lasting a couple of
>     hours or so,
>     with posters hanged on numbered hardboard panels arranged along a
>     walkway.  A
>     poster may be sized A0, or ~50 in, or consist of an equivalent
>     number of
>     smaller sheets.  Posters may stay exposed for a few hours
>     before/after the
>     scheduled time period.  During the session time, however, authors
>     should
>     stand beside their posters and thus have their chance to talk to any
>     interested ietfers, one by one or in small knots, informally.  A
>     few dozens
>     of posters per session may provide for adequate gathering.
>
>     IME, this way of participating is easier and less binding for both
>     authors
>     and attendees.  A poster would suit subjects for which it's
>     difficult to
>     carve a niche within a hosting WG's session, but it may also work
>     as a means
>     to achieve consensus on a given topic before raising it in a more
>     official
>     discussion.
>
>     Opinions/suggestions?
>     _______________________________________________
>     Ietf mailing list
>     Ietf@ietf.org <mailto:Ietf@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ietf
>
>

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

<br><br><div class=3D"gmail_quote"><br>
<div class=3D"im"><br>
On 07/Jan/11 05:26, rajesh rajesh wrote:<br>
&gt; Poster sessions at IETF meeting sounds quite meaningful considering<br=
>
&gt; fact that thoughts are written and author available for discussion and=
<br>
&gt; will give way for fresh subject.<br>
&gt;<br>
&gt; Rajesh<br>
&gt;<br>
&gt; On Thu, Jan 6, 2011 at 2:56 PM, Alessandro Vesely &lt;<a href=3D"mailt=
o:vesely@tana.it">vesely@tana.it</a><br>
</div><div><div></div><div class=3D"h5">&gt; &lt;mailto:<a href=3D"mailto:v=
esely@tana.it">vesely@tana.it</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 I&#39;ve never attended an IETF meeting. =A0Why? =A0Because it=
 seems to me<br>
&gt; =A0 =A0 quite<br>
&gt; =A0 =A0 unlikely to have a chance to say something useful by going the=
re.<br>
&gt; =A0 =A0 =A0I mean<br>
&gt; =A0 =A0 useful with respect to a problem that I consider important. =
=A0That<br>
&gt; =A0 =A0 is, not<br>
&gt; =A0 =A0 just a minimal contribution to an already scheduled session th=
at I<br>
&gt; =A0 =A0 may happen<br>
&gt; =A0 =A0 to attend. =A0Perhaps, I should request a session...<br>
&gt;<br>
&gt; =A0 =A0 Problems are often expressed in the form of tentative solution=
s. =A0Such<br>
&gt; =A0 =A0 solutions may occasionally happen to be discussed, refined, an=
d<br>
&gt; =A0 =A0 agreed upon<br>
&gt; =A0 =A0 by a group of individuals. =A0Implementation, standardization,=
 and<br>
&gt; =A0 =A0 adoption may<br>
&gt; =A0 =A0 eventually follow =A0--not necessarily in this order. =A0Isn&#=
39;t this<br>
&gt; =A0 =A0 how the IRTF<br>
&gt; =A0 =A0 and the IETF should work?<br>
&gt;<br>
&gt; =A0 =A0 A poster session would be a sort of plenary, lasting a couple =
of<br>
&gt; =A0 =A0 hours or so,<br>
&gt; =A0 =A0 with posters hanged on numbered hardboard panels arranged alon=
g a<br>
&gt; =A0 =A0 walkway. =A0A<br>
&gt; =A0 =A0 poster may be sized A0, or ~50 in, or consist of an equivalent=
<br>
&gt; =A0 =A0 number of<br>
&gt; =A0 =A0 smaller sheets. =A0Posters may stay exposed for a few hours<br=
>
&gt; =A0 =A0 before/after the<br>
&gt; =A0 =A0 scheduled time period. =A0During the session time, however, au=
thors<br>
&gt; =A0 =A0 should<br>
&gt; =A0 =A0 stand beside their posters and thus have their chance to talk =
to any<br>
&gt; =A0 =A0 interested ietfers, one by one or in small knots, informally. =
=A0A<br>
&gt; =A0 =A0 few dozens<br>
&gt; =A0 =A0 of posters per session may provide for adequate gathering.<br>
&gt;<br>
&gt; =A0 =A0 IME, this way of participating is easier and less binding for =
both<br>
&gt; =A0 =A0 authors<br>
&gt; =A0 =A0 and attendees. =A0A poster would suit subjects for which it&#3=
9;s<br>
&gt; =A0 =A0 difficult to<br>
&gt; =A0 =A0 carve a niche within a hosting WG&#39;s session, but it may al=
so work<br>
&gt; =A0 =A0 as a means<br>
&gt; =A0 =A0 to achieve consensus on a given topic before raising it in a m=
ore<br>
&gt; =A0 =A0 official<br>
&gt; =A0 =A0 discussion.<br>
&gt;<br>
&gt; =A0 =A0 Opinions/suggestions?<br>
&gt; =A0 =A0 _______________________________________________<br>
&gt; =A0 =A0 Ietf mailing list<br>
</div></div>&gt; =A0 =A0 <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a>=
 &lt;mailto:<a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a>&gt;<br>
<div><div></div><div class=3D"h5">&gt; =A0 =A0 <a href=3D"https://www.ietf.=
org/mailman/listinfo/ietf" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/ietf</a><br>
&gt;<br>
&gt;<br>
<br>
</div></div></div><br>

--0016364ee2f44d1c3d049979287b--

From hannes.tschofenig@gmx.net  Mon Jan 10 00:37:32 2011
Return-Path: <hannes.tschofenig@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 3896028C106 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 00:37:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.429
X-Spam-Level: 
X-Spam-Status: No, score=-102.429 tagged_above=-999 required=5 tests=[AWL=0.170, 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 b163J0uqnSkX for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 00:37:31 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 048F228C0DF for <ietf@ietf.org>; Mon, 10 Jan 2011 00:37:30 -0800 (PST)
Received: (qmail invoked by alias); 10 Jan 2011 08:39:43 -0000
Received: from unknown (EHLO [10.255.131.194]) [192.100.123.77] by mail.gmx.net (mp007) with SMTP; 10 Jan 2011 09:39:43 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+ZjVEJOgeZtRtBnp0gsBnobbc3eIRGTPTkoBWn4l lN4mXCG77UW81t
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Contacts to Czech Technical University in Prague?
Date: Mon, 10 Jan 2011 10:39:39 +0200
Message-Id: <DB1268BC-E64F-46CE-B60A-2893672798F0@gmx.net>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 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, 10 Jan 2011 08:37:32 -0000

Hi all,=20

this is a rather unusual request but maybe someone on the IETF list can =
help me (us).=20

A punch of us from the IAB and the IESG are trying to put a workshop on =
"Interconnecting Smart Objects with the Internet" together. The workshop =
days are March 25th/26th, i.e. Friday/Saturday before the start of the =
IETF meeting in Prague.=20

We would need a meeting room for these two days and were hoping that we =
could get some help from the folks at the university.=20

Unfortunately, nobody of us has contacts to the technical university in =
Prague. But maybe someone of you has these contacts.=20

Your help is appreciated.=20

Ciao
Hannes
(on behalf of the other workshop organizers)=

From lars.eggert@nokia.com  Mon Jan 10 01:29:10 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 AF3EA3A6AE8 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 01:29:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.691
X-Spam-Level: 
X-Spam-Status: No, score=-104.691 tagged_above=-999 required=5 tests=[AWL=-2.092, 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 EjTr6+XHCJ4A for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 01:29:08 -0800 (PST)
Received: from mgw-da02.nokia.com (mgw-da02.ext.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id E8A4D3A6AE5 for <ietf@ietf.org>; Mon, 10 Jan 2011 01:29:07 -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 p0A9VHiF032112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2011 11:31:18 +0200
Subject: Re: Poster sessions
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-3-664572836; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>
Date: Mon, 10 Jan 2011 11:31:08 +0200
Message-Id: <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>
To: "R. B." <framefritti@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); Mon, 10 Jan 2011 11:31:15 +0200 (EET)
X-Nokia-AV: Clean
Cc: IETF Discussion <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, 10 Jan 2011 09:29:10 -0000

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

Hi,

On 2011-1-8, at 19:41, R. B. wrote:
> I'm really in a rush, but I want to send my 0.02 too.  I like the idea =
of a
> poster session, since a single I-D could go unobserved in the churn of =
other
> I-Ds.

many areas have open meetings where folks already can present such =
ideas.

It's up to the ADs or chairs of such meetings to decide if presentation =
time is warranted, with or without an accompanying ID.

Lars=

--Apple-Mail-3-664572836
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExMDA5MzEwOVowIwYJKoZIhvcNAQkE
MRYEFLR1Uwy6Je6UiEOs8UgFYO1eDVeQMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AH9I8qpTNbeECBpkmuDcGa0iLPRbHiUTzsbv/fNWFIO4yC+ss7mAUIHZIwFXrj1m74GT0VJEygXD
syQ1Plrw67CZyxBpglhhnkGWbQx0jkyDuPB6tm9rhzfEf1ijMDYLEJ/dTS+EWAa19PmHg0cIJS3W
PGu4yqpL6XdBrnfdCw8+0v9AcxxA6fzwfpakCVLv3H7mdkj+yAZOWPfAfPDNHmeOyqZNpC5D/lR2
hPJjdaB0a5+Sz3cOeDDfiu7uwdUEMGNOEJgfnxFsefrlduOx90VyLT75zEZS5c7g/6t8WvsY9kTu
zffRzxyo3q3DtKgjZwtb0/KzokOjc/+ULSUAO4IAAAAAAAA=

--Apple-Mail-3-664572836--

From ynir@checkpoint.com  Mon Jan 10 02:12: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 428F928C0F2 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 02:12:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.931
X-Spam-Level: 
X-Spam-Status: No, score=-9.931 tagged_above=-999 required=5 tests=[AWL=0.668,  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 3pIMODqa8e6l for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 02:12:06 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 0FE1028C0ED for <ietf@ietf.org>; Mon, 10 Jan 2011 02:12:05 -0800 (PST)
X-CheckPoint: {4D2ADBFA-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p0AAEG5k013729;  Mon, 10 Jan 2011 12:14:16 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 10 Jan 2011 12:14:16 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Lars Eggert <lars.eggert@nokia.com>
Date: Mon, 10 Jan 2011 12:14:18 +0200
Subject: Re: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: AcuwryLgYqaKhNhjTTOtCxIMppMkJw==
Message-ID: <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>
In-Reply-To: <ED6A886C-2FBC-4312-9066-18108363249C@nokia.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 Discussion <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, 10 Jan 2011 10:12:07 -0000

On Jan 10, 2011, at 11:31 AM, Lars Eggert wrote:

> Hi,
>=20
> On 2011-1-8, at 19:41, R. B. wrote:
>> I'm really in a rush, but I want to send my 0.02 too.  I like the idea o=
f a
>> poster session, since a single I-D could go unobserved in the churn of o=
ther
>> I-Ds.
>=20
> many areas have open meetings where folks already can present such ideas.
>=20
> It's up to the ADs or chairs of such meetings to decide if presentation t=
ime is warranted, with or without an accompanying ID.

True, but in those meetings you usually get about 5 minutes to present (whi=
ch is good), but then some other people present other things. Following tha=
t, those people in the audience who are interested will have to seek you ou=
t among the 1200 participants, or go to a mailing list just to ask question=
s.

A poster session would allow for more interaction.

Yoav=

From henk@ripe.net  Mon Jan 10 03:07:25 2011
Return-Path: <henk@ripe.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 2FCEE28C137 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 03:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.627
X-Spam-Level: 
X-Spam-Status: No, score=-102.627 tagged_above=-999 required=5 tests=[AWL=-0.028, 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 vVkF9Zte+Z1Q for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 03:07:24 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id A2D7F28C132 for <ietf@ietf.org>; Mon, 10 Jan 2011 03:07:23 -0800 (PST)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <henk@ripe.net>) id 1PcFcy-0007ll-QN for ietf@ietf.org; Mon, 10 Jan 2011 12:09:33 +0100
Received: from [193.0.21.124] (helo=guest133.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <henk@ripe.net>) id 1PcFcy-0003y8-MW for ietf@ietf.org; Mon, 10 Jan 2011 12:09:32 +0100
Message-ID: <4D2AE8EC.2060202@ripe.net>
Date: Mon, 10 Jan 2011 12:09:32 +0100
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>
In-Reply-To: <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
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 -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5c08f28c454a28c619671d4ed4d399a58
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, 10 Jan 2011 11:07:25 -0000

On 10/01/2011 11:14, Yoav Nir wrote:
> 
> On Jan 10, 2011, at 11:31 AM, Lars Eggert wrote:
> 
>> Hi,
>> 
>> On 2011-1-8, at 19:41, R. B. wrote:
>>> I'm really in a rush, but I want to send my 0.02 too.  I like the idea of
>>> a poster session, since a single I-D could go unobserved in the churn of
>>> other I-Ds.
>> 
>> many areas have open meetings where folks already can present such ideas.
>> 
>> It's up to the ADs or chairs of such meetings to decide if presentation
>> time is warranted, with or without an accompanying ID.
> 
> True, but in those meetings you usually get about 5 minutes to present (which
> is good), but then some other people present other things. Following that,
> those people in the audience who are interested will have to seek you out
> among the 1200 participants, or go to a mailing list just to ask questions.
> 
> A poster session would allow for more interaction.

I think that there is another issue.  Some people are good at doing 5
minute pitches of an idea, others aren't.  In case one is not, then I
think a poster session might be a good alternative.

The costs for a poster session are almost 0.  Isn't this something we
can just try?

Henk



-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.

From loa@pi.nu  Mon Jan 10 03:20:27 2011
Return-Path: <loa@pi.nu>
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 BFA1A28C146 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 03:20:27 -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 AQ1jxaAUj8AD for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 03:20:26 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by core3.amsl.com (Postfix) with ESMTP id C096328C138 for <ietf@ietf.org>; Mon, 10 Jan 2011 03:20:26 -0800 (PST)
Received: from [192.168.1.7] (unknown [182.53.167.243]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id AC38351407F for <ietf@ietf.org>; Mon, 10 Jan 2011 12:22:37 +0100 (CET)
Message-ID: <4D2AEC03.8040205@pi.nu>
Date: Mon, 10 Jan 2011 12:22:43 +0100
From: Loa Andersson <loa@pi.nu>
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: ietf@ietf.org
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net>
In-Reply-To: <4D2AE8EC.2060202@ripe.net>
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: Mon, 10 Jan 2011 11:20:27 -0000

ALl,

what is here called "poster session" reminds me a awful lot of the
bar bof's we been running for a long time.

Anyone care to draw the line between the two and try to motivate why
we need boths. As I see nothing stops from bringing a poster to a bar
bof, or a white board for taht matter.

/Loa

On 2011-01-10 12:09, Henk Uijterwaal wrote:
> On 10/01/2011 11:14, Yoav Nir wrote:
>>
>> On Jan 10, 2011, at 11:31 AM, Lars Eggert wrote:
>>
>>> Hi,
>>>
>>> On 2011-1-8, at 19:41, R. B. wrote:
>>>> I'm really in a rush, but I want to send my 0.02 too.  I like the idea of
>>>> a poster session, since a single I-D could go unobserved in the churn of
>>>> other I-Ds.
>>>
>>> many areas have open meetings where folks already can present such ideas.
>>>
>>> It's up to the ADs or chairs of such meetings to decide if presentation
>>> time is warranted, with or without an accompanying ID.
>>
>> True, but in those meetings you usually get about 5 minutes to present (which
>> is good), but then some other people present other things. Following that,
>> those people in the audience who are interested will have to seek you out
>> among the 1200 participants, or go to a mailing list just to ask questions.
>>
>> A poster session would allow for more interaction.
>
> I think that there is another issue.  Some people are good at doing 5
> minute pitches of an idea, others aren't.  In case one is not, then I
> think a poster session might be a good alternative.
>
> The costs for a poster session are almost 0.  Isn't this something we
> can just try?
>
> Henk
>
>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From ynir@checkpoint.com  Mon Jan 10 05:45:31 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 4D87728C163 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.946
X-Spam-Level: 
X-Spam-Status: No, score=-9.946 tagged_above=-999 required=5 tests=[AWL=0.653,  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 gIrMbsfYlz+X for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:45:30 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 15B3E28C161 for <ietf@ietf.org>; Mon, 10 Jan 2011 05:45:29 -0800 (PST)
X-CheckPoint: {4D2B0DFE-2-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p0ADlgsI018239;  Mon, 10 Jan 2011 15:47:42 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 10 Jan 2011 15:47:42 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Loa Andersson <loa@pi.nu>
Date: Mon, 10 Jan 2011 15:47:44 +0200
Subject: Re: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: AcuwzPN9yY0w7ZgZQPaPkcQi5nBLmA==
Message-ID: <521AF45A-BB95-4D1E-B35A-8B84A259DE49@checkpoint.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu>
In-Reply-To: <4D2AEC03.8040205@pi.nu>
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: Mon, 10 Jan 2011 13:45:31 -0000

On Jan 10, 2011, at 1:22 PM, Loa Andersson wrote:

> ALl,
>=20
> what is here called "poster session" reminds me a awful lot of the
> bar bof's we been running for a long time.

No coincidence. There's been a lot of criticism of these bar BoFs, and we k=
eep looking for better ways to present new ideas.

> Anyone care to draw the line between the two and try to motivate why
> we need boths. As I see nothing stops from bringing a poster to a bar
> bof, or a white board for taht matter.

Despite the name, a bar BoF today is very much lecture-style. You have a pr=
esentation and a time for questions. There's really very little room for ac=
tual discussion (which supposedly happens later in some mailling list). A p=
oster session allows for conversation with the I-D author, which may or may=
 not lead to better results.

>=20
> /Loa
>=20


From tme@americafree.tv  Mon Jan 10 05:54:48 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 3C5CA28C170 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.222
X-Spam-Level: 
X-Spam-Status: No, score=-102.222 tagged_above=-999 required=5 tests=[AWL=0.377, 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-VrrZxC8FEp for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:54:46 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id DDC1D3A69A4 for <ietf@ietf.org>; Mon, 10 Jan 2011 05:54:45 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 8DE8499EB986; Mon, 10 Jan 2011 08:56:59 -0500 (EST)
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <4D2AEC03.8040205@pi.nu>
Date: Mon, 10 Jan 2011 08:56:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1081)
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, 10 Jan 2011 13:54:48 -0000

On Jan 10, 2011, at 6:22 AM, Loa Andersson wrote:

> ALl,
>=20
> what is here called "poster session" reminds me a awful lot of the
> bar bof's we been running for a long time.
>=20
> Anyone care to draw the line between the two and try to motivate why
> we need boths. As I see nothing stops from bringing a poster to a bar
> bof, or a white board for taht matter.

Well, the bar bofs I have attended (and even organized) in actual bars =
wouldn't lend themselves to bringing white boards...

However, the real answer is that a bar bof is synchronous, a poster =
session is asynchronous. You can go, read the poster=20
and formulate opinions and questions independently of anyone else, =
including the author. If there is a time when the author is=20
supposed to be present, you can then go back and clarify any issues. You =
can't establish any consensus this way, but
it can be efficient at resolving issues.=20

Regards
Marshall=20
=20

>=20
> /Loa
>=20
> On 2011-01-10 12:09, Henk Uijterwaal wrote:
>> On 10/01/2011 11:14, Yoav Nir wrote:
>>>=20
>>> On Jan 10, 2011, at 11:31 AM, Lars Eggert wrote:
>>>=20
>>>> Hi,
>>>>=20
>>>> On 2011-1-8, at 19:41, R. B. wrote:
>>>>> I'm really in a rush, but I want to send my 0.02 too.  I like the =
idea of
>>>>> a poster session, since a single I-D could go unobserved in the =
churn of
>>>>> other I-Ds.
>>>>=20
>>>> many areas have open meetings where folks already can present such =
ideas.
>>>>=20
>>>> It's up to the ADs or chairs of such meetings to decide if =
presentation
>>>> time is warranted, with or without an accompanying ID.
>>>=20
>>> True, but in those meetings you usually get about 5 minutes to =
present (which
>>> is good), but then some other people present other things. Following =
that,
>>> those people in the audience who are interested will have to seek =
you out
>>> among the 1200 participants, or go to a mailing list just to ask =
questions.
>>>=20
>>> A poster session would allow for more interaction.
>>=20
>> I think that there is another issue.  Some people are good at doing 5
>> minute pitches of an idea, others aren't.  In case one is not, then I
>> think a poster session might be a good alternative.
>>=20
>> The costs for a poster session are almost 0.  Isn't this something we
>> can just try?
>>=20
>> Henk
>>=20
>>=20
>>=20
>=20
> --=20
>=20
>=20
> Loa Andersson                         email: =
loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From ynir@checkpoint.com  Mon Jan 10 05:55:26 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 D164E28C174 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:55:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.959
X-Spam-Level: 
X-Spam-Status: No, score=-9.959 tagged_above=-999 required=5 tests=[AWL=0.640,  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 Epjh29MNPNWG for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:55:26 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 9AFD83A69A4 for <ietf@ietf.org>; Mon, 10 Jan 2011 05:55:25 -0800 (PST)
X-CheckPoint: {4D2B1052-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p0ADvcYW020100;  Mon, 10 Jan 2011 15:57:38 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Mon, 10 Jan 2011 15:57:38 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Henk Uijterwaal <henk@ripe.net>
Date: Mon, 10 Jan 2011 15:57:40 +0200
Subject: Re: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: AcuwzlbNt+i9KgFoQBCXbDccBwHrkA==
Message-ID: <EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net>
In-Reply-To: <4D2AE8EC.2060202@ripe.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
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: Mon, 10 Jan 2011 13:55:26 -0000

On Jan 10, 2011, at 1:09 PM, Henk Uijterwaal wrote:

>=20
> The costs for a poster session are almost 0.  Isn't this something we
> can just try?

I don't agree that the costs are zero. You can't have the poster session la=
st all week long, because the presenter may want to go to other sessions. S=
o we need about 2 hours reserved for this. Maybe a morning session.=20

But then scheduling a WG meeting at the same time is like scheduling a TV s=
eries episode opposite the superbowl (substitute your country's favorite sp=
ort finals here). And all the ADs would want to go to the poster session, b=
ecause that's where the action is. So this reduces the amount of time slots=
 that we have in an IETF week.

Also, this puts another constraint on choosing a venue.  You need an area w=
ith room for lots of people, and space to put the "booths" or "desks" all a=
round. For example, Anaheim did not have a good area to hold a poster sessi=
on. Maastricht did. No idea about Beijing.

It may be a cost we agree to bear, but it is not zero.


From jmh@joelhalpern.com  Mon Jan 10 05:59:57 2011
Return-Path: <jmh@joelhalpern.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 6244728C10E for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.08
X-Spam-Level: 
X-Spam-Status: No, score=-103.08 tagged_above=-999 required=5 tests=[AWL=0.519, 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 IjlMNwVhF9GA for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 05:59:56 -0800 (PST)
Received: from hermes.mail.tigertech.net (hermes.mail.tigertech.net [64.62.209.72]) by core3.amsl.com (Postfix) with ESMTP id 5426328C161 for <ietf@ietf.org>; Mon, 10 Jan 2011 05:59:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 6E8024300D8 for <ietf@ietf.org>; Mon, 10 Jan 2011 06:02:10 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hermes.tigertech.net
Received: from [10.10.10.101] (pool-71-161-51-169.clppva.btas.verizon.net [71.161.51.169]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hermes.tigertech.net (Postfix) with ESMTPSA id 4BF094300B0 for <ietf@ietf.org>; Mon, 10 Jan 2011 06:02:09 -0800 (PST)
Message-ID: <4D2B115C.4040803@joelhalpern.com>
Date: Mon, 10 Jan 2011 09:02:04 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.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" <ietf@ietf.org>
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <521AF45A-BB95-4D1E-B35A-8B84A259DE49@checkpoint.com>
In-Reply-To: <521AF45A-BB95-4D1E-B35A-8B84A259DE49@checkpoint.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: Mon, 10 Jan 2011 13:59:57 -0000

To be blunt, if someone is holding a bar BoF without making it primarily 
a focus for discussion, they are missing the benefit of a Bar BoF.  Yes, 
we have a lot of "bar bofs."  And to the degree people are using these 
as unapproved BoFs for presenting their ideas to a wider audience, 
rather than for small group discussions in order to figure out what 
takes place, I think folks are making a mistake.  (The existence of, or 
attendance at, such a  pre-BoF is basically irrelevant to the process of 
getting a BoF or working group at a future IETF.)  In fact, whether they 
get called that or not, we have a very large number of very effective, 
ad hoc, bar bofs where a group of people working on a topic get together 
to work on a set of issues around that topic.  If this is not yete a 
topic that the IETF is working on, then often the issues include 
figuring out more clearly what the problem is, so that it can be 
effectively presented to the IETF.

I think that the requester is asking for some way to have a large number 
of different individuals briefly present their ideas, somewhat 
informally, to the community, to see if there is interest in the idea. 
In principle, this sounds good.  It is indeed one of the functions of 
the area meetings, but that does not mean we can not do something 
additional.
However, when I try to work out the logistics of such a thing, at the 
scale of the IETF, my head starts to hurt.  We would not want it to 
conflict with any working group sessions, for example, since there could 
be "posters" on any imaginable topic.  And we would want some filtering, 
since there are many ideas that, while interesting, belong in other fora 
(NANOG does review, limit, and select their lightning talks, for 
example.)  And it is not clear how one would use such a session to take 
thing forward.  Finding a more effective way to get early ideas useful 
airing in the community seems like a very good thing for the community, 
and would help encourage new ideas.

Yours,
Joel

On 1/10/2011 8:47 AM, Yoav Nir wrote:
>
> On Jan 10, 2011, at 1:22 PM, Loa Andersson wrote:
>
>> ALl,
>>
>> what is here called "poster session" reminds me a awful lot of the
>> bar bof's we been running for a long time.
>
> No coincidence. There's been a lot of criticism of these bar BoFs, and we keep looking for better ways to present new ideas.
>
>> Anyone care to draw the line between the two and try to motivate why
>> we need boths. As I see nothing stops from bringing a poster to a bar
>> bof, or a white board for taht matter.
>
> Despite the name, a bar BoF today is very much lecture-style. You have a presentation and a time for questions. There's really very little room for actual discussion (which supposedly happens later in some mailling list). A poster session allows for conversation with the I-D author, which may or may not lead to better results.
>
>>
>> /Loa
>>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From tme@americafree.tv  Mon Jan 10 06:06:36 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 AC7713A6962 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 06:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.225
X-Spam-Level: 
X-Spam-Status: No, score=-102.225 tagged_above=-999 required=5 tests=[AWL=0.374, 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 f0IPTb+BL320 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 06:06:35 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id B9BB63A6834 for <ietf@ietf.org>; Mon, 10 Jan 2011 06:06:35 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 7764799EBE71; Mon, 10 Jan 2011 09:08:49 -0500 (EST)
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com>
Date: Mon, 10 Jan 2011 09:08:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BDB01D0F-6C25-4414-85C0-A892F07396C4@americafree.tv>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1081)
Cc: Henk Uijterwaal <henk@ripe.net>, "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, 10 Jan 2011 14:06:36 -0000

On Jan 10, 2011, at 8:57 AM, Yoav Nir wrote:

>=20
> On Jan 10, 2011, at 1:09 PM, Henk Uijterwaal wrote:
>=20
>>=20
>> The costs for a poster session are almost 0.  Isn't this something we
>> can just try?
>=20
> I don't agree that the costs are zero. You can't have the poster =
session last all week long, because the presenter may want to go to =
other sessions. So we need about 2 hours reserved for this. Maybe a =
morning session.=20

What I would suggest (if this goes forward) is

- some space is set aside, ideally in or near the break area / room

- posters SHOULD be put up in the AM, starting at breakfast.=20
=20
- the last refreshment break of the day, the authors are supposed to be =
at their posters. (They can be at other times, but they SHOULD be at =
this time.)

People could then read posters at any time during the day, come back at =
the break and ask questions, raise issues, etc.=20

ADs could also quickly judge the interest in a poster, by how many =
people are haranguing the author.=20

As the "session" would last one full day, different days could =
accommodate different areas.=20

Regards
Marshall

>=20
> But then scheduling a WG meeting at the same time is like scheduling a =
TV series episode opposite the superbowl (substitute your country's =
favorite sport finals here). And all the ADs would want to go to the =
poster session, because that's where the action is. So this reduces the =
amount of time slots that we have in an IETF week.
>=20
> Also, this puts another constraint on choosing a venue.  You need an =
area with room for lots of people, and space to put the "booths" or =
"desks" all around. For example, Anaheim did not have a good area to =
hold a poster session. Maastricht did. No idea about Beijing.
>=20
> It may be a cost we agree to bear, but it is not zero.
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From vesely@tana.it  Mon Jan 10 06:41:47 2011
Return-Path: <vesely@tana.it>
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 6925A3A69B7 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 06:41:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.176
X-Spam-Level: 
X-Spam-Status: No, score=-5.176 tagged_above=-999 required=5 tests=[AWL=-0.457, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 UdL1Jmy1be8s for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 06:41:46 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 362523A6975 for <ietf@ietf.org>; Mon, 10 Jan 2011 06:41:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1294670638; bh=uvVtF1ZWn4H9tN3MqxMBhYuIvIOLdmvxbIOrx0m4dr0=; l=1107; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=SPvaQ1/MsrdmxF4h9Hg+pjLk4CVXlHmcTykpw2yscvmrWwhzIc9d0AXbVz/8ZEQB4 KSbl9gcdAOmlSwaD5Q8iL2b7uue7IUfLdRGXMTt0gVGbZlB0tD+2pAUde9DQRcZKBa iljMs4Yr0pqLgNBf2Gan4nK5IduQRQnURdlpzTWo=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 10 Jan 2011 15:43:58 +0100 id 00000000005DC047.000000004D2B1B2E.00004DD8
Message-ID: <4D2B1B2E.7040000@tana.it>
Date: Mon, 10 Jan 2011 15:43:58 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.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: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net>	<EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com> <BDB01D0F-6C25-4414-85C0-A892F07396C4@americafree.tv>
In-Reply-To: <BDB01D0F-6C25-4414-85C0-A892F07396C4@americafree.tv>
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: Mon, 10 Jan 2011 14:41:47 -0000

On 10/Jan/11 15:08, Marshall Eubanks wrote:
> What I would suggest (if this goes forward) is
> 
> - some space is set aside, ideally in or near the break area / room
> 
> - posters SHOULD be put up in the AM, starting at breakfast. 
>  
> - the last refreshment break of the day, the authors are supposed to be at their posters. (They can be at other times, but they SHOULD be at this time.)
> 
> People could then read posters at any time during the day, come back at the break and ask questions, raise issues, etc. 
> 
> ADs could also quickly judge the interest in a poster, by how many people are haranguing the author. 
> 
> As the "session" would last one full day, different days could accommodate different areas. 

+1!

For filtering, Brian already mentioned that posting a draft is
necessary for assigning floor space.  To expand, those I-Ds would
contain a short "visually impaired" version of the proposed poster.
It would then take an AD or similar role to formally accept the
proposal by telling the secretariat (or equivalent web-app) to
allocate a poster slot for it.


From henk@ripe.net  Mon Jan 10 06:53:22 2011
Return-Path: <henk@ripe.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 426BA28C190 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 06:53:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[AWL=-0.673, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 0HQkmdm3O6mV for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 06:53:21 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id D379D3A69B6 for <ietf@ietf.org>; Mon, 10 Jan 2011 06:53:20 -0800 (PST)
Received: from ayeaye.ripe.net ([193.0.23.5]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <henk@ripe.net>) id 1PcJ9f-0007ME-Vb for ietf@ietf.org; Mon, 10 Jan 2011 15:55:34 +0100
Received: from [193.0.21.124] (helo=guest133.guestnet.ripe.net) by ayeaye.ripe.net with esmtp (Exim 4.72) (envelope-from <henk@ripe.net>) id 1PcJ9f-000439-Qr for ietf@ietf.org; Mon, 10 Jan 2011 15:55:31 +0100
Message-ID: <4D2B1DE3.7090005@ripe.net>
Date: Mon, 10 Jan 2011 15:55:31 +0100
From: Henk Uijterwaal <henk@ripe.net>
Organization: RIPE NCC
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net> <EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com>
In-Reply-To: <EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: -
X-RIPE-Spam-Report: Spam Total Points:   -1.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 MISSING_HEADERS        Missing To: header -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d585882252cb18356a2fc989ad7eaec489
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, 10 Jan 2011 14:53:22 -0000

On 10/01/2011 14:57, Yoav Nir wrote:
> 
> On Jan 10, 2011, at 1:09 PM, Henk Uijterwaal wrote:

>> The costs for a poster session are almost 0.  Isn't this something we can
>> just try?
> 
> I don't agree that the costs are zero. You can't have the poster session last
> all week long, because the presenter may want to go to other sessions. So we
> need about 2 hours reserved for this. Maybe a morning session.

My idea would be that the pinboards for the posters are available from day one
onwards and people with a poster can put it up on Sunday.  Folks can come and
watch.  Select 2 or 3 coffee breaks where the person presenting the poster
must be near his poster for questions and discussion.

> Also, this puts another constraint on choosing a venue.  You need an area
> with room for lots of people, and space to put the "booths" or "desks" all
> around. For example, Anaheim did not have a good area to hold a poster
> session. Maastricht did. No idea about Beijing.

As far as I remember Anaheim: it did have a few hallways between meeting
rooms and coffee pot.  Sounds like an ideal place for a poster session.
Beijing had the same options.

Henk


-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

I confirm today what I denied yesterday.            Anonymous Politician.

From tme@americafree.tv  Mon Jan 10 08:48:27 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 4C2E23A6B04 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 08:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level: 
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 naCz++qc0r-o for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 08:48:26 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 40FFF3A67FA for <ietf@ietf.org>; Mon, 10 Jan 2011 08:48:23 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 5363C99EFA52 for <ietf@ietf.org>; Mon, 10 Jan 2011 11:50:37 -0500 (EST)
From: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: National Strategy for Trusted Identities in Cyberspace
Date: Mon, 10 Jan 2011 11:50:37 -0500
Message-Id: <A297E310-B602-44AC-9E0A-E818DBF2B866@americafree.tv>
To: "ietf@ietf.org Discussion" <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: Mon, 10 Jan 2011 16:48:27 -0000

Friday, the White House blog announced the creation of=20

"A National Program Office for Enhancing Online Trust and Privacy"

=
http://www.whitehouse.gov/blog/2011/01/07/national-program-office-enhancin=
g-online-trust-and-privacy

This activity will be based on the National Strategy for
Trusted Identities in Cyberspace, which is available in draft form

http://www.dhs.gov/xlibrary/assets/ns_tic.pdf

There was a comment period, which is now closed (and the comments have =
now been taken down)

http://www.msnbc.msn.com/id/37943900/

http://www.nstic.ideascale.com/

The draft action items include

Action 2:
Develop a Shared, Comprehensive Public/Private Sector Implementation =
Plan

Action 4:
Work Among the Public/Private Sectors to Implement Enhanced Privacy
Protections

Action 5:
Coordinate the Development and Refinement of Risk Models and =
Interoperability
Standards

Standards that cover interoperability requirements, trustmark criteria, =
and accreditation will pave a path that supports choice across =
solutions, ultimately accelerating Identity Ecosystem adoption. All =
detailed actions associated with Identity Ecosystem standards will build =
on existing efforts undertaken by the Federal Government, trust =
framework providers, private sector, standards bodies, and international =
organizations.

Standards established within the Identity Ecosystem will require =
incorporation of privacy guidelines. They should also require, to the =
extent feasible, adoption of protocols that minimize the ability to link =
or aggregate transactions and transaction data across Identity Ecosystem =
participants and relying parties, while maintaining individual =
transaction history, integrity, and auditability.	Standards =
development, adoption, or enhancement will support autonomy and choice =
among Identity Ecosystem providers and flexibility within industry =
sectors, while facilitating cross-sector and international =
interoperability.

 -----

What is proposed is apparently something like an official version of the =
existing Certificate system, and apparently will involve technical =
standards setting.

This is an area where the IETF has some expertise, and also should have =
some concerns. I must admit that statements such as this

"The Governance Layer enables unaffiliated entities to trust each =
other=92s digital identities. A Governance Authority will establish the =
criteria for assessing and certifying Accrediting Authorities, who in =
turn assess and certify service providers. In addition, the Governance =
Authority will control the rules for trustmarks that indicate the =
service provider=92s standing as a participant within the Identity =
Ecosystem."

make me nervous.=20

Has the IETF (presumably, the IAB) considered a response to this =
proposal ?  Should it ?

Regards
Marshall=

From john-lame@jck.com  Sat Jan  8 03:50:30 2011
Return-Path: <john-lame@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 BB3C23A69CE for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 03:50:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 WO3N-VZTEccQ for <ietf@core3.amsl.com>; Sat,  8 Jan 2011 03:50:29 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 9B5ED28B23E for <ietf@ietf.org>; Sat,  8 Jan 2011 03:50:29 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PbXLY-000MsA-OR; Sat, 08 Jan 2011 06:52:36 -0500
Date: Sat, 08 Jan 2011 06:52:36 -0500
From: John C Klensin <john-lame@jck.com>
To: Andrew Sullivan <ajs@shinkuro.com>, ietf@ietf.org
Subject: Re: Old transport-layer protocols to Historic?
Message-ID: <826A5991A05D9E61F34B3DB4@PST.JCK.COM>
In-Reply-To: <20110107141542.GB34186@shinkuro.com>
References: <20110106144531.665a7a7059d7ee80bb4d670165c8327d.33917bb4b8.wbe@email03.secureserver.net> <AANLkTinUhozsniX1OOKyRhSmNy=HzEMJF6Bu=ZmHc1_J@mail.gmail.com> <4D26B529.8070303@gmail.com> <20110107141542.GB34186@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-Mailman-Approved-At: Mon, 10 Jan 2011 09:02: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: Sat, 08 Jan 2011 11:50:30 -0000

+1

--On Friday, January 07, 2011 09:15 -0500 Andrew Sullivan
<ajs@shinkuro.com> wrote:

> I'm not keen to start a language war, but. . .
> 
> On Fri, Jan 07, 2011 at 08:39:37AM +0200, Mykyta Yevstifeyev
> wrote:
> 
>> Moreover, 'obsoleted' means the same as 'deprecated' or
>> 'non-current'   (see
>> http://www.synonym.com/synonyms/obsolete/ or  
>> http://dictionary.sensagent.com/obsolete/en-en/#synonyms). So
>> it is a   problem in RFC2026.
> 
> . . .I fully disagree with that, regardless of what those
> claims of synonymy say.  To deprecate something is to express
> disapproval.  To mark something as obsolete doesn't do that;
> it merely says that the marked thing is outdated.  There is a
> useful distinction here worth maintaining.
> 
> A





From bidulock@openss7.org  Sun Jan  9 00:04:05 2011
Return-Path: <bidulock@openss7.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 A722C3A6955; Sun,  9 Jan 2011 00:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level: 
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120,  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 GldLkzpxynx0; Sun,  9 Jan 2011 00:04:04 -0800 (PST)
Received: from gw.openss7.com (gw.openss7.com [206.75.119.236]) by core3.amsl.com (Postfix) with ESMTP id A1AA03A694F; Sun,  9 Jan 2011 00:04:04 -0800 (PST)
Received: from wilbur.pigworks.openss7.net (ns5.evil.openss7.net [192.168.9.5]) by gw.openss7.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0986A4g024931; Sun, 9 Jan 2011 01:06:10 -0700
Received: from wilbur.pigworks.openss7.net (localhost [127.0.0.1]) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id p0986AfW013001; Sun, 9 Jan 2011 01:06:10 -0700
Received: (from brian@localhost) by wilbur.pigworks.openss7.net (8.14.3/8.14.3/Submit) id p0986AOS013000; Sun, 9 Jan 2011 01:06:10 -0700
Date: Sun, 9 Jan 2011 01:06:10 -0700
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Old transport-layer protocols to Historic?
Message-ID: <20110109080610.GA12782@openss7.org>
Mail-Followup-To: Mykyta Yevstifeyev <evnikita2@gmail.com>, Bob Hinden <bob.hinden@gmail.com>, tsvwg@ietf.org, IETF Discussion <ietf@ietf.org>
References: <4D2556C9.9020901@gmail.com> <AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com> <4D2842B8.7090100@gmail.com> <4D29556A.6060902@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D29556A.6060902@gmail.com>
Organization: http://www.openss7.org/
Dsn-Notification-To: <bidulock@openss7.org>
X-Spam-To: <blockme@openss7.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Mailman-Approved-At: Mon, 10 Jan 2011 09:02:47 -0800
Cc: Bob Hinden <bob.hinden@gmail.com>, tsvwg@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bidulock@openss7.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: Sun, 09 Jan 2011 08:04:05 -0000

Mykyta,

RDP is still in use (I know of companies using it).  It is
used heavily as a transport for a "popular brand" of NAS for
dial access call control and was a precursor to MEGACO/H.248.
RDP was the initial transport used for gateway control (such
as SGCP) until SCTP was developed.  Many commercial gateways
still support these older pre-standard (to MEGACO) control
protocols.  Some older devices still provisioned in the network
only support the older protocols.

Yah, I know it was EXPERIMENTAL, but we had nothing before SCTP
that would fit the bill.  Its limitations was one of the driving
forces behind developing SCTP.  One of the original protocol
attempts abandonned before SCTP was based on RDP.

Please leave RDP alone.

--brian

-- 
Brian F. G. Bidulock
bidulock@openss7.org
http://www.openss7.org/

From erosen@cisco.com  Mon Jan 10 09:43:44 2011
Return-Path: <erosen@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 D743B3A6AFE; Mon, 10 Jan 2011 09:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.542
X-Spam-Level: 
X-Spam-Status: No, score=-10.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 fvE3nwR1NE1W; Mon, 10 Jan 2011 09:43:44 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id CB5A93A6AFC; Mon, 10 Jan 2011 09:43:43 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 10 Jan 2011 17:45:58 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0AHjvdi025805; Mon, 10 Jan 2011 17:45:57 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id p0AHju44022832;  Mon, 10 Jan 2011 12:45:57 -0500
To: bidulock@openss7.org
Subject: Re: Old transport-layer protocols to Historic?
In-reply-to: Your message of Sun, 09 Jan 2011 01:06:10 -0700. <20110109080610.GA12782@openss7.org>
Date: Mon, 10 Jan 2011 12:45:56 -0500
Message-ID: <22831.1294681556@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, tsvwg@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@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: Mon, 10 Jan 2011 17:43:45 -0000

> RDP is still in use

> was the initial transport used for gateway control (such as SGCP) until
> SCTP was developed.

> Many commercial gateways still support these older pre-standard (to
> MEGACO) control protocols.  Some older devices still provisioned in the
> network only support the older protocols.

> but we had nothing before SCTP that would fit the bill.  Its limitations
> was one of the driving forces behind developing SCTP.

So RDP is a useful and deployed pre-standards protocol that was one of the
driving forces behind a successful standardization effort.  But newer
applications that need that kind of transport instead use the standard,
SCTP.

I don't know how one could possibly make a stronger case for classifying the
RDP spec as Historic!

However, I do agree with John Klensin's remark that reclassification is not
worth the energy it takes.










From doug@ewellic.org  Mon Jan 10 09:52:55 2011
Return-Path: <doug@ewellic.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 97AE43A67AB for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 09:52:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.504
X-Spam-Level: 
X-Spam-Status: No, score=-2.504 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, SARE_SUB_ENC_UTF8=0.152]
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 lHG6WNR6AHA2 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 09:52:54 -0800 (PST)
Received: from smtpoutwbe02.prod.mesa1.secureserver.net (smtpoutwbe02.prod.mesa1.secureserver.net [208.109.78.113]) by core3.amsl.com (Postfix) with SMTP id 7740B3A6822 for <ietf@ietf.org>; Mon, 10 Jan 2011 09:52:54 -0800 (PST)
Received: (qmail 16802 invoked from network); 10 Jan 2011 17:55:07 -0000
Received: from unknown (HELO localhost) (72.167.218.134) by smtpoutwbe02.prod.mesa1.secureserver.net with SMTP; 10 Jan 2011 17:55:07 -0000
Received: (qmail 7448 invoked by uid 99); 10 Jan 2011 17:55:07 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.190
User-Agent: Web-Based Email 5.3.03
Message-Id: <20110110105507.665a7a7059d7ee80bb4d670165c8327d.0eecac8a2f.wbe@email03.secureserver.net>
From: "Doug Ewell" <doug@ewellic.org>
To: erosen@cisco.com, "IETF Discussion" <ietf@ietf.org>
Subject: RE: Old transport-layer protocols to =?UTF-8?Q?Historic=3F?=
Date: Mon, 10 Jan 2011 10:55:07 -0700
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, 10 Jan 2011 17:52:55 -0000

Eric Rosen <erosen at cisco dot com> wrote:

> So RDP is a useful and deployed pre-standards protocol that was one of th=
e
> driving forces behind a successful standardization effort.  But newer
> applications that need that kind of transport instead use the standard,
> SCTP.
>=20
> I don't know how one could possibly make a stronger case for classifying =
the
> RDP spec as Historic!

If "Historic" has taken on the connotation of "this spec is deprecated,
don't use it any more," then to the extent it is useful and deployed,
this would send the wrong message.  Just like FTP.

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =C2=AD



From hannes.tschofenig@gmx.net  Mon Jan 10 10:49:55 2011
Return-Path: <hannes.tschofenig@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 E10BF3A6B0B for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 10:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.61
X-Spam-Level: 
X-Spam-Status: No, score=-101.61 tagged_above=-999 required=5 tests=[AWL=-1.013, BANKING_LAWS=2.002, 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 wW5ycf95bU9H for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 10:49:54 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 191603A6B08 for <ietf@ietf.org>; Mon, 10 Jan 2011 10:49:53 -0800 (PST)
Received: (qmail invoked by alias); 10 Jan 2011 18:52:07 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.7]) [88.115.222.204] by mail.gmx.net (mp070) with SMTP; 10 Jan 2011 19:52:07 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/OGOx7YmLONCU1Sv0pMgnT+aDHM/DDc4xjVufX25 H8oZWtwkRcYk5r
Subject: Re: National Strategy for Trusted Identities in Cyberspace
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=windows-1252
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <A297E310-B602-44AC-9E0A-E818DBF2B866@americafree.tv>
Date: Mon, 10 Jan 2011 20:52:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F1CEE29-9EF7-4B81-BC58-FEC02320D0E6@gmx.net>
References: <A297E310-B602-44AC-9E0A-E818DBF2B866@americafree.tv>
To: Marshall Eubanks <tme@americafree.tv>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Cc: "ietf@ietf.org Discussion" <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, 10 Jan 2011 18:49:56 -0000

Hi Marshall,=20

the comment period last year was very short; too short for us to reply =
at the time when we learned about it. Other groups had problems getting =
their feedback in as well.=20

The work they are looking into is related to web identity management =
protocols and trust frameworks. There are technical aspects as well as =
policy parts to the larger body of work.=20

To provide a comparison I would pick the credit card industry. There are =
technical standards (such as a completely insecure "authentication =
mechanism") but there are also security best current practices (such as =
the PCI DSS work), an architecture how the different actors (such as =
merchants, acquirer, payment networks, issuers, and banks) interact, and =
regulation (banking laws, liability guarantees for unauthorized credit =
and debit card charges), policies regarding levels of authentication =
assurances, etc.=20

=46rom the technical work a lot centers around OpenID and SAML profiles. =
Other protocols would be relevant to the exchange of data but the work =
has not progressed so far yet.=20
=20
You raised the question whether the IETF/IAB should have a look at this =
topic. Maybe not a bad idea and the next IETF meeting is upcoming to =
talk about it. And "yes", there are also interesting privacy questions.=20=


Ciao
Hannes

PS: There are similar efforts outside the US (such as in Europe). They =
do not, however, receive so much press attention.=20

On Jan 10, 2011, at 6:50 PM, Marshall Eubanks wrote:

> Friday, the White House blog announced the creation of=20
>=20
> "A National Program Office for Enhancing Online Trust and Privacy"
>=20
> =
http://www.whitehouse.gov/blog/2011/01/07/national-program-office-enhancin=
g-online-trust-and-privacy
>=20
> This activity will be based on the National Strategy for
> Trusted Identities in Cyberspace, which is available in draft form
>=20
> http://www.dhs.gov/xlibrary/assets/ns_tic.pdf
>=20
> There was a comment period, which is now closed (and the comments have =
now been taken down)
>=20
> http://www.msnbc.msn.com/id/37943900/
>=20
> http://www.nstic.ideascale.com/
>=20
> The draft action items include
>=20
> Action 2:
> Develop a Shared, Comprehensive Public/Private Sector Implementation =
Plan
>=20
> Action 4:
> Work Among the Public/Private Sectors to Implement Enhanced Privacy
> Protections
>=20
> Action 5:
> Coordinate the Development and Refinement of Risk Models and =
Interoperability
> Standards
>=20
> Standards that cover interoperability requirements, trustmark =
criteria, and accreditation will pave a path that supports choice across =
solutions, ultimately accelerating Identity Ecosystem adoption. All =
detailed actions associated with Identity Ecosystem standards will build =
on existing efforts undertaken by the Federal Government, trust =
framework providers, private sector, standards bodies, and international =
organizations.
>=20
> Standards established within the Identity Ecosystem will require =
incorporation of privacy guidelines. They should also require, to the =
extent feasible, adoption of protocols that minimize the ability to link =
or aggregate transactions and transaction data across Identity Ecosystem =
participants and relying parties, while maintaining individual =
transaction history, integrity, and auditability.	Standards =
development, adoption, or enhancement will support autonomy and choice =
among Identity Ecosystem providers and flexibility within industry =
sectors, while facilitating cross-sector and international =
interoperability.
>=20
> -----
>=20
> What is proposed is apparently something like an official version of =
the existing Certificate system, and apparently will involve technical =
standards setting.
>=20
> This is an area where the IETF has some expertise, and also should =
have some concerns. I must admit that statements such as this
>=20
> "The Governance Layer enables unaffiliated entities to trust each =
other=92s digital identities. A Governance Authority will establish the =
criteria for assessing and certifying Accrediting Authorities, who in =
turn assess and certify service providers. In addition, the Governance =
Authority will control the rules for trustmarks that indicate the =
service provider=92s standing as a participant within the Identity =
Ecosystem."
>=20
> make me nervous.=20
>=20
> Has the IETF (presumably, the IAB) considered a response to this =
proposal ?  Should it ?
>=20
> Regards
> Marshall
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From hannes.tschofenig@gmx.net  Mon Jan 10 11:10:48 2011
Return-Path: <hannes.tschofenig@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 AB9703A6B08 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, 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 vgyEi1YI+r7Z for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:10:48 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 6F6D93A69C5 for <ietf@ietf.org>; Mon, 10 Jan 2011 11:10:46 -0800 (PST)
Received: (qmail invoked by alias); 10 Jan 2011 19:13:00 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.7]) [88.115.222.204] by mail.gmx.net (mp066) with SMTP; 10 Jan 2011 20:13:00 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX187kLN1SwQ7HCfFTcsHE30GRO7huylUcX65d0+3zi 3Z/z3Hz/JbqoAm
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <521AF45A-BB95-4D1E-B35A-8B84A259DE49@checkpoint.com>
Date: Mon, 10 Jan 2011 21:12:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C83D389E-077E-42DC-A0E6-178B24D80A6C@gmx.net>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <521AF45A-BB95-4D1E-B35A-8B84A259DE49@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 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: Mon, 10 Jan 2011 19:10:48 -0000

Lars has written a draft in response to "bar BoFs" you describe below:=20=


"Considerations for Having a Successful Bar BOF Session"
http://tools.ietf.org/html/draft-eggert-successful-bar-bof-00
=20

On Jan 10, 2011, at 3:47 PM, Yoav Nir wrote:

> Despite the name, a bar BoF today is very much lecture-style. You have =
a presentation and a time for questions. There's really very little room =
for actual discussion (which supposedly happens later in some mailling =
list). A poster session allows for conversation with the I-D author, =
which may or may not lead to better results.


From huitema@microsoft.com  Mon Jan 10 11:26:31 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 C1E2328C0E4 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.371
X-Spam-Level: 
X-Spam-Status: No, score=-10.371 tagged_above=-999 required=5 tests=[AWL=0.228, 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 EnxStII5Yy-r for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:26:30 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.212]) by core3.amsl.com (Postfix) with ESMTP id D8B133A6B1D for <ietf@ietf.org>; Mon, 10 Jan 2011 11:26:30 -0800 (PST)
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) by TK5-EXGWY-E801.partners.extranet.microsoft.com (10.251.56.50) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 10 Jan 2011 11:28:45 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC103.redmond.corp.microsoft.com (157.54.86.9) with Microsoft SMTP Server (TLS) id 14.1.255.3; Mon, 10 Jan 2011 11:28:45 -0800
Received: from TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com ([169.254.3.137]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Mon, 10 Jan 2011 11:28:45 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Yoav Nir <ynir@checkpoint.com>
Subject: RE: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: AQHLrcd6vonkcaXl+0yg4NyvmygTcZPE59EAgACGlICAAnLGgIACm5oAgAAMEACAAA9uAIAAA6+AgAAohQCAAFrfgP//ffIg
Date: Mon, 10 Jan 2011 19:28:43 +0000
Message-ID: <CEBCE3CF81D2D441B14B84256C3C46810F8614@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <521AF45A-BB95-4D1E-B35A-8B84A259DE49@checkpoint.com> <C83D389E-077E-42DC-A0E6-178B24D80A6C@gmx.net>
In-Reply-To: <C83D389E-077E-42DC-A0E6-178B24D80A6C@gmx.net>
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: "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, 10 Jan 2011 19:26:31 -0000

In the old days, you would get a bar BOF by rounding up a few buddies and p=
aying for the drinks. I suppose that you can still do that, and don't need =
to get the secretariat involved!

-- Christian Huitema


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Han=
nes Tschofenig
Sent: Monday, January 10, 2011 11:13 AM
To: Yoav Nir
Cc: ietf@ietf.org
Subject: Re: Poster sessions

Lars has written a draft in response to "bar BoFs" you describe below:=20

"Considerations for Having a Successful Bar BOF Session"
http://tools.ietf.org/html/draft-eggert-successful-bar-bof-00
=20

On Jan 10, 2011, at 3:47 PM, Yoav Nir wrote:

> Despite the name, a bar BoF today is very much lecture-style. You have a =
presentation and a time for questions. There's really very little room for =
actual discussion (which supposedly happens later in some mailling list). A=
 poster session allows for conversation with the I-D author, which may or m=
ay not lead to better results.

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


From dhc2@dcrocker.net  Mon Jan 10 11:48:54 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 1963B3A6B0A for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:48:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.581
X-Spam-Level: 
X-Spam-Status: No, score=-6.581 tagged_above=-999 required=5 tests=[AWL=0.018,  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 01smMoKfUVoD for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:48:53 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id B1A243A6830 for <ietf@ietf.org>; Mon, 10 Jan 2011 11:48:48 -0800 (PST)
Received: from [192.168.1.117] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0AJosbP026104 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2011 11:50:59 -0800
Message-ID: <4D2B631E.1050701@dcrocker.net>
Date: Mon, 10 Jan 2011 11:50:54 -0800
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: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Contacts to Czech Technical University in Prague?
References: <DB1268BC-E64F-46CE-B60A-2893672798F0@gmx.net>
In-Reply-To: <DB1268BC-E64F-46CE-B60A-2893672798F0@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 10 Jan 2011 11:50:59 -0800 (PST)
Cc: 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: Mon, 10 Jan 2011 19:48:54 -0000

On 1/10/2011 12:39 AM, Hannes Tschofenig wrote:
> A punch of us from the IAB and the IESG are trying to put a workshop on
> "Interconnecting Smart Objects with the Internet" together. The workshop days
> are March 25th/26th, i.e. Friday/Saturday before the start of the IETF
> meeting in Prague.


Just to check:  I assume you folk know about a somewhat related event that 
overlaps with this, on Friday, in nearby Leipzig:

    The Governance Dimension of the Internet of Things

    <http://www.medienstadt-leipzig.org/euronf/programme.html>

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From hannes.tschofenig@gmx.net  Mon Jan 10 11:59:32 2011
Return-Path: <hannes.tschofenig@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 A9DAE28C0F4 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, 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 M0Yl4ygtM2mN for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 11:59:31 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 3D00828B23E for <ietf@ietf.org>; Mon, 10 Jan 2011 11:59:31 -0800 (PST)
Received: (qmail invoked by alias); 10 Jan 2011 20:01:44 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.7]) [88.115.222.204] by mail.gmx.net (mp045) with SMTP; 10 Jan 2011 21:01:44 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19ifDhGp2diuK+hrDxLRbDlyK0tPCUbPS7kPhgKyQ p4oi8bGB5Q4su+
Subject: Re: Contacts to Czech Technical University in Prague?
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <4D2B631E.1050701@dcrocker.net>
Date: Mon, 10 Jan 2011 22:01:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <79A07C88-F7B1-4D14-A5F9-A975E4CDEE3B@gmx.net>
References: <DB1268BC-E64F-46CE-B60A-2893672798F0@gmx.net> <4D2B631E.1050701@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
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, 10 Jan 2011 19:59:32 -0000

Hi Dave,=20

Yes, we know about this other workshop. We also checked how likely the =
participants overlap.=20
Based on our assessment after the discussions with some of the workshop =
organizers we concluded that it is OK to move forward with our workshop =
organization as initially planned.=20

Ciao
Hannes

On Jan 10, 2011, at 9:50 PM, Dave CROCKER wrote:

>=20
>=20
> On 1/10/2011 12:39 AM, Hannes Tschofenig wrote:
>> A punch of us from the IAB and the IESG are trying to put a workshop =
on
>> "Interconnecting Smart Objects with the Internet" together. The =
workshop days
>> are March 25th/26th, i.e. Friday/Saturday before the start of the =
IETF
>> meeting in Prague.
>=20
>=20
> Just to check:  I assume you folk know about a somewhat related event =
that overlaps with this, on Friday, in nearby Leipzig:
>=20
>   The Governance Dimension of the Internet of Things
>=20
>   <http://www.medienstadt-leipzig.org/euronf/programme.html>
>=20
> d/
> --=20
>=20
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net


From dhc2@dcrocker.net  Mon Jan 10 12:06:48 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 050CD3A6B11 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 12:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 QAtiTe3OpzHs for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 12:06:47 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 230E83A6B0C for <ietf@ietf.org>; Mon, 10 Jan 2011 12:06:47 -0800 (PST)
Received: from [192.168.1.117] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0AK8sw1026837 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 10 Jan 2011 12:08:59 -0800
Message-ID: <4D2B6756.1010600@dcrocker.net>
Date: Mon, 10 Jan 2011 12:08:54 -0800
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: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Contacts to Czech Technical University in Prague?
References: <DB1268BC-E64F-46CE-B60A-2893672798F0@gmx.net> <4D2B631E.1050701@dcrocker.net> <79A07C88-F7B1-4D14-A5F9-A975E4CDEE3B@gmx.net>
In-Reply-To: <79A07C88-F7B1-4D14-A5F9-A975E4CDEE3B@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 10 Jan 2011 12:08:59 -0800 (PST)
Cc: 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: Mon, 10 Jan 2011 20:06:48 -0000

On 1/10/2011 12:01 PM, Hannes Tschofenig wrote:
> Yes, we know about this other workshop. We also checked how likely the participants overlap.


ack. tnx.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From jdfalk-lists@cybernothing.org  Mon Jan 10 13:01:49 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 C79693A67D8 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:01:49 -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 wqBn8zP4K0M2 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:01:48 -0800 (PST)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by core3.amsl.com (Postfix) with ESMTP id 817A73A67AE for <ietf@ietf.org>; Mon, 10 Jan 2011 13:01:48 -0800 (PST)
Received: from [192.168.11.38] (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 p0AL3xd8004646 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Mon, 10 Jan 2011 13:04:02 -0800
X-DKIM: Sendmail DKIM Filter v2.6.0 ocelope.disgruntled.net p0AL3xd8004646
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybernothing.org; s=triac; t=1294693442; bh=5wXQaJ1b3yw7aiNgj0OC2OqQ9iNHYDCSrfCbfFVpS g4=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=Wr807DaEB5kl x+sD/CVAI69bvTMBSjHjd+XvgcKopZLIoMSGe0ru1UC68UCOS03NS0hXmZ/T7olnDJ6 xNzWOVfkN93ylVks/owTT/KPOYx9Ox51eowJWSwngUkXAzYxbJ8EebvrdBrsH+to6z8 7yRxRTboWvjoyiA5Q+t7ucwqY=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Poster sessions
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
In-Reply-To: <4D2B1B2E.7040000@tana.it>
Date: Mon, 10 Jan 2011 13:03:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E9983D6-C8D7-4C83-84BC-9FD89D484E50@cybernothing.org>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net>	<EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com> <BDB01D0F-6C25-4414-85C0-A892F07396C4@americafree.tv> <4D2B1B2E.7040000@tana.it>
To: IETF Discussion <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, 10 Jan 2011 21:01:50 -0000

On Jan 10, 2011, at 6:43 AM, Alessandro Vesely wrote:

> On 10/Jan/11 15:08, Marshall Eubanks wrote:
>> What I would suggest (if this goes forward) is
>>=20
>> - some space is set aside, ideally in or near the break area / room
>>=20
>> - posters SHOULD be put up in the AM, starting at breakfast.=20
>>=20
>> - the last refreshment break of the day, the authors are supposed to =
be at their posters. (They can be at other times, but they SHOULD be at =
this time.)
>>=20
>> People could then read posters at any time during the day, come back =
at the break and ask questions, raise issues, etc.=20
>>=20
>> ADs could also quickly judge the interest in a poster, by how many =
people are haranguing the author.=20
>>=20
>> As the "session" would last one full day, different days could =
accommodate different areas.=20
>=20
> +1!

+1

> For filtering, Brian already mentioned that posting a draft is
> necessary for assigning floor space.

+1


From spencer@wonderhamster.org  Mon Jan 10 13:11:23 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 2321F3A67B2 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.15
X-Spam-Level: 
X-Spam-Status: No, score=-102.15 tagged_above=-999 required=5 tests=[AWL=0.448, 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 R4uYef67dYj7 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:11:17 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id E28E33A67B4 for <ietf@ietf.org>; Mon, 10 Jan 2011 13:11:16 -0800 (PST)
Received: from S73602b ([12.172.14.11]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0LtHlr-1QHPwT0JyN-012XJ1; Mon, 10 Jan 2011 16:13:22 -0500
Message-ID: <90C86C2FDDB843D49216F239769642CF@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Marshall Eubanks" <tme@americafree.tv>, "Yoav Nir" <ynir@checkpoint.com>
References: <4D258AB3.9010903@tana.it><CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com><tslipy2ndm6.fsf@mit.edu><CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com><4D26940F.3020404@gmail.com><AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com><ED6A886C-2FBC-4312-9066-18108363249C@nokia.com><E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com><4D2AE8EC.2060202@ripe.net><EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com> <BDB01D0F-6C25-4414-85C0-A892F07396C4@americafree.tv>
Subject: Re: Poster sessions
Date: Mon, 10 Jan 2011 15:13:04 -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:+yw8WCt/G5WH3AQp9u8UM8dxA1KatqdsYFv3+e573NO WLKyxvvfhoToHwEuF2soGFymAJAwJw9dEMduvGX60nJN06femA +196GfwewOJo89k91KLslbGs+cv9zAoay8WBX9RASYE8S1z0vL gv4jMg1n9RcLZ4IXIe9/F9LB1z60LvY1KEq6x3WyiefEKFrELZ v3aOrrBdiZecqD2S1UcP8XpTUuTcqOBdVQjEgxg9zw=
Cc: Henk Uijterwaal <henk@ripe.net>, 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, 10 Jan 2011 21:11:23 -0000

I like the idea of using break time for these conversations, much better 
than either burning a regular meeting slot or expecting poster authors to 
hang around all day waiting for interested parties to surface ... if this 
goes forward, that's what I would suggest.

Thanks,

Spencer

> On Jan 10, 2011, at 8:57 AM, Yoav Nir wrote:
>
>>
>> On Jan 10, 2011, at 1:09 PM, Henk Uijterwaal wrote:
>>
>>>
>>> The costs for a poster session are almost 0.  Isn't this something we
>>> can just try?
>>
>> I don't agree that the costs are zero. You can't have the poster session 
>> last all week long, because the presenter may want to go to other 
>> sessions. So we need about 2 hours reserved for this. Maybe a morning 
>> session.
>
> What I would suggest (if this goes forward) is
>
> - some space is set aside, ideally in or near the break area / room
>
> - posters SHOULD be put up in the AM, starting at breakfast.
>
> - the last refreshment break of the day, the authors are supposed to be at 
> their posters. (They can be at other times, but they SHOULD be at this 
> time.)
>
> People could then read posters at any time during the day, come back at 
> the break and ask questions, raise issues, etc.
>
> ADs could also quickly judge the interest in a poster, by how many people 
> are haranguing the author.
>
> As the "session" would last one full day, different days could accommodate 
> different areas.
>
> Regards
> Marshall
>
>>
>> But then scheduling a WG meeting at the same time is like scheduling a TV 
>> series episode opposite the superbowl (substitute your country's favorite 
>> sport finals here). And all the ADs would want to go to the poster 
>> session, because that's where the action is. So this reduces the amount 
>> of time slots that we have in an IETF week.
>>
>> Also, this puts another constraint on choosing a venue.  You need an area 
>> with room for lots of people, and space to put the "booths" or "desks" 
>> all around. For example, Anaheim did not have a good area to hold a 
>> poster session. Maastricht did. No idea about Beijing.
>>
>> It may be a cost we agree to bear, but it is not zero.
>>
>> _______________________________________________
>> 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 richard@shockey.us  Mon Jan 10 13:36:29 2011
Return-Path: <richard@shockey.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 AA0653A6833 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.271
X-Spam-Level: 
X-Spam-Status: No, score=-100.271 tagged_above=-999 required=5 tests=[AWL=-0.421, BAYES_40=-0.185, HTML_MESSAGE=0.001, 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 Wm6joZRQO3Yt for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:36:26 -0800 (PST)
Received: from oproxy2-pub.bluehost.com (oproxy2-pub.bluehost.com [67.222.39.60]) by core3.amsl.com (Postfix) with SMTP id 693753A67DA for <ietf@ietf.org>; Mon, 10 Jan 2011 13:36:26 -0800 (PST)
Received: (qmail 31820 invoked by uid 0); 10 Jan 2011 21:38:41 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy2.bluehost.com with SMTP; 10 Jan 2011 21:38:41 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=AMOvd7toXjUtgClT+LBdJnvqx1E7sgcCY9VxFsaZFpclyzUhIiQUEHNBoM3zK3Km3pvsqAqlLMpx3Vwkxn+uE7lVGJ62kkSYan2zClOp+/CiPo0tGzb5swqjtvkHiycA;
Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1PcPRo-0002mr-SV for ietf@ietf.org; Mon, 10 Jan 2011 14:38:41 -0700
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
Subject: It is my understanding that there may some major revisions to the XML2RFC tools forthcoming
Date: Mon, 10 Jan 2011 16:38:39 -0500
Message-ID: <025201cbb10e$befd7050$3cf850f0$@us>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0253_01CBB0E4.D6276850"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuxDr5TCmWXoBAES4OtTWbNeSseKg==
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.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, 10 Jan 2011 21:36:29 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0253_01CBB0E4.D6276850
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 

May I make a minor suggestion. I know its not spring and the daffodils are
not in bloom but it might be nice if a possible output file for the XML2RFC
tools were in .epub as well as .pdf

 

Thank you for your attention. No need to flame. 

 

We will now return you to your regularly schedule program.

Richard Shockey
Shockey Consulting
Chairman of the Board of Directors SIP Forum
PSTN Mobile: +1 703.593.2683
< <mailto:richard(at)shockey.us> mailto:richard(at)shockey.us>
skype-linkedin-facebook: rshockey101
http//www.sipforum.org

 


------=_NextPart_000_0253_01CBB0E4.D6276850
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;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</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=3DSection1>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>May I make a minor suggestion&#8230; I know its not =
spring
and the daffodils are not in bloom but it might be nice if a possible =
output
file for the XML2RFC tools were in .epub as well as .pdf<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thank you for your attention. No need to flame. =
<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>We will now return you to your regularly schedule =
program.<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style=3D'font-size:10.0pt;font-family:"Times New Roman","serif"'>Richard =
Shockey<br>
Shockey Consulting<br>
Chairman of the Board of Directors SIP Forum<br>
PSTN Mobile: +1 703.593.2683<br>
&lt;<a href=3D"mailto:richard(at)shockey.us"><span =
style=3D'color:blue'>mailto:richard(at)shockey.us</span></a>&gt;<br>
skype-linkedin-facebook: rshockey101<br>
http//www.sipforum.org</span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0253_01CBB0E4.D6276850--


From tme@americafree.tv  Mon Jan 10 13:46:30 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 4EED33A6804 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.231
X-Spam-Level: 
X-Spam-Status: No, score=-102.231 tagged_above=-999 required=5 tests=[AWL=0.368, 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 aiJ9CLeGkQkC for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 13:46:29 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id EF54D3A6841 for <ietf@ietf.org>; Mon, 10 Jan 2011 13:46:28 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id D8DAD99F6A5D; Mon, 10 Jan 2011 16:48:42 -0500 (EST)
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <4D2B1DE3.7090005@ripe.net>
Date: Mon, 10 Jan 2011 16:48:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E85650C6-4356-498D-8DD9-247691EB6ECC@americafree.tv>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net> <EF3F8097-F6F2-4948-9151-EE240CF3CBD6@checkpoint.com> <4D2B1DE3.7090005@ripe.net>
To: Henk Uijterwaal <henk@ripe.net>
X-Mailer: Apple Mail (2.1081)
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: Mon, 10 Jan 2011 21:46:30 -0000

On Jan 10, 2011, at 9:55 AM, Henk Uijterwaal wrote:

> On 10/01/2011 14:57, Yoav Nir wrote:
>>=20
>> On Jan 10, 2011, at 1:09 PM, Henk Uijterwaal wrote:
>=20
>>> The costs for a poster session are almost 0.  Isn't this something =
we can
>>> just try?
>>=20
>> I don't agree that the costs are zero. You can't have the poster =
session last
>> all week long, because the presenter may want to go to other =
sessions. So we
>> need about 2 hours reserved for this. Maybe a morning session.
>=20
> My idea would be that the pinboards for the posters are available from =
day one
> onwards and people with a poster can put it up on Sunday.  Folks can =
come and
> watch.  Select 2 or 3 coffee breaks where the person presenting the =
poster
> must be near his poster for questions and discussion.

There are places where we wouldn't be able to do that in the break room =
/ area (i.e., we would have to=20
dedicate a room to posters, merely to keep them from being removed at =
night). That seems like too much process to me.=20

My feeling is that one day for a poster session is enough (possibly with =
different sessions on different days). You can buzz through a set of =
uninteresting posters amazingly fast.

Regards
Marshall


>=20
>> Also, this puts another constraint on choosing a venue.  You need an =
area
>> with room for lots of people, and space to put the "booths" or =
"desks" all
>> around. For example, Anaheim did not have a good area to hold a =
poster
>> session. Maastricht did. No idea about Beijing.
>=20
> As far as I remember Anaheim: it did have a few hallways between =
meeting
> rooms and coffee pot.  Sounds like an ideal place for a poster =
session.
> Beijing had the same options.
>=20
> Henk
>=20
>=20
> --=20
> =
--------------------------------------------------------------------------=
----
> Henk Uijterwaal                           Email: =
henk.uijterwaal(at)ripe.net
> RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
> P.O.Box 10096          Singel 258         Phone: +31.20.5354414
> 1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
> The Netherlands        The Netherlands    Mobile: +31.6.55861746
> =
--------------------------------------------------------------------------=
----
>=20
> I confirm today what I denied yesterday.            Anonymous =
Politician.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From dyork@voxeo.com  Mon Jan 10 14:22:20 2011
Return-Path: <dyork@voxeo.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 4E3863A63C9 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 14:22:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.202
X-Spam-Level: 
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 2tUJPKniB3jP for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 14:22:19 -0800 (PST)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with ESMTP id DF9DB3A65A5 for <ietf@ietf.org>; Mon, 10 Jan 2011 14:22:18 -0800 (PST)
Received: from [166.137.136.241] (account dyork@voxeo.com HELO [10.49.80.188]) by voxeo.com (CommuniGate Pro SMTP 5.3.8) with ESMTPA id 78837698; Mon, 10 Jan 2011 22:24:32 +0000
References: <025201cbb10e$befd7050$3cf850f0$@us>
In-Reply-To: <025201cbb10e$befd7050$3cf850f0$@us>
Mime-Version: 1.0 (iPhone Mail 8B117)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-3-710946721
Message-Id: <D28B5BD1-012F-4690-95D4-C834CCCDDAE1@voxeo.com>
X-Mailer: iPhone Mail (8B117)
From: Dan York <dyork@voxeo.com>
Subject: Re: It is my understanding that there may some major revisions to the XML2RFC tools forthcoming
Date: Mon, 10 Jan 2011 17:23:59 -0500
To: Richard Shockey <richard@shockey.us>
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: Mon, 10 Jan 2011 22:22:20 -0000

--Apple-Mail-3-710946721
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+1  It would be great to support an open format that would be viewable in a w=
ide number of ebook readers.=20

--
Dan York, Dir. of Conversations, Voxeo
http://Voxeo.com http://blogs.voxeo.com
http://danyork.com http://twitter.com/danyork


On Jan 10, 2011, at 4:38 PM, "Richard Shockey" <richard@shockey.us> wrote:

> =20
>=20
> May I make a minor suggestion=E2=80=A6 I know its not spring and the daffo=
dils are not in bloom but it might be nice if a possible output file for the=
 XML2RFC tools were in .epub as well as .pdf
>=20
> =20
>=20
> Thank you for your attention. No need to flame.
>=20
> =20
>=20
> We will now return you to your regularly schedule program.
>=20
> Richard Shockey
> Shockey Consulting
> Chairman of the Board of Directors SIP Forum
> PSTN Mobile: +1 703.593.2683
> <mailto:richard(at)shockey.us>
> skype-linkedin-facebook: rshockey101
> http//www.sipforum.org
>=20
> =20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

--Apple-Mail-3-710946721
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=utf-8

<html><body bgcolor="#FFFFFF"><div>+1 &nbsp;It would be great to support an open format that would be viewable in a wide number of ebook readers.&nbsp;<br><br>--<div>Dan York, Dir. of Conversations, Voxeo</div><div><a href="http://Voxeo.com">http://Voxeo.com</a> <a href="http://blogs.voxeo.com"><a href="http://blogs.voxeo.com">http://blogs.voxeo.com</a></a></div><div><a href="http://danyork.com">http://danyork.com</a>&nbsp;<span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "><a href="http://twitter.com/danyork">http://twitter.com/danyork</a></span></div><div><br></div></div><div><br>On Jan 10, 2011, at 4:38 PM, "Richard Shockey" &lt;<a href="mailto:richard@shockey.us">richard@shockey.us</a>&gt; wrote:<br><br></div><div></div><blockquote type="cite"><div>

<div class="Section1">

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">May I make a minor suggestion… I know its not spring
and the daffodils are not in bloom but it might be nice if a possible output
file for the XML2RFC tools were in .epub as well as .pdf<o:p></o:p></p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">Thank you for your attention. No need to flame. <o:p></o:p></p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

<p class="MsoNormal">We will now return you to your regularly schedule program.<o:p></o:p></p>

<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-size:10.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;">Richard Shockey<br>
Shockey Consulting<br>
Chairman of the Board of Directors SIP Forum<br>
PSTN Mobile: +1 703.593.2683<br>
&lt;<a href="mailto:richard(at)shockey.us"><span style="color:blue">mailto:richard(at)shockey.us</span></a>&gt;<br>
skype-linkedin-facebook: rshockey101<br>
http//www.sipforum.org</span><span style="font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;"><o:p></o:p></span></p>

<p class="MsoNormal"><o:p>&nbsp;</o:p></p>

</div>




</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Ietf mailing list</span><br><span><a href="mailto:Ietf@ietf.org">Ietf@ietf.org</a></span><br><span><a href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a></span><br></div></blockquote></body></html>
--Apple-Mail-3-710946721--

From fred@cisco.com  Mon Jan 10 14:36:27 2011
Return-Path: <fred@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 E683B3A67A8 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 14:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
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 dnjdVLfGyfDz for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 14:36:25 -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 B07A03A63D3 for <ietf@ietf.org>; Mon, 10 Jan 2011 14:36:24 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: a.csv.pdf : 325670
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 10 Jan 2011 22:38:39 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0AMcECC003851 for <ietf@ietf.org>; Mon, 10 Jan 2011 22:38:19 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Mon, 10 Jan 2011 14:38:19 -0800
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Mon, 10 Jan 2011 14:38:19 -0800
From: Fred Baker <fred@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Poster sessions
Date: Mon, 10 Jan 2011 14:38:04 -0800
In-Reply-To: <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv>
To: IETF list <ietf@ietf.org>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv>
Message-Id: <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
X-Mailer: Apple Mail (2.1082)
Content-Type: multipart/mixed; boundary=Apple-Mail-194-711788497
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, 10 Jan 2011 22:36:28 -0000

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


On Jan 10, 2011, at 5:56 AM, Marshall Eubanks wrote:

> You can go, read the poster and formulate opinions and questions =
independently of anyone else, including the author. If there is a time =
when the author is supposed to be present, you can then go back and =
clarify any issues. You can't establish any consensus this way, but it =
can be efficient at resolving issues.

I'm attaching a chart that may be useful in this discussion. Using the =
rsync-able directory of all IETF ID's since 1992 (btw, I don't believe =
the database before about 1996, but 14 years is still interesting data), =
I did a brief scan of the arrival of drafts to the Internet Draft =
directory. The blue line shows the arrivals by month; the red bar graph =
tries (somewhat crudely) to aggregate drafts-by-IETF-meeting.

I'm envisioning the process and requirements of the poster sessions. In =
terms of process, today if I post a -00 draft to a working group, I can =
generally get discussion during the coming IETF meeting. What I think =
this suggests is that instead I would show a poster at the coming =
meeting and get working group discussion the meeting following. I'm not =
sure I like that implication.

I'm also thinking about the implications of 500-or-so posters. In terms =
of simple floor space, if we presume a poster and the conversation in =
front of it occupy a 3 meter-by 3 meter (10' X 10') space, we need 4500 =
square meters or 50,000 square feet of floor space to park them in. =
Time-wise, we need to assume that 1/3-to-1/2 of people who attend an =
IETF meeting will, instead of chairing or presenting in sessions, be out =
standing by their posters - and not wandering around looking at other =
posters. The mechanics look a little daunting.

Personally, call me stuck-in-the-mud, but this isn't an academic =
conference in which grad students are advertising for a professor that =
might be interested in mentoring them or a sponsor might fund their =
research. This is an SDO, and internet drafts are what any other SDO =
calls "contributions" or "work in progress". I would far rather have =
people who ant to talk about something contribute an internet draft on =
their topic, and talk with other people about their ideas - whether on =
working group lists or other places. For those of us that *do* =
participate, it seems to mostly work.


--Apple-Mail-194-711788497
Content-Disposition: inline;
	filename=a.csv.pdf
Content-Type: application/pdf;
	name="a.csv.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjMKJcTl8uXrp/Og0MTGCjQgMCBvYmoKPDwgL0xlbmd0aCA1IDAgUiAvRmlsdGVyIC9G
bGF0ZURlY29kZSA+PgpzdHJlYW0KeAHNnVuPHTdyx9/Pp2hFXlvyxsfdvPQll02yTgJknxJYwD5E
eQgMLxxDk8R2gv36+f3ZJJtk94yO5vRgYwHW6D91imSxqlhVvJyfun/pfuq86yZz7flv7sbZdW6c
u5+/737f/Wf39Te/DN13v3RD+PPLd6Kd++tofL904+T1U+f8crWTv/CZP3yZOIrKBY6iWmnGR9nO
/urmfp66wS3X3ruxG+1wHZwznZ2m6+L8p7BfPL36I13+cR3AN992/RXMLb3Zfrps2LffIIY+iGCa
J9cPY9fz56sayp30ZhItknnovvLDfF2Wabi4YXBmMd0DEhq8t0OXkA8bVWedmV1FlZCC6mImZ8aK
KiEFVWd6P841VUQKqstgp6GvqBJSUDHx3iwDM7V1P0MF3eUr3zMfyzgUhBv2ofsWBZBSSViO6Zyv
1iApTSd9sNN8nUxQgwva9c/f//zd9//9P//77x+6n/+DD03XOQjejlc7dsMwiHhw9jojUkn76396
GLq//68b2pA2Bg1+rI2JjnWDMVcmu2nCNE1cwoQ7RjwNfGzs4r8/pH/nYX5ox/2h+6EbGE5v3ByU
e5wWf3kAQ4UmYzPWfaixYATCis9G7Ifu919im09J+InRY9zS7XX41hxI2DbDp49Hs/hEG2UTzN5e
wu6kJhbcRjd4i942c+hPasEMQRVHd+2lzpUqjne3ESfDTdeJEUxuP47p7jbWycCvYn8DSrMfx3xS
G55lYpEnbwW13N1AFJQfrw63h03sJmPo725kldRgWLo6M9DUbiDDWd5nGKzGYMwYpqXWq6F1QM+1
QBkukjM4G/nTppWz7Fw+Cl9q0GKpWNPKWaY+GCf2xuOL9mM5y9yHwV9pZJxZidqRnGbuxhIy0MpE
3LQfymbxl6dcfI6lHlvgjB+uhsmfl2Isl7iI3mjyH21kQFKoq+37q9lMMrVyo90/0Uq0+2FmuZw7
O/T7sZgbDf+JVlbDl8kTb1hc/n4s5kbL/3grvbsSZFsCIgaXdCxKzNxo+R9vBWth8oktNT1tKzda
/hOtxHkxy0iY31lvjgZzo+k/0UycGAxlGTs7EkrsB3Oj6X+0FYsvZiiTvfrNKNO83Gj7TzQSJWat
JxXp7OyOxrLZ/pPh3RPNRInNYV2xizsazFnGb51T3OJ6v9Ow0ywfaySPQma7ObGn2T1uFj9MxtUO
gxzupmTjo/Nh+1nLvWOlDFnRGkZG5WLtPKmVgWTcjWRLu4GcZ/F+Teeno4GcZvA+BMRuJCHcj+Us
gzdLH9SXnFSpYIxb0qScZvGG9QQf6WZiiv1gTrN4oi9sxC3EFPvBnGXxZraERxR/Qr7SSOx+m0/u
fpRv9MThu5G4+40+L11h9r0NfzWz784yfEWSBC7eEVO0KkZx6xy7N6zyaJgn4OOvdijnmT7VAsJW
P5qDsZxm+khKAqMieTCW00x/CJUDjzrTWCuxE02fGiPlooUCxX5izjP9kKqOBJYHgznN9E2I9MeB
kGKvyqfZPhkrC+WoZG+3HPvzjH8Kof64BmPN/FPGOMkuKYyz3I/OHw3mNOtfXcwYaiPtUM4z/nGR
Do8jgeV+Ys6yfmvWVqj57+zFn2X82D5rwEhKSR7WCqywfdUC+sku0IRNCaJcdHPC/3Xq5uKJfQ+r
zJcbNhM25iqJ+96G8va3PwzdLz/E8vZgCHvdoj7GTZHcvrZg3OKdebQIW29dHOxmVNxDVVqlgW9/
MEUHiCV9z55J3QE3ezZLYgfukEDJXR2IErBFB9DpBYE3HQgzwAQs4x3Dz6xZNSdJch2+K1on/HSq
ae7ELx84TURzz5/+xJucdrSUG9bWfdG69r3MqNSqnX0tkdb1yx2jz8yJgft5nuLox6J94lV2wrL2
MwlJ+4n7hsVOyx3Dz8wXggk3J+2fivYX4uVpWndIws7H1j61jcmO9yh/Zs7SbM2cZn/e2jcEudQ1
FB2U8pfyA4wT23jPH//GnI5M7O3F+V+K9nFTMz07aF/F48XYsCV6uMf1UeM3ibkhmFumeYjzTxE9
ux9DZGx7mxWwcH8DFXg7uukOASTmhnzSDYSVqwFQYN864AjN0bJ6AmT8AxawLGykHdrfLXu5JvLW
nifKlcdfeL9QP/UhXS8VILSP//fzYO8Yv4qzYm5w/4QhSxp/4f3MqP3PpdVA7Y4PbDobZ+8Yf+Jt
cEQGH5sUoPB/hhicLeadBap96hmeDtwhgMTckOv7ac4CKFwg2s9K3RenAoILkAkacpFhHO/RgMTc
zkyFGbIKFD7Q4B0Gz153rYKhA9S+/HyXCSTmVukB/0sqUDhB7I9fUdapOxBUgBmknjQ9Xwcyc5XV
3TIkJzgUXtCy1GHtOyOUDnDEw9o7nGDmrajPzvOYBFB4QZZGxBzK8ZUR0r6h1z2qe4cAEnPsj1UQ
e4ohUOEFVa/t0c+jGcB3D364RwKJuaV6w7ZmFAAlz+wELcmDt6GksxcAlqO1+9leMDO3hPWjs0kD
2IbYOkCgxDke5nu3DmprabEsUYcduCUKtom505bYYqYkgcINqm9upiJz0AGK9abv7wgDM3PHSRDW
oiyBwg9aksXFb3F4WgjRQatcwpIiPF8CiTmnrnB2uLaog4UftKQqzrpshGUHyMrnwdwjgcTcERPO
xDXJCAo/aBdi0YEcpZ4CuSGDFyCauCMTysw5PUVcR1UsSqDwg471xs4+rwSlBNjcXpbhjrUwM3fa
ZXR+ThIo/KBjwZ3HsPsUzLDsAC7SYMDP14HM3JENYFRpJTCFI5RwLNqapqDogEIITzj0fD+QmTtO
to2EJVECbLFkP+As8ehOAFoKbc8COtG1ZxtB4u28lhRiwFUD2H7ZmudXhrN5B+PX5opZ/B02oHYD
c0cwYn2fYgHc7taBUYXiXT4QbICi1dLjoZ4vgMQ8GIPPS6Et/KCbELMlVYpGWGoA0WQ/2vkODUjM
ObN5JbpMSyHr+yYBAqWJg2upA+hiyAiDFyAjwQrvkEBi7iw1Wc9+XNSBwg9ybvI6zLRy4IYwwplf
3SGBxFzbzAuRVbKBwg/6noB0ZLwHHSChmBUsP1sHMnOrExueuD9KoPCDnsyPgKNuPoSjLCPO9Xek
xJG1o+hEzUkL8YVqkC18oDcEowMngA8UkOqgM3iHw9F3P3HWVueLnzhcm5nLGVJkS5EAa2tWQG+p
cC+hxr2LhajkSwGfP/+ZeVLAOP/sOG0dUNA/hgS0XQWUrFlDoHoogVtiIdzuytwR2BJzpIwIv7J1
gGwZR3OogMSSi7vDCfrEm4VWs5VSQhbkrf2RaHSYDi2Q4xNGlYznCyAx5zA57jjFAWSZW/v8hjAR
11cFo8EJoxwc4bjHAhJznCzRRp/iALL0rQMcrND5+Lr9YIGDztISJT5//JG3VW4+o/ir/bvCA3rO
2+Cb8hpQumBcw8w57zssIDGntEaww3ISO1B4wJHT31hoXgPKRYgAYaKm8XwBZOYkg0ggjb/wfyPn
r+cFjazlH+Y/nNSlknUo/1tqQpm5nciH0eU0/sIHEgBQ+Qo7IDsXRFGKhOoRH3iLB8jMLVVZy6WC
JIHCBzItbFtkAyjljw/mXP49Aoi8qcdducKQxs+2W9b/EbvjQH9eA0oFDIfAqBceTsBN40/MqTtf
J+oycfzU4LcOkKqzV9DmQsECowu+QwMS8+SCowYwqVsHUA4z7QLhoIIqprIM3iGBxJyrIzi6MWkA
ccXWATKuiaMxyQYKFWABomZ+T2GYctvKXNHmYpILwKq39imZGgpmqf1CBXCBC3XRewSQmSPLfsgF
ATb/cgfiHaTd7aI077dd/9kuAnXPvP4j5dAVITtydYZOuYkIhOjkAdYLhSt+od+biRoR+zjb3Zg/
1QAM9XztpqX7SxrAwHnqXgnH1ntyEBbf9G/uoGSSfMMpksR/bySXdJnpoVtJ0r83Eire6W7TSpL+
XZKs15i4JxNJ8rWm3Jd0hymRpH8XXPL9pUhzyUBBtN1dSpw25E8/Y7pMUV6La1UO7RvIPKmCFtex
0L55WibK1v9PB5CuzFFC1kYW4Vxxj44pZ8jopG5EEdHrJEhJmLBLQcePE+Wzii5jBR1JlZOPKvkl
rOQ30QXtD5d0GSv4sURPXEwrhrEiJa9hWCbCgpIoQQWnwS7jwiZIwSpCFS/iP8qNFVWESl7TMpqJ
9WGT7rBCFS/2zxZ58YIqQgUvSnveaxN6o4pQyctYfC43QkuqCJW8qKHO2k4qeK1QxWtanEOfS6oI
lbzIAojXKqoVKnlRnuWGTTXGBBW8qN9iRNUYI1Tx8gu5bzVGtg0CVPKaFma3GiMb5YIqXlonVEjZ
JEG4F6CCF2FY7wiCCqoIlbyonbFOVr1PUMnLz3iEqvcUOgVVvNiHc2xrli1GqOSForIlUlGtUMkL
I58b40hQwcsT6jfWEaGKl8ehLX3Zoo9QyYvyQmMdbNwIqnjhK6iYVrwiVPAah5n7t5XsI1TyIhjn
2BXB8DaPCSp5sU/I0lNRrVDFa2IDiopvyStCJa+FxFCHIooWV6jkNfHrxjoSVPAiwiZhrsYYoYoX
22+NdUwRKnkRMjTWwQEZQRWvZcZ7VL3HrQao4HXLFeIU6xEh9n246/275r43nWZbYiAWo5w1DJzV
IrK14b9bAz7OCC49RWjL2jKz1RhWX93cWEj0dX2rn8mEiBvYyaRoGW50BejDHnrQ0TliapaL+MHL
hx0Er4F75cvGnDWwBnR12KLAiUu4NyyAO+OpP8PoJ7qNlrNjMIuiBuChIkrVSgUQeLHBju0UrTQA
FCxF7ExvrTQAFAvrrc0d+xCBzDRITnvorFaMwNBTRFkCUIyechCXC61jlMisBiR9+R5b9KMBHrh2
wcez3GllBXLHoBg9iQsLfhIiNC0E1cICVsqkBpAat/7ZSC+4NAAUI9sLZTsNAMUye7dN54cIZKZo
Ehm4ZBInHD2qAemaH6lV53aCrtUQkuME3cA5HFElTdlB3HlnQ4asftPaGoDPREl81AysCsi1+BqA
YpmHIJfUzgowAyvAowOWsmLuL3PUAFCQZlW6UgNIn/WMQzv0I2lTAzx0CwkQJ4q2njYAFGyD95K+
Q3d7+rECfGQFoCA9CvIYnI4AQlEDsmHLnVgJhIIwZUQZcYUEOx+dtjK4IEDCPsKGYxYVIj4L7ztI
9LGpS4tAwww63hFANOxeq8MtIhqOlwTBcNJobWtFGOaKiGaZSPlk1ZyGdIFPjUBjOCnCcZyizzXC
HLAX7bzEwyURohfxaRDRLFi1piEJuUUeeLWCO6UUOTifxEmzMK4GgQ9Cxm4rmhoRDW9zGJzQaBBC
kPOK8KkVgYYpHyWfjaZBRMMvqULwP1yl05zWiObUseCwQceaNPC4g8beINBQK5iokHDWQOtT9+HS
IqLBoCUfuE0sXPBpENFQHQryCf0JNAFhpCsCzWhZtegzCfdEDQs+DSKa0eCnuVRv2HleaSpEc8pZ
51lLztj7fgxz0SDQsCSiXNDoOEKgaRDmVPun2sDEG0yrjjWI+GBwQT70bF28GgQaIpLFLowUx772
eUVofUVEMw5Uyhk7BkIhhrE3iGgo27CZYbgExLKuOa0RzSlFMMo6/MYRMAe7aBDR8AyO5OMn3qJA
hpcWEc2C9JCP56GV1S4ahPVSsyX9YSuQhIo+R+SSENGwBadFiGwBToGmRkSDtWtp5oKmC/beIMwp
m3Uzrq6Y0xYRzWi02bPNe4s8XJQNsmjQVo99yt5bBD7U0ict0ZgMEYloGkQ0nK6wAyNlTQq6ERGk
sSKiYWNSYYtPutEi0Og0r+SDIjFA5rRBmFNDcDxLPhyh19Eq0dSIaPhdkE+0wUuLQMNxCR38SBYH
nwYRzUgBh+Bfsxb0JyKXhIiGlFenazD2nohSfGoEGhRsURCD52SAoqkRzSlHFXmMqfCrLSKaBacb
+pz51AhziqvTZr4nql3mtdMtBKcRhdaSnS2sRcRpcVyZgGYeRrYt6XWDwIfQz0tCnD0ixBNNg4iG
jY0eL87SxBIUaALCeFZENMhHq9OmHQ0CzawglZlnre1dL+2oEWnHPPIAlLwUN6pWjW4Q0SzsAjEb
6DzvRWHxLQINx9mwBcaeVuYWEQ17XshHKq89BfqzIqx/KyIaGGl1YlqG4FlbhBi455davfNcNAja
YXsiS8mHgoQP42oR0SxkSMwFE6bEinC7QR4uFv/O7iByjt6OU3A1Ah86SlWF/qh+KW1tEdFwhp0z
3BxkJ5yVbkSEHq4INBQHoWLs1DjW/jSIaFBp5MNKrys5zGmDMKck1iy7kk/uT4NAQzLM41ayfKr3
mtMWEQ3uW6sTPWam1OcGEc1iGLyevCKgIroWUYAuGYKKgxZe6zcuw4b1oEVE4xdcOT3SA15BijWi
WWUBHIOElHmEHjUINB7nioSkz3qkRT1qIHGipMK7ZcwrgVLQxRYRDW1oheKIEOFdYFQj6IcWQ2RE
V3W4PLTWQnAa8YeKcTZtbBBxUvkOGeV1o0XgQ8ivu0PR36tHDSIabutwPg4NYoBBRiuCH1gR0bDK
sIYTu+raeeh1C0HFUeSZt+joFkF/sI8VkXUGRDSs4UFGHFcLzrNFREPJUXpEmdkZ+aEGkc7KPFil
yOUIuq+ThtZCovKEUswIfpVynjjVSOCEGunQBudD9KqcaGqE3JYXykhnOyaBjmn8lx0kKk8hRDaS
VvsWEQ29Ro82/xkRRUXBo0LDWu+1UhFQErHRoxYRjZ+094Gv4hZKmJEWQmtVEUW5Cz1qEWgwMmJ8
5ojVOthRizxcMEfCaWZk4LRtsKMWER9VcheySBwEBxHU7RaCE7E7DqBsrUHgRMoXSjTZsltENDxX
6JeLTrytK35EFKUGBBqch8o0JKK4wKAjO0hUqgehtY4oJ1htRPCHKyIaljStVtTnmGMNrUGg8eQI
Ws3z6tkg6BovNY4q2JDMI8dVRi0kKoLqICOKEiFKaxBxwq2Fsk32tS0iGoJP6VHSx0uLiIaDgVrP
CSBwwxpZg0CjTL1czxPC6rSu8KKhr5JQXodbRDQhgYCGqnZYHxpEGjvT2xARkg+FaLhFRMMxM8ln
048GQc9mrkxovdr60yDwwYGG4g0zR1FGY28Q0TA/oyUP1XaAvGNElGMGRDTBYSFDjsqGrKxFqFuR
QYYSDqEQrh9P1CDMqeeulV49ZFwTDoe2WkQ0M4VjrefklNLES4tAM+Dvw3oeyoLi0yCi4RHOsJ5T
/QxeLyLM6YqIBpEpHmTCSB0DnxqBhl+qmjPgq0m5RVMjzKkeF+UuThFftIhoSADCak4tPsRELfJw
IXvkEVH5Dmrsa1sNAh9WqFDNYb0agz63iGhwCNNymZVprzFIhCiSRQgq3KCeaN3yxBYRjec0DnnZ
mk9p9CuSV1zRkOGwls/UfKKn3kFQERVQ0UH6efwrQvsrIhq4o4NYHTsYstUWEc1MiSHLSHpWI9Iz
BKPDI1wU5IKKHHWLiIZTxkQDLDOYYdCzBhENTozDEJs9twg0Ew4qxIRZh1aEKGFFRINkkRALMCls
WMt2kKhU7tHqmjV2RUqNpZBKMg1NWoGJ2ioEPuyyhppOji0bRBqL81BNB7OhvhYk1CDQKGpFQqzV
6EywjgZBY0mTsVfRxCi+RcSHSChIiAJtiCxbhFo0rpXlnbyHuQ+aHxH8wIqIhuIZtYFNPi0iGrL+
TT5oR4OgHWSOlHSCJ49RXIuIBquSfCjB9ooZLi0iGmJBvAZ+kghNnqFFoGFBJfEqZBgR5nSVqmjw
FsrJiTzhJD4NIhrKVyHOidlJizCnpBcUz9iOxKCpXotPg4iGLYkgnzSnLfJAmkKSwwqV7FJ8agQ+
OgWqmgUJNGquthpENHhKLpXBJ2acERHngIiGaz2ST85cWwQaygyhpkMviCA1pzWiOcW9hJpO9oot
IpqZpZZtZKIg0knNaYNAwxSGmg5hubwDbTWIaFg3gnySl4oII10R0bCLI/nkFbNFoMG3EEkWq0aD
aE55GwKnCk3uT4OIhuKkMvKclbQIcyqvrwhnjd00rgaBD5OsPQSWIJL/MKcNIhq8vLansoeOCHOa
x054qorOFktTK6kQ+DD/LMvQDKhQmNMa0ZzquA79YNmggCj/0yLsLPWKogr5XFpENOTskk/K7HeI
aNikRz55eWQXa4W2RRQqVIc1U5KOtZgWEY3intBauBCgV6IrhFll4gmSVUdIa0aLQMOSq5rOQNTA
gsLoW+ThQqpLdoSE2EzQ0+2iqRHxYRNWEiLRkncQTY1AQ3mGIkUxqxEpZpVSJxVVPGKuhLeI+LCf
x/rNy+0USDSrDcKsshSQhEpbU02nRUSDkkk+pOdU0bDUFhGNjkLoGXomY83GdhBUqLR8oYERmZk4
NYhoFFCF2RjokyTUIKKZWXHR17xHFJFQLdWYoaHEGWo6xUZojYiGbF4RTkFTIdIOSiyhplPQ1Ag0
KBXDLvk0CNrB/hpUFU2NiA8FUMlna6tBoKF4qwvyBc2K5E+JhvKD5LPxaRDR4HK0fq800o4akQzp
Md4n0WguGkQ0BJxav1NblxYRDYaK5mSa/DL9Y6dvw6ltvUr/zS9cPfklvJLOyffvuDrAKRL+DJjt
lWgJE9BVGSJVnU//7bv4PQGme/cdrmolDQ/uDP3lHW/q/COf4sPv/tC9efVnb7t3P3b/8C4+8fNk
X9bvX0h9uTR94bB7uFKFjXBaX+fBP9aZLnXmsnbm9as7usMwJRpYraLZusP1OXbTwu2VJ2WTuxNl
85m6c3mmdGJ38kzl7hDs0J31dYdP6s6vbpZOOov0hOJs3dERIMKzj05Wqzmf39ydfPsg6TGa85ju
6LYfLjZctrxNOlF3vnh+d4LCHOuO6uW6JfhR6bS68/7NiygPu4M683WbZKIav3+7E42uyFPt8uGr
U8K1BZ2x1JEx4v0ntEcu5ysZmC5lBAasc1OPs4sC2rwNF6YsRW7IW5/zr92bL99y9s10b37952/l
q1z35qvwA9A1/uqz+Df+6d+6d7+LHopLO9wJ63dd54ouGd124TtpWp5afohd5/OUeIk+Ft5rocr2
lDy596qEjlsTDCw5q1WsGsXXdHro3vTrX19dP8NdFJ2Vn9Y3hrA3fCjonV0c9JZYlNcMYJAEHbt7
KOiDLj4laO7AIvBfHQpafafJcJCfyV6/OUdKcizpYNHRprOkxUC7XFnUT1lRKerG1RyJ+le1Xqi7
egSM/h6K+hadFgP2PrSKv5BOf34oanRal0jIJOuuH0s66MhO0lwTC3WR83X6871O860gFLnJTEq9
4MVXXQNNV+2eMEASefyMMj/Ug8Ma4RQrHu08lf7iUM7SEa4xqjxQd/1Y0McqrReaxSB5jxNV+oud
SrMZxZ27MiT7RDdNbs1hYxi8mEq/f3Mg64u+b0mvTJOwNmvMsawPlZpUlLd0YJBkfaKnfv9mp9ZU
gPRiwFTrxu1qrc9zQF8J0Aup9fu3B7IO323FeTHyAIqmlUkey/pQr8VgFIMk6xP1+v3bvWLr/LoO
d1b9XWV9i6umrMTNZhVroqxPDz+GQ1HjqqlU4P3IzauuH4v6WK31mIEYJFGfqNbDTqvD96DoCaOq
u7drtT5P1q609YW0OgV8OyVhg1j3Btfv98tB6rGkD5WaEhK3FWGQJH2iUl/33eX7UyhSNt39hJia
wz16O+wFnPWrqMzp77rvKDW2xCMKbP1WWnIs6kOlFgOOqxCmnh6BhDyqjqr1IA4nvJ7tqvV5qmYv
4KpfvV2D6teH7oNVUd83SJWw8XzHkj5WajJSKpq4vijp85T61etaMdRdfV8LNyQrvfgUnebb1/QG
0enxR1LlR9NEPZjA0crn+2kx4A2xl/DTr/aJouoe1I5bP71m5LdE1Zyo55UiGCRRn5YoJp1+NFHk
vCtvX3N4otKST9BpTgjxfjMMXkCn94minlTjkFgTmH6CUosBW6gEpmcnikmrH00UHe9LsuPzfEct
Bmwfvoij3qeK4StmuEBXa8bt0QcHvvT8HmHp2dFHUupHU0W2e3jrnuvVz1VqdhOpgsPgBZR6nyqy
S8prodzNrrr7CUotBmwg4e5eSqkfTxU52IDzY5+r6vyxAzkMPzg3g/ODQZL1eTH1q4NUMXyvDTuW
dX9vV2tOBvBsoM5/vpRaP54qsh3IS053RNViwP7vizjrg1RR34jDQcnWW4dq0y2poj4/6vNJ1qel
islZP5oqss3Lg/m8qvBstQ7fnQWDF1DrfaoYvkiH8+x1d2/Xao4j6emhLSk/PQJ5NFXkEiGvz98R
VYsBe9Mv4qz3qeL6/TvcnaoU4xOcNbeZefQv3CA/uVSdEpek3HVGQKpIRMx3TfDiZNX3T/DVXO+8
6t7lCyj1a+3X1qniyBvS7P02seknKLXeoNbnk/s4TalffyxVHPUcPwfub5H0YaooBly63wqo56WK
r/epIrVenmNuNzE+Qaknfb/JejrkhZT60WSRM088o8vhDNJVHSjl/BIvf3OagSuHFNA5E/XIY9qk
yB99SDYz5ygPVZb8iiOi+ugLck9kfumcAyfKyVPp+0DEqudz1v3hbTelP969NGnr1apWwRbsr51+
sN0bH37DxibWxO4sP4yJdoq0uIX1N/MSfuJTf5F++Mvwg9fHI9FfhWrI5c1fx0+nv3+TCPI28N/E
LtRuBymXmyCcQOT70DmWzcOXKQRArJxT/SN7s+c/u8JVnfXxR9ZzroDzrjci1vCJW3Hl+pErSDNH
ZPVuGIe69E4Dr1hQQZj4CoXb3zx74rwGt3GoG3GsOc7yLopJs3wpTvewcXrTLMdpamb50k5g9+Zv
0xznCfu73wYI9TmaMr5SRUeC9N1mvEY45ufAt9n6Uaebhu6bbxGYbihww+jwp9teRERLOOOqNsOD
6ciEuIDjddzB4S4AN42wbAJCx/FNWVZ41+f/APfFhGYKZW5kc3RyZWFtCmVuZG9iago1IDAgb2Jq
CjgxNjIKZW5kb2JqCjIgMCBvYmoKPDwgL1R5cGUgL1BhZ2UgL1BhcmVudCAzIDAgUiAvUmVzb3Vy
Y2VzIDYgMCBSIC9Db250ZW50cyA0IDAgUiAvTWVkaWFCb3ggWzAgMCA3OTIgNjEyXQo+PgplbmRv
YmoKNiAwIG9iago8PCAvUHJvY1NldCBbIC9QREYgL1RleHQgL0ltYWdlQiAvSW1hZ2VDIC9JbWFn
ZUkgXSAvQ29sb3JTcGFjZSA8PCAvQ3MyIDE3NSAwIFIKL0NzMSA3IDAgUiA+PiAvRm9udCA8PCAv
RjEuMSAxNzcgMCBSID4+IC9YT2JqZWN0IDw8IC9JbTUgMTYgMCBSIC9JbTQ3IDEwMCAwIFIKL0lt
NDUgOTYgMCBSIC9JbTIgMTAgMCBSIC9JbTIxIDQ4IDAgUiAvSW00MyA5MiAwIFIgL0ltMjIgNTAg
MCBSIC9JbTQ5IDEwNCAwIFIKL0ltMTAgMjYgMCBSIC9JbTEzIDMyIDAgUiAvSW01MyAxMTIgMCBS
IC9JbTMzIDcyIDAgUiAvSW04IDIyIDAgUiAvSW0yOSA2NCAwIFIKL0ltMTQgMzQgMCBSIC9JbTE4
IDQyIDAgUiAvSW0zNyA4MCAwIFIgL0ltNDEgODggMCBSIC9JbTE2IDM4IDAgUiAvSW0zNSA3NiAw
IFIKL0ltMjQgNTQgMCBSIC9JbTM4IDgyIDAgUiAvSW0xNyA0MCAwIFIgL0ltNTEgMTA4IDAgUiAv
SW0yNSA1NiAwIFIgL0ltNDQgOTQgMCBSCi9JbTQ4IDEwMiAwIFIgL0ltNTYgMTE4IDAgUiAvSW0z
IDEyIDAgUiAvSW0xOSA0NCAwIFIgL0ltMTIgMzAgMCBSIC9JbTYgMTggMCBSCi9JbTIwIDQ2IDAg
UiAvSW0yNyA2MCAwIFIgL0ltMTUgMzYgMCBSIC9JbTM0IDc0IDAgUiAvSW0xMSAyOCAwIFIgL0lt
NTIgMTEwIDAgUgovSW0xIDggMCBSIC9JbTU0IDExNCAwIFIgL0ltNDAgODYgMCBSIC9JbTQyIDkw
IDAgUiAvSW03IDIwIDAgUiAvSW01MCAxMDYgMCBSCi9JbTMxIDY4IDAgUiAvSW0zMiA3MCAwIFIg
L0ltMjggNjIgMCBSIC9JbTkgMjQgMCBSIC9JbTQgMTQgMCBSIC9JbTM5IDg0IDAgUgovSW0zNiA3
OCAwIFIgL0ltMjMgNTIgMCBSIC9JbTU1IDExNiAwIFIgL0ltMjYgNTggMCBSIC9JbTQ2IDk4IDAg
UiAvSW0zMCA2NiAwIFIKPj4gL1NoYWRpbmcgPDwgL1NoMjYgMTQ1IDAgUiAvU2g1MiAxNzEgMCBS
IC9TaDEyIDEzMSAwIFIgL1NoMTMgMTMyIDAgUiAvU2gyCjEyMSAwIFIgL1NoMjIgMTQxIDAgUiAv
U2gyOSAxNDggMCBSIC9TaDQ1IDE2NCAwIFIgL1NoNDMgMTYyIDAgUiAvU2gxNyAxMzYgMCBSCi9T
aDUwIDE2OSAwIFIgL1NoMSAxMjAgMCBSIC9TaDU1IDE3NCAwIFIgL1NoNDIgMTYxIDAgUiAvU2gx
NSAxMzQgMCBSIC9TaDQ5CjE2OCAwIFIgL1NoNDAgMTU5IDAgUiAvU2gzMiAxNTEgMCBSIC9TaDI0
IDE0MyAwIFIgL1NoMjcgMTQ2IDAgUiAvU2g5IDEyOCAwIFIKL1NoNTMgMTcyIDAgUiAvU2gyMCAx
MzkgMCBSIC9TaDcgMTI2IDAgUiAvU2gzNCAxNTMgMCBSIC9TaDM4IDE1NyAwIFIgL1NoMjMKMTQy
IDAgUiAvU2g0OCAxNjcgMCBSIC9TaDUgMTI0IDAgUiAvU2g0NiAxNjUgMCBSIC9TaDMwIDE0OSAw
IFIgL1NoNDQgMTYzIDAgUgovU2gxNCAxMzMgMCBSIC9TaDE5IDEzOCAwIFIgL1NoNTEgMTcwIDAg
UiAvU2gxOCAxMzcgMCBSIC9TaDExIDEzMCAwIFIgL1NoMTYKMTM1IDAgUiAvU2gzMyAxNTIgMCBS
IC9TaDM3IDE1NiAwIFIgL1NoMjUgMTQ0IDAgUiAvU2gzIDEyMiAwIFIgL1NoMTAgMTI5IDAgUgov
U2gyOCAxNDcgMCBSIC9TaDM2IDE1NSAwIFIgL1NoMjEgMTQwIDAgUiAvU2g4IDEyNyAwIFIgL1No
NCAxMjMgMCBSIC9TaDM1CjE1NCAwIFIgL1NoNiAxMjUgMCBSIC9TaDU0IDE3MyAwIFIgL1NoMzEg
MTUwIDAgUiAvU2g0NyAxNjYgMCBSIC9TaDM5IDE1OCAwIFIKL1NoNDEgMTYwIDAgUiAvU2g1NiAx
NzggMCBSID4+ID4+CmVuZG9iagoxNDUgMCBvYmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRp
bmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUyIDQxNzU5MjAgXSAvRG9tYWluClsgMCAxIF0g
L0V4dGVuZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAxNzkgMCBSID4+CmVuZG9iagoxNzEgMCBv
YmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTEuNSAw
IDY2NTEuNSAzMzE4Nzk0IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAv
RnVuY3Rpb24gMTgwIDAgUiA+PgplbmRvYmoKMTMxIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBS
IC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiAxODAzMzk0IF0gL0RvbWFpbgpb
IDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMTgxIDAgUiA+PgplbmRvYmoK
MTMyIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2
NjUyIDAgNjY1MiAxNjQ1NjgzIF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUg
XSAvRnVuY3Rpb24gMTgyIDAgUiA+PgplbmRvYmoKMTIxIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcg
MCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiA3OTM3IF0gL0RvbWFpbiBb
CjAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMTgzIDAgUiA+PgplbmRvYmoK
MTQxIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2
NjUyIDAgNjY1MiAyNzYzMzc2IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUg
XSAvRnVuY3Rpb24gMTg0IDAgUiA+PgplbmRvYmoKMTQ4IDAgb2JqCjw8IC9Db2xvclNwYWNlIDcg
MCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiAzOTkwNzgxIF0gL0RvbWFp
bgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMTg1IDAgUiA+PgplbmRv
YmoKMTY0IDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMg
WyA2NjUxLjUgMCA2NjUxLjUgMjcwMTY2MyBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1
ZSB0cnVlIF0gL0Z1bmN0aW9uIDE4NiAwIFIgPj4KZW5kb2JqCjE2MiAwIG9iago8PCAvQ29sb3JT
cGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMjg3MzA4OCBd
IC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDE4NyAwIFIg
Pj4KZW5kb2JqCjEzNiAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAv
Q29vcmRzIFsgNjY1MS41IDAgNjY1MS41IDMxMDYyMjYgXSAvRG9tYWluClsgMCAxIF0gL0V4dGVu
ZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAxODggMCBSID4+CmVuZG9iagoxNjkgMCBvYmoKPDwg
L0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUyIDM0
Mjg1MDYgXSAvRG9tYWluClsgMCAxIF0gL0V4dGVuZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAx
ODkgMCBSID4+CmVuZG9iagoxMjAgMCBvYmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdU
eXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUyIDM3NzEzNiBdIC9Eb21haW4KWyAwIDEgXSAvRXh0
ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDE5MCAwIFIgPj4KZW5kb2JqCjE3NCAwIG9iago8
PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIg
MTY0NTY4IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24g
MTkxIDAgUiA+PgplbmRvYmoKMTYxIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5n
VHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiAyOTk2NTE0IF0gL0RvbWFpbgpbIDAgMSBdIC9F
eHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMTkyIDAgUiA+PgplbmRvYmoKMTM0IDAgb2Jq
Cjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1
MiAxMzc4MjU5IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rp
b24gMTkzIDAgUiA+PgplbmRvYmoKMTY4IDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFk
aW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiAzMDY1MDg0IF0gL0RvbWFpbgpbIDAgMSBd
IC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMTk0IDAgUiA+PgplbmRvYmoKMTU5IDAg
b2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAg
NjY1MiAzNjA2Nzg4IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVu
Y3Rpb24gMTk1IDAgUiA+PgplbmRvYmoKMTUxIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9T
aGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiAzOTE1MzU0IF0gL0RvbWFpbgpbIDAg
MSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMTk2IDAgUiA+PgplbmRvYmoKMTQz
IDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUx
LjUgMCA2NjUxLjUgMzQ2OTY0OCBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVl
IF0gL0Z1bmN0aW9uIDE5NyAwIFIgPj4KZW5kb2JqCjE0NiAwIG9iago8PCAvQ29sb3JTcGFjZSA3
IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzU1ODc4OSBdIC9Eb21h
aW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDE5OCAwIFIgPj4KZW5k
b2JqCjEyOCAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRz
IFsgNjY1MS41IDAgNjY1MS41IDYzMDg0NSBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1
ZSB0cnVlIF0gL0Z1bmN0aW9uIDE5OSAwIFIgPj4KZW5kb2JqCjE3MiAwIG9iago8PCAvQ29sb3JT
cGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzMzOTM2NSBd
IC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIwMCAwIFIg
Pj4KZW5kb2JqCjEzOSAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAv
Q29vcmRzIFsgNjY1MiAwIDY2NTIgMjY2NzM3NyBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsg
dHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIwMSAwIFIgPj4KZW5kb2JqCjEyNiAwIG9iago8PCAvQ29s
b3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgNTQ4NTYx
IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMjAyIDAg
UiA+PgplbmRvYmoKMTUzIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAy
IC9Db29yZHMgWyA2NjUyIDAgNjY1MiAzMTg4NTEwIF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQg
WyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMjAzIDAgUiA+PgplbmRvYmoKMTU3IDAgb2JqCjw8IC9D
b2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUxLjUgMCA2NjUxLjUg
MzUxMDc5MCBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9u
IDIwNCAwIFIgPj4KZW5kb2JqCjE0MiAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGlu
Z1R5cGUgMiAvQ29vcmRzIFsgNjY1MS41IDAgNjY1MS41IDM2ODIyMTUgXSAvRG9tYWluClsgMCAx
IF0gL0V4dGVuZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAyMDUgMCBSID4+CmVuZG9iagoxNjcg
MCBvYmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTIg
MCA2NjUyIDI4MTEzNzUgXSAvRG9tYWluClsgMCAxIF0gL0V4dGVuZCBbIHRydWUgdHJ1ZSBdIC9G
dW5jdGlvbiAyMDYgMCBSID4+CmVuZG9iagoxMjQgMCBvYmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIg
L1NoYWRpbmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUyIDE4NTEzOSBdIC9Eb21haW4KWyAw
IDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIwNyAwIFIgPj4KZW5kb2JqCjE2
NSAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1
MiAwIDY2NTIgMjcxNTM3NyBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0g
L0Z1bmN0aW9uIDIwOCAwIFIgPj4KZW5kb2JqCjE0OSAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAg
UiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzUzODIxOCBdIC9Eb21haW4K
WyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIwOSAwIFIgPj4KZW5kb2Jq
CjE2MyAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsg
NjY1MiAwIDY2NTIgMjk3NTk0MyBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVl
IF0gL0Z1bmN0aW9uIDIxMCAwIFIgPj4KZW5kb2JqCjEzMyAwIG9iago8PCAvQ29sb3JTcGFjZSA3
IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMTUwMTY4NiBdIC9Eb21h
aW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIxMSAwIFIgPj4KZW5k
b2JqCjEzOCAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRz
IFsgNjY1MiAwIDY2NTIgMjI5MDI0MiBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0
cnVlIF0gL0Z1bmN0aW9uIDIxMiAwIFIgPj4KZW5kb2JqCjE3MCAwIG9iago8PCAvQ29sb3JTcGFj
ZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzIwOTA4MSBdIC9E
b21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIxMyAwIFIgPj4K
ZW5kb2JqCjEzNyAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29v
cmRzIFsgNjY1MiAwIDY2NTIgMjA1MDI0NiBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1
ZSB0cnVlIF0gL0Z1bmN0aW9uIDIxNCAwIFIgPj4KZW5kb2JqCjEzMCAwIG9iago8PCAvQ29sb3JT
cGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMTM1MDgzMSBd
IC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIxNSAwIFIg
Pj4KZW5kb2JqCjEzNSAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAv
Q29vcmRzIFsgNjY1MS41IDAgNjY1MS41IDI5NDg1MTUgXSAvRG9tYWluClsgMCAxIF0gL0V4dGVu
ZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAyMTYgMCBSID4+CmVuZG9iagoxNTIgMCBvYmoKPDwg
L0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUyIDMx
NjEwODIgXSAvRG9tYWluClsgMCAxIF0gL0V4dGVuZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAy
MTcgMCBSID4+CmVuZG9iagoxNTYgMCBvYmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdU
eXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUyIDMwNTgyMjcgXSAvRG9tYWluClsgMCAxIF0gL0V4
dGVuZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlvbiAyMTggMCBSID4+CmVuZG9iagoxNDQgMCBvYmoK
PDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRpbmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTIgMCA2NjUy
IDQwNTkzNTEgXSAvRG9tYWluClsgMCAxIF0gL0V4dGVuZCBbIHRydWUgdHJ1ZSBdIC9GdW5jdGlv
biAyMTkgMCBSID4+CmVuZG9iagoxMjIgMCBvYmoKPDwgL0NvbG9yU3BhY2UgNyAwIFIgL1NoYWRp
bmdUeXBlIDIgL0Nvb3JkcyBbIDY2NTEuNSAwIDY2NTEuNSA3OTM3IF0gL0RvbWFpbgpbIDAgMSBd
IC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMjIwIDAgUiA+PgplbmRvYmoKMTI5IDAg
b2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUxLjUg
MCA2NjUxLjUgMTQ0NjgyOSBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0g
L0Z1bmN0aW9uIDIyMSAwIFIgPj4KZW5kb2JqCjE0NyAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAg
UiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgNDI5MjQ4OSBdIC9Eb21haW4K
WyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIyMiAwIFIgPj4KZW5kb2Jq
CjE1NSAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsg
NjY1MiAwIDY2NTIgMjcyOTA5MSBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVl
IF0gL0Z1bmN0aW9uIDIyMyAwIFIgPj4KZW5kb2JqCjE0MCAwIG9iago8PCAvQ29sb3JTcGFjZSA3
IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMjUxNjUyMyBdIC9Eb21h
aW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIyNCAwIFIgPj4KZW5k
b2JqCjEyNyAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRz
IFsgNjY1MiAwIDY2NTIgNTYyMjc1IF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRy
dWUgXSAvRnVuY3Rpb24gMjI1IDAgUiA+PgplbmRvYmoKMTIzIDAgb2JqCjw8IC9Db2xvclNwYWNl
IDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUyIDAgNjY1MiAzNDI4NSBdIC9Eb21h
aW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIyNiAwIFIgPj4KZW5k
b2JqCjE1NCAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRz
IFsgNjY1MiAwIDY2NTIgMzYwNjc4OCBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0
cnVlIF0gL0Z1bmN0aW9uIDIyNyAwIFIgPj4KZW5kb2JqCjEyNSAwIG9iago8PCAvQ29sb3JTcGFj
ZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgNTIxMTMzIF0gL0Rv
bWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rpb24gMjI4IDAgUiA+Pgpl
bmRvYmoKMTczIDAgb2JqCjw8IC9Db2xvclNwYWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29y
ZHMgWyA2NjUyIDAgNjY1MiA0MTAwNDkzIF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVl
IHRydWUgXSAvRnVuY3Rpb24gMjI5IDAgUiA+PgplbmRvYmoKMTUwIDAgb2JqCjw8IC9Db2xvclNw
YWNlIDcgMCBSIC9TaGFkaW5nVHlwZSAyIC9Db29yZHMgWyA2NjUxLjUgMCA2NjUxLjUgMzgyNjIx
MiBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIzMCAw
IFIgPj4KZW5kb2JqCjE2NiAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUg
MiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzA0NDUxMyBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5k
IFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIzMSAwIFIgPj4KZW5kb2JqCjE1OCAwIG9iago8PCAv
Q29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzQy
MTY0OSBdIC9Eb21haW4KWyAwIDEgXSAvRXh0ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIz
MiAwIFIgPj4KZW5kb2JqCjE2MCAwIG9iago8PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5
cGUgMiAvQ29vcmRzIFsgNjY1MiAwIDY2NTIgMzMxODc5NCBdIC9Eb21haW4KWyAwIDEgXSAvRXh0
ZW5kIFsgdHJ1ZSB0cnVlIF0gL0Z1bmN0aW9uIDIzMyAwIFIgPj4KZW5kb2JqCjE3OCAwIG9iago8
PCAvQ29sb3JTcGFjZSA3IDAgUiAvU2hhZGluZ1R5cGUgMiAvQ29vcmRzIFsgMTIxOTIwIDAgMTIx
OTIwIDY5NzUyIF0gL0RvbWFpbgpbIDAgMSBdIC9FeHRlbmQgWyB0cnVlIHRydWUgXSAvRnVuY3Rp
b24gMjM0IDAgUiA+PgplbmRvYmoKMTYgMCBvYmoKPDwgL0xlbmd0aCAxNyAwIFIgL1R5cGUgL1hP
YmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDc5IC9JbnRlcnBvbGF0ZQp0
cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyMzUgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDgg
L0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dABDQAAAMKg909tDjeIQGHAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
wOXAADwtAAEKZW5kc3RyZWFtCmVuZG9iagoxNyAwIG9iago5MQplbmRvYmoKMTAwIDAgb2JqCjw8
IC9MZW5ndGggMTAxIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0
IC9IZWlnaHQgMTgzOCAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sg
MjM3IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVh
bQp4Ae3QAQ0AAADCoPdPbQ8HESgMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwICBt4EBYssAAQplbmRzdHJlYW0KZW5kb2JqCjEwMSAwIG9iagoxNTYy
CmVuZG9iago5NiAwIG9iago8PCAvTGVuZ3RoIDk3IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlw
ZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjAwOSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JT
cGFjZSA3IDAgUiAvU01hc2sgMjM5IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQsviEBhwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwauAwP6lgABCmVuZHN0cmVhbQplbmRv
YmoKOTcgMCBvYmoKMTczMgplbmRvYmoKMTAgMCBvYmoKPDwgL0xlbmd0aCAxMSAwIFIgL1R5cGUg
L1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDYxIC9JbnRlcnBvbGF0
ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNDEgMCBSIC9CaXRzUGVyQ29tcG9uZW50
IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dCBAAAAAMOg+VOf4AaFUGHAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBu7AAC53AAEKZW5k
c3RyZWFtCmVuZG9iagoxMSAwIG9iago3NgplbmRvYmoKNDggMCBvYmoKPDwgL0xlbmd0aCA0OSAw
IFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDE4MDYg
L0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI0MyAwIFIgL0JpdHNQ
ZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt0IEAAAAAw6D5
Ux/khVBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwICB
94EBX/UAAQplbmRzdHJlYW0KZW5kb2JqCjQ5IDAgb2JqCjE1NTgKZW5kb2JqCjkyIDAgb2JqCjw8
IC9MZW5ndGggOTMgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUg
L0hlaWdodCAyMDIyIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAy
NDUgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFt
CngB7dAxAQAAAMKg9U9tCF+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYeAcGBIwAAQplbmRzdHJlYW0KZW5kb2JqCjkzIDAg
b2JqCjE3NDMKZW5kb2JqCjUwIDAgb2JqCjw8IC9MZW5ndGggNTEgMCBSIC9UeXBlIC9YT2JqZWN0
IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAxNzA3IC9JbnRlcnBvbGF0ZQp0cnVl
IC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNDcgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0Zp
bHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tBn+IQGHAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDgGBgUjAABCmVuZHN0cmVhbQplbmRvYmoKNTEgMCBvYmoKMTQ3NQplbmRv
YmoKMTA0IDAgb2JqCjw8IC9MZW5ndGggMTA1IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAv
SW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMTkwMSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFj
ZSA3IDAgUiAvU01hc2sgMjQ5IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlCj4+CnN0cmVhbQp4Ae3QAQ0AAADCoPdPbQ8HESgMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBwNTCo
UgABCmVuZHN0cmVhbQplbmRvYmoKMTA1IDAgb2JqCjE2MzkKZW5kb2JqCjI2IDAgb2JqCjw8IC9M
ZW5ndGggMjcgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hl
aWdodCA0NzAgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI1MSAw
IFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt
0AENAAAAwqD3T20PBxEoDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYOBhYGCPAAEKZW5kc3RyZWFtCmVuZG9iagoyNyAwIG9iago0MTYKZW5kb2JqCjMyIDAg
b2JqCjw8IC9MZW5ndGggMzMgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lk
dGggNjUgL0hlaWdodCAxMjM5IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9T
TWFzayAyNTMgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4K
c3RyZWFtCngB7dAxAQAAAMKg9U9tDB+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYOAwMr/IA
AQplbmRzdHJlYW0KZW5kb2JqCjMzIDAgb2JqCjEwNzcKZW5kb2JqCjExMiAwIG9iago8PCAvTGVu
Z3RoIDExMyAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVp
Z2h0IDIyMzQgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI1NSAw
IFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt
0DEBAAAAwqD1T20MH4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBh4DgymCAABCmVuZHN0cmVhbQplbmRvYmoK
MTEzIDAgb2JqCjE5MjMKZW5kb2JqCjcyIDAgb2JqCjw8IC9MZW5ndGggNzMgMCBSIC9UeXBlIC9Y
T2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyNjI1IC9JbnRlcnBvbGF0
ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNTcgMCBSIC9CaXRzUGVyQ29tcG9uZW50
IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dCBAAAAAICg/akXKYQKAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wEADz+wAAQplbmRzdHJlYW0KZW5kb2JqCjczIDAgb2JqCjIyNTMKZW5kb2JqCjIyIDAgb2JqCjw8
IC9MZW5ndGggMjMgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUg
L0hlaWdodCA0MTYgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI1
OSAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0K
eAHt0DEBAAAAwqD1T20LL4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYOA3MDzvAAEKZW5kc3RyZWFtCmVuZG9iagoyMyAw
IG9iagozNzcKZW5kb2JqCjY0IDAgb2JqCjw8IC9MZW5ndGggNjUgMCBSIC9UeXBlIC9YT2JqZWN0
IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyODczIC9JbnRlcnBvbGF0ZQp0cnVl
IC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNjEgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0Zp
bHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tDB+IQGHAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAwGFgjOMAAQplbmRzdHJlYW0KZW5k
b2JqCjY1IDAgb2JqCjI0NjYKZW5kb2JqCjM0IDAgb2JqCjw8IC9MZW5ndGggMzUgMCBSIC9UeXBl
IC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAxMTM2IC9JbnRlcnBv
bGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNjMgMCBSIC9CaXRzUGVyQ29tcG9u
ZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tDQ+IQGHA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDgd2BhfQAB
CmVuZHN0cmVhbQplbmRvYmoKMzUgMCBvYmoKOTg5CmVuZG9iago0MiAwIG9iago8PCAvTGVuZ3Ro
IDQzIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQg
MjA5NCAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMjY1IDAgUiAv
Qml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QAQ0A
AADCoPdPbQ43iEBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwaeBgY7ZAABCmVuZHN0cmVhbQplbmRvYmoKNDMgMCBvYmoK
MTgwNAplbmRvYmoKODAgMCBvYmoKPDwgL0xlbmd0aCA4MSAwIFIgL1R5cGUgL1hPYmplY3QgL1N1
YnR5cGUgL0ltYWdlIC9XaWR0aCA2NCAvSGVpZ2h0IDE4NDcgL0ludGVycG9sYXRlCnRydWUgL0Nv
bG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI2NyAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVy
IC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt0DEBAAAAwqD1T20MH4hAYcCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG/gMDaYsAAQpl
bmRzdHJlYW0KZW5kb2JqCjgxIDAgb2JqCjE1NzAKZW5kb2JqCjg4IDAgb2JqCjw8IC9MZW5ndGgg
ODkgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdodCAy
NDIzIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNjkgMCBSIC9C
aXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dCBAAAA
AMOg+VNf4QCFUGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAwDswGakAAQplbmRzdHJl
YW0KZW5kb2JqCjg5IDAgb2JqCjIwNTIKZW5kb2JqCjM4IDAgb2JqCjw8IC9MZW5ndGggMzkgMCBS
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCA5NjAgL0lu
dGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI3MSAwIFIgL0JpdHNQZXJD
b21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt0DEBAAAAwqD1T20N
D4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQOPAwPbXgABCmVuZHN0cmVhbQplbmRvYmoKMzkgMCBvYmoKODQw
CmVuZG9iago3NiAwIG9iago8PCAvTGVuZ3RoIDc3IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlw
ZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjE0OCAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JT
cGFjZSA3IDAgUiAvU01hc2sgMjczIDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQwfiEBhwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMPAcGZIYAAQplbmRzdHJlYW0K
ZW5kb2JqCjc3IDAgb2JqCjE4NTAKZW5kb2JqCjU0IDAgb2JqCjw8IC9MZW5ndGggNTUgMCBSIC9U
eXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdodCAyNDcyIC9JbnRl
cnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAyNzUgMCBSIC9CaXRzUGVyQ29t
cG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tDQ+I
QGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgy8Dww+aQABCmVuZHN0cmVhbQplbmRvYmoKNTUgMCBvYmoKMjA5Mwpl
bmRvYmoKODIgMCBvYmoKPDwgL0xlbmd0aCA4MyAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUg
L0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDIwNjMgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3Bh
Y2UgNyAwIFIgL1NNYXNrIDI3NyAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0
ZURlY29kZQo+PgpzdHJlYW0KeAHt0DEBAAAAwqD1T20IX4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDFwDAyPHAAEKZW5kc3RyZWFtCmVuZG9iago4MyAwIG9iagox
Nzc4CmVuZG9iago0MCAwIG9iago8PCAvTGVuZ3RoIDQxIDAgUiAvVHlwZSAvWE9iamVjdCAvU3Vi
dHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMTk5MSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29s
b3JTcGFjZSA3IDAgUiAvU01hc2sgMjc5IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QAQ0AAADCoPdPbQ43iEBhwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDDwNDDV
iwABCmVuZHN0cmVhbQplbmRvYmoKNDEgMCBvYmoKMTY5MAplbmRvYmoKMTA4IDAgb2JqCjw8IC9M
ZW5ndGggMTA5IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9I
ZWlnaHQgMjMwNiAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMjgx
IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4
Ae3QgQAAAADDoPlTX+AIhVBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwICBPzDB2gABCmVuZHN0cmVhbQplbmRvYmoKMTA5IDAgb2JqCjE5NTQKZW5kb2JqCjU2
IDAgb2JqCjw8IC9MZW5ndGggNTcgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAv
V2lkdGggNjUgL0hlaWdodCAyMzMzIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBS
IC9TTWFzayAyODMgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUK
Pj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tCU+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAwHlg8XEAAQplbmRzdHJlYW0KZW5kb2JqCjU3IDAgb2JqCjIwMDcKZW5k
b2JqCjk0IDAgb2JqCjw8IC9MZW5ndGggOTUgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9J
bWFnZSAvV2lkdGggNjQgL0hlaWdodCAxOTQxIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNl
IDcgMCBSIC9TTWFzayAyODUgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVE
ZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tDB+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgIHPwACwCwABCmVuZHN0cmVhbQplbmRvYmoKOTUgMCBvYmoKMTY0OQplbmRvYmoKMTAyIDAg
b2JqCjw8IC9MZW5ndGggMTAzIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dp
ZHRoIDY1IC9IZWlnaHQgMjA1NCAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAv
U01hc2sgMjg3IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+
CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQsviEBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGHgPDBzsAAEKZW5kc3RyZWFtCmVuZG9iagoxMDMgMCBvYmoKMTc3MAplbmRvYmoKMTE4IDAg
b2JqCjw8IC9MZW5ndGggMTE5IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dp
ZHRoIDY1IC9IZWlnaHQgMTY0IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9T
TWFzayAyODkgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4K
c3RyZWFtCngB7dCBAAAAAMOg+VMf5IVQYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMDA48AAfOwAAQpl
bmRzdHJlYW0KZW5kb2JqCjExOSAwIG9iagoxNjIKZW5kb2JqCjEyIDAgb2JqCjw8IC9MZW5ndGgg
MTMgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdodCA2
MSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMjkxIDAgUiAvQml0
c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADC
oPVPbQsviEBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
A4+BAS3AAAEKZW5kc3RyZWFtCmVuZG9iagoxMyAwIG9iago3NQplbmRvYmoKNDQgMCBvYmoKPDwg
L0xlbmd0aCA0NSAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAv
SGVpZ2h0IDE0MDEgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDI5
MyAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0K
eAHt0IEAAAAAw6D5Ux/khVBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBg4GJgK2cAAQplbmRzdHJlYW0KZW5kb2JqCjQ1IDAgb2JqCjEyMTMKZW5kb2JqCjMw
IDAgb2JqCjw8IC9MZW5ndGggMzEgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAv
V2lkdGggNjUgL0hlaWdodCA5NDIgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIg
L1NNYXNrIDI5NSAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+
PgpzdHJlYW0KeAHt0IEAAAAAw6D5Ux/khVBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM/A4MzagAAQplbmRzdHJlYW0KZW5kb2JqCjMxIDAg
b2JqCjgyMwplbmRvYmoKMTggMCBvYmoKPDwgL0xlbmd0aCAxOSAwIFIgL1R5cGUgL1hPYmplY3Qg
L1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDE3OCAvSW50ZXJwb2xhdGUKdHJ1ZSAv
Q29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMjk3IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQ0PiEBhwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwZeBgaHlgABCmVuZHN0cmVhbQplbmRvYmoKMTkgMCBvYmoK
MTc1CmVuZG9iago0NiAwIG9iago8PCAvTGVuZ3RoIDQ3IDAgUiAvVHlwZSAvWE9iamVjdCAvU3Vi
dHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMTU1OSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29s
b3JTcGFjZSA3IDAgUiAvU01hc2sgMjk5IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQZ/iEBhwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGPgGBpF8AAEKZW5kc3RyZWFtCmVuZG9i
ago0NyAwIG9iagoxMzI5CmVuZG9iago2MCAwIG9iago8PCAvTGVuZ3RoIDYxIDAgUiAvVHlwZSAv
WE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMjc5NiAvSW50ZXJwb2xh
dGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMzAxIDAgUiAvQml0c1BlckNvbXBvbmVu
dCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QAQ0AAADCoPdPbQ43iEBhwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGPge
GDF4AAEKZW5kc3RyZWFtCmVuZG9iago2MSAwIG9iagoyMzY0CmVuZG9iagozNiAwIG9iago8PCAv
TGVuZ3RoIDM3IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9I
ZWlnaHQgMTA0MSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMzAz
IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4
Ae3QAQ0AAADCoPdPbQ8HESgMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMXA0MGSAAAQplbmRz
dHJlYW0KZW5kb2JqCjM3IDAgb2JqCjkwOAplbmRvYmoKNzQgMCBvYmoKPDwgL0xlbmd0aCA3NSAw
IFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NCAvSGVpZ2h0IDIxMzAg
L0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDMwNSAwIFIgL0JpdHNQ
ZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt0IEAAAAAw6D5
U9/gBIVQYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgw8AYGPdoAAQplbmRzdHJlYW0KZW5kb2JqCjc1IDAgb2JqCjE4
MDcKZW5kb2JqCjI4IDAgb2JqCjw8IC9MZW5ndGggMjkgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAxMDA1IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xv
clNwYWNlIDcgMCBSIC9TTWFzayAzMDcgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAv
RmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tDQ+IQGHAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgycDgz9pQABCmVuZHN0cmVhbQpl
bmRvYmoKMjkgMCBvYmoKODc4CmVuZG9iagoxMTAgMCBvYmoKPDwgL0xlbmd0aCAxMTEgMCBSIC9U
eXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyMTYyIC9JbnRl
cnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzMDkgMCBSIC9CaXRzUGVyQ29t
cG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U/tbwaI
QGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDgBwZvMAABCmVuZHN0cmVhbQplbmRvYmoKMTExIDAgb2JqCjE4NjIKZW5k
b2JqCjggMCBvYmoKPDwgL0xlbmd0aCA5IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1h
Z2UgL1dpZHRoIDY1IC9IZWlnaHQgMzAzIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcg
MCBSIC9TTWFzayAzMTEgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNv
ZGUKPj4Kc3RyZWFtCngB7dCBAAAAAICg/akXKYQKAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GGjmzQABCmVuZHN0cmVhbQplbmRvYmoKOSAwIG9iagoyNzgKZW5kb2JqCjExNCAwIG9iago8PCAv
TGVuZ3RoIDExNSAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NCAv
SGVpZ2h0IDIyNDcgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDMx
MyAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0K
eAHt0DEBAAAAwqD1T20Gf4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBj4BgaVmgABCmVuZHN0cmVhbQplbmRvYmoKMTE1IDAgb2JqCjE5MDUK
ZW5kb2JqCjg2IDAgb2JqCjw8IC9MZW5ndGggODcgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBl
IC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyMzAxIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNw
YWNlIDcgMCBSIC9TTWFzayAzMTUgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxh
dGVEZWNvZGUKPj4Kc3RyZWFtCngB7dCBAAAAAMOg+VMf4QKFUGHAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAwBkY
2REAAQplbmRzdHJlYW0KZW5kb2JqCjg3IDAgb2JqCjE5ODAKZW5kb2JqCjkwIDAgb2JqCjw8IC9M
ZW5ndGggOTEgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hl
aWdodCAyMjM0IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzMTcg
MCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB
7dAxAQAAAMKg9U9tDB+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYeA4MpggAAQplbmRzdHJlYW0KZW5kb2Jq
CjkxIDAgb2JqCjE5MjMKZW5kb2JqCjIwIDAgb2JqCjw8IC9MZW5ndGggMjEgMCBSIC9UeXBlIC9Y
T2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdodCAzOTggL0ludGVycG9sYXRl
CnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNrIDMxOSAwIFIgL0JpdHNQZXJDb21wb25lbnQg
OCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt0DEBAAAAwqD1T20Gf4hAYcCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBj4BgYqjwABCmVuZHN0cmVh
bQplbmRvYmoKMjEgMCBvYmoKMzU3CmVuZG9iagoxMDYgMCBvYmoKPDwgL0xlbmd0aCAxMDcgMCBS
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyMDY3IC9J
bnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzMjEgMCBSIC9CaXRzUGVy
Q29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9t
CU+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDgMDAm0wAB
CmVuZHN0cmVhbQplbmRvYmoKMTA3IDAgb2JqCjE3ODEKZW5kb2JqCjY4IDAgb2JqCjw8IC9MZW5n
dGggNjkgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdo
dCAyMzc4IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzMjMgMCBS
IC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAx
AQAAAMKg9U9tCU+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED/4EBE8cAAQplbmRzdHJlYW0K
ZW5kb2JqCjY5IDAgb2JqCjIwNDYKZW5kb2JqCjcwIDAgb2JqCjw8IC9MZW5ndGggNzEgMCBSIC9U
eXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyNTY3IC9JbnRl
cnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzMjUgMCBSIC9CaXRzUGVyQ29t
cG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dAxAQAAAMKg9U9tBn+I
QGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgIFjYKO+AAEKZW5kc3RyZWFtCmVuZG9iago3MSAwIG9iagoyMjA2CmVu
ZG9iago2MiAwIG9iago8PCAvTGVuZ3RoIDYzIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAv
SW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjM5MSAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFj
ZSA3IDAgUiAvU01hc2sgMzI3IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlCj4+CnN0cmVhbQp4Ae3QgQAAAADDoPlTX+EAhVBhwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMXAMDHa4AAQplbmRzdHJlYW0KZW5kb2JqCjYzIDAgb2JqCjIwNTcKZW5k
b2JqCjI0IDAgb2JqCjw8IC9MZW5ndGggMjUgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9J
bWFnZSAvV2lkdGggNjUgL0hlaWdodCA0MjUgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2Ug
NyAwIFIgL1NNYXNrIDMyOSAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURl
Y29kZQo+PgpzdHJlYW0KeAHt0DEBAAAAwqD1T20Hb4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwcA4MQ8oA
AQplbmRzdHJlYW0KZW5kb2JqCjI1IDAgb2JqCjM4NQplbmRvYmoKMTQgMCBvYmoKPDwgL0xlbmd0
aCAxNSAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0
IDYxIC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzMzEgMCBSIC9C
aXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dCBAAAA
AMOg+VOf4AaFUGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBu7AAC53AAEKZW5kc3RyZWFtCmVuZG9iagoxNSAwIG9iago3NgplbmRvYmoKODQgMCBvYmoK
PDwgL0xlbmd0aCA4NSAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2
NSAvSGVpZ2h0IDIzNjAgL0ludGVycG9sYXRlCnRydWUgL0NvbG9yU3BhY2UgNyAwIFIgL1NNYXNr
IDMzMyAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZQo+PgpzdHJl
YW0KeAHt0AENAAAAwqD3T20ON4hAYcCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDLwODAYRAAEKZW5kc3RyZWFtCmVuZG9iago4
NSAwIG9iagoyMDMwCmVuZG9iago3OCAwIG9iago8PCAvTGVuZ3RoIDc5IDAgUiAvVHlwZSAvWE9i
amVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjQyMyAvSW50ZXJwb2xhdGUK
dHJ1ZSAvQ29sb3JTcGFjZSA3IDAgUiAvU01hc2sgMzM1IDAgUiAvQml0c1BlckNvbXBvbmVudCA4
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQo/iEBhwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
XAYGNg4AAQplbmRzdHJlYW0KZW5kb2JqCjc5IDAgb2JqCjIwODQKZW5kb2JqCjUyIDAgb2JqCjw8
IC9MZW5ndGggNTMgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUg
L0hlaWdodCAxODY5IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAz
MzcgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFt
CngB7dAxAQAAAMKg9U9tDQ+IQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgIHrgQGP8gABCmVuZHN0cmVhbQplbmRvYmoKNTMgMCBvYmoKMTYxMwplbmRvYmoK
MTE2IDAgb2JqCjw8IC9MZW5ndGggMTE3IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1h
Z2UgL1dpZHRoIDY1IC9IZWlnaHQgMjc0NyAvSW50ZXJwb2xhdGUKdHJ1ZSAvQ29sb3JTcGFjZSA3
IDAgUiAvU01hc2sgMzM5IDAgUiAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlCj4+CnN0cmVhbQp4Ae3QMQEAAADCoPVPbQdviEBhwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIAB
AwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYM
GDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBg
wIABAwYMGDBgwIABAwYMGDBgwIABAwYMGDBgwICBc2As6QABCmVuZHN0cmVhbQplbmRvYmoKMTE3
IDAgb2JqCjIzNTkKZW5kb2JqCjU4IDAgb2JqCjw8IC9MZW5ndGggNTkgMCBSIC9UeXBlIC9YT2Jq
ZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyNzIwIC9JbnRlcnBvbGF0ZQp0
cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAzNDEgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDgg
L0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFtCngB7dABDQAAAMKg909tDwcRKAwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgIG3gQEYWAABCmVuZHN0cmVhbQplbmRvYmoKNTkgMCBvYmoK
MjMzNgplbmRvYmoKOTggMCBvYmoKPDwgL0xlbmd0aCA5OSAwIFIgL1R5cGUgL1hPYmplY3QgL1N1
YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDE4MjkgL0ludGVycG9sYXRlCnRydWUgL0Nv
bG9yU3BhY2UgNyAwIFIgL1NNYXNrIDM0MyAwIFIgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVy
IC9GbGF0ZURlY29kZQo+PgpzdHJlYW0KeAHt0DEBAAAAwqD1T20KP4hAYcCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
DBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgw
YMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCA
AQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMGDBgwYMCAAQMG
7gMDcXoAAQplbmRzdHJlYW0KZW5kb2JqCjk5IDAgb2JqCjE1NzkKZW5kb2JqCjY2IDAgb2JqCjw8
IC9MZW5ndGggNjcgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQg
L0hlaWdodCAyNjc1IC9JbnRlcnBvbGF0ZQp0cnVlIC9Db2xvclNwYWNlIDcgMCBSIC9TTWFzayAz
NDUgMCBSIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUKPj4Kc3RyZWFt
CngB7dABDQAAAMKg909tDjeIQGHAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDA
gAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAED
BgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwY
MGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBgwYMGDAgAEDBv4GBtapAAEKZW5kc3RyZWFtCmVuZG9i
ago2NyAwIG9iagoyMjYzCmVuZG9iagoyNjMgMCBvYmoKPDwgL0xlbmd0aCAyNjQgMCBSIC9UeXBl
IC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAxMTM2IC9Db2xvclNw
YWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0Zp
bHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB7ZvZkhrLDkVtxmIeC6iJwf//kWdLWQLazdSO
uBH3YeVDdwdGu6QtaTlt41+/ODjwv3bgt59/fEoKvn79oco17u6HH0jcRX398TONu5iOn7sXPlGI
t6fg+Bqvvldo3xmBt+8fSqS3eVj37vgLrcTLJG7xHt1Lx36+SbwSuMYrIsX2+33/oZVIb3gu4b+u
Z3m4Yq9HIknC3/FMIMI9XrGD27E83iuEgD3fwoc6WZbpq5SsEnfC3vU4hS/xFp5lIz8mIgVPQvU9
U/gan8LH6YxGSiMptAKPcmgFPH89X08fT9ozHoeCFeFvfFCEvZ4aYOVnFj6d+ZlOJuOxlaEqwoan
Akog4hU+T2cmiZErpFboUc8F1ID0/Olsvlj6Wczns6mqsBw8hUcC9wV4/opfLler9Xq9Wi0X89nE
fLBm2lDbu78m4a+4AxqAYTaeTPX41WrjZ20K01B4I6AJsgSmM8WvN9ttnufbzXq9XMiHcUrhVQZu
YUpA8Ra+2+1cYplsGKZGPC1BAoNBSkDPz/O9n52SWHkRYeNzgV7PWiAHlsp/tz8ciqI47KXgRYxH
bR8eCqi0jg2BKpADKiDfK7wsy6KQQkphlGmYHs6SJK8CsnC+UAG7g8KrqipL5aAUrJWZluqFgHk4
HKYKVECh8Lquq6o47PL1So3wPjwXMI5ZEyfqoSVQKrxpmroqi32qwU1wsCjlL9PsJSjeBMYSWG1y
S6BpjsdjU6uI3UY1TCfuog3jMwEbI7NgtZUDVX08nk6nY1PJhWTCewFvgpoogbLW803gWFeFBGSC
ZTDwdXiawSCzDJZr9VACp9P5fD65gJkgAY3SOwHrogkUcqAVkAuHJGBteCvgc+gCx/P5crmcT1cB
7+N7AXUxZfCXgNrwWQbWRY1R1dwL+Cz+RMCbECU0VfEvAsfT5fLnz5/LWZOAAB4wB+wCPICJ/L5Q
1niAB3bTZQ7wgDnQn1jYBTywP7kyB3jAHPjfxbEL8MD/Ng8mwkSYCBP9H3lgIky0f+xjDvCAOdCH
B9gFPOgzB/ocC3OAB/Z5JuYAD5gD+4Qtc4AHzIE+p8ou4IF9Xpk5wAPm4Jc+Rc4c4AFzoP8Owi7g
gf2vIOYAD5gDc4A5wAMfA5jILvgg8HsjTISJMDE5wC6wC+wCuxAOwAN4AA9iG7grwwN4AA/gQTgA
D+ABPIht4H4AD+ABPIAH4QA8gAfwILaB+wE8gAfwAB6EA/AAHsCD2AbuB/AAHsADeBAOwAN4AA9i
G7gfwAN4AA/gQTgAD+ABPIht4H4AD+ABPIAH4QA8gAfwILaB+wE8gAfwAB6EA/AAHsCD2AbuB/AA
HsADeBAOwAN4AA9iG7gfwAN4AA/gQTgAD+ABPIht4H4AD+ABPIAH4QA8gAfwILaB+wE8gAfwAB6E
A/AAHsCD2AbuB/AAHsADeBAOwAN4AA9iG7gfwAN4AA/gQTgAD+ABPIht4H4AD+ABPIAH4QA8gAfw
ILaB+wE8gAfwAB6EA/AAHsCD2AbuB/AAHsADeBAOwAN4AA9iG7gfwAN4AA/gQTgAD+ABPIht4H4A
D+ABPIAH4QA8gAfwILaB+wE8gAfwAB6EA/AAHsCD2AbuB/AAHsADeBAOwAN4AA9iG7gfwAN4AA/g
QTgAD+ABPIht4H4AD+ABPIAH4QA8gAfwILaB+wE8gAfwAB6EA/AAHsCD2AbuB/AAHsADeBAOwAN4
AA9iG7gf/P/y4Hg+Xy6X8+nYVMVuu17Op+NsOOj1up2O2hYd9O/f27gvqiYEmro8/FBgnf8tkG9W
n2cwXz4UWMw+K2E8vQqcTuezWaASlMFiNvnEg6wVOJR10wrUVbFPAqP3Jg6TwHZnAsfj6XQ6Hk1g
u7YMRsPBmy70XWCxkkBR1UmgqcqDBJZzF+i/bGPPBWaL1cbaUDXKQQ5IYLexMbAMXgp0TWA0mS2W
m1w1VHXdNE1dl8V+Jw81RybQ7T4fpBBQG7a7fVHWfqrisM/NAu/iC4FORwKD4UhtWKxVg1zwIwd8
Dq2LA8ug82SUWwG1QSZYCoeiKMuyUAHWRLMgG/SfCvz+bQK9gdowmakGubA/SKI4HHa5emAVuIfK
QKvzfZlcoNsbDDLVYCmYgiSUf761BNIc9ntvBNyEiaZZRWx3fhRvQ6AEsmH/tUByMaUghc12m+f5
drv2FkxSBb1k4eMSOt1uP1JYmIKf9WrpBdgiKIE3AtZIpSAfF8vlarXW0z3eC2jH8IGJwpIZ631o
FaYusdRZzN2ANoEHY5jg1grYLKUcprPZfL5YeLhGIOLfCMgFK8KrmErCznQ6GVsHNETWw+9jeMvA
atAwWRHyYTyZTKaKtvC7eEv1K5K/CHgKnkM2koYfhafnP2lBEnAXlUKbg5UhCTuZwj3/awEPM0h9
8CKsCrNSx4MVbvXf4ttH/v3Ni/MUXEESLmLfUvjjGbqXuUn0LAkdD7ZwPf59/NUG+aAkWg2LbsPT
CD5qQaThKZiTJuEabbQ//vEIR2z6flNwCZOxY5Lt41893zSSgidhQRF8DX8Xf1W4SpjMD8JvOVgq
KThy1wupzrdf2zK+f3sbeX3D99jPH9+K/C1x1f7RD63Kj2J4Mw78kwP/AYcRyeoKZW5kc3RyZWFt
CmVuZG9iagoyNjQgMCBvYmoKMTk1NwplbmRvYmoKMjgzIDAgb2JqCjw8IC9MZW5ndGggMjg0IDAg
UiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjMzMyAv
Q29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVu
dCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2b2XbiyhJE2xOjGIUAicF2//9H
nsgqBWCMMD5n3Ze7dj1gcCtDWVGZm2wb//nDwoH/vQNPT0//9iYKvVi/VrmI9dPfaDjm6uujEpdh
z8/Ply8fkThdr9jzOn33Z4n20nNs+6z9/k8Cl+Ev55VEHpHI16TLU/RrrPTsQuJOEud4BaVgP+h1
SOQLuhXSv+u6HP52XimPk0KnwDleAYrueel52olz6FIIgXT/CFdw36vXC4m8jbioQ+BrvIIHg8Fw
ONRjvx8SkUSbw02FiFcC4Z5un6NHsUJDEs4hXXdLIcc/O344HI3GeUlDElnhTgrp/pGA9t8fRHhR
FJPJRI/jyEIK5010ZJA20MYrfDKZxpLGOJI4KehWdwV6Pd1/HOGz2Xw+n82yhASUQ/h4SyAMyA6G
gSl+quhFLGlMlURK4aRwlUOKt4AM0P2nCl8uy7JcLhdJod1Em8LVLk4COkKd/2is+MWiLFexyjIp
jEetC21LfLGhFYgjiBMYF9PZYlmuqmq9XlfVKhQmhVJoXUiXdwoMBqPYQMSvN7HW1Uq7mOooUgra
Q7dA7EBHEAmk+G1d19uskFLo96MWOgSijVREsYNIQPffbuumaertdl2Vy0hBBxEFnavx2xayQDrD
cED513Wz2+2aut7EJqYT7+FHgUJHUFabbdPs9vv9rmkihUXsIZvQKZAOISyYaQdr5b/bHw4HKaQU
ZtN0DqdSurGF1IgqgkI7WG1S/PF4lEK9Xa9aE1JHfa/mOJfwUGUQVaQzqCSwPxzf39+l0Gw3VTmX
CaqEdAzf2sECaoQQCAu2ze5ggZ32ECaEQDRUdwZRhyEQFkjg+P7x8aEUJLBeZYHo6fsC6sQkUMtB
C2gPrcDwAQF1YmQgAcV/fn4qBQvoGB4SiDq8IaBafFRAHn4TqOIcfyGwafYXW4hj+L3AQRb8/ftX
JsQxIIAH1AG9AA9gIu8LvDdqSmQ+wAMNmtQBHlTUgf7rTB3gQfwIhTrAA+qgmOIBHsQvF6gDPKAO
9GsmegEP9Jsu6gAP4jfv1AEeUAfxGQ7qAA+og/RZHHoBHqTPtcFEmAgTYWL7GU3eF3hf4H0hf16Z
XqAX6AV64fznB/wsDSbCRJgIE2Hinz94gAfxl5LUAR5QB+EAdYAHqQxgIr2QCoH3RpgIE2FidoBe
oBfoBXrBDsADeAAP3A3MyvAAHsADeGAH4AE8gAfuBuYDeAAP4AE8sAPwAB7AA3cD8wE8gAfwAB7Y
AXgAD+CBu4H5AB7AA3gAD+wAPIAH8MDdwHwAD+ABPIAHdgAewAN44G5gPoAH8AAewAM7AA/gATxw
NzAfwAN4AA/ggR2AB/AAHrgbmA/gATyAB/DADsADeAAP3A3MB/AAHsADeGAH4AE8gAfuBuYDeAAP
4AE8sAPwAB7AA3cD8wE8gAfwAB7YAXgAD+CBu4H5AB7AA3gAD+wAPIAH8MDdwHwAD+ABPIAHdgAe
wAN44G5gPoAH8AAewAM7AA/gATxwNzAfwAN4AA/ggR2AB/AAHrgbmA/gATyAB/DADsADeAAP3A3M
B/AAHsADeGAH4AE8gAfuBuYDeAAP4AE8sAPwAB7AA3cD8wE8gAfwAB7YAXgAD+CBu4H5AB7AA3gA
D+wAPIAH8MDdwHwAD+ABPIAHdgAewAN44G5gPoAH8AAewAM7AA/gATxwNzAfwAN4AA/ggR2AB/AA
HrgbmA/gATyAB/DADsADeAAP3A3MB/AAHsADeGAH4AE8gAfuBuYDeAAP4AE8sAPwAB7AA3cD8wE8
gAfwAB7YAXgAD+CBu4H5AB7AA3gAD+wAPIAH8MDdwHwAD+ABPIAHdgAewAN44G5gPoAH8AAewAM7
AA/gATxwNzAfwAN4AA/ggR2AB/AAHrgbmA/gATyAB/DADsADeAAP3A3MB/AAHsADeGAH4AE8gAfu
BuYDeAAP4AE8sAPwAB7AA3cD8wE8gAfwAB7YAXgAD+CBu4H5AB7AA3gAD+wAPIAH8MDdwHwAD+AB
PIAHdgAewAN44G5gPoAH8AAewAM7AA/gATxwNzAfwAN4AA/ggR2AB/AAHrgbmA/gATyAB/DADsAD
eAAP3A3MB/AAHsADeGAH4AE8gAfuBuYDeAAP4AE8sAPwAB7AA3cD8wE8gAfwAB7YAXgAD+CBu4H5
AB7AA3gAD+wAPIAH8MDdwHwAD+ABPIAHdgAewAN44G5gPoAH8AAewAM7AA/gATxwNzAfwAN4AA/g
gR2AB/AAHrgbmA/gATyAB/DADsADeAAP3A3MB/AAHsADeGAH4AE8gAfuBuYDeAAP4AE8sAPwAB7A
A3cD8wE8gAfwAB7YAXgAD+CBu4H5AB7AA3gAD+wAPIAH8MDdwHwAD+ABPIAHdgAewAN44G5gPoAH
8AAewAM7AA/gATxwNzAfwAN4AA/ggR2AB/AAHrgbmA/gATyAB/DADsADeAAP3A3MB/AAHsADeGAH
4AE8gAfuBuYDeAAP4AE8sAPwAB7AA3cD8wE8gAfwAB7YAXgAD+CBu4H5AB7AA3gAD+wAPIAH8MDd
wHwAD+ABPIAHdgAewIP/cx4c3z8+Pz8/3o+HXb2plvNpMRr2e2+vL8/PmgfOjaBnN+aDerc/Ceyb
7fp3AsvV+lpgtXg8g8n8psBs8tgWRuOTgPbwIQuOsYXVYjYZP+LBoBXYNrtDKxAeZoHh4EcTe1mg
rJLA8f1dCaRDKCOD4aD3wym8JYHZQgJ1s1cKEjhoB5uqnGeBt7vH+JoECgmsNnWzk4Luv9+FBaUO
ITJ4e71TBy8hMBwVsziGrQ5yfzgc9vtkQa6jEHjpLiQLTOfLcr2RC/tYSkA7WMYpZg87BZ5DoD8c
jadhwiY2EauJM1gupjpFH0JHKYfAW38wHE/SHrSJummaulYdl7EDWdDPHt4UeHqSwGsIjIqUQrXZ
SqLeagNKINdhP3kYrfO9mUIgmTAYFZFCuVrLB4WvdQSLOMSTBfcFYg+RghSqdaxqpQ3MopftYadA
7KHXl43FZDoPhVVVVSvFL2ZhYYJBWwW3t5D30Fc1xybmy2UZaxn3j050AmHhlUAiytNzFkgnqU3M
5ovFcrlcaP+KjyPoxRnkKrgWyFRqFeIglENIxJql+K8JfOFZ+0JZZQEVU1KQhDRmU92+kAFpA06g
UyBt4q2fFMZFMYkV4Tk+b+BbFZ0zUAqpmHoph9F4LI1Cj6Nh3L/to2RhRwZJIMoxFAbD4SgvhWcD
0wbuClwqSEIaWvraT/c/x3+t41M6cbqxicghktBKwSk8mkAn2Hn/UAkBKySJJNLT0vlfxHfc/4tC
SuIt8lBwG+77d8fnFHIOUtCK4Li5so/wlP+NGjyZcFaQEWFFu+LFQ/GtDZFDeHle6RvJorv3PxmZ
rLRK+qqHx+Kdw1kix7fRP97/IocIaW9+ir7j/9lHPTsHXD37ctXdF1eB+eXdiO//eKXx/YJHvtOK
PHIp1+DAf3PgHzVT0zEKZW5kc3RyZWFtCmVuZG9iagoyODQgMCBvYmoKMjYwMQplbmRvYmoKMjU3
IDAgb2JqCjw8IC9MZW5ndGggMjU4IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2Ug
L1dpZHRoIDY1IC9IZWlnaHQgMjYyNSAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xh
dGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVh
bQp4Ae3b2XIbuRKEYWshxZ3s5iI2Fy1+/4ecrEJnU7K42RHn5sTfF5ZkCkmggPqM8ci/fvFQgf9x
BR665x/eqBvrT/4uw6O+f7w74/uwr1/dF9GNePTT/c7DPQntd3tw+9EZNxO+DX8qT8loX7mRUL4r
R7Sjv4SUF68mnMbHuOfu0RcZmq9fSejGt6N75YmcNuJGQr6st8rxMbgfT3zSRcS3XJzCafzzcxn9
Ek8J8STymy5ExGv5/jG+39fYQTwlRJPIZVwOyFdO42P0sDwREitRhF6/mBAv6PVHFT/eXsNHo9F4
PNavw2GbkJsR33huDW2Adi/HD4caPYknMpTwEnOIhCsBZQFlfAyflkcZbUK3iAszKBvY0/z19pPp
bDabz+f6dXpKaKdwJUAL8Pj5fBFPZEwnMYd+qeO5GsS6VMI4vhGQ7z9fVFVd11WljNk0V6GEro7f
C3kKKBPQ/BcavVytVktlKCFWEXW8EZATiALM5lUMX6/XilgqQXUoizh/FsoMYgt7qoAKmOPXm9fX
140ylJCLiCp4J88toauAFqD31/DtdhsRq7oqU+j3cyfz/b7tRDuDdgUxgeVqreFN0yhis17WOQVt
xOWAPMVqolhBTEDjm108jRJWy6hClrFriD9nUAL6fe3hdL6IBTS7/eFw2EfCelnFRsQ+XAnINtAh
yBVoAhp/PB4jQVPINWgfoopPP/tBNchjpFMwHGkFVUwgx2eCplBrDePRjYBSwyzBarPdHQ7Ht7e3
o1bR5BpUhAiIjYyi/6xBnALNIEpQr1UBjX9/f1fCvtlusggRkCfhYoAkiYBKe9DsNf7j4yMSdgpQ
EWIG5ShdDohzGAGb7feA16iiAga3A2IXI2B30AJiBpqCilAChvcE5C6WgI/Pz89YQxswVT/dMYM8
h2cC1A73B6x0jLSE0wy2cRb/KkA1VAViCVqDtuHfAj5///4dRSCAGnAO6AU8EMqYSA30hyvngBrE
JYtzQA04B/FffZwDasA5qFfUgBroryM5B9Qg/jqQc0ANOAf6PyT0AjWI/1PGOaAGnIP80QF6AQ/i
R0g4B9SAc1B+nIpeoBfoBXpBP6HKHYkaxE8qcw6oAecgf1qYXsCD+KlxzgE14BzonxPQC9TgF+fg
FzXQv2ziHFCD+AdunANqwDmICnAOqEEeA0ykF/Ig8GcjJmIiJpYK0Av0Ar1AL7gCeIAHeOBu4K6M
B3iAB3jgCuABHuCBu4H7AR7gAR7ggSuAB3iAB+4G7gd4gAd4gAeuAB7gAR64G7gf4AEe4AEeuAJ4
gAd44G7gfoAHeIAHeOAK4AEe4IG7gfsBHuABHuCBK4AHeIAH7gbuB3iAB3iAB64AHuABHrgbuB/g
AR7gAR64AniAB3jgbuB+gAd4gAd44ArgAR7ggbuB+wEe4AEe4IErgAd4gAfuBu4HeIAHeIAHrgAe
4AEeuBu4H+ABHuABHrgCeIAHeOBu4H6AB3iAB3jgCuABHuCBu4H7AR7gAR7ggSuAB3iAB+4G7gd4
gAd4gAeuAB7gAR64G7gf4AEe4AEeuAJ4gAd44G7gfoAHeIAHeOAK4AEe4IG7gfsBHuABHuCBK4AH
eIAH7gbuB3iAB3iAB64AHuABHrgbuB/gAR7gAR64AniAB3jgbuB+gAd4gAd44ArgAR7ggbuB+wEe
4AEe4IErgAd4gAfuBu4HeIAHeIAHrgAe4AEeuBu4H+ABHuABHrgCeIAHeOBu4H6AB3iAB3jgCuAB
HuCBu4H7AR7gAR7ggSuAB3iAB+4G7gd4gAd4gAeuAB7gAR64G7gf4AEe4AEeuAJ4gAd44G7gfoAH
eIAHeOAK4AEe4IG7gfsBHuABHuCBK4AHeIAH7gbuB3iAB3iAB64AHuABHrgbuB/gAR7gAR64AniA
B3jgbuB+gAd4gAd44ArgAR7ggbuB+wEe4AEe4IErgAd4gAfuBu4HeIAHeIAHrgAe4AEeuBu4H+AB
HuABHrgCeIAHeOBu4H6AB3iAB3jgCuABHuCBu4H7AR7gAR7ggSuAB3iAB+4G7gd4gAd4gAeuAB7g
AR64G7gf4AEe4AEeuAJ4gAd44G7gfoAHeIAHeOAK4AEe4IG7gfsBHuABHuCBK4AHeIAH7gbuB3iA
B3iAB64AHuABHrgbuB/gAR7gAR64AniAB3jgbuB+gAd4gAd44ArgAR7ggbuB+wEe4AEe4IErgAd4
gAfuBu4HeIAHeIAHrgAe4AEeuBu4H+ABHuABHrgCeIAHeOBu4H6AB3iAB3jgCuABHuCBu4H7AR7g
AR7ggSuAB3iAB+4G7gd4gAd4gAeuAB7gAR64G7gf4AEe4AEeuAJ4gAd44G7gfoAHeIAHeOAK4AEe
4IG7gfsBHuABHuCBK4AHeIAH7gbuB3iAB3iAB64AHuABHrgbuB/gAR7gAR64AniAB3jgbuB+gAd4
gAd44ArgAR7ggbuB+wEe4AEe4IErgAd4gAfuBu4HeIAHeIAHrgAe4AEeuBu4H+ABHuABHrgCeIAH
eOBu4H6AB3iAB3jgCuABHuCBu4H7AR7gAR7ggSuAB3iAB+4G7gd4gAd4gAeuAB7gAR64G7gf4AEe
4AEeuAJ4gAd44G7gfoAHeIAHeOAK4AEe4IG7gfsBHuABHuCBK4AHeIAH7gbuB3iAB3iAB64AHuAB
HrgbuB/gAR7gAR64AniAB3jgbuB+gAd4gAd44ArgAR7ggbuB+wEe4AEe4IErgAd4gAfuBu4HePD/
7MHb+8fn5+fH+9vbYbddL6v5dDwc9HvPT0+POvoPboP8+KMXNtvdoQs47pvXvwuolj8CVvX9M5jO
zwYsZncuYdwFaA0fUYJYwqpezCaje2owLAGvzf7YBhxVwzZgcLOI/ZcMqNcZ8Pb+HhNQwGaZMxi8
3NiFXgbMFgrQNmgKCjge9o0CqrmWMHjpXd3G5wyYKGClbdgrId5/3+1iBDxfOQdPGTBSQLXaaA2H
w/F4PBz2WsG6XuQ5UsDT5YOUAYPRJLYh1qAEPftd87qJTYhdzIDHCyfxMQL6g9F4mmt4bXb7eHbN
Ns9h7GLW8PFaQK8/GI4ns3m9XG+2TbPb7RqNjwnMp1HD2IQLAQ8PmkFbBK2hXmkRimi2Gr9e1tqD
cQSohmUCP5opAtoixBqq5WqzUYSGx3g1Qp7DfuxBluBSQO9lMIwyLurlar2JZ71SI+kc5wTyFFwM
6NYQVaiUsFqvNVzvnxXQHnwpwbkZeA3D2AjNoV7GU8d4T6AXK7gyg1LGXIQSqqrW6Gqh8dOxOrFt
hHMBYqmgVMqoKUw0h/kinrmGqwBlfLsH3zhrv2gDTgmKUMZ8Npt6fOnEWMDFgKyCOkqL0CQm03gm
k/L+XxdwIeBB9YmzkAlaxlgZE/06ivnH+O4QXArIBB3HSBgMNYt8hsOB6tcvEpQKXg2InVCCIpSh
Rx/19n7/M1vYpak47SIiQREZEh/y7ROCa+NjI7uEjMiQvp6epl/GXw34kqBlKCLmEYPvHJ5nqcxB
exERmaH31hOOnT3DXQHyk1xE1CESMsKjT8PPHqIupiRkRGZETjyRWZZ/fbxXURLKRHJsN/zWeE2l
nUSXUQL8u91cr3zi780tjeGn37jj/SP4y4Dvn1551z9e+j6u/eqP77n15Z8Zt77/7Ov/9tZno/hN
KnC9Av8BecxtaQplbmRzdHJlYW0KZW5kb2JqCjI1OCAwIG9iagoyNzQ0CmVuZG9iagoyNzEgMCBv
YmoKPDwgL0xlbmd0aCAyNzIgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lk
dGggNjUgL0hlaWdodCA5NjAgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRy
dWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHt
m1lzwkgMhHMBNhjf98GR//8jt6WxDCS2IVu1L1s9DwkhqEfqkb5MJeTtjYsO/LcOvN+tv+90Fzw+
/IvG72h95mWJhXg8/ZLEFP5xW9NzLyiMr70Fj49M45nEffynLafhvrUucBduweNn1Xgu4V4hL0bc
122Jijz7TGGKd+EbW6LkJPQVi1XcxSMC0Vu3ROdBYek4VWDMXqN3bkFGFJCEVbGQgwho+dh+u0Ww
5xYeOQlR0F1mBcb9YZ+L9zzfludBwpWxovBjf4Tv9wdd+70PCVFQJ+WFcyk4gWl/CQ/cOhz2vm8K
LoUFAWeA1O/5CD8ej2EY4mMACc0BRjofFwVcAmN8GEa6oBEcXA6qsFyCHCEOwOKjOE6SJI6jKDwG
8AE2mMAvE8QAHKEm4OLDCNGpriSGAnxQhYVmuAloAqgf8WmW5XmeZWkKhUAUcBJPBKQFxMBjiPg8
L3TlGRTEhikF3e/BSJeBOLBBBZIA9i/KsqqqsizyLIm1CHFhvh1HAUlg5xKQ+KrWpQpSBGrYTjY+
+ggBaYKxAkkgyxHf6KqqAkVICqhhaoV5ATQRKoADaV4gvu26rm3ruswzcWHvaw2ul5YEdh4sjGIk
IPF933dd01RFDhdQw24HExYFxi7aByEqKCqJH4ah79sGKWgNOAc3UeLZz1OwNvQhECeSAOJPp9Mw
dG1dFWkSqQmrAu4Q1IKirFuNh0TfoYYMAgFcVLgpVmYyQBfgFMWCVCqAwPl8FoG2LqUVVEA7YaEE
6QIVUAs6xF8ul/N56CEgJoiAa6UVATlFeIgK7gWaygnIOEgvrgnIKapAjwSu1+vlchpgggpILz4X
0FMUD38JHF8ViFMp4YeAHMPrArkcwn0GtZ7jnwS6ARZ8f39fr+cTjoEC9IB9wFkgD8hE/lzgz8aG
94OKHuCiyT6gByn7AL89YB/QA/ktEvuAHrAP5PeR7AN6wD7AXwc4C/QAfypkH9AD+Yst+4AesA/c
2yc4C5wFzgJnQd7Lwz6gB+wDfW8gZ4E8kPeIsg/oAfsAb9rkLNCDN/bBGz3AG9DZB/RA/g+BfUAP
2AfiAPuAHmgbkImcBW0E/mwkE8lEMtE5wFngLHAWOAvmAHlAHpAHNg28K5MH5AF5QB6YA+QBeUAe
2DTwfkAekAfkAXlgDpAH5AF5YNPA+wF5QB6QB+SBOUAekAfkgU0D7wfkAXlAHpAH5gB5QB6QBzYN
vB+QB+QBeUAemAPkAXlAHtg08H5AHpAH5AF5YA6QB+QBeWDTwPsBeUAekAfkgTlAHpAH5IFNA+8H
5AF5QB6QB+YAeUAekAc2DbwfkAfkAXlAHpgD5AF5QB7YNPB+QB6QB+QBeWAOkAfkAXlg08D7AXlA
HpAH5IE5QB6QB+SBTQPvB+QBeUAekAfmAHlAHpAHNg28H5AH5AF5QB6YA+QBeUAe2DTwfkAekAfk
AXlgDpAH5AF5YNPA+wF5QB6QB+SBOUAekAfkgU0D7wfkAXlAHpAH5gB5QB6QBzYNvB+QB+QBeUAe
mAPkAXlAHtg08H5AHpAH5AF5YA6QB+QBeWDTwPsBeUAekAfkgTlAHpAH5IFNw//1fnA6X67X6+Vy
OvVtXWRJdDz43nbz9fn5gZLfrXz9/MuDsm77SWDomupvAkn2SyBPX8/gGM0KxOGLJRwmAdRwuZzP
JykhT+Mw2L/ige8EqqYbRoEBHo4C3lMTtzsVSAsVOJ2x/0kEykwz8HZPTmGjAmEMARwDUhCBvmsg
kEQowdttVo/xSwUCCOQ4hg4K2H/oplMUga+VPvhUgT0EkrxEDX0/DEPfd6igSGPtIwh8LjeSCnj7
QI5BaoCCrLapSjkEOUUV+FjoxA8R2Hr7w1FrqJq209XU2odyiurhx5rAZuv5hyCM0qwo66Zp27ZB
vCQQHcVDOYQFgfd3ZDCagBrSHEVAoqkRX2QpzuAgAvDQJfBrmERgNEFqSLK8LCFRVxqPQdA+3MoZ
qAVLApud54uNcZrlRakrxyChjzUB7YJFgakGcSGBQl4URZ5niHcJ3Fswl4HV4MtBIIc00yXxlsBG
KljJwNmoRUAhSdI0TZIY8ccDJnEchDkBYMlBydmIFALkEMW6EA4DXPx4Bg84G78YBW4KkIBGFIZH
i3eTKAUsCqgLmCgUgSSCo67A7X9fwILAO/yRXlAFlHGARoCPe8lf4qcmWBJQBbSjKHg+stDl+x78
2zoSOAdXBeQkoAAJaMhCuMS7/WeOcFKDOWMRogAJFZFPur2CYC1eDnJSUAkV2WJtkL6LXxW4U0AZ
kJA8JPjFcO0llwPOQiRUA3tjCcdme3gyQB9oEeKDKKiERd/CZ5toknEKKqEaoiNLNF356/FWhVNw
iWjsFP4sHqmMSUwaTsCenXJdeWCv1SOV8NsTL+wvwncBjw9Xdv3xrce48asfr3n25U+NZ6+f/f6/
23pWik/SgXUH/gG177luCmVuZHN0cmVhbQplbmRvYmoKMjcyIDAgb2JqCjE4NDIKZW5kb2JqCjIz
OSAwIG9iago8PCAvTGVuZ3RoIDI0MCAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdl
IC9XaWR0aCA2NSAvSGVpZ2h0IDIwMDkgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9s
YXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJl
YW0KeAHtm9l2IskORcuASZKZHJgHu/7/I/tIkUrAjK617stdOx4A2+iEdCK0rXbRf/6wcOB/78DH
x8e/bqLQi/VblYvQ9uUvNNqYHy/elbgM63Q6l1++I9G+X7HnFd99rdC88xwar5ofvFK4jO+el6u8
I5HeY29PwT1b/vJC4kkSV/EeHA8SMYn0hscK/vO0vSI/zyvlEQoPBc7xHt5vl5S8klcpmIDvb7v3
+1m7+n1TkBlNDg9SuI7PsoFWnud6zLIk8VyhKaDb1f7a3oOHtkxDEl7GMxtSAm18ng+Ho7SkIQlT
eJpCa4Dvnyt6PB5PJhM9jiyLK4V7LriAEpB/2UDxFjy1JY3RcOg52KXyo3gsYAY08dPpbDafz2cz
l7AU+qkIbXUjYAboCC2BNl7RC1vSmE7G8kFFpLO0N19L2HcuBZT/VNFFUZZlUSxMQT5I4SxwrdAK
yAEvwOIVXdkqS1OQD00KzX28SqERaCqQgdOZ4qu6Xi6XdV2ZghfRHKW//aGATsAKKEqFr2wtXSGl
kO7CY4Fezyz0BMpK4evNZrNereqqWHgKycbU1TcZWBv5GQxHlkBVr9brzXa73azXy7oszIV84DWk
+/xQQBXIgbJeWvhut5PEalkVczuIgV+FpwJZZhXMFyrA4vf7vRQsBa/Bz6Fp6jsZ2CGYBZPZvFAC
2n5/OBz2u91GLixUwzA3E+7dZrPVLDABWaAzrJWA4o/HoxSUgtUgExoXzcZ7Gfg1ShaoAos/nU5S
2K5XtZvwWkCnKIH5olQFyj8JHKwGO0jLwGq4bcgowTrJBIrKBY6nr68vpSCBpbkoATfhmYDdQxNo
KkgCqqERiGN46EHf72ESUAFf39/fSiEExqmfnpbQnKJl8FNAx/CugO7hjYCf4y8E7BDOJcjFfxCw
+L9//8oEOwYE8IB7QC/AA5jI7wV+N273eIAHtQZN7gEecA/0X230Ah7YX5G4B3jAPbC/R3IP8IB7
4H8Wphfggf0jD/cAD7gH9m9t3AM84B7o8wv0Ah7Y51i4B3jAPUif6aIX6AV6gV5IH3CkF+gFeoFe
OH9amPkAJsJEmAgTYeKfP3iAB/Y/NnEP8IB7YA5wD/DArwFMpBf8IvC7ESbCRJiYHKAX6AV6gV4I
B+ABPIAH0Q3MyvAAHsADeBAOwAN4AA+iG5gP4AE8gAfwIByAB/AAHkQ3MB/AA3gAD+BBOAAP4AE8
iG5gPoAH8AAewINwAB7AA3gQ3cB8AA/gATyAB+EAPIAH8CC6gfkAHsADeAAPwgF4AA/gQXQD8wE8
gAfwAB6EA/AAHsCD6AbmA3gAD+ABPAgH4AE8gAfRDcwH8AAewAN4EA7AA3gAD6IbmA/gATyAB/Ag
HIAH8AAeRDcwH8ADeAAP4EE4AA/gATyIbmA+gAfwAB7Ag3AAHsADeBDdwHwAD+ABPIAH4QA8gAfw
ILqB+QAewAN4AA/CAXgAD+BBdAPzATyAB/AAHoQD8AAewIPoBuYDeAAP4AE8CAfgATyAB9ENzAfw
AB7AA3gQDsADeAAPohuYD+ABPIAH8CAcgAfwAB5ENzAfwAN4AA/gQTgAD+ABPIhuYD6AB/AAHsCD
cAAewAN4EN3AfAAP4AE8gAfhADyAB/AguoH5AB7AA3gAD8IBeAAP4EF0A/MBPIAH8AAehAPwAB7A
g+gG5gN4AA/gATwIB+ABPIAH0Q3MB/AAHsADeBAOwAN4AA+iG5gP4AE8gAfwIByAB/AAHkQ3MB/A
A3gAD+BBOAAP4AE8iG5gPoAH8AAewINwAB7AA3gQ3cB8AA/gATyAB+EAPIAH8CC6gfkAHsADeAAP
wgF4AA/gQXQD8wE8gAfwAB6EA/AAHsCD6AbmA3gAD+ABPAgH4AE8gAfRDcwH8AAewAN4EA7AA3gA
D6IbmA/gATyAB/AgHIAH8AAeRDcwH8ADeAAP4EE4AA/gATyIbmA+gAfwAB7Ag3AAHsADeBDdwHwA
D+ABPIAH4QA8gAfwILqB+QAewAN4AA/CAXgAD+BBdAPzATyAB/AAHoQD8AAewIPoBuYDeAAP4AE8
CAfgATyAB9ENzAfwAB7AA3gQDsADeAAPohuYD+ABPIAH8CAcgAfwAB5ENzAfwAN4AA/gQTgAD+AB
PIhuYD6AB/AAHsCDcAAewAN4EN3AfAAP4AE8gAfhADyAB/AguoH5AB7AA3gAD8IBeAAP4EF0A/MB
PIAH8AAehAPwAB7Ag+gG5gN4AA/gATwIB+ABPIAH0Q3MB/AAHsADeBAOwAN4AA+iG5gP4AE8gAfw
IByAB/AAHkQ3MB/AA3gAD+BBOAAP4AE8iG5gPoAH/9c8OJ6+vr+/v07Hw26zqor5dDwcZP3PXrfT
0d2PNvDn215YbXaHVmC/XS9/J1BUNwLl4v0MpvO7ArPJeyUMx62AaviSBUcroVzMJqN3PBg0Auvt
3kwwAfMwCeSvTcySQLl0gePppARMoC4sgzzrvziFTxeYLSSw2VkKEjioAgnMpy7w+fQYeyYwmkig
1jGYgvbf7+IULYPP3pN70DWBXALzolYNu/3+cDjs92ZB5afoAt3HFykE7BiWq40paCmBVW2HEKf4
UKAjgX6W6xi8hrUUbG0tAbdgOGg8fHCVk4COwWpQCuvNZrvdbjbrZV0Ws+l4lA/6ycO7Ah8fEuj1
zUWlUJS1FCSxWauAyg5xPAwPrXVum8kEur1+f6AadA6mYBLr1XJZWSO097Br+z8UkAmewnxRVJUk
tOqqLOaewCCzCp4INCZ4ClIoJVHXleIX5kBbweMMVMNnpDCTQlHaKrS/FdA0QjrE+yWYCSaQ6zZO
Z/P5QhrFYmHxctAbySq4k0FD5o6dQ6MwloQ0tGYW/yOBK541X8hYCVgKKYfxZDKVxmyq8Iv4O9fw
UqApwqsYj6WhZeGpAD+CW6KeBVIKkcNwNBpJRI/D3A04x1/foisBT8GrGOT5MC2Fm4GpkR84KBG/
Xh23wXPIBgNpaOk5a+JlwGOBmBIsh56uQz/T8mCFp/0jvsn55sly8BRcQRIuYk+Wvt+AZ/tfVZEk
LA8FN+Gx/10HUzZuQ5uENrVg21y7W3ja/4lAMtIUZIRZ0Sz74q345ihcwSUs0pZFN9s/29/qSFUk
CQVF8NvxrUIrYXu3u7/a3q1scrCnFBy56xvJ65ePFxLXL19Gtm+4jmu+an/61oufEm8F3bzpn7a+
UeEbOPCGA/8BHWEY2AplbmRzdHJlYW0KZW5kb2JqCjI0MCAwIG9iagoyNDA0CmVuZG9iagozMDcg
MCBvYmoKPDwgL0xlbmd0aCAzMDggMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAv
V2lkdGggNjUgL0hlaWdodCAxMDA1IC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0
ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFt
CngB7ZvZViNJDER7wHhfa/FuDP3/HzkRmSXb4Cpj5px5u/kAxl2KlCKlSzZN//nDwoH/1YF/btbv
N7oJbl7+SuM+PL3zrEZHuN5+TuES/3Jdl/d+lohHr8HNq+YPflTIz+Wg11jpy6cUbsIjuPlsjZ8l
rvEO612XvroqPKgiCejJJvotlpSyRN6hS+Gyf4p3cD8vvUoSlyo6FK776/EUPchLMpZISaSHHgu4
eIcreJiXXknCCk0O7QKXBFK8o0exhsNvCq09aYHsn/Z3+Hg8nniNx6PRd4W2HELA+Q+0u6KneVni
RsEPdgj4BFWA93f4bDabz+f6OJ2EQtjQKdDEj0YOn88XXtJoFBoj2zNoKsgJjMbTmaKXy9VqtVwu
bhScQouAo+WgWjAVoPoVr+jCSxqLJodrCt9suArIQfk/mSq+KMqyqqqyLLKCjXxLzZAe/2JDIxAJ
yADFK7r2qiopzGc2MrVTM5bdAqmA5apU+Hqz2azrWjm4CKWglpYL3Rn0en1V4AIcv95svSRRFjkF
19DrEshNoB6wgyrA8TsvKVSlU7jWcHcQzikJqIl8hItlWa23293+cDjspVBXKQWZYBv1pJ6/8yAL
DAauYLmqau2/PxyPRysoBR3lZJzPoUvAHHnTFKQKlIDjT6eTFTa1aphPG4GWXkolNAKyYLEqlIDj
39/fpeAUdJIy4aYT7ktIJJGHsmBV1ptdjrfCfruuswnNMbR74ApUwtgWlOucwPl8toBqKGyCM0gu
tprY9KEFClmwVwHnj48PKRyyCRZINXScQhIQCZLAZncroBrcCe7FfI7dGaQ+VAaywAl8fn4qBZuQ
BC7n+FDAfdgqcDnHhyWoDTwI9xnoGKIRnhCot19L2G3czL8S2B9twd+/f2WCjwEBPKAPmAV4ABP5
vsD3Ru4HtS6q9AEe0Af6ayOzgAf+8QF9gAf0QfopDrMAD9KPVGEiTISJMNH/yEMf4AF94H+1pg/w
gD7wr4DQB3hAH+Rfh2IWmAVmgVnQ7+blX+rinsj9gDsSswAP9HunMBEP1Ab0AR78oQ/+4IH+Nwd9
gAf+Tz30AR7QB3aAPsCD1AYwkVlIjcD3RpgIE2FidoBZYBaYBWYhHIAH8AAexDRwV4YH8AAewINw
AB7AA3gQ08D9AB7AA3gAD8IBeAAP4EFMA/cDeAAP4AE8CAfgATyABzEN3A/gATyAB/AgHIAH8AAe
xDRwP4AH8AAewINwAB7AA3gQ08D9AB7AA3gAD8IBeAAP4EFMA/cDeAAP4AE8CAfgATyABzEN3A/g
ATyAB/AgHIAH8AAexDRwP4AH8AAewINwAB7AA3gQ08D9AB7AA3gAD8IBeAAP4EFMA/cDeAAP4AE8
CAfgATyABzEN3A/gATyAB/AgHIAH8AAexDRwP4AH8AAewINwAB7AA3gQ08D9AB7AA3gAD8IBeAAP
4EFMA/cDeAAP4AE8CAfgATyABzEN3A/gATyAB/AgHIAH8AAexDRwP4AH8AAewINwAB7AA3gQ08D9
AB7AA3gAD8IBeAAP4EFMA/cDeAAP4AE8CAfgATyABzEN3A/gATyAB/AgHIAH8AAexDRwP+jiwfv5
4/Pz8+P8fjrsNlWxnE/Hw0H/rff68iLTwr/0+d7Eze5wuggc99v17wSK6k6gXD2fwXzZKrCYPVfC
eHoRUA0fsuDdJZSrxWzyjAfDRmC7P9oEC9jDLDD62cRBFijXSeD9fFYCFqgLZzAa9H84hbcksFhJ
YHdwChI4qQIJLOdJ4O3hMfYsMJlJoNYxWEH7Hw9xis7grfegD14tMJLAsqhVw+F4PJ1Ox6MtqNIp
JoHXrkZ6eQ0BH8N6s7OClhLY1D6EOMVOgRcJ9AcjHUOqYSsFr70TSBaMh42H7a38kgV0DK5BKWx3
u/1+v9tt13VZLObTyWjYzx62CvxjgV7fLiqFoqylIIndVgVUPsTpODz06NwPkwVee/3+UDXoHKxg
ie1mva48CJc+fPX+nQIyIaWwXBVVJQmtuiqLZUpgOHAFDwQaE1IKUiglUdeV4ld24FJBdwaq4S1S
WEihKL0K7e8CmkHIh9heQuoE1TBSN84Xy+VKGsVq5Xg5mAbJFbRkYCzJl3QOTkEKU0lIQ2vh+G8J
fOFZ80UWcC+FwmwujcVc4TfxLW14K9AUkXOYTmdeDs8FpCO4J+pVILeC+9kK48lkMlX0ROknA67x
X7voi0BKIVUxHEkjLYXbwDzIHQ5KxN2lFKyQfBgMh9LQ0udBEy8DugVC4TUpOAmtFKzwvH/ENzl/
/3RNwTmoo7Sk4U9OP3XAg/0t910iiUgqh8f+rQ7mbEJAPigJLQc7Wrs7PO//QCCnYCctkTWa8Ofi
myKSQpKwjJclm+0f7X+xIR1nCorgp+Mjh6tE0ondf9o+WZmczB9y8CX6GwOy8W0fbyS+vmx7uP29
r3HNV+2Pdr37XaLrucfv/6etH0vypzjQ7sC/HfI+WQplbmRzdHJlYW0KZW5kb2JqCjMwOCAwIG9i
agoxODU0CmVuZG9iagoyNTkgMCBvYmoKPDwgL0xlbmd0aCAyNjAgMCBSIC9UeXBlIC9YT2JqZWN0
IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCA0MTYgL0NvbG9yU3BhY2UKL0Rldmlj
ZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0
ZURlY29kZSA+PgpzdHJlYW0KeAHtXdt24jAM7G4poRCg5MKt5dL+/0fujGQnQEMakt1z9mH80JDL
jKWxZAcI6tOTmhT41wr88tavmwCOmwdJIuxq253jCna5043iAvHbW32kC0O8OoBvOX6kCPgIf35+
ji/DmR8Y/CrDAFs1O9CFocYTO4qNO+Tw0y02VPiIfmEjTUcGI0BPhjfweDwOHE5hV9w1IeC9+5cX
gMdJknBjZpgbrQw8af2PRoQDnEwmE26comJoNiH0D/uBJxzgVzYjAQWViEo2UdT9W/dET72RIzE3
KoY2Au9/AvRsNkvTFH+noKAbtQl3CFyAF5r/CniaztnAMZ2SAVJGE+4SQAD6TzzQi8VyuVwsjMIY
XAY4204Q8EC/sYFjDiOcgSY0EYQhMAMcT/hqlWXZavVmDBdO2NVXRtgRxEAgoP3oPctytiwzhmsT
bryoCEYjEyCdL95WWV4UZVkWRZ6tYAOcgI5QISRVkwW1AYsl8eWarQQDbEhrE+66YAQYAToA/Hq9
2W63m/W6yKEDTOBQciTvEyCIkgkUgAF5WQK+2+1AURZwYg4TksR8aCZgFCGJQGAGoH/A9/s9KNYl
nFikMwwEg8kT4psGTjBO4IEZsNns9u9s+91mDRMoo/twlyBIMMMQZDn8379/sL3v4USe0YcowrdY
olMhCiavM0pYwAHgD4cDGMwE+IBxCBmF6xtcsIkAGs4hYUEHPg7H4/FAEzAQLkIdCY0EmAmgoUmw
3e2BP51OYDAfOJC0wFS8ZwEykQSQoIQC6J8ExwN8KHMMJAnow/d8ChoglTmKIIAEJDidz2eYYCI4
gYVSKwFHkQSQEAYYwRE+rAsSeDq0W4BBqAhO58/PT5gQCRiLP7rAUVwFC64JbBw7EuTlhi5cEpQM
5s4WgMAGMbhgw9CDAAZ8fX1BBBFIA8WBckHzwUFz4oc0wOKqOJAGvMlSHEgDxYG/4VAuKBeUC8oF
fpSnOJAGigP7TFa5oPmAn80rDqSB4sC+IlEuaD7Q2pgoF/DVu+JAGuDbf8WBNOBTIIoDaaA44HNt
igNpoDjgE5KKA2mgOPCnhZULygXlgnLh6eLJeb1n0r2y1gWtC1oXtC5oXcAv3LQ2SgP+0FFxIA0U
B1RAcSANLAw0JyoXLBC0NmpO1JyoOdEVUC4oF5QLyoWogOYDzQeaD2I26F5Z84HmA80Hmg+iApoP
NB9oPojZ8L/eH1Q1JHtVcBxWhHJgGcyBhTiHlgIdWox0aDnUoQVZ8TjQoJKwfOZ6UFHaSIBx7FUW
NzzNg3G0n8o+XpiXBANKA6M0Lwvr9i9OTAIXYUB5ZBJEE/oUaKYPg0pE9y9SbV808Ykk94Fluh8r
kx0W2CuG+UOFusGAmTkQmAw9S4UHJ/oWK4cJFkxerrxHuXQjYDyToVfB9sCAcOpRMj7e7FGGXkXr
ncBGAgxGQTseKZsfwwk2mBEo2W8190PV/VDh+6ZAdlyfbctFmtHgDGbGY/86wE0gAynoiDfu8KB3
cNXn7Y5fwouNgkg2O+Dnrit83+KDkOZGZLEt/nTDVwzmR8RW6DYBK2NCT9wEgvpIdVH7ixpw86od
dnn2Bui7lxd0eH3D0QHRcEkgaTijQ1LgLyvwB0RaQIEKZW5kc3RyZWFtCmVuZG9iagoyNjAgMCBv
YmoKMTIxMQplbmRvYmoKMzExIDAgb2JqCjw8IC9MZW5ndGggMzEyIDAgUiAvVHlwZSAvWE9iamVj
dCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMzAzIC9Db2xvclNwYWNlCi9EZXZp
Y2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxh
dGVEZWNvZGUgPj4Kc3RyZWFtCngB7Zxbd9pADITbhmAgXHwBzC0hyf//kZ2RtGuDvca0p+f0QfuQ
gLEGaVZrJyHf/vjhwx34pw78bI+n36kdbI+f0egJ56GxEonw0RIx/lcz4rHHSYRTm2B7ZC88UrDT
JOglDtUYI6HntMInk4nK8NhjhSaeUQgOg08biXQZIoATNfo1Dui0FZICN/GInobx+hol5JyUAl+U
98fpDM/CmE4pIUmMEGDxGj4LI8sgQQVzsj8D0Wb9Ep9ls9l8Pl8sFvg6m0ECSQznoAWEeIQj+I2D
GlFhIIcogPwzvDuilzqgwSRCFTyxrwgcpoMogPEMX61W6/UaX5dQmLMK+KApJAWa+CWCNzKgAYUF
U6AN0pFdAS2gSQDxm02eF0WR5xtRgA9IwQTua2A4K4CFVgDiEV1WVVVCAxL0IWtSuLMhCrADaMAS
8SXCt9stJaCwfNMU6IKcflOFCYQE4B/iEb3b7/e77ZYKksJ0Ku30QAAJrNaMR3hd15SAQkwBLqQF
JpMpKmABBePrA0e931WlpmAz2S8gTUALNYHtrq4Px9PpdITCtgop0MaeVqBkEJgv4AAS2B8Qfz6f
qcAiMBE2k4MCWcYK8gIJHBF/uVyowBRoo7ZCUoCTgC4WC5EA49/f36nAFDCTi9ms6aXONGobiQWb
otzVB8Z/fHxAgSmUmAf00rAAFhIExAJUoPFUOB0wEbmYYAsKnvVlgD6kACyo9prA9XqVFGoIwARm
INOQFOAsQqCEBScUcP38/ITCmSbQxTgNaQEsBBGoj20B1KACc1mR3RUNQa5FLEXpQ2QAC5jA19cX
UqAJIrAYJcCF1CvAaRiTgfRhNwOdx7ECO0xCuwS4+LTAhRZ8f3/DBJkGF3ATuRy9D9wD7wO/Jvp9
we+N/vOB/4zkPyfiFxb/Wdk9wC9d3gfuQeV9ULgH+Gui94F7wL/meR+4B94H+IDD14J7wA+6vA/c
A+8D+bzR14JfD/i5s/eBe+B9oP+D4WvB14KvBV8L4X+y/Hrg1wO/Hvj1wK8Hzf+p+jXRr4l+TfRr
ol8T/ZrY5hf8vuD3Bb8v+H3B7wv/5X0hUmV/QlR1oLDnUJxeLE3owFFUGdG8TgYE48ZxbQHNA5YG
E8j2PUfWGRwIvPEGDjS2LyCWaTjQ6ELiicQjiScqXSiMJvBEEpIDcKDyjfjkGoQmAUnlG0/ARMfx
jUJY6sc8cDEimoQLQViS1h0mLAMkCrxwJ4ilQKJgPEG6KpH1gPEMAoJYApEkpUpOlRWUnMU2sdzD
eMoVJSNiyY/vydmCkyUpywQIyj7iXFVAMFNSnlAQVBeQKmFfpYUHUF1AmgC2hfVFCmUlrPDxeAQt
TFJX+zAT7JtEZxdTpcCL0MZCulJBcGPwymSFG1J3CFcmJopWEtq3VF6auDNpZeFsZSkNCJgJwhvn
AL4hsQNwDWZboW/GDyLbqEGoeWW+C0LfpMb5/lyJ7Uns9+COOid2Xhp0bsx4w63fmsimgLFt8N7A
9xzYew/3ftNF9kQFaCN8JLlOcB/oPcF7svtSQADnkwJWhCosSf+D/Ce4L/FaAKHzhABrEPpfcuDm
Bdh+gBsYcP8CuRIYMD4gIClIFdzBQIfsoGC7OPRh940HtDHmgC0YuAcDo7l9grRASKA3A5mHqGB7
SEiwhD/eA6IlQB+4j4RsRMFvWIOtPSQS749KYK9VoRIiwu00xm2DYQJaBRQwGMxo3X/CDEwn0FKA
lZxQG3wCe203kb4eiMekCObA2WiGHNDXht6fMnaWRKhKeDguPipoFiHYkodGzDX9wN6J3yy+OZKO
unmlCbh7dHPW4JO7QH06GNF58V6ic8KoA6Yy6lw/yR34Kwd+A33s7yMKZW5kc3RyZWFtCmVuZG9i
agozMTIgMCBvYmoKMTM5MAplbmRvYmoKMjM1IDAgb2JqCjw8IC9MZW5ndGggMjM2IDAgUiAvVHlw
ZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgNzkgL0NvbG9yU3Bh
Y2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtltuy2jAMRU9bSCBA7lf4///s3pLsXBqbnJk+
tDPogYHgvSLJsuSvr499MvBvZ+DH0r7t6lJs37/D2JHz0VFEQH4Y4fU/Z/PPDjhha2exfbPn7wgr
+S9nyjiCWOhVfDqd9AsZ7wm6gmupgtgZf86IcBgCMD20Z2f4viQEAU4vb4c4cYbvDiFrQgQDmD5J
UmdJ4glvARI/nKf84ixNBSF5IGHfg8X7oaf8er1mWYbPywUIOCGJCPrAP/z7oaf6RiPDE7CCC/d8
UAB3D+/H66G+q4FBJxLJZBRAB1SP19/uj8cjz3N83kGAE0JQFwIesICYwJTe3x95oZaTkF0tDeLC
nwAXAAAIQN6fF2VZVVVZFkJQF3weNwjqkUJ1QPSQV1VNA6PIGcVFd8IOxZqwANAB+A993TRt2zZN
DQKicC5EAacTKuiaIX7q247WkoAomIUEJR0BMAJxAPkTfU8TAvIwuyD+7oVggOzGAJq274dxHIe+
bxsGcctkJ1HQYQCKIGUEdKDthmGcpmkchq6tK+QRMaQspgBAquh8lhQiA3AA+ufzCYK4gI1AGnki
9mpJNhFlaICirJuuFz0JfdfUZXEMoDnUCAB4vV50QWLwWYx6AABziBT0AwIg4DkhBiTBZ/G/AXTD
ZDmYXA6sEKIhyDaijlgGqySyko5vY67baHWg2/i2DnCc2Y6WlThKJdouvq1EA/Aw8iywklDLOAuD
1hF2kU0pXMoEzKcRp7ntcJogx3GU83zsNKIfoCFJP2E74GnGcZaOwpbEfhA6TNLStCcjBnY0aUhs
Sexprg6jDWWOgS0ZUaCpNWiK2lYPtTSeRzkOSmBXlZ7Kxs52wvG229LQn+REuzTaWChpxbqti37d
z/SXA/jBACc4WjCb7tLUdQ/VgSDAjSbsBJzgcMNgk7k0B8COFgC46YzWzuGMyYzpyvkskxFFFL0h
gGsABAGCzHfcD2S64/1uOEfH+5LACwouF7xe8Haw0u+GIPvgCXLHkVsOL0rukqSdICBXgCPINYkX
JYhVPicgCGApWB54y+QtUcS8okFu82B/C3wpeAIRwqCacq8PO2BBMArUA4rSmcl1pMX0juARVNKI
NHlcvyJQ5MSH9Z4gThChJunlx14Nb5/5xQ4yP9guDfyeBZtvgfU7jzdC/bmzLvZow4gtDf9nkPCC
zz+fDPytDPwGtJFDKQplbmRzdHJlYW0KZW5kb2JqCjIzNiAwIG9iago4OTgKZW5kb2JqCjMyNSAw
IG9iago8PCAvTGVuZ3RoIDMyNiAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9X
aWR0aCA2NSAvSGVpZ2h0IDI1NjcgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRl
IHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0K
eAHt2tdWG80SBlCbJIJyQoHo93/Iv6pHJWEsCVjrXJyLPReAhbqm+5uuTdvm1y+XBP6/E/j98frx
VD8O3n39kxpHhudL3y1xYvh3S+yHX3y89q9+PYvdWz+Obl/vXv+qwMfhl4fr2yW68e3tbfRVXu2r
fO3rSRzGx6A2uD7Enw8lTi+jFcg3tuHXh6vNY1/hZIEa324fo2/qiq/bSqJEe8+pCvnNdvvLqza8
V9fNTZbolpFvOlFgP/4qxt/c9Hq3t7d3d3fxsdfLEjmJ3RyOVsjxMYGcf4zP4Xd393lljShRc2jv
O1ahG38R6ef4GH5//9BdUSNKdBXOTKHdv+Wf4+PuD/1+fzAYxMeHnEVUOCzixAza82v3z9vH6GFe
UeMhJ7GvELc6WyDya7cfDEej8Xg8Gg1jFjGJTLLleLRAl0AGGONv8/bDGD3JK2pEiYf7Qwz55k9z
yJfaI4gCEcB9Gz+ZTmez2XQ6aRV2i8hH2d79d4UqEI8gHuD9Q95/MpvN85rNWoVuCpHjmQJtBd0E
cvx8sVgul4vFPCsM+jGFXQonZ9AK3LYJjCfT+WL5mNdyMY9VDAe7KcQaThfIFWQCw1E3frVer1dd
hdEwptDr5V44USDbKDZhFHjoD2MBi+Vqtd5sNuvVarmIRQz7D7EXckN3u/GfELsCbQ8M2gQe1+vN
drvdrNePuYjRfg1fFugPuglsNtunp6ftZtNNIWJsu/H0DLoMM4JxJPgY9396fn6OCm0KsYZ8Dic2
Y+SaEcQ2yl04jAiXq3WMf3l5iQrr1TLW0EJoHdV2wpEMqsBgGBE+rjYx/vX1NSpsVo8RYzzINoPd
VjpaIBohd8EoC7QJdAW2sYZZprjbSqdnkI2QBVoE25jA29tbTCELzKetQPZ0t5lPzCA7OQssV5sP
BeI5dAWip78sEJ3cFXiKCby/v8cUIoRWIPfidwrkU4wZfC7QnuM3C+Q+/lRgMftZgXwIhyW0x/Dj
As8RwZ8/fyKE9hh+PgMF1lsZyCBJtA9kYB+M2/FAL+gFvaAX4m88PJBB/t3dPpCBfdBr/46lF/SC
XtAL8U+iPJBB/h+RfSAD+yD/s88+kIF90P7XVy/woP0CBBOZyEQm7n4byM8FPxf8XOh+M04v6AW9
oBd++dn4Swbxi8P2gQzy98ftAxnYB5mAfSCDtg2YqBfaRvCzkYlMZGKXgF7QC3pBL1QCPOABD6ob
nJV5wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyoBHjAAx5UNzgf8IAHPOBBJcAD
HvCgusH5gAc84AEPKgEe8IAH1Q3OBzzgAQ94UAnwgAc8qG5wPuABD3jAg0qABzzgQXWD8wEPeMAD
HlQCPOABD6obnA94wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyoBHjAAx5UNzgf
8IAHPOBBJcADHvCgusH5gAc84AEPKgEe8IAH1Q3OBzzgAQ94UAnwgAc8qG5wPuABD3jAg0qABzzg
QXWD8wEPeMADHlQCPOABD6obnA94wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyo
BHjAAx5UNzgf8IAHPOBBJcADHvCgusH5gAc84AEPKgEe8IAH1Q3OBzzgAQ94UAnwgAc8qG5wPuAB
D3jAg0qABzzgQXWD8wEPeMADHlQCPOABD6obnA94wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPq
BucDHvCABzyoBHjAAx5UNzgf8IAHPOBBJcADHvCgusH5gAc84AEPKgEe8IAH1Q3OBzzgAQ94UAnw
gAc8qG5wPuABD3jAg0qABzzgQXWD8wEPeMADHlQCPOABD6obnA94wAMe8KAS4AEPeFDd4HzAAx7w
gAeVAA94wIPqBucDHvCABzyoBHjAAx5UNzgf8IAHPOBBJcADHvCgusH5gAc84AEPKgEe8IAH1Q3O
BzzgAQ94UAnwgAc8qG5wPuABD3jAg0qABzzgQXWD8wEPeMADHlQCPOABD6obnA94wAMe8KAS4AEP
eFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyoBHjAAx5UNzgf8IAHPOBBJcADHvCgusH5gAc84AEP
KgEe8IAH1Q3OBzzgAQ94UAnwgAc8qG5wPuABD3jAg0qABzzgQXWD8wEPeMADHlQCPOABD6obnA94
wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyoBHjAAx5UNzgf8IAHPOBBJcADHvCg
usH5gAc84AEPKgEe8IAH1Q3OBzzgAQ94UAnwgAc8qG5wPuABD3jAg0qABzzgQXWD8wEPeMADHlQC
POABD6obnA94wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyoBHjAAx5UNzgf8IAH
POBBJcADHvCgusH5gAc84AEPKgEe8IAH1Q3OBzzgAQ94UAnwgAc8qG5wPuABD3jAg0qABzzgQXWD
8wEPeMADHlQCPOABD6obnA94wAMe8KAS4AEPeFDd4HzAAx7wgAeVAA94wIPqBucDHvCABzyoBHjA
Ax5UNzgf8IAHPOBBJcADHvCgusH5gAc84AEPKgEe8IAH1Q3OBzzgAQ/OevDy+vb+/v72+vK8XT8u
ZuNh//6ud3N9dXlxEX7U0BMhLlebp32Bp81q+bMC0/k/BebT789gMDpaYDT43hLuH/YFYg1vEcFL
LmE+HQ0evpPB7a7A43r7vCuQGXYF7m6/DPGmKzBbtAIvr68xge4h5Azubm++eArXXYFJFIjHEFOI
As+xgniKk67A9dnHeNUK9IeTWT6GbVSI+z9tM4LZZNjPGVxfndkHl1ng7r4/HMdjiDU8PT0/Pz89
dRG0p5gFLk9vpCowGE/bGqJCXDGBWMF0HE+xy/BkgYss0LvLxzBpU9hs89q0Z5AR7ApcnNrKWeC6
d3v30B/lFJar9Xqz2azXuY+n41FG0OsyPNoLv39HgassECHkFOJBRIn1KhYwn05GrZV6LcNopSPN
lAVaCG0njPNBLKPE6nGZj2B8WMFl3v9Mgd0UYhHzxTKvxTwXkBOoDE8WyDXc9CLG/iAXMZvPF4vF
PMbHAqqTdrvg+Ay6NbQYo8J4Op3lNc37D1qEh11wrsBNL1LIOYwnk+l0Oon15/j2DPfb6HOBcCkW
drGfQldhNM5r1I3fJ/DvM/yoWm6FmELspn5MYjiK0XH7uH83/vg+/lCgTaGr0EoM4srh3fhuAWdm
EGtom+km5xCTeIhp9OPj/V3ef5dg2wXdPf/+mA83C+R2zApZortieDe+LeBsgY8VokTUiCs+99r9
D+M//VComXycQ04irja4Dc8miD4+ef8skgVqDvkw4ooa+Sl68MP4E/f/q0IEESVakfzUhtf9T4/v
ptDNIbPsauTomP1+/kf2YGWwW0RWiIfRlcjRNbyt/+z4qrAvkWXyypK74WcW0CbSgmxRtkE1+Nvj
93Nok2g12odd3S/m32Wxf+9+HodXDmmd/eow4NNXZ0f99c1PA7s//vWOr//wqcbXA469Y1fk2Le8
JoH/bQL/ARNid30KZW5kc3RyZWFtCmVuZG9iagozMjYgMCBvYmoKMjY5MAplbmRvYmoKMjU1IDAg
b2JqCjw8IC9MZW5ndGggMjU2IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dp
ZHRoIDY1IC9IZWlnaHQgMjIzNCAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUg
dHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4
Ae2a13bbWgxEXUX1QvXmkv//yDvA4ajYasla923zQbYVYgjMAXaQWE9PXDjw/zvw/Pz8zw9R7Mn1
tzInof72byQc8/PrgxqnYS8vL6c/PqJwuF+xx+vw7n2J5tZjbPOdJe4onIa/Hq8Uaf7spkK5J2/P
6Le4ik68Wf74hsIxXkEZ7Bf9/IhCCsSNGf5+vEoezuFqCo7Pxyu6dbje31PinkII5ONf3zK8Olyt
VkhkGXHTlRQO8W+Kb7Wqqt1udzodvbar6gGFiFcCUb7iI7zT6caVIpWSKDnkfZdyKPEhEPEK73Z7
5QqN9rnCFYHif8br6b1+vz8YDPTak0RRsA1XBbIAPT8er+hhXCHSSwU5GQrK9ZZA+Ncu4aPReDwe
jaRhBdlwRaA4YAM6evxQ0ZO4pHGi0KTwM4m0No8gDOx0M35S19PptK6lEQphw6GGn2VYQEeYBcTz
J9PpLC5phELaEC5cHKoiEBW0WpFAxs/m88ViMZ/PpDAaygankHefG3kikA4Ox5N6Nl8s45LEtI4i
dBKlhusCqqCqwoFRiV+t1+vVcrGYTTOFcCHO4bJAdJGaUBb2+sNxPZ0vVqv1ZrNZr1bL+SxScA3N
UJ71gjSLQGNhJLBcrzfb7XajJBbzTKHbyXO4KxAVRAKbzXa3222VhFLQQegkqyqPIYv4nUEeQjmD
TEDx+/0+FJRCPR4NohWOnXBBILqgsWCmBBT/8fERCkpBJ5kmxFCXTrguMBiOp/PlaqP4z8/PUFgv
FzJBB6kMDq10SSDbqJcWLNfbfSOw36mGaZjQtNL1DHIQQmC2CIGPz6+vr0hBAnGQDwl0OkWgVNAI
qIYiUHrxZgalD8PDnRL4/v6OFCygY4hmviegQbgokOf4mEAdbXSeQfRiNMKjAvLwREAu/oPAXhb8
+fMnTEAAD+gDZgEewMQtfy9oQaEP8CAWVfoAD+iDWv9wpg/wgD7Qf0MxC3gQ/x1JH+ABfRC/XKAP
8IA+aMXvuZgFPKAP9Ns+ZgEP4tML9AEe0AfxORb6AA/og/hoIn2AB/RBfj6RWYAH+XFtmAgTYSJM
fHrCAzyIz+DTB3hAH4QD9AEeZBvARGYhG4G/G2EiTISJxQFmgVlgFpgFOwAP4AE88DSwK8MDeAAP
4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAe
wANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+A
B/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hg
B+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA
08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8
gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4
AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSw
H8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+AB
PLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsAD
eOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7Afw
AB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/s
ADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54
GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH
8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP
4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2
A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyA
B3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gA
DzwN7AfwAB7AA3hgB+ABPIAHnoaL+8HH59f39/fX58fHbrOaTyejQa/Tbr2/vb686P5nx+bXXwKL
1WZ3ENhv18u/E5jMfgnM6sczGIwuCoyHD5bQOwiohq+wIEqY1eNhv/uAB+1OEViut/tGYC8PG4H2
XRNbRWA6T4GPz89IQAKLaWbQru6cwnsRGEtAx6AUJLDfbdcSmIxUQrt6v3mMbynQH46ncQxbKcTz
t4dTDIG3G33wmgJdCdSzhWrY7fb7/W63VQXzepx9JIHX640UAlW72x+M6qxBCrq2m/VyEYcQp3hT
4KUR6A2Gk0xhs41rs15lH8YpNh5eaeUQeK90DFHDdL5YrdebzWat+EhgNAgPyyFcFHh+lsDbe1V1
ogaloIOQxHql+Pm01hn0QiA8jFH6PUwhcKhhNJ7oIBaSUHjEaxCyD1vh4T0BpTAcqYjZfBHXfKZB
Uh9nAnkIVwWyhpZqkI0qYjqbzecK1/PTAZ3BsQ8vluAawoXIoZ7GVUe8E3h3F1wXiFbQQYTCZFIr
ejJW/KCnScwEmjY6B1JQSYW9HFNIhdE4rpHCZUCJb/r4DGfNDxbIbpQNfSUxHCl6OHB8OFASuCqQ
KWQR3ZQY6Or3y/NdQJziFQHVUIoIG5RET2n09drN/PV8J3BHQA0thZAoV6fTln+tIIEK+N3GRw/C
xkhBNrQqSUhDl75WEV+eX9rwUgl5DgeFlEiRSlc+/vbzQzI7tMkhytCVwRGez79VQOZ0VFAZkkiR
+HIWftHBUlMKRBUyIiRSQ8G69IbeLjeUmy++nimkhKMj/H58Y0MeRmah55Yrwh+JP1dQjMIz9hB+
w4CmplKFXh1Yvvrti5X/eNP3HjSOb9x/fmqdBJx/++NJN348j2t+unH/pT/6qXHpnrvv/duj78py
Aw78duA/s1fTEwplbmRzdHJlYW0KZW5kb2JqCjI1NiAwIG9iagoyNTE5CmVuZG9iagoyNDUgMCBv
YmoKPDwgL0xlbmd0aCAyNDYgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lk
dGggNjUgL0hlaWdodCAyMDIyIC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0
cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB
7ZvZcttKDETjRQuplZt2yXb+/yNvA0NQVixSSqru25mH2JaFJtADnKAS+9cvDg78vw68XM8/POga
3H72dxo/wv2FpzXuh9urT0lcw1+70732hEK8twtuP4nXH0m070tRb+ncSDwQSPEe0UZ/E0nfHFS4
xlvce3fsK1P17w8odPFt9Cgd03lK4TZeweN09Fknkd7Tk4R/U4la8il8YsdUTCIl4W8aEOjix+PJ
ZJqOi6Qkhmy4fb6HZ+lIRnl4EkNGmkA8X4+fTrM8z2ezmf7MMkmYgldhb7xXQwiofotX+Gw2t2Mi
WZZysNscEEgJtPGKXiyWy+ViIY089xzkZCqiJ4P2Avz5s7miV3akoSxSFa7QX4ILjLr41XpdFMV6
LY3FPM/Mhl4Bq0sWegeMJ1luz18VRWlHGlKQD67gPe1vvynjKpASUPy6KKuqruuqKk1BPmRT3cQD
AbsCT8Dj68aOJKQgH9oU7vZCykAVjEa6QRWw0vObZrPdbjcmUay9CHMhbvK2F1oBT2Caz1RAWdUK
3+12JlGXRUphPA4b/2gmE5CHbQWWgMXv9nZ2UqhKT0E29gtYF6mCsVWgBOpG8Yfj8XgwhboyF/LM
a2hN+PMWkoCaQBWs1krA4k+nkys0dWEXoYaWCb0C5qEJeAVKQPHn89kVNrXXoHtIE2Ul/8wgCWS5
KijkwF7xl8vFFHbbplQNs/yBQPIwWbDZHfR8E5DCfttUdg8uYBfZk4F5OMnMgrLZ7iVw+fj4SCls
JLB0Ae+EXgGByASKSgJHxX9+fprCYbexizSB1EoDArpFE9AdfBfYb81FCWgcBktob9EEDidPwFOQ
CS6gcXhCYK5BDoGvry+roRVYPCugQWgz+C6ga3heoFYbWQmdwM7v8W8E5KHHew26hn8U+P37t5mA
AB7QB8zCFzz4xAP9xUIf4IEtGPQBHtAHadlmFpgFZoFZqO1fQPi7EQ/og5JZ0D9L0wd4YP89QR/g
AX1g/9FFH+ABfWD/a0wf4AF9kH6CgllgFpgFZiF+ogoewAN4AA/ggf+cq/+UKUyEiTARJsJEmJh+
gYJZYBaYBWbhl361hj7AA/pAv2PHLOCB/aolfYAH9IE5QB/ggbcBTGQWvBH4uxEmwkSYmBxgFpgF
ZoFZCAfgATyABzEN7MrwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgA
D+ABPIhpYD+AB/AAHsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFM
A/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8
gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EA
PIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcx
DewH8AAewAN4EA7AA3gAD2Ia2A/gATyAB/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfw
AB7Ag3AAHsADeBDTwH4AD+ABPIAH4QA8gAfwIKaB/QAewAN4AA/CAXgAD+BBTAP7ATyAB/AAHoQD
8AAewIOYBvYDeAAP4AE8CAfgATyABzEN7AfwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7E
NLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AAHsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7A
A3gAD8IBeAAP4EFMA/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3sB/AAHsADeBAO
wAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ
08B+AA/gATyAB+EAPIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AAHsCDmAb2A3gA
D+ABPAgH4AE8gAcxDewH8AAewAN4EA7AA3gAD2Ia2A/gATyAB/AgHIAH8AAexDSwH8ADeAAP4EE4
AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDTwH4AD+ABPIAH4QA8gAfwIKaB/QAewAN4AA/CAXgAD+BB
TAP7ATyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN7AfwAB7AA3gQDsADeAAPYhrYD+AB
PIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB708uHx8fn19fX5cLqfDrqmK1WKWTcej
97e3V/XNS/SQf/zRSJvd4dQJnI/77d8JFNUPgbp8PoPF6q7AevlkCbNOQDV8mgVWQl2ul/P8GQ+y
JLDdH8+twFketgLThyaOJy5QNi5w+fiwBCSwqTyD6eTBLYxcYLmWgK5BKUjgfDruJVCsVMJ0Mhq8
xncXmEug1jUcpWDPP3a3aALvA33w5gK5BIp6oxpOp/P5fDodVUFTrr2PJPDW30guMM3ndg1WgxR0
jof9dmOXYLfoAq89nfhqAuNpPlt4Ddv94WjnsN95H9otuoevQwKj8TSbzZersmo2u/3+cDjsFW8J
rBbmoV1Cj8DLizJoTVANZa0iJLHfKb6pSt3BzATkYUrgxzCZQGuC1VBU9WYjCYVbvAbB+3Bsd+AW
9AmMJtPMbFyXVd1s7DS1Bkl97Al4F/QKdDWYC4UU6qZRuJ7vDugOvllwL4OoIbOLUA5lZae0+Ehg
ZBUMZJBs9CKkUBSloou14hczTWI7CPcEhKUEpWSjUpgrh9XazkrhMiDFt3dwg7P2i1bgqiAJaayW
y0XEp0m0AnoF3AVNlIpQEvOFnfk8Pf97AT0CL/LHesEVVMZMGnP9mXv+en7XBH0CrqB2NIVppiz8
ZNlU/o0TCZKDgwJ2E1KQhDR09HFi8en5d66wU5M5bRGmIAkXsQ/+eM9/KN4uslNwCRcZ64yUvoOk
pwUih6uCypCE5WHBT4Z7L6UcdBcm4Rp6to5xrH383SZoc/AUzAdTcImItvBU/1B85OASrmE6diz8
mfhbBcVEbBc+/HwvJJXh12GPbU+8Gn4PfYz3dhrXF554vil/C7j9dOixt9+7jWu/un3Lw6/+1HgY
cO8N//boe0q8hgMPHPgPkgBJdwplbmRzdHJlYW0KZW5kb2JqCjI0NiAwIG9iagoyNDE1CmVuZG9i
agozMDMgMCBvYmoKPDwgL0xlbmd0aCAzMDQgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9J
bWFnZSAvV2lkdGggNjUgL0hlaWdodCAxMDQxIC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRl
cnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4K
c3RyZWFtCngB7ZvZduJKDEXTGQAbg8EDMxn6/z+yj1QWEGIMWevet10PCRB0LJ2StqvT4emJhQP/
qwN/LtbvL3QRHA9/IxIxV98flriKOz99TOH0/ufzOr32gET33nNw96h7/a5Cel8KeomVnqYfDStc
XD6Cu++m8UASp+tb2Ot52dOTwkAOHq83duFvsaT0kELES0Ahih6lpUcucSrjVg6dQBeu4HFaemQS
noS/Z0jA89fVPXqSlmRc4uRDv0AUoAQ8fjLJYk0mpmA5hJN9EibgBqp8Ja/wPJ/ayvMsmyiJS4Xb
AmaA4nV5hRdpmYQl0SnYlW4IWAKn+Gkxm83m87m+FlNTSFWkIm4KJAMs/alFl7akYQrZZQo9AskC
E1ABii8Uvlgsl8vFokwKXoT52FeDvSYLL+NLRVe2pFHOvYqx2iEUrmz4LqDrzxRf1XXTNHVdSUFV
aCvk4x2B11crQPHzRVU1TWuraaSgKmTkaKRm6Mbyuw0pg6hgOpuXy7pu29V6vV61rXKQD+cU/N29
AraHcrCQf1Wj8I0tSdSVbNBOpI1IYPgh0DWBVaAClrXFb21JoalVhNUwtmbqawXfA3WR9jCTgCVg
8bv9fr+TQtsohVMN9wTyqSXQePzhcDAFT2E2zdM+3BRwD92CRVW3dv3D8Xg0hbW5oBrUz6eN7PEg
CeR5US5VwWar+Pf3dylYCtXSTRgW8E3QFGgP29V25/GmsNtoI5a+kT6S3gl9GRhJJhKwPVjvTODj
48MErIalu2hwS63UL6A+NAE1wXq3V/zn56cU9hJoqstt0K7dEVhtLgVUw8MC2dQzWG32ByXw9fWl
FMwEF0i9OFyCJkmDpE34KWDb4AM5YKIaUQJqo58CtTfzowLtWl1wUYJtw28FDkdZ8PfvX5ng24AA
Jto40gd4QB/ARO4L3Bs5H3BG4py43uIBHuhfvvQBHthvQOgDPKAP7DdZ9AEe0Afpt7rMArPALDAL
8b888AAewAN4AA/8TzD8f75hIkyEiTARJsLE7k/zuC90fxXGvZF7I/dG7o3cG7k3cm+0z0/QB3hA
H/jnWJgFeOCfKYOJMBEmwsSnJzzAA/uoJH2AB/SBOUAf4IG3AUxkFrwRuDfCRJgIE5MDzAKzwCww
C+EAPIAH8CCmgbMyPIAH8AAehAPwAB7Ag5gGzgfwAB7AA3gQDsADeAAPYho4H8ADeAAP4EE4AA/g
ATyIaeB8AA/gATyAB+EAPIAH8CCmgfMBPIAH8AAehAPwAB7Ag5gGzgfwAB7AA3gQDsADeAAPYho4
H8ADeAAP4EE4AA/gATyIaeB8AA/gATyAB+EAPIAH8CCmgfMBPIAH8AAehAPwAB7Ag5gGzgfwAB7A
A3gQDsADeAAPYho4H8ADeAAP4EE4AA/gATyIaeB8AA/gATyAB+EAPIAH8CCmgfMBPIAH8AAehAPw
AB7Ag5gGzgfwAB7AA3gQDsADeAAPYho4H8ADeAAP4EE4AA/gATyIaeB8AA/gATyAB+EAPIAH8CCm
gfMBPIAH8AAehAPwAB7Ag5gGzgfwAB7AA3gQDsADeAAPYho4H8ADeAAP4EE4AA/gATyIaeB8AA/g
ATyAB+EAPIAH8CCmgfMBPIAH8GCQB+8fn19fX58f78f9dt3Wi3mRZ+PR2+vL87P4EaG3TNzsDyeB
w26z+p1A1ayuBZrq8Qxmi16BcvZYCfn0JKAaPmXBu5XQVOVs+ogHk05gvdsfOwHzMAlkk7smjpJA
3brA+8eHEkibYBlkk9GdXXhzgXIpge3uoBQkcFQF2sVlEngb3MZXFygk0Ky2u70UdP3D3iyol/PC
Mnh7HeiDFxPI8qL0bdjuD4fj8Xg4JAt8F03g5XYjhcB8UamGjVKwpQRUQbXQLiYPbwo8m8A4y6dz
q2EtF/a2dr4HZkEn8HyrlU3gbTzJpjPVUK9Wm+12t9ttt9bH1aI0C8bJw95Z+PNHAq8mkBdKoWpV
hCS2GxXQVMvSR2nsHmqUeobJBNyESV4oBduIlSQ265VtweJcwYtdf0DAalAKKqJpV7baxgqwBMLD
mwJWw2gsG4uZFVE3Tdu2jeJVQExS1wX9GaQaxupmKSwWVVXbquz6M7fw3AVDAr6TskE+LKuqWqp+
i/c9PLXRtYC4pMKeIwX1glVRLmyVKf7kwM89vKSatcLItnJaSEIa5VyX1/VTfH8fXwh4Cm9jVzAJ
Wxae4lMBAxmoBm+mkeeQT6fSKPQ1z+z6nYPeBema37/a5pqAtaMpTLIsT0vhKd4LGBS4VJCENLT0
fezXP8df3RQik8scLAktD/ZwGwLN8c3rm4gJRA62GVrSsG+awYv4G9f/pmBG2PLgLjyufzs+pZBy
MC87EXvwotXl39OD4UFXhCloM5KERUe41z8Yf6ngEiZjyyS78IECPBE30q30oAh+OD5yOEu4Tlz9
Tv7Jiy6Hbkst/vzK2a3BR+eAq0eDUd9+eBWYnn57x/0nVxr3A/re0Yn0/YjXcOC/deAfsumYOgpl
bmRzdHJlYW0KZW5kb2JqCjMwNCAwIG9iagoxODcyCmVuZG9iagozNDUgMCBvYmoKPDwgL0xlbmd0
aCAzNDYgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdo
dCAyNjc1IC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVy
Q29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB7d3XYuLIEgDQGQfA
JuccvP//kVvVEsgBbHz35T4cPewyDFXdXRK21Kel+fPHpgL/hxX4+2H7ZQc/xFZ/+EWGK9HlrftS
3IqO9+9JcAl/eLdd3vwxQ/3Jd7H1y/ovvk/wPvqx2UqKexJUn8mPl+CnspWX+V71t7d78DG6Cr6k
uCNBic/PRYsR93zZ4g/x1rkHtzpwbr5ER2zrsj0/f0hwYz/WzdfhEdyut3hZZfi+BxFfOp89z+BO
p/Py8hL/7bTbkSG7UCe4NoLz4GPoJTyDX8uWOdqXHlSj/Jrh0vsMj8YjuFttr6+RoelB+eD1+Kx8
9L4K73Z7vX6/3+v1upGhSvDNCCJttePO4RE9KFuk6JYEUcRMkB242n5pPnsfnc/o4XA0Gg2Hg0H/
nCBqeD0+c0Zxq95HeLdEj8s2Gr5LcH0EGV7Hl9a7vcFwNJ5MptPpZDIeZ4JqBM0+/DCEc3wpXue1
2+tn+HRWtulkPBr0SwmyAtcOoiq+Kn4Ovj8YjafT2XyxWMzns0gwHEQJ8ii4VPBK++XQaWfzg+F4
MpstlmXLBKNhGcHP8a121fxkOl8sV+v1erVaLGbTGEGvmwfBZQ98bj+r/xg7r/NSmp9G66v1ZrOJ
DMv5bDLOClQDiE/mMfD+EKir/xjfm4jP0c/mGb7dbiPDajGfjssASgG+jY/hZ/En80WG73a7yLDO
DpQBtNvVDrjafnzx49iL4Uf1pvNlhu/3+91us1lFBXIXRgFyB1TH4Jf+Z/kjPoY/mkyz+d3+cDjs
96UDOYAsQP1j4Nr4q4O3DH8yW6w22/3heDweDrvtermYlQL8FB8/diI+d/5yHb2v43c5gNyDH46g
r/1/eopvfonP4W93h+PpdDoe9xk/zwLeEZ+7L8sX3W/iYwBV/EunOQKvt192X4nf7Y+nt7e30+mw
P8fHDrgjvuy+VVT/U3zsgPviR5NZ9P9TfNmBd8cvsvxN+1HAX8fvD6e3f/755+3teMgdIP43+y/q
r36OH98fPz/8/PT7w+9P5w95Av6b8zfnD84fnD84f3D+4PzB+YPzB+cPzp+cP94z/xrzp+bfzD+a
vzZ/zy/4Db/id/yS35p/Nf981/oN1w+un6zf4E/8iT/xJ/7En/gTf+JP/Ik/8afzHUA375+I209c
P7p+dP3o+tH1o+tH14+uH10/un50/ej60fWj60fXj7ee35DPP4jnD7h+Nn9g/bL1y9YvW79s/bL1
y9YvW79s/bL1y9YvW79s/fLlCZT8ualAeX5lPL/R/IH5E/NH1p9Yf2P9jfU31t9Yf2P9jfU31t9Y
f2P9jfU31t9Yf2P9jfU31t9c//dnzB+aPzV/av7U/Kn5U/On5k/Nn5o/NX9q/tT8qflT86fmT82f
mj81f2r+1Pyp+dMr/3669afW37p/2f3b7l93/7r7192/7v5196+7f9396+5fd/+6+9fdv+7+dfev
u3/d/euP5o/NH5s/bp7e8OeP5zf8fXjgB/yAH/ADfsAP+AE/4Af8gB/wA37AD/gBP+AH/IAf8AN+
8MAP+AE/aCrAT/gJP/L8Js9v8vwmz2/y/CbPb/L8Js9v8vwmz2/y/CbPb/L8Js9v8vwmz2/y/CbP
b/L8Js9vcv8NP+NnjR65/4af8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf
8TN+1lSAn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/GzRo/cf8bP+Bk/
42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/ayrAz/gZP+Nn/Iyf8TN+xs/4
GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/hZo0fuP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/
42f8jJ/xM37Gz/gZP+Nn/IyfNRXgZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4
GT/jZ/ys0SP3n/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbPmgrw
M37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37W6JH7z/gZP+Nn/Iyf8TN+
xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+NnTQX4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/x
M37Gz/gZP+Nn/Iyf8TN+xs/4GT9r9Mj9Z/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+
xs/4GT/jZ/yMn/GzpgL8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ81
euT+M37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/hZUwF+xs/4GT/j
Z/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs8aPXL/GT/jZ/yMn/EzfsbP+Bk/42f8
jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/ysqQA/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/j
Z/yMn/EzfsbP+Bk/42eNHrn/jJ/xM37Gz/gZP+Nn/Iyf8TN+9l/97Hh6e3s7nQ7/y/z7arPbn+P3
2/XyV/O34+n8c/x8cvf8Z394NX40uG/+sHuJPxxPp9PxeMj+zyejQe/1jvm3lyp+ud7u6vj9brOq
4zudH+avWu0SP5mV+MMxWj9k/GJW2u+0v49/LvGD+AWwXG22+yp+t11H/HgY/e+0n5+/mz8q8fkL
dLqI+N3+EK3vtzn8aZS/xD/djn98zPjX3iB2wGK53ux2+/1+t9tG9+fT0TDL387mb83flPg4gYkd
MJkvV1HBsm3i6Mnh/xT/kPGtzmu3nwVYZAXKto7qTyc5/JdSvofY4oLxy/Vzxj+3Oi/dMoB5jGC9
2WzWER7N18PP8l+P//s34p+qAvSH0YH5YrVaR3SER/PZ/Sh/K8pXWv/S/iW+DCAqGAmWq4gu4aX5
OPpa5+rfin9ud2IPZAUyQdlm0fs4eLv18G+3//DwVA2gW3bBZDabz+ez2TTCc+fH3quHH9W71v5D
XIJFAaIDsQuGo/FkWrYMPzf/nDs/q38rvk4QI4gE48lkMh6PIjyKVzd/NT72ZWSM9usOlBJEhrJF
dA6+9P5c/fc7v3pdx58TdHvRhcFwOBwM+ufw5rv34eB5F186UJXgNTOUrVe1fv7qltFfbf88gpLg
5fW1Gyl63W73NTpf9/7azru0n/F5FRxHcbvTeYkMZXvJ6Gi9+uZ/Lf6n+DpBZIgUuZXoGHs59G6F
R5LcqdmBKkGrHVvkyP+1svHLF//jrm8qkfFVgjpDK3O0Ynu+hH/TfNWBS4KoQtShxGb0T53PbpQO
ZIIYQ3QhC5lbvio/tK4cuE3vy6vzEDJBlaIOzqO26vuVQ6dJUvWgdKFKUfKU78w94echlDLW48j/
5Vanbtq68ar+XNWHKrSJ/rbzdcJzgksnmjfuCW/G8C6uenmjx1/f/hKZb3z92HfvfE7x3Wdv/V2d
49Zfe18F/nMF/gWdZAN8CmVuZHN0cmVhbQplbmRvYmoKMzQ2IDAgb2JqCjI3MDgKZW5kb2JqCjI3
NSAwIG9iago8PCAvTGVuZ3RoIDI3NiAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdl
IC9XaWR0aCA2NCAvSGVpZ2h0IDI0NzIgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9s
YXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJl
YW0KeAHt3VlTIkEWBtB2Q0DZ903t+f8/cu7NKqpQAbEjJmIeTj50u325VSKVnCr880cxA/+TGbhr
yu+rb6LNB7+powl9+uDWGj6FPn1yUw1t4r4u7Vfufq6h/uFj9vh//eUf89XP1amHqlSf3VRDG6+z
p1VU37zWhfIT2VzGHpuSn+VXy7ev5E/jGX6qSn5Y1XC9B8d41XZkO6VkJZ8quNCDT/ESfi4lKskK
ogvXh1Dnc+CZjmy3lPigqqGp4FwHqqHl1NXxyPaq0u1GDdUYLveg7X22Hm33ev3+S5R+v9eLGqIL
MYQf89H7jEfbEX4tJaqIGpoKSkPfR5Bfrnsf8Wg80oOqvGYNVQXHKbiUz+aj86XxwXA4yjIcDF6r
Cp6qZRAtXczH5EXz0fggwuNSsoaTCsoy/JIvY8rel+a7vRIfjyfTLJNxXUEchAtT2OZz8nr9bD3S
s3mU2XQyGUcPyhTECM4dgiZfeh/NZ3w2my+ilBpGwxxB6cCVfNX9mLxBxueL5SrKcpFdGMUUxDGI
VRSHoDR3OgV1+7H0Op0c/XA0mWZ8HWW1ygpiCl76cQx/zOfkR/PTWcY3WdbL5Xw2jg5UA7jQfgwr
ln49e9n7iG9L2UQPZjGFOYB4GJxbQtH/Nh/dz+aj9d0+ym67Xi/n0+hADCAeBRfz+WvjKZbuy2AY
o1+uN9v9Icp+t1mvFmUGywSU30TR4Jf5K7/zMp/Dn2Tz213Go4LtZrUsAygTcCUfizfyr4NRTP4q
en94ixId2JYB5AQcl+D59uOhm/lh5KP7u/3be5S3wy46UE3Aj/l87MT0xeyvY/TvH1He32IGVvNZ
LKFsv1MeApfa73SrfA7/NL+OI5j5WEE/5OPBE+3n8A9vVfvvMYN1Pg/AT/k4fMf8x98oH23+9bZ8
OXzZ/qf8NFbgrfky/Z/yuQJ/ld/G0ava/4gjuPmn/N//RPkrb/6sn395/Hn8+P3h96fnD88fnj88
f/z+/NXzp+dPz5+ePz1/ev70/On58zevn+XrX84fnD84f3D+4PzB+YPzB+cPzh9u8s/RpPCt8yfn
j84fnT86f3T+6PzR+aPzR+ePzh9vuH7Q+bP9Q1y+av9k/2T/ZP9k/2T/ZP9k/2T/ZP9k/2T/lLdw
Xr7/LW4ftH+0f7R/tH92/Vpsn+0f7R/tH+0f7R/tH+0f7R/tH+0f7Z+9fnDu/ZPi7Z/y7Ze8fuL1
E6+feP3E6ydeP/H6kfdv8/533v/P+x/+w/tHun6PP/AX/sJf+At/4S/8hb/wF/7CX/gLfzn5Ax6x
HOo//sKf+Bt/5I/8kT/yR/7IH/kjf+SP/JE//vrv9/FX/spf+St/5a/8lb/yV/7KX/krf+Wv/JW/
NjPAn/n7/cOD+1/d/+v+Z/d/+/tNS9dfuP7C9Reuv3D9hesvXH/h+gvXX7j+wvUXfX7CT/gJP+En
/KTRgz9/+AE/4Af8xPunun/X/bvu33X/Lj/iR/yIH/EjfsSP+BE/4kf8iB898yN+xI/4ET/iR80M
8DN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nnj/yMn/Ezftbokfuv+Bk/42f8jJ/x
M37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfvbAz/gZP+NnzQzwM37Gz/gZP+Nn/Iyf8TN+xs/4
GT/jZ/yMn/EzfsbP+Bk/42f8jJ/d8zN+1uiR+8/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZ
P+Nn/Iyf8TN+xs/42R0/42fNDPAzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yM
n/EzftbgUXzAj/gRP+JH/Igf8SN+xI/4ET/iR/yIH/EjfsSP+BE/4kf8iB/xI37Ej/gRP2pngJ/x
M37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xs1aP3H/Fz/gZP+Nn/Iyf8TN+
xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP2tngJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/j
Z/yMn/EzfsbP+Bk/42f8jJ/xs1aP3H/Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8
jJ/xM37Gz/gZP2tngJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xs1aP
3H/Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP2tngJ/xM37Gz/gZ
P+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xs1aP3H/Gz/gZP+Nn/Iyf8TN+xs/4GT/j
Z/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP2tngJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/Ez
fsbP+Bk/42f8jJ/xs1aP3H/Gz/gZP+Nn/Iyf8bP/Fz97+/gb5eP9X16/W212h2P+sN+uf/f6z2zx
Nb+YTca3vn4wHJ/Njwavt+y/+69N/v0jSgw/+h/tjwYvN+S7dT4A7FDn97vNqsr3uj/tf59LfloA
8fD2HuXtLfPzabbfe+50ru4fn0p+lPnNLgQq84fddh358bDkn67lH0t+MJqWCYwjGOWwj/xyli9f
ZfvX8vEE9lz9Apstluvtbn+Ist9vN6tlTF8cvsw/PFzc/x3zw0kMYLXZ7kvZbdarRQ6/HL7L+fv7
fAJ97uUByAHEDJQSoy+rLw9fJ9u/vz+7/6rzcQAGo9KB9WYbZRO9z6OXw+92ni7l7/IM7vGxEwcg
foNlB5bRgyjr9XIRs5/dL9MX7cfp7rf9T8k/PHY63RxAdKBUsF5H5xfzbL5afU+P1/NlAl4Gw3GM
YL4sJeJ58KP57vPT1Xw1gdmBGEH0YL6IMp9Py+S/VN1/rGbvbP/jFO6p6kCMICsoZToZl97n4o/m
r+fzCEYHYgSjcdQQZVLipff14vs+f7GXyiktR6Cu4LXUMI4yGpbB181/X3zVRqzO5xKKNRQ9eB1E
DVEyHYf+GL+er05in7s5hNeoIUuk+zn3sXby4H1bfG371SagTEFU0H+JKiKc6ZN4dvSuypz+W74c
lT/ECGIKsgtRRSmRrlo/P/l1LScVlDkoNfSidCNdOt/0/lz71REoI8ge5CxmJzIb6Rx7Gz/td/tx
24F4HJUasorIHtNnl06bb3qQc1BqiE5kNtuOxn+MlzUUI8hJzBqyE1W4TlcL78zkHztRhnCsoVSR
1URtpfGz6/YYrf5vK8g+NCX7VDd+pfWsoqqgdKEaR446S/2NH+JNBccaqvDN6bYH2d6X8PllUw38
9N9jV7/9f/pDVz/+lswvXE18/ebXGr5+/6bP60pu+lk/ZAb+YQb+CyQgsHkKZW5kc3RyZWFtCmVu
ZG9iagoyNzYgMCBvYmoKMjU0OQplbmRvYmoKMjgxIDAgb2JqCjw8IC9MZW5ndGggMjgyIDAgUiAv
VHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMjMwNiAvQ29s
b3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae3d6XaqzBaF4cReULBDRQF13/9FfnOt
AsQdbLLHOOfXy4+0zqJqQZKCxzJfX2xU4H9Wge/vf236+2H7ZSsP2fqTz5voS9vXPmyhGx8Mup99
0kL7+EF3a776tgv1A7vZ8HH9jTcNdOPDduu28LKBELeHe3bkm39oXwvffdFAG7dICNdv9fkHLXg+
7Fy5cbvpk24DT3rQ2bunJ+02HnsLb4ZgeeukdX08nkym7TaZWAuhC/ao/g7UeY9beqZtPp/r7XTq
LXgDz/L2ddt/E7ds5Js10TTw/CA8xLVzS8dhi9SCuuBDqBv4OYJm78ORDX1m6cVisVwuF4s4iv5u
4HneSmfxWNnENzURq4HZVEX000C7eppX6Zt4kqTparVK0yQ0YDUY2WnUkw+9H9iRa+Ppau3bKk0S
70EoQX0WPPTA4nbsm7w6nyi92Wy3281mvUq9B6qhzoI6/zCEe348tsF7fLPd+bZVAz4EHcV2AI8l
qPPDoRcvipdJulY8y/b7fZapAatBNJvpPLSTyB/eHUA3b7tP0tVmm2UH3/ZqQDVYxDqIb/KhevFC
g9/u9vvjMc/z42G/2/kI5nMfQP/+VRaVz6qv7qv3u+yg9Ol0UgNZZiNY6CSwAvQcQvU/5HXqWfe1
+2x/VPp8PqsBjcA6EEWzyeRNfjqdq/u++1zpoijUgEagDizjSEfgeV6VHdnJY9233Z9ORVGWpRrQ
CLYagM5iz2sA6vBf9Q8/ufXwVfyDdl+WVVWVhUZghyCJY8t7B57kvXw6epvd/pCfi6q6XC5VeVYF
dsrrCDan8Ov8SvnjqdDePa8OeAE+yOsXh5Xfh1+Ul8v1er1UlrcCWH5qv0Wejj+c/Ja37rf588kL
GM7Ad3k7+zxfVtfr7Xa7Xsomrx+B9/vX4evPr+xH6KP8Widvfn7cvw7AL/Kh/E3/i7MfwF/mq8vt
9ufPn9u1Ik/9fn/+cf7w88PvD35/8veDv5/8/eTv52/nr8wfmD8wf2D+wPyB+QPzB+YPzB8+v39o
9/+YPzF/Yv7E/In5E/Mn5k/Mn5g/MX/61J+ZPzJ/5vqB6weuH7h+4PqB6weuH7h+4PqB6weuH94+
/9ievu1Pf2b+zPyZ+TPzZ+bPzJ+ZPzN/Zv7M/Jn5M/PnN+sXuX7g+onrR56/xvP3WH/M+mvWn7P+
ntcf4PUb7AVIeP2Kj18/hOdv8fwt/Al/wp/wJ/wJf8KfmD8yf8af8Cf8CX96+fqh+Bv+hr/hb/gb
/oa/4W/4G/6Gv+Fv+CP+ir9++P8r8Gf8GX/Gn/Fn/Bl/xp/xZ/wZf8af8Wf8GX/Gn5/9/9D635/i
r/gr/oq/4q/4K/6Kv+Kv+Cv+ir/ir/jriPsH3D/g/sH3V2dTOQaD4XA05v7JnPUbrN/g/iH3D7l/
yP1D7h9y/5D7h9w/5P4h9w+5f8j9Q+4fcv+Q+4dD7h9y/5D7h9w/bSvA/WPun+MH+Al+NMOP+P+l
/P9W1u+zfp/1+6zfZ/0+6/dZv8/6fdbvs36f9fus32f9Puv3ef49foaf4WetHn194Uf4EX6EH+FH
+BHrr1h/xfor1l+x/or1V6y/Yv0V669Yf8X6K9Zfsf6K9Vesv2L9FeuvWH81wI/wI/yorQB+hp/h
Z/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+9o2ftXrE+iv8DD/Dz/Az/Aw/
w8/wM/wMP8PP8DP8DD/Dz/Az/Aw/w8/wM/wMP8PP8DP8DD/r8BmvX/iNH+FH+BF+hB/hR/gRfoQf
4Uf4EX6EH+FH+BF+hB/hR/gRfoQf4Uf4EX6EH+FH9wqw/go/w8/wM/wMP8PP8DP8DD/Dz/Az/Aw/
w8/wM/wMP8PP8DP8DD/Dz/Az/Aw/u+sRr1+In+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/h
Z/gZfoaf4Wf4GX6Gn+Fn+Nm9AvgZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+
hp/hZ/gZfnbXI9af4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4
GX52rwB+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/d9Yj1Z/gZ
foaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf3SuAn+Fn+Bl+hp/h
Z/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fndz1i/Rl+hp/hZ/gZfoaf4Wf4GX6G
n+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/hZ/cK4Gf4GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4
GX6Gn+Fn+Bl+hp/hZ/gZfoaf4Wf42V2PWH+Gn+Fn+Bl+hp/hZ/gZfoaf4Wf4GX6Gn+Fn+Bl+hp/h
Z/jZ/9vPquv1drtdL//y++eQn8smX55Ph9+dv9vs73y2Xa8+HX+y6s2nn+WjRZu/XK5XDd/6r/2n
i/gDv5vVeU3gyzpfnPI6P5+98a/J1PMbvwAqq+pyuVSV8iqf7X8+nYxf+lHIp5bPz0XIl+f8aOVP
3udHnl+mGy/guVQPqrJQPts2+dGL/Q8tP7cL+G22P57ORVGWZVGcjj78JI7U/9Fw+NR/mnyy1gAO
+anw7ZwfDjb8pZX/RX4wUH4yndsBsAGoAr5p93vr/jKKZhPLDwa9/mL5cV0A78Axz0+nU54f9nb0
k0U0n6n8T/Lfdgc35FUA68D+cFQL+fG4z1R9O/v88Cmv290//MPzw/FkMrMBpGtvQC2o89nOdr+M
dfZMxla+F3kNYB7Fy2SlEez2vmnvNnrr/nT8Ml8PQB3QCNSD3S7Lsp1qr+L7yW/DD9Xr7b/lQwc0
AmvAt816peLZwbez903eK+gjSFer9Xqz0c4V17H30fvJ93P8shSriR2BpoHFUl3wTWmL6+Ddd9/F
l/BxnbdDqBKqB4vlMknSNE1UOtUu7L7v4D/mwzmggxgv1IJtCxv7zI5d/8lzzwcE8BGogSiO1cYi
jqM6rsGHH53H4j/k/S66jsF0NtMgwmY79733F7+TVwesAa+BtzDX5unQ+Wb33yHz+DZUUHk7C6yK
2mYWnqrwGnv7k9ObDkcwdMB6YC14G3pbp3tPnW4frAfNEKwFb8Pe2S+t5tD1Fa9upMn7GJSxqIfr
dDjxnnTf2vAGrAfWgkYRNvvYvha+2+3wj4/vDXgLlrTN0p/E6w54ETzTZJv0i8HXfQk9uLfgzdT7
fp9ua+DNhGwb/ij+2ELTG3//o1pPv/AQaz55+ui+bzSh5n3fY95+rQ6/fRwPoAL/WIH/AH2okzIK
ZW5kc3RyZWFtCmVuZG9iagoyODIgMCBvYmoKMjUzMgplbmRvYmoKMjQ5IDAgb2JqCjw8IC9MZW5n
dGggMjUwIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWln
aHQgMTkwMSAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1Bl
ckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2b23biyg5FOyTB
XGxsbMydXPr/P3IvqSwDCTikxzhjnIdZD4HuWKtUS6WJdif7zx8WDvzvHXh6evrXTRR6uX4pcxna
v/+FRh9z/eZRhcuo0Wh0+cdHJPrnFXte/d/+KNE9eQ7t36Xv/CRwGf98Xq7SfW9QIj3jj3v0iy1/
dyExoHCOV5AHxxf92STSA/cV/Pt6LoW/nlfKIxTuCpzjFaDocSy9d4mfFEzA9+/Cs1jjsUv4Meyh
OylcxY/HWTaZTKbTqb5mmUmYnV0ONxUsXgmYe0pe4Qqe2TIRl0gK/twthRRvAjq9dlf0PC1pKAvL
YTAF37+P1+7zPM+LotDXubK4VriTQRxA6Wt3RS9sSWMuCVPoDzEkoPwz217RZVlVVVlKw5KQD+kQ
yvWbgDvjCbgBHq/opS1puML5EP70tcaFgAyc2v5ltazrpmnqepkU0iHMxwEBK2E2mc09vmlWtprG
FeazzoUBASvheCwHc9u/WbXter1u25Ur5PJR98lKeTcDF0gJePx6Y2vtCouiS2FQQCewEiiBZb1q
N5vtbrfbbjbtql6WC6WQZVbJOxlYG+kSuoWLqm7a9Xa72+/3u+123TZ1tcjnstGuY2qIb1VIAslC
S2C9UfjhcJDEZm0p9Gf4USAv5IASUPzxeJSCpbCsijzV4X4G7qHXoDIHdofD8XQ6HQ+HnbmgM1gd
7lxGFcYsUBXtFi3sBFvtf3p7e5OCUtAZ3ATvB78JNzzwRpZAsdAJNtu94t/f36Ww3250BhXSMnAX
teFtAbtG86I0gd3h1Amc7AyNudhdpYEMvBGK0mtwUPzHx4dSkIDO4ALekYMCU8vALbATJAGdoROY
PiAwy0NA8Z+fn0ohBOwuWhmGM9BFVhVVhOMXAa/jgwJ+ja4F2uZ3AirChYCX4dcCJ1nw9+9fmZDq
iMA/VAEThQMuEh7YxwL3AA+4B2lEohfoBXqBXlhUeIAH9t+N3AM84B74PwbSC/DA/lGYe4AH3IMx
TNSPubgHeGA/7uQe4AH3wH7wzT3AA+6B/wYEvQAP/JeBYCJMhIkwsfvNOD4X+FzgcyH9lii9QC/Q
C/TCHz4b/+CBfo2fe4AH9n9zcA/wgHtgDnAP8MCvAUykF/wi8NkIE2EiTEwO0Av0Ar1AL4QD8AAe
wIPoBmZleAAP4AE8CAfgATyAB9ENzAfwAB7AA3gQDsADeAAPohuYD+ABPIAH8CAcgAfwAB5ENzAf
wAN4AA/gQTgAD+ABPIhuYD6AB/AAHsCDcAAewAN4EN3AfAAP4AE8gAfhADyAB/AguoH5AB7AA3gA
D8IBeAAP4EF0A/MBPIAH8AAehAPwAB7Ag+gG5gN4AA/gATwIB+ABPIAH0Q3MB/AAHsADeBAOwAN4
AA+iG5gP4AE8gAfwIByAB/AAHkQ3MB/AA3gAD+BBOAAP4AE8iG5gPoAH8AAewINwAB7AA3gQ3cB8
AA/gATyAB+EAPIAH8CC6gfkAHsADeAAPwgF4AA/gQXQD8wE8gAfwAB6EA/AAHsCD6AbmA3gAD+AB
PAgH4AE8gAfRDcwH8AAewAN4EA7AA3gAD6IbmA/gATyAB/AgHIAH8AAeRDcwH8ADeAAP4EE4AA/g
ATyIbmA+gAfwAB7Ag3AAHsADeBDdwHwAD+ABPIAH4QA8gAfwILqB+QAewAN4AA/CAXgAD+BBdAPz
ATyAB/AAHoQD8AAewIPoBuYDeAAP4AE8CAfgATyAB9ENzAfwAB7AA3gQDsADeAAPohuYD+ABPIAH
8CAcgAfwAB5ENzAfwAN4AA/gQTgAD+ABPIhuYD6AB/AAHsCDcAAewAN4EN3AfAAP4AE8gAfhADyA
B/AguoH5AB7AA3gAD8IBeAAP4EF0A/MBPIAH8AAehAPwAB7Ag+gG5gN4AA/gATwIB+ABPIAH0Q3M
B/AAHsADeBAOwAN4AA+iG5gP4AE8gAfwIByAB/AAHkQ3MB/AA3gAD+BBOAAP4AE8iG5gPoAH8AAe
wINwAB7AA3gQ3cB8AA/gATyAB+EAPIAH8CC6gfkAHsADeAAPwgF4AA/gQXQD8wE8gAfwAB6EA/AA
HsCD6AbmA3gAD+ABPAgH4AE8gAfRDcwH8AAewAN4EA7AA3gAD6IbmA/gATyAB/AgHIAH8AAeRDcw
H8ADeAAP4EE4AA/gATyIbmA+gAfwAB7Ag3AAHsADeBDdwHwAD+ABPIAH4QA8gAfwILqB+QAewAN4
AA/CAXgAD+BBdAPzATyAB/AAHoQD8AAewIPoBuYDePB/zIO394/Pz8+P97fTYbdpm2qRz6bZ+PXl
eTTSzY1LnF6/XeX1dn/sBY777fp3AvXqm8CqfjyDorwpUBYPHmHeC+gMH7LgzY6wqsti/ogHk2kS
2OwOp07APEwC08mPJo6TQNO6wNv7uxJIRbAMppPxD1V4TQJLCagMSkECJ51AVVwmgdfBMr64QL5Y
NlaGgxS0//FgFjTLRW4ZvL4M3INnF5jli0pl0BmOx9PpdDwmC7yKJvB8/yK5wGSWF1XtZ5CClhLQ
CepKVUwe3hUYmUA2makMS09hf7C19xqYBZ3A6N5VNoHXTGXIS0thvd3t9vv9bmf3uK5KsyBLHt7s
hacnCby8ZtlUJlgKKoQkdlsdYFUvS2+lzD1U59xoJhM4n6GyQqwlsd2srQTV+QTPtv+ggKegQ6za
ta12ZQewBMLDuwJ2hvHYzlDYIZrVqm3bleJ1gOik7hbcziDOIBulUNV1Y6u2/Qu38HwLBgRSJV1h
uazreqnzW7zXsL9GXwXEJR1s1Kcw8xzKylaZ4nsHvtfwkmpWSV2mqRSUxKJUtLbX/in+9j2+EPAU
koJLFFoWnuLTAQYy0BnSISwHJTFXGrm+zqa2f+eg34K05/VXK24S0CGkYBJpKTzF+wEGBS4VJCEN
Lb1mvv85/suHQmRymYMloeXBHm5NoD6+u7+JmEDkoL4ca0nDXtSDF/F39r9SUDUl4SL24uGx//34
lELKQY3ZaVi0su/zv3EHw4PuEKagaiYJi45wP/9gfCj0EibjyzTdoh/irxS6ROzF1mPxvYInkSIv
wwcM/GpEV9KLvfU354cG33XJfn8ZjLr65vfYx7cPoS8a8de/e+1EfhfE0zjwLw78Bzyen3sKZW5k
c3RyZWFtCmVuZG9iagoyNTAgMCBvYmoKMjM0NgplbmRvYmoKMjk1IDAgb2JqCjw8IC9MZW5ndGgg
Mjk2IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQg
OTQyIC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29t
cG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB7ZrJQuNADEQZyGI73pck
XpLA/P9HTkndckywnXCYW/VhCMGqlqqlRw/w9sZFB/6vA38m69c7TWLt5W80LObh48sSD3H3T19T
GJ9/v6/xvRck/LP3YP/Kv/9UwT3ngj5suU/dl9YVJttbsP8oGs+TuMdL2Oa+5NNXFJwAnnThW1tQ
mkosVqHxkqvujuidW3ilEvIlfWZJwQvo9hq9dwsyo8RTAbe/hCM4cAuvVEKNEIX5DPz+mr/EB0Fo
KwhMYa0IEXD7b7bYHuFRdJAVRWEYIAkYMZ7FXA5OQPxDPLZHeOyWSEgSXkEeXBCQBCR+J/GHOEmS
NE3xb3y4K7giFgV8Akgf8WmayRINKISBnIUUMZ/BWIEU4OKzPC+KIs8hoTlIEV7gRw0SDguRwHbr
4tMM0aUsaGQ/FR4kJgKSAPJHfFlVdV1XVQkF8UF9tBRmBcQBOBhGqB/xdd3IquuyzFMo4DB3epS6
3XcfXQZSgSaQpBn2b47H0+l0PDZ1VWRpogLqwrKA9gAchAESfzrLOkGhFBtwltoLcxMFTd8E6gAK
qGrEt7JEoSpQhKQgzTTXCibgK0ACdYP4ru/7ThQkBQiEepLPBKJDoglI/DAMqgAX8hTdtC6gHgZB
FKfiwEniL5eLKjQVDsKbMNuMWoITwCGmOMLjuUX89XqFQntGDUUWR5G4uCIgh4AuStICR3DuNF4U
ulZshAkqIC5iwx99IJMIEolABgFUAIHb7SYpdCc5ByeAFFYEXBtlcgZtj/jPz08oiADOQQS8i4sZ
jAKoYCogJrwogD5MkIFYgAS+vr6QwtB7gYOd40oGcggLApjpFwVy9PGPDKriNwJ6CJMSWjmGXwr0
F1jw9+9fmHAZKEAP2AecBfKATOT3BVxQ+L2RHshFlX1AD9gH8r8+9gE9YB+kOT2gB/LDPPYBPWAf
7OVHopwFesA+2HEW8Ks29gE9kF8asw/oAftAfnXOPqAH7AP5eyj2AT1gH7g/6uIscBY4C5yFtzd6
QA/kj27ZB/SAfSAOsA/ogbYBmchZ0Ebg90YykUwkE50DnAXOAmeBs2AOkAfkAXlg08C7MnlAHpAH
5IE5QB6QB+SBTQPvB+QBeUAekAfmAHlAHpAHNg28H5AH5AF5QB6YA+QBeUAe2DTwfkAekAfkAXlg
DpAH5AF5YNPA+wF5QB6QB+SBOUAekAfkgU0D7wfkAXlAHpAH5gB5QB6QBzYNvB+QB+QBeUAemAPk
AXlAHtg08H5AHpAH5AF5YA6QB+QBeWDTwPsBeUAekAfkgTlAHpAH5IFNA+8H5AF5QB6QB+YAeUAe
kAc2DbwfkAfkAXlAHpgD5AF5QB7YNPB+QB6QB+QBeWAOkAfkAXlg08D7AXlAHpAH5IE5QB6QB+SB
TQPvB+QBeUAekAfmAHlAHpAHNg28H5AH5AF5QB6YA+QBeUAe2DTwfkAekAfkAXlgDpAH5AF5YNPA
+wF5QB6QB+SBOUAekAfkgU0D7wfkAXlAHpAH5gB5QB6QBzYNvB+QB+QBeUAemAPkAXlAHtg08H7w
v3hwvX1+fX193q6XoT01VZHGh3C/224+3t9huvm/0InHczeMAkN//qVAWT8KHOvy9QySbFYgT14s
4TAKoIZPWHBFCcggTw7RCx4EoRM4tf3FC1z67uQFgqcm7pxA1ajA9XZDAiLQVJpBsHtyClsnUEAA
x4AUIHAZOj3FDCUEu+3qMW5UIE6LSo6hhwL2H/quPdZVkcUqsFnpgw8ViOI0xzGghmG4XC7D0Lfq
YRZHITLYfCw3kgjsgyhO8lJrgAJW30kblXn6VODdC+AYCk2h62XBgZNUkN5PcaGVRWC7xzHEmaRw
PLdt13UtCjgiAXgYBnvn4azAnz8Q2Gz3+xAmSAo4CEi0ZxTQlEhAKthvxUOM0swwicC9hlwO4giJ
8+koR4AE4ijwHj4T0BRQRN0cZTW1FCCz7PpwJQOtYSc1JFJEVddN09SIRwFIINzvd9YF8yVYDbAR
CnlZVrLKMs8Rjy7SQXBdsCKgreAUiqIsywL1wwA9w3sbPQqAS3DmfUwhUoUsl5VJ/oifJvCdZ1Oq
yUmiG0MooIw0QzTCLX6hjycCmoJTUIkEC+G6vzYRHPjZRaMAanBFSA5I4oA0EH2INH8YIIOobbRQ
ghdAEVAQCbfCMED9Gv9MYKoACWhg4SMa4Fv8wzcFy0c61BWBoUISWBqs4ZL/2v4ioi3uFVRCRXZY
mMFJ/ML+3xRwmpCQPBCMJeG2/3K8S8FVgcH0GrK5hI/xKwJ3BZymk5BoC3ccWIv3NqiV0hH3BWdc
A8zMgJ2B+6hGegX1UzLX5b/y/fGZz/xzd41v4ev5e7lRQuyUdX/jpfjRiEmcfzmT8MJbP2PxzsKz
S28/aCw9tv7+rzNfl+NX6cCyA/8AFlxuCwplbmRzdHJlYW0KZW5kb2JqCjI5NiAwIG9iagoxODA5
CmVuZG9iagoyODcgMCBvYmoKPDwgL0xlbmd0aCAyODggMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyMDU0IC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5
IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4Kc3RyZWFtCngB7ZrZduJYDEUrQBgC2GBjRpuh/v8jW9L1AUKY0qv7bd+HCpWgY+lcaUcr
yZ8/HBz4/x34+Pj4tw+x0KvzW5Wr0PPLX2icY25evCtxHdbpdK7/+47E+f0Wezn67GuF9p2XUL1q
v/BK4Tq+ezmh8o5Eeo+/PYJ7ceLllcSTJL7Fp+j2XxNxifSGxwrx9fR4C/y8nF7P05DCI4Hz87vd
CO+fjymFxIsULs/3p/f7g/Pp913BsmhzeJCCC0T+Fu/hQzuj0cj+HQySxFMFFeD5e7wHf8VxDSk8
saEt4Bzv4eN0vr5GnoSV8SyFSwHxfA+fTCbT6XQyGY9NwZK4UrjjQhKwBMy/wXBk4dNpFsc0pOC3
GVfxWMANaOOzLM9ns1meZybhVZiTUYQ964fAdQGKz2fzOCHhOVgR6S793d8l/DPtFUYCln9m4UVR
lmVRzGd5FlUM+heB7wpnAXMgEvD4olzEKV3BfWhTaPvxWwqtgFtoDpiBWe7xVbVcLquqLOezLGxo
LyLe/lDAbmAyzWdFWVWrOMtqUc6jiOEg3eRjgV7Pr8ASmM3LxXK1Xm82m/XKFAov4muUbExTfZuB
NWlHFUyzebGoVha+3W5DIaUwGkYNqZ8fClgFWW4FLNcWvtvtQsFSyKZmY7TCU4HBICoorICNhdd1
7QrLqph7DXEP7VD/zMDatOeXODYLPYGthTdN4wqrKmpIJtzrZrPVOWp97Jc4zedl5Qk0zX6/b+rt
dr0srYbJWC66jfcyiDZyC+Zewa7e7w+Hw77ZbderZMJrAW8jv8SFVVDb80Og3m1MwEzwDHygfg6k
Sog+NIHCLaibw+F4PB72LuAmuIB3wlMB70MX8ArOAvV23QroGh560E99GALN/ng8nU7Hg9mYBC73
+FTAB8EzuBWwazg3wguBuMUbAb+GXwikSziXsNss/4XA/nA6/f3793S0TkAAD+gDZgEewES+L2xr
PMADX7LoAzygD+YlHuCB//yBPsAD+sB/mEcf4AF94D9TpQ/wgD6w37QxC3jgv6+kD/CAPvBfXNMH
eEAfpD/iYBaYBWaBWbC/Doo/6oIH8AAeMAvw4M8fPMAD/8Nl+gAP6AN3gD7Ag2gDmMgsRCPwvREm
wkSYmBxgFpgFZoFZkAPwAB7AA00DuzI8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4A
D+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BA
DsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CB
poH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4
AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPw
AB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlg
P4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsAD
eCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH
8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/g
ATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7I
AXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQ
NLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP
4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAe
wAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3s
B/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gA
D+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AA
Hmga2A/gATyAB/BADsCDxzzYH4+n0+l42De7zXJRzLLJ13DQ/+x1Ox37RnJx0F79/May2uwaCTT1
dv1LgaK6FajK+fsZZLO7Avn0vRK+JmeBw+F4dAusBMsgn47f8WDYCqy3ddMK1LvNKgmMXps4SAKL
pQvs94fDYb93gUXhGYwG/Re38BkC+dwENrs6CTS77doEZlkIfD69xp4LjKf5vPRr2DWWgzlgAsvS
28Az+Ow96YOuC4xMYFZWVsOurpumqevtZrU0D62PQqD7qJE6XQnYNSyWq822jrPbrFeVW6BbfCjQ
MYH+YGTXkBdWg7kQxxyIPvRbbD2838qdJGDXYCZ4CuvNZrvdbqwAv0S3YNhPHt4T+PhwgV4/XLQa
zIXV2iQ26/WysjvwCuShjc7PYQqBbq/fH1oNnoIrmITlXy08gXMfdv35DwXMBLtI62YrYrGMY/He
BJbAcOAVPBFoTYgUTKFcLKqqWiyKuILxuYLHGdhFfiqF3BXiFPNZFNAOQrrE+yVEJ1gNI+vGLJ/N
5vPCnh7xUUC04V2BBKV0D56CKUxCYmYnz9wAd8AH6U4XJbi5sXaR3ktSmGZZnke4tYDiXwi0RaQc
JtM4k8m4fX5K4EcXXTJIKXg/D62Kr/F4PLFoD4/nX+K/I/mbQKRgCi5hGnEs3OtPg3znDpOAo91d
cIXwISRGdoYW3sabAY8FpNANBbfSTgRbeHq+4ttH3n64pOA5WEfZMQ3/EOn7DT55vstdJHohESIm
ZdVbA7yOPwuYD5aERPxFCk/Pv3cFqiZScCddImmk6Hj86/i2iFAICZfx45Jt+LPnn22I64wgBb8d
rxwuEqGjp796fFiRfNCFePzlM/LqxcdLwM2rF3FXX74JTP+9+vobL28l3gi585ZW5c5X+BQO/McO
/AO/GrCfCmVuZHN0cmVhbQplbmRvYmoKMjg4IDAgb2JqCjI0NDQKZW5kb2JqCjMwMSAwIG9iago8
PCAvTGVuZ3RoIDMwMiAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2
NCAvSGVpZ2h0IDI3OTYgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUg
L0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHt3dlW
G0kSAFA3ILSvbGLH8/8fORGRpQKMJITnzFPffOjGWJFLVEqliquSf/3SZOD/koF/+vYX3fex3Q8/
6uLP4PbnU7vYH52/PamH9/Czrr3/5oQOdg/eBbf/7377XQfd47rg82qfZ3G8hxZfES34Qxft747G
10MyOsMu+pZ/yt/WXx/pYBfeRQ+6Fv10PXzTQf51GzxCIviyWvzQeuhmcGgC76NXdMQOq8UPXQ/H
l/Bh9Bp6OBxVGw5bDy0J+ah9M6jRY/aZtwyP4HHXRqPoIaeQWWyP+9pD/b4Wf5HRw4iedG08HuUc
BhV/6CB08TF8jJ6DTybTWbXpZDLOKcQM+gnsH7+bfYTH4NPZvGuz6SSnEBPoOzgSn6PX4PPFYhlt
sZhHBzGF7GA3gYPxNfs2+GK5qrZczLOHcVtBy+Af8X3yIvcxfM49otfrTbT1ehU9RAfdCvZtgvf4
zH0MX+Gbq+toV5vqoCaQK/guPlY/neXoEX0TLXrIDmbTLgNH4s/PB4NhDD+bR/jm+ua22s11zmA+
iwwMB4NdBj9twt3Br9WPc/YVfreNdnebHUQK3idQD/+Ywk/xsfrlanN1c7vd3kfbbm9vrjYxgS6D
uz38R3ws6yz23mUc+9kiF397d/9Q7f7uNlOwiAWMugTmJt4bfxnx01kNf7d9eKz2sL2rCWQGLy/r
AOyNj+fnRe69mH6sPoZ/fHqO9vSYE4gMtATEFmwr+DJ+i8+DH9OP1T9UeHTwkBlYryIBsQePxV/E
+Hn0VnHsaviXaDWBOASrOoKX/XNoz/h5+Cp9Mf3t/ePzy2u0l+fH+20soBL44Tl0JD6zH9Ov8Ogg
FxBHIA/Ad/H51J0tYvmR/Yh/i1bxcQQqfjTsn8N7x4/nXhcf039t8a+xgC4+noPfxsfuzfEz/u13
tLc+vnbgCfHL2Lxf4zdtB58U39L/Yfw8AD+Lj/S9tfm/tQPwF/G//xPtt/jawPJ3+v5vT/83+8fz
x+uH10+vn393/vb66fXT66fXT6+fXj//5vrP+cP5w/nD+cP5w/nD+ePn9VPnT+dP50/nT+dP50/n
T+fP/ATCqX6b/ur9g/cP3j94/+D9g/cP3j94/+D9g/dP3j+eH/z868UgPzs9X+bHT71/dv3g+sn1
k+sn10+un1w/uX5y/eT6yfWT6yfXT3UP7qH7/1w/un5WP1A/4a/8Ocon6gfqB+oH6gfqB+oH6gfq
B+oH6gfqB/u+/yq/uo2/+/yBz1/4/InP3/j8kc8f+fyR+pn6ofqh+qH6ofqh+qH6ofqh+qH6ofqh
+uHXfz9A/VT9WP1c/Vz9XP1c/Vz9XP1c/Vz9XP1c/Vz9XP1c/Vz9XP1c/Vz9XP1c/Vz9XP38ww3s
sR3q3772+Wvf/+b7C3x/ge8v8P0Fvr/A9xdE+Vj9VP1U/VT9VP1U/VT9VP1U/VT9VP1U/VT9VP20
z4D6sfr5mfsP3H/g/gP3H7j/wP0H7j9w/4H7D9x/wI/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/1evTr
Fz/iR/zIv3/g/iP3H7n/yP1H7j9y/5H7j9x/FHzET/gJP+En/ISf8BN+wk/4CT/hJ/yEn/QZ4Ef8
iB/xI37Ej/gRP+JH/Igf8SN+xM9+8zN+xs/4GT/jZ/yMn/EzfsbP+FmvR+4/4mf8jJ/xM37Gz/gZ
P+Nn/Iyf8TN+xs/42Qs/42f8jJ/xM37Gz/gZP+Nn/Iyf9RngZ/yMn/EzfsbP+Bk/42f8jJ/xM37G
z/gZP3vgZ/yMn/EzfsbP+Bk/42f8rNcj95/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/GzW37G
z/gZP+Nn/Iyf8TN+xs/6DPAzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+tuFn/Iyf8TN+xs/4
GT/r9cj9Z/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8bM5P+Nn/Iyf8TN+xs/4WZ8BfsbP
+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT+b8DN+xs/4GT/jZ70euf+Mn/EzfsbP+Bk/42f8
jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/42ZCf8TN+xs/4GT/rM8DP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf
8TN+xs/4GT/jZ/yMn13wM37Gz/hZr0fuP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/x
M37Gz/jZOT/jZ/yMn/UZ4Gf8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/O+Nn
/KzXI/ef8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8bN/+Bk/6zPAz/gZ
P+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/hZj0fxAz/iR/yIH/EjfsSP+BE/
4kf8iB/xI37Ej/gRP+JH/Igf8SN+xI/4ET/iR/zoPQP8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/j
Z/yMn/EzfsbP+Bk/42f8jJ+965H7r/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/x
M37Gz/gZP+Nn7xngZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/zsXY/c
f8bP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/8uP3t9+x3t7fVvXv/v7h+fd/HPj/d3
P3r9WF/d/Bl/c7Venrr/FvvjF6fFT2a7+JfXt2ivLzn/GH8xm5xw/MddfF5AdfFPD9sufjz6xh8v
hxW/aRegL6/RXrr05/jj4eXgqN+1+FXGxwFo8TH9baR/dUL8RcXPV5s6AE/PL9Gen2r5m9W8xr84
Mv55xo+jgBIH4DYS8PQc7SmWf9sO3zjmH+EH/S3jRxUfC4gd8FSt7Z48/JG+I/FnZxF/OcoE1gK2
D4/VKvtt+aPLiD+LFgX/L/6R8YPL0Sjil+uawP1DtPvavOtlpG80yvTvj/8nK+gRP6wKWk7gdru9
j7bN1W9Wbfe2+Bj9y/gVf57x48k8JxAd3G2j3WV4DD+f5PIHXfYOxQ+GuYPmi1Ws4Oa22s31Zr1a
1NEbDo7GdwsYT2fzZXZwfRPtOsOX81llvy3/0PwrPrfQNFIYHVxVy/DFbJqbt0vfkfjKYHQQKVit
15to6wyPp26tPnZfO3qf1x/HMvusIxApHOcMsodqEZ2j53Onpp+P/Hjw289dfB7C2EOtg8Uy2qIL
j73TP/eOxdcK4iBOZ7N5tVmOPspj1z93DsQ3hNl1MJlGFxE8nXwJPxxfihEpGI5iCl3LwdviDyWv
y1/bg5GCyEH1MM5W0ZW7fu/tGX93BGIC2UH1EJPI4DzumfoMz2fe3ugWHxmoDloPMYkMrugP4Qfi
+xlkDi6yh5hEBUfi61Xr2Oi5C3JuOYM2hdZFTLyid0/7Q7OvXVQd7HrISVSLhb9HH5z8Hx3kHPqW
c6rMHR19t4JuEW0dNXIf/V18l4P3HnLgaG1h30d/mELL5Mfgk8I/9bAbtv2/MnTKfz6H7f50SmT/
mF3Q7v/9X/zgh/8l9gfDeOi/OAP/BX7pXmMKZW5kc3RyZWFtCmVuZG9iagozMDIgMCBvYmoKMjcx
MQplbmRvYmoKMjQzIDAgb2JqCjw8IC9MZW5ndGggMjQ0IDAgUiAvVHlwZSAvWE9iamVjdCAvU3Vi
dHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMTgwNiAvQ29sb3JTcGFjZQovRGV2aWNlR3Jh
eSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+CnN0cmVhbQp4Ae2bW3viyA5Fu5NwNdgGG7CxDUn//x85W1UlSAZz6fnOeVv1MKRJtC3t
klarM8mvXxwc+P868Pt6/v5B11j/6K80POjn68sSP8O+/+k1iUvE2+Vc3vr9XMK/9hKcPvD3nyrE
L0xR7/HEPyWJJwrX+BT8XSN+8qFC+BJ7oMV9XI79yd59qvA93qIn8diHUeKxQvxsfHyMnsYjmZcU
/Pkh+8lEwbN4ptMk4VXcsSEJWPEWruB5PLOZSVgSSWFc4JJAiA/Ri3jmc0n8UBhtKBMI9tvz9fDF
YrlcZlm2XC4WklAST3JwgRiv8CxbhRM0XOFBESGBNzNAz9fTFb5e53m+Xq9W2XIRFdyGMRdiBTF+
HsLzIhyTiAqpCH3lM4FFtlorvCw3m01ZFvlVwVIYEdBb5qA6OBVg8eVmG44kkoL7GL78RxJXAd2A
DMhifFXVdV1VyqJYr4INk9AMDwRiAtnKnl9Vu3Dqarspc7NB3aCrTEM1lkGswBKw+Hq33x8Oh/3O
FJRCpptQO8mFuxnoDqeqQA6qfsUfDk3THA67XbWVDdlSVxlSGBcwDyUw0xWu83JbKb4Np9nv68pS
+FnDTQlBQE20WK7WhQrYH5rjseu6Y6scaqVgNdhIpJG6IzCbqYK8UAGHpu26vu+7Y9MoBV1EquGu
gHFgoi62CpRA0x77fhiGvmubwy7WEEwY6yVzxThoAnYHm0oJHLthOJ1OQ68i9rXdZDThgYAGQQJm
gSpoOz3fBAYVsd9FE751wq0HlkAQyMuNKjh2/el0Pp9PEmgPEpAJ1krBRWU8LmC3uNIlmkA/nM+f
n5/nk1yIJkjAUhiZp+SBGnkeBVTBD4Fmby5aLz4VsFsst2bBcNLzLQXZmARiLz7OINziReDr6+sq
oGt4KQNdwpiAXcPLApXaKJTgGbSH0Mx/I3DsT2eFm4Iu8j8L/PnzBwE8+KIPvvBAQKEP8MD+YqEP
8IA+iEsWs8AsMAvMgv3Llz7AA/pgo+9g0Ad4QB/YN3XpAzygD/S9dWYBD+z/lNEHeEAf2P/6pw/w
gD6wn6OhD/CAPog/U8YsMAvMArMQfjqQvxvDT6nCRJgIE2EiTPz2E9N8/4B/N7IfsB/Yb5HQB3hA
H8TfqGIWmAVmgVn4xa78Cw/0C6v0AR7Y7y3TB3hAH5gD9AEehDaAicxCaAT+boSJMBEmRgeYBWaB
WWAW3AF4AA/ggU8DuzI8gAfwAB64A/AAHsADnwb2A3gAD+ABPHAH4AE8gAc+DewH8AAewAN44A7A
A3gAD3wa2A/gATyAB/DAHYAH8AAe+DSwH8ADeAAP4IE7AA/gATzwaWA/gAfwAB7AA3cAHsADeODT
wH4AD+ABPIAH7gA8gAfwwKeB/QAewAN4AA/cAXgAD+CBTwP7ATyAB/AAHrgD8AAewAOfBvYDeAAP
4AE8cAfgATyABz4N7AfwAB7AA3jgDsADeAAPfBrYD+ABPIAH8MAdgAfwAB74NLAfwAN4AA/ggTsA
D+ABPPBpYD+AB/AAHsADdwAewAN44NPAfgAP4AE8gAfuADyAB/DAp4H9AB7AA3gAD9wBeAAP4IFP
A/sBPIAH8AAeuAPwAB7AA58G9gN4AA/gATxwB+ABPIAHPg3sB/AAHsADeOAOwAN4AA98GtgP4AE8
gAfwwB2AB/AAHvg0sB/AA3gAD+CBOwAP4AE88GlgP4AH8AAewAN3AB7AA3jg08B+AA/gATyAB+4A
PIAH8MCngf0AHsADeAAP3AF4AA/ggU8D+wE8gAfwAB64A/AAHsADnwb2A3gAD+ABPHAH4AE8gAc+
DewH8AAewAN44A7AA3gAD3wa2A/gATyAB/DAHYAH8AAe+DSwH8ADeAAP4IE7AA/gATzwaWA/gAfw
AB7AA3cAHsADeODTwH4AD+ABPIAH7gA8gAfwwKeB/QAewAN4AA/cAXgAD+CBTwP7ATyAB/AAHrgD
8AAewAOfBvYDeAAP4AE8cAfgATyABz4N7AfwAB7AA3jgDsADeAAPfBrYD+ABPIAH8MAdgAfwAB74
NLAfwAN4AA/ggTsAD+ABPPBpYD+AB/AAHsADdwAewAN44NPAfgAP4AE8gAfuADyAB/DAp4H9AB7A
A3gAD9wBeAAP4IFPA/sBPIAH8AAeuAPwAB7AA58G9gN4AA/gATxwB+ABPIAHPg3sB/AAHsADeOAO
wAN4AA98GtgP4AE8gAfwwB2AB/AAHvg0jO8Hp8/Pr6+vz/Np6NpDvS3z1XI+m04+3t/eFOCx4fVW
4NB2gwsM/bHZ/53AdncjUG1ezyAvRwWK9WslLFcXgfP589MssBKqTbHOXvFgngSaYz8kgV4eRoHF
cxNnUaDem8DpdD6fTycT2G0tg8Vs+uQWJkGg2Eig7fooMHTHRgJlHgQmD6/xwwSydbGp7Bq6QTnI
AQnEW7QMJh8P+uDdBBYSKKudauj6fhiGvj/KgnpTqI+CwPu9Rnp7dwFdQ70/tMc+nK5VBXYJfot3
Bd4kMJ0tdA3FVjXIhXDkQKjAbjF5ON7Kb1FA1yATLIWmbY/HY6sCdtVWFWSL+TR6OCrw2wQ+puai
tZJcODSSaJtmv6vtEpMF8tBG53aYTOD9YzqdqwZLwRQkofx3tQ3CpQ8fC8iEmIKKqPfhKH5bhgTm
M6vggUAyIaRQKoe63u12db1VAXIgXmLqgvESVMPEUyhMIZztpiysgDQI8RLvCthFyoVsnRdludls
9fQQLwfDIFkFIyYalmRsuIeksAoSpU6R52srIE7iSBcluEUB66WYw2q9zvOiCOHf4p8IhHaezkIV
K0nYWSk8Pj9cwS1RrxnEVgg2yIdllmUrRVt4yP8a/7OLfgiEFGTDbD5fSCMchVv9cZDvOBhNNBtN
IfgQJBY6c4WneBlwX8CuIVxEUDArdUKwwuPzPT7l/O+XJKAULAd1lI407CWkbx3w4Pkmd5X4CBJB
RFKqXg30PP4iEJNwEb2m8Pj80StI5YQUzEmTUCHx2Mf2+OfxqYigECRCaIpO4Y+ef7EhXKc90lTC
q/4Ts3sW7zlcJWJ8in4e7ldxNeP6bL2XrHr24o+7eX0WeP38Tai9cf30Kx/9W+KVmNuvSSq3n+Ad
HPhfO/AP/fbBagplbmRzdHJlYW0KZW5kb2JqCjI0NCAwIG9iagoyMzMzCmVuZG9iagoyOTkgMCBv
YmoKPDwgL0xlbmd0aCAzMDAgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lk
dGggNjQgL0hlaWdodCAxNTU5IC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0
cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB
7Z3bdrJIEEbzJ4oKeADFIx4y7/+Q81V1QzyAmpk1F7PWrotEjV91dXUj3bWFfHxgZOA/ysAfs3/o
27Xtj186aXVXD953cSW6efiehyvJp9nV83dy0bzdte2P5tWXIcQ3tsL2QfzDCwfhXS76ujJ/Ifzt
qYMfuYkH0eyxeXjl4Ebt2qHMHkQPLxz4n9VOaNq00YKLJoK+HjRy6QcDKZPW9MRiaBz0DKPpvXU1
Z+rRaDSW6VeStA48CZ0RxOYt+KCWdiJzF/JwHUGHA5erfY9dbZs2dTMXiiE6CO97dNA2r+BdnqZZ
tFQe7hx06kPnFbz6PZE6n5rleZalCsG64BPBWnqmj/J8Oos2zc2BZdEH4alewUuv1qWezxey+XzW
OLAUhGl43775tPC98ybPTV24Le4dPI6hyYPecmfyqdRluZSVZbGYWwTqQQggHAjXIdzox0Eu9aqS
rZZyoC5YCjSN2ln4qFd2lfzxOFXqFsVyWVVrWVUFByGAoU1jb65bb8mzzhdqfL1xW5uD+cwC0Dx+
qrepM5lY50uTb3ey7Wa9WioFeWZj6B3oaj9OnkTJt+ZLl+9lclCtFMA0ZtASYD24iz/ok2Scpup9
uVTr+/1Btt9vrQcL64DmkCewXz9S9qdqfrXe7g6HWnY47NSDspipAzoK2s+Bh/btyFX308yyV212
+0N9lNUHD8A6YAloj4FHvT43pM8yC79S9PXxJDvW+91GHYgJCB8DXf0Pk9dGT9lfb/eH4+ksOx1D
B2wEwwCEGdDVvg1flnv3d4o+6mt1YOUJfKn32WPdX0t/Ol9k55Ppq6UNgD5G2mO4s/1Wv9nXP3p1
IOjtEGg+A3r0aa74lX5l73z5ll3OlgDX2wC81k917HTpwwC+o9fkf2h/FSfAe/r19nD8id8H4Nf6
0+X7L9n3xQfg9+2jJ3/MH44fPj/4/NUCgPOPL+DeP39z/uT8yfmT8yfnT86fnD9ZP/ymfmD7f9YP
rB9YP7B+YP3A+oH1A+sH1g/v8hvDX6yfWD+yfmT9yPqR9SPrR9aPrB9ZP7J+fO/7T6yf2T+wf2L/
xP6J/RP7J/ZP7J/YP7F/Yv/E/on9E99//Xpy/ZQuH8unfvkV+yf2T+yf2D+xf2L/xP6J/RP7J/ZP
7J/YP7F/Yv/Uff8Su38H+0f2z9QP+P4B3z+gfkb9jPoZ9TPqZ9TPqJ9RP6N+Rv2M+hn1M+pn1M+o
n/Xd/5f6IfVD6ofUD6kfUj+kfkj9kPoh9UPqh9QPqR9SP6R+SP2Q+iH1Q+qH1A+pHz7+/zi+f8n3
T6mfUz+nfk79nPo59XPq59TPqZ9TP6d+Tv2c+jn1c+rn1M+pn1M/p35O/Zz6OfXzjx/TdPj8hB/A
D+AH8AP4AfwAfgA/gB/AD+AH8AP4AfwAfgA/gB/AD+AH8AP4AfwAfgA/+MEHH/AD+An8iPufc/93
/n8a/z+O/5+3gh/Bj+BH8CP4EfwIfgQ/gh/Bj+BH8CP4EfwIfgQ/gh/Bj+BHbQbgZ/Az+Bn8DH4G
P4Ofwc/gZ1v4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4WUuPPrj+ivvXcf8+7l/I/Qu5
fyH3L+T+hdy/kOvP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwszYDXH/G9Wdcf8b1
Z1x/xvVnXH/G9Wdcf8b1Z0f4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8LOWHnH9GfwMfgY/
g5/Bz+Bn8DP4GfwMfgY/u8DP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn7UZgJ/Bz+Bn8DP4
GfwMfgY/g5/Bz+Bn8DPhM/gR/Ah+BD+CH8GP4EfwI/gR/Ah+BD+CH7X0hOuv4EfwI/gR/Ah+BD+C
H8GP4EfwI/gR/Ah+BD/7hp/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4WZsB+Bn8DH4GP4Ofwc/gZ/Az
+Bn8DH4GP4Ofwc/gZyf4GfwMfgY/g5/9r/jZ+fItu5z/yef3Zl8fG/3xsNusf3P8F8vqXl8ti7eP
n3mnfjGbvjX/srzRn84X2flk8VfLxSxPJ6/HbxL1u0Pd6HX6i/rxK30ycn25Wpv+dJadQvpLa388
Sp7zR9fPfAO+PxyDXuHr9FPO39APGv2y2u4P9fEkO9be/XI+9fYHg17+9/Vl+jSbeQJ3+7o+ymo7
+7fDl0j+1cPPXD9Os+m8KFebrTLg5rOnLMLwPdF/mj4Zp+lUCViuN+qBm2ff0zcZJdJ/yrr4lemH
yXiS5t6B9Wa328t2NnlLzb4m/d36P3+CXgnIp3ONQLXebney7Ua9LxeavXH4vPU/9/zI9V/DZDSe
ZFMLQA42W5nLCxu9yThJhjF7fXpVIC0Ay4AcuFWK3iZ/qu4Pn+k/VcK2ANJMPSjKcrWqZCuTW+81
+W32hex1tR/1NgWUwkVRLt1MPstj86/0HoAcKAWLQjGUZWFyi96b79YLxDiC8Q5oCN2BPLhJba23
cr3zJvmB4kR9yIAc5EribC6bBbnNnfbYe6q3FGoQMnlwy731eOiGud+t1xSwOeQpkIM0kwuJs1TB
x+ijvF/vFEIRaBrIQzBT29D7kWtTv6f/ngIdnoPhMLE+yIWZq9X3K3lH+z4C6kDogTyMZPKhpi1z
3nozd1pudvPAA3MHlgOFoCBc7OrwudEXvTu6cSAPwYf9HlwHf9Po9RPXWxfUB4VgQURxbPxp6+bp
xoO7MDfyZj0P6s7UtVH8OLAYWjP1O/IYgE0kN3MQHwbPXSPfNu4PmvdF2S/VbQ7MzZ1Wr9w21fes
CeH+d9/7H16/F/rzh3c9feHexdM39/yx8dHzZ14mA/86A38DAL3SDgplbmRzdHJlYW0KZW5kb2Jq
CjMwMCAwIG9iagoyMTUxCmVuZG9iagoyNDEgMCBvYmoKPDwgL0xlbmd0aCAyNDIgMCBSIC9UeXBl
IC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCA2MSAvQ29sb3JTcGFj
ZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2WS3LEIAxETSbJ+P4njtQtiU+VQcQ1O7MYMKYf
LRmUHMfTngx8PgOllH9vItratilVGqMdRoj6QRrRy5qnJKEqvtjqRCajsdrUA2RtwgC9XJ5sfglo
9S9vpPHVgsBFELgaPWYShKqH7JstEEtCrzc5OmGoiRUhALJedT9sOmwJ12kAQDai3uTaBQErLgGu
FwC3/2Ujgh6mBAfAgKhML5158CxcWagAhC/CtzblKAEWlg48A7o/5IZgGszCzAEAaoD7n+dJD7Sw
BxCl6I1wE/Duk5AMoXFwGzB8hrwDJAFZ3M/B+BlxEBJfodhNGM6BGpCTZPdxFoIAcBV4ksX97kkk
QC5Texdk7Bd6eZSLW0Ax0GsgR8AC0JoyBRx+m3ifvZ5AbhVlridALVhJIULS1wUw++uCDSwNKGoQ
Q15r4tU30PkAwAMLo5pnSV3W1CAgCg0jmoaV0bsHEhwBtclnCWBsjMIIlOLX5rlo+msrcSAC4JNT
pb/0xdoLoX30JYu+lXTjha553cn8oXmfGLoq+oRmXBLaG/9sjszn+cnApzLwB4joDxcKZW5kc3Ry
ZWFtCmVuZG9iagoyNDIgMCBvYmoKNDIzCmVuZG9iagozMjMgMCBvYmoKPDwgL0xlbmd0aCAzMjQg
MCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyMzc4
IC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9u
ZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB7ZvbdhpJDEUTg7lDA00DDd1c
8v8fOZKqDtiYW2bNwzzseogdG52WTkk7ikN+/eLgwP/agd/fzl+n+i06/eYvNO5Ex5felXgUb19/
R+IS/vH16KuvFfIrvwanz/M3Xil8je9cT2i8I5Fe4y+P4G6c+NS/9lrhW3yKzr+ayFXicRkhkB5v
gZ/X0+1+VXgkcHl+pxPhvcsxpSyRXvNA4fp8f3qv17+cXu+iEEY8EYj8Ld7DB3aGw6H92u9LIlt5
T0EFeP4e78GjOK6RFMLJeOEdhVzAJd7Dx+mMRkNPwsq4KDwQSAXE8z18MplMp9PJZDzOCu5kaoeH
ApaA+dcfDC18Op3FMQ1XsDI8haTwWMANyPGzWVHM5/OimFkWnoM5qRR+CLgDKkDxxXwRJySiChOQ
ws1kZwdtAlIClv/MwpfLsiyXy8W8mEUV/d5V4LvCRcAciAQ8flmu4pSu4D6EC91s412BnIAZOCs8
vqrW63VVleVibj6YDfkq43nfbMgZhIDdwGRazJdlVW3irKvVchFFDPqpFx4LdLt+BZbAfFGu1uvt
tq7r7cYVUgp+k1bDXQG7g49k4Wg8nS2Wq2pj4bvdLhTKSCHXYK80idsSLgJWgTlQVuuthe/3e1eo
Vu6C2Rit8FSg348KPIHawpumcYV1ZS6YjakbHwlYm3b9EsdmoTmw3e2apm1bV9hUUcNomNr5QQkW
7wJmgVfgCbTt4XBoG0+hNBsn45cC3kZ+iYvVelPvm8PheDwe2v1uu4l7SAK5lX6aqDbyS/QKGgk0
+9oEzAQX8IF6XIJPol3CfGl3sGva4/F0Oh0PLuAmuECY8EzA+9AFvIKLQLPbZgFdw90+yI3sfRgC
7eF0Op/Pp6PZmASu9/hUwAfBM7gVsGu4NMILgbjFGwG/hr8QCA+vJezr9b8QOBzP5z9//pxP1gkI
4AF9wCzAA5jInwu7Bg/wwJcs+gAP6INFiQd44D9/oA/wgD7wH+bRB3hAH/TiB9vMArPALDAL9s+d
8AAP/N9s6QM8oA/SW0CYBWaBWWAW7E1leh8Kf1/g7wvsSOyJ8AAm+puN6QM8oA9+2Ttn6QM8oA/s
TfjMAh74/8WgD/CAPnAH6AM8iDaAicxCNAJ/NsJEmAgTkwPMArPALDALcgAewAN4oGlgV4YH8AAe
wAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8
gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4A
D+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BA
DsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CB
poH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4
AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPw
AB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlg
P4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsAD
eCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH
8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/g
ATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7I
AXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQ
NLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP
4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAe
wAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3s
B/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gA
D+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AA
Hmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8
gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4ADx7z4HA6nc/n0/HQ7uv1ajmfTUaDfu+z
2/n4sMZRD8XHn420qfetBNpmt/1LgWV1K1CVi/czmM3vChTT90oYTS4Cx+Pp5BZYCZZBMR2/48Eg
C2x3TZsFmn29SQLD1yb2k8Bq7QKHw/F4PBxcYLX0DIb93otb+AyBYmEC9b5JAu1+tzWB+SwEPp9e
YzcEpsWi9GvYt5aDOWAC69LbwDP47D7pg44LDMfTYl5WVsO+adq2bZpdvVmbh9ZHIdB53EgSsGtY
rTf1romzr7ebyi3QLT4S+PgwgV5/aNdQLK0GcyGOORB96LeYPbzfylnArsFM8BS2db3b7WorwC/R
LRj0kof3BH7/doFuz65hPLUazIXN1iTq7XZd2R14BfLQRufnMIVAp9vrDawGT8EVTMLyr1aewKUP
O/78hwJhwti62YpYreNYvDeBJTDoewVPBJKLKQVTKFerqqpWq2VcwfhSweMMPjqdT0vBXLCLcIU4
y8U8CsiDkC7xfgkm4BdpKZiPxXy+WCzt6REfBUQb3hUwLLkvcQ9ZYRISczvFzA1wB3yQ7nRRglsW
8BRSDpPpdDYrigi3FlD8C4FcRFQxMQk/k8k4Pz8l8KOLrhl4DdZMXoT5MBqPxxOL9vB4/jX+O5K/
CUQKpuASphHHwr3+NMh37jAJhIuWQs4hSwztDCw8x5sBjwWk0Ikq3Eo7EWzh6fmKz4+8/eD3kFJw
H6yj7JiGf4j0/QafPN/lrhLdkAgRk7LqrQFex18EzAdLImt4dA5Pz793BaomUvAyXCI0cnQ8/nV8
LiIUQsJl/LhkDn/2/IsN4WUEKfjteOVwlQgdPf3V48OK5IMuxOOvX5FXLz5eA24+exH35ds3gem3
X77/xqe3Em+E3HlJVrnzHb6EA/+xA/8AL/mIJwplbmRzdHJlYW0KZW5kb2JqCjMyNCAwIG9iagoy
NjEzCmVuZG9iagozMTcgMCBvYmoKPDwgL0xlbmd0aCAzMTggMCBSIC9UeXBlIC9YT2JqZWN0IC9T
dWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAyMjM0IC9Db2xvclNwYWNlCi9EZXZpY2VH
cmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgPj4Kc3RyZWFtCngB7ZtZW+NYDESBhqxOnNhxEjsL0P//R07p2pUF4hBmvnk794Gto7JU
VzqoG/rpiYMD/78Dz8/P//YhCr04v1a5iPWHv9FwzJf3j0pchr28vFx++ojE6fWKPZ/TV3+W6F56
ju0+6r7+k8Bl+J/zSSKPSLSvSS9P0a9x0kcXEneSOMcrKAX7jT4PifYF/Qrpz/W6NvztfNo8rNAr
cI5XgKIHPvo4VfKTQgik50e4goc+g0En0Sn0pHAdr+DRaDQej/V2OAyJSOKeQldAuKfHt9GTOKEh
CSuk193KwQl08ePxZDJtjzQkEQp3U5BAa4DqH44iPMuy2Wymt9PI4kqhJ4O4wPAv4hU+m83jSGMa
SUihtUGPuiswGKR4hef5YrHI81ZCAlKIIm4JhAGqIBKQgfF8hS8WyzjSmCuJiyLixdc5xFdOAiog
4hVeFGVZFsUyKXRFdCl8UTgJ6Ap0/5Op4pfLslzFKcukMJ10LnQjcZVCJ5AqSAnM82VRrqpqvV5X
1SopZEqhcyG9vFdgNJpEARG/3sRZVytVMddVpBRUQ79AVKAryJRAit/Wdb1tFfKZUhgO4yZ7BKKL
1ARRQSSg52+3ddM09Xa7rsoiUtBFRDu2A/GthFYg3WE4oPzrutntdk1db6KI+cw1/CiQ6QrKarNt
mt1+v981TaSwjBpaE3oF0iWEBbkqWCv/3f5wOEghpZDP0z3cbsawNSxQH6oJMlWw2qT44/EYCtv1
qjMhzcP3br4WmOkOKgnsD8f393cpNNtNVS5kgjohXcO3cbCABiHaMCzYNrtDJ3DYqYYwIQRioPoz
iEkOgbBAAsf3j48PpSCB9aoViJm+L6BJTAK1HLSAaugExg8IaBIjAwko/vPzUylYIHrx5wymaoOb
AurFRwXk4bcMqrjHXwhsmv1FCXENvxc4yIK/f//KhHSPCGAijcQswAOYyPcFvjfu2Q+0KdMHeKBl
mz7Ag4o+0D8f0Ad4EP+MRB/gAX2QzfEAD/QTHvoAD4b0gX7URh/ggX7aRx/ggX5uTR/gQfweDX2A
B/RB+n0mZgEexO+10Qd4QB+kX3BkFuAB3xvbX/ZlFpgFZoFZOP/qPX93hokwESbCRJj49IQHeBD/
0ZE+wAP6IBygD/AgtQFMZBZSI/C9ESbCRJjYOsAsMAvMArNgB+ABPIAHngZ2ZXgAD+ABPLAD8AAe
wANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+A
B/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hg
B+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA
08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8
gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4
AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSw
H8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+AB
PLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsAD
eOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7Afw
AB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/s
ADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54
GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH
8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyAB3YAHsADeOBpYD+AB/AAHsADOwAP
4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gADzwN7AfwAB7AA3hgB+ABPIAHngb2
A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggaeB/QAewAN4AA/sADyAB/DA08B+AA/gATyA
B3YAHsADeOBpYD+AB/AAHsADOwAP4AE88DSwH8ADeAAP4IEdgAfwAB54GtgP4AE8gAfwwA7AA3gA
DzwN7AfwAB7AA3hgB+ABPIAHngb2A3gAD+ABPLAD8AAewANPA/sBPIAH8AAe2AF4AA/ggafh9n5w
fP/4/Pz8eD8edvWmKhbzbDIeDt5e/7y8KMCx6f0NgXq3Pwnsm+36dwLFav1VYLV8PIPZ4qZAPnus
hMn0JKAaPmTBMUpYLfPZ9BEPRp3AttkdOoHwsBUYj340cdAKlFUSOL6/K4F0CWVkMB4NfriFtySQ
LyVQN3ulIIGDKthU5aIVeLt7ja9JIJPAalM3Oyno+ftdWFDqEiKDt9c7ffAnBMaTLI9r2Ooi94fD
Yb9PFrR9FAJ/+hvJAvNFUa43cmEfRwmogiJusfWwV+AlBIbjyXQeJmyiiDhN3EGxnOsWfQk9rRwC
b8PReDpLNaiIummaulYfl1GBLBi2Ht4UeH6WwGsITLKUQrXZSqLeqgAl0PbhMHkYo/N9mEIgmTCa
ZJFCuVrLB4WvdQXLuMSTBfcFooZIQQrVOk61UgF5zLI97BWIGgZD2ZjN5otQWFVVtVL8Mg8LEwy6
LrhdQlvDUN0cRSyKooxTxPNjEp1AWPhF4Cl96aUVSDepIvLFclkUxVL1Kz6uYBB30HbBVwFxSRqd
QlyEcgiJOHmKv07gimfdJycBNVNSkIQ08rken8mAVIAT6BVIRbwNk8I0y2ZxIryNbwv41kXnDFRD
aqZBymEynUoj09vJOJ7fzVGysCeDJBDtGAqj8XjSHoW3BqYC7gpcKkhCGjp6P0zPP8df9/EpnbjL
KCJyiCR0UnAKjyHQDfY+P1RCwApJIokMdHT/F/E9z79SSEm8RR4K7sL9/P74NoU2BynoRHA8XNlH
eMr/Rg+eTDgryIiwojvxyUPxnQ2RQ3h5PukLyaK7zz8Zmay0SnqvN4/FO4ezRBvfRf/4/IscIqR7
+Cn6jv9nH/XROeDLR1evuvvJl8D207sR3//wi8b3FzzylU7kkZfyGhz4bw78Ax/UqJ0KZW5kc3Ry
ZWFtCmVuZG9iagozMTggMCBvYmoKMjU0MgplbmRvYmoKMjg1IDAgb2JqCjw8IC9MZW5ndGggMjg2
IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMTk0
MSAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBv
bmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2d2XqjSAxGsznGZjF4xXt6
3v8h55eqACfBmKS/uZqji24n7V9SqQpM6Rj66QmjAv9JBZ5b+7n7Vtq++ImPVvTpxVgPn0Sffhjj
oRO8tNb97qGH5q2tNr5ofv/AQXxbEL1GCz/Ffxp2EN5kgkYc/rbfhH8b1PtbGvVba+aj9TDgoJHb
+yWeRNPL6MHfcM9ByE9xGvV7tMkkeHgwhi66x5Z46qYX0UPjoD8D03t0y9zESbTpNHjwIti7+vT2
e9PbyCU39SxaksiDpWAOwvu+e2jlr28W3NTzeSqbz2czeVAKVsXo4L4+RDd1mmZuciEPMYNBfcxe
0S12lueFLM8zy8EcdCPojy+9wrtcsfNi4VbkmTw0DkIC9/VWO+Vu6rKsZGW5kAc58BHEAnzRx+I1
4aO8WrpV0UEcQd8i6PSqvQbv0avVai1brYIDjcDn4JFexUszJV+t1hu3tTvI0lABO5A83O0Q2smf
TKYafZYH+XYn227cQZ6pAtPJpHcJNPpQ/DQvymq53ux2tWy326yXVVnkXQK98W3pu36eKvxytdnW
e7d6u1kty0Wezr2CzQC+5C+56616Cr9ab3f7w1F22O+2NoJCA0hsEds7lUGv3tZOmim8sq8Px5Ps
eKhtBOUiVPC+3k4brs8XFr7eH09n2em4ry0BDcBmoD2IvsUPeq29XOlb+NP5IjufLAENQAXQGhzS
vym+zZ6nvz+eg/583PsAfAbf22OoJ76V38u3VPqH4/lylV3OqsBWBbAC2kEYV0Cv3ldP4cM/nC7X
D9n1ogFYAVw/faD36bPh72/1GkDQJw/1OvYUX/rj2cMrAS+A6W0FPYqv8nf6P7JO7ytwhH6hxRvi
3+qXYQWP0vvqUf6t3ibgZ3qVz+UaQJiA3+j/kaGnfn4C+MX6Y/1w/HD+4PzB+eN3n9+cPzl/cv7k
/Mn5k/Mn+7fx+29rX9j+l89PPj/5/OTzk89PPj/5/OTzc1z/f+H4g+sHrp+4fuT6ketHrh+5fuT6
ketHrh+5fhzz/Rmun+k/0n9l/8j+kf0j+0f2j+wf2T+yf2T/yP6R/SP7x+H7ZxK7+wn+xPd3+P4S
39/i+2vaQLN/Yv/E/on9E/sn9k/sn9g/sX8KzyDpf/4C+0f2z/QP4O/wd/g7/B3+Tv+E/hH9I/pH
9I/oH9E/on9E/4j+Ef2j3ue/6vGtkyn9M/pn9M/on9E/o39G/4z+Gf0z+mf0z+if0T+jf0b/jP4Z
/TP6Z/TP6J/1/P9R9A/pn9I/5v5F7t/k/lXuX+X+Ve5f5f5V7l/l/l3+/03/D2DpH9I/pH9I/5D+
If1D+of0D7l/uavA8/Pzywv9Y/rH9I/pH9M/pn9M/5j+Mf1j+sf0j+kf0z+mf1zz/WP4AfwAfgA/
gB/AD+AH8IOue/70RP8cfgA/4fklPL+F59fw/BqeX8Pza3h+Dc+v4fk1PL+G59fw/BqeX8Pza+BH
8CP4EfwIfgQ/gh/Bj+BH8KOuAvAz+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4G
P4Ofwc/gZ/Az+FlHj7j/Cn4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az
+Bn8DH4GP4OfdRWAn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+D
n8HPOnrE/WfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ
/KyrAPwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMftbRI+4/
g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+BnXQXgZ/Az
+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Czjh5x/xn8DH4GP4Of
wc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP+sqAD+Dn8HP4GfwM/gZ
/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn3X0iPvP4GfwM/gZ/Ax+Bj+Dn8HP
4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/hZVwH4GfwMfgY/g5/Bz+Bn8DP4GfwM
fgY/g5/9DT+7fvyRfVx/w192++O50Z+P+92P+vfVavNVv1lVi7H936JfX4zTz7NGf7l+yK4Xy1/x
i2w+ov86i3o7AUf96VBH/Sx50L98n7p+GT7ALlfZJZbf4s+m75PB/l/Ql6bXBAS90q9V/nKE/s31
ebn0CTidL7LzyYe/LHOP/zYQ/9X0M12AaQK2KsDpLDtp+NswfTPlL/nd/p3pE9drAFoBJ7ewemz6
Vb4B/cuL9O+JFdAHUB+Obl79MPzkXfoXmRoGXfcgfv/Y9JP3JJF+UXkC+4Ns74u3Wqh8SWLl79c/
2w5c+qlfgVsC27rey2ob/bIMqzfoFf1bfNe/mn42zy0BOdjVsp3JFT6f2/AnsXr39JOpraC8KDWC
zdZts15WZeGzN50M6uMAZmmWL8zBeiNbm3yRZ179MPx7+bvellCqEsrBys3kRZba4o3lG9B7BeVA
JSiraimrTK5D10ev1Rdm7/P4NZfm02dAJZxZBubBTWqLbseOp2/vvJ388DrqbQq1hoKDYiErolxr
pz32hvQ+Ak1immW5W2bRE5u79ti5ow9NnMbBPJULidP5N/l9vXdBVIJpohSiWfAw+HvFi/ULa1Al
UA3cw8zM1V67du31xG9mQAmYA/egJExs826lN7kdeb3qoFcF3EHwoCRM7Oob+R19m4HV4M08KAkX
q/B+1hqKbqvAcrMMQgrBhRJ3dXPY38veV5E7aDxYEm4aeKe+m/wXB5ZDa5aTV24wejOCOIgwDo/c
qh/pYw06DxZYFgb2WH2TQqjkrXiU/JOHJmz42ys05o/PsuanMcr2PY2o+bv9hx+8+BvtD8Lw1v9x
Bf4FUP9FRQplbmRzdHJlYW0KZW5kb2JqCjI4NiAwIG9iagoyMzA2CmVuZG9iagozMjcgMCBvYmoK
PDwgL0xlbmd0aCAzMjggMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGgg
NjUgL0hlaWdodCAyMzkxIC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVl
IC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB7ZvX
diM5DERnbIVupVZqJSt5/v8jt0B2KVhx9uy+XT6MbVkogkXgCmNbv36xcOD/deD3af2bfU7B/uSv
RBx0/fFtieuwy6/ekzhHfHidH3pDonmyY/3RGi8VruI/88oizXdeKORnRUQTfKmRv/lUIT0lbajA
1mmFSjz6UuEU34S38wqhLPFCwfE5PII7seKTtxSu4nNwN1bWCAmf4oENjUA6vPZWaJFXaOQkGoX7
AqcEWq3YPqLLvIpCElcKv+9JhIB2UAKK1+5l2ev1+v2+/i0loSQuTvFY4BwfwYNYoVFa4ckhmgR0
gLR/T9HDvEKiUbCRDzLIB0jx2n04GlWxRqPhICs0h9BWjwVSAkXZU3hVjfOqLhQihTsCeujkoPwv
e33Fj8eTaazJuFHQVWQf09OvkjgLxA0ofqB4hc/m8/ksJJRDsqGdyumJQDhYlDq/4mcKr+s6JCbV
KGzIKTRNdS+DuMOUwHCkeEUvlsvloq5DQUbqJlROcuFhBurgTicnMJnOI3y1WklCOegQ/Z6KIVx4
LtAtwsHxdKb41TrWKhQihdMZ7mcQZZxPEA7M5hG/iSUFHWIsF8oiWqJpyhsPTgJxBZNZHfFf2+32
SwpKYVz5DA8FgiPtuIM4wXyR4ne7nRQihXSGZMK9WopDBUZDQBZU46kS0P6KD4W1XFAtNCY8EVAd
S0AWxAnWyn+33+932+1GZ8gmXFTCrQepk0MgLNAJlMD+cDhIYbNe1tMwIUopuaiM7wuoDiWgS1ys
NhF/PB6loDMkE0JAlXCnnxoPdItFFpjLgkuB1SJcjFp8KaBOjkuQBXGAyOCwDxOSQK7F5xk0t5gF
jt/f3zqDBQZvClRqhFuBuIa3BWa1LiE8PGWwTPf4NwKbbdxBCBwPcQ3/TuD7z58/MgEBPKAO6IUj
PBCUqQM8iBdn6gAPqIM0aNIL8CD+w0Ed4AF1oB9g0At4UFMH+kkWdYAH+rk0dYAH8fsJ6gAPqAP9
so9ewAP9vpE6wIP46wHqAA+oA/0VCL2AB/HXQNQBHlAH6S806QV4EH/nSh3gAXWQ3rlAL8ADXhvj
3QPUAR5QB/mdNPQCvUAv0Au/Lt5Vxs+RmJV5XeB1gdcFXhd4XdCbt3ltxIN4Dz91gAfUQThAHeBB
KgOYSC+kQuC1ESbCRJiYHaAX6AV6gV6wA/AAHsADdwOzMjyAB/AAHtgBeAAP4IG7gfkAHsADeAAP
7AA8gAfwwN3AfAAP4AE8gAd2AB7AA3jgbmA+gAfwAB7AAzsAD+ABPHA3MB/AA3gAD+CBHYAH8AAe
uBuYD+ABPIAH8MAOwAN4AA/cDcwH8AAewAN4YAfgATyAB+4G5gN4AA/gATywA/AAHsADdwPzATyA
B/AAHtgBeAAP4IG7gfkAHsADeAAP7AA8gAfwwN3AfAAP4AE8gAd2AB7AA3jgbmA+gAfwAB7AAzsA
D+ABPHA3MB/AA3gAD+CBHYAH8AAeuBuYD+ABPIAH8MAOwAN4AA/cDcwH8AAewAN4YAfgATyAB+4G
5gN4AA/gATywA/AAHsADdwPzATyAB/AAHtgBeAAP4IG7gfkAHsADeAAP7AA8gAfwwN3AfAAP4AE8
gAd2AB7AA3jgbmA+gAfwAB7AAzsAD+ABPHA3MB/AA3gAD+CBHYAH8AAeuBuYD+ABPIAH8MAOwAN4
AA/cDcwH8AAewAN4YAfgATyAB+4G5gN4AA/gATywA/AAHsADdwPzATyAB/AAHtgBeAAP4IG7gfkA
HsADeAAP7AA8gAfwwN3AfAAP4AE8gAd2AB7AA3jgbmA+gAfwAB7AAzsAD+ABPHA3MB/AA3gAD+CB
HYAH8AAeuBuYD+ABPIAH8MAOwAN4AA/cDcwH8AAewAN4YAfgATyAB+4G5gN4AA/gATywA/AAHsAD
dwPzATyAB/AAHtgBeAAP4IG7gfkAHsADeAAP7AA8gAfwwN3AfAAP4AE8gAd2AB7AA3jgbmA+gAfw
AB7AAzsAD+ABPHA3MB/AA3gAD+CBHYAH8AAeuBuYD+ABPIAH8MAOwAN4AA/cDcwH8AAewAN4YAfg
ATyAB+4G5gN4AA/gATywA/AAHsADdwPzATyAB/AAHtgBeAAP4IG7gfkAHsADeAAP7AA8gAfwwN3A
fAAP4AE8gAd2AB7AA3jgbmA+gAfwAB7AAzsAD+ABPHA3MB/AA3gAD+CBHYAH8AAeuBuYD+ABPIAH
8MAOwAN4AA/cDcwH8AAewAN4YAfgATyAB+4G5gN4AA/gATywA/AAHsADdwPzATyAB/AAHtgBeAAP
4IG7gfkAHsADeAAP7AA8gAfwwN3AfAAP4AE8gAd2AB7AA3jgbmA+gAfwAB7AAzsAD+ABPHA3MB/A
A3gAD+CBHYAH8AAeuBuYD+ABPIAH8MAOwAN4AA/cDcwH8AAewAN4YAfgATyAB+4G5gN4AA/gATyw
A/AAHsADdwPzATyAB/AAHtgBeAAP4IG7gfkAHsADeAAP7AA8gAfwwN3AfAAP4AE8gAd2AB7AA3jg
bmA+gAfwAB7AAzsAD+ABPHA3MB/AA3gAD+CBHYAH8AAeuBuYD+ABPIAH8MAOwAN48L/yYH84fn9/
Hw/73dd6OZ+OR4Ne0e20W58fH3o1PpehPrt9dV6uv3Ynge1mtfg7gen8RmA2eT+D0fiuQDV87wi9
wUlAZzjKgn0cYTaphv13PCgagdVmGyaEQHiYBcrXJnazwGyRBPaHgxIIgXoaGZTdzotbaCeBaiKB
9VekIIGdTiCB8SgJtJ9eYysE+kMJ1LqGUND+2y/fYmTQbj2pg88QKCUwntY6w9d2u9vtttuwYJ5u
MQl8Piqkj08LxDUslutQ0FICyzouwbf4UOBDAp1uqWtIZ1hJIdYmEkgW9IrGw/ul/JEFdA1xBqWw
Wq83m816vVrUs2k1GvTLopM9vCvwOwRanXBRKUxntRQksV7pAPO4xEHPHkbr3DZTCHy2Op1CZ9A9
hEJIrJaLxTwa4VSHn7H/QwGZkFIYT6bzuSS06vlsOk4JFN04wROBxoSUghRmkqjrueIn4cDpBI8z
0BnaTqGSwnQWa6r94wBNI+RLvH+EVAk6Q6lqHFXj8UQa08kk4uVgaqQ4wZ0MAk/yJd1DpCCFgSSk
oVVF/I8ErnjWfJEFopasMBxJoxop/CL+ThleCjSHyDkMBsNYEZ4PkK7glqhngVwKzqHX7/cHiu4r
/WTAOf66iq4EUgrpFEVZ9vJSeBiYG/mBgxKJ6lIKoZBy6BaFNLT0sdvEy4DHAtcKkYRWClZ43t/x
Tc4/P5xTiBxUUVrSiA+RfqqAJ/uH3E+JJCKpHO797zqYs0kC2QcloRXBEa3dIzzv/0QgpxAKsjLM
bFZ88VZ8c4ikkCQiMlZEN9s/2/9kQ7rOFOTgt+Odw1ki6Xj3V9snK7OTvpCIPz+SvX757zngx2cv
I09P+BGYvzx9961Pfkq8FXTzpEbl5nEewIH/3IF/APd2qAcKZW5kc3RyZWFtCmVuZG9iagozMjgg
MCBvYmoKMjYwNQplbmRvYmoKMjkzIDAgb2JqCjw8IC9MZW5ndGggMjk0IDAgUiAvVHlwZSAvWE9i
amVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMTQwMSAvQ29sb3JTcGFjZQov
RGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2a2Xbqyg5F04EN2BiD6Zsk+/8/8iypLEOCaXLHuG+z
HhICaJW0VJqpnc3LCwsH/r8OvJ7X/7DRObh99DeNq3B/4mmN/nB79imJc/hbt7rnnlCI93bB7YP2
+YcK7fs86j1W0kgv3VfoDXcZ13gskd6hN1vQx3nZjybhr9/J4TJe0YNYevyUgsfbRr67oodpmU5I
3M0hBCzeo7O0JNMpPBRo97f4LMvTkkxIJBv6Xfixv4ePYuV5KNwz0gRif9t9NBqPx5PJRF9Ho1xJ
qAzvhb2xL4cQUP3DYZ4rfDIpbJnIyJIwhTaFGwKWgMdr/7Giy3I6nZalNFoF9SIp3BTwBgxTvKIr
W9IoilCwIm6X4Cdg0MVXs1ld17OZNErLQUW4C30CZoAsVAJqoOdfVoqe25JGNfUqLhR+i1wIeAKF
xc8Xi6ZpFou5FEpXOKdwS+DjQx2QgeXU4pulLZOYyYeJFeE2+nY/W5kysAosgUkxrRS/XK7W6/XK
JOpkQ1vDbQHrYWYJVDPFK3yz2ZhEM/ciRrlqUCf7BdpDkEmgKGf1olmtN1tbGyksahUxGeeZC/RM
hDRdYDCwCuTAvFkqfrff73emkFIYj7Jbp7ETkAVWgSVg8YfDwRWUgrVy5Cakw3hlYnuK8nwsC+XA
eqP44/HoCitvhPpw0cgfx9kz8CaoiYVVsFpvFX86nUxhs27mdWUm3BewJiQL1ILNTvubgBS2a6uh
LFzABsr60JNBOsfWRFWwlcDp8/MzpeB9cAGf6ZsCfozkoXqw3Sv+6+vLFHYbOwpTCbQuPhZQDy4F
ttbI5wT8HNZq4u6gBL6/vy2FfSvQ9fFOBtYEldArUD4rYF28ysDa8LyAN+GyhNTHPwnsj7Lg379/
ZsJhhwAecA6YBXgAE/m9wO9Gu6RxDvCAczD3f7AwC8wCs8As6G8w8AAP7G9xnAM84Bykv0szC8wC
s8As2P/1cQ7wgHOQ/t+bWWAWmAVmQR9m8s/BwAN4AA+YBXhgn4/kHOAB50CfN2QW8OCFc/CCB/rw
NecAD+wz+JwDPOAcmAOcAzzwYwATmQU/CPxuhIkwESYmB5gFZoFZYBbCAXgAD+BBTAN3ZXgAD+AB
PAgH4AE8gAcxDdwP4AE8gAfwIByAB/AAHsQ0cD+AB/AAHsCDcAAewAN4ENPA/QAewAN4AA/CAXgA
D+BBTAP3A3gAD+ABPAgH4AE8gAcxDdwP4AE8gAfwIByAB/AAHsQ0cD+AB/AAHsCDcAAewAN4ENPA
/QAewAN4AA/CAXgAD+BBTAP3A3gAD+ABPAgH4AE8gAcxDdwP4AE8gAfwIByAB/AAHsQ0cD+AB/AA
HsCDcAAewAN4ENPA/QAewAN4AA/CAXgAD+BBTAP3A3gAD+ABPAgH4AE8gAcxDdwP4AE8gAfwIByA
B/AAHsQ0cD+AB/AAHsCDcAAewAN4ENPA/QAewAN4AA/CAXgAD+BBTAP3A3gAD+ABPAgH4AE8gAcx
DdwP4AE8gAfwIByAB/AAHsQ0cD+AB/AAHsCDcAAewAN4ENPA/QAewAN4AA/CAXgAD+BBTAP3A3gA
D+ABPAgH4AE8gAcxDdwP4AE8gAfwIByAB/AAHsQ0cD+AB/AAHsCDcAAewAN4ENPA/QAewAN4AA/C
AXgAD+BBTAP3A3gAD+ABPAgH4AE8gAcxDdwP4AE8gAfwIByAB/AAHsQ0cD+AB/AAHsCDcAAewAN4
ENPA/QAewAN4AA/CAXgAD+BBTAP3A3gAD+ABPAgH4AE8gAcxDdwP4AE8gAfwIByAB/AAHsQ0cD+A
B/AAHsCDcAAewAN4ENPA/QAewAN4AA/CAXgAD+BBTAP3A3gAD+ABPAgH4AE8gAcxDb33g9Pn1/f3
99fn6XTYrZeLuiono2w4+Hh/e9P7XyPWv18JrDa7Qydw3G//KFA3vwVWzfz5DMqqV2A2fbKESSeg
Gr7MApWgDGbTYvyEB/koCay3+2MrcDzsNq1A/tDEYRJYLF3g9PlpCUhgufAM8uGDLgySwEwCaoNS
kMDxsN9KoK5UQj4c3G3jhwsU09nC2rCXgu2/VxcbPwYm8HHnHLy7wFgC82alGg6H4/F4OOyTBXaO
TOD99kEygSwfF2U19xqkoLXfbdcrs+ChwFsrMCmntaew29vabTd+Di+6eOMom8AgUxushsVytdlu
d7vdVvHWxKqUh1nysFfg9VUCH4MsG1kNSkGNkMR2o/jUg4kJmIc2StfDZAJdDdWsViNWklC44lMC
4eEjAaUwrVREs1zZWjY2SNPCEkhNuCngNQxVg2xUEYumWS4VvpjXaoEGQQLdKegtIWowFyyH+cLW
XPFy8JzAbQ9cwI6CGmEKdT1XdD2beQGWwPkY/QSSUUmFvZ1TcIVqZquqlP/EC+jif+Cs/SEE/DTK
hkJJTCtFT8uIPydwU+BcxNglSq2iSPtHAWbBDQHVkIowG5TERGkU+jr2/LW/DeL1KTyX0AroQEvB
JNIajXL55yR4JNApDIeZJKShpe+ZxWv/iO8twfvQKQxMwkXsm29/ju9zwJ7zE5ps0FRJwkXsm2bQ
9m9JcmP/HwqaS0m4iH3z9B/k36VgVagXJuEatnm7fd8Ztrjz8iJCwSUi2rZ/HN/aYGdaS1l0y59I
8ufteh+lNyWFJOKx+tK+0ht1+WT7vjaLiI7w2w240OgkIo/zE0/Fd0ZcxLUPL3Z58PA6Vs88iPn9
8i+N3y8/9/OfM39OlnfhwLUD/wH6Uul7CmVuZHN0cmVhbQplbmRvYmoKMjk0IDAgb2JqCjIwNTMK
ZW5kb2JqCjI2MSAwIG9iago8PCAvTGVuZ3RoIDI2MiAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5
cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDI4NzMgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkg
L0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PgpzdHJlYW0KeAHt21dzGzsSBlAnMYgUMykGBdv//0duN4ZNSTaDXLUPW1tnHqxE9ADfoA9x
bd0vX1wS+N9O4OuH61/n+mFw98W/lDgzPL/12RIXhn+6xGn8t3fX6Zu3Z3F86bvB3afH798q8H74
97er1fhMiXfju9E/4mqfZYnbFbpX5GtzUA6uK758K3F5Ga1ANz5H3tWVX3Ql2isuFqjx7e4xuFdX
fP6pCscCOb4N79cVhboSMbt80aUpxI/a/HPyvV6/PxgMhsNh/BmFPlHhw/3b8Bh9H1fW6Cq0HNrr
zs0hfxATaPPvxd1j8Ki7Wo1+LCOCuLKIrkA+vbsYHzcfjcbjh4eH8Xg0ihKDWEUmeTmFNoHj+H7e
PkZP8mo1ugp3VeHCEroFRH6DGD5+mEyns9lsOs0So6iQizhO4e8CpwXEA4gFxO0nMXqeV9SYtAot
hguLyPERYSaY4+/b+PlisVwuF4t5q3CMoQr8sRuqQJfg/SjvP18sV3ktF/N5zGF0Hw+zexDt1R+3
U1cgI+z12gRifAxfbzabdSsxjUV0TyKmcK1AriASnMT9c/hjXFFiuZhFDPeDQRfj5QJtBZnANOa/
3jxud7vdtlWIRYwzhbaG8wVyF0YTtEcQE1iuNtvtbr/f77bbmMM8ppBriKY6uxujZlegreBhkgt4
3O32h8Nhv9vFHBbzacQ4zO14u0CuIBaw3e8PT09Ph/1++7hexhRiDdcLtF2Qz2AybROI8c/Pz1Fh
t92sIsYM4W0z/vUYj9sod+FktogEdjH+5eUlKsQiVrGG2M83CuRDiAIPk1lbQYx/fX2NCvtdriFD
yAIZQj6HD/3QQsx93ApkBI9tAl2Bw36bIbQCXYqXC+RTjAzzGRxiAj9//owpZIEIoe3mmwWGXYF4
Bu8KHHaZ4rvneGUG3T6MDPdPMYFfv37FFCLGViDa4fgcrxeYxBLOFZh8ukB7in/OYDn/lwLtIbxb
wj6f478WeI4Ifv/+HSHETlBABvaBXuABE70vHLw3xiHNPpBBHtbtAxnYB4v2H656QS/oBb0QfxfH
Axnk38naBzKwD/IfOOwDGdgHvfgna/tABvZB/vqDfSAD+yB/j8U+kIF9kL8XZx/IwD44/WqdM5L3
RiZ6X2i/M+690Xuj90bvjV++yEAG+f9i2AcysA8yAftABm0bMFEvtI3gvZGJTGRil4Be0At6QS9U
AjzgAQ+qG5yVecADHvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbnAx7wgAc8qAR4wAMeVDc4H/CA
BzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAHPKhucD7gAQ94wINKgAc84EF1
g/MBD3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbnAx7wgAc8qAR4
wAMeVDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAHPKhucD7gAQ94
wINKgAc84EF1g/MBD3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbn
Ax7wgAc8qAR4wAMeVDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAH
PKhucD7gAQ94wINKgAc84EF1g/MBD3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAH
lQAPeMCD6gbnAx7wgAc8qAR4wAMeVDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc8
4AEPeFAJ8IAHPKhucD7gAQ94wINKgAc84EF1g/MBD3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ
3eB8wAMe8IAHlQAPeMCD6gbnAx7wgAc8qAR4wAMeVDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoB
HvCAB9UNzgc84AEPeFAJ8IAHPKhucD7gAQ94wINKgAc84EF1g/MBD3jAAx5UAjzgAQ+qG5wPeMAD
HvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbnAx7wgAc8qAR4wAMeVDc4H/CABzzgQSXAAx7woLrB
+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAHPKhucD7gAQ94wINKgAc84EF1g/MBD3jAAx5UAjzg
AQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbnAx7wgAc8qAR4wAMeVDc4H/CABzzg
QSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAHPKhucD7gAQ94wINKgAc84EF1g/MB
D3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbnAx7wgAc8qAR4wAMe
VDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAHPKhucD7gAQ94wINK
gAc84EF1g/MBD3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAHlQAPeMCD6gbnAx7w
gAc8qAR4wAMeVDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEPeFAJ8IAHPKhu
cD7gAQ94wINKgAc84EF1g/MBD3jAAx5UAjzgAQ+qG5wPeMADHvCgEuABD3hQ3eB8wAMe8IAHlQAP
eMCD6gbnAx7wgAc8qAR4wAMeVDc4H/CABzzgQSXAAx7woLrB+YAHPOABDyoBHvCAB9UNzgc84AEP
eFAJ8IAHPKhucD7gAQ94wINK4P/Xg5fXn79+/fr5+vL8tH9cL+eT8WjY7939+P7tW7wNfH0LID77
631hs90/nQo8HXb/WGC++rPAZrX4/AwepmcLzB4+uYTRqUCs4WdE8BJLiBnMHkb3n8hgMOwKPO4O
z8cCz4f99lhgcDPEXldguW4FXl5fYwJZYL1sMxj0bjyFu67ALArEY4gpRIF4iLsoMJ/GEga9u6uP
8UcrMJ7MlvkYDlEh7v902O8eV1Fg3Ar8uLIPvrcC91FgsdrEGp6enp+fnyLCFsF0fD+MGfz4fnkj
ZYH+4H78MF20NUSFuCKBx01EMLlZ4NuxwOhhMm9T2B/yigXkPpxO3p7iha2cBe768RhyDcv1Zrvb
7ff7XSwgH2JkOBz0uwzPFvj6NQr8uOv3h7mGmEI8iCix224f120CuYL+XWaYrfR3M2WB0xqms3k8
iE2UiPVvVpHA9GF8PzhmeKtATGEyjUWs1pu81jE+EohG6PbhlRm0NfRiDRFjLGK5Wq3X61WOn01i
AsN+v3faBWeXUGvIFHIOi2Vei8UsFxC7qDXCcRdcLpBbIR5EVpjPF4vFfD6b5gKyE99to48gpU6R
zLe3KbQK01leMTzvf0ogH8IHzo5fVIG2GyOGcUxiMo3RMbzGn/bxxQJtCm0R963EQ1wxvN2/baJI
4MoMYg3dIjKGmMQophGjR/dt/hFANuLfu/BtCccCsaGjQpboruFwEA+gjb9V4FSh1+tHiagRV3yM
DfBh/NkQ23M4VbjLEq1IfojhOf9r9891tC3exRBdFSVakfyQw9/GX7j/hwrRl1GiFckP7fZ1/8vj
uynkKuJZZIlWI2+etz+Nv1LgY4VWokbn8HMOHB/h6UOLIfd0XHHT09W+0f3w9Nrzn7yv0BVpY+OP
40/OD3v33ePrjrOo0TX82vpPRU4lupWc7p3fP73o6idvFf747OqoDz/8Y2D35YdX3P7ijxq3B5x7
xbHIuR/5ngT+uwn8B2EcL84KZW5kc3RyZWFtCmVuZG9iagoyNjIgMCBvYmoKMjg1NQplbmRvYmoK
MzM3IDAgb2JqCjw8IC9MZW5ndGggMzM4IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1h
Z2UgL1dpZHRoIDY1IC9IZWlnaHQgMTg2OSAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJw
b2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0
cmVhbQp4Ae2c23bi2A5Fc+N+x8YYsIHU/39kL2lbJiQ2oWqM83LG3A9duaBlaW1pou5K+uWFgwP/
Wwdeb+cfHnQLjo/+SiSC7v98WuI+7OtnT0ncAt7a037tCYV4bRvcfBBf/02ieV2Kek/nTuIXgRTv
EU30F5H0zYcKt3iL+2iPfWaq/v0HCm18Ez1Ix3SeUriPV/AwHX3USqTX9CTh31SinryHj/xIxiRS
Ev6iBwJNvIWPRuN0pBISj2z4+nzFW/gkHclIwpMII187cjCBeL4eb+HT6Ww2m06nk4kkTMGr6Csi
BD4+LP2xR8/9SEQSjUJ/EW0CTfxsPl8slsvlYjGfKw1XkJNNEd0lpAtQ/Xr+zMJXfpYu4VW4guX6
QKCNX67W681ms16vVpKY3VLoErCvyULrgMEwPV/xm62fzdoUmiK8p/3ld0ncBFIC88VST8+yPM+z
bOsKcnKsm/hFwBIYmQGK32b5zk+WmUIUETbe25AyUAWDgRyUgSuPL/b7fVHsclNYKAVdpXqh6yYb
AU9gPJ2pAHv+fl+WpSR2uapwH4fD9h5+ZiAPmwqUwDrLi6I8+JFCtl0vlYK6qacVlIG1sSrQHbgD
9vzD8XQ6HY/lvlARK7sIr0GvNLR8v4UkoCZSBav1Ni/K8niqqup0OpR7FeE2jkYyoVfAPDQBszDb
7cvDqarruqqOh1IpWA1qpttE/cwgCUymdodZoQKq+nw+1/VJReysBjPhoUDy0CywCo6nOglUp4Nq
cBNMIC6yIwPzcDRJFpiD9flyuZzPlVIoJLCcWwZtJ3QKCEQmsMnyvRw4X67X6+VSVyagizSBWyv1
COgW3UOz8CagGpKAxuFhCc0t6hJKWWgJ6JxrM8EEdA1PCMyXdotJ4PPz84uA3eNTAhqEDgG7x6cF
7BathDaDsvBG+AuBgy7R4nUuZ7uGfxP48+cPAnjwSR9c8UBAoQ/wwN5Y6AM8oA/SksUsMAvMArOQ
F3iAB/bfYOgDPKAP0n+PZBaYBWaBWdDfkPjfT8ADeAAPmAV44H9rDBN5X7CfHqAP8IA+SD9Jwyww
C8wCsxA/WQcP4AE8gAfwwH/emX9vbH7imvcF3hd4X+B9gfcF3hf8F7J4X7Dfh2I/wAP6wH5Bkz7A
A/rAf1GWWYAH7EgvzMILHuj3z+kDPLD/DQF9gAf0gTlAH+CBtwFMZBa8EXhvhIkwESYmB5gFZoFZ
YBbCAXgAD+BBTAO7MjyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN7AfwAB7AA3gQDsAD
eAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AAHsCDcAAewAN4ENPA
fgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/g
ATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP
4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD
+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7AA3gAD2Ia2A/gATyA
B/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDTwH4AD+ABPIAH4QA8
gAfwIKaB/QAewAN4AA/CAXgAD+BBTAP7ATyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN
7AfwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AA
HsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPw
AB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0
sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsAD
eAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7A
A3gAD2Ia2A/gATyAB/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfw4P+cB5fr5+fn9Xo+
V8eyyDarxWwyHg4+3t/f3jT/gQL/8ycPymNVh0B9Ouz/TmCT7b4L7LbPZ7BYdQqsl0+WMGsFzpfr
9Xq5nK2E3Xa9nE+f8WCSBPaHU9UI1PKwERj/auJw5ALb3AXOFz3/bAJF7hmMR7/cwsAFlmsJlMdT
nQSq00ECm5VKGI8GD6/xwwXmEsgKCVT1Wc+vT2aBt4EJfDzog3cXmM6XuoZifzhWVV3XVXVSBbts
7X0kgff+RnKB8XSua9ju9qVs9HNUG5kFdosu8NbTiW8mMBxPZwszoTAX/Bx0B9nWLJi4h4rvbmUT
GAzHk5nXsFMRh+PxeFC8ElAfmod2CT0Cr68SaExYrJTCrijLg8IVrwSsAhOQh/78n8NkAo0JqkE2
SmFfKtzjPQH14TDuoFdgMBpPZKPdpBT85CpAfewJtF3QKdDWMPOL2Ob5brfL80zx5oDuoLFA098j
kGqY2EWs1ptt5sfiI4GBNYHdQa+A2ZiKkMJmu91uNmvFy8EmgW4BYUmab2HjZGo2KAk/CpcBKT7u
4I5n6ZNGoClCzeASq9VyuYj42yTeA/GLgKeQipiahJ95en5MsjvQnYFquCmojJk05rPZbKr8/QZ6
mqDNwFzwq7QcxhNJ+JlYuJ6feqDjCr4JWENLQRLSsOPhqt+f3xsvFbvcVIQpSMJF7I+hPb4FwbcW
uNlhAkkhJTF0Ef1T4RH/KIGUQqugLCwPC7bwX/O3RDwFU9BdKAnzIgU36Xf18K2AHwpJw3QkFxTR
M+5Dvn2WcvAkLIv2WFap/MfxUUVSSKV4bBv+W7wSapJoNZJAfPVbxp2fxmv9Si389oUnnm+SXwLu
P+x8XucX7+Oazzpf2f/F7xr9r3zwnX979ANBvoUDfQ78B07mgLEKZW5kc3RyZWFtCmVuZG9iagoz
MzggMCBvYmoKMjM3MAplbmRvYmoKMzEzIDAgb2JqCjw8IC9MZW5ndGggMzE0IDAgUiAvVHlwZSAv
WE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMjI0NyAvQ29sb3JTcGFj
ZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2d23qqSBBGt0dEQAXPiafM+z/k/FXdoCaIZH8z
d6tuYtS/urq6RbpWg3/+YGTgf8nAoLHfu2+kzYPf+GhETw/6engSPf3Tx8NdMGzs/txbD/VbG218
UD//xkF8WxCNooX/4kvdDsKbTFCLw197JrzWqfe31OpxY+aj8dDhoJbb+yWeRNPDPg6a2Bv11E1e
Gg9dfbi37m1Lm7jpgXkIIfib2rtgL6mXFvpkYuJZtCSpPcQstundsfRRbuo02mwmDyGE16Pgeh+2
cWg8TefzTDafp2l04F3wN/6MoNZ78Na4xLmbXKQKIUQQA2jXx+inidTzLC+i5RaDObAkBgcv9Wre
5Wq8WCzdFkXuIQQH7/RKfaLYTb1albLVamke5qEH7e3Hzg9t6NR8lJeVWxkc1D2IYzh47MJdr9yr
8956Wa03snUVHCgFmgZj+yD8GIJHvZKX5Qq+XG+2bpu1OcizEECXfjSaTBL1Pi+CfLeX7bbuoNAo
JslkUo9AW/yjkPxMuSurzXa/P8j2++2mKp8CeBV/0M8zNV+tt7vD0e2w266r1VIB+ByII/C9faVF
6Z949hbW+d3++OF23O+sB0VuGQwJtAx+y3/Q29zJcm9+f/j4PMk+Pw57CyBm0AegVW+HDdcX1ntF
/3k6y06fx8NOGVgUPgLhONDWftBr7hUKf6vmXS4HHkBpCUiTaZd+rPZt9FaWfGv+IrMAbAiWlgDp
68/Qj/4rfJ/7+UJ6C/98ucou59ABjaDplcAwAh16y77Cv1xvsutFHdAIKIHv9fbJzxex+w96jYDr
Z0l3+/rsRb3C9+YVgDoQ9ZpBb/Wavda+679kd73PwB76pSbvT70PYK/2lzH911vTvhL4S73S73J1
IAzA3+j/kaEnf/YBZv70//yHw9/ti88Pxw+Onxw/OX7y/cH3J9+f/dYffv7v5++cP3D+wPkD5w+c
P3D+wPkD5w+cP/Sp33L+RP3J8AP1N9YPrB9YP7B+YP3A+oH1A+sH1g+sHzr379jetYL1E+sn1k+s
H1k/s35m/cz6mfUz62fWz6yfWT+zfmb9zPq54/of6gfUT6gf2fVb8Gf4O9f/qIDC+pn1M+tn1s+s
n1k/s35m/cz6mfXzi/unjCfUD6gfUD+gfkD9hPoR9SPqR9SPqJ9x/zK/gR71E+on1E+on1A/oX5C
/aTl/r12/1rqR9SPqB9RP6J+RP2I+hH1I+pH1I+oH1E/4v713L8//IJMr9/vYP82+9e5/p/r/7n+
n/37XL/A9Qtcv8D1C/B3+Dv8Hf4Of4e/w9/h762/f8v+A/YfsP+A/QfsP2D/AfsP2H/A/gP2H7D/
gP0H7D9g/wH7DzLqp9RPqZ9SP6V+Sv2U+uk9A4PBYDjk+jWu34MfwA/gB/AD+AH8AH4AP4AfwA/g
B/AD+AH8AH4AP5jBD+AH8AP4AfzgXj3/84f6OfwAfsL9D7n/4wx+Aj+Bn8BP4CfwE/gJ/AR+Aj+B
n8BP4CfwE/gJ/IT7n47gJ/AT+An85J4B+BH8CH4EP4IfwY8y+BH8CH4EP4IfwY/gR/Aj+BH8CH4E
P4IfwY/gR/Aj+NEQfgQ/utMTrr+BH8GP4EfwI/gR/Ah+tIQfwY/gR/Aj+BH8CH4EP4IfwY/gR/Aj
+BH8CH4EP4IfCRjAT+4ZgJ/AT+An8BP4CfwEfgI/2cBP4CfwE/gJ/AR+Aj+Bn8BP4CfwE/gJ/AR+
Aj+Bn8BP4Ed3fMTv/wzgR/Aj+BH8CH4EP4IfwY8O8CP4EfwIfgQ/gh/Bj+BH8CP4EfwIfgQ/gh/B
j+BH8CP4UZMBrr+Cn8HP4GfwM/gZ/Ax+Bj+Dn53gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Of
wc8aesTvP8HP4GfwM/gZ/Ax+Bj+Dn8HP4Gfwsxv8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az
+FmTAfgZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj8TPoMfwY/gR/Aj+BH8CH4EP4IfwY/gR/Aj+FFDT7j+
Cn4EP4IfwY/gR/Aj+BH8CH4EP4IfwY/gR/CzL/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+DnzUZgJ/B
z+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfnaBn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GcNPeL6M/gZ/Ax+
Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4Gfwsw/4GfwMfgY/g5/Bz+Bn8DP4GfwMftZkAH4GP4Ofwc/g
Z/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH62g5/Bz+Bn8DP4GfwMfgY/g5819Ijrz+Bn8DP4GfwMfgY/
g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8LMSfgY/g5/Bz+Bn8DP4GfwMftZkAH4GP4Ofwc/gZ/Az+Bn8
DH4GP4Ofwc/gZ/Az+Bn8DH4GP4OfFfAz+Bn8DH4GP4Ofwc8aesT1Z+387Hr7kt2uf7N+2B8/z7X+
/Hnc/+r8s1xvv+u36/7nb4tW/WrR7/xnntf6y/Umu14s/u16tcjn8/fnD2nUWwEu6vXz01GfvtNP
E9dXoYB5ucouIf2VtZ8m0+7v76BfmV4DEPQKX7evr5Y99GPXF6vKB+B0vsjOJ+9+tSy8/fH49ffn
yPSpCvAagJ0ScDrLTvbr22H4UsUv+ejV94/pZ65XBzQDTm4+e6pSw6f0deiHQ+mnM0ugd+Dw8enm
2Q/pm02lH8rajv+mn0xnM+nVAQvg+CE72uStNPvy+Wxm6W/XD4zASp84gbEAdofDUXbYq/fVKuze
C3q1Pvh+/HX9yPTpvFAA5mB/kLm89NFT9ycxe6/0k8RmULFYldVmu3PbKnqf/GmSTDr1sQNplhdL
c7DZyjYm98G35r37r+J3vU2hTCmUg7WbyRd5ZpP3vd4zKAdKwaosK1lpcn10bfAnmn1h9J77r0O5
xeQjoBSmFoF5cJPaWje5h2/vfDj2x4dRb0OoORQcLJayRZDH6MPc7dJ7DzSIWZ4Xbrm3HqPv1AeI
XzuYZ3IhcTZX8M/yF+1L7xRcKUhmCiGaqUPnXyUv5i/MQaVAOXAPqZmrPfXN3Gtpvx4BBWAO3IOC
MLGNu6Xe5PbJa1UHfejBaBw8KAgTu/pB/kLfRGA5cA8KwsWaNn7U6mrdpoHFZhF4H6ILBe5qi92D
f9l67aD2YEG4qeN3dZc8RuAOLIbGrO3QeLc89CB2QhJz4Npa/Sr31vtgnoO7h1+q5aN2EDLZxO1P
1410/717eH7UrXp49VkW/3t4vcfD7y56SH68pfbx4wWeIAP/UQb+BYgJ2ecKZW5kc3RyZWFtCmVu
ZG9iagozMTQgMCBvYmoKMjQ2OQplbmRvYmoKMzMxIDAgb2JqCjw8IC9MZW5ndGggMzMyIDAgUiAv
VHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgNjEgL0NvbG9y
U3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAv
RmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtlVtyxCAMBO287PufONLMyCCnwPJWbeXH
fCwQ040QjyzLU54MvD8D67q+PImxrdy2NDRatxQB5bquyFzXqyk64IOl/aViiNGCT45rg/iMe08f
Lg0cR/5Thb2aoeMDRw0HP05jaDywLxZv1wyJF40qFBgwCQHffS4DHPxm8SaD4AxjQwjIC/cKAl/G
NATqY37nflhgsBhCMLqgnQDhC7cqYgjDYA1pAZh+Q4EBaSgLPH2Gkd82GVoeLyOgwPl93+3XDX0I
cwG2wCMgLwN3QmuoCBrPEP5DYEuwDEQSbkRg5/hIonjL4osC3wgr5NtZnCdREXAbxOcApkfZNurY
Rx2leydxhWF4F3hfBktY0mXwx8DmxvTM4OVtXP4aTOIFxxivGuYYBdAE+UUyXA+S3vax4AjBDXjU
HLZiPcvNNU+B5xEGOVzW8aNNZFzMshukAA28+L+JBgRxOOAr8lrEKgNR/5V4Hn+/iqwIvMJrM9tS
Dtgakw3sP/VIaveD5u2ERWeOnL4G1OrTgEq3wdW1V6zPmCcD78nALwn/DyoKZW5kc3RyZWFtCmVu
ZG9iagozMzIgMCBvYmoKNDEzCmVuZG9iagoyNDcgMCBvYmoKPDwgL0xlbmd0aCAyNDggMCBSIC9U
eXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAxNzA3IC9Db2xv
clNwYWNlCi9EZXZpY2VHcmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDgg
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB7ZvZVuNYDEUpIIMzeYideYD6/4/sI10r
MZA4odbqt30fCE2hY+lI2lwaeHnh4MD/68Cf6/mHB12D2/d+p/Ej3D7wvMTN8OclruGvca4feiKL
+OQIbl/jww8V0ie2UW/pfNF4oNCJb6M7GukfexUu8R72Hsf/S3k8VOjGK3gQR+9L47GCx1vBb28p
fJiOdFzC/sk/514VIWDxg4GCR+noPZO45tAnkJ6vZ1r4OJ3RyBQGV4XbAl+e7+FZnLFLPMrBBNr6
B/b0LJtMJtPpVG+zzCS6VdzKIQRUv8db9MyOaVwUWh/vCFgCFj8cj7OJoufzxWIxn0tDCmMZoSqS
wl0Bb8BQ+Ste0bkdabjCpQjl2iegAtr4vCjKsiyKvKNgvbwlYAbIQiWgBrbxiq7sSKNVsHFoFb4n
0RGwBJR/XpTVclnX9XJZlUWuKmSkXHgg8P6uCcgmqt/i68ZObQrKYZJpoNxGf9xXG1IGVoEnMF/k
im+a1Xq9XjWNFOTDNYX7Aj4D48lUBShe4ZvNxiSWlYqYTrwGdfK2QDsEI6tABSzr1XqztbNZr+ql
irAaRvdGQZouMBiYhZZA3Sh+t9/vd1Joak9BNlofbs3SRUAWWAWWgMUfDgdTsBQuNdwXcA/HY6tA
Dqw3ij8ej1JQCnJBNWieL4380YU0RjZFs0VZyYGt4k+nkxS2cqEqzYQHAtYEm6JFqRZsdnq+CRwP
u40aIQE1sl0olXwrgzTHbkGz3krgdD6flcJuqxrMBBNwF+8KpDHKrQfbveI/Pj6koBrUBxfwab6x
T96FyxxKQD3oCqgPzwqIBHMX2B08AUvBTHABW4dHJVgTrgKfn59XAZ/FpwQ0h9YEZdAVSMP8nIDG
SE3oCFgbfiuwP3oCVoO34d8E/v79iwAefDIHH3ggoDAHeGBfWJgDPGAOdFFlF/DAvuNhDvCAObDv
XJkDPGAOFgUe4IH9X2HmAA+Yg/QzHnaBXWAX2AX91Nl/5gsP4AE8YBfggf8GBEzk64L9RhZzgAfM
gX5DlF3AA/tNYeYAD5gD/6VzdgEe2B8fMAd4wBxc/3qA75n4ngkmwkSYCBNfXvAAD+wvHZkDPGAO
zAHmAA98DGAiu+CDwNdGmAgTYWJygF1gF9gFdiEcgAfwAB7ENnBXhgfwAB7Ag3AAHsADeBDbwP0A
HsADeAAPwgF4AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7A
g3AAHsADeBDbwP0AHsADeAAPwgF4AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfw
AB7ENnA/gAfwAB7Ag3AAHsADeBDbwP0AHsADeAAPwgF4AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3c
D+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7Ag3AAHsADeBDbwP0AHsADeAAPwgF4AA/gQWwD9wN4AA/g
ATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7Ag3AAHsADeBDbwP0AHsADeAAPwgF4
AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7Ag3AAHsADeBDb
wP0AHsADeAAPwgF4AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfw
AB7Ag3AAHsADeBDbwP0AHsADeAAPwgF4AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAc
gAfwAB7ENnA/gAfwAB7Ag3AAHsADeBDbwP0AHsADeAAPwgF4AA/gQWwD9wN4AA/gATwIB+ABPIAH
sQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7Ag3AAHsADeBDbwP0AHsADeAAPwgF4AA/gQWwD9wN4
AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7Ag3AAHsADeBDbwP0AHsADeAAP
wgF4AA/gQWwD9wN4AA/gATwIB+ABPIAHsQ3cD+ABPIAH8CAcgAfwAB7ENnA/gAfwAB7Ag3AAHsAD
eBDbwP0AHsCD/5MHp/PH5+fnx/l03G/XzbJYzCbZaDh4f3t91fLFHt7JYLXZHS4Ch91m9TuBqv4h
UFfPZzDPbwrk8ydLmF4EVMOHLDhZCXWVz6fPeDDOksB6uz+2AuZhEsjGD00cJoFl4wKn81kJpCZY
Btl4+KALgyRQSkBtUAoSOKoCdbFMAoPeNr67wGxRLq0Neyno+Ye9WbAsFzPLYPDeMwdvLjCZLQq1
QTUcDsfj8XBIFngXTeDt/iCZwGg8mc2LymuQgo4SUAVVoS6O+wVeWwG1ofQUdns7O++BWTCJJtwZ
ZRMYjNSGWW4prDbb7W63225tjqsiNwtGycObAn/+SOB9MBplMsFSUCMksd2ogLoqc1+lkXuoVbqx
TCZwraGwRqwksVmvrAXFtYI3e36vgKegIupmZaeprQBLIFnQI+A1DK2GuRWxrOumaWrFq4C0ScOY
gtsZRA2yUQpFVS3tVPb8uVt4nYIeAR+FpFCWVVWVqt/ivYeXMfouIC7Jl9dLChNXyAs7eYq/OPCz
h12qWSc1jZkUVMYiV7Qer+en+Ntz3BHwFJKCS8x1LDzFpwJ6MlANqQjLQUlMlcZMbyeZPb910Kcg
PfPrWxuOJKAipGAS6Sg8xXsBvQJdBUlIQ0evI3/+Nf7bF4XIpJuDJaHjwR5uSyAQ3H2+iZhA5KC9
HOpIw160g534O8//oqBuSsJF7MXD4/n341MKKQctZqth0cr+kv+NGQwP2iJMQd1MEhYd4V5/b3wo
uIRrmI4d03SLHsR/VUiJWKyd5+IvCt6OFNkN7zHwuxFtSzvP1keun9T7Xpvsz5feqC//+DP2+ceH
0DeN+PDvXluR3wXx2TjwLw78Bx72WtoKZW5kc3RyZWFtCmVuZG9iagoyNDggMCBvYmoKMjIxNQpl
bmRvYmoKMzMzIDAgb2JqCjw8IC9MZW5ndGggMzM0IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlw
ZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjM2MCAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAv
SW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+CnN0cmVhbQp4Ae2a2XYi2Q5EqzwwQ0IyJ+Ch/v8jO6STAZTN5F5917oP+zzYLowipTjSLnU1
v35xcOD/24Hf5+fHqZ4Htz//RONCeLz0qMSV8EcljuFP5+f46v0s2reeR+fP7ev3BM7Dn0/nYYkS
n2/P6Jc4+dOZxI0kTvEKymB/0Z9DorzhukL+Pt6Y4a+nk3kcFa4KON7hHR8pWSLfc00hfpmPf35R
SKfT9el0QqKUEW+6InCMf1F8hPd6vX6/r6/dbkiEndK/qhC/UAJhXxve7w/ihEZKFIV836UcSnz4
p+fr6YoeliMNSZQcbqSQz0//I15PH45Go/F4rK/DyCIVXMSVDMr9Zbwer+hJHGkMI4mjgh51SyAM
iMcrvKqm02lVFYl+OJk+XhQoDtiAiJ8oehZHGpNIQimcFL7mEPF5BboBGVDiZ3U9n8/relYUsgin
8LUKC6gFJDAYxvNn8/kiznyeCpFCN5qhHYm/bSgCpQV0gaNxxC+Wy9VqtVwuQmE8Kj5GCvnuqwIl
gemsXixX6zir5UJVTMZKoVdMuC6gCrq6gtGkKvGb7Xa7KQrVJFPIGi4LxBipCdPCybSeL1ebzbZp
mu1ms1rO6+lkNJSNMVSlG7+VUASKhZnAerttdrtds92uo4hKNagXHhEYjeWgEmia3X6/3zVNpDCb
ho23BfIS4g5UwWK51vP3h8NBCpmCatA9nFrpQgnC4GsnumgiC1ebreLf3t6ksN2sVINMGIRA2wk3
BMYTVbDeNIp/f3+XQrNZq4a8yDsCGiRlMK5CIBMoAjvVME8XezkO2YsXMyiDMK5UgQSUwMfHh1KQ
gGqIa4iZvlWCBPqRQViQFRQB1dAK+BrUStcyyEEoAkrg8/NTKVhArfRABuUWI4MvAtmLDwpkG/0t
sJz/TCAu4ZRBXsOPBQ6y4M+fPzIhruFfZICAOhkT8SCIRh/gAX2Q6wGzAA9iTaQP8IA+mMLECR7o
v/7pAzyIfz+gD/CAPsh/FGYW4EH+yzhMhIkwESbG/+WhD/CAPohPb9AHeEAf5IdAmAV4EB8Gog/w
gD6IDxfSB3hAH+jTfswCHvyiD37hgT73Sx/gQXz8mz7AA/ogHKAP8CDbACYyC9kI/N0IE2EiTCwO
MAvMArPALNgBeAAP4IGngV0ZHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7A
AzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyA
B54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP
4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAO
wAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGn
gf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gA
D+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AA
HsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/
gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4
YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfw
wNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+AB
PIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgB
eAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0
sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/g
ATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7A
A3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH
8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP
7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAe
eBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADT8P/Zj94
e//4/Pz8eH877Lbr5Xw6GQ373c7ry/PTkx7oZ1+5hdWm2R8F9s1m9TOBevFNYFE/nsG4uihQjR8s
YXgUUA0fsuAtSljU1Xg4eMCDXr8IrLe7QysQHrYCvbsmdorAfJkCb+/vSqBcQmbQ69y5hdciMJOA
rkEpSOCgCnSLsyih13m9eY0vKTCazOZxDTsp6Pn7XVgwn6kNQuDlRh88p8BgNJnqGlTDfn84HPb7
YoFucdAPgefrjRQC3d5gNJ7WWYMUdJSAKqin47sCT62ArmGWKTS7OE3eQVrgW7zSyiHw2tU1jKpI
YbXZbpum2W6jj+tppTbqdYuHFwV+/5bAy2u325cJkYIuQhLbjQpY1LMqLeimhxqlC8MUAqcapnER
K0ls1qu4gmleYuvhPYFMQUUslqs4y0UUUBIol3BVIGvoRA3jKGK+WCyXy4XiVUDcQbfbcRdcLsE1
yEYpTOt6HqeO58cklkEoXXBDIFuhKMxmdV3PVH/EDxR/aqOvAuKSCns6pjBIhWoapyrxfyXwN8/O
qRY3qW7sS0FlTCpF6/F6fsZf6eMzgUyhKKTEWCfCz+O/d9FRQDWUIiIHJTFUGiN9HfTj+e0gRvwX
JH8VUBFSCIlyFO54XcFNgTaFVJCENHT0XQ2Qz3f8xQzyHo4KkYROBmd4DIHjS8rfv2aHFht0F5JI
kfimGTyLv/J8CZ4UdJuSSJH4luF+/vX4IlCq0GC2GhGt7I/5X76Ctp5MIRR0m0Uioh2e/t+Mb4uI
nm41QidO/Lmo3yggs2jfFQFx2tj48bH4Yw5tFhGZpw2/9/zzJBTyJVivtF7d+eanfft+J+7s199C
44Wz3z/y4xeNR0K+v6cV+f4LXsGB/9qBfwAziwmhCmVuZHN0cmVhbQplbmRvYmoKMzM0IDAgb2Jq
CjI1ODQKZW5kb2JqCjMxNSAwIG9iago8PCAvTGVuZ3RoIDMxNiAwIFIgL1R5cGUgL1hPYmplY3Qg
L1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDIzMDEgL0NvbG9yU3BhY2UKL0Rldmlj
ZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0
ZURlY29kZSA+PgpzdHJlYW0KeAHtm9l24toORVOp0BjTY4wBG0j9/0ceSdvLhMQ0VWPclzvmfjiV
Bi1La0sTnark7Y2DA/9jB3515x8e1MV2H/yVSBd188HLEjdRN5+8JHGNeO9O97UXFPTaLrj9QF9/
JtG+LkX9TudG4olAio+INvqLSPrmQ4VrvMd9dMc/c9X4/gOFLr6NHqTjOi8p3MZ78DCOfdBJpNfc
SSK+aYlG8hE9imMqLpGSiBc9EGjjPXw0GqdjKiYRSTyy4evzLd7Ds3RMxiQiCRn5qycHF9Dz7fEe
PpnkeT6ZTLKsVYgq7hUhgY8PT38c0dM4JpJZEp6D3+YDgZRAG5/n01k606mlYUm4D94OrtBfQroA
q9+e7+HzRZz5bGpJRBWh8ESgi58vlsvVarVcLhYucU2hT8C/ZhZ6B5hAPN/iV+s4JmEKbRHR0/Hy
myquAimB6WxuT19viqLYbNYrV3AnzccnAl0CFm/h2zibjSuoCNl462PKwCoYDMxBM3AR8eVutyvL
beEKnoJfRP9NtgKRwHiSWwH+/N2uqiqT2Bbr1SJ8HA67e+jNoK3AElhuirKs9nFMYbNeugvWC/cF
vIusgqFXYA5s7Pn7Q5xqV1oRlkJbg73Sm+n7LSQBayKrYLFcF2VVHY51XR+P+2pnKYSNo5GZcFfA
PXQBt9ASqPbHummauj7sq7KIGqyZ3MU0ED8zSALZJCoorQCPt3M8eApxD08EkodugVdgBTSn08ly
OO532yJMcAFdZE8G7uEoSxZYAsfmdD6fTycTsBpWZoJdw3WmewWMBC6w2hQ7c+B0vlwu53NTH5IJ
LnBtpX4B78Pw0C38IrDbmosmYOPwsIT2Fu0SKrPQE7BzatyEEPB5eiownfstJoHPz88vAjODwksC
Ngg9AnYNrwv4LXoJXQZV6c38NwJ7u0SPt3M++TX8m8CfP38QwINP+uCCBwYU+gAP/I2FPsAD+iAt
WcwCs8AsMAtFiQd44H8HQx/gAX2Q/j6SWWAWmAVmwf6FJP59Ah7AA3jALMCD+FdjmMj7gv/0AH2A
B/RB+kkaZoFZYBaYBf1kHTyAB/AAHsCD+Hln/r+x/Ylr3hd4X+B9gfcF3hd4X4hfyOJ9wX8fiv0A
D+gD/wVN+gAP6AP7vVdmAQ/e6IM3PLDfvaYP8MB/BZ8+wAP6wB2gD/Ag2gAmMgvRCLw3wkSYCBOT
A8wCs8AsMAtyAB7AA3igaWBXhgfwAB7AAzkAD+ABPNA0sB/AA3gAD+CBHIAH8AAeaBrYD+ABPIAH
8EAOwAN4AA80DewH8AAewAN4IAfgATyAB5oG9gN4AA/gATyQA/AAHsADTQP7ATyAB/AAHsgBeAAP
4IGmgf0AHsADeAAP5AA8gAfwQNPAfgAP4AE8gAdyAB7AA3igaWA/gAfwAB7AAzkAD+ABPNA0sB/A
A3gAD+CBHIAH8AAeaBrYD+ABPIAH8EAOwAN4AA80DewH8AAewAN4IAfgATyAB5oG9gN4AA/gATyQ
A/AAHsADTQP7ATyAB/AAHsgBeAAP4IGmgf0AHsADeAAP5AA8gAfwQNPAfgAP4AE8gAdyAB7AA3ig
aWA/gAfwAB7AAzkAD+ABPNA0sB/AA3gAD+CBHIAH8AAeaBrYD+ABPIAH8EAOwAN4AA80DewH8AAe
wAN4IAfgATyAB5oG9gN4AA/gATyQA/AAHsADTQP7ATyAB/AAHsgBeAAP4IGmgf0AHsADeAAP5AA8
gAfwQNPAfgAP4AE8gAdyAB7AA3igaWA/gAfwAB7AAzkAD+ABPNA0sB/AA3gAD+CBHIAH8AAeaBrY
D+ABPIAH8EAOwAN4AA80DewH8AAewAN4IAfgATyAB5oG9gN4AA/gATyQA/AAHsADTQP7ATyAB/AA
HsgBeAAP4IGmgf0AHsADeAAP5AA8gAfwQNPAfgAP4AE8gAdyAB7AA3igaWA/gAfwAB7AAzkAD+AB
PNA0sB/AA3gAD+CBHIAH8AAeaBrYD+ABPIAH8EAOwAN4AA80DewH8AAewAN4IAfgATyAB5oG9gN4
AA/gATyQA/AAHsADTQP7ATyAB/AAHsgBeAAP4IGmgf0AHsADeAAP5AA8gAfwQNPAfgAP4AE8gAdy
AB7AA3igaWA/gAfwAB7AAzkAD+ABPNA0sB/AA3gAD+CBHIAH8AAeaBrYD+ABPIAH8EAOwAN4AA80
DewH8AAewAN4IAfgATyAB5oG9gN4AA/gATyQA/AAHsADTQP7ATyAB/AAHsgBeAAP4IGmgf0AHsAD
eAAP5AA8gAfwQNPAfgAP4AE8gAdyAB7AA3igaWA/gAfwAB7AAzkAD+ABPNA0sB/AA3gAD+CBHIAH
8AAeaBrYD+ABPIAH8EAOwAN4AA80DewH8AAewAN4IAfgATyAB5oG9gN4AA/gATyQA/AAHsADTQP7
ATyAB/AAHsgBeAAP4IGmgf0AHsADeAAP5AA8gAfwQNPAfgAP4AE8gAdyAB7AA3igaWA/gAfwAB7A
AzkAD+ABPNA0sB/AA3gAD+CBHIAH8AAeaBrYD+ABPIAH8EAOwAN4AA80Df+3+8H58vn5ebmcTvWh
KjerxSzPxsPBx+/f7+9Ws8qPP396UB3qRgLNcb/7O4HVZvtdYLt+PYPZoldgOX+xhLwTOJ0vl8v5
fPIStuvlfDp5xYMsCez2x7oVaMzDVmD81MThKATWRQiczvb8kwuURWQwHj25hUEIzJcmUB2OTRKo
j3sTWC2shPFo8PAaP0JgagKb0gTq5mTPb45ugbdBCHw86IPfITCZzu0ayt3+UNdN09T10SrYbpbR
RyNP4G4jhcB4MrVrWG93ldkY52Bt5Bb4LT4UeHeB4XiSz9yE0l2Is7c72Kzdgiw8fLfT28ouMBiO
szxq2FoR+8PhsLd4S6C1wC/hjsCvXybQmjBbWArbsqr2Fm7xloBXYJcwNA/j+T+HyQVaE6wGs9EU
dpWFR3wkYH041B3cFRiMxpnZ6DdpCnEKK8D6OG8teJBBV0MeF7Euiu12WxQbi/cmsDtoLTALezNQ
DZlfxGK5Wm/ieLwn4PEDbwK/g7sCbmMqwhRW6/V6tVpavDnYJtAvYFgyzfdrCm6DJRHHwt2AKEB3
cMOz9EkrkC4is2YIicViPp8p/jqJt0D8IhAppCImLhFnmp6vSQ4H+jOwGq4K2WSSm8Y0z/OJ5d8W
0HuHXQbuQlyl5zDOTCJO5uF+A9FEPVfwTcAb2hRMwjT8RLjV/zjeVPxyUxGuYBIh4n8M/fEdCL61
wNUOF0gKKYlhiNh/LVzxdwsImRsFy8Lz8GAPf5q/K4SA52B3YUm4F210Sr+vh68F/FBIGq5jct7A
Kf2+HrqqpBwiCc+iOx7+SryqSAoWYwoR24U/fn5k0ibRaSQBffWa7P2P9Nq4Ug+/fuGF57vul4Db
D+8/9Pt3buPaz76/6Mnn3zWevLz/2//26H4tvooDDx34D+RRoBAKZW5kc3RyZWFtCmVuZG9iagoz
MTYgMCBvYmoKMjU4NQplbmRvYmoKMzQzIDAgb2JqCjw8IC9MZW5ndGggMzQ0IDAgUiAvVHlwZSAv
WE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMTgyOSAvQ29sb3JTcGFj
ZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2a13bbWgxE46ZOkWKTqOKS///IDECClByqOGvd
l7v2eYhlRxgCc4AdJNGvXxwc+O8deHp6+teHKPT8/FTmPDZe/0AjQr5/fVDiPOz5+fn820cU+vcr
djj9T+9LtG8dQvtXncYdhe5dHvUynFal/c2bCsPjPfi1Pf7aNO4qXMR30b3GIwouoDfqkYp7G46+
088ih6tFXMQrehJHr13inoIJ+PP96ZPJNI6ETKLP4UoKF/EWPpvN5vO5fpXQAwpdAVa+sle4ghd2
XGSqJNoc/H1jOQwJWLwevlgs22Mas06hs+GKQGuAx+vpy9VqlSSJfl0uF51C2HBVwAvQ8xW+XCXr
9kijVZCTpqBcbwl4/Xq8wtM0y7I0Xa+TULgqMDjYFmDxit7YkUanYEZ2KXxP4kzAC/D4TZ4XRZHn
JqEczIYzgcsyQkBXKIHF0p6/KYrSjjQ22TqRDdOpXeXoULUCslD9KwdXHl9WVV3XVVVKIV3LhkjB
3z2WgQtYAqu1nl9W9dZObQpKYbWYzdoarguogulUCSTpJi+r7XbXNM1uu5WCpyAXvIZxAesiNbF6
wBLIi6re7Zr9ft/sdsrBUjAbrRXGulGarUBnoRKotwo/HA6SUBXugmy0Gu4KWAWWgMKPx6Mkdtu6
0EWs7gm4h+0dmAON4k+nkxSaXa0a0kQTcdYJF+3sJdgg6xLdgtISOJ7e39+loCJK1aBWMIHohDEB
9bEEknVWVNvdXvEfHx9SkEBl9+ACboLdw6iAtdHSLVAFp07gJBckkLlA6+J1AbtFCdgdHBT/+fmp
FCRgJphAdw03BOadQFtBK3A8NJ1A3OMtAe9D8/CoBL6+vpRCCGgiH8hAk5SphBGB9HGB3NroMgO7
hp8IyMNBQBfp9/hDgZMs+P37t0xAAA/oA2YBHsBE/eHMnwt4YEsafYAH9EFuf2djFvCAPsiYBf0z
FH2AB/bPkfQBHtAH9p8L9AEe0AcT+38uZgEP6AP9rzWzgAf26QX6AA/oA/scC32AB/SBPpPFLOCB
fTaPPsAD+uCXPrBIH+ABfaAPHjMLeGCfP6cP8IA+MAfoAzzwNoCJzII3An82wkSYCBNbB5gFZoFZ
YBbCAXgAD+BBTAO7MjyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN7AfwAB7AA3gQDsAD
eAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AAHsCDcAAewAN4ENPA
fgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/g
ATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP
4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD
+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7AA3gAD2Ia2A/gATyA
B/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDTwH4AD+ABPIAH4QA8
gAfwIKaB/QAewAN4AA/CAXgAD+BBTAP7ATyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN
7AfwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AA
HsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPw
AB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0
sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsAD
eAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7A
A3gAD2Ia2A/gATyAB/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDT
wH4AD+DB/5sH7x+fX19fnx/vp+N+WxWbdLWcTydvry/Pzxr/p0CBf/2LB/Vuf+wFjofmhwKb8rtA
XeaPZ5CkowLZ+sESlr2AaviUBe8qQRlk6+XiAQ9m81Zg2xxOncDpsN91ArO7Jk5agaJygfePDyVg
AlXhGcwmd27hrRXIJKBrUAoS0CU2EtikKmE2ebt5ja8usFpnhV3DQQp6/vGwb7alBBIXeL3RBy8u
sJBAXtaq4Xg8nU5HWegWpMlirgxeX643kglMZ4tVkuZegxR05MC2NgvuCjx3AstkvfEU9gc7KsD7
cL3qb/FKK5vA21TXYDUUVb1rmv1+36gAu8Q0Wc1n09bDUYGnJwm8vk2nc6tBKegiJNHsdtvK70B9
KAHz0Ebp72Eygb6GNNvoImpJqP66lANKYDHrPLwnoBTWqYooq9pOpXg1wUqX6H14IwOvYaIaZKOK
KMqyqqrS4nUFZuF00nfBaAlRg7lgOeSFnTzPrIAhgeseuIC1gi7CFDabPM83myz1AtRFZ210CSSj
kpx5HlJwhTSzo3B7vq5giL/AWfdNCHg3yoaVklinilZ4xPd9fFVgKGLhEomOwv35kYBZcEVANbRF
mA1KYqk0FL1ceP4qwAbx7y4cSugE1NBSMIn2zOcz1e8kuCfQK0wmU0lIQ0df1QD+/IgfLcHvoVd4
MwkXsS/+eAfB1QKsDm/x1gZNlSRcxL5oBlX/nedfKGguJeEi9sXseyC+TcGq0F2YhGvYwy/irxjg
d+FFhIJLRLSlPzYDHnb2S6vgEpZFfyz8kfjOSJuK9kghXnbaZ08bf9m9b9BoBeLH40GXP4339hrD
D275dyZyFnD58uw9d15exnXf3Yn5/tvfNL7/9mPf/9ujH9PmXThw4cAfgojqDQplbmRzdHJlYW0K
ZW5kb2JqCjM0NCAwIG9iagoyMzAwCmVuZG9iagoyOTcgMCBvYmoKPDwgL0xlbmd0aCAyOTggMCBS
IC9UeXBlIC9YT2JqZWN0IC9TdWJ0eXBlIC9JbWFnZSAvV2lkdGggNjUgL0hlaWdodCAxNzggL0Nv
bG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQg
OCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtWtdi2zAQS5vEK3asveWR///IAnck
LVnTeeoD76GRbQHEDY8SfHvz4Svwf1fgTzdel9pF6/UrHEO0PLOWYgLOp1dROPzfTtgnVzCYWztg
vVxJ0YO/uxAO89qsiA5ewR8fH3rRoZhhUDzvJQpgF3jIp/WGaQZ53eCB/XSBB0ohd0wSWAG6OtAb
E7jsMUy10wgQvKC3JjYbQ2GzmNBAAtzC7LE4wDsT2y0pKMKUYZTArE88lid6v98fDgf8u9+BYpHh
sT7lbwE/HL4kQLLbUcRDw5gEJVD9WH8P9FHj64sUwmCTmCDQAoh+4I/H0zfjdDqCggzIguOApSYJ
TAG4PuBnDXAcDQOSmCJwGUCA4AEPQkYQnA0DyzCRBOFooVRA8Fg+CMIojuMoCoVBkxACHeleGpaA
EwCCryPwgCcMUkCDJPGowlMdlEBbwAROik+zLEtTUEADysA6uhz6hXQEn58qAOsnSZbleQ4KYTgd
D/tFAsmAAr6DKE7TvJAgQxhAwn632dg+DFPgEHCItQJhnGR5UVZVVZZ5niZRyCpoDjoKgxSUYEMC
CkiwflnVdV1VRZGlcXh2OcwTbHdSQgggvmmauoYGSJActls3jCMKOIZo4gE9DCGgLOumbdumqcoi
S+IAOWCe2YZ3GYTnOZAxAsEeBEEoApr2crm0bV0VueTAIswSaBOkBGlWVDXxiKYu8yyRIpCAk8C2
jyiQTxLU8BxEyKAGwfV6JUGFHNhIKpBRmiTAJxEJwpgEzeV6u92u17YBQcoqulmcIWAXQcAMOgTo
gxBglJYUSBeFoGmvt/v9frtdWhRBCDiLywTsIhUMCM7s4yoCzOGQgLP4AkFe9hSgii8ToIm3+8/P
z/1+vbANnsDXwM+Bfy/4zwP/mei/F/x3o/99gB+q/jeSr0Hi5yDyNcD/2vwc+BpwF8nPga+BnwPu
R/o58DXwcyCb+/a9YPeVf7OnOtgWfm1TdnRjev2+stlbH+xsi0OxYmfbbs7DntDd/cfeOtyuZQKz
u49v187uPiwOtQcWCWCRUIEYFM1FDQrxF8SlWfYX6LGoRZKLRWIcDro08NuWHQ66PHTqMAjiUBiT
hvaCbK2LSTPjsYhNRJcHNlHG/X21iWixpHEg7sC8y2N9JjVZCpRRoqLJgxo6n0nN46HLQ68NVpl6
dbTa6JQhStpMEUugdt+sVWbNOph9SELNuoICjM3EMZgggGUqljetLjYygVdVlGVZAA8BtNrYxWm7
kASmCGwk/EJogN8IyxJ4EYA53KxyPCkBjiUYJBIkYAWISbRk2tJ0RicjmKYpHFcYpvB96Tb2/MqB
12ZsYxqGYpqKbQvbGMYxfWPj2X7Sd55RoGUEA31v+NYRLGN1rq31PUGAoYD/Zi1Hcb5hvMO7Zljj
m57vtHVuCbQRLAO9e5jv6t5LAfSzgAn0ptA8EAX2+AI0CMWJcVTr3prOMwTmAAUPQJjzCziAgDMM
5gTDigMMwgDjlAxCgSMUPESBAxBYX2dAWjCRAsuoJwDAwCMcPH9h4FLA8RY6NvqgDwYeAyEJ/9hD
IHp6YbyGoCGBMnAc5BiLgAmX/BcEPDGAQkj4B3B5E42MoNPPC5FADSgERFCGggnn8ksEfQblIA/Q
D/joEDkdqkFEUIULrq7Lz+NtFsoADBgE6+BLeFcIaYfFPuAr8E6EtpQcJi/+cbnOXnQA/ctZVO/F
Ps486t2x/OCZYxkxcsfvlh4h8k/5CixV4B8ilHC9CmVuZHN0cmVhbQplbmRvYmoKMjk4IDAgb2Jq
CjEzMDgKZW5kb2JqCjI1MSAwIG9iago8PCAvTGVuZ3RoIDI1MiAwIFIgL1R5cGUgL1hPYmplY3Qg
L1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NCAvSGVpZ2h0IDQ3MCAvQ29sb3JTcGFjZQovRGV2aWNl
R3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlID4+CnN0cmVhbQp4Ae1dWXviMAzclnKFm3IkEI7u//+ROyPbBGgSYvzt2+ih0CQjS7ID
lmUyf/5IFIH/E4EPL+9oD9jwGqUjgB5eu2t4gN39001DBfh0Uh346KAhXO3BTzpeKXhC9yBRGhze
IMQGsQPuXKsFFZzILy98Tw0vFdgFvNKD+ybUcq+h2QLiHRwQYgcQvpoGnuEVTXieI9wad+AhxKkI
JthF9Rru4IYGdgQxFbTB+cCr6vCmGM2zdRpO8NiEKuCGt8Bd91uDHTfrCTd05mVsGswCH4IaCzye
vQY42s6yyWQKmUyyjBqcBb4X69un9Tc4wDMTqPiloAUP3+F4NpnO5vMFZD6fUcHYYsCBREsb8ea8
hy+WJgungB6gE2rxt+A569H6bL5YrlZryGq1hAa64EJQF8IKz56j8YSvv03WVEAXnAev8MPRGL4T
vtlsIZsNFcym3gDeSdbcfQh8+71evz9E8wgd4dudyZYKzIPhsN8PEXwIYYVH148zOA/jt7t9Dtnv
tt/rFTxwBrTibeggeIsl4XleQJwCeDDJLIK+B57bh1ufGPmD0ShD8GD9bl8UB0hR7HfwgBEYjTAI
GQBG4Ml/h+fYAZ7N7/PD0eSQ7+HB0hwYDJrxvPPoPsx3zR9Lk6MzABHkEHC3cV37Dj82PL0/lOUJ
UpaHHCGEAxMO4jb8F9pn75n5xbE8nSGnEgbAARsCwENBvf/84DA83N/s8uJ4Ol8g59OxyBFB60EO
4dd4ug/zzw5/pgMbF8BXeI6e6Xxl0S/PlyvkQjwccB0wbG9/OMo83sx3eDjg8RhBL/G4ddk+8Jfr
D+R6CXgbgR3wi1o8O7Bb+wsbvI/t7zZxeIY/2O86IB5//fkL+bkKzwGs+MWMX44/jR/dP/r80Oen
vj/0/aHvT80fNH/oPv/X/EnzR82fNX/W/FnzZ82fNX/W/FnzZ82fNX/uUr9g/UD5g/IH5Q/KH5Q/
KH9Q/qD8QfmD8gflD8oflD+07l/D/jFs31P+pPxR+5e0f0v7H7X/U/tftf/XNrArf1D+oPxB+YPy
h5bfDyl/Uv6o/FnrB1o/0PqB1g+0fqD1A60faP1A6wf6/bR+Px71/APtX9T+Re1f1P5F7V/U/kXt
X9T+Re1fVP1R9UfVH1V/VP1R9cfa51fy+Y2qv6r+qvqr6q+qv6r+qvqr6q+qv6r+qvqr6q+qv6r+
Gl1/TXl+/PPz86PWbxOfn5/2/P5E/oA0/gLHv/A+f0Iif0MifwT5L1L4K9L4M8j/kcLfkcYfQuof
I9CwXxDH85cYvkfqnAT+lET+Fu/A2/wxhucQfJ+/xhhgovlzwOVCChrrAXKY0AIy8HTl76nw7MIU
/qAk/iKjb7oRIMXzJwFPBqX3+ZvMAFMQzR8VesATUBkDVQx/lcM7DxhEI9+K4s+6WWAsUtQAIyL4
uyoLzAdPAWbkX1hzD7RBj8RB9yRCfhAZBxg1wAsnfO9Jh554f57g3gIGgR1ZiR3gCG9t/WaAM8Hr
MKznfHqJDxbcNESi70y4qTCz3Z9f/tYeuAM8vK29uO7gAyr8U3dh87GACq/NVzafScE2a9UZRaCK
wD9Pl+IjCmVuZHN0cmVhbQplbmRvYmoKMjUyIDAgb2JqCjExODYKZW5kb2JqCjI3OSAwIG9iago8
PCAvTGVuZ3RoIDI4MCAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2
NCAvSGVpZ2h0IDE5OTEgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUg
L0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtndt6
okoQRhMVQUXEs8Zj9vs/5P6rGhpNUHH2t69m1cUkk/hXV1U3QtfC8PGBUYH/qwKfsj/0bdLG3nTS
CJvvurtoNPffdfRwI+rJbv7bxUF8uWlriz986aF6ZS1svla/eOEgvCqo+tHC/8Pvnjpo5K4duPm3
5uKlgyg3SRA3Ljo4ML0NFNRJNDnRj+w39opHGdjvXO9jJ8kwWpK4h0r/yEOl1uiDganTaMOheXgR
QTW6x+7qLMtGMn1JU/fgOfjLWlLwnyt7H12Dm3jsZi7MQYggvO63gzi8glfopp5UNpYHhXDroF0f
R9fgUuf5VJbnk8nYQ7hx8ESv0mn08UTiwk0u3IEV0WpokT7UW+UreTGblbLZrAgOlIEctOvNpy0c
Tz6MXszKuVt540A1bFtFJq/0VvqRgpd6sVjKFot5ObMIbBIa/V0KjT5En08LyZcrt6UcWAqaBM1B
PX6bvt/37MeTaTGTfL3eyNZrObAULIAkqSv4SG/Fy5W75Jut20YOVINck5i+0NvSseyV/HK12e72
st12s1paCZoEPN3bKQzVU/mTYZYpfEW/Wkv+JZOD9coyUAWzqgC2Blr1w6GH79FLfpDJgWfgCWgG
rIDteh06IfxCw2+2kh9lcqAMFECYgXAYt41vR+4wHY0sfBVvJ/lJJgcWwNwKMEo1fjUDv+K3I1d6
S1/F1/DH01l2OioAm4KpjgLp62OgTa/y++x5+IfT+SI7nw6eQGkF8BUUjoEn+lL6nQ0f9EcloAJ0
0ac+funpH8+Xq+xyNr0K4Po0HsOt44fVJ/12f2j0SqDSawU+zT/V6smLoD9drt+y68UK4Ho7Bl/r
dej6+D/1msCO+rkW7/5wr18t3tF7+WP8YQLe1Z+v3//Ivq8+Ae+Pj576sX44fnj/4P3XLgA4/3Q/
/9v5m/Mn50/On5w/OX9y/uT8yfUD109cP3XrP829/cb1I9ePXD9y/cj1I9ePXD9y/cj1I9ePXD92
4bdcP9N/pv/O/pH9I/tH9o/sH9k/sn9k/8j+kf0j+0f2j/0n93/b/dO6fR3+xP1b3L/G/fPaPrJ/
Yv/E/on9E/sn9k/sn9g/sX9i/9T++Wl9fjlh/8j+mf4B/RPuP+D+A+4/4P4D+kf0z+if0T+jf0b/
jP4Z/TP6Z/TP6J/RP2v/+4n0D+mf0j+lf0r/lP4p/VP6p/RP6Z/SP6V/Sv+U/in9U/qn9E/pn9I/
pX9K/5T+6e/n/3D/Kf1z+uf0z+mf0z+nf07/nP45/XP65/TP6Z/TP6d/Tv+c/jn9c/rn9M/pn9M/
p39O//zmAfRaDr0e/AB+AD+AH8AP4AfwA/gB/AB+AD+AH8AP4AfwA/gB/AB+AD+AH8AP4AfwA/gB
/CBWAH4CP4Kf8ffv+fv/PD+P5wfy/ESeH8nzI3l+JM+PFD6DH8GP4EfwI/gR/Ah+BD+CH8GP4Efw
I/hRpCcfH/AT+An8BH4CP4GfwE/gJ/AT+An8BH4CP4EffcOP4EfwI/gR/Ah+BD+CH8GP4EfwI/gR
/ChWAH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+NkZfgY/g5/Bz+Bn8DP4GfwMfgY/g59FesTn
r+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz77gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+FmsAPwM
fgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfxsAz+Dn8HP4GfwM/gZ/Ax+Bj+L9IjPn8HP4Gfw
M/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GcL+Bn8DH4GP4Ofwc/gZ/Az+FmsAPwMfgY/g5/B
z+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/m8LP4GfwM/gZ/Ax+Bj+L9IjPn8HP4GfwM/gZ/Ax+
Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/jZGH4GP4Ofwc/gZ/Az+FmsAPwMfgY/g5/Bz+Bn8DP4
GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz1L4GfwMfgY/g59FesTnz+Bn8DP4GfwMfgY/g5/Bz+Bn
8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/G8DP4GfwM/gZ/CxWAH4GP4Ofwc/gZ/Az+Bn8DH4GP4Of
wc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+FkffgY/g59FesTnz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwM
fgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz3rws7+An12u37Lr5U+uf7f7w6nWnw777XvXT8v1T/16OZ91
Pf8WZau+6KYf57X+fLnKLmeLX+MX+bjD+W9U6a2BVOmPX7tKP3r1/NBh6vpFaMCdL7JzVX4bf5QO
n//94KCfmV4TEPQKf6fylx30A9dPZwsv4PF0lp2Onv6inPr4gyfv/33Tj6yBvFxvVIDjSXZU+psw
fSPFL/nD90/TZ9IXcyWgFXB0C6vHpl/le6Lv9aQfZqGASmD3dXDz6of0s6H0PVnb+5fpk2GWjXMl
4AHsv2R7W7xafSpflln52/WfRhClT50glKrgZrvby3aW/aIMqzfoNfrnz/cP1/dNbwkoAHew2+22
Jtfw07Gln1TVe6RPUq0gVbBUBuuN23q1mJeFz16aPNVXCSiA6cwcrNaylcln09yrH9J/FL/rbQlN
lIEcLN1MXuQTW7xV+Z7ovYKegRzMF7K5yXXoevZafWH27vMXyjefPgOhhJN8qhDcpLbR7djx8O2V
N+y/+rbS2xTaIlYK06KYyYpKrrUTj71nes9AkzjJ86lbbqNnNnfx2HmgDxC6djCeyIXEk/Ev+WO9
U1yVIM0UQmU2eEj+UfGq+oU12B94DcyDm6u9dnHttYxfz4ACUA0Tq6IFYWKbdyu9ye3Ia1UHvSrg
DoIHcyGxq2/kD/QxAquBcvAgXKzC+7vWs9FtGVhsFkEIIbhQ4K6uD/tH0fsycge1BwvCTYk36ofB
/3BgMUSzmLxyT0evM6iSCHn4yFH9Sl/VoPFgA8tCYq/VNyE0PmpxJ/m9h0aq77xCnf65k9X/6aSs
X1SL6q/1z9/5+l+074zDa//eCvwLEtnTHAplbmRzdHJlYW0KZW5kb2JqCjI4MCAwIG9iagoyMzEx
CmVuZG9iagozMDUgMCBvYmoKPDwgL0xlbmd0aCAzMDYgMCBSIC9UeXBlIC9YT2JqZWN0IC9TdWJ0
eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdodCAyMTMwIC9Db2xvclNwYWNlCi9EZXZpY2VHcmF5
IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4Kc3RyZWFtCngB7Z3beqJKEEZzUlABRaOAeMjs93/I/Vc1h5ggkuxvX82qixmT8a+qrm6E
rjXI0xNGBf6XCjx39nP3nbR78RMfnejmxVQPN6KbH6Z46AUvnfW/e+ihfWunbV60v3/goHlbEL02
Fn5q/mncQXiTCVpx+Nt+E/5tVO9vadVvnZmPzsOIg89yiWeN6WXjwd9wz0HIT3H05qCeu5kX9/Bg
DG10l89m0kZuemEOlEPrYDgD03t0y9zEcWNRFDx0Dob0bfaWu+SmXjQWx/IQxnB/FprsLfkgXyyW
y5VsuVwszMF8ZlVsHHzPoNWH6AouceJmLpRCyGBUb6WXfh5JvVwlaZpmWZamiTwoBSXgNbRIw/Gl
b+UKnmZrtyxNkt5BSOC+3gYfW/Bsvdnkss1mLQ9y4CNoCvBF3wy+Cx/k+dYtbxw0IxhaBL1eE6/B
e/R8u3uX7bZKQRmoBD4Hj/Qq3ipR8vnufe/2vsvzdZasQgkHF2ET//V1NosizVwa5IdCdtgrhc3a
Eoii2WxwCbT6MHcKv8m37/uiKGVFIQe5RtAn4G//XMIbvYff7vaHsnIrlYElsFp6BYeWoPQqi8o/
C9WzwR+K6nis6/pYaQiWgFdQi9jeKcGX+EFvS8/SV/iiPNYnWX0si4NVIFTwvt4OHdenmYUvq/p0
lp3qqixUAQ3AZqA7iL7FD3qvfu7hJb9cLueTErABqABag2P6N8W3xbO24lt4yaVXAlZBn8F5dwwN
xLfpkz6T3tI/X66yy7muqoP0VkA7CJsVMKLf2PCPp8v1Q3a9nI7S7/IpejvyVX4Nv7rRWwF8AqPx
+H7oBn199vBK4Fwfg95W0GN92uv/yHq9r8AJ+rVNn8p3/fis34YVPEkfyv9JX2oCfqZX+Ty8BnA5
1b/U/yNDT/1YP787/jh++Pzg85PPTz4/+fz8zfUb5w/OH5w/OH9w/uD8wfljev8ltJ8+/nD+5PzJ
+ZPzJ+dPzp+cPzl/TuM/65zrB8N3XD9x/cj1I9ePXD9y/cj1I9ePXD9y/Tjl/09x/cz+gf0D+yf2
j+wf2T+yf2T/yP6R/SP7R/aP7B/ZP47eP2X3L6Xsn9k/s39m/8z+mf0z+2f2z+yf2T+zf2b/zP6Z
/TP7Z/bP4RtwBr9/hf4B/RP6R/z/bf/6JfoH9A/oH9A/oH9A/4D+Af0D+gf0D+gf0D+gfzD4/b/2
zdf0T+if0D+hf0L/hPv/+f4Dvj9LDUT6R/SP6B/RP6J/RP+I/hH9I/pH9I/oHw08P4v+Gf1D+qf0
T+mf0j+lf0r/lP4p/VP6p/SPef4oz1/l+bO/en4v/38d/gZ/hD/CH+GP8Ef4I/wR/gh/hD/CH+GP
fP9DX4Hn5+eXF/gz/Bn+DH+GP8Of4c/wZ/gz/Bn+DH+GP8Of4c/w5zX8AH4AP4AfwA/gB/CDvnv+
9ET/HH4AP+H7v/j+M56/x/MHef4iz1/k+Ys8f5HnJ3D/CfefcP8J959w/wn3n3D/CfwIfgQ/gh/B
j+BH8CP4UV8B+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8
rKdH3H8FP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/6
CsDP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4Gc9PeL+M/gZ
/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+1lcAfgY/g5/B
z+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/6+kR95/Bz+Bn8DP4GfwM
fgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8LO+AvAz+Bn8DH4GP4Ofwc/g
Z/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+FlPj7j/DH4GP4Ofwc/gZ/Az+Bn8DH4G
P4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Of9RWAn8HP4GfwM/gZ/Ax+Bj+Dn8HP4Gfw
M/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HPenrE/WfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+D
n8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/KyvAPwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4
GfwMfgY/g5/Bz+Bn8DP4GfwMftbTI+4/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/B
z+Bn8DP4GfwMfva38LPrxx/Zx/U31z9FVZ9b/bk+Fj87f+72X/X7Xb6e+vmbbQb12TT9Mmn1l+uH
7Hqx/BU/S5YTPv8Wjd4aCI3+dKwa/SJ+8Pkxj1y/DQ2Yy1V2uUiv8ln8RTSfjR5/Qb82vSYg6M91
VUq/maB/c3263noBT+eL7HySfr/bblKP/zYS/9X0C2sg7vYHFeB0lp1Ox9KGr+lbKH/J7x4/po+l
z3INQCvg5FZXRaHhmz4e07+8SD+PQwE1gPJYuyn8Qenb8OO54r/IBLy+8T/Tz+ZxvEw0AE+gOsqq
qjhY+tLHsZV/WP9sBEn6yDvIG1XwUJSVrCwPe1U/rN6gV/Rv8V3/anobgBJwB2Wp5PfvFj5V+pr+
pnr39LNIK0gV3GgE+4Obomv0PnvRbFTfDEAJpGtz8L6Xvav2Kn7i1Q/Dv5e/620JrTQCOdi5bfON
ireyxduUb0TvFfQRyEG+leUm16Hro9fqC7N3O37Npfn0GQglXCWpUnCT2uR27Hj69s7Pkx9eN3qb
QlvEGkKaZWtZptJp6dja6Y69Mb2PQJO4SpLULbGxxzZ33bFzRx8gZOtguZILiVfLb/L7eqd4KkEU
K4XGLHgY/L3iNfULa/D1zWtgHtxc7bXr1t5A/HYGlIBqOLMqWhImtnm30pvcjrxBddCrAu4geDAX
Erv6k/yOvsvAaqAxeBIuVuH9U2ssuq0Cy80yCCkEF0rc1e1hfy97X0XuoPVgSbhp4L36bvJfHFgO
nVlOXrnR6O0ImkGEcXjkTv1I39Sg92CBZWFgj9WfUuh9tOJJ8lsPvVSvvEKT/riRtT9MUrZvakXt
3+3vf/L3f9H+JA7v/Xsr8C8No4C7CmVuZHN0cmVhbQplbmRvYmoKMzA2IDAgb2JqCjI0MDIKZW5k
b2JqCjM0MSAwIG9iago8PCAvTGVuZ3RoIDM0MiAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUg
L0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDI3MjAgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0lu
dGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PgpzdHJlYW0KeAHt28l6WjkQBtBMNmDAzJjBQ9Lv/5BdpXvLI2CnV704d2HHMSqkX6pjfRm+ffNI
4P+dwPc3z9/O9c3g7ou/KXFiePutL9Y4Nzx+/0sVnsf/ePU8/+bnJfqXvhrc/bJKfFLh9fCfL0+r
0X/vYoVX49voX/l0dbJG9+0LFboX5EtzUBvdf4gvv1KhFejGx8Crl6ebR3ynveLsFGoC7d1j9PXz
c3XVVvJZhSwQr+nHX18P6olCXYm+wrkp1PicfQ4fDoej0Sg+DgeDL1RoC2gTyPE5fDS6ySeLvKrQ
XndqDvmNl/Ex/OZm3D1ZYziIZWQQXZDnC+Tu5fvHu48nk8l0Oo2P4yjRVWi7Ge90pkAXYIwfDuPt
Y/RtPllj3CpEkv0ULhSI948Co3j76e1sNp/PZ7OoURViEW0NHwt0CfQLiPXn8Pl8kU/UeFXhTAo5
PiLMAvn+N+Mcv1guV6vVcrlYZIVuEbWGePmbWVSBluAw1p/jV6t1PlEjK7QYMoWTTdUViAnEEWgL
yPHrzWa73W4266yQMcROtBjbq0/NoBUYtAnE/Neb7V0+26ww7xbxWYG2gpbgYrmK8bv9fr+7227X
q1jEZJyHIffh9AzyFHYryARiAdvdbn84HPa73d1mnVOoNZxqqajZFbi+jhVMb+exgLv9/nA8Hg8x
ie0mppAb0UK4XCAimExn81jA7nA43t/fH2MSMYXFPNcwGLRtaIt4v43tFMQxjghiBTmBGP/w8JAV
dttuDRHC82n+sAvPBSKCWMF2t4/xj4+PWSGmkDuZIWRLnujIlkHXiKMWQa4gxj89PWWF/d22C+Gz
AtlIUWC2WMYKcgJdgftYwypD6I/S+Rk0CbLAKgvE+N+/f+cU+hC+VCA6OQvECl4ViDVkitlQeRYv
zqDtYitwHxP48+dPTqEKxFn8SoE8h5nh+wKxDV8s0HbxXYF2Fv+iQG7Cqxkcdv+hwENE8M8//2QI
sQ0KyMA50As8YKKfC342xiXN/UAGeVl3DmTgHCzXMpBB/hmMcyAD5yD+QFMvyCD+TNU5kEH+DYlz
IAPnIP/O2jmQgXMQf3evF2SQ/4bDOZCBc5D/Jsw5kIFz0P+7ND8XeMDE9m+F/Vzwc8HPBT8Xvn2T
gQzyvxE4BzJwDjIB50AG7RgwUS+0g+BnIxOZyMQuAb2gF/SCXqgEeMADHlQ3uCvzgAc84EElwAMe
8KC6wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEPeMCDSoAHPOBBdYP7AQ94wAMe
VAI84AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG9wMe8IAHPKgEeMADHlQ3uB/w
gAc84EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEPeMCDSoAHPOBB
dYP7AQ94wAMeVAI84AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG9wMe8IAHPKgE
eMADHlQ3uB/wgAc84EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEP
eMCDSoAHPOBBdYP7AQ94wAMeVAI84AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG
9wMe8IAHPKgEeMADHlQ3uB/wgAc84EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCA
BzyobnA/4AEPeMCDSoAHPOBBdYP7AQ94wAMeVAI84AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCA
B5UAD3jAg+oG9wMe8IAHPKgEeMADHlQ3uB/wgAc84EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4H
POABD3hQCfCABzyobnA/4AEPeMCDSoAHPOBBdYP7AQ94wAMeVAI84AEPqhvcD3jAAx7woBLgAQ94
UN3gfsADHvCAB5UAD3jAg+oG9wMe8IAHPKgEeMADHlQ3uB/wgAc84EElwAMe8KC6wf2ABzzgAQ8q
AR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEPeMCDSoAHPOBBdYP7AQ94wAMeVAI84AEPqhvcD3jA
Ax7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG9wMe8IAHPKgEeMADHlQ3uB/wgAc84EElwAMe8KC6
wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEPeMCDSoAHPOBBdYP7AQ94wAMeVAI8
4AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG9wMe8IAHPKgEeMADHlQ3uB/wgAc8
4EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEPeMCDSoAHPOBBdYP7
AQ94wAMeVAI84AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG9wMe8IAHPKgEeMAD
HlQ3uB/wgAc84EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4HPOABD3hQCfCABzyobnA/4AEPeMCD
SoAHPOBBdYP7AQ94wAMeVAI84AEPqhvcD3jAAx7woBLgAQ94UN3gfsADHvCAB5UAD3jAg+oG9wMe
8IAHPKgEeMADHlQ3uB/wgAc84EElwAMe8KC6wf2ABzzgAQ8qAR7wgAfVDe4H/1sPHp9+//nz5/fT
4+P9YbdZLWbT8Wh4ffXr548fsWvfawfb5w/buN0d7p8LPBz3d39XYLH6UGC9/PoMprOTBea3X1zC
+LlArOF3RpBLWC/nt5Obr2Qw6grc7Y8PfYGHyLAvMPw0xOtBK7DctAKPT085gSiwXbUZDAef7MJV
K3A7jwKxDTGFKPBwf9xHgcUsljAcXF3cxl+twCQKrGMbjlEh3//4vItZ4NeFc/CzFbiJAov1NtZw
f//w8HB/f4wVbJbzdo6iwM/zB6kVGN5MchtyDVEhnuNhf7fNTchdvFjgRxa4Ht6Mp20Nd/vDMZ/D
ftfOYe5in+GZo5wFrq6Ho/HkdrZcbba7/f5wOOxjfE5gNs0Mu004WeD79yjQhxBrWK5jEVFiv4vx
m9Uy9mCcBTLDbKWPzZQF+hByDYvVeruNEjE8x0cjtHN4nRleLHA1GI4yxvlytd5s89mso5HiHLcJ
tE04W+B5DZnCIiqsN5sYHu/fEog9eDmHJ5dQaxjlRsQclqt8ljm+JnBVp+BsgYyxLSIqLBbLGL2Y
x/jpODqxTaA/Ru8KBEuxsB+vpjCJOczm+cxieATQje/P8RvO+i/6At1GxCImUSJqzG5vpzU+E+gm
cLZAm0K3iFZiGs9k0r1/LSB38UyBWMNLhZjEOKYxiY83bf7x/jWBswVahTiOOYfhaHTTPaPRMPK7
TgliAR+P8UsGGWNOoVWIElEjnvg8yPHd+3fH8NQS2j68qnA9iKcNbsNfjz89vCtQFXIS8USN/HQV
04/5X1pAK9rOeFtFLCNKtCL56c3wkwl2k2oFcg4RRJZoNWJwPC9vf3oP+1W9qdBK1Oic/ak2fh9H
V6FNImfx/OTwr4zvg2zb2cZEhfb5efiFAGoy/SS6WdTo/t0vrr8KZFv2Tz+8vozPzy+6+ItXA97+
8uKoN998O67/6s0rPv/ifY3PR5x4xX976xOF/JYEPkvgXxhGgYYKZW5kc3RyZWFtCmVuZG9iagoz
NDIgMCBvYmoKMjc2NQplbmRvYmoKMjUzIDAgb2JqCjw8IC9MZW5ndGggMjU0IDAgUiAvVHlwZSAv
WE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMTIzOSAvQ29sb3JTcGFj
ZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2a2XbiWAxFq0iYBzMYY7DNUP//kX2kawEJhlBr
da/VD/s+dGiCjqUjaedWVX794uDAf+vA77vz90+6C25f/pXGY7i987ZEd/jbEtfw3u1c33sjifjs
LTq9ivd/kmg/l4I+2nMv8YNAireACL7XSN99JfEl/vN2TMVU/fsvBK7x+rxF99tjr5PEa4W7+BQ9
SMdkvig8mwgX8PLt4QoepqNXrcQPVZjAXfxwOEpHMiZhSbyy4cvz7emj0bg9o5EkXCFS6CqiFTD7
lP5Q0ZPJZDqd6r/jsSRMwZ30D3a0IgQi3qJnfiQiiVbheRESSAak508UPZ8vFov5fDZTGq4gG9oi
ujOw+bMElL/iFZ75MQ0lYTm4guX6QuAav8iWy9VqtVxm2UIKrwVaA3qeQHq+ha/9rJam0KbgM+0f
/5LETSAlMJtnCt9s8jzfbNauYEWoE68FrgnMFxafb/1IQjlEEWHjVxtSBrKw35eDMjDz+GK32xXF
Nt8oh7lSMBu7x/EmMBiqA0pgvdlud7uyLCWxzVWFpzAYXPvwkEEMgQTMgU1eFOXejxRUxEIpqJNp
FIwM3010AS2hKjAH8u2u3B+qqjocyl2hIjJrhNegTz4X0BCpgmy5zouyPFR1XVfVvtypCK9hOJQJ
TwW0KtbEyWyRrTaWQFU3TVPXh32pFKwGDdNtox5LSAKyQBVsit3+UDfH47FpKhWxtRrMhJcCvgdu
gVVwqJokUFd71eAmmEA0siODEDALlEDVHE+n0/FYK4Uit0ZaBtdJ6BQQiJSBLJBAVR9P5/P5dGpq
EzAXrY8/CVgXzUOz8CagGpKA1uFlCW0XTUAWns6Xy+V8PjZmQurjOwKpi10C1sc3MlAXtQgPAt7H
twXywqbgroSy+GsBNfF8+fPnz+VyOlobEMAD5oBdgAcwkZ8L/GzkflDs8QAP9Ecm5gAP7A//zAEe
MAf2NxjMAR4wB/aXuswBHjAH6R842AV2gV1gFz4/8QAP7NcfmAM8YA7020zsAh7Yb7UxB3jAHPzS
7+oxB3jAHOh3JdkFPLBfmWUO8IA5MAeYAzzwMYCJ7IIPAj8bYSJMhInJAXaBXWAX2IVwAB7AA3gQ
28BdGR7AA3gAD8IBeAAP4EFsA/cDeAAP4AE8CAfgATyAB7EN3A/gATyAB/AgHIAH8AAexDZwP4AH
8AAewINwAB7AA3gQ28D9AB7AA3gAD8IBeAAP4EFsA/cDeAAP4AE8CAfgATyAB7EN3A/gATyAB/Ag
HIAH8AAexDZwP4AH8AAewINwAB7AA3gQ28D9AB7AA3gAD8IBeAAP4EFsA/cDeAAP4AE8CAfgATyA
B7EN3A/gATyAB/AgHIAH8AAexDZwP4AH8AAewINwAB7AA3gQ28D9AB7AA3gAD8IBeAAP4EFsA/cD
eAAP4AE8CAfgATyAB7EN3A/gATyAB/AgHIAH8AAexDZwP4AH8AAewINwAB7AA3gQ28D9AB7AA3gA
D8IBeAAP4EFsA/cDeAAP4AE8CAfgATyAB7EN3A/gATyAB/AgHIAH8AAexDZwP4AH8AAewINwAB7A
A3gQ28D9AB7AA3gAD8IBeAAP4EFsA/cDeAAP4AE8CAfgATyAB7EN3A/gATyAB/AgHIAH8AAexDZw
P4AH8AAewINwAB7AA3gQ28D9AB7AA3gAD8IBeAAP4EFsA/cDeAAP4AE8CAfgATyAB7EN3A/gATyA
B/AgHIAH8AAexDZwP4AH8AAewINwAB7AA3gQ28D9AB7Ag/83D07ny+VyPh+P9aEsNqtsPh2PBv3P
j49eT+sbm+xfH9e5PNRNCDTVfvd3AqvN9rvAdv1+BvOsU2C5eLOE6VXgeDqfz6fT0UrYrpeL2eQd
D8ZJYLev6lagkYetwOhHEwdDF1jnLnA86flHEyhyz2A0/KELfRdYLCVQHqomCdTVXgKrTCWMhv3X
bXSBmQQ2hQTq5qjnN5VZYGPgAp8v5uDjwwQms4XaUOz2h7pumqauK1Ww3Sx9joaWwNNBcoHRZKY2
rLe7Ujb6OWiMzALr4kuBngkMRpPp3EwozAU/e/VgszYLxu5hT6dzlE2gPxiNp17DVkXsD4fDXvFK
oLXAmvBE4PdvCXwmE+aZUtgWZblXuOKVgFWgJgzkoT//cZmuAl6DbJTCrlS4x3sCmsNB9OCpQH84
Uh/MBVPwk6sAzfG0teBFBr3eZ6ph6o1Y5/l2u83zjeJtCNSD1gJZ2JlBr+cmKAU1Iluu1hs/Fh8J
9G0IrAdPBSyFVIQUVuv1erVaKl4Otgl0CwhL0lQGbQpug5Lwo3AzwAuIHnzhWfqfViAUpjM5uciy
bLGYR/xtE78C8U7AU0hFTEzCzyw9PzbZHejOIIpwhfFkMpXGbDqdTpR/W0BnD68ZmIAa8amBHo5G
Y0n4GVu4np9I0NGCbwKtgiSkYcfDVb8P4dN4qVhzLYWkMBjqSMS+DOzxVxB8G4GbHSaQFFqJgYkM
dPrX+FcJpBSuCnJCXniwhf+YvyXiKZiCylAS5qYde+Uc65rhWwH+KqowhaTRRtsAp/S7ZuimknLw
JJKGC/kCvRUfVbiXbSn2xU6rfXvYs1ftB1MWKfYW/jr/VjIUrmnc3ngr/lbGXWB6+Szpx/cfQu2N
x4+9fOe7xssPP/tmK/Ls27yPA/+eA/8AkRcDuQplbmRzdHJlYW0KZW5kb2JqCjI1NCAwIG9iagox
OTk3CmVuZG9iagoyMzcgMCBvYmoKPDwgL0xlbmd0aCAyMzggMCBSIC9UeXBlIC9YT2JqZWN0IC9T
dWJ0eXBlIC9JbWFnZSAvV2lkdGggNjQgL0hlaWdodCAxODM4IC9Db2xvclNwYWNlCi9EZXZpY2VH
cmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgPj4Kc3RyZWFtCngB7Z3ZduI6EEU7JIwGDB4YjM3Q//+R91TJU4gZ0mvdt62HXiTxKVWV
BJG0U+o/f2hk4P/KwMfHx7+alrTXfmmlp2xfvm+ildy9eM9CXzQajfpfvpOM5nlJu9Z887WB+slO
2ryqf/A8hr76s9fcSPjhUwP+iD/s4i9v/tK++cpA+Lk9KUnQ1v+aidcGmt7t6a+vcddkpWfgUQRN
94160rbx2C288MD07rseHo8nk2nbJhOz0IUw6EFPHtSz2Ww+n+vf2XQqCy8MuPfWfd25aRfezEZn
wJ8bmEe1XplT79PpTOIotMVCFuRC7YE/+DMCfTsEb3J5LvVyuVqtlstlFC3kgoXQpuCB3lLfyCVe
e5MNMyAHggFz4KFecnWv3iWO481mE8frdWtAOQzT8F5vNuvkBfnS1Ftvm7hnYDgCk9f6Wr6SOknS
NE2S7XYTywOPoMvAtxAavcZO+kW0XK0lTzNvabLdyANLgWVAbvrj/RCCPoydgnd5mub5brfL80wG
FEK0sBS6A8/03v063qZZvtt7y/M0UQ7Mgdf6ydS6V/AmPxyPx8Nhv8tSpSBkoB2B+/h98mjuzOaR
cr9NXF4UhSzs80wRtAHoScvAXfxBP5koe0pekqr3ojidTrJw2FkEFoAn4Kle4cv9bZLtDsfiVJal
LBwVQbJdK4DptJvDP/rX5NXoKXzLXr43eVVVslCYAxaAjaAGIMzBn3offQtf7ufyvqzO53NVmQMK
ICSgexM+1Fv4cr84VefL5XI+lycPwEYwzKDH/eu9M49C+Ed5H/RVqQAyT2B/Bg31rw8O16f5Tvrz
5Xq9Xi6uz1MbgNd6Db/6V/qKstMrgKDvz8Dh/sPwub66XG+32/V6rhq9BqCbwQ/1eusN6n0A39In
mfn/vf8sTIA39buD0t/67wPwW311vt7+/v17u13O6DWByZ99AL0//5g/vH/4/ODzk98f/P60BSC/
P/n9yfqB9VNzgvBk/2TbT+0+WT+xfmL9xPqJ9RPrJ9aPrJ9ZP7N+Zv3M+vkJfzL8FvAV+wf2T/Ar
+B38En4Lv+b8Hf7wm78/4fyV9SPrR9aPrB9ZP7J+ZP3I+pH1I+tH/v6Vv/9tK2D4+5UuAyqn8cox
Kz7i/N3LZ9g/sn9k/8j+kf0j+0f2j+wf2T+yf2T/yP6R/eOT+wvYP7J/5vyA8wPqv6h/o/6P+kfq
H6l/pP6R+kfqH6l/pP6R+kfqH6l/pP6R+sfB+1t1czHnh5wfcn7I+SHnh5wfcn7I+SHnh5wfcn7I
+SHnh5wfcn7I+SHnh5wfcn7I+SHnhwP//xXnp5wfU79J/Sr3Z/L/D3D/F/Xb1G9Tv039NvXb1G9T
v039NvXb1G9Tv039NvXb1G+POD/m/Li7/e7PH+6/4/6/EfwEfgI/gZ/AT+An8BP4CfwEfgI/gZ/A
T+An8BP4CfwEfgI/gZ/AT+AnAgbwgy4D8BP4CfyE+4u4v4n7m7i/ifubuL+J+5u4v4n7m7i/ifub
uL+J+5u4v4n7m7i/ifubuL+J+5u4v4n7m6i/gR919Ij6G/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+D
n8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+1mUAfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4
GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/6+gR9WfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4Gfw
M/gZ/Ax+Bj+Dn8HP4GfwM/gZ/KzLAPwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/
g5/Bz+Bn8DP4GfwMftbRI+rP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+
Bj+Dn8HP4GfwM/hZlwH4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn
8DP4Gfyso0fUn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP
4Gfwsy4D8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4WUeP
qD+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+Dn8HP4GddBuBn
8DP4GfwMfgY/g5/Bz+Bn8DP42eV6u92u1/O/nJ/vi7Jq9NXpuP/V+es2ze/1efr2+eUqHtRv1u+d
/0Wt/ny5Xq+Xy9n8z9PNerl44/xsXuuPp7LWV2VxqPWz2Yvzp8nU9Um2M/35ot7Ppt9lifU/mz7X
j12/9g/w4lQFfXk6mj52/Xj87PzH9fYLMM0Pxamszuq9Onn4Sbyy/sdfj/Wfn6ZfLNc+AMeiLKuq
KsuT3G+GT/rPz0fnL67XAkQDkGT7gzLgrbDZk2x9+J7pR6afzBbRygLY7RWBt6Nl39M39/SN1LTh
63Z/9d+Pmn48mc2jEMBufzwWRXGU3LoP4Vv6h/UfH9J/hQSsYo1AvjscjlJLbt3Hq8iGT+nz3n/0
3+o9AGVQBvYHqV2+tdHT7Js02X+kH09nGgHPgAx4y+S9Tf5FCP9x/6PRVwgg8iFIsizP8yxLJbfo
52H2hewN9T/SFkoJkAMagnizTVJvJl8vQ/djG3zL/iN9bUARyMA2SZLtdiO5ed9O/p96jaUsqv/a
AfdAFrxJbb27vMl+f/DD61rfGljKhXUcx+v1yuVKXvfe+zZ5enp3wFMgD2TB29J7/+79YP9NBGZA
SVxEMrGMomgh52vvhwav7d/0tovVLJ5qFGTB29zUmvnhnT+YPJmwIXF9MGAuyIQ1Vyt2n3qP5LUF
c8ANmAtywrTqW513b/zvQ99lovOgdmFiNiZqpg6fG0+674cgA8qC8uBaU79y3txwBywHisEsuAkX
150/7b21UBsIJsyMrNmsD+qBqXOXAh8G98GE3kz9hrwJobbgNlzaqp/27n6EJLQWannz3c7Vh6+a
R1sT3Tde925We89/f/mwy/sffJfVX90/9PzrexPPnx7+6T91PGyK75KBwQz8BxpVGgUKZW5kc3Ry
ZWFtCmVuZG9iagoyMzggMCBvYmoKMjMxNAplbmRvYmoKMjczIDAgb2JqCjw8IC9MZW5ndGggMjc0
IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjE0
OCAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBv
bmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2b2XbbSAxE400StZHUvtvO
/3/koLpZ1GJtyZw5Zx5uPySyRygC1cAVJnF+/eLgwH/rwEt7/uY5bbBf/JGIg85/f1riPOz0q+ck
2ojX9rTfenlCwm9uo/MLf/uhQn5jE/2Wz5nEA4VjfBN8qpH/412F9BY9UHHv7dFX+u5DhdN4RX/k
o5dZ4oGC4/PTFdzR0Ysk0SZxq4pGIMXn4K5O1lASruKegMpPyXcitJePNJREq3BdoC1AtXc6ii7y
6fWSxInC1YaSQOQYCUR8PL0o+v3+YDCIX4sk8SgHCzhewUMdaRQ9lRE5NDZcK6JJIApQ+kU/okf5
SOJC4aaACnD8aDwudcbj0TArNEXEox4JxPNHEV1VdV1XVXmioJu4IqD6ZWGTgPIflxE90anrRqGr
y2wULpI4E0j1jyJ+MpnOZrNpSFSRQ7LhocD7ezhQDIajcVVPp7O5TkhIIWyIm0gXkZ53ZkOTQa4g
G1ArfLFcLhfzeSiU4+FAN5FSuC2gO0wJlNVkpvDVahUSkUNVRgpJIHrhhkB4GALdnm4gCoj41Vpn
JYW6kgvdbmqm6wJq4+jCbtEfhoOTmeI3OqEQRVS5Bt1D7sYfHmSBTjcsHJeRgOK3u91uGwpKoa3h
tkDyMCyICibTRYrf7/ehkFIoo4ZeL7v4o5dUVNNGskAVLFfx/IiXwjpcUA3RCvcF0iXIgrjD5Try
3x8Oh/1ut1EN2YRmJOOBVzxIJOj1swWrENgfPj8/Q2GzDht1kcoguXhTIPowBMKC+Wqj+K+vr1CI
GubJxaaVfs5T40Ea5SQwW5wLRA26hmcEog0ig9livc0JKIVkQrrHGIdHJeRbtMD39/dRQNfwlEBZ
txmcCOR7fFIg+jCX0Aos538qsNnFHUS8akjX8HcCv3//RgAPvumDLzwIoNAHeKAPFvoAD+iDvGQx
C8wCs8AszJd4gAf6UyT6AA/oA/15JH2AB/RB/Lkys4AH8ddM9AEe6K8b6QM8oA/0t770AR7QB/o5
FvoAD+gD/UQUfYAH9EH+6UBmgVlgFpiFXyc/Kcv/M7Er87nA5wKfC3wu8LkQ/6KFz0Y80D9sog/w
gD6QA/QBHqQ2gInMQmoEPhthIkyEidkBZoFZYBaYBTsAD+ABPPA0sCvDA3gAD+CBHYAH8AAeeBrY
D+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AA
HtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+AB
PPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4
AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2
AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88
DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsAD
eAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH
8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7
ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7A
AzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyA
B54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP
4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gAD+CBHYAH8AAeeBrYD+ABPIAH8MAO
wAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AAHsADTwP7ATyAB/AAHtgBeAAP4IGn
gf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/gAfwAB7AAzsAD+ABPPA0sB/AA3gA
D+CBHYAH8AAeeBrYD+ABPIAH8MAOwAN4AA88DewH8AAewAN4YAfgATyAB54G9gN4AA/gATywA/AA
HsADTwP7ATyAB/AAHtgBeAAP4IGngf0AHsADeAAP7AA8gAfwwNPAfgAP4AE8gAd2AB7AA3jgaWA/
gAfwAB7AAzvw/+XB4fPr+/v76/Ow366X80k1HvaLbufj/e31NTB+zD9eXcH6ertvBXab1eLPBCaz
xaXArH4+g3F1VaAcPVdCf9gKRA1fYcFBJczqcjR4xoNeI7Da7GSCBORhFih6D03sZIHpPAkcPj8j
gXQJU2VQ9DoPbuEjCZR1CKy3SiEE9lHBcj6tssDH3Wt8l8BgFAKz5XorhXj+bisLpnEJyuDj/U4f
vEmgCAFdw2qz3e32+/1ulyzIfSSBt9uNZIG4huliuZZCnEggKpjoFrOHNwVeJdAt4hpkwnIVCjob
3cGkHsct+hJutLIEPrpxDbmGUFhvNpv1Ovp4qgrCgm728KrAy0sIvEtgkFNYLFchsV5FAZFA7sNu
8lCj83OYJJBNyClM5wtJrJaLuIJal9hacF/AKUxms5CIM59FAaVm2R7eFFANnW4vbByNq3oyDYn5
fBbxdSkLEwyaLrheQq4hpRA+1pPJVGei52sSnYAsvBBIRHl5tUCRfKyqOjQmddQf8bqCju4gd8Gl
QKbSmcJoXJaVTpnizxM441nzRWTVCCQbBsPRaBwa5TgePwwDUgFO4KZAU4SMHAyHoRFH4Tk+F/Cj
i44ZRAqpmToph/5gIJH4tV/o+c0cJQtvZJAE1M9S6BVFP58IzwamAu4KNAoxU51uSIRGnPi9m55/
jD/v4zYd3a6K0EgkiSTSjRPpawjiBm8+XyoSCIU3KSQJ5RHBOfwYf+P5R4Us8aGTgvX0CPfzb8fn
FHIVSkJpxNGLHJ7yv9KDrQlHBSWRNZpwPf5xfGODckhWSCWd9I1k0d3nt0amy7BK+j1+eS7eORwl
cnwT/fD5JzkopHl4G33H/6OP8eoYcPHq7F13v7gIzF/ejfj5Hy80fr7hme80Is+8lffgwL9z4B8B
SL8oCmVuZHN0cmVhbQplbmRvYmoKMjc0IDAgb2JqCjI0NzMKZW5kb2JqCjMyOSAwIG9iago8PCAv
TGVuZ3RoIDMzMCAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAv
SGVpZ2h0IDQyNSAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0
c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2dWZeaQBCF
TSbiriOK4jrL//+RubeqGxAZRTh5ybn9EBeoj6rb1aVjoBgMNKTAv1bgl49uhwnGxcNrlMKs+qQ9
omp187wlorT57aN841cLRLF3sK5BnhKCfbR+e3uLT8OWJ4SqPYyLYRTf+JDgu3Bvmv6Jgy/45lPC
jT2thxyGccQzgm33wwfrJEkCpEL4MYjS3sxhnIxGIz6YHyXiJwIBdnz6bsaj8XgMBiCMxITgTs0A
binsaQ7jCYdBgKgQGhFV+2EC88lk6oMMd+KhDyWA7tN8NpvN53P8O51OjOA+cMemIPC2C4D4YT+d
wnrBQQgJI0QRXfgRwOxxe5ovl6vVarkEwwjUgYRHHgAQ7RewfucAIxIoZDOAcSEC2htghsOv3tfr
NE3XazCWC/ehcKEuQwVgAph9mm44wAABUUDI4TDEAIMbHSLAFID+OP463Wy3WZZttxsSFnObCrjQ
uKgcUCgwh/+wz3YcQIAQXaCMtneTBwEABxD/Zrvb7fM83wMBH9yFJHkMQASj0WQ6XyCAbQbzw+FA
BAhRBc5DswfMIswBcmg2XyKAbAfz4/EIxH63TU0FykgRDFEX0QGYA0oIB3b7w/HEcQQh26zhwnTy
GBAlQARwYJ8fT2cOEMwF5AISusyEew8MgFXACOgA7C+XCwn5LmMMTwHMApcAU0AHLtfr9XI+nQ4W
A7KRHsRMaPCAeQwAJtEigP3HxwcJh3znIgBQpFIjIHHAGoDDCccnAATEsEmRS5bNDz3gQoAHa5MA
Dnx+ftKFY77HRBIw9nlkJjR7gDRyQH48wwEDXC8QwQGTNgDmITU8w/7r64suBACnoYUHmMVGAJZD
a0CKPK55wFx8BWCTEEO4QsUuANh/f39TBAGkgfJAa0H1QDXxdJEG0oBfMJQH0kB5kNpfPFoLWgta
C1oL+BFH9UAa8Mc85YE0UB74D9taC1oLWgtaCwn/r0+fjdJAeYBTB7QWpAHPQVEeSAPlAc/lUR5I
A+UBTy5UHkgD5QFO9tNakAYD5cFAGuC0X+WBNODZ38oDaaA8oALKA2lgaaCaqLVgiaDPRtVE1UTV
RFdAa0FrQWtBayEqoHqgeqB6EFeDviurHqgeqB6oHkQFVA9UD1QP4mrQ9wPVA9UD1QPVg6iA6oHq
gepBXA36fqB6oHqgevC/14OiHWqXVqA9u5n27Kfat6Nrz56yfbva9u2r27ezL65D6dVbmBey9Opu
bFfCjNkhult/Zb+MpEeHZwJ69JjG2fvsVN69yzUBQQS2aO7WZ9sBvNC0W6dvi4FX53XtNR5jgAvs
lt6l2znnwdpEv9pvHdXZv6hFFaxj+wsd3ysAXpeFfO7Yc75sGt+p6z0uhnEd6QOceLnvfgC4kJ06
/xeELvcesHkoCB3ufuCASGAYL99/ganAK2ogJO8/wVs/+M0b/OYLsVX8bZPx+PlujwYgISCMgQbr
GOXtH2pdym8A7kIkdLgLRpDBwjAvcFwf9KqpW/7t8fnKozAnaANzPnCELfcmtXfCfsELty3NHwhY
cgpE9KN8o5V9EUbFLjwtD/Ls2b0t3nlmVNteZ9Q2t3v5suftsNpLCtwr8Bc9PGAICmVuZHN0cmVh
bQplbmRvYmoKMzMwIDAgb2JqCjExOTgKZW5kb2JqCjI2NSAwIG9iago8PCAvTGVuZ3RoIDI2NiAw
IFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAvSGVpZ2h0IDIwOTQg
L0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25l
bnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtm9l2IkkMRL1gdqgFMLuX/v+P
nIjMUmEMBfTMmbebD15RlBQpXas9nqcnDg78vw48t+ffPKcNjg/+SiSCzt8/LHEe9vOzxyTaiJf2
tF96vi8Rr22Dmw/i63cV8gubqNd88meNxB2FU3wT/FMjf/OmQnqJH+i4XnuSir56V+FnvKPf8vGH
0rivEPH56Q7u+/iDJOHU0mu6qvA39ZoUn4MHPlnDSTwmkIrXsxU6zMcaTqJVuJ5BW4BrV7iCR/kM
h0nih8LVhsoFOP8cPxqNx+PJZKK3oyRxL4cQiHgHT32sMRq6DOXQ2HCtiMZBFdBX+nr4dDqbzefz
2cwSvxQ6BdQ9KX6kpyu68JHGNCs0RehR9wRGY4UXRVlWVVWWxQ8F38QVAdfvHrCDKmA0nihe0bVP
VTUKA19mo/AriZOAbsDxU8fX9WK5XC4kUSqHZMNdgZyA6lf8YrFc+UjCCrJBN5EuIj3vzIYmg1xB
KkDxCn9fr9fvq5UUivl04ptIKXQL9Hp9VeAEqnrp8M1mIwnlUBZKIQmoFzoE5KEEBkM7WNYLxW+2
PhsrVKVdGAxyM1nhogTPoS3wFRblYun43X6/30lhtazLXIPvIXdjh8BgoArmRbVYpfjD4WAFp9DW
0C1gD9UEqYLlu59/OB6PUlAKi7pQDcNhdvGil1xTbqNkQVHWSsDxHx8fUtjKBdegVrgtoEGQgO9A
FWz3h0bgsHMN2YRmJK+baBJYwBaoAifw+fmpFHZb1eCLdAbJxU4B3+LUl/i+2Tn+6+tLCqphlVxs
WulynhoPdIsigQWW6+2ZgGrwNTwioDbIAvucgFNIJqR71DjcKSFuUR5a4Pv7+yTga3hIwINwKZDv
8UGBxUqXcJbBevW3ArtDrsA1pGv4dwJ//vxBAA++6YMvPBAS6QM88A8W+gAP6IO8ZDELzAKzwCys
9C9f+gAP6AP9HopZwAP/PpI+wAP6YJJ+N88sMAvMArPg/85EH+ABfeA/f6AP8IA+8N+x0Ad4QB/k
v+liFpgFZoFZSH8hyc/G9HeuMBEmwkSYCBN//NU4vz/g343sB+wH/j9p6AM8oA/0w5FZwAN2pKcn
PMAD/0+/9AEe0Ad2gD7Ag9QGMJFZSI3Az0aYCBNhYnaAWWAWmAVmIRyAB/AAHsQ0sCvDA3gAD+BB
OAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsADeAAPwgF4AA/g
QUwD+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7AA3gAD2Ia2A/g
ATyAB/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDTwH4AD+ABPIAH
4QA8gAfwIKaB/QAewAN4AA/CAXgAD+BBTAP7ATyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyA
BzEN7AfwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+A
B/AAHsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAe
hAPwAB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AA
HsQ0sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0A
HsADeAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4
EA7AA3gAD2Ia2A/gATyAB/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsAD
eBDTwH4AD+ABPIAH4QA8gAfwIKaB/QAewAN4AA/CAXgAD+BBTAP7ATyAB/AAHoQD8AAewIOYBvYD
eAAP4AE8CAfgATyABzEN7AfwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/g
QTgAD+ABPIhpYD+AB/AAHsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP
4EFMA/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP
4AE8gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyA
B+EAPIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AAHsCDmAb2A3jQzYOPz6/v7++v
z4/jfrte1eV8Oh4N+m+915cXNU70UHp/2Ujr7f7YChx2m/e/E6iXFwLL6vEM5uVVgWL2WAnjaSug
Gr5kwYdLWFbFbPKIB8NGYLM72AQL2MMsMBreNXGQBRbvSeDj81MJpEtYOIPRsH/nFt6SQFFJYLt3
ChI4qoL1alFmgbeb19izwGQmgZWuwQp6/mFvCxa6BGfw1rvRB68WGEmgrFeqYX84HI/HwyFZkPvI
Aq/djRQCvob39dYKOkpAFdS+xexhp8CLBPqDka4h1bCRgs/Od1BXc91iXEJHK2cBXYNrUAqb7Xa3
22236uOFK5AFg+zhVYHnZwn0+nZRKdSLlRQksd2oACWQ+3CQPPToXA6TBV57/f5QNegerGCJzfpd
V1D5ElsLbgnIhJRCWdXLpSR0VksVUHiWw8NOgcaElIIUFpJYrZaKrwpbmGDQdMH1ElTDW6RQSKFe
+NR+vicxErCFvwSe0pdebIIFRurGeVGWlTTqSvUr3lfQ9x3kLvgtIC5JQwq9UJhKQho6RYo/T+CM
Z80nWcAp5Byms9lcGsVcj5/KgFRAJNAp0BSRqphOpaHj8ByfC7joolMGriEVkXIYTyYTiejteOTn
N3OULOzIQAIphVTFcDQa56PwbGAq4KZAo5B8GAyH0tDR+0F6/in+vI/bdHyXOYee2qE/0EnBKdxD
oBvsfL5VWgH7YIkk4ne6/x/xHc9vFHIOWSKJSCqHx/O743M/tgp6qIMdrewdnvK/0oOtCScFXYYv
tDn+5KH4bENy0vd5Oo5uHn+jgJSIjdRJEXrTPPrx+MjhJJGlsqzensrt/Kh9bSty+kpn0Pk3TgG/
Pjp/2a3PfgXmT28FXH7vt8TlKx75SqPyyEt5DQ78Nwf+AcCjK64KZW5kc3RyZWFtCmVuZG9iagoy
NjYgMCBvYmoKMjQ1MwplbmRvYmoKMjc3IDAgb2JqCjw8IC9MZW5ndGggMjc4IDAgUiAvVHlwZSAv
WE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjA2MyAvQ29sb3JTcGFj
ZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2a2XYaSwxFbcDM0DPQQDPk/z/ySqpSM5hu46yb
t10PMbZbB+mUtK0k/vjg4MC/d+Dz8/Nv30RC785vVe5C25e/0Ghjnl68K3EfNhgM7j99R6J9XmJv
x7/6s0J88hbqr+I3flK4jx/ejqm8IxGe0ccteGTHXt5J9CTxEB+i458iohLhgW4F+354ewn8uh35
LEjYE10C7fsPhxY+bo8oRYXeFG7vr+8+Hk/aMx6rgiQRq+hIQQUsf4nX8Kmc2Wwmf04mQaJfISag
+Wu8Bs/tqIZIWBlu5KscQgJtvIYvwpnPVUIVelNoC7D31/DlcrlareTPxVyyeFDoyED7R/2bTGcS
vlqt7YjGYj63HMJlylt1C6gBMX69TpI0TZNkrRKawjgU8UogGGAJtPFJmtkRjfVqKT5IEeEu9enH
HPQr8QotAcl/LeF5XhRFnmeqID6Iwk3gUaEVEAesAI3Pi9JOUaiC+BBTiCPxkEIUUAulAjFwnWh8
VW02m6oqVcGKiFdpj3cKyA0sV0maF1W1tbMxhZBC6IVugdFILZQE0qwoN9vdrq7r3VYU8sxSCDaG
qf6WgY5BrGC1zvKy2kr4fr+vd7tNVeTqwmxqNYR+7hSQCtaJFLDZSfjhcNjX9XZT5qlexNRaoVdg
MrEKcimglvDj8XjY7zUFq8HuIQ719wyEOSO9xIVYqAnsJbxpGlGot1WZSQ3zmZqgEyU2vhKQPtZL
XCVZUWkCTXM6nVRhZzWICdHFTgFtI7Ug0woOx9PpfD6Lwn63rcyEnwW0jfQSS6ngKO9vAs1BatCL
1Ay0hu4SrA9FIFcLjs35fLlcJAUR2KiLImAm9AloH6qAVtAKSA1RwK+hy8SvcehDE2hOl8v1epUU
XGAZ5qm3hHCLLwVSuce3Moi3eHjMQHvxFwLhEtoSxMW/EDidr9c/f/6ICXoNCOABfcAswAOYyM8F
fjbuj3iAB7po0gd4QB9kBR7ggf7tnT7AA/pA/0GTPsAD+kD/XZk+wAP6QP6vjlnAA/0/W/oAD+iD
8DskzAKzwCwwC/JLYfYbWfAAHsADZgEeyO/qwUQ8+KAPPvBAfvWZPsAD/Q14+gAP6AN1gD7AA2sD
mMgsWCPwsxEmwkSYGBxgFpgFZoFZcAfgATyABz4N7MrwAB7AA3jgDsADeAAPfBrYD+ABPIAH8MAd
gAfwAB74NLAfwAN4AA/ggTsAD+ABPPBpYD+AB/AAHsADdwAewAN44NPAfgAP4AE8gAfuADyAB/DA
p4H9AB7AA3gAD9wBeAAP4IFPA/sBPIAH8AAeuAPwAB7AA58G9gN4AA/gATxwB+ABPIAHPg3sB/AA
HsADeOAOwAN4AA98GtgP4AE8gAfwwB2AB/AAHvg0sB/AA3gAD+CBOwAP4AE88GlgP4AH8AAewAN3
AB7AA3jg08B+AA/gATyAB+4APIAH8MCngf0AHsADeAAP3AF4AA/ggU8D+wE8gAfwAB64A/AAHsAD
nwb2A3gAD+ABPHAH4AE8gAc+DewH8AAewAN44A7AA3gAD3wa2A/gATyAB/DAHYAH8AAe+DSwH8AD
eAAP4IE7AA/gATzwaWA/gAfwAB7AA3cAHsADeODTwH4AD+ABPIAH7gA8gAfwwKeB/QAewAN4AA/c
AXgAD+CBTwP7ATyAB/AAHrgD8AAewAOfBvYDeAAP4AE8cAfgATyABz4N7AfwAB7AA3jgDsADeAAP
fBrYD+ABPIAH8MAdgAfwAB74NLAfwAN4AA/ggTsAD+ABPPBpYD+AB/AAHsADdwAewAN44NPAfgAP
4AE8gAfuADyAB/DAp4H9AB7AA3gAD9wBeAAP4IFPA/sBPIAH8AAeuAPwAB7AA58G9gN4AA/gATxw
B+ABPIAHPg3sB/AAHsADeOAOwAN4AA98GtgP4AE8gAfwwB2AB/AAHvg0sB/AA3gAD+CBOwAP4AE8
8GlgP4AH8AAewAN3AB7AA3jg08B+AA/gATyAB+4APIAH8MCngf0AHsADeAAP3AF4AA/ggU8D+wE8
gAfwAB64A/AAHsADnwb2A3gAD+ABPHAH4AE8gAc+DewH8AAewAN44A7AA3gAD3wa2A/gATyAB/DA
HYAH8AAe+DSwH8ADeAAP4IE7AA/gATzwaWA/gAfwAB7AA3cAHsADeODTwH4AD+ABPIAH7gA8gAfw
wKeB/QAewAN4AA/cAXgAD+CBTwP7ATyAB/AAHrgD8AAewAOfBvYDeAAP4AE8cAfgATyABz4N7Afw
AB7AA3jgDsADeAAPfBrYD+ABPIAH8MAdgAfwAB74NLAfwAN4AA/ggTsAD+ABPPBpYD+AB/AAHsAD
dwAewAN44NPAfgAP4AE8gAfuADyAB/DAp4H9AB7AA3gAD9wBePAPeXC6XK7X6+V8ag71tszT9XI+
nYy/RsPBQH4S3a5AXn3/ybStD00rcNzvNr8TyKtvAkX2fgbr9KVAsnqvhPmyFTifLxex4KQlFFmy
WrzjwTQK7PbHJgqoh0Fg9rOJkyBQblTgdDqfJQEVqHLNYDYZ/3ALXyaQZCJQH45BoJEKRCBdm8BX
7zWOVGCxSrJCr+HQSA6n5njwW9QMvkY9fTBUgZkIpEUlNRyOx6Zpjke1oMwS6SMTGHY10mDoAnIN
5WZb7492JIFtpZfgt9gpMBCB8WQm15DkUoO4YGevCZgF82n08HUrD4KAXIOYoCns6nq/39f1blMV
uVSwmE3HwcOXAp8qMBqri9pK4sJ2JxL1Tgoo9RKjBeKhjs73YVKB4Wg8nkoNmoIqiMRuu9mUOght
H/YLiAkhBSmi3NipyiJPLYHpRCvoEYgmWAqp5FCWVVWVEq93uAiXGLvgdQlSw5enkKiCnVzeXwuI
gxAusVNAL1JcWKzWSZpmWZ7nWabx4qANklbwwsTIRbuHqLA0iVROovFPCTzwLH4iN2P38DUOOSxX
q/U6kWgJv4t/0Yb3AtbO44lVsRQJPRoeCrAr+E7Um0BIwWwQH+aLxWIp0QtJ3wy4xT920YOApSA2
TKbTmWjYkXA1MAxyh4MiYv05MBskhygxkzOV8BgvBnQLuMJQGnok7SASmocES3h4f4+POT9/uKVg
CiJhIvrB0tcO6Hl/lbtJjDQJORas4dJAP8e3AuKkJOEi+iKEh/d/eQWxHEtBLlOtjBoh2t7+5/hY
hCmYhMroUckY3vf+rQ3a1OF48NvxnsNNIgiF2p5mONb9/MGflY8xjdtXnp/t+PwW8PSq4/kXX34K
DJ++eK7nS88SPY/2fCuq9DzBt3Dgf3LgP90408YKZW5kc3RyZWFtCmVuZG9iagoyNzggMCBvYmoK
MjQ1NAplbmRvYmoKMzM1IDAgb2JqCjw8IC9MZW5ndGggMzM2IDAgUiAvVHlwZSAvWE9iamVjdCAv
U3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjQyMyAvQ29sb3JTcGFjZQovRGV2aWNl
R3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlID4+CnN0cmVhbQp4Ae2a2Xbq2A5F04HpDbgBG0hz/v8jS9L2MpDgQB7uGPdh7oc0BC1L
a0szqlN5euLgwP+3A89X56+5XgWnb/4icSM8XnpQYyjcXn9EoQ9/uTz9q/clurdeRsfX3ev3BC7D
X8/nYYkUH2+P6Dc/8dWFxC9JnOMtKIL1wb53ifSGYYX4ub8xwkfnk/KQwqCA4uPxFj3uz2gUEvcU
XCAe//oW4Vl/xmOXiDL8TQMp9PFvFj8eZ9lkMplOp/ZxkmUPKHi8JeD5W7yHT6czPyGSWRIph3jf
rRxSvPvn8RY+m83TcY1Jp9DZMCAQBlgBFm9Pny8Wi+VyaR/nJpEUZMOggN9fxNvjLXrlx0XmoWBO
uoLl+puA+zdJ4Xm+Xq/z3DSkMCyQHJABU3v8yqI3fkzjp8L3JMLa6MBUQMRvttuiKLZb03AFt6Gv
4XsZEkgOzOb+/E1RlH5MwxXCBr/KmyORBLyC8dgucLH0+LKq6rquqtIU8pXZoBTi3ddGXgiEg6v1
ZltW9c6PSRRbL8JuItUwLGAVZFkkkOL3TdPsd3VdFpGCuRA13BbwLrImtB6aL1brbVHV+33Ttm2z
3++q0lPwGrwVbnWjaSaB6IHlyhPYNU17OBxaS6KuzAWvIe7hroBZuPEE2vZwPB4PlsSuKuwi7CZ/
F4hL8DtY5ZGAxZ9OJ1fY16kGuRhsu2rnKCHmoLOgrPeNxb+/v7tCsyu9BjMhhjp1wrDAcrUuqt2+
tfiPjw9XiBrchHsC0UbzsGAXCSSBY7tPJpiAd8JwBjEILlDWJmAJfH5+egqdCZZB56J3wq0STGA6
TQKpgk7g0ISL53v8TcAHwTIwAUvg6+vLU5BAf4+/C9gg3BSwa1Aj3BPYehtdZ2Au/knAL+FcwrH1
XvyrwMks+Pfvn5uAAB7QB8wCPICJB34v2IJCH+CBL6r0AR7QB1v7D2f6AA/oA/tnKGYBD/yfI+kD
PKAP/B+26QM8oA/sf1AwC3jg/6OKPsAD+sD/+oA+wAP6IP6OhVmAB/73TPQBHtAH/ieq9AEe0Af2
54LMAh480QdPeGB/+kwf4IH/BTx9gAf0gTtAH+BBtAFMZBaiEfjdCBNhIkxMDjALzAKzwCzIAXgA
D+CBpoFdGR7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAf
wAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8
kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4
oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AA
HsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QA
PIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga
2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfw
AB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/g
ATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYD
eAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAH
cgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAP
NA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7A
A3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyA
B/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D
+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4AD+ABPIAHcgAewAN4oGlgP4AH8AAe
wAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BADsADeAAPNA3sB/AAHsADeCAH4AE8
gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CBpoH9AB7AA3gAD+QAPIAH8EDTwH4A
D+ABPIAHcgAewAN4oGlgP4AH8AAewAM5AA/gATzQNLAfwAN4AA/ggRyAB/AAHmga2A/gATyAB/BA
DsADeAAPNA3sB/AAHsADeCAH4AE8gAeaBvYDeAAP4AE8kAPwAB7AA00D+wE8gAfwAB7IAXgAD+CB
poH9AB7AA3gAD+QAPIAH/0sevH98fn19fX68vx/bXVVs8uV8mo1Hb68vL/bL+PnchvbVj9/O9b49
9gKnQ/NHgU35XaAut49nsMxvCqxXD5Yw7wWshk+3wEqwDNarxewBDybTJLBrDqdO4HRs953A5K6J
4yRQVCHw/vHhCZhAVUQGk/GdWxglgbUJ2DVYCiZwOh4aE9jkVsJkPPr1Gt9CYLFaF34NB1Pw5x/s
FstoAxd4+6UPXkNgZgLbsrYajsfT6XQ8HpIF3kcu8DrcSC6QTWaLZb6NGkzBzqFtdrVbcFfgpROY
L1ebSKE9+GmbffThxS0OtLILjDK7Bq+hqOp907Rt21i8X2K+NA+z5OFNgednE3gbZdnUa7AU7CJM
otlbfLqDuQu4hz5KP4fJBfoa8vXGLqI2CQu3+JSAPLwnYCmsciuirGo/VemDtFp4AukSBgWihrHV
YDZaEUVZVpWFF9uNXYENggn0XXCzBNXgLngO28LP1uLNwXMCwx6EgLeCXYQrbDZbi96s11GAJ3Bu
o2sgOZ2ssJdzCqGQr/3kueU/jwL6+Cucdd9IILrRbFhYEqvcoldLxZ8TGBQ4FzELiaWdxSI9XwW4
BQMCVkMqwm2wJOaWxsI+ziJ/e74P4s8uPJfQCVhDm4JLpDOdTsy/IME9gV5hPM5MwjTs2OfM4+35
ir9ZQtxDrzByiRDxT/H4c/wtB/y16NBkg02VSYSIf7IZ9Od3JBl4/pWCzaVJhIh/ivTv5N+n4FXY
XbhEaPjDu8ff6mGPO58oQgohoWh//P34zgbvaTuWRX/ihSR/ftzNr9KbkkISiVj70P3kZtTli937
uiwUrfDhC7jQ6CWUx/mFh+J7Iy7iui8vnnLny5+x9sqdmO8//qbx/cePff/nzB+T5V048NOB/wDn
ov5UCmVuZHN0cmVhbQplbmRvYmoKMzM2IDAgb2JqCjI2MDgKZW5kb2JqCjMyMSAwIG9iago8PCAv
TGVuZ3RoIDMyMiAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdlIC9XaWR0aCA2NSAv
SGVpZ2h0IDIwNjcgL0NvbG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0Jp
dHNQZXJDb21wb25lbnQgOCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtm9l220gM
RONF+8pNC0Vt+f+PnAKaoK1YopScM2+3HxI5FopANXCFyTi/fnFw4H924K07//CgLrZ78VciXdTN
i5clbqJuvnhJ4ivivTvdn72gEO/tgtsX8efPJNr3paiPdG4kngikeI9oo7+JpG/2KnzFW9xnd+wr
U/Xv9yh08W30IB3TeUnhNt6Ch370opNI73mQhH9TiVryKXrkRyomkZLwN/UIdPHD4Wg0TkcqkvAk
+my4fb6HT9KRjCQ8iT4jTSCer8ePx5PpdDqbzfTrZNIqeBX2xns1hIDqt3iFz2ZzPxKZKAnLwW6z
RyAl0MYrfLFYLpeLxXyuNJSE+WDt8DiD9gL8+QpfLld+lou5kvAcXOGJwKCLX63XWZat16uVSXyl
cE/A6pKF3gHD0WRqz19lWe4nW5tCW4T3tL/9xsgvgZSA4tcKL8qyLIrcFcxJ+fhEwK7AE7D4oqz8
FIUpRBGtjX9cZcpAFQwGukEVsFJ8VW222+1mU5WmsFAKdhFxk7e90Ap4AuPpTAXo+Qrf7XaSqEpV
4T4Oh3EPdzKQh20FloDF7/Z+pFDk66VSUC88FrAuUgVDq0AJlJXi68PhUNe77UZFrOwivIbUSz9K
SAJqAlWwWisBi2+a5nDY77ZKwW0cjWTCQwHz0AS8AiWg+OPx2DT1fqcUrAY1k7n48XMeZKK3kV+i
KsjkwF7xp9PpeDyoiKrwe3gikDxMFmx2ddMKNIf9tirdBBOwi7Rb+7MTWw9HE7Mgr7b7WvHn8/l0
koBqyGSCriHN9EMBgcgEskICB8VfLpfz+djUEtBFmkBqpR4B3aIJ6A6+C6iGJKBx6C2hvUUTqBtP
QDmcjmaCC9g8PRWYa5BD4Hq9fhOwe3xJQIPQZvBdQNfwukCpNrISOoHdxpr5bwTkocdL4nyya/g3
gd+/fyOAB1f64IIHAgp9gAf2wUIf4AF9kJYsZoFZYBaYhdL+y5fPRjygD3JmQX8dSR/ggf21NH2A
B/TB1P8XDbPALDALzIL9H1P6AA/og/TTA8wCs8AsMAvx00TwAB7AA3gAD/znE/0nLGEiTISJMBEm
wkT/yfn2J+/5XOBzgc8FPhf4XOBzgc+FX/onVvQBHtAH+peOzAIe2D94pQ/wgD4wB+gDPPA2gInM
gjcCn40wESbCxOQAs8AsMAvMQjgAD+ABPIhpYFeGB/AAHsCDcAAewAN4ENPAfgAP4AE8gAfhADyA
B/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/gATwIB+ABPIAHMQ3s
B/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP4AE8iGlgP4AH8AAe
wINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD+wE8gAfwAB6EA/AA
HsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7AA3gAD2Ia2A/gATyAB/AgHIAH8AAexDSw
H8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDTwH4AD+ABPIAH4QA8gAfwIKaB/QAewAN4
AA/CAXgAD+BBTAP7ATyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN7AfwAB7AA3gQDsAD
eAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AAHsCDcAAewAN4ENPA
fgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPwAB7Ag5gG9gN4AA/g
ATwIB+ABPIAHMQ3sB/AAHsADeBAOwAN4AA9iGtgP4AE8gAfwIByAB/AAHsQ0sB/AA3gAD+BBOAAP
4AE8iGlgP4AH8AAewINwAB7AA3gQ08B+AA/gATyAB+EAPIAH8CCmgf0AHsADeAAPwgF4AA/gQUwD
+wE8gAfwAB6EA/AAHsCDmAb2A3gAD+ABPAgH4AE8gAcxDewH8AAewAN4EA7AA3gAD2Ia2A/gATyA
B/AgHIAH8AAexDSwH8ADeAAP4EE4AA/gATyIaWA/gAfwAB7Ag3AAHsADeBDTwH4AD+ABPIAH4QA8
gAfwIKaB/QAewAN4AA/CAXgAD+BBTAP7ATyAB/AAHoQD8AAewIOYBvYDeAAP4AE8CAfgATyABzEN
7AfwAB7AA3gQDsADeAAPYhrYD+ABPIAH8CAcgAfwAB7ENLAfwAN4AA/gQTgAD+ABPIhpYD+AB/AA
HsCDcAAewAN4ENPAfgAP4AE8gAfhADyAB/AgpoH9AB7AA3gAD8IBeAAP4EFMA/sBPIAH8AAehAPw
AB7Ag5gG9gN4AA/+Tx6czpfr9Xq5nE5NvdsU2Woxm4yHg8+Pj3cN31sMov/+Yxo3u7rpBI6H/fbv
BLLih0CVv57BYnVXYL18sYRZJ6AaLpfz+WQlVPl6OZ++4sEkCWz3h2MrcJSHrcD4qYnDkQvklQuc
znr+yQQ2pWcwHj25hYELLNcS0DUoBRNoDnsJZCuVMB4Neq/x0wXmEih1DQcp6PnHg1ngbWACnz19
8OEC0/lylZUb1dA0x+OxaQ6qoCrW3kcS+HjcSC4wns7tGqwGKdip1UZmgd2iC7w/6MR3ExiOp7OF
17Dd1wc/e91BkZsFE/fwvU9gMBxPZqohL6rNbr+v63qveCWgPjQP7RIeCLy9KYPWBNWQlypCEvud
4pWA2mhmAvIwJfBjmEygNcFqyIpys5HEbuvxnoD6cGh34BY8EhiMxhOzcZ0XZbXxU6qASMC74KFA
V4O5kEmhrKqqLAvFmwO6g28W3MsgapjYRSiHvPBj8a0Dg4FV0JNBstGLkEKW5XmeZWvFL2aRwH0B
YSlBKdmoFObKYbX2o3DdQCqgvYMbnLVftAJfCpKQxmq5XER8mkQr4KGAu6CJUhFKYr7wM0/PbyfZ
HXgg8CZ/rBdcQWXMpDHXr1Pl7zfQNcEjAVdQO5rCeKIs/EwsXM9PPeBX0CtgNyEFSUjDjoerfn/+
nSvs1GROW4QpSMJF7LehPd5B0BdvF9kqpCSGLqJfFR7xvQK3CsrC8rBgC3+avxXiKVgVugslYV6k
4Db9ez3cGeAvbhSShulIzho4pX+3iTqZpOBJWBbdsfBX4qOKpKAYKXhsF97//G9l+HVE7Ff4C/Fd
EulKTaOty37rau198S3g9mVv1M03b+Par27e8fyLPzWeR9x5x789+o4Qf4QDzxz4D8p44YgKZW5k
c3RyZWFtCmVuZG9iagozMjIgMCBvYmoKMjQ1NgplbmRvYmoKMzM5IDAgb2JqCjw8IC9MZW5ndGgg
MzQwIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQg
Mjc0NyAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNv
bXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae3bW3MaSRIGUI8uIAQS
dwToPv//R25mdScSNkjyRmzEPpx+8EWmsqu+7jzO8Gh+/XJJ4P86gX+Orr/e6tHq7jd/UePE6val
n5Y4tz6+/pMSh+UXn67DF7+vUB/9tLr7Zf8H31XoP9bWXH5c7fc/KdF9Jj/eLb7Kq/0yv/Z9haP1
bXH/Q9b4KHH+GK1Ad/tYeX24ssynCucKHO4ft8vlg8MVldpJ6hRnKnzcv18+rGswOK7wRYG2/7Z+
OLyJazQaxY/DYV+iz+F0gX4D/fZjfSy+zStrRInYRMuhfe5UifyDfHxx/8Egl9/ejrsrakSJowpn
CnQH6NbH8slkcnd3N5mMx7GL3EP3LPJOZwvEBiL+uH8uv7u7zytqjG9v2ynypWqP4nyBPEC3PlZP
p7PZbDq9z12MPg5xcgctgEzgY32snucVNaJE5PDFIfJYkeBHgcnd/XQ+XyyWy+ViMc8KkUNU+Ejh
OIZDgUigHSDXx+pVXstWIXLot9C/j0cx9AX6E0SAd7l+tVpvNpt1lIg9tEP0D6J9/GyBeAJxgFms
X28e8ooSsYf7toXubTpf4OoqH8F4EgdYrjabh+1ut9tGhThFy7GLsYPhjx1khu0Z3I5zA6v1w3a7
2+/3u+12E4eYxhZGN+11jE/GHs4WyBPEBtabuP3+8fFxv9s9xCFm8SCiQKSQtJwvMBzmCWbz2EDc
/vHp6elxv9/GIVqM7TmcLZCO5EPsTrDZ5vrn5+eokFvIM9yOMoRTb3PG2jXi8CYiiGeYG4j1Ly8v
UWEXKcQZIoQfFWgRbB52uf719TUq5Bm6EPrHcDqDeo0ygmWc4OlQ4DHOsJhPI8WkKVM8GeKnAotV
FogNvL29xRayQDzILNDO8FWBfA/zLehP0BeIM3QF6jGc30F7D7sCuYH39/fYQoaQBSZdP315hHyK
0zMF4jn+aAf5HuYRjnfQnuPPC6y3+88FIsW/L/CUEfz7778RQj4GBWTgPdALPGCivxf83bg3H8Sg
6j2QQQzb3gMZLL0H8S8o3gMZ5L+keQ9k4D3If5P1HsjAe9D+aVwv8CD/E4n3QAbegwETr2UQ37/g
PZBBfh+L90AG3oPu2+L0gl7QC3qh+wZHvaAX9IJeqG945gEPeMADHvz6JQMZ5P/Y5D2QgfcgE/Ae
yKC9BkzUC+1F8HcjE5nIxC4BvaAX9IJeqAR4wAMeVDeYlXnAAx7woBLgAQ94UN1gPuABD3jAg0qA
BzzgQXWD+YAHPOABDyoBHvCAB9UN5gMe8IAHPKgEeMADHlQ3mA94wAMe8KAS4AEPeFDdYD7gAQ94
wINKgAc84EF1g/mABzzgAQ8qAR7wgAfVDeYDHvCABzyoBHjAAx5UN5gPeMADHvCgEuABD3hQ3WA+
4AEPeMCDSoAHPOBBdYP5gAc84AEPKgEe8IAH1Q3mAx7wgAc8qAR4wAMeVDeYD3jAAx7woBLgAQ94
UN1gPuABD3jAg0qABzzgQXWD+YAHPOABDyoBHvCAB9UN5gMe8IAHPKgEeMADHlQ3mA94wAMe8KAS
4AEPeFDdYD7gAQ94wINKgAc84EF1g/mABzzgAQ8qAR7wgAfVDeYDHvCABzyoBHjAAx5UN5gPeMAD
HvCgEuABD3hQ3WA+4AEPeMCDSoAHPOBBdYP5gAc84AEPKgEe8IAH1Q3mAx7wgAc8qAR4wAMeVDeY
D3jAAx7woBLgAQ94UN1gPuABD3jAg0qABzzgQXWD+YAHPOABDyoBHvCAB9UN5gMe8IAHPKgEeMAD
HlQ3mA94wAMe8KAS4AEPeFDdYD7gAQ94wINKgAc84EF1g/mABzzgAQ8qAR7wgAfVDeYDHvCABzyo
BHjAAx5UN5gPeMADHvCgEuABD3hQ3WA+4AEPeMCDSoAHPOBBdYP5gAc84AEPKgEe8IAH1Q3mAx7w
gAc8qAR4wAMeVDeYD3jAAx7woBLgAQ94UN1gPuABD3jAg0qABzzgQXWD+YAHPOABDyoBHvCAB9UN
5gMe8IAHPKgEeMADHlQ3mA94wAMe8KAS4AEPeFDdYD7gAQ94wINKgAc84EF1g/mABzzgAQ8qAR7w
gAfVDeYDHvCABzyoBHjAAx5UN5gPeMADHvCgEuABD3hQ3WA+4AEPeMCDSoAHPOBBdYP5gAc84AEP
KgEe8IAH1Q3mAx7wgAc8qAR4wAMeVDeYD3jAAx7woBLgAQ94UN1gPuABD3jAg0qABzzgQXWD+YAH
POABDyoBHvCAB9UN5gMe8IAHPKgEeMADHlQ3mA94wAMe8KAS4AEPeFDdYD7gAQ94wINKgAc84EF1
g/mABzzgAQ8qAR7wgAfVDeYDHvCABzyoBHjAAx5UN5gPeMADHvCgEuABD3hQ3WA+4AEPeMCDSoAH
POBBdYP5gAc84AEPKgEe8IAH1Q3mAx7wgAc8qAR4wAMeVDeYD3jAAx7woBLgAQ94UN1gPuABD3jA
g0qABzzgQXWD+YAHPOABDyoBHvCAB9UN5gMe8IAHPKgEeMADHlQ3mA94wAMe8KAS4AEPeFDdYD7g
AQ94wINKgAc84EF1g/mABzzgAQ8qAR7wgAfVDeYDHvCABzyoBHjAAx5UN5gPeMADHvCgEuABD3hQ
3WA+4AEPeMCDSoAHPOBBdYP5gAc84AEPKgEe8IAH1Q3mAx7wgAc8qAR4wAMeVDeYD3jAAx7woBLg
AQ94UN1gPuABD3jAg0qABzzgQXWD+YAHPODB/9iDl9e39/f3t9eX58fdw2oxu5/c3gwH11eXFxch
UN28/fynSA+7x+dDgaf9dvN3BRarPwos5z/fwf3sZIHp3c+OcDs5FIgzvEUEL3mE5Xx6N/5JBjd9
ge3+KUPIAplhV2D0fYjDrsBy0wq8vL7GBrLAepE7GA0H3zyF61ZgOo8Cu8fcQhR4jhNEgdl9K3D9
5WO8ygLjuyiwjseQFeL+T4/1FHMH11dfvAeXWWAUBWaLdZzh8enp+fn56SkjWLWn2ApcnnuRLi6r
QD6GzcMuK8QVG3hY50Oop3i2wEUUGAxH8RjaGbZRIa99bqBFcHvTZ3j6Vb7oCsRjyDPEFra73X6/
3+22m/VyMb2fjEc3gy7DkwX+yQJXg0wxtrBYrqNClNht4wCrfIiT28owW+fPZsoCl1eDwU2cIZ5D
VsgS24fNZpWNcHgPL/P+ZwtECG0Ls/litYoSca1Xy8WsbeBmmCf4okAfQttCVFhGifV6FevnmcDh
BOd3EGe4ri1Mo8Jimdci7p8H6Buhe4inj9DehDjDKN7G++lsNo8ai/k810eCrZHyBCd2kCxFLu05
5BaiwiRKRI24prn+tw0cedb/piuQ71JVuLuPGtP7WP5p/YnX8HOB/hDdHiaTu7xyeXeA9gj+FPWj
QPcq5PucFW7H4/EkVo9j+y2Aj/XHb9FRgbaFdoqbUdRoVyzPALtGPpNgFMm3K7aQFVoOw5ubqBFX
/Dzs10cA5wtUhctWITcRV1scy7v71/p+z7//9LGF3EO8UXFFjfwpt9/egC/un+V+L9GKRKlued3/
ZILdbqpA5BCbiCsX5+q4ey7v7v9FgW4LmWSW6Gr0y3+2vj9Eq9BKZJm8smR/+6/uf4ihPc62qBb/
eH3t4aNEq1N3/+72LcqWZPdDt/iw+jcDuuBP/fipxPEvT3349NeO1/W/O/3Rc1/9vcS5z3399f/q
1l+X9KcSOJ3AfwB76t27CmVuZHN0cmVhbQplbmRvYmoKMzQwIDAgb2JqCjI3NjcKZW5kb2JqCjMx
OSAwIG9iago8PCAvTGVuZ3RoIDMyMCAwIFIgL1R5cGUgL1hPYmplY3QgL1N1YnR5cGUgL0ltYWdl
IC9XaWR0aCA2NCAvSGVpZ2h0IDM5OCAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xh
dGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVh
bQp4Ae2c2ZqiMBCFx27bBRcEUQFZtN//IedUJUFQke2bqzm5QZG/qlKJpoJ6/vxhYwb+UQZmpo2x
btHqMMxGhdUf9DZRh+qP+xmoEV+mPc70sOAutuyTiU4DFnf09/e3e2hf+WzBXKQI0KrpCfPaR/6B
Czq3Tc3ARKcBvUB8WfhHm1jBCTnfYcHx6lrZxWIhx8qCXtHShQeNyAGBXSyXSzmIBRPCBwOWl9iV
BrtCw2EpQYgF24V3ASg9077Du3herdbaxIaGoBGY614tWO9IHbxb2jNtvUYQpg8uh628pA44fHve
ZrPZbrebjeetJQTbA3X0njfRWxzsThtMeBKCROBS0MZL9Oj7eu1tQO/3vu/v97vt1hro5k30iu/9
gzaxoH1AEud2CJ7815OHzgPfCR0EYRgGwcFHCMiBScG7FD54yb14Bx6ER22hGkAOZBBcALNZPYSK
19yvve1O8Sg6nU5RhBj8HZKoAbg59I7X7In73R7eo+is7RQdw4Ptwc+PTKKXIbT+wS8W6D2iB346
Xy5xHF/OMBAgBRvNwEd+Pkf24N4/hEfgcZwkSRzDQHhAD5ABScB7/0jrlww+ePQ+OEbAkyRN0yRB
BBKADIHh9YPgKX8VL+GLe+BXbSm6oBnwvNVi8XYKof/mQ+cHg4/soffnS5Jm2q5JfIlkCHQEwGMI
ALz4xwtzwyP80zlOr1mW53mWpclFOyBTQPy38pi8pvsSPqLP86Io8uyaxifpwHYjPD5H2vzjnS/8
3kf46H1WFGVZFjn4M0bA8PIubuc1/Ugf+DTLBS+LIrsm4ANf/XfwK/F/kOyDL8vb7VYKrwkAv1p2
8Tp82n1xr3yepZbHW6CTl8lv+dvtfr/fSsdjBvbiZfiQ/rxo8of+vMyeJi8DMIRH+gr0XuPHCOoA
Dubv99/f3/uNPPM3av5x/vD9w88Pfn5y/eH6O6Z+4frB9YPrB9cPrh9cP7h+DN//c/3k+sn1k+sn
10+un1w/uX72/v5Cv74pStYPrB9YP7B+YP3A+oH1A+sH1g89f//B+kl/f8L6kfUj60fWj6wfWT+y
fmT9yPqR9WOP31/7Aetn1s/4/Tr3D9w/cP/A/QP3D9w/cP/A/QP3D9w/cP/w8f+38vdj7p+4f+T+
kftH7p/5/3X+f5/6BdRvoH4D9RtG6Kfw/jPvP/P+M+8/8/4z7z//h/efnX7ZmPpxmn7ZNP20afpt
Vn9O9NfG6MdN1K9T/b1KP0/194bo503U75uoHzhVv9Dx4/QTrf7jaP3Ghn6kCDgO0o9UBcgJ+pVG
QbKmnykCmEP1M1UAc7x+pxXQRAbH6YdCPLZNv1Q0XHvol2oH3umnAv+gnwotTShqigZnq34rFGTb
9VsfvAQwQT9W5XMhgildaOjXqgBul36tiohO0M+18r/j9XutAc3BQP1gMwLaA+QQIYj2MWz01S+u
eCPePEI/uW4BKqewIFGIdDK+MzKyqa/KtXUVVp1DkgITgjUhsKW79KONAWehoV8tVmWKNnVfG97l
iblELpYYqqYnzGsvSPOEuUhDsEaUdc473FcRyHup3qzZhmht03H1zF2K45PrbufGSM1C42HlovNB
A3NPOqn6BQ5yx/prvR9buPf1vJAZGJiBv2SxChYKZW5kc3RyZWFtCmVuZG9iagozMjAgMCBvYmoK
MTIyNAplbmRvYmoKMjg5IDAgb2JqCjw8IC9MZW5ndGggMjkwIDAgUiAvVHlwZSAvWE9iamVjdCAv
U3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMTY0IC9Db2xvclNwYWNlCi9EZXZpY2VH
cmF5IC9JbnRlcnBvbGF0ZSB0cnVlIC9CaXRzUGVyQ29tcG9uZW50IDggL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgPj4Kc3RyZWFtCngB7ZpZd6JAEIWTSeKCiIKAgnH9/z9y7q3qZlF2zpwzD90PQwTq69ra
M6mbjw+3XAb+dQY+dU3bxhjby0iINatdhzNqZtUPAxGlyR9d5Y3PAQj7tjG2F3u7l2BetHZfX1/2
R/Okh1Cxh225hKIPOwn6Ct+m7bdd/MCbvYTC3pr/cBFTQ7T7IADdHkY0XiwWvACiTsgbrYDSXsxh
vFgul7yIGxJGJ4EPZX/uLsYrLoEUTvClZhf4pLCnOWzXXMKAFwzDZrIJ8WJPa08XGYikSugG/HB7
mG82G9/38a/nrRGIEIwLLQBNAOKHvefBestFhhCQBxtEK4Ddo/YbWAfBbrcLAjCEwGKQgGC7AIU9
rPdcYBSEVgAziBLAAQkA7m+D3T4MoygKQyCEIIk0Lrw6UQEwAWofRQeuKNrvxQeUooihDfD9jQ5Y
e9w/jA5xnCRJHB+ikFF4a1QCzWAOVT0N6gEjkAr48B/2ScqVgLDfBf4GtVQX5O0OgLfZIv5DnKbH
0+l0TNM4Rh7gwmrVB0ANl4yAAcQJzLMsAyJJJAg2A9tRvxfePGAXoQaSQgaQpDDP8xyINGUQW8bA
VtBubAEgBYyAARyz/MyVZ8djfEAe0U2ShFaA5HC1Qg3owPGUn3+5zjmCgAsB6mCS8N6MRRstcAr8
YB/RAdhfLhcQEESMGPoBPAfsooAR0IHL9Xq9wIUsZQw4EfTAdEJDDqSPAWAKGAHsb7cbCMhCAsBW
AJJFeNwMWNCD7Y4pyM5iT8I5lyQIgJ3QcCA1B9qHBEgKALjf7wpgEggwZWj3AG2kAERwNYDr71my
CICtYyfAFw8IuN0fjwdcsAAchyEeaBXfASHP00CAFqHqAcswDoAi3EwIt8uv1HE84P54Pp9IggO4
HLg+cGfBfR9c8J3q+sDlwPUB/4Ph+sDlwPWB/MbjzoL7PuBvvq4PXA5cH+gUyJ2F/+EsFHOkKVMc
jBPro7BxgyhM814BcTR8kjV3GDdzHKgTzekDyfpIVGaqo0aiMtWdMZSdOxamOjBrMK3ywvTROKf7
djgvg+HKcJ76QDnUbZmtz5QHoPJQZGoXKDib7xIoCChjqEskh6ESiQJEI5kk0kgMc2QiG8MMoQox
aCXHSmVQG1QhsFkQsWyEWFcBqMggaqOVC6E4soRD5MJC75smWBrNlorvu2SqoqtqTC8Ci8otyEFV
9J0m2lYJo2VjqUNBUOGaEOjWlDr7RGOGwSAsQbRvUb9HSOcVAv90gKK96O6DxXsFqA84mIYB3yma
U6xVobGxBFqIkoB+UAStrXm/vUmDJEL/CIIcLuw+YP8ikYYAG2tbmHf5r2FIKUw5uK1Z9raJtfNi
3y38KG/07y/kikH9x859aw/rduZT7Y3+Dy+MfoOmN6Zt3URy91wGejLwF7/fRT4KZW5kc3RyZWFt
CmVuZG9iagoyOTAgMCBvYmoKMTA1NwplbmRvYmoKMjkxIDAgb2JqCjw8IC9MZW5ndGggMjkyIDAg
UiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgNjEgL0Nv
bG9yU3BhY2UKL0RldmljZUdyYXkgL0ludGVycG9sYXRlIHRydWUgL0JpdHNQZXJDb21wb25lbnQg
OCAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAHtlt12hDAIhLWt1fd/4sIMEHTVkPZs
r+Si/uUbYMLmdJqeeBx4lwPzPP9WWtAWwyIN9bsRCWf216rCnspPJYUGfDDai4qZvtrgg0a3AsP3
tD7Zh47ADv+0oBg/VXisdxhXvCkIcImuVuyLEQpdASw40NBQCXnfEYjsuly4haEK5ClwaUFOH7Rq
hABWXPE5PfBvBhX6HaT0GRcRq0CduanAeetduBVhAqmA8w6UlwzwblkCX9cQ6OcHD+uRfds2LYEd
tC3s5NfuHYeC8gv3sNO/5T/wLAAG/IGXArr+n+engUP5F2yedK8GDvYvs28GYP9H/OcAkLfx8fRo
/93zZxNoEyS+Idr8Y/sujmF+ww7AAcyw8C8/4At+goDw/An48fGCn0+vvI0CTMAUpJna+WMKrQIl
NWRy9Pi7M59F7SrwA1jphl81fxTACQ7UaGa/x80CnSIJo/lQwt1DjIFxvLCzwr8zvtBqGKRjF8PJ
0JMbetT9m5F83wV9QYbi3j+WrkHFTQnLi4Is953p5/5x4D8c+AEvEQ8pCmVuZHN0cmVhbQplbmRv
YmoKMjkyIDAgb2JqCjQwOAplbmRvYmoKMjY3IDAgb2JqCjw8IC9MZW5ndGggMjY4IDAgUiAvVHlw
ZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWlnaHQgMTg0NyAvQ29sb3JT
cGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBvbmVudCA4IC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2d2XriOBBGs5odjI2N2SHv/5DzV8kWhjbg
9HxzNUcX3SThr00ySHWC8/bGoAL/VQXe39//1rSkrfFLKy1lfNjfRJTcPehnoS36+Phof9mnGM3z
Jb2O5puvDdTPvEqbR/UPXuQQnuWaz9bwb4SfPTVwlbv4y4c/NAsvDUS5JEFb/2smehgwvTkK8u84
ZKVl4FEGLe9fX9ImcXx/u4UXEVy9mzxJBnEkiVnwFLwInRG4+xB7UA+Hw9FopH+Hg4Es1Ab8aR0G
muitcubcxGMfZuNqIDzvTwPRvckHA1NP6jGWBYVQR/AgAPu2Re9yOZd6Op3NZtPpdDIZKwRLwWfB
ntnt3/VK3uUSz33IhhlQAGYgLKOHequ8gh9PpF4s0jRdLBbzaEA17NaH6D/q6CWfzueLdOkjvTfw
5xya3Fae9FZ6yWdSZ1me51mWLdOFIvAMPIBwIbRTuOo9esnnkucrH7kMKAUrgVWgWYUd+s9Pz35c
y4uiLMuiKGRAKUzGXsKmgjdTUPs3vRVvOl8s87wo1z5KGVANLABNwVO9LZ3haGLJr1blutpsNlW1
Lle5StBUoJ6Be/9KS+WzuR9P5D4rCsm3260srIuVMqgT8AJYBe/yD/ok8fDTLC/Larvd7XYyUXkG
loAugyd6LV4Pfyr3in6z3e33e1nYKINsOVcCugrCZdzl3151ksHI0l/mil7yw+EgCx6AJWBLIF4D
f8Rv1470WroKv1Dy+8PxeJQFBaApqAsQXga6/Vv5bfZShV9tdofj6XSShZ0nYDNoK6C5hrr813pL
390H/V4JrLK0j37g/pW+6Y+n8/msCExf5EE/eO4/rD4rn6oX9Uog6O0SeBq/X3vzoD+czpfLRRFY
AVxvE/BaH6Zvu7vXhwnso89WFv+tflUvgH76stLiifH7BPxafzxffn5+VAGfgN/7R0/9WD9cP7x+
8PqrDQDvP76B6//+zfsn75+8f/L+yfsn75+8f7J/+E3/wM7/7B/YP7B/YP/A/oH9A/sH9g/sH/ry
G8Nf7J/YP7J/ZP/I/pH9I/tH9o/sH9k/sn/s9/tP7J85P3B+4vzE+YnzE+cnzk+cnzg/cX7i/MT5
ifMTv/9afwLurTX0cazw2UX7/NFswfmZ8zPnZ87PnJ85P3N+5vzM+ZnzM+dnzs+cnzk/c37m/Oz3
IGq1D97oH9A/sXtn6e5L9I/on9E/pH9I/5D+If1D+of0D+kf0j+kf0j/kP4h/UP6h/QP6R/SP3x0
/2v6Z/QP6R/SP6R/SP+Q/iH9Q/qH9A/pH9I/pH9I/5D+If1D+of0D+kf0j+kf/jn30/k9w/5/Uv6
5/TP6Z/TP6d/Tv+c/jn9c/rn9M/pn9M/p39O/5z+Of1z+uf0z+mf0z+nf07/vHUDC+5fwf0ruH8F
9+/g/iXcv4X7H3P/Z/7+Kn9/dg8/gh/Bj+BH8CP4EfwIfgQ/gh/Bj+BH8CP4EfwIfgQ/ihWAn8HP
4GfwM/gZ/Ax+Bj+Dn8HP4Gdn+Bn8DH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ5EevfH3g9/hR/Aj
+BH8CH4EP4IfwY/gR/Aj+NEP/Ah+BD+CH8GP4EfwI/gR/Ah+BD+CH8GP4Efwo1gBPn8FP4Ofwc/g
Z/Az+Bn8DH4GP4Ofwc/gZz/wM/gZ/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+L9IjPX8HP4GfwM/gZ/Ax+
Bj+Dn8HP4GfwM/gZ/Ax+doGfwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az+FmsAPwMfgY/g5/Bz+Bn8DP4
GfwMfgY/g5/Bz+Bn8LMj/Ax+Bj+Dn8HP4GfwM/gZ/Ax+Bj+L9IjPn8HP4GfwM/gZ/Ax+Bj+Dn8HP
4GfwM/gZ/Ax+Bj+Dn23hZ/Az+Bn8DH4GP4Ofwc/gZ/Az+FmsAPwMfgY/g5/Bz+Bn8DP4GfwMfgY/
g5/Bz+Bn8DP4GfyshJ/Bz+Bn8DP4GfwMfgY/g59FesTnz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwM
fgY/g5/Bz+Bn8LMl/Ax+Bj+Dn8HP4GfwM/gZ/CxWAH4GP4Ofwc/gZ/Az+Bn8DH4GP4Ofwc/gZ/Az
+Bn8DH4GP4OfzeBn8DP4GfwMfgY/g59FesTnz+Bn8DP4GfwMfgY/g5/Bz+Bn8DP4GfwMfgY/g5/B
z+Bn8DP4GfxsBD+Dn8HP4GfwM/gZ/CxWAH4GP4Ofwc/gZ21+djpfLpfz+fQ3/ZP1dndo9IfdZv2r
8/cyL+71Rd7//Drv1Kfzfue/8bTRH09nZX86WvxFns6n4x7np1Gt32z3jX6/rWr98NX5Kxm4PluV
pj+e5P0Yyp+Z/+EgeX5+CfpU+mqzOwS9wq/KVbboof9y/SzN8kL6/UHOD4e9p58tZu7/6+vx+eHT
9CMBSJuAarvfH6TeK/0yTl8i+eej/bfph67PVuu1AvDhqydbhul7ov/4kD4ZWgGVQKkAdj68+l6+
0SCR/kOja/9r+u9kOJTeEijXm812u91sbPFmWn1N+bv17/YOKv3AryDNQFFWlcRVtVb2Waq7/9TT
597f7/efrv80/Wg8swBkYF1J7fKlzd5omCTfdfUe6b8HtoJmqoBF4KNQ9Lb4x0r/+6m+TmA0mWoK
l9lqVRTFamVyy16L31ZfqF6nf9fbEpqohOkyy32YfD6t3b/SewVlQCVIFUKWLZcmt+jdfbdeGznN
aJgBlXBkBsyCD6nNe5TbM+POLz6o9TaFWkOqoYo4XywW83mQ29qJ194zvWegSZzIgo+pe68v3bD2
H+jDJqwxMJ7IxHQymYwVfB19LX+s912MSjAYKoR6mNqm3q9cW/qP8g9rUCVQDdzCyIarlXtL3uG/
mQEFYAbcgoKQZ/mWc/PerJ1Y9JsHHphWlxkIFhSEtEHdknd6N1Nmwa5OM2AWFIR5lu928DdOb75o
IgghBBMurp0/ql004gbqEDwIOTbXnnlQPwzejVwNWAxxWFJ95F4Bs+ECL2X9qFZ3zXyMvhVBtFDL
Q1yv1TLRPDWauH7jee4xjpbg5mF8wqsHN6rmi1ei2583qub/25/2++rfaPt54Fn/9wr8A5+tGUIK
ZW5kc3RyZWFtCmVuZG9iagoyNjggMCBvYmoKMjMwNwplbmRvYmoKMjY5IDAgb2JqCjw8IC9MZW5n
dGggMjcwIDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY0IC9IZWln
aHQgMjQyMyAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1Bl
ckNvbXBvbmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae3dx0LjSBQFUBqM
bXDOOTD//5HzXkkODcaYWc3iaEHTwK3wVIBUB9tPTw4V+B9W4M9fx28H+Fe4+s/jTdwIlw892MJ3
8fj4Ay2c08/Xx+mjPzZQf+F1tnq//sQPDVzHXy5HaeKBFqovya8u2UY5yrv5seqzd0bwV7wK12+j
jQdaKPmq88i9Xo5G47qBb0Zw7v3lpaSb5yMaqlu4N4VL79l3s9k6H83muYFShNsDyHwZfMQz3Y7j
7e0t3rZapxaqKt7KVyPLwlfxzL6XI5uoGihFLF/4tYXy4at4pjvV8f7+lkOIOWQDd/LV6HPw7Ux3
u91er9ftdjp1A1nEqoHb/Zfuo3QZ70S2X45oIhuIOeQAqga+zefk63i/PxgMh8PBoB9jyBFEEU8D
+JzPSZ1Gf4oPhqNylBbKFCLfyHWYX/1XC/mB63wMvh/p8XgymYzHo+GgX6bQal7yfzVwzsfCKd1n
fDyZlmOSDWQNSgUadf+38nHuc/ZRu/4g47PZfD6fzSaT0TBqECWoz2Hp7noCdf8lH7Xv9gbD8WQ2
W5RjPpuOR2UG7Va1Br7NNxpZ/Oh+OJpM5/PlcrVaLRfZQDWA6hR+XULRYEzr+TT8Xn80ns4WkV6v
16WBSRlAmcBpEX8a/zkfw4/ZT2bzZaQ3m002MJtmBaKCsQTu51utMvzsfhXp7XabDcxnUYGoYJ6B
b/OxNht59jpRvZj9cr3ebne7XTawmJUJvL+V/NclXOZfvnPz7PVy+Nn9brff73fbHMAkKtjtZP7W
Ej7lc/Xk2RtN54vVZrvfHw6H/W6zXi7KGajyuYQj8KV+p9WTZy+Hv43eS367WUU+CpD5agn/kB9H
9SN/OByPx8M+81mAzNffAt/mc/X1h+OY/uaS366XdT5OQPkWupPP1Vfyu/3x+PHxcTxEBat8OYE/
5nPxZ/+f83ECcgE8kC+n71M+T8Dj+ar85/FvVvPf5/eHj49//vnn4xgrQF79frv+rB/fP35++Pnp
94ffn64fXD+4fvjd9bvrJ9dPrp9cP7l+cv3k+sn1k+sn10+P7h/n/q/rR9ePrh9dP7p+dP3o+tH1
o+tH14+uHx/7+wvXz+4f3D+5f3L/5P7J/ZP7J/dP7p/cP7l/cv/k/unu4x/KwzdGE/eP7h/dP7p/
dP/o/tH9o/tH94/uH90/un90/+j+0f3jnecPcP9cnr7B/oH9A/sH9g/sH9g/sH9g/8D+gf0D+wf2
D+wf2D+wf2D/4N7zF+bTP9o/sH9g/8D+gf0D+wf2D+wf2D+wf2D/wP6B/QP7B/YP7B/YP/jm9Sv8
/Ym/P7F/Zv/Q8+d5/kCvf+P1f7z+kdd/8vpXXv/L66f9+vXn+CN/5I/8kT/yR/7IH/kjf+SP/JE/
8kf+yB+fLkcsh+fnl5fGa5O/8lf+yl/5K3/lr/yVv/JX/spf+St/7ds/tX9q/9T+qf1T+6f2Ty/b
p0/2T+0f2z/nB/yEH/EjfsSP+BE/4kf8iB/xI37Ej/gRP+JH7/yIH/EjfsSP+BE/OleAn/EzfsbP
+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4WYuf8TN+xs/42VmPnjz+yvN3ef4yz9/m+es8f98b
P+JH/Igf8SN+xI/4ET/iR/yIH/EjfsSP+FGDH/EjfsSP+NG5Ah5/5fFXHn/l8Vcef+XxV/yMn/Ez
fsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/OyFn/EzfnbWI4+/4mf8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4
GT/jZ/yMn/EzfsbP+Bk/e+Zn/IyfnSvAz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8
jJ/xM37Gz/7ws7MeefwZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn
V3z2xI/4ET/iR/yIH/EjfsSP+BE/4kf8iB/xI37Ej/gRP+JH/Igf8SN+xI/4ET+6VICf8TN+xs/4
GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/Iyf8bOLHnn+Qn7Gz/gZP+Nn/Iyf8TN+xs/4
GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/jZpQL8jJ/xM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yM
n/EzfsbP+Bk/42f8jJ9d9Mjjz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37G
z/gZP+NnlwrwM37Gz/gZP+Nn/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM3520SOPP+Nn
/Iyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/gZP+Nn/IyfXSrAz/gZP+Nn/Iyf8TN+
xs/4GT/jZ/yMn/EzfsbP+Bk/42f8jJ/xM37Gz/jZRY88/oyf8TN+xs/4GT/jZ/yMn/EzfsbP+Bk/
42f8jJ/xM37Gz/gZP+Nn/Iyf8TN+dqnA/9PP9sfjx8fH8fBf7l8Wq83ulN9t18vfXf+OZ5/zs8lo
+Oj1U394Mz/odR+5/njvnvOHw/GY04/xR/+DXueBfLvOxwbgrs5vN6tFlX9r//T7v1Xlp/PM7/eH
w2G/z/x0nP2/tZrNu78/X0t+MIr8arOt8rvNehn5Yb/kX+/lGyXfiw3sPAGbXYwgZh/5+SQv37P/
e/kAsFYBkOFkFhPYbLe73W67Xa8W8yhfnL7Mv7x8+/vvlI8TMJ0vVuttOTar5WKW0y+n7/v883MC
XOstTsBgHBOICpQjZl9WX56+Zvb//Hzz90+djxMQBcgBLFer9Xq9itHn2cvpt5uv3+X/pAA3Gs04
AZ1eTCAqsFhGC6vlcj6L6ufwS/mi//h2//Lzv+RfGs1mOyaQA8gGooUY/Gya3Ver77VxP18K0Ikl
HDOYzssR8Tz50X279Xo3XxWwGkA0MJlOZ7PZdDouxe9Uw29U1bs5/iDg19MABtlAOcajYRl9Lv7o
/n4+z2AMIEo4GA5Ho3H0XeJl9PXi+1q/+EmaJS1noG6gW1oYxjHol8nX3X9dfNWP4TqfS6gaQbfX
6/cHg5KOU3+K389XCN4qU+hGC3l0u533rH2snTx5Xxbfpf/qjwhKCaIG751OpxvhTF/Fc6B/qsz1
2/LhaPwlZhAlaLXbb9FEOSJd9X67+HUrVw2UGpQW3uJoR7oM/jz6W/1XZ6DMIL4NYggxhhxFZCOd
c7/Er8d9ef8ygNJAtFDayH+q9M2lc8mfR5A1yCHEUbKZjs5/jJc1FDPIImYLVRMZrtPVwrtR/NMg
yhROLZQm6nDp/Oa6PUWrfy8N5BjOR46p7vxO79lE1UAZQmaihfwnjvoTP8TPDZxb+F36MoLsr8qe
u769bKqJX789DfXLv9dfdPf9L8n8wN3E509+buHz5x/6f93IQ1/ri1TgP1TgXybTB44KZW5kc3Ry
ZWFtCmVuZG9iagoyNzAgMCBvYmoKMjU3MQplbmRvYmoKMzA5IDAgb2JqCjw8IC9MZW5ndGggMzEw
IDAgUiAvVHlwZSAvWE9iamVjdCAvU3VidHlwZSAvSW1hZ2UgL1dpZHRoIDY1IC9IZWlnaHQgMjE2
MiAvQ29sb3JTcGFjZQovRGV2aWNlR3JheSAvSW50ZXJwb2xhdGUgdHJ1ZSAvQml0c1BlckNvbXBv
bmVudCA4IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4Ae2b25aiQBJF66Z4BQVBQK1L
//9HzolMAtQStWbWvO18sNQmDhEnM7bR1fbLCwsH/v8OvL6+/rc3UejZ+qvKWWj/9A8afczVk2cl
zsPe3t7OXz4j0V+v2GH17z6W6C4dYrtn3fuPBM7D34cVRJ6RiNeEy0P0h63w7EziThJDvIJCsD/o
tUnEC8YVwp/ruhg+GVbMwxVGBYZ4BUwm035JKVTySMEEwv1jeNKv6bST6BRGUriMT5KZ1nw+12OS
mIQlcU+hK8DcU/YKV/DClmlIwhXCdbdy8AS6eItexiUNSZjC3RQkEA0I97fw1Wq1Xq/1uLQsLhRG
MrANNPuT2VzhCk5tSWNpSUgh2qBb3RXw+DTNss1mk2VRQgJSsCJuCZgBqsAS6OMVvbUljVRJnBVh
F1/mYO+cCyj/VNF5XhRFnm+DQldEl8KVQi+gLQgGWLyid7aKIigsF50LXUtcpNAJdBXIwDRT/K4s
q6oqy11QWCmFzoVw+aiAdsAKyAuF721VQSHVVoQUVMO4QKwgJFDsqmpfN01Tm0K+zdZKIUlsJ0cE
7BTpECSzxdIS2JX7um7atm3quiqLfKMUtBF2HGND/CohCkwTVWAOlJVu3x4Oh7Zp9pVSSNdewyMB
VbDZFuVetz8cj8dD21oKoYZowqhA2ITZfLnOVEFVW/zpdJJCs5cLWRr24fZhNFvNAp1Ds0AV7JSA
4j8/P02hVg3RhNAPv0+zC6iRZtrELFRg8V9fX1Jo631ZbGSCTkLYhl/t0AtMTSBYULfKPwqcDqrB
TDABa6g7GaiTTCBYYAl8f38rBQlUuyhgPX1fwHbRBJpQQRRQDZ3A/AkB28UgYAn8/PwoBRews/g4
g24Xm8O1gLbhWQFtgkq4FChtH/8gsNcmDCXYNvxdwOL//fsnE8I+IoCJHCR6AR7ARD4X+Gw8Mh+0
eKBBk3OAByXnQH/55xzggf0KhXOAB5yD+OtEeoFeoBfoBfsHDs4BHnAO9M+N9AIe6LsDnAM8sO+Q
cA7wgHNg3+XhHOAB5yB8qYtegAfh+40wESbCRJjYfdmXzwU+F/hciF98pxfoBXqBXhj+Gwq/S4OJ
MBEmwkSY+PKCB3hg/+mXc4AHnANzgHOAB+EYwER6IRwEPhthIkyEidEBeoFeoBfoBXcAHsADeODd
wKwMD+ABPIAH7gA8gAfwwLuB+QAewAN4AA/cAXgAD+CBdwPzATyAB/AAHrgD8AAewAPvBuYDeAAP
4AE8cAfgATyAB94NzAfwAB7AA3jgDsADeAAPvBuYD+ABPIAH8MAdgAfwAB54NzAfwAN4AA/ggTsA
D+ABPPBuYD6AB/AAHsADdwAewAN44N3AfAAP4AE8gAfuADyAB/DAu4H5AB7AA3gAD9wBeAAP4IF3
A/MBPIAH8AAeuAPwAB7AA+8G5gN4AA/gATxwB+ABPIAH3g3MB/AAHsADeOAOwAN4AA+8G5gP4AE8
gAfwwB2AB/AAHng3MB/AA3gAD+CBOwAP4AE88G5gPoAH8AAewAN3AB7AA3jg3cB8AA/gATyAB+4A
PIAH8MC7gfkAHsADeAAP3AF4AA/ggXcD8wE8gAfwAB64A/AAHsAD7wbmA3gAD+ABPHAH4AE8gAfe
DcwH8AAewAN44A7AA3gAD7wbmA/gATyAB/DAHYAH8AAeeDcwH8ADeAAP4IE7AA/gATzwbmA+gAfw
AB7AA3cAHsADeODdwHwAD+ABPIAH7gA8gAfwwLuB+QAewAN4AA/cAXgAD+CBdwPzATyAB/AAHrgD
8AAewAPvBuYDeAAP4AE8cAfgATyAB94NzAfwAB7AA3jgDsADeAAPvBuYD+ABPIAH8MAdgAfwAB54
NzAfwAN4AA/ggTsAD+ABPPBuYD6AB/AAHsADdwAewAN44N3AfAAP4AE8gAfuADyAB/DAu4H5AB7A
A3gAD9wBeAAP4IF3A/MBPIAH8AAeuAPwAB7AA+8G5gN4AA/gATxwB+ABPIAH3g3MB/AAHsADeOAO
wAN4AA+8G5gP4AE8gAfwwB2AB/AAHng3MB/AA3gAD+CBOwAP4AE88G5gPoAH8AAewAN3AB7AA3jg
3cB8AA/gATyAB+4APIAH8MC7gfkAHsADeAAP3AF4AA/ggXcD8wE8gAfwAB64A/AAHsAD7wbmA3gA
D+ABPHAH4AE8gAfeDcwH8AAewAN44A7AA3gAD7wbmA/gATyAB/DAHYAH8AAeeDcwH8ADeAAP4IE7
AA/gATzwbmA+gAfwAB7AA3cAHsADeODdwHwAD+ABPIAH7gA8gAfwwLuB+QAewAN4AA/cAXgAD+CB
dwPzATyAB/AAHrgD8AAewAPvBuYDeAAP4AE8cAfgATyAB94NzAfwAB7AA3jgDsADeAAPvBuYD+AB
PIAH8MAdgAfwAB54NzAfwAN4AA/ggTsAD+ABPPBuYD6AB/DgHg8+v75/fn6+vz5Ph2Zf5pt0tZgn
08nH+9ubmsf7KPy80UzN4dQLHNu6+ptAvquuBXbb5zNINzcFsvVzJSxWvYBq+JYFn1bCbputl894
MOsE6vZoJpiAeRgF5rOHJk6jQFEGgc+vLyUQNqGwDOaz6YNdmASBbCuB5mApSOCkCvZlsYkCk7vb
+GECy7UEdvvmYAq6//FgFhTaBMtg8nHnHLybwFwCtg11ezgeT6fT8RgsiOfIBN7HD5ILaBuKat+Y
gpYSUAW57WL0cFTgzQSSubbBTNjXUrDV2h7k21S76JswcpRNYJJoG2INUmjatm0anePCKpAFSfTw
psDrqwQ+TGAZU6j2tSSaWgUogXgOk+Chtc7vZjKBaEJMoSgrk6j3lbZga5vYW3BfwFPIdztJaJU7
FZBZL7uHowJWwzSZycZ1utnmhSTKcqf4bWYWBhh0p+B2CbGGkIJ83OZ5YSu3+1snegJm4ZXAS3jr
zQXmwcfNZiuNfKv6FW9bMLU9iKfgWkBcksaFwjrNso2tLMRfJnDBs+7FIBBsWK7W61QaWarbr2RA
KMATGBXoijAjl6uVNLQsPMbHAn6doiED1RAO0zTksFguTUSPi7ndv+ujYOFIBkHAzrMpzObzRVwK
jwaGAu4KdArqqWkiCWlo6WcS7j/EX57jPh3bSyvCWiJIBJFES+lbE2gHR+9vKiYghXdTCBKWh4Jj
+BA/cv9BIUpMbIVgu7vC/f7j8TGFWIUlYWlo2ZMYHvK/cQZ7EwYFSyJqdOF2+8fxnQ2WQ7DCVMIK
bwSL7t6/NzJshquEn3p4Lt5zGCRifBf98P5nOVhId/M++o7/g496NgRcPbu46u6Lq8D48m7E7z+8
0vh9wTPvdCLPXMo1OPC/OfAfazPoGAplbmRzdHJlYW0KZW5kb2JqCjMxMCAwIG9iagoyNDkyCmVu
ZG9iagozNDcgMCBvYmoKPDwgL0xlbmd0aCAzNDggMCBSIC9OIDMgL0FsdGVybmF0ZSAvRGV2aWNl
UkdCIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZ2Wd1RT2RaHz703vdASIiAl9Bp6
CSDSO0gVBFGJSYBQAoaEJnZEBUYUESlWZFTAAUeHImNFFAuDgmLXCfIQUMbBUURF5d2MawnvrTXz
3pr9x1nf2ee319ln733XugBQ/IIEwnRYAYA0oVgU7uvBXBITy8T3AhgQAQ5YAcDhZmYER/hEAtT8
vT2ZmahIxrP27i6AZLvbLL9QJnPW/3+RIjdDJAYACkXVNjx+JhflApRTs8UZMv8EyvSVKTKGMTIW
oQmirCLjxK9s9qfmK7vJmJcm5KEaWc4ZvDSejLtQ3pol4aOMBKFcmCXgZ6N8B2W9VEmaAOX3KNPT
+JxMADAUmV/M5yahbIkyRRQZ7onyAgAIlMQ5vHIOi/k5aJ4AeKZn5IoEiUliphHXmGnl6Mhm+vGz
U/liMSuUw03hiHhMz/S0DI4wF4Cvb5ZFASVZbZloke2tHO3tWdbmaPm/2d8eflP9Pch6+1XxJuzP
nkGMnlnfbOysL70WAPYkWpsds76VVQC0bQZA5eGsT+8gAPIFALTenPMehmxeksTiDCcLi+zsbHMB
n2suK+g3+5+Cb8q/hjn3mcvu+1Y7phc/gSNJFTNlReWmp6ZLRMzMDA6Xz2T99xD/48A5ac3Jwyyc
n8AX8YXoVVHolAmEiWi7hTyBWJAuZAqEf9Xhfxg2JwcZfp1rFGh1XwB9hTlQuEkHyG89AEMjAyRu
P3oCfetbEDEKyL68aK2Rr3OPMnr+5/ofC1yKbuFMQSJT5vYMj2RyJaIsGaPfhGzBAhKQB3SgCjSB
LjACLGANHIAzcAPeIACEgEgQA5YDLkgCaUAEskE+2AAKQTHYAXaDanAA1IF60AROgjZwBlwEV8AN
cAsMgEdACobBSzAB3oFpCILwEBWiQaqQFqQPmULWEBtaCHlDQVA4FAPFQ4mQEJJA+dAmqBgqg6qh
Q1A99CN0GroIXYP6oAfQIDQG/QF9hBGYAtNhDdgAtoDZsDscCEfCy+BEeBWcBxfA2+FKuBY+DrfC
F+Eb8AAshV/CkwhAyAgD0UZYCBvxREKQWCQBESFrkSKkAqlFmpAOpBu5jUiRceQDBoehYZgYFsYZ
44dZjOFiVmHWYkow1ZhjmFZMF+Y2ZhAzgfmCpWLVsaZYJ6w/dgk2EZuNLcRWYI9gW7CXsQPYYew7
HA7HwBniHHB+uBhcMm41rgS3D9eMu4Drww3hJvF4vCreFO+CD8Fz8GJ8Ib4Kfxx/Ht+PH8a/J5AJ
WgRrgg8hliAkbCRUEBoI5wj9hBHCNFGBqE90IoYQecRcYimxjthBvEkcJk6TFEmGJBdSJCmZtIFU
SWoiXSY9Jr0hk8k6ZEdyGFlAXk+uJJ8gXyUPkj9QlCgmFE9KHEVC2U45SrlAeUB5Q6VSDahu1Fiq
mLqdWk+9RH1KfS9HkzOX85fjya2Tq5FrleuXeyVPlNeXd5dfLp8nXyF/Sv6m/LgCUcFAwVOBo7BW
oUbhtMI9hUlFmqKVYohimmKJYoPiNcVRJbySgZK3Ek+pQOmw0iWlIRpC06V50ri0TbQ62mXaMB1H
N6T705PpxfQf6L30CWUlZVvlKOUc5Rrls8pSBsIwYPgzUhmljJOMu4yP8zTmuc/jz9s2r2le/7wp
lfkqbip8lSKVZpUBlY+qTFVv1RTVnaptqk/UMGomamFq2Wr71S6rjc+nz3eez51fNP/k/IfqsLqJ
erj6avXD6j3qkxqaGr4aGRpVGpc0xjUZmm6ayZrlmuc0x7RoWgu1BFrlWue1XjCVme7MVGYls4s5
oa2u7act0T6k3as9rWOos1hno06zzhNdki5bN0G3XLdTd0JPSy9YL1+vUe+hPlGfrZ+kv0e/W3/K
wNAg2mCLQZvBqKGKob9hnmGj4WMjqpGr0SqjWqM7xjhjtnGK8T7jWyawiZ1JkkmNyU1T2NTeVGC6
z7TPDGvmaCY0qzW7x6Kw3FlZrEbWoDnDPMh8o3mb+SsLPYtYi50W3RZfLO0sUy3rLB9ZKVkFWG20
6rD6w9rEmmtdY33HhmrjY7POpt3mta2pLd92v+19O5pdsN0Wu067z/YO9iL7JvsxBz2HeIe9DvfY
dHYou4R91RHr6OG4zvGM4wcneyex00mn351ZzinODc6jCwwX8BfULRhy0XHhuBxykS5kLoxfeHCh
1FXbleNa6/rMTdeN53bEbcTd2D3Z/bj7Kw9LD5FHi8eUp5PnGs8LXoiXr1eRV6+3kvdi72rvpz46
Pok+jT4Tvna+q30v+GH9Av12+t3z1/Dn+tf7TwQ4BKwJ6AqkBEYEVgc+CzIJEgV1BMPBAcG7gh8v
0l8kXNQWAkL8Q3aFPAk1DF0V+nMYLiw0rCbsebhVeH54dwQtYkVEQ8S7SI/I0shHi40WSxZ3RslH
xUXVR01Fe0WXRUuXWCxZs+RGjFqMIKY9Fh8bFXskdnKp99LdS4fj7OIK4+4uM1yWs+zacrXlqcvP
rpBfwVlxKh4bHx3fEP+JE8Kp5Uyu9F+5d+UE15O7h/uS58Yr543xXfhl/JEEl4SyhNFEl8RdiWNJ
rkkVSeMCT0G14HWyX/KB5KmUkJSjKTOp0anNaYS0+LTTQiVhirArXTM9J70vwzSjMEO6ymnV7lUT
okDRkUwoc1lmu5iO/kz1SIwkmyWDWQuzarLeZ0dln8pRzBHm9OSa5G7LHcnzyft+NWY1d3Vnvnb+
hvzBNe5rDq2F1q5c27lOd13BuuH1vuuPbSBtSNnwy0bLjWUb326K3tRRoFGwvmBos+/mxkK5QlHh
vS3OWw5sxWwVbO3dZrOtatuXIl7R9WLL4oriTyXckuvfWX1X+d3M9oTtvaX2pft34HYId9zd6brz
WJliWV7Z0K7gXa3lzPKi8re7V+y+VmFbcWAPaY9kj7QyqLK9Sq9qR9Wn6qTqgRqPmua96nu37Z3a
x9vXv99tf9MBjQPFBz4eFBy8f8j3UGutQW3FYdzhrMPP66Lqur9nf19/RO1I8ZHPR4VHpcfCj3XV
O9TXN6g3lDbCjZLGseNxx2/94PVDexOr6VAzo7n4BDghOfHix/gf754MPNl5in2q6Sf9n/a20FqK
WqHW3NaJtqQ2aXtMe9/pgNOdHc4dLT+b/3z0jPaZmrPKZ0vPkc4VnJs5n3d+8kLGhfGLiReHOld0
Prq05NKdrrCu3suBl69e8blyqdu9+/xVl6tnrjldO32dfb3thv2N1h67npZf7H5p6bXvbb3pcLP9
luOtjr4Ffef6Xfsv3va6feWO/50bA4sG+u4uvnv/Xtw96X3e/dEHqQ9eP8x6OP1o/WPs46InCk8q
nqo/rf3V+Ndmqb307KDXYM+ziGePhrhDL/+V+a9PwwXPqc8rRrRG6ketR8+M+YzderH0xfDLjJfT
44W/Kf6295XRq59+d/u9Z2LJxPBr0euZP0reqL45+tb2bedk6OTTd2nvpqeK3qu+P/aB/aH7Y/TH
kensT/hPlZ+NP3d8CfzyeCZtZubf94Tz+wplbmRzdHJlYW0KZW5kb2JqCjM0OCAwIG9iagoyNjEy
CmVuZG9iagoxNzUgMCBvYmoKWyAvSUNDQmFzZWQgMzQ3IDAgUiBdCmVuZG9iagozNDkgMCBvYmoK
PDwgL0xlbmd0aCAzNTAgMCBSIC9OIDMgL0FsdGVybmF0ZSAvRGV2aWNlUkdCIC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlID4+CnN0cmVhbQp4AYVUz2sTQRT+Nm6p0CIIWmsOsniQIklZq2hF1Db9EWJrDNsf
tkWQZDNJ1m426+4mtaWI5OLRKt5F7aEH/4AeevBkL0qFWkUo3qsoYqEXLfHNbky2perAzn7z3jfv
fW923wANctI09YAE5A3HUqIRaWx8Qmr8iACOoglBNCVV2+xOJAZBg3P5e+fYeg+BW1bDe/t3snet
mtK2mgeE/UDgR5rZKrDvF3EKWRICiDzfoSnHdAjf49jy7I85Tnl4wbUPKz3EWSJ8QDUtzn9NuFPN
JdNAg0g4lPVxUj6c14uU1x0HaW5mxsgQvU+QprvM7qtioZxO9g6QvZ30fk6z3j7CIcILGa0/RriN
nvWM1T/iYeGk5sSGPRwYNfT4YBW3Gqn4NcIUXxBNJ6JUcdkuDfGYrv1W8kqCcJA4ymRhgHNaSE/X
TG74uocFfSbXE6/id1ZR4XmPE2fe1N3vRdoCrzAOHQwaDJoNSFAQRQRhmLBQQIY8GjE0snI/I6sG
G5N7MnUkart0YkSxQXs23D23UaTdPP4oInGUQ7UIkvxB/iqvyU/lefnLXLDYVveUrZuauvLgO8Xl
mbkaHtfTyONzTV58ldR2k1dHlqx5erya7Bo/7FeXMeaCNY/Ec7D78S1flcyXKYwUxeNV8+pLhHVa
MTffn2x/Oz3iLs8utdZzrYmLN1abl2f9akj77qq8k+ZV+U9e9fH8Z83EY+IpMSZ2iuchiZfFLvGS
2EurC+JgbccInZWGKdJtkfok1WBgmrz1L10/W3i9Rn8M9VGUGczSVIn3f8IqZDSduQ5v+o/bx/wX
5PeK558oAi9s4MiZum1Tce8QoWWlbnOuAhe/0X3wtm5ro344/ARYPKsWrVI1nyC8ARx2h3oe6CmY
05aWzTlShyyfk7rpymJSzFDbQ1JS1yXXZUsWs5lVYul22JnTHW4coTlC98SnSmWT+q/xEbD9sFL5
+axS2X5OGtaBl/pvwLz9RQplbmRzdHJlYW0KZW5kb2JqCjM1MCAwIG9iago3MzcKZW5kb2JqCjcg
MCBvYmoKWyAvSUNDQmFzZWQgMzQ5IDAgUiBdCmVuZG9iagoyMjkgMCBvYmoKPDwgL0xlbmd0aCAz
NTEgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9E
b21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2Rl
ID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL
3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb
63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZz
Bpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzz
dRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUv
M35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp
1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHV
NHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHb
Cdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0Xsuxyk
PdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8Smr
racdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4s
k4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHI
umADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWv
lja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xv
B5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzUxIDAgb2JqCjgwNQplbmRvYmoK
MjMyIDAgb2JqCjw8IC9MZW5ndGggMzUyIDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1w
bGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEg
XSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GI
iNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqew
w7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN
2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xB
nzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq
1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7g
f3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6
XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignI
qYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48
eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe
08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTef
MJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lE
xY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+
n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN8
5WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2Jq
CjM1MiAwIG9iago4MDUKZW5kb2JqCjIxMCAwIG9iago8PCAvTGVuZ3RoIDM1MyAwIFIgL0Z1bmN0
aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBd
IC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngB
lcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0P
yvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6
cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb
02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnx
Alx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXl
pcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxW
o06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQ
o0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb
4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K4
5/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8gir
LZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TF
YSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGR
AF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdY
w/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9
A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozNTMgMCBvYmoKODA1CmVuZG9iagoxOTkgMCBvYmoKPDwg
L0xlbmd0aCAzNTQgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsg
MTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0Zs
YXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSju
wdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur
78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxg
qyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv5
1psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/
V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYud
v//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhs
qUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rb
yTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8a
oj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrva
z/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2l
sqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIj
MTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQ
J+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcC
sqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzU0IDAgb2JqCjgw
NQplbmRvYmoKMjA1IDAgb2JqCjw8IC9MZW5ndGggMzU1IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0Jp
dHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAx
IDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uI
iIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nch
C7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgp
bVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pE
aTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjbo
Pq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4
j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtN
MFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xO
Uyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9
ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7sv
ers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIq
O2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCS
hhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFy
fkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfL
Ax7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJl
YW0KZW5kb2JqCjM1NSAwIG9iago4MDUKZW5kb2JqCjE4MCAwIG9iago8PCAvTGVuZ3RoIDM1NiAw
IFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFp
bgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4K
c3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J7
7sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL
5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aY
KU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr
8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxd
flz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS
2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6
RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHR
W8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ
770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0s
y0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvp
N4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOs
qC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/a
h+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/U
vzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozNTYgMCBvYmoKODA1CmVuZG9iagoyMzAg
MCBvYmoKPDwgL0xlbmd0aCAzNTcgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4
IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1Dpx
sTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw
4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs
2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujf
gNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGr
zzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9g
W/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqr
Z4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv4
8bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4
GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ3
53l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I
8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTr
jxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZf
hy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVT
buVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzU3
IDAgb2JqCjgwNQplbmRvYmoKMjAzIDAgb2JqCjw8IC9MZW5ndGggMzU4IDAgUiAvRnVuY3Rpb25U
eXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1Jh
bmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW
2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09
+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05
Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqT
MY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/Z
RN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF
+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqIn
NGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVU
OUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y
+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXj
vp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaW
SBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4k
FYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8I
kNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKr
vDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dS
rgplbmRzdHJlYW0KZW5kb2JqCjM1OCAwIG9iago4MDUKZW5kb2JqCjE4NiAwIG9iago8PCAvTGVu
Z3RoIDM1OSAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1
IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVE
ZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZ
WklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpd
eebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNs
zljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5x
e+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaY
rq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+
5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlH
jKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJ
sVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/
Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPb
WWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6
kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW
4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFr
eT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg
6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozNTkgMCBvYmoKODA1CmVu
ZG9iagoyMTkgMCBvYmoKPDwgL0xlbmd0aCAzNjAgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1Bl
clNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAx
IDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiI
iHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuw
nsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep
3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg
9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK
157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/
mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXm
StWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiaj
sHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4
eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6f
s9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd58
0oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIo
JMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0
C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI4
5NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQpl
bmRvYmoKMzYwIDAgb2JqCjgwNQplbmRvYmoKMTg0IDAgb2JqCjw8IC9MZW5ndGggMzYxIDAgUiAv
RnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsg
MCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJl
YW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9
D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5Y
R86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL
2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjx
uoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl7
6XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8
y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGb
KatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvx
EeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxg
sb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvk
p+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvL
ShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggp
CIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r4
5F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8h
K7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM2MSAwIG9iago4MDUKZW5kb2JqCjIyNCAwIG9i
ago8PCAvTGVuZ3RoIDM2MiAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1Np
emUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRl
ciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+
VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI
8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozN
CrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228G
RP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpP
utWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA
/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMz
cYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynK
yfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00
cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH
5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1S
pk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF
9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjx
E3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFx
BfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozNjIgMCBv
YmoKODA1CmVuZG9iagoyMDEgMCBvYmoKPDwgL0xlbmd0aCAzNjMgMCBSIC9GdW5jdGlvblR5cGUg
MCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2Ug
WyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA
0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13
tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOe
K5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2Z
jGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/
AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cX
i5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxs
QoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49
FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PAN
cOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+novi
blZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uy
SJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5po
NoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbq
EYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5
VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVu
ZHN0cmVhbQplbmRvYmoKMzYzIDAgb2JqCjgwNQplbmRvYmoKMTc5IDAgb2JqCjw8IC9MZW5ndGgg
MzY0IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAv
RG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29k
ZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPD
S95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68
G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEW
cwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V8
83UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwV
LzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXssw
qdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx
1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR
2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7Lsc
pD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Ep
q62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+
LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RB
yLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1
r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9uc
bwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM2NCAwIG9iago4MDUKZW5kb2Jq
CjE4OSAwIG9iago8PCAvTGVuZ3RoIDM2NSAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2Ft
cGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAx
IF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++B
iIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6n
sMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVo
zdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOs
QZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ
6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu
4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoE
elytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJ
yKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+
PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN1
3tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3
nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9J
RMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6
vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxD
fOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9i
agozNjUgMCBvYmoKODA1CmVuZG9iagoyMTYgMCBvYmoKPDwgL0xlbmd0aCAzNjYgMCBSIC9GdW5j
dGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEg
XSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4
AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29
D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1
OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErD
G9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb65
8QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF
5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8
VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TE
EKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGR
G+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/ey
uOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fII
qy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0
xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogB
kQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4X
WMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC
/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzY2IDAgb2JqCjgwNQplbmRvYmoKMTg3IDAgb2JqCjw8
IC9MZW5ndGggMzY3IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBb
IDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9G
bGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo
7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjel
K+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRs
YKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb
+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1
f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGL
nb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4
bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK
28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/
GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza7
2s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcct
pbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DC
IzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B
0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3
ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM2NyAwIG9iago4
MDUKZW5kb2JqCjIxMSAwIG9iago8PCAvTGVuZ3RoIDM2OCAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9C
aXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAg
MSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2ur
iIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953
IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XY
KW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPK
RGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l42
6D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/
+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52b
TTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+M
TlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoU
fWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7
L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzS
Kjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrA
koYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUB
cn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzH
ywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3Ry
ZWFtCmVuZG9iagozNjggMCBvYmoKODA1CmVuZG9iagoyMjMgMCBvYmoKPDwgL0xlbmd0aCAzNjkg
MCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21h
aW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+
CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvS
e+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lm
y+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2
mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtx
a/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35c
XX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDn
ktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBm
OkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx
0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3
ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8Smrracd
LMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb
6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumAD
rKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/
2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv
1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzY5IDAgb2JqCjgwNQplbmRvYmoKMjA0
IDAgb2JqCjw8IC9MZW5ndGggMzcwIDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUg
OCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAv
RmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6
cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7
sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2sva
rNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo
34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7x
q886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/
YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2K
q2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7
+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0c
uBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2
d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJee
yPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00
648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zG
X4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1
U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM3
MCAwIG9iago4MDUKZW5kb2JqCjIxNSAwIG9iago8PCAvTGVuZ3RoIDM3MSAwIFIgL0Z1bmN0aW9u
VHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9S
YW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKH
VtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9
Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgzt
OWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZK
kzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/
2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfi
Rfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06i
JzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pF
VDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDN
GPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF
476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2
lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+
JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8v
CJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xi
q7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/X
Uq4KZW5kc3RyZWFtCmVuZG9iagozNzEgMCBvYmoKODA1CmVuZG9iagoyMjAgMCBvYmoKPDwgL0xl
bmd0aCAzNzIgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2
NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRl
RGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI6
2VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6
XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWD
bM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51pse
cXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57W
mK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//O
vuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZ
R4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4
ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Y
f0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j
21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZj
upJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEo
FuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+AB
a3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqri
oOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzcyIDAgb2JqCjgwNQpl
bmRvYmoKMTkxIDAgb2JqCjw8IC9MZW5ndGggMzczIDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQ
ZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAg
MSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiI
iIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7
sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlH
qd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk
4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/r
Stee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sL
v5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl
5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyom
o7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOga
OHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+
n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2He
fNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCy
KCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI
9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7y
OOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0K
ZW5kb2JqCjM3MyAwIG9iago4MDUKZW5kb2JqCjIxMiAwIG9iago8PCAvTGVuZ3RoIDM3NCAwIFIg
L0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpb
IDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3Ry
ZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP
/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxO
WEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1p
C9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW4
8bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5
e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnk
PMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcR
mymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb
8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770c
YLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy087
5Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4ab
y0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4I
KQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6
+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/Uvzhf
ISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozNzQgMCBvYmoKODA1CmVuZG9iagoyMjUgMCBv
YmoKPDwgL0xlbmd0aCAzNzUgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9T
aXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO
/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54
yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKM
zQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtv
BkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6
T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uw
wPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4iz
M3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bsp
ysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9
NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3
x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cct
UqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxop
xfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o
8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVh
cQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzc1IDAg
b2JqCjgwNQplbmRvYmoKMjIyIDAgb2JqCjw8IC9MZW5ndGggMzc2IDAgUiAvRnVuY3Rpb25UeXBl
IDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1Jhbmdl
IFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAA
ANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3d
d7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nD
niubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1N
mYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9Y
fwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+X
F4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrs
bEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+
PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujw
DXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L
4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvL
skibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYea
aDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG
6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVM
eVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgpl
bmRzdHJlYW0KZW5kb2JqCjM3NiAwIG9iago4MDUKZW5kb2JqCjIyOCAwIG9iago8PCAvTGVuZ3Ro
IDM3NyAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0g
L0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklD
w0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebO
vBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljB
FnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uV
fPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48
FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7L
MKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmU
MdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI
0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7
HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfx
Kautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZ
PiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huE
Qci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5i
ta+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvb
nG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozNzcgMCBvYmoKODA1CmVuZG9i
agoyMjcgMCBvYmoKPDwgL0xlbmd0aCAzNzggMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNh
bXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAg
MSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvv
gYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKu
p7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZl
aM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9Skj
rEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157X
merWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4s
LuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWq
BHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeK
CcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2C
Pjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nT
dd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqV
N58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEf
SUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nE
Or6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWc
Q3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRv
YmoKMzc4IDAgb2JqCjgwNQplbmRvYmoKMTgyIDAgb2JqCjw8IC9MZW5ndGggMzc5IDAgUiAvRnVu
Y3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAx
IF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0K
eAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9
vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86F
dTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxK
wxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+
ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGF
xeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rk
PFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatU
xBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSx
kRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3
srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3y
CKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvD
dMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqI
AZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+
F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8
gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM3OSAwIG9iago4MDUKZW5kb2JqCjIwOCAwIG9iago8
PCAvTGVuZ3RoIDM4MCAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUg
WyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAv
RmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUl
KO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43
pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZk
bGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32
G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWn
tX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5B
i52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK
+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7
ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXs
vxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2
u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3H
LaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQ
wiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+
AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUB
twKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozODAgMCBvYmoK
ODA1CmVuZG9iagoxODUgMCBvYmoKPDwgL0xlbmd0aCAzODEgMCBSIC9GdW5jdGlvblR5cGUgMCAv
Qml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAw
IDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9r
q4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfe
dyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t1
2CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBD
ykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/Aepe
Nug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+
//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOd
m00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWf
jE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6
FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7
uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss
0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSa
wJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1
AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48
x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0
cmVhbQplbmRvYmoKMzgxIDAgb2JqCjgwNQplbmRvYmoKMTkwIDAgb2JqCjw8IC9MZW5ndGggMzgy
IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9t
YWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+
PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L
0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty
5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwab
tpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883Ub
cWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+
XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg
55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRw
ZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY
8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Q
d4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62n
HSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOE
m+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpg
A6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2
v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwec
r9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM4MiAwIG9iago4MDUKZW5kb2JqCjIx
MyAwIG9iago8PCAvTGVuZ3RoIDM4MyAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxl
IDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0g
L0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjU
OnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOy
u7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL
2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y
6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae
8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98
f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelyt
iqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJ
O/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhN
HLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJ
dnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCX
nsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWN
NOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8
xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVh
NVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagoz
ODMgMCBvYmoKODA1CmVuZG9iagoyMjEgMCBvYmoKPDwgL0xlbmd0aCAzODQgMCBSIC9GdW5jdGlv
blR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAv
UmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXC
h1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3
/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM
7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9Nm
SpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJc
f9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH
4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNO
oic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNK
RVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+Dw
zRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfz
BeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R
9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEp
PiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBf
LwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP1
4qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf
11KuCmVuZHN0cmVhbQplbmRvYmoKMzg0IDAgb2JqCjgwNQplbmRvYmoKMTk3IDAgb2JqCjw8IC9M
ZW5ndGggMzg1IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEz
NjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0
ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHS
OtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/B
ul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKsl
g2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dab
HnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee
1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//
zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlK
GUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx
+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI9
2H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+
Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKm
Y7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzEx
KBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0Cfg
AWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq
4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM4NSAwIG9iago4MDUK
ZW5kb2JqCjIwOSAwIG9iago8PCAvTGVuZ3RoIDM4NiAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRz
UGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAw
IDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiI
iIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7
O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1Z
R6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0
pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v
60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+L
C7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBU
JeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMq
JqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWTo
Gjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7
Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth
3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQ
sigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5A
SPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe
8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFt
CmVuZG9iagozODYgMCBvYmoKODA1CmVuZG9iagoyMDIgMCBvYmoKPDwgL0xlbmd0aCAzODcgMCBS
IC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4K
WyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0
cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7H
z/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+Zc
TlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClN
aQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MV
uPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c
+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq5
5DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZX
EZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvK
m/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9
HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtP
O+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeG
m8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKgu
CCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn
+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84
XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzg3IDAgb2JqCjgwNQplbmRvYmoKMTg4IDAg
b2JqCjw8IC9MZW5ndGggMzg4IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAv
U2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmls
dGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3
jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMu
eMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnS
jM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34Db
bwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886
uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7
sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eI
szNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7
KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqm
PTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5
d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHH
LVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648a
KcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cu
qPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27l
YXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjM4OCAw
IG9iago4MDUKZW5kb2JqCjIzNCAwIG9iago8PCAvTGVuZ3RoIDM4OSAwIFIgL0Z1bmN0aW9uVHlw
ZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5n
ZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQ
AADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi9
3Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWep
w54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGN
TZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTf
WH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/
lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq
7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlF
Pj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro
8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476e
i+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgb
y7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWH
mmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDX
BuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1
THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4K
ZW5kc3RyZWFtCmVuZG9iagozODkgMCBvYmoKODA1CmVuZG9iagoyMjYgMCBvYmoKPDwgL0xlbmd0
aCAzOTAgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBd
IC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVj
b2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJ
Q8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnm
zrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5Y
wRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvr
lXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6u
PBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZe
yzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yp
lDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFb
yNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0Xs
uxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln
8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJj
GT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIb
hEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+
YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob
25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzkwIDAgb2JqCjgwNQplbmRv
YmoKMTkyIDAgb2JqCjw8IC9MZW5ndGggMzkxIDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJT
YW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAw
IDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh7
74GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7C
rqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2W
ZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUp
I6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee
15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+
LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krV
qgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3
ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9
gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ
03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKK
lTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTB
H0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5
xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTV
nEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5k
b2JqCjM5MSAwIG9iago4MDUKZW5kb2JqCjIxNyAwIG9iago8PCAvTGVuZ3RoIDM5MiAwIFIgL0Z1
bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAg
MSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFt
CngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o
/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfO
hXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hs
SsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqF
vrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lx
hcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq
5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymr
VMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHk
sZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/
97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft
8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0ob
w3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiK
iAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORe
PhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu/
/IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozOTIgMCBvYmoKODA1CmVuZG9iagoyMDYgMCBvYmoK
PDwgL0xlbmd0aCAzOTMgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXpl
IFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIg
L0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWV
JSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMe
N6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2
ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT9
9hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rV
p7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+
QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GG
yvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnx
O8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF
7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+cz
Nrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZN
xy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVH
kMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5
fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1
AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKMzkzIDAgb2Jq
CjgwNQplbmRvYmoKMjAwIDAgb2JqCjw8IC9MZW5ndGggMzk0IDAgUiAvRnVuY3Rpb25UeXBlIDAg
L0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsg
MCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAf
a6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z3
3nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniub
ddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxg
Q8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHq
XjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uX
Pv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKD
nZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWF
n4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDo
ehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5W
e7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskib
LNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaE
msCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGF
tQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVe
PMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRz
dHJlYW0KZW5kb2JqCjM5NCAwIG9iago4MDUKZW5kb2JqCjE5NSAwIG9iago8PCAvTGVuZ3RoIDM5
NSAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0Rv
bWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUg
Pj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0ve
S9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvr
cubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMG
m7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1
G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9XntaYrq48FS8z
flxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnV
YOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0
cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ
2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ9
0HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKaut
px0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyT
hJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6
YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+W
Nr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8H
nK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozOTUgMCBvYmoKODA1CmVuZG9iagoy
MDcgMCBvYmoKPDwgL0xlbmd0aCAzOTYgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBs
ZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBd
IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI
1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyELuzuwnsKup7DD
sruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3a
y9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGf
MujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+r+tK157XmerW
nvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/
fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpc
rYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcip
iTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4
TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7T
yXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58w
l57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTF
jTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6f
vMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zl
YTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoK
Mzk2IDAgb2JqCjgwNQplbmRvYmoKMjMxIDAgb2JqCjw8IC9MZW5ndGggMzk3IDAgUiAvRnVuY3Rp
b25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0g
L1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGV
wodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K
9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svmXE5YR86FdTpy
DO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvT
ZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvzFbjxuoW+ufEC
XH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWl
x+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFaj
TqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCj
SkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg
8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn
8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKst
kfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVh
KT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEA
Xy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD
9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0D
n9dSrgplbmRzdHJlYW0KZW5kb2JqCjM5NyAwIG9iago4MDUKZW5kb2JqCjIzMyAwIG9iago8PCAv
TGVuZ3RoIDM5OCAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDggL1NpemUgWyAx
MzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0ZpbHRlciAvRmxh
dGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGxN47+VZUlKO7B
0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7DjLnjI8x43pSvv
wbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ0ozNCrZkbGCr
JYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A228GRP32G/nW
mx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avPOrpPutWntX9X
ntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb+7DA/H5Bi52/
/86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtniLMzcYbK+Gyp
ShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jxuynKyfE7ytvJ
MfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLgapj00cEXsvxqi
Pdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfneXfH5zM2u9rP
/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjxxy1Spk3HLaWy
pmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuPGinF9UeQwiMx
MSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+HLqjxE3l+AdAn
4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu5WFxBfUBtwKy
quKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iagozOTggMCBvYmoKODA1
CmVuZG9iagoyMTggMCBvYmoKPDwgL0xlbmd0aCAzOTkgMCBSIC9GdW5jdGlvblR5cGUgMCAvQml0
c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFuZ2UgWyAwIDEg
MCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1baUAAA0B9rq4iI
iIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34vd13tnfedyEL
uzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7TlnqcOeK5t12Clt
WUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMxjU2ZjGBDykRp
NKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE31h/AepeNug+
r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6v5cXi5c+//iP
iwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0auxsQoOdm00w
VCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5RT49FYWfjE5T
KiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj66PANcOh6FH1k
6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+noviblZ7uy96
uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZIG8uySJss0io7
Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQVh5poNoSawJKG
ELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ1wbqEYW1AXJ+
QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8NUx5VV48x8sD
HvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11KuCmVuZHN0cmVh
bQplbmRvYmoKMzk5IDAgb2JqCjgwNQplbmRvYmoKMTk4IDAgb2JqCjw8IC9MZW5ndGggNDAwIDAg
UiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUgXSAvRG9tYWlu
ClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURlY29kZSA+Pgpz
dHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtlaSUPDS95L0nvu
x8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul155s68G+ty5svm
XE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zOWMEWcwabtpgp
TWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF765V883UbcWvz
FbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piurjwVLzN+XF1+
XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7mXsswqdVg55La
ueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeMqZQx1TRwZjpG
VxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+ImxW8jR2wnY8dFb
ypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F7LscpD3Qd4nv
vRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZZ/Epq62nHSzL
Tzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qSYxk+LJOEm+k3
hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbiG4RByLpgA6yo
LggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5PmK1r5Y2v9qH
5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDqG9ucbwecr9S/
OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjQwMCAwIG9iago4MDUKZW5kb2JqCjE5MyAw
IG9iago8PCAvTGVuZ3RoIDQwMSAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVyU2FtcGxlIDgg
L1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEgMCAxIF0gL0Zp
bHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiIe++BiIjUOnGx
N47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Cewq6nsMOyu7Dj
LnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6ndlmVozdrL2qzZ
0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1KSOsQZ8y6N+A
228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rXnteZ6tae8avP
OrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+ZPiwu4H98f2Bb
+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK1aoEelytiqtn
iLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOwd4oJyKmJO/jx
uynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4PYI+PHhNHLga
pj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z2dN13tPJdnfn
eXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzSipU3nzCXnsjx
xy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigkwR9JRMWNNOuP
GinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL+cQ6vp+8xl+H
LqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk1ZxDfOVhNVNu
5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVuZG9iago0MDEg
MCBvYmoKODA1CmVuZG9iagoxODEgMCBvYmoKPDwgL0xlbmd0aCA0MDIgMCBSIC9GdW5jdGlvblR5
cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAwIDEgXSAvUmFu
Z2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVhbQp4AZXCh1ba
UAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P6P29D8r3/T34
vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhHzoV1OnIM7Tln
qcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvYbErDG9NmSpMx
jU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6hb658QJcf9lE
31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+XvpcYXF5aXH4kX6
v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL6uQ8VqNOoic0
auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZspq1TEEKNKRVQ5
RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER5LGRG+DwzRj6
6PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCxv/eyuOfzBeO+
noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn7fIIqy2R9pZI
G8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tKG8N0xWEpPiQV
h5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkIiogBkQBfLwiQ
1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjkXj4XWMP14qu8
NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyErv/yC/QOf11Ku
CmVuZHN0cmVhbQplbmRvYmoKNDAyIDAgb2JqCjgwNQplbmRvYmoKMTk2IDAgb2JqCjw8IC9MZW5n
dGggNDAzIDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6ZSBbIDEzNjUg
XSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVyIC9GbGF0ZURl
Y29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5VlSUo7sHSOtla
SUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjzHjelK+/Bul15
5s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0KtmRsYKslg2zO
WMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE/fYb+dabHnF7
65V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+61ae1f1ee1piu
rjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8fkGLnb//zr7m
XsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNxhsr4bKlKGUeM
qZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ8TvK28kx+Imx
W8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRwRey/GqI92H9F
7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fnMza72s/+Y9tZ
Z/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKmTcctpbKmY7qS
Yxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1R5DCIzExKBbi
G4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPETeX4B0CfgAWt5
PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF9QG3ArKq4qDq
G9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjQwMyAwIG9iago4MDUKZW5k
b2JqCjE4MyAwIG9iago8PCAvTGVuZ3RoIDQwNCAwIFIgL0Z1bmN0aW9uVHlwZSAwIC9CaXRzUGVy
U2FtcGxlIDggL1NpemUgWyAxMzY1IF0gL0RvbWFpbgpbIDAgMSBdIC9SYW5nZSBbIDAgMSAwIDEg
MCAxIF0gL0ZpbHRlciAvRmxhdGVEZWNvZGUgPj4Kc3RyZWFtCngBlcKHVtpQAADQH2uriIiIiIiI
e++BiIjUOnGxN47+VZUlKO7B0jrZWklDw0veS9J77sfP/Q/o/b0Pyvf9Pfi93Xe2d953IQu7O7Ce
wq6nsMOyu7DjLnjI8x43pSvvwbpdeebOvBvrcubL5lxOWEfOhXU6cgztOWepw54rm3XYKW1ZR6nd
lmVozdrL2qzZ0ozNCrZkbGCrJYNszljBFnMGm7aYKU1pC9hsSsMb02ZKkzGNTZmMYEPKRGk0pOD1
KSOsQZ8y6N+A228GRP32G/nWmx5xe+uVfPN1G3Fr8xW48bqFvrnxAlx/2UTfWH8B6l426D6v60rX
nteZ6tae8avPOrpPutWntX9XntaYrq48FS8zflxdflz5e+lxhcXlpcfiRfq/lxeLlz7/+I+LC7+Z
Piwu4H98f2Bb+7DA/H5Bi52//86+5l7LMKnVYOeS2rnkPMvq5DxWo06iJzRq7GxCg52bTTBUJeZK
1aoEelytiqtniLMzcYbK+GypShlHjKmUMdU0cGY6RlcRmymrVMQQo0pFVDlFPj0VhZ+MTlMqJqOw
d4oJyKmJO/jxuynKyfE7ytvJMfiJsVvI0dsJ2PHRW8qb8RHksZEb4PDNGPro8A1w6HoUfWToGjh4
PYI+PHhNHLgapj00cEXsvxqiPdh/Rey7HKQ90HeJ770cYLG/97K45/MF476ei+JuVnu7L3q7Pp+z
2dN13tPJdnfneXfH5zM2u9rP/mPbWWfxKautpx0sy0875Kft8girLZH2lkgby7JImyzSKjth3nzS
ipU3nzCXnsjxxy1Spk3HLaWypmO6kmMZPiyThJvpN4aby0obw3TFYSk+JBWHmmg2hJrAkoYQsigk
wR9JRMWNNOuPGinF9UeQwiMxMSgW4huEQci6YAOsqC4IKQiKiAGRAF8vCJDXBuoRhbUBcn5ASPQL
+cQ6vp+8xl+HLqjxE3l+AdAn4AFreT5ita+WNr/ah+f6+ORePhdYw/Xiq7w1THlVXjzHywMe8jjk
1ZxDfOVhNVNu5WFxBfUBtwKyquKg6hvbnG8HnK/UvzhfISu//IL9A5/XUq4KZW5kc3RyZWFtCmVu
ZG9iago0MDQgMCBvYmoKODA1CmVuZG9iagoyMTQgMCBvYmoKPDwgL0xlbmd0aCA0MDUgMCBSIC9G
dW5jdGlvblR5cGUgMCAvQml0c1BlclNhbXBsZSA4IC9TaXplIFsgMTM2NSBdIC9Eb21haW4KWyAw
IDEgXSAvUmFuZ2UgWyAwIDEgMCAxIDAgMSBdIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+CnN0cmVh
bQp4AZXCh1baUAAA0B9rq4iIiIiIiHvvgYiI1DpxsTeO/lWVJSjuwdI62VpJQ8NL3kvSe+7Hz/0P
6P29D8r3/T34vd13tnfedyELuzuwnsKup7DDsruw4y54yPMeN6Ur78G6XXnmzrwb63Lmy+ZcTlhH
zoV1OnIM7TlnqcOeK5t12CltWUep3ZZlaM3ay9qs2dKMzQq2ZGxgqyWDbM5YwRZzBpu2mClNaQvY
bErDG9NmSpMxjU2ZjGBDykRpNKTg9SkjrEGfMujfgNtvBkT99hv51psecXvrlXzzdRtxa/MVuPG6
hb658QJcf9lE31h/AepeNug+r+tK157XmerWnvGrzzq6T7rVp7V/V57WmK6uPBUvM35cXX5c+Xvp
cYXF5aXH4kX6v5cXi5c+//iPiwu/mT4sLuB/fH9gW/uwwPx+QYudv//OvuZeyzCp1WDnktq55DzL
6uQ8VqNOoic0auxsQoOdm00wVCXmStWqBHpcrYqrZ4izM3GGyvhsqUoZR4yplDHVNHBmOkZXEZsp
q1TEEKNKRVQ5RT49FYWfjE5TKiajsHeKCcipiTv48bspysnxO8rbyTH4ibFbyNHbCdjx0VvKm/ER
5LGRG+DwzRj66PANcOh6FH1k6Bo4eD2CPjx4TRy4GqY9NHBF7L8aoj3Yf0XsuxykPdB3ie+9HGCx
v/eyuOfzBeO+noviblZ7uy96uz6fs9nTdd7TyXZ353l3x+czNrvaz/5j21ln8SmrracdLMtPO+Sn
7fIIqy2R9pZIG8uySJss0io7Yd580oqVN58wl57I8cctUqZNxy2lsqZjupJjGT4sk4Sb6TeGm8tK
G8N0xWEpPiQVh5poNoSawJKGELIoJMEfSUTFjTTrjxopxfVHkMIjMTEoFuIbhEHIumADrKguCCkI
iogBkQBfLwiQ1wbqEYW1AXJ+QEj0C/nEOr6fvMZfhy6o8RN5fgHQJ+ABa3k+YrWvlja/2ofn+vjk
Xj4XWMP14qu8NUx5VV48x8sDHvI45NWcQ3zlYTVTbuVhcQX1AbcCsqrioOob25xvB5yv1L84XyEr
v/yC/QOf11KuCmVuZHN0cmVhbQplbmRvYmoKNDA1IDAgb2JqCjgwNQplbmRvYmoKMTk0IDAgb2Jq
Cjw8IC9MZW5ndGggNDA2IDAgUiAvRnVuY3Rpb25UeXBlIDAgL0JpdHNQZXJTYW1wbGUgOCAvU2l6
ZSBbIDEzNjUgXSAvRG9tYWluClsgMCAxIF0gL1JhbmdlIFsgMCAxIDAgMSAwIDEgXSAvRmlsdGVy
IC9GbGF0ZURlY29kZSA+PgpzdHJlYW0KeAGVwodW2lAAANAfa6uIiIiIiIh774GIiNQ6cbE3jv5V
lSUo7sHSOtlaSUPDS95L0nvux8/9D+j9vQ/K9/09+L3dd7Z33nchC7s7sJ7Crqeww7K7sOMueMjz
HjelK+/Bul155s68G+ty5svmXE5YR86FdTpyDO05Z6nDniubddgpbVlHqd2WZWjN2svarNnSjM0K
tmRsYKslg2zOWMEWcwabtpgpTWkL2GxKwxvTZkqTMY1NmYxgQ8pEaTSk4PUpI6xBnzLo34DbbwZE
/fYb+dabHnF765V883UbcWvzFbjxuoW+ufECXH/ZRN9YfwHqXjboPq/rStee15nq1p7xq886uk+6
1ae1f1ee1piurjwVLzN+XF1+XPl76XGFxeWlx+JF+r+XF4uXPv/4j4sLv5k+LC7gf3x/YFv7sMD8
fkGLnb//zr7mXsswqdVg55LaueQ8y+rkPFajTqInNGrsbEKDnZtNMFQl5krVqgR6XK2Kq2eIszNx
hsr4bKlKGUeMqZQx1TRwZjpGVxGbKatUxBCjSkVUOUU+PRWFn4xOUyomo7B3ignIqYk7+PG7KcrJ
8TvK28kx+ImxW8jR2wnY8dFbypvxEeSxkRvg8M0Y+ujwDXDoehR9ZOgaOHg9gj48eE0cuBqmPTRw
Rey/GqI92H9F7LscpD3Qd4nvvRxgsb/3srjn8wXjvp6L4m5We7svers+n7PZ03Xe08l2d+d5d8fn
Mza72s/+Y9tZZ/Epq62nHSzLTzvkp+3yCKstkfaWSBvLskibLNIqO2HefNKKlTefMJeeyPHHLVKm
TcctpbKmY7qSYxk+LJOEm+k3hpvLShvDdMVhKT4kFYeaaDaEmsCShhCyKCTBH0lExY00648aKcX1
R5DCIzExKBbiG4RByLpgA6yoLggpCIqIAZEAXy8IkNcG6hGFtQFyfkBI9Av5xDq+n7zGX4cuqPET
eX4B0CfgAWt5PmK1r5Y2v9qH5/r45F4+F1jD9eKrvDVMeVVePMfLAx7yOOTVnEN85WE1U27lYXEF
9QG3ArKq4qDqG9ucbwecr9S/OF8hK7/8gv0Dn9dSrgplbmRzdHJlYW0KZW5kb2JqCjQwNiAwIG9i
ago4MDUKZW5kb2JqCjMgMCBvYmoKPDwgL1R5cGUgL1BhZ2VzIC9NZWRpYUJveCBbMCAwIDc5MiA2
MTJdIC9Db3VudCAxIC9LaWRzIFsgMiAwIFIgXSA+PgplbmRvYmoKNDA3IDAgb2JqCjw8IC9UeXBl
IC9DYXRhbG9nIC9QYWdlcyAzIDAgUiAvVmVyc2lvbiAvMS40ID4+CmVuZG9iago0MDggMCBvYmoK
PDwgL0xlbmd0aCA0MDkgMCBSIC9MZW5ndGgxIDI0MTYwIC9GaWx0ZXIgL0ZsYXRlRGVjb2RlID4+
CnN0cmVhbQp4AdV8d3hcxd313L3be1dZSbvSSivJq96LLa16ty1La0u2ZEuW5N57t7CpMoQOcULA
EGIgBrxaGywbCE7ihARiIISS0AIJJJSYkpBQJX1n7uzI5Q15v+f5/skn6+w5U3fmN33ulTdt2DxE
dGSYiCRnYHX/OiL9FEwH9Qxs2eRh7pRlhCjilqxbupq5p11OiCZ26artS5i74D1C0ruWDfUPMjf5
Bly0DB7MLRSAk5et3rSNufMPge9YtXYgEl7wXbhnr+7fFvl+8jrcnjX9q4fA+FkYwIdn3YahSLjQ
hezMwhfwVf3pZvn1tYdumLbCFQPn9SX4kH6MhAgQqYKHmMnPiYrIwNkEOVpuEPYROUJpuOLOses+
f8ayyDT9nyRGLaV87MNdv6HiqavuP/D1V+MHNH9TPQqnBjmwH6RT3Tn+KiHaQ19/9dUhzd+knCKB
EqWGNaJnTHb5cU200Ayxn4t9XFzGxTAXe7nYw8VuLnZxsZOLHVxs52IbF1u52MLFZi42cbGRi/Vc
rONiLRdruFjNxSouVnKxgovlXCzjYikXS7gY4mKQiwEuFnPRz0UfF4u4WMhFLxc9XCzgYj4X3Vx0
cTGPi7lcBLno5KKDizlctHMxm4tZXMzkoo2LVi5auGjmoomLRi4auKjnoo6LWi5quKjmooqLABeV
XFRwMYOL6VyUc1HGRSkXJVwUc1HERSEXBVzkc5HHRS4XOVxkc5HFRSYXGVz4uZjGRToXaVykcuHj
IoWLZC68XCRxkciFhws3FwlcxHMRx4WLi1guYriI5iKKCycXDi7sXNi4sHJh4cLMhYkLIxcGLvRc
6LjQcqHhQs2FigslFwou5FyIXMi4ELggESFMcjHBxTgX33DxNRdfcfElF19w8TkX/+Lin1x8xsU/
uPg7F59y8QkXH3PxERfnuPgbFx9y8QEX73PxHhd/5eIvXLzLxTtc/JmLP3HxNhdvcfFHLt7k4g0u
XufiNS5e5eIPXPyei1e4eJmLl7h4kYvfcfECF7/l4nkunuPiWS7OcvEbLp7h4mkufs3Fr7h4iotf
cvELLs5w8XMufsbFT7k4zcWTXPyEiye4eJyLx7g4xcVJLsa4OMHFo1w8wsVxLo5xEeZilIsQF0e5
eJiLh7h4kIsjXPyYiwe4uJ+L+7g4zMWPuLiXix9ycQ8Xd3NxiIu7uLiTix9wcQcX3+fie1wc5OK7
XNzOxW1c3MrFLVzczMVNXNzIxQ1cXM/Fd7i4jotruTjAxQgX13BxNRdXcXElF1dwcTkX+7nYx8Vl
XAxzsZeLPVzs5mIXFzu52MHFdi62cbGViy1cbOZiExcbudjAxXou1nGxlos1XKzmYhUXK7lYwcVy
LpZxsZSLJVwMcTHIxQAXi7no56KPi0VcLOSil4seLhZwMZ+Lbi66uJjHxVwuglx0ctHBxRwuZnMx
i4uZXLRy0cJFMxdNXDRy0cBFPRd1XNRyUXOM7paxaw4nVLixZw4nOED7mOuycEIZXMPMtZfRnnCC
Hp67mWsXo52MdjDaHo6vQpRt4fga0FZGWxhtZmGbmGsjow3Mc304vhoJ1jFay2gNi7Ka0SpGK8Nx
dYi5gtFyRssYLWW0JBxXiyhDzDXIaIDRYkb9jPoYLWK0kKXrZa4eRgsYzWfUzaiL0TxGcxkFGXUy
6mA0h1E7o9mMZjGayaiNUSujFkbNYVcT6tDEqDHsaoargVF92NUCV13Y1QqqZVTDqJqFVbF0AUaV
LF0FoxmMprOY5YzKWPJSRiWMihkVMSpkmRUwyme55DHKZZTDMstmlMXSZTLKYORnNI1ROqM0Rqks
ax+jFJZnMiMvoySWdSIjD0vnZpTAKJ5RHCMXo9hw7EwYK4ZRdDh2FlxRjJzM08HIzjxtjKyMLCzM
zMjEPI2MDIz0LEzHSMtIw8LUjFSMlOGY2fh2RTimHSRnJDJPGXMJjIhEwiSjCSmKMM5c3zD6mtFX
LOxL5vqC0eeM/sXon+HoTveY8Fk4ugP0D+b6O6NPGX3Cwj5mro8YnWP0Nxb2IaMPmOf7jN5j9FdG
f2FR3mWud5jrz8z1J0ZvM3qLhf2R0ZvM8w1GrzN6jdGrLMofmOv3jF4JR81DVV4OR80FvcToReb5
O0YvMPoto+dZlOcYPcs8zzL6DaNnGD3Novya0a+Y51OMfsnoF4zOMPo5i/kz5vopo9OMnmRhP2H0
BPN8nNFjjE4xOslojMU8wVyPMnqE0XFGx8LOSlQ6HHYuAI0yCjE6yuhhRg8xepDREUY/Djsx6wsP
sFzuZ3QfCzvM6EeM7mX0Q0b3MLqb0SFGd7HM7mS5/IDRHSzs+4y+x+ggo++yBLcz122MbmV0Cwu7
meVyE6MbWdgNjK5n9B1G1zG6lsU8wFwjjK5hdDWjqxhdGXb0o+5XhB2LQZcz2h92LIFrH6PLwo4g
XMNhBxYbYW/YUQTaw2g3S76LpdvJaEfYMYgo21nybYy2MtrCaDOjTYw2sqw3sOTrGa0LOwaQy1qW
2RoWczWjVYxWMlrBaDlLt4zRUlayJSz5EKNBFnOA0WJG/Yz6GC1itJBVupeVrIfRAlbp+SzrbvZF
XYzmseLOZV8UZLl0MupgNIdRe9geQMVmh+3UrLPCdjpgZ4bt+0FtYXsmqJVFaWHUHLZjIyE0MVcj
owbmWR+270FYXdh+Fag2bN8Lqgnbh0HVYWs9qIpRgFElo4qwFfsCYQZzTQ9buuEqZ1QWttBxVMqo
JGxpgKs4bOkCFYUt80GFLKyAUX7YkgHPPBYzN2yhFcsJW+iElM0oiyXPZN+QwcjPMpvGKJ1llsYo
lZGPUUrYQq2UzMjL8kxieSayzDwsFzejBJYunlEcIxejWEYxYXMv8owOmxeCosLmRSAnIwcjOyMb
IytLYGEJzMzTxMjIyMBIz2LqWEwt89QwUjNSMVKymAoWU848RUYyRgIjEpg0LXZTTJgG3OOmQfc3
0F8DXwFfwu8L+H0O/Av4J/AZ/P8B/B1hn8L9CfAx8BFwDv5/Az5E2Adwvw+8B/wV+Itxqftd4zL3
O8CfgT8Bb8PvLfAfgTeBN+B+Hfwa8CrwB+D3hpXuVwy57pfBLxlWuV80+Ny/A16A/q3B734eeA54
FuFn4fcbw2r3M9BPQ/8a+leGFe6nDMvdvzQsc//CsNR9Bml/jvx+BvwUCEyexueTwE+AJ/Tr3Y/r
N7gf0290n9Jvcp8ExoAT8H8UeARhxxF2DH5hYBQIAUd1290P63a4H9Ltcj+o2+0+otvj/jHwAHA/
cB9wGPiRLtN9L/iHwD1Iczf4kG6l+y7oO6F/ANwB/X3k9T3kdRB5fRd+twO3AbcCtwA3Azch3Y3I
7wbtTPf12lnu72iXuq/T/sh9rfY+9xViivtyscS9Xyhx7wsOBy87MhzcG9wd3HNkd1C3W9Dtdu1u
2b1z95Hdr+0OWJXaXcEdwZ1HdgS3B7cGtx3ZGjwlu5IskV0RmB7ccmRzUL7ZvnnTZvGzzcKRzULt
ZiFnsyAjm82bPZtF/abghuDGIxuCZMPsDcMbQhvk5aENb22QkQ2Cdmzy9LENroR6cGDXBoO5fn1w
bXDdkbXBNUtWB1eggMtLlgaXHVkaXFIyGBw6MhgcKFkc7C/pCy4q6Q0uPNIb7CmZH1xwZH6wu6Qr
OA/x55Z0BoNHOoMdJe3BOUfag7NKZgZnwr+tpCXYeqQl2FzSGGw60hhsKKkP1qHyJM4c54kTzbQA
M+NQEuISqnNcAddbrk9ccuIKuU67RKsp1h0rSzfFCDWzYoS1MXtjro8RTdHPRcsC0ekZ9aao56L+
GPVxlNwWiErPqidOs9PjFB20bs62Tlq3Y87KWsa5hVJd25xeX73JIZgcboeszu0QiOUtyycW0fGk
+TmzzGQSTKZJkyxgQnST0W2U0Y9Joxgw5hbXmwxug4x+TBpEZ8AAH1r4VP3sznqTzq2TBSt1s3Sy
gK6ypj6gy8ypJ6LgEfDkxwwS1bQ0gsNdPyaQY05BIYwJN4x2dvj9LWNqMqclpJ69ICRcHUrpoJ+B
9vkh5dUhEpy/oGtUEL7TPSrIajpD9pb2+cx9xXXXker4llB8R1foUHx3S2gYIkDFJASJH3WS6m7/
wo2bN/r9mxbiY+HGTX7pFy5hM3XhBwH43bgJbvoPBDehId/+w6Ih3qKN+JGyYbl/e5L/D0KE/w/K
+F9exFGCLtpVNSm7nAzK9gP7gMuAYWAvsAfYDewCdgI7gO3ANmArsAXYDGwCNgLrgXXAWmANsBpY
BawEVgDLgWXAUmAJMAQMAgPAYqAf6AMWAQuBXqAHWADMB7qBLmAeMBcIAp1ABzAHaAdmA7OAmUAb
0Aq0AM1AE9AINAD1QB1QC9QA1UAVEAAqgQpgBjAdKAfKgFKgBCgGioBCoADIB/KAXCAHyAaygEwg
A/AD04B0IA1IBXxACpAMeIEkIBHwAG4gAYgH4gAXEAvEANFAFOAEHIAdsAFWwAKYARNgBAyAHtAB
WkADqAEVoAQUgLxqEp8iIAMEgJBBAX7CBDAOfAN8DXwFfAl8AXwO/Av4J/AZ8A/g78CnwCfAx8BH
wDngb8CHwAfA+8B7wF+BvwDvAu8Afwb+BLwNvAX8EXgTeAN4HXgNeBX4A/B74BXgZeAl4EXgd8AL
wG+B54HngGeBs8BvgGeAp4FfA78CngJ+CfwCOAP8HPgZ8FPgNPAk8BPgCeBx4DHgFHASGANOAI8C
jwDHgWNAGBgFQsBR4GHgIeBB4AjwY+AB4H7gPuAw8CPgXuCHwD3A3cAh4C7gTuAHwB3A94HvAQeB
7wK3A7cBtwK3ADcDNwE3AjcA1wPfAa4DrgUOACPANcDVwFXAlcAVZLBqWLgcaj+wD7gMGAb2AnuA
3cAuYCewA9gObAO2AluAzcAmYCOwAVgPrAPWAmuA1cAqYCWwAlgOLAOWAkuAIWAQGAAWA/1AH7AI
WAj0Aj3AAmA+0A10AfOAuUAQ6AQ6gDnAbGAWMBNoBVqAZqAJaAQagHqgDqgFasjgf/k0/d9evO7/
9gL+l5cvetFC+sYQIRM3X/iSEJlNVpCNZBj/riTXkZvJk+Q1spjshzpIDpHD5AESIj8lvyavXJTq
/9ExsV2xmujFE0RJbIRMfjV5buIwMKYwXuBzM1w2uee8z6R58qNL/D6auHnSPDGmtBKtlNYgewG5
/UMYn/wK66uSGCaLqFt2FbRJ+qZPVXdOHJ2476IKzCbtZD5ZQHpIL+kj/aj/IFlGlsMyK8kqspqs
kVxrELYUeglcixALc4mkz8daS9aRtWQD2UQ2ky34tw56Y8RFw9ZL7s1kK/5tI9vJDrKT7CK7I59b
JZ9dCNkh+W5DyB6yFy1zGdknKc7MZz+5nFyBVruKXE2uQYt9u+uaqVgj5AC5Fu38HXI9+TZ93UUh
N5AbyI3kJvSHW8it5DbyXfSL75M7LvG9XfL/HrmT3IU+Q1PcCp+7JHUbuZ08Tn5JHiEPk6PkUcmW
A7Atswi3yxLJ0utgg12o8/4LSsysuXXKWntgDVrvkUi9t8F++y5IsSViR2q9/YhJrTMSaQeay+6I
D7fEDagZ0+frSW1E63D9RfXkKf43X1pjaqc7YC9uGWqz2+D3vf/he2GMC/Vt5AcYgXfjk1qVqnug
mbpL0hf63zkV95AU9kNyL/kR2uI+QhVn5nMYfveR+zG2f0yOkAfx77y+ULHQh8lDUsuFyCgJk2Pk
OFryUXKCjEn+/ynsKOaOS9Mci+QVnsrlJDlFHkMP+Qk5jZnmZ/jHfZ6A35MR3zNSLOb+Gd6lPCPF
oqE/Q996CjPU0+QZ8hvyHPkFXM9Kn7+C63nyAvkdeUUwQP2WvI/PcfK84h1iJFV48fIUWuMOshAv
dzYMLlrY27NgfndXsLNjTvvsWTPbWluamxob6utqa6qrApUVM6aXl5WWFBcVZmdlZqT5UpK9Se5o
u8VsMui0GrVKqZCL2Nlm1Hnr+zwhX19I7vM2NmZSt7cfHv0XePSFPPCqvzhOyEPT9SPoopgBxFxy
ScwAixmYiimYPdPJ9MwMT53XEzpb6/WMCfPbu6Cvq/V2e0LnJN0mablPchjgSExECk9d9LJaT0jo
89SF6rcsG6nrq83MEEZ12hpvzZA2M4OManWQOqhQmnfdqJBWIUhCllZXNiojagP92pCYUtc/GJrd
3lVX60pM7Jb8SI2UV0hZE1JJeXmWh1BmcsAzmnF65NoxM1nc59cPegf7e7pCYj8SjYh1IyNXhSz+
ULq3NpS+451oGHAolOGtrQv5vShYy5ypLxBCihSz1zPyT4LCe8/9DaW+wKc/4qNMMf+T0EBaxSkz
hYR+rgnKhhKifomJtCwHxgJkMRyh4fYu5vaQxa4wCWT7u0OyPhpymoc4gjRkmIdMJe/zwrJ13rq+
yO+WZdGh4cWezAy0rPSbEpKnINwTEn19iweWUe4fGvHWooawJenEpU0tRKA/Ysy60ZxsxO/vQyWW
UzO0d4WyvetCdm81szY8kElK3fKOLikJ860L2WtCpG8gkiqUXYe06CJ1I7RhaAFpXt72rpMkf/Kt
0QKP61g+KSDdtBwhZw0axVc30jW4JOTucw2ify7xdLkSQ4FumK/b2zXUTVvJaw6lv4Wvww8aUEqF
ul0Sm0dGtUOqFLWnS+YSu2lrwcNTjw9v9XQEmENK5qQtWj3d0yW4CI+Gb4nEoOqifOAQU2oakRiM
pDWNrkR0bunnPxTJxSqAYoTUU2WSoxCK82Vi3/OtRWOxaYHSPXVDtRcU8KJM4ZAKGMnt35dTRm0R
MQaKoKbN2UjrkJkhg/YgWB2SoZ6SF23FaE+IzPZ0eYe83V70ocDsLto41NZS+7Z0eOnFoNTakV7S
eZGLhZewsBBJbOns4g56ZxOq90vtSptVcjdI7iln4yXBTTzYM6L2tnSM0C/3RjIkHowgNI7S19R/
oMRagMFaj4nSW9/v9Zg99SP9Y5PDi0dGA4GRdXV9y8owDEa8TYMj3o6u6WhLadzvdu2gX20lLUJL
Z3VmBuae6lGvcHX7aEC4umN+10kzIZ6rO7vCMlyK9lV3jyYjrOukh5CA5CujvtSTRvFQB81pDhxq
Kb7rZICQYSlULnlI7gHcy0p+LBL8BDIwJmN+Zh5PBj858wtIft34wQiLXoYmwDxc5xmkzbOre9lI
XzcdXMSJpsSvEBK8FSQk81bgKlepD2m9Q9Uhnbea+ldS/0rmr6T+Km91SHAKMM4Y5qSRPi/mKXS5
LlyRd6N3mGnvl6V4xiYnO7sSz7rOdSdiSPQA87tCGj/WAUVKM+I1UPTBuyE0PNBPy0GCGOp0ZDYN
dGMs8AwRpSmkQQ6aSA6IUS+lod0RiQbQNmhAKf0wHKHh7lC3n35p13JaIo/HHCKN3jI0O8tT4aNf
lN09YvXm0Y6NqCFtylWUNCgbwSW15OOCE1+GCZfWSKVHyQe8CBro86AF5GSgA12dzaVa2m7wGcKU
KPcNSdC6IoGEVktM0Rm0IU0WMsQv1bosZIhfVTeMQisvua6KRMB3m0M6lMh3gSkjCWAdBDXRsuD3
KhSeRv0pzaZ9jMzxbsPUSAstfZUKwSFDSlM/Jn+WXgcfbwlPjLzUKdSL5nGG+apozfWwu5jSOTZ5
n3c7nQH4T2aGly4OtGMS10l0bNI9cqlHaIE/M0N9qa9B8h4ZURv+fQJmL7VhimkunjqsNYTI6Z+x
PEeI+B55UHyIPCiTA9cRlfgXYhJfIj3yAnIQ6BO/Jr3ycyRFPEMKqR/uzg4qB6Wwg/ISMl/2NDko
JpJ22cMkUb45ggJyi3gXSUJcgtvdOnzXSmAO0Ag8DGwAlgI5wBBAwwcAGmcODMH+hoYQPc54M+FO
JEkkHr4JxE08kstLkokCf31jJrHER6Kw90vBX9JY8TdHNqIm0eg9MqQVcULUEgfysRA7MSAngj33
3UK8cKXwW1mR7Adiq/iufJciXvGMckw1XbVX3af+VLNX84X2J7oyXb3ucX2rflT/kv4Lw2Hjb0x7
zUXmly1PW6+31dpabR/a/mF/EGUgExvFF3BSFVGaUtKG8i54nBhwpeQkZcIjjzhqa9WZqp/gukhG
PLhwUhNBqAmY5DLDidjYSu+JQuV1oqVpTMg8Xqm6DlepleNvjj+bPf7mOWtp9jkh+42333zb/Omz
ltLs/LdffDs3R7AkWiTYjTKVyq70JmXJClN9Rfn5eRWywgKfN8kok/wKioorxPy8BJmImMynQkbd
gvjCN/PFWeNK2R5v5dx8RUKsyW5QKmRx0dbM6SnmjgUp07PiVaJKKSrUqrTi6qSWVXVJr6os8Q5n
vFWttsY7HfEW1fhrCuNXf1cYv66Rr/r6FlFZ3lOZLH5Xq5bJlcqxhOiYaeWJTXNNNrNcZzNbnGqV
1aJPq+0Zv9IRR/OIczhYXuNtaNUH0Q93wYIZZMtobOrY5HvHzEIb+JNjpggbJP7XMb3E7x3TUZZZ
AhqNzWPzoOFjxwR1wDDsE077hOd9gs+njBkT9GFDeypoVNlJKs9VUov2rt8Ao2ZbS0uzs81vS/c7
ebk5KdREiUm+QktBUX4ibOSQPCyXSHGXXGtQj98clZ4eJVuiNqgVCnxMKIWw2qCRyzXQM2WC2qCV
N1hdVrU7Vb4v1a22uuxWl0U9sUJjjrNZY82qiVy1xUX7+IOTX4mdqHcq6RlV2SL1Bkv1lhj1Bkv1
lsJRbxvq/YghniTEq1C1YzZbjHJMSDuW1B4TJJVSHWkFz1hKp2on/I/K8B7Bqyt2omKqCVhPhcJL
OqC2e2Kjk+xqVLVe8j1ji0MtGlVml8PmsmjG31UZVAoFPuQP01rGR2okdCnsGHGzT1RGzYo6GiWS
SL3AUr0kRr3AUr2kcNSLnMJTCO3k6RMOoU1rnqOgtRGy/awWuTm9UhvRzm4pYP3YIXSp7YkxtIwa
R2JUTKJdHavW0yLp1fJXuaKlUk1+JLyDUqURbIoJ617/V8WJR3EsQlu80TtH85iQh6klWsgaVczF
IH3xHEp3vniSjZOylIWRwkmj8XxJ34mrXTsnrjgrSadSyES1Tq2O8Wa5k3I8ZlYFm0aobxuen6sx
WfR6S4zViRFmsposWe1V4p20PnLUBzUxoce8gh6TRIZORAdgxWgLKnL6OLWnMmJosGRoiREAlgwt
hcPQSmpoy+TpRxBmUVpp54lv10udJw8G/1QaFL/wm8/4MduwrjPVXxJpA9Aq0pEhviJ1+Vt4K0zc
woeEeLk0IKQe8/WdvCnki9WWOJuNDXwsDaRn8pxYKT5N8rHohQIeU7W7Orta1GmiCvQY6AVmFLAg
GiUuMJvMQmvBmPB5AIMl1UQEPTFjaiBltKqICn7vGGJLjASUj9M0ZWMydcBuifoFKTAXyMpPFwik
QCgoyKqaNia4Aqbnk4SkJHn8B1nNM17Xt8lJNp8lzlmkuWJhL8aS1APP+Bf2lkZmjLzS3JyF6I9K
TL4+X2Eh5YhZ8gsLsjDZTk24cjrhOlTUx2F35ucVFYuV5jhXrNtYfmN7w8b2zIpN9y/f5cydWTqj
vylXr9Zr5CpX9dwlBf1Xd/ruva52sNrdPbtq7YxovV6p1OvnV9an1C+pal3XnFJfMLvQFe+NV5tj
TDHxsd54W0ZwT+eZqMzK9PqO6lpY9yCs+5JiPZlGZpArHsFg0iYWRboC+BNqL7A0l1K3ZK+iMeGL
gMvht8Kofg9i+Kn9/dGYj/3U4v4xmTagIQ5tUWGiXJEzJige9TW76s2tpZCjijY6zdJJKKpUyH6R
DV02y1Kb9UYGiSxVml4vGssWtlapIuZTWZywVoVMfCl/4IZef1N9fSrmUYc9zqpU2TzRMR6rOq2l
sTFt8YF5aQ87CuYGPBWButTaXTUVXcUxwl83P3Z5vcVXlr4GXU8ux/hRlKjZIFKPv5te4jXP3B/a
XLdvcIZ1WnXexMGOedMHdsJifbDYHbjF9mEdPxBwV5YLOlcp7YWlWtij1AwrlFIrlFKjlD6GZ5qE
ZE++RS2ZHRl8YGnwSYxEkj9iZ1PDaW2J9brSVJfciO6nCEc3o0vLjxnbFK105pbMhkmFmS1iPclu
U1PfhV0tzxk1Nb+IPmndd9gTsMJXyIrFO1SWODtdahsOLhi4dl5a3uIbF83aH1DZ3dR2msM1u2sr
YSlYripxRqA+NYYbamvb3Lb9o4s3PXZ5Q12NTMen+PE62GjxrkDtviHYrCaXjt5eWOsgRq8ftwsP
B6ZlF1UWrS0SbbTX2Dywks2WmGGGCTKotTKoGTOkcZwxJnz5SK3/Xr/MD2M9QntVgXyMmRH8ER3Q
khvJwGwgy6n9EhMznhqW3yCXnZYLz8sFuTwu+3Vfc/QHfcZ1RplR80Ec+t/4i70XrvSSMfPe8PdK
AoPaj1kNHVHpTYwYSxqhduP5MUxHbGqRZFCVeDA1ZjycUL+uPTDYlK1X6ZSiTFTpiuauD6y9b0PZ
9PWHBlbc2pd5WNy+dUZPRZJMJktNbNk2N8sR61AZY6wGm0mvi4m2VewY27Hp5GV1tRu/32Xbd0tW
61AxXZdSJj+WP6jYhr8d7x4NNNOhpx/yeknB0JC+viufwE7HnGb9THSSgGNRW6Axv7GszJl5Lq6h
mejPORuVUrfJy5MWfTrshOyz+W/nvXgG1cwHzG9jayNYpiZvzFbS3I1JSlpB5XwYStOTI5GvXQ4H
s4nS67XQSSuy3NqNcmmeswgr1BiD0R6beq/ZjIVJvdfbsBozUoJeJYpKtUJtT0h3peSjD9ymtnpi
ojFY/0JXBqvpr0WNzpQ4hwqR5BpzQnq2s2EwEC9mffMhlkSscTq16PAk22Itqt6FV81NNxn0NpfN
FmVUaHSa6Pz2ssUvqzBDyjV61csqS6wt2TOh7V2k0WoUxmhrfJLZqFGmtGyciTcYRFI4cbN4jfgr
UoH9+CLyfMBhzWygY7dBje7V4DHbhNaG/MqxyS9odwNLoxb81qM0qFI1CzJgMFmF1lkuuSlHzFep
aB/FFOCib4IZIDLzVS6XKj9TjiX4rUABuivpol/R5TEjWde0lIAOnGLKUYklza/qO95zOPpKxPen
N07zVP+hpHnBHzyzItvSSmm9Ofcymzj9+Wf9/jP+KGxRscPwWzCbms/68evnH3RhRus4nawFfalK
JZaXqKgEkTcpbctiLE44BdBP2oTOqMQ8p8BOCNJiVCGzFfhSU41IxCbba2ymy7xxeb3DM4sHXNao
qqIPa9bNySpYeXj96oOLM8yJuZ7c7LwUd3JBz2Wt6Q1uwWyxTEwM9eY0ZEcNLchtzI7qWNT+vic9
WnP5lpahCpe4yetOnpc9c1tHRrzTmpXgzZJpZYkzussr1gVzUwLdBYkVJfkxMa0ZM/p8Kb3VbTs6
MzXqxIlPe5Z6SprSupe4ixvHF5ZVytQxmelpjqqa+JwKOmoOYg90COtaHtl+vLJAmHZ+YxxZxC7Y
MUurnI2OrKgEHZ3EdXQe0tEZSSdNRjoapiUBBJGEaTHmMUF5IrM5uT6mVZqU6VqGpSyyz2NLGV3J
pmZki7RgKVXnRxkbWzKHpahIGkbiIQwCacWKzmrKqdhVy8aETcUXsoYbmubvbE2M4UNAZmpbWJvc
FRw/wH0uXL1ammYsuaY/YgehAnZwkIC0114r7bWlGqNDXry35us75pQvjmvN9VLlIkvNxdWJDHah
4tJiTpXvfGkipVA8j1VgNvkg4LKaYVgbta7PrNMLranR9HPdHKH+gjaRdhxwf0IHk8R0sRib/ICu
o1JbJSQ4IRMS8rS0ybS0ybQ0U63UZFrMiydmB7Avn12BQ6JUUenQiBjSoRHZSoxsJUby1Mfw8lEe
MQvKcEtzMho5YKhqrqjPLGnKbJ1qahwK6SrMV+DSF9nhA0fvyCmEtrz0yuR/an66//t3/cHB+kMU
2+g4FM+zbmFT2zNqs0o31tE5NSrRpnJm1GSVbprqJUprXJQz3qxqvb6ppLs2x5zZ3tKQPG9Lk3uq
PWTe0kv6y//0wYZcpxFFjU69NTgrNrsqLbd2mg0dqZWPJ7RgHrklYGItSJsxMrQubaXIiGJmR6tF
WpNuGxN0dIfERhidB9mAk8Yaut2JyCCjQyygzWyeFpPcxE1vheGnRpk/ci6PWPs/2TrSWSOmdXzr
UJsy4u1t/8tQu8hQMFAf3enMx07nTVjIhpP6/YG4ynQhzSqkWwSfQfDpBZ9a8KmEaaKQLhMSIttA
sLSggKXtIVja10jhMG4C3c4kZGsFrZ3ure3UXHa6c7LTnbed2sx+Cm/eERxATaRtHZoJ9xlC2NTs
HRNkkY02TNYb6ZnZbH9D9zb8h2+2+arOt9Z8kyi+WbbxoQ1rf7SmqHTjgxvBxQ+7KlbMalpem+iq
XDGrcUWtR3h3zckrW6r3HN8Abgbvatq3uLRg0b625n39pQUL97HeI7sPtsknA8fXFQo+U2REgqWu
AWZHCyroCDfRGddKAjbMuHQQE1ptEotRnRLQ+Jt9JoenyUF3NtJwFLLPYNmTNm8XniDojuXfzLkO
aXApZffJlBq1Oio+2RGTU1jm5VMZ7wYpVWWl8YbE5Hi9XBTExc4Ei0ajUduzWovHQ3zOPd8R9hfV
pppEtVarMUq3Nu2T52TPosZN5NmAPrulsmVWy96Woy2KqkgFwdKcJLnRruDTx1BbyY3GlhgNXDUm
vB5wJ+cl5+lddIpz0cnORYeQi44/F+0TrlN4WRKdIKCFg+gD8NfT7YcP+VXqj+pl+qw3irUfWmZb
+izrLGKxpdjinP5alUuR3ux8jx3HYMZzFnrd1Ws+Z5a6jD8ysfmlWzB23GC7YuncKuc9RrrDKJi6
08AWg51r2Wk2QSl7Nn/hvpk58+pynFq5UqfS+SvnlkyrzXOlBmYH2wOp6XN2zkluLEt3YFsoqrRK
TVJRU/a0QLojLTAn2BFIFYx1q9DeUTH2ZLcN92Iuj8vqLUrxFaS5k/wVc6cX9jdl6K0Os97kNFti
zCpnjNPmzYlLLUzzJE2b3klXn8TJj2Wr5Q+RMtJzPJ1YvJmRcScxbAqW2gIsXSpKDCNm0k6ojzJk
nvM2xhvORTXmYpM9qpLOr+fO0skon9kl7+wZdj8Y2fteuoeW/fvNsmy12uxJz4qqx/Z2j8lKrwl3
8/X+r/SUj71wcUNUcpxdrdAo5Asu3LyyDfC373TJ5CStt/ixIhvvAjtxBlWRGBneAmP2EF+HParI
jHB2FabaL477ExL8GHNfBvRiob+q0ew/V17YaKcHz5Q2DTt4nj2Xh3Nn3htvs0NDNraXeU7H+S1N
4r89BvwbU4j3JzixjkXF4GwwkX1BBb/dGuIJV+w3t0+NOseFO/pEy9SO/lKjoK630NO6+DjWrZtw
Vi8QdKl0FKXSUZSqRhunSruFVDqWcAn85aNstnFHRilY6hngL6SrDyrovTKNwD0+YR4wnsaW2ZSq
U8Q0YfOgOH9kp3MU3y9MDauLNoj8yD51VrdI586i4ikPHNat8Y6oeIuy7TZpeVLZ2ekqKrsxp2Jn
HQ7t9AylmVrwtwZnTl96zWJZEl/Txz+btagmpSso28x9aF9ImrhF3AX7JJM5J4lr8pNAIWpX7BLS
XUK0tEWLFnzGIqMsVSPE0omlLFaIKQGXxwjuphitrUnbIp9FWjAT07m4EkuLv9cvYHnx4zdRZLde
xTafL1XwFUQ2N0K+TTpqOO0qWf42ZW5erMciU+7SmMWJJ9Xm5ISEJLtGIQjiF0pLkicu2aKceMRs
UejtRqFUbtWKPY5oo0JUmwzjWbKXbToFPddh/SXiCaFdkY1nO3pixw2ubP1xpUbUN5LKN8/C+uw0
RA+32HE7BaE9o7zMTzFxVH62bFp6KTAxCovUCcdlWbIZeCZkPE5UunO48MNIP8vS0+v/yO2/LMtq
mVhoxY9wDy4yFcKXqQluny9BaYlFaVai3z2h8ODWo5EcPEmaMR1HmWRtfc2Cf3OlsKRSqKkUCiqF
5EqhckxWE7Dr4+L0OwqFFYVCS6FQVij4C4VCBDyKRd2DQtEdAp3cMUOdQDYkRy9giv8KM76sTV82
mZOj8OFxddjWXTsmOEYVi/iTDJTc3/uiH43xtrTkS2NXUpiw0FBssqaTOb2EvGjyVl1y2Ra5CRGf
KFh1eH37rp4ZKWZr1qyth9ektAYyjCq5TFDpNDpfUVt+75XBdDG2qm1u7vIbun0PRxXNr05prquM
TaxcWBlYWBEv/DB41/amtOZVI/cu7PjxnQeWTteYrDqDyWbEgw+10WJsHX6gx5QQbSoduqavbFF1
siHKbb3s4eWZOe1DaGYyB7Y9pUjEPquYNAj7TpIiOhgtQqt0Q6k3CK2F0vCEjySoTwH3kQT1yadj
HFsLiWHbJiyZj9ImahJyaGQaRxL0ivhCn7foeM/Bf54QiLGnmWm0NGkSiWgPQtPGZNGB2ASTNwG1
oFs1+pFgT9CWSPFLxiZx1xAvtJVICSOeNGHJKVkNlvIXj9FGPt/op4/ZpcY/TU9D8D9N90iUjyMN
qUZxA1pakOocZEqd0twkCcmb5oSY1bSrWbR0HGsLZygyx2O668anOguOsJGNIjoM/WGLm7T+++k2
gG252SftPVN/GHbhLrI4S+RbA7oVUCWIIjv90i1lVFGRDS5+m1Aknpq+/vDKwTvXlKW1rKmb3hNI
zB04uGTx9b0ZiYHe6Q1rW1J/H1/SUbhqrat03vShVdOS6pbWVi6a4b7i8uH9Qmvn/vlZ0+Zsa5ux
ZG5LkruuvaeodmtXfnb7msr8hZ1NHm9zcJFs0bTanJjFwdSa6aXugj3j92S1VM1IdFdUN2X0r1iJ
cdqIvvQU+pINN5QfBGIu2bKn8C07tgSnAym0d2QKF2zG6QnUTtcSO208ezRVj8nw5Jx42FbCQzsZ
Gh8snVzB0oICfu9RxE72CPgPGjMDGq2H5OABh4i/w/wkoEGKbO0srYzQjkJdONRKHYLu8SC0BO/n
ucYEbdjUkQKSnjbhVGqxCnQTh7bD/Gt+u1dqxshJiW7eMA+wnwtbjF5AYN+PvQt9/pBAL4fl4lPZ
q0OX7bhviT9nVWh4JzhkdPmnt+UEV8xwJlQNNZYEZ6RFa2Qjt/5rtH/eA58fuuVziR/s/96WYHHM
7GsfX3XjM8NlyTULN1yB6ethDNu7FFEki7wbSE5OEJLjheQ4wesSkmOF5BjBh0UmSkiXjktWD7o4
hhtuz6i5cwRCTUvSI3szsGRQiWF9sGRQsLQwp9MHvsaEaJooWkc/dZbIOAJL4wosjaML/E/T+z24
YXqkOIRn5zY88qo85p2Tju2Rij0azqscx0LCbOo/i7u3fP4UjA0GuupFfqTj6PnHYBaVUsku2IpT
Iid7C7W6eJcST1THe1R6nVKJB8OC8St6jykqdRphmlxvjbZiSVd+oDZqFLV076syx+LZsEUj/v5W
rdyQEGWJNuuVT4py3HLj0vnr6zVYemDtDbD2HejTFTirG9KLBH+CkB4v+BKEADWrtAwFBCc9UuLi
GLOGk5rJiW74aH4K/pHSiK1LT+HP9HQwFoyjgxEDOvREnaWk1OMpRefLejTfqczqMOOpThq3EGYJ
nCPok3NMJphAzk49Qpds1EttdJFxim0VmC/odQg7NmDuUEo3YnTuUEkPEO9QaEya8UKjw6QStSb9
1/OWl1rjCmcXSA/DVDqsPAp1dHn3yvKF1/VmORuuXHtWlq826RTN1jibRmVOcNoToqIMgrbnpm2L
/f62sqSktCS1NcGBA4PRkeyNLuzZUVex8/qjG17WWKWz21LMCTfBfl2C4iSO9acDcbQnzhdy1TBZ
Lj1x5Up2y6V2yx2TFQa0Mzt8M2dG47wFE78X8CGKjz7dCMDXFxCNLpqSndWklC6aElfEUpd1wfKP
ELoZxXDHgwyMb2Oky4Kl3g4+HbChGYzlAWRbHqDNll0uSF0ZHpTZClBuKbc48YBOF9A2dWT8w+NR
NHU44YzMEFj/z5Wa2VGPThJ+2kzYk/K5XrpOhg+ebJ6f5yOThVLaOknzAx7vosnOP9CU3ir5lkZ0
YAW4qWLTj1dWre8qM6mVotGgKexYW1s9WJvk79jethNtpVLqjJr11cubUmML2gvL+lvztGhYUaZU
28qCawPzr16Q6amYX16zdnamsKH7+iXFjni30WiPdyTHeVI8SRXBvOKuQBKGh8MWY1IlBbqL05qK
3N40r8LkcpqiLEYb2jmrc3PDjOXtpTqZqnA2nftzcEf8Ozzxn4Z56etAWUqW4MsUUjOE5FQh2Sek
xAk+l+CVJqiUaCElSvA5BZ9D8NkFnxlXGEKyQkiWC34X3S6cDljZbJXpjIZw0knMGWlEyifQds64
rCzz2OQ3gXjEMNPhZ6Z9yUwPJGa6iJjpKcT8GB68pxI5m6vwaOt5Ovzoo66AFsFyeU52qitLamC5
P9Fs1ibO0dLH8mhZa2n+ubw8ugbQRo2cTf15FvqkwO+XNnxEGoF8moqw9JjggoNc5Dl1sXB+rnIK
XiFR/J3dehPe+MBBw6Ya/0BvNihkSq1KeEFhS8hISMxNMN9kcUzcLZtYINwnrEv0TXzCT2yCWWlO
iLYlxEQZRCueBeGlIYPmm196Ze+Pl9EZawgj7ja8sVBBfhowpBYLqUXShZkozVjSpiwgFEdmJfAn
x3Xo/8X0FYU0mD4Npkyj4yLNOCtvbd7ePDEvnpo3npo3Xhpw8XTAxZ+S5WNz9V5kc3WaPlXEFRNa
7wTd49ls0Rg4GQF9RtlnHvrMX5HRHn3R0OnF3Qi96BXML0dGzJneF9ngYdMbte750cIuHiMXJPTC
lx6G+ds0Dvp0MXL9L95WPzy6avqqziITXrHCmx8q7bSG5Y0169qzUtt3zZ3R5YuLdsfLZqhNWoXd
OhHvbcpZe3htqXBo2T1ryywx0Ua9JdZqwetDeMbvqV3aXLGo0q2PTZGZEj0aTILJaRO3KmSF/SO4
E4icS/D3uZjqYPkBjIGjsLybvHIS73u8F9BaEoVWC71gwqQCU7F1ke43JTf6IhhPQ2DPTbjctAjo
0pFUZpqKOmkqsHSTJwXr6A3/Zowa3K1TfyROhNmllk2kpxu+sf29tKGV/sMGfBNYuh6UGHmC33oE
g8ehsOBVuGOx7bqpF1LQwdHLaSvQgyf9iZB0xlEJRhHG9xUVC9IJDi0jLS1HRYVGOZGlMEUlxyb5
cAgVPhi/2WZTaI0a2d+NDp1SfsYa74oxfv2s3qQRlQabQd6clmzDuoJbQlgzchKBNeNgTZnkPoyV
I4dUkycCtvQsYZpCSJcL6aIwDe+baYVaOlV46FRRi+UERmUrSfyOXKE0tyl3ea7ozxWwpGTg/Qmj
0YM/HaN7QJz92HHgOO2x5XTdQFLwJwErXQk2lwtF5fXlS8rF5HKhfEzmDxizU3BT+nePR1X02bQO
9GL1qAovJGGLSFcA7GLocZA+P/RLL6zAkcesR9CB6bSAXkwvsy665iu+4B2WvAT5xXfFReJhe077
zgfW+durMuwwlk6tS5sxJ7//QFeGrPCWvlU3d6fmrbh3Q/vunkCq5WhSdV9lVU95XEzJ/OqWa2Wn
Oh+868Cycp3ZanXHOmONCrzX1LLncI87p3zJtR1zv7+lPr1t9cjd9cNHV+VkzxosLF9cm0K32ejB
VoD+KAneVp1f3zW7bpa/pn/V8sUblv8fWwlI5QplbmRzdHJlYW0KZW5kb2JqCjQwOSAwIG9iagox
MzE4NwplbmRvYmoKNDEwIDAgb2JqCjw8IC9UeXBlIC9Gb250RGVzY3JpcHRvciAvQXNjZW50IDk1
MiAvQ2FwSGVpZ2h0IDY0NCAvRGVzY2VudCAtMjY5IC9GbGFncyA0Ci9Gb250QkJveCBbLTUwMyAt
MzA3IDEyNDAgOTY0XSAvRm9udE5hbWUgL1pGWFBFTytDYWxpYnJpIC9JdGFsaWNBbmdsZSAwIC9T
dGVtVgowIC9BdmdXaWR0aCA1MjEgL01heFdpZHRoIDEzMjggL1hIZWlnaHQgNDc2IC9Gb250Rmls
ZTIgNDA4IDAgUiA+PgplbmRvYmoKNDExIDAgb2JqClsgNTA3IDIyNiA1MDcgNTA3IDUwNyA1MDcg
NTA3IDUwNyA1MDcgMzE5IDQ3OSA1MjUgMzA2IDUwNyA1MjUgMjI5IDUwNyA1MjUKMzQ5IDYxNiAz
OTEgNTI1IDQ1MyAyNTIgNDg4IDQ4NyA0NTkgNzk5IDQ5OCA1NTcgNDcxIDUyNyAzMzUgNTI1IF0K
ZW5kb2JqCjQxMiAwIG9iago8PCAvTGVuZ3RoIDQxMyAwIFIgL0ZpbHRlciAvRmxhdGVEZWNvZGUg
Pj4Kc3RyZWFtCngBXZLLasMwEEX3/got00XxWHaSBoyhtASy6IOm/QBZGqeGRjaKs8jf984kTWkX
V3A0D821J3/YPG5iP5n8NQ1+y5Pp+hgSH4Zj8mxa3vUxK6wJvZ8upHd+78YsR/H2dJh4v4ndYOo6
MyZ/Q8lhSiczuw9Dyzdy95ICpz7uzOzjYas32+M4fvGe42QoaxoTuEO7Jzc+uz2bXEtvNwHxfjrd
ouo34/00ssFEqCjOI/kh8GF0npOLO85qoqZer5uMY/gXuhS0nf90KautbWpDRCs5Ag5LOBwZrb1k
/a8JWmMl3QVjqfibbqvzUG13mcYWTS0iKqnBmyVwpVgIOiBEVDnBFggRLTTqgRCQJcpACK1Wgh0Q
IlrOgWivQrIXxJsiJN8JwqsI0UoQY4hQawXnQAhYCi6AEJI1ugRCiMq76KfCzIpwg3kQrXQMuCnV
0VwfgptSHVULqYUbEToHQXxNEVBr4aZUR4slohUciRDtBOFGhDGkcwU3IkRhED/755PLf5f9vO6T
P6aEVdIl1i2T7ekjX/d8HEZpoPoGZ47WlAplbmRzdHJlYW0KZW5kb2JqCjQxMyAwIG9iago0MTQK
ZW5kb2JqCjE3NyAwIG9iago8PCAvVHlwZSAvRm9udCAvU3VidHlwZSAvVHJ1ZVR5cGUgL0Jhc2VG
b250IC9aRlhQRU8rQ2FsaWJyaSAvRm9udERlc2NyaXB0b3IKNDEwIDAgUiAvV2lkdGhzIDQxMSAw
IFIgL0ZpcnN0Q2hhciAzMyAvTGFzdENoYXIgNjYgL1RvVW5pY29kZSA0MTIgMCBSID4+CmVuZG9i
ago0MTQgMCBvYmoKKGEuY3N2KQplbmRvYmoKNDE1IDAgb2JqCihNYWMgT1MgWCAxMC42LjYgUXVh
cnR6IFBERkNvbnRleHQpCmVuZG9iago0MTYgMCBvYmoKKEZyZWQgQmFrZXIpCmVuZG9iago0MTcg
MCBvYmoKKE1pY3Jvc29mdCBFeGNlbCkKZW5kb2JqCjQxOCAwIG9iagooRDoyMDExMDExMDE5MzAx
NlowMCcwMCcpCmVuZG9iago0MTkgMCBvYmoKKCkKZW5kb2JqCjQyMCAwIG9iagpbIF0KZW5kb2Jq
CjEgMCBvYmoKPDwgL1RpdGxlIDQxNCAwIFIgL0F1dGhvciA0MTYgMCBSIC9Qcm9kdWNlciA0MTUg
MCBSIC9DcmVhdG9yIDQxNyAwIFIgL0NyZWF0aW9uRGF0ZQo0MTggMCBSIC9Nb2REYXRlIDQxOCAw
IFIgL0tleXdvcmRzIDQxOSAwIFIgL0FBUEw6S2V5d29yZHMgNDIwIDAgUiA+PgplbmRvYmoKeHJl
ZgowIDQyMQowMDAwMDAwMDAwIDY1NTM1IGYgCjAwMDAzMTY5MjEgMDAwMDAgbiAKMDAwMDAwODI3
OCAwMDAwMCBuIAowMDAwMzAyMTcwIDAwMDAwIG4gCjAwMDAwMDAwMjIgMDAwMDAgbiAKMDAwMDAw
ODI1OCAwMDAwMCBuIAowMDAwMDA4MzgyIDAwMDAwIG4gCjAwMDAyNDY2MzcgMDAwMDAgbiAKMDAw
MDA3ODYwNyAwMDAwMCBuIAowMDAwMDc5MDgzIDAwMDAwIG4gCjAwMDAwMjIxOTcgMDAwMDAgbiAK
MDAwMDAyMjQ3MiAwMDAwMCBuIAowMDAwMDY0OTYwIDAwMDAwIG4gCjAwMDAwNjUyMzQgMDAwMDAg
biAKMDAwMDA5NTc0MiAwMDAwMCBuIAowMDAwMDk2MDE3IDAwMDAwIG4gCjAwMDAwMTgxNDcgMDAw
MDAgbiAKMDAwMDAxODQzNyAwMDAwMCBuIAowMDAwMDY3NzMxIDAwMDAwIG4gCjAwMDAwNjgxMDYg
MDAwMDAgbiAKMDAwMDA4NTU3OSAwMDAwMCBuIAowMDAwMDg2MTM2IDAwMDAwIG4gCjAwMDAwMzYz
NTUgMDAwMDAgbiAKMDAwMDAzNjkzMiAwMDAwMCBuIAowMDAwMDk1MTM3IDAwMDAwIG4gCjAwMDAw
OTU3MjIgMDAwMDAgbiAKMDAwMDAyOTc5NyAwMDAwMCBuIAowMDAwMDMwNDEzIDAwMDAwIG4gCjAw
MDAwNzU0MjEgMDAwMDAgbiAKMDAwMDA3NjUwMCAwMDAwMCBuIAowMDAwMDY2Njg4IDAwMDAwIG4g
CjAwMDAwNjc3MTEgMDAwMDAgbiAKMDAwMDAzMDQzMyAwMDAwMCBuIAowMDAwMDMxNzExIDAwMDAw
IG4gCjAwMDAwMzk2NDAgMDAwMDAgbiAKMDAwMDA0MDgzMCAwMDAwMCBuIAowMDAwMDcyMjYzIDAw
MDAwIG4gCjAwMDAwNzMzNzIgMDAwMDAgbiAKMDAwMDA0Njk0MiAwMDAwMCBuIAowMDAwMDQ3OTgy
IDAwMDAwIG4gCjAwMDAwNTQzODkgMDAwMDAgbiAKMDAwMDA1NjI4MCAwMDAwMCBuIAowMDAwMDQw
ODUwIDAwMDAwIG4gCjAwMDAwNDI4NTUgMDAwMDAgbiAKMDAwMDA2NTI1MyAwMDAwMCBuIAowMDAw
MDY2NjY3IDAwMDAwIG4gCjAwMDAwNjgxMjYgMDAwMDAgbiAKMDAwMDA2OTY1NiAwMDAwMCBuIAow
MDAwMDIyNDkxIDAwMDAwIG4gCjAwMDAwMjQyNTAgMDAwMDAgbiAKMDAwMDAyNjIzNiAwMDAwMCBu
IAowMDAwMDI3OTEyIDAwMDAwIG4gCjAwMDAxMDA1OTQgMDAwMDAgbiAKMDAwMDEwMjQwOCAwMDAw
MCBuIAowMDAwMDUwMDc0IDAwMDAwIG4gCjAwMDAwNTIzNjggMDAwMDAgbiAKMDAwMDA1ODQ4MCAw
MDAwMCBuIAowMDAwMDYwNjg4IDAwMDAwIG4gCjAwMDAxMDUwMTMgMDAwMDAgbiAKMDAwMDEwNzU1
MCAwMDAwMCBuIAowMDAwMDY5Njc3IDAwMDAwIG4gCjAwMDAwNzIyNDIgMDAwMDAgbiAKMDAwMDA5
Mjg1OCAwMDAwMCBuIAowMDAwMDk1MTE2IDAwMDAwIG4gCjAwMDAwMzY5NTIgMDAwMDAgbiAKMDAw
MDAzOTYxOSAwMDAwMCBuIAowMDAwMTA5MzcyIDAwMDAwIG4gCjAwMDAxMTE4MzYgMDAwMDAgbiAK
MDAwMDA4ODE2MiAwMDAwMCBuIAowMDAwMDkwNDA5IDAwMDAwIG4gCjAwMDAwOTA0MzAgMDAwMDAg
biAKMDAwMDA5MjgzNyAwMDAwMCBuIAowMDAwMDMzODgwIDAwMDAwIG4gCjAwMDAwMzYzMzQgMDAw
MDAgbiAKMDAwMDA3MzM5MiAwMDAwMCBuIAowMDAwMDc1NDAwIDAwMDAwIG4gCjAwMDAwNDgwMDIg
MDAwMDAgbiAKMDAwMDA1MDA1MyAwMDAwMCBuIAowMDAwMDk4Mjg4IDAwMDAwIG4gCjAwMDAxMDA1
NzMgMDAwMDAgbiAKMDAwMDA0Mjg3NiAwMDAwMCBuIAowMDAwMDQ0NjQ3IDAwMDAwIG4gCjAwMDAw
NTIzODkgMDAwMDAgbiAKMDAwMDA1NDM2OCAwMDAwMCBuIAowMDAwMDk2MDM2IDAwMDAwIG4gCjAw
MDAwOTgyNjcgMDAwMDAgbiAKMDAwMDA4MTIzMiAwMDAwMCBuIAowMDAwMDgzNDEzIDAwMDAwIG4g
CjAwMDAwNDQ2NjggMDAwMDAgbiAKMDAwMDA0NjkyMSAwMDAwMCBuIAowMDAwMDgzNDM0IDAwMDAw
IG4gCjAwMDAwODU1NTggMDAwMDAgbiAKMDAwMDAyNDI3MSAwMDAwMCBuIAowMDAwMDI2MjE1IDAw
MDAwIG4gCjAwMDAwNjA3MDkgMDAwMDAgbiAKMDAwMDA2MjU1OSAwMDAwMCBuIAowMDAwMDIwMjQz
IDAwMDAwIG4gCjAwMDAwMjIxNzYgMDAwMDAgbiAKMDAwMDEwNzU3MSAwMDAwMCBuIAowMDAwMTA5
MzUxIDAwMDAwIG4gCjAwMDAwMTg0NTYgMDAwMDAgbiAKMDAwMDAyMDIyMSAwMDAwMCBuIAowMDAw
MDYyNTgwIDAwMDAwIG4gCjAwMDAwNjQ1NTMgMDAwMDAgbiAKMDAwMDAyNzkzMyAwMDAwMCBuIAow
MDAwMDI5Nzc1IDAwMDAwIG4gCjAwMDAwODYxNTYgMDAwMDAgbiAKMDAwMDA4ODE0MCAwMDAwMCBu
IAowMDAwMDU2MzAxIDAwMDAwIG4gCjAwMDAwNTg0NTggMDAwMDAgbiAKMDAwMDA3NjUyMCAwMDAw
MCBuIAowMDAwMDc4NTg1IDAwMDAwIG4gCjAwMDAwMzE3MzIgMDAwMDAgbiAKMDAwMDAzMzg1OCAw
MDAwMCBuIAowMDAwMDc5MTAyIDAwMDAwIG4gCjAwMDAwODEyMTAgMDAwMDAgbiAKMDAwMDEwMjQy
OSAwMDAwMCBuIAowMDAwMTA0OTkxIDAwMDAwIG4gCjAwMDAwNjQ1NzUgMDAwMDAgbiAKMDAwMDA2
NDkzOSAwMDAwMCBuIAowMDAwMDExNjQ1IDAwMDAwIG4gCjAwMDAwMTA2MzIgMDAwMDAgbiAKMDAw
MDAxNTk4MCAwMDAwMCBuIAowMDAwMDE2ODQ4IDAwMDAwIG4gCjAwMDAwMTQxMDUgMDAwMDAgbiAK
MDAwMDAxNzEzNCAwMDAwMCBuIAowMDAwMDEzMzc4IDAwMDAwIG4gCjAwMDAwMTY3MDUgMDAwMDAg
biAKMDAwMDAxMjk0MyAwMDAwMCBuIAowMDAwMDE2MTI1IDAwMDAwIG4gCjAwMDAwMTUyNTYgMDAw
MDAgbiAKMDAwMDAxMDM0NCAwMDAwMCBuIAowMDAwMDEwNDg4IDAwMDAwIG4gCjAwMDAwMTQ2ODAg
MDAwMDAgbiAKMDAwMDAxMjA3NSAwMDAwMCBuIAowMDAwMDE1NDAwIDAwMDAwIG4gCjAwMDAwMTEz
NTMgMDAwMDAgbiAKMDAwMDAxNTExMiAwMDAwMCBuIAowMDAwMDE0ODI0IDAwMDAwIG4gCjAwMDAw
MTMyMzQgMDAwMDAgbiAKMDAwMDAxNjU2MSAwMDAwMCBuIAowMDAwMDEwNzczIDAwMDAwIG4gCjAw
MDAwMTM4MTMgMDAwMDAgbiAKMDAwMDAxMjY1MSAwMDAwMCBuIAowMDAwMDE1ODM2IDAwMDAwIG4g
CjAwMDAwMTAwNTIgMDAwMDAgbiAKMDAwMDAxMjc5OSAwMDAwMCBuIAowMDAwMDE2MjczIDAwMDAw
IG4gCjAwMDAwMTA5MTcgMDAwMDAgbiAKMDAwMDAxNDM5MiAwMDAwMCBuIAowMDAwMDE3NDIxIDAw
MDAwIG4gCjAwMDAwMTI1MDcgMDAwMDAgbiAKMDAwMDAxNTU0OCAwMDAwMCBuIAowMDAwMDEzNTIx
IDAwMDAwIG4gCjAwMDAwMTY5OTAgMDAwMDAgbiAKMDAwMDAxNjQxNyAwMDAwMCBuIAowMDAwMDE1
NjkyIDAwMDAwIG4gCjAwMDAwMTM2NjUgMDAwMDAgbiAKMDAwMDAxNzcxMyAwMDAwMCBuIAowMDAw
MDEyMzYzIDAwMDAwIG4gCjAwMDAwMTc4NTcgMDAwMDAgbiAKMDAwMDAxMTkzMSAwMDAwMCBuIAow
MDAwMDExMjA5IDAwMDAwIG4gCjAwMDAwMTQ1MzYgMDAwMDAgbiAKMDAwMDAxMTA2MSAwMDAwMCBu
IAowMDAwMDE0MjQ4IDAwMDAwIG4gCjAwMDAwMTc1NjkgMDAwMDAgbiAKMDAwMDAxMzk2MSAwMDAw
MCBuIAowMDAwMDEyMjE5IDAwMDAwIG4gCjAwMDAwMTE1MDEgMDAwMDAgbiAKMDAwMDAxNDk2OCAw
MDAwMCBuIAowMDAwMDEwMTk2IDAwMDAwIG4gCjAwMDAwMTMwOTAgMDAwMDAgbiAKMDAwMDAxNzI3
NyAwMDAwMCBuIAowMDAwMDExNzg4IDAwMDAwIG4gCjAwMDAyNDU3MzUgMDAwMDAgbiAKMDAwMDAw
MDAwMCAwMDAwMCBuIAowMDAwMzE2NTI4IDAwMDAwIG4gCjAwMDAwMTgwMDEgMDAwMDAgbiAKMDAw
MDI1OTU1NyAwMDAwMCBuIAowMDAwMjUxNjI5IDAwMDAwIG4gCjAwMDAyOTcyMTUgMDAwMDAgbiAK
MDAwMDI3NDQyMiAwMDAwMCBuIAowMDAwMjk5MTk3IDAwMDAwIG4gCjAwMDAyNTY1ODQgMDAwMDAg
biAKMDAwMDI3NjQwNCAwMDAwMCBuIAowMDAwMjU0NjAyIDAwMDAwIG4gCjAwMDAyNjI1MzAgMDAw
MDAgbiAKMDAwMDI4MzM0MSAwMDAwMCBuIAowMDAwMjYwNTQ4IDAwMDAwIG4gCjAwMDAyNzczOTUg
MDAwMDAgbiAKMDAwMDI2ODQ3NiAwMDAwMCBuIAowMDAwMjg2MzE0IDAwMDAwIG4gCjAwMDAyOTYy
MjQgMDAwMDAgbiAKMDAwMDMwMTE3OSAwMDAwMCBuIAowMDAwMjkwMjc4IDAwMDAwIG4gCjAwMDAy
OTgyMDYgMDAwMDAgbiAKMDAwMDI4MDM2OCAwMDAwMCBuIAowMDAwMjk1MjMzIDAwMDAwIG4gCjAw
MDAyNDk2NDcgMDAwMDAgbiAKMDAwMDI4OTI4NyAwMDAwMCBuIAowMDAwMjU4NTY2IDAwMDAwIG4g
CjAwMDAyODIzNTAgMDAwMDAgbiAKMDAwMDI1MzYxMSAwMDAwMCBuIAowMDAwMjY1NTAzIDAwMDAw
IG4gCjAwMDAyNTA2MzggMDAwMDAgbiAKMDAwMDI4ODI5NiAwMDAwMCBuIAowMDAwMjkxMjY5IDAw
MDAwIG4gCjAwMDAyNzU0MTMgMDAwMDAgbiAKMDAwMDI4MTM1OSAwMDAwMCBuIAowMDAwMjQ4NjU2
IDAwMDAwIG4gCjAwMDAyNjM1MjEgMDAwMDAgbiAKMDAwMDI2OTQ2NyAwMDAwMCBuIAowMDAwMjc4
Mzg2IDAwMDAwIG4gCjAwMDAzMDAxODggMDAwMDAgbiAKMDAwMDI2NjQ5NCAwMDAwMCBuIAowMDAw
MjYxNTM5IDAwMDAwIG4gCjAwMDAyODczMDUgMDAwMDAgbiAKMDAwMDI5NDI0MiAwMDAwMCBuIAow
MDAwMjU1NTkzIDAwMDAwIG4gCjAwMDAyNjc0ODUgMDAwMDAgbiAKMDAwMDI3OTM3NyAwMDAwMCBu
IAowMDAwMjcxNDQ5IDAwMDAwIG4gCjAwMDAyNjQ1MTIgMDAwMDAgbiAKMDAwMDI1NzU3NSAwMDAw
MCBuIAowMDAwMjcwNDU4IDAwMDAwIG4gCjAwMDAyODUzMjMgMDAwMDAgbiAKMDAwMDI3MzQzMSAw
MDAwMCBuIAowMDAwMjcyNDQwIDAwMDAwIG4gCjAwMDAyNDY2NzQgMDAwMDAgbiAKMDAwMDI1MjYy
MCAwMDAwMCBuIAowMDAwMjkyMjYwIDAwMDAwIG4gCjAwMDAyNDc2NjUgMDAwMDAgbiAKMDAwMDI5
MzI1MSAwMDAwMCBuIAowMDAwMjg0MzMyIDAwMDAwIG4gCjAwMDAxMjk1ODUgMDAwMDAgbiAKMDAw
MDEzMDY3NSAwMDAwMCBuIAowMDAwMjExMTk2IDAwMDAwIG4gCjAwMDAyMTM3MDQgMDAwMDAgbiAK
MDAwMDEyMTg2NCAwMDAwMCBuIAowMDAwMTI0NDYyIDAwMDAwIG4gCjAwMDAxNjQ1ODIgMDAwMDAg
biAKMDAwMDE2NTE5NyAwMDAwMCBuIAowMDAwMTU5NjY2IDAwMDAwIG4gCjAwMDAxNjIxOTMgMDAw
MDAgbiAKMDAwMDEzNjMzNyAwMDAwMCBuIAowMDAwMTM4OTQ2IDAwMDAwIG4gCjAwMDAxODczODUg
MDAwMDAgbiAKMDAwMDE4OTc5NCAwMDAwMCBuIAowMDAwMTQ5NDkzIDAwMDAwIG4gCjAwMDAxNTIw
MzMgMDAwMDAgbiAKMDAwMDE5OTQ1NiAwMDAwMCBuIAowMDAwMjAwODM1IDAwMDAwIG4gCjAwMDAy
MDg5ODMgMDAwMDAgbiAKMDAwMDIxMTE3NCAwMDAwMCBuIAowMDAwMTMzNjAyIDAwMDAwIG4gCjAw
MDAxMzYzMTUgMDAwMDAgbiAKMDAwMDExNjg0NyAwMDAwMCBuIAowMDAwMTE5Nzg1IDAwMDAwIG4g
CjAwMDAxMjY1NTQgMDAwMDAgbiAKMDAwMDEyNzk1OCAwMDAwMCBuIAowMDAwMTc4NDE3IDAwMDAw
IG4gCjAwMDAxODE0NjYgMDAwMDAgbiAKMDAwMDExMTg1NyAwMDAwMCBuIAowMDAwMTE0MDA4IDAw
MDAwIG4gCjAwMDAyMTc4MjggMDAwMDAgbiAKMDAwMDIyMDQ3NSAwMDAwMCBuIAowMDAwMjM0OTc4
IDAwMDAwIG4gCjAwMDAyMzc0NzkgMDAwMDAgbiAKMDAwMDIzNzUwMSAwMDAwMCBuIAowMDAwMjQw
MjY2IDAwMDAwIG4gCjAwMDAxMTk4MDcgMDAwMDAgbiAKMDAwMDEyMTg0MiAwMDAwMCBuIAowMDAw
MjEzNzI2IDAwMDAwIG4gCjAwMDAyMTYzOTMgMDAwMDAgbiAKMDAwMDE0Mzk4MCAwMDAwMCBuIAow
MDAwMTQ2NzIzIDAwMDAwIG4gCjAwMDAyMjA0OTcgMDAwMDAgbiAKMDAwMDIyMzE0NSAwMDAwMCBu
IAowMDAwMjAwODU3IDAwMDAwIG4gCjAwMDAyMDMzNjIgMDAwMDAgbiAKMDAwMDE0Njc0NSAwMDAw
MCBuIAowMDAwMTQ5NDcxIDAwMDAwIG4gCjAwMDAxMTQwMzAgMDAwMDAgbiAKMDAwMDExNjgyNSAw
MDAwMCBuIAowMDAwMTcwODA1IDAwMDAwIG4gCjAwMDAxNzMzMDUgMDAwMDAgbiAKMDAwMDE1NDA3
OSAwMDAwMCBuIAowMDAwMTU2NzE3IDAwMDAwIG4gCjAwMDAyMzMwODUgMDAwMDAgbiAKMDAwMDIz
NDMzNSAwMDAwMCBuIAowMDAwMjM0MzU3IDAwMDAwIG4gCjAwMDAyMzQ5NTcgMDAwMDAgbiAKMDAw
MDE3NjE0OCAwMDAwMCBuIAowMDAwMTc4Mzk1IDAwMDAwIG4gCjAwMDAxNTIwNTUgMDAwMDAgbiAK
MDAwMDE1NDA1NyAwMDAwMCBuIAowMDAwMTk3OTMzIDAwMDAwIG4gCjAwMDAxOTk0MzQgMDAwMDAg
biAKMDAwMDE2MjIxNSAwMDAwMCBuIAowMDAwMTY0NTYwIDAwMDAwIG4gCjAwMDAxNTY3MzkgMDAw
MDAgbiAKMDAwMDE1OTY0NCAwMDAwMCBuIAowMDAwMTM4OTY4IDAwMDAwIG4gCjAwMDAxNDEwMzQg
MDAwMDAgbiAKMDAwMDIwMzM4NCAwMDAwMCBuIAowMDAwMjA1OTgwIDAwMDAwIG4gCjAwMDAxMjQ0
ODQgMDAwMDAgbiAKMDAwMDEyNjUzMiAwMDAwMCBuIAowMDAwMjQwMjg4IDAwMDAwIG4gCjAwMDAy
NDI5NzQgMDAwMDAgbiAKMDAwMDEyNzk4MCAwMDAwMCBuIAowMDAwMTI5NTYzIDAwMDAwIG4gCjAw
MDAxODQwNzQgMDAwMDAgbiAKMDAwMDE4NjczNyAwMDAwMCBuIAowMDAwMTkyNjE2IDAwMDAwIG4g
CjAwMDAxOTUzOTUgMDAwMDAgbiAKMDAwMDE2ODA0NyAwMDAwMCBuIAowMDAwMTcwNzgzIDAwMDAw
IG4gCjAwMDAyMzE2NDYgMDAwMDAgbiAKMDAwMDIzMzA2MyAwMDAwMCBuIAowMDAwMjI1OTkxIDAw
MDAwIG4gCjAwMDAyMjg2NDEgMDAwMDAgbiAKMDAwMDE2NTIxOCAwMDAwMCBuIAowMDAwMTY4MDI1
IDAwMDAwIG4gCjAwMDAxMzA2OTYgMDAwMDAgbiAKMDAwMDEzMzU4MCAwMDAwMCBuIAowMDAwMTcz
MzI3IDAwMDAwIG4gCjAwMDAxNzYxMjYgMDAwMDAgbiAKMDAwMDIxNjQxNSAwMDAwMCBuIAowMDAw
MjE3ODA2IDAwMDAwIG4gCjAwMDAxODY3NTkgMDAwMDAgbiAKMDAwMDE4NzM2NCAwMDAwMCBuIAow
MDAwMTg5ODE2IDAwMDAwIG4gCjAwMDAxOTI1OTQgMDAwMDAgbiAKMDAwMDIyMzE2NyAwMDAwMCBu
IAowMDAwMjI1OTY5IDAwMDAwIG4gCjAwMDAxODE0ODggMDAwMDAgbiAKMDAwMDE4NDA1MiAwMDAw
MCBuIAowMDAwMjI4NjYzIDAwMDAwIG4gCjAwMDAyMzE2MjQgMDAwMDAgbiAKMDAwMDIwNjAwMiAw
MDAwMCBuIAowMDAwMjA4OTYxIDAwMDAwIG4gCjAwMDAxOTU0MTcgMDAwMDAgbiAKMDAwMDE5Nzkx
MSAwMDAwMCBuIAowMDAwMTQxMDU2IDAwMDAwIG4gCjAwMDAxNDM5NTggMDAwMDAgbiAKMDAwMDI0
Mjk5NiAwMDAwMCBuIAowMDAwMjQ1NzEzIDAwMDAwIG4gCjAwMDAyNDU3NzQgMDAwMDAgbiAKMDAw
MDI0NjYxNiAwMDAwMCBuIAowMDAwMjQ3NjQ0IDAwMDAwIG4gCjAwMDAyNDg2MzUgMDAwMDAgbiAK
MDAwMDI0OTYyNiAwMDAwMCBuIAowMDAwMjUwNjE3IDAwMDAwIG4gCjAwMDAyNTE2MDggMDAwMDAg
biAKMDAwMDI1MjU5OSAwMDAwMCBuIAowMDAwMjUzNTkwIDAwMDAwIG4gCjAwMDAyNTQ1ODEgMDAw
MDAgbiAKMDAwMDI1NTU3MiAwMDAwMCBuIAowMDAwMjU2NTYzIDAwMDAwIG4gCjAwMDAyNTc1NTQg
MDAwMDAgbiAKMDAwMDI1ODU0NSAwMDAwMCBuIAowMDAwMjU5NTM2IDAwMDAwIG4gCjAwMDAyNjA1
MjcgMDAwMDAgbiAKMDAwMDI2MTUxOCAwMDAwMCBuIAowMDAwMjYyNTA5IDAwMDAwIG4gCjAwMDAy
NjM1MDAgMDAwMDAgbiAKMDAwMDI2NDQ5MSAwMDAwMCBuIAowMDAwMjY1NDgyIDAwMDAwIG4gCjAw
MDAyNjY0NzMgMDAwMDAgbiAKMDAwMDI2NzQ2NCAwMDAwMCBuIAowMDAwMjY4NDU1IDAwMDAwIG4g
CjAwMDAyNjk0NDYgMDAwMDAgbiAKMDAwMDI3MDQzNyAwMDAwMCBuIAowMDAwMjcxNDI4IDAwMDAw
IG4gCjAwMDAyNzI0MTkgMDAwMDAgbiAKMDAwMDI3MzQxMCAwMDAwMCBuIAowMDAwMjc0NDAxIDAw
MDAwIG4gCjAwMDAyNzUzOTIgMDAwMDAgbiAKMDAwMDI3NjM4MyAwMDAwMCBuIAowMDAwMjc3Mzc0
IDAwMDAwIG4gCjAwMDAyNzgzNjUgMDAwMDAgbiAKMDAwMDI3OTM1NiAwMDAwMCBuIAowMDAwMjgw
MzQ3IDAwMDAwIG4gCjAwMDAyODEzMzggMDAwMDAgbiAKMDAwMDI4MjMyOSAwMDAwMCBuIAowMDAw
MjgzMzIwIDAwMDAwIG4gCjAwMDAyODQzMTEgMDAwMDAgbiAKMDAwMDI4NTMwMiAwMDAwMCBuIAow
MDAwMjg2MjkzIDAwMDAwIG4gCjAwMDAyODcyODQgMDAwMDAgbiAKMDAwMDI4ODI3NSAwMDAwMCBu
IAowMDAwMjg5MjY2IDAwMDAwIG4gCjAwMDAyOTAyNTcgMDAwMDAgbiAKMDAwMDI5MTI0OCAwMDAw
MCBuIAowMDAwMjkyMjM5IDAwMDAwIG4gCjAwMDAyOTMyMzAgMDAwMDAgbiAKMDAwMDI5NDIyMSAw
MDAwMCBuIAowMDAwMjk1MjEyIDAwMDAwIG4gCjAwMDAyOTYyMDMgMDAwMDAgbiAKMDAwMDI5NzE5
NCAwMDAwMCBuIAowMDAwMjk4MTg1IDAwMDAwIG4gCjAwMDAyOTkxNzYgMDAwMDAgbiAKMDAwMDMw
MDE2NyAwMDAwMCBuIAowMDAwMzAxMTU4IDAwMDAwIG4gCjAwMDAzMDIxNDkgMDAwMDAgbiAKMDAw
MDMwMjI1MyAwMDAwMCBuIAowMDAwMzAyMzE4IDAwMDAwIG4gCjAwMDAzMTU1OTggMDAwMDAgbiAK
MDAwMDMxNTYyMSAwMDAwMCBuIAowMDAwMzE1ODU4IDAwMDAwIG4gCjAwMDAzMTYwMTUgMDAwMDAg
biAKMDAwMDMxNjUwNyAwMDAwMCBuIAowMDAwMzE2Njk0IDAwMDAwIG4gCjAwMDAzMTY3MTkgMDAw
MDAgbiAKMDAwMDMxNjc3MiAwMDAwMCBuIAowMDAwMzE2ODAyIDAwMDAwIG4gCjAwMDAzMTY4Mzcg
MDAwMDAgbiAKMDAwMDMxNjg4MCAwMDAwMCBuIAowMDAwMzE2OTAwIDAwMDAwIG4gCnRyYWlsZXIK
PDwgL1NpemUgNDIxIC9Sb290IDQwNyAwIFIgL0luZm8gMSAwIFIgL0lEIFsgPGJjYzY2MjBhODNi
YTAyYjU0ODhiM2E3YzQwMjdkYTYwPgo8YmNjNjYyMGE4M2JhMDJiNTQ4OGIzYTdjNDAyN2RhNjA+
IF0gPj4Kc3RhcnR4cmVmCjMxNzA4OAolJUVPRgo=

--Apple-Mail-194-711788497--

From john-ietf@jck.com  Mon Jan 10 17:36:54 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 E7A573A6896 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 17:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.211
X-Spam-Level: 
X-Spam-Status: No, score=-103.211 tagged_above=-999 required=5 tests=[AWL=-0.612, 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 ia4KiRRiZ9Me for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 17:36:54 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id CCC343A6837 for <ietf@ietf.org>; Mon, 10 Jan 2011 17:36:53 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PcTCW-000BVN-GR; Mon, 10 Jan 2011 20:39:08 -0500
Date: Mon, 10 Jan 2011 20:39:07 -0500
From: John C Klensin <john-ietf@jck.com>
To: Fred Baker <fred@cisco.com>, IETF list <ietf@ietf.org>
Subject: Re: Poster sessions
Message-ID: <0AEE9B5160EFE527C0EFE27C@PST.JCK.COM>
In-Reply-To: <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.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: Tue, 11 Jan 2011 01:36:55 -0000

+1.  Very strongly.

Whether the logistics of space and times could be worked out or
not, poster sessions strike me as a really bad idea and Fred has
summarized at least most of the reasons.  If we had a high
barrier to posting I-Ds, it might be different.  But we don't.

   john


--On Monday, January 10, 2011 14:38 -0800 Fred Baker
<fred@cisco.com> wrote:

> 
> On Jan 10, 2011, at 5:56 AM, Marshall Eubanks wrote:
> 
>> You can go, read the poster and formulate opinions and
>> questions independently of anyone else, including the author.
>> If there is a time when the author is supposed to be present,
>> you can then go back and clarify any issues. You can't
>> establish any consensus this way, but it can be efficient at
>> resolving issues.
> 
> I'm attaching a chart that may be useful in this discussion.
> Using the rsync-able directory of all IETF ID's since 1992
> (btw, I don't believe the database before about 1996, but 14
> years is still interesting data), I did a brief scan of the
> arrival of drafts to the Internet Draft directory. The blue
> line shows the arrivals by month; the red bar graph tries
> (somewhat crudely) to aggregate drafts-by-IETF-meeting.
> 
> I'm envisioning the process and requirements of the poster
> sessions. In terms of process, today if I post a -00 draft to
> a working group, I can generally get discussion during the
> coming IETF meeting. What I think this suggests is that
> instead I would show a poster at the coming meeting and get
> working group discussion the meeting following. I'm not sure I
> like that implication.
> 
> I'm also thinking about the implications of 500-or-so posters.
> In terms of simple floor space, if we presume a poster and the
> conversation in front of it occupy a 3 meter-by 3 meter (10' X
> 10') space, we need 4500 square meters or 50,000 square feet
> of floor space to park them in. Time-wise, we need to assume
> that 1/3-to-1/2 of people who attend an IETF meeting will,
> instead of chairing or presenting in sessions, be out standing
> by their posters - and not wandering around looking at other
> posters. The mechanics look a little daunting.
> 
> Personally, call me stuck-in-the-mud, but this isn't an
> academic conference in which grad students are advertising for
> a professor that might be interested in mentoring them or a
> sponsor might fund their research. This is an SDO, and
> internet drafts are what any other SDO calls "contributions"
> or "work in progress". I would far rather have people who ant
> to talk about something contribute an internet draft on their
> topic, and talk with other people about their ideas - whether
> on working group lists or other places. For those of us that
> *do* participate, it seems to mostly work.
> 





From hannes.tschofenig@gmx.net  Mon Jan 10 23:06:38 2011
Return-Path: <hannes.tschofenig@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 49C913A69BF for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 23:06:38 -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=1.140, BAYES_00=-2.599, GB_I_INVITATION=-2, 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 evXrxZyQDZ04 for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 23:06:35 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 7F3B43A6765 for <ietf@ietf.org>; Mon, 10 Jan 2011 23:06:33 -0800 (PST)
Received: (qmail invoked by alias); 11 Jan 2011 07:08:48 -0000
Received: from unknown (EHLO [10.255.136.225]) [192.100.123.77] by mail.gmx.net (mp057) with SMTP; 11 Jan 2011 08:08:48 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+ZcpAF35GZgh+RKMGD4n02eJyHHUt8I7vEOX9QMT lZU1s5lCzOWxzu
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: IAB and INT Area Workshop on "Interconnecting Smart Objects with the Internet"
Date: Tue, 11 Jan 2011 09:08:45 +0200
Message-Id: <C2F89699-1BEF-49F1-B4B6-D2D6C4F36C85@gmx.net>
To: IETF Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 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, 11 Jan 2011 07:06:38 -0000

The Internet Architecture Board and the IETF Internet Area will hold a =
workshop on the Friday, 25th March 2011 in Prague on the topic:

             "Interconnecting Smart Objects with the Internet"

Attached to this workshop is a tutorial day on the same topic on =
Saturday, 26th March 2011. Please find more information about it at:=20
http://www.iab.org/about/workshops/smartobjects/tutorial.html

- Background

Today's Internet is experienced by users as a set of applications, such =
as email, instant messaging, and social networks. While these =
applications do not require users to be present at the time of service =
execution in many cases they are. There are also substantial differences =
in performance between the various end devices, but in general end =
devices participating in the Internet are considered to have high =
performance. =20

As we move forward with the interconnection of all kinds of devices via =
the Internet, these characteristics will change. The term "Internet of =
Things" denotes a trend where a large number of devices benefit from =
communication services that use Internet protocols. Many of these =
devices are not directly operated by humans, but exist as components in =
buildings, vehicles, and the environment. There will be a lot of =
variation in the computing power, available memory, and communications =
bandwidth between different types of devices.

Many of these devices provide new services or provide more value for =
previously unconnected devices. Some devices have been connected in =
various legacy ways in the past but are now migrating to the use of the =
Internet Protocol, sharing the same communications medium between all =
applications and enabling rich communications services.

Much of this development can simply run on existing Internet protocols. =
For instance, home entertainment and monitoring systems often offer a =
web interface to the end user. In many cases the new, constrained =
environments can benefit from additional protocols that help optimize =
the communications and lower the computational requirements. Examples of =
standardization efforts targeted for these environments include the =
"Constrained RESTful Environments (CoRE)", IPv6 over Low power WPAN =
(6LoWPAN)", and Routing Over Low power and Lossy networks (ROLL)" =
working groups at the IETF.

This workshop aims to explore the experience and approaches taken by =
researchers and developers of Internet technology, when considering the =
characteristics of constrained devices. Engineers know that many design =
considerations need to be taken into account when developing protocols =
and architecture. Balancing between the conflicting goals of computing =
performance, code size, economical incentives, and security is often =
difficult, as illustrated by Clark, et al. in "Tussle in Cyberspace: =
Defining Tomorrow's Internet", see =
http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle2002.pdf

This workshop aims to discuss the experience and approaches taken when =
designing protocols and architectures for interconnecting smart objects =
to the Internet. To frame the discussion we suggest, as examples, to =
investigate the area of integration in the following categories:
* Scalability
* Power efficiency
* Interworking between different technologies and network domains
* Usability and manageability
* Security and Privacy

The goal of the IETF is "to make the Internet work better" and the =
workshop organizers are interested in receiving contributions that =
support this goal. Results may lead to guidelines and recommendations, =
proposals for new standards development, start of new research =
activities, and the documentation of best current practices regarding =
implementation and configuration.=20

- Workshop Style

The workshop=92s main focus will be on the discussions of technical =
topics. (This is not a mini-conference where every author just briefly =
talks about their papers.)

In order to keep the group at a manageable size, participants are =
required to submit a position paper as an expression of interest. =
Submitters of accepted position papers will be invited to attend the =
workshop. Active participation will be expected.

The workshop will be structured as a series of working sessions =
punctuated by invited speakers who will present relevant background =
information or controversial ideas that help participants reach a deeper =
understanding of the subject. The organizing committee may ask =
submitters of particularly salient papers to present their ideas and =
experiences at the workshop. For each slot, there will be one or two =
invited controversial speakers, and group work on the problem that=92s =
identified, hopefully reaching either a deeper understanding of the =
problem or some means of approaching it.=20

- Important Dates

Position papers must be submitted at latest February, 11th, 2011. Note: =
An early submission allows us to provide you feedback!

Submitted position papers will be reviewed immediately by the program =
organizers and an invitation to the workshop will be sent to one of the =
paper authors. At the latest, invitations will be distributed by =
February, 25th.=20

This one-day workshop will take place on Friday, 25th March, 2011, right =
before the 80th IETF meeting in Prague, which starts on Sunday, 27th =
March. Independent of this workshop but relevant for the participants, =
are tutorial events on Saturday, 26th March 2011. These tutorials will =
focus on ongoing IETF efforts related to the IETF CoRE, ROLL, and =
6LoWPAN working groups. More details can be found at:=20

- Position Paper Requirements

Interested parties must submit a brief contribution describing their =
work or approach, as it relates to the workshop theme. We welcome =
visionary ideas for how to tackle the integration of constrained =
devices, as well as write-ups of deployment experience, and =
lessons-learned from successful or failed attempts at integrating these =
constrained devices with the Internet. Contributions are not required to =
be original in content.

We solicit brief write-ups with 1 to 3 pages, formatted in HTML, PDF, or =
plain text (for example as a submitted Internet Draft). We encourage =
paper authors to limit themselves on the most important challenge. A =
focused message will be key! Accepted position papers will be published =
(in addition to meeting minutes, slides, and a workshop report).=20

Please send your position paper to iot-workshop-prep@lists.i1b.org. =20

- Venue

The planned date and location for the workshop is Friday, March 25th, in =
Prague. Details about the meeting venue will be provided to the invited =
workshop participants. During the breaks coffee and tea will be served.=20=


There are no plans for remote participation.  Minutes of discussions =
will be available, and offers to organize audio recording would be =
gladly appreciated.

- Workshop Organizers=20

We look forward to your input. The workshop organizers are Jari Arkko =
(Internet Area Director), Hannes Tschofenig (IAB), Bernard Aboba (IAB), =
Carsten Bormann (CoRE and 6LoWPAN WG Chair), David Culler (ROLL WG =
Chair), Lars Eggert (Transport Area Director, and upcoming IRTF Chair), =
JP Vasseur (ROLL WG Chair), Stewart Bryant (Routing Area Director), =
Adrian Farrel (Routing Area Director), Ralph Droms (Internet Area =
Director), Geoffrey Mulligan (6LoWPAN WG Chair), Alexey Melnikov  =
(Applications Area Director), Peter Saint-Andre (Applications Area =
Director), Marcelo Bagnulo (IAB), Zach Shelby (Smart Power Directorate), =
Isidro Ballesteros Laso (European Commission), Fred Baker (Member of the =
Smart Power Directorate and liaison to the US Smart Grid =
Interoperability Panel - SGIP).

Up-to-date information about the workshop is available at:
http://www.iab.org/about/workshops/smartobjects/

Feel free to contact us at iot-workshop-prep@lists.i1b.org.=

From ynir@checkpoint.com  Mon Jan 10 23:30:29 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 BEBB83A69CF for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 23:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.997
X-Spam-Level: 
X-Spam-Status: No, score=-9.997 tagged_above=-999 required=5 tests=[AWL=0.602,  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 3P7SI+y3YFyP for <ietf@core3.amsl.com>; Mon, 10 Jan 2011 23:30:29 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by core3.amsl.com (Postfix) with ESMTP id 222CC3A69C0 for <ietf@ietf.org>; Mon, 10 Jan 2011 23:30:27 -0800 (PST)
X-CheckPoint: {4D2C079B-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com (il-ex01.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p0B7Wdg7003031;  Tue, 11 Jan 2011 09:32:40 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Tue, 11 Jan 2011 09:32:39 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: John C Klensin <john-ietf@jck.com>
Date: Tue, 11 Jan 2011 09:32:38 +0200
Subject: Re: Poster sessions
Thread-Topic: Poster sessions
Thread-Index: AcuxYbk3nKivi+xOSryZVcnErUFx9Q==
Message-ID: <6D992F32-6249-41C8-ADC9-2A85A7EDE138@checkpoint.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <0AEE9B5160EFE527C0EFE27C@PST.JCK.COM>
In-Reply-To: <0AEE9B5160EFE527C0EFE27C@PST.JCK.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 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, 11 Jan 2011 07:30:29 -0000

We can have as high a barrier as necessary to ensure there are no more than=
, say, 12 posters.

On Jan 11, 2011, at 3:39 AM, John C Klensin wrote:

> +1.  Very strongly.
>=20
> Whether the logistics of space and times could be worked out or
> not, poster sessions strike me as a really bad idea and Fred has
> summarized at least most of the reasons.  If we had a high
> barrier to posting I-Ds, it might be different.  But we don't.
>=20
>   john


From tme@americafree.tv  Tue Jan 11 00:05:06 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 2C05F3A69F7 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 00:05:06 -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 MwNtJtu9Xdn1 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 00:05:05 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 299B73A69BE for <ietf@ietf.org>; Tue, 11 Jan 2011 00:05:05 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id CB4B89A03903; Tue, 11 Jan 2011 03:07:20 -0500 (EST)
Subject: Re: Poster sessions
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
Date: Tue, 11 Jan 2011 03:07:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CFE341E1-F055-4417-B08B-DE54323BD011@americafree.tv>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF 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, 11 Jan 2011 08:05:06 -0000

On Jan 10, 2011, at 5:38 PM, Fred Baker wrote:

>=20
> On Jan 10, 2011, at 5:56 AM, Marshall Eubanks wrote:
>=20
>> You can go, read the poster and formulate opinions and questions =
independently of anyone else, including the author. If there is a time =
when the author is supposed to be present, you can then go back and =
clarify any issues. You can't establish any consensus this way, but it =
can be efficient at resolving issues.
>=20
> I'm attaching a chart that may be useful in this discussion. Using the =
rsync-able directory of all IETF ID's since 1992 (btw, I don't believe =
the database before about 1996, but 14 years is still interesting data), =
I did a brief scan of the arrival of drafts to the Internet Draft =
directory. The blue line shows the arrivals by month; the red bar graph =
tries (somewhat crudely) to aggregate drafts-by-IETF-meeting.
>=20
> I'm envisioning the process and requirements of the poster sessions. =
In terms of process, today if I post a -00 draft to a working group, I =
can generally get discussion during the coming IETF meeting. What I =
think this suggests is that instead I would show a poster at the coming =
meeting and get working group discussion the meeting following. I'm not =
sure I like that implication.
>=20
> I'm also thinking about the implications of 500-or-so posters. In =
terms of simple floor space, if we presume a poster and the conversation =
in front of it occupy a 3 meter-by 3 meter (10' X 10') space, we need =
4500 square meters or 50,000 square feet of floor space to park them in. =
Time-wise, we need to assume that 1/3-to-1/2 of people who attend an =
IETF meeting will, instead of chairing or presenting in sessions, be out =
standing by their posters - and not wandering around looking at other =
posters. The mechanics look a little daunting.
>=20
> Personally, call me stuck-in-the-mud, but this isn't an academic =
conference in which grad students are advertising for a professor that =
might be interested in mentoring them or a sponsor might fund their =
research. This is an SDO, and internet drafts are what any other SDO =
calls "contributions" or "work in progress". I would far rather have =
people who ant to talk about something contribute an internet draft on =
their topic, and talk with other people about their ideas - whether on =
working group lists or other places. For those of us that *do* =
participate, it seems to mostly work.

Dear Fred;

I think that you are correct in your logistics. However, I understood =
the current proposal was to use posters as an alternative to Bar Bofs, =
which=20
would be a lot fewer in number. I would not support any plan to (say) =
double the IETF's throughput by the use of posters.=20

Regards
Marshall




>=20
> <a.csv.pdf>_______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From john-ietf@jck.com  Tue Jan 11 00:18:19 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 787653A69FE for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 00:18:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.183
X-Spam-Level: 
X-Spam-Status: No, score=-103.183 tagged_above=-999 required=5 tests=[AWL=-0.584, 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 JVLHLULLifng for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 00:18:18 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 467CE28C0D8 for <ietf@ietf.org>; Tue, 11 Jan 2011 00:18:18 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PcZSx-000LSZ-TC; Tue, 11 Jan 2011 03:20:32 -0500
Date: Tue, 11 Jan 2011 03:20:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Poster sessions
Message-ID: <C96D5CB531C22B5F3C55589F@PST.JCK.COM>
In-Reply-To: <6D992F32-6249-41C8-ADC9-2A85A7EDE138@checkpoint.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <0AEE9B5160EFE527C0EFE27C@PST.JCK.COM> <6D992F32-6249-41C8-ADC9-2A85A7EDE138@checkpoint.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 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, 11 Jan 2011 08:18:19 -0000

--On Tuesday, January 11, 2011 09:32 +0200 Yoav Nir
<ynir@checkpoint.com> wrote:

> We can have as high a barrier as necessary to ensure there are
> no more than, say, 12 posters.

Yes, but that is another aspect of why I don't want to go down
this path.   As soon as you say "high barrier", you imply some
sort of review process.  That takes up someone's time.  Given
our requirements about openness, there is considerable potential
for our having to create a process for appointing the reviewers
and/or a requirement for an appeals procedure for anyone who
thinks they have been put at a disadvantage by having a poster
turned down, etc.

That is very different from academic conferences in which review
norms are already in place and the culture doesn't permit making
claims based on being put at a disadvantage for standardization
because a contribution was turned down.   As Fred pointed out in
a different way, we need to remember that the IETF has become
primarily an SDO and that, as an open SDO, we have procedural
and openness requirements that don't apply to various sorts of
conferences.

Academic conferences also tend to be a lot more leisurely than
IETF meetings -- people can wander through poster sessions with
having a negative effect on more important schedules.

Alternate suggestion that might accomplish part of the goal:
convince an AD or two that there would be benefit in conducting
micro-BOFs (or, if you prefer, a cross between a BOF and
speed-dating).  The entry requirement would be an I-D posted
well in advance and a fairly normal BOF proposal but with
extremely short, presentation-only, or presentation and quick
questions, with maybe six to 10 presentations based on a poster
or handful of slides.

So...

ADs/IESG get BOF proposals.  Those that are clearly ready get
BOFs as usual.  Of those that are not but that would seem to
benefit from presentation time, ADs could allocate micro-BOF
slots either in area meetings or in a normal slot divided among
many of these.   Note that we are already doing presentations
like that in some area meetings -- this is not a radical
suggestion nor one that requires major logistical changes.

No formal requirement for minutes, no status for any decisions.
People who discover that they want to have further discussions
could arrange to meet informally --in the halls, at breaks, even
at the bar.

But note that any proposal for such a session starts with a
posted I-D that people can look at in advance if they are
interested.  If the real goal is to avoid the need to post an
I-D, I just don't see that working or the "poster" time being
well-spent.

   john


From john-ietf@jck.com  Tue Jan 11 01:07:15 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 97C8B3A6A26 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 01:07:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.158
X-Spam-Level: 
X-Spam-Status: No, score=-103.158 tagged_above=-999 required=5 tests=[AWL=-0.559, 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 MGrNSyBL3q0O for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 01:07:14 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 132843A6A19 for <ietf@ietf.org>; Tue, 11 Jan 2011 01:07:14 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PcaEL-000MfR-KN; Tue, 11 Jan 2011 04:09:29 -0500
Date: Tue, 11 Jan 2011 04:09:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: Lixia Zhang <lixia@cs.ucla.edu>, IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action:draft-white-tsvwg-netblt-00.txt
Message-ID: <154FFBA5C44220EC28FF5899@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
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, 11 Jan 2011 09:07:15 -0000

--On Saturday, January 08, 2011 07:37 -0800 Lixia Zhang
<lixia@cs.ucla.edu> wrote:

> I am not sure why this rush to get a new internet draft out,
> without consultation to any of its original authors, and given
> the rough consensus on ietf mailing list discussion is to keep
> NETBLT RFC as is (experimental).  

Lixia,

I'm not sure there is any rush.  I'm also not sure that the
effort that is going into this could not be better spent in
other ways.  I'm also not sure about the opposite of either -- I
actually don't have a strong opinion one way or the other.

However, it seems to me that...

(i) It has been a very long time since we published
specifications that might now be considered Experimental with
disclaimers that said, more or less, "don't even think about
implementing this without a discussion with, and maybe
permission from, the author".  If a spec is published as
Experimental, then people are assumed to be free, modulo any IPR
issues, to implement and test it.

(ii) To the extent to which it is worthwhile publishing
Experimental specifications at all, it is worthwhile (at least
if anyone is willing to do that work) to publish experimental
results, reports on implementations, and other things from which
the community might learn.  When I looked at White's original
spec a week or two ago, it appeared to be, in most respects,
just an implementation and deployment report that pointed to a
modified version of NETBLT that was then in important use.   As
of that time, White didn't know whether it was still in use or
not.  I certainly don't know.

(iii)  Despite (i), I think there may be a legitimate complaint
(at least about bad judgment) if those who created and specified
a variant of the original spec for a particular set of
applications did not consult the original authors while doing
so.   But that complaint is probably irrelevant at this late
date and, in any event, is about the behavior of various folks
whose identities I can't discern from the documentation I've
seen and not about Mykyta's behavior or even that of John While.

(iv) If you have concluded, based on your own work, what you
understand of the implications of the work While summarized, or
for other reasons what people should not be encouraged to
implement and experiment with NETBLT, then it seems to me
entirely reasonable to publish White's document and whatever
discussion you think it appropriate to provide (either as part
of that document or separately), and to do so as immediately
Historic, taking the original spec with it.

Again, I think it is an open question whether any of this is
worth the effort.  I could say the same thing for an extended
discussion of the subject on the IETF list.   But it seems clear
to me that, if the effort is going to be invested, it would be
more worthwhile to spend it documenting the status, history, and
strengths and weaknesses of the idea in a permanent form than in
having an extended conversation about procedures, modes of
consultation, etc.

Just my opinion as usual.
     best regards,
      john


From vesely@tana.it  Tue Jan 11 03:22:26 2011
Return-Path: <vesely@tana.it>
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 31ED628C26F for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 03:22:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.152
X-Spam-Level: 
X-Spam-Status: No, score=-5.152 tagged_above=-999 required=5 tests=[AWL=-0.433, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 d6NjChS5h3KZ for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 03:22:24 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 7CBD428C100 for <ietf@ietf.org>; Tue, 11 Jan 2011 03:22:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1294745077; bh=fISHDXBKqwktbNoQWvNJJuIjy/B819iMO1fBJIakju0=; l=1966; h=Message-ID:Date:From:MIME-Version:To:CC:References:In-Reply-To: Content-Transfer-Encoding; b=bhT9lkYxA30bSjvOeTc6IgajfGw2mvZxY+9/qMti3+QCr78k2xAWDm9j8od8UHblJ oIyS2I7+tkVVnz2IqDqsuNyo1T4l0WMeDiUax1JfvXtlWzc/YyM2AqRY/3ZeHltoTd tL1jrWLg+YBzXoCKVw5no5qtri3gT4UlBqd6Ldwc=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 11 Jan 2011 12:24:37 +0100 id 00000000005DC035.000000004D2C3DF5.0000348C
Message-ID: <4D2C3DF5.8020204@tana.it>
Date: Tue, 11 Jan 2011 12:24:37 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: SDO vs academic conference, was poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu>	<094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
In-Reply-To: <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
Content-Type: text/plain; charset=us-ascii
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: Tue, 11 Jan 2011 11:22:26 -0000

On 10/Jan/11 23:38, Fred Baker wrote:
> Personally, call me stuck-in-the-mud, but this isn't an academic
> conference in which grad students are advertising for a professor
> that might be interested in mentoring them or a sponsor might fund
> their research. This is an SDO, and internet drafts are what any
> other SDO calls "contributions" or "work in progress". I would far
> rather have people who ant to talk about something contribute an
> internet draft on their topic, and talk with other people about
> their ideas - whether on working group lists or other places. For
> those of us that *do* participate, it seems to mostly work.

OTOH, for those of us who don't participate, it doesn't :-)

My ignorance of IETF's inner functioning is so deep that I cannot even
tell what is the equivalent of a mentoring professor or a sponsoring
organization within the IETF, let alone finding one.  As an Internet
user, I may have a problem, hypothesize possible causes, and wait for
solutions to be proposed or formulate a tentative solution myself.
The question is, is the IETF the natural referent of such occurrences?
 Does the "I" in its name promote it as the universal coordinator for
Internet related issues?

I think a negative answer would affirm the view of the IETF as an SDO
only.  This would rise further questions such as who are its customers
--possibly the IGF or similar assemblies-- and what kind of mechanisms
do they use to order what has to be standardized and how.

A positive answer would imply the IETF is something more than an SDO.
Possibly the embryo of a technocracy.  That would call for more
dendritic links to the Internet at large.  For example, someone
proposed to add more entries and comments to the IETF's Outcomes Wiki.
 By symmetry, some means to campaign for input topics may also be
desirable --not necessarily poster sessions, just something that may
motivate outsiders to join the meetings.

From eburger@standardstrack.com  Tue Jan 11 04:24:30 2011
Return-Path: <eburger@standardstrack.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 8AEAC28C157 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 04:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.405
X-Spam-Level: 
X-Spam-Status: No, score=-102.405 tagged_above=-999 required=5 tests=[AWL=-0.121, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, 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 iT1PLcjPuqqd for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 04:24:28 -0800 (PST)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.249.249]) by core3.amsl.com (Postfix) with ESMTP id B55AA28C11E for <ietf@ietf.org>; Tue, 11 Jan 2011 04:24:28 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com;  h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=cks9QAncTd8Q+tch4ChgYFTtYj8bPDq2cQRHdvcsvppvz/AmYhNHTkh7C+vhRxa5uUoYzd34mSua8Ml6v0ePB3LaNexj8pLV6m7qmSAp3iYWxZuRjumbj84WxlJfH9od;
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.184]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1PcdER-0004Mc-34; Tue, 11 Jan 2011 04:21:47 -0800
Subject: Re: SDO vs academic conference, was poster sessions
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-49-761505579; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4D2C3DF5.8020204@tana.it>
Date: Tue, 11 Jan 2011 07:26:41 -0500
Message-Id: <DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu>	<094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <4D2C3DF5.8020204@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1082)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
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, 11 Jan 2011 12:24:30 -0000

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

Speaking personally, with none of my official hats on, I would offer the =
IETF is *only* an SDO.

There are no sponsoring organizations, because the IETF is a collection =
of individuals.  No sponsor needed.  For that matter, some individuals =
consider some sponsors toxic, so sometimes having a sponsor is a =
negative.

When one mentions 'finding a problem and proposing a solution,' if the =
problem is with an Internet protocol or an Internet protocol can solve =
the problem, then the IETF is the place to take the work.  However, if =
the problem is with Internet operations, then a place like the INET =
(ISOC-sponsored) or NANOG/APNOG/AfNOG/EOF would be a better place to go. =
 If the problem is about domain administration or governance, then ICANN =
is where to go.  If the question is about governance, then your local =
ISOC chapter or IGF would be a better place to go.

Parochially and from a purely self-serving perspective, I would offer =
the Internet Society has *a* I* organizational coordination role.  =
However, before the flames start from long-time I* participants, I would =
also offer that Internet governance is BY DEFINITION distributed and ANY =
organization that claims to be to be the center of the Internet =
universe/governance/technology is both delusional and probably does not =
have the support of ALL constituents (users, manufacturers, operators, =
and governments).  I would offer the IETF has near universal support for =
producing protocols from the global constituency, and near no support =
for anything else.

On another one of your questions, I would offer that for better or =
worse, the IETF ignores the question "who is the consumer of IETF work =
product" at a formal level.  The IETF does not produce protocols for =
governments.  The IETF does not produce protocols for operators.  The =
IETF does not produce protocols for vendors.  Rather, as a collection of =
volunteer individuals, the IETF produces protocols the individuals are =
WILLING to produce.  This is microeconomics at its best.  For people to =
volunteer literally millions of dollars worth of engineering time per =
year to the IETF, the IETF has to be relevant.  However, rather than =
being relevant because some government says it is relevant or being =
relevant because an industry consortium says it is relevant, the IETF is =
relevant because it has a history of producing relevant work.  Because =
of that history, people (individuals!) bring important, relevant work to =
the IETF.  Presuming other INDIVIDUALS see that work as being important, =
it gets worked on.

The fastest way to find out if ones work is relevant to the Internet =
*protocol* community, and note this is NOT necessarily the Internet =
community at large, is to bring it to the IETF.  If it is relevant work, =
it gets worked on.  You do not have to be from a member state, a member =
vendor, a member operator, a member institution.  You just need an email =
address.

FInally, one of my personal goals is to keep reminding folks that the =
IETF does engineering, NOT research.  If one has an idea that is not =
fully baked, the IRTF is a great place to bring the idea to where one =
can get the benefits of experienced IETF people without the drawbacks of =
an SDO.


On Jan 11, 2011, at 6:24 AM, Alessandro Vesely wrote:

> On 10/Jan/11 23:38, Fred Baker wrote:
>> Personally, call me stuck-in-the-mud, but this isn't an academic
>> conference in which grad students are advertising for a professor
>> that might be interested in mentoring them or a sponsor might fund
>> their research. This is an SDO, and internet drafts are what any
>> other SDO calls "contributions" or "work in progress". I would far
>> rather have people who ant to talk about something contribute an
>> internet draft on their topic, and talk with other people about
>> their ideas - whether on working group lists or other places. For
>> those of us that *do* participate, it seems to mostly work.
>=20
> OTOH, for those of us who don't participate, it doesn't :-)
>=20
> My ignorance of IETF's inner functioning is so deep that I cannot even
> tell what is the equivalent of a mentoring professor or a sponsoring
> organization within the IETF, let alone finding one.  As an Internet
> user, I may have a problem, hypothesize possible causes, and wait for
> solutions to be proposed or formulate a tentative solution myself.
> The question is, is the IETF the natural referent of such occurrences?
> Does the "I" in its name promote it as the universal coordinator for
> Internet related issues?
>=20
> I think a negative answer would affirm the view of the IETF as an SDO
> only.  This would rise further questions such as who are its customers
> --possibly the IGF or similar assemblies-- and what kind of mechanisms
> do they use to order what has to be standardized and how.
>=20
> A positive answer would imply the IETF is something more than an SDO.
> Possibly the embryo of a technocracy.  That would call for more
> dendritic links to the Internet at large.  For example, someone
> proposed to add more entries and comments to the IETF's Outcomes Wiki.
> By symmetry, some means to campaign for input topics may also be
> desirable --not necessarily poster sessions, just something that may
> motivate outsiders to join the meetings.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggY6MIIFIqAD
AgECAhEAxcM7lN0zgrA71mfq+sG6xjANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU
Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMDA5MDgwMDAw
MDBaFw0xMTA5MDgyMzU5NTlaMIHhMTUwMwYDVQQLEyxDb21vZG8gVHJ1c3QgTmV0d29yayAtIFBF
UlNPTkEgTk9UIFZBTElEQVRFRDFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNl
OiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMyBDb21v
ZG8gTGltaXRlZDEUMBIGA1UEAxMLRXJpYyBCdXJnZXIxKTAnBgkqhkiG9w0BCQEWGmVidXJnZXJA
c3RhbmRhcmRzdHJhY2suY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqeauFkEq
5Pj7AIAaDRbUWIpoblTKyrjcSfXRaHvjk0jWBTsBPe6oOZjudMK0Vo9A1Sl52BixDgf1/qb2Z+PT
7M0mqSOOsSucEBid48IMvGi79xmKKAVf5jiyFNNAaTZWn76dwNLMkKd/+Ki0fn8kEbb2zG+gGKyZ
MNHiNX+GQfPpHyzo2MTwnb16lXMfGJrGv4uLZS/pY9PENdFQnwV0ASZoqX+ArtLY2xeuC+rYG9xQ
Cz7qiLbJhCJzWsEGETyHLDjE5bN4HB9DsJKtGFLQuOdTanwGigNz9cVH9pLFNQxiotavAouXgqS4
wGvcq4mGP9w9zTychoUqIKsEg9OD1wIDAQABo4ICHDCCAhgwHwYDVR0jBBgwFoAUiYJnfcSdJnAA
S7RQSHzePa4Ebn0wHQYDVR0OBBYEFAlgEOVj6Hl0La8sPRP388HEMiWvMA4GA1UdDwEB/wQEAwIF
oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB
hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0
cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwgaUGA1UdHwSBnTCBmjBMoEqgSIZGaHR0cDovL2Ny
bC5jb21vZG9jYS5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls
LmNybDBKoEigRoZEaHR0cDovL2NybC5jb21vZG8ubmV0L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0
aGVudGljYXRpb25hbmRFbWFpbC5jcmwwbAYIKwYBBQUHAQEEYDBeMDYGCCsGAQUFBzAChipodHRw
Oi8vY3J0LmNvbW9kb2NhLmNvbS9VVE5BQUFDbGllbnRDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6
Ly9vY3NwLmNvbW9kb2NhLmNvbTAlBgNVHREEHjAcgRplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNv
bTANBgkqhkiG9w0BAQUFAAOCAQEACRTppSEc5DMYn8YXcbfX36iTaNBGw1gUvTNam0U8pXH0E7H3
2d4cTq6DEMu5ifEvxMGBqhUyv0sKxQ7+UvtDwrk7Kiy2L6TUC4zNEklZbtDqY7+Wd7EQZkN4k/zx
kMLlz2VIIRL/Cg48NrBKP5bo1la78NTJx8m4+VForLseEBabxMQoWB/GOVC7WpO/+RCgd93gz6H/
RzW1hnK0Uvu5H3Kz7HEC3R1Qk/sE9nXVzTfoJOMJRnyMS5Ut61mgoWSm/kUtczAlRRYh6IBOhzAl
awoXz+yk9hMCheYRAWx0EamBBpSzvqXj0N2vXYc62v3e3ddcLZncjiB0pYIfCE3s4DGCA/8wggP7
AgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBD
aXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cu
dXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIEVtYWlsAhEAxcM7lN0zgrA71mfq+sG6xjAJBgUrDgMCGgUAoIICDzAYBgkqhkiG9w0B
CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTAxMTExMjI2NDJaMCMGCSqGSIb3DQEJ
BDEWBBRBtNrSOPXD6YYO6Rsz4WNDzB0uWDCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG
EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg
VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG
A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7
lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD
VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg
TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t
VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6
wbrGMA0GCSqGSIb3DQEBAQUABIIBAFypssAsyIkjksTFdJXKGIIVJxESqFjdY2eVuqFTeFT6yf0f
+e0UPJz72ZCWE9Ld9JL6ANYMhpqEBUlS3tTraOlCPAid8COmoUohP7QlTrhs85aKwRM06paglwu5
H8rANO2gZZNqouLrUtedfqVsUQlbmQz2l5Gl8/1RsuzMCnXF1940YWtHxjiALXHdPyVZGgAUaVor
rLxUS6dHJaF/xbIU7jqzp4dY97DaGBALA0e4SdEd4GEwanEJ5PKs/u/3wa3bRVNA1uAVUpCOGSPn
4mRdZSAU35k4zb4W8kipLws5Qz/sHEJajIiyVZIjwUdCgp7H9EUM9sAt9cNkVBYKi4UAAAAAAAA=

--Apple-Mail-49-761505579--

From daedulus@btconnect.com  Tue Jan 11 04:37:38 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 3D6F428C11E for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 04:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTRoM2AXYQ6t for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 04:37:35 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by core3.amsl.com (Postfix) with ESMTP id EF09B28C0EE for <ietf@ietf.org>; Tue, 11 Jan 2011 04:37:32 -0800 (PST)
Received: from host217-44-202-158.range217-44.btcentralplus.com (HELO pc6) ([217.44.202.158]) by c2bthomr13.btconnect.com with SMTP id BGZ14711; Tue, 11 Jan 2011 12:39:36 +0000 (GMT)
Message-ID: <035701cbb183$c2c65100$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <bidulock@openss7.org>, "Mykyta Yevstifeyev" <evnikita2@gmail.com>
References: <4D2556C9.9020901@gmail.com><AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com><4D2842B8.7090100@gmail.com> <4D29556A.6060902@gmail.com> <20110109080610.GA12782@openss7.org>
Subject: Re: Old transport-layer protocols to Historic?
Date: Tue, 11 Jan 2011 12:36:10 +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.4D2C4F87.010B, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4D2C4F8B.0022,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 <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, 11 Jan 2011 12:37:38 -0000

----- Original Message -----
From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
Cc: "Bob Hinden" <bob.hinden@gmail.com>; <tsvwg@ietf.org>; "IETF Discussion"
<ietf@ietf.org>
Sent: Sunday, January 09, 2011 9:06 AM

> Mykyta,
>
> RDP is still in use (I know of companies using it).  It is
> used heavily as a transport for a "popular brand" of NAS for
> dial access call control and was a precursor to MEGACO/H.248.
> RDP was the initial transport used for gateway control (such
> as SGCP) until SCTP was developed.  Many commercial gateways
> still support these older pre-standard (to MEGACO) control
> protocols.  Some older devices still provisioned in the network
> only support the older protocols.
>
> Yah, I know it was EXPERIMENTAL, but we had nothing before SCTP
> that would fit the bill.  Its limitations was one of the driving
> forces behind developing SCTP.  One of the original protocol
> attempts abandonned before SCTP was based on RDP.
>
> Please leave RDP alone.
>

>From the tsvwg list
Date: Tue, 11 Jan 2011 11:21:38 +0200
Message-ID: <AANLkTi=wOurS4rfJrvNH64pn8_RoXrfJ9-HioXG8XeAt@mail.gmail.com>
"I personally think there is no useful way in moving NETBLT spec to
historic, as well as RDP. I consider that useful only for IRTP. Do you
think there is still a need in such protocol? what has it been made
for?

Mykyta."

which sounds like consensus on NETBLT and RDP.

Tom Petch


> --brian
>
> --
> Brian F. G. Bidulock
> bidulock@openss7.org
> http://www.openss7.org/


From evnikita2@gmail.com  Tue Jan 11 07:09:56 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 AD6F428C193; Tue, 11 Jan 2011 07:09:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level: 
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[AWL=-1.406, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_RAND_LETTRS4=0.799]
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 WOg-sQ6BbQGC; Tue, 11 Jan 2011 07:09:55 -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 4EA4828C152; Tue, 11 Jan 2011 07:09:55 -0800 (PST)
Received: by ewy8 with SMTP id 8so9513177ewy.31 for <multiple recipients>; Tue, 11 Jan 2011 07:12:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=SZOjYUA7s+Wverc+L5IyiOm5QG7fhwe4kVUv1U2qPfk=; b=SqiGNXx6WUFyz2r2Ku37h2uhqoyLhTKYkEzCqzIqvfL+8GxeH/MEwGNP/76gBFt+QF ++Z/rJZVFvtGNw1uadn25fv8TZ+5/SKWV6JJ1S5eYitqJvCXo796HncVnxtDZlOl5/we Pik/5di8zn/oBOPZLvXUjvotRzeVjsEPWkUSY=
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=XA5e6SfuS/Q3Q+ceJQuItedLxeCEnfLBQlXMdcTvO4stsPUxwn4HYiZRq3mvJEcOCy 8BF6FqDmL+tP7Fsb8GY5MPSD6I/o/eElszxjxz54hivR95yyPsQcD8uUa6yInw2S0OBm 135gzjJlU/6/Ml+7Af6hPT1CEpgvbPiKkmvfk=
Received: by 10.204.120.3 with SMTP id b3mr4043894bkr.41.1294758731583; Tue, 11 Jan 2011 07:12:11 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id x38sm15155074bkj.1.2011.01.11.07.12.09 (version=SSLv3 cipher=RC4-MD5); Tue, 11 Jan 2011 07:12:10 -0800 (PST)
Message-ID: <4D2C735C.7070302@gmail.com>
Date: Tue, 11 Jan 2011 17:12:28 +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: "t.petch" <ietfc@btconnect.com>
Subject: Re: Draft Review Request - IRTP IANA Considerations
References: <4D1715BE.6040100@gmail.com><4D199D89.4080508@gmail.com><00eb01cba6a5$b5606840$4001a8c0@gateway.2wire.net><4D1D6EB3.40803@gmail.com><4D2223E4.2040104@isi.edu><D3AB3EC9-7C73-4CDA-8702-3B70CD778ED7@nokia.com><4D240101.6090308@gmail.com><5131531F-D1E6-44F1-8FC0-94CBCF6CC2A8@isi.edu><024801cbaccd$e347d580$4001a8c0@gateway.2wire.net><4D2554F8.7060201@gmail.com><4D257766.7060808@isi.edu><4D25A0BC.9050505@gmail.com><84DCE00C-E6FE-4148-9ADB-A573672DC5F0@isi.edu><4D26ADE8.5080001@gmail.com><4D26B462.3040001@isi.edu><4D27F316.2000607@gmail.com><4D2B4994.9080009@isi.edu> <AANLkTinrxAixH_qLskfnfZrOshNd=B6WV20gwjUfxRj2@mail.gmail.com> <034201cbb183$42ac2080$4001a8c0@gateway.2wire.net>
In-Reply-To: <034201cbb183$42ac2080$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, "tsvwg@ietf.org" <tsvwg@ietf.org>, IETF Discussion <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, 11 Jan 2011 15:09:56 -0000

11.01.2011 13:28, t.petch wrote:
> ----- Original Message -----
> From: "Mykyta Yevstifeyev"<evnikita2@gmail.com>
> To: "Joe Touch"<touch@isi.edu>
> Cc: "t.petch"<ietfc@btconnect.com>;<gorry@erg.abdn.ac.uk>
> Sent: Tuesday, January 11, 2011 10:24 AM
>
>> Joe,
>>
>> 2011/1/10, Joe Touch<touch@isi.edu>:
>>>
>>> On 1/7/2011 9:16 PM, Mykyta Yevstifeyev wrote:
>>> ...
>>>>> "You need to explain why these protocols *need* to be moved to
>>>>> Historic". Such actions are typically reserved for protocols in
>>>>> current use that are dangerous, or protocols that are in current use
>>>>> that are being replaced by other protocols. Neither is the case here.
>>>>> There is no need to "move to Historic" (i.e., "deprecate", within the
>>>>> IETF process) such protocols.
>>>   >
>>>> See my message in IETF Discussion list.
>>> For those not on that list:
>>>
>>> - there are many others who share my view that moving experimental
>>> protocols to historic isn't useful per se, especially these protocols in
>>> particular
>> What 'these'? See that below.
>>> - your argument appears to be "the definition of Historic is incorrect"
>>>
>> Maybe a bit. It is more narrow and unclear than incorrect.
>>> Given your argument, it's difficult to appreciate why you claim it is
>>> urgent to move these protocols to a status whose definition you
>>> explicitly disagree with.
>> What protocols? Curently I'm speaking only about one - IRTP.
Joe,
> Yes, and that is one of the three (IRTP, NETBLT, RDP) that you
> raised on the ietf list under 'Old transport-layer protocols to Historic?'
It was to request the discussion on topics related with all these 
protocols.
> And as Joe has accurately pointed out, the ietf list has generated a lot
> of responses, from names I know well and have a high regard for,
> almost all of which say that this is a bad idea.  It is true that for
> NETBLT and for RDP concrete reasons have been given why this
> is a very bad idea; doubtless we coud find similar reasons for IRTP.
As well as I know, almost all responses concerned only RDP and NETBLT, 
and nearly nobody said anything about IRTP.  So I want to ask that now - 
what was IRTP developed for?  Is there any real reason it may be used?

Mykyta
> So you have proposed moving protocols to Historic and practically
> no-one agrees with what you say.
>
> Tom Petch
>
>> Mykyta
>>> Joe
>>>


From evnikita2@gmail.com  Tue Jan 11 07:13:02 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 EB0A228C18B for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 07:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.024
X-Spam-Level: 
X-Spam-Status: No, score=-2.024 tagged_above=-999 required=5 tests=[AWL=-0.985, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 YZ5QK0GK9EKJ for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 07:13:02 -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 A01A028C179 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:13:01 -0800 (PST)
Received: by bwz12 with SMTP id 12so20161580bwz.31 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:15:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ajU57unpM4M9tykgFzTB/dFKvRZ30qKtHj9VQd0K+5A=; b=HEJwQ3MXqnvv7s+IrrkReaOgrNR0jiC+J94P0sGGO3aspmdtWkjAjb7Ajbub9Cd/Qu 2WzFVzNx8hKY2iX16hTC1bkwsGyD6E0tOI67N/bEwXPSFt6/Y5Xh29QaiZBqxkdIK9dG MHOdrr19Mlg5ZLdSJgNC13m0ccf7WmQ3oi3zc=
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=rJnyVvPRphQ0U93XBUi6JSyJG+tC1KaKxUjab+4XeaC6UK/r+cRgCkR7SoQ2b1jP1Y 90ksZnUWaKTk07xr+01V1+h3z+bPwvFo4MSvyPZzQawf9Q6bhvg5rxLdcNCcmUyxkf0u e6LqNCwR6Vqmn1gb0dj2Vp1WIOSweEoblBQok=
Received: by 10.204.59.140 with SMTP id l12mr3606074bkh.2.1294758916061; Tue, 11 Jan 2011 07:15:16 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id b6sm15590007bkb.10.2011.01.11.07.15.14 (version=SSLv3 cipher=RC4-MD5); Tue, 11 Jan 2011 07:15:15 -0800 (PST)
Message-ID: <4D2C7415.7020903@gmail.com>
Date: Tue, 11 Jan 2011 17:15:33 +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: "t.petch" <daedulus@btconnect.com>
Subject: Re: Old transport-layer protocols to Historic?
References: <4D2556C9.9020901@gmail.com><AFC50009-6908-4AAB-89FB-45C776F40BE2@gmail.com><4D2842B8.7090100@gmail.com> <4D29556A.6060902@gmail.com> <20110109080610.GA12782@openss7.org> <035701cbb183$c2c65100$4001a8c0@gateway.2wire.net>
In-Reply-To: <035701cbb183$c2c65100$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: bidulock@openss7.org, IETF Discussion <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, 11 Jan 2011 15:13:03 -0000

11.01.2011 13:36, t.petch wrote:
> ----- Original Message -----
> From: "Brian F. G. Bidulock"<bidulock@openss7.org>
> To: "Mykyta Yevstifeyev"<evnikita2@gmail.com>
> Cc: "Bob Hinden"<bob.hinden@gmail.com>;<tsvwg@ietf.org>; "IETF Discussion"
> <ietf@ietf.org>
> Sent: Sunday, January 09, 2011 9:06 AM
>
>> Mykyta,
>>
>> RDP is still in use (I know of companies using it).  It is
>> used heavily as a transport for a "popular brand" of NAS for
>> dial access call control and was a precursor to MEGACO/H.248.
>> RDP was the initial transport used for gateway control (such
>> as SGCP) until SCTP was developed.  Many commercial gateways
>> still support these older pre-standard (to MEGACO) control
>> protocols.  Some older devices still provisioned in the network
>> only support the older protocols.
>>
>> Yah, I know it was EXPERIMENTAL, but we had nothing before SCTP
>> that would fit the bill.  Its limitations was one of the driving
>> forces behind developing SCTP.  One of the original protocol
>> attempts abandonned before SCTP was based on RDP.
>>
>> Please leave RDP alone.
>>
> > From the tsvwg list
> Date: Tue, 11 Jan 2011 11:21:38 +0200
> Message-ID:<AANLkTi=wOurS4rfJrvNH64pn8_RoXrfJ9-HioXG8XeAt@mail.gmail.com>
> "I personally think there is no useful way in moving NETBLT spec to
> historic, as well as RDP. I consider that useful only for IRTP. Do you
> think there is still a need in such protocol? what has it been made
> for?
>
> Mykyta."
>
> which sounds like consensus on NETBLT and RDP.
Tom,

But not IRTP.  I was initially, and I am now strongly concerned that 
this protocols is not useful anyway.

Mykyta
> Tom Petch
>
>
>> --brian
>>
>> --
>> Brian F. G. Bidulock
>> bidulock@openss7.org
>> http://www.openss7.org/
>


From tytso@thunk.org  Tue Jan 11 07:20:22 2011
Return-Path: <tytso@thunk.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 977BD3A67D2 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 07:20:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.265
X-Spam-Level: 
X-Spam-Status: No, score=-4.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, IP_NOT_FRIENDLY=0.334]
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 cWNQRoCtz2I5 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 07:20:20 -0800 (PST)
Received: from thunker.thunk.org (thunk.org [69.25.196.29]) by core3.amsl.com (Postfix) with ESMTP id 77B563A66B4 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:20:20 -0800 (PST)
Received: from root (helo=tytso-glaptop) by thunker.thunk.org with local-esmtp   (Exim 4.50 #1 (Debian)) id 1Pcg3N-0004Yd-JZ; Tue, 11 Jan 2011 10:22:33 -0500
Received: from tytso by tytso-glaptop with local (Exim 4.71) (envelope-from <tytso@thunk.org>) id 1Pcg3L-0000o0-I8; Tue, 11 Jan 2011 10:22:31 -0500
Date: Tue, 11 Jan 2011 10:22:30 -0500
From: Ted Ts'o <tytso@mit.edu>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: SDO vs academic conference, was poster sessions
Message-ID: <20110111152230.GA2917@thunk.org>
References: <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <4D2C3DF5.8020204@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D2C3DF5.8020204@tana.it>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on thunker.thunk.org); SAEximRunCond expanded to false
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, 11 Jan 2011 15:20:22 -0000

On Tue, Jan 11, 2011 at 12:24:37PM +0100, Alessandro Vesely wrote:
> My ignorance of IETF's inner functioning is so deep that I cannot even
> tell what is the equivalent of a mentoring professor or a sponsoring
> organization within the IETF, let alone finding one.  As an Internet
> user, I may have a problem, hypothesize possible causes, and wait for
> solutions to be proposed or formulate a tentative solution myself.
> The question is, is the IETF the natural referent of such occurrences?

Nope.

> Does the "I" in its name promote it as the universal coordinator for
> Internet related issues?

I think the more critical letter is the "E" in the name.  It is an
engineering organization; that is, it is a place where engineers can
get together to collaborate on engineering problems.  There are
several steps between "a user having a problem", and "working together
on an engineering solution".

Some of these steps might include include, "gathering requirements
from end-users to figure out what a valid solution to their problem
might look like" (as we all know, what users *think* is the problem
isn't always the problem; and just because a truck driver is the
'customer' of the bridge does not make a truck driver competent to
design bridges), and "figuring out whether there are enough customers
who are willing to pay at the right price point so it is economically
viable to put engineers to work on a problem".  Those are both areas
where the IETF does not function well; which is fine, that's not its
job.

So if you are an Internet user, you should talk to your providers, and
tell them your problems.  It's admittedly easier if you are a CIO of a
major company, and can tell a few router companies, "fix this problem
and my next $10 million order will go your company."  If you don't
have that kind of buying power, maybe you can get a large number of
like-minded users together and together you'll have enough buying
power to attract the attention of companies.

Or, if you have enough technical expertise that you can design
internet protocols by yourself, the IETF is open to submissions from
anyone; not just large companies who receive $10 million purchase
orders from aforementioned CIO's.  But you have to bring your own
engineering talent.  It's unlikely you will be able to get people to
do work for you for free.

(The same is true for the open source projects, BTW; if you want some
feature which isn't already in open source software, you can either
pay to have it developed, or you can do it yourself.  "Open" means
that you can have your choices of which company or engineer you hire
to do the work.  It's like buying a car which does not have its hood
locked so that mechanics at the car dealership have a monopoly on
fixing your problem.  But having a car which does not have its hood
welded shut does not mean that car maintenance gets done for free;
just that there's honest competition for your car maintenance
dollars.)

> I think a negative answer would affirm the view of the IETF as an SDO
> only.

It's an SDO only.

> A positive answer would imply the IETF is something more than an SDO.
> Possibly the embryo of a technocracy.  That would call for more
> dendritic links to the Internet at large.  For example, someone
> proposed to add more entries and comments to the IETF's Outcomes Wiki.

And once you tell us how you plan to pay for all of these engineers to
do the work proposed on an "Outcomes Wiki", maybe we could talk about
such a hypothetical organization.  But for now, capitalism, and
customer buying products which fund companies to send engineers to
IETF meetings is the only model I know of which has been proven to
work.

Best regards,

						- Ted

From hallam@gmail.com  Tue Jan 11 07:40:44 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 1EFE028C183 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 07:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.462
X-Spam-Level: 
X-Spam-Status: No, score=-4.462 tagged_above=-999 required=5 tests=[AWL=1.136,  BAYES_00=-2.599, GB_I_INVITATION=-2, 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 4WKG8SfhMQ2Z for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 07:40: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 C6BB728C153 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:40:41 -0800 (PST)
Received: by yxt33 with SMTP id 33so8985719yxt.31 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:42:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=4ZLW0xdYmyMb2jDbtT3Rw0vfsExGC3Yp608J4UWE5ws=; b=iz+ybcyaFow/h7M+8iXZwrFyBH+S0zj1p+QGu1q0ywCL+2ANV6svCY6TpAK9tdVPoS tv+oaRouwFatPDHFxlbA90+6kquYZYkw/dliWiT34YX77kVY77M3+4tAnuKnXFRnTr4B 864JQHv/ZbGECbsZwYbs+WP74akgwO0UekV4k=
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=awiQ6hOMNwKtMFBdi3Z8hiUxOsXhbcUcbZ+gztei0wpOrG7YhBRCdxUwBZXZkeQ9N2 MEabHenXsCuhHqdmIMrivsuhYeOcituiFMENhE9P+6LCJwat7GKnXwjAfYY+LvTHL684 twFM/DNI18MIcIqMxI/488s6aRckv/Zoi0PUw=
MIME-Version: 1.0
Received: by 10.100.153.17 with SMTP id a17mr2154577ane.239.1294760578306; Tue, 11 Jan 2011 07:42:58 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Tue, 11 Jan 2011 07:42:58 -0800 (PST)
In-Reply-To: <C2F89699-1BEF-49F1-B4B6-D2D6C4F36C85@gmx.net>
References: <C2F89699-1BEF-49F1-B4B6-D2D6C4F36C85@gmx.net>
Date: Tue, 11 Jan 2011 10:42:58 -0500
Message-ID: <AANLkTinnXfX3k5D4YhAJWkemvy8X9zk-qg5azTCY7+j9@mail.gmail.com>
Subject: Re: IAB and INT Area Workshop on "Interconnecting Smart Objects with the Internet"
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: multipart/alternative; boundary=0016e644d5cc56d282049993f09e
Cc: IETF Discussion <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, 11 Jan 2011 15:40:44 -0000

--0016e644d5cc56d282049993f09e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

What are the IPR constraints here?



On Tue, Jan 11, 2011 at 2:08 AM, Hannes Tschofenig <
hannes.tschofenig@gmx.net> wrote:

> The Internet Architecture Board and the IETF Internet Area will hold a
> workshop on the Friday, 25th March 2011 in Prague on the topic:
>
>             "Interconnecting Smart Objects with the Internet"
>
> Attached to this workshop is a tutorial day on the same topic on Saturday=
,
> 26th March 2011. Please find more information about it at:
> http://www.iab.org/about/workshops/smartobjects/tutorial.html
>
> - Background
>
> Today's Internet is experienced by users as a set of applications, such a=
s
> email, instant messaging, and social networks. While these applications d=
o
> not require users to be present at the time of service execution in many
> cases they are. There are also substantial differences in performance
> between the various end devices, but in general end devices participating=
 in
> the Internet are considered to have high performance.
>
> As we move forward with the interconnection of all kinds of devices via t=
he
> Internet, these characteristics will change. The term "Internet of Things=
"
> denotes a trend where a large number of devices benefit from communicatio=
n
> services that use Internet protocols. Many of these devices are not direc=
tly
> operated by humans, but exist as components in buildings, vehicles, and t=
he
> environment. There will be a lot of variation in the computing power,
> available memory, and communications bandwidth between different types of
> devices.
>
> Many of these devices provide new services or provide more value for
> previously unconnected devices. Some devices have been connected in vario=
us
> legacy ways in the past but are now migrating to the use of the Internet
> Protocol, sharing the same communications medium between all applications
> and enabling rich communications services.
>
> Much of this development can simply run on existing Internet protocols. F=
or
> instance, home entertainment and monitoring systems often offer a web
> interface to the end user. In many cases the new, constrained environment=
s
> can benefit from additional protocols that help optimize the communicatio=
ns
> and lower the computational requirements. Examples of standardization
> efforts targeted for these environments include the "Constrained RESTful
> Environments (CoRE)", IPv6 over Low power WPAN (6LoWPAN)", and Routing Ov=
er
> Low power and Lossy networks (ROLL)" working groups at the IETF.
>
> This workshop aims to explore the experience and approaches taken by
> researchers and developers of Internet technology, when considering the
> characteristics of constrained devices. Engineers know that many design
> considerations need to be taken into account when developing protocols an=
d
> architecture. Balancing between the conflicting goals of computing
> performance, code size, economical incentives, and security is often
> difficult, as illustrated by Clark, et al. in "Tussle in Cyberspace:
> Defining Tomorrow's Internet", see
> http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle2002.pdf
>
> This workshop aims to discuss the experience and approaches taken when
> designing protocols and architectures for interconnecting smart objects t=
o
> the Internet. To frame the discussion we suggest, as examples, to
> investigate the area of integration in the following categories:
> * Scalability
> * Power efficiency
> * Interworking between different technologies and network domains
> * Usability and manageability
> * Security and Privacy
>
> The goal of the IETF is "to make the Internet work better" and the worksh=
op
> organizers are interested in receiving contributions that support this go=
al.
> Results may lead to guidelines and recommendations, proposals for new
> standards development, start of new research activities, and the
> documentation of best current practices regarding implementation and
> configuration.
>
> - Workshop Style
>
> The workshop=92s main focus will be on the discussions of technical topic=
s.
> (This is not a mini-conference where every author just briefly talks abou=
t
> their papers.)
>
> In order to keep the group at a manageable size, participants are require=
d
> to submit a position paper as an expression of interest. Submitters of
> accepted position papers will be invited to attend the workshop. Active
> participation will be expected.
>
> The workshop will be structured as a series of working sessions punctuate=
d
> by invited speakers who will present relevant background information or
> controversial ideas that help participants reach a deeper understanding o=
f
> the subject. The organizing committee may ask submitters of particularly
> salient papers to present their ideas and experiences at the workshop. Fo=
r
> each slot, there will be one or two invited controversial speakers, and
> group work on the problem that=92s identified, hopefully reaching either =
a
> deeper understanding of the problem or some means of approaching it.
>
> - Important Dates
>
> Position papers must be submitted at latest February, 11th, 2011. Note: A=
n
> early submission allows us to provide you feedback!
>
> Submitted position papers will be reviewed immediately by the program
> organizers and an invitation to the workshop will be sent to one of the
> paper authors. At the latest, invitations will be distributed by February=
,
> 25th.
>
> This one-day workshop will take place on Friday, 25th March, 2011, right
> before the 80th IETF meeting in Prague, which starts on Sunday, 27th Marc=
h.
> Independent of this workshop but relevant for the participants, are tutor=
ial
> events on Saturday, 26th March 2011. These tutorials will focus on ongoin=
g
> IETF efforts related to the IETF CoRE, ROLL, and 6LoWPAN working groups.
> More details can be found at:
>
> - Position Paper Requirements
>
> Interested parties must submit a brief contribution describing their work
> or approach, as it relates to the workshop theme. We welcome visionary id=
eas
> for how to tackle the integration of constrained devices, as well as
> write-ups of deployment experience, and lessons-learned from successful o=
r
> failed attempts at integrating these constrained devices with the Interne=
t.
> Contributions are not required to be original in content.
>
> We solicit brief write-ups with 1 to 3 pages, formatted in HTML, PDF, or
> plain text (for example as a submitted Internet Draft). We encourage pape=
r
> authors to limit themselves on the most important challenge. A focused
> message will be key! Accepted position papers will be published (in addit=
ion
> to meeting minutes, slides, and a workshop report).
>
> Please send your position paper to iot-workshop-prep@lists.i1b.org.
>
> - Venue
>
> The planned date and location for the workshop is Friday, March 25th, in
> Prague. Details about the meeting venue will be provided to the invited
> workshop participants. During the breaks coffee and tea will be served.
>
> There are no plans for remote participation.  Minutes of discussions will
> be available, and offers to organize audio recording would be gladly
> appreciated.
>
> - Workshop Organizers
>
> We look forward to your input. The workshop organizers are Jari Arkko
> (Internet Area Director), Hannes Tschofenig (IAB), Bernard Aboba (IAB),
> Carsten Bormann (CoRE and 6LoWPAN WG Chair), David Culler (ROLL WG Chair)=
,
> Lars Eggert (Transport Area Director, and upcoming IRTF Chair), JP Vasseu=
r
> (ROLL WG Chair), Stewart Bryant (Routing Area Director), Adrian Farrel
> (Routing Area Director), Ralph Droms (Internet Area Director), Geoffrey
> Mulligan (6LoWPAN WG Chair), Alexey Melnikov  (Applications Area Director=
),
> Peter Saint-Andre (Applications Area Director), Marcelo Bagnulo (IAB), Za=
ch
> Shelby (Smart Power Directorate), Isidro Ballesteros Laso (European
> Commission), Fred Baker (Member of the Smart Power Directorate and liaiso=
n
> to the US Smart Grid Interoperability Panel - SGIP).
>
> Up-to-date information about the workshop is available at:
> http://www.iab.org/about/workshops/smartobjects/
>
> Feel free to contact us at iot-workshop-prep@lists.i1b.org.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

--0016e644d5cc56d282049993f09e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

What are the IPR constraints here?<div><br></div><div><br></div><div><br><d=
iv class=3D"gmail_quote">On Tue, Jan 11, 2011 at 2:08 AM, Hannes Tschofenig=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:hannes.tschofenig@gmx.net">hannes.=
tschofenig@gmx.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">The Internet Architecture Board and the IET=
F Internet Area will hold a workshop on the Friday, 25th March 2011 in Prag=
ue on the topic:<br>

<br>
 =A0 =A0 =A0 =A0 =A0 =A0 &quot;Interconnecting Smart Objects with the Inter=
net&quot;<br>
<br>
Attached to this workshop is a tutorial day on the same topic on Saturday, =
26th March 2011. Please find more information about it at:<br>
<a href=3D"http://www.iab.org/about/workshops/smartobjects/tutorial.html" t=
arget=3D"_blank">http://www.iab.org/about/workshops/smartobjects/tutorial.h=
tml</a><br>
<br>
- Background<br>
<br>
Today&#39;s Internet is experienced by users as a set of applications, such=
 as email, instant messaging, and social networks. While these applications=
 do not require users to be present at the time of service execution in man=
y cases they are. There are also substantial differences in performance bet=
ween the various end devices, but in general end devices participating in t=
he Internet are considered to have high performance.<br>

<br>
As we move forward with the interconnection of all kinds of devices via the=
 Internet, these characteristics will change. The term &quot;Internet of Th=
ings&quot; denotes a trend where a large number of devices benefit from com=
munication services that use Internet protocols. Many of these devices are =
not directly operated by humans, but exist as components in buildings, vehi=
cles, and the environment. There will be a lot of variation in the computin=
g power, available memory, and communications bandwidth between different t=
ypes of devices.<br>

<br>
Many of these devices provide new services or provide more value for previo=
usly unconnected devices. Some devices have been connected in various legac=
y ways in the past but are now migrating to the use of the Internet Protoco=
l, sharing the same communications medium between all applications and enab=
ling rich communications services.<br>

<br>
Much of this development can simply run on existing Internet protocols. For=
 instance, home entertainment and monitoring systems often offer a web inte=
rface to the end user. In many cases the new, constrained environments can =
benefit from additional protocols that help optimize the communications and=
 lower the computational requirements. Examples of standardization efforts =
targeted for these environments include the &quot;Constrained RESTful Envir=
onments (CoRE)&quot;, IPv6 over Low power WPAN (6LoWPAN)&quot;, and Routing=
 Over Low power and Lossy networks (ROLL)&quot; working groups at the IETF.=
<br>

<br>
This workshop aims to explore the experience and approaches taken by resear=
chers and developers of Internet technology, when considering the character=
istics of constrained devices. Engineers know that many design consideratio=
ns need to be taken into account when developing protocols and architecture=
. Balancing between the conflicting goals of computing performance, code si=
ze, economical incentives, and security is often difficult, as illustrated =
by Clark, et al. in &quot;Tussle in Cyberspace: Defining Tomorrow&#39;s Int=
ernet&quot;, see <a href=3D"http://groups.csail.mit.edu/ana/Publications/Pu=
bPDFs/Tussle2002.pdf" target=3D"_blank">http://groups.csail.mit.edu/ana/Pub=
lications/PubPDFs/Tussle2002.pdf</a><br>

<br>
This workshop aims to discuss the experience and approaches taken when desi=
gning protocols and architectures for interconnecting smart objects to the =
Internet. To frame the discussion we suggest, as examples, to investigate t=
he area of integration in the following categories:<br>

* Scalability<br>
* Power efficiency<br>
* Interworking between different technologies and network domains<br>
* Usability and manageability<br>
* Security and Privacy<br>
<br>
The goal of the IETF is &quot;to make the Internet work better&quot; and th=
e workshop organizers are interested in receiving contributions that suppor=
t this goal. Results may lead to guidelines and recommendations, proposals =
for new standards development, start of new research activities, and the do=
cumentation of best current practices regarding implementation and configur=
ation.<br>

<br>
- Workshop Style<br>
<br>
The workshop=92s main focus will be on the discussions of technical topics.=
 (This is not a mini-conference where every author just briefly talks about=
 their papers.)<br>
<br>
In order to keep the group at a manageable size, participants are required =
to submit a position paper as an expression of interest. Submitters of acce=
pted position papers will be invited to attend the workshop. Active partici=
pation will be expected.<br>

<br>
The workshop will be structured as a series of working sessions punctuated =
by invited speakers who will present relevant background information or con=
troversial ideas that help participants reach a deeper understanding of the=
 subject. The organizing committee may ask submitters of particularly salie=
nt papers to present their ideas and experiences at the workshop. For each =
slot, there will be one or two invited controversial speakers, and group wo=
rk on the problem that=92s identified, hopefully reaching either a deeper u=
nderstanding of the problem or some means of approaching it.<br>

<br>
- Important Dates<br>
<br>
Position papers must be submitted at latest February, 11th, 2011. Note: An =
early submission allows us to provide you feedback!<br>
<br>
Submitted position papers will be reviewed immediately by the program organ=
izers and an invitation to the workshop will be sent to one of the paper au=
thors. At the latest, invitations will be distributed by February, 25th.<br=
>

<br>
This one-day workshop will take place on Friday, 25th March, 2011, right be=
fore the 80th IETF meeting in Prague, which starts on Sunday, 27th March. I=
ndependent of this workshop but relevant for the participants, are tutorial=
 events on Saturday, 26th March 2011. These tutorials will focus on ongoing=
 IETF efforts related to the IETF CoRE, ROLL, and 6LoWPAN working groups. M=
ore details can be found at:<br>

<br>
- Position Paper Requirements<br>
<br>
Interested parties must submit a brief contribution describing their work o=
r approach, as it relates to the workshop theme. We welcome visionary ideas=
 for how to tackle the integration of constrained devices, as well as write=
-ups of deployment experience, and lessons-learned from successful or faile=
d attempts at integrating these constrained devices with the Internet. Cont=
ributions are not required to be original in content.<br>

<br>
We solicit brief write-ups with 1 to 3 pages, formatted in HTML, PDF, or pl=
ain text (for example as a submitted Internet Draft). We encourage paper au=
thors to limit themselves on the most important challenge. A focused messag=
e will be key! Accepted position papers will be published (in addition to m=
eeting minutes, slides, and a workshop report).<br>

<br>
Please send your position paper to <a href=3D"mailto:iot-workshop-prep@list=
s.i1b.org">iot-workshop-prep@lists.i1b.org</a>.<br>
<br>
- Venue<br>
<br>
The planned date and location for the workshop is Friday, March 25th, in Pr=
ague. Details about the meeting venue will be provided to the invited works=
hop participants. During the breaks coffee and tea will be served.<br>

<br>
There are no plans for remote participation. =A0Minutes of discussions will=
 be available, and offers to organize audio recording would be gladly appre=
ciated.<br>
<br>
- Workshop Organizers<br>
<br>
We look forward to your input. The workshop organizers are Jari Arkko (Inte=
rnet Area Director), Hannes Tschofenig (IAB), Bernard Aboba (IAB), Carsten =
Bormann (CoRE and 6LoWPAN WG Chair), David Culler (ROLL WG Chair), Lars Egg=
ert (Transport Area Director, and upcoming IRTF Chair), JP Vasseur (ROLL WG=
 Chair), Stewart Bryant (Routing Area Director), Adrian Farrel (Routing Are=
a Director), Ralph Droms (Internet Area Director), Geoffrey Mulligan (6LoWP=
AN WG Chair), Alexey Melnikov =A0(Applications Area Director), Peter Saint-=
Andre (Applications Area Director), Marcelo Bagnulo (IAB), Zach Shelby (Sma=
rt Power Directorate), Isidro Ballesteros Laso (European Commission), Fred =
Baker (Member of the Smart Power Directorate and liaison to the US Smart Gr=
id Interoperability Panel - SGIP).<br>

<br>
Up-to-date information about the workshop is available at:<br>
<a href=3D"http://www.iab.org/about/workshops/smartobjects/" target=3D"_bla=
nk">http://www.iab.org/about/workshops/smartobjects/</a><br>
<br>
Feel free to contact us at <a href=3D"mailto:iot-workshop-prep@lists.i1b.or=
g">iot-workshop-prep@lists.i1b.org</a>.<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>

--0016e644d5cc56d282049993f09e--

From hannes.tschofenig@nsn.com  Tue Jan 11 08:14:41 2011
Return-Path: <hannes.tschofenig@nsn.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 6EAA43A6809 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 08:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.282
X-Spam-Level: 
X-Spam-Status: No, score=-104.282 tagged_above=-999 required=5 tests=[AWL=2.317, 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 8A7u-8YV9Dln for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 08:14:40 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 5E0893A698E for <ietf@ietf.org>; Tue, 11 Jan 2011 08:14:40 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0BGGnId031372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Jan 2011 17:16:49 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0BGGnOt007164; Tue, 11 Jan 2011 17:16:49 +0100
Received: from FIESEXC015.nsn-intra.net ([10.159.0.23]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 11 Jan 2011 17:16:48 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: IAB and INT Area Workshop on "Interconnecting Smart Objects withthe Internet"
Date: Tue, 11 Jan 2011 18:16:47 +0200
Message-ID: <3D3C75174CB95F42AD6BCC56E5555B4503A0A316@FIESEXC015.nsn-intra.net>
In-Reply-To: <AANLkTinnXfX3k5D4YhAJWkemvy8X9zk-qg5azTCY7+j9@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IAB and INT Area Workshop on "Interconnecting Smart Objects withthe Internet"
Thread-Index: Acuxpm9I8Erhh/1XRaOUKxvkkKX+BQABBfog
References: <C2F89699-1BEF-49F1-B4B6-D2D6C4F36C85@gmx.net> <AANLkTinnXfX3k5D4YhAJWkemvy8X9zk-qg5azTCY7+j9@mail.gmail.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Phillip Hallam-Baker" <hallam@gmail.com>, "Hannes Tschofenig" <hannes.tschofenig@gmx.net>
X-OriginalArrivalTime: 11 Jan 2011 16:16:48.0945 (UTC) FILETIME=[F2FD8A10:01CBB1AA]
Cc: IETF Discussion <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, 11 Jan 2011 16:14:41 -0000

Hi Phillip,=20
=20
> What are the IPR constraints here?

Note well does not apply. That's how I handled it with other workshops
as well.
I wanted to explicitly point to this at the beginning of the workshop
but it could be useful to put it on the webpage. I was just worried that
it will confuse people more than it helps.

Ciao
Hannes

From daedulus@btconnect.com  Tue Jan 11 09:30:42 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 E0B013A69D3; Tue, 11 Jan 2011 09:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAZT0H+aEI0O; Tue, 11 Jan 2011 09:30:42 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by core3.amsl.com (Postfix) with ESMTP id 73AB13A67E7; Tue, 11 Jan 2011 09:30:40 -0800 (PST)
Received: from host217-44-202-158.range217-44.btcentralplus.com (HELO pc6) ([217.44.202.158]) by c2bthomr09.btconnect.com with SMTP id BIP29911; Tue, 11 Jan 2011 17:32:56 +0000 (GMT)
Message-ID: <003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Mykyta Yevstifeyev" <evnikita2@gmail.com>, "IETF Discussion" <ietf@ietf.org>
References: <4D23FFBA.5030804@gmail.com>
Subject: Last Call On draft-yevstifeyev-tn3270-uri-12
Date: Tue, 11 Jan 2011 17:29:29 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4D2C9448.0076, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4D2C9449.005A,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>
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, 11 Jan 2011 17:30:43 -0000

tn3270 is a widely used protocol but also a venerable one, so it is a little
surprising that the IETF is to register a provisional URI for it at this stage.

I have always seen it as an IBM protocol, and while that is no bar to being
an RFC - there are plenty of Cisco or Microsoft parallels - I am somewhat
surprised that the I-D contains no hint thereof; it does seem discourteous for
IBM not to appear in some guise, or perhaps I am missing something.

The provenance of the editor is unknown to
me - and of course, once an RFC has been through the IETF processes,
then the editorship is an irrelevance - but I am concerned that I have
no awareness of the contact provided as the scheme 'Author/Change controller',
no track record, no affiliation, a gmail address.  This seems more than
discourtesy, this seems wrong.

As such, I believe that this I-D should not progress to an RFC.

Tom Petch

----- Original Message -----
From: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
To: "IETF Discussion" <ietf@ietf.org>; <uri-review@ietf.org>; "URI" <uri@w3.org>
Sent: Wednesday, January 05, 2011 6:20 AM
Subject: FYI: Last Call On draft-yevstifeyev-tn3270-uri-12


> That is FYI. Any comments are welcome. Excuses if you receive multiple
> copies of this. Mykyta.
> > Date: Tue, 04 Jan 2011 09:52:23 -0800
> > From: The IESG<iesg-secretary@ietf.org>
> > Subject: Last Call:<draft-yevstifeyev-tn3270-uri-12.txt>  (The tn3270
> > Uniform Resource Identifier Scheme) to Informational RFC
> > To: IETF-Announce<ietf-announce@ietf.org>
> > Message-ID:<20110104175223.26076.55590.idtracker@localhost>
> > Content-Type: text/plain; charset="us-ascii"
> >
> >
> > The IESG has received a request from an individual submitter to consider
> > the following document:
> > - 'The tn3270 Uniform Resource Identifier Scheme'
> >    <draft-yevstifeyev-tn3270-uri-12.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-01. Exceptionally, comments may be
> > sent toiesg@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-yevstifeyev-tn3270-uri/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-yevstifeyev-tn3270-uri/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
>
>


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


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


From md3135@att.com  Tue Jan 11 04:32:46 2011
Return-Path: <md3135@att.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 6091328C11E for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 04:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.442
X-Spam-Level: 
X-Spam-Status: No, score=-106.442 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_MILLIONSOF=0.315, 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 WvoxrCV-LUzo for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 04:32:45 -0800 (PST)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id C809228C0EE for <ietf@ietf.org>; Tue, 11 Jan 2011 04:32:44 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: md3135@att.com
X-Msg-Ref: server-15.tower-121.messagelabs.com!1294749300!45991609!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 27631 invoked from network); 11 Jan 2011 12:35:00 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-15.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jan 2011 12:35:00 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0BCYANZ018299 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:34:10 -0500
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0BCY8f8018291 for <ietf@ietf.org>; Tue, 11 Jan 2011 07:34:08 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: SDO vs academic conference, was poster sessions
Date: Tue, 11 Jan 2011 07:34:55 -0500
Message-ID: <14C85D6CCBE92743AF33663BF5D24EBA08D06800@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SDO vs academic conference, was poster sessions
Thread-Index: Acuxit4A7TvxaWqIRHOINNa9PgK8ygAAN/Iw
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net><4D2AEC03.8040205@pi.nu>	<094C6685-62A8-435C-8467-A77A34A14963@americafree.tv><17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com><4D2C3DF5.8020204@tana.it> <DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com>
From: "DOLLY, MARTIN C (ATTSI)" <md3135@att.com>
To: "Eric Burger" <eburger@standardstrack.com>, "Alessandro Vesely" <vesely@tana.it>
X-Mailman-Approved-At: Tue, 11 Jan 2011 09:50:12 -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: Tue, 11 Jan 2011 12:32:46 -0000

At issue though is that these individuals get paid (sponsored) by
someone, either directly or indirectly by corporations and/or
governments.


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Eric Burger
Sent: Tuesday, January 11, 2011 7:27 AM
To: Alessandro Vesely
Cc: ietf@ietf.org
Subject: Re: SDO vs academic conference, was poster sessions

Speaking personally, with none of my official hats on, I would offer the
IETF is *only* an SDO.

There are no sponsoring organizations, because the IETF is a collection
of individuals.  No sponsor needed.  For that matter, some individuals
consider some sponsors toxic, so sometimes having a sponsor is a
negative.

When one mentions 'finding a problem and proposing a solution,' if the
problem is with an Internet protocol or an Internet protocol can solve
the problem, then the IETF is the place to take the work.  However, if
the problem is with Internet operations, then a place like the INET
(ISOC-sponsored) or NANOG/APNOG/AfNOG/EOF would be a better place to go.
If the problem is about domain administration or governance, then ICANN
is where to go.  If the question is about governance, then your local
ISOC chapter or IGF would be a better place to go.

Parochially and from a purely self-serving perspective, I would offer
the Internet Society has *a* I* organizational coordination role.
However, before the flames start from long-time I* participants, I would
also offer that Internet governance is BY DEFINITION distributed and ANY
organization that claims to be to be the center of the Internet
universe/governance/technology is both delusional and probably does not
have the support of ALL constituents (users, manufacturers, operators,
and governments).  I would offer the IETF has near universal support for
producing protocols from the global constituency, and near no support
for anything else.

On another one of your questions, I would offer that for better or
worse, the IETF ignores the question "who is the consumer of IETF work
product" at a formal level.  The IETF does not produce protocols for
governments.  The IETF does not produce protocols for operators.  The
IETF does not produce protocols for vendors.  Rather, as a collection of
volunteer individuals, the IETF produces protocols the individuals are
WILLING to produce.  This is microeconomics at its best.  For people to
volunteer literally millions of dollars worth of engineering time per
year to the IETF, the IETF has to be relevant.  However, rather than
being relevant because some government says it is relevant or being
relevant because an industry consortium says it is relevant, the IETF is
relevant because it has a history of producing relevant work.  Because
of that history, people (individuals!) bring important, relevant work to
the IETF.  Presuming other INDIVIDUALS see that work as being important,
it gets worked on.

The fastest way to find out if ones work is relevant to the Internet
*protocol* community, and note this is NOT necessarily the Internet
community at large, is to bring it to the IETF.  If it is relevant work,
it gets worked on.  You do not have to be from a member state, a member
vendor, a member operator, a member institution.  You just need an email
address.

FInally, one of my personal goals is to keep reminding folks that the
IETF does engineering, NOT research.  If one has an idea that is not
fully baked, the IRTF is a great place to bring the idea to where one
can get the benefits of experienced IETF people without the drawbacks of
an SDO.


On Jan 11, 2011, at 6:24 AM, Alessandro Vesely wrote:

> On 10/Jan/11 23:38, Fred Baker wrote:
>> Personally, call me stuck-in-the-mud, but this isn't an academic
>> conference in which grad students are advertising for a professor
>> that might be interested in mentoring them or a sponsor might fund
>> their research. This is an SDO, and internet drafts are what any
>> other SDO calls "contributions" or "work in progress". I would far
>> rather have people who ant to talk about something contribute an
>> internet draft on their topic, and talk with other people about
>> their ideas - whether on working group lists or other places. For
>> those of us that *do* participate, it seems to mostly work.
>=20
> OTOH, for those of us who don't participate, it doesn't :-)
>=20
> My ignorance of IETF's inner functioning is so deep that I cannot even
> tell what is the equivalent of a mentoring professor or a sponsoring
> organization within the IETF, let alone finding one.  As an Internet
> user, I may have a problem, hypothesize possible causes, and wait for
> solutions to be proposed or formulate a tentative solution myself.
> The question is, is the IETF the natural referent of such occurrences?
> Does the "I" in its name promote it as the universal coordinator for
> Internet related issues?
>=20
> I think a negative answer would affirm the view of the IETF as an SDO
> only.  This would rise further questions such as who are its customers
> --possibly the IGF or similar assemblies-- and what kind of mechanisms
> do they use to order what has to be standardized and how.
>=20
> A positive answer would imply the IETF is something more than an SDO.
> Possibly the embryo of a technocracy.  That would call for more
> dendritic links to the Internet at large.  For example, someone
> proposed to add more entries and comments to the IETF's Outcomes Wiki.
> By symmetry, some means to campaign for input topics may also be
> desirable --not necessarily poster sessions, just something that may
> motivate outsiders to join the meetings.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From william.polk@nist.gov  Tue Jan 11 08:41:58 2011
Return-Path: <william.polk@nist.gov>
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 4C3D23A6A3C for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 08:41:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.521
X-Spam-Level: 
X-Spam-Status: No, score=-7.521 tagged_above=-999 required=5 tests=[AWL=1.078,  BAYES_00=-2.599, GB_I_INVITATION=-2, 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 eomWCI7B+T6d for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 08:41:57 -0800 (PST)
Received: from smtp.nist.gov (rimp1.nist.gov [129.6.16.226]) by core3.amsl.com (Postfix) with ESMTP id C0D3A3A67FD for <ietf@ietf.org>; Tue, 11 Jan 2011 08:41:56 -0800 (PST)
Received: from WSXGHUB2.xchange.nist.gov (WSXGHUB2.xchange.nist.gov [129.6.18.19]) by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id p0BGiFiR017785; Tue, 11 Jan 2011 11:44:15 -0500
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Tue, 11 Jan 2011 11:43:56 -0500
From: "Polk, William T." <william.polk@nist.gov>
To: Phillip Hallam-Baker <hallam@gmail.com>, Hannes Tschofenig <hannes.tschofenig@gmx.net>
Date: Tue, 11 Jan 2011 11:44:01 -0500
Subject: Re: IAB and INT Area Workshop on "Interconnecting Smart Objects with the Internet"
Thread-Topic: IAB and INT Area Workshop on "Interconnecting Smart Objects with the Internet"
Thread-Index: Acuxpkv4Hi24aw3xRDKd8UCrsUi65wACHPP6
Message-ID: <C951F301.1D436%wpolk@nist.gov>
In-Reply-To: <AANLkTinnXfX3k5D4YhAJWkemvy8X9zk-qg5azTCY7+j9@mail.gmail.com>
Accept-Language: en-US
Content-Language: en
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-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: william.polk@nist.gov
X-Mailman-Approved-At: Tue, 11 Jan 2011 09:50:12 -0800
Cc: IETF Discussion <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, 11 Jan 2011 16:41:58 -0000

Phillip,

Are you asking if the IETF=B9s disclosure rules apply?  I believe they do.
Presentation or participation in the workshop would seem to satisfy the
second part of the definition of an IETF Contribution as stated in RFC 3979=
:

   c. "IETF Contribution": =B3... and any
      statement made within the context of an IETF activity=B2

A workshop is *not* included on the bulleted list that follows, but I read
that list as examples rather than a limiting set.  The out clause that ends
clause c. would not seem to apply:

      Statements made outside of an IETF session, mailing list or other
      function, that are clearly not intended to be input to an IETF
      activity, group or function, are not IETF Contributions in the
      context of this document.

I would consider the workshop an "IETF activity" or an "IETF function." If
that is correct, it is a contribution, and the rules apply.

I am unsure if it is productive to apply the same rules in a IAB workshop a=
s
in other IETF activities, but that is how I read it...

Tim

On 1/11/11 10:42 AM, "Phillip Hallam-Baker" <hallam@gmail.com> wrote:

> What are the IPR constraints here?
>=20
>=20
>=20
> On Tue, Jan 11, 2011 at 2:08 AM, Hannes Tschofenig <hannes.tschofenig@gmx=
.net>
> wrote:
>> The Internet Architecture Board and the IETF Internet Area will hold a
>> workshop on the Friday, 25th March 2011 in Prague on the topic:
>>=20
>>  =A0 =A0 =A0 =A0 =A0 =A0 "Interconnecting Smart Objects with the Interne=
t"
>>=20
>> Attached to this workshop is a tutorial day on the same topic on Saturda=
y,
>> 26th March 2011. Please find more information about it at:
>> http://www.iab.org/about/workshops/smartobjects/tutorial.html
>>=20
>> - Background
>>=20
>> Today's Internet is experienced by users as a set of applications, such =
as
>> email, instant messaging, and social networks. While these applications =
do
>> not require users to be present at the time of service execution in many
>> cases they are. There are also substantial differences in performance be=
tween
>> the various end devices, but in general end devices participating in the
>> Internet are considered to have high performance.
>>=20
>> As we move forward with the interconnection of all kinds of devices via =
the
>> Internet, these characteristics will change. The term "Internet of Thing=
s"
>> denotes a trend where a large number of devices benefit from communicati=
on
>> services that use Internet protocols. Many of these devices are not dire=
ctly
>> operated by humans, but exist as components in buildings, vehicles, and =
the
>> environment. There will be a lot of variation in the computing power,
>> available memory, and communications bandwidth between different types o=
f
>> devices.
>>=20
>> Many of these devices provide new services or provide more value for
>> previously unconnected devices. Some devices have been connected in vari=
ous
>> legacy ways in the past but are now migrating to the use of the Internet
>> Protocol, sharing the same communications medium between all application=
s and
>> enabling rich communications services.
>>=20
>> Much of this development can simply run on existing Internet protocols. =
For
>> instance, home entertainment and monitoring systems often offer a web
>> interface to the end user. In many cases the new, constrained environmen=
ts
>> can benefit from additional protocols that help optimize the communicati=
ons
>> and lower the computational requirements. Examples of standardization ef=
forts
>> targeted for these environments include the "Constrained RESTful Environ=
ments
>> (CoRE)", IPv6 over Low power WPAN (6LoWPAN)", and Routing Over Low power=
 and
>> Lossy networks (ROLL)" working groups at the IETF.
>>=20
>> This workshop aims to explore the experience and approaches taken by
>> researchers and developers of Internet technology, when considering the
>> characteristics of constrained devices. Engineers know that many design
>> considerations need to be taken into account when developing protocols a=
nd
>> architecture. Balancing between the conflicting goals of computing
>> performance, code size, economical incentives, and security is often
>> difficult, as illustrated by Clark, et al. in "Tussle in Cyberspace: Def=
ining
>> Tomorrow's Internet", see
>> http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle2002.pdf
>>=20
>> This workshop aims to discuss the experience and approaches taken when
>> designing protocols and architectures for interconnecting smart objects =
to
>> the Internet. To frame the discussion we suggest, as examples, to invest=
igate
>> the area of integration in the following categories:
>> * Scalability
>> * Power efficiency
>> * Interworking between different technologies and network domains
>> * Usability and manageability
>> * Security and Privacy
>>=20
>> The goal of the IETF is "to make the Internet work better" and the works=
hop
>> organizers are interested in receiving contributions that support this g=
oal.
>> Results may lead to guidelines and recommendations, proposals for new
>> standards development, start of new research activities, and the
>> documentation of best current practices regarding implementation and
>> configuration.
>>=20
>> - Workshop Style
>>=20
>> The workshop=B9s main focus will be on the discussions of technical topi=
cs.
>> (This is not a mini-conference where every author just briefly talks abo=
ut
>> their papers.)
>>=20
>> In order to keep the group at a manageable size, participants are requir=
ed to
>> submit a position paper as an expression of interest. Submitters of acce=
pted
>> position papers will be invited to attend the workshop. Active participa=
tion
>> will be expected.
>>=20
>> The workshop will be structured as a series of working sessions punctuat=
ed by
>> invited speakers who will present relevant background information or
>> controversial ideas that help participants reach a deeper understanding =
of
>> the subject. The organizing committee may ask submitters of particularly
>> salient papers to present their ideas and experiences at the workshop. F=
or
>> each slot, there will be one or two invited controversial speakers, and =
group
>> work on the problem that=B9s identified, hopefully reaching either a dee=
per
>> understanding of the problem or some means of approaching it.
>>=20
>> - Important Dates
>>=20
>> Position papers must be submitted at latest February, 11th, 2011. Note: =
An
>> early submission allows us to provide you feedback!
>>=20
>> Submitted position papers will be reviewed immediately by the program
>> organizers and an invitation to the workshop will be sent to one of the =
paper
>> authors. At the latest, invitations will be distributed by February, 25t=
h.
>>=20
>> This one-day workshop will take place on Friday, 25th March, 2011, right
>> before the 80th IETF meeting in Prague, which starts on Sunday, 27th Mar=
ch.
>> Independent of this workshop but relevant for the participants, are tuto=
rial
>> events on Saturday, 26th March 2011. These tutorials will focus on ongoi=
ng
>> IETF efforts related to the IETF CoRE, ROLL, and 6LoWPAN working groups.=
 More
>> details can be found at:
>>=20
>> - Position Paper Requirements
>>=20
>> Interested parties must submit a brief contribution describing their wor=
k or
>> approach, as it relates to the workshop theme. We welcome visionary idea=
s for
>> how to tackle the integration of constrained devices, as well as write-u=
ps of
>> deployment experience, and lessons-learned from successful or failed att=
empts
>> at integrating these constrained devices with the Internet. Contribution=
s are
>> not required to be original in content.
>>=20
>> We solicit brief write-ups with 1 to 3 pages, formatted in HTML, PDF, or
>> plain text (for example as a submitted Internet Draft). We encourage pap=
er
>> authors to limit themselves on the most important challenge. A focused
>> message will be key! Accepted position papers will be published (in addi=
tion
>> to meeting minutes, slides, and a workshop report).
>>=20
>> Please send your position paper to iot-workshop-prep@lists.i1b.org.
>>=20
>> - Venue
>>=20
>> The planned date and location for the workshop is Friday, March 25th, in
>> Prague. Details about the meeting venue will be provided to the invited
>> workshop participants. During the breaks coffee and tea will be served.
>>=20
>> There are no plans for remote participation. =A0Minutes of discussions w=
ill be
>> available, and offers to organize audio recording would be gladly
>> appreciated.
>>=20
>> - Workshop Organizers
>>=20
>> We look forward to your input. The workshop organizers are Jari Arkko
>> (Internet Area Director), Hannes Tschofenig (IAB), Bernard Aboba (IAB),
>> Carsten Bormann (CoRE and 6LoWPAN WG Chair), David Culler (ROLL WG Chair=
),
>> Lars Eggert (Transport Area Director, and upcoming IRTF Chair), JP Vasse=
ur
>> (ROLL WG Chair), Stewart Bryant (Routing Area Director), Adrian Farrel
>> (Routing Area Director), Ralph Droms (Internet Area Director), Geoffrey
>> Mulligan (6LoWPAN WG Chair), Alexey Melnikov =A0(Applications Area Direc=
tor),
>> Peter Saint-Andre (Applications Area Director), Marcelo Bagnulo (IAB), Z=
ach
>> Shelby (Smart Power Directorate), Isidro Ballesteros Laso (European
>> Commission), Fred Baker (Member of the Smart Power Directorate and liais=
on to
>> the US Smart Grid Interoperability Panel - SGIP).
>>=20
>> Up-to-date information about the workshop is available at:
>> http://www.iab.org/about/workshops/smartobjects/
>>=20
>> Feel free to contact us at iot-workshop-prep@lists.i1b.org.
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20


From randy_presuhn@mindspring.com  Tue Jan 11 10:28:33 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 A49413A684C; Tue, 11 Jan 2011 10:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.74
X-Spam-Level: 
X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 Xj1tBrVQZzy3; Tue, 11 Jan 2011 10:28:31 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by core3.amsl.com (Postfix) with ESMTP id 3B09B3A6A3D; Tue, 11 Jan 2011 10:28:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=LwFcSV0YDYjjP4izhPPIH7zuGr6EstjudJFJHOYf5VPVkr8eHRF5TIN20TcPMnUn; h=Received:Message-ID:From:To:Cc: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.23.161.247] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1PcizX-0008OM-Vb; Tue, 11 Jan 2011 13:30:48 -0500
Message-ID: <005a01cbb1bd$f0147940$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <4D23FFBA.5030804@gmail.com> <003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net>
Subject: Re: Last Call On draft-yevstifeyev-tn3270-uri-12
Date: Tue, 11 Jan 2011 10:32:42 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888d26d9b9edb73dbfb035abbc4993393c071576d1616694cc2350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.161.247
Cc: 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, 11 Jan 2011 18:28:33 -0000

Hi -

> From: "t.petch" <daedulus@btconnect.com>
> To: "Mykyta Yevstifeyev" <evnikita2@gmail.com>; "IETF Discussion" <ietf@ietf.org>
> Cc: "iesg" <iesg@ietf.org>
> Sent: Tuesday, January 11, 2011 8:29 AM
> Subject: Last Call On draft-yevstifeyev-tn3270-uri-12
....
> The provenance of the editor is unknown to
> me - and of course, once an RFC has been through the IETF processes,
> then the editorship is an irrelevance - but I am concerned that I have
> no awareness of the contact provided as the scheme 'Author/Change controller',
> no track record, no affiliation, a gmail address.  This seems more than
> discourtesy, this seems wrong.
...

As someone with no affiliation and as someone who chooses not to give
out his home address indiscriminately, I object to this line of objection.

Randy


From randy_presuhn@mindspring.com  Tue Jan 11 10:32:48 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 04DFC3A6A65 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 10:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.930, 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 A4iVyUHRKvaW for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 10:32:47 -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 F395F3A6A3D for <ietf@ietf.org>; Tue, 11 Jan 2011 10:32:46 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=pCBem6iK63uThYph5u3zbH1rwlNEqQ3ubGXsWydenwCA7zrxY9O/gUgTsX45JucR; 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.23.161.247] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Pcj3S-0005UB-QH for ietf@ietf.org; Tue, 11 Jan 2011 13:34:51 -0500
Message-ID: <006701cbb1be$73207280$6801a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net><4D2AEC03.8040205@pi.nu>	<094C6685-62A8-435C-8467-A77A34A14963@americafree.tv><17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com><4D2C3DF5.8020204@tana.it><DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com> <14C85D6CCBE92743AF33663BF5D24EBA08D06800@gaalpa1msgusr7e.ugd.att.com>
Subject: Re: SDO vs academic conference, was poster sessions
Date: Tue, 11 Jan 2011 10:35:57 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888d26d9b9edb73dbfbd7d7e1a8070ccb2ce27caf4cbea6017c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.161.247
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, 11 Jan 2011 18:32:48 -0000

Hi -
 
> From: "DOLLY, MARTIN C (ATTSI)" <md3135@att.com>
> To: "Eric Burger" <eburger@standardstrack.com>; "Alessandro Vesely" <vesely@tana.it>
> Cc: <ietf@ietf.org>
> Sent: Tuesday, January 11, 2011 4:34 AM
> Subject: RE: SDO vs academic conference, was poster sessions
>
> At issue though is that these individuals get paid (sponsored) by
> someone, either directly or indirectly by corporations and/or
> governments.

Not necessarily.  Some of us have no employer and just do this
stuff for the fun of it.

Randy


From john-ietf@jck.com  Tue Jan 11 11:30:09 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 6CE3628C103 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 11:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.134
X-Spam-Level: 
X-Spam-Status: No, score=-103.134 tagged_above=-999 required=5 tests=[AWL=-0.535, 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 WU7UaQrlyo9v for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 11:30:05 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id AEBC03A6A8D for <ietf@ietf.org>; Tue, 11 Jan 2011 11:30:04 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1Pcjx7-000Ees-Eq; Tue, 11 Jan 2011 14:32:21 -0500
Date: Tue, 11 Jan 2011 14:32:20 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>, ietf@ietf.org
Subject: Re: SDO vs academic conference, was poster sessions
Message-ID: <8C373906B2FB9C011E59FE7F@PST.JCK.COM>
In-Reply-To: <006701cbb1be$73207280$6801a8c0@oemcomputer>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net><4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <4D2C3DF5.8020204@tana.it> <DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com> <14C85D6CCBE92743AF33663BF5D24EBA08D06800@gaalpa1msgusr7e.ugd.att.com> <006701cbb1be$73207280$6801a8c0@oemcomputer>
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: Tue, 11 Jan 2011 19:30:09 -0000

--On Tuesday, January 11, 2011 10:35 -0800 Randy Presuhn
<randy_presuhn@mindspring.com> wrote:

>> At issue though is that these individuals get paid
>> (sponsored) by someone, either directly or indirectly by
>> corporations and/or governments.
> 
> Not necessarily.  Some of us have no employer and just do this
> stuff for the fun of it.

Indeed.  Although I'm increasingly taking exception to the "fun"
part.

   john





From mstjohns@comcast.net  Tue Jan 11 11:49:41 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 09E593A67D2 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 11:49:41 -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 Zjye4JEQLLhh for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 11:49:39 -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 AFED73A6A90 for <ietf@ietf.org>; Tue, 11 Jan 2011 11:49:38 -0800 (PST)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta09.westchester.pa.mail.comcast.net with comcast id uCC61f0050xGWP859KrwpX; Tue, 11 Jan 2011 19:51:56 +0000
Received: from Mike-PC3.comcast.net ([68.83.217.57]) by omta12.westchester.pa.mail.comcast.net with comcast id uKrw1f0051EtFYL3YKrwKc; Tue, 11 Jan 2011 19:51:56 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 11 Jan 2011 14:51:50 -0500
To: John C Klensin <john-ietf@jck.com>,Yoav Nir <ynir@checkpoint.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Poster sessions
In-Reply-To: <C96D5CB531C22B5F3C55589F@PST.JCK.COM>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <0AEE9B5160EFE527C0EFE27C@PST.JCK.COM> <6D992F32-6249-41C8-ADC9-2A85A7EDE138@checkpoint.com> <C96D5CB531C22B5F3C55589F@PST.JCK.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20110111194938.AFED73A6A90@core3.amsl.com>
Cc: IETF 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, 11 Jan 2011 19:49:41 -0000

Fred said:
>Personally, call me stuck-in-the-mud, but this isn't an academic conference in which grad students are advertising for a professor that might be interested in mentoring them or a sponsor might fund their research.

Ted said:
>But you have to bring your own
>engineering talent.  It's unlikely you will be able to get people to
>do work for you for free.


One of the goals of the Bar Bof is to solicit interest in new ideas AND to get people to do work for you for free.   Although I'm mostly in agreement with Fred about going overboard on the Poster idea, perhaps there's something we can use


At the risk of being flamed - let me suggest a high-tech, low impact, no presenter, poster show proposal.

Secretariat provides a projector and PC and a wall.

Individuals provide a 1 page PDF that can be blown up to be displayed using the above.  They're projected for 5 minutes (1 minute, 10 minutes - pick a number), and then on to the next - a very slow slide show.  When you get to the end, repeat - or randomize the order and repeat.

Maybe have one of those 2D bar codes with contact information for the poster child - I mean IETF attendee.

Posters are also available as part of the proceedings.

Poster is suggested for any Bar Bof, others may take advantage to drum up business for their WG.

Due in at least 1 week before the meeting.  Secretariat does a simple content pass to ensure items are relevant technical (as opposed to political, social etc).


IDs are useful as ways to start discussion, but tend to require time to consume.  Posters - or at least good posters - can convey enough information in a short time to let someone know whether or not to pay attention and maybe attend the Bar BOF for free beer.

Mike


At 03:20 AM 1/11/2011, John C Klensin wrote:


>--On Tuesday, January 11, 2011 09:32 +0200 Yoav Nir
><ynir@checkpoint.com> wrote:
>
>> We can have as high a barrier as necessary to ensure there are
>> no more than, say, 12 posters.
>
>Yes, but that is another aspect of why I don't want to go down
>this path.   As soon as you say "high barrier", you imply some
>sort of review process.  That takes up someone's time.  Given
>our requirements about openness, there is considerable potential
>for our having to create a process for appointing the reviewers
>and/or a requirement for an appeals procedure for anyone who
>thinks they have been put at a disadvantage by having a poster
>turned down, etc.
>
>That is very different from academic conferences in which review
>norms are already in place and the culture doesn't permit making
>claims based on being put at a disadvantage for standardization
>because a contribution was turned down.   As Fred pointed out in
>a different way, we need to remember that the IETF has become
>primarily an SDO and that, as an open SDO, we have procedural
>and openness requirements that don't apply to various sorts of
>conferences.
>
>Academic conferences also tend to be a lot more leisurely than
>IETF meetings -- people can wander through poster sessions with
>having a negative effect on more important schedules.
>
>Alternate suggestion that might accomplish part of the goal:
>convince an AD or two that there would be benefit in conducting
>micro-BOFs (or, if you prefer, a cross between a BOF and
>speed-dating).  The entry requirement would be an I-D posted
>well in advance and a fairly normal BOF proposal but with
>extremely short, presentation-only, or presentation and quick
>questions, with maybe six to 10 presentations based on a poster
>or handful of slides.
>
>So...
>
>ADs/IESG get BOF proposals.  Those that are clearly ready get
>BOFs as usual.  Of those that are not but that would seem to
>benefit from presentation time, ADs could allocate micro-BOF
>slots either in area meetings or in a normal slot divided among
>many of these.   Note that we are already doing presentations
>like that in some area meetings -- this is not a radical
>suggestion nor one that requires major logistical changes.
>
>No formal requirement for minutes, no status for any decisions.
>People who discover that they want to have further discussions
>could arrange to meet informally --in the halls, at breaks, even
>at the bar.
>
>But note that any proposal for such a session starts with a
>posted I-D that people can look at in advance if they are
>interested.  If the real goal is to avoid the need to post an
>I-D, I just don't see that working or the "poster" time being
>well-spent.
>
>   john
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf



From tobias.gondrom@gondrom.org  Tue Jan 11 12:31:59 2011
Return-Path: <tobias.gondrom@gondrom.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 2FC7A28C2E2 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 12:31:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -93.062
X-Spam-Level: 
X-Spam-Status: No, score=-93.062 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, MANGLED_LIST=2.3, RDNS_DYNAMIC=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 XT70FZd40T2l for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 12:31:59 -0800 (PST)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by core3.amsl.com (Postfix) with ESMTP id 1B88C28C127 for <ietf@ietf.org>; Tue, 11 Jan 2011 12:31:57 -0800 (PST)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=h1E77DU5zEsJO6T6P1g+cLGDMYwBmw+oiy/oB6/h4eqEjZGGhFeQWe2WSDb6g+cuTye3wVWO2Kj9lZdCLK5N1k/aFq0hhhqoKnCUG07qLV6Xn4MELFd3h8zL8AqHhsiT; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 7294 invoked from network); 11 Jan 2011 21:33:32 +0100
Received: from host-52-160.london.edu (HELO seraphim.heaven) (163.119.52.160) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Jan 2011 21:33:32 +0100
Message-ID: <4D2CBEA5.30406@gondrom.org>
Date: Tue, 11 Jan 2011 20:33:41 +0000
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.1.6 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: ben@nostrum.com
Subject: Re: Gen-ART LC Review of draft-ietf-ltans-xmlers-08
References: <9D732565-9596-4451-BF74-DE4CA0FC9B27@nostrum.com>
In-Reply-To: <9D732565-9596-4451-BF74-DE4CA0FC9B27@nostrum.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-ltans-xmlers.all@tools.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, 11 Jan 2011 20:31:59 -0000

Dear Ben,

thank you very much for your thorough review of xmlers.
I corrected nearly all of the items you raised and sent the revised
version to my co-authors for approval and publication as version -10. On
a note of further language style improvement beyond your comments, the
AD advised us at the time of submission to rely on the RFC Editor.
Details inline below.

Kind regards,
Tobias




On 01/06/2011 11:32 PM, Ben Campbell wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments you may receive.
>
> Document: draft-ietf-ltans-xmlers-08
> Reviewer: Ben Campbell
> Review Date: 11-01-06
> IETF LC End Date: 11-01-11
>
> Summary:
>
> This draft is on the right track for proposed standard, but I think it needs more editing prior to publication.
>
> Note that I have not attempted to verify the XML schema or examples. These should be mechanically verified prior to publication, if they have not already been done so.
xml schema has been verified.

> -Major issues:
>
> None
>
> -Minor issues:
>
> -- General: I'd like to see some more architectural background. Who are the actors? What are their roles? You mention the time stamp authorities, but not much else. Who are the verifiers? How to Certificate Authorities fit in?
For the architectural background I would refer you to ERS (RFC4998)
which is the ASN variant. Furthermore the systems mainly need the time
stamp authorities, all other players can actually vary with implementation.
For this reason we are currently working on an informational draft
draft-ietf-ltans-ari to exactly give a more detailed view on the use
scenarios and actors and roles.

> -- general: I'd like to see at least one complete example.
>
> -- 3.1.2, 1st paragraph: "exact time (obtained from trusted time source) of Time-Stamping."
>
> How exact?
Actually to be precise "how exact" depends on the time source. So not
sure what you mean here?
> -- 3.1.2, paragraph before example: "The Attribute type must be used"
>
> Normative?
yes, corrected to MUST

> -- 3.1.3, 1st paragraph:
>
> Is that a normative SHOULD? Can you offer examples or an explanation of when thus might not be possible?
corrected to SHOULD.
Example of when this might not be possible is when the data structure of
the used time-stamp token does not allow storing further verification data.
> -- 3.1.3, 2nd paragraph: "Following values SHOULD be used as identifiers for the Type attribute"
>
> Just should? Don't you mean to say the type MUST be something in the IANA registry?
yes, corrected to MUST
> -- 4.1, last paragraph "must be valid at the present time"
>
> Normative?
yes normative. Corrected to MUST
> -- 4.1.1, general:
>
> (comments also apply to the Canonicalization method URL)
>
> What does the URI represent? Does that point to the actual definition of the algorithm? Can I make up arbitrary ones? Is there a registry? What schemes are allowed and/or reasonable?
>
> Are there any required-to-support algorithms?
The URI is an identifier for the algorithm as specified in RFC4051 and 3275.
The draft is intentionally algorithm agile, meaning it references
algorithm identifiers from the listed RFCs and there are no
"required-to-support algorithms" as these will obviously evolve over
time and new ones may have to be developed and supported in the future
when current ones become weak.
> -- 4.1.1, 2nd paragraph: "those must be used as defined in [RFC3275] and [RFC4051]"
>
> Normative?
Yes normative. Corrected to MUST.
> -- 4.1.1, last paragraph:
>
> What do you mean by equal? The same algorithm? One of equal strength? How do you determine relative strength?
Corrected language. They must be the same digest algorithm. 
> -- 4.2.1, last paragraph: "The new ATS and its hash tree MUST use the same digest algorithm as the preceding one"
>
> Does this imply they can't change to a new algorithm? What if an algorithm becomes deprecated over time?
No it does not imply the digest algorithm can't be changed to a new one.
But to change the hash algorithm you must use the hash tree renewal
(section 4.2.2)

> -- 7, 1st paragraph: "have to be considered by verifying components"
>
> Normative?
Actually not. Because verifying components may use different criteria
to  determine which algorithm is considered secure. These can vary by
country and legislation, so it would be inappropriate to make this
normative.

> -- 7, 4th paragraph:
>
> should "recommended" and "must" be normative?
>
> Why different TSAs? Wouldn't different algorithms be good enough? Are you assuming a given TSA is limited to a single algorithm at a time?
Changed recommended to normative "RECOMMENDED".
And changed non-normative "must" to normative "SHOULD": because there
may theoretically be scenarios where redundancies still have value even
without hash algorithm redundancy or two different secure hash
algorithms may not be available.
Different TSAs are recommended, because there may be events when one TSA
(and all its keys) is compromised. In which case a redundant TSA would
help mitigate this risk. (on a personal side note: in practice different
TSAs are sometimes also needed because some of them do only offer a very
limited range of algorithms.)

> -- 7, last paragraph: "Time-Stamps should have the same or higher quality"
>
> Normative?
>
Yes, changed to normative.
> -Nits/editorial comments:
>
> -- General: The draft could really use another editing pass to check for punctuation errors and awkward style. There's lots of missing or misused commas, missing articles, passive voice that obscures actors, etc. It looks like sections were edited in isolation from each other, with redundant assertions (how many times do you need to open with "time stamps prove the existence of data at a particular time"), inconsistent use of acronyms, etc.  I will highlight some examples, but they are by no means exhaustive.
>
> Much of this could be handled by the RFC editor, but its best to minimize their work load, and better to minimize the opportunity for outside editors to misconstrue your meaning.
Regarding punctuation errors and style the AD advised to rely on the
editor for this in this case.
However, as you kindly outlined some of the vulnerable areas, I will
revisit each of them again and try to improve language there.

> -- General: The pagination and vertical spacing seem strange.
>
> -- Abstract : "This document specifies XML syntax and processing rules for creating evidence for long-term non- repudiation of existence of data."
>
> I assume this is for non-repudiation of more than just the "existence" of the data, right? Also, please expand the acronyms in the abstract.
expanded.
> -- section 1: "define XML Schema and processing rules for Evidence Record Syntax in XML format. The document is related to initial ASN.1 syntax"
>
> Missing articles. Also, since you use an acronym for this later, why not declare it here?
done: declared ASN.1 and XML.
> -- 1.1, first paragraph: "Such data and non-repudiable proof of existence must endure for long periods of time, even when information to prove data existence and integrity weakens or ceases to exist."
>
> That seems to say the proof must continue to exist past it's own existence. I assume that is not the intent.
corrected
> -- "digital signatures defined in [RFC5652] for example do not provide absolute reliability"
>
> Missing commas around "for example"
corrected
> -- 2nd paragraph: "All integrity and authenticity related techniques used today suffer from the same problem of time related reliability degradation including techniques for Time-Stamping, which are generally recognized as data existence and integrity proof mechanisms."
>
> I find it hard to parse that sentence. 
improved sentences structure. Will ask RFC Editor for further language
improvements
> -- "Some of the problems might not even be technically related like a decomposing Time-Stamping authority."
>
> Technically related to what? Do you mean to say "might not even be of a technical nature..."? Also, I'm not sure I understand "decomposing" in this context.
yes, changed and replaced "decomposing"

> -- 3rd paragraph: " introduced for example by"
>
> Missing commas
corrected
> -- "long term signature syntaxes like [RFC5126]"
>
> Missing words? (i.e. .... syntaxes like those defined in...)
corrected
> -- "Long term signature syntaxes and processing rules address mostly the long term endurance of digital signatures..."
>
> Seems self-redundant
corrected
> -- 4th paragraph:
>
> Please expand XMLERS on first mention. Also, this is not consistent with the acronym used in the abstract.
expanded
> -- 6th paragraph: "support for example import"
>
> commas
corrected
> -- section 1.2, first paragraph
>
> Multiple missing articles
corrected
> -- 3rd paragraph: "Evidence Record maintains a close relationship to Time-Stamping techniques"
>
> I doubt it "maintains" anything. It think you mean to say "is closely related to..."
corrected
> -- 1.2, 4th paragraph: "packed into a structure called a "hash tree""
>
> The text appears to be trying to introduce the concept of a "hash tree", but that's already been mentioned several times.
no change: yes it has been mentioned, but hash tree is one of the key
elements of XMLERS so it should be mentioned in the overview provided in
this section (1.2 general overview)
> -- 1.2, 5th paragraph: "collected evidence data must be monitored and renewed before such events occur"
>
> monitored by whom?
actually who monitors can vary with implementation (it could be the
system operator, user or a third party) so we did intentionally not
specify it here.
> -- 1.3, 2nd paragraph:
>
> "multitude" connotes a large number. I think you just mean "set". Also, why the parentheses?
corrected
> -- 1.3, definition of "canonicalization"
>
> This seems like a definition of "canonicalization rules". Wouldn't "canonicalization" refer to the act of following the rules, rather than the rules themselves?
>
> Also, the draft needs a definition for "canonical form"
unchanged: in this case I think the definition is appropriate and also
the term "canonical form" is sufficiently well known in XML terms, so
that it is not necessary to repeat definitions here. 
> -- section 2, first paragraph:
>
> It would be nice to have definitions of integrity and non-reputability in the terminology section. Maybe even "existence" as used in the context.
Not changed: I would prefer to not "over-define" in the terminology
section (as this can also reduce readability of the document). Words
like existence and integrity should be sufficiently clear.
> -- section 2, first paragraph: "unit of data, which is to be used"
>
> I think you mean "unit of data that is to be used"
corrected
> -- section 2, 1st paragraph: "Time-Stamp Tokens obtained from the Time-Stamping Authority (TSA)"
>
> Obtained by whom?
corrected
> -- section 2, 2nd paragraph "number of reasons"
>
> More than one example would be nice.
added one more reason
> -- 2.1, 1st paragraph: "CRLs or OCSP"
>
> Expand on first mention
expanded.
> -- 2.1, paragraph made up of "<CanonicalizationMethod> is a required element that specifies the canonicalization algorithm applied over the archive data in case of XML data objects, <ArchiveTimeStampSequence> or <TimeStamp> element prior to performing digest value calculations."
>
> Sentence does not make sense. Are therre missing words?
corrected
> -- 2.2, 3rd paragraph after numbered list: "the application not defined in this draft"
>
> I'm not sure what you mean. Is there a specific application defined elsewhere, or are you just trying to say it is out of scope?
corrected
> -- 2.2, 2nd to last paragraph:
>
> I'm not sure what this is an example of. It just looks like a continuation of the section text.
Corrected.
> -- "provide also evidence"
>
> also provide evidence
corrected
> -- 3.1.1, third to last paragraph "When a single Time-Stamp is obtained for a set of archive objects, a hash tree MUST be constructed to generate a single hash value to bind all archive objects from that group and then a reduced hash tree MUST be extracted from the hash tree for each archive object respectively (see Section 3.2.1)."
>
> Meaning obscured by passive voice. Who or what MUST generate and/or extract hash trees?
corrected to active voice
> -- 3.1.1, 2nd to last paragraph: "For example, the text value"
>
> Is this a second example, or a continuation of the previous one?
corrected
> -- 3.1.2, 1st paragraph "Since at the time being there is no standard"
>
> Won't is statement become false when this draft is published as an RFC?
No, because the draft defines the Evidence Record in XML, but the time
stamps are still not standardised in XML, only in ASN.1 (RFC3161).
> -- 3.1.2, paragraph before example: "in particular, e.g."
>
> "in particular" or "e.g", not both.
corrected
> -- 3.2.1, 2nd paragraph: "This is the case:"
>
> Confusing. Do you mean to say "The values are unequal when either of the following are true:"?
corrected
> -- 3.2.1, 1st bullet list entry "is having"
>
> has
corrected
> -- 3.2.1, paragraph before 2nd numbered list: "is built from bottom to the root."
>
> Leaves to the root, or bottom to top. Also, who builds it?
corrected, but kept passive voice in this case because who builds it is
not important.
> -- "The leaves represent the digest values of the archive objects:"
>
> It looks like you mean this sentence to introduce the following list, but it doesn't seem to do so.
corrected
> -- List entry 3: Need to define N. Is this the order of the tree?
corrected
> -- 3.3, list item 2: "If an additional proof is necessary that the Archive Time-Stamp relates to a data object group (e.g. a document and all its digital signatures), it can also be verified that only the hash values of the given data objects are in the first hash value list."
>
> I don't understand this sentence
corrected
> -- 3.3, numbered list:
>
> Is there a need to distinguish between kinds of negative results?
No. For the standard there is no need to distinguish between different
kinds of negative results. (Though a verification application may do
that, to give further detailed information to the user.)
> -- 4.1.2, last paragraph: "it is recommended to use c14n- 20010315."
>
> Reference?
corrected. was already listed in references, just added it to section 4.1.2
> -- 4.2 "Archive Time-Stamps have to be renewed "
>
> by whom?
put in active voice (LTA renews time-stamps)
> -- section 7, "Secure Algorithms", etc
>
> Should these be numbered subsections?
Ok. Introduced subsections in the security considerations section
> -- 7, 1st paragraph: "have to be considered by verifying components"
>
> They need to be considered by people, not components, right? Also, is this a verification issue or a generation issue?
corrected
> -- section 8, 1st paragraph: "namespace has been registered in the IANA XML Registry."
>
> It's already been registered, or are you instrucing IANA to register it? (repeats several times in section)
Yes, we instructed IANA to register it. And IANA has already responded
and listed that they understood the required actions.
> -- Appendix A, general:
>
> Why is this in an appendix? It seems central to the draft. lots of readers will stop reading when they get to the references sections.
>
>
>
In the last point I disagree. The appendix is the right place as it only
provides a summary list of the verification steps of 2.3., 3.3. and 4.3.
and how to bind it all together.


From jdfalk-lists@cybernothing.org  Tue Jan 11 15:46:07 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 73F883A6AC6 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 15:46:07 -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 4e89rv40aTpa for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 15:46:06 -0800 (PST)
Received: from ocelope.disgruntled.net (ocelope.disgruntled.net [97.107.131.76]) by core3.amsl.com (Postfix) with ESMTP id 4D7943A6806 for <ietf@ietf.org>; Tue, 11 Jan 2011 15:46:06 -0800 (PST)
Received: from [192.168.11.38] (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 p0BNmKdU026327 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Tue, 11 Jan 2011 15:48:23 -0800
X-DKIM: Sendmail DKIM Filter v2.6.0 ocelope.disgruntled.net p0BNmKdU026327
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybernothing.org; s=triac; t=1294789703; bh=UFXTej+UZ+ZCjcTN80r79J6q/wVf+GGF0yviC9XwR Zo=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date: Content-Transfer-Encoding:Message-Id:References:To; b=AhB7Qdr4mNqa ddXSaphGZhfXTHwaIDI6bPTxIQRImsYpsESlskhGa3rauc1kXNBcbh4w9lDa5yx4kmD 7x0trEOFonYAyA/b7X14n8xiVs+0dH3WmTa1AdnVcJX0Md5QD45B59nSev20VfExPtO m9fkI9wVp2szfAWOOddIfiazk=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Poster sessions
From: "J.D. Falk" <jdfalk-lists@cybernothing.org>
In-Reply-To: <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
Date: Tue, 11 Jan 2011 15:48:20 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <14CB397B-5B77-44F2-BC89-D46654D2E9AD@cybernothing.org>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>
To: IETF 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: Tue, 11 Jan 2011 23:46:07 -0000

On Jan 10, 2011, at 2:38 PM, Fred Baker wrote:

> I'm envisioning the process and requirements of the poster sessions. =
In terms of process, today if I post a -00 draft to a working group, I =
can generally get discussion during the coming IETF meeting. What I =
think this suggests is that instead I would show a poster at the coming =
meeting and get working group discussion the meeting following. I'm not =
sure I like that implication.

Ah, good point.  I'd been imagining that the poster time would be for =
drafts where there isn't already a WG working on 'em, or /maybe/ where =
the WG (or the author) feels there's a need for wider participation.

That's what I'd be excited to peruse, anyhow.


From sm@resistor.net  Tue Jan 11 17:07:55 2011
Return-Path: <sm@resistor.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 66E393A680B for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 17:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.293
X-Spam-Level: 
X-Spam-Status: No, score=-103.293 tagged_above=-999 required=5 tests=[AWL=-0.294, 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 vPkIZWi8NA0u for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 17:07:52 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id A26A73A6802 for <ietf@ietf.org>; Tue, 11 Jan 2011 17:07:52 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0C1A0Bc002142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 11 Jan 2011 17:10:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1294794609; x=1294881009; bh=lQGbAbatuoeHn/FuqMcc1213i59NE/nyi3bVIQZc/sY=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=uMB3rjs6KqWJXqk9QtssF0FT7vE3K+jfVXGzb6DpKvUlbArj1J93P5x2vgAZMU6DT z3BPJNrmIQnB8nAcOcKxXFg3UHeG4sEUdq2QaeFsnG+DWJmLKlpMjV+U+86WI+n3Cz hIy9jbCLxxDlo42mcysKI1Uh+ffMi0z53rp/Fx7g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1294794609; x=1294881009; bh=lQGbAbatuoeHn/FuqMcc1213i59NE/nyi3bVIQZc/sY=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=wszRcWNxUITBt4TVDYasYaAi0tZf4yzJ0MTZMjOW9JPG/yl2d+9ZYYEYB4ojvclFk EPAEd+5dN2QebDW4B89djsolblUr8f5gyjo0jy7O85o6ODv+h6xtP0j5keofpigmOM KpT+vs90GAVvKer+XJT1a8wsvY+rCACD1J/c9I+U=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=vXyM3RES+PtBsICWDOOdUcttWG90g4ki5FVKt3HAukDM4wamQH+waWm0h/PTR+jZT qhcLlvxhztGf+FGSLuf+5mD9vHwadD6zgz/zqQvrznf/Tj64zVIs6dUwEIZK69GA+YR uOvKaKJMJ5kiqH6edwAy9VRCvpwOvPNrIJF5xwM=
Message-Id: <6.2.5.6.2.20110111162923.08f3a598@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 11 Jan 2011 17:00:11 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call On draft-yevstifeyev-tn3270-uri-12
In-Reply-To: <003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net>
References: <4D23FFBA.5030804@gmail.com> <003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 12 Jan 2011 01:07:55 -0000

At 08:29 11-01-11, t.petch wrote:
>The provenance of the editor is unknown to
>me - and of course, once an RFC has been through the IETF processes,
>then the editorship is an irrelevance - but I am concerned that I have
>no awareness of the contact provided as the scheme 'Author/Change controller',
>no track record, no affiliation, a gmail address.  This seems more than
>discourtesy, this seems wrong.

There is a city and country mentioned under Author's Address.  It is 
not the first time an author uses a gmail address.  If an author is 
new to the IETF, he or she won't have any track record within the IETF.

According to the RFC Style Guide:

   "Contact information must include at least one, and ideally would
    include all, of a postal address, a telephone number and/or FAX
    number, and a long-lived email address.  The purpose of this section
    is to (1) unambiguously define author/contributor identity (e.g., the
    John Smith who works for FooBar Systems) and to (2) provide contact
    information for future readers who have questions or comments.  Note
    that some professional societies offer long-lived email addresses for
    their members."

Regards,
-sm 


From evnikita2@gmail.com  Tue Jan 11 23:34:56 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 670BF3A69CD for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 23:34:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.803
X-Spam-Level: 
X-Spam-Status: No, score=-3.803 tagged_above=-999 required=5 tests=[AWL=-0.804, BAYES_00=-2.599, J_CHICKENPOX_15=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 bAa0k4ONIXGA for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 23:34: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 43F543A69B0 for <ietf@ietf.org>; Tue, 11 Jan 2011 23:34:55 -0800 (PST)
Received: by gxk28 with SMTP id 28so128117gxk.31 for <ietf@ietf.org>; Tue, 11 Jan 2011 23:37:14 -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=9NSFEVHHd6cfMRXHOK5CqaSca/0IZbLb0w03E6A5KKg=; b=APwf4JXOudKbIMqZU9qq/+EpI5Z4PHekfNFdpjbqLI2Kub9WExyZmTuQ1uW7kG1TyB mX/XwTVlY/ZhcSpkJpn2ilok5Nt8MOpHuId2quArnuF4u058OAVDhEqqNqU2qHCLLNTP uoOwJLawwzlPcOkNqTU0ND7Qf4aygA4RK0Fk0=
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=LWFm6wEMSMi+DJExODBqnsNVtyGrfVTtuZNXgmSx53bKDkp6u8aIwNiy0pdjFH8w/u mhFEuOq7suRYbtphEJxFZ0pxlSnjRO7NX7MsBpHKso3mvfAC19ZdKZLmN5z9VvKy+Rem 9nQGVSU6MM3/ZAz0CwxUJmTL0FFfiNqfzUA3o=
MIME-Version: 1.0
Received: by 10.151.84.11 with SMTP id m11mr1425324ybl.212.1294817832257; Tue, 11 Jan 2011 23:37:12 -0800 (PST)
Received: by 10.150.53.6 with HTTP; Tue, 11 Jan 2011 23:37:12 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20110111162923.08f3a598@resistor.net>
References: <4D23FFBA.5030804@gmail.com> <003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110111162923.08f3a598@resistor.net>
Date: Wed, 12 Jan 2011 09:37:12 +0200
Message-ID: <AANLkTik0WFRyWgJT=V=1pSoZXAqurewAHbPD1EOTm8W2@mail.gmail.com>
Subject: Re: Last Call On draft-yevstifeyev-tn3270-uri-12
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
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, 12 Jan 2011 07:34:56 -0000

Dear all,

I think that if there is an objetion of many people, that would be OK
if we put the IETF as author and IESG as contact.  This, I think, will
be considered as appropriate for this ocasion.

Moreover, if I do not want to provide my contact data except email to
the community, that is my right, anyway.

All the best,
Mykyta Yevstifeyev

2011/1/12, SM <sm@resistor.net>:
> At 08:29 11-01-11, t.petch wrote:
>>The provenance of the editor is unknown to
>>me - and of course, once an RFC has been through the IETF processes,
>>then the editorship is an irrelevance - but I am concerned that I have
>>no awareness of the contact provided as the scheme 'Author/Change
>> controller',
>>no track record, no affiliation, a gmail address.  This seems more than
>>discourtesy, this seems wrong.
>
> There is a city and country mentioned under Author's Address.  It is
> not the first time an author uses a gmail address.  If an author is
> new to the IETF, he or she won't have any track record within the IETF.
>
> According to the RFC Style Guide:
>
>    "Contact information must include at least one, and ideally would
>     include all, of a postal address, a telephone number and/or FAX
>     number, and a long-lived email address.  The purpose of this section
>     is to (1) unambiguously define author/contributor identity (e.g., the
>     John Smith who works for FooBar Systems) and to (2) provide contact
>     information for future readers who have questions or comments.  Note
>     that some professional societies offer long-lived email addresses for
>     their members."
>
> Regards,
> -sm
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From hannes.tschofenig@gmx.net  Tue Jan 11 23:49:15 2011
Return-Path: <hannes.tschofenig@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 8FC8B3A6B08 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 23:49:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.506
X-Spam-Level: 
X-Spam-Status: No, score=-103.506 tagged_above=-999 required=5 tests=[AWL=1.093, BAYES_00=-2.599, GB_I_INVITATION=-2, 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 8hMfYezsERO1 for <ietf@core3.amsl.com>; Tue, 11 Jan 2011 23:49:14 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 874BC3A69C2 for <ietf@ietf.org>; Tue, 11 Jan 2011 23:49:13 -0800 (PST)
Received: (qmail invoked by alias); 12 Jan 2011 07:51:31 -0000
Received: from unknown (EHLO [10.255.136.70]) [192.100.123.77] by mail.gmx.net (mp033) with SMTP; 12 Jan 2011 08:51:31 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+6eQJSfnm6sT+jA+t59JB22rwUdctNhCHiS4vIis EPC+mAxF0P9lQi
Subject: **Tutorial** on "Interconnecting Smart Objects with the Internet" 
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=windows-1252
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <20110111185038.DC9FE3A6A7E@core3.amsl.com>
Date: Wed, 12 Jan 2011 09:51:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <90A5770E-B66E-43A8-A879-D72FE091C422@gmx.net>
References: <20110111185038.DC9FE3A6A7E@core3.amsl.com>
To: IETF Announcement list <ietf-announce@ietf.org>, IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 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, 12 Jan 2011 07:49:15 -0000

Hi all,=20

In case you have not read through the announcement text I wanted to draw =
your attention to the tutorial day (Saturday, 26th March 2011) that is =
attached to the workshop. =20

The tutorials are open for everyone BUT there are two constraints:

1) We have to limit the number of participants (because of the size of =
the available room)

2) You need to put your name on a list. Deadline is 11th February 2011.
The registration page is: http://www.doodle.com/xarbbx7b4cah9wfn

Hence, if you are not quick enough you may not be able to attend the =
workshop.=20

More information about the tutorial, including a preliminary agenda, can =
be found at:=20
http://www.iab.org/about/workshops/smartobjects/tutorial.html

Ciao
Hannes

PS: We are still looking for sponsors. It would be nice to offer coffee =
& refreshments during the day to the participants, for example.=20

On Jan 11, 2011, at 8:50 PM, IETF Secretariat wrote:

> The Internet Architecture Board and the IETF Internet Area will hold a
> workshop on the Friday, 25th March 2011 in Prague on the topic:
>=20
> "Interconnecting Smart Objects with the Internet"
>=20
> Attached to this workshop is a tutorial day on the same topic on
> Saturday, 26th March 2011. Please find more information about it at:
> http://www.iab.org/about/workshops/smartobjects/tutorial.html
>=20
> - Background
>=20
> Today's Internet is experienced by users as a set of applications, =
such
> as email, instant messaging, and social networks. While these =
applications
> do not require users to be present at the time of service execution in
> many cases they are. There are also substantial differences in =
performance
> between the various end devices, but in general end devices =
participating
> in the Internet are considered to have high performance.
>=20
> As we move forward with the interconnection of all kinds of devices =
via
> the Internet, these characteristics will change. The term "Internet of
> Things" denotes a trend where a large number of devices benefit from
> communication services that use Internet protocols. Many of these =
devices
> are not directly operated by humans, but exist as components in =
buildings,
> vehicles, and the environment. There will be a lot of variation in the
> computing power, available memory, and communications bandwidth =
between
> different types of devices.
>=20
> Many of these devices provide new services or provide more value for
> previously unconnected devices. Some devices have been connected in
> various legacy ways in the past but are now migrating to the use of =
the
> Internet Protocol, sharing the same communications medium between all
> applications and enabling rich communications services.
>=20
> Much of this development can simply run on existing Internet =
protocols.
> For instance, home entertainment and monitoring systems often offer a =
web
> interface to the end user. In many cases the new, constrained =
environments
> can benefit from additional protocols that help optimize the
> communications and lower the computational requirements. Examples of
> standardization efforts targeted for these environments include the
> "Constrained RESTful Environments (CoRE)", IPv6 over Low power WPAN
> (6LoWPAN)", and Routing Over Low power and Lossy networks (ROLL)" =
working
> groups at the IETF.
>=20
> This workshop aims to explore the experience and approaches taken by
> researchers and developers of Internet technology, when considering =
the
> characteristics of constrained devices. Engineers know that many =
design
> considerations need to be taken into account when developing protocols =
and
> architecture. Balancing between the conflicting goals of computing
> performance, code size, economical incentives, and security is often
> difficult, as illustrated by Clark, et al. in "Tussle in Cyberspace:
> Defining Tomorrow's Internet", see
> http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle2002.pdf
>=20
> This workshop aims to discuss the experience and approaches taken when
> designing protocols and architectures for interconnecting smart =
objects to
> the Internet. To frame the discussion we suggest, as examples, to
> investigate the area of integration in the following categories:
> * Scalability
> * Power efficiency
> * Interworking between different technologies and network domains
> * Usability and manageability
> * Security and Privacy
>=20
> The goal of the IETF is "to make the Internet work better" and the
> workshop organizers are interested in receiving contributions that =
support
> this goal. Results may lead to guidelines and recommendations, =
proposals
> for new standards development, start of new research activities, and =
the
> documentation of best current practices regarding implementation and
> configuration.
>=20
> - Workshop Style
>=20
> The workshop=82s main focus will be on the discussions of technical =
topics.
> (This is not a mini-conference where every author just briefly talks =
about
> their papers.)
>=20
> In order to keep the group at a manageable size, participants are
> required to submit a position paper as an expression of interest.
> Submitters of accepted position papers will be invited to attend the
> workshop. Active participation will be expected.
>=20
> The workshop will be structured as a series of working sessions
> punctuated by invited speakers who will present relevant background
> information or controversial ideas that help participants reach a =
deeper
> understanding of the subject. The organizing committee may ask =
submitters
> of particularly salient papers to present their ideas and experiences =
at
> the workshop. For each slot, there will be one or two invited
> controversial speakers, and group work on the problem that=82s =
identified,
> hopefully reaching either a deeper understanding of the problem or =
some
> means of approaching it.
>=20
> - Important Dates
>=20
> Position papers must be submitted at latest February, 11th, 2011. =
Note:
> An early submission allows us to provide you feedback!
>=20
> Submitted position papers will be reviewed immediately by the program
> organizers and an invitation to the workshop will be sent to one of =
the
> paper authors. At the latest, invitations will be distributed by =
February,
> 25th.
>=20
> This one-day workshop will take place on Friday, 25th March, 2011, =
right
> before the 80th IETF meeting in Prague, which starts on Sunday, 27th
> March. Independent of this workshop but relevant for the participants, =
are
> tutorial events on Saturday, 26th March 2011. These tutorials will =
focus
> on ongoing IETF efforts related to the IETF CoRE, ROLL, and 6LoWPAN
> working groups. More details can be found at:
>=20
> - Position Paper Requirements
>=20
> Interested parties must submit a brief contribution describing their =
work
> or approach, as it relates to the workshop theme. We welcome visionary
> ideas for how to tackle the integration of constrained devices, as =
well as
> write-ups of deployment experience, and lessons-learned from =
successful or
> failed attempts at integrating these constrained devices with the
> Internet. Contributions are not required to be original in content.
>=20
> We solicit brief write-ups with 1 to 3 pages, formatted in HTML, PDF, =
or
> plain text (for example as a submitted Internet Draft). We encourage =
paper
> authors to limit themselves on the most important challenge. A focused
> message will be key! Accepted position papers will be published (in
> addition to meeting minutes, slides, and a workshop report).
>=20
> Please send your position paper to iot-workshop-prep@lists.i1b.org.
>=20
> - Venue
>=20
> The planned date and location for the workshop is Friday, March 25th, =
in
> Prague. Details about the meeting venue will be provided to the =
invited
> workshop participants. During the breaks coffee and tea will be =
served.
>=20
> There are no plans for remote participation. Minutes of discussions =
will
> be available, and offers to organize audio recording would be gladly
> appreciated.
>=20
> - Workshop Organizers
>=20
> We look forward to your input. The workshop organizers are Jari Arkko
> (Internet Area Director), Hannes Tschofenig (IAB), Bernard Aboba =
(IAB),
> Carsten Bormann (CoRE and 6LoWPAN WG Chair), David Culler (ROLL WG =
Chair),
> Lars Eggert (Transport Area Director, and upcoming IRTF Chair), JP =
Vasseur
> (ROLL WG Chair), Stewart Bryant (Routing Area Director), Adrian Farrel
> (Routing Area Director), Ralph Droms (Internet Area Director), =
Geoffrey
> Mulligan (6LoWPAN WG Chair), Alexey Melnikov (Applications Area =
Director),
> Peter Saint-Andre (Applications Area Director), Marcelo Bagnulo (IAB),
> Zach Shelby (Smart Power Directorate), Isidro Ballesteros Laso =
(European
> Commission), Fred Baker (Member of the Smart Power Directorate and =
liaison
> to the US Smart Grid Interoperability Panel - SGIP).
>=20
> Up-to-date information about the workshop is available at:
> http://www.iab.org/about/workshops/smartobjects/
>=20
> Feel free to contact us at iot-workshop-prep@lists.i1b.org.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From evnikita2@gmail.com  Wed Jan 12 01:22:15 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 5C93728C0D6 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 01:22:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.073
X-Spam-Level: 
X-Spam-Status: No, score=-4.073 tagged_above=-999 required=5 tests=[AWL=-0.474, 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 N6xtGk03A5uB for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 01:22:14 -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 7484C3A6A02 for <ietf@ietf.org>; Wed, 12 Jan 2011 01:22:14 -0800 (PST)
Received: by yxt33 with SMTP id 33so161100yxt.31 for <ietf@ietf.org>; Wed, 12 Jan 2011 01:24:33 -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:cc :content-type; bh=rPTiRH4NzfWG+trNKKHSlJPg04S2HMmefzaeyILU48U=; b=knvdO3JRjNrDCb9Qvi857DypPNxRdUby5ABEJmGzOlLZ9CdLRW0+lSK6iI/TfMDXuJ pvUtw7haImb06OMikElyS9/m9OLFhcFswnvJQHj+FtZ/eEII6HB4FB0K1KCc3F2O6K0G XhRdJZwX5Xvfu07A2dcYonZcdCbiQIZyuGmYY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=x6C+wgUexAZj4yaiC/ua+2sTJa5Mf1TkRLH8UPKRK0gDmPxsgoh284KttoSCnonFxh xQsXVk3lY8NzpxH9T6es2wpYXqzq70XNVhO8UgG3TWby5HHECoTjGKk0iBlVhFPKS7hD rrhCADTGXjAXxmqZLyi5V8nUc4a6O0uTJxb14=
MIME-Version: 1.0
Received: by 10.151.84.11 with SMTP id m11mr1535702ybl.212.1294824273273; Wed, 12 Jan 2011 01:24:33 -0800 (PST)
Received: by 10.150.53.6 with HTTP; Wed, 12 Jan 2011 01:24:33 -0800 (PST)
Date: Wed, 12 Jan 2011 11:24:33 +0200
Message-ID: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
Subject: Last Call on draft-ietf-pim-registry-03.txt
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: The IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: stig@cisco.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, 12 Jan 2011 09:22:15 -0000

Hello all,

I am writing to provide some review on the draft-ietf-pim-registry,
that is currently in Last Call,

Furstly, this document does not explain the abreviatures once they has
appeared in the title, abstract and main text.

Moreover, the initial contents of the regsitry does not mention that
values that are Unassigned.  What is more, the document does not have
clear regsitry format description, eg. Message Type - an integer,
values from 0 to 15 are assigned etc.  I propose to create the
separate section and name it 'Regsitry Description' and place a number
of sub-section tehre that would describe the regsutry as detailed as
possible.  And in this occasion out the follwoing IANA Considerations'
Section:

'IANA is asked to create the 'name' regsitry following Section 2 of
this document."

So I recommend not to publih this document in the current view, stop
the Last Call, if posible, and work on it a bit more.

All the best,
Mykyta Yevstifeyev

From daedulus@btconnect.com  Wed Jan 12 01:52:03 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 152C628C0F5 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 01:52:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=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 7KBorp5deo2W for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 01:52:02 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by core3.amsl.com (Postfix) with ESMTP id EC3E928C0D8 for <ietf@ietf.org>; Wed, 12 Jan 2011 01:52:00 -0800 (PST)
Received: from host217-44-202-158.range217-44.btcentralplus.com (HELO pc6) ([217.44.202.158]) by c2bthomr09.btconnect.com with SMTP id BIT17942; Wed, 12 Jan 2011 09:54:18 +0000 (GMT)
Message-ID: <009501cbb235$d5a0ff20$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <ietf@ietf.org>, "SM" <sm@resistor.net>
References: <4D23FFBA.5030804@gmail.com><003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110111162923.08f3a598@resistor.net>
Subject: Re: Last Call On draft-yevstifeyev-tn3270-uri-12
Date: Wed, 12 Jan 2011 09:50:48 +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.4D2D7A46.00B9, actions=tag
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4D2D7A4B.0206,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
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, 12 Jan 2011 09:52:03 -0000

----- Original Message -----
From: "SM" <sm@resistor.net>
To: <ietf@ietf.org>
Sent: Wednesday, January 12, 2011 2:00 AM

> At 08:29 11-01-11, t.petch wrote:
> >The provenance of the editor is unknown to
> >me - and of course, once an RFC has been through the IETF processes,
> >then the editorship is an irrelevance - but I am concerned that I have
> >no awareness of the contact provided as the scheme 'Author/Change
controller',
> >no track record, no affiliation, a gmail address.  This seems more than
> >discourtesy, this seems wrong.
>
> There is a city and country mentioned under Author's Address.  It is
> not the first time an author uses a gmail address.  If an author is
> new to the IETF, he or she won't have any track record within the IETF.
>
> According to the RFC Style Guide:
>
>    "Contact information must include at least one, and ideally would
>     include all, of a postal address, a telephone number and/or FAX
>     number, and a long-lived email address.  The purpose of this section
>     is to (1) unambiguously define author/contributor identity (e.g., the
>     John Smith who works for FooBar Systems) and to (2) provide contact
>     information for future readers who have questions or comments.  Note
>     that some professional societies offer long-lived email addresses for
>     their members."

True, but not relevant to the point I am making.

This is a provisional registration of an URI scheme (for which a provisional
registration already exists in IANA) so it is the rules of  RFC4395 which apply.

Except that they do not appear to cater for re-registration of a provisional
scheme.

The nearest would appear to be
"   o  Contact information identifying the person supplying the
      registration is included.  Previously unregistered URI schemes
      discovered in use may be registered by third parties on behalf of
      those who created the URI scheme; in this case, both the
      registering party and the scheme creator SHOULD be identified."

and it is the complete lack of the original scheme creator that
concerns me.  Yes we have contact details for the third party
but that is not enough.

Tom Petch

> Regards,
> -sm


From Adrian.Farrel@huawei.com  Wed Jan 12 05:23:43 2011
Return-Path: <Adrian.Farrel@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 E91823A6B27 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 05:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.556
X-Spam-Level: 
X-Spam-Status: No, score=-103.556 tagged_above=-999 required=5 tests=[AWL=-0.957, 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 fWlAJ2YHRPx1 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 05:23:43 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 8657B28C0E9 for <ietf@ietf.org>; Wed, 12 Jan 2011 05:23:42 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEW008A9VZDR8@usaga01-in.huawei.com> for ietf@ietf.org; Wed, 12 Jan 2011 05:26:01 -0800 (PST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LEW004JSVZBF0@usaga01-in.huawei.com> for ietf@ietf.org; Wed, 12 Jan 2011 05:26:01 -0800 (PST)
Date: Wed, 12 Jan 2011 13:25:59 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
Subject: RE: Last Call on draft-ietf-pim-registry-03.txt
In-reply-to: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
To: 'Mykyta Yevstifeyev' <evnikita2@gmail.com>, 'The IETF' <ietf@ietf.org>
Message-id: <01bc01cbb25c$41590700$c40b1500$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AQKkr0ca3wjOiQC5JrjJaFD3Dw+ep5IbVd4A
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
Cc: stig@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.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, 12 Jan 2011 13:23:44 -0000

Hi Mykyta,

> I am writing to provide some review on the draft-ietf-pim-registry,
> that is currently in Last Call,

Many thanks for reviewing.

> Furstly, this document does not explain the abreviatures once they has
> appeared in the title, abstract and main text.

Good catch. It looks like a number of the acronyms we expected to be
"well-known" are not.
I find:
PIM
RFC (wow, that is a real surprise)

On the other hand, some *are* well-known and don't need to be expanded:
IANA
IGMP
IETF

For reference, see
http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
 
> Moreover, the initial contents of the regsitry does not mention that
> values that are Unassigned. 

Yeah, probably worth adding an entry...

11-14  Unassigned

>  What is more, the document does not have
> clear regsitry format description, eg. Message Type - an integer,
> values from 0 to 15 are assigned etc.  I propose to create the
> separate section and name it 'Regsitry Description' and place a number
> of sub-section tehre that would describe the regsutry as detailed as 
> possible. 

You are right. The description of the Message Type should be included. In
particular the range is very important.
This should be added to the end of the paragraph in Section 3.

> And in this occasion out the follwoing IANA Considerations'
> Section:
> 
> 'IANA is asked to create the 'name' regsitry following Section 2 of
> this document."

I am not sure what your suggestion is here. Section 3 begins with exactly this
request (using different words).
 
> So I recommend not to publih this document in the current view,

Agreed. Thanks for catching these issues which can be fixed.

> stop
> the Last Call, if posible, and work on it a bit more.

No, I don't think so. 
The purpose of a last call is not necessarily to have everyone agree that a
document is perfect. The purpose is to catch exactly the type of issue you have
raised.

I do not believe that your input here (which *is* valuable) results in changes
to the I-D that make a fundamental difference to the document that would
necessitate a further last call.

Thanks,
Adrian


From julian.reschke@gmx.de  Wed Jan 12 05:55:52 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 03C013A6B2F for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 05:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.237
X-Spam-Level: 
X-Spam-Status: No, score=-104.237 tagged_above=-999 required=5 tests=[AWL=-1.638, 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 PBLIOtDhEZdu for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 05:55:51 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id C05473A6B27 for <ietf@ietf.org>; Wed, 12 Jan 2011 05:55:50 -0800 (PST)
Received: (qmail invoked by alias); 12 Jan 2011 13:58:08 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp024) with SMTP; 12 Jan 2011 14:58:08 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/KsRkcD0bKZQxSQ/OW1vaprTASaYJzqfhF2VDeXx 98JaVKsMUcq9fO
Message-ID: <4D2DB36C.7070107@gmx.de>
Date: Wed, 12 Jan 2011 14:58:04 +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: Adrian.Farrel@huawei.com
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com>
In-Reply-To: <01bc01cbb25c$41590700$c40b1500$@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: 'The IETF' <ietf@ietf.org>, stig@cisco.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, 12 Jan 2011 13:55:52 -0000

On 12.01.2011 14:25, Adrian Farrel wrote:
> ...
>> Moreover, the initial contents of the regsitry does not mention that
>> values that are Unassigned.
>
> Yeah, probably worth adding an entry...
>
> 11-14  Unassigned
> ...

My understanding was that if something isn't registered then it's 
unassigned. When did we start to list those in a registry?

 > ...

Best regards, Julian

From Adrian.Farrel@huawei.com  Wed Jan 12 06:20:28 2011
Return-Path: <Adrian.Farrel@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 134F028C11A for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 06:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.557
X-Spam-Level: 
X-Spam-Status: No, score=-105.557 tagged_above=-999 required=5 tests=[AWL=1.042, 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 JjAM3kYNVT9T for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 06:20:26 -0800 (PST)
Received: from usaga03-in.huawei.com (usaga03-in.huawei.com [206.16.17.220]) by core3.amsl.com (Postfix) with ESMTP id CACC328C0E8 for <ietf@ietf.org>; Wed, 12 Jan 2011 06:20:26 -0800 (PST)
Received: from huawei.com (usaga03-in [172.18.4.17]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LEW00L50YLY1M@usaga03-in.huawei.com> for ietf@ietf.org; Wed, 12 Jan 2011 08:22:46 -0600 (CST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LEW00IATYLWMR@usaga03-in.huawei.com> for ietf@ietf.org; Wed, 12 Jan 2011 08:22:46 -0600 (CST)
Date: Wed, 12 Jan 2011 14:22:44 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
Subject: RE: Last Call on draft-ietf-pim-registry-03.txt
In-reply-to: <4D2DB36C.7070107@gmx.de>
To: 'Julian Reschke' <julian.reschke@gmx.de>
Message-id: <01da01cbb264$2f1462d0$8d3d2870$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AQKkr0ca3wjOiQC5JrjJaFD3Dw+epwKlsayuANzo8E6R/1P5oA==
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de>
Cc: 'The IETF' <ietf@ietf.org>, stig@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.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, 12 Jan 2011 14:20:28 -0000

Entirely at random I clicked on:

http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
http://www.iana.org/assignments/calipso/calipso.xhtml
http://www.iana.org/assignments/lmp-parameters

Looks like IANA tries to fill up all the blanks with markers of "unassigned".

Is that harmful?

Adrian

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: 12 January 2011 13:58
> To: Adrian.Farrel@huawei.com
> Cc: 'Mykyta Yevstifeyev'; 'The IETF'; stig@cisco.com
> Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
> 
> On 12.01.2011 14:25, Adrian Farrel wrote:
> > ...
> >> Moreover, the initial contents of the regsitry does not mention that
> >> values that are Unassigned.
> >
> > Yeah, probably worth adding an entry...
> >
> > 11-14  Unassigned
> > ...
> 
> My understanding was that if something isn't registered then it's
> unassigned. When did we start to list those in a registry?
> 
>  > ...
> 
> Best regards, Julian


From julian.reschke@gmx.de  Wed Jan 12 06:33:40 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 9CF743A6B30 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 06:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.22
X-Spam-Level: 
X-Spam-Status: No, score=-104.22 tagged_above=-999 required=5 tests=[AWL=-1.621, 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 AUgg8F8cnsRE for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 06:33:39 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id D003228C0E8 for <ietf@ietf.org>; Wed, 12 Jan 2011 06:33:37 -0800 (PST)
Received: (qmail invoked by alias); 12 Jan 2011 14:35:56 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp059) with SMTP; 12 Jan 2011 15:35:56 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1++8wsqmxm+v8HXNbz0qzLaSesyKY2sutJ11BhkpV ZYs9KpOPol0jLw
Message-ID: <4D2DBC48.2080302@gmx.de>
Date: Wed, 12 Jan 2011 15:35: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: Adrian.Farrel@huawei.com
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de> <01da01cbb264$2f1462d0$8d3d2870$@huawei.com>
In-Reply-To: <01da01cbb264$2f1462d0$8d3d2870$@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: 'The IETF' <ietf@ietf.org>, stig@cisco.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, 12 Jan 2011 14:33:40 -0000

On 12.01.2011 15:22, Adrian Farrel wrote:
> Entirely at random I clicked on:
>
> http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
> http://www.iana.org/assignments/calipso/calipso.xhtml
> http://www.iana.org/assignments/lmp-parameters
>
> Looks like IANA tries to fill up all the blanks with markers of "unassigned".
>
> Is that harmful?

Minimally, it's redundant. Also, it only makes sense on certain types of 
registries.

I just checked the XML version of the first registry, and, indeed, it 
contains entries for unassigned values. /me shakes head in disbelief.

What *should* be done is computing the unassigned ranges for 
*presentation*; that is, they should not be part of the actual registry. 
The way it's done currently defeats one of the reasons of having a 
machine-readable registry (consumers will have to hard-wire knowledge of 
the specific "unassigned" entry to make sense of the registry).

Best regards, Julian


From elwynd@dial.pipex.com  Wed Jan 12 09:06:47 2011
Return-Path: <elwynd@dial.pipex.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 412093A6B3F; Wed, 12 Jan 2011 09:06:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.348
X-Spam-Level: 
X-Spam-Status: No, score=-102.348 tagged_above=-999 required=5 tests=[AWL=0.251, 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 jYaJ-d+gUmBX; Wed, 12 Jan 2011 09:06:46 -0800 (PST)
Received: from auth.a.painless.aaisp.net.uk (a.painless.aaisp.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by core3.amsl.com (Postfix) with ESMTP id D75C13A6A4A; Wed, 12 Jan 2011 09:06:45 -0800 (PST)
Received: from 250.254.187.81.in-addr.arpa ([81.187.254.250]) by a.painless.aaisp.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1Pd4By-0007H7-QG; Wed, 12 Jan 2011 17:09:02 +0000
Subject: Gen-art review of draft-lear-iana-timezone-database-01
From: Elwyn Davies <elwynd@dial.pipex.com>
To: General Area Review Team <gen-art@ietf.org>
Content-Type: text/plain
Date: Wed, 12 Jan 2011 17:10:16 +0000
Message-Id: <1294852216.17554.17972.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: draft-lear-iana-timezone-database.all@tools.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, 12 Jan 2011 17:06:47 -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-lear-iana-timezone-database-01.txt
Reviewer: Elwyn Davies
Review Date: 11 January 2010
IETF LC End Date: 11 January 2011
IESG Telechat date: (if known)

Summary:
This document is not quite ready for the IESG.  The appeals process (if
there is to be one) needs to clarified as it currently points indirectly
to a hole in RFC 5226. As explained below, I have a feeling that it
would be wise to avoid tying the processes in this document to the
Designated Expert processes in RFC 5226 despite the similarities.
Making it clear what does apply and what doesn't is probably more work
than doing it from scratch in this document, especially given the hole
in RFC 5226.

Major(ish) issue:
s4: 
> As RFC-5226 states, the IESG is not a
>    normal avenue for appeals of specific decisions of the coordinator,
>    but rather a last resort when a coordinator is thought not to be
>    functioning in an appropriate way.

I think the draft should make it explicit that it is referring to the
'Designated Expert' sections in RFC 5226 here if it continues to
reference RFC 5226 - although there is a clear relationship with
Designated Experts, the differences between the selection process and
the operations of the TZ Coordinator and generic Deisgnated Experts may
mean that citing RFC 5226 might lead to legalistic disputes about which
set of rules applies.  Also, I am unable to find statements in RFC 5226
backing up the sentence above.  Regrettably, RFC 5226 appears
effectively to have a 'dsngling reference' in this area. Section 3.2,
para 3 of RFC 5226 points at Section 5.2 which (allegedly) discusses
'disputes and appeals in more detail'.  However s5.2 is titled 'Updating
Registrations' and says nothing about appeals and disputes.  Section 7
of RFC 5226 covers appeals of IANA decisions but says nothing specific
about appealing designated expert rulings.  I think this area may need a
little more work.  Overall, my inclination would be to make this a
standalone document that does not try to partially modify the RFC 5226
Designated Expert process and operations.  Appeals... >*sigh*<.  

Minor Issue:
s3, para 3: Is it intended that that the supporting info should also be
signed?  If so the order of the phrases should be reversed.


Nits/Editorial:
s3:  'tar files' is jargon. s/tar files/archive files/ maybe adding "in
the format used by the 'tar' program".

s4, last para: s/may/MAY/
s4, last para: 'OR MORE' - this isn't RFC 2119 language - is there any
real need for capitalization?

s5: The three instances of 'shall' ought to to be RFC 2119 terms:
s/No change shall be made to licenses, where they exist./Licenses, where
they exist SHALL NOT be changed./
s/IANA shall allow for the downloading of this reference code.  The
reference implementation shall be distributed/IANA SHALL allow for the
downloading of this reference code.  The reference implementation SHALL
be distributed.../

s7: Arguably the various 'will's and 'may' in the later part of the
section (from 'The IANA will provide' onwards) should be capitalised as
RFC 2119 requirements: s/will/SHALL/ (5 places) and s/may/MAY/.


From stig@venaas.com  Wed Jan 12 09:32:32 2011
Return-Path: <stig@venaas.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 A76503A6A53 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 09:32:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.317
X-Spam-Level: 
X-Spam-Status: No, score=-102.317 tagged_above=-999 required=5 tests=[AWL=0.283, 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 xPJYZdDQuBZE for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 09:32:31 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by core3.amsl.com (Postfix) with ESMTP id 65E3A3A68E2 for <ietf@ietf.org>; Wed, 12 Jan 2011 09:32:31 -0800 (PST)
Received: from [IPv6:2001:420:4:ea0c:d40c:38b5:7951:601d] (unknown [IPv6:2001:420:4:ea0c:d40c:38b5:7951:601d]) by ufisa.uninett.no (Postfix) with ESMTPSA id 983798018; Wed, 12 Jan 2011 18:34:49 +0100 (CET)
Message-ID: <4D2DE632.6000506@venaas.com>
Date: Wed, 12 Jan 2011 09:34:42 -0800
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Adrian.Farrel@huawei.com
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com>
In-Reply-To: <01bc01cbb25c$41590700$c40b1500$@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 12 Jan 2011 17:32:32 -0000

On 1/12/2011 5:25 AM, Adrian Farrel wrote:
> Hi Mykyta,
>
>> I am writing to provide some review on the draft-ietf-pim-registry,
>> that is currently in Last Call,
>
> Many thanks for reviewing.
>
>> Furstly, this document does not explain the abreviatures once they has
>> appeared in the title, abstract and main text.
>
> Good catch. It looks like a number of the acronyms we expected to be
> "well-known" are not.
> I find:
> PIM
> RFC (wow, that is a real surprise)

PIM is also in the list. The only one missing is RFC. Which indeed is
a surprise :) I can expand that if you want me to. Or we can leave it
to the RFC-Editor to decide?

> On the other hand, some *are* well-known and don't need to be expanded:
> IANA
> IGMP
> IETF
>
> For reference, see
> http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>
>> Moreover, the initial contents of the regsitry does not mention that
>> values that are Unassigned.
>
> Yeah, probably worth adding an entry...
>
> 11-14  Unassigned

I find it a bit superfluous, but I can certainly do that. Just so it's
clear that nothing may have been omitted.

>>   What is more, the document does not have
>> clear regsitry format description, eg. Message Type - an integer,
>> values from 0 to 15 are assigned etc.  I propose to create the
>> separate section and name it 'Regsitry Description' and place a number
>> of sub-section tehre that would describe the regsutry as detailed as
>> possible.
>
> You are right. The description of the Message Type should be included. In
> particular the range is very important.
> This should be added to the end of the paragraph in Section 3.

I agree. The document notes in the introduction that its 4 bits, but it
should be as part of the registry. Once the last call is ended I'll
do a new version where I point this out.

Stig

>> And in this occasion out the follwoing IANA Considerations'
>> Section:
>>
>> 'IANA is asked to create the 'name' regsitry following Section 2 of
>> this document."
>
> I am not sure what your suggestion is here. Section 3 begins with exactly this
> request (using different words).
>
>> So I recommend not to publih this document in the current view,
>
> Agreed. Thanks for catching these issues which can be fixed.
>
>> stop
>> the Last Call, if posible, and work on it a bit more.
>
> No, I don't think so.
> The purpose of a last call is not necessarily to have everyone agree that a
> document is perfect. The purpose is to catch exactly the type of issue you have
> raised.
>
> I do not believe that your input here (which *is* valuable) results in changes
> to the I-D that make a fundamental difference to the document that would
> necessitate a further last call.
>
> Thanks,
> Adrian
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From tme@americafree.tv  Wed Jan 12 09:35:32 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 BD30F28C12C for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 09:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.245
X-Spam-Level: 
X-Spam-Status: No, score=-102.245 tagged_above=-999 required=5 tests=[AWL=0.354, 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 q8z0sOXQHqrM for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 09:35:31 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id AECE628C133 for <ietf@ietf.org>; Wed, 12 Jan 2011 09:35:31 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 8ABD29A31D62 for <ietf@ietf.org>; Wed, 12 Jan 2011 12:37:51 -0500 (EST)
From: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: World IPv6 Day
Date: Wed, 12 Jan 2011 12:37:48 -0500
Message-Id: <8D428F38-CA31-4EAB-9873-2166D2639A7A@americafree.tv>
To: IETF list <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: Wed, 12 Jan 2011 17:35:32 -0000

Seems relevant.

June 8, 2011

http://isoc.org/wp/worldipv6day/

http://www.networkworld.com/news/2011/011211-world-ipv6-day.html?hpg1=bn

Regards
Marshall


From sm@resistor.net  Wed Jan 12 10:08:44 2011
Return-Path: <sm@resistor.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 6ED443A69C4 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 10:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.285
X-Spam-Level: 
X-Spam-Status: No, score=-103.285 tagged_above=-999 required=5 tests=[AWL=-0.286, 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 lAUwhnv3aCIT for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 10:08:43 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 2CCE53A6817 for <ietf@ietf.org>; Wed, 12 Jan 2011 10:08:43 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0CI9V3C006860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2011 10:10:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1294855840; x=1294942240; bh=XcF/0/fjXX7+n+V8/GTE/LrdrsMa9s98TvwGbwL2yvI=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=lFtp4If5mfkuR7mRW/JwqCHdpZgpsDBpWEXsw2VMlWwbj5+4emH/dn1xrOzLrL+cF u2n6UAI/G77kXdf9/5Q3CpTMRvLGVbc7JRkalut/96teF0RQ3SG6/KjhKFn/2/f3Ck kJSI7pO5IL1S7zB8+gNFUdzWHHJFsVsTMOWIPEcA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1294855840; x=1294942240; bh=XcF/0/fjXX7+n+V8/GTE/LrdrsMa9s98TvwGbwL2yvI=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=qymJcXXbOHoVt5pP3GDIr50el3i299AnxmFyILmByEtQDS4ntdvxar0sXyPV6swcs MY/nJFhAQcvrclTKsbqqjlWRNf/BP3UApNBY5niozvnVJZvcd7hQTxkjjwGzrNRY79 DVhsA6HTi1VEi0GYzexcyXpcCjJAgrQlna7uUqBA=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=FWPlrNYw4wssR7YII0jPnEs6zqjhV0l8o3P24kdd/IoKIzE1j7GFzEDpSJlAFYZEu oMnRKe4b0QXUrNPsclcvcGgOr9GlVYMNFTQF4Z1Z5C3aKqWHT9bMOYepXq00w98BsIM 8lpWGnOT+0shyzqz5xlP1+z3QsghBUZfVUYJ0iY=
Message-Id: <6.2.5.6.2.20110112082925.0cc1b768@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Jan 2011 10:00:49 -0800
To: "t.petch" <daedulus@btconnect.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call On draft-yevstifeyev-tn3270-uri-12
In-Reply-To: <009501cbb235$d5a0ff20$4001a8c0@gateway.2wire.net>
References: <4D23FFBA.5030804@gmail.com> <003101cbb1ac$bd6b2cc0$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20110111162923.08f3a598@resistor.net> <009501cbb235$d5a0ff20$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 12 Jan 2011 18:08:44 -0000

Hi Tom,
At 00:50 12-01-11, t.petch wrote:
>This is a provisional registration of an URI scheme (for which a provisional
>registration already exists in IANA) so it is the rules of  RFC4395 
>which apply.
>
>Except that they do not appear to cater for re-registration of a provisional
>scheme.
>
>The nearest would appear to be
>"   o  Contact information identifying the person supplying the
>       registration is included.  Previously unregistered URI schemes
>       discovered in use may be registered by third parties on behalf of
>       those who created the URI scheme; in this case, both the
>       registering party and the scheme creator SHOULD be identified."
>
>and it is the complete lack of the original scheme creator that
>concerns me.  Yes we have contact details for the third party
>but that is not enough.

Agreed.

RFC 1738 reserves a scheme name for tn3270.  There is also a TN3270E 
defined in RFC 2335.  The Introduction section of 
draft-yevstifeyev-tn3270-uri-12 mentions RFC 1738 while the  scheme 
definition seems to cover TN3270 and TN3270E.

The Security Considerations section does not look like a clear 
analysis (see RFC 4395).

One of the points you mentioned is that there is already a 
provisional registration in the URI Schemes registry.  The proposal 
mentions that there are no clear and acceptable specifications so far 
while saying that the URI is similar to Telnet.

I am reluctant to take a position on this draft.

Regards,
-sm 


From d3e3e3@gmail.com  Wed Jan 12 12:05:55 2011
Return-Path: <d3e3e3@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 B86613A6A90 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 12:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.37
X-Spam-Level: 
X-Spam-Status: No, score=-103.37 tagged_above=-999 required=5 tests=[AWL=0.229, 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 bFHQ4AqORRBs for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 12:05:54 -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 7F7603A69A4 for <ietf@ietf.org>; Wed, 12 Jan 2011 12:05:54 -0800 (PST)
Received: by wwa36 with SMTP id 36so914238wwa.13 for <ietf@ietf.org>; Wed, 12 Jan 2011 12:08:14 -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:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=JcfpHnYv6WBUf/H/XIR7JwKhO2OUzdvRLyDOTThGkGY=; b=vx3Kke6VI6HI9DOMHUMwbaYq/QtldfbtEC6rGD5KtFyNozlBE061/tLG0b79lNZIR3 gncgOCGeVvLnJSbTdhUpqUTU5OhUlE2uwMZ2x99P8/G/38ODWWJXp+XAZZgFQoA2XSgy 3o7E0ZN+XrZhcNn68fuX346kH5PRrhSz6U/QM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=JIsR2DxiRariA9EjxDNykwBNMKFApx9F3upxAo+YII5SLAg7xjZe/DhlQJVvE0ii7w TXJdeC9ksk0mBwLXle3RsCieklN1uOIUr/JpUeTKBSmxEd6jHb481jjMhEIiGii/1CBp 0TXOnpAgjNoX2aV4wdaxLs99lzp0VroKIXFj8=
Received: by 10.227.138.129 with SMTP id a1mr1466996wbu.37.1294862894188; Wed, 12 Jan 2011 12:08:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 12 Jan 2011 12:07:54 -0800 (PST)
In-Reply-To: <4D2DBC48.2080302@gmx.de>
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de> <01da01cbb264$2f1462d0$8d3d2870$@huawei.com> <4D2DBC48.2080302@gmx.de>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 12 Jan 2011 15:07:54 -0500
Message-ID: <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: stig@cisco.com, Adrian.Farrel@huawei.com, 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: Wed, 12 Jan 2011 20:05:55 -0000

Almost all registries I'm familiar with explicitly list unassigned
ranges. In some cases, different unassigned subranges have different
allocation policies. For example, there may be a small unassigned
range of lower values requiring Standards Action with the bulk of the
unassigned values allocatable on a less stringent basis.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com



On Wed, Jan 12, 2011 at 9:35 AM, Julian Reschke <julian.reschke@gmx.de> wro=
te:
> On 12.01.2011 15:22, Adrian Farrel wrote:
>>
>> Entirely at random I clicked on:
>>
>> http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
>> http://www.iana.org/assignments/calipso/calipso.xhtml
>> http://www.iana.org/assignments/lmp-parameters
>>
>> Looks like IANA tries to fill up all the blanks with markers of
>> "unassigned".
>>
>> Is that harmful?
>
> Minimally, it's redundant. Also, it only makes sense on certain types of
> registries.
>
> I just checked the XML version of the first registry, and, indeed, it
> contains entries for unassigned values. /me shakes head in disbelief.
>
> What *should* be done is computing the unassigned ranges for *presentatio=
n*;
> that is, they should not be part of the actual registry. The way it's don=
e
> currently defeats one of the reasons of having a machine-readable registr=
y
> (consumers will have to hard-wire knowledge of the specific "unassigned"
> entry to make sense of the registry).
>
> Best regards, Julian
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From evnikita2@gmail.com  Wed Jan 12 16:28:20 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 382133A67B4 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:28:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=-0.682, 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 wCIsJyUjqA8s for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:28: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 AB9723A67AE for <ietf@ietf.org>; Wed, 12 Jan 2011 16:28:18 -0800 (PST)
Received: by bwz12 with SMTP id 12so1171257bwz.31 for <ietf@ietf.org>; Wed, 12 Jan 2011 16:30:37 -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=vWETLGTvH8uz1HUzKBP05bQHrLh/321SGSBr3s7iqNA=; b=gB7achWM98tFgvxhgRUTaNo1CMA/UAytmf0ehZkqFKYgwI4N0Kzg1fO72Ol3aN315M ygk6mdrhTGAmHd3+CJy2x5nu1jSqcVilvlH5ZUeknIKXFU97Dg75SukGs6bdChvNoq7w Xm2+NsHcUqN7VjgPQ96g+gGdCbUosBLHEOXGw=
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=gsw/ijEsayAj2q2WS5V8OVg52VTSvScI2nVSuSTwCE7rltS5ORggMIkWLU0u/R1g3+ TgFN7fM434hoaaz1cR/kKBoPs2pyfh6GBazjpcenghhgwZ6ft1CKXGHwW4dVyh7sPI65 6eSRTH9IJUGg2EQVEyX7LVPEkTPdAovaE3nxQ=
Received: by 10.204.81.72 with SMTP id w8mr1272461bkk.205.1294878636167; Wed, 12 Jan 2011 16:30:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id j11sm349125bka.12.2011.01.12.16.30.34 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Jan 2011 16:30:34 -0800 (PST)
Message-ID: <4D2E47BD.5040305@gmail.com>
Date: Thu, 13 Jan 2011 02:30:53 +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: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com> <4D2DBC48.2080302@gmx.de> <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
In-Reply-To: <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, The IETF <ietf@ietf.org>, Adrian.Farrel@huawei.com, stig@cisco.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: Thu, 13 Jan 2011 00:28:20 -0000

12.01.2011 22:07, Donald Eastlake wrote:
> Almost all registries I'm familiar with explicitly list unassigned
> ranges. In some cases, different unassigned subranges have different
> allocation policies. For example, there may be a small unassigned
> range of lower values requiring Standards Action with the bulk of the
> unassigned values allocatable on a less stringent basis.
RFC 5226 has an exact rule: Unassigned values shall be mentioned while 
creating registries.

And another (not from 5226): it is RECOMMENDED to explain all 
abbreviation, even well-known once they occur.

I do not know what is the problem here.

Mykyta
> Thanks,
> Donald
> =============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street
>   Milford, MA 01757 USA
>   d3e3e3@gmail.com
>
>
>
> On Wed, Jan 12, 2011 at 9:35 AM, Julian Reschke<julian.reschke@gmx.de>  wrote:
>> On 12.01.2011 15:22, Adrian Farrel wrote:
>>> Entirely at random I clicked on:
>>>
>>> http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
>>> http://www.iana.org/assignments/calipso/calipso.xhtml
>>> http://www.iana.org/assignments/lmp-parameters
>>>
>>> Looks like IANA tries to fill up all the blanks with markers of
>>> "unassigned".
>>>
>>> Is that harmful?
>> Minimally, it's redundant. Also, it only makes sense on certain types of
>> registries.
>>
>> I just checked the XML version of the first registry, and, indeed, it
>> contains entries for unassigned values. /me shakes head in disbelief.
>>
>> What *should* be done is computing the unassigned ranges for *presentation*;
>> that is, they should not be part of the actual registry. The way it's done
>> currently defeats one of the reasons of having a machine-readable registry
>> (consumers will have to hard-wire knowledge of the specific "unassigned"
>> entry to make sense of the registry).
>>
>> Best regards, Julian
>>
>> _______________________________________________
>> 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 evnikita2@gmail.com  Wed Jan 12 16:54:32 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 F31093A67E4 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:54:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.315
X-Spam-Level: 
X-Spam-Status: No, score=-2.315 tagged_above=-999 required=5 tests=[AWL=-0.676, 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 ijv4Oxm1Sjxp for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:54:31 -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 CFB773A67E3 for <ietf@ietf.org>; Wed, 12 Jan 2011 16:54:30 -0800 (PST)
Received: by bwz12 with SMTP id 12so1187314bwz.31 for <ietf@ietf.org>; Wed, 12 Jan 2011 16:56:51 -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:content-transfer-encoding; bh=sFDIFMRJegINgCxLxRTKyh7RvvL9hjC+JbzpnOJmVbY=; b=pKvmjS1k614YbfrkUDfUw7PdzIek7kFRZuJin3dUt5F1awpQkYLyrcjTZrOQhFE31Y 5MeLlXlUHz0/UJYVWcpDFEFHirXzAcZj4dBMuCySJtGPulUqwRZNIB8Dbe22EFLN1y7H y1eIQKY59LtVPBl/jCqjFwWfG9jn0YM1ganHQ=
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:content-transfer-encoding; b=Z1PInQvwSMaOZhRtuFPcy0hIahyIXAPOKoTVWjtZxqoASegA10MyP5+WL3jDw/pWJc V2+2cAQa39vmkTjSYOc/pGYZHJH/9nEHDAceNBLuuAoBfk27sGl0xNt2cU8nTDjWLaSy gERUoOp6Gxkdse6zRVparbEau3pAgDX58dMqg=
Received: by 10.204.42.24 with SMTP id q24mr1297207bke.208.1294880210666; Wed, 12 Jan 2011 16:56:50 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id x38sm355708bkj.13.2011.01.12.16.56.49 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Jan 2011 16:56:49 -0800 (PST)
Message-ID: <4D2E4DE4.3040608@gmail.com>
Date: Thu, 13 Jan 2011 02:57:08 +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>
Subject: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
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, 13 Jan 2011 00:54:32 -0000

I'm forwarding the OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12 
that is currently in LC to this list.  Mykyta

-----Original Message-----
From: ops-dir-bounces@ietf.org [mailto:ops-dir-bounces@ietf.org] On
Behalf Of ext Ersue, Mehmet (NSN - DE/Munich)
Sent: Wednesday, January 12, 2011 1:07 PM
To: ops-dir@ietf.org
Cc: draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org
Subject: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12

I reviewed draft-yevstifeyev-tn3270-uri-12 for its operational impacts..

Summary:
The document gives a specification of syntax, semantics and use of
'tn3270' URI scheme.

Obviously this is an individual submission without any document write-up
and supporting AD.
I would like to read a document write-up with the regular template even
if it is written by the author.

The main purpose of the document, namely to update the IANA registration
of tn3270 URI scheme using the given registration template, should be
added to the Introduction section. In general I would suggest to include
in the Introduction section the purpose of the action and more
importantly why existing IANA registrations are not sufficient and why
the publication of this RFC is needed.

Obviously the GEN-Area reviewer (Tom Petch) has an opposite opinion and
does not see this IANA registration in the interest of IETF (see
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=55119&tid=129
4831574). The reviewer furthermore states, following the rules in
RFC4395 the document should provide concrete contact information for the
editor instead of an anonymous email address only.

I don't see any additional operation impact other than above.

Other issues:

- The used language needs some polishing.

- Following are draft nits suggesting correction:

== The copyright year in the IETF Trust and authors Copyright Line does
not
    match the current year

->  Use new template or: s/2010/2011/

-- Obsolete informational reference (is this intentional?): RFC 1738
    (Obsoleted by RFC 4248, RFC 4266)

->  Use correct reference or clarify.


Mehmet

_______________________________________________
OPS-DIR mailing list
OPS-DIR@ietf.org
https://www.ietf.org/mailman/listinfo/ops-dir



From evnikita2@gmail.com  Wed Jan 12 16:55:00 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 89C3D3A67EC for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:55:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.309
X-Spam-Level: 
X-Spam-Status: No, score=-2.309 tagged_above=-999 required=5 tests=[AWL=-0.670, 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 mhL9rCDQmqKI for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 16:54: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 487C63A67AE for <ietf@ietf.org>; Wed, 12 Jan 2011 16:54:59 -0800 (PST)
Received: by mail-bw0-f44.google.com with SMTP id 12so1187314bwz.31 for <ietf@ietf.org>; Wed, 12 Jan 2011 16:57:20 -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=fBIhrZfxEY9kbJv8jHNaweTBMopxx2/pNioEBh+wRR4=; b=FWYfSKOqxCud5iG75ZgZDazQIWV7nEKLpFQer/RDFI7e6pMhbs/H4YKY+lEQPz21VF CqMm8cYCynOgIx4aJOxohobBibQrsiR/ZEpDfkCbebnRzEXUo0GtG5Si4aYveoajvUBr /cZDhXyPB59688IL3Y0j7vEv6kb7N/JQ9XZSQ=
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=FSEx9ayF6KWklUxe4wuC1kX2E/D4+wi5elGrVcSIGr3OQEswjonGDsTMgwnb0KX7u3 rNltQr+PSRKooVewuWom56Yz8hv2yU4e7xgnZXYL3BYF+HySEH69g8jaSx4BdPJb62qx 8DUlO1VQ9ca/H3IpSwm1v3LQqUG+FtUgLFfXE=
Received: by 10.204.72.6 with SMTP id k6mr1320438bkj.88.1294880238308; Wed, 12 Jan 2011 16:57:18 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id v25sm358202bkt.6.2011.01.12.16.57.16 (version=SSLv3 cipher=RC4-MD5); Wed, 12 Jan 2011 16:57:17 -0800 (PST)
Message-ID: <4D2E4DFF.6020507@gmail.com>
Date: Thu, 13 Jan 2011 02:57:35 +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: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>,  IETF Discussion <ietf@ietf.org>
Subject: Re: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>
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, 13 Jan 2011 00:55:00 -0000

12.01.2011 14:19, Ersue, Mehmet (NSN - DE/Munich) wrote:
> -----Original Message-----
> From: ops-dir-bounces@ietf.org [mailto:ops-dir-bounces@ietf.org] On
> Behalf Of ext Ersue, Mehmet (NSN - DE/Munich)
> Sent: Wednesday, January 12, 2011 1:07 PM
> To: ops-dir@ietf.org
> Cc: draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org
> Subject: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
>
> I reviewed draft-yevstifeyev-tn3270-uri-12 for its operational impacts..
>
> Summary:
> The document gives a specification of syntax, semantics and use of
> 'tn3270' URI scheme.
>
> Obviously this is an individual submission without any document write-up
> and supporting AD.
Why without?  Peter Saint-Andre is sponsoring AD.
> I would like to read a document write-up with the regular template even
> if it is written by the author.
>
> The main purpose of the document, namely to update the IANA registration
> of tn3270 URI scheme using the given registration template, should be
> added to the Introduction section. In general I would suggest to include
> in the Introduction section the purpose of the action and more
> importantly why existing IANA registrations are not sufficient and why
> the publication of this RFC is needed.
Agreed.  I'll add that as soon as possible.
> Obviously the GEN-Area reviewer (Tom Petch) has an opposite opinion and
> does not see this IANA registration in the interest of IETF (see
> https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=55119&tid=129
> 4831574). The reviewer furthermore states, following the rules in
> RFC4395 the document should provide concrete contact information for the
> editor instead of an anonymous email address only.
That would be corrected so that the author will be IETF and contact - IESG.
> I don't see any additional operation impact other than above.
>
> Other issues:
>
> - The used language needs some polishing.
>
> - Following are draft nits suggesting correction:
>
> == The copyright year in the IETF Trust and authors Copyright Line does
> not
>     match the current year
>
> ->  Use new template or: s/2010/2011/
Will be corrected.
> -- Obsolete informational reference (is this intentional?): RFC 1738
>     (Obsoleted by RFC 4248, RFC 4266)
>
> ->  Use correct reference or clarify.
Obsolete Informational references are allowed.  I don't see a problem here.

Mykyta
>
> Mehmet
>
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir
>


From sm@resistor.net  Wed Jan 12 17:14:17 2011
Return-Path: <sm@resistor.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 1640F3A6778; Wed, 12 Jan 2011 17:14:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.643
X-Spam-Level: 
X-Spam-Status: No, score=-103.643 tagged_above=-999 required=5 tests=[AWL=-0.044, 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 qNn5PNXdQ-Pt; Wed, 12 Jan 2011 17:14:13 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 4C8F23A67A4; Wed, 12 Jan 2011 17:14:13 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0D1GGu1000393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2011 17:16:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1294881387; x=1294967787; bh=D4qYwHet7dbd8GKfbp6TI8wPmjRs9Y+57r94bTqDzVA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=oaNAuu1Rvvab8KTCAhz8Z2S7YaDOqbOiI6p/9tX/ODvFXYGNHA/EDkmz2m7+bzgEL SOpz6jmLS6KfmfsguEuDNxjY5vAV5kMyr1ZTHhu1c1ruGsXjw0SQS+o9IytPWomdDE /0wFJK2xCIBWbYY4RLioBoPB63daUNojK1fF8uBY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1294881387; x=1294967787; bh=D4qYwHet7dbd8GKfbp6TI8wPmjRs9Y+57r94bTqDzVA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=MDgXba3VoL38wnmY2EMxMg39X4EiDgVObsRPKXcg6iyu89ITrRgnhjTDCBBwXY8yw z+jebPuePw4BZfuzC0DEqp/idt+63NFqiSKsZEsaQp3sfaRNQu1/MHSTD1965mJUuV 2cfLJOt7mB1oZICZaYvXNuN0LhXTORN8SMIn3hm0=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=xTju0V6K/LAkO4tcvcZVYSDwFQOnAuvBouA0yCDLvP1pHlSbyV336GF/1cSDRwTgO gsFRhIeSICmTbYjxJgj0HlMyuFW5OEXNfrrsLkgKyQ3IBds0z+YCkNKfwXm3EUEagvm GYJxHSJGaoZkJIRWiMIVEeU/26K+3ePefA3e+8E=
Message-Id: <6.2.5.6.2.20110112162845.07374c30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Jan 2011 17:13:03 -0800
To: Elwyn Davies <elwynd@dial.pipex.com>
From: SM <sm@resistor.net>
Subject: Re: Gen-art review of draft-lear-iana-timezone-database-01
In-Reply-To: <1294852216.17554.17972.camel@mightyatom.folly.org.uk>
References: <1294852216.17554.17972.camel@mightyatom.folly.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-lear-iana-timezone-database.all@tools.ietf.org, General Area Review Team <gen-art@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, 13 Jan 2011 01:14:17 -0000

Hi Elwyn,
At 09:10 12-01-11, Elwyn Davies wrote:
>This document is not quite ready for the IESG.  The appeals process (if
>there is to be one) needs to clarified as it currently points indirectly
>to a hole in RFC 5226. As explained below, I have a feeling that it
>would be wise to avoid tying the processes in this document to the
>Designated Expert processes in RFC 5226 despite the similarities.
>Making it clear what does apply and what doesn't is probably more work
>than doing it from scratch in this document, especially given the hole
>in RFC 5226.

[snip]

>I think the draft should make it explicit that it is referring to the
>'Designated Expert' sections in RFC 5226 here if it continues to
>reference RFC 5226 - although there is a clear relationship with
>Designated Experts, the differences between the selection process and
>the operations of the TZ Coordinator and generic Deisgnated Experts may

Yes, there are significant differences.  According to RFC 5226:

   "The designated expert is responsible for initiating and coordinating
    the appropriate review of an assignment request."

It might be helpful to get some feedback from IANA and the IETF Trust 
on this draft before it is evaluated by the IESG.

>mean that citing RFC 5226 might lead to legalistic disputes about which
>set of rules applies.  Also, I am unable to find statements in RFC 5226
>backing up the sentence above.  Regrettably, RFC 5226 appears
>effectively to have a 'dsngling reference' in this area. Section 3.2,
>para 3 of RFC 5226 points at Section 5.2 which (allegedly) discusses
>'disputes and appeals in more detail'.  However s5.2 is titled 'Updating
>Registrations' and says nothing about appeals and disputes.  Section 7
>of RFC 5226 covers appeals of IANA decisions but says nothing specific
>about appealing designated expert rulings.  I think this area may need a
>little more work.  Overall, my inclination would be to make this a
>standalone document that does not try to partially modify the RFC 5226
>Designated Expert process and operations.  Appeals... >*sigh*<.

Section 7 of RFC 5226 states that:

   "Appeals of registration decisions made by IANA can be made using the
    normal IETF appeals process as described in Section 6.5 of
    [IETF-PROCESS]."

Section 4 of mentions that:

   "In keeping with [RFC5226], the IESG selects the TZ
    coordinator(s).  The IESG will use rough consensus of the TZ mailing
    list as their primary guide to further action, when it exists, and
    whatever other means they have at their disposal, when rough
    consensus cannot be found.  As RFC-5226 states, the IESG is not a
    normal avenue for appeals of specific decisions of the coordinator,
    but rather a last resort when a coordinator is thought not to be
    functioning in an appropriate way."

That could be rewritten as:

    The IESG selects the TZ coordinator(s).  The IESG will use the rough
    consensus of the TZ mailing list as their primary guide for any action,
    when it exists, and whatever other means they have at their disposal,
    when rough consensus cannot be found.

    The IESG is not an avenue for appeals of specific decisions of the
    coordinator, but rather a last resort when a coordinator is thought not
    to be functioning in an appropriate way.  An appeal can be made in such
    a case by using the normal IETF appeals process as described in Section
    6.5 of RFC 2606.

The following sentence in Section 1.1 might have to be removed then:

   "The TZ coordinatior is a Designated Expert, as defined in [RFC5226]"

Regards,
-sm 


From fluffy@cisco.com  Wed Jan 12 17:50:08 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 9D1523A67E3; Wed, 12 Jan 2011 17:50:08 -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 yPlN7xjQEzDV; Wed, 12 Jan 2011 17:50:04 -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 CB0943A67B1; Wed, 12 Jan 2011 17:50:03 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJzpLU2rR7Ht/2dsb2JhbACkRXOjKJh+gweCRQSEaIYogyA
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 13 Jan 2011 01:52:24 +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 p0D1qM60008467; Thu, 13 Jan 2011 01:52:23 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Review of draft-saintandre-tls-server-id-check-12
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <58FE898B-BD2A-4C6E-B769-256008D8A58B@cisco.com>
Date: Wed, 12 Jan 2011 18:53:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <98BE4336-F5EC-4426-9DA5-404B67BFB428@cisco.com>
References: <58FE898B-BD2A-4C6E-B769-256008D8A58B@cisco.com>
To: IESG IESG <iesg@ietf.org>, The 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: Thu, 13 Jan 2011 01:50:09 -0000

The latest version of this draft resolved all my concerns. Thanks to =
everyone that put in all the time and effort.=20

Cullen

On Dec 16, 2010, at 12:17 AM, Cullen Jennings wrote:

>=20
> So let me start with I think there is great information in here and I =
think it should be published as a standards track RFC however I do think =
there are some issues with the relation with this draft and the =
realities of what would help improve security in deployment of SIP, =
HTTP, IMAP, XMPP etc.=20
>=20
> There are many places where this draft makes choices to improve the =
security from many current practices. At face value this seems like a =
good thing but it's not always. The thing reducing the overall security =
available to users of TLS is not if certs use CN-ID or DNS-ID, it is =
that it's such a PITA to deploy a TLS  server that people choose to not =
use TLS at all. Everywhere there is a trade off between making things =
marginally more secure, or making things cheaper and easer to deploy, I =
think we need to seriously consider the cheaper and easier approach. =
Yes, some things are just broken even if they are easy and obviously we =
can't do those. Let me give an example of this. I looked at the cert for =
the domains for the authors of this draft. www.cisco.com has 3 DNS names =
even though as fas as I can tell one of these are for something that =
would typically be used in a ftp URI and the other HTTP URI. This is =
because it makes it easier and cheaper for them to use TLS yet seems to =
go against the recommendation of this "BCP". Then I went over the =
www.paypal.com domain which uses, gasp, a CN-ID. Do we really believe =
that paypal is seriously compromising their security by using a CN =
instead of URI-ID? If so, how? I'm pretty sure the paypal guys know how =
to run a secure web server. With the exception of Microsoft small =
business server certificates (which are outrageously expensive by the =
way) it pretty hard to get SRV name certs. In making these =
recommendations, did the TLS WG consider the relative prices of various =
types of certificates? Lets say I had a certificate for the domain =
example.org because I was using it for email and it has a CN because I =
got it years ago. Now lets say I am going to go deploy a SIP service on =
example.org. My position is that best way to encourage the use of =
security on the internet is to just reuse the certificate I have. It =
cheap, it's easy, it secure enough even if it does make you feel a bit =
dirty. I think Jeff disagrees with me, we argued for years about this =
topic and my understanding is his position is that it would be better to =
say that all new deployments MUST not use a CN name because it's less =
secure. Give the prevalence of CN on the internet today, I think it is =
fine to tell people how DNS-ID is better but I don't think it's OK to =
tell them they should not use CN-ID and I definitely don't think it is =
OK to tell implementors they don't need to implement CN-ID.=20
>=20
> I encouraged Chris to write this draft long ago and what we had =
discussed at the time was forming a RFC with one or more boiler plate =
pieces of text that could be used in creation of the name matching =
section of new protocols that got developed. I was thinking of something =
similar to the way we use rfc 5226 for writing IANA consideration =
section. Instead we have a document that is creating a very complex =
situations about whats normative. This draft is a BCP level, and it says =
you have to do everything in PKIX and PKIX takes precedence. That is =
basically elevating PKIX to a BCP without appropriate process review. =
Next this draft contradicts the procedures in existing protocols and =
says that it does not apply to the existing protocols but that it would =
take precedence over any future updates of existing protocols that use =
TLS within the scope specified here. I do not believe you have the =
consensus of the people woking on SIP that the next time some =
specification is marked as an UPDATE to 3261, that implementations need =
to implement the procedures in this draft. Furthermore, I think that =
would be counter productive. I think you should make it clear this =
guidelines for designers of new protocol and people updating existing =
protocol and that these protocols could make their own choices but would =
want to take into account the information in this draft. When I read the =
sentence,=20
>  "However, the best current practices described here can
>   be referenced by future specifications, including updates to
>   specifications for existing application protocols if the relevant
>   technology communities agree to do so."
> I think that is exactly the right solution to the problem. However, =
that not a BCP, thats a standards track spec. Furthermore, I think this =
draft is going to have all the normal bugs etc of any other spec that =
defines algorithms and such it should proceed through the standards =
track process. If this draft is going to go as a BCP, that text =
contradicts what a BCP is and needs to come out and the rest of the =
draft be adjusted appropriately. My preference would be that this draft =
be standards track. Its writing exactly the same sort of normative =
algorithm text that we put in all kinds of other thing like SIP, HTTP, =
and even TLS. They are all standards track. This should be the same.=20
>=20
> Most RFCs today that use TLS have a page plus or minus that tells an =
implementer what they need to know about matching names in certs. This =
draft move that to 30 to 50 pages depending on how you count. Most =
implementers are just going to ignore this thus worsening the security =
situation. Think about why is the part implementers need to read 10x =
longer than existing deceptions - this just seems wrong. Now it's easy =
to blow off this type concern and say get over it, it's the same number =
of lines of code they need to write. But the problem is when an =
implementors goes to start doing this and encounters something that is =
50 pages long, they instantly decide this is a big task and down it goes =
on the priority list of actually happening. The other problem is that =
even thous it is long, it is still very confusing on how to do things =
(such at URI). I'll provide more detailed examples of this later in this =
email. If the document was restructured to have all the normative text =
in one short simple description and the rest moved to an appendix, it =
would be much easier to get people to take this seriously and easier to =
review that it was correct.=20
>=20
> My final big issue is the use of normative language. Lets say there =
are two procedures A and B and we 100% consensus that B is better than A =
but we still have to support A for existing deployment reasons. To =
describe this, the text this draft would use is is MUST do A and SHOULD =
NOT do B. Now reading 2119 it is pretty clear that SHOULD NOT means you =
don't implement it unless there are real good reasons to implement it. =
So on the things were we agree A is preferred to B but you need both for =
backwards compatibility, this draft needs to say MUST implement A and =
MUST implement B but deployments are encouraged to use B as we are =
trying to move away from A. I think the whole document needs a careful =
read checking for this issue. You can insert the usual rant here about =
why SHOULD is a awful word in specs 90% of the time it used because =
implementer thinks it means "ignore rest of sentence". For example,  =
section 5.4 discusses they this spec continues to mandate protocols MUST =
support CN yet this draft continually use "SHOULD NOT" when what it =
really means is MUST implement. This is going to confuse implementors of =
IETF specification and be ignored by operators. Given the goals of this =
spec it would be much better if it was clearly defining what IETF =
required implementers of protocols to do instead of confusing that with =
how we wish security was deployed.=20
>=20
>=20
> On to the nits.
>=20
> Take an applications like a web server. Is the preferred thing in a =
cert a DNS-ID or a URI-ID. My reading of the 3.3 is that URI-ID is =
preferred over DNS-ID yet the examples don't match that. I think point 3 =
in section 3.1 tries to explain this away but I don't understand that - =
clearly web browsers use a URI.=20
>=20
> The rules in section 3.1 don't make sense for a CA. How will the CA =
know if the cert I want is going to be used for a protocol that uses =
SRV?
>=20
> In section 3.2, in the imap example, you are saying that if I =
configure my imap server to mail.example.com and it presents a =
certificate with a DNS-ID of example.com that this is OK. That does not =
sound OK to me but I don't know how IMAP works. In the SIP example, the =
cert should have a SRV and DNS name too. As well as a CN if you actually =
want it to work in the real world.=20
>=20
> In section 4.2.1 you have a long discussion on how the information =
used must come from a way that can't be tampered with over the internet. =
I generally agree with this but would like to point out that protocols =
like LOST (see section 18 of rfc5222) specially do the opposite of this =
and actually match the cert agains the output of NAPTR process not the =
input to the NAPTR process.
>=20
> The example just seem plain wrong in some cases. Take for example =
section 4.2.2 where the SIP example has only a URI reference identifiers =
and no DNS yet the section right before this has said the list MUST =
include a DNS-ID. This text has been through how many reviews and Last =
Calls? The problem here is that this draft is too long to review for =
stuff like this. Even after the IESG is done reviewing it, statistics =
suggest it will still be littered with bugs like this and implementors =
will use the examples to guide them. If someone implements what is in =
the example, it will break in lots of sip deployments.=20
>=20
> There is a whole algorithm about matching various ID types, but the =
note about you ignore CN if you have other things is off in "Security =
Warning" very much out of any flow of the algorithm description then =
pointed out again in some other section. It's not wrong, but it's a bit =
weird from an implementer point of view.=20
>=20
> Many applications do need to deal with IP matching as well as domain =
names. The way this text is written here makes it harder to figure out =
how and where to mix that in. I'd rather see it just dealt with than =
instead of making it out of scope. Obviously it's not common on internet =
but it is common on private networks and walled gardens where many of =
the protocols were are talking about are deployed. Many of the "internet =
of things" people I work with have no intention of using DNS at all. I =
scoffed at multiple large service providers 10 years ago when they said =
they were not using DNS with SIP but many still use IPs. This sounds =
less insane when you consider the major OS don't ship with an =
asynchronous DNS library.=20
>=20
> I'm baffled on why checking the service name in a SRV record is a =
SHOULD not a MUST. Could you add text explain why and when one would not =
check it. If you were in a really good mood you could do that for all =
the SHOULDs. Actually, when I read section 4.5 carefully, I think it =
literally says that when using a URI, checking the domain name is a =
SHOULD not a MUST. Surely check the domain name matches is not a SHOULD =
level sort of thing.=20
>=20
> Section 5.4. I have no idea why it matters that some major OS does not =
support SNI. Even if that OS did support SNI, many many applications =
running on that OS and the others would not support SNI. It seems like =
it is the applications acting as TLS servers and clients that are the =
important thing, not the OS.=20
>=20
> How you process URI-ID needs work. I could not figure out how to =
implement given the text in the draft as is. Even ignoring the special =
tar pit the SIP guys dug for themselves with tel URL processing, just =
the normal sip, sips issues seems unclear.=20
>=20
> This seems like a long list of complaints delivered fairly late but, =
once again, I really do like much of the information in here and think =
it should be published as PS - it just would be significantly improved =
with a bit of a re-factored and clean up. If this had been run through =
the TLS working group, I would have caught all of this in the WG LC. =
This is a draft that, as a BCP,  profoundly effects many of the =
protocols I work on including SIP but as far as I can tell has not done =
much to gather the consensus of the people working on protocol that this =
draft changes - I don't recall hearing about it until after it went to =
the IESG so I'm pretty un apologetic about providing these comments =
during IETF LC.=20
>=20
> In summary, I like the information in this but I think it still has =
many small things that need fixing and needs to be changed to get crisp =
about what implementors need to do and drop the confusing stuff about =
how we wish operators and CA might use certificates. I also feel =
strongly that the right way to look at this draft is, as that draft says
> "practices described here can
>   be referenced by future specifications, including updates to
>   specifications for existing application protocols if the relevant
>   technology communities agree to do so"
> and that for that reason it has to be standards track not BCP. If it =
was not being written and pushed by two IESG members, I don't think we =
would even be discussing if it should be a BCP.=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20


From doug@ewellic.org  Wed Jan 12 18:54:32 2011
Return-Path: <doug@ewellic.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 7C4D83A6805 for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 18:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.137
X-Spam-Level: 
X-Spam-Status: No, score=-0.137 tagged_above=-999 required=5 tests=[AWL=-0.139, BAYES_50=0.001, STOX_REPLY_TYPE=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 ipZCv-DBr6Pi for <ietf@core3.amsl.com>; Wed, 12 Jan 2011 18:54:31 -0800 (PST)
Received: from smtpauth03.prod.mesa1.secureserver.net (smtpauth03.prod.mesa1.secureserver.net [64.202.165.183]) by core3.amsl.com (Postfix) with SMTP id 4E1AA3A6802 for <ietf@ietf.org>; Wed, 12 Jan 2011 18:54:31 -0800 (PST)
Received: (qmail 25537 invoked from network); 13 Jan 2011 02:56:51 -0000
Received: from unknown (24.8.55.39) by smtpauth03.prod.mesa1.secureserver.net (64.202.165.183) with ESMTP; 13 Jan 2011 02:56:51 -0000
Message-ID: <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>
From: "Doug Ewell" <doug@ewellic.org>
To: "The IETF" <ietf@ietf.org>
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com><01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de><01da01cbb264$2f1462d0$8d3d2870$@huawei.com> <4D2DBC48.2080302@gmx.de> <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
In-Reply-To: <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
Date: Wed, 12 Jan 2011 19:56:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
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, 13 Jan 2011 02:54:32 -0000

Donald Eastlake wrote:

> Almost all registries I'm familiar with explicitly list unassigned 
> ranges.

The IANA Language Subtag Registry doesn't:

http://www.iana.org/assignments/language-subtag-registry

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­


From julian.reschke@gmx.de  Thu Jan 13 00:00:16 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 4F3E23A6AB3 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 00:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.075
X-Spam-Level: 
X-Spam-Status: No, score=-104.075 tagged_above=-999 required=5 tests=[AWL=-1.476, 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 0HNebEDYt3EH for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 00:00:15 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id D7E873A6A99 for <ietf@ietf.org>; Thu, 13 Jan 2011 00:00:14 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 08:02:35 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp055) with SMTP; 13 Jan 2011 09:02:35 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18kwBN+do4kvFSHXfYqFdrPxN1kgyaYHU3f11313b MT9+2CMNvmVaEY
Message-ID: <4D2EB195.60604@gmx.de>
Date: Thu, 13 Jan 2011 09:02:29 +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: Doug Ewell <doug@ewellic.org>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com><01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de><01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com> <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>
In-Reply-To: <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Thu, 13 Jan 2011 08:00:16 -0000

On 13.01.2011 03:56, Doug Ewell wrote:
> Donald Eastlake wrote:
>
>> Almost all registries I'm familiar with explicitly list unassigned
>> ranges.
>
> The IANA Language Subtag Registry doesn't:
>
> http://www.iana.org/assignments/language-subtag-registry

Obviously it depends on the datatype whether saying what's unassigned is 
useful or feasible.

Back to ma point: for registries where it *can* be done, the unassigned 
values can be *computed*. Thus, they shouldn't be part of the registry 
data, but simply be displayed as such. That would ensure that the 
information always is up-to-date.

Best regards, Julian

From evnikita2@gmail.com  Thu Jan 13 01:19:35 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 4EE483A6B3B for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 01:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.056
X-Spam-Level: 
X-Spam-Status: No, score=-4.056 tagged_above=-999 required=5 tests=[AWL=-0.457, 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 gR74kv2OQlFL for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 01:19:34 -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 336CA3A6B49 for <ietf@ietf.org>; Thu, 13 Jan 2011 01:19:34 -0800 (PST)
Received: by gyd12 with SMTP id 12so659796gyd.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 01:21:56 -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=xu4wTxsmt3uAOeQPpsRbsvbN2UwAVWVxXidmJP9k/mw=; b=Ld37TRLHKN9zZ0aPw62OZ1h2F3tqz/iJMM8WBVQp23sdBZ6A8sicqcyxJZaHI1iq+i 5b7MVNePRIVX1jYjXBMd39wtJmMQS+vTOdsb0JqEpKlAFI1HAc6w2wyoubj5PQcNGCEK mB7T1luXH2qRIkmsYGLk29gbPoLERDI38Lo+4=
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=UAdwTQSPRpjZMSXGNLGYeL5lVaG47hNYJZb068dzzFWZIvK688z9Lg7Pze8bGTY+og NiWA32U0NF3wPkfQNIEpmx3dhZRqJRB6h+xI9ue6+5cHeY5JH7W6eRizdP7VkLqlgMJ3 9QGZkp73r+5MdBJNxoXuxakiHYX20uwXmdv/g=
MIME-Version: 1.0
Received: by 10.150.185.2 with SMTP id i2mr3326457ybf.155.1294910514945; Thu, 13 Jan 2011 01:21:54 -0800 (PST)
Received: by 10.150.53.6 with HTTP; Thu, 13 Jan 2011 01:21:54 -0800 (PST)
In-Reply-To: <4D2EB195.60604@gmx.de>
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <01bc01cbb25c$41590700$c40b1500$@huawei.com> <4D2DB36C.7070107@gmx.de> <01da01cbb264$2f1462d0$8d3d2870$@huawei.com> <4D2DBC48.2080302@gmx.de> <AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com> <0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell> <4D2EB195.60604@gmx.de>
Date: Thu, 13 Jan 2011 11:21:54 +0200
Message-ID: <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
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: Thu, 13 Jan 2011 09:19:35 -0000

Hello all,

Let me cite RFC 5226, that says:

<...>
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered values) MUST
provide clear instructions on details of the namespace.  In
particular, instructions *MUST* include:
<...>
5) Initial assignments and reservations.  Clear instructions should be
provided to identify any initial assignments or registrations.  In
addition, any ranges that are to be reserved  for "Private Use",
"Reserved", *"Unassigned"*, etc. should be *clearly indicated*.
<...>

So the document specifying the regsitry MUST mention what are
Unassigned.  Moreover, IMO, it would be useful to assign one value for
Experimentation.

Mykyta

2011/1/13, Julian Reschke <julian.reschke@gmx.de>:
> On 13.01.2011 03:56, Doug Ewell wrote:
>> Donald Eastlake wrote:
>>
>>> Almost all registries I'm familiar with explicitly list unassigned
>>> ranges.
>>
>> The IANA Language Subtag Registry doesn't:
>>
>> http://www.iana.org/assignments/language-subtag-registry
>
> Obviously it depends on the datatype whether saying what's unassigned is
> useful or feasible.
>
> Back to ma point: for registries where it *can* be done, the unassigned
> values can be *computed*. Thus, they shouldn't be part of the registry
> data, but simply be displayed as such. That would ensure that the
> information always is up-to-date.
>
> Best regards, Julian
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From julian.reschke@gmx.de  Thu Jan 13 03:29:38 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 52BE328B23E for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 03:29:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.065
X-Spam-Level: 
X-Spam-Status: No, score=-104.065 tagged_above=-999 required=5 tests=[AWL=-1.466, 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 3bzQyXKB+GAc for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 03:29:37 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id D0A5A3A6B11 for <ietf@ietf.org>; Thu, 13 Jan 2011 03:29:36 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 11:31:57 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp055) with SMTP; 13 Jan 2011 12:31:57 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18atl9NMHga1kV+B1CUFLK8krbKVNXrQPKulsaKtU wG29XFC7/RlgFY
Message-ID: <4D2EE2A7.5060805@gmx.de>
Date: Thu, 13 Jan 2011 12:31:51 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com>
In-Reply-To: <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Thu, 13 Jan 2011 11:29:38 -0000

On 13.01.2011 10:21, Mykyta Yevstifeyev wrote:
> Hello all,
>
> Let me cite RFC 5226, that says:
>
> <...>
> Documents that create a new namespace (or modify the definition of an
> existing space) and that expect IANA to play a role in maintaining
> that space (e.g., serving as a repository for registered values) MUST
> provide clear instructions on details of the namespace.  In
> particular, instructions *MUST* include:
> <...>
> 5) Initial assignments and reservations.  Clear instructions should be
> provided to identify any initial assignments or registrations.  In
> addition, any ranges that are to be reserved  for "Private Use",
> "Reserved", *"Unassigned"*, etc. should be *clearly indicated*.
> <...>
> ...

That sounds like an editorial error to me.

"any ranges to be *reserved* for .... "Unassigned"..."

doesn't make any sense at all. They are not reserved.

This should probably be raised as erratum.

> So the document specifying the regsitry MUST mention what are
> Unassigned.  Moreover, IMO, it would be useful to assign one value for
> Experimentation.

No. should != must.

There are tons of registries where this is not the case; namely all or 
most of those where the values are strings, not numbers.


Best regards, Julian

From hallam@gmail.com  Thu Jan 13 05:42:35 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 6641A28C0D0 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 05:42:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.658
X-Spam-Level: 
X-Spam-Status: No, score=-3.658 tagged_above=-999 required=5 tests=[AWL=-0.060, 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 zb2JqVlE+cDI for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 05:42:34 -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 F16A228B23E for <ietf@ietf.org>; Thu, 13 Jan 2011 05:42:33 -0800 (PST)
Received: by gwj17 with SMTP id 17so767065gwj.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 05:44:56 -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=7FQOmX2n0K/tvea62xYYhwT8O1pkFeed5EeOIzCl+dI=; b=Ure2nfwm3xHWPJdTTbpjyQqpx4W3t7pCTnz/91A44GM+bVN6v4UhxulbDinnFGwc4z 2kWSfMY3HqA451bkefwsvbaTLH85CRQQmzjXD801BAErFL5ylJ+nd7P0gFg5VXjYvZVa Ie8doC+7ezu5tyTSeeYyVSgLl24IeDmhJCtbA=
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=rDie6xoj4Lj8KB6rAtQIO0oxTRS8uYWmljuOmegAZDeooALGeOtGoHw83Nijj+Yajx nH51BPMglnY+cxN04GPyobDL2BV82p6Ew5DX/m/Pid4CEeyahMY7L53YeL5R9nxeSjFc QOSF515TIXTt/RdGZTpUe6vZSCxJDSley2n9A=
MIME-Version: 1.0
Received: by 10.100.174.5 with SMTP id w5mr1454908ane.171.1294926296150; Thu, 13 Jan 2011 05:44:56 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Thu, 13 Jan 2011 05:44:56 -0800 (PST)
In-Reply-To: <6D992F32-6249-41C8-ADC9-2A85A7EDE138@checkpoint.com>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <0AEE9B5160EFE527C0EFE27C@PST.JCK.COM> <6D992F32-6249-41C8-ADC9-2A85A7EDE138@checkpoint.com>
Date: Thu, 13 Jan 2011 08:44:56 -0500
Message-ID: <AANLkTi=apzkcF5YqiAk=CVAGjztgqLPZTs_DgVWKWFc-@mail.gmail.com>
Subject: Re: Poster sessions
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=0016e64405a0e481d20499ba85a2
Cc: John C Klensin <john-ietf@jck.com>, IETF 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, 13 Jan 2011 13:42:35 -0000

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

On Tue, Jan 11, 2011 at 2:32 AM, Yoav Nir <ynir@checkpoint.com> wrote:

> We can have as high a barrier as necessary to ensure there are no more
> than, say, 12 posters.


That means someone has to judge them and that takes time.




> On Jan 11, 2011, at 3:39 AM, John C Klensin wrote:
>
> > +1.  Very strongly.
> >
> > Whether the logistics of space and times could be worked out or
> > not, poster sessions strike me as a really bad idea and Fred has
> > summarized at least most of the reasons.  If we had a high
> > barrier to posting I-Ds, it might be different.  But we don't.
> >
> >   john
>

+1


The problem that this is attempting to get round is the low barrier to
publication of IDs which means that there are many of them and ideas get
lost.

That is not a problem that can be solved by introducing another low barrier
to publication venue.





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

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

<div>On Tue, Jan 11, 2011 at 2:32 AM, Yoav Nir <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:ynir@checkpoint.com">ynir@checkpoint.com</a>&gt;</span> wrote:<=
br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
We can have as high a barrier as necessary to ensure there are no more than=
, say, 12 posters.</blockquote><div><br></div><div><meta charset=3D"utf-8">=
That means someone has to judge them and that takes time.<div><br></div></d=
iv>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"=
im">
On Jan 11, 2011, at 3:39 AM, John C Klensin wrote:<br>
<br>
&gt; +1. =A0Very strongly.<br>
&gt;<br>
&gt; Whether the logistics of space and times could be worked out or<br>
&gt; not, poster sessions strike me as a really bad idea and Fred has<br>
&gt; summarized at least most of the reasons. =A0If we had a high<br>
&gt; barrier to posting I-Ds, it might be different. =A0But we don&#39;t.<b=
r>
&gt;<br>
&gt; =A0 john<br></div></blockquote><div><br></div><div>+1</div><div><br></=
div><div><br></div><div>The problem that this is attempting to get round is=
 the low barrier to publication of IDs which means that there are many of t=
hem and ideas get lost.</div>
<div><br></div><div>That is not a problem that can be solved by introducing=
 another low barrier to publication venue.=A0</div><div><br></div><div><br>=
</div><div><br></div><div>=A0</div></div><br>-- <br>Website: <a href=3D"htt=
p://hallambaker.com/">http://hallambaker.com/</a><br>
<br>
</div>

--0016e64405a0e481d20499ba85a2--

From evnikita2@gmail.com  Thu Jan 13 07:49:06 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 118933A6BAC for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 07:49:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.304
X-Spam-Level: 
X-Spam-Status: No, score=-2.304 tagged_above=-999 required=5 tests=[AWL=-0.665, 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 axzIH4gZZIqB for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 07:49:05 -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 071433A6BA7 for <ietf@ietf.org>; Thu, 13 Jan 2011 07:49:04 -0800 (PST)
Received: by eyd10 with SMTP id 10so942251eyd.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 07:51:26 -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=YKLs85uh2CJqRgZyj01LJnfk4Gre7HzJ4dnJ6nYJbuU=; b=WZ9gsQL95tCzG8LJKJ2ReXq4TfT1VdRzbKYxxLzQezumMpziOvOvbX8t0U4FpvZb9o FSDhxcP0pWUWNyzh35aQXcmyLQCImuCkQGMVXz4jzQkKmrfRWF+1YAAaexIwLcYYhEpo 3KJB7wrShLWczy9Jt8AgEDAuUTcem3VrXmTjo=
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=bCTwyPqUmQp806TWUOdQKUzF5tynXWCSrEIsJE1HiD9WNgxU66Lse9/1rTWex6HbNt /5DvLajJriVDBsah5cpejmFt2u+3uhTNV46LRAyktLPz7K4oJ9/VYODk48AbUfgjir18 Txn5RYI/8pNZiF8d4f20z4TmvglfC6VJE66I0=
Received: by 10.204.59.140 with SMTP id l12mr1907578bkh.2.1294933886483; Thu, 13 Jan 2011 07:51:26 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id x38sm743449bkj.13.2011.01.13.07.51.24 (version=SSLv3 cipher=RC4-MD5); Thu, 13 Jan 2011 07:51:25 -0800 (PST)
Message-ID: <4D2F1F8F.5060304@gmail.com>
Date: Thu, 13 Jan 2011 17:51:43 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de>
In-Reply-To: <4D2EE2A7.5060805@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 13 Jan 2011 15:49:06 -0000

13.01.2011 13:31, Julian Reschke wrote:
> On 13.01.2011 10:21, Mykyta Yevstifeyev wrote:
>> Hello all,
>>
>> Let me cite RFC 5226, that says:
>>
>> <...>
>> Documents that create a new namespace (or modify the definition of an
>> existing space) and that expect IANA to play a role in maintaining
>> that space (e.g., serving as a repository for registered values) MUST
>> provide clear instructions on details of the namespace.  In
>> particular, instructions *MUST* include:
>> <...>
>> 5) Initial assignments and reservations.  Clear instructions should be
>> provided to identify any initial assignments or registrations.  In
>> addition, any ranges that are to be reserved  for "Private Use",
>> "Reserved", *"Unassigned"*, etc. should be *clearly indicated*.
>> <...>
>> ...
>
> That sounds like an editorial error to me.
>
> "any ranges to be *reserved* for .... "Unassigned"..."
>
> doesn't make any sense at all. They are not reserved.
Yes, that is a type of error, but the meaning is that unassigned and 
reserved values MUST (yes, must, that is in RFC 5226; see citation 
below) be mentioned.
>
> This should probably be raised as erratum.
>
>> So the document specifying the regsitry MUST mention what are
>> Unassigned.  Moreover, IMO, it would be useful to assign one value for
>> Experimentation.
>
> No. should != must.
See below.
>
> There are tons of registries where this is not the case; namely all or 
> most of those where the values are strings, not numbers.
The strings registries are rather exceptions from the rule I cited above.

Mykyta
>
>
> Best regards, Julian
>


From evnikita2@gmail.com  Thu Jan 13 07:53:18 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 6B54A3A6BA7; Thu, 13 Jan 2011 07:53:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.659, 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 bwr-t03+KbqC; Thu, 13 Jan 2011 07:53:17 -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 6733A3A6BA4; Thu, 13 Jan 2011 07:53:16 -0800 (PST)
Received: by bwz12 with SMTP id 12so1772462bwz.31 for <multiple recipients>; Thu, 13 Jan 2011 07:55: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:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sP9+CJjRYq+eyrUVxehASGIM6VEOZgOgFvlA2v/nyLU=; b=Iwm+FKkM+H3p9fY243qYgM0FfKahXGaTDI2Ve7OJ0LK6ImG7jMqJMRMWWpdsK8KNwH pGulR7+yAlLIHNyFVxcL5fKyyzSuw8ibePSMpP5NsV8JRXqSJYJtcophVWy2qS33iSJ0 WztCporB9xsGNC1Jhl17tz4CEnOivTGjRcFeY=
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=q8lynk0l/r3JkPQy3LKGycZjHi3WheUf9z5RL0cloVZWqX4oQ8LmD+cicUViVpiTGu ccTSaskje5EuTFEIrLlsN4Kx115kRQS3PW3gWl4P9XeV8Fzi56FfHo3eyTvIDKaeSl7r 2P6aH0DYWIaSYM727HAjHeMgpnJy73P+GRKYc=
Received: by 10.204.72.20 with SMTP id k20mr1850164bkj.184.1294934136373; Thu, 13 Jan 2011 07:55:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id 12sm744738bki.19.2011.01.13.07.55.34 (version=SSLv3 cipher=RC4-MD5); Thu, 13 Jan 2011 07:55:35 -0800 (PST)
Message-ID: <4D2F2089.2000306@gmail.com>
Date: Thu, 13 Jan 2011 17:55:53 +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: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Subject: Re: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>
In-Reply-To: <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ops-dir@ietf.org, IETF Discussion <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, 13 Jan 2011 15:53:18 -0000

13.01.2011 13:28, Ersue, Mehmet (NSN - DE/Munich) wrote:
>>> The reviewer furthermore states, following the rules in
>>> RFC4395 the document should provide concrete contact information for
> the
>>> editor instead of an anonymous email address only.
>> That would be corrected so that the author will be IETF and contact -
> IESG.
>
> I am not really sure whether this is appropriate.
>
> Why are you keen of keeping it more or less anonymous?
Mehmet, all,

Mentioning my full contact data makes no sense.  I can hardly imagine 
that somebody will come to Ukraine, search Kotovsk (that is rather small 
town) and than particular street, etc. to ask me about the URI scheme.  
Those who want that would prefer to contact me by email.

And nevertheless I'd like the registration template shall contain IETF 
as author and IESG as contact.  That is rather usual for IETF-stream RFCs.

All the best,
Mykyta Yevstifeyev
> Cheers,
> Mehmet
>
>
>> -----Original Message-----
>> From: ext Mykyta Yevstifeyev [mailto:evnikita2@gmail.com]
>> Sent: Thursday, January 13, 2011 1:58 AM
>> To: Ersue, Mehmet (NSN - DE/Munich); IETF Discussion
>> Subject: Re: Fwd: [OPS-DIR] OPS-DIR Review of
> draft-yevstifeyev-tn3270-
>> uri-12
>>
>> 12.01.2011 14:19, Ersue, Mehmet (NSN - DE/Munich) wrote:
>>> -----Original Message-----
>>> From: ops-dir-bounces@ietf.org [mailto:ops-dir-bounces@ietf.org] On
>>> Behalf Of ext Ersue, Mehmet (NSN - DE/Munich)
>>> Sent: Wednesday, January 12, 2011 1:07 PM
>>> To: ops-dir@ietf.org
>>> Cc: draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org
>>> Subject: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
>>>
>>> I reviewed draft-yevstifeyev-tn3270-uri-12 for its operational
>> impacts..
>>> Summary:
>>> The document gives a specification of syntax, semantics and use of
>>> 'tn3270' URI scheme.
>>>
>>> Obviously this is an individual submission without any document
>> write-up
>>> and supporting AD.
>> Why without?  Peter Saint-Andre is sponsoring AD.
>>> I would like to read a document write-up with the regular template
>> even
>>> if it is written by the author.
>>>
>>> The main purpose of the document, namely to update the IANA
>> registration
>>> of tn3270 URI scheme using the given registration template, should
> be
>>> added to the Introduction section. In general I would suggest to
>> include
>>> in the Introduction section the purpose of the action and more
>>> importantly why existing IANA registrations are not sufficient and
>> why
>>> the publication of this RFC is needed.
>> Agreed.  I'll add that as soon as possible.
>>> Obviously the GEN-Area reviewer (Tom Petch) has an opposite opinion
>> and
>>> does not see this IANA registration in the interest of IETF (see
>>>
> https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=55119&tid=12
>> 9
>>> 4831574). The reviewer furthermore states, following the rules in
>>> RFC4395 the document should provide concrete contact information for
>> the
>>> editor instead of an anonymous email address only.
>> That would be corrected so that the author will be IETF and contact -
>> IESG.
>>> I don't see any additional operation impact other than above.
>>>
>>> Other issues:
>>>
>>> - The used language needs some polishing.
>>>
>>> - Following are draft nits suggesting correction:
>>>
>>> == The copyright year in the IETF Trust and authors Copyright Line
>> does
>>> not
>>>      match the current year
>>>
>>> ->   Use new template or: s/2010/2011/
>> Will be corrected.
>>> -- Obsolete informational reference (is this intentional?): RFC 1738
>>>      (Obsoleted by RFC 4248, RFC 4266)
>>>
>>> ->   Use correct reference or clarify.
>> Obsolete Informational references are allowed.  I don't see a problem
>> here.
>>
>> Mykyta
>>> Mehmet
>>>
>>> _______________________________________________
>>> OPS-DIR mailing list
>>> OPS-DIR@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ops-dir
>>>
>


From julian.reschke@gmx.de  Thu Jan 13 07:56: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 54D653A6BB2 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 07:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.055
X-Spam-Level: 
X-Spam-Status: No, score=-104.055 tagged_above=-999 required=5 tests=[AWL=-1.456, 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 2g1nJJZZX+bg for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 07:56:11 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id D7CDB3A6BAC for <ietf@ietf.org>; Thu, 13 Jan 2011 07:56:10 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 15:58:30 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp026) with SMTP; 13 Jan 2011 16:58:30 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX188teAovX88BSFnh4YrnejnC7RTbTb7cr8Wqg7SSp /49bH9EihZqiG0
Message-ID: <4D2F211E.4080207@gmx.de>
Date: Thu, 13 Jan 2011 16:58:22 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com>
In-Reply-To: <4D2F1F8F.5060304@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Thu, 13 Jan 2011 15:56:12 -0000

On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
> ...
>> That sounds like an editorial error to me.
>>
>> "any ranges to be *reserved* for .... "Unassigned"..."
>>
>> doesn't make any sense at all. They are not reserved.
> Yes, that is a type of error, but the meaning is that unassigned and
> reserved values MUST (yes, must, that is in RFC 5226; see citation
> below) be mentioned.

I do not see a citation "below".

>> This should probably be raised as erratum.
>>
>>> So the document specifying the regsitry MUST mention what are
>>> Unassigned. Moreover, IMO, it would be useful to assign one value for
>>> Experimentation.
>>
>> No. should != must.
> See below.

Even further? :-)

>> There are tons of registries where this is not the case; namely all or
>> most of those where the values are strings, not numbers.
> The strings registries are rather exceptions from the rule I cited above.

Well, we have many of them. The rules should takes those into account.

Best regards, Julian

From evnikita2@gmail.com  Thu Jan 13 08:05:58 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 F14823A6BA2 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:05:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.293
X-Spam-Level: 
X-Spam-Status: No, score=-2.293 tagged_above=-999 required=5 tests=[AWL=-0.654, 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 o+H5NGvAd94s for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:05:58 -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 03EAF3A6BA0 for <ietf@ietf.org>; Thu, 13 Jan 2011 08:05:57 -0800 (PST)
Received: by eyd10 with SMTP id 10so957997eyd.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 08:08:20 -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=a0dBMKCtRXUY8Hz3FOJAtn4bV5RcVbQesp0LpF293Jk=; b=tXdly7FzUl0vmdshRpMvMQo/LpnxIPS+Wjnw6hFWk0MVASMsR3YcpiUvcBDnQkjKu9 Q6NQX6QfBQNAts+K6mJgq/aJDeejMakjwKma7jZmSCf7Fn4LkV0t2SSvoDSULdZiznNG 9elxdw65nimX/QOYbqWzaRFFivawtZ9niyOKY=
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=ksN0RyXTxpDJz2bI3KWzmsd6VQTP202CFQ3eyB4fIzj5FTEvcTTlbGqR3zvfUDAIFT ozwFjaahy53F3axIJDg9SnHT7dwuZVSncjIr8NWv622bGJlC08036JtAaIWXTwELJm1W u43sDGaTOyi6J+lN0k8mmdGOVvZkMPROahmlE=
Received: by 10.204.126.230 with SMTP id d38mr1891900bks.120.1294934900249; Thu, 13 Jan 2011 08:08:20 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id q18sm757154bka.3.2011.01.13.08.08.18 (version=SSLv3 cipher=RC4-MD5); Thu, 13 Jan 2011 08:08:19 -0800 (PST)
Message-ID: <4D2F2385.6050301@gmail.com>
Date: Thu, 13 Jan 2011 18:08:37 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de>
In-Reply-To: <4D2F211E.4080207@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Thu, 13 Jan 2011 16:05:59 -0000

13.01.2011 17:58, Julian Reschke wrote:
> On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
>> ...
>>> That sounds like an editorial error to me.
>>>
>>> "any ranges to be *reserved* for .... "Unassigned"..."
>>>
>>> doesn't make any sense at all. They are not reserved.
>> Yes, that is a type of error, but the meaning is that unassigned and
>> reserved values MUST (yes, must, that is in RFC 5226; see citation
>> below) be mentioned.
>
> I do not see a citation "below".
I meant in the previous message.
>
>>> This should probably be raised as erratum.
>>>
>>>> So the document specifying the regsitry MUST mention what are
>>>> Unassigned. Moreover, IMO, it would be useful to assign one value for
>>>> Experimentation.
>>>
>>> No. should != must.
>> See below.
>
> Even further? :-)
The same.
>
>>> There are tons of registries where this is not the case; namely all or
>>> most of those where the values are strings, not numbers.
>> The strings registries are rather exceptions from the rule I cited 
>> above.
>
> Well, we have many of them. The rules should takes those into account.
That, IMO, was the mistake of authors of RFC 5226 that didn't take the 
text registries into considerations.  We have no way to correct that now.

Mykyta
>
> Best regards, Julian
>


From julian.reschke@gmx.de  Thu Jan 13 08:08:36 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 BEEEB3A6BAC for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:08:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.046
X-Spam-Level: 
X-Spam-Status: No, score=-104.046 tagged_above=-999 required=5 tests=[AWL=-1.447, 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 QXxH7foV8Zhg for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:08:36 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 88C5B3A6BA0 for <ietf@ietf.org>; Thu, 13 Jan 2011 08:08:34 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 16:10:54 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp002) with SMTP; 13 Jan 2011 17:10:54 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+o+iIuxe2ociT/sSfnZZ9ATgp3gaebQiAmJvkFuP 8IjfHsYvg62N3j
Message-ID: <4D2F2402.401@gmx.de>
Date: Thu, 13 Jan 2011 17:10:42 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de> <4D2F2385.6050301@gmail.com>
In-Reply-To: <4D2F2385.6050301@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Thu, 13 Jan 2011 16:08:36 -0000

On 13.01.2011 17:08, Mykyta Yevstifeyev wrote:
> 13.01.2011 17:58, Julian Reschke wrote:
>> On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
>>> ...
>>>> That sounds like an editorial error to me.
>>>>
>>>> "any ranges to be *reserved* for .... "Unassigned"..."
>>>>
>>>> doesn't make any sense at all. They are not reserved.
>>> Yes, that is a type of error, but the meaning is that unassigned and
>>> reserved values MUST (yes, must, that is in RFC 5226; see citation
>>> below) be mentioned.
>>
>> I do not see a citation "below".
> I meant in the previous message.

Please cite where the spec says "must" or "MUST".

> ...
>>> The strings registries are rather exceptions from the rule I cited
>>> above.
>>
>> Well, we have many of them. The rules should takes those into account.
> That, IMO, was the mistake of authors of RFC 5226 that didn't take the
> text registries into considerations. We have no way to correct that now.
> ...

We can raise errata, and have the authors and the IESG approve them. We 
can also use common sense, and note that IANA apparently doesn't enforce 
these rules when they do not make sense.

Best regards, Julian

From evnikita2@gmail.com  Thu Jan 13 08:11:42 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 749973A6BAB for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:11:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.287
X-Spam-Level: 
X-Spam-Status: No, score=-2.287 tagged_above=-999 required=5 tests=[AWL=-0.649, 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 1Ph+x8Cbf1XR for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:11:41 -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 1CF683A6BA0 for <ietf@ietf.org>; Thu, 13 Jan 2011 08:11:40 -0800 (PST)
Received: by bwz12 with SMTP id 12so1793764bwz.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 08:14: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=QrI72wRZT2waozV+Kx4Ocw8Qwa0Q16aU4yKVGjrmtRY=; b=oM5Pkht4qme6IwI0vKapIpMfPfDY2L1vIUAHx+/wDqzgEJxyOAOs2zOxAHziBZivwc EvW7zitb9mGnDPzdQ4De1NpaLOJZifjVE4Bjn3WFCb+0XFCWrX0894d+yoDovXcuaVJM TWY8X8JaJZ9WZtQhAfHfUwpSePXdYrv6GxM5I=
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=nxzOOrJFGCex73Ic+Ckus4140fOFDo7dVPwk+jeFLZseVkAM1VRBz3qbOhg1eITPiZ w8CjBMVUr3WAWtF9VOxDMjBGLlOUEwkLgsbvletdX9YSMRCpH5UDIAOQy3Wwu4spt/Gd Nft1SbKmxryEXXaUbeLFi7cJninW2Nk8LGeDM=
Received: by 10.204.62.73 with SMTP id w9mr1922102bkh.11.1294935243184; Thu, 13 Jan 2011 08:14:03 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id b6sm758591bkb.10.2011.01.13.08.14.01 (version=SSLv3 cipher=RC4-MD5); Thu, 13 Jan 2011 08:14:02 -0800 (PST)
Message-ID: <4D2F24DC.4070908@gmail.com>
Date: Thu, 13 Jan 2011 18:14:20 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de> <4D2F2385.6050301@gmail.com> <4D2F2402.401@gmx.de>
In-Reply-To: <4D2F2402.401@gmx.de>
Content-Type: multipart/alternative; boundary="------------030807000008040807040605"
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: Thu, 13 Jan 2011 16:11:42 -0000

This is a multi-part message in MIME format.
--------------030807000008040807040605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

13.01.2011 18:10, Julian Reschke wrote:
> On 13.01.2011 17:08, Mykyta Yevstifeyev wrote:
>> 13.01.2011 17:58, Julian Reschke wrote:
>>> On 13.01.2011 16:51, Mykyta Yevstifeyev wrote:
>>>> ...
>>>>> That sounds like an editorial error to me.
>>>>>
>>>>> "any ranges to be *reserved* for .... "Unassigned"..."
>>>>>
>>>>> doesn't make any sense at all. They are not reserved.
>>>> Yes, that is a type of error, but the meaning is that unassigned and
>>>> reserved values MUST (yes, must, that is in RFC 5226; see citation
>>>> below) be mentioned.
>>>
>>> I do not see a citation "below".
>> I meant in the previous message.
>
> Please cite where the spec says "must" or "MUST".
That is a citation of RFC 5226

<...>
Documents that create a new namespace (or modify the definition of an
existing space) and that expect IANA to play a role in maintaining
that space (e.g., serving as a repository for registered values) MUST
provide clear instructions on details of the namespace.  In
particular, instructions *MUST* include:
<...>
5) Initial assignments and reservations.  Clear instructions should be
provided to identify any initial assignments or registrations.  In
addition, any ranges that are to be reserved  for "Private Use",
"Reserved", **"Unassigned"**, etc. should be *clearly indicated*.
<...>
>
>> ...
>>>> The strings registries are rather exceptions from the rule I cited
>>>> above.
>>>
>>> Well, we have many of them. The rules should takes those into account.
>> That, IMO, was the mistake of authors of RFC 5226 that didn't take the
>> text registries into considerations. We have no way to correct that now.
>> ...
>
> We can raise errata, and have the authors and the IESG approve them. 
> We can also use common sense, and note that IANA apparently doesn't 
> enforce these rules when they do not make sense.
>
> Best regards, Julian
>


--------------030807000008040807040605
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">
    13.01.2011 18:10, Julian Reschke wrote:
    <blockquote cite="mid:4D2F2402.401@gmx.de" type="cite">On 13.01.2011
      17:08, Mykyta Yevstifeyev wrote:
      <br>
      <blockquote type="cite">13.01.2011 17:58, Julian Reschke wrote:
        <br>
        <blockquote type="cite">On 13.01.2011 16:51, Mykyta Yevstifeyev
          wrote:
          <br>
          <blockquote type="cite">...
            <br>
            <blockquote type="cite">That sounds like an editorial error
              to me.
              <br>
              <br>
              "any ranges to be *reserved* for .... "Unassigned"..."
              <br>
              <br>
              doesn't make any sense at all. They are not reserved.
              <br>
            </blockquote>
            Yes, that is a type of error, but the meaning is that
            unassigned and
            <br>
            reserved values MUST (yes, must, that is in RFC 5226; see
            citation
            <br>
            below) be mentioned.
            <br>
          </blockquote>
          <br>
          I do not see a citation "below".
          <br>
        </blockquote>
        I meant in the previous message.
        <br>
      </blockquote>
      <br>
      Please cite where the spec says "must" or "MUST".
      <br>
    </blockquote>
    That is a citation of RFC 5226<br>
    <br>
    &lt;...&gt;
    <br>
    Documents that create a new namespace (or modify the definition of
    an
    <br>
    existing space) and that expect IANA to play a role in maintaining
    <br>
    that space (e.g., serving as a repository for registered values)
    MUST
    <br>
    provide clear instructions on details of the namespace.&nbsp; In
    <br>
    particular, instructions <b class="moz-txt-star"><span
        class="moz-txt-tag">*</span>MUST<span class="moz-txt-tag">*</span></b>
    include:
    <br>
    &lt;...&gt;
    <br>
    5) Initial assignments and reservations.&nbsp; Clear instructions should
    be
    <br>
    provided to identify any initial assignments or registrations.&nbsp; In
    <br>
    addition, any ranges that are to be reserved&nbsp; for "Private Use",
    <br>
    "Reserved", *<b>"Unassigned"</b>*, etc. should be <b
      class="moz-txt-star"><span class="moz-txt-tag">*</span>clearly
      indicated<span class="moz-txt-tag">*</span></b>.
    <br>
    &lt;...&gt;
    <br>
    <blockquote cite="mid:4D2F2402.401@gmx.de" type="cite">
      <br>
      <blockquote type="cite">...
        <br>
        <blockquote type="cite">
          <blockquote type="cite">The strings registries are rather
            exceptions from the rule I cited
            <br>
            above.
            <br>
          </blockquote>
          <br>
          Well, we have many of them. The rules should takes those into
          account.
          <br>
        </blockquote>
        That, IMO, was the mistake of authors of RFC 5226 that didn't
        take the
        <br>
        text registries into considerations. We have no way to correct
        that now.
        <br>
        ...
        <br>
      </blockquote>
      <br>
      We can raise errata, and have the authors and the IESG approve
      them. We can also use common sense, and note that IANA apparently
      doesn't enforce these rules when they do not make sense.
      <br>
      <br>
      Best regards, Julian
      <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------030807000008040807040605--

From julian.reschke@gmx.de  Thu Jan 13 08:17:32 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 535073A6BA0 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.037
X-Spam-Level: 
X-Spam-Status: No, score=-104.037 tagged_above=-999 required=5 tests=[AWL=-1.438, 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 wvJn+EcaSQ8O for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 08:17:31 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 1FAB93A6A46 for <ietf@ietf.org>; Thu, 13 Jan 2011 08:17:30 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 16:19:50 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp055) with SMTP; 13 Jan 2011 17:19:50 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/sxXQhvQjseQdIP8OONtIiVjF+DrPvHHWUtZK3g2 OOP1R35hcO8E8k
Message-ID: <4D2F261A.6040105@gmx.de>
Date: Thu, 13 Jan 2011 17:19:38 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de> <4D2F2385.6050301@gmail.com> <4D2F2402.401@gmx.de> <4D2F24DC.4070908@gmail.com>
In-Reply-To: <4D2F24DC.4070908@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Thu, 13 Jan 2011 16:17:32 -0000

On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
> <...>
> Documents that create a new namespace (or modify the definition of an
> existing space) and that expect IANA to play a role in maintaining
> that space (e.g., serving as a repository for registered values) MUST
> provide clear instructions on details of the namespace. In
> particular, instructions *MUST* include:
> <...>
> 5) Initial assignments and reservations. Clear instructions should be
> provided to identify any initial assignments or registrations. In
> addition, any ranges that are to be reserved for "Private Use",
> "Reserved", **"Unassigned"**, etc. should be *clearly indicated*.
> <...>

Yes.

There's still no "MUST" applying to unassigned code points. Note the "In 
addition" and "should".

> ...

Best regards, Julian

From mehmet.ersue@nsn.com  Thu Jan 13 03:26:39 2011
Return-Path: <mehmet.ersue@nsn.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 505A13A6B75; Thu, 13 Jan 2011 03:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.706
X-Spam-Level: 
X-Spam-Status: No, score=-104.706 tagged_above=-999 required=5 tests=[AWL=1.893, 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 xS7cKr9qxpYR; Thu, 13 Jan 2011 03:26:38 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by core3.amsl.com (Postfix) with ESMTP id 095EA3A6B11; Thu, 13 Jan 2011 03:26:37 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id p0DBSwit010931 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 13 Jan 2011 12:28:58 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id p0DBSvF9003550; Thu, 13 Jan 2011 12:28:58 +0100
Received: from DEMUEXC006.nsn-intra.net ([10.150.128.18]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 12:28:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
Date: Thu, 13 Jan 2011 12:28:53 +0100
Message-ID: <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>
In-Reply-To: <4D2E4DFF.6020507@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
Thread-Index: AcuyvNY4Qno32mm3QoeJ3+qPq/+/5wAV92Ew
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com>
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "ext Mykyta Yevstifeyev" <evnikita2@gmail.com>, "IETF Discussion" <ietf@ietf.org>
X-OriginalArrivalTime: 13 Jan 2011 11:28:55.0108 (UTC) FILETIME=[0FCEB040:01CBB315]
X-Mailman-Approved-At: Thu, 13 Jan 2011 08:17:59 -0800
Cc: ops-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, 13 Jan 2011 11:26:40 -0000

> > The reviewer furthermore states, following the rules in
> > RFC4395 the document should provide concrete contact information for
the
> > editor instead of an anonymous email address only.
> That would be corrected so that the author will be IETF and contact -
IESG.

I am not really sure whether this is appropriate.

Why are you keen of keeping it more or less anonymous?

Cheers,
Mehmet


> -----Original Message-----
> From: ext Mykyta Yevstifeyev [mailto:evnikita2@gmail.com]
> Sent: Thursday, January 13, 2011 1:58 AM
> To: Ersue, Mehmet (NSN - DE/Munich); IETF Discussion
> Subject: Re: Fwd: [OPS-DIR] OPS-DIR Review of
draft-yevstifeyev-tn3270-
> uri-12
>=20
> 12.01.2011 14:19, Ersue, Mehmet (NSN - DE/Munich) wrote:
> > -----Original Message-----
> > From: ops-dir-bounces@ietf.org [mailto:ops-dir-bounces@ietf.org] On
> > Behalf Of ext Ersue, Mehmet (NSN - DE/Munich)
> > Sent: Wednesday, January 12, 2011 1:07 PM
> > To: ops-dir@ietf.org
> > Cc: draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org
> > Subject: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
> >
> > I reviewed draft-yevstifeyev-tn3270-uri-12 for its operational
> impacts..
> >
> > Summary:
> > The document gives a specification of syntax, semantics and use of
> > 'tn3270' URI scheme.
> >
> > Obviously this is an individual submission without any document
> write-up
> > and supporting AD.
> Why without?  Peter Saint-Andre is sponsoring AD.
> > I would like to read a document write-up with the regular template
> even
> > if it is written by the author.
> >
> > The main purpose of the document, namely to update the IANA
> registration
> > of tn3270 URI scheme using the given registration template, should
be
> > added to the Introduction section. In general I would suggest to
> include
> > in the Introduction section the purpose of the action and more
> > importantly why existing IANA registrations are not sufficient and
> why
> > the publication of this RFC is needed.
> Agreed.  I'll add that as soon as possible.
> > Obviously the GEN-Area reviewer (Tom Petch) has an opposite opinion
> and
> > does not see this IANA registration in the interest of IETF (see
> >
>
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D5511=
9&tid=3D12
> 9
> > 4831574). The reviewer furthermore states, following the rules in
> > RFC4395 the document should provide concrete contact information for
> the
> > editor instead of an anonymous email address only.
> That would be corrected so that the author will be IETF and contact -
> IESG.
> > I don't see any additional operation impact other than above.
> >
> > Other issues:
> >
> > - The used language needs some polishing.
> >
> > - Following are draft nits suggesting correction:
> >
> > =3D=3D The copyright year in the IETF Trust and authors Copyright =
Line
> does
> > not
> >     match the current year
> >
> > ->  Use new template or: s/2010/2011/
> Will be corrected.
> > -- Obsolete informational reference (is this intentional?): RFC 1738
> >     (Obsoleted by RFC 4248, RFC 4266)
> >
> > ->  Use correct reference or clarify.
> Obsolete Informational references are allowed.  I don't see a problem
> here.
>=20
> Mykyta
> >
> > Mehmet
> >
> > _______________________________________________
> > OPS-DIR mailing list
> > OPS-DIR@ietf.org
> > https://www.ietf.org/mailman/listinfo/ops-dir
> >


From dworley@avaya.com  Thu Jan 13 09:40:59 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 5A2DD3A6BBA; Thu, 13 Jan 2011 09:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, 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 b7ThmI0gQqAO; Thu, 13 Jan 2011 09:40:58 -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 73AE43A6B3C; Thu, 13 Jan 2011 09:40:58 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOrILk3GmAcF/2dsb2JhbACkSHOnBQKWKoVMBIRoiWSCWw
X-IronPort-AV: E=Sophos;i="4.60,318,1291611600"; d="scan'208";a="259476862"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 13 Jan 2011 12:43:18 -0500
X-IronPort-AV: E=Sophos;i="4.60,318,1291611600"; d="scan'208";a="569979984"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Jan 2011 12:43:18 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.160]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Thu, 13 Jan 2011 12:43:17 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>, "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
Date: Thu, 13 Jan 2011 12:42:29 -0500
Subject: RE: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
Thread-Topic: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
Thread-Index: AcuzOmAaKOkzMyhITqmky0qnoN3VDwADt/aL
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com>
In-Reply-To: <4D2F2089.2000306@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: "ops-dir@ietf.org" <ops-dir@ietf.org>, IETF Discussion <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, 13 Jan 2011 17:40:59 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mykyta Yev=
stifeyev [evnikita2@gmail.com]

Mentioning my full contact data makes no sense.  I can hardly imagine
that somebody will come to Ukraine, search Kotovsk (that is rather small
town) and than particular street, etc. to ask me about the URI scheme.
Those who want that would prefer to contact me by email.
_______________________________________________

In many cases, a person's postal address is more stable and easier to trans=
late into other contact information than the person's e-mail address.

Dale

From ole@cisco.com  Thu Jan 13 09:50:52 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 238683A6A50; Thu, 13 Jan 2011 09:50:52 -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 GTAHOQDj5KwP; Thu, 13 Jan 2011 09:50:50 -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 A06993A6A61; Thu, 13 Jan 2011 09:50:50 -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: AvsEAAfLLk1AaMHG/2dsb2JhbACkS3OkU4JRDgGVboMOgj4EhGiBNIQog26CdQ
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-2.cisco.com with ESMTP; 13 Jan 2011 17:53:12 +0000
Received: from [10.24.17.59] ([10.24.17.59]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0DHr9Jr011355; Thu, 13 Jan 2011 17:53:10 GMT
Date: Thu, 13 Jan 2011 09:53:08 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: RE: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com>
Message-ID: <alpine.OSX.2.00.1101130945300.96657@173-11-110-133-sfba.hfc.comcastbusiness.net>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "Ersue, Mehmet \(NSN - DE/Munich\)" <mehmet.ersue@nsn.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, IETF Discussion <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: Thu, 13 Jan 2011 17:50:52 -0000

I agree with Dale. I have subscriber database of with around 30,000 
records and the "churn" in e-mail addresses is much higher than 
changes in postal information. Of course in (some parts of) the real 
world, the concept of forwarding, address correction etc exists so 
that I (sometimes) get notified of the new postal address. In most 
e-mail cases all I get is a mailer-daemon message.

I don't think there is any simple solution to the author contact 
information problem. Like most things, it will be correct at the
time of publication but subject to change in the future. Given that
RFCs are archival documents this could only be solved with some
large dynamic errata database that nobody is prepared to maintain
I am sure.

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj


On Thu, 13 Jan 2011, Worley, Dale R (Dale) wrote:

> ________________________________________

> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of 
> Mykyta Yevstifeyev [evnikita2@gmail.com]
> 
> Mentioning my full contact data makes no sense.  I can hardly imagine
> that somebody will come to Ukraine, search Kotovsk (that is rather small
> town) and than particular street, etc. to ask me about the URI scheme.
> Those who want that would prefer to contact me by email.
> _______________________________________________
> 
> In many cases, a person's postal address is more stable and easier 
> to translate into other contact information than the person's e-mail 
> address.
> 
> Dale


From jmh@joelhalpern.com  Thu Jan 13 09:51:06 2011
Return-Path: <jmh@joelhalpern.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 6C3FF28C13D; Thu, 13 Jan 2011 09:51:06 -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 OrQ4UYXyqjLH; Thu, 13 Jan 2011 09:51:04 -0800 (PST)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id BE7623A6A51; Thu, 13 Jan 2011 09:51:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 19A13325ABE9; Thu, 13 Jan 2011 09:53:24 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.101] (pool-71-161-51-169.clppva.btas.verizon.net [71.161.51.169]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 22DF8322822F; Thu, 13 Jan 2011 09:53:23 -0800 (PST)
Message-ID: <4D2F3C11.7000904@joelhalpern.com>
Date: Thu, 13 Jan 2011 12:53:21 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.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: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Ersue, Mehmet \(NSN - DE/Munich\)" <mehmet.ersue@nsn.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>, IETF Discussion <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, 13 Jan 2011 17:51:06 -0000

I would also point out that there is a difference between a contact for 
a draft and a contact for a registry.
For a draft, there is always an individual contact.  We frequently 
accept that the only contact information is an email address.

For a registry, the contact information requirement depends upon what 
the update policy is for the registry.

Yours,
Joel

On 1/13/2011 12:42 PM, Worley, Dale R (Dale) wrote:
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mykyta Yevstifeyev [evnikita2@gmail.com]
>
> Mentioning my full contact data makes no sense.  I can hardly imagine
> that somebody will come to Ukraine, search Kotovsk (that is rather small
> town) and than particular street, etc. to ask me about the URI scheme.
> Those who want that would prefer to contact me by email.
> _______________________________________________
>
> In many cases, a person's postal address is more stable and easier to translate into other contact information than the person's e-mail address.
>
> Dale
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From stpeter@stpeter.im  Thu Jan 13 10:10:00 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 254183A6A6D for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 10:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.636
X-Spam-Level: 
X-Spam-Status: No, score=-102.636 tagged_above=-999 required=5 tests=[AWL=-0.037, 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 LC88FQ0H9euu for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 10:09:59 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 196BF3A683D for <ietf@ietf.org>; Thu, 13 Jan 2011 10:09:59 -0800 (PST)
Received: from dhcp-64-101-72-173.cisco.com (dhcp-64-101-72-173.cisco.com [64.101.72.173]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 39433400EE; Thu, 13 Jan 2011 11:27:27 -0700 (MST)
Message-ID: <4D2F4086.3050601@stpeter.im>
Date: Thu, 13 Jan 2011 11:12:22 -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: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12)
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com> <4D2F3C11.7000904@joelhalpern.com>
In-Reply-To: <4D2F3C11.7000904@joelhalpern.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="------------ms060200060206030606060701"
Cc: IETF Discussion <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, 13 Jan 2011 18:10:00 -0000

This is a cryptographically signed message in MIME format.

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

On 1/13/11 10:53 AM, Joel M. Halpern wrote:
> I would also point out that there is a difference between a contact for=

> a draft and a contact for a registry.
> For a draft, there is always an individual contact.  We frequently
> accept that the only contact information is an email address.
>=20
> For a registry, the contact information requirement depends upon what
> the update policy is for the registry.

For what it's worth, Section 10 of the informational RFC 2223
("Instructions to RFC Authors") states:

   Each RFC must have at the very end a section giving the author's
   address, including the name and postal address, the telephone number,
   (optional: a FAX number) and the Internet email address.

However, I agree that inclusion of all but the name and email address
has not been enforced.

Peter

--
Peter Saint-Andre
https://stpeter.im/


--------------ms060200060206030606060701
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
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEx
MzE4MTIyMlowIwYJKoZIhvcNAQkEMRYEFEThGzbDktNiefdK0UQZWrYcjBV+MF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQBszvM6t5/jSkgCN7k1Fi1GCyoGwnM3St7dr1ouxn0FpZgR/pxM998+EGxy
NDsVwW8uGW2JmJstNFC2XiGWFtjY6Nr6wyJ/sRcr1h9OX3fnXf24ZjmOnbJv3BC+x7rJ0HXP
kxhkU2Tl+jiGgODQqmY/MiGASRHmV0OV/5jYSj72sgpTLb9GewjtN1eJTL9QFDJ/+HSGdCvq
CvCjyj3bJqhwnjMAOUmcPH8ecpRdEQA86/dDCMrns8Tdqv3dmiJFPDJVG1HhnQqIg7goUGxG
Ry2ZBXKOneQIkpZ2CcMBExb6pcyTE/aDWcrouhtp2kLutXuRv6kJo1cpj5xTG3ksL9aVAAAA
AAAA
--------------ms060200060206030606060701--

From michelle.cotton@icann.org  Thu Jan 13 12:40:52 2011
Return-Path: <michelle.cotton@icann.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 737CA3A6A90 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 12:40:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.443
X-Spam-Level: 
X-Spam-Status: No, score=-106.443 tagged_above=-999 required=5 tests=[AWL=0.156, 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 CarsBGamRkBW for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 12:40:51 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 8309F3A6A86 for <ietf@ietf.org>; Thu, 13 Jan 2011 12:40:51 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 13 Jan 2011 12:43:14 -0800
From: Michelle Cotton <michelle.cotton@icann.org>
To: Julian Reschke <julian.reschke@gmx.de>, Adrian Farrel <adrian.farrel@huawei.com>
Date: Thu, 13 Jan 2011 12:43:11 -0800
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
Thread-Topic: Last Call on draft-ietf-pim-registry-03.txt
Thread-Index: AcuyZhh0yZW4n6xvRr+sysI0AFMUMgA/GVpg
Message-ID: <C954A3DF.2B01C%michelle.cotton@icann.org>
In-Reply-To: <4D2DBC48.2080302@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'The IETF' <ietf@ietf.org>, "stig@cisco.com" <stig@cisco.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: Thu, 13 Jan 2011 20:40:52 -0000

Many believe it makes it very clear to the users of the registry what is
available for assignment.  Something we will be rolling out soon (for those
registries with a finite space) will be small charts showing how much of th=
e
registry space is unassigned, assigned and reserved (utilizing the
unassigned entries).
--Michelle


On 1/12/11 6:35 AM, "Julian Reschke" <julian.reschke@gmx.de> wrote:

> On 12.01.2011 15:22, Adrian Farrel wrote:
>> Entirely at random I clicked on:
>>=20
>> http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml
>> http://www.iana.org/assignments/calipso/calipso.xhtml
>> http://www.iana.org/assignments/lmp-parameters
>>=20
>> Looks like IANA tries to fill up all the blanks with markers of "unassig=
ned".
>>=20
>> Is that harmful?
>=20
> Minimally, it's redundant. Also, it only makes sense on certain types of
> registries.
>=20
> I just checked the XML version of the first registry, and, indeed, it
> contains entries for unassigned values. /me shakes head in disbelief.
>=20
> What *should* be done is computing the unassigned ranges for
> *presentation*; that is, they should not be part of the actual registry.
> The way it's done currently defeats one of the reasons of having a
> machine-readable registry (consumers will have to hard-wire knowledge of
> the specific "unassigned" entry to make sense of the registry).
>=20
> Best regards, Julian
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From julian.reschke@gmx.de  Thu Jan 13 13:11:59 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 72CCC3A6BD8 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 13:11:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.027
X-Spam-Level: 
X-Spam-Status: No, score=-104.027 tagged_above=-999 required=5 tests=[AWL=-1.428, 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 JG9bYrKg+OPJ for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 13:11:58 -0800 (PST)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 3323D3A6BC9 for <ietf@ietf.org>; Thu, 13 Jan 2011 13:11:57 -0800 (PST)
Received: (qmail invoked by alias); 13 Jan 2011 21:14:18 -0000
Received: from p508FA62D.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.166.45] by mail.gmx.net (mp041) with SMTP; 13 Jan 2011 22:14:18 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+/az1FkcS/X+IfuWYJKqZej005ToE8G5H8bZlO3+ GuWqmtlkttAZOu
Message-ID: <4D2F6B19.1030407@gmx.de>
Date: Thu, 13 Jan 2011 22:14:01 +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: Michelle Cotton <michelle.cotton@icann.org>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <C954A3DF.2B01C%michelle.cotton@icann.org>
In-Reply-To: <C954A3DF.2B01C%michelle.cotton@icann.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "stig@cisco.com" <stig@cisco.com>, Adrian Farrel <adrian.farrel@huawei.com>, '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: Thu, 13 Jan 2011 21:11:59 -0000

On 13.01.2011 21:43, Michelle Cotton wrote:
>
> Many believe it makes it very clear to the users of the registry what is
> available for assignment.  Something we will be rolling out soon (for those
> registries with a finite space) will be small charts showing how much of the
> registry space is unassigned, assigned and reserved (utilizing the
> unassigned entries).
> --Michelle
> ...

Exactly my point -- we should distinguish between the actual registry 
contents (assigned / reserved), and how it's presented.

Best regards, Julian

From fluffy@cisco.com  Thu Jan 13 14:09:07 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 CC6A03A6BEE for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 14:09:07 -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 uR+xnVpZ1P6W for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 14:09:04 -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 1848D3A6A57 for <ietf@ietf.org>; Thu, 13 Jan 2011 14:09:04 -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: AvsEALsHL02rR7Ht/2dsb2JhbACkTXOkHJg2hUwEhGiGKIMi
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 13 Jan 2011 22:11:27 +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 p0DMBQMd028787; Thu, 13 Jan 2011 22:11:27 GMT
Subject: Re: Feedback on Day Passes
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4CF3F35E.5080302@gondrom.org>
Date: Thu, 13 Jan 2011 15:13:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C86774C-42FB-47A5-A373-B79B5C361439@cisco.com>
References: <9DDAD8FE-64E2-4396-A4D1-4A6F84F18AA7@gmail.com> <201011222128.oAMLSPAW002622@sj-core-4.cisco.com> <4CF3F35E.5080302@gondrom.org>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
X-Mailer: Apple Mail (2.1082)
Cc: 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: Thu, 13 Jan 2011 22:09:07 -0000

On Nov 29, 2010, at 11:39 AM, Tobias Gondrom wrote:

> Bob,
>=20
> agree with James request for more detail on the used day passes, if
> possible.
>=20
> Personally, I believe the risen cost for day passes probably knocked =
out
> some of the demand (basic supply-demand curve from economics ;-) ).
> Probably day passes are more attractive to local participants who want
> to get a taste of the IETF or only visit one WG session.=20

I you want to get a taste of IETF, you can do it for free. You join =
ISOC, which is free, then as an ISOC member you can come to IETF for =
free on the tuesday of any IETF meeting. You might not be able to go to =
the WG meeting you want if it is not on tuesday, but you can get a taste =
of IETF.=20

I think this is a good thing and have encouraged people to do it - it's =
how we get new people to IETF. I know there are some people that =
disagree with me because it basically results in tourists at the =
meetings. So far the number people doing this is so low that it is not a =
problem.=20



From krishnabirth@gmail.com  Thu Jan 13 15:43:23 2011
Return-Path: <krishnabirth@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 83F583A6C27 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 15:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 jUsI+S96Rjlb for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 15:43:22 -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 1C7373A6C25 for <ietf@ietf.org>; Thu, 13 Jan 2011 15:43:21 -0800 (PST)
Received: by wyf23 with SMTP id 23so2370799wyf.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 15:45:44 -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=Qsf7xYZKV5pRQ1WMg/ithJtcRuqoU1aJ2Mr33poSQsM=; b=VP36w7VCiIuIFpr9+OgZlQT9lOHz2kG6t/m4CZX/GEj7ruFQwoNyYW4wi3BZYEz907 GeaJ4pFVsTuCOmalXLUEHci/jnGtp0g1/oWxRSRRdpOr1EAqFB1+m/w16wRRM8h8sv6E oHVt1Vcjab6CMHjWSXRDp3uOuSNP0H3JMrqlQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TPQ+pusXQctIKoa6izia6QZJfuETuHvgTlCWyGo+2t28UXvmYQ51smQoVbJODGgCGy i6VYHaZQVcN4GL9E8tPix6qg+hmQ85LmAYNWxLKzJaAXf1GaRtmRoNd9cXWrzruGrrHY XNpPCcImp/BZbyaavn8l1CQLzuM78VYQ3n9No=
MIME-Version: 1.0
Received: by 10.216.51.67 with SMTP id a45mr1160461wec.19.1294962344143; Thu, 13 Jan 2011 15:45:44 -0800 (PST)
Received: by 10.216.153.136 with HTTP; Thu, 13 Jan 2011 15:45:44 -0800 (PST)
Date: Thu, 13 Jan 2011 23:45:44 +0000
Message-ID: <AANLkTi=tRXZ4gC_eVpCuLZe6tZuNeHu9z=ErVg_uEk1-@mail.gmail.com>
Subject: Increasing character limit for registration in internet domain names: 76 or 68 or 91 or 83 or 64 higher the better
From: Krishna Birth <krishnabirth@gmail.com>
To: ietf@ietf.org, unicode@unicode.org
Content-Type: multipart/alternative; boundary=0016e6dd8f98852ba40499c2eabc
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, 13 Jan 2011 23:44:55 -0000

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

(please view this email with UTF-8 enabled on your viewer)

This is a request for internet engineers to increase the character limit fo=
r
registration in the various internet domain names (com, net, org, info etc)
from 63 characters to more at least 76 or 68 or 91 or 83 or 64, the higher
it is the better.  I believe the raising the characters on the internet
domain names will very good from a spiritual perspective.  I base these
figures on the spiritual prayer and chant:

harekrishnaharekrishnakrishnakrishnahareharehareramahareramaramaramaharehar=
e
=3D 76 characters

harekrsnaharekrsnakrsnakrsnahareharehareramahareramaramaramaharehare =3D 68
characters

hare-krishna-hare-krishna-krishna-krishna-hare-hare-hare-rama-hare-rama-ram=
a-rama-hare-hare
=3D 91 characters

hare-krsna-hare-krsna-krsna-krsna-hare-hare-hare-rama-hare-rama-rama-rama-h=
are-hare
=3D 83 characters

harekrsnaharekrsnakrsnakrsnahareharehareramhareramramramharehare =3D 64
characters


It would allow the Hare =E0=A4=95rishna Mahamantra, the great prayer for de=
liverance
in this Age to be fully put on an internet domain name.  The chanting and
recitation of the Mahamantra cleanses the heart of the impurities and
pollution.  Caitanya Mahaprabhu and incarnation of =E0=A4=95rishna, the Sup=
reme
Personality of Godhead Movement, popularised the chanting of the Mahamantra
some 500 years ago and is meant for every town and village in the world.

Now His Divine Grace A C Bha=E0=A4=95tivedanta Swami  Prabhupada, Founder, =
Eternal
Di=E0=A4=95sa and Si=E0=A4=95sa Spiritual Master of the Hare =E0=A4=95rishn=
a Movement in the chain
of disciplic succession has popularised it in the West and continues to
popularise.


p.s. Some time ago I posted on the IETF mailing list via another email
account.


Best,


Mee=E0=A4=95u

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

(please view this email with UTF-8 enabled on your viewer)<br><br>This is a=
 request for internet engineers to increase the character limit for registr=
ation in the various internet domain names (com, net, org, info etc) from 6=
3 characters to more at least 76 or 68 or 91 or 83 or 64, the higher it is =
the better.=C2=A0 I believe the raising the characters on the internet doma=
in names will very good from a spiritual perspective.=C2=A0 I base these fi=
gures on the spiritual prayer and chant:<br>
<br>harekrishnaharekrishnakrishnakrishnahareharehareramahareramaramaramahar=
ehare =3D 76 characters<br>
<br>
harekrsnaharekrsnakrsnakrsnahareharehareramahareramaramaramaharehare =3D 68=
 characters<br>
<br>
hare-krishna-hare-krishna-krishna-krishna-hare-hare-hare-rama-hare-rama-ram=
a-rama-hare-hare =3D 91 characters<br>
<br>
hare-krsna-hare-krsna-krsna-krsna-hare-hare-hare-rama-hare-rama-rama-rama-h=
are-hare =3D 83 characters<br>
<br>
harekrsnaharekrsnakrsnakrsnahareharehareramhareramramramharehare =3D 64 cha=
racters<br><br><br>It would allow the Hare =E0=A4=95rishna Mahamantra, the =
great prayer for deliverance in this Age to be fully put on an internet dom=
ain name.=C2=A0 The chanting and recitation of the Mahamantra cleanses the =
heart of the impurities and pollution.=C2=A0 Caitanya Mahaprabhu and incarn=
ation of =E0=A4=95rishna, the Supreme Personality of Godhead Movement, popu=
larised the chanting of the Mahamantra some 500 years ago and is meant for =
every town and village in the world.=C2=A0 <br>
<br>Now His Divine Grace A C Bha=E0=A4=95tivedanta Swami=C2=A0 Prabhupada, =
Founder, Eternal Di=E0=A4=95sa and Si=E0=A4=95sa Spiritual Master of the Ha=
re =E0=A4=95rishna Movement in the chain of disciplic succession has popula=
rised it in the West and continues to popularise.<br>
<br><br>p.s. Some time ago I posted on the IETF mailing list via another em=
ail account.<br><br><br>Best,<br><br><br>Mee=E0=A4=95u

--0016e6dd8f98852ba40499c2eabc--

From hallam@gmail.com  Thu Jan 13 16:56:59 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 C7CA828C0EE for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 16:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.469
X-Spam-Level: 
X-Spam-Status: No, score=-3.469 tagged_above=-999 required=5 tests=[AWL=0.129,  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 dl2AyBZplepc for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 16:56:58 -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 549D228B23E for <ietf@ietf.org>; Thu, 13 Jan 2011 16:56:58 -0800 (PST)
Received: by ywk9 with SMTP id 9so759179ywk.31 for <ietf@ietf.org>; Thu, 13 Jan 2011 16:59:21 -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=iwiLSlA3UFd7TJ9Gf8E3WBoXIkpBakmy5cZoxnQP1YY=; b=sZ2EiqAcwXlc8vfjFGYNojCbmh+W4a8dr/Gil7cIIeGb0hyCVrkvSnCM+Lrf/M2Vge myDNOBaoWOzBN//ab2mnaluXex7cII5+A55dLu7c0DPXT7rg2fIdqjevN2+kFcpzF1db 3LVUjezes8Ha8sotuvwiLQtUYXJAL0jTsPt9M=
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=oT97gTpCWs+VuXLeC3URtUFMf4wE1JvWcmAiaW+TF6ZSGqmkaKRVaSww7aSnlq4yWh Gc3OjgpxhbLghiEmrCHuoO0ddAgbg9ElF5xr8W491DBdQO5p0OePWcnsYQDexVdfAU9C svMyyOLYD+G33Es46qHN7mnsJlPyxauahb2pI=
MIME-Version: 1.0
Received: by 10.100.242.4 with SMTP id p4mr151501anh.205.1294966761802; Thu, 13 Jan 2011 16:59:21 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Thu, 13 Jan 2011 16:59:21 -0800 (PST)
In-Reply-To: <AANLkTi=tRXZ4gC_eVpCuLZe6tZuNeHu9z=ErVg_uEk1-@mail.gmail.com>
References: <AANLkTi=tRXZ4gC_eVpCuLZe6tZuNeHu9z=ErVg_uEk1-@mail.gmail.com>
Date: Thu, 13 Jan 2011 19:59:21 -0500
Message-ID: <AANLkTi=rYs2dYNVDE2Vs__VJSX_n_fgfsC6jb86n7Tp5@mail.gmail.com>
Subject: Re: Increasing character limit for registration in internet domain names: 76 or 68 or 91 or 83 or 64 higher the better
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Krishna Birth <krishnabirth@gmail.com>
Content-Type: multipart/alternative; boundary=001636af0272d54f890499c3f168
Cc: ietf@ietf.org, unicode@unicode.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, 14 Jan 2011 00:57:00 -0000

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

Too many applications have the existing DNS segment lengths encoded.

I suggest that you instead consider.


hare.krishna.hare.krishna.krishna.krishna.hare.hare.hare.rama.hare.ramarama=
.rama.hare.hare

You would have to talk to ICANN to get the .hare TLD assigned.


On Thu, Jan 13, 2011 at 6:45 PM, Krishna Birth <krishnabirth@gmail.com>wrot=
e:

> (please view this email with UTF-8 enabled on your viewer)
>
> This is a request for internet engineers to increase the character limit
> for registration in the various internet domain names (com, net, org, inf=
o
> etc) from 63 characters to more at least 76 or 68 or 91 or 83 or 64, the
> higher it is the better.  I believe the raising the characters on the
> internet domain names will very good from a spiritual perspective.  I bas=
e
> these figures on the spiritual prayer and chant:
>
> harekrishnaharekrishnakrishnakrishnahareharehareramahareramaramaramahareh=
are
> =3D 76 characters
>
> harekrsnaharekrsnakrsnakrsnahareharehareramahareramaramaramaharehare =3D =
68
> characters
>
> hare-krishna-hare-krishna-krishna-krishna-hare-hare-hare-rama-hare-rama-r=
ama-rama-hare-hare
> =3D 91 characters
>
> hare-krsna-hare-krsna-krsna-krsna-hare-hare-hare-rama-hare-rama-rama-rama=
-hare-hare
> =3D 83 characters
>
> harekrsnaharekrsnakrsnakrsnahareharehareramhareramramramharehare =3D 64
> characters
>
>
> It would allow the Hare =E0=A4=95rishna Mahamantra, the great prayer for
> deliverance in this Age to be fully put on an internet domain name.  The
> chanting and recitation of the Mahamantra cleanses the heart of the
> impurities and pollution.  Caitanya Mahaprabhu and incarnation of =E0=A4=
=95rishna,
> the Supreme Personality of Godhead Movement, popularised the chanting of =
the
> Mahamantra some 500 years ago and is meant for every town and village in =
the
> world.
>
> Now His Divine Grace A C Bha=E0=A4=95tivedanta Swami  Prabhupada, Founder=
, Eternal
> Di=E0=A4=95sa and Si=E0=A4=95sa Spiritual Master of the Hare =E0=A4=95ris=
hna Movement in the chain
> of disciplic succession has popularised it in the West and continues to
> popularise.
>
>
> p.s. Some time ago I posted on the IETF mailing list via another email
> account.
>
>
> Best,
>
>
> Mee=E0=A4=95u
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>


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

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

Too many applications have the existing DNS segment lengths encoded.<div><b=
r></div><div>I suggest that you instead consider.</div><div><br><div><div><=
br></div><div><meta charset=3D"utf-8">hare.krishna.hare.krishna.krishna.kri=
shna.hare.hare.hare.rama.hare.ramarama.rama.hare.hare</div>
<div><br></div><div>You would have to talk to ICANN to get the .hare TLD as=
signed.</div><div><br><br><div class=3D"gmail_quote">On Thu, Jan 13, 2011 a=
t 6:45 PM, Krishna Birth <span dir=3D"ltr">&lt;<a href=3D"mailto:krishnabir=
th@gmail.com">krishnabirth@gmail.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;">(please view this email with UTF-8 enabled =
on your viewer)<br><br>This is a request for internet engineers to increase=
 the character limit for registration in the various internet domain names =
(com, net, org, info etc) from 63 characters to more at least 76 or 68 or 9=
1 or 83 or 64, the higher it is the better.=C2=A0 I believe the raising the=
 characters on the internet domain names will very good from a spiritual pe=
rspective.=C2=A0 I base these figures on the spiritual prayer and chant:<br=
>

<br>harekrishnaharekrishnakrishnakrishnahareharehareramahareramaramaramahar=
ehare =3D 76 characters<br>
<br>
harekrsnaharekrsnakrsnakrsnahareharehareramahareramaramaramaharehare =3D 68=
 characters<br>
<br>
hare-krishna-hare-krishna-krishna-krishna-hare-hare-hare-rama-hare-rama-ram=
a-rama-hare-hare =3D 91 characters<br>
<br>
hare-krsna-hare-krsna-krsna-krsna-hare-hare-hare-rama-hare-rama-rama-rama-h=
are-hare =3D 83 characters<br>
<br>
harekrsnaharekrsnakrsnakrsnahareharehareramhareramramramharehare =3D 64 cha=
racters<br><br><br>It would allow the Hare =E0=A4=95rishna Mahamantra, the =
great prayer for deliverance in this Age to be fully put on an internet dom=
ain name.=C2=A0 The chanting and recitation of the Mahamantra cleanses the =
heart of the impurities and pollution.=C2=A0 Caitanya Mahaprabhu and incarn=
ation of =E0=A4=95rishna, the Supreme Personality of Godhead Movement, popu=
larised the chanting of the Mahamantra some 500 years ago and is meant for =
every town and village in the world.=C2=A0 <br>

<br>Now His Divine Grace A C Bha=E0=A4=95tivedanta Swami=C2=A0 Prabhupada, =
Founder, Eternal Di=E0=A4=95sa and Si=E0=A4=95sa Spiritual Master of the Ha=
re =E0=A4=95rishna Movement in the chain of disciplic succession has popula=
rised it in the West and continues to popularise.<br>

<br><br>p.s. Some time ago I posted on the IETF mailing list via another em=
ail account.<br><br><br>Best,<br><br><br>Mee=E0=A4=95u
<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>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a href=3D=
"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div></div></div>

--001636af0272d54f890499c3f168--

From narten@us.ibm.com  Thu Jan 13 21:50:55 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 95B4B3A6926 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 21:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.061
X-Spam-Level: 
X-Spam-Status: No, score=-106.061 tagged_above=-999 required=5 tests=[AWL=0.538, 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 Q8pYAVYwPYVq for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 21:50:53 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by core3.amsl.com (Postfix) with ESMTP id AFEF63A6929 for <ietf@ietf.org>; Thu, 13 Jan 2011 21:50:50 -0800 (PST)
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id p0E5h5TS022249 for <ietf@ietf.org>; Thu, 13 Jan 2011 22:43:05 -0700
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p0E5r2sR164134 for <ietf@ietf.org>; Thu, 13 Jan 2011 22:53:02 -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 p0E5r2Qw010664 for <ietf@ietf.org>; Thu, 13 Jan 2011 22:53:02 -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 p0E5r1No010642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 13 Jan 2011 22:53:02 -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 p0E5r231009691 for <ietf@ietf.org>; Fri, 14 Jan 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p0E5r2is009677 for ietf@ietf.org; Fri, 14 Jan 2011 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201101140553.p0E5r2is009677@rotala.raleigh.ibm.com>
Date: Fri, 14 Jan 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, 14 Jan 2011 05:50:55 -0000

Total of 113 messages in the last 7 days.
 
script run at: Fri Jan 14 00:53:02 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  0.88% |    1 | 35.69% |   447080 | fred@cisco.com
  9.73% |   11 |  4.45% |    55771 | julian.reschke@gmx.de
  5.31% |    6 |  3.68% |    46098 | hannes.tschofenig@gmx.net
  5.31% |    6 |  3.54% |    44394 | evnikita2@gmail.com
  5.31% |    6 |  2.82% |    35297 | tme@americafree.tv
  4.42% |    5 |  2.58% |    32259 | john-ietf@jck.com
  4.42% |    5 |  2.46% |    30757 | daedulus@btconnect.com
  3.54% |    4 |  3.25% |    40724 | lixia@cs.ucla.edu
  2.65% |    3 |  3.30% |    41392 | hallam@gmail.com
  3.54% |    4 |  1.59% |    19924 | ynir@checkpoint.com
  2.65% |    3 |  1.64% |    20599 | sm@resistor.net
  1.77% |    2 |  2.33% |    29148 | ben@nostrum.com
  2.65% |    3 |  1.10% |    13813 | dhc2@dcrocker.net
  2.65% |    3 |  1.08% |    13513 | doug@ewellic.org
  1.77% |    2 |  1.75% |    21975 | fluffy@cisco.com
  1.77% |    2 |  1.03% |    12934 | henk@ripe.net
  1.77% |    2 |  1.02% |    12837 | d3e3e3@gmail.com
  1.77% |    2 |  1.02% |    12814 | jmh@joelhalpern.com
  1.77% |    2 |  0.99% |    12388 | bob.hinden@gmail.com
  1.77% |    2 |  0.96% |    12026 | vesely@tana.it
  1.77% |    2 |  0.96% |    12020 | joelja@bogus.com
  1.77% |    2 |  0.90% |    11228 | adrian.farrel@huawei.com
  1.77% |    2 |  0.86% |    10808 | jdfalk-lists@cybernothing.org
  1.77% |    2 |  0.81% |    10137 | randy_presuhn@mindspring.com
  0.88% |    1 |  1.59% |    19881 | tobias.gondrom@gondrom.org
  0.88% |    1 |  1.29% |    16187 | eburger@standardstrack.com
  0.88% |    1 |  1.11% |    13937 | stpeter@stpeter.im
  0.88% |    1 |  1.09% |    13706 | william.polk@nist.gov
  0.88% |    1 |  0.88% |    11040 | lars.eggert@nokia.com
  0.88% |    1 |  0.87% |    10920 | md3135@att.com
  0.88% |    1 |  0.85% |    10686 | msrajesha@gmail.com
  0.88% |    1 |  0.72% |     8963 | richard@shockey.us
  0.88% |    1 |  0.72% |     8958 | mstjohns@comcast.net
  0.88% |    1 |  0.68% |     8528 | krishnabirth@gmail.com
  0.88% |    1 |  0.67% |     8390 | narten@us.ibm.com
  0.88% |    1 |  0.63% |     7850 | tytso@mit.edu
  0.88% |    1 |  0.62% |     7809 | pekkas@netcore.fi
  0.88% |    1 |  0.62% |     7729 | mehmet.ersue@nsn.com
  0.88% |    1 |  0.61% |     7654 | dyork@voxeo.com
  0.88% |    1 |  0.57% |     7151 | framefritti@gmail.com
  0.88% |    1 |  0.54% |     6791 | elwynd@dial.pipex.com
  0.88% |    1 |  0.54% |     6759 | spencer@wonderhamster.org
  0.88% |    1 |  0.53% |     6634 | rja.lists@gmail.com
  0.88% |    1 |  0.52% |     6510 | stig@venaas.com
  0.88% |    1 |  0.47% |     5870 | huitema@microsoft.com
  0.88% |    1 |  0.47% |     5848 | ole@cisco.com
  0.88% |    1 |  0.46% |     5734 | loa@pi.nu
  0.88% |    1 |  0.45% |     5579 | lear@cisco.com
  0.88% |    1 |  0.42% |     5241 | michelle.cotton@icann.org
  0.88% |    1 |  0.41% |     5134 | dworley@avaya.com
  0.88% |    1 |  0.40% |     5044 | bidulock@openss7.org
  0.88% |    1 |  0.39% |     4857 | hannes.tschofenig@nsn.com
  0.88% |    1 |  0.37% |     4667 | erosen@cisco.com
  0.88% |    1 |  0.35% |     4395 | ajs@shinkuro.com
  0.88% |    1 |  0.35% |     4353 | john-lame@jck.com
--------+------+--------+----------+------------------------
100.00% |  113 |100.00% |  1252741 | Total

From doug@ewellic.org  Thu Jan 13 21:53:31 2011
Return-Path: <doug@ewellic.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 592993A690E for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 21:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.409
X-Spam-Level: 
X-Spam-Status: No, score=-1.409 tagged_above=-999 required=5 tests=[AWL=1.189,  BAYES_00=-2.599, STOX_REPLY_TYPE=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 bwXMFNoQlikN for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 21:53:29 -0800 (PST)
Received: from smtpauth21.prod.mesa1.secureserver.net (smtpauth21.prod.mesa1.secureserver.net [64.202.165.38]) by core3.amsl.com (Postfix) with SMTP id A0D723A68E7 for <ietf@ietf.org>; Thu, 13 Jan 2011 21:53:29 -0800 (PST)
Received: (qmail 11211 invoked from network); 14 Jan 2011 05:55:52 -0000
Received: from unknown (24.8.55.39) by smtpauth21.prod.mesa1.secureserver.net (64.202.165.38) with ESMTP; 14 Jan 2011 05:55:52 -0000
Message-ID: <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell>
From: "Doug Ewell" <doug@ewellic.org>
To: "The IETF" <ietf@ietf.org>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com><4D2F3C11.7000904@joelhalpern.com> <4D2F4086.3050601@stpeter.im>
In-Reply-To: <4D2F4086.3050601@stpeter.im>
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Review ofdraft-yevstifeyev-tn3270-uri-12)
Date: Thu, 13 Jan 2011 22:56:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
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, 14 Jan 2011 05:53:31 -0000

Peter Saint-Andre wrote:

> For what it's worth, Section 10 of the informational RFC 2223
> ("Instructions to RFC Authors") states:
>
> Each RFC must have at the very end a section giving the author's
> address, including the name and postal address, the telephone number,
> (optional: a FAX number) and the Internet email address.

The Internet is not the type of chummy small-town environment where we 
can trust just anybody with our home address and phone number, or our 
bank account and credit card numbers, and where we can leave our front 
doors unlocked at night.

I worked on two I-Ds in a WG where participant A once responded to 
participant B's support of an RFC 3683 P-R action against A by 
contacting B's employer, gleaned from his e-mail address, demanding that 
the employer take professional action against B.  In this type of 
hostile environment, I declined to state my employer's name or post to 
the WG list from my work address, much less divulge other personal 
information, and edited both RFC 4645 and 5646 as "Consultant."

The argument that personal information is necessary to distinguish the 
author from other people with the same name probably carries some weight 
for authors named "John Smith" or "Bob Miller."  There are few enough 
people named "Doug Ewell" in the world that the risk of ambiguity of 
authorship seems much more remote than the risk to personal security if 
too much personal information is provided.  I suspect the same is true 
for people named "Mykyta Yevstifeyev."

Having said that, I don't think there is any precedent for I-D authors 
or editors to claim their document was written by "IETF" or "IESG," and 
I doubt this will be permitted.

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­


From doug@ewellic.org  Thu Jan 13 22:12:29 2011
Return-Path: <doug@ewellic.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 C26663A6A82 for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 22:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.608
X-Spam-Level: 
X-Spam-Status: No, score=-1.608 tagged_above=-999 required=5 tests=[AWL=0.991,  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 8W37MDZZwQkU for <ietf@core3.amsl.com>; Thu, 13 Jan 2011 22:12:28 -0800 (PST)
Received: from smtpauth05.prod.mesa1.secureserver.net (smtpauth05.prod.mesa1.secureserver.net [64.202.165.99]) by core3.amsl.com (Postfix) with SMTP id 1C3DB3A68A3 for <ietf@ietf.org>; Thu, 13 Jan 2011 22:12:24 -0800 (PST)
Received: (qmail 24787 invoked from network); 14 Jan 2011 06:14:48 -0000
Received: from unknown (24.8.55.39) by smtpauth05.prod.mesa1.secureserver.net (64.202.165.99) with ESMTP; 14 Jan 2011 06:14:48 -0000
Message-ID: <43F87EDD9E2441F0A469866B48D04D8F@DougEwell>
From: "Doug Ewell" <doug@ewellic.org>
To: "The IETF" <ietf@ietf.org>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com><4D2F3C11.7000904@joelhalpern.com><4D2F4086.3050601@stpeter.im> <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell>
In-Reply-To: <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell>
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
Date: Thu, 13 Jan 2011 23:14:58 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
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, 14 Jan 2011 06:12:29 -0000

I wrote:

> I [...] edited both RFC 4645 and 5646 as "Consultant."

s/5646/5645/

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­


From vesely@tana.it  Fri Jan 14 00:21:04 2011
Return-Path: <vesely@tana.it>
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 12F913A6C4E for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 00:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.179
X-Spam-Level: 
X-Spam-Status: No, score=-5.179 tagged_above=-999 required=5 tests=[AWL=-0.460, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 j1KekknmFQhJ for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 00:21:03 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id A670F3A6C46 for <ietf@ietf.org>; Fri, 14 Jan 2011 00:21:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1294993402; bh=gZuNJfxbRhlV3Wv6wgWFn1bVbCFiAX2t9suuRLF4vVY=; l=598; h=Message-ID:Date:From:MIME-Version:To:CC:References:In-Reply-To: Content-Transfer-Encoding; b=TrSCJycD2Mnsz8SXXIYujw4RgA/6mc1/TaghKjQwJRiVcpBV6qkE1CB7ayCgspPut BLLjY6F7no1ZNo4YlHuLcnpjojZYvfjc29Hnc9Cw4h/jP8rslcLrM1B+4sH5VcXgFV 8tNqa2jJX5wH377SkQpp7TQVRHfoz74Bpundrwk0=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 14 Jan 2011 09:23:22 +0100 id 00000000005DC039.000000004D3007FA.000049F0
Message-ID: <4D3007FB.102@tana.it>
Date: Fri, 14 Jan 2011 09:23:23 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: SDO vs academic conference, was poster sessions
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net><4D2AEC03.8040205@pi.nu>	<094C6685-62A8-435C-8467-A77A34A14963@americafree.tv>	<17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>	<4D2C3DF5.8020204@tana.it>	<DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com>	<14C85D6CCBE92743AF33663BF5D24EBA08D06800@gaalpa1msgusr7e.ugd.att.com>	<006701cbb1be$73207280$6801a8c0@oemcomputer> <8C373906B2FB9C011E59FE7F@PST.JCK.COM>
In-Reply-To: <8C373906B2FB9C011E59FE7F@PST.JCK.COM>
Content-Type: text/plain; charset=us-ascii
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, 14 Jan 2011 08:21:04 -0000

On 11/Jan/11 20:32, John C Klensin wrote:
> --On Tuesday, January 11, 2011 10:35 -0800 Randy Presuhn
> <randy_presuhn@mindspring.com> wrote:
> 
>>> At issue though is that these individuals get paid
>>> (sponsored) by someone, either directly or indirectly by
>>> corporations and/or governments.
>> 
>> Not necessarily.  Some of us have no employer and just do this
>> stuff for the fun of it.
> 
> Indeed.  Although I'm increasingly taking exception to the "fun"
> part.

If you remove fun, what else remains that can be used as a compass to
take a bearing in iffy circumstances?

From lars.eggert@nokia.com  Fri Jan 14 00:24:02 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 D9A073A6ABD for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 00:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.729
X-Spam-Level: 
X-Spam-Status: No, score=-104.729 tagged_above=-999 required=5 tests=[AWL=-1.130, 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 MSgXLlPyWzuA for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 00:24:02 -0800 (PST)
Received: from mgw-da01.nokia.com (mgw-da01.ext.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id EC69B3A6AB9 for <ietf@ietf.org>; Fri, 14 Jan 2011 00:24:01 -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 p0E8NY2I010232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 14 Jan 2011 10:23:36 +0200
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
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-19-1006110016; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <C954A3DF.2B01C%michelle.cotton@icann.org>
Date: Fri, 14 Jan 2011 10:23:26 +0200
Message-Id: <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
References: <C954A3DF.2B01C%michelle.cotton@icann.org>
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Fri, 14 Jan 2011 10:23:31 +0200 (EET)
X-Nokia-AV: Clean
Cc: Julian Reschke <julian.reschke@gmx.de>, "stig@cisco.com" <stig@cisco.com>, Adrian Farrel <adrian.farrel@huawei.com>, '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, 14 Jan 2011 08:24:02 -0000

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

Hi,

On 2011-1-13, at 22:43, Michelle Cotton wrote:
> Many believe it makes it very clear to the users of the registry what =
is
> available for assignment.  Something we will be rolling out soon (for =
those
> registries with a finite space) will be small charts showing how much =
of the
> registry space is unassigned, assigned and reserved (utilizing the
> unassigned entries).

I mentioned in the past that the term "unassigned" to me at least =
doesn't make it sufficiently clear that IANA assignment is often needed =
before codepoints may be taken into use. We have several cases (the many =
different squats on TCP option numbers, for example) were people pick =
unassigned codepoints during development and only later realize that =
they should have registered them.

If you want to explicitly list unassigned codepoints in the registries, =
I'm wondering if we can find a short phrase that makes it more clear =
that an IANA action is normally required - maybe "available for IANA =
assignment"?

Lars=

--Apple-Mail-19-1006110016
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExNDA4MjMyNlowIwYJKoZIhvcNAQkE
MRYEFPE0ZuYpAqSp6g2ia6dpBop/Sp2KMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AE0hGLLPKZWRS+Yz2bGj7rtQbBG1AI2G8HIiATEOXFbcfFXPj6Ikw6VMLA6V3LWSq5VVDW9wRNPb
nHocbQFXQunBosZKzEbLmZdgvQPZ2Xg8FAQU/+aQ8zxJWYBv+JS3GcZ7rXZ9UF/3WvjZDKCHWw3z
jrXmLgR3fYuKuPRNOM+3neaVtxM8tvJ8rrigJNUdXfUrCy16FkWs6iVIpmK6JTY1hRVLevG7bqSV
zscN8eELwtozXERaUrs1M8tRmfSbhPah+PXRy5Hhkv4AYJ27FzsiL7HtAwfQe1NPK6z66r7Ih/Sz
xARnW7rpInpg5NoqFPg3df6uI/935KSTIVasuzEAAAAAAAA=

--Apple-Mail-19-1006110016--

From Chris.Dearlove@baesystems.com  Fri Jan 14 01:56:54 2011
Return-Path: <Chris.Dearlove@baesystems.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 917993A6AC9 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 01:56:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.166
X-Spam-Level: 
X-Spam-Status: No, score=-6.166 tagged_above=-999 required=5 tests=[AWL=0.433,  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 2F3jnWyIX1L9 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 01:56:53 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by core3.amsl.com (Postfix) with ESMTP id 660D63A6A0D for <ietf@ietf.org>; Fri, 14 Jan 2011 01:56:53 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.60,322,1291593600"; d="scan'208";a="109865598"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 14 Jan 2011 09:59:16 +0000
Received: from glkms1103.GREENLNK.NET (glkms1103.greenlnk.net [10.108.36.194]) by baemasodc004.greenlnk.net (Switch-3.4.3/Switch-3.4.3) with ESMTP id p0E9xCt4002049; Fri, 14 Jan 2011 09:59:15 GMT
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1103.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 09:59:14 +0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: Last Call on draft-ietf-pim-registry-03.txt
Date: Fri, 14 Jan 2011 09:59:09 -0000
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D03D0AC20@GLKMS2100.GREENLNK.NET>
In-Reply-To: <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call on draft-ietf-pim-registry-03.txt
Thread-Index: AcuzxMIqW2bzSWLIRVa9l9c6psZvtgAC7TRA
References: <C954A3DF.2B01C%michelle.cotton@icann.org> <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: "Lars Eggert" <lars.eggert@nokia.com>, "Michelle Cotton" <michelle.cotton@icann.org>
X-OriginalArrivalTime: 14 Jan 2011 09:59:14.0594 (UTC) FILETIME=[B32F2820:01CBB3D1]
Cc: Julian Reschke <julian.reschke@gmx.de>, The IETF <ietf@ietf.org>, Adrian Farrel <adrian.farrel@huawei.com>, stig@cisco.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: Fri, 14 Jan 2011 09:56:54 -0000

RFC 5226 (BCP 26) says

   IANA must be given a set of
   guidelines that allow it to make allocation decisions with minimal
   subjectivity and without requiring any technical expertise with
   respect to the protocols that make use of a registry.
 
and goes on to discuss categories of unassigned code points (though
it does also define the unqualified word Unassigned). We were thus
advised, when publishing RFC 5444, to specify this clearly and
so we had tables such as

       +---------+-----------------------+------------------------+
       |   Type  | Description           | Allocation Policy      |
       +---------+-----------------------+------------------------+
       |  0-127  | Unassigned            | Expert Review          |
       | 128-223 | Message-Type-specific | Reserved, see Table 11 |
       | 224-255 | Unassigned            | Experimental Use       |
       +---------+-----------------------+------------------------+

(For the purposes of this discussion I suggest ignoring the 128 to
223 line above.)

This seemed to keep everyone (IESG, IANA, RFC Editor) happy.

-- 
Christopher Dearlove
Technology Leader, Communications Group
Communications and Networks Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194  Fax: +44 1245 242124

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87,
Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Lars Eggert
Sent: 14 January 2011 08:23
To: Michelle Cotton
Cc: Julian Reschke; stig@cisco.com; Adrian Farrel; 'The IETF'
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt

Hi,

On 2011-1-13, at 22:43, Michelle Cotton wrote:
> Many believe it makes it very clear to the users of the registry what
is
> available for assignment.  Something we will be rolling out soon (for
those
> registries with a finite space) will be small charts showing how much
of the
> registry space is unassigned, assigned and reserved (utilizing the
> unassigned entries).

I mentioned in the past that the term "unassigned" to me at least
doesn't make it sufficiently clear that IANA assignment is often needed
before codepoints may be taken into use. We have several cases (the many
different squats on TCP option numbers, for example) were people pick
unassigned codepoints during development and only later realize that
they should have registered them.

If you want to explicitly list unassigned codepoints in the registries,
I'm wondering if we can find a short phrase that makes it more clear
that an IANA action is normally required - maybe "available for IANA
assignment"?

Lars

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From olaf@NLnetLabs.nl  Fri Jan 14 02:10:51 2011
Return-Path: <olaf@NLnetLabs.nl>
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 CB32B3A6ACE for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 02:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbZRYtf659ex for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 02:10:49 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id DF3683A6ACF for <ietf@ietf.org>; Fri, 14 Jan 2011 02:10:48 -0800 (PST)
Received: from dhcp-96.nlnetlabs.nl (dhcp-96.nlnetlabs.nl [213.154.224.96]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p0EADCxB027811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Jan 2011 11:13:12 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
Subject: Re: SDO vs academic conference, was poster sessions
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-25-1012695883; protocol="application/pkcs7-signature"; micalg=sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <4D3007FB.102@tana.it>
Date: Fri, 14 Jan 2011 11:13:11 +0100
Message-Id: <C594029A-75E7-4EC7-9260-5E4484B3A353@NLnetLabs.nl>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com>	<4D2AE8EC.2060202@ripe.net><4D2AEC03.8040205@pi.nu>	<094C6685-62A8-435C-8467-A77A34A14963@americafree.tv>	<17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com>	<4D2C3DF5.8020204@tana.it>	<DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com>	<14C85D6CCBE92743AF33663BF5D24EBA08D06800@gaalpa1msgusr7e.ugd.att.com>	<006701cbb1be$73207280$6801a8c0@oemcomputer> <8C373906B2FB9C011E59FE7F@PST.JCK.COM> <4D3007FB.102@tana.it>
To: Alessandro Vesely <vesely@tana.it>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [213.154.224.1]); Fri, 14 Jan 2011 11:13:12 +0100 (CET)
Cc: John C Klensin <john-ietf@jck.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: Fri, 14 Jan 2011 10:10:52 -0000

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


On Jan 14, 2011, at 9:23 AM, Alessandro Vesely wrote:

> On 11/Jan/11 20:32, John C Klensin wrote:
>> --On Tuesday, January 11, 2011 10:35 -0800 Randy Presuhn
>> <randy_presuhn@mindspring.com> wrote:
>>=20
>>>> At issue though is that these individuals get paid
>>>> (sponsored) by someone, either directly or indirectly by
>>>> corporations and/or governments.
>>>=20
>>> Not necessarily.  Some of us have no employer and just do this
>>> stuff for the fun of it.
>>=20
>> Indeed.  Although I'm increasingly taking exception to the "fun"
>> part.
>=20
> If you remove fun, what else remains that can be used as a compass to
> take a bearing in iffy circumstances?

For some of us: A feeling of responsibility in shaping the future of the =
Internet that is beyond direct corporate interest and next year's line =
items.


--Olaf



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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFMTCCBS0w
ggMVoAMCAQICAwbqdTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wOTA1MjUwODQ4MTJaFw0x
MTA1MjUwODQ4MTJaMDkxFTATBgNVBAMTDE9sYWYgS29sa21hbjEgMB4GCSqGSIb3DQEJARYRb2xh
ZkBubG5ldGxhYnMubmwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxtZNngmuLgcf
rto+Uax1WhonECqb5W8US2Z+ZPw/ASKsjKEF8Wa3Nnispys6Gj9Sl7C1X0/2pH//qauLpBqA+lHW
L9mgdGW1T9KU1Fb8Odqw0PBnIIhbLNQzecZL+BchEetcrubplQWzDOpROCJ00IwXksusBiKqhew4
u7X2QoraW+z32Knj5ogajIhdkAeBHUy1pwXsk/mDnV8cIEdz1MhaZWDSn7kJUQtRMVCpFBjVoiXh
ToXMJfiMvn0CKaeFxFm72dcdzvFsw906Ndafd2MOfdP7QSsTVP6sG9am790AOgkzxT5CM77IDPbD
zxZlQ8jTdhcp/WtUrFWIU4QBAgMBAAGjgf0wgfowDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0E
SRZHVG8gZ2V0IHlvdXIgb3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRw
Oi8vd3d3LkNBY2VydC5vcmcwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3
CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZo
dHRwOi8vb2NzcC5jYWNlcnQub3JnMBwGA1UdEQQVMBOBEW9sYWZAbmxuZXRsYWJzLm5sMA0GCSqG
SIb3DQEBBQUAA4ICAQCLpawAoUQAxivf6blyMswVokRmDl2JGEbtmEu8j0h1BVOlGh6hlI8WaeWy
3x2jJ9uun3VK6oYnHy45ez+dUDjBLjOZdAgwFg225lm1OPdmisghDDVwCIiEogHPqmJtvKYMFoPF
3iFUambJDoQF8DeVeg8ctDvsxsaVGjA8OrMpo0K4I11vnNbCLv7mWCjnaZWt/6Y6TD8ErHQl5dmI
rpsHmEZx1/nsocdPkZGRA4QVf1omYHUNs79DtxpYdGKHoorpBNzlzIIjpceiqeOeykoDeYLTZX2G
c7Mh4Gdj2MHFqZucxV1cHibb8XKv8ebaGltMV5SrciqRn8yFXmiyTvmId6myNXLiOx+VJiGbLSS3
TltM/kf7UejXeEHulEKufU6Ya6EfH7W2/spTayYCauyLljOjE2Ey5A4oIoJV9eY64OCDuLF2nmGR
jOh3JB9nGkZIPhmTUwGZnMELLhzKz+eOZoulM4tXH6KEubed1shQEq1dkJ+tFtRS3Lm+vLCKWvVo
1iZScqPaQf9riPApAVrL+3Wat0p/jtCk5gLBF02uTiWvT2t4ZfSHMEBXR7CvVm58etRQuyZSMHyz
UQC4wkDvCeVawNRCZjq6wWdvx5hmr2JeDSkkRtSZ/Fa1WXf26b3BZugI75p5JXafbWdOTRpNc8M5
YMk7tx29ZG3u0qODgDGCAzMwggMvAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT
FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0
eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMG6nUwCQYFKw4DAhoFAKCCAYcw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwMTE0MTAxMzEyWjAj
BgkqhkiG9w0BCQQxFgQU7iN+X8LOlobjF7Q4sFg5DppLApQwgZEGCSsGAQQBgjcQBDGBgzCBgDB5
MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNV
BAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2Fj
ZXJ0Lm9yZwIDBup1MIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDBup1MA0GCSqGSIb3
DQEBAQUABIIBAHu5v78BR0sy/tQAa4Od4ge7HbeWBuWVxFGRXQj6hKFvk7LwHaWaLTKhjJ3ynbEr
h9Fi75rnM+kz61wIx0YOUFeUeY3Fa71Pt1cuyQzzThyUEopmyY5sVhYxlZh5k/vZgfOvGUt9g/Q4
8HptuxDw1xK67lVbAZc1VTmzsLMw7uagACUtxiDTDQucgseNcinKVCmwUWSOdH1gvB7/bU1jt5P0
xRvfl+TEPkeYKxpwfXE0T14jCkBSHROYzgtL+SyRkzgbFHoPdNlQRyEAehWzvK5eNvQnIwrh/fYZ
z38+nGBu82IG3+2jlzKZsbsVCQhjstRe8DCN2FPY75lGZ9FBGUIAAAAAAAA=

--Apple-Mail-25-1012695883--

From daedulus@btconnect.com  Fri Jan 14 02:12:33 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 A9A2228C0D0; Fri, 14 Jan 2011 02:12:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h8KrDI8KYugy; Fri, 14 Jan 2011 02:12:32 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by core3.amsl.com (Postfix) with ESMTP id 3F41728B56A; Fri, 14 Jan 2011 02:12:31 -0800 (PST)
Received: from host86-134-205-117.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.117]) by c2beaomr10.btconnect.com with SMTP id BHW74787; Fri, 14 Jan 2011 10:14:52 +0000 (GMT)
Message-ID: <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Doug Ewell" <doug@ewellic.org>, "The IETF" <ietf@ietf.org>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com><4D2F3C11.7000904@joelhalpern.com><4D2F4086.3050601@stpeter.im> <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell>
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
Date: Fri, 14 Jan 2011 10:11:24 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A0B0302.4D30221B.018A, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4D30221D.019B,ss=1,pt=DBB_66871,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>
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, 14 Jan 2011 10:12:33 -0000

----- Original Message -----
From: "Doug Ewell" <doug@ewellic.org>
To: "The IETF" <ietf@ietf.org>
Sent: Friday, January 14, 2011 6:56 AM
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR
Reviewofdraft-yevstifeyev-tn3270-uri-12)


> Peter Saint-Andre wrote:
>
> > For what it's worth, Section 10 of the informational RFC 2223
> > ("Instructions to RFC Authors") states:
> >
> > Each RFC must have at the very end a section giving the author's
> > address, including the name and postal address, the telephone number,
> > (optional: a FAX number) and the Internet email address.
>
> The Internet is not the type of chummy small-town environment where we
> can trust just anybody with our home address and phone number, or our
> bank account and credit card numbers, and where we can leave our front
> doors unlocked at night.

As Joel pointed out, the Last Call issue is the contact details for change
control
in the registration of a widely used URI with IANA, details which consist
solely of a gmail address.  Is that enough to grant change control of this
URI (in which a number of people from a number of organisations have
expressed an ongoing interest)?

RFC4395 appears to be silent.

Tom Petch

> I worked on two I-Ds in a WG where participant A once responded to
> participant B's support of an RFC 3683 P-R action against A by
> contacting B's employer, gleaned from his e-mail address, demanding that
> the employer take professional action against B.  In this type of
> hostile environment, I declined to state my employer's name or post to
> the WG list from my work address, much less divulge other personal
> information, and edited both RFC 4645 and 5646 as "Consultant."
>
> The argument that personal information is necessary to distinguish the
> author from other people with the same name probably carries some weight
> for authors named "John Smith" or "Bob Miller."  There are few enough
> people named "Doug Ewell" in the world that the risk of ambiguity of
> authorship seems much more remote than the risk to personal security if
> too much personal information is provided.  I suspect the same is true
> for people named "Mykyta Yevstifeyev."
>
> Having said that, I don't think there is any precedent for I-D authors
> or editors to claim their document was written by "IETF" or "IESG," and
> I doubt this will be permitted.
>
> --
> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From olaf@NLnetLabs.nl  Fri Jan 14 02:51:49 2011
Return-Path: <olaf@NLnetLabs.nl>
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 1B49E3A6B66 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 02:51:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.607
X-Spam-Level: 
X-Spam-Status: No, score=-102.607 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 Kho3lTeJ1HBF for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 02:51:48 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id 577D93A6AA1 for <ietf@ietf.org>; Fri, 14 Jan 2011 02:51:47 -0800 (PST)
Received: from dhcp-96.nlnetlabs.nl (dhcp-96.nlnetlabs.nl [213.154.224.96]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p0EAsBJb040989 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 14 Jan 2011 11:54:11 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-27-1015154577; protocol="application/pkcs7-signature"; micalg=sha1
Subject: Re: Poster sessions
Date: Fri, 14 Jan 2011 11:54:10 +0100
In-Reply-To: <14CB397B-5B77-44F2-BC89-D46654D2E9AD@cybernothing.org>
To: IETF list <ietf@ietf.org>
References: <4D258AB3.9010903@tana.it>	<CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com>	<tslipy2ndm6.fsf@mit.edu>	<CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com>	<4D26940F.3020404@gmail.com>	<AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com>	<ED6A886C-2FBC-4312-9066-18108363249C@nokia.com>	<E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <14CB397B-5B77-44F2-BC89-D46654D2E9AD@cybernothing.org>
Message-Id: <31EE0BCD-21DF-4D43-82CD-7DCD763902B2@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [213.154.224.1]); Fri, 14 Jan 2011 11:54:11 +0100 (CET)
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, 14 Jan 2011 10:51:49 -0000

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


I see an opportunity for the IETF Store[*]

A T-shirt with a blank space in which you can write your draft name... =
See http://www.secret-wg.org/Poster-Session.png for the artist =
impression of the random IETF participant wearing such shirt.

--Olaf


[*] http://www.cafepress.co.uk/ietf=

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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFMTCCBS0w
ggMVoAMCAQICAwbqdTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wOTA1MjUwODQ4MTJaFw0x
MTA1MjUwODQ4MTJaMDkxFTATBgNVBAMTDE9sYWYgS29sa21hbjEgMB4GCSqGSIb3DQEJARYRb2xh
ZkBubG5ldGxhYnMubmwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxtZNngmuLgcf
rto+Uax1WhonECqb5W8US2Z+ZPw/ASKsjKEF8Wa3Nnispys6Gj9Sl7C1X0/2pH//qauLpBqA+lHW
L9mgdGW1T9KU1Fb8Odqw0PBnIIhbLNQzecZL+BchEetcrubplQWzDOpROCJ00IwXksusBiKqhew4
u7X2QoraW+z32Knj5ogajIhdkAeBHUy1pwXsk/mDnV8cIEdz1MhaZWDSn7kJUQtRMVCpFBjVoiXh
ToXMJfiMvn0CKaeFxFm72dcdzvFsw906Ndafd2MOfdP7QSsTVP6sG9am790AOgkzxT5CM77IDPbD
zxZlQ8jTdhcp/WtUrFWIU4QBAgMBAAGjgf0wgfowDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0E
SRZHVG8gZ2V0IHlvdXIgb3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRw
Oi8vd3d3LkNBY2VydC5vcmcwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3
CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZo
dHRwOi8vb2NzcC5jYWNlcnQub3JnMBwGA1UdEQQVMBOBEW9sYWZAbmxuZXRsYWJzLm5sMA0GCSqG
SIb3DQEBBQUAA4ICAQCLpawAoUQAxivf6blyMswVokRmDl2JGEbtmEu8j0h1BVOlGh6hlI8WaeWy
3x2jJ9uun3VK6oYnHy45ez+dUDjBLjOZdAgwFg225lm1OPdmisghDDVwCIiEogHPqmJtvKYMFoPF
3iFUambJDoQF8DeVeg8ctDvsxsaVGjA8OrMpo0K4I11vnNbCLv7mWCjnaZWt/6Y6TD8ErHQl5dmI
rpsHmEZx1/nsocdPkZGRA4QVf1omYHUNs79DtxpYdGKHoorpBNzlzIIjpceiqeOeykoDeYLTZX2G
c7Mh4Gdj2MHFqZucxV1cHibb8XKv8ebaGltMV5SrciqRn8yFXmiyTvmId6myNXLiOx+VJiGbLSS3
TltM/kf7UejXeEHulEKufU6Ya6EfH7W2/spTayYCauyLljOjE2Ey5A4oIoJV9eY64OCDuLF2nmGR
jOh3JB9nGkZIPhmTUwGZnMELLhzKz+eOZoulM4tXH6KEubed1shQEq1dkJ+tFtRS3Lm+vLCKWvVo
1iZScqPaQf9riPApAVrL+3Wat0p/jtCk5gLBF02uTiWvT2t4ZfSHMEBXR7CvVm58etRQuyZSMHyz
UQC4wkDvCeVawNRCZjq6wWdvx5hmr2JeDSkkRtSZ/Fa1WXf26b3BZugI75p5JXafbWdOTRpNc8M5
YMk7tx29ZG3u0qODgDGCAzMwggMvAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT
FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0
eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMG6nUwCQYFKw4DAhoFAKCCAYcw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwMTE0MTA1NDExWjAj
BgkqhkiG9w0BCQQxFgQUbY2KZiJWjWfyJgUt2RsJMnahh74wgZEGCSsGAQQBgjcQBDGBgzCBgDB5
MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNV
BAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2Fj
ZXJ0Lm9yZwIDBup1MIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDBup1MA0GCSqGSIb3
DQEBAQUABIIBAJYA3PEDecVtoX2+yEYHjVQYOHXA3szKWU8wqr7YzMTmUDQhwO5+zhRJ2t5Jl6GP
/ZTD+gJOBYKOa/uxOdUJdL6NUKVmfWOUoM2f50seFr/PrcW3Me5p/ZgNMPbGWaPkRmuxztFxFvil
KY7BkrDfhnY7upIwYiUuWfPQlEAdtWbN7eQ+AUHgtffvek8JttusHC/a5LXZMVhSSYtpxR+k6eR9
LUr+0lg7zpfQad0pYPok+ucorMTP5Zp0abVCxTTDXrH+EaTz17/V6DmVwihCJpqE8HqLqOPVzvh/
5iM+ypuqNQ8ZULECSq0J4XhBaocJ1epbHW/GO3BOJ8U7xL9XB2wAAAAAAAA=

--Apple-Mail-27-1015154577--

From hallam@gmail.com  Fri Jan 14 04:42:49 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 675FD3A6B74; Fri, 14 Jan 2011 04:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.17
X-Spam-Level: 
X-Spam-Status: No, score=-3.17 tagged_above=-999 required=5 tests=[AWL=-0.172,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=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 Dpr0FmJ2noyN; Fri, 14 Jan 2011 04:42:48 -0800 (PST)
Received: from mail-yi0-f42.google.com (mail-yi0-f42.google.com [209.85.218.42]) by core3.amsl.com (Postfix) with ESMTP id BA3F13A6ABC; Fri, 14 Jan 2011 04:42:47 -0800 (PST)
Received: by yia28 with SMTP id 28so1554420yia.15 for <multiple recipients>; Fri, 14 Jan 2011 04:45:12 -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=4x9PYxbAyXWPf+tJy84ozA+V6VnGQAmjU37Vseh0iPA=; b=MIXFJkHuHCyHDMbrjw5lLN+XUn1oedAJ4wEJCZJYmkq7T1/654SEkA0DEqIG93fK8G Vp+BrLqzRPvx0+AWLJkewTSZGztyE4RZqlIwy+/EwjNcL6BiEHLr7HwzE0BUln/UsT+3 QxXvcjxkMGidzAY9aJ7tAezG09oHKsG2YJghY=
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=YUISnXHH+JjECTpYmSz7Kkfjg+MqdudFjqMJpXaPnPRtflbb0lgJMvRG9BDnRvGGYS 2cY3EeKboNa6zzpoO0NiWWY6uw7HfSR9nweofQISWOopU58L/fU8ZcF0vWR+UdMOKq9j 3AXbImHNCMKvTwrbvFOGB4wUbCj8lX/MaUv7c=
MIME-Version: 1.0
Received: by 10.101.67.16 with SMTP id u16mr542262ank.1.1295009111925; Fri, 14 Jan 2011 04:45:11 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Fri, 14 Jan 2011 04:45:11 -0800 (PST)
In-Reply-To: <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net> <4D2F2089.2000306@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com> <4D2F3C11.7000904@joelhalpern.com> <4D2F4086.3050601@stpeter.im> <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell> <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>
Date: Fri, 14 Jan 2011 07:45:11 -0500
Message-ID: <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com>
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=00163662e65b18e4aa0499cdceae
Cc: The 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: Fri, 14 Jan 2011 12:42:49 -0000

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

I believe that my personal security trumps any and all considerations that
might be raised here.

I do not give my home address out and do not intend to change. If the RFC
editor were to insist that the fields are filled they are going to get a
fake address.


Corporate addresses are even less useful. Very few people in the IETF have
the same employer for more than five years. And even those who have the sam=
e
employer are unlikely to have the same office building very long.


On Fri, Jan 14, 2011 at 4:11 AM, t.petch <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: "Doug Ewell" <doug@ewellic.org>
> To: "The IETF" <ietf@ietf.org>
> Sent: Friday, January 14, 2011 6:56 AM
> Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR
> Reviewofdraft-yevstifeyev-tn3270-uri-12)
>
>
> > Peter Saint-Andre wrote:
> >
> > > For what it's worth, Section 10 of the informational RFC 2223
> > > ("Instructions to RFC Authors") states:
> > >
> > > Each RFC must have at the very end a section giving the author's
> > > address, including the name and postal address, the telephone number,
> > > (optional: a FAX number) and the Internet email address.
> >
> > The Internet is not the type of chummy small-town environment where we
> > can trust just anybody with our home address and phone number, or our
> > bank account and credit card numbers, and where we can leave our front
> > doors unlocked at night.
>
> As Joel pointed out, the Last Call issue is the contact details for chang=
e
> control
> in the registration of a widely used URI with IANA, details which consist
> solely of a gmail address.  Is that enough to grant change control of thi=
s
> URI (in which a number of people from a number of organisations have
> expressed an ongoing interest)?
>
> RFC4395 appears to be silent.
>
> Tom Petch
>
> > I worked on two I-Ds in a WG where participant A once responded to
> > participant B's support of an RFC 3683 P-R action against A by
> > contacting B's employer, gleaned from his e-mail address, demanding tha=
t
> > the employer take professional action against B.  In this type of
> > hostile environment, I declined to state my employer's name or post to
> > the WG list from my work address, much less divulge other personal
> > information, and edited both RFC 4645 and 5646 as "Consultant."
> >
> > The argument that personal information is necessary to distinguish the
> > author from other people with the same name probably carries some weigh=
t
> > for authors named "John Smith" or "Bob Miller."  There are few enough
> > people named "Doug Ewell" in the world that the risk of ambiguity of
> > authorship seems much more remote than the risk to personal security if
> > too much personal information is provided.  I suspect the same is true
> > for people named "Mykyta Yevstifeyev."
> >
> > Having said that, I don't think there is any precedent for I-D authors
> > or editors to claim their document was written by "IETF" or "IESG," and
> > I doubt this will be permitted.
> >
> > --
> > Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> > RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

I believe that my personal security trumps any and all considerations that =
might be raised here.<div><br></div><div>I do not give my home address out =
and do not intend to change.=A0If the RFC editor were to insist that the fi=
elds are filled they are going to get a fake address.</div>
<div><br></div><div><br></div><div>Corporate addresses are even less useful=
. Very few people in the IETF have the same employer for more than five yea=
rs. And even those who have the same employer are unlikely to have the same=
 office building very long.</div>
<div><br></div><div><br></div><div><div class=3D"gmail_quote">On Fri, Jan 1=
4, 2011 at 4:11 AM, t.petch <span dir=3D"ltr">&lt;<a href=3D"mailto:daedulu=
s@btconnect.com">daedulus@btconnect.com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex;">
<div class=3D"im">----- Original Message -----<br>
From: &quot;Doug Ewell&quot; &lt;<a href=3D"mailto:doug@ewellic.org">doug@e=
wellic.org</a>&gt;<br>
To: &quot;The IETF&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org=
</a>&gt;<br>
Sent: Friday, January 14, 2011 6:56 AM<br>
Subject: Re: author&#39;s address (was: Re: Fwd: [OPS-DIR] OPS-DIR<br>
Reviewofdraft-yevstifeyev-tn3270-uri-12)<br>
<br>
<br>
&gt; Peter Saint-Andre wrote:<br>
&gt;<br>
&gt; &gt; For what it&#39;s worth, Section 10 of the informational RFC 2223=
<br>
&gt; &gt; (&quot;Instructions to RFC Authors&quot;) states:<br>
&gt; &gt;<br>
&gt; &gt; Each RFC must have at the very end a section giving the author&#3=
9;s<br>
&gt; &gt; address, including the name and postal address, the telephone num=
ber,<br>
&gt; &gt; (optional: a FAX number) and the Internet email address.<br>
&gt;<br>
&gt; The Internet is not the type of chummy small-town environment where we=
<br>
&gt; can trust just anybody with our home address and phone number, or our<=
br>
&gt; bank account and credit card numbers, and where we can leave our front=
<br>
&gt; doors unlocked at night.<br>
<br>
</div>As Joel pointed out, the Last Call issue is the contact details for c=
hange<br>
control<br>
in the registration of a widely used URI with IANA, details which consist<b=
r>
solely of a gmail address. =A0Is that enough to grant change control of thi=
s<br>
URI (in which a number of people from a number of organisations have<br>
expressed an ongoing interest)?<br>
<br>
RFC4395 appears to be silent.<br>
<br>
Tom Petch<br>
<div><div></div><div class=3D"h5"><br>
&gt; I worked on two I-Ds in a WG where participant A once responded to<br>
&gt; participant B&#39;s support of an RFC 3683 P-R action against A by<br>
&gt; contacting B&#39;s employer, gleaned from his e-mail address, demandin=
g that<br>
&gt; the employer take professional action against B. =A0In this type of<br=
>
&gt; hostile environment, I declined to state my employer&#39;s name or pos=
t to<br>
&gt; the WG list from my work address, much less divulge other personal<br>
&gt; information, and edited both RFC 4645 and 5646 as &quot;Consultant.&qu=
ot;<br>
&gt;<br>
&gt; The argument that personal information is necessary to distinguish the=
<br>
&gt; author from other people with the same name probably carries some weig=
ht<br>
&gt; for authors named &quot;John Smith&quot; or &quot;Bob Miller.&quot; =
=A0There are few enough<br>
&gt; people named &quot;Doug Ewell&quot; in the world that the risk of ambi=
guity of<br>
&gt; authorship seems much more remote than the risk to personal security i=
f<br>
&gt; too much personal information is provided. =A0I suspect the same is tr=
ue<br>
&gt; for people named &quot;Mykyta Yevstifeyev.&quot;<br>
&gt;<br>
&gt; Having said that, I don&#39;t think there is any precedent for I-D aut=
hors<br>
&gt; or editors to claim their document was written by &quot;IETF&quot; or =
&quot;IESG,&quot; and<br>
&gt; I doubt this will be permitted.<br>
&gt;<br>
&gt; --<br>
&gt; Doug Ewell | Thornton, Colorado, USA | <a href=3D"http://www.ewellic.o=
rg" target=3D"_blank">http://www.ewellic.org</a><br>
&gt; RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD<b=
r>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ietf</a><br>
&gt;<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>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--00163662e65b18e4aa0499cdceae--

From hallam@gmail.com  Fri Jan 14 04:45:09 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 B99303A6B74 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 04:45:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.469
X-Spam-Level: 
X-Spam-Status: No, score=-3.469 tagged_above=-999 required=5 tests=[AWL=0.129,  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 1o7byYffGcIA for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 04:45:08 -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 6B4063A6ABC for <ietf@ietf.org>; Fri, 14 Jan 2011 04:45:08 -0800 (PST)
Received: by gyd12 with SMTP id 12so1226472gyd.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 04:47:33 -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=8dI+GHSJm5HBPwzbNozEFLnfpBkIQ6n8ycu5JvRq3Vo=; b=IoUsLsxNF59xIxnEjlolDHG/YYxjB1K+p6XZYbllOhHTvzgXG7y8VaRrdxWpacR5gp YZNQ/sXZiXZ37C7DJozON4PnK7bVQ8z8nkhBaUy4Vcvpldx15OFnF2mdQ9ZB8yyZVTBu jYJ+fFh/YxwuzQvucW8DZqI3Bnk0BYwmtmD3M=
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=wLEJaAZIYxzG+V/LGrZmhrua21jyNSQt8nRz6xA+LjRb0QqYMnMBeBsMtm6gIaOlHy 9zFP0tWbJKISp1l7Wfq5ZdZm66Hivztx//JPbcsnQZJ7QBTiZKR39skjCk2o1cicyiZ3 0g3TUOox9jPXjJbilV9L04nf9qdWNQVldCOwE=
MIME-Version: 1.0
Received: by 10.100.5.15 with SMTP id 15mr537766ane.35.1295009253336; Fri, 14 Jan 2011 04:47:33 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Fri, 14 Jan 2011 04:47:33 -0800 (PST)
In-Reply-To: <31EE0BCD-21DF-4D43-82CD-7DCD763902B2@NLnetLabs.nl>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <14CB397B-5B77-44F2-BC89-D46654D2E9AD@cybernothing.org> <31EE0BCD-21DF-4D43-82CD-7DCD763902B2@NLnetLabs.nl>
Date: Fri, 14 Jan 2011 07:47:33 -0500
Message-ID: <AANLkTinBetRE3m2+uEyt8zFVS1pS=X9nRxc1iVfi=s7O@mail.gmail.com>
Subject: Re: Poster sessions
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary=0016e645aacc86a84a0499cdd687
Cc: IETF 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, 14 Jan 2011 12:45:09 -0000

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

That would be highly unfair and discriminatory.

Some people would have more advertising space than others.


I suggest putting the information on a standard sized helium balloon that
would float above the wearer.


On Fri, Jan 14, 2011 at 5:54 AM, Olaf Kolkman <olaf@nlnetlabs.nl> wrote:

>
> I see an opportunity for the IETF Store[*]
>
> A T-shirt with a blank space in which you can write your draft name... See
> http://www.secret-wg.org/Poster-Session.png for the artist impression of
> the random IETF participant wearing such shirt.
>
> --Olaf
>
>
> [*] http://www.cafepress.co.uk/ietf
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>


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

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

That would be highly unfair and discriminatory.<div><br></div><div>Some peo=
ple would have more advertising space than others.<br><br></div><div><br></=
div><div>I suggest putting the information on a standard sized helium ballo=
on that would float above the wearer.</div>
<div><br></div><div><br><div class=3D"gmail_quote">On Fri, Jan 14, 2011 at =
5:54 AM, Olaf Kolkman <span dir=3D"ltr">&lt;<a href=3D"mailto:olaf@nlnetlab=
s.nl">olaf@nlnetlabs.nl</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex;">
<br>
I see an opportunity for the IETF Store[*]<br>
<br>
A T-shirt with a blank space in which you can write your draft name... See =
<a href=3D"http://www.secret-wg.org/Poster-Session.png" target=3D"_blank">h=
ttp://www.secret-wg.org/Poster-Session.png</a> for the artist impression of=
 the random IETF participant wearing such shirt.<br>

<br>
--Olaf<br>
<br>
<br>
[*] <a href=3D"http://www.cafepress.co.uk/ietf" target=3D"_blank">http://ww=
w.cafepress.co.uk/ietf</a><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>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a href=3D=
"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e645aacc86a84a0499cdd687--

From alexey.melnikov@isode.com  Fri Jan 14 05:29:57 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 684E03A6B83 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 05:29:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 pdtLnF6J+mWw for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 05:29:56 -0800 (PST)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id DC4213A6B7F for <ietf@ietf.org>; Fri, 14 Jan 2011 05:29:55 -0800 (PST)
Received: from [192.168.1.124] ((unknown) [62.3.217.253])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <TTBQZAAJUHZr@rufus.isode.com>; Fri, 14 Jan 2011 13:32:20 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D30504C.2060300@isode.com>
Date: Fri, 14 Jan 2011 13:31:56 +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: ietf@ietf.org
Subject: Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt>  ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC
References: <20101213132808.2379.30041.idtracker@localhost>
In-Reply-To: <20101213132808.2379.30041.idtracker@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; 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: Fri, 14 Jan 2011 13:29:57 -0000

The IESG wrote:

>The IESG has received a request from an individual submitter to consider
>the following document:
>- ''Headers-Not-Recognized' HTTP Header Field'
>  <draft-yevstifeyev-http-headers-not-recognized-08.txt> as an
>Experimental RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2011-01-14. Exceptionally, comments may be
>sent to iesg@ietf.org instead. In either case, please retain the
>beginning of the Subject line to allow automated sorting.
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-yevstifeyev-http-headers-not-recognized/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-yevstifeyev-http-headers-not-recognized/
>
>
>No IPR declarations have been submitted directly on this I-D.
>  
>
Based on the feedback received during the IETF LC the author decided to 
withdraw this document. So I will be moving it to the Dead state in the 
datatracker.

Thank you to all people who commented.

Alexey,
As the shepherding AD

-- 
IETF Application Area Director, <http://www.ietf.org/iesg/members.html>
Internet Messaging Team Lead, <http://www.isode.com>
JID: same as my email address



From jmabdp@gmail.com  Fri Jan 14 05:36:53 2011
Return-Path: <jmabdp@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 557B83A6B7F; Fri, 14 Jan 2011 05:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.675
X-Spam-Level: 
X-Spam-Status: No, score=-1.675 tagged_above=-999 required=5 tests=[AWL=-0.917, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_63=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_LWSHORTT=1.24, SARE_OBFUMONEY2=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 tu9W8gmj24QK; Fri, 14 Jan 2011 05:36:51 -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 6D19A3A6B26; Fri, 14 Jan 2011 05:36:51 -0800 (PST)
Received: by iwn40 with SMTP id 40so2702352iwn.31 for <multiple recipients>; Fri, 14 Jan 2011 05:39:16 -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=qJSpY5sEiUZ6X5oI0hjhkHiZGXKjXghfCoGLdzJF85k=; b=XWf5OiSceGy0ME8mCDG8vMvkmgI6fTST9oTysFL6EUwA/c1mA55Y9GD6bDQ5pmAIOr VfiGAYmDV0InajE5ZqAwTgKzZ6x3ZWCTS0PQ4GAIKXsq85OoDM4hXKyaVckGIfE2cJD8 2e2w8fk2blPqB1s3z4AbVbcKHYvL4Nu29//b8=
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=f+SCl6HHAMH5Jd/2Sno5pztvnRu9JkZStVIxIGGQCDiZbc/EgDhrwDRo6MSKTrNky5 G9MyTBcnHqsBgxaiYDub+1Elk+vIm0RqJUVASlEW/7LCVTRtn9jAeEz4gS0XKrSVqfxH hGTnWcY9gDrnRzidWCibzUgV0eZclP2BYc6GA=
MIME-Version: 1.0
Received: by 10.231.37.12 with SMTP id v12mr690162ibd.83.1295012356674; Fri, 14 Jan 2011 05:39:16 -0800 (PST)
Received: by 10.231.129.2 with HTTP; Fri, 14 Jan 2011 05:39:16 -0800 (PST)
In-Reply-To: <C594029A-75E7-4EC7-9260-5E4484B3A353@NLnetLabs.nl>
References: <4D258AB3.9010903@tana.it> <CD5674C3CD99574EBA7432465FC13C1B2202288B51@DC-US1MBEX4.global.avaya.com> <tslipy2ndm6.fsf@mit.edu> <CD5674C3CD99574EBA7432465FC13C1B2202288B59@DC-US1MBEX4.global.avaya.com> <4D26940F.3020404@gmail.com> <AANLkTi=5X=L5C1NJPBRPcwsvWBDfsUA=jhqVTf2RuTr6@mail.gmail.com> <ED6A886C-2FBC-4312-9066-18108363249C@nokia.com> <E0444BE9-83B6-42F9-8B6B-D514F7C1A28D@checkpoint.com> <4D2AE8EC.2060202@ripe.net> <4D2AEC03.8040205@pi.nu> <094C6685-62A8-435C-8467-A77A34A14963@americafree.tv> <17D4AE0F-AB65-4F28-8F99-4105959386CD@cisco.com> <4D2C3DF5.8020204@tana.it> <DBDB1DDE-3512-4B35-81C2-70B877D17F9D@standardstrack.com> <14C85D6CCBE92743AF33663BF5D24EBA08D06800@gaalpa1msgusr7e.ugd.att.com> <006701cbb1be$73207280$6801a8c0@oemcomputer> <8C373906B2FB9C011E59FE7F@PST.JCK.COM> <4D3007FB.102@tana.it> <C594029A-75E7-4EC7-9260-5E4484B3A353@NLnetLabs.nl>
Date: Fri, 14 Jan 2011 14:39:16 +0100
Message-ID: <AANLkTinrH0kaDxS8_JLvNxMSexZaOP1B83HbEb5ViPH1@mail.gmail.com>
Subject: Re: SDO vs academic conference, was poster sessions
From: jean-michel bernier de portzamparc <jmabdp@gmail.com>
To: Olaf Kolkman <olaf@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary=0022152d60257fd4160499ce8f7a
Cc: John C Klensin <john-ietf@jck.com>, iucg@ietf.org, ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
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, 14 Jan 2011 13:36:53 -0000

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

2011/1/14 Olaf Kolkman <olaf@nlnetlabs.nl>

>
> On Jan 14, 2011, at 9:23 AM, Alessandro Vesely wrote:
>
> > On 11/Jan/11 20:32, John C Klensin wrote:
> >> --On Tuesday, January 11, 2011 10:35 -0800 Randy Presuhn
> >> <randy_presuhn@mindspring.com> wrote:
> >>
> >>>> At issue though is that these individuals get paid
> >>>> (sponsored) by someone, either directly or indirectly by
> >>>> corporations and/or governments.
> >>>
> >>> Not necessarily.  Some of us have no employer and just do this
> >>> stuff for the fun of it.
> >>
> >> Indeed.  Although I'm increasingly taking exception to the "fun"
> >> part.
> >
> > If you remove fun, what else remains that can be used as a compass to
> > take a bearing in iffy circumstances?
>
> For some of us: A feeling of responsibility in shaping the future of the
> Internet that is beyond direct corporate interest and next year's line
> items.
>

+1
Portzamparc


Jean-Michel,

This what lead us to identify three areas of not yet cloned people's
responsibility:

- the operance for the short term operational issues that are mostly
addressed by agreements and contracts and are related to machines.
- the governance for mid-term relational issues that are mostly addressed by
international rules and national laws and are related to people.
- the adminance for the long-term architectural orientations that operance
and governance may trust, that make the Internet (hence in part the world)
constitution (as per L. Lessig) and that are related to humanity.

We feel that up to now operance managers/corporates and governance
politicians/governments have left the adminance to IAB and IRTF, applied by
the IETF, forgetting that they shape the possible futures of people,and
leaving an under influence "market" to "decide". The claim of the young
emerging IUse (Intelligent Internet and IETF Users) community is to be an
active part of the Internet adminance. Moreover this is an urgent issue as
the technology (cf. the IDNA2008 example) has reached the fringes of
possible semantic facilitation services, i.e. the possibility of social
meaning engineering.

If "fun" and "monney" are the only IETF motivations, there is some urgency
to work on new meanings production. The IUse value added meaning is to
permit everyone to technically empower him/herself, to do what he/she likes
in life better, for the good of networked others. Because we beleive that
such a distributed and intricated network of diverse meaning and purpose in
life is the only solution we (the people) will be left with "the day after
the google-stream stops".

Also, I fear this very interesting thread forgets two important aspects we
IUsers try to deal with:

- we also are engineers and developers who can engineer and document. But we
are not dedicated to the sole global internet, being first interested in our
internets (possibly through different technologies, and for our own
business). These internets do not have the budget to pay for an IETF time,
we cannot wait for years, and most of all why would this be under ISOC
Copyright? We need many things we can think off to be used elsewhere and
therefore to be public domain.

- in uncoupling the Internet functions from the Internet Use Interface
possibilities, IDNA2008 has open an entire new engineering area, outside/on
top of the IETF scope. We are interested in "fringe to fringe" smart
services (extended services) and to directly support semantic facilitation
you could dub as "brain to brain". For that we need the IETF underlaying
Internet we use to work well, and its engineers to seriously want to
understand what we need and why and to help us with it.

jfc

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

<br><br><div class=3D"gmail_quote">2011/1/14 Olaf Kolkman <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:olaf@nlnetlabs.nl">olaf@nlnetlabs.nl</a>&gt;</span><=
br><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bo=
rder-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class=3D"im"><br>
On Jan 14, 2011, at 9:23 AM, Alessandro Vesely wrote:<br>
<br>
&gt; On 11/Jan/11 20:32, John C Klensin wrote:<br>
&gt;&gt; --On Tuesday, January 11, 2011 10:35 -0800 Randy Presuhn<br>
&gt;&gt; &lt;<a href=3D"mailto:randy_presuhn@mindspring.com">randy_presuhn@=
mindspring.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt;&gt; At issue though is that these individuals get paid<br>
&gt;&gt;&gt;&gt; (sponsored) by someone, either directly or indirectly by<b=
r>
&gt;&gt;&gt;&gt; corporations and/or governments.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Not necessarily. =A0Some of us have no employer and just do th=
is<br>
&gt;&gt;&gt; stuff for the fun of it.<br>
&gt;&gt;<br>
&gt;&gt; Indeed. =A0Although I&#39;m increasingly taking exception to the &=
quot;fun&quot;<br>
&gt;&gt; part.<br>
&gt;<br>
&gt; If you remove fun, what else remains that can be used as a compass to<=
br>
&gt; take a bearing in iffy circumstances?<br>
<br>
</div>For some of us: A feeling of responsibility in shaping the future of =
the Internet that is beyond direct corporate interest and next year&#39;s l=
ine items.<br></blockquote><br>+1 <br>
Portzamparc<br><br><br>Jean-Michel,<br><br>
This what lead us to identify three areas of not yet cloned people&#39;s re=
sponsibility:<br><br>
- the operance for the short term operational issues that are mostly addres=
sed by agreements and contracts and are related to machines.<br>
- the governance for mid-term relational issues that are mostly addressed b=
y international rules and national laws and are related to people.<br>
- the adminance for the long-term architectural orientations that operance =
and governance may trust, that make the Internet (hence in part the world) =
constitution (as per L. Lessig) and that are related to humanity.<br><br>

We feel that up to now operance managers/corporates and governance politici=
ans/governments have left the adminance to IAB and IRTF, applied by the IET=
F, forgetting that they shape the possible futures of people,and=A0 leaving=
 an under influence &quot;market&quot; to &quot;decide&quot;. The claim of =
the young emerging IUse (Intelligent Internet and IETF Users) community is =
to be an active part of the Internet adminance. Moreover this is an urgent =
issue as the technology (cf. the IDNA2008 example) has reached the fringes =
of possible semantic facilitation services, i.e. the possibility of social =
meaning engineering.<br>
<br>
If &quot;fun&quot; and &quot;monney&quot; are the only IETF motivations, th=
ere is some urgency to work on new meanings production. The IUse value adde=
d meaning is to permit everyone to technically empower him/herself, to do w=
hat he/she likes in life better, for the good of networked others. Because =
we beleive that such a distributed and intricated network of diverse meanin=
g and purpose in life is the only solution we (the people) will be left wit=
h &quot;the day after the google-stream stops&quot;. <br>
<br>
Also, I fear this very interesting thread forgets two important aspects we =
IUsers try to deal with:<br><br>
- we also are engineers and developers who can engineer and document. But w=
e are not dedicated to the sole global internet, being first interested in =
our internets (possibly through different technologies, and for our own bus=
iness). These internets do not have the budget to pay for an IETF time, we =
cannot wait for years, and most of all why would this be under ISOC Copyrig=
ht? We need many things we can think off to be used elsewhere and therefore=
 to be public domain.<br>
<br>
- in uncoupling the Internet functions from the Internet Use Interface poss=
ibilities, IDNA2008 has open an entire new engineering area, outside/on top=
 of the IETF scope. We are interested in &quot;fringe to fringe&quot; smart=
 services (extended services) and to directly support semantic facilitation=
 you could dub as &quot;brain to brain&quot;. For that we need the IETF und=
erlaying Internet we use to work well, and its engineers to seriously want =
to understand what we need and why and to help us with it.<br>
<br>
jfc<br></div><br><div style=3D"visibility: hidden; display: inline;" id=3D"=
avg_ls_inline_popup"></div><style type=3D"text/css">#avg_ls_inline_popup { =
 position:absolute;  z-index:9999;  padding: 0px 0px;  margin-left: 0px;  m=
argin-top: 0px;  width: 240px;  overflow: hidden;  word-wrap: break-word;  =
color: black;  font-size: 10px;  text-align: left;  line-height: 13px;}</st=
yle>

--0022152d60257fd4160499ce8f7a--

From evnikita2@gmail.com  Fri Jan 14 06:02:13 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 495CF3A6B87 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 06:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.282
X-Spam-Level: 
X-Spam-Status: No, score=-2.282 tagged_above=-999 required=5 tests=[AWL=-0.643, 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 END86HAX3FdA for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 06:02:12 -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 4BEAF3A6B7A for <ietf@ietf.org>; Fri, 14 Jan 2011 06:02:12 -0800 (PST)
Received: by bwz12 with SMTP id 12so2723854bwz.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 06:04:37 -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=xx29gQzVLZkeQz8MMbC/3rE95Kd2nSqxRWYvH2w3fYQ=; b=vRDHxhqrbnUkHKHe/iH+5AX+2xohs7lZpTxSCL+RPpEdxxzBcpEE5d+puFCtJaAH7/ HeLZFEseS2r/l/vlitJrv+ZiB+sxa2qnNlA+mG1NhXFIE1hfgbL+99p/HYCAYWdDoAtj Su138SZkk5u0QiIFMbQ7s9e/p/x9acP7kS+P4=
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=gD8b+ayPEpxbTq6qG02FlVP/Ca6sgNQe9tjtRSH+h5JXBBoEKA5rEbgB0wbvBL+sFE BwpvBUFde9ufhYtBml49xvyWgRaJIBeGrk0LQzVOvzPtrMbQlgOJLd7DLOULqbmJ1dlc WBO+sHYo0rlLUm1AoeJIRD4Bckkjb5anwLuxU=
Received: by 10.204.126.230 with SMTP id d38mr630458bks.120.1295013876960; Fri, 14 Jan 2011 06:04:36 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id x38sm1318750bkj.13.2011.01.14.06.04.34 (version=SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 06:04:35 -0800 (PST)
Message-ID: <4D305806.6070502@gmail.com>
Date: Fri, 14 Jan 2011 16:04:54 +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: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de> <4D2F2385.6050301@gmail.com> <4D2F2402.401@gmx.de> <4D2F24DC.4070908@gmail.com> <4D2F261A.6040105@gmx.de>
In-Reply-To: <4D2F261A.6040105@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 14 Jan 2011 14:02:13 -0000

13.01.2011 18:19, Julian Reschke wrote:
> On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
>> <...>
>> Documents that create a new namespace (or modify the definition of an
>> existing space) and that expect IANA to play a role in maintaining
>> that space (e.g., serving as a repository for registered values) MUST
>> provide clear instructions on details of the namespace. In
>> particular, instructions *MUST* include:
>> <...>
>> 5) Initial assignments and reservations. Clear instructions should be
>> provided to identify any initial assignments or registrations. In
>> addition, any ranges that are to be reserved for "Private Use",
>> "Reserved", **"Unassigned"**, etc. should be *clearly indicated*.
>> <...>
>
> Yes.
>
> There's still no "MUST" applying to unassigned code points. Note the 
> "In addition" and "should".
There is MUST before the list of the criteria for the documents defining 
the registry.  This MUST applies to everything mentioned in this list.

Mykyta
>
>> ...
>
> Best regards, Julian
>


From julian.reschke@gmx.de  Fri Jan 14 06:04:51 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 63D7E3A6B26 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 06:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.204
X-Spam-Level: 
X-Spam-Status: No, score=-104.204 tagged_above=-999 required=5 tests=[AWL=-1.605, 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 Y5tHhU5palEw for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 06:04:50 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id C3CCD3A6B7F for <ietf@ietf.org>; Fri, 14 Jan 2011 06:04:49 -0800 (PST)
Received: (qmail invoked by alias); 14 Jan 2011 14:07:13 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp066) with SMTP; 14 Jan 2011 15:07:13 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18K5o4bZEIKekhTbT6BbelqoeHucRFWVdpNG8UTbI lavyz2NmQx71bF
Message-ID: <4D305885.9030003@gmx.de>
Date: Fri, 14 Jan 2011 15:07:01 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>	<01bc01cbb25c$41590700$c40b1500$@huawei.com>	<4D2DB36C.7070107@gmx.de>	<01da01cbb264$2f1462d0$8d3d2870$@huawei.com>	<4D2DBC48.2080302@gmx.de>	<AANLkTikTks15pML38XSAuJZY-yRmDXdQBhe12ynWq+Pz@mail.gmail.com>	<0FCCAC8F1FBB48FDA5A5C347233271AA@DougEwell>	<4D2EB195.60604@gmx.de> <AANLkTi=6pMxR56z3safr3gQ0q8Aw8sJ3WAcRfwOuNiUk@mail.gmail.com> <4D2EE2A7.5060805@gmx.de> <4D2F1F8F.5060304@gmail.com> <4D2F211E.4080207@gmx.de> <4D2F2385.6050301@gmail.com> <4D2F2402.401@gmx.de> <4D2F24DC.4070908@gmail.com> <4D2F261A.6040105@gmx.de> <4D305806.6070502@gmail.com>
In-Reply-To: <4D305806.6070502@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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, 14 Jan 2011 14:04:51 -0000

On 14.01.2011 15:04, Mykyta Yevstifeyev wrote:
> 13.01.2011 18:19, Julian Reschke wrote:
>> On 13.01.2011 17:14, Mykyta Yevstifeyev wrote:
>>> <...>
>>> Documents that create a new namespace (or modify the definition of an
>>> existing space) and that expect IANA to play a role in maintaining
>>> that space (e.g., serving as a repository for registered values) MUST
>>> provide clear instructions on details of the namespace. In
>>> particular, instructions *MUST* include:
>>> <...>
>>> 5) Initial assignments and reservations. Clear instructions should be
>>> provided to identify any initial assignments or registrations. In
>>> addition, any ranges that are to be reserved for "Private Use",
>>> "Reserved", **"Unassigned"**, etc. should be *clearly indicated*.
>>> <...>
>>
>> Yes.
>>
>> There's still no "MUST" applying to unassigned code points. Note the
>> "In addition" and "should".
> There is MUST before the list of the criteria for the documents defining
> the registry. This MUST applies to everything mentioned in this list.
> ...

Well, we can go on repeating this exchange over and over, or just stop. 
I'll stop.

Best regards, Julian

From evnikita2@gmail.com  Fri Jan 14 06:47:41 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 88FC63A6B89; Fri, 14 Jan 2011 06:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.938, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 IZEDyzDJ5qZ2; Fri, 14 Jan 2011 06:47:40 -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 DE7343A6B7B; Fri, 14 Jan 2011 06:47:39 -0800 (PST)
Received: by bwz12 with SMTP id 12so2766860bwz.31 for <multiple recipients>; Fri, 14 Jan 2011 06:50:04 -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=3O8Rsy7RgdjSpSmFQ0pKQ6UbXF1ilfyTweqEnLXpQog=; b=NUIN/NUMh6PCAlk8QZDna5dih2FPxDNz2tWPCv7fRhatdNCUEAJ/RTZKyb1gl02S19 1yvC+U/mBYWg+MhvIyigA8521vYvmZXd9f6fKqybGkDTWHSa3rOq/ApKR+CuxZrKa0pI ctUl2yCx+wMlPSlGhlBtxaK/SYUArqx4BYao8=
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=U6n4Zqb9rqUuD39aJUbVMqiKNrN8O/VCGkiz5hI+EHbsJeKN1H+1goKeHGyECIpqfH 6jj4kwlrScdnPTCh33QFFHyKVFIQ5yAJD+Ryg0KsnF5+93NonntZjD7jYPu6UneL8keO aGsCVzu6BRlg33Vtp+oYFyDIOOEOoYutwMKUQ=
Received: by 10.204.66.65 with SMTP id m1mr672200bki.71.1295016604023; Fri, 14 Jan 2011 06:50:04 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id 12sm1343753bki.19.2011.01.14.06.50.02 (version=SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 06:50:03 -0800 (PST)
Message-ID: <4D3062AD.6050804@gmail.com>
Date: Fri, 14 Jan 2011 16:50: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: "t.petch" <daedulus@btconnect.com>
Subject: Re: author's address
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>, <4D2F2089.2000306@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com><4D2F3C11.7000904@joelhalpern.com><4D2F4086.3050601@stpeter.im>	<A618ECBD1CEA466899166BD12E3CB2D9@DougEwell> <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>
In-Reply-To: <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: The 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: Fri, 14 Jan 2011 14:47:41 -0000

14.01.2011 11:11, t.petch wrote:
> ----- Original Message -----
> From: "Doug Ewell"<doug@ewellic.org>
> To: "The IETF"<ietf@ietf.org>
> Sent: Friday, January 14, 2011 6:56 AM
> Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR
> Reviewofdraft-yevstifeyev-tn3270-uri-12)
>
>
>> Peter Saint-Andre wrote:
>>
>>> For what it's worth, Section 10 of the informational RFC 2223
>>> ("Instructions to RFC Authors") states:
>>>
>>> Each RFC must have at the very end a section giving the author's
>>> address, including the name and postal address, the telephone number,
>>> (optional: a FAX number) and the Internet email address.
>> The Internet is not the type of chummy small-town environment where we
>> can trust just anybody with our home address and phone number, or our
>> bank account and credit card numbers, and where we can leave our front
>> doors unlocked at night.
> As Joel pointed out, the Last Call issue is the contact details for change
> control
> in the registration of a widely used URI with IANA, details which consist
> solely of a gmail address.  Is that enough to grant change control of this
> URI (in which a number of people from a number of organisations have
> expressed an ongoing interest)?
Hello all,

Summarizing all discussions I propose and find appropriate the following:

-----------
<....>
4. IANA Considerations
<.....>
Contact: IESG <iesg@ietf.org>
Author/Change controller: IETF <ietf@ietf.org>
<.....>
Author's Addresses

Mykyta Yevstifeyev
8 Kuzovkov St., flat 25,
Kotovsk, Ukraine

EMail: evnikita2@gmail.com
-----------

All the best,
Mykyta Yevstifeyev
> RFC4395 appears to be silent.
>
> Tom Petch
>
>> I worked on two I-Ds in a WG where participant A once responded to
>> participant B's support of an RFC 3683 P-R action against A by
>> contacting B's employer, gleaned from his e-mail address, demanding that
>> the employer take professional action against B.  In this type of
>> hostile environment, I declined to state my employer's name or post to
>> the WG list from my work address, much less divulge other personal
>> information, and edited both RFC 4645 and 5646 as "Consultant."
>>
>> The argument that personal information is necessary to distinguish the
>> author from other people with the same name probably carries some weight
>> for authors named "John Smith" or "Bob Miller."  There are few enough
>> people named "Doug Ewell" in the world that the risk of ambiguity of
>> authorship seems much more remote than the risk to personal security if
>> too much personal information is provided.  I suspect the same is true
>> for people named "Mykyta Yevstifeyev."
>>
>> Having said that, I don't think there is any precedent for I-D authors
>> or editors to claim their document was written by "IETF" or "IESG," and
>> I doubt this will be permitted.
>>
>> --
>> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
>> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­
>>
>> _______________________________________________
>> 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 tme@americafree.tv  Fri Jan 14 07:04:09 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 1A7863A6B91; Fri, 14 Jan 2011 07:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, J_CHICKENPOX_15=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 B+z7BxVsXkko; Fri, 14 Jan 2011 07:04:07 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id AC5F13A6B27; Fri, 14 Jan 2011 07:04:07 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 1D5809A710A0; Fri, 14 Jan 2011 10:06:31 -0500 (EST)
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com>
Date: Fri, 14 Jan 2011 10:06:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <69147F44-0025-47D6-8CAC-B47BC3A9CF89@americafree.tv>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net> <4D2F2089.2000306@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com> <4D2F3C11.7000904@joelhalpern.com> <4D2F4086.3050601@stpeter.im> <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell> <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net> <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: The 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: Fri, 14 Jan 2011 15:04:09 -0000

On Jan 14, 2011, at 7:45 AM, Phillip Hallam-Baker wrote:

> I believe that my personal security trumps any and all considerations =
that might be raised here.
>=20
> I do not give my home address out and do not intend to change. If the =
RFC editor were to insist that the fields are filled they are going to =
get a fake address.
>=20
>=20

They should not insist on anything of the sort.=20

> Corporate addresses are even less useful. Very few people in the IETF =
have the same employer for more than five years. And even those who have =
the same employer are unlikely to have the same office building very =
long.
>=20
>=20
> On Fri, Jan 14, 2011 at 4:11 AM, t.petch <daedulus@btconnect.com> =
wrote:
> ----- Original Message -----
> From: "Doug Ewell" <doug@ewellic.org>
> To: "The IETF" <ietf@ietf.org>
> Sent: Friday, January 14, 2011 6:56 AM
> Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR
> Reviewofdraft-yevstifeyev-tn3270-uri-12)
>=20
>=20
> > Peter Saint-Andre wrote:
> >
> > > For what it's worth, Section 10 of the informational RFC 2223
> > > ("Instructions to RFC Authors") states:
> > >
> > > Each RFC must have at the very end a section giving the author's
> > > address, including the name and postal address, the telephone =
number,
> > > (optional: a FAX number) and the Internet email address.
> >
> > The Internet is not the type of chummy small-town environment where =
we
> > can trust just anybody with our home address and phone number, or =
our
> > bank account and credit card numbers, and where we can leave our =
front
> > doors unlocked at night.
>=20
> As Joel pointed out, the Last Call issue is the contact details for =
change
> control
> in the registration of a widely used URI with IANA, details which =
consist
> solely of a gmail address.  Is that enough to grant change control of =
this
> URI (in which a number of people from a number of organisations have
> expressed an ongoing interest)?
>=20

What, exactly, is the issue here ? How IANA authenticates someone with =
change control over some resource ?
That, clearly, is a lot bigger than just this RFC. I would assume (and =
feel sure) that IANA is not just blindly going by
email address, but by their judgement. I am also not sure what having an =
address will do to help with this. I doubt IANA
will be sending inspectors to people's houses asking to see ID.

If there seems to be of particular risk of such attacks for this URI, I =
would suggest adding=20
text in the security section (or the IANA considerations).

If impersonation attacks seem like a real threat in general, then =
someone who feels that way=20
should write a draft specifying how IANA should authenticate people.

Regards
Marshall

> RFC4395 appears to be silent.
>=20
> Tom Petch
>=20
> > I worked on two I-Ds in a WG where participant A once responded to
> > participant B's support of an RFC 3683 P-R action against A by
> > contacting B's employer, gleaned from his e-mail address, demanding =
that
> > the employer take professional action against B.  In this type of
> > hostile environment, I declined to state my employer's name or post =
to
> > the WG list from my work address, much less divulge other personal
> > information, and edited both RFC 4645 and 5646 as "Consultant."
> >
> > The argument that personal information is necessary to distinguish =
the
> > author from other people with the same name probably carries some =
weight
> > for authors named "John Smith" or "Bob Miller."  There are few =
enough
> > people named "Doug Ewell" in the world that the risk of ambiguity of
> > authorship seems much more remote than the risk to personal security =
if
> > too much personal information is provided.  I suspect the same is =
true
> > for people named "Mykyta Yevstifeyev."
> >
> > Having said that, I don't think there is any precedent for I-D =
authors
> > or editors to claim their document was written by "IETF" or "IESG," =
and
> > I doubt this will be permitted.
> >
> > --
> > Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> > RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s=20
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20
>=20
> --=20
> Website: http://hallambaker.com/
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From paul.hoffman@vpnc.org  Fri Jan 14 07:23: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 E392D3A6A61 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 07:23:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.704
X-Spam-Level: 
X-Spam-Status: No, score=-101.704 tagged_above=-999 required=5 tests=[AWL=0.342, 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 0M7a8FG3ha2F for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 07:23:22 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 275793A6ACF for <ietf@ietf.org>; Fri, 14 Jan 2011 07:23:22 -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 p0EFPkca092828 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 14 Jan 2011 08:25:47 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D306AFB.8000702@vpnc.org>
Date: Fri, 14 Jan 2011 07:25:47 -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: Lars Eggert <lars.eggert@nokia.com>
Subject: Use of "unassigned" in IANA registries
References: <C954A3DF.2B01C%michelle.cotton@icann.org> <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
In-Reply-To: <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com>
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, 14 Jan 2011 15:23:23 -0000

On 1/14/11 12:23 AM, Lars Eggert wrote:
> Hi,
>
> On 2011-1-13, at 22:43, Michelle Cotton wrote:
>> Many believe it makes it very clear to the users of the registry
>> what is available for assignment.  Something we will be rolling out
>> soon (for those registries with a finite space) will be small
>> charts showing how much of the registry space is unassigned,
>> assigned and reserved (utilizing the unassigned entries).
>
> I mentioned in the past that the term "unassigned" to me at least
> doesn't make it sufficiently clear that IANA assignment is often
> needed before codepoints may be taken into use. We have several cases
> (the many different squats on TCP option numbers, for example) were
> people pick unassigned codepoints during development and only later
> realize that they should have registered them.
>
> If you want to explicitly list unassigned codepoints in the
> registries, I'm wondering if we can find a short phrase that makes it
> more clear that an IANA action is normally required - maybe
> "available for IANA assignment"?

If IANA *doesn't* explicitly list unassigned codepoints in the 
registries, do you think that would make the problem of unintentional 
squatting better or worse? I can see it going either way, but you have 
probably thought about this more than I.

The unintentional squatting problem might be reduced by a note in every 
registry that says "unassigned code points must be assigned by IANA" or 
some such wording.

From dworley@avaya.com  Fri Jan 14 07:53:24 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 8F58A3A6BAC; Fri, 14 Jan 2011 07:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, 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 TWDYiQzjJ3Wj; Fri, 14 Jan 2011 07:53:23 -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 9EA933A6BA2; Fri, 14 Jan 2011 07:53:23 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACsAME3GmAcF/2dsb2JhbACkVnOkdwKWIIVPBIRriWeCXA
X-IronPort-AV: E=Sophos;i="4.60,323,1291611600"; d="scan'208";a="259652023"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 14 Jan 2011 10:55:48 -0500
X-IronPort-AV: E=Sophos;i="4.60,323,1291611600"; d="scan'208";a="570350257"
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; 14 Jan 2011 10:55:47 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.160]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 14 Jan 2011 10:55:11 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Phillip Hallam-Baker <hallam@gmail.com>, t.petch <daedulus@btconnect.com>
Date: Fri, 14 Jan 2011 10:52:40 -0500
Subject: RE: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
Thread-Topic: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
Thread-Index: Acuz6PC603mWdXGvRsmN6dic4QOgWgAGiHqb
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22092C4DE7@DC-US1MBEX4.global.avaya.com>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net> <4D2F2089.2000306@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com> <4D2F3C11.7000904@joelhalpern.com> <4D2F4086.3050601@stpeter.im> <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell> <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>, <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com>
In-Reply-To: <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: The 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: Fri, 14 Jan 2011 15:53:24 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Phillip Ha=
llam-Baker [hallam@gmail.com]

I believe that my personal security trumps any and all considerations that =
might be raised here.

I do not give my home address out and do not intend to change. If the RFC e=
ditor were to insist that the fields are filled they are going to get a fak=
e address.
_______________________________________________

There are a number of ways of establishing a postal address that is not con=
nected to one's physical residence.  Indeed, such postal addresses are ofte=
n more stable than one's residence address.  So I don't see any conflict of=
 requirements here.

(Though the idea of an author being targeted for assassination for writing =
an RFC does pique my interest!)

Dale

From dworley@avaya.com  Fri Jan 14 07:58:55 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 AFBBB3A6BB2 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 07:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, 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 7WutrW9FjxPa for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 07:58:54 -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 C2CC13A6BA7 for <ietf@ietf.org>; Fri, 14 Jan 2011 07:58:53 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJIBME2HCzI1/2dsb2JhbACkVnOkbQKWIIJ3glgEhGuJZw
X-IronPort-AV: E=Sophos;i="4.60,323,1291611600"; d="scan'208";a="54371651"
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; 14 Jan 2011 11:01:12 -0500
X-IronPort-AV: E=Sophos;i="4.60,323,1291611600"; d="scan'208";a="582409664"
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; 14 Jan 2011 11:00:27 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.160]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 14 Jan 2011 10:59:50 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Doug Ewell <doug@ewellic.org>, The IETF <ietf@ietf.org>
Date: Fri, 14 Jan 2011 10:57:40 -0500
Subject: RE: author's address
Thread-Topic: author's address
Thread-Index: AQHLtAQSnR7Gzi+P+0C0LiE18Z8QOA==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22092C4DE8@DC-US1MBEX4.global.avaya.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: Fri, 14 Jan 2011 15:58:55 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Doug Ewell=
 [doug@ewellic.org]

The argument that personal information is necessary to distinguish the
author from other people with the same name probably carries some weight
for authors named "John Smith" or "Bob Miller."  There are few enough
people named "Doug Ewell" in the world that the risk of ambiguity of
authorship seems much more remote than the risk to personal security if
too much personal information is provided.
_______________________________________________

OTOH, if "Doug Elwell" is unique enough to identify you personally, it's pr=
obably unique enough to allow tracing of your residence and employer, if so=
meone was willing to put in any significant effort.

Dale

From julian.reschke@gmx.de  Fri Jan 14 08:28:34 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 CF4773A6C4E for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 08:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.173
X-Spam-Level: 
X-Spam-Status: No, score=-104.173 tagged_above=-999 required=5 tests=[AWL=-1.574, 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 jLnt8CBM45xP for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 08:28:33 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 823E73A6C2A for <ietf@ietf.org>; Fri, 14 Jan 2011 08:28:31 -0800 (PST)
Received: (qmail invoked by alias); 14 Jan 2011 16:30:57 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp043) with SMTP; 14 Jan 2011 17:30:57 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/PraUi1FPPBQZC2lUPiPT/LsyuEi1F2qnPySO9kL IVNT4xtF6JDVpJ
Message-ID: <4D307A39.9070608@gmx.de>
Date: Fri, 14 Jan 2011 17:30:49 +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: author's address
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net>	<4D2E4DFF.6020507@gmail.com>	<80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net>	<4D2F2089.2000306@gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com>	<4D2F3C11.7000904@joelhalpern.com> <4D2F4086.3050601@stpeter.im>	<A618ECBD1CEA466899166BD12E3CB2D9@DougEwell>	<007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net>, <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DE7@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22092C4DE7@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: Phillip Hallam-Baker <hallam@gmail.com>, The 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: Fri, 14 Jan 2011 16:28:34 -0000

On 14.01.2011 16:52, Worley, Dale R (Dale) wrote:
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Phillip Hallam-Baker [hallam@gmail.com]
>
> I believe that my personal security trumps any and all considerations that might be raised here.
>
> I do not give my home address out and do not intend to change. If the RFC editor were to insist that the fields are filled they are going to get a fake address.
> _______________________________________________
>
> There are a number of ways of establishing a postal address that is not connected to one's physical residence.  Indeed, such postal addresses are often more stable than one's residence address.  So I don't see any conflict of requirements here.
>
> (Though the idea of an author being targeted for assassination for writing an RFC does pique my interest!)
> ...

We probably should require a Facebook URI.

Best regards, Julian

From hallam@gmail.com  Fri Jan 14 08:41:38 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 B057928C100 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 08:41:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.656
X-Spam-Level: 
X-Spam-Status: No, score=-3.656 tagged_above=-999 required=5 tests=[AWL=-0.058, 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 y479wl67Nlgl for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 08:41:37 -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 B986928C0FF for <ietf@ietf.org>; Fri, 14 Jan 2011 08:41:36 -0800 (PST)
Received: by gwj17 with SMTP id 17so1325620gwj.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 08:44: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=iQS97plTF0xjEhA5A+cUtrLjkP/+vwRrXieUBfd7u6w=; b=B6ILIFDW3pQ/9h0eRxYbBwLlY6EQTHN9KMnSHFOtF62i8FehSkffHr07bu85Wa8oAB cuUKYd6gS9VgWQZK9bFUoHYDN1QIDE2eJgzvYjg1t6Sdl5kLkvzG00jXU7aAIrqC+wUL m4DqYVjmuN2gxTm2RFyLkHqyYPNIpVQL/BWRg=
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=pIQRAn9dTLU6UuAiZQIPhzagvB2EJWHrvBsCWIS7fLd0T9a6qbqlyjhUjZyqJY7nuQ +t8PgPt9bcNBzojOTG0i7ixVY8psA9w/FZ1eW0KfGgqHODGlovNmkW1Nfz9du25RUV57 yZ5OsLaboyrfIgA2yiD7i7NMnfRLXrWv8OMrs=
MIME-Version: 1.0
Received: by 10.100.255.4 with SMTP id c4mr424225ani.69.1295023441945; Fri, 14 Jan 2011 08:44:01 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Fri, 14 Jan 2011 08:44:01 -0800 (PST)
In-Reply-To: <4D306AFB.8000702@vpnc.org>
References: <C954A3DF.2B01C%michelle.cotton@icann.org> <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com> <4D306AFB.8000702@vpnc.org>
Date: Fri, 14 Jan 2011 11:44:01 -0500
Message-ID: <AANLkTinvGSAaESzqLNYWLVRKFvxfo=hYkvHjTvmLVJBu@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=0016368e1bf03ba6180499d12489
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, 14 Jan 2011 16:41:38 -0000

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

The first law of the Internet is

   'You are so not in charge (for all values of you).'


The illusion of control is comforting to some but it is an illusion. At the
end of the day the IETF has roughly 2000 people involved. Nobody elected us.
We are accountable to no-one.

The Internet has 2 billion users. We do not accept accountability to those
users. We cannot even understand what their requirements might be. And even
if we did, we may well reject them out of hand.


At certain levels in the protocol stack the use of registries is
unavoidable. We have to have compact representations at the IP level. At the
application layer, they really don't matter at all.


The illusion of control is comforting, but it comes with costs.

The first cost is the cost of maintaining the registry. Assigning code
points requires an administrator, it frequently requires expert review. That
incurs time and money.

The second cost is that where there is control, the granting of a code point
will inescapably imply approval. I have no problems with the Russian
government using GOST but I do have serious problems with the fact that the
IETF has assigned code points for GOST.

The third (and in practice minor) cost is the confusion that can arise when
folk decide to freeboot themselves a code point. That could cause real
problems at the IP layer, but the risk is really rather marginal at all at
the application layer. We have remarkably few problems from collisions of
file name extensions and we have far more than three characters.


I suggest that the IAB consider a policy for registries that requires all
cryptographic and application layer code points to make use of an approved
extensible identifier format, with the two approved forms being URIs and
ASN.1 OIDs.

Such registries as are then maintained would be strictly limited to tracking
identifiers to be used for mandatory and preferred algorithms. Such
registries might assign abbreviated identifiers for such algorithms.


The main impact of this would be felt in cryptographic protocols. Instead of
having separate private use code spaces being maintained for IPSEC, DNSSEC,
TLS and PKIX, each of the protocols would be extended to allow the use of
ASN.1 OIDs (where these are not already used) for private code space. It
would be up to the developer of the algorithm to assign the OID.

(yes, yes, TLS suites, blah, its fixable)

[There is a small issue to do with URIs in XML based protocols. I think we
should collapse that registry into the ASN.1 format by using the OID URN
form]

The IETF would then cease considering requests to add code points for
non-recommended algorithms for those protocols. The only question that would
be considered in IETF space would be whether we want to add a new protocol
to the approved list.

The advantage of this approach would be that the 'vanity crypto' problem
would largely disappear. Particularly if the IETF/SAAG took the approach
that it would only recommend algorithms after it was demonstrated that a
very substantial community were either using them or planing to do so and
there were clear advantages over existing options.


The same principles would apply across the IETF. Anything that touches an
application has to have an extensible registry of OIDs or URIs for code
points that affect the application layer.

Removing the barriers to proliferation has the counterintuitive effect of
making it harder to establish a new algorithm. There being no barriers,
there are more candidates to choose from and the IETF is not available as a
forum to promote the proposal. Proposals have to win on their own merits.

Let a hundred flowers bloom and then Darwin can take care from that point
on.


This approach would not save people from themselves. But that is a futile
effort in an Internet of two billion people where we are not in charge
anyway (and neither is anyone else).


On Fri, Jan 14, 2011 at 10:25 AM, Paul Hoffman <paul.hoffman@vpnc.org>wrote:

> On 1/14/11 12:23 AM, Lars Eggert wrote:
>
>> Hi,
>>
>> On 2011-1-13, at 22:43, Michelle Cotton wrote:
>>
>>> Many believe it makes it very clear to the users of the registry
>>> what is available for assignment.  Something we will be rolling out
>>> soon (for those registries with a finite space) will be small
>>> charts showing how much of the registry space is unassigned,
>>> assigned and reserved (utilizing the unassigned entries).
>>>
>>
>> I mentioned in the past that the term "unassigned" to me at least
>> doesn't make it sufficiently clear that IANA assignment is often
>> needed before codepoints may be taken into use. We have several cases
>> (the many different squats on TCP option numbers, for example) were
>> people pick unassigned codepoints during development and only later
>> realize that they should have registered them.
>>
>> If you want to explicitly list unassigned codepoints in the
>> registries, I'm wondering if we can find a short phrase that makes it
>> more clear that an IANA action is normally required - maybe
>> "available for IANA assignment"?
>>
>
> If IANA *doesn't* explicitly list unassigned codepoints in the registries,
> do you think that would make the problem of unintentional squatting better
> or worse? I can see it going either way, but you have probably thought about
> this more than I.
>
> The unintentional squatting problem might be reduced by a note in every
> registry that says "unassigned code points must be assigned by IANA" or some
> such wording.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

The first law of the Internet is=A0<div><br></div><div>=A0=A0 &#39;You are =
so not in charge (for all values of you).&#39;<br><br></div><div><br></div>=
<div>The illusion of control is comforting to some but it is an illusion. A=
t the end of the day the IETF has roughly 2000 people involved. Nobody elec=
ted us. We are accountable to no-one.=A0</div>
<div><br></div><div>The Internet has 2 billion users. We do not accept acco=
untability to those users. We cannot even understand what their requirement=
s might be. And even if we did, we may well reject them out of hand.=A0</di=
v>
<div><br></div><div><br></div><div>At certain levels in the protocol stack =
the use of registries is unavoidable. We have to have compact representatio=
ns at the IP level. At the application layer, they really don&#39;t matter =
at all.=A0</div>
<div><br></div><div><br></div><div>The illusion of control is comforting, b=
ut it comes with costs.</div><div><br></div><div>The first cost is the cost=
 of maintaining the registry. Assigning code points requires an administrat=
or, it frequently requires expert review. That incurs time and money.</div>
<div><br></div><div>The second cost is that where there is control, the gra=
nting of a code point will inescapably imply approval. I have no problems w=
ith the Russian government using GOST but I do have serious problems with t=
he fact that the IETF has assigned code points for GOST.=A0</div>
<div><br></div><div>The third (and in practice minor) cost is the confusion=
 that can arise when folk decide to freeboot themselves a code point. That =
could cause real problems at the IP layer, but the risk is really rather ma=
rginal at all at the application layer. We have remarkably few problems fro=
m collisions of file name extensions and we have far more than three charac=
ters.</div>
<div><br></div><div><br></div><div>I suggest that the IAB consider a policy=
 for registries that requires all cryptographic and application layer code =
points to make use of an approved extensible identifier format, with the tw=
o approved forms being URIs and ASN.1 OIDs.</div>
<div><br></div><div>Such registries as are then maintained would be strictl=
y limited to tracking identifiers to be used for mandatory and preferred al=
gorithms. Such registries might assign abbreviated identifiers for such alg=
orithms.</div>
<div><br></div><div><br></div><div>The main impact of this would be felt in=
 cryptographic protocols. Instead of having separate private use code space=
s being maintained for IPSEC, DNSSEC, TLS and PKIX, each of the protocols w=
ould be extended to allow the use of ASN.1 OIDs (where these are not alread=
y used) for private code space. It would be up to the developer of the algo=
rithm to assign the OID.</div>
<div><br></div><div>(yes, yes, TLS suites, blah, its fixable)</div><div><br=
></div><div>[There is a small issue to do with URIs in XML based protocols.=
 I think we should collapse that registry into the ASN.1 format by using th=
e OID URN form]</div>
<div><br></div><div>The IETF would then cease considering requests to add c=
ode points for non-recommended algorithms for those protocols. The only que=
stion that would be considered in IETF space would be whether we want to ad=
d a new protocol to the approved list.</div>
<div><br></div><div>The advantage of this approach would be that the &#39;v=
anity crypto&#39; problem would largely disappear. Particularly if the IETF=
/SAAG took the approach that it would only recommend algorithms after it wa=
s demonstrated that a very substantial community were either using them or =
planing to do so and there were clear advantages over existing options.</di=
v>
<div><br></div><div><br></div><div>The same principles would apply across t=
he IETF. Anything that touches an application has to have an extensible reg=
istry of OIDs or URIs for code points that affect the application layer.</d=
iv>
<div><br></div><div>Removing the barriers to proliferation has the counteri=
ntuitive effect of making it harder to establish a new algorithm. There bei=
ng no barriers, there are more candidates to choose from and the IETF is no=
t available as a forum to promote the proposal. Proposals have to win on th=
eir own merits.</div>
<div><br></div><div>Let a hundred flowers bloom and then Darwin can take ca=
re from that point on.</div><div><br></div><div><br></div><div>This approac=
h would not save people from themselves. But that is a futile effort in an =
Internet of two billion people where we are not in charge anyway (and neith=
er is anyone else).</div>
<div><br></div><div><br><div class=3D"gmail_quote">On Fri, Jan 14, 2011 at =
10:25 AM, Paul Hoffman <span dir=3D"ltr">&lt;<a href=3D"mailto:paul.hoffman=
@vpnc.org">paul.hoffman@vpnc.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">
On 1/14/11 12:23 AM, Lars Eggert wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 2011-1-13, at 22:43, Michelle Cotton wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Many believe it makes it very clear to the users of the registry<br>
what is available for assignment. =A0Something we will be rolling out<br>
soon (for those registries with a finite space) will be small<br>
charts showing how much of the registry space is unassigned,<br>
assigned and reserved (utilizing the unassigned entries).<br>
</blockquote>
<br>
I mentioned in the past that the term &quot;unassigned&quot; to me at least=
<br>
doesn&#39;t make it sufficiently clear that IANA assignment is often<br>
needed before codepoints may be taken into use. We have several cases<br>
(the many different squats on TCP option numbers, for example) were<br>
people pick unassigned codepoints during development and only later<br>
realize that they should have registered them.<br>
<br>
If you want to explicitly list unassigned codepoints in the<br>
registries, I&#39;m wondering if we can find a short phrase that makes it<b=
r>
more clear that an IANA action is normally required - maybe<br>
&quot;available for IANA assignment&quot;?<br>
</blockquote>
<br>
If IANA *doesn&#39;t* explicitly list unassigned codepoints in the registri=
es, do you think that would make the problem of unintentional squatting bet=
ter or worse? I can see it going either way, but you have probably thought =
about this more than I.<br>

<br>
The unintentional squatting problem might be reduced by a note in every reg=
istry that says &quot;unassigned code points must be assigned by IANA&quot;=
 or some such wording.<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">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>

--0016368e1bf03ba6180499d12489--

From jpv@cisco.com  Thu Jan 13 22:41:25 2011
Return-Path: <jpv@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 4BC973A6AA8; Thu, 13 Jan 2011 22:41:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.41
X-Spam-Level: 
X-Spam-Status: No, score=-110.41 tagged_above=-999 required=5 tests=[AWL=0.188, 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 Ui9dGiRrHhxa; Thu, 13 Jan 2011 22:41:23 -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 099EF3A6A91; Thu, 13 Jan 2011 22:41:23 -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: ApYFAH9/L02rRN+J/2dsb2JhbACCPZoGiBFzpR+YVoVPBIsWgyg
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-2.cisco.com with ESMTP; 14 Jan 2011 06:43:47 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p0E6hkuj019098; Fri, 14 Jan 2011 06:43:47 GMT
Received: from xfe-ams-202.cisco.com ([144.254.231.96]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 07:43:45 +0100
Received: from ams-jvasseur-8711.cisco.com ([10.55.201.130]) by xfe-ams-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 07:43:44 +0100
Subject: Re: Gen-ART LC review of draft-ietf-roll-routing-metrics-14
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-138-1000128584
From: JP Vasseur <jpv@cisco.com>
In-Reply-To: <4d0f9da0.2308e30a.48c5.ffffae42@mx.google.com>
Date: Fri, 14 Jan 2011 07:43:44 +0100
Message-Id: <515C4A60-2334-4F40-8AE6-813042109560@cisco.com>
References: <4d0f9da0.2308e30a.48c5.ffffae42@mx.google.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-OriginalArrivalTime: 14 Jan 2011 06:43:44.0827 (UTC) FILETIME=[63B2C0B0:01CBB3B6]
X-Mailman-Approved-At: Fri, 14 Jan 2011 09:00:53 -0800
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>, draft-ietf-roll-routing-metrics.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, 14 Jan 2011 06:41:25 -0000

--Apple-Mail-138-1000128584
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi Roni,

Thanks for your thorough review - please see in line JP>

On Dec 20, 2010, at 7:14 PM, 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>.
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-roll-routing-metrics-14
> Reviewer: Roni Even
> Review Date:2010=9612=9620
> IETF LC End Date: 2011=961=965
> IESG Telechat date:
> =20
> Summary: This draft is almost ready for publication as an Standard =
track RFC.
> =20
> Major issues:
> No Major issues
> =20
> Minor issues:
> =20
> 1.  In section 2.1 after figure 1 you specify the different fields. =
Please specify the size in bits of the flags field the A-field and the =
prec field.

JP> Done.

> 2.  In section 2.1 in example 1 how is it known that all nodes MUST be =
main powered.

JP> In this example, we first explain how the headers flags are =
determined. To help clarify I modified the text:

OLD:

As far as the constraint is concerned, if the constraint signalled in =
the DIO message is not satisfied, the advertising node is just not =
selected as a parent by the node that processes the DIO message.

NEW:

As far as the constraint is concerned, the object body will carry a node =
energy constraint object defined in Section 3.1 indicating that nodes =
must be mains-powered: if the constraint signalled in the DIO message is =
not satisfied, the advertising node is just not selected as a parent by =
the node that processes the DIO message.

> Do you need to provide a value to prec field?

JP> As indicated earlier, the Prec field is only useful when a DAG =
Metric Container contains several Routing Metric objects. In this =
example, there is just one metric (the node energy is a constraint).

> 3.  In section 3.1 and throughout the document when you define the =
different object you have =93recommended value=3Dxx=94. I think that =
since this draft defines the table and create the initial table in the =
IANA consideration section these are the actual values. So maybe say =
that these are the actual values as specified in section 6 (6.1)

JP> We added "recommended values" until IANA confirms.

> 4.  In section 3.1 the flag field =96 how many bits, specify.

JP> Done.

> 5.  In section 3.2 figure 4 shows a flag field, how many bits, what is =
the value.

JP> Done.

> 6.  In section 6 according to rfc5226 =93IETF consensus=94 is now =
=93IETF review=94.

JP> Fixed.

> 7.  In section 6.1 you should say that the table has the initial =
values and add which numbers are available for allocation.

JP> Done.

> 8.  In section 6.2 what values are available for allocation.  Also say =
that currently the table is empty.

JP> Done.

> 9.  In section 6.2 is there a reason to create an empty table. Why not =
do it when there is a request to define a TLV

JP> Just to have the registry already in place. There is more than =
likely be TLVs defined in a very near future. This also allows to make =
sure that all TLVs have the same structure.

> 10.In section 6.3, are there more values allowed, can they be =
allocated. If not why have it managed by IANA.

JP> The A field is a 3-bit field and there are currently 4 defined =
values.

> 11.After the table in section in section 6.3 there is a request to =
create another table. Maybe it should be in a separate section.

JP> This is just because we put all registries belonging to the Routing =
Metric/Constraint Common Header in the same section.

> 12.In section 6.3 =93New bit numbers may be allocated=94, how many =
bits are available.

JP> The text was misplaced, thanks.

> 13.The same paragraph in section 6.3 also talks about the registration =
policy, is it different from the one that is common in section 6, why =
specify it again. Also look at comment 6

JP> This was a duplicate. Fixed.

> 14.Comment 12 and 13 are also true for section 6.4 and 6.5.
> =20

JP> Fixed too.

> =20
> =20
> Nits/editorial comments:
> =20
> 1.  In section first paragraph =93object=94 should be =93object=94
> 2.  In section 4.3.2 first paragraph =93wich=94 should be =93which=94
> =20

JP> Fixed.

Many Thanks. These changes are all incorporated in revision 15.

JP.

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


--Apple-Mail-138-1000128584
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><base href=3D"x-msg://673/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Hi Roni,<div><br></div><div>Thanks for your =
thorough review - please see in line JP&gt;<br><div><br><div><div>On Dec =
20, 2010, at 7:14 PM, Roni Even wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; ">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" =
style=3D"color: blue; text-decoration: underline; =
">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o=
:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10.5pt; font-family: Consolas; ">Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10.5pt; font-family: Consolas; ">Document: =
draft-ietf-roll-routing-metrics-14<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; ">Reviewer: =
Roni Even<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; ">Review Date:2010=9612=9620<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; ">IETF LC =
End Date: 2011=961=965<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
10.5pt; font-family: Consolas; ">IESG Telechat =
date:<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10.5pt; font-family: Consolas; ">Summary: This draft is =
almost ready for publication as an Standard track =
RFC.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10.5pt; font-family: Consolas; ">Major =
issues:<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; ">No Major issues<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 10.5pt; =
font-family: Consolas; ">Minor issues:<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><span>1.<span =
style=3D"font: normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 2.1 after figure 1 you specify the =
different fields. Please specify the size in bits of the flags field the =
A-field and the prec =
field.</div></div></div></span></blockquote><div><br></div><div>JP&gt; =
Done.</div><br><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0.5in; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; =
"><o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><span>2.<span =
style=3D"font: normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 2.1 in example 1 how is it known that all =
nodes MUST be main powered. =
</div></div></div></span></blockquote><div><br></div><div>JP&gt;&nbsp;In =
this example, we first explain how the headers flags are determined. To =
help clarify I modified the =
text:</div><div><br></div><div>OLD:</div><div><br></div><div>As far as =
the constraint is concerned, if the constraint signalled in the DIO =
message is not satisfied, the advertising node is just not selected as a =
parent by the node that processes the DIO =
message.</div><div><br></div><div>NEW:</div><div><br></div><div>As far =
as the constraint is concerned, the object body will carry a node energy =
constraint object defined in Section 3.1 indicating that nodes must be =
mains-powered: if the constraint signalled in the DIO message is not =
satisfied, the advertising node is just not selected as a parent by the =
node that processes the DIO message.</div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0.5in; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; ">Do you =
need to provide a value to prec =
field?</div></div></div></span></blockquote><div><br></div><div>JP&gt; =
As indicated earlier, the Prec field is only useful when a DAG Metric =
Container contains several Routing Metric objects. In this example, =
there is just one metric (the node energy is a =
constraint).</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>3.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 3.1 and throughout the document when you =
define the different object you have =93recommended value=3Dxx=94. I =
think that since this draft defines the table and create the initial =
table in the IANA consideration section these are the actual values. So =
maybe say that these are the actual values as specified in section 6 =
(6.1)</div></div></div></blockquote><div><br></div><div>JP&gt; We added =
"recommended values" until IANA confirms.</div><br><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div =
class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0.5in; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; =
"><span>4.<span style=3D"font: normal normal normal 7pt/normal 'Times =
New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 3.1 the flag field =96 how many bits, =
specify.</div></div></div></blockquote><div><br></div><div>JP&gt; =
Done.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue"=
 vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>5.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 3.2 figure 4 shows a flag field, how many =
bits, what is the =
value.</div></div></div></blockquote><div><br></div><div>JP&gt; =
Done.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue"=
 vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>6.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 6 according to rfc5226 =93IETF consensus=94 =
is now =93IETF =
review=94.</div></div></div></blockquote><div><br></div><div>JP&gt; =
Fixed.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>7.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 6.1 you should say that the table has the =
initial values and add which numbers are available for =
allocation.</div></div></div></blockquote><div><br></div><div>JP&gt; =
Done.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue"=
 vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>8.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 6.2 what values are available for =
allocation.&nbsp; Also say that currently the table is =
empty.</div></div></div></blockquote><div><br></div><div>JP&gt; =
Done.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue"=
 vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>9.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 6.2 is there a reason to create an empty =
table. Why not do it when there is a request to define a =
TLV</div></div></div></blockquote><div><br></div><div>JP&gt; Just to =
have the registry already in place. There is more than likely be TLVs =
defined in a very near future. This also allows to make sure that all =
TLVs have the same structure.</div><div><br></div><blockquote =
type=3D"cite"><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div =
class=3D"WordSection1" style=3D"page: WordSection1; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0.5in; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; =
"><span>10.</span><span dir=3D"LTR"></span>In section 6.3, are there =
more values allowed, can they be allocated. If not why have it managed =
by IANA.</div></div></div></blockquote><div><br></div><div>JP&gt; The A =
field is a 3-bit field and there are currently 4 defined =
values.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>11.</span><span dir=3D"LTR"></span>After =
the table in section in section 6.3 there is a request to create another =
table. Maybe it should be in a separate =
section.</div></div></div></blockquote><div><br></div><div>JP&gt; This =
is just because we put all registries belonging to the&nbsp;Routing =
Metric/Constraint Common Header in the same =
section.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>12.</span><span dir=3D"LTR"></span>In =
section 6.3 =93New bit numbers may be allocated=94, how many bits are =
available.</div></div></div></blockquote><div><br></div><div>JP&gt; The =
text was misplaced, thanks.</div><br><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0.5in; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; =
"><o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><span>13.</span><span =
dir=3D"LTR"></span>The same paragraph in section 6.3 also talks about =
the registration policy, is it different from the one that is common in =
section 6, why specify it again. Also look at comment =
6</div></div></div></blockquote><div><br></div><div>JP&gt; This was a =
duplicate. Fixed.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>14.</span><span dir=3D"LTR"></span>Comment =
12 and 13 are also true for section 6.4 and 6.5.<o:p></o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; =
"><o:p>&nbsp;</o:p></div></div></div></blockquote><div><br></div><div>JP&g=
t; Fixed too.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 0.0001pt; margin-left: 0.25in; font-size: 10.5pt; =
font-family: Consolas; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10.5pt; font-family: Consolas; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0in; font-size: 10.5pt; font-family: Consolas; =
">Nits/editorial comments:<o:p></o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; =
font-size: 10.5pt; font-family: Consolas; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; =
margin-left: 0.5in; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span>1.<span style=3D"font: normal normal =
normal 7pt/normal 'Times New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section first paragraph =93object=94 should be =
=93object=94<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0.5in; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; =
"><span>2.<span style=3D"font: normal normal normal 7pt/normal 'Times =
New Roman'; ">&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span><span =
dir=3D"LTR"></span>In section 4.3.2 first paragraph =93wich=94 should be =
=93which=94<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-bottom: 0.0001pt; margin-left: 0.5in; font-size: 10.5pt; =
font-family: Consolas; =
"><o:p>&nbsp;</o:p></div></div></div></blockquote><div><br></div><div>JP&g=
t; Fixed.</div><div><br></div><div>Many Thanks. These changes are all =
incorporated in revision =
15.</div><div><br></div><div>JP.</div><br><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: =
11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div></div>___________________________________________=
____<br>Ietf mailing list<br><a href=3D"mailto:Ietf@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">Ietf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/ietf</a><br></div></blockquote></d=
iv><br></div></div></body></html>=

--Apple-Mail-138-1000128584--

From paul@xelerance.com  Fri Jan 14 09:54:56 2011
Return-Path: <paul@xelerance.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 1B7A13A6BA3 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 09:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  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 cLrv0HcvB03J for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 09:54:55 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id 190E93A6A82 for <ietf@ietf.org>; Fri, 14 Jan 2011 09:54:55 -0800 (PST)
Received: from tla.xelerance.com (tla.xelerance.com [193.110.157.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id C74BCC4BA; Fri, 14 Jan 2011 12:57:19 -0500 (EST)
Date: Fri, 14 Jan 2011 12:57:19 -0500 (EST)
From: Paul Wouters <paul@xelerance.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
In-Reply-To: <AANLkTinvGSAaESzqLNYWLVRKFvxfo=hYkvHjTvmLVJBu@mail.gmail.com>
Message-ID: <alpine.LFD.1.10.1101141250280.11572@newtla.xelerance.com>
References: <C954A3DF.2B01C%michelle.cotton@icann.org> <D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com> <4D306AFB.8000702@vpnc.org> <AANLkTinvGSAaESzqLNYWLVRKFvxfo=hYkvHjTvmLVJBu@mail.gmail.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: Paul Hoffman <paul.hoffman@vpnc.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, 14 Jan 2011 17:54:56 -0000

On Fri, 14 Jan 2011, Phillip Hallam-Baker wrote:

> I suggest that the IAB consider a policy for registries that requires all cryptographic and application layer code
> points to make use of an approved extensible identifier format, with the two approved forms being URIs and ASN.1 OIDs.

-1

Not technology agnostic. 
Variable length instead of fixed length

A single byte or two bytes can work for anyone with any technology, now and 50 years from now.

> The main impact of this would be felt in cryptographic protocols. Instead of having separate private use code spaces
> being maintained for IPSEC, DNSSEC, TLS and PKIX, each of the protocols would be extended to allow the use of ASN.1 OIDs
> (where these are not already used) for private code space. It would be up to the developer of the algorithm to assign
> the OID.

It's too late for that now anyway isn't it. The code path is there, and if you want to be compatible
you have to implement it. Adding a second (complicated!) code path isn't going to help anyone make it
easier.

> The advantage of this approach would be that the 'vanity crypto' problem would largely disappear. Particularly if the
> IETF/SAAG took the approach that it would only recommend algorithms after it was demonstrated that a very substantial
> community were either using

catch-22. How can a substantial community use them before it has become a real standard?

> Let a hundred flowers bloom and then Darwin can take care from that point on.

I prefer my crypto more intelligently designed.

Paul

From dworley@avaya.com  Fri Jan 14 13:21:33 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 B6E443A6C81 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 13:21:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, 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 EXvzNHx813yB for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 13:21:31 -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 6177F3A6C86 for <ietf@ietf.org>; Fri, 14 Jan 2011 13:21:31 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPtNME3GmAcF/2dsb2JhbACkWXOkHAKWWoVPBIRriWc
X-IronPort-AV: E=Sophos;i="4.60,324,1291611600"; d="scan'208";a="54415996"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 14 Jan 2011 16:23:57 -0500
X-IronPort-AV: E=Sophos;i="4.60,324,1291611600"; d="scan'208";a="570466042"
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; 14 Jan 2011 16:23:55 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.160]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 14 Jan 2011 16:23:36 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 14 Jan 2011 16:22:46 -0500
Subject: Is the xml2rfc mailing list working?
Thread-Topic: Is the xml2rfc mailing list working?
Thread-Index: AQHLtDFNRgf875RRiEKV8+CnYdjNwg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22092C4DF1@DC-US1MBEX4.global.avaya.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: Fri, 14 Jan 2011 21:21:33 -0000

I've attempted to subscribe to the xml2rfc mailing list several times in th=
e last month, but never gotten a response.  Is it still working?

Dale

From mrex@sap.com  Fri Jan 14 14:04:11 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 372823A6BD8 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 14:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.15
X-Spam-Level: 
X-Spam-Status: No, score=-10.15 tagged_above=-999 required=5 tests=[AWL=0.099,  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 84mXGoXYktze for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 14:04:10 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id DB3743A6BD0 for <ietf@ietf.org>; Fri, 14 Jan 2011 14:04:09 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p0EM6XpL012090 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 14 Jan 2011 23:06:33 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>
Subject: Re: Use of "unassigned" in IANA registries
To: hallam@gmail.com (Phillip Hallam-Baker)
Date: Fri, 14 Jan 2011 23:06:33 +0100 (MET)
In-Reply-To: <AANLkTinvGSAaESzqLNYWLVRKFvxfo=hYkvHjTvmLVJBu@mail.gmail.com> from "Phillip Hallam-Baker" at Jan 14, 11 11:44:01 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: paul.hoffman@vpnc.org, 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: Fri, 14 Jan 2011 22:04:11 -0000

Phillip Hallam-Baker wrote:
> 
> The illusion of control is comforting to some but it is an illusion. At the
> end of the day the IETF has roughly 2000 people involved. Nobody elected us.
> We are accountable to no-one.

I assume the number of IETF contributors is more like 5000-10000.

> 
> The Internet has 2 billion users. We do not accept accountability to those
> users. We cannot even understand what their requirements might be. And even
> if we did, we may well reject them out of hand.

Everybody can get involved with the IETF and although some working groups
may have superseded rough consensus by voting these days, there are still
significant numbers of contributors involved in the IETF with non-marginal
levels of dignity about the technologies they are creating.


> 
> The first cost is the cost of maintaining the registry. Assigning code
> points requires an administrator, it frequently requires expert review.
> That incurs time and money.

You are asserting here that by _not_ using an IANA registry, but instead
relying on ASN.1 OIDs, suddenly the use of DSA with MD4 for a digital
signature obiviates expert review and becomes technically sound?


The assignment of a code point itself is a cost infinitesimal close to
zero.  No matter how you look at it, at the abstract level there is
no difference between an IANA code point assignment for something
and the assignment of an ASN.1 OID or an URIs by some organization.

But building and implementing protocols with small fixed-size integer
IANA-assiged values is magnitudes easier than messing around with
ASN.1 OIDs and URIs in terms of code, CPU cycles, storage requirements
and network bandwidth.  But the IANA assignment has the clear advantage
that it is a well-known single location that keeps track of all
assignments and associated specifications, while with ASN.1 OIDs
and URIs you might find yourself lost where no google/bing/whatever
heuristics can help you.

I know of a colleague who is struggling trying to move an RSA keypair
created on an IPhone to a Windows machine, but the default RSA CSP in
MS CryptoAPI rejects the keypair on PKCS#12 input (Firefox and OpenSSL
don't have a problem).  I'm suspecting it might be due to a primality test
suggested by X9.31, but that document is available at $$$ only.

With an IANA registry, the IETF can (and should) enforce free availability
of the relevant specifications plus at least availability of RAND conditions
for the surrounding (known) IPR claims.


> 
> The second cost is that where there is control, the granting of a code point
> will inescapably imply approval. I have no problems with the Russian
> government using GOST but I do have serious problems with the fact that the
> IETF has assigned code points for GOST.

I have no problem whatsoever with _code_points_ being assigned for GOST
by the IETF as long as there is a specification that describes the
exact semantics for the specific protocol context where this assignment
applies.

Attributing a recommendation level to the _use_ of GOST algorithms
for specific purposes is an entirely different matter.

There are code points assigned for cryptographic algorithms
like RC4-40 and MD4 for use with IETF protocols.  I'm much more
concerned about those than I am concerned about GOST.

Frankly, I'm actually more concerned about code assignments for
severely IPR-impaired algorithms (e.g. Elliptic Curve related)
than about GOST.  (Admittedly, the GOST 34.10-2001 signature
algorithm appears to use Elliptic curve math, and it's entirely
unclear to me whether and how existing EC-related IPR claims might
apply.)


> 
> (yes, yes, TLS suites, blah, its fixable)

The most appreciable part of TLS is, that it did not add any new
ASN.1 nonsense to the existing mess of X.509/PKIX.



-Martin

From julian.reschke@gmx.de  Fri Jan 14 14:49:05 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 1C3233A67E1 for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 14:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.983
X-Spam-Level: 
X-Spam-Status: No, score=-103.983 tagged_above=-999 required=5 tests=[AWL=-1.384, 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 jxk21BJa56Co for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 14:49:04 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id A6FD43A6813 for <ietf@ietf.org>; Fri, 14 Jan 2011 14:49:02 -0800 (PST)
Received: (qmail invoked by alias); 14 Jan 2011 22:51:27 -0000
Received: from p508FA993.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.169.147] by mail.gmx.net (mp051) with SMTP; 14 Jan 2011 23:51:27 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18CRwlRWikC04Lk/L4bwWyH6W1SX5jMJqBBmeELbR hWJjivxD1FdZbp
Message-ID: <4D30D365.8050308@gmx.de>
Date: Fri, 14 Jan 2011 23:51:17 +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: Is the xml2rfc mailing list working?
References: <CD5674C3CD99574EBA7432465FC13C1B22092C4DF1@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22092C4DF1@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: "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, 14 Jan 2011 22:49:05 -0000

On 14.01.2011 22:22, Worley, Dale R (Dale) wrote:
> I've attempted to subscribe to the xml2rfc mailing list several times in the last month, but never gotten a response.  Is it still working?

The mailing list definitively works (see the archives) -- may be just 
the admin part has a problem?

Best regards, Julian

From evnikita2@gmail.com  Fri Jan 14 17:28:33 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 46EAD3A6CEB for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 17:28:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.264
X-Spam-Level: 
X-Spam-Status: No, score=-2.264 tagged_above=-999 required=5 tests=[AWL=-0.625, 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 KWHboFotysMv for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 17:28:32 -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 39B373A6CE8 for <ietf@ietf.org>; Fri, 14 Jan 2011 17:28:32 -0800 (PST)
Received: by fxm9 with SMTP id 9so3738466fxm.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 17:30:58 -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=4m3WoEbnTyAUizz0xhEAY5crIdx7CQS7blCi6428wlc=; b=C6lzkNg5yFPrWiZUFttks6/+ePpco36PCITuq8vmxZ1G2wyJZ1eH8txx0uNmwnyEre hdYLUtFAdp41Ga6uVuHjrXpyBG4opMw6U9Lkv3UuMHYmlQpZZPWi89UvOgtyAOCk6QjT iog3dpQdrlWjqQ3SKxtNd6lsxtdjnCvKPQVwI=
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=IQcqQZAhkBhDNiJZR/cv+JTJ5xk6Ek6OH5KoeGBKB/Ig4FB2KLykGodJZ8vTn3IFwo A96+hExwnpeM6eEV/oGaY3/CkGK4fDRTs2Sw2JpOzgsB8lLGDPpNAlyluNDRlSN4OyN9 qWzncV5BKC1MGA8xAVJCXspvtlexLwIY1gBPk=
Received: by 10.223.98.197 with SMTP id r5mr1479344fan.68.1295055058479; Fri, 14 Jan 2011 17:30:58 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n7sm713489fam.35.2011.01.14.17.30.56 (version=SSLv3 cipher=RC4-MD5); Fri, 14 Jan 2011 17:30:57 -0800 (PST)
Message-ID: <4D30F8E4.3020809@gmail.com>
Date: Sat, 15 Jan 2011 03:31:16 +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: stig@cisco.com
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <C954A3DF.2B01C%michelle.cotton@icann.org>	<D21961EC-F70B-48EA-B0DE-C94110EA80E1@nokia.com> <ABE739C5ADAC9A41ACCC72DF366B719D03D0AC20@GLKMS2100.GREENLNK.NET>
In-Reply-To: <ABE739C5ADAC9A41ACCC72DF366B719D03D0AC20@GLKMS2100.GREENLNK.NET>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 15 Jan 2011 01:28:33 -0000

Hello all,

Summarizing all LC comments received so far, I'd like to propose the 
author of draft-ietf-pim-registry-03.txt the following changes to his 
document:

1. Abstract

Explain the abbreviations.

2. Introduction

Explain the abbreviations.

3. Add a new section directly after Introduction named '2. Registry 
Description' with the following content:

   2.1. The Name of the Registry

    The name of created registry is 'Protocol Independent Multicast 
(PIM) Message Types'.

2.2. The Format of the Registry

    The 'Protocol Independent Multicast (PIM) Message Types' registry
    consists of 3 values: Packet Type, Description and Reference. They
    are described below:

      Packet Type - an integer; values form 0 to 15 are assigned.

      Description - a brief decryption of packet type.

      Reference - the reference document, that defines the packet type.

2.3. Registration Procedures

    New assignments to 'Protocol Independent Multicast (PIM) Message Types'
    registry SHALL be made following the 'IETF Consensus' policies.
    [RFC5226]

2.4. The Initial Contents of the Registry

    This section contains the initial contents of the 'Protocol 
Independent Multicast (PIM)
  Message Types' registry.

   +---------+-------------------------------------+------------------+
    |  Type  | Description                         | Reference         |
    +--------+-------------------------------------+-------------------+
    |0       | Hello                               |[RFC3973] [RFC4601]|
    |1       | Register                            |[RFC4601]          |
    |2       | Register Stop                       |[RFC4601]          |
    |3       | Join/Prune                          |[RFC3973] [RFC4601]|
    |4       | Bootstrap                           |[RFC4601]          |
    |5       | Assert                              |[RFC3973] [RFC4601]|
    |6       | Graft                               |[RFC3973]          |
    |7       | Graft-Ack                           |[RFC3973]          |
    |8       | Candidate RP Advertisement          |[RFC4601]          |
    |9       | State Refresh                       |[RFC3973]          |
    |10      | DF Election                         |[RFC5015]          |
    |11-14   | Unassigned                          |this document      |
    |15      | Reserved                            |this document      |
    +--------+-------------------------------------+-------------------+

2.5. Sub-Registries

    No sub-registries are currently defined in 'Protocol Independent 
Multicast (PIM)
  Message Types' registry.

4. Security Consideration: renumber

5. IANA Considerations: renumber, modify in the following way:

IANA is asked to create the Protocol Independent Multicast (PIM)
  Message Types' registry following Section 2 of this document.

6. Other sections: renumber.

I suppose the author will accept my proposal that makes the registry 
description more clear.

All the best,
Mykyta Yevstifeyev




From chair@ietf.org  Fri Jan 14 18:48:27 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 BC8A03A6D03; Fri, 14 Jan 2011 18:48:27 -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 rPF2Ztku37U0; Fri, 14 Jan 2011 18:48:26 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id C2E793A6CFC; Fri, 14 Jan 2011 18:48:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 25A2FE089A; Fri, 14 Jan 2011 18:50: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 kzDBaW-6AZzC; Fri, 14 Jan 2011 18:50:54 -0800 (PST)
Received: from new-host.home (pool-173-79-232-76.washdc.fios.verizon.net [173.79.232.76]) by c1a.amsl.com (Postfix) with ESMTPSA id B872BE088D; Fri, 14 Jan 2011 18:50:53 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: IETF Turns 25 on 16 January 2011
Date: Fri, 14 Jan 2011 21:50:52 -0500
Message-Id: <DFC443A2-454C-4035-B75F-8668F8E67388@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: Sat, 15 Jan 2011 02:48:27 -0000

THE IETF CELEBRATES 25TH ANNIVERSARY

Many thanks to all of the volunteer IETF participants who over the
last 25 years have set the standards for a global Internet that now
connects more than 2 billion people.

Since the first meeting was held on the afternoon of January 16, 1986
in San Diego, California (see http://www.ietf.org/proceedings/01.pdf),
the IETF has published more than 4500 RFCs that describe the
fundamental technologies and widely used services on today's global
Internet.

IETF standards enabled every aspect of the phenomenal growth of the
Internet.  The IETF pioneered a unique, open standards process that is
based on "rough consensus and running code," not voting.  The process
is transparent, with every Internet-Draft and RFC available to
everyone without charge.  The process is accessible to everyone with
an email account.  While much of our work takes place on mail lists,
more that 80,000 participants have gathered at face-to-face meetings
over the last 25 years.

The 25th anniversary will be celebrated at IETF 80 in Prague (see
http://www.ietf.org/meeting/80/index.html), and we are assembling a
web page to remember some of the accomplishments, experiences, and
memories of the last 25 years (see http://www.ietf.org/25years).  The
web page will evolve greatly over the next few weeks, and your
contributions are encouraged.  Please send your contributions to
25years@ietf.org.

Once again, thank for all you have done for the Internet.  I look
forward to working with you in the future to make the Internet even
better.

Happy anniversary,
  Russ Housley
  IETF Chair


From hallam@gmail.com  Fri Jan 14 19:14:21 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 17DD73A680B for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 19:14:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level: 
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[AWL=0.128,  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 8BYcjGAKE+pX for <ietf@core3.amsl.com>; Fri, 14 Jan 2011 19:14:19 -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 7E13F3A680A for <ietf@ietf.org>; Fri, 14 Jan 2011 19:14:19 -0800 (PST)
Received: by yxt33 with SMTP id 33so1531880yxt.31 for <ietf@ietf.org>; Fri, 14 Jan 2011 19:16:46 -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=UubOv+euaVKD8o033KRlOUbwCu4XL1uJiyNJldlPz2M=; b=FM23lvPJSOvva8R4E9+Rw6H+qljX3+4iZEIdk0XDZ11N0jVONNSEJsdwtaIwyQohx7 0hJjbkJ1ytBmaFRB8acVfk0e5SlcJp2D5v4VrjjxYR5pzZfl4Th8Q3KwMZA0fB3t9c6l MowTDcdL64VrZYdrTlHpKV0qQ97QZDIRaqzb0=
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=pBQrCslmdP2sgIlk0qXIwvUT19ztjrp+FCTrXpAZrTZ7nEVmstfjNii6srCuIlw9Ks aWIpUFJFmLR6DBH7+HndovKkjscYMnzOnbaYnuAeV12SJpettHzYjyP3HipGsshUvGuU AuqQhVbPnpp0Bgu+IzYt30aTuold2MTJj8XR4=
MIME-Version: 1.0
Received: by 10.100.5.15 with SMTP id 15mr1055807ane.35.1295061405397; Fri, 14 Jan 2011 19:16:45 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Fri, 14 Jan 2011 19:16:45 -0800 (PST)
In-Reply-To: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>
References: <AANLkTinvGSAaESzqLNYWLVRKFvxfo=hYkvHjTvmLVJBu@mail.gmail.com> <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>
Date: Fri, 14 Jan 2011 22:16:45 -0500
Message-ID: <AANLkTim67mGk1v3Nrf+s6YmuBOtjUbW-xr0tEWb5BOve@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
From: Phillip Hallam-Baker <hallam@gmail.com>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=0016e645aacc07f4f20499d9fb9f
Cc: paul.hoffman@vpnc.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: Sat, 15 Jan 2011 03:14:21 -0000

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

On Fri, Jan 14, 2011 at 5:06 PM, Martin Rex <mrex@sap.com> wrote:

> Phillip Hallam-Baker wrote:
> >
> > The illusion of control is comforting to some but it is an illusion. At
> the
> > end of the day the IETF has roughly 2000 people involved. Nobody elected
> us.
> > We are accountable to no-one.
>
> I assume the number of IETF contributors is more like 5000-10000.
>
> >
> > The Internet has 2 billion users. We do not accept accountability to
> those
> > users. We cannot even understand what their requirements might be. And
> even
> > if we did, we may well reject them out of hand.
>
> Everybody can get involved with the IETF and although some working groups
> may have superseded rough consensus by voting these days, there are still
> significant numbers of contributors involved in the IETF with non-marginal
> levels of dignity about the technologies they are creating.


It is hard to imagine any structure that could provide for significantly
more than one person in a million being involved in the IETF.

We can face that fact or we can pretend that it doesn't matter and that we
can have power without accountability, I believe Rudyard Kippling's quote on
that topic was on point.


> The first cost is the cost of maintaining the registry. Assigning code
> > points requires an administrator, it frequently requires expert review.
> > That incurs time and money.
>
> You are asserting here that by _not_ using an IANA registry, but instead
> relying on ASN.1 OIDs, suddenly the use of DSA with MD4 for a digital
> signature obiviates expert review and becomes technically sound?
>

No, the proliferation of cryptographic algorithms is a bad thing in and of
itself.

In the past it was believed that having a backup algorithm was a good thing.
Then we discovered that in fact the security of a scheme is usually
determined by the least secure algorithm supported rather than the best and
that adding a backup algorithm merely created additional opportunities to
crack the system.


We should not therefore be in the business of expertly reviewing any crypto
unless we believe it to be a significant improvement on the existing
algorithms.

Your straw man case of DSA with MD4 is easy to reject. But what would be the
acceptance conditions?

>From a protocol standpoint the correct response is arguably to reject every
application. But doing that is impossible as the GOST case demonstrates. If
the IETF had not assigned the code points then they would have been assigned
by the GRU.


We cannot stop people from shooting themselves in the foot and we should not
try either.


>
> The assignment of a code point itself is a cost infinitesimal close to
> zero.  No matter how you look at it, at the abstract level there is
> no difference between an IANA code point assignment for something
> and the assignment of an ASN.1 OID or an URIs by some organization.
>

>From a political standpoint it is totally different. Assignment of an IANA
code point is an IETF endorsement no matter how many caveats we attempt to
apply.

The cost of expert review is non zero.



> With an IANA registry, the IETF can (and should) enforce free availability
> of the relevant specifications plus at least availability of RAND
> conditions
> for the surrounding (known) IPR claims


Nonsense.

If the IETF refuses to issue code points people will issue them themselves.
That was the original observation at the start of this thread.


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

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

<br><br><div class=3D"gmail_quote">On Fri, Jan 14, 2011 at 5:06 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:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">Phillip Hallam-Baker wrote:<br>
&gt;<br>
&gt; The illusion of control is comforting to some but it is an illusion. A=
t the<br>
&gt; end of the day the IETF has roughly 2000 people involved. Nobody elect=
ed us.<br>
&gt; We are accountable to no-one.<br>
<br>
</div>I assume the number of IETF contributors is more like 5000-10000.<br>
<div class=3D"im"><br>
&gt;<br>
&gt; The Internet has 2 billion users. We do not accept accountability to t=
hose<br>
&gt; users. We cannot even understand what their requirements might be. And=
 even<br>
&gt; if we did, we may well reject them out of hand.<br>
<br>
</div>Everybody can get involved with the IETF and although some working gr=
oups<br>
may have superseded rough consensus by voting these days, there are still<b=
r>
significant numbers of contributors involved in the IETF with non-marginal<=
br>
levels of dignity about the technologies they are creating.</blockquote><di=
v><br></div><div>It is hard to imagine any structure that could provide for=
 significantly more than one person in a million being involved in the IETF=
.</div>
<div><br></div><div>We can face that fact or we can pretend that it doesn&#=
39;t matter and that we can have power without accountability, I believe Ru=
dyard Kippling&#39;s quote on that topic was on point.</div><div><br></div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;"><div class=3D"im">
&gt; The first cost is the cost of maintaining the registry. Assigning code=
<br>
&gt; points requires an administrator, it frequently requires expert review=
.<br>
&gt; That incurs time and money.<br>
<br>
</div>You are asserting here that by _not_ using an IANA registry, but inst=
ead<br>
relying on ASN.1 OIDs, suddenly the use of DSA with MD4 for a digital<br>
signature obiviates expert review and becomes technically sound?<br></block=
quote><div><br></div><div>No, the proliferation of cryptographic algorithms=
 is a bad thing in and of itself.=A0</div><div><br></div><div>In the past i=
t was believed that having a backup algorithm was a good thing. Then we dis=
covered that in fact the security of a scheme is usually determined by the =
least secure algorithm supported rather than the best and that adding a bac=
kup algorithm merely created additional opportunities to crack the system.<=
/div>
<div><br></div><div><br></div><div>We should not therefore be in the busine=
ss of expertly reviewing any crypto unless we believe it to be a significan=
t improvement on the existing algorithms.</div><div><br></div><div>Your str=
aw man case of DSA with MD4 is easy to reject. But what would be the accept=
ance conditions?</div>
<div><br></div><div>From a protocol standpoint the correct response is argu=
ably to reject every application. But doing that is impossible as the GOST =
case demonstrates. If the IETF had not assigned the code points then they w=
ould have been assigned by the GRU.</div>
<div><br></div><div><br></div><div>We cannot stop people from shooting them=
selves in the foot and we should not try either.</div><div>=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">

<br>
The assignment of a code point itself is a cost infinitesimal close to<br>
zero. =A0No matter how you look at it, at the abstract level there is<br>
no difference between an IANA code point assignment for something<br>
and the assignment of an ASN.1 OID or an URIs by some organization.<br></bl=
ockquote><div><br></div><div>From a political standpoint it is totally diff=
erent. Assignment of an IANA code point is an IETF endorsement no matter ho=
w many caveats we attempt to apply.</div>
<div><br></div><div>The cost of expert review is non zero.</div><div><br></=
div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">
With an IANA registry, the IETF can (and should) enforce free availability<=
br>
of the relevant specifications plus at least availability of RAND condition=
s<br>
for the surrounding (known) IPR claims</blockquote><div><br></div><div>Nons=
ense.</div><div><br></div><div>If the IETF refuses to issue code points peo=
ple will issue them themselves. That was the original observation at the st=
art of this thread.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br><br>

--0016e645aacc07f4f20499d9fb9f--

From dhc2@dcrocker.net  Sat Jan 15 08:18:52 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 F2B483A6C00 for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 08:18:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.584
X-Spam-Level: 
X-Spam-Status: No, score=-6.584 tagged_above=-999 required=5 tests=[AWL=0.015,  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 kk4nNGtZtmqd for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 08:18:50 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id DDFF43A6D5E for <ietf@ietf.org>; Sat, 15 Jan 2011 08:18:49 -0800 (PST)
Received: from [192.168.1.179] (adsl-67-127-191-82.dsl.pltn13.pacbell.net [67.127.191.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0FGLD5v030933 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sat, 15 Jan 2011 08:21:18 -0800
Message-ID: <4D31C972.50509@dcrocker.net>
Date: Sat, 15 Jan 2011 08:21:06 -0800
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: IETF Discussion <ietf@ietf.org>
Subject: Re: New Year's Exploration:  Changing the Internet's Infrastructure
References: <4D1DEF2E.2070506@dcrocker.net>
In-Reply-To: <4D1DEF2E.2070506@dcrocker.net>
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]); Sat, 15 Jan 2011 08:21:18 -0800 (PST)
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: Sat, 15 Jan 2011 16:18:52 -0000

On 12/31/2010 6:56 AM, Dave CROCKER wrote:
> So I would like to ask for folks to help the community develop some concrete
> information about this, by adding entries and comments to the IETF's Outcomes Wiki:
>
> <http://trac.tools.ietf.org/misc/outcomes/>[2]
...
> Some infrastructure changes are designed for the router level of things and some
> are designed for host-level. But they provide underlying services that can then
> be used for better performance, reliability, or control or to make new
> applications viable.


G'day.

On some further thought about this question, the term "infrastructure" does not 
seem to be very helpful.

I suggest we distinguish where the "benefit barrier" is.  What kind of adoption 
is required before the adopters can gain benefit?


Single:

    In very rare cases, a single adopter can gain benefit immediately.  Even 
among the cases that qualify for this classification on a theoretical basis, I 
suspect the fact that they qualify is an accident and that they were expected to 
have a different adoption requirement, and probably do have a different one, 
predominantly.  That is, the single-adopter benefit is probably deemed 
insufficient.  DKIM is an example of this.


Pair:

    Any communicating pair of systems can gain immediate benefit.  I like citing 
MIME as a stellar example of this.  I suppose ARP also qualifies.


Path:

    All of the systems along the path need to adopt the change before it can 
provide benefit.  IPv6 is an obvious example of this.  In the email arena, so is 
Delivery Service Notice.  However note that the ability to predict the path is 
very poor, so that broader adoption is typically required before a particular 
path will happen to provide the necessary support.


Subsystem:

    Very broad-based adoption by an extended service must first occur.  BGP and 
DNSSEC are examples.


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From krishnabirth@gmail.com  Sat Jan 15 13:26:49 2011
Return-Path: <krishnabirth@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 91A7128B56A for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 13:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.668
X-Spam-Level: 
X-Spam-Status: No, score=-2.668 tagged_above=-999 required=5 tests=[AWL=-0.559, BAYES_05=-1.11, 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 VyfLcehY8e0k for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 13:26:48 -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 443693A6D0A for <ietf@ietf.org>; Sat, 15 Jan 2011 13:26:43 -0800 (PST)
Received: by wwa36 with SMTP id 36so3902235wwa.13 for <ietf@ietf.org>; Sat, 15 Jan 2011 13:28:57 -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=Ou6/qDhRHECW0N9T/TO0LrjG8ogBZe9WKKHq1QIJwlQ=; b=lrp5JWy5Zx/7uUboZ0slYR8EhWcbiF8pvjdtw6oQKf0dQkP7W2XKVlJ3D3i1+N7uzv LWtTqMRpWes8kr0TLXQj/a1d0mCDQkV0G+CRlSK1LV5YxO7APPGme1RHSIsDMuW5ueXU dClVIL7VB6t7Wk7lGFDx/XbkAmrjRGCUAc01U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=EVjShpePJyzeasjHXkPocBwThPh/2d+rLcjfFGj9tkj1fO6bGUbum8NQPWviSMGPX2 h+5BOlsrVVnraPLmmZQfFP+gvZucwxcFh/5vBvlQtptL77mk93FtWgdsibljwyMDzXXJ ApWfkXOU43nwgUHaJ76Ob3Hqs6j8uzWy3dVfU=
MIME-Version: 1.0
Received: by 10.216.169.71 with SMTP id m49mr1909730wel.4.1295125245696; Sat, 15 Jan 2011 13:00:45 -0800 (PST)
Received: by 10.216.153.136 with HTTP; Sat, 15 Jan 2011 13:00:45 -0800 (PST)
Date: Sat, 15 Jan 2011 21:00:45 +0000
Message-ID: <AANLkTik1_yccbxXBPRiDGGD2gV3EkiABJVLTNE_dX0O6@mail.gmail.com>
Subject: RFC for Internet Interfacing Items (e.g. Rail Modelling, Server Types) / Rail Model Free font for Coders
From: Krishna Birth <krishnabirth@gmail.com>
To: ietf@ietf.org, unicode@unicode.org
Content-Type: multipart/alternative; boundary=0016367b664e359b8e0499e8d8e4
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, 15 Jan 2011 21:26:49 -0000

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

(please view this email with UTF-8 enabled on your viewer)

I would be interested to find out from the IETF (Internet Engineering Tas=
=E0=A4=95
Force) if there is a RFC (http://en.wikipedia.org/wiki/Request_for_Comments=
)
for computer users that allows them to individually control, for example
rail modelling / railroad modelling (my specific circumstance, see next
paragraph) in other geographic locations via the Internet and World Wide
Web.  Thus users could view on website/s live videos of the rail modelling
station and rail modelling train/s and could enable their movement includin=
g
things for example pulley, cranes etc.

The reasons for this (my specific circumstance) is for My Spiritual Master,
His Divine Grace A C Bha=E0=A4=95tivedanta Swami Prabhupada (Hare =E0=A4=95=
rishna Founder)
signalling automated initiations via Rail Modelling in November 1977 in
order to continue spiritually being the initiating spiritual master
eternally till humanity remains humanity.

Also please tell me if there is any RFCs for server types, for example I am
interested in hosting applications and sites on servers that are watercoole=
d
with India's holy rivers (for example, River Ganges) distilled water.

There is a font for coders called Rail Model:

http://code.google.com/p/railmodel/downloads/detail?name=3DRailModelFont.zi=
p&can=3D2&q=3D

Copyright: Copyright (c) 2010, Copyright (c) Holder for the commissioned
(Unicode 0915) devanagri glyph design as the new 11th english and european
glyph and the cancellation of the previous k / K is (His Divine Grace)
Prabhupada, Founder Acharya & Permanent Sole Initiator of the Panca Tattva =
/
Caitanya Mahaprabhu / Vaisnava Movement, the permanent person not the
estate, state, representative/s or representative organisation/s etc. All
Rights Reserved. (full and also other copyright information at accompanying
font files)

Description: November 20 2010 (Hrant H Papazian) Version 1.1 =C3=90 k/K (Un=
icode
glyphs /006B and /004B) exchanged through Unicode glyph / uni0915 =C3=90 re=
leased
as

N: Hrant H Papazian
E: hpapazian.....
W: http://www.themicrofoundry.com
D: Designer =C3=90 Unicode glyph /uni0915 upper and lower case



Best,


Mee=E0=A4=95u

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

<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;" id=3D"internal-source-marker_0=
.5624929827876415">(please view this email with UTF-8 enabled on your viewe=
r)</span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;"></span><br><span style=3D"font=
-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: tra=
nsparent; font-weight: normal; font-style: normal; text-decoration: none; v=
ertical-align: baseline;">I
would be interested to find out from the IETF (Internet Engineering
Tas=E0=A4=95 Force) if there is a RFC
(<a href=3D"http://en.wikipedia.org/wiki/Request_for_Comments">http://en.wi=
kipedia.org/wiki/Request_for_Comments</a>) for computer users
that allows them to individually control, for example rail modelling /
railroad modelling (my specific circumstance, see next paragraph) in
other geographic locations via the Internet and World Wide Web. =C2=A0Thus
users could view on website/s live videos of the rail modelling station
and rail modelling train/s and could enable their movement including
things for example pulley, cranes etc. </span><br><span style=3D"font-size:=
 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transpare=
nt; font-weight: normal; font-style: normal; text-decoration: none; vertica=
l-align: baseline;"></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">The
reasons for this (my specific circumstance) is for My Spiritual Master,
His Divine Grace A C Bha=E0=A4=95tivedanta Swami Prabhupada (Hare =E0=A4=95=
rishna
Founder) signalling automated initiations via Rail Modelling in
November 1977 in order to continue spiritually being the initiating
spiritual master eternally till humanity remains humanity.</span><br><span =
style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); backgrou=
nd-color: transparent; font-weight: normal; font-style: normal; text-decora=
tion: none; vertical-align: baseline;"></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">Also
please tell me if there is any RFCs for server types, for example I am
interested in hosting applications and sites on servers that are
watercooled with India&#39;s holy rivers (for example, River Ganges)
distilled water.</span><br><span style=3D"font-size: 11pt; font-family: Ari=
al; color: rgb(0, 0, 0); background-color: transparent; font-weight: normal=
; font-style: normal; text-decoration: none; vertical-align: baseline;"></s=
pan><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">There is a font for coders cal=
led Rail Model:</span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;"></span><br><span style=3D"font=
-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: tra=
nsparent; font-weight: normal; font-style: normal; text-decoration: none; v=
ertical-align: baseline;"><a href=3D"http://code.google.com/p/railmodel/dow=
nloads/detail?name=3DRailModelFont.zip&amp;can=3D2&amp;q=3D">http://code.go=
ogle.com/p/railmodel/downloads/detail?name=3DRailModelFont.zip&amp;can=3D2&=
amp;q=3D</a></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;"></span><br><span style=3D"font=
-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: tra=
nsparent; font-weight: normal; font-style: normal; text-decoration: none; v=
ertical-align: baseline;">Copyright:
Copyright (c) 2010, Copyright (c) Holder for the commissioned (Unicode
0915) devanagri glyph design as the new 11th english and european glyph
and the cancellation of the previous k / K is (His Divine Grace)
Prabhupada, Founder Acharya &amp; Permanent Sole Initiator of the Panca
Tattva / Caitanya Mahaprabhu / Vaisnava Movement, the permanent person
not the estate, state, representative/s or representative
organisation/s etc. All Rights Reserved. (full and also other copyright
information at accompanying font files)</span><br><span style=3D"font-size:=
 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: transpare=
nt; font-weight: normal; font-style: normal; text-decoration: none; vertica=
l-align: baseline;"></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">Description:
November 20 2010 (Hrant H Papazian) Version 1.1 =C3=90 k/K (Unicode glyphs
/006B and /004B) exchanged through Unicode glyph / uni0915 =C3=90 released =
as</span><br><span style=3D"font-size: 11pt; font-family: Arial; color: rgb=
(0, 0, 0); background-color: transparent; font-weight: normal; font-style: =
normal; text-decoration: none; vertical-align: baseline;"></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">N: Hrant H Papazian</span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">E: hpapazian.....</span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">W: <a href=3D"http://www.themi=
crofoundry.com">http://www.themicrofoundry.com</a></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">D: Designer =C3=90 Unicode gly=
ph /uni0915 upper and lower case</span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;"> </span><br><span style=3D"fon=
t-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: tr=
ansparent; font-weight: normal; font-style: normal; text-decoration: none; =
vertical-align: baseline;"></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;"></span><br><span style=3D"font=
-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: tra=
nsparent; font-weight: normal; font-style: normal; text-decoration: none; v=
ertical-align: baseline;">Best,</span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;"></span><br><span style=3D"font=
-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); background-color: tra=
nsparent; font-weight: normal; font-style: normal; text-decoration: none; v=
ertical-align: baseline;"></span><br>
<span style=3D"font-size: 11pt; font-family: Arial; color: rgb(0, 0, 0); ba=
ckground-color: transparent; font-weight: normal; font-style: normal; text-=
decoration: none; vertical-align: baseline;">Mee=E0=A4=95u</span>

--0016367b664e359b8e0499e8d8e4--

From lixia@cs.ucla.edu  Sat Jan 15 20:19:25 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 4F5963A6DA3 for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 20:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 gzREB3Siy3Tx for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 20:19:24 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by core3.amsl.com (Postfix) with ESMTP id ED66E3A6818 for <ietf@ietf.org>; Sat, 15 Jan 2011 20:19:23 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 8FA7239E80E1; Sat, 15 Jan 2011 20:21:53 -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 QjzrPYJzmkaQ; Sat, 15 Jan 2011 20:21:52 -0800 (PST)
Received: from [10.0.1.2] (cpe-76-174-94-219.socal.res.rr.com [76.174.94.219]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 4943C39E8083; Sat, 15 Jan 2011 20:21:52 -0800 (PST)
Subject: Re: I-D Action:draft-white-tsvwg-netblt-00.txt
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-15--983068302
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <154FFBA5C44220EC28FF5899@PST.JCK.COM>
Date: Sat, 15 Jan 2011 20:21:51 -0800
Message-Id: <AE59B6A0-2C30-42A7-89CD-448F0CE9634D@cs.ucla.edu>
References: <154FFBA5C44220EC28FF5899@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.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: Sun, 16 Jan 2011 04:19:25 -0000

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


On Jan 11, 2011, at 1:09 AM, John C Klensin wrote:

> --On Saturday, January 08, 2011 07:37 -0800 Lixia Zhang
> <lixia@cs.ucla.edu> wrote:
>=20
>> I am not sure why this rush to get a new internet draft out,
>> without consultation to any of its original authors, and given
>> the rough consensus on ietf mailing list discussion is to keep
>> NETBLT RFC as is (experimental). =20
>=20
> Lixia,
>=20
> I'm not sure there is any rush.  I'm also not sure that the
> effort that is going into this could not be better spent in
> other ways.  I'm also not sure about the opposite of either -- I
> actually don't have a strong opinion one way or the other.
>=20
> However, it seems to me that...
>=20
> (i) It has been a very long time since we published
> specifications that might now be considered Experimental with
> disclaimers that said, more or less, "don't even think about
> implementing this without a discussion with, and maybe
> permission from, the author".  If a spec is published as
> Experimental, then people are assumed to be free, modulo any IPR
> issues, to implement and test it.

Hi John,

I could see that my earlier msg could be read in a wrong way.
The reason for contacting original authors is to find out what are the =
things that they know about the protocol (that were not mentioned in the =
specification), so one can either save the time to reinvent the wheel or =
even overlook problems/solutions that were discovered earlier.  As I =
said in my earlier msg =
(http://www6.ietf.org/mail-archive/web/ietf/current/msg65063.html),

.......
unless there is clearly identified need for a protocol like NETBLT (as =
its name suggested, it is a specialized protocol for bulk data transfer =
only), I do not see the need to move NETBLT to standard.

In case such a need is identified, personally I think we need a clear =
problem statement first, so that we better understand the context the =
protocol will be applied to.  We (the MIT crew at the time) did various =
trials of NETBLT after the RFC998's publication, and collected a list of =
issues for further investigation.

For example, one issue I can still recall clearly is NETBLT's congestion =
control design and the interaction with TCP traffic (I cannot recall the =
whole list on top of my head now after all these years, though there may =
still be old notes around).

But I would like to pop up a level here: this thread started with a =
notion that rfc2026 was wrong regarding experimental rfcs so actions are =
taken now to do something with these rfcs.  I agree with Bob's comment =
that (http://www6.ietf.org/mail-archive/web/ietf/current/msg65072.html),
Hi,
> > I think that the author of RFC2026 was wrong while writing the =
definition of Historic status. This document says that Historic should =
be assigned only to that documents that were standards and now are =
obsolete. But why do we need such narrow definition? Non-standards RFCs =
are not made Historic while obsoleting, according to 2026. Moreover, =
such status will just duplicate the obsoleted-by one. When there will be =
the attempt to revise RFC 2026, we should put there that Historic status =
is to be assigned to that documents that are considered to be =
deprecated. I fully share the opinion of Doug here.

If you think RFC20206 is wrong, then propose changes to it and see if =
people agree with the changes.  Until it is changed, IMHO you should not =
propose actions based on what you as an individual think is incorrect.  =
There needs to be a community consensus that RFC2026 is wrong before any =
action should be taken.

Bob

Lixia=

--Apple-Mail-15--983068302
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 Jan 11, 2011, at 1:09 AM, John C Klensin =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>--On Saturday, January 08, 2011 07:37 -0800 Lixia =
Zhang<br>&lt;<a =
href=3D"mailto:lixia@cs.ucla.edu">lixia@cs.ucla.edu</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">I am not sure why this rush to =
get a new internet draft out,<br></blockquote><blockquote =
type=3D"cite">without consultation to any of its original authors, and =
given<br></blockquote><blockquote type=3D"cite">the rough consensus on =
ietf mailing list discussion is to keep<br></blockquote><blockquote =
type=3D"cite">NETBLT RFC as is (experimental). =
&nbsp;<br></blockquote><br>Lixia,<br><br>I'm not sure there is any rush. =
&nbsp;I'm also not sure that the<br>effort that is going into this could =
not be better spent in<br>other ways. &nbsp;I'm also not sure about the =
opposite of either -- I<br>actually don't have a strong opinion one way =
or the other.<br><br>However, it seems to me that...<br><br>(i) It has =
been a very long time since we published<br>specifications that might =
now be considered Experimental with<br>disclaimers that said, more or =
less, "don't even think about<br>implementing this without a discussion =
with, and maybe<br>permission from, the author". &nbsp;If a spec is =
published as<br>Experimental, then people are assumed to be free, modulo =
any IPR<br>issues, to implement and test =
it.<br></div></blockquote><div><br></div>Hi =
John,</div><div><br></div><div>I could see that my earlier msg could be =
read in a wrong way.</div><div>The reason for contacting original =
authors is to find out what are the things that they know about the =
protocol (that were not mentioned in the specification), so one can =
either save the time to reinvent the wheel or even overlook =
problems/solutions that were discovered earlier. &nbsp;As I said in my =
earlier msg (<a =
href=3D"http://www6.ietf.org/mail-archive/web/ietf/current/msg65063.html">=
http://www6.ietf.org/mail-archive/web/ietf/current/msg65063.html</a>),</di=
v><div><br></div><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin: 0 0 0 40px; border: none; padding: =
0px;"><div>.......</div></blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px; border: =
none; padding: 0px;"><div>unless there is clearly identified need for a =
protocol like NETBLT (as its name suggested, it is a specialized =
protocol for bulk&nbsp;data transfer only), I do not see the need to =
move NETBLT to standard.</div><div><br></div><div>In case such a need is =
identified, personally I think we need a clear problem statement first, =
so that we better understand the&nbsp;context the protocol will be =
applied to. &nbsp;We (the MIT crew at the time) did various trials of =
NETBLT after the RFC998's&nbsp;publication, and collected a list of =
issues for further investigation.</div><div><br></div></blockquote>For =
example, one issue I can still recall clearly is NETBLT's congestion =
control design and the interaction with TCP traffic (I cannot recall the =
whole list on top of my head now after all these years, though there may =
still be old notes around).<div><br></div><div>But I would like to pop =
up a level here: this thread started with a notion that rfc2026 was =
wrong regarding experimental rfcs so actions are taken now to do =
something with these rfcs. &nbsp;I agree with Bob's comment that (<a =
href=3D"http://www6.ietf.org/mail-archive/web/ietf/current/msg65072.html">=
http://www6.ietf.org/mail-archive/web/ietf/current/msg65072.html</a>),</di=
v><blockquote class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 =
40px; border: none; padding: 0px;"><div><span class=3D"Apple-style-span" =
style=3D"font-family: 'Times New Roman'; =
"><pre><div>Hi,</div></pre></span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: 'Times New Roman'; =
"><pre><blockquote type=3D"cite">&gt; I think that the author of RFC2026 =
was wrong while writing the definition of Historic status. This document =
says that Historic should be assigned only to that documents that were =
standards and now are obsolete. But why do we need such narrow =
definition? Non-standards RFCs are not made Historic while obsoleting, =
according to 2026. Moreover, such status will just duplicate the =
obsoleted-by one. When there will be the attempt to revise RFC 2026, we =
should put there that Historic status is to be assigned to that =
documents that are considered to be deprecated. I fully share the =
opinion of Doug here.</blockquote></pre></span></div><div><span =
class=3D"Apple-style-span" style=3D"font-family: 'Times New Roman'; =
"><pre><div>If you think RFC20206 is wrong, then propose changes to it =
and see if people agree with the changes.  Until it is changed, IMHO you =
should not propose actions based on what you as an individual think is =
incorrect.  There needs to be a community consensus that RFC2026 is =
wrong before any action should be taken.

Bob</div></pre></span></div></blockquote><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;"><br></span></font><div><font class=3D"Apple-style-span" =
face=3D"monospace"><span class=3D"Apple-style-span" style=3D"white-space: =
pre;">Lixia</span></font></div></body></html>=

--Apple-Mail-15--983068302--

From ron.even.tlv@gmail.com  Sun Jan 16 05:05:26 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 BDD0A3A6B61; Sun, 16 Jan 2011 05:05:26 -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 3CwXSrGVIkPK; Sun, 16 Jan 2011 05:05:18 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 548C63A6B49; Sun, 16 Jan 2011 05:05:18 -0800 (PST)
Received: by qwi2 with SMTP id 2so4164169qwi.31 for <multiple recipients>; Sun, 16 Jan 2011 05:07:49 -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:x-mailer:thread-index :content-language; bh=KSeGzLaS+DQFEP8oATkGL4xWQEee5qU5jjKdLeCySUw=; b=pmwYKs0c4gsbywl2CV0/lqe2ZhoLjZI2R/RZ0cnX9hyJyAsUwdGz4wVKxI7Gt7AMqJ pKHDm9eia3WWNEdhyIM05BTcojjshoYckuQBiVtsTKD76X87V72Kdl54KpYS2nSOGxYK f8d00dgkOmq1xWs6ClCKM3RDEWag6VgDjOr0g=
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:x-mailer:thread-index:content-language; b=WG+BQ8QtWPrwFkN071iQmeZCtlAqpoVFTuHLJMU4iPGrTZFMwFVTSVM/FVtl5GzdlV t8FuhI9iMguEOEETXeWN9+7cVIwDxrld4RB0+0COsLfi8TvsfApg5RajW13JU95DJWmg zxMe+UMJa+UL6HF97zwfOO/xoZVEHqB4ui+Gg=
Received: by 10.224.2.141 with SMTP id 13mr2798620qaj.284.1295183269256; Sun, 16 Jan 2011 05:07:49 -0800 (PST)
Received: from YOUR6108 (user-0ccehtm.cable.mindspring.com [24.199.71.182]) by mx.google.com with ESMTPS id e29sm2202363qck.27.2011.01.16.05.07.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 16 Jan 2011 05:07:47 -0800 (PST)
From: "rontlv" <ron.even.tlv@gmail.com>
To: "'JP Vasseur'" <jpv@cisco.com>
References: <4d0f9da0.2308e30a.48c5.ffffae42@mx.google.com> <515C4A60-2334-4F40-8AE6-813042109560@cisco.com>
In-Reply-To: <515C4A60-2334-4F40-8AE6-813042109560@cisco.com>
Subject: RE: Gen-ART LC review of draft-ietf-roll-routing-metrics-14
Date: Sun, 16 Jan 2011 15:07:59 +0200
Message-ID: <4d32eda3.1d4de50a.4290.ffffaf99@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01CBB58F.2AB3AC40"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcuztmYvYxTPBxqhTcOjuXhiNXFfcwBx+aWw
Content-Language: he
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>, draft-ietf-roll-routing-metrics.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, 16 Jan 2011 13:05:26 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01CBB58F.2AB3AC40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi JP,

Thanks, I am OK with all your responses

Roni

 

From: JP Vasseur [mailto:jpv@cisco.com] 
Sent: Friday, January 14, 2011 8:44 AM
To: Roni Even
Cc: gen-art@ietf.org; draft-ietf-roll-routing-metrics.all@tools.ietf.org;
IETF-Discussion list
Subject: Re: Gen-ART LC review of draft-ietf-roll-routing-metrics-14

 

Hi Roni,

 

Thanks for your thorough review - please see in line JP>

 

On Dec 20, 2010, at 7:14 PM, 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-roll-routing-metrics-14

Reviewer: Roni Even

Review Date:2010-12-20

IETF LC End Date: 2011-1-5

IESG Telechat date:

 

Summary: This draft is almost ready for publication as an Standard track
RFC.

 

Major issues:

No Major issues

 

Minor issues:

 

1.  In section 2.1 after figure 1 you specify the different fields. Please
specify the size in bits of the flags field the A-field and the prec field.

 

JP> Done.





2.  In section 2.1 in example 1 how is it known that all nodes MUST be main
powered. 

 

JP> In this example, we first explain how the headers flags are determined.
To help clarify I modified the text:

 

OLD:

 

As far as the constraint is concerned, if the constraint signalled in the
DIO message is not satisfied, the advertising node is just not selected as a
parent by the node that processes the DIO message.

 

NEW:

 

As far as the constraint is concerned, the object body will carry a node
energy constraint object defined in Section 3.1 indicating that nodes must
be mains-powered: if the constraint signalled in the DIO message is not
satisfied, the advertising node is just not selected as a parent by the node
that processes the DIO message.





Do you need to provide a value to prec field?

 

JP> As indicated earlier, the Prec field is only useful when a DAG Metric
Container contains several Routing Metric objects. In this example, there is
just one metric (the node energy is a constraint).





3.  In section 3.1 and throughout the document when you define the different
object you have "recommended value=xx". I think that since this draft
defines the table and create the initial table in the IANA consideration
section these are the actual values. So maybe say that these are the actual
values as specified in section 6 (6.1)

 

JP> We added "recommended values" until IANA confirms.





4.  In section 3.1 the flag field - how many bits, specify.

 

JP> Done.





5.  In section 3.2 figure 4 shows a flag field, how many bits, what is the
value.

 

JP> Done.





6.  In section 6 according to rfc5226 "IETF consensus" is now "IETF review".

 

JP> Fixed.





7.  In section 6.1 you should say that the table has the initial values and
add which numbers are available for allocation.

 

JP> Done.





8.  In section 6.2 what values are available for allocation.  Also say that
currently the table is empty.

 

JP> Done.





9.  In section 6.2 is there a reason to create an empty table. Why not do it
when there is a request to define a TLV

 

JP> Just to have the registry already in place. There is more than likely be
TLVs defined in a very near future. This also allows to make sure that all
TLVs have the same structure.

 

10.In section 6.3, are there more values allowed, can they be allocated. If
not why have it managed by IANA.

 

JP> The A field is a 3-bit field and there are currently 4 defined values.





11.After the table in section in section 6.3 there is a request to create
another table. Maybe it should be in a separate section.

 

JP> This is just because we put all registries belonging to the Routing
Metric/Constraint Common Header in the same section.





12.In section 6.3 "New bit numbers may be allocated", how many bits are
available.

 

JP> The text was misplaced, thanks.





13.The same paragraph in section 6.3 also talks about the registration
policy, is it different from the one that is common in section 6, why
specify it again. Also look at comment 6

 

JP> This was a duplicate. Fixed.





14.Comment 12 and 13 are also true for section 6.4 and 6.5.

 

 

JP> Fixed too.





 

 

Nits/editorial comments:

 

1.  In section first paragraph "object" should be "object"

2.  In section 4.3.2 first paragraph "wich" should be "which"

 

 

JP> Fixed.

 

Many Thanks. These changes are all incorporated in revision 15.

 

JP.





 

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

 



__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5785 (20110113) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


------=_NextPart_000_000C_01CBB58F.2AB3AC40
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)"><base href=3D"x-msg://673/"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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 style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi JP,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks, I am OK with all your responses<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-right:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
JP Vasseur [mailto:jpv@cisco.com] <br><b>Sent:</b> Friday, January 14, =
2011 8:44 AM<br><b>To:</b> Roni Even<br><b>Cc:</b> gen-art@ietf.org; =
draft-ietf-roll-routing-metrics.all@tools.ietf.org; IETF-Discussion =
list<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-ietf-roll-routing-metrics-14<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Hi =
Roni,<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Thanks for your thorough review - please see in line =
JP&gt;<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Dec 20, 2010, at 7:14 PM, Roni Even wrote:<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>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">http://w=
iki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></span=
></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Document: =
draft-ietf-roll-routing-metrics-14<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Reviewer: Roni =
Even<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Review =
Date:2010&#8211;12&#8211;20<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>IETF LC End Date: =
2011&#8211;1&#8211;5<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>IESG Telechat =
date:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Summary: This draft is =
almost ready for publication as an Standard track =
RFC.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Major =
issues:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>No Major =
issues<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Minor =
issues:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>1.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 2.1 after =
figure 1 you specify the different fields. Please specify the size in =
bits of the flags field the A-field and the prec =
field.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Done.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>2.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 2.1 in =
example 1 how is it known that all nodes MUST be main powered. =
<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt;&nbsp;In this example, we first explain how the =
headers flags are determined. To help clarify I modified the =
text:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>OLD:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>As far as the constraint is concerned, if the =
constraint signalled in the DIO message is not satisfied, the =
advertising node is just not selected as a parent by the node that =
processes the DIO message.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>NEW:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>As far as the constraint is concerned, the object body =
will carry a node energy constraint object defined in Section 3.1 =
indicating that nodes must be mains-powered: if the constraint signalled =
in the DIO message is not satisfied, the advertising node is just not =
selected as a parent by the node that processes the DIO =
message.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Do you need to provide a =
value to prec field?<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; As indicated earlier, the Prec field is only =
useful when a DAG Metric Container contains several Routing Metric =
objects. In this example, there is just one metric (the node energy is a =
constraint).<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>3.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 3.1 and =
throughout the document when you define the different object you have =
&#8220;recommended value=3Dxx&#8221;. I think that since this draft =
defines the table and create the initial table in the IANA consideration =
section these are the actual values. So maybe say that these are the =
actual values as specified in section 6 =
(6.1)<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; We added &quot;recommended values&quot; until =
IANA confirms.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>4.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 3.1 the flag =
field &#8211; how many bits, =
specify.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Done.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>5.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 3.2 figure 4 =
shows a flag field, how many bits, what is the =
value.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Done.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>6.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 6 according =
to rfc5226 &#8220;IETF consensus&#8221; is now &#8220;IETF =
review&#8221;.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Fixed.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>7.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 6.1 you =
should say that the table has the initial values and add which numbers =
are available for allocation.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Done.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>8.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 6.2 what =
values are available for allocation.&nbsp; Also say that currently the =
table is empty.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Done.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>9.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 6.2 is there =
a reason to create an empty table. Why not do it when there is a request =
to define a TLV<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Just to have the registry already in place. =
There is more than likely be TLVs defined in a very near future. This =
also allows to make sure that all TLVs have the same =
structure.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>10.In section 6.3, are =
there more values allowed, can they be allocated. If not why have it =
managed by IANA.<o:p></o:p></span></p></div></div></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; The A field is a 3-bit field and there are =
currently 4 defined values.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>11.After the table in =
section in section 6.3 there is a request to create another table. Maybe =
it should be in a separate =
section.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; This is just because we put all registries =
belonging to the&nbsp;Routing Metric/Constraint Common Header in the =
same section.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>12.In section 6.3 =
&#8220;New bit numbers may be allocated&#8221;, how many bits are =
available.<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; The text was misplaced, =
thanks.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>13.The same paragraph in =
section 6.3 also talks about the registration policy, is it different =
from the one that is common in section 6, why specify it again. Also =
look at comment 6<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; This was a duplicate. =
Fixed.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>14.Comment 12 and 13 are =
also true for section 6.4 and 6.5.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Fixed too.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div =
style=3D'margin-left:18.0pt'><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>Nits/editorial =
comments:<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div><div style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>1.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section first =
paragraph &#8220;object&#8221; should be =
&#8220;object&#8221;<o:p></o:p></span></p></div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal =
style=3D'text-indent:-18.0pt'><span =
style=3D'font-size:10.5pt;font-family:Consolas'>2.</span><span =
style=3D'font-size:7.0pt'>&nbsp;<span =
class=3Dapple-converted-space>&nbsp;</span></span><span =
style=3D'font-size:10.5pt;font-family:Consolas'>In section 4.3.2 first =
paragraph &#8220;wich&#8221; should be =
&#8220;which&#8221;<o:p></o:p></span></p></div><div =
style=3D'margin-left:36.0pt'><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;font-family:Consolas'>&nbsp;<o:p></o:p></span><=
/p></div></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP&gt; Fixed.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Many Thanks. These changes are all incorporated in =
revision 15.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>JP.<o:p></o:p></p></div><p =
class=3DMsoNormal><br><br><o:p></o:p></p><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p></div><p =
class=3DMsoNormal>_______________________________________________<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">https://www.ietf.org/=
mailman/listinfo/ietf</a><o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p =
class=3DMsoNormal><br><br>__________ Information from ESET NOD32 =
Antivirus, version of virus signature database 5785 (20110113) =
__________<br><br>The message was checked by ESET NOD32 =
Antivirus.<br><br><a =
href=3D"http://www.eset.com">http://www.eset.com</a><o:p></o:p></p></div>=
</div> <BR><BR>__________ Information from ESET NOD32 Antivirus, version =
of virus signature database 5791 (20110116) __________<BR><BR>The =
message was checked by ESET NOD32 Antivirus.<BR><BR><A =
HREF=3D"http://www.eset.com">http://www.eset.com</A><BR> </body></html>
------=_NextPart_000_000C_01CBB58F.2AB3AC40--


From iljitsch@muada.com  Sun Jan 16 14:28:02 2011
Return-Path: <iljitsch@muada.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 414233A67DF for <ietf@core3.amsl.com>; Sun, 16 Jan 2011 14:28:02 -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, 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 l64LdR910Tqw for <ietf@core3.amsl.com>; Sun, 16 Jan 2011 14:28:01 -0800 (PST)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id A7CB93A6C2B for <ietf@ietf.org>; Sun, 16 Jan 2011 14:28:00 -0800 (PST)
Received: from [IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2] ([IPv6:2001:470:1f0b:1289:223:12ff:fe56:36b2]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id p0GMU8o5076130 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 16 Jan 2011 23:30:09 +0100 (CET) (envelope-from iljitsch@muada.com)
Subject: Re: Use of "unassigned" in IANA registries
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>
Date: Sun, 16 Jan 2011 23:30:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1082)
Cc: Phillip Hallam-Baker <hallam@gmail.com>, paul.hoffman@vpnc.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: Sun, 16 Jan 2011 22:28:03 -0000

On 14 jan 2011, at 23:06, Martin Rex wrote:

> Frankly, I'm actually more concerned about code assignments for
> severely IPR-impaired algorithms (e.g. Elliptic Curve related)
> than about GOST.  (Admittedly, the GOST 34.10-2001 signature
> algorithm appears to use Elliptic curve math, and it's entirely
> unclear to me whether and how existing EC-related IPR claims might
> apply.)

Withholding registration just means that people are going to pick an =
unregistered number with all the problems that that entails. In cases =
where there are no scarcity issues registration should happen as long as =
there is a reasonable expectation of non-negligible use, regardless of =
whether the registered protocol is endorsed by the IETF (whatever that =
means) or IANA.=

From hallam@gmail.com  Sun Jan 16 15:21:19 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 080D528C0D0 for <ietf@core3.amsl.com>; Sun, 16 Jan 2011 15:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.47
X-Spam-Level: 
X-Spam-Status: No, score=-3.47 tagged_above=-999 required=5 tests=[AWL=0.128,  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 X-AtQtlr+2qw for <ietf@core3.amsl.com>; Sun, 16 Jan 2011 15:21:17 -0800 (PST)
Received: from mail-yi0-f42.google.com (mail-yi0-f42.google.com [209.85.218.42]) by core3.amsl.com (Postfix) with ESMTP id 0076C28C0CE for <ietf@ietf.org>; Sun, 16 Jan 2011 15:21:16 -0800 (PST)
Received: by yia28 with SMTP id 28so2439439yia.15 for <ietf@ietf.org>; Sun, 16 Jan 2011 15:23:49 -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=7h5AYhdv7I05rlcBPU8LTrULdoUZUyAHx86dq8iPfno=; b=SO7vkLBoWg21LA2M581+p6yxFwxq9zDSfqbf7qX6GbpFjiByp/lANtkHUXZbnQcIcK agPsNrnSIYhuDTCTfwSwaFG0aUPI0kz8OE9nWFsQLhzseFoecTLKkOGJpFcc6fYYsMLO H3jgzBMxYuL8GL/bxSmkHo5nJpwY95WHGtAwk=
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=hwNnZXu0zkvAPGqEDQoeIFKxlFyDpeODeB+WES75AN+LFooKMslMlG/CtMQEYTwZQj HFKfQ1OzcjdNCIOSincbU0pdmQu/1+VjXMy1bfn4gcIx9aVApaZ0zJ5QxYOJqTt7GyNG UFW44xFfwtpyVYGJGQALgcNXhZYYGzYf6kOhs=
MIME-Version: 1.0
Received: by 10.100.153.17 with SMTP id a17mr2088917ane.239.1295220229060; Sun, 16 Jan 2011 15:23:49 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Sun, 16 Jan 2011 15:23:49 -0800 (PST)
In-Reply-To: <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com>
Date: Sun, 16 Jan 2011 18:23:49 -0500
Message-ID: <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Content-Type: multipart/alternative; boundary=0016e644d5cca8b7900499fef5da
Cc: paul.hoffman@vpnc.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: Sun, 16 Jan 2011 23:21:19 -0000

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

On Sun, Jan 16, 2011 at 5:30 PM, Iljitsch van Beijnum <iljitsch@muada.com>wrote:

> On 14 jan 2011, at 23:06, Martin Rex wrote:
>
> > Frankly, I'm actually more concerned about code assignments for
> > severely IPR-impaired algorithms (e.g. Elliptic Curve related)
> > than about GOST.  (Admittedly, the GOST 34.10-2001 signature
> > algorithm appears to use Elliptic curve math, and it's entirely
> > unclear to me whether and how existing EC-related IPR claims might
> > apply.)
>
> Withholding registration just means that people are going to pick an
> unregistered number with all the problems that that entails. In cases where
> there are no scarcity issues registration should happen as long as there is
> a reasonable expectation of non-negligible use, regardless of whether the
> registered protocol is endorsed by the IETF (whatever that means) or IANA.


+1

If people think that IANA is a tool they can use to impose their own
personal political agenda on the Internet, they are mistaken.

Here we have a proposal to enforce a particular royalty free agenda. Some
Internet users might support such an agenda but most don't even understand
what the argument would be about.

It is very easy to accept the idea of someone imposing a political agenda
you agree with. But what if the agenda turned out to be something else? What
happens if the representation from authoritarian leaning countries increases
and there is a group of people who agree on the need to fight 'information
terrorism' as defined in the SCO treaty.

All that is necessary to keep the Internet open is to prevent any party from
gaining control.

And the best way to prevent that is to ensure that there is no control
point.



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

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

<br><br><div class=3D"gmail_quote">On Sun, Jan 16, 2011 at 5:30 PM, Iljitsc=
h van Beijnum <span dir=3D"ltr">&lt;<a href=3D"mailto:iljitsch@muada.com">i=
ljitsch@muada.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On 14 jan 2011, at 23:06, Martin Rex wrote:<br>
<br>
&gt; Frankly, I&#39;m actually more concerned about code assignments for<br=
>
&gt; severely IPR-impaired algorithms (e.g. Elliptic Curve related)<br>
&gt; than about GOST. =A0(Admittedly, the GOST 34.10-2001 signature<br>
&gt; algorithm appears to use Elliptic curve math, and it&#39;s entirely<br=
>
&gt; unclear to me whether and how existing EC-related IPR claims might<br>
&gt; apply.)<br>
<br>
</div>Withholding registration just means that people are going to pick an =
unregistered number with all the problems that that entails. In cases where=
 there are no scarcity issues registration should happen as long as there i=
s a reasonable expectation of non-negligible use, regardless of whether the=
 registered protocol is endorsed by the IETF (whatever that means) or IANA.=
</blockquote>
</div><br>+1<div><br></div><div>If people think that IANA is a tool they ca=
n use to impose their own personal political agenda on the Internet, they a=
re mistaken.</div><div><br></div><div>Here we have a proposal to enforce a =
particular royalty free agenda. Some Internet users might support such an a=
genda but most don&#39;t even understand what the argument would be about.<=
/div>
<div><br></div><div>It is very easy to accept the idea of someone imposing =
a political agenda you agree with. But what if the agenda turned out to be =
something else? What happens if the representation from authoritarian leani=
ng countries increases and there is a group of people who agree on the need=
 to fight &#39;information terrorism&#39; as defined in the SCO treaty.</di=
v>
<div><br></div><div>All that is necessary to keep the Internet open is to p=
revent any party from gaining control.=A0</div><div><br></div><div>And the =
best way to prevent that is to ensure that there is no control point.</div>
<div><br></div><div><br></div><div><br>-- <br>Website: <a href=3D"http://ha=
llambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e644d5cca8b7900499fef5da--

From evnikita2@gmail.com  Mon Jan 17 09:50:44 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 B687328C1D1 for <ietf@core3.amsl.com>; Mon, 17 Jan 2011 09:50:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level: 
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=-0.622,  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 IhtB-skUv8fQ for <ietf@core3.amsl.com>; Mon, 17 Jan 2011 09:50:43 -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 1DC0528C1A2 for <ietf@ietf.org>; Mon, 17 Jan 2011 09:50:43 -0800 (PST)
Received: by gwj17 with SMTP id 17so2269815gwj.31 for <ietf@ietf.org>; Mon, 17 Jan 2011 09:53:17 -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=CJffEc4rEFsXjYNWJwkHCVxbtuXzVP4T8nmOKHoiIQQ=; b=LT2ApBFP78YhnSu0R4bfdr435Q/zc+aHzbG43q0VLyoSpztXTnGEhSdQcuqwXNIdim ywpPwQdZK4RIUcBKptLdHHzu+bLR/JIKJNdrE2886DmUXNSbs2MFGvtJ3tDa7UnGK4ve PQBa5Fs3VB3Yns36dH37WRMIwpu+0rN1KuIAM=
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=k9sj8HdJLo+65/wwNXL+6Srl7bp6XvWbPmKxnzBP9P4gmc0ZV46SFVAolbWlE1m+pI K2UhFXO/Nxatux180mVs6AOgZDccRJ+qkmadR3j7lkTIwz1QzGVbSumoth8hem2q1Av1 iFT1o3eH6y0yY7UmfRCx4nVzb6onbK2QBCXm0=
Received: by 10.204.72.71 with SMTP id l7mr2470156bkj.55.1295286796996; Mon, 17 Jan 2011 09:53:16 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id 12sm2192620bki.7.2011.01.17.09.53.15 (version=SSLv3 cipher=RC4-MD5); Mon, 17 Jan 2011 09:53:16 -0800 (PST)
Message-ID: <4D348220.10804@gmail.com>
Date: Mon, 17 Jan 2011 19: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: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>	<06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com>
In-Reply-To: <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090605080600090603000508"
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 17 Jan 2011 17:50:45 -0000

This is a multi-part message in MIME format.
--------------090605080600090603000508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

The isues discussed here is the use of unassigned values in IANA 
registries.  And I really agree with the authors of RFC5226 that sets 
MUST criterion for mentioning these values.  Not mentioning them will 
lead to misunderstanding by IANA and other people whether the values are 
available for assignment, reserved or not used et al.  So I think that 
there is just no need to discuss what is clearly set by the document.

All the best,
Mykyta Yevstifeyev

17.01.2011 1:23, Phillip Hallam-Baker wrote:
>
>
> On Sun, Jan 16, 2011 at 5:30 PM, Iljitsch van Beijnum 
> <iljitsch@muada.com <mailto:iljitsch@muada.com>> wrote:
>
>     On 14 jan 2011, at 23:06, Martin Rex wrote:
>
>     > Frankly, I'm actually more concerned about code assignments for
>     > severely IPR-impaired algorithms (e.g. Elliptic Curve related)
>     > than about GOST.  (Admittedly, the GOST 34.10-2001 signature
>     > algorithm appears to use Elliptic curve math, and it's entirely
>     > unclear to me whether and how existing EC-related IPR claims might
>     > apply.)
>
>     Withholding registration just means that people are going to pick
>     an unregistered number with all the problems that that entails. In
>     cases where there are no scarcity issues registration should
>     happen as long as there is a reasonable expectation of
>     non-negligible use, regardless of whether the registered protocol
>     is endorsed by the IETF (whatever that means) or IANA.
>
>
> +1
>
> If people think that IANA is a tool they can use to impose their own 
> personal political agenda on the Internet, they are mistaken.
>
> Here we have a proposal to enforce a particular royalty free agenda. 
> Some Internet users might support such an agenda but most don't even 
> understand what the argument would be about.
>
> It is very easy to accept the idea of someone imposing a political 
> agenda you agree with. But what if the agenda turned out to be 
> something else? What happens if the representation from authoritarian 
> leaning countries increases and there is a group of people who agree 
> on the need to fight 'information terrorism' as defined in the SCO treaty.
>
> All that is necessary to keep the Internet open is to prevent any 
> party from gaining control.
>
> And the best way to prevent that is to ensure that there is no control 
> point.
>
>
>
> -- 
> Website: http://hallambaker.com/
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--------------090605080600090603000508
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">
    Dear all,<br>
    <br>
    The isues discussed here is the use of unassigned values in IANA
    registries.&nbsp; And I really agree with the authors of RFC5226 that
    sets MUST criterion for mentioning these values.&nbsp; Not mentioning
    them will lead to misunderstanding by IANA and other people whether
    the values are available for assignment, reserved or not used et
    al.&nbsp; So I think that there is just no need to discuss what is
    clearly set by the document.<br>
    <br>
    All the best,<br>
    Mykyta Yevstifeyev<br>
    <br>
    17.01.2011 1:23, Phillip Hallam-Baker wrote:
    <blockquote
      cite="mid:AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com"
      type="cite"><br>
      <br>
      <div class="gmail_quote">On Sun, Jan 16, 2011 at 5:30 PM, Iljitsch
        van Beijnum <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:iljitsch@muada.com">iljitsch@muada.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          <div class="im">On 14 jan 2011, at 23:06, Martin Rex wrote:<br>
            <br>
            &gt; Frankly, I'm actually more concerned about code
            assignments for<br>
            &gt; severely IPR-impaired algorithms (e.g. Elliptic Curve
            related)<br>
            &gt; than about GOST. &nbsp;(Admittedly, the GOST 34.10-2001
            signature<br>
            &gt; algorithm appears to use Elliptic curve math, and it's
            entirely<br>
            &gt; unclear to me whether and how existing EC-related IPR
            claims might<br>
            &gt; apply.)<br>
            <br>
          </div>
          Withholding registration just means that people are going to
          pick an unregistered number with all the problems that that
          entails. In cases where there are no scarcity issues
          registration should happen as long as there is a reasonable
          expectation of non-negligible use, regardless of whether the
          registered protocol is endorsed by the IETF (whatever that
          means) or IANA.</blockquote>
      </div>
      <br>
      +1
      <div><br>
      </div>
      <div>If people think that IANA is a tool they can use to impose
        their own personal political agenda on the Internet, they are
        mistaken.</div>
      <div><br>
      </div>
      <div>Here we have a proposal to enforce a particular royalty free
        agenda. Some Internet users might support such an agenda but
        most don't even understand what the argument would be about.</div>
      <div><br>
      </div>
      <div>It is very easy to accept the idea of someone imposing a
        political agenda you agree with. But what if the agenda turned
        out to be something else? What happens if the representation
        from authoritarian leaning countries increases and there is a
        group of people who agree on the need to fight 'information
        terrorism' as defined in the SCO treaty.</div>
      <div><br>
      </div>
      <div>All that is necessary to keep the Internet open is to prevent
        any party from gaining control.&nbsp;</div>
      <div><br>
      </div>
      <div>And the best way to prevent that is to ensure that there is
        no control point.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
        -- <br>
        Website: <a moz-do-not-send="true"
          href="http://hallambaker.com/">http://hallambaker.com/</a><br>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Ietf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090605080600090603000508--

From julian.reschke@gmx.de  Mon Jan 17 14:47: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 F0E6D3A6F56 for <ietf@core3.amsl.com>; Mon, 17 Jan 2011 14:47:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.978
X-Spam-Level: 
X-Spam-Status: No, score=-103.978 tagged_above=-999 required=5 tests=[AWL=-1.379, 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 k8oEGYb7gF5H for <ietf@core3.amsl.com>; Mon, 17 Jan 2011 14:47:25 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id B2CB43A6F52 for <ietf@ietf.org>; Mon, 17 Jan 2011 14:47:24 -0800 (PST)
Received: (qmail invoked by alias); 17 Jan 2011 22:49:57 -0000
Received: from p508FBCBE.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.188.190] by mail.gmx.net (mp007) with SMTP; 17 Jan 2011 23:49:57 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+nb2NoOLCn87n4Iaj4EFCAb5B65+6t+ET7hxGJ1p EZfeGGKwzIIDUa
Message-ID: <4D34C77F.6000500@gmx.de>
Date: Mon, 17 Jan 2011 23:49:35 +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: Mykyta Yevstifeyev <evnikita2@gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp>	<06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com>	<AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com> <4D348220.10804@gmail.com>
In-Reply-To: <4D348220.10804@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 17 Jan 2011 22:47:26 -0000

On 17.01.2011 18:53, Mykyta Yevstifeyev wrote:
> Dear all,
>
> The isues discussed here is the use of unassigned values in IANA
> registries. And I really agree with the authors of RFC5226 that sets
> MUST criterion for mentioning these values. Not mentioning them will
> lead to misunderstanding by IANA and other people whether the values are
> available for assignment, reserved or not used et al. So I think that
> there is just no need to discuss what is clearly set by the document.
>
> All the best,
> Mykyta Yevstifeyev

Maybe you should ask the authors of RFC 5226 whether they agree with 
your interpretation of the spec.

Best regards, Julian

From lars.eggert@nokia.com  Mon Jan 17 23:44:34 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 9B52E3A6F0B for <ietf@core3.amsl.com>; Mon, 17 Jan 2011 23:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.95
X-Spam-Level: 
X-Spam-Status: No, score=-103.95 tagged_above=-999 required=5 tests=[AWL=-1.351, 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 Ms90UOX5WwBJ for <ietf@core3.amsl.com>; Mon, 17 Jan 2011 23:44:33 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 93D1D3A6D05 for <ietf@ietf.org>; Mon, 17 Jan 2011 23:44:33 -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 p0I7l240015381 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 09:47:04 +0200
Subject: Re: Use of "unassigned" in IANA registries
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-1--797964971; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com>
Date: Tue, 18 Jan 2011 09:46:54 +0200
Message-Id: <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@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); Tue, 18 Jan 2011 09:47:00 +0200 (EET)
X-Nokia-AV: Clean
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 18 Jan 2011 07:44:34 -0000

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

Hi,

On 2011-1-17, at 1:23, Phillip Hallam-Baker wrote:
> If people think that IANA is a tool they can use to impose their own
> personal political agenda on the Internet, they are mistaken.

that isn't the point of this thread.

The point of IANA assignment is to avoid conflicting codepoint usage. =
Squatting on codepoints defeats this goal.

For example, see the TCP option number registry at =
http://www.iana.org/assignments/tcp-parameters/tcp-parameters.xml#tcp-para=
meters-1. The highest IANA-assigned option number is currently 29. IANA =
assigns in-order. I happen to know that option number 32 is being =
squatted on. If IANA assigns number 32 to some other option, conflicts =
*will* arise. (There are several TCP options being developed in the IETF =
at the moment, so this is not a constructed argument.)

I know of about 5 or so TCP option numbers that are being squatted on at =
the moment (there are likely more). I've been in discussion with the =
folks who are squatting, and in all cases the story was either "we were =
going to ask for assignment but it got forgotten" or "oh, you mean =
unassigned doesn't mean it's free for the taking?"

Using a term other than "unassigned" might prevent some instances of the =
latter.

Lars



--Apple-Mail-1--797964971
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExODA3NDY1NVowIwYJKoZIhvcNAQkE
MRYEFAGLQ1v298z5jSNoXP2uXf2VX79/MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ADVcEv3B0vzaI2KOpqlvWcGNqtjt6aF1V75n12nZkCAFkLx4S0m9D6jzB5/8lkA1grL3D4AP1Cvd
zhbuWQyZsypvsJaihhs3MA/Dat1zhhgf7xw/itgQUFEWe8BH9JbWubgGcFCL3Xmag9P7hSh5Mjvm
85ZX3ZBA7iwSS4+sxTYM/KRnM5sVTAReJIXPcFz6Xy3WK2UY1ya8qBSHI9lKCOBQugpG7hCW3yFz
ZPXA4jqBB+GiMC2ffsj9nnni8XNDB7tYxDGfDaC9HPo2vhr63hnV/KjUFBkehrnSd8JS8Y/moNEz
pjlMBOhpQXM9jNh4MnSZkADHx/kWPARmExkPJfgAAAAAAAA=

--Apple-Mail-1--797964971--

From hallam@gmail.com  Tue Jan 18 05:49:19 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 E1ECC3A6FCB for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.46
X-Spam-Level: 
X-Spam-Status: No, score=-3.46 tagged_above=-999 required=5 tests=[AWL=0.138,  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 MYDLVcrWfLTw for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:49:18 -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 66CF63A6FB6 for <ietf@ietf.org>; Tue, 18 Jan 2011 05:49:18 -0800 (PST)
Received: by gxk28 with SMTP id 28so2590175gxk.31 for <ietf@ietf.org>; Tue, 18 Jan 2011 05:51: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=x2TKFej8+9bO3wNR1BImP3NZwGUcYMfyFbUnutwR+UE=; b=nwwf+n0Fbo/2WOpISIfoHzHVjjjzWL1E93/HSSRGPF4r0/wsVjBciN1YdwWqIXPp7c VYjnlB10gxHGM6Mpk0zL8vMkwd3Bu7gn/w56c8tYtENnCLew4E3cXEJODnncJS5brfT+ WCG8MuPnWEbuX986//lC8jn06SsiXezqtiAnE=
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=uIH3icJ3GPqs38NfVr1OD1DK7RtaW3dfeBkY2Zu29tyjA/49KmZ2WohTiTwAWyAUTa qvOVsgwEp1MByEUhY4rKPjUL2MNMXsKi3P8Ag6fPUIuNbGntcieuJsqxkHBNcjotUMq2 gFp6Uw7vZzIPGUQAdBn9KTIP6vQMnIaaOd53I=
MIME-Version: 1.0
Received: by 10.100.242.4 with SMTP id p4mr3462876anh.205.1295358715143; Tue, 18 Jan 2011 05:51:55 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Tue, 18 Jan 2011 05:51:55 -0800 (PST)
In-Reply-To: <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com> <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com>
Date: Tue, 18 Jan 2011 08:51:55 -0500
Message-ID: <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Lars Eggert <lars.eggert@nokia.com>
Content-Type: multipart/alternative; boundary=001636af027212a628049a1f34db
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 18 Jan 2011 13:49:20 -0000

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

On Tue, Jan 18, 2011 at 2:46 AM, Lars Eggert <lars.eggert@nokia.com> wrote:

> Hi,
>
> On 2011-1-17, at 1:23, Phillip Hallam-Baker wrote:
> > If people think that IANA is a tool they can use to impose their own
> > personal political agenda on the Internet, they are mistaken.
>
> that isn't the point of this thread.
>
> The point of IANA assignment is to avoid conflicting codepoint usage.
> Squatting on codepoints defeats this goal.
>

But it meets the goal of the people squatting. Is there any reason to think
that changing the name of the code points is going to make a difference?


I know of about 5 or so TCP option numbers that are being squatted on at the
> moment (there are likely more). I've been in discussion with the folks who
> are squatting, and in all cases the story was either "we were going to ask
> for assignment but it got forgotten" or "oh, you mean unassigned doesn't
> mean it's free for the taking?"
>

Those sound like excuses to me rather than reasons.

I am currently applying for a DNS RR code assignment. More than one person
involved suggested that we should just assign the RR code ourselves by fiat
because they didn't want to wait six weeks for a review.

My name is on the draft so we have applied for an assignment. But now that
six weeks have passed we have a major industry meeting next week that is to
discuss the proposal (amongst others) as part of a DNSSEC deployment effort
and there has been no response.


Using a term other than "unassigned" might prevent some instances of the
> latter.


I don't see how changing the name is going to affect behavior for the
positive here. If you do succeed in confusing people as to which numbers are
unassigned and which are not it is going to increase the risk of a
collision.


If five people are experimenting with TCP options and this is not causing
collisions, what is the problem?


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

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

<br><br><div class=3D"gmail_quote">On Tue, Jan 18, 2011 at 2:46 AM, Lars Eg=
gert <span dir=3D"ltr">&lt;<a href=3D"mailto:lars.eggert@nokia.com">lars.eg=
gert@nokia.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<div class=3D"im"><br>
On 2011-1-17, at 1:23, Phillip Hallam-Baker wrote:<br>
&gt; If people think that IANA is a tool they can use to impose their own<b=
r>
&gt; personal political agenda on the Internet, they are mistaken.<br>
<br>
</div>that isn&#39;t the point of this thread.<br>
<br>
The point of IANA assignment is to avoid conflicting codepoint usage. Squat=
ting on codepoints defeats this goal.<br>
</blockquote><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote=
">But it meets the goal of the people squatting. Is there any reason to thi=
nk that changing the name of the code points is going to make a difference?=
</div>
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex;">I know of about 5 or so TCP option numbers t=
hat are being squatted on at the moment (there are likely more). I&#39;ve b=
een in discussion with the folks who are squatting, and in all cases the st=
ory was either &quot;we were going to ask for assignment but it got forgott=
en&quot; or &quot;oh, you mean unassigned doesn&#39;t mean it&#39;s free fo=
r the taking?&quot;<br>
</blockquote><div><br></div><div>Those sound like excuses to me rather than=
 reasons.</div><div><br></div><div>I am currently applying for a DNS RR cod=
e assignment. More than one person involved suggested that we should just a=
ssign the RR code ourselves by fiat because they didn&#39;t want to wait si=
x weeks for a review.</div>
<div><br></div><div>My name is on the draft so we have applied for an assig=
nment. But now that six weeks have passed we have a major industry meeting =
next week that is to discuss the proposal (amongst others) as part of a DNS=
SEC deployment effort and there has been no response.</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Using a term other than &quot;unassigned&quot; might prevent some instances=
 of the latter.</blockquote><div><br></div><div>I don&#39;t see how changin=
g the name is going to affect behavior for the positive here. If you do suc=
ceed in confusing people as to which numbers are unassigned and which are n=
ot it is going to increase the risk of a collision.</div>
<div><br></div><div><br><meta charset=3D"utf-8"></div><div>If five people a=
re experimenting with TCP options and this is not causing collisions, what =
is the problem?</div><div><br></div><div><br></div></div>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
<br>

--001636af027212a628049a1f34db--

From spencer@wonderhamster.org  Tue Jan 18 05:56:17 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 9675A3A6E98 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.144
X-Spam-Level: 
X-Spam-Status: No, score=-102.144 tagged_above=-999 required=5 tests=[AWL=0.454, 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 Gj95-8SvokqX for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:56:16 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 3C12D3A6D3D for <ietf@ietf.org>; Tue, 18 Jan 2011 05:56:16 -0800 (PST)
Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MXane-1Pj7zK3Dp0-00WneS; Tue, 18 Jan 2011 08:58:41 -0500
Message-ID: <2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Phillip Hallam-Baker" <hallam@gmail.com>, "Lars Eggert" <lars.eggert@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp><06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com><AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com><27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com> <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
Date: Tue, 18 Jan 2011 07:58:25 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_1150_01CBB6E5.7C482520"
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:v8TnlAnjJL9PHMk/Ik3iJ8sho2SHqf0pUZDzUUgbwz3 AeDimZVo9nLSIj94otOfDDu9fvP1UuN3cKGzLm8RswB3l1UqAF 0zRnd2jKc1PkZ6b/WUJUZaOo5oGfxKskuR83g3jypRkv3Gskdb JBUcSIIIfiJ0XsTKvZNywBye3PxeFzjOojng1MMhbB99vk7rMb CzYfItvuJEsv7KuTkin5H3XKj2up/9oC7VFoIBjGpI=
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 18 Jan 2011 13:56:17 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_1150_01CBB6E5.7C482520
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Phillip,

Lars can speak for himself, but what I THOUGHT he was talking was =
changing the phrase "unassigned" to something like "reserved for future =
assignment".=20

That made sense to me...

Spencer
  ----- Original Message -----=20
  From: Phillip Hallam-Baker=20
  To: Lars Eggert=20
  Cc: Iljitsch van Beijnum ; paul.hoffman@vpnc.org ; ietf@ietf.org=20
  Sent: Tuesday, January 18, 2011 7:51 AM
  Subject: Re: Use of "unassigned" in IANA registries





  On Tue, Jan 18, 2011 at 2:46 AM, Lars Eggert <lars.eggert@nokia.com> =
wrote:

    Hi,


    On 2011-1-17, at 1:23, Phillip Hallam-Baker wrote:
    > If people think that IANA is a tool they can use to impose their =
own
    > personal political agenda on the Internet, they are mistaken.


    that isn't the point of this thread.

    The point of IANA assignment is to avoid conflicting codepoint =
usage. Squatting on codepoints defeats this goal.



  But it meets the goal of the people squatting. Is there any reason to =
think that changing the name of the code points is going to make a =
difference?




    I know of about 5 or so TCP option numbers that are being squatted =
on at the moment (there are likely more). I've been in discussion with =
the folks who are squatting, and in all cases the story was either "we =
were going to ask for assignment but it got forgotten" or "oh, you mean =
unassigned doesn't mean it's free for the taking?"



  Those sound like excuses to me rather than reasons.


  I am currently applying for a DNS RR code assignment. More than one =
person involved suggested that we should just assign the RR code =
ourselves by fiat because they didn't want to wait six weeks for a =
review.


  My name is on the draft so we have applied for an assignment. But now =
that six weeks have passed we have a major industry meeting next week =
that is to discuss the proposal (amongst others) as part of a DNSSEC =
deployment effort and there has been no response.




    Using a term other than "unassigned" might prevent some instances of =
the latter.


  I don't see how changing the name is going to affect behavior for the =
positive here. If you do succeed in confusing people as to which numbers =
are unassigned and which are not it is going to increase the risk of a =
collision.




  If five people are experimenting with TCP options and this is not =
causing collisions, what is the problem?




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




-------------------------------------------------------------------------=
-----


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

------=_NextPart_000_1150_01CBB6E5.7C482520
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18999">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Phillip,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Lars can speak for himself, but what I THOUGHT he =
was talking=20
was changing the phrase "unassigned" to something like "reserved for =
future=20
assignment". </FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>That made sense to me...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Spencer</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; =
PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: =
black"><B>From:</B>=20
  <A title=3Dhallam@gmail.com href=3D"mailto:hallam@gmail.com">Phillip=20
  Hallam-Baker</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dlars.eggert@nokia.com=20
  href=3D"mailto:lars.eggert@nokia.com">Lars Eggert</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A =
title=3Diljitsch@muada.com=20
  href=3D"mailto:iljitsch@muada.com">Iljitsch van Beijnum</A> ; <A=20
  title=3Dpaul.hoffman@vpnc.org=20
  href=3D"mailto:paul.hoffman@vpnc.org">paul.hoffman@vpnc.org</A> ; <A=20
  title=3Dietf@ietf.org href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, January 18, 2011 =
7:51=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: Use of =
"unassigned" in IANA=20
  registries</DIV>
  <DIV><BR></DIV><BR><BR>
  <DIV class=3Dgmail_quote>On Tue, Jan 18, 2011 at 2:46 AM, Lars Eggert =
<SPAN=20
  dir=3Dltr>&lt;<A=20
  =
href=3D"mailto:lars.eggert@nokia.com">lars.eggert@nokia.com</A>&gt;</SPAN=
>=20
  wrote:<BR>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; =
PADDING-LEFT: 1ex"=20
  class=3Dgmail_quote>Hi,<BR>
    <DIV class=3Dim><BR>On 2011-1-17, at 1:23, Phillip Hallam-Baker =
wrote:<BR>&gt;=20
    If people think that IANA is a tool they can use to impose their =
own<BR>&gt;=20
    personal political agenda on the Internet, they are=20
    mistaken.<BR><BR></DIV>that isn't the point of this =
thread.<BR><BR>The point=20
    of IANA assignment is to avoid conflicting codepoint usage. =
Squatting on=20
    codepoints defeats this goal.<BR></BLOCKQUOTE>
  <DIV class=3Dgmail_quote><BR></DIV>
  <DIV class=3Dgmail_quote>But it meets the goal of the people =
squatting. Is there=20
  any reason to think that changing the name of the code points is going =
to make=20
  a difference?</DIV>
  <DIV class=3Dgmail_quote><BR></DIV>
  <DIV class=3Dgmail_quote><BR></DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; =
PADDING-LEFT: 1ex"=20
  class=3Dgmail_quote>I know of about 5 or so TCP option numbers that =
are being=20
    squatted on at the moment (there are likely more). I've been in =
discussion=20
    with the folks who are squatting, and in all cases the story was =
either "we=20
    were going to ask for assignment but it got forgotten" or "oh, you =
mean=20
    unassigned doesn't mean it's free for the taking?"<BR></BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>Those sound like excuses to me rather than reasons.</DIV>
  <DIV><BR></DIV>
  <DIV>I am currently applying for a DNS RR code assignment. More than =
one=20
  person involved suggested that we should just assign the RR code =
ourselves by=20
  fiat because they didn't want to wait six weeks for a review.</DIV>
  <DIV><BR></DIV>
  <DIV>My name is on the draft so we have applied for an assignment. But =
now=20
  that six weeks have passed we have a major industry meeting next week =
that is=20
  to discuss the proposal (amongst others) as part of a DNSSEC =
deployment effort=20
  and there has been no response.</DIV>
  <DIV><BR></DIV>
  <DIV><BR></DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; =
PADDING-LEFT: 1ex"=20
  class=3Dgmail_quote>Using a term other than "unassigned" might prevent =
some=20
    instances of the latter.</BLOCKQUOTE>
  <DIV><BR></DIV>
  <DIV>I don't see how changing the name is going to affect behavior for =
the=20
  positive here. If you do succeed in confusing people as to which =
numbers are=20
  unassigned and which are not it is going to increase the risk of a=20
  collision.</DIV>
  <DIV><BR></DIV>
  <DIV><BR></DIV>
  <DIV>If five people are experimenting with TCP options and this is not =
causing=20
  collisions, what is the problem?</DIV>
  <DIV><BR></DIV>
  <DIV><BR></DIV></DIV>-- <BR>Website: <A=20
  href=3D"http://hallambaker.com/">http://hallambaker.com/</A><BR><BR>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Ietf mailing =

  =
list<BR>Ietf@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ietf<BR></=
BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_1150_01CBB6E5.7C482520--


From lars.eggert@nokia.com  Tue Jan 18 05:59:46 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 DDB133A6F0F for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.383
X-Spam-Level: 
X-Spam-Status: No, score=-104.383 tagged_above=-999 required=5 tests=[AWL=-0.784, 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 TaYCtQ600n5c for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 05:59:46 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 07C453A6F2C for <ietf@ietf.org>; Tue, 18 Jan 2011 05:59:45 -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 p0IE2I6o020635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 16:02:19 +0200
Subject: Re: Use of "unassigned" in IANA registries
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-14--775449584; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com>
Date: Tue, 18 Jan 2011 16:02:10 +0200
Message-Id: <9A63E4EE-0847-43A6-BBAC-5D47E63038B4@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com> <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com> <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@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); Tue, 18 Jan 2011 16:02:15 +0200 (EET)
X-Nokia-AV: Clean
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 18 Jan 2011 13:59:47 -0000

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

Hi,

On 2011-1-18, at 15:51, Phillip Hallam-Baker wrote:
> >Using a term other than "unassigned" might prevent some instances of =
the latter.
>=20
> I don't see how changing the name is going to affect behavior for the =
positive here. If you do succeed in confusing people as to which numbers =
are unassigned and which are not it is going to increase the risk of a =
collision.

huh? The purpose here is to make it *clearer* that assignment is needed.

> If five people are experimenting with TCP options and this is not =
causing collisions, what is the problem?

Have you read my original email? It *is* going to cause collisions.

Lars=

--Apple-Mail-14--775449584
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExODE0MDIxMFowIwYJKoZIhvcNAQkE
MRYEFIzYpeLsljS3z62dh9/ceAvfydsiMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AL90OyIm9e05/5t9JtAAf97GOpqFV2cMX17b/LB3+Vs1lkntn+recfDewzBb4laG2ku66NOw2aj8
E17+/V/iVnkDocBRCfeel4jctO9Eyrjb8/vtCvGEsNArIgPlCjH74VvaS8zKD3a+7YhpghNKPyH9
uo1gZA8kHFMBqpggpUBOsgb8xF6wHVF/o81BMspZYaErhV1f96IZyd4bDQtTOnISaCsacM1/K79X
W6ws65QJhkxWicVFTu5oFSkKmn9FR0d92EAoisgb5s3bHbuwHnkLytwZYhJINFel3qzb/nEJrcTd
hyhjm3yrHONo6OfeaaWWBNXCMDtgVy27EiFkzJQAAAAAAAA=

--Apple-Mail-14--775449584--

From lars.eggert@nokia.com  Tue Jan 18 06:00:04 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 67AF428C105 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 06:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.368
X-Spam-Level: 
X-Spam-Status: No, score=-104.368 tagged_above=-999 required=5 tests=[AWL=-0.769, 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 FLebaWThs3gA for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 06:00:01 -0800 (PST)
Received: from mgw-da01.nokia.com (mgw-da01.ext.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id AC3C028C0F5 for <ietf@ietf.org>; Tue, 18 Jan 2011 06:00:01 -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 p0IE2YLk020860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 16:02:35 +0200
Subject: Re: Use of "unassigned" in IANA registries
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-15--775427985; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com>
Date: Tue, 18 Jan 2011 16:02:31 +0200
Message-Id: <8FC44D17-C2DD-499C-99C1-B9294A1B9DD8@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp><06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com><AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com><27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com> <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com> <2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Tue, 18 Jan 2011 16:02:31 +0200 (EET)
X-Nokia-AV: Clean
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, Phillip Hallam-Baker <hallam@gmail.com>, paul.hoffman@vpnc.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, 18 Jan 2011 14:00:04 -0000

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

On 2011-1-18, at 15:58, Spencer Dawkins wrote:
> Lars can speak for himself, but what I THOUGHT he was talking was =
changing the phrase "unassigned" to something like "reserved for future =
assignment".=20

Exactly.

Lars


>=20
> That made sense to me...
>=20
> Spencer
>  ----- Original Message -----=20
>  From: Phillip Hallam-Baker=20
>  To: Lars Eggert=20
>  Cc: Iljitsch van Beijnum ; paul.hoffman@vpnc.org ; ietf@ietf.org=20
>  Sent: Tuesday, January 18, 2011 7:51 AM
>  Subject: Re: Use of "unassigned" in IANA registries
>=20
>=20
>=20
>=20
>=20
>  On Tue, Jan 18, 2011 at 2:46 AM, Lars Eggert <lars.eggert@nokia.com> =
wrote:
>=20
>    Hi,
>=20
>=20
>    On 2011-1-17, at 1:23, Phillip Hallam-Baker wrote:
>> If people think that IANA is a tool they can use to impose their own
>> personal political agenda on the Internet, they are mistaken.
>=20
>=20
>    that isn't the point of this thread.
>=20
>    The point of IANA assignment is to avoid conflicting codepoint =
usage. Squatting on codepoints defeats this goal.
>=20
>=20
>=20
>  But it meets the goal of the people squatting. Is there any reason to =
think that changing the name of the code points is going to make a =
difference?
>=20
>=20
>=20
>=20
>    I know of about 5 or so TCP option numbers that are being squatted =
on at the moment (there are likely more). I've been in discussion with =
the folks who are squatting, and in all cases the story was either "we =
were going to ask for assignment but it got forgotten" or "oh, you mean =
unassigned doesn't mean it's free for the taking?"
>=20
>=20
>=20
>  Those sound like excuses to me rather than reasons.
>=20
>=20
>  I am currently applying for a DNS RR code assignment. More than one =
person involved suggested that we should just assign the RR code =
ourselves by fiat because they didn't want to wait six weeks for a =
review.
>=20
>=20
>  My name is on the draft so we have applied for an assignment. But now =
that six weeks have passed we have a major industry meeting next week =
that is to discuss the proposal (amongst others) as part of a DNSSEC =
deployment effort and there has been no response.
>=20
>=20
>=20
>=20
>    Using a term other than "unassigned" might prevent some instances =
of the latter.
>=20
>=20
>  I don't see how changing the name is going to affect behavior for the =
positive here. If you do succeed in confusing people as to which numbers =
are unassigned and which are not it is going to increase the risk of a =
collision.
>=20
>=20
>=20
>=20
>  If five people are experimenting with TCP options and this is not =
causing collisions, what is the problem?
>=20
>=20
>=20
>=20
>  --=20
>  Website: http://hallambaker.com/
>=20
>=20
>=20
>=20
> =
--------------------------------------------------------------------------=
----
>=20
>=20
>  _______________________________________________
>  Ietf mailing list
>  Ietf@ietf.org
>  https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-15--775427985
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExODE0MDIzMlowIwYJKoZIhvcNAQkE
MRYEFPLL/Joa3aAk/9ZKLvgrUtkU94SLMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ACuTPxQmE9KBK64YG0QG7ctdkEGIiMgmz+XiYwSybLxghEcWH4KdH6yBI2AX5B8Awu9/XfWWX440
V1EK2gHErbHbO7/ABCfTxARnBibjwM583Xk9vy0yEwWl9Y+IBZatt2qrKaNaSkafrdsZjP59sT3a
MrPppMuVR5JqUDso5V8dFsEUXuRP0s5zW0k5T2HD7JZhi6y2gdTb7HVzep4h6uy6wzpIGjZmIfPO
TX1g3+1642OGghXSxa2TXVAg4HxHWt7hT+UnU7kGM/CLxZVoAGjwU/J/FixtmWUK2Ngh+V06mYiW
E3bmEuGVTECiuaY+yzjSio1F/xGs8Z5Sn8wmdzcAAAAAAAA=

--Apple-Mail-15--775427985--

From hallam@gmail.com  Tue Jan 18 06:29:41 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 10DD23A7001 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 06:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.46
X-Spam-Level: 
X-Spam-Status: No, score=-3.46 tagged_above=-999 required=5 tests=[AWL=0.138,  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 vIO144ZIqkul for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 06:29:39 -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 6C6133A6F33 for <ietf@ietf.org>; Tue, 18 Jan 2011 06:29:39 -0800 (PST)
Received: by gyd12 with SMTP id 12so2594772gyd.31 for <ietf@ietf.org>; Tue, 18 Jan 2011 06:32:16 -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=x/0uwg0rZi6nryENQCJ4XAfRjkcKC+Pwm07F+PxBPSw=; b=sNoq2FZZw8K1NGUnSJRW8gDLip3OAQKr/NoHO2+PqE0qU1IAn6+jCAYosvGn3ZDdv5 9i5JJMXZsQzRAS61Z+O0cX/JBhxUHiujpjJ/j6Ltpz5bx/skTnMt8obBS7rboMBrFyFE 7YOtpony5UIjH1hqUWfenekGanA3RVgkQDZKw=
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=H9NYz5bAvcjgmUZgEjp2Gom3cJQsIG68YIE8/gr3hIXzMLw9wXWH1+2m2Jj1P6GA4b lwcp6Mvvmj0U+RYHMNCqPDmxWPtwrCIrzvYHi0YiOuwfK7he8zmj9a5mgRdYdieZzmce bGKZjQ2B170c7UysTtCJTFFeaArIr6bm7ohYA=
MIME-Version: 1.0
Received: by 10.100.174.5 with SMTP id w5mr3569440ane.171.1295361136385; Tue, 18 Jan 2011 06:32:16 -0800 (PST)
Received: by 10.100.31.8 with HTTP; Tue, 18 Jan 2011 06:32:16 -0800 (PST)
In-Reply-To: <2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com> <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com> <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com> <2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com>
Date: Tue, 18 Jan 2011 09:32:16 -0500
Message-ID: <AANLkTin9d1qyCHBzmfgJiscijDKqMvvCw4gaO8G+Kwg4@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Spencer Dawkins <spencer@wonderhamster.org>
Content-Type: multipart/alternative; boundary=0016e64405a063deac049a1fc4ad
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 18 Jan 2011 14:29:41 -0000

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

On Tue, Jan 18, 2011 at 8:58 AM, Spencer Dawkins
<spencer@wonderhamster.org>wrote:

>  Phillip,
>
> Lars can speak for himself, but what I THOUGHT he was talking was changing
> the phrase "unassigned" to something like "reserved for future assignment".
>
> That made sense to me...
>

That would work IF the reason this is happening is that people don't
understand that unassigned means reserved for future assignment.

But I rather suspect that the reason that this is happening is that people
know full well that there is a process and choose to ignore it because they
either can't be bothered to put up with the hassle or don't think that the
application will be accepted.


At the moment we do in fact have code points that are reserved as distinct
from being 'unassigned' and this is done because it is known that use of
that code point will cause a collision. Often because the code point was
hijacked.

For example the DNS code points for Apple's Bonjour protocol are reserved
rather than assigned.

SRV code points are an even bigger mess because there isn't even a proper
registry to enter them in.


I think it is rather more likely that the root cause here goes back to the
fact that the old three track standard process has broken down and the
criteria for acceptance as a PROPOSED standard are now essentially those for
DRAFT.

One of the reasons for having a low bar for initial drafts was that they
were necessary to get the required code point assignments.


Lars writes:

>> If five people are experimenting with TCP options and this is not causing
collisions, what is the problem?

>Have you read my original email? It *is* going to cause collisions.

This type of behavior certainly could cause collisions. But that seems to be
a risk that the people who engage in that behavior prefer to take rather
than apply for an assignment.


What I am saying here is that people need to be very clear as to what the
objectives they are trying to achieve here and make sure that they do not
overstep the mark.

If the only priority is to prevent collisions, then it is really easy to
avoid problems, just open the registry first come first served.

For many lower level registries that is not an option because there is a
real risk of code point exhaustion. That is particularly true with some of
the deep down one byte codes. But that is relatively manageable.

What creates real problems and puts those objectives at risk is when control
of the registry is seen as a means of ensuring that nobody can deploy
proprietary code or encumbered technology or something that someone feels
should really be built on the basis of their little pet project so that it
gets deployed and used.


There are plenty of cliques who try to engage in that particular type of
behavior and far too few people who have the courage to stand up to them and
call them out when they do so.

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

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

<blockquote class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0 40px;=
 border: none; padding: 0px;"><br></blockquote><br><div class=3D"gmail_quot=
e">On Tue, Jan 18, 2011 at 8:58 AM, Spencer Dawkins <span dir=3D"ltr">&lt;<=
a href=3D"mailto:spencer@wonderhamster.org">spencer@wonderhamster.org</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">





<div bgcolor=3D"#ffffff">
<div><font size=3D"2">Phillip,</font></div>
<div><font size=3D"2"></font>=A0</div>
<div><font size=3D"2">Lars can speak for himself, but what I THOUGHT he was=
 talking=20
was changing the phrase &quot;unassigned&quot; to something like &quot;rese=
rved for future=20
assignment&quot;. </font></div>
<div><font size=3D"2"></font>=A0</div>
<div><font size=3D"2">That made sense to me...</font></div></div></blockquo=
te><div><br></div><div>That would work IF the reason this is happening is t=
hat people don&#39;t understand that unassigned means reserved for future a=
ssignment.</div>
<div><br></div><div>But I rather suspect that the reason that this is happe=
ning is that people know full well that there is a process and choose to ig=
nore it because they either can&#39;t be bothered to put up with the hassle=
 or don&#39;t think that the application will be accepted.</div>
<div><br></div><div><br></div><div>At the moment we do in fact have code po=
ints that are reserved as distinct from being &#39;unassigned&#39; and this=
 is done because it is known that use of that code point will cause a colli=
sion. Often because the code point was hijacked.=A0</div>
<div><br></div><div>For example the DNS code points for Apple&#39;s Bonjour=
 protocol are reserved rather than assigned.</div><div><br></div><div>SRV c=
ode points are an even bigger mess because there isn&#39;t even a proper re=
gistry to enter them in.=A0</div>
<div><br></div><div><br></div><div>I think it is rather more likely that th=
e root cause here goes back to the fact that the old three track standard p=
rocess has broken down and the criteria for acceptance as a PROPOSED standa=
rd are now essentially those for DRAFT.</div>
<div><br></div><div>One of the reasons for having a low bar for initial dra=
fts was that they were necessary to get the required code point assignments=
.=A0</div><div><br></div></div><div><br></div><div>Lars writes:</div><div>
<br></div><div><span class=3D"Apple-style-span" style=3D"font-family: arial=
, sans-serif; border-collapse: collapse; color: rgb(51, 51, 51); "><div cla=
ss=3D"im" style=3D"color: rgb(80, 0, 80); ">&gt;&gt; If five people are exp=
erimenting with TCP options and this is not causing collisions, what is the=
 problem?<br>
<br></div>&gt;Have you read my original email? It *is* going to cause colli=
sions.</span></div><div><br></div><div>This type of behavior certainly coul=
d cause collisions. But that seems to be a risk that the people who engage =
in that behavior prefer to take rather than apply for an assignment.=A0</di=
v>
<div><br></div><div><br></div><div>What I am saying here is that people nee=
d to be very clear as to what the objectives they are trying to achieve her=
e and make sure that they do not overstep the mark.</div><div><br></div>
<div>If the only priority is to prevent collisions, then it is really easy =
to avoid problems, just open the registry first come first served.</div><di=
v><br></div><div>For many lower level registries that is not an option beca=
use there is a real risk of code point exhaustion. That is particularly tru=
e with some of the deep down one byte codes. But that is relatively managea=
ble.</div>
<div><br></div><div>What creates real problems and puts those objectives at=
 risk is when control of the registry is seen as a means of ensuring that n=
obody can deploy proprietary code or encumbered technology or something tha=
t someone feels should really be built on the basis of their little pet pro=
ject so that it gets deployed and used.</div>
<div><br></div><div><br></div><div>There are plenty of cliques who try to e=
ngage in that particular type of behavior and far too few people who have t=
he courage to stand up to them and call them out when they do so.</div>
<br>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br><br>

--0016e64405a063deac049a1fc4ad--

From lars.eggert@nokia.com  Tue Jan 18 06:41:49 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 1E03828C0EB for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 06:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.355
X-Spam-Level: 
X-Spam-Status: No, score=-104.355 tagged_above=-999 required=5 tests=[AWL=-0.756, 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 lhY+sqh4mltK for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 06:41:48 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 3FE5F28C117 for <ietf@ietf.org>; Tue, 18 Jan 2011 06:41:48 -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 p0IEiL8i003909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 16:44:22 +0200
Subject: Re: Use of "unassigned" in IANA registries
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-17--772926297; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <AANLkTin9d1qyCHBzmfgJiscijDKqMvvCw4gaO8G+Kwg4@mail.gmail.com>
Date: Tue, 18 Jan 2011 16:44:13 +0200
Message-Id: <3A80901E-5D2D-4EAC-9D3E-809C0CD299FE@nokia.com>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp> <06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com> <AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com> <27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com> <AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com> <2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com> <AANLkTin9d1qyCHBzmfgJiscijDKqMvvCw4gaO8G+Kwg4@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@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); Tue, 18 Jan 2011 16:44:18 +0200 (EET)
X-Nokia-AV: Clean
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 18 Jan 2011 14:41:49 -0000

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

Hi,

On 2011-1-18, at 16:32, Phillip Hallam-Baker wrote:
> That would work IF the reason this is happening is that people don't
> understand that unassigned means reserved for future assignment.

that *is* the reason, for at least those cases that I have been involved =
in.

> But I rather suspect that the reason that this is happening is that =
people
> know full well that there is a process and choose to ignore it because =
they
> either can't be bothered to put up with the hassle or don't think that =
the
> application will be accepted.

Suspect all you want, but it doesn't match my experience.

> SRV code points are an even bigger mess because there isn't even a =
proper
> registry to enter them in.

We're very close to fixing this: =
http://tools.ietf.org/html/draft-ietf-tsvwg-iana-ports

> I think it is rather more likely that the root cause here goes back to =
the
> fact that the old three track standard process has broken down and the
> criteria for acceptance as a PROPOSED standard are now essentially =
those for
> DRAFT.

RFC2026 has almost nothing to do with IANA allocation procedures. (The =
only relation is that some registries require a Standards Action, but =
even then it is irrelevant which level of the standards track the RFC is =
on. And yes, it's somewhat more difficult to have a Standards Action =
occur than passing the bar for the other RFC5226 policies, but then =
again, few registries actually need a Standards Action.)

Lars


--Apple-Mail-17--772926297
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExODE0NDQxM1owIwYJKoZIhvcNAQkE
MRYEFIzwHfviAqaHJ/pCciz4IHCy9b63MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AFVbMEmwARY4+s3t/w64djvKLMSIAJWWtcFWiLM+WgqlAKKrvAEtuQJvu0dafIi++EfWE4D31mKJ
Y0HFIDt7jW8HuJehYfk3FEwAtW3KqRc60g6Huuw8MWm+seGX5E9GsTGMtpJB/LXV4kMvo+JL2ajZ
TCjRg0rEshTAsBJO0EI4fZpSmnlslK6+7A6RTcUyA56JykoknDavNaaUlUqc5363gaW7TkqCLc23
wq6p+EZt/nukNxIkI6CDwdin2stFjMxWZ4ho8QHmAcvudFD9EKukzjXM2g/V3kWAQ1GkPBQAwrhj
i4sK7A18aJZZ83UWHf5TY0ulMVXMcav0WqufQN4AAAAAAAA=

--Apple-Mail-17--772926297--

From erosen@cisco.com  Tue Jan 18 07:12:55 2011
Return-Path: <erosen@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 3958E3A7013 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 07:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.53
X-Spam-Level: 
X-Spam-Status: No, score=-10.53 tagged_above=-999 required=5 tests=[AWL=0.069,  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 SQ6nrxDMp1qZ for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 07:12:54 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 4F4093A7010 for <ietf@ietf.org>; Tue, 18 Jan 2011 07:12:54 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 18 Jan 2011 15:15:31 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0IFFVLE019256; Tue, 18 Jan 2011 15:15:31 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id p0IFFTDT020472;  Tue, 18 Jan 2011 10:15:30 -0500
To: Lars Eggert <lars.eggert@nokia.com>
Subject: Re: Use of "unassigned" in IANA registries
In-reply-to: Your message of Tue, 18 Jan 2011 16:44:13 +0200. <3A80901E-5D2D-4EAC-9D3E-809C0CD299FE@nokia.com>
Date: Tue, 18 Jan 2011 10:15:29 -0500
Message-ID: <20471.1295363729@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, Phillip Hallam-Baker <hallam@gmail.com>, paul.hoffman@vpnc.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@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, 18 Jan 2011 15:12:55 -0000

Phillip> But I rather suspect that the reason that this is happening is that
Phillip> people know full well that there is a process and choose to ignore
Phillip> it because they either can't be bothered to put up with the hassle
Phillip> or don't think that the application will be accepted.

Lars> Suspect all you want, but it doesn't match my experience.

Phillip's suspicion certainly matches my experience over the past 15 years,
and I've even done my own share of codepoint squatting.  He is also correct
to state that many folks try to use control over the codepoint space as part
of their competitive marketing strategy.  The only way to avoid collisions
due to "squatting" is to adopt a policy that all codepoint fields be large
enough so that a significant number of codepoints are available for FCFS
allocations.



From xavier.marjou@gmail.com  Tue Jan 18 08:07:06 2011
Return-Path: <xavier.marjou@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 AD51528C166 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 08:07:06 -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 d5DLtIEuEuTP for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 08:07:05 -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 789F628C0F3 for <ietf@ietf.org>; Tue, 18 Jan 2011 08:07:05 -0800 (PST)
Received: by qyj19 with SMTP id 19so6657049qyj.10 for <ietf@ietf.org>; Tue, 18 Jan 2011 08:09:42 -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:content-type; bh=K2BoRvEuUX0XOg0Ij1gEMPlURQj0Tlhm0e3Mg55MqNw=; b=ZlxT3MlD4RHssIG5DWLOCyc3mIzEK8lzO/3HrL41qE1lWxnwZQrBREOZb5s9etqLUn ROm+GRsby9aORlcbuUcWQ2bSAqQsRF4pNOC6U2u7nStoPHlIGe1kSeUjz0Y8X1ry2eMQ 7StnFzbuSby8lSRQERqzExoA14iVEhOBMDE4Y=
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 :content-type; b=pcKQDHkC/Gt0QiF8tgY11F+fZHryOT65xQRCALvAfI1NnQ99RAQZuP0qpqkPpc06/y sy7lC+ZykuTxMCxOXeLDb6SWAuDbBSmyq4NnCm4DiWepQkgRbNR9OI5Xse12reyDVQgs z9vmotR2b8crXMJVUAXZO+sPc4TFC43cKufDY=
MIME-Version: 1.0
Received: by 10.229.94.143 with SMTP id z15mr4834647qcm.282.1295366982257; Tue, 18 Jan 2011 08:09:42 -0800 (PST)
Received: by 10.220.195.202 with HTTP; Tue, 18 Jan 2011 08:09:42 -0800 (PST)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22092C4DF1@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B22092C4DF1@DC-US1MBEX4.global.avaya.com>
Date: Tue, 18 Jan 2011 17:09:42 +0100
Message-ID: <AANLkTintfCWksjUVr-xMOiNN5LvLA2CYF=WaeGdv3d_c@mail.gmail.com>
Subject: Re: Is the xml2rfc mailing list working?
From: Xavier Marjou <xavier.marjou@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016e6408980d4cba1049a212084
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, 18 Jan 2011 16:07:06 -0000

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

Hi,

I experimented the same problem this morning. I filled the
http://lists.xml.resource.org/mailman/listinfo/xml2rfc form twice but I did
not receive any requesting confirmation mail in my mailbox.

Cheers,
Xavier

On Fri, Jan 14, 2011 at 10:22 PM, Worley, Dale R (Dale)
<dworley@avaya.com>wrote:

> I've attempted to subscribe to the xml2rfc mailing list several times in
> the last month, but never gotten a response.  Is it still working?
>
> Dale
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Hi,<div><br></div><div>I experimented the same problem this morning. I fill=
ed the=A0<a href=3D"http://lists.xml.resource.org/mailman/listinfo/xml2rfc"=
>http://lists.xml.resource.org/mailman/listinfo/xml2rfc</a>=A0form twice bu=
t I did not receive any requesting confirmation mail in my mailbox.<div>
<br></div><div>Cheers,</div><div>Xavier<br><br><div class=3D"gmail_quote">O=
n Fri, Jan 14, 2011 at 10:22 PM, Worley, Dale R (Dale) <span dir=3D"ltr">&l=
t;<a href=3D"mailto:dworley@avaya.com">dworley@avaya.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">I&#39;ve attempted to subscribe to the xml2=
rfc mailing list several times in the last month, but never gotten a respon=
se. =A0Is it still working?<br>

<br>
Dale<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></div></div>

--0016e6408980d4cba1049a212084--

From lars.eggert@nokia.com  Tue Jan 18 08:23:15 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 5493F3A7021 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 08:23:15 -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=-0.704, 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 xByKOlVWuu5G for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 08:23:14 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 7C4F43A6BD7 for <ietf@ietf.org>; Tue, 18 Jan 2011 08:23:14 -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 p0IGPku0015281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 18:25:48 +0200
Subject: Re: Use of "unassigned" in IANA registries
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-26--766835556; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <20471.1295363729@erosen-linux>
Date: Tue, 18 Jan 2011 18:25:44 +0200
Message-Id: <2E7AF194-C041-4239-924C-EA542CBA3F5A@nokia.com>
References: <20471.1295363729@erosen-linux>
To: <erosen@cisco.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); Tue, 18 Jan 2011 18:25:44 +0200 (EET)
X-Nokia-AV: Clean
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, Phillip Hallam-Baker <hallam@gmail.com>, paul.hoffman@vpnc.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, 18 Jan 2011 16:23:15 -0000

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

On 2011-1-18, at 17:15, Eric Rosen wrote:
> The only way to avoid collisions
> due to "squatting" is to adopt a policy that all codepoint fields be =
large
> enough so that a significant number of codepoints are available for =
FCFS
> allocations.

That's certainly a suggestion we should follow for new registries, but =
unfortunately doesn't help us with existing ones.

Lars=

--Apple-Mail-26--766835556
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDExODE2MjU0NFowIwYJKoZIhvcNAQkE
MRYEFE4PAfp+16vxwEjRTA+Vi0qc0Id2MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AEzumVy7DHxOmT3Zc1QK3cYcB7fqVsSqe0wYlgTfpEShgQD2y0RSfSxavBLF9zBAMzucgzub4a4F
t9IC1SA44cFcleEDJeBYD9bMIC1+w5438ATqt8W5fSjrg//ZIOi6/pSGVhueepZEkv4Kbun+rWG0
7FfTkbiD1rAkPWEvARBr+xDO7Gtz5iq2DxyvYYN3GqZCDJYdhRs5JUAp0jPR2Z1V7vwpYbz68tVA
1+OH6MKhA1G6CvexKA/fcuhHqXyGpXveojmG7M1GEeThiAbBIf0P5010jV1Rb3boBdjGTDK1MARB
pjN3h1O9SBSAg9JvfhnZWylICOydOxiPWa2ifvwAAAAAAAA=

--Apple-Mail-26--766835556--

From michal@krsek.cz  Tue Jan 18 08:39:13 2011
Return-Path: <michal@krsek.cz>
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 6726D28C0F1 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 08:39:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.627
X-Spam-Level: *
X-Spam-Status: No, score=1.627 tagged_above=-999 required=5 tests=[AWL=0.277,  BAYES_50=0.001, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
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 5p-69C2dYqj0 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 08:39:12 -0800 (PST)
Received: from io.pinknet.cz (io.pinknet.cz [217.31.57.96]) by core3.amsl.com (Postfix) with ESMTP id 9C92628C0D8 for <ietf@ietf.org>; Tue, 18 Jan 2011 08:39:11 -0800 (PST)
Received: from [195.113.228.228] (michal-xp.w2lan.cesnet.cz [195.113.228.228]) by io.pinknet.cz (Postfix) with ESMTP id 759EB23B01F for <ietf@ietf.org>; Tue, 18 Jan 2011 17:46:14 +0100 (CET)
Message-ID: <4D35C2CB.4090104@krsek.cz>
Date: Tue, 18 Jan 2011 17:41:47 +0100
From: Michal Krsek <michal@krsek.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Cell data connectivity in CZ
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 8bit
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, 18 Jan 2011 16:39:13 -0000

Dear all,
please note we have three relevant cell operators in Prague.

O2 - http://www.o2.cz/osobni/en/mobile_internet/
(closest shop @ "Sokolovská 17, Praha" 
http://maps.google.com/maps?f=q&source=s_q&hl=cs&q=o2&sll=50.090418,14.440632&sspn=0.004374,0.005295&ie=UTF8&t=h&rq=1&ev=p&split=1&radius=0.14&hq=o2&hnear=&ll=50.090968,14.440198&spn=0.004374,0.005295&z=18 
)

T-Mobile - 
http://www.t-mobile.cz/web/en/internet/webnwalk-tariffs-and-add-ons
same locality as O2

Vodafone - https://www.vodafone.cz/live_en/index.htm
(closest schop @ námìstí Republiky 1078/1, Praha)

I think most of them cover area neighboring Prague Hilton and Prague 
city center by UMTS network in 2.1 Ghz band together with 1800/900 Mhz 
GPRS/EDGE. All of the operators have USB modem for purchase but I'm 
afraid drivers are Windows only.

I'm visiting shop selling O2 and T-Mobile in next few weeks to make sure 
they can support non-czech customers with non-windows based devices :-) 
Vodafone is located in a big shopping center crowded by tourists.

I can do one more favor for community. O2 has an promo proposal for 
prepaid SIM card for CZK 95 (slightly lower value than 5 newly printed 
USD). This card covers one week (seven days) for free Internet and I 
regullary use them as "use and discard". I can buy a bunch of these 
cards and make them available on basis of demand from the community for 
not-for profit. So if you like to use this sim card, just drop me 
PERSONAL e-mail message (do not reply to the list).

                         Regards
                             Michal Krsek

P.S: With those with iPad devices please note Czech mobile operators do 
NOT provide micro SIM cards.

P.P.S: I'm resending this message later to 80attendees list.

From marc.blanchet@viagenie.ca  Sat Jan 15 11:35:58 2011
Return-Path: <marc.blanchet@viagenie.ca>
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 D241F3A6E29 for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 11:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, 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 yu1yqZuD33ws for <ietf@core3.amsl.com>; Sat, 15 Jan 2011 11:35:57 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id B48373A6E27 for <ietf@ietf.org>; Sat, 15 Jan 2011 11:35:57 -0800 (PST)
Received: from mbl.lan (unknown [IPv6:2607:f2c0:f00e:6100:5ab0:35ff:fe6a:294a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 283DB20D25 for <ietf@ietf.org>; Sat, 15 Jan 2011 14:38:23 -0500 (EST)
Message-ID: <4D31F7AE.4050603@viagenie.ca>
Date: Sat, 15 Jan 2011 14:38:22 -0500
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: ietf@ietf.org
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>
In-Reply-To: <20110113235830.13395.80271.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 18 Jan 2011 09:00:31 -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, 15 Jan 2011 19:35:59 -0000

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

Marc.

Le 11-01-13 18:58, The IESG a écrit :
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Scalable Operation of Address Translators with Per-Interface Bindings'
>    <draft-arkko-dual-stack-extra-lite-03.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-02-10. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-arkko-dual-stack-extra-lite/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-arkko-dual-stack-extra-lite/
>
>
> 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


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN Implementation: http://postellation.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From jpv@cisco.com  Sun Jan 16 08:05:12 2011
Return-Path: <jpv@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 9D6493A6BFC; Sun, 16 Jan 2011 08:05:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.42
X-Spam-Level: 
X-Spam-Status: No, score=-110.42 tagged_above=-999 required=5 tests=[AWL=0.178, 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 ve6GhWamNuSa; Sun, 16 Jan 2011 08:05:10 -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 19BB43A6BCD; Sun, 16 Jan 2011 08:05:08 -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: Ak0GAHKmMk2Q/khNgWdsb2JhbACCPZoaiBMVAQEWIiSkRZgLhVAEix+DKg
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 16 Jan 2011 16:07:39 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p0GG7dh5005127; Sun, 16 Jan 2011 16:07:39 GMT
Received: from xfe-ams-102.cisco.com ([144.254.231.94]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 16 Jan 2011 17:07:39 +0100
Received: from ams-jvasseur-8711.cisco.com ([10.55.201.130]) by xfe-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 16 Jan 2011 17:07:37 +0100
Subject: Re: Gen-ART LC review of draft-ietf-roll-routing-metrics-14
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-170--940722355
From: JP Vasseur <jpv@cisco.com>
In-Reply-To: <4d32eda3.1d4de50a.4290.ffffaf99@mx.google.com>
Date: Sun, 16 Jan 2011 17:07:37 +0100
Message-Id: <A5438C36-A93F-4D87-BA11-58DDB8A80ECD@cisco.com>
References: <4d0f9da0.2308e30a.48c5.ffffae42@mx.google.com> <515C4A60-2334-4F40-8AE6-813042109560@cisco.com> <4d32eda3.1d4de50a.4290.ffffaf99@mx.google.com>
To: rontlv <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-OriginalArrivalTime: 16 Jan 2011 16:07:38.0025 (UTC) FILETIME=[7EAE9190:01CBB597]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.500.1024-17898.000
X-TM-AS-Result: No--39.476100-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-Mailman-Approved-At: Tue, 18 Jan 2011 09:00:31 -0800
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>, draft-ietf-roll-routing-metrics.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, 16 Jan 2011 16:05:12 -0000

--Apple-Mail-170--940722355
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Thanks Roni.

On Jan 16, 2011, at 2:07 PM, rontlv wrote:

> Hi JP,
> Thanks, I am OK with all your responses
> Roni
> =20
> From: JP Vasseur [mailto:jpv@cisco.com]=20
> Sent: Friday, January 14, 2011 8:44 AM
> To: Roni Even
> Cc: gen-art@ietf.org; =
draft-ietf-roll-routing-metrics.all@tools.ietf.org; IETF-Discussion list
> Subject: Re: Gen-ART LC review of draft-ietf-roll-routing-metrics-14
> =20
> Hi Roni,
> =20
> Thanks for your thorough review - please see in line JP>
> =20
> On Dec 20, 2010, at 7:14 PM, Roni Even wrote:
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> =20
> Please resolve these comments along with any other Last Call comments =
you may receive.
> =20
> Document: draft-ietf-roll-routing-metrics-14
> Reviewer: Roni Even
> Review Date:2010=9612=9620
> IETF LC End Date: 2011=961=965
> IESG Telechat date:
> =20
> Summary: This draft is almost ready for publication as an Standard =
track RFC.
> =20
> Major issues:
> No Major issues
> =20
> Minor issues:
> =20
> 1.  In section 2.1 after figure 1 you specify the different fields. =
Please specify the size in bits of the flags field the A-field and the =
prec field.
> =20
> JP> Done.
>=20
>=20
> 2.  In section 2.1 in example 1 how is it known that all nodes MUST be =
main powered.
> =20
> JP> In this example, we first explain how the headers flags are =
determined. To help clarify I modified the text:
> =20
> OLD:
> =20
> As far as the constraint is concerned, if the constraint signalled in =
the DIO message is not satisfied, the advertising node is just not =
selected as a parent by the node that processes the DIO message.
> =20
> NEW:
> =20
> As far as the constraint is concerned, the object body will carry a =
node energy constraint object defined in Section 3.1 indicating that =
nodes must be mains-powered: if the constraint signalled in the DIO =
message is not satisfied, the advertising node is just not selected as a =
parent by the node that processes the DIO message.
>=20
>=20
> Do you need to provide a value to prec field?
> =20
> JP> As indicated earlier, the Prec field is only useful when a DAG =
Metric Container contains several Routing Metric objects. In this =
example, there is just one metric (the node energy is a constraint).
>=20
>=20
> 3.  In section 3.1 and throughout the document when you define the =
different object you have =93recommended value=3Dxx=94. I think that =
since this draft defines the table and create the initial table in the =
IANA consideration section these are the actual values. So maybe say =
that these are the actual values as specified in section 6 (6.1)
> =20
> JP> We added "recommended values" until IANA confirms.
>=20
>=20
> 4.  In section 3.1 the flag field =96 how many bits, specify.
> =20
> JP> Done.
>=20
>=20
> 5.  In section 3.2 figure 4 shows a flag field, how many bits, what is =
the value.
> =20
> JP> Done.
>=20
>=20
> 6.  In section 6 according to rfc5226 =93IETF consensus=94 is now =
=93IETF review=94.
> =20
> JP> Fixed.
>=20
>=20
> 7.  In section 6.1 you should say that the table has the initial =
values and add which numbers are available for allocation.
> =20
> JP> Done.
>=20
>=20
> 8.  In section 6.2 what values are available for allocation.  Also say =
that currently the table is empty.
> =20
> JP> Done.
>=20
>=20
> 9.  In section 6.2 is there a reason to create an empty table. Why not =
do it when there is a request to define a TLV
> =20
> JP> Just to have the registry already in place. There is more than =
likely be TLVs defined in a very near future. This also allows to make =
sure that all TLVs have the same structure.
> =20
> 10.In section 6.3, are there more values allowed, can they be =
allocated. If not why have it managed by IANA.
> =20
> JP> The A field is a 3-bit field and there are currently 4 defined =
values.
>=20
>=20
> 11.After the table in section in section 6.3 there is a request to =
create another table. Maybe it should be in a separate section.
> =20
> JP> This is just because we put all registries belonging to the =
Routing Metric/Constraint Common Header in the same section.
>=20
>=20
> 12.In section 6.3 =93New bit numbers may be allocated=94, how many =
bits are available.
> =20
> JP> The text was misplaced, thanks.
>=20
>=20
> 13.The same paragraph in section 6.3 also talks about the registration =
policy, is it different from the one that is common in section 6, why =
specify it again. Also look at comment 6
> =20
> JP> This was a duplicate. Fixed.
>=20
>=20
> 14.Comment 12 and 13 are also true for section 6.4 and 6.5.
> =20
> =20
> JP> Fixed too.
>=20
>=20
> =20
> =20
> Nits/editorial comments:
> =20
> 1.  In section first paragraph =93object=94 should be =93object=94
> 2.  In section 4.3.2 first paragraph =93wich=94 should be =93which=94
> =20
> =20
> JP> Fixed.
> =20
> Many Thanks. These changes are all incorporated in revision 15.
> =20
> JP.
>=20
>=20
> =20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> =20
>=20
>=20
> __________ Information from ESET NOD32 Antivirus, version of virus =
signature database 5785 (20110113) __________
>=20
> The message was checked by ESET NOD32 Antivirus.
>=20
> http://www.eset.com
>=20
>=20
> __________ Information from ESET NOD32 Antivirus, version of virus =
signature database 5791 (20110116) __________
>=20
> The message was checked by ESET NOD32 Antivirus.
>=20
> http://www.eset.com


--Apple-Mail-170--940722355
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><base href=3D"x-msg://673/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; ">Thanks Roni.<div><br><div><div>On Jan 16, 2011, at =
2:07 PM, rontlv wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0cm; margin-right: 0cm; =
margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: =
'Times New Roman', serif; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; color: rgb(31, 73, 125); ">Hi =
JP,<o:p></o:p></span></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">Thanks, I =
am OK with all your responses<o:p></o:p></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">Roni<o:p></o:p></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"border-top-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-right-style: solid; =
border-right-color: blue; border-right-width: 1.5pt; padding-top: 0cm; =
padding-right: 0cm; padding-bottom: 0cm; padding-left: 4pt; "><div><div =
style=3D"border-right-style: none; border-bottom-style: none; =
border-left-style: none; border-width: initial; border-color: initial; =
border-top-style: solid; border-top-color: rgb(181, 196, 223); =
border-top-width: 1pt; padding-top: 3pt; padding-right: 0cm; =
padding-bottom: 0cm; padding-left: 0cm; "><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">From:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; "><span class=3D"Apple-converted-space">&nbsp;</span>JP =
Vasseur [mailto:jpv@cisco.com]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Friday, January 14, 2011 =
8:44 AM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Roni =
Even<br><b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:gen-art@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">gen-art@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-roll-routing-metrics.all@tools.ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">draft-ietf-roll-routing-metrics.all@tools.ietf.org</a>; =
IETF-Discussion list<br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: Gen-ART LC review of =
draft-ietf-roll-routing-metrics-14<o:p></o:p></span></div></div></div><div=
 style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Hi =
Roni,<o:p></o:p></div><div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Thanks for your thorough =
review - please see in line JP&gt;<o:p></o:p></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div><div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">On Dec 20, 2010, at 7:14 =
PM, Roni Even wrote:<o:p></o:p></div></div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Consolas; ">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" =
style=3D"color: blue; text-decoration: underline; =
">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o=
:p></span></div></div><div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">Please resolve =
these comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">Document: =
draft-ietf-roll-routing-metrics-14<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 10.5pt; font-family: Consolas; =
">Reviewer: Roni Even<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 10.5pt; font-family: Consolas; =
">Review Date:2010=9612=9620<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 10.5pt; font-family: Consolas; ">IETF =
LC End Date: 2011=961=965<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 10.5pt; font-family: Consolas; ">IESG =
Telechat date:<o:p></o:p></span></div></div><div><div style=3D"margin-top:=
 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">Summary: This draft =
is almost ready for publication as an Standard track =
RFC.<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">Major =
issues:<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Consolas; ">No Major =
issues<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">Minor =
issues:<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div style=3D"margin-left: 36pt; =
"><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">1.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 2.1 =
after figure 1 you specify the different fields. Please specify the size =
in bits of the flags field the A-field and the prec =
field.<o:p></o:p></span></div></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Done.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">2.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 2.1 in =
example 1 how is it known that all nodes MUST be main =
powered.<o:p></o:p></span></div></div></div><div><div style=3D"margin-top:=
 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt;&nbsp;In this =
example, we first explain how the headers flags are determined. To help =
clarify I modified the text:<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
">OLD:<o:p></o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">As far as the constraint =
is concerned, if the constraint signalled in the DIO message is not =
satisfied, the advertising node is just not selected as a parent by the =
node that processes the DIO message.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
">NEW:<o:p></o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">As far as the constraint =
is concerned, the object body will carry a node energy constraint object =
defined in Section 3.1 indicating that nodes must be mains-powered: if =
the constraint signalled in the DIO message is not satisfied, the =
advertising node is just not selected as a parent by the node that =
processes the DIO message.<o:p></o:p></div></div><div style=3D"margin-top:=
 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">Do you need to provide a value to prec =
field?<o:p></o:p></span></div></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; As indicated =
earlier, the Prec field is only useful when a DAG Metric Container =
contains several Routing Metric objects. In this example, there is just =
one metric (the node energy is a constraint).<o:p></o:p></div></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; =
"><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">3.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 3.1 and =
throughout the document when you define the different object you have =
=93recommended value=3Dxx=94. I think that since this draft defines the =
table and create the initial table in the IANA consideration section =
these are the actual values. So maybe say that these are the actual =
values as specified in section 6 =
(6.1)<o:p></o:p></span></div></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; We added =
"recommended values" until IANA confirms.<o:p></o:p></div></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; =
"><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">4.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 3.1 the =
flag field =96 how many bits, =
specify.<o:p></o:p></span></div></div></div><div><div style=3D"margin-top:=
 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Done.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">5.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 3.2 =
figure 4 shows a flag field, how many bits, what is the =
value.<o:p></o:p></span></div></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Done.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">6.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 6 =
according to rfc5226 =93IETF consensus=94 is now =93IETF =
review=94.<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Fixed.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">7.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 6.1 you =
should say that the table has the initial values and add which numbers =
are available for =
allocation.<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Done.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">8.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 6.2 what =
values are available for allocation.&nbsp; Also say that currently the =
table is empty.<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Done.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">9.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 6.2 is =
there a reason to create an empty table. Why not do it when there is a =
request to define a TLV<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; Just to =
have the registry already in place. There is more than likely be TLVs =
defined in a very near future. This also allows to make sure that all =
TLVs have the same structure.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><blockquote style=3D"margin-top: =
5pt; margin-bottom: 5pt; "><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">10.In section 6.3, are there more values =
allowed, can they be allocated. If not why have it managed by =
IANA.<o:p></o:p></span></div></div></div></blockquote><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; The A =
field is a 3-bit field and there are currently 4 defined =
values.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">11.After the table in section in section 6.3 =
there is a request to create another table. Maybe it should be in a =
separate section.<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; This is =
just because we put all registries belonging to the&nbsp;Routing =
Metric/Constraint Common Header in the same =
section.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">12.In section 6.3 =93New bit numbers may be =
allocated=94, how many bits are =
available.<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; The =
text was misplaced, thanks.<o:p></o:p></div></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; =
"><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">13.The same paragraph in section 6.3 also talks =
about the registration policy, is it different from the one that is =
common in section 6, why specify it again. Also look at comment =
6<o:p></o:p></span></div></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; This was a =
duplicate. Fixed.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 36pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">14.Comment 12 and 13 are also true for section =
6.4 and 6.5.<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div></div><div><div style=3D"margin-top:=
 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">JP&gt; Fixed =
too.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div style=3D"margin-left: 18pt; "><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><span style=3D"font-size: 10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">Nits/editorial =
comments:<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Consolas; =
">&nbsp;<o:p></o:p></span></div></div><div style=3D"margin-left: 36pt; =
"><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">1.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section first =
paragraph =93object=94 should be =
=93object=94<o:p></o:p></span></div></div><div style=3D"margin-left: =
36pt; "><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; text-indent: -18pt; "><span style=3D"font-size: 10.5pt; =
font-family: Consolas; ">2.</span><span style=3D"font-size: 7pt; =
">&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 10.5pt; font-family: Consolas; ">In section 4.3.2 =
first paragraph =93wich=94 should be =
=93which=94<o:p></o:p></span></div></div><div style=3D"margin-left: =
36pt; "><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 10.5pt; font-family: =
Consolas; ">&nbsp;<o:p></o:p></span></div></div></div><div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: =
0cm; margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; =
font-size: 12pt; font-family: 'Times New Roman', serif; ">JP&gt; =
Fixed.<o:p></o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Many Thanks. These =
changes are all incorporated in revision =
15.<o:p></o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
">JP.<o:p></o:p></div></div><div style=3D"margin-top: 0cm; margin-right: =
0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><br><br><o:p></o:p></div><div><div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; =
">&nbsp;<o:p></o:p></span></div></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-bottom: 0.0001pt; margin-left: 0cm; font-size: =
12pt; font-family: 'Times New Roman', serif; =
">_______________________________________________<br>Ietf mailing =
list<br><a href=3D"mailto:Ietf@ietf.org" style=3D"color: blue; =
text-decoration: underline; ">Ietf@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/ietf</a><o:p></o:p></div></div></d=
iv><div style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: =
0.0001pt; margin-left: 0cm; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-bottom: 0.0001pt; =
margin-left: 0cm; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><br><br>__________ Information from ESET NOD32 Antivirus, =
version of virus signature database 5785 (20110113) =
__________<br><br>The message was checked by ESET NOD32 =
Antivirus.<br><br><a href=3D"http://www.eset.com" style=3D"color: blue; =
text-decoration: underline; =
">http://www.eset.com</a><o:p></o:p></div></div></div><br><br>__________ =
Information from ESET NOD32 Antivirus, version of virus signature =
database 5791 (20110116) __________<br><br>The message was checked by =
ESET NOD32 Antivirus.<br><br><a href=3D"http://www.eset.com" =
style=3D"color: blue; text-decoration: underline; =
">http://www.eset.com</a><br></div></span></blockquote></div><br></div></b=
ody></html>=

--Apple-Mail-170--940722355--

From mrex@sap.com  Tue Jan 18 09:06: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 7CB463A7046 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 09:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.155
X-Spam-Level: 
X-Spam-Status: No, score=-10.155 tagged_above=-999 required=5 tests=[AWL=0.094, 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 iGFQYEiUO2JZ for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 09:06:32 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by core3.amsl.com (Postfix) with ESMTP id 6D0BB3A703F for <ietf@ietf.org>; Tue, 18 Jan 2011 09:06:31 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p0IH8sR2010692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 18 Jan 2011 18:08:54 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201101181708.p0IH8rOQ020964@fs4113.wdf.sap.corp>
Subject: Re: Use of "unassigned" in IANA registries
To: lars.eggert@nokia.com (Lars Eggert)
Date: Tue, 18 Jan 2011 18:08:53 +0100 (MET)
In-Reply-To: <2E7AF194-C041-4239-924C-EA542CBA3F5A@nokia.com> from "Lars Eggert" at Jan 18, 11 06:25:44 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: erosen@cisco.com, iljitsch@muada.com, hallam@gmail.com, paul.hoffman@vpnc.org, 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: Tue, 18 Jan 2011 17:06:33 -0000

Lars Eggert wrote:
> 
> On 2011-1-18, at 17:15, Eric Rosen wrote:
> > The only way to avoid collisions
> > due to "squatting" is to adopt a policy that all codepoint fields
> > be large enough so that a significant number of codepoints are
> > available for FCFS allocations.
> 
> That's certainly a suggestion we should follow for new registries, but
> unfortunately doesn't help us with existing ones.


A possibility for existing registries would be to allow for optimistic
reservation.  e.g. allow WG conensus to request a reservation of a code
point for registries that require standards action, which would cause
IANA to change a code point from "unassigned" to "reserved" (or "tentative")
for a certain amount of time.

It depends on the priorities: is it better to have a clean and strictly
sequential official assignments of code points (with collisions created
by those who do not want to wait), or is it better to prevent
collisions at the risk of somewhat scattered final assignments appearing
in the registry, and potential collisions with abandoned proposals when
the pool of available code points is getting exhausted.

-Martin

From daedulus@btconnect.com  Tue Jan 18 09:38:30 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 F05073A7036 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 09:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 VRnDuH+NnYFg for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 09:38:29 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id CE75A3A6F6C for <ietf@ietf.org>; Tue, 18 Jan 2011 09:38:26 -0800 (PST)
Received: from host86-134-205-117.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.117]) by c2beaomr07.btconnect.com with SMTP id BLC29353; Tue, 18 Jan 2011 17:40:41 +0000 (GMT)
Message-ID: <00b101cbb72d$f6093140$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Lars Eggert" <lars.eggert@nokia.com>, "Spencer Dawkins" <spencer@wonderhamster.org>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp><06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com><AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com><27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com><AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com><2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com> <8FC44D17-C2DD-499C-99C1-B9294A1B9DD8@nokia.com>
Subject: Re: Use of "unassigned" in IANA registries
Date: Tue, 18 Jan 2011 17:37:02 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4D35D096.01FB, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0208.4D35D0A1.01EB,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: Iljitsch van Beijnum <iljitsch@muada.com>, Phillip Hallam-Baker <hallam@gmail.com>, paul.hoffman@vpnc.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, 18 Jan 2011 17:38:30 -0000

----- Original Message -----
From: "Lars Eggert" <lars.eggert@nokia.com>
To: "Spencer Dawkins" <spencer@wonderhamster.org>
Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>; "Phillip Hallam-Baker"
<hallam@gmail.com>; <paul.hoffman@vpnc.org>; <ietf@ietf.org>
Sent: Tuesday, January 18, 2011 3:02 PM

On 2011-1-18, at 15:58, Spencer Dawkins wrote:
> Lars can speak for himself, but what I THOUGHT he was talking was changing the
phrase "unassigned" to something like "reserved for future assignment".

Exactly.

<tp>
Which, presumably, would be in a BCP updating RFC5226 which only allows for

  Private Use:
  Experimental:
  Reserved:  Not to be assigned.
  Unassigned: Unused and available for assignment via documented  procedures.

Tom Petch

</tp>

Lars


From bmanning@isi.edu  Tue Jan 18 12:01:13 2011
Return-Path: <bmanning@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 B2CFD28C108 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 12:01:13 -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 6grx+KvSM3bV for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 12:01:12 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 0A68C3A7070 for <ietf@ietf.org>; Tue, 18 Jan 2011 12:01:01 -0800 (PST)
Received: from mew.isi.edu (mew.isi.edu [128.9.160.177]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0IK3EtQ002690 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 18 Jan 2011 12:03:14 -0800 (PST)
From: bill manning <bmanning@isi.edu>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/mixed; boundary=Apple-Mail-4--753789534
Date: Tue, 18 Jan 2011 12:03:10 -0800
Subject: this seems to have become broken some time back
To: IETF discussion list <ietf@ietf.org>
Message-Id: <E48F738E-F0EB-4A91-BAB1-E01F2A0CF9F9@isi.edu>
X-Mailer: Apple Mail (2.1082)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: 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: Tue, 18 Jan 2011 20:01:13 -0000

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

and I guess I am the only one who might still use it - but regardless, =
if its broken, it should be fixed


to wit:


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-(ofthehour).txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Apple-Mail-4--753789534
Content-Disposition: attachment;
	filename="Mail Attachment"
Content-Type: application/octet-stream;
	name="Mail Attachment"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain<BR>Content-ID: &lt;2011-01-18052724.I-D@ietf.org&gt;<BR><BR>
--Apple-Mail-4--753789534
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org


....  seems that the mail attachment (MIME) is no longer a copy of the =
draft in question, its a dummy text block.

We are sad.

--bill=

--Apple-Mail-4--753789534--

From ebw@abenaki.wabanaki.net  Tue Jan 18 12:45:55 2011
Return-Path: <ebw@abenaki.wabanaki.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 6CA3328C12F; Tue, 18 Jan 2011 12:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.341
X-Spam-Level: 
X-Spam-Status: No, score=-2.341 tagged_above=-999 required=5 tests=[AWL=-0.342, BAYES_00=-2.599, J_CHICKENPOX_64=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 nnZlFv9Ig-BP; Tue, 18 Jan 2011 12:45:54 -0800 (PST)
Received: from abenaki.wabanaki.net (abenaki.wabanaki.net [65.99.1.133]) by core3.amsl.com (Postfix) with ESMTP id 53C3F28C112; Tue, 18 Jan 2011 12:45:54 -0800 (PST)
Received: from limpet.local (cpe-67-255-5-237.twcny.res.rr.com [67.255.5.237]) by abenaki.wabanaki.net (8.14.4/8.14.4) with ESMTP id p0IJAO2k042014; Tue, 18 Jan 2011 14:10:24 -0500 (EST) (envelope-from ebw@abenaki.wabanaki.net)
Message-ID: <4D35FC94.5050904@abenaki.wabanaki.net>
Date: Tue, 18 Jan 2011 15:48:20 -0500
From: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
Organization: wampumpeag
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: dnsop@ietf.org, ietf@ietf.org
Subject: Re: [DNSOP] Fwd: Last Call:	<draft-cheshire-dnsext-special-names-01.txt> (Special-Use	Domain Names) to Proposed Standard
References: <20110117230048.26192.84056.idtracker@localhost> <2A149A97-3B0A-49AA-88CA-9741F88B9274@gmail.com>
In-Reply-To: <2A149A97-3B0A-49AA-88CA-9741F88B9274@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 18 Jan 2011 20:45:55 -0000

There are label segments that have semantics.

The "--" violation, prepended by something, "^xn", where "^" indicates 
a label boundary, to indicate a (the current) "IDN" processing.

Bytes within a label with values in excess of 127.

Off hand I can't think of anything else (that is intentional). Along 
the accidental sort-of-intended mumble access of forensic engineering 
are terminating (TLD) labels that brain-dead dead-ware interprets (if 
anyone living were to ask it) character representations of digit 
sequences as v4 addresses that currently has the pants scared off of 
ICANN and some folks from this side of the policy|tech divide.

Everything else seems to just be intentional carve outs of string 
spaces, suited, if there is a purpose, to the (defunct) User Services 
Area Directorate and its inform-the-community mission that "example" 
is not a means to repeat for the bazillionth time the flagship brand 
of Verisign.

.local has sufficient meaning to care about.

John Levin's draft covers some "don't pretend you're ARPA" ground, 
which is a useful restriction on what appears in the IANA root (and 
any other used by every user in China) and in SLDs, assuming that a 
means other than persuasion is available to inform both 
auctions-are-good gTLD operators and ICANN-is-irrelevant ccTLD 
operators that some restrictions are beneficial.

The chief defect of Stewart's draft is that it makes an analogy to the 
semantics of addressing, and postulates a pseudo-technical set of 
implementation responsibilities, and fails to mention ICANN, which has 
some coordination mission.

What isn't a layer 9 is worth documenting. What is at layer 9 should 
be documented as being at layer 9.

Eric

From jabley@hopcount.ca  Tue Jan 18 18:09:38 2011
Return-Path: <jabley@hopcount.ca>
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 E55A03A70AB for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 18:09:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, 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 RXxeUkWfA0+3 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 18:09:38 -0800 (PST)
Received: from monster.hopcount.ca (monster.hopcount.ca [216.235.14.38]) by core3.amsl.com (Postfix) with ESMTP id DB54B3A6DA7 for <ietf@ietf.org>; Tue, 18 Jan 2011 18:09:37 -0800 (PST)
Received: from [199.212.90.28] (helo=dh28.r1.owls.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1PfNb4-000Ajg-ON; Wed, 19 Jan 2011 02:16:32 +0000
Subject: Re: this seems to have become broken some time back
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <E48F738E-F0EB-4A91-BAB1-E01F2A0CF9F9@isi.edu>
Date: Tue, 18 Jan 2011 21:12:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5444AF4B-7A0A-4DE7-9F06-67535B1F5ECE@hopcount.ca>
References: <E48F738E-F0EB-4A91-BAB1-E01F2A0CF9F9@isi.edu>
To: bill manning <bmanning@isi.edu>
X-Mailer: Apple Mail (2.1082)
X-SA-Exim-Connect-IP: 199.212.90.28
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
Cc: bill manning <bmanning@sfc.keio.ac.jp>, 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, 19 Jan 2011 02:09:39 -0000

On 2011-01-18, at 15:03, bill manning wrote:

> and I guess I am the only one who might still use it - but regardless, =
if its broken, it should ....  seems that the mail attachment (MIME) is =
no longer a copy of the draft in question, its a dummy text block.

I don't think it was ever a copy of the draft in question; it has been =
an RFC1873-compliant Message/External-Body section as long as I have =
been watching. To draw from another random example that came through =
recently on i-d-announce:

> Content-Type: Message/External-body;
> 	name=3D"draft-ietf-idr-bgp-identifier-13.txt"; =
site=3D"ftp.ietf.org";
> 	access-type=3D"anon-ftp"; directory=3D"internet-drafts"

I've never used a mail client that knows what to do with that, though.


Joe


From hallam@gmail.com  Tue Jan 18 20:07:34 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 7AC1828C126 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 20:07:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.465
X-Spam-Level: 
X-Spam-Status: No, score=-3.465 tagged_above=-999 required=5 tests=[AWL=0.133,  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 0a3vsnZK4gLr for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 20:07:33 -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 45C5128C120 for <ietf@ietf.org>; Tue, 18 Jan 2011 20:07:33 -0800 (PST)
Received: by gyd12 with SMTP id 12so121090gyd.31 for <ietf@ietf.org>; Tue, 18 Jan 2011 20:10:12 -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=IVW1B3G7NFprBSaf+2eyRD/jVGyQMJxcGdf9ZPZAmzo=; b=EXX7dMkJyC15tuygKYRhw5w0WT1vvylQzlAO/gcVvyfOWPAkZqiVsIyzagh6DJmB0E X53k9uDbBM2q53hEU+i9tyzVytA7iatUL2D00spKV7TjPYLuRI3OXioVj5S4Tq7QNnJK UWfrvZgu3X4oNHGH8Flchv9V+sqOsHQIVqDhk=
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=tS8P03+DoUMRmqjy6GY4I2DFXk6xJOCGVGmbJBX5RG9vWW4rSsheDZ0kYflncLp2pn AQwOtATtZgYGc8sFiD2NnX273TXgBMqi5qkGaAd0bfJsgXSjLLS0oQbxZc2/49aY8DT4 +TIo5exJmE1Cz+WvrgL37QWfnSx9FMgrgvPfQ=
MIME-Version: 1.0
Received: by 10.100.4.11 with SMTP id 11mr151684and.52.1295410211100; Tue, 18 Jan 2011 20:10:11 -0800 (PST)
Received: by 10.100.201.18 with HTTP; Tue, 18 Jan 2011 20:10:10 -0800 (PST)
In-Reply-To: <20471.1295363729@erosen-linux>
References: <3A80901E-5D2D-4EAC-9D3E-809C0CD299FE@nokia.com> <20471.1295363729@erosen-linux>
Date: Tue, 18 Jan 2011 23:10:10 -0500
Message-ID: <AANLkTi=Th=_1U-dNLg8uuuY6dLtiHSdJnpGMG8PT4=oR@mail.gmail.com>
Subject: Re: Use of "unassigned" in IANA registries
From: Phillip Hallam-Baker <hallam@gmail.com>
To: erosen@cisco.com
Content-Type: multipart/alternative; boundary=0016e646526c789794049a2b31d5
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, paul.hoffman@vpnc.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, 19 Jan 2011 04:07:34 -0000

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

On Tue, Jan 18, 2011 at 10:15 AM, Eric Rosen <erosen@cisco.com> wrote:

>
> Phillip> But I rather suspect that the reason that this is happening is
> that
> Phillip> people know full well that there is a process and choose to ignore
> Phillip> it because they either can't be bothered to put up with the hassle
> Phillip> or don't think that the application will be accepted.
>
> Lars> Suspect all you want, but it doesn't match my experience.
>
> Phillip's suspicion certainly matches my experience over the past 15 years,
> and I've even done my own share of codepoint squatting.  He is also correct
> to state that many folks try to use control over the codepoint space as
> part
> of their competitive marketing strategy.  The only way to avoid collisions
> due to "squatting" is to adopt a policy that all codepoint fields be large
> enough so that a significant number of codepoints are available for FCFS
> allocations.
>


One rather critical consideration here is that the lack of control provides
the IETF with some rather important protection against this type of attack
and is one of the reasons that the loose organizational structures are
relatively stable.

If the registry was a control point there would be far more people
attempting to capture it.





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

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

<br><br><div class=3D"gmail_quote">On Tue, Jan 18, 2011 at 10:15 AM, Eric R=
osen <span dir=3D"ltr">&lt;<a href=3D"mailto:erosen@cisco.com">erosen@cisco=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Phillip&gt; But I rather suspect that the reason that this is happening is =
that<br>
Phillip&gt; people know full well that there is a process and choose to ign=
ore<br>
Phillip&gt; it because they either can&#39;t be bothered to put up with the=
 hassle<br>
Phillip&gt; or don&#39;t think that the application will be accepted.<br>
<br>
Lars&gt; Suspect all you want, but it doesn&#39;t match my experience.<br>
<br>
Phillip&#39;s suspicion certainly matches my experience over the past 15 ye=
ars,<br>
and I&#39;ve even done my own share of codepoint squatting. =A0He is also c=
orrect<br>
to state that many folks try to use control over the codepoint space as par=
t<br>
of their competitive marketing strategy. =A0The only way to avoid collision=
s<br>
due to &quot;squatting&quot; is to adopt a policy that all codepoint fields=
 be large<br>
enough so that a significant number of codepoints are available for FCFS<br=
>
allocations.<br></blockquote><div><br></div><div><br></div><div>One rather =
critical consideration here is that the lack of control provides the IETF w=
ith some rather important protection against this type of attack and is one=
 of the reasons that the loose organizational structures are relatively sta=
ble.</div>
</div><div><br></div><div>If the registry was a control point there would b=
e far more people attempting to capture it.=A0</div><div><br></div><div><br=
></div><div><br></div><div><br></div><br>-- <br>Website: <a href=3D"http://=
hallambaker.com/">http://hallambaker.com/</a><br>
<br>

--0016e646526c789794049a2b31d5--

From ned+ietf@mauve.mrochek.com  Tue Jan 18 20:34:45 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 232D83A70C9 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 20:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxq5mKWTMg46 for <ietf@core3.amsl.com>; Tue, 18 Jan 2011 20:34:43 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 8FDD63A6F6B for <ietf@ietf.org>; Tue, 18 Jan 2011 20:34:43 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NWS5YPY0RK00I20G@mauve.mrochek.com> for ietf@ietf.org; Tue, 18 Jan 2011 20:37:21 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NWRL7QI6DS007CHU@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 18 Jan 2011 20:37:17 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NWS5YOMEMA007CHU@mauve.mrochek.com>
Date: Tue, 18 Jan 2011 20:23:22 -0800 (PST)
Subject: Re: this seems to have become broken some time back
In-reply-to: "Your message dated Tue, 18 Jan 2011 21:12:11 -0500" <5444AF4B-7A0A-4DE7-9F06-67535B1F5ECE@hopcount.ca>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <E48F738E-F0EB-4A91-BAB1-E01F2A0CF9F9@isi.edu> <5444AF4B-7A0A-4DE7-9F06-67535B1F5ECE@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1295408802; i=@mrochek.com; bh=vfAe0HG0RJI4Nlabm7tAVe5JZbRw8LeahrRdagCCG+k=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=TJeH7YkyKYGIL3xp6aJLDw9i5queKsIqmPnXDIyLDClaW4Eh/RPC3jZASm7O+t0/a BonOWL41hIeuVgjpMBq131Rn/u8KszLnBbX07kSvB0/9tt+xADr0nmP9M/n+nHKVJV gGijXQr1Cj3DLvqKWbYEPx8XDw4rckw1lMVwCeOM=
Cc: bill manning <bmanning@sfc.keio.ac.jp>, IETF discussion list <ietf@ietf.org>, bill manning <bmanning@isi.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, 19 Jan 2011 04:34:45 -0000

> On 2011-01-18, at 15:03, bill manning wrote:

> > and I guess I am the only one who might still use it - but regardless, if its broken, it should ....  seems that the mail attachment (MIME) is no longer a copy of the draft in question, its a dummy text block.

> I don't think it was ever a copy of the draft in question; it has been an
> RFC1873-compliant Message/External-Body section as long as I have been
> watching. To draw from another random example that came through recently on
> i-d-announce:

> > Content-Type: Message/External-body;
> > 	name="draft-ietf-idr-bgp-identifier-13.txt"; site="ftp.ietf.org";
> > 	access-type="anon-ftp"; directory="internet-drafts"

That's an anon-ftp access type, which is described in RFC 2046 section
5.2.3.3. RFC 1873 defines the content-id access-type.

> I've never used a mail client that knows what to do with that, though.

The client I'm using right now (which I coauthored) is one of the very few with
support for external body dereferencing. It's too bad really; it's a very
useful feature, especially if the client does a good job of merging the
external reference into the message.

				Ned

From evnikita2@gmail.com  Wed Jan 19 01:11:12 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 A59873A70C7 for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 01:11:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.993
X-Spam-Level: 
X-Spam-Status: No, score=-3.993 tagged_above=-999 required=5 tests=[AWL=-0.394, 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 yDKJswxY0uJC for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 01:11:07 -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 18B813A70DE for <ietf@ietf.org>; Wed, 19 Jan 2011 01:11:02 -0800 (PST)
Received: by gyd12 with SMTP id 12so188109gyd.31 for <ietf@ietf.org>; Wed, 19 Jan 2011 01:13:41 -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=cKIJZM3JENYVNoFtgd3ssCQ09d8U07PkjpYidjVtHvI=; b=gcWyG/SglPMKgcIHue31tYNwxjZGDRPxVsWEiuEi16Nd+Pe0UAIuBkSfmEkS8aQBMx OjbYEzvlKE/iKEZxysAMJxhtPI5ftwZA569Mot/iNhVRlbt2gC0KDqBIwrQsUph/sDcC vbUhKfgbm6tdplCWmq0NCQPkxdn8Idr0ZYNgs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=efBD9RAT5otsTa8ybukpyzg1EA4r/hqmK5nwB6S3SdLlRYBxiw7QSVm9x8dXFf4XDt Zab2OTHNcbrkmQZul8/yaPfGEvq2VM8JrcNqLmJ3iIoSik0dqPI1PWKj7KAh0AV1p1lZ 2nhM2jXGdgw3rr92HJPl3AuD4Qo65eKtmyAI0=
MIME-Version: 1.0
Received: by 10.150.251.13 with SMTP id y13mr539883ybh.383.1295428421143; Wed, 19 Jan 2011 01:13:41 -0800 (PST)
Received: by 10.150.53.6 with HTTP; Wed, 19 Jan 2011 01:13:40 -0800 (PST)
Date: Wed, 19 Jan 2011 11:13:40 +0200
Message-ID: <AANLkTikm284rViBOE4W4B_thyLqoUxcJUHR7yCmCr=EX@mail.gmail.com>
Subject: Re: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: The IETF <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: Wed, 19 Jan 2011 09:11:12 -0000

Hello all,

I am writing to comment draft-cheshire-dnsext-special-names-01, that
is currently in Last Call.

I've noticed that there is no clear definition of the created IANA
regsitry, as defined by RFC 5226.  Among other, there is no clear
definition of registry format and initial values.  I'd like to propose
you to take RFC 5797 as a base for registry desription.  That IANA
considerations section present in the current version is unsuitable
for Standards Track doc., IMO.

Moreover, as a minor note, there are no all abbreviations explained
once they appear in title, abstract and main text.

So I'd like the authors to correct this upon the end of LC.

All the best,
Mykyta

2011/1/18, The IESG <iesg-secretary@ietf.org>:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Special-Use Domain Names'
>   <draft-cheshire-dnsext-special-names-01.txt> as a Proposed Standard
>
>    Abstract
>
>    This document describes what it means to say that a DNS name is
>    reserved for special use, when reserving such a name is appropriate,
>    and the procedure for doing so.
>
> 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-14. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-cheshire-dnsext-special-names/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-cheshire-dnsext-special-names/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>

From daedulus@btconnect.com  Wed Jan 19 04:15:46 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 93BE43A7084 for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 04:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id au3QGUsUT1Bn for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 04:15:45 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by core3.amsl.com (Postfix) with ESMTP id 61AC13A6FCD for <ietf@ietf.org>; Wed, 19 Jan 2011 04:15:44 -0800 (PST)
Received: from host86-134-205-117.range86-134.btcentralplus.com (HELO pc6) ([86.134.205.117]) by c2beaomr09.btconnect.com with SMTP id BLC62446; Wed, 19 Jan 2011 12:18:18 +0000 (GMT)
Message-ID: <003401cbb7ca$13d082e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "t.petch" <daedulus@btconnect.com>, "Lars Eggert" <lars.eggert@nokia.com>,  "Spencer Dawkins" <spencer@wonderhamster.org>
References: <201101142206.p0EM6XNB027935@fs4113.wdf.sap.corp><06456B13-F9E5-4530-B7E8-7CF7F41000E0@muada.com><AANLkTiksCOABzGAVqrHQzpbyROhMPVR65zsuGVe=Q6Wg@mail.gmail.com><27DB0613-457D-4B99-89B4-D13DC2D7232E@nokia.com><AANLkTinHxBS7h-Y+=9fAoJgR=Az3jqd6c_bD05+K5_Lt@mail.gmail.com><2DE3ADEAB1B54D65ADA8007B79FB4647@china.huawei.com><8FC44D17-C2DD-499C-99C1-B9294A1B9DD8@nokia.com> <00b101cbb72d$f6093140$4001a8c0@gateway.2wire.net>
Subject: Re: Use of "unassigned" in IANA registries
Date: Wed, 19 Jan 2011 12:14: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=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D36D685.0283, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4D36D68B.00D8,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@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, 19 Jan 2011 12:15:46 -0000

Perhaps what we should do is to ask IANA to amend their web page so that when
you go to the protocol registry, that massive page with hundreds of entries with
a brief explanation at the top, the top includes the definition of 'unassigned'
from RFC5226, with a reference to RFC5226 and a note to the effect that obscure
terms like FCFS, Standards Action are also defined there.  Then noone could
claim ignorance if they squatted on an unassigned code point, their behaviour
would be knowingly malicious.

A bit like 'Note Well' which means that noone can claim that they did not know
what they were doing when they were granting us the right to use their text.

Tom Petch

----- Original Message -----
From: "t.petch" <daedulus@btconnect.com>
To: "Lars Eggert" <lars.eggert@nokia.com>; "Spencer Dawkins"
<spencer@wonderhamster.org>
Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>; "Phillip Hallam-Baker"
<hallam@gmail.com>; <paul.hoffman@vpnc.org>; <ietf@ietf.org>
Sent: Tuesday, January 18, 2011 5:37 PM
Subject: Re: Use of "unassigned" in IANA registries


> ----- Original Message -----
> From: "Lars Eggert" <lars.eggert@nokia.com>
> To: "Spencer Dawkins" <spencer@wonderhamster.org>
> Cc: "Iljitsch van Beijnum" <iljitsch@muada.com>; "Phillip Hallam-Baker"
> <hallam@gmail.com>; <paul.hoffman@vpnc.org>; <ietf@ietf.org>
> Sent: Tuesday, January 18, 2011 3:02 PM
>
> On 2011-1-18, at 15:58, Spencer Dawkins wrote:
> > Lars can speak for himself, but what I THOUGHT he was talking was changing
the
> phrase "unassigned" to something like "reserved for future assignment".
>
> Exactly.
>
> <tp>
> Which, presumably, would be in a BCP updating RFC5226 which only allows for
>
>   Private Use:
>   Experimental:
>   Reserved:  Not to be assigned.
>   Unassigned: Unused and available for assignment via documented  procedures.
>
> Tom Petch
>
> </tp>
>
> Lars
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From lear@cisco.com  Wed Jan 19 05:35:45 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 7AB513A6ED0; Wed, 19 Jan 2011 05:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.167
X-Spam-Level: 
X-Spam-Status: No, score=-110.167 tagged_above=-999 required=5 tests=[AWL=0.432, 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 LDDoyuaDt0y4; Wed, 19 Jan 2011 05:35:44 -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 BBDB83A7121; Wed, 19 Jan 2011 05:35:43 -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: AjYEAH94Nk2Q/khNgWdsb2JhbACED6A1FQEBFiIkpguKV49ZgSSDOHQEix4
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 19 Jan 2011 13:38:23 +0000
Received: from dhcp-10-61-109-82.cisco.com (dhcp-10-61-109-82.cisco.com [10.61.109.82]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p0JDcM3n023025; Wed, 19 Jan 2011 13:38:22 GMT
Message-ID: <4D36E94D.5000908@cisco.com>
Date: Wed, 19 Jan 2011 14:38:21 +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: SM <sm@resistor.net>
Subject: Re: Gen-art review of draft-lear-iana-timezone-database-01
References: <1294852216.17554.17972.camel@mightyatom.folly.org.uk> <6.2.5.6.2.20110112162845.07374c30@resistor.net>
In-Reply-To: <6.2.5.6.2.20110112162845.07374c30@resistor.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: draft-lear-iana-timezone-database.all@tools.ietf.org, General Area Review Team <gen-art@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, 19 Jan 2011 13:35:45 -0000

Elwyn, SM,

Thank you for your reviews.  Here is my current thinking:

1.  There was probably some confusion in that we probably meant section
5.2 and not 5.3 in RFC 5226.  Nevertheless, I find RFC 5226 difficult to
apply here because of the way it is worded.  Specifically, it is
designed for assignment purposes and not for change purposes.  Hence,
I've removed most references to 5226.  To be clear, the TZ coordinator
should be given great deference, but that in limited circumstances
appeals to the IESG must be allowed (one could imagine a designated
expert who went crazy and took sides in a political fight, for instance).

2.  Clearly there is a need for criteria for updating the database. 
We're going to take a swing at that.

3.  The licensing terms listed in the current draft seem to satisfy
almost nobody.  Therefore they have to be redone.  I have asked for
opinions on this very subject from one or two knowledgeable people, and
hope to have a new proposal before the draft cut-off date.

4.  I've accepted your minor point and your nits.

Eliot

On 1/13/11 2:13 AM, SM wrote:
> Hi Elwyn,
> At 09:10 12-01-11, Elwyn Davies wrote:
>> This document is not quite ready for the IESG.  The appeals process (if
>> there is to be one) needs to clarified as it currently points indirectly
>> to a hole in RFC 5226. As explained below, I have a feeling that it
>> would be wise to avoid tying the processes in this document to the
>> Designated Expert processes in RFC 5226 despite the similarities.
>> Making it clear what does apply and what doesn't is probably more work
>> than doing it from scratch in this document, especially given the hole
>> in RFC 5226.
>
> [snip]
>
>> I think the draft should make it explicit that it is referring to the
>> 'Designated Expert' sections in RFC 5226 here if it continues to
>> reference RFC 5226 - although there is a clear relationship with
>> Designated Experts, the differences between the selection process and
>> the operations of the TZ Coordinator and generic Deisgnated Experts may
>
> Yes, there are significant differences.  According to RFC 5226:
>
>   "The designated expert is responsible for initiating and coordinating
>    the appropriate review of an assignment request."
>
> It might be helpful to get some feedback from IANA and the IETF Trust
> on this draft before it is evaluated by the IESG.
>
>> mean that citing RFC 5226 might lead to legalistic disputes about which
>> set of rules applies.  Also, I am unable to find statements in RFC 5226
>> backing up the sentence above.  Regrettably, RFC 5226 appears
>> effectively to have a 'dsngling reference' in this area. Section 3.2,
>> para 3 of RFC 5226 points at Section 5.2 which (allegedly) discusses
>> 'disputes and appeals in more detail'.  However s5.2 is titled 'Updating
>> Registrations' and says nothing about appeals and disputes.  Section 7
>> of RFC 5226 covers appeals of IANA decisions but says nothing specific
>> about appealing designated expert rulings.  I think this area may need a
>> little more work.  Overall, my inclination would be to make this a
>> standalone document that does not try to partially modify the RFC 5226
>> Designated Expert process and operations.  Appeals... >*sigh*<.
>
> Section 7 of RFC 5226 states that:
>
>   "Appeals of registration decisions made by IANA can be made using the
>    normal IETF appeals process as described in Section 6.5 of
>    [IETF-PROCESS]."
>
> Section 4 of mentions that:
>
>   "In keeping with [RFC5226], the IESG selects the TZ
>    coordinator(s).  The IESG will use rough consensus of the TZ mailing
>    list as their primary guide to further action, when it exists, and
>    whatever other means they have at their disposal, when rough
>    consensus cannot be found.  As RFC-5226 states, the IESG is not a
>    normal avenue for appeals of specific decisions of the coordinator,
>    but rather a last resort when a coordinator is thought not to be
>    functioning in an appropriate way."
>
> That could be rewritten as:
>
>    The IESG selects the TZ coordinator(s).  The IESG will use the rough
>    consensus of the TZ mailing list as their primary guide for any
> action,
>    when it exists, and whatever other means they have at their disposal,
>    when rough consensus cannot be found.
>
>    The IESG is not an avenue for appeals of specific decisions of the
>    coordinator, but rather a last resort when a coordinator is thought
> not
>    to be functioning in an appropriate way.  An appeal can be made in
> such
>    a case by using the normal IETF appeals process as described in
> Section
>    6.5 of RFC 2606.
>
> The following sentence in Section 1.1 might have to be removed then:
>
>   "The TZ coordinatior is a Designated Expert, as defined in [RFC5226]"
>
> Regards,
> -sm
>

From fanf2@hermes.cam.ac.uk  Wed Jan 19 05:39:23 2011
Return-Path: <fanf2@hermes.cam.ac.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 9137C3A6ED4; Wed, 19 Jan 2011 05:39:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 bjNMivzRzJ1Q; Wed, 19 Jan 2011 05:39:22 -0800 (PST)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by core3.amsl.com (Postfix) with ESMTP id 8AC163A6ED0; Wed, 19 Jan 2011 05:39:22 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:45031) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1PfYIR-0007u4-Rq (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 19 Jan 2011 13:41:59 +0000
Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1PfYIR-0007G0-KC (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 19 Jan 2011 13:41:59 +0000
Date: Wed, 19 Jan 2011 13:41:59 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
Subject: Re: [DNSOP] Fwd: Last Call:	<draft-cheshire-dnsext-special-names-01.txt> (Special-Use	Domain Names) to Proposed Standard
In-Reply-To: <4D35FC94.5050904@abenaki.wabanaki.net>
Message-ID: <alpine.LSU.2.00.1101191339560.5244@hermes-1.csi.cam.ac.uk>
References: <20110117230048.26192.84056.idtracker@localhost> <2A149A97-3B0A-49AA-88CA-9741F88B9274@gmail.com> <4D35FC94.5050904@abenaki.wabanaki.net>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: dnsop@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, 19 Jan 2011 13:39:23 -0000

On Tue, 18 Jan 2011, Eric Brunner-Williams wrote:
>
> The "--" violation

It is not a violation. Double hyphens have been permitted by the syntax
forever.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7,
DECREASING 4 OR 5, OCCASIONALLY 6 LATER IN HUMBER AND THAMES. MODERATE OR
ROUGH. RAIN THEN FAIR. GOOD.

From jhutz@cmu.edu  Wed Jan 19 08:56:22 2011
Return-Path: <jhutz@cmu.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 BD42428B56A; Wed, 19 Jan 2011 08:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.529
X-Spam-Level: 
X-Spam-Status: No, score=-106.529 tagged_above=-999 required=5 tests=[AWL=0.070, 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 t6vr70qb1RXf; Wed, 19 Jan 2011 08:56:19 -0800 (PST)
Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) by core3.amsl.com (Postfix) with ESMTP id 310CD3A7178; Wed, 19 Jan 2011 08:56:19 -0800 (PST)
Received: from MINBAR.FAC.CS.CMU.EDU (MINBAR.FAC.CS.CMU.EDU [128.2.216.42]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id p0JGwvEV005422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Jan 2011 11:58:57 -0500 (EST)
Date: Wed, 19 Jan 2011 11:58:57 -0500
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: ietf@ietf.org, secdir@ietf.org, draft-groves-eccsi.all@tools.ietf.org
Subject: secdir review of draft-groves-eccsi-00.txt
Message-ID: <1AF6DD3921E5919222492B24@minbar.fac.cs.cmu.edu>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.217.197
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, 19 Jan 2011 16:56:22 -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.  Document editors and WG chairs should treat these comments just
like any other last call comments.

This document defines an identity-based encryption algorithm, using
elliptic-curve crypto, based in part on the design of ECDSA.  In the
system described, each participant has a well-known identifier and a
public/private key pair generated by a central keying authority, which
itself has a well-known public key.  Each participant's public key is
a function of that participant's identifer, the keying authority's
well-known public key, and a long-term "validation token" which is
initially provided the keying authority, and then transmitted by that
participant along with each of its signatures.

This system shares the usual security considerations of any public
key cryptosystem, of ECC in general, and of ECDSA in particular; the
security considerations section seems to do a reasonable job of calling
these out.  Recommendations are made for selecting an appropriate
group size based on the desired symmetric-equivalent strength, but no
information is given as to the  derivation of this advice.  I suggest
a reference to RFC3766, or perhaps some more recent document which
pays particular attention to ECC algorithms.

Naturally, the security of the system depends on secure delivery of
the agreed-upon group parameters, the keying authority's public key,
and the generated keying material to each participant.  This document
calls out the need for suitable protection, but considers protocols
or mechanisms for delivering this data to be out of scope.

No explicit mechanism is provided for revocation or expiration of
keys.  However, identifiers are free-form, and could easily be
extended to include timestamps, as discussed in the security
considerations section.  This is one of the most serious concerns
I have with any identity-based crypto scheme, and I'm glad to see
it called out and addressed.


This document is unusual for the IETF, in that it defines a new
cryptographic algorithm, which we normally don't do.  While there
is no particular reason not to publish it here, I would be wary
of using this algorithm in any IETF protocol until it has seen
extensive review by the cryptographic community.  It looks to me
like it should work, but I am not a cryptographer and may well
have missed an obvious flaw.


From vesely@tana.it  Wed Jan 19 09:36:19 2011
Return-Path: <vesely@tana.it>
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 B50EF28C0EB for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 09:36:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.149
X-Spam-Level: 
X-Spam-Status: No, score=-5.149 tagged_above=-999 required=5 tests=[AWL=-0.430, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 slE9rofQfV9o for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 09:36:18 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 87B413A7183 for <ietf@ietf.org>; Wed, 19 Jan 2011 09:36:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1295458732; bh=BBcDl+TXdMeZ31wOKs/xKCCVRaJS0DddPjIdgLY+czw=; l=330; h=Message-ID:Date:From:MIME-Version:To:CC:References:In-Reply-To: Content-Transfer-Encoding; b=ZN5uju03wfpCvveeXHUoEIfb/dUzn8MZ9SlqJq+5uRMYVDY2UnY+68wzx8DXp7jlp 4IiaxQ5pcRu5EUVGo72aM6O1W8ys+3uswRU9aXQhYmfv/2D0JsB58s4JGwHBk+l43B 1GyOgT9u3bKgauow0OxPAt4Xgd4tuQ+QWZAOG6zk=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 19 Jan 2011 18:38:51 +0100 id 00000000005DC035.000000004D3721AB.00001D5C
Message-ID: <4D3721AB.1090606@tana.it>
Date: Wed, 19 Jan 2011 18:38:51 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: this seems to have become broken some time back
References: <E48F738E-F0EB-4A91-BAB1-E01F2A0CF9F9@isi.edu>	<5444AF4B-7A0A-4DE7-9F06-67535B1F5ECE@hopcount.ca> <01NWS5YOMEMA007CHU@mauve.mrochek.com>
In-Reply-To: <01NWS5YOMEMA007CHU@mauve.mrochek.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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, 19 Jan 2011 17:36:19 -0000

On 19/Jan/11 05:23, ned+ietf@mauve.mrochek.com wrote:
> The client I'm using right now (which I coauthored) is one of the very few with
> support for external body dereferencing.

However, your client apparently omits to identify itself by means of a
User-Agent header field...  Would you mind mentioning it by name?

TIA



From wwwrun@core3.amsl.com  Wed Jan 19 13:31:26 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 E3D2228C0F4; Wed, 19 Jan 2011 13:31:25 -0800 (PST)
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Subject: IETF 83 Venue 
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110119213125.E3D2228C0F4@core3.amsl.com>
Date: Wed, 19 Jan 2011 13:31:25 -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: Wed, 19 Jan 2011 21:31:26 -0000

The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
March 2012.  The IETF last met in the city in 2005 at IETF 63.

Paris was the number one choice for a European venue in a venue
preference survey conducted after IETF 78.

Those who may be interested in hosting or sponsoring this or any future
meeting are invited to contact Drew Dvorshak at dvorshak@isoc.org.  See
meeting opportunities below.

Registration has opened for IETF 80 in Prague. 
http://www.ietf.org/meeting/80/index.html
Hope to see you there in 64 days!  Sponsorship opportunities are still
available for Prague, such as the Welcome Reception and beverage breaks. 
Contact Drew if interested.

Ray Pelletier
IETF Administrative Director

2011
IETF 80  Prague  27 March - 1 April  Host: CZ.NIC
IETF 81  Quebec City 24 - 29 July  Host:  RIM
IETF 82  Taipei  13 - 18 November  Host: TWNIC

2012
IETF 83  Paris 25 - 30 March 	Host:  <your name here>
IETF 84  Asia - Pacific  29 July - 3 Aug  Host:   <your name here>
IETF 85  Atlanta  4 - 9 November   Host:  <your name here>

2013
IETF 86  Orlando  10 - 15 March  Host:  <your name here> (Back-to-back
with IEEE)
IETF 87  Europe  28 July - 2 Aug  Host:  <your name here>
IETF 88  Asia  3 - 8 November  Host:  <your name here>

From sm@resistor.net  Wed Jan 19 14:26:36 2011
Return-Path: <sm@resistor.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 8233828C117 for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 14:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.638
X-Spam-Level: 
X-Spam-Status: No, score=-103.638 tagged_above=-999 required=5 tests=[AWL=-0.039, 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 3YA3nAVGnhPq for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 14:26:31 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id F0B8028C0EF for <ietf@ietf.org>; Wed, 19 Jan 2011 14:26:30 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0JMSFRl010217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 19 Jan 2011 14:29:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1295476151; x=1295562551; bh=IiS44+In3zC2KIaIl/5Xa0j7lnt8EULHpEQ8YqyQt60=; h=Message-Id:Date:To:From:Subject:Mime-Version:Content-Type:Cc; b=jrrolnBX4j5YbI/nqZA3p6kFwH3ZpBhk98uGe61tO58LrColSofURozdc90XeIaw6 n7GlUYjoureDYTBWrHV3YFY0TCadfK7Qvk2HLtoK4qfzk3KCuCYqO27zxrIUAt+9sh RLg+p9XjQSzOQw+g9lJuYNbtKt7/IIPXeHMsoHpc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1295476151; x=1295562551; bh=IiS44+In3zC2KIaIl/5Xa0j7lnt8EULHpEQ8YqyQt60=; h=Message-Id:Date:To:From:Subject:Mime-Version:Content-Type:Cc; b=ySip6GsTGdQzawU14J2/lcxOToMffsuaMZPiALHEoIiX5hwbxmrt49HWmRN1iwGcC Eyh0RRph1uaQoswfGhxONQSyssSTdYfBWNqf2hUZy7ndcDUrpVYzoPQ8T0SnbrVAYe hhuHLWT0+55GFrh19erOVqD4WcPxP1Jebl8f6PdQ=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=We/8NhXQcglAzj01S+e7TpVqtYbLVqdlwv9yya/oZvgVS0DaUjAz9iyf02ag5OQA1 pB+RLPBavAQqQtyXuG3NGv7tLu4FMOYGeUHmNnJ8vekjCmapQJmQjFgbVEYz1oFmbz7 7vCba3PhYoeXrTx8aOwXMRxGLwW1eRw3hToRISA=
Message-Id: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Jan 2011 14:20:39 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Change control
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 19 Jan 2011 22:26:36 -0000

Hello,

This is the second time in a year that I came across a case where a 
non-IETF group sought to maintain change control over a draft.  In 
the first case, several iterations of the draft were posted and the 
author solicited comments on an IETF mailing list.

   (a) By making an IETF Submission, is an author allowing the IETF to have
       change control on the work?

   (b) Is it appropriate to use a WG mailing list to discuss a work on
       which the IETF does not have change control?

   (c) If the IETF Submission is covered by the WG Charter, can the WG
       enhance the original contribution in accordance with the IETF
       Standards Process by adopting it as a WG work item?

Regards,
-sm


From d3e3e3@gmail.com  Wed Jan 19 15:02:06 2011
Return-Path: <d3e3e3@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 6B74928C133 for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 15:02:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.314
X-Spam-Level: 
X-Spam-Status: No, score=-103.314 tagged_above=-999 required=5 tests=[AWL=0.285, 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 7SLgGviU0qve for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 15:02:05 -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 516DA28C0E0 for <ietf@ietf.org>; Wed, 19 Jan 2011 15:02:05 -0800 (PST)
Received: by eyd10 with SMTP id 10so931328eyd.31 for <ietf@ietf.org>; Wed, 19 Jan 2011 15:04:45 -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:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=zy8hbtLJzLzqz8H+GbjDK9At2eIJyiuFrNQBBs0lDHc=; b=G7AHv0LA+25TVzf4MZ5VyS1Dab1Fh1UR/w7TLK7180RjaZo6TyFZoysGHJTzPrGX+R Uvae2WtiH7MLf4wHaBkMQ3FfBT8C/RB33/I7JVV35rIi47YVuaVtQvUYx+ZN2dF2AB48 Gmm4Y0GHUroc/ggXQTfrmlFdzRW5FiBgtTuog=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=D9ReGYZ13kVTd7/JWQgA0RinxEStzgRHOqAAx2XrJlZ0doIBdn8DqaxaUEDfdGaPgy ZIzcI5mNAzxT4ZjnW74CU5/JBEIvklgjbnwiN8Q6W6R44AwXAJXLerlOO1qesuW2EbJu nuaGYvM8DSnC7AgmB5MLK+4ICSPDU/HLWggfQ=
Received: by 10.227.145.139 with SMTP id d11mr1526488wbv.8.1295478285689; Wed, 19 Jan 2011 15:04:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 19 Jan 2011 14:58:12 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com>
References: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 19 Jan 2011 17:58:12 -0500
Message-ID: <AANLkTim6b-_=r7MbT12VRv69d=QMJSU0+G+ze2PFry3M@mail.gmail.com>
Subject: Re: Change control
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 19 Jan 2011 23:02:06 -0000

Hi,

On Wed, Jan 19, 2011 at 5:20 PM, SM <sm@resistor.net> wrote:
> Hello,
>
> This is the second time in a year that I came across a case where a non-I=
ETF
> group sought to maintain change control over a draft. =A0In the first cas=
e,
> several iterations of the draft were posted and the author solicited
> comments on an IETF mailing list.
>
> =A0(a) By making an IETF Submission, is an author allowing the IETF to ha=
ve
> =A0 =A0 =A0change control on the work?

It depends. That's why there are different versions of the boilerplate
depending on what rights the submitter is granting to the IETF.

> =A0(b) Is it appropriate to use a WG mailing list to discuss a work on
> =A0 =A0 =A0which the IETF does not have change control?

Generally, yes. There's nothing wrong is such discussion if there
appears to be a WG consensus to do so. You refer to this hypothetical
submission as a "work", which is a technically correct copyright term,
but I believe you are thinking of it as a standards specification or a
part of or an amendment to such a specification. But it can just be
that the submitter wanted to use the draft format as a convenient way
to make a statement to the WG, presumably a statement relevant to what
the WG is doing. In such a case, the whole point would be
consideration and, if appropriate, discussion of that statement in the
WG.

> =A0(c) If the IETF Submission is covered by the WG Charter, can the WG
> =A0 =A0 =A0enhance the original contribution in accordance with the IETF
> =A0 =A0 =A0Standards Process by adopting it as a WG work item?

It depends. That's why there are different versions of the
boilerplate. If the submitter has denied the IETF permission to
produce derivative works, then it seems improper to attempt to adopt
that draft as a WG draft. That's because being a WG draft implies WG
change control. However, the ideas in the draft could be used in a WG
draft.

> Regards,
> -sm

Thanks,
Donald

From hallam@gmail.com  Wed Jan 19 15:43: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 D925428C0E4 for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 15:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.466
X-Spam-Level: 
X-Spam-Status: No, score=-3.466 tagged_above=-999 required=5 tests=[AWL=0.132,  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 bLPHtqC+NYft for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 15:43:53 -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 87ACB28C0CE for <ietf@ietf.org>; Wed, 19 Jan 2011 15:43:53 -0800 (PST)
Received: by gyd12 with SMTP id 12so675928gyd.31 for <ietf@ietf.org>; Wed, 19 Jan 2011 15:46:34 -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=RPDxtb5/FdXCD5oNCxsRMynysAeR/wnvM9s6RwHOM+Y=; b=nR98sopjpLSy3GMwLP/QcOFkudw0CT4WIP1f8HdrFacWWrXntTUojPHUIiEuEkeaaa fsjcGr8opBQqwultE+W1221Ww7cl8h493wSXiCOd2LBVLyrQlfyJniRh5e+7lS6TcGCi mQu3iP9MXpgm217vXdDFZqReT9S+Rye+udXkc=
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=AsfGem1BJWp1ZLP5h7unNFquzSqFA4nmkatZKFNMyYSnZRd6s+CneglNv3/m0+0zxo FXllyzWf4JgziLdEt/g9MJNByeHJZonU8ADW/q7ONVUvTNJe4LisJe39G1ZnHxuDIT2r dBiHblkyuQ7xG5KikmWyyYdOQ/eGLNtcfnKZs=
MIME-Version: 1.0
Received: by 10.100.8.9 with SMTP id 9mr947229anh.120.1295480793470; Wed, 19 Jan 2011 15:46:33 -0800 (PST)
Received: by 10.100.201.18 with HTTP; Wed, 19 Jan 2011 15:46:33 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com>
References: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com>
Date: Wed, 19 Jan 2011 18:46:33 -0500
Message-ID: <AANLkTimAn-wvkiGAS7849KYZ0zCE1LGdbJGmqWtBGDKa@mail.gmail.com>
Subject: Re: Change control
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=0016e6441dd882186e049a3ba066
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, 19 Jan 2011 23:43:54 -0000

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

What is?

I generally reserve change control over non WG IDs because I have
experienced people hijacking a draft, changing the principles entirely and
adding their name.

Since there is an explicit allowance for that in the IPR regime, I don't see
why this would be an issue.


On Wed, Jan 19, 2011 at 5:20 PM, SM <sm@resistor.net> wrote:

> Hello,
>
> This is the second time in a year that I came across a case where a
> non-IETF group sought to maintain change control over a draft.  In the first
> case, several iterations of the draft were posted and the author solicited
> comments on an IETF mailing list.
>
>  (a) By making an IETF Submission, is an author allowing the IETF to have
>      change control on the work?
>
>  (b) Is it appropriate to use a WG mailing list to discuss a work on
>      which the IETF does not have change control?
>
>  (c) If the IETF Submission is covered by the WG Charter, can the WG
>      enhance the original contribution in accordance with the IETF
>      Standards Process by adopting it as a WG work item?
>
> Regards,
> -sm
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

What is?<div><br></div><div>I generally reserve change control over non WG =
IDs because I have experienced people hijacking a draft, changing the princ=
iples entirely and adding their name.=A0</div><div><br></div><div>Since the=
re is an explicit allowance for that in the IPR regime, I don&#39;t see why=
 this would be an issue.</div>
<div><br><br><div class=3D"gmail_quote">On Wed, Jan 19, 2011 at 5:20 PM, SM=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.net">sm@resistor.net</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br>
<br>
This is the second time in a year that I came across a case where a non-IET=
F group sought to maintain change control over a draft. =A0In the first cas=
e, several iterations of the draft were posted and the author solicited com=
ments on an IETF mailing list.<br>

<br>
 =A0(a) By making an IETF Submission, is an author allowing the IETF to hav=
e<br>
 =A0 =A0 =A0change control on the work?<br>
<br>
 =A0(b) Is it appropriate to use a WG mailing list to discuss a work on<br>
 =A0 =A0 =A0which the IETF does not have change control?<br>
<br>
 =A0(c) If the IETF Submission is covered by the WG Charter, can the WG<br>
 =A0 =A0 =A0enhance the original contribution in accordance with the IETF<b=
r>
 =A0 =A0 =A0Standards Process by adopting it as a WG work item?<br>
<br>
Regards,<br>
-sm<br>
<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">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>

--0016e6441dd882186e049a3ba066--

From mrex@sap.com  Wed Jan 19 18:40:55 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 936E13A6FE9 for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 18:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level: 
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.083, 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 N6Kr7dV5rKyn for <ietf@core3.amsl.com>; Wed, 19 Jan 2011 18:40:54 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by core3.amsl.com (Postfix) with ESMTP id 779743A6FAB for <ietf@ietf.org>; Wed, 19 Jan 2011 18:40:53 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p0K2hYCL019866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2011 03:43:34 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201101200243.p0K2hXCw014373@fs4113.wdf.sap.corp>
Subject: Re: Change control
To: sm@resistor.net (SM)
Date: Thu, 20 Jan 2011 03:43:33 +0100 (MET)
In-Reply-To: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com> from "SM" at Jan 19, 11 02:20:39 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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: Thu, 20 Jan 2011 02:40:55 -0000

SM wrote:
> 
> This is the second time in a year that I came across a case where a 
> non-IETF group sought to maintain change control over a draft.  In 
> the first case, several iterations of the draft were posted and the 
> author solicited comments on an IETF mailing list.
> 
>    (a) By making an IETF Submission, is an author allowing the IETF to have
>        change control on the work?

It is up to the author to include a suitable Copyright statement in
I-Ds that he uploads/submits to the IETF for publication as I-D.

You may find useful information about this here:

  http://tools.ietf.org/html/bcp78#section-3

> 
>    (b) Is it appropriate to use a WG mailing list to discuss a work on
>        which the IETF does not have change control?

Ideally, a WG should keep the focus on the work that it chartered
_itself_ to work on.  WG chairs are entrusted with significant
discretion to contain discussions on the WG-list either within
chartered scope or when off-topic at acceptable levels--or
occasionally gauge WG consensus for rechartering.


> 
>    (c) If the IETF Submission is covered by the WG Charter, can the WG
>        enhance the original contribution in accordance with the IETF
>        Standards Process by adopting it as a WG work item?

Copyright must be _granted_ by the author, so it is the other way round.
Before an individual submission I-D can be adopted as a WG item,
the contributor must grant the necessary rights (to produce derivative
works) to the IETF.

That's how I understand the second paragraph here:
http://tools.ietf.org/html/bcp78#page-7

While the inclusion of the respective Copyright boilerplate by the
author in the the submission is technically sufficient,
I would consider it a courtesy to ask the original author for
consent anyway, especially if it is about a new I-D
(rather than an older RFC).


-Martin

From matthew.bocci@alcatel-lucent.com  Thu Jan 20 00:45:15 2011
Return-Path: <matthew.bocci@alcatel-lucent.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 7629228B23E; Thu, 20 Jan 2011 00:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.528
X-Spam-Level: 
X-Spam-Status: No, score=-104.528 tagged_above=-999 required=5 tests=[AWL=-0.579, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 TOAztNkMmj9n; Thu, 20 Jan 2011 00:45:14 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id 0EFFD28C0CF; Thu, 20 Jan 2011 00:45:13 -0800 (PST)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p0K8ljCI003460 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 20 Jan 2011 09:47:53 +0100
Received: from FRMRSSXCHMBSA3.dc-m.alcatel-lucent.com ([135.120.45.38]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Thu, 20 Jan 2011 09:47:48 +0100
From: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-mpls-tp-uni-nni.all@tools.ietf.org" <draft-ietf-mpls-tp-uni-nni.all@tools.ietf.org>
Date: Thu, 20 Jan 2011 09:47:44 +0100
Subject: Re: Gen-ART LC Review of draft-ietf-mpls-tp-uni-nni-02
Thread-Topic: Gen-ART LC Review of draft-ietf-mpls-tp-uni-nni-02
Thread-Index: Acu4fraH6eMlcwTGQGmTT79mQ6IKkw==
Message-ID: <C95DA46E.7A00%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <C9378145.6221%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.0.101115
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Cc: General Area Review Team <gen-art@ietf.org>, 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: Thu, 20 Jan 2011 08:45:15 -0000

Ben,

Apologies for missing your additional questions. Please see below for a
response.

Best regards,

Matthew

From: Ben Campbell <ben@nostrum.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
Reply-to: ben@nostrum.com
Subject: Re: [Gen-art] Gen-ART LC Review of draft-ietf-mpls-tp-uni-nni-02
X-RSN: 1/0/933/9723/54927
=20
Thanks for the quick response. Also see below. I elided sections that I
think have been addressed.
=20
On Dec 22, 2010, at 5:44 AM, Bocci, Matthew (Matthew) wrote:
=20
> Ben,=20
> =20
> Thank you for your comments. Please see below.
> =20
> Best regards=20
> =20
> Matthew=20
> =20
> On 21/12/2010 22:13, "Ben Campbell" <ben@nostrum.com> wrote:
> =20
=20
[...]=20
=20
>> =20
>> -- Section 1.1, 1st paragraph:
>> =20
>> More conventional in what context? Useful for what purpose?
> =20
> It is the convention to represent a UNI or NNI as a specific reference
> point between functional groups e.g. MEF E-NNI (Figure 2 of MEF26) or
>ATM=20
> UNI (ITU-T I.413), rather than to represent these as a span as in the
> original diagrams in RFC5921. I propose to rephrase this sentence to:
> "However, it is convention to illustrate these interfaces as reference
> points."=20
> =20
> With regard to your second question, I propose to rephrase the sentence
>as=20
> follows:=20
> "Furthermore, in the case of a UNI, it is useful to illustrate the
> distribution of UNI functions between the Customer Edge (CE) side and
>the=20
> Provider Edge (PE) side of the UNI (the UNI-C and UNI-N) in order to
>show=20
> their relationship to one another."
> =20
> =20
=20
WFM=20
=20
> =20
>> =20
>> -- Figures 1 and 2:
>> =20
>> Is the meaning of the various line types described elsewhere? If so, a
>> statement to that effect with a reference would be helpful.
> =20
> We have used the same convention as RFC5921. However, there is no key
> there. I am not sure that a complete key would clarify the diagram as
>the=20
> same line type is used to represent multiple entities due to the limited
> umber of characters that are useful for ASCII drawing.
=20
Ah, I agree it probably would be too much to add a complete key, and on
re-reading, I see most of the lines are sufficiently labeled. But I am
still confused by a few of them. For example, in under the UNI column, I
see both a single and double dashed (equal signs) line under the label of
"Client Traffic Flows". Should I assume those to just be two arbitrary
flows where the line type just helps me follow a particular flow, or are
they somehow different classes of flows?=20

MB> They are just flows belonging to arbitrary transport service
instances, and helps the reader to follow the path of the flow.
=20
On the right side of the same diagram, I see 3 Transport Paths with an
outer set of arrows, and the lower two having another arrow between.
Should the outer arrows be interpreted as a "channel" over which client
traffic flows?=20

MB> The outer arrows are supposed to look like two sides of a tunnel (the
transport path) other which the transport service instance (TSI) is
transported.=20
=20
> =20
>> =20
>> -- Figure 2:=20
>> =20
>> I suggest expanding CP somewhere.
> =20
> CP is expanded in the terminology section.
=20
So it is, right there at the top. (I could have sworn I did a text search
for that--looks like the search option in the iPad tool I use for
reviewing drafts is not reliable :-|)
=20
> =20
> =20


On 22/12/2010 11:44, "Bocci, Matthew (Matthew)"
<matthew.bocci@alcatel-lucent.com> wrote:

>Ben,
>
>Thank you for your comments. Please see below.
>
>Best regards
>
>Matthew
>
>On 21/12/2010 22:13, "Ben Campbell" <ben@nostrum.com> wrote:
>
>>I am the assigned Gen-ART reviewer for this draft. For background on
>>Gen-ART, please see the FAQ at
>><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>Please resolve these comments along with any other Last Call comments you
>>may receive.
>>
>>Document: draft-ietf-mpls-tp-uni-nni-02
>>Reviewer: Ben Campbell
>>Review Date: 2010-12-21
>>IETF LC End Date: 2010-12-23
>>IESG Telechat date: (if known)
>>
>>
>>Summary: This draft is ready for publication as in informational RFC. I
>>have a small number of editorial comments that I think could further
>>improve the draft if there is another round of editing.
>>
>>Major issues: None
>>
>>Minor issues: None
>>
>>Nits/editorial comments:
>>
>>-- Section 1, 1st paragraph:
>>
>>I suggest moving the expansion of MPLS-TP TP the first mention in the
>>body of the draft.
>
>
>OK. I have moved this to the first use of the acronym in that section.
>
>>
>>-- Section 1.1, 1st paragraph:
>>
>>More conventional in what context? Useful for what purpose?
>
>It is the convention to represent a UNI or NNI as a specific reference
>point between functional groups e.g. MEF E-NNI (Figure 2 of MEF26) or ATM
>UNI (ITU-T I.413), rather than to represent these as a span as in the
>original diagrams in RFC5921. I propose to rephrase this sentence to:
>"However, it is convention to illustrate these interfaces as reference
>points."
>
>With regard to your second question, I propose to rephrase the sentence as
>follows:
>"Furthermore, in the case of a UNI, it is useful to illustrate the
>distribution of UNI functions between the Customer Edge (CE) side and the
>Provider Edge (PE) side of the UNI (the UNI-C and UNI-N) in order to show
>their relationship to one another."
>
>
>>
>>-- Section 1.2, definition of UNI-N
>>
>>I suggest expanding PE in the definition.
>
>OK=20
>
>>
>>-- Figures 1 and 2:
>>
>>Is the meaning of the various line types described elsewhere? If so, a
>>statement to that effect with a reference would be helpful.
>
>We have used the same convention as RFC5921. However, there is no key
>there. I am not sure that a complete key would clarify the diagram as the
>same line type is used to represent multiple entities due to the limited
>umber of characters that are useful for ASCII drawing.
>
>>
>>-- Figure 2:
>>
>>I suggest expanding CP somewhere.
>
>CP is expanded in the terminology section.
>
>


From sm@resistor.net  Thu Jan 20 11:27:29 2011
Return-Path: <sm@resistor.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 B2AF23A67E4 for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 11:27:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.636
X-Spam-Level: 
X-Spam-Status: No, score=-103.636 tagged_above=-999 required=5 tests=[AWL=-0.037, 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 gM46nyKJz3Dx for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 11:27:28 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 0ECAE3A67E2 for <ietf@ietf.org>; Thu, 20 Jan 2011 11:27:27 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0KJTAYO024987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jan 2011 11:30:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1295551806; x=1295638206; bh=akWNFIYlEmeUq53TGLGdw+HraMAFpZQeLxynDv3HSdQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=lUBYEw9tdrDQ9aCwfITwMFfVHYuStf1N5ncFZU8nB6m4Vckjw+Z6vDCDxwoj2e3cL 9WY8JsRmyzrokpusjJCpkNht0poFTVkworwUNsA38DmUZwN8ycfsJ0HX2PNK8/3yog cWFEC1Zm8Ba5lg/VkA7FSp8AHah49eZroryLef8E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1295551806; x=1295638206; bh=akWNFIYlEmeUq53TGLGdw+HraMAFpZQeLxynDv3HSdQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=XUIA88cFly1Pxnx/gp47Kf1/OsfHoTf3CIlUiqWdPGvtB5q07TkD3TOuMCuZZuyG4 CgK4ZH+ti25ZVxt4lXFqbnGg1i0e1rD5nCYwYo1NtLkjhQTJLkvgTsO11V+COTAge4 D0In2RV0lVcTrctV4t1g6X5l+E3uSayQPm0/wDKU=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=NXofcf3u51dP2FvW3HQzcgxcDFTYJzrG/cXgAwywAv1yXMWpbYqQ/jZDeiNL1DwTP EivXXI7ZVblVx0aN1YZIVYlW9zUNKASAvXwz9MF0G+mzvuxTRbD20TsJ715dEZlBQe7 rPdFEqjBlxjrZcGpQARjQ9Fm+hZfzU5kNgtdT0s=
Message-Id: <6.2.5.6.2.20110119153443.07737800@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Jan 2011 10:56:12 -0800
To: Donald Eastlake <d3e3e3@gmail.com>, Phillip Hallam-Baker <hallam@gmail.com>, Martin Rex <mrex@sap.com>
From: SM <sm@resistor.net>
Subject: Re: Change control
In-Reply-To: <AANLkTim6b-_=r7MbT12VRv69d=QMJSU0+G+ze2PFry3M@mail.gmail.c om>
References: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com> <AANLkTim6b-_=r7MbT12VRv69d=QMJSU0+G+ze2PFry3M@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 20 Jan 2011 19:27:29 -0000

At 14:58 19-01-11, Donald Eastlake wrote:
>It depends. That's why there are different versions of the boilerplate
>depending on what rights the submitter is granting to the IETF.

I'll reproduce the notice for completeness:

   "This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
    carefully, as they describe your rights and restrictions with respect
    to this document.  Code Components extracted from this document must
    include Simplified BSD License text as described in Section 4.e of
    the Trust Legal Provisions and are provided without warranty as
    described in the Simplified BSD License."

I gather that an IETF Submission with the above notice allows the 
IETF to have change control on the work.

>Generally, yes. There's nothing wrong is such discussion if there
>appears to be a WG consensus to do so. You refer to this hypothetical
>submission as a "work", which is a technically correct copyright term,
>but I believe you are thinking of it as a standards specification or a
>part of or an amendment to such a specification. But it can just be
>that the submitter wanted to use the draft format as a convenient way
>to make a statement to the WG, presumably a statement relevant to what
>the WG is doing. In such a case, the whole point would be
>consideration and, if appropriate, discussion of that statement in the
>WG.

I was thinking of it in terms of "work", BCP 78 and BCP 79.  Thanks 
for providing a better perspective.

>It depends. That's why there are different versions of the
>boilerplate. If the submitter has denied the IETF permission to
>produce derivative works, then it seems improper to attempt to adopt
>that draft as a WG draft. That's because being a WG draft implies WG
>change control. However, the ideas in the draft could be used in a WG
>draft.

At 15:46 19-01-11, Phillip Hallam-Baker wrote:
>I generally reserve change control over non WG IDs because I have 
>experienced people hijacking a draft, changing the principles 
>entirely and adding their name.
>
>Since there is an explicit allowance for that in the IPR regime, I 
>don't see why this would be an issue.

Some people post drafts with the notice quoted above.  They have not 
given any thought to the "explicit allowance" and end up being 
unhappy when they are asked to give up control.  The first case (see 
my previous message) wasn't a pleasant situation.

At 18:43 19-01-11, Martin Rex wrote:
>That's how I understand the second paragraph here:
>http://tools.ietf.org/html/bcp78#page-7

Yes.

For what it's worth, there was a case where changes to the SDO 
specification, which was not an IETF Submission, are only accepted 
from members of the SDO.  There is a parallel with the IETF here as 
Contributions require acceptance of the Note Well, i.e. changes are 
only accepted from IETF participants.

>While the inclusion of the respective Copyright boilerplate by the
>author in the the submission is technically sufficient,
>I would consider it a courtesy to ask the original author for
>consent anyway, especially if it is about a new I-D
>(rather than an older RFC).

Agreed.

Regards,
-sm 


From sm@resistor.net  Thu Jan 20 11:27:31 2011
Return-Path: <sm@resistor.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 1F54B3A67E5 for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 11:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.635
X-Spam-Level: 
X-Spam-Status: No, score=-103.635 tagged_above=-999 required=5 tests=[AWL=-0.036, 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 KIwR1I9Yo10s for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 11:27:30 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 32DB03A67E2 for <ietf@ietf.org>; Thu, 20 Jan 2011 11:27:30 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0KJTAYQ024987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 20 Jan 2011 11:30:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1295551813; x=1295638213; bh=BBQ3isgEzSf8AVJAhHzptz2L9ARWD0lZlBICgsAS+lM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=v2vfXmmdfzdKSLAWdD1rAjSXFBSZlGNIvrI/T7KxaGQ3YYqW67no4a2dBctaGVGG6 IOhBU7jrBuP7Tgne+bJfSzn1k5uSkseOJEe6l/WNPe52rmV5lLCQrfMXaQOQvI6oa2 Hdb7SwJsqeDp9Cmfuxgx2moIx20D9FgQhGml0/tM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1295551813; x=1295638213; bh=BBQ3isgEzSf8AVJAhHzptz2L9ARWD0lZlBICgsAS+lM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=0a8BUVP0II+DRNiooZ/7HF2QCgEOf83U0ZCIbSRfOzmuL228Ma6aZiPKTJxSr4LmX e8EL96/9yYoLFDB/aq3hIZ6pD9az++WhGT3S2QqVAthwn4/3xjLosD9gfZSN1YqBWy e8diD78DcWZgew7POL1dpxSmEYC4XaRFUxxGpD1E=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=lwkVoorHiiD593qj1bE4NecRwa0N0QmO5yZvSnuIQ3YnrGwwGE33tKayDfV2TyQpm 5Mi+Z6a18UAN3zZvV49Dln+jvIXOac+6gHzoZ6G8Fc0OMmxOukU0SA3iM+0tM9gj04Q FWaWtc9cD2Rz+qL3svJbmaremDpbDQbqmeJhCeQ=
Message-Id: <6.2.5.6.2.20110120110057.0d0f5228@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Jan 2011 11:18:47 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
In-Reply-To: <20110114155632.17927.70550.idtracker@localhost>
References: <20110114155632.17927.70550.idtracker@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 20 Jan 2011 19:27:31 -0000

At 07:56 14-01-11, The IESG wrote:

>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'The 'about' URI scheme'
>   <draft-holsten-about-uri-scheme-06.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

There is a IANA registration in Section 8.  The arguments at 
http://www.ietf.org/mail-archive/web/ietf/current/msg65163.html are 
also applicable to draft-holsten-about-uri-scheme-06.

In Section 5.2:

   "Applications MAY resolve any unreserved "about" URI to any resource,
    either internal or external, or redirect to an alternative URI."

What happens when the unreserved "about" URI becomes a reserved 
"about" URI in future?

Regards,
-sm


From msk@cloudmark.com  Thu Jan 20 12:50:47 2011
Return-Path: <msk@cloudmark.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 7813D3A6824 for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 12:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.945
X-Spam-Level: 
X-Spam-Status: No, score=-103.945 tagged_above=-999 required=5 tests=[AWL=-0.346, 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 GM0806LuCFUn for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 12:50:46 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by core3.amsl.com (Postfix) with ESMTP id 3ADB33A6804 for <ietf@ietf.org>; Thu, 20 Jan 2011 12:50:46 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 20 Jan 2011 12:53:30 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 20 Jan 2011 12:53:28 -0800
Subject: RE: Change control
Thread-Topic: Change control
Thread-Index: Acu42HvaERp0Us1OTIiV5tttvvQdkgACunRg
Message-ID: <F5833273385BB34F99288B3648C4F06F1341E73F6E@EXCH-C2.corp.cloudmark.com>
References: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com> <AANLkTim6b-_=r7MbT12VRv69d=QMJSU0+G+ze2PFry3M@mail.gmail.com> <6.2.5.6.2.20110119153443.07737800@resistor.net>
In-Reply-To: <6.2.5.6.2.20110119153443.07737800@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 20 Jan 2011 20:50:47 -0000

To be honest, I'm not even clear on what the issue is.

If an organization creates a BCP in its own context based on the experience=
s of its constituents, and then the IETF uses that material to inform its o=
wn BCP on the same subject, and reasonable permission and attribution are g=
iven, what constitutes "change control"?  The IETF controls its version, an=
d the other organization controls its own.

For example, OpenBSD was forked from NetBSD.  Who now has change control?  =
Does that even mean anything?

Apart from copyright matters, I think the only problem arises when there's =
debate over whose version is the "official" one.  But that's a matter of th=
e perception that exists outside of the two organizations.  Otherwise, aren=
't they merely two perspectives on the same subject matter, and that's that=
?

-MSK

From hallam@gmail.com  Thu Jan 20 13:13:27 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 D8C093A6822 for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 13:13:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.63
X-Spam-Level: 
X-Spam-Status: No, score=-3.63 tagged_above=-999 required=5 tests=[AWL=-0.032,  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 714qzk178KoX for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 13:13:26 -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 7A4163A6820 for <ietf@ietf.org>; Thu, 20 Jan 2011 13:13:26 -0800 (PST)
Received: by gwb20 with SMTP id 20so363178gwb.31 for <ietf@ietf.org>; Thu, 20 Jan 2011 13:16:10 -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=sP/H1EECj/uQ5Nvw3/NjipBauZklhMzXcT7Y7TiKSzo=; b=riCfFNf/8vPyQCuSvjNs7+0/Pve2kh45y5CCC25Ug1vH3weu3kLympGemaR/qL1prd XU15SPrfaI/+rtrSUHsUZXZqbs9NrtqRNrpppwpq8EFY0Sx7070waVs6rZCJ3f4CuBmk G37LYZbWBLT0HV318EtMQoUg8hHHzPd25A6ao=
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=jhzbjKa/2cZaWV82IQG+kJu3lKAkGCd/wNtfNjWXf9W2IE/iU3theeu+CoqujNK0sc H1WsqFfq5lNzyCCwQWHoGUQY1q6m7l1r5SHouF8+teEr+AG3IaFswfdxhBOxNDCfhrxX +Eho/nuUR5kPhAmER7qiZIoPtGFxurA3D+L5U=
MIME-Version: 1.0
Received: by 10.100.44.17 with SMTP id r17mr1784000anr.222.1295558169971; Thu, 20 Jan 2011 13:16:09 -0800 (PST)
Received: by 10.100.201.18 with HTTP; Thu, 20 Jan 2011 13:16:09 -0800 (PST)
In-Reply-To: <F5833273385BB34F99288B3648C4F06F1341E73F6E@EXCH-C2.corp.cloudmark.com>
References: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com> <AANLkTim6b-_=r7MbT12VRv69d=QMJSU0+G+ze2PFry3M@mail.gmail.com> <6.2.5.6.2.20110119153443.07737800@resistor.net> <F5833273385BB34F99288B3648C4F06F1341E73F6E@EXCH-C2.corp.cloudmark.com>
Date: Thu, 20 Jan 2011 16:16:09 -0500
Message-ID: <AANLkTimp9_sBmy5emNbsmSTZtt9TOqEspOppdn-B+7=q@mail.gmail.com>
Subject: Re: Change control
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: multipart/alternative; boundary=0016e644bc7681cb03049a4da474
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, 20 Jan 2011 21:13:27 -0000

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

That is why I really want to see a specific example of harm (which I note SM
has refused to do).

This is the sort of case where it is very easy to make the wrong decision if
people are allowed to waffle on about what they imagine to be high principle
when the rules were made the way they are to support important real world
requirements.

If we are to discuss this further, I want to see an example.

<eom>


On Thu, Jan 20, 2011 at 3:53 PM, Murray S. Kucherawy <msk@cloudmark.com>wrote:

> To be honest, I'm not even clear on what the issue is.
>
> If an organization creates a BCP in its own context based on the
> experiences of its constituents, and then the IETF uses that material to
> inform its own BCP on the same subject, and reasonable permission and
> attribution are given, what constitutes "change control"?  The IETF controls
> its version, and the other organization controls its own.
>
> For example, OpenBSD was forked from NetBSD.  Who now has change control?
>  Does that even mean anything?
>
> Apart from copyright matters, I think the only problem arises when there's
> debate over whose version is the "official" one.  But that's a matter of the
> perception that exists outside of the two organizations.  Otherwise, aren't
> they merely two perspectives on the same subject matter, and that's that?
>
> -MSK
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

That is why I really want to see a specific example of harm (which I note S=
M has refused to do).<div><br></div><div>This is the sort of case where it =
is very easy to make the wrong decision if people are allowed to waffle on =
about what they imagine to be high principle when the rules were made the w=
ay they are to support important real world requirements.</div>
<div><br></div><div>If we are to discuss this further, I want to see an exa=
mple.</div><div><br></div><div>&lt;eom&gt;</div><div><br><br><div class=3D"=
gmail_quote">On Thu, Jan 20, 2011 at 3:53 PM, Murray S. Kucherawy <span dir=
=3D"ltr">&lt;<a href=3D"mailto:msk@cloudmark.com">msk@cloudmark.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;">To be honest, I&#39;m not even clear on wha=
t the issue is.<br>
<br>
If an organization creates a BCP in its own context based on the experience=
s of its constituents, and then the IETF uses that material to inform its o=
wn BCP on the same subject, and reasonable permission and attribution are g=
iven, what constitutes &quot;change control&quot;? =A0The IETF controls its=
 version, and the other organization controls its own.<br>

<br>
For example, OpenBSD was forked from NetBSD. =A0Who now has change control?=
 =A0Does that even mean anything?<br>
<br>
Apart from copyright matters, I think the only problem arises when there&#3=
9;s debate over whose version is the &quot;official&quot; one. =A0But that&=
#39;s a matter of the perception that exists outside of the two organizatio=
ns. =A0Otherwise, aren&#39;t they merely two perspectives on the same subje=
ct matter, and that&#39;s that?<br>

<font color=3D"#888888"><br>
-MSK<br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<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>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e644bc7681cb03049a4da474--

From msk@cloudmark.com  Thu Jan 20 13:55:12 2011
Return-Path: <msk@cloudmark.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 564273A6839 for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 13:55:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.932
X-Spam-Level: 
X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-0.334, 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 sVnmQVnNOMuU for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 13:55:07 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.35]) by core3.amsl.com (Postfix) with ESMTP id 1DD0E3A684A for <ietf@ietf.org>; Thu, 20 Jan 2011 13:55:07 -0800 (PST)
Received: from EXCH-C2.corp.cloudmark.com ([172.22.1.74]) by malice.corp.cloudmark.com ([172.22.10.71]) with mapi; Thu, 20 Jan 2011 13:57:51 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Date: Thu, 20 Jan 2011 13:57:49 -0800
Subject: RE: Change control
Thread-Topic: Change control
Thread-Index: Acu450MAjBGvRVCJS/eishJ95kr8TAABQJUw
Message-ID: <F5833273385BB34F99288B3648C4F06F1341E73F7C@EXCH-C2.corp.cloudmark.com>
References: <6.2.5.6.2.20110119072819.07795bc0@elandnews.com> <AANLkTim6b-_=r7MbT12VRv69d=QMJSU0+G+ze2PFry3M@mail.gmail.com> <6.2.5.6.2.20110119153443.07737800@resistor.net> <F5833273385BB34F99288B3648C4F06F1341E73F6E@EXCH-C2.corp.cloudmark.com> <AANLkTimp9_sBmy5emNbsmSTZtt9TOqEspOppdn-B+7=q@mail.gmail.com>
In-Reply-To: <AANLkTimp9_sBmy5emNbsmSTZtt9TOqEspOppdn-B+7=q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_F5833273385BB34F99288B3648C4F06F1341E73F7CEXCHC2corpclo_"
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, 20 Jan 2011 21:55:12 -0000

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

The only thing I can dream up (without an example) is that the submitting o=
rganization's version of something and the IETF's version end up diverging,=
 and the submitting organization doesn't like that.  To wit, the submitting=
 organization wanted the added credibility of the "RFC" label without any s=
ubstantive changes to the material.  But that strikes me as a failure of du=
e diligence more than anything.

Caveat emptor.


From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
Sent: Thursday, January 20, 2011 1:16 PM
To: Murray S. Kucherawy
Cc: ietf@ietf.org
Subject: Re: Change control

That is why I really want to see a specific example of harm (which I note S=
M has refused to do).

This is the sort of case where it is very easy to make the wrong decision i=
f people are allowed to waffle on about what they imagine to be high princi=
ple when the rules were made the way they are to support important real wor=
ld requirements.

If we are to discuss this further, I want to see an example.

<eom>

On Thu, Jan 20, 2011 at 3:53 PM, Murray S. Kucherawy <msk@cloudmark.com<mai=
lto:msk@cloudmark.com>> wrote:
To be honest, I'm not even clear on what the issue is.

If an organization creates a BCP in its own context based on the experience=
s of its constituents, and then the IETF uses that material to inform its o=
wn BCP on the same subject, and reasonable permission and attribution are g=
iven, what constitutes "change control"?  The IETF controls its version, an=
d the other organization controls its own.

For example, OpenBSD was forked from NetBSD.  Who now has change control?  =
Does that even mean anything?

Apart from copyright matters, I think the only problem arises when there's =
debate over whose version is the "official" one.  But that's a matter of th=
e perception that exists outside of the two organizations.  Otherwise, aren=
't they merely two perspectives on the same subject matter, and that's that=
?

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



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

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUI=
V=3D"Content-Type" CONTENT=3D"text/html; charset=3Dus-ascii"><meta name=3DG=
enerator 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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The only =
thing I can dream up (without an example) is that the submitting organizati=
on&#8217;s version of something and the IETF&#8217;s version end up divergi=
ng, and the submitting organization doesn&#8217;t like that.&nbsp; To wit, =
the submitting organization wanted the added credibility of the &#8220;RFC&=
#8221; label without any substantive changes to the material.&nbsp; But tha=
t strikes me as a failure of due diligence more than anything.<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"=
Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'>Caveat emptor.<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:=
#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fo=
nt-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp=
;</o:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;pa=
dding:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B=
5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Phillip Ha=
llam-Baker [mailto:hallam@gmail.com] <br><b>Sent:</b> Thursday, January 20,=
 2011 1:16 PM<br><b>To:</b> Murray S. Kucherawy<br><b>Cc:</b> ietf@ietf.org=
<br><b>Subject:</b> Re: Change control<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>That is why I r=
eally want to see a specific example of harm (which I note SM has refused t=
o do).<o:p></o:p></p><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><=
div><p class=3DMsoNormal>This is the sort of case where it is very easy to =
make the wrong decision if people are allowed to waffle on about what they =
imagine to be high principle when the rules were made the way they are to s=
upport important real world requirements.<o:p></o:p></p></div><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>If we are=
 to discuss this further, I want to see an example.<o:p></o:p></p></div><di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal=
>&lt;eom&gt;<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-=
bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Thu, Jan 2=
0, 2011 at 3:53 PM, Murray S. Kucherawy &lt;<a href=3D"mailto:msk@cloudmark=
.com">msk@cloudmark.com</a>&gt; wrote:<o:p></o:p></p><p class=3DMsoNormal>T=
o be honest, I'm not even clear on what the issue is.<br><br>If an organiza=
tion creates a BCP in its own context based on the experiences of its const=
ituents, and then the IETF uses that material to inform its own BCP on the =
same subject, and reasonable permission and attribution are given, what con=
stitutes &quot;change control&quot;? &nbsp;The IETF controls its version, a=
nd the other organization controls its own.<br><br>For example, OpenBSD was=
 forked from NetBSD. &nbsp;Who now has change control? &nbsp;Does that even=
 mean anything?<br><br>Apart from copyright matters, I think the only probl=
em arises when there's debate over whose version is the &quot;official&quot=
; one. &nbsp;But that's a matter of the perception that exists outside of t=
he two organizations. &nbsp;Otherwise, aren't they merely two perspectives =
on the same subject matter, and that's that?<br><span style=3D'color:#88888=
8'><br>-MSK</span><o:p></o:p></p><div><div><p class=3DMsoNormal>___________=
____________________________________<br>Ietf mailing list<br><a href=3D"mai=
lto:Ietf@ietf.org">Ietf@ietf.org</a><br><a href=3D"https://www.ietf.org/mai=
lman/listinfo/ietf" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/ietf</a><o:p></o:p></p></div></div></div><p class=3DMsoNormal style=3D'mar=
gin-bottom:12.0pt'><br><br clear=3Dall><br>-- <br>Website: <a href=3D"http:=
//hallambaker.com/">http://hallambaker.com/</a><o:p></o:p></p></div></div><=
/div></body></html>=

--_000_F5833273385BB34F99288B3648C4F06F1341E73F7CEXCHC2corpclo_--

From ted.ietf@gmail.com  Thu Jan 20 17:11:16 2011
Return-Path: <ted.ietf@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 53A133A688C for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 17:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.962
X-Spam-Level: 
X-Spam-Status: No, score=-2.962 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, J_CHICKENPOX_55=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 BA5NiIHaSGPZ for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 17:11:05 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id D66A63A6897 for <ietf@ietf.org>; Thu, 20 Jan 2011 17:11:03 -0800 (PST)
Received: by qwi2 with SMTP id 2so1319889qwi.31 for <ietf@ietf.org>; Thu, 20 Jan 2011 17:13:47 -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=ly7fTT1Skzc4Lk4z3NVlfKWwdBSd66knARh2tMKsoMQ=; b=N6untS4iZ7+1+xxLRiWwuqvPHaDqZNtFRAC3O9ntpsKN4voU9eVh2uXas1YNEtSTm4 jHFqSD4TQc1HXOaZV7Mwg8xAGYKobGN4lJTjSGjKFakIPaTVB2njGebt2zccKArRoXjA /L16aSbupbXHl2e6T38aSi1ftpUhf/IHc60Yg=
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=IJ73kW9/4ZA/OSmZBaPWNoXkyyGfB8TIzD1yZevTs7u7UPkGUadn1jFlpsKIdd4JTv 7t2b/d6j28+5YjfeZw10xZyRbLs1MiGW8frCK4u9/KHCoX6BP3whW7S4oHeQUJ/R9KUn XLn3J1mknONbYIHrBTkUMCfqQBUUj10n6CsJo=
MIME-Version: 1.0
Received: by 10.229.189.20 with SMTP id dc20mr2269815qcb.231.1295572427733; Thu, 20 Jan 2011 17:13:47 -0800 (PST)
Received: by 10.229.230.138 with HTTP; Thu, 20 Jan 2011 17:13:47 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20110120110057.0d0f5228@resistor.net>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net>
Date: Thu, 20 Jan 2011 17:13:47 -0800
Message-ID: <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Ted Hardie <ted.ietf@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 21 Jan 2011 01:11:16 -0000

I agree with SM's concern that the mechanism by which this is
extended is underspecified.  The draft contains one reserved
token, "blank", and a set of examples which make clear that there
is an unwritten set of known and unknown tokens which populate the "segment=
"
portion of the given ABNF.  Providing a registry for those tokens,
possibly with simple "reserved" status if no specification exists, might
help.  Standardizing a method for querying what about: tokens are
available in a specific context might as well (about:about, for example,
or about:?about).

But the reality is that the behavior resulting from these URIs is totally
non-deterministic and varies from context to context.  In most contexts
outside of a browser location bar, they are meaningless. Inside that
context, the browser's definition seems to be definitive.  If the aim
is only to get about:blank fully specified, I'd suggest saying so outright,
and noting clearly that all other uses are context-dependent, with
returning about:blank recommended practice  for those unknown.

As a thought experiment, would the W3C counsel against the presence
of an about URI in an XML namespace?

Additionally, naming a change controller should generally be a bit more
precise than an organization name.  The W3C director or TAG seems
more appropriate than just "W3C".

regards,

Ted Hardie

On Thu, Jan 20, 2011 at 11:18 AM, SM <sm@resistor.net> wrote:
> At 07:56 14-01-11, The IESG wrote:
>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'The 'about' URI scheme'
>> =A0<draft-holsten-about-uri-scheme-06.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
>
> There is a IANA registration in Section 8. =A0The arguments at
> http://www.ietf.org/mail-archive/web/ietf/current/msg65163.html are also
> applicable to draft-holsten-about-uri-scheme-06.
>
> In Section 5.2:
>
> =A0"Applications MAY resolve any unreserved "about" URI to any resource,
> =A0 either internal or external, or redirect to an alternative URI."
>
> What happens when the unreserved "about" URI becomes a reserved "about" U=
RI
> in future?
>
> Regards,
> -sm
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From jmpolk@cisco.com  Thu Jan 20 17:49:10 2011
Return-Path: <jmpolk@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 EEDF63A6897; Thu, 20 Jan 2011 17:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.525
X-Spam-Level: 
X-Spam-Status: No, score=-110.525 tagged_above=-999 required=5 tests=[AWL=0.074, 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 KdfQXoQ25SzZ; Thu, 20 Jan 2011 17:49:09 -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 385BB3A67AA; Thu, 20 Jan 2011 17:49:09 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEABZ1OE2rR7H+/2dsb2JhbACkYXOkI5sKhVAEhG8
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 21 Jan 2011 01:51:53 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8716.cisco.com [10.99.80.23]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0L1pqVe014924; Fri, 21 Jan 2011 01:51:53 GMT
Message-Id: <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 20 Jan 2011 19:51:51 -0600
To: IETF Administrative Director <iad@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: IETF 83 Venue 
In-Reply-To: <20110119213125.E3D2228C0F4@core3.amsl.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: iesg@ietf.org, iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@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, 21 Jan 2011 01:49:10 -0000

At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
>The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
>March 2012.  The IETF last met in the city in 2005 at IETF 63.
>
>Paris was the number one choice for a European venue in a venue
>preference survey conducted after IETF 78.

I don't know about this... after all, the last time we had an IETF 
there is when EKR blew a gasket at the lack of (real) cookies during 
the breaks. This cannot be overlooked as an isolated incident, or 
hand-waved away.  I wouldn't want to be around him if this were to occur again.

;-)

James

>2012
>IETF 83  Paris 25 - 30 March    Host:  <your name here>


From narten@us.ibm.com  Thu Jan 20 21:55:36 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 0003F3A68BB for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 21:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.96
X-Spam-Level: 
X-Spam-Status: No, score=-104.96 tagged_above=-999 required=5 tests=[AWL=-0.661, 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 qzJLmwQPUIhF for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 21:55:34 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by core3.amsl.com (Postfix) with ESMTP id 9CF753A68C0 for <ietf@ietf.org>; Thu, 20 Jan 2011 21:55:34 -0800 (PST)
Received: from d01dlp01.pok.ibm.com (d01dlp01.pok.ibm.com [9.56.224.56]) by e8.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p0L5ZbDe004751 for <ietf@ietf.org>; Fri, 21 Jan 2011 00:35:37 -0500
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id B49B1728045 for <ietf@ietf.org>; Fri, 21 Jan 2011 00:53:04 -0500 (EST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p0L5r4qp483338 for <ietf@ietf.org>; Fri, 21 Jan 2011 00:53:04 -0500
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p0L5r3RR004677 for <ietf@ietf.org>; Thu, 20 Jan 2011 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p0L5r3PC004330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 20 Jan 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 p0L5r2hp004821 for <ietf@ietf.org>; Fri, 21 Jan 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p0L5r28p004782 for ietf@ietf.org; Fri, 21 Jan 2011 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201101210553.p0L5r28p004782@rotala.raleigh.ibm.com>
Date: Fri, 21 Jan 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-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, 21 Jan 2011 05:55:36 -0000

Total of 73 messages in the last 7 days.
 
script run at: Fri Jan 21 00:53:02 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.70% |   10 | 16.89% |   108644 | hallam@gmail.com
  8.22% |    6 | 11.13% |    71600 | lars.eggert@nokia.com
  2.74% |    2 | 12.02% |    77333 | jpv@cisco.com
  5.48% |    4 |  3.00% |    19280 | julian.reschke@gmx.de
  4.11% |    3 |  2.93% |    18861 | sm@resistor.net
  4.11% |    3 |  2.86% |    18371 | daedulus@btconnect.com
  4.11% |    3 |  2.69% |    17312 | mrex@sap.com
  4.11% |    3 |  2.31% |    14854 | dworley@avaya.com
  1.37% |    1 |  4.66% |    29945 | ron.even.tlv@gmail.com
  2.74% |    2 |  3.12% |    20038 | msk@cloudmark.com
  2.74% |    2 |  2.69% |    17290 | olaf@nlnetlabs.nl
  2.74% |    2 |  1.58% |    10179 | doug@ewellic.org
  2.74% |    2 |  1.52% |     9808 | vesely@tana.it
  1.37% |    1 |  2.36% |    15165 | krishnabirth@gmail.com
  1.37% |    1 |  2.21% |    14246 | jmabdp@gmail.com
  1.37% |    1 |  2.11% |    13568 | lixia@cs.ucla.edu
  1.37% |    1 |  1.97% |    12698 | spencer@wonderhamster.org
  1.37% |    1 |  1.57% |    10074 | matthew.bocci@alcatel-lucent.com
  1.37% |    1 |  1.37% |     8834 | lear@cisco.com
  1.37% |    1 |  1.32% |     8505 | tme@americafree.tv
  1.37% |    1 |  1.22% |     7834 | narten@us.ibm.com
  1.37% |    1 |  1.19% |     7658 | chris.dearlove@baesystems.com
  1.37% |    1 |  1.09% |     6994 | ted.ietf@gmail.com
  1.37% |    1 |  1.02% |     6569 | xavier.marjou@gmail.com
  1.37% |    1 |  0.99% |     6362 | d3e3e3@gmail.com
  1.37% |    1 |  0.95% |     6105 | evnikita2@gmail.com
  1.37% |    1 |  0.93% |     5991 | jhutz@cmu.edu
  1.37% |    1 |  0.90% |     5786 | dhc2@dcrocker.net
  1.37% |    1 |  0.84% |     5407 | ned+ietf@mauve.mrochek.com
  1.37% |    1 |  0.84% |     5384 | ebw@abenaki.wabanaki.net
  1.37% |    1 |  0.83% |     5316 | paul@xelerance.com
  1.37% |    1 |  0.82% |     5301 | marc.blanchet@viagenie.ca
  1.37% |    1 |  0.82% |     5246 | chair@ietf.org
  1.37% |    1 |  0.81% |     5241 | paul.hoffman@vpnc.org
  1.37% |    1 |  0.81% |     5217 | michal@krsek.cz
  1.37% |    1 |  0.77% |     4924 | alexey.melnikov@isode.com
  1.37% |    1 |  0.76% |     4874 | bmanning@isi.edu
  1.37% |    1 |  0.74% |     4773 | erosen@cisco.com
  1.37% |    1 |  0.70% |     4510 | jabley@hopcount.ca
  1.37% |    1 |  0.70% |     4506 | jmpolk@cisco.com
  1.37% |    1 |  0.69% |     4452 | iljitsch@muada.com
  1.37% |    1 |  0.69% |     4423 | dot@dotat.at
  1.37% |    1 |  0.59% |     3769 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |   73 |100.00% |   643247 | Total

From evnikita2@gmail.com  Thu Jan 20 23:37:48 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 2BA753A68E2 for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 23:37:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.68
X-Spam-Level: 
X-Spam-Status: No, score=-3.68 tagged_above=-999 required=5 tests=[AWL=-0.681,  BAYES_00=-2.599, J_CHICKENPOX_55=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 eVEyD865fd3s for <ietf@core3.amsl.com>; Thu, 20 Jan 2011 23:37:47 -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 2416C3A68E1 for <ietf@ietf.org>; Thu, 20 Jan 2011 23:37:47 -0800 (PST)
Received: by yxt33 with SMTP id 33so505085yxt.31 for <ietf@ietf.org>; Thu, 20 Jan 2011 23:40:32 -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=ljL/NAmQ3pMJIOkPL5hY4ItwpktfFx8mJAUEeZPnsVE=; b=VQMzwi08TC/76YmNHv20BvcpReT0ZKYgBhpRVPxDN1oXAVynXXihYBRnZFt1FpsIcX 4HenD9i8eoSq4xEwyu+dvdAt1Y/lbuM0dWmUKockrATGOZv76H5fbL0eViKKSt6cP8zf ObMZJk9lLCVDFh1J3WkFzI+6Aqc1OHJzluVdA=
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=XSeDHB70cky2tRVykb7SFeLa/g7s6K25tXqOkN2C/+Hv7qc1snjCHBMTcpq8G504bg dwZ5Jg5y1MjCR3JhDhLAuoiFuY9ALLultsBFVKPX4riZFqW1oMClmUDNnBldrmmNKtDK EZPQUPQGmMH57aenlHTsQa6KsF2U0FcGEfIMY=
MIME-Version: 1.0
Received: by 10.150.91.10 with SMTP id o10mr318662ybb.440.1295595632000; Thu, 20 Jan 2011 23:40:32 -0800 (PST)
Received: by 10.150.53.6 with HTTP; Thu, 20 Jan 2011 23:40:31 -0800 (PST)
In-Reply-To: <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net> <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>
Date: Fri, 21 Jan 2011 09:40:31 +0200
Message-ID: <AANLkTimq8UfAwP0UHD3BQ=3JfAA4dDNP4=b1DiOgQ4DL@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, 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, 21 Jan 2011 07:37:48 -0000

2011/1/21, Ted Hardie <ted.ietf@gmail.com>:
> I agree with SM's concern that the mechanism by which this is
> extended is underspecified.  The draft contains one reserved
> token, "blank", and a set of examples which make clear that there
> is an unwritten set of known and unknown tokens which populate the "segment"
> portion of the given ABNF.  Providing a registry for those tokens,
> possibly with simple "reserved" status if no specification exists, might
> help.  Standardizing a method for querying what about: tokens are
> available in a specific context might as well (about:about, for example,
> or about:?about).

Hello all,

I'd like to agree with the proposition to create the regsitry for
'about' URI tokens  That will allow to track what tokens become
'reserved', 'unreserved', etc. simplier.

Mykyta Yevstifeyev
>
> But the reality is that the behavior resulting from these URIs is totally
> non-deterministic and varies from context to context.  In most contexts
> outside of a browser location bar, they are meaningless. Inside that
> context, the browser's definition seems to be definitive.  If the aim
> is only to get about:blank fully specified, I'd suggest saying so outright,
> and noting clearly that all other uses are context-dependent, with
> returning about:blank recommended practice  for those unknown.
>
> As a thought experiment, would the W3C counsel against the presence
> of an about URI in an XML namespace?
>
> Additionally, naming a change controller should generally be a bit more
> precise than an organization name.  The W3C director or TAG seems
> more appropriate than just "W3C".
>
> regards,
>
> Ted Hardie
>
> On Thu, Jan 20, 2011 at 11:18 AM, SM <sm@resistor.net> wrote:
>> At 07:56 14-01-11, The IESG wrote:
>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'The 'about' URI scheme'
>>>  <draft-holsten-about-uri-scheme-06.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
>>
>> There is a IANA registration in Section 8.  The arguments at
>> http://www.ietf.org/mail-archive/web/ietf/current/msg65163.html are also
>> applicable to draft-holsten-about-uri-scheme-06.
>>
>> In Section 5.2:
>>
>>  "Applications MAY resolve any unreserved "about" URI to any resource,
>>   either internal or external, or redirect to an alternative URI."
>>
>> What happens when the unreserved "about" URI becomes a reserved "about"
>> URI
>> in future?
>>
>> Regards,
>> -sm
>>
>> _______________________________________________
>> 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 julian.reschke@gmx.de  Fri Jan 21 00:26:35 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 27A343A68EE for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 00:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.62
X-Spam-Level: 
X-Spam-Status: No, score=-103.62 tagged_above=-999 required=5 tests=[AWL=-1.621, BAYES_00=-2.599, J_CHICKENPOX_55=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 hLzNtVv-YKnH for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 00:26:34 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id A7C8B3A68E4 for <ietf@ietf.org>; Fri, 21 Jan 2011 00:26:33 -0800 (PST)
Received: (qmail invoked by alias); 21 Jan 2011 08:29:16 -0000
Received: from p508FC81C.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.200.28] by mail.gmx.net (mp007) with SMTP; 21 Jan 2011 09:29:16 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/CjHFDa7LCcNWXgcwZEOcKfj1wINoH3Um8fS6gKU tdwVmWJ+jZ9JqK
Message-ID: <4D3943C8.5010206@gmx.de>
Date: Fri, 21 Jan 2011 09:28:56 +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: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <20110114155632.17927.70550.idtracker@localhost>	<6.2.5.6.2.20110120110057.0d0f5228@resistor.net> <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>
In-Reply-To: <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, 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, 21 Jan 2011 08:26:35 -0000

On 21.01.2011 02:13, Ted Hardie wrote:
> ...
> But the reality is that the behavior resulting from these URIs is totally
> non-deterministic and varies from context to context.  In most contexts
> outside of a browser location bar, they are meaningless. Inside that
> context, the browser's definition seems to be definitive.  If the aim
> is only to get about:blank fully specified, I'd suggest saying so outright,
> and noting clearly that all other uses are context-dependent, with
> returning about:blank recommended practice  for those unknown.
> ...

That sounds reasonable. Let's not make it more complicated than it needs 
to be.

> As a thought experiment, would the W3C counsel against the presence
> of an about URI in an XML namespace?

Reminder: the reason this was written down was so that 
"about:legacy-compat" can be specified as XML system identifier in HTML5 
(<http://dev.w3.org/html5/spec/Overview.html#the-doctype>).

> Additionally, naming a change controller should generally be a bit more
> precise than an organization name.  The W3C director or TAG seems
> more appropriate than just "W3C".

I just checked an image/svg+xml has "W3C" as change controller. Why 
would the requirement be different here?

Best regards, Julian

From daedulus@btconnect.com  Fri Jan 21 04:15:47 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 455FA3A6949 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 04:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 3aWounBmeqRS for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 04:15:46 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id DC25E3A6944 for <ietf@ietf.org>; Fri, 21 Jan 2011 04:15:45 -0800 (PST)
Received: from host86-134-204-119.range86-134.btcentralplus.com (HELO pc6) ([86.134.204.119]) by c2beaomr07.btconnect.com with SMTP id BMB56493; Fri, 21 Jan 2011 12:18:26 +0000 (GMT)
Message-ID: <009901cbb95c$6eb24de0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <ietf@ietf.org>, "SM" <sm@resistor.net>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The'about' URI scheme) to Proposed Standard
Date: Fri, 21 Jan 2011 12:14:46 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4D397992.00BF, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4D397996.00DF,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
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, 21 Jan 2011 12:15:47 -0000

----- Original Message -----
From: "SM" <sm@resistor.net>
To: <ietf@ietf.org>
Sent: Thursday, January 20, 2011 8:18 PM
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The'about' URI
scheme) to Proposed Standard


> At 07:56 14-01-11, The IESG wrote:
>
> >The IESG has received a request from an individual submitter to consider
> >the following document:
> >- 'The 'about' URI scheme'
> >   <draft-holsten-about-uri-scheme-06.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
>
> There is a IANA registration in Section 8.  The arguments at
> http://www.ietf.org/mail-archive/web/ietf/current/msg65163.html are
> also applicable to draft-holsten-about-uri-scheme-06.

Further to that, I did ask IANA if, when carrying out the procedures of
registration in accordance with RFC4395, they performed any checks
on the contact details of the Change Controller for the URI.  So far,
I have heard no more so I am assuming that whatever the IETF and
IESG approves in the I-D is taken as gospel by IANA.

Tom Petch
>
> In Section 5.2:
>
>    "Applications MAY resolve any unreserved "about" URI to any resource,
>     either internal or external, or redirect to an alternative URI."
>
> What happens when the unreserved "about" URI becomes a reserved
> "about" URI in future?
>
> Regards,
> -sm
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From daedulus@btconnect.com  Fri Jan 21 04:44:05 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 9C1E43A6952 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 04:44:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id URlqIqFYGIHR for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 04:44:04 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr08.btconnect.com [213.123.26.186]) by core3.amsl.com (Postfix) with ESMTP id 4EE7B3A6950 for <ietf@ietf.org>; Fri, 21 Jan 2011 04:44:03 -0800 (PST)
Received: from host86-134-204-119.range86-134.btcentralplus.com (HELO pc6) ([86.134.204.119]) by c2beaomr08.btconnect.com with SMTP id BKE13836; Fri, 21 Jan 2011 12:46:47 +0000 (GMT)
Message-ID: <00ec01cbb960$6499ef80$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
References: <4D36A12C.9010301@ericsson.com>
Subject: 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
Date: Fri, 21 Jan 2011 12:43:07 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D398037.01A1, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr08.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0205.4D398038.00DC,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 <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, 21 Jan 2011 12:44:05 -0000

I would like to see more clarity in 8.1
" For assignments done through IETF-published RFCs, the Contact will be the
IESG."
in that I am unclear what IETF-published RFCs are; presumably that is Standards
Track, BCP
and Individual Submissions, but not Independent Submissions  or IRTF RFC.

I think that the terminology here should follow that of RFC4844 with a reference
thereto.

Tom Petch


----- Original Message -----
From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
To: <apps-discuss@ietf.org>; "Internet Area" <int-area@ietf.org>;
<rai-discuss@ietf.org>; <ops-area@ietf.org>; "SAAG" <saag@ieft.org>
Sent: Wednesday, January 19, 2011 9:30 AM
Subject: [apps-discuss] Fwd: 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


Hi,

I just want to make people aware of this IETF last call for an update of
the IANA procedures for registration of Service Name and Transport
protocol port numbers.

Best Regards

Magnus Westerlund

-------- Ursprungligt meddelande --------
Ämne: 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
Datum: Tue, 18 Jan 2011 22:26:03 +0100
Från: The IESG <iesg-secretary@ietf.org>
Till: IETF-Announce <ietf-announce@ietf.org>
Kopia: tsvwg@ietf.org <tsvwg@ietf.org>


The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document:
- 'Internet Assigned Numbers Authority (IANA) Procedures for the
   Management of the Service Name and Transport Protocol Port Number
   Registry'
  <draft-ietf-tsvwg-iana-ports-09.txt> as a BCP

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.

The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/


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

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss


From magnus.westerlund@ericsson.com  Fri Jan 21 04:47:55 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 1C3E23A6950; Fri, 21 Jan 2011 04:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.492
X-Spam-Level: 
X-Spam-Status: No, score=-106.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 c-fKaS-0Lcl9; Fri, 21 Jan 2011 04:47:54 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id AFC263A6958; Fri, 21 Jan 2011 04:47:53 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-1c-4d39811ebbc0
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 86.08.13987.E11893D4; Fri, 21 Jan 2011 13:50:38 +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; Fri, 21 Jan 2011 13:50:37 +0100
Message-ID: <4D39811D.6070208@ericsson.com>
Date: Fri, 21 Jan 2011 13:50:37 +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: "t.petch" <daedulus@btconnect.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: <4D36A12C.9010301@ericsson.com> <00ec01cbb960$6499ef80$4001a8c0@gateway.2wire.net>
In-Reply-To: <00ec01cbb960$6499ef80$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: AAAAAA==
Cc: ietf <ietf@ietf.org>, "port-srv-reg@ietf.org" <port-srv-reg@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, 21 Jan 2011 12:47:55 -0000

t.petch skrev 2011-01-21 12:43:
> I would like to see more clarity in 8.1
> " For assignments done through IETF-published RFCs, the Contact will be the
> IESG."
> in that I am unclear what IETF-published RFCs are; presumably that is Standards
> Track, BCP
> and Individual Submissions, but not Independent Submissions  or IRTF RFC.
> 
> I think that the terminology here should follow that of RFC4844 with a reference
> thereto.
> 

I guess we should use the "IETF Stream", and I do agree that a reference
for the definition of that should be included.

Cheers

Magnus

> Tom Petch
> 
> 
> ----- Original Message -----
> From: "Magnus Westerlund" <magnus.westerlund@ericsson.com>
> To: <apps-discuss@ietf.org>; "Internet Area" <int-area@ietf.org>;
> <rai-discuss@ietf.org>; <ops-area@ietf.org>; "SAAG" <saag@ieft.org>
> Sent: Wednesday, January 19, 2011 9:30 AM
> Subject: [apps-discuss] Fwd: 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
> 
> 
> Hi,
> 
> I just want to make people aware of this IETF last call for an update of
> the IANA procedures for registration of Service Name and Transport
> protocol port numbers.
> 
> Best Regards
> 
> Magnus Westerlund
> 
> -------- Ursprungligt meddelande --------
> Ämne: 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
> Datum: Tue, 18 Jan 2011 22:26:03 +0100
> Från: The IESG <iesg-secretary@ietf.org>
> Till: IETF-Announce <ietf-announce@ietf.org>
> Kopia: tsvwg@ietf.org <tsvwg@ietf.org>
> 
> 
> The IESG has received a request from the Transport Area Working Group WG
> (tsvwg) to consider the following document:
> - 'Internet Assigned Numbers Authority (IANA) Procedures for the
>    Management of the Service Name and Transport Protocol Port Number
>    Registry'
>   <draft-ietf-tsvwg-iana-ports-09.txt> as a BCP
> 
> 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.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-tsvwg-iana-ports/
> 
> 
> 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
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
> 
> 


-- 

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 hallam@gmail.com  Fri Jan 21 05:02:52 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 5C9A03A6952 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 05:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[AWL=0.131,  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 tkMvw7rywRC4 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 05:02:49 -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 2BB163A6911 for <ietf@ietf.org>; Fri, 21 Jan 2011 05:02:49 -0800 (PST)
Received: by yie19 with SMTP id 19so585918yie.31 for <ietf@ietf.org>; Fri, 21 Jan 2011 05:05:34 -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=K4+tDxjaDjokz4ydZutboTX1Svn0kkw26hkaqKfaDck=; b=jQ47gVdgQljBzvGoxM+V3Is48B1yQgbqBmj6RHw2xueCSIicKCt+qbsxsJvK1amlIu royltYxLXjmuzGCIA9QCypKd7I+8VD/2Hv/OFR6Hs6hsf6vwKGrYrJwidm+odWRt7L/o VLxL9kQG5LTpLkv9H/WjVCUd01uuxgb92y+jc=
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=QSYn0rBkSQsvB7x9oa05P0hgGh13pLNXaxww9F1ufn42HpcXlUYR1u932biLCEDiko 4Ddb0jwNfFSls49y71HfikIgj7lKdZ8t/Gr6WtCAgs4sMh1ICiDMmKeOHRni1jsKr6Ja w68gO+80HT7Wfu3CNfsoQ0EgzZ14KYSs2WpbQ=
MIME-Version: 1.0
Received: by 10.100.44.17 with SMTP id r17mr451126anr.222.1295615134594; Fri, 21 Jan 2011 05:05:34 -0800 (PST)
Received: by 10.101.71.15 with HTTP; Fri, 21 Jan 2011 05:05:34 -0800 (PST)
In-Reply-To: <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
Date: Fri, 21 Jan 2011 08:05:34 -0500
Message-ID: <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "James M. Polk" <jmpolk@cisco.com>
Content-Type: multipart/alternative; boundary=0016e644bc76dcf65e049a5ae71d
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, 21 Jan 2011 13:02:52 -0000

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

No, that was Prague '68
http://www.ietf.org/proceedings/68/plenaryw.html

I think the issue there was that we were in one of the cheapest cities in
Europe to buy food outside the hotel and the prices inside the hotel were
much higher than for other hotels in European capitals for Communist era
quality food.



On Thu, Jan 20, 2011 at 8:51 PM, James M. Polk <jmpolk@cisco.com> wrote:

> At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
>
>> The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
>> March 2012.  The IETF last met in the city in 2005 at IETF 63.
>>
>> Paris was the number one choice for a European venue in a venue
>> preference survey conducted after IETF 78.
>>
>
> I don't know about this... after all, the last time we had an IETF there is
> when EKR blew a gasket at the lack of (real) cookies during the breaks. This
> cannot be overlooked as an isolated incident, or hand-waved away.  I
> wouldn't want to be around him if this were to occur again.
>
> ;-)
>
> James
>
>
>  2012
>> IETF 83  Paris 25 - 30 March    Host:  <your name here>
>>
>
>


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

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

No, that was Prague &#39;68<div><a href=3D"http://www.ietf.org/proceedings/=
68/plenaryw.html">http://www.ietf.org/proceedings/68/plenaryw.html</a></div=
><div><br></div><div>I think the issue there was that we were in one of the=
 cheapest cities in Europe to buy food outside the hotel and the prices ins=
ide the hotel were much higher than for other hotels in European capitals f=
or Communist era quality food.</div>
<div><br></div><div><br><br><div class=3D"gmail_quote">On Thu, Jan 20, 2011=
 at 8:51 PM, James M. Polk <span dir=3D"ltr">&lt;<a href=3D"mailto:jmpolk@c=
isco.com">jmpolk@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex;">
<div class=3D"im">At 03:31 PM 1/19/2011, IETF Administrative Director wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30<=
br>
March 2012. =A0The IETF last met in the city in 2005 at IETF 63.<br>
<br>
Paris was the number one choice for a European venue in a venue<br>
preference survey conducted after IETF 78.<br>
</blockquote>
<br></div>
I don&#39;t know about this... after all, the last time we had an IETF ther=
e is when EKR blew a gasket at the lack of (real) cookies during the breaks=
. This cannot be overlooked as an isolated incident, or hand-waved away. =
=A0I wouldn&#39;t want to be around him if this were to occur again.<br>

<br>
;-)<br><font color=3D"#888888">
<br>
James</font><div><div></div><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
2012<br>
IETF 83 =A0Paris 25 - 30 March =A0 =A0Host: =A0&lt;your name here&gt;<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e644bc76dcf65e049a5ae71d--

From joao@bondis.org  Fri Jan 21 05:19:01 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 09A543A6914 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 05:19:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.527
X-Spam-Level: 
X-Spam-Status: No, score=-1.527 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3]
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 cS0847HciXGj for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 05:19:00 -0800 (PST)
Received: from smtp1.bondis.org (voyager.c-l-i.net [194.176.119.229]) by core3.amsl.com (Postfix) with ESMTP id 059583A68FE for <ietf@ietf.org>; Fri, 21 Jan 2011 05:18:59 -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 DE20F1AB301; Fri, 21 Jan 2011 13:21:43 +0000 (UTC)
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com>
In-Reply-To: <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
Message-Id: <49C83D1E-EA87-4103-8596-7BEB2FEE510D@bondis.org>
Content-Transfer-Encoding: quoted-printable
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
Subject: Re: IETF 83 Venue
Date: Fri, 21 Jan 2011 14:21:43 +0100
To: Phillip Hallam-Baker <hallam@gmail.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: Fri, 21 Jan 2011 13:19:01 -0000

On 21 Jan 2011, at 14:05, Phillip Hallam-Baker wrote:

> No, that was Prague '68

you mean IETF 68 in Prague. Prague '68 refers to rather different events =
in this corner of the world.

Joao


From michal@krsek.cz  Fri Jan 21 05:37:18 2011
Return-Path: <michal@krsek.cz>
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 F404D3A6916 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 05:37:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.189
X-Spam-Level: 
X-Spam-Status: No, score=0.189 tagged_above=-999 required=5 tests=[AWL=1.438,  BAYES_00=-2.599, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, 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 QDsO5jhlURUg for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 05:37:16 -0800 (PST)
Received: from io.pinknet.cz (io.pinknet.cz [217.31.57.96]) by core3.amsl.com (Postfix) with ESMTP id 6B5523A6914 for <ietf@ietf.org>; Fri, 21 Jan 2011 05:37:16 -0800 (PST)
Received: from [195.113.228.228] (michal-xp.w2lan.cesnet.cz [195.113.228.228]) by io.pinknet.cz (Postfix) with ESMTP id A832323B026; Fri, 21 Jan 2011 14:44:37 +0100 (CET)
Message-ID: <4D398CAF.5010906@krsek.cz>
Date: Fri, 21 Jan 2011 14:39:59 +0100
From: Michal Krsek <michal@krsek.cz>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IETF 83 Venue
References: <20110119213125.E3D2228C0F4@core3.amsl.com>	<201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com>
In-Reply-To: <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030706000201050209080606"
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, 21 Jan 2011 13:37:18 -0000

This is a multi-part message in MIME format.
--------------030706000201050209080606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Phillip,
as a person living in Prague I have to say that if you want to have 
western style services, you need to pay western (or higher) prices.

Please be sure local community spend last time some time to crawl around 
conference hotel talking to the management about "large group of english 
speaking people is comming, please have somebody understanding basics of 
english and have english menu ready". Without this crawling, some 
services shall be somehow ... ehm ...

And ... Prague isn't one of cheapest cities in Europe. It is in middle 
tier of the european capitals and more expensive than some regions of 
Germany/France/UK.

It seems like Prague city council marketing has too much pink color :-) 
Anyway, we are trying to do our best to make next IETF even better than 
'68 (but, we have no responsibility on cookies - yet?).

             Michal


> No, that was Prague '68
> http://www.ietf.org/proceedings/68/plenaryw.html
>
> I think the issue there was that we were in one of the cheapest cities 
> in Europe to buy food outside the hotel and the prices inside the 
> hotel were much higher than for other hotels in European capitals for 
> Communist era quality food.
>
>
>
> On Thu, Jan 20, 2011 at 8:51 PM, James M. Polk <jmpolk@cisco.com 
> <mailto:jmpolk@cisco.com>> wrote:
>
>     At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
>
>         The IAOC is pleased to announce Paris as the site for IETF 83
>         from 25 - 30
>         March 2012.  The IETF last met in the city in 2005 at IETF 63.
>
>         Paris was the number one choice for a European venue in a venue
>         preference survey conducted after IETF 78.
>
>
>     I don't know about this... after all, the last time we had an IETF
>     there is when EKR blew a gasket at the lack of (real) cookies
>     during the breaks. This cannot be overlooked as an isolated
>     incident, or hand-waved away.  I wouldn't want to be around him if
>     this were to occur again.
>
>     ;-)
>
>     James
>
>
>         2012
>         IETF 83  Paris 25 - 30 March    Host: <your name here>
>
>
>
>
>
> -- 
> Website: http://hallambaker.com/
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

--------------030706000201050209080606
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 text="#000000" bgcolor="#ffffff">
    Hi Phillip,<br>
    as a person living in Prague I have to say that if you want to have
    western style services, you need to pay western (or higher) prices.
    <br>
    <br>
    Please be sure local community spend last time some time to crawl
    around conference hotel talking to the management about "large group
    of english speaking people is comming, please have somebody
    understanding basics of english and have english menu ready".
    Without this crawling, some services shall be somehow ... ehm ...<br>
    <br>
    And ... Prague isn't one of cheapest cities in Europe. It is in
    middle tier of the european capitals and more expensive than some
    regions of Germany/France/UK. <br>
    <br>
    It seems like Prague city council marketing has too much pink color
    :-) Anyway, we are trying to do our best to make next IETF even
    better than '68 (but, we have no responsibility on cookies - yet?).<br>
    <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Michal<br>
    <br>
    <br>
    <blockquote
      cite="mid:AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com"
      type="cite">No, that was Prague '68
      <div><a moz-do-not-send="true"
          href="http://www.ietf.org/proceedings/68/plenaryw.html">http://www.ietf.org/proceedings/68/plenaryw.html</a></div>
      <div><br>
      </div>
      <div>I think the issue there was that we were in one of the
        cheapest cities in Europe to buy food outside the hotel and the
        prices inside the hotel were much higher than for other hotels
        in European capitals for Communist era quality food.</div>
      <div><br>
      </div>
      <div><br>
        <br>
        <div class="gmail_quote">On Thu, Jan 20, 2011 at 8:51 PM, James
          M. Polk <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:jmpolk@cisco.com">jmpolk@cisco.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
            0.8ex; border-left: 1px solid rgb(204, 204, 204);
            padding-left: 1ex;">
            <div class="im">At 03:31 PM 1/19/2011, IETF Administrative
              Director wrote:<br>
              <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
                0.8ex; border-left: 1px solid rgb(204, 204, 204);
                padding-left: 1ex;">
                The IAOC is pleased to announce Paris as the site for
                IETF 83 from 25 - 30<br>
                March 2012. &nbsp;The IETF last met in the city in 2005 at
                IETF 63.<br>
                <br>
                Paris was the number one choice for a European venue in
                a venue<br>
                preference survey conducted after IETF 78.<br>
              </blockquote>
              <br>
            </div>
            I don't know about this... after all, the last time we had
            an IETF there is when EKR blew a gasket at the lack of
            (real) cookies during the breaks. This cannot be overlooked
            as an isolated incident, or hand-waved away. &nbsp;I wouldn't
            want to be around him if this were to occur again.<br>
            <br>
            ;-)<br>
            <font color="#888888">
              <br>
              James</font>
            <div>
              <div class="h5"><br>
                <br>
                <blockquote class="gmail_quote" style="margin: 0pt 0pt
                  0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
                  padding-left: 1ex;">
                  2012<br>
                  IETF 83 &nbsp;Paris 25 - 30 March &nbsp; &nbsp;Host: &nbsp;&lt;your name
                  here&gt;<br>
                </blockquote>
                <br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
        <br clear="all">
        <br>
        -- <br>
        Website: <a moz-do-not-send="true"
          href="http://hallambaker.com/">http://hallambaker.com/</a><br>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Ietf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
    </blockquote>
  </body>
</html>

--------------030706000201050209080606--

From mary.ietf.barnes@gmail.com  Fri Jan 21 08:01:28 2011
Return-Path: <mary.ietf.barnes@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 8E3343A6A36; Fri, 21 Jan 2011 08:01:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.306
X-Spam-Level: 
X-Spam-Status: No, score=-103.306 tagged_above=-999 required=5 tests=[AWL=0.292, 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 PUrdQK8Jj+me; Fri, 21 Jan 2011 08:01:27 -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 5770C3A6A35; Fri, 21 Jan 2011 08:01:27 -0800 (PST)
Received: by yxt33 with SMTP id 33so645960yxt.31 for <multiple recipients>; Fri, 21 Jan 2011 08:04:13 -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=hMB4sA/b0JgF4gFUDUvvWtwa490ir0S4N4CLyI9LGYg=; b=xO+QQxMIRCLB6Ld6V986gTn2fvxiB847txEgWCVC8vCqcbG/edt5Blli/0d7Jz2FXX Z+ukAonsYAlXC7Sxcb9Pm6nqHkIoaf4qn2rzywAe0H7RhdG+IyQWTMW6DGMCCAVwBLZM wluGfgwtET5O3Shu957r7GSNQ1z7Hlfxfisao=
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=bpYETyI2mfzuc/dUvJ1hLi5droS7TYdbsN2BMzPjXN91Ng8RE+5SyMSGioo3dMHawj QzlJGQR0eHpQ5lTY5xbReCKQl3kw24JJebtJHUeEyo7F01MkbUk2beaOru7bo2kW5dH6 2yIp91SKsqSLOkyq7FxIHCMx6kIWeXG740Fl4=
MIME-Version: 1.0
Received: by 10.42.173.71 with SMTP id q7mr1001487icz.65.1295625852971; Fri, 21 Jan 2011 08:04:12 -0800 (PST)
Received: by 10.42.202.12 with HTTP; Fri, 21 Jan 2011 08:04:12 -0800 (PST)
In-Reply-To: <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com>
Date: Fri, 21 Jan 2011 10:04:12 -0600
Message-ID: <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "James M. Polk" <jmpolk@cisco.com>
Content-Type: multipart/alternative; boundary=90e6ba6e8d2aba6c6f049a5d66bd
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@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, 21 Jan 2011 16:01:28 -0000

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

If it's the same conference center that we were at for IETF-63, there should
be few complaints about food given that there is a very nice (real) food
market in the shopping area in the Palais de Congres - i.e., if there aren't
enough cookies for you at the meeting, then you can go buy a whole package
at the food market.

Mary.

On Thu, Jan 20, 2011 at 7:51 PM, James M. Polk <jmpolk@cisco.com> wrote:

> At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
>
>> The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30
>> March 2012.  The IETF last met in the city in 2005 at IETF 63.
>>
>> Paris was the number one choice for a European venue in a venue
>> preference survey conducted after IETF 78.
>>
>
> I don't know about this... after all, the last time we had an IETF there is
> when EKR blew a gasket at the lack of (real) cookies during the breaks. This
> cannot be overlooked as an isolated incident, or hand-waved away.  I
> wouldn't want to be around him if this were to occur again.
>
> ;-)
>
> James
>
>
>  2012
>> IETF 83  Paris 25 - 30 March    Host:  <your name here>
>>
>
>

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

If it&#39;s the same conference center that we were at for IETF-63, there s=
hould be few complaints about food given that there is a very nice (real) f=
ood market in the shopping area in the Palais de Congres - i.e., if there a=
ren&#39;t enough cookies for you at the meeting, then you can go buy a whol=
e package at the food market.<div>
<br></div><div>Mary.<br><div><br></div><div>On Thu, Jan 20, 2011 at 7:51 PM=
, James M. Polk <span dir=3D"ltr">&lt;<a href=3D"mailto:jmpolk@cisco.com">j=
mpolk@cisco.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">
<div class=3D"im">At 03:31 PM 1/19/2011, IETF Administrative Director wrote=
:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IAOC is pleased to announce Paris as the site for IETF 83 from 25 - 30<=
br>
March 2012. =A0The IETF last met in the city in 2005 at IETF 63.<br>
<br>
Paris was the number one choice for a European venue in a venue<br>
preference survey conducted after IETF 78.<br>
</blockquote>
<br></div>
I don&#39;t know about this... after all, the last time we had an IETF ther=
e is when EKR blew a gasket at the lack of (real) cookies during the breaks=
. This cannot be overlooked as an isolated incident, or hand-waved away. =
=A0I wouldn&#39;t want to be around him if this were to occur again.<br>

<br>
;-)<br><font color=3D"#888888">
<br>
James</font><div><div></div><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
2012<br>
IETF 83 =A0Paris 25 - 30 March =A0 =A0Host: =A0&lt;your name here&gt;<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div></div>

--90e6ba6e8d2aba6c6f049a5d66bd--

From ole@cisco.com  Fri Jan 21 08:08:13 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 A7B803A6A3F; Fri, 21 Jan 2011 08:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.577
X-Spam-Level: 
X-Spam-Status: No, score=-110.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 Ft7BpS7CCM0L; Fri, 21 Jan 2011 08:08:12 -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 BA3D83A6A3B; Fri, 21 Jan 2011 08:08:12 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from syd-core-1.cisco.com ([64.104.193.198]) by sj-iport-3.cisco.com with ESMTP; 21 Jan 2011 16:10:57 +0000
Received: from [10.24.17.59] ([10.24.17.59]) by syd-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0LGAs9q006553; Fri, 21 Jan 2011 16:10:55 GMT
Date: Fri, 21 Jan 2011 08:10:54 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: IETF 83 Venue
In-Reply-To: <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1101210808570.70222@macpro.local>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: iaoc@ietf.org, ietf@ietf.org, iab@iab.org, wgchairs@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: Fri, 21 Jan 2011 16:08:13 -0000

Does anyone see the irony of us even discussing concerns about, of all 
things, FOOD when it comes to Paris?

I can't wait to back to London :-)

Ole


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj




From ted.ietf@gmail.com  Fri Jan 21 08:54:52 2011
Return-Path: <ted.ietf@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 A6E9628C0F1 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 08:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level: 
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, J_CHICKENPOX_56=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 QCPT5Lpr2XR1 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 08:54:49 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 0802728C0F8 for <ietf@ietf.org>; Fri, 21 Jan 2011 08:54:48 -0800 (PST)
Received: by qyk34 with SMTP id 34so748986qyk.10 for <ietf@ietf.org>; Fri, 21 Jan 2011 08:57:35 -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=Gwh+grrmLL41IKQthnkj067OnXJa34k2Xd8HeKazmZM=; b=slpkvQMvk85rdyU8zFOh/ItqiCUNCPm7wc1SPYGGLaWjKuWz28xdwK6VLvCE90PCAF zcDPbQaG7rWiFc1L6xY2vK54iC4i1hc3JuZAi7ZjmMwuySBHvRsLcAf6P5kPzUjeZ/1V D8Bk8whaUm2SPCh1uxQQeoPtShqwEtfF/hGUo=
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=TBZvr+/bcWuKHQL4B17IKyMfZcnjlxw93pa/1u/VpCb07uibzJlwejnG5I4/aTJmJc ryv8QBQdi+fp/Vr3jsV9+SwqUPAFglBflGhzoTbZFVHgUcrklXVM9tPYOTjSXoZMnNwa sohff1QQX/uq+SaU9Khzv6pA7RP+NxT+97HwM=
MIME-Version: 1.0
Received: by 10.229.215.147 with SMTP id he19mr768258qcb.79.1295629055079; Fri, 21 Jan 2011 08:57:35 -0800 (PST)
Received: by 10.229.230.138 with HTTP; Fri, 21 Jan 2011 08:57:35 -0800 (PST)
In-Reply-To: <4D3943C8.5010206@gmx.de>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net> <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com> <4D3943C8.5010206@gmx.de>
Date: Fri, 21 Jan 2011 08:57:35 -0800
Message-ID: <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Ted Hardie <ted.ietf@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 21 Jan 2011 16:54:53 -0000

Howdy,

Some comments in-line.

On Fri, Jan 21, 2011 at 12:28 AM, Julian Reschke <julian.reschke@gmx.de> wr=
ote:
> On 21.01.2011 02:13, Ted Hardie wrote:
>>
>> ...
>> But the reality is that the behavior resulting from these URIs is totall=
y
>> non-deterministic and varies from context to context. =A0In most context=
s
>> outside of a browser location bar, they are meaningless. Inside that
>> context, the browser's definition seems to be definitive. =A0If the aim
>> is only to get about:blank fully specified, I'd suggest saying so
>> outright,
>> and noting clearly that all other uses are context-dependent, with
>> returning about:blank recommended practice =A0for those unknown.
>> ...
>
> That sounds reasonable. Let's not make it more complicated than it needs =
to
> be.
>

Okay.
>> As a thought experiment, would the W3C counsel against the presence
>> of an about URI in an XML namespace?
>
> Reminder: the reason this was written down was so that "about:legacy-comp=
at"
> can be specified as XML system identifier in HTML5
> (<http://dev.w3.org/html5/spec/Overview.html#the-doctype>).
>

This rationale isn't in the draft, nor is the token legacy-compat.
Having looked
at the section you reference, I see it also defines about:srcdoc as reserve=
d,
unresolvable URI.  It should be included in this doc, if it goes forward.

That said, I note that HTML5 has a number of what it calls "willful violati=
ons"
of the URI spec, in which it counsels the reading who actually knows what
the spec says to pretend it was using a term other than URI.  (One of these
is just past the fragment identifier used above).  Most uses of about
are outliers in the URI world by a long chalk.  Why not simply define about
as a different identifier form that happens to have a colon in it
(which, broadly,
it is) and make its use as system identifier in HTML5 a "willful violation"=
 of
the XML spec?  That seems entirely consistent with the document's modus ope=
randi
and save IANA the trouble of setting up a registry.

best regards,

Ted


>> Additionally, naming a change controller should generally be a bit more
>> precise than an organization name. =A0The W3C director or TAG seems
>> more appropriate than just "W3C".
>
> I just checked an image/svg+xml has "W3C" as change controller. Why would
> the requirement be different here?
>
> Best regards, Julian
>

From tme@americafree.tv  Fri Jan 21 09:26:23 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 815F43A6A68; Fri, 21 Jan 2011 09:26:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.273
X-Spam-Level: 
X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=0.326, 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 g-7t-PGX+uou; Fri, 21 Jan 2011 09:26:22 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 894883A6A67; Fri, 21 Jan 2011 09:26:22 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 9707B9B4F203; Fri, 21 Jan 2011 12:29:08 -0500 (EST)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
Date: Fri, 21 Jan 2011 12:29:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BE5F222-1495-4137-9E43-7D214954EC93@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: iaoc@ietf.org, ietf@ietf.org, iab@iab.org, wgchairs@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, 21 Jan 2011 17:26:23 -0000

On Jan 21, 2011, at 11:04 AM, Mary Barnes wrote:

> If it's the same conference center that we were at for IETF-63, there =
should be few complaints about food given that there is a very nice =
(real) food market in the shopping area in the Palais de Congres - i.e., =
if there aren't enough cookies for you at the meeting, then you can go =
buy a whole package at the food market.
>=20

It is - and  the main hotel is actually the one connected to that venue.=20=


Regards
Marshall


> Mary.
>=20
> On Thu, Jan 20, 2011 at 7:51 PM, James M. Polk <jmpolk@cisco.com> =
wrote:
> At 03:31 PM 1/19/2011, IETF Administrative Director wrote:
> The IAOC is pleased to announce Paris as the site for IETF 83 from 25 =
- 30
> March 2012.  The IETF last met in the city in 2005 at IETF 63.
>=20
> Paris was the number one choice for a European venue in a venue
> preference survey conducted after IETF 78.
>=20
> I don't know about this... after all, the last time we had an IETF =
there is when EKR blew a gasket at the lack of (real) cookies during the =
breaks. This cannot be overlooked as an isolated incident, or hand-waved =
away.  I wouldn't want to be around him if this were to occur again.
>=20
> ;-)
>=20
> James
>=20
>=20
> 2012
> IETF 83  Paris 25 - 30 March    Host:  <your name here>
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From tme@americafree.tv  Fri Jan 21 09:27:53 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 CF1C928C11F for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 09:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.127
X-Spam-Level: 
X-Spam-Status: No, score=-102.127 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, MIME_8BIT_HEADER=0.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 mdgRuYydhKnN for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 09:27:51 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id E1CE628C11B for <ietf@ietf.org>; Fri, 21 Jan 2011 09:27:49 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 4A6989B4F2A3; Fri, 21 Jan 2011 12:30:36 -0500 (EST)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <49C83D1E-EA87-4103-8596-7BEB2FEE510D@bondis.org>
Date: Fri, 21 Jan 2011 12:30:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <91F18CCA-E6E1-4E94-9DDB-9A7CD08BE87E@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com> <49C83D1E-EA87-4103-8596-7BEB2FEE510D@bondis.org>
To: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
X-Mailer: Apple Mail (2.1081)
Cc: Phillip Hallam-Baker <hallam@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: Fri, 21 Jan 2011 17:27:53 -0000

On Jan 21, 2011, at 8:21 AM, Jo=E3o Damas wrote:

>=20
> On 21 Jan 2011, at 14:05, Phillip Hallam-Baker wrote:
>=20
>> No, that was Prague '68
>=20
> you mean IETF 68 in Prague. Prague '68 refers to rather different =
events in this corner of the world.

Yes. We thankfully have yet to have tanks sent in to close down an IETF =
meeting.=20

Regards
Marshall

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


From julian.reschke@gmx.de  Fri Jan 21 09:35:23 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 18B363A6A66 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 09:35:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.853
X-Spam-Level: 
X-Spam-Status: No, score=-103.853 tagged_above=-999 required=5 tests=[AWL=-1.854, BAYES_00=-2.599, J_CHICKENPOX_56=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 Ul8YcRWpbAAa for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 09:35:22 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id DFC723A6A5F for <ietf@ietf.org>; Fri, 21 Jan 2011 09:35:21 -0800 (PST)
Received: (qmail invoked by alias); 21 Jan 2011 17:38:06 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.133]) [217.91.35.233] by mail.gmx.net (mp003) with SMTP; 21 Jan 2011 18:38:06 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+u9rEu9Zyunr94PzHQ7v3LxLUR3QyUMAy8xCixUs 1e10xmJHxxGhpJ
Message-ID: <4D39C46C.3020804@gmx.de>
Date: Fri, 21 Jan 2011 18:37: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: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <20110114155632.17927.70550.idtracker@localhost>	<6.2.5.6.2.20110120110057.0d0f5228@resistor.net>	<AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>	<4D3943C8.5010206@gmx.de> <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com>
In-Reply-To: <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, 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, 21 Jan 2011 17:35:23 -0000

On 21.01.2011 17:57, Ted Hardie wrote:
> Howdy,
> ...
>> Reminder: the reason this was written down was so that "about:legacy-compat"
>> can be specified as XML system identifier in HTML5
>> (<http://dev.w3.org/html5/spec/Overview.html#the-doctype>).
>>
>
> This rationale isn't in the draft, nor is the token legacy-compat.

...because HTML5 defines it... (I think)

> Having looked
> at the section you reference, I see it also defines about:srcdoc as reserved,
> unresolvable URI.  It should be included in this doc, if it goes forward.

I don't think the goal of the registration document is to define all 
about URIs out there. (and I don't think it should).

> That said, I note that HTML5 has a number of what it calls "willful violations"
> of the URI spec, in which it counsels the reading who actually knows what

Sadly.

> the spec says to pretend it was using a term other than URI.  (One of these
> is just past the fragment identifier used above).  Most uses of about
> are outliers in the URI world by a long chalk.  Why not simply define about
> as a different identifier form that happens to have a colon in it
> (which, broadly,
> it is) and make its use as system identifier in HTML5 a "willful violation" of
> the XML spec?  That seems entirely consistent with the document's modus operandi
> and save IANA the trouble of setting up a registry.
> ...

:-)

Browsers use "about:" where URIs are entered. So no matter what we 
think, it will be very hard to ever register a "about" URI scheme for 
something else.

Why not just accept it, and have a registration that at least enhances 
the situation (as opposed to it not being registered)?

Also -- the spec doesn't define an IANA registry, so there won't be any 
trouble for them anyway.

Best regards, Julian



From sginoza@amsl.com  Fri Jan 21 09:13:56 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 CC69528C10C; Fri, 21 Jan 2011 09:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.943
X-Spam-Level: 
X-Spam-Status: No, score=-0.943 tagged_above=-999 required=5 tests=[AWL=1.055,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=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 zEtgxTyhQj67; Fri, 21 Jan 2011 09:13:55 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 1D46E3A6A4C; Fri, 21 Jan 2011 09:13:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id C0C64E0819; Fri, 21 Jan 2011 09:16:41 -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 vBr22jjr2i2c; Fri, 21 Jan 2011 09:16:41 -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 25B0AE0143; Fri, 21 Jan 2011 09:16:41 -0800 (PST)
Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR Reviewofdraft-yevstifeyev-tn3270-uri-12)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-186--504579033
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <69147F44-0025-47D6-8CAC-B47BC3A9CF89@americafree.tv>
Date: Fri, 21 Jan 2011 09:16:40 -0800
Message-Id: <4F303B60-55D6-4680-B25A-4A6616D79B37@amsl.com>
References: <80A0822C5E9A4440A5117C2F4CD36A640177235F@DEMUEXC006.nsn-intra.net> <4D2E4DFF.6020507@gmail.com> <80A0822C5E9A4440A5117C2F4CD36A6401772A90@DEMUEXC006.nsn-intra.net> <4D2F2089.2000306@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22092C4DDC@DC-US1MBEX4.global.avaya.com> <4D2F3C11.7000904@joelhalpern.com> <4D2F4086.3050601@stpeter.im> <A618ECBD1CEA466899166BD12E3CB2D9@DougEwell> <007601cbb3cb$082eaa00$4001a8c0@gateway.2wire.net> <AANLkTin9nfpnQ1umSLv1Vx57XmCFWp_sB-Xfn-uNbuhd@mail.gmail.com> <69147F44-0025-47D6-8CAC-B47BC3A9CF89@americafree.tv>
To: Marshall Eubanks <tme@americafree.tv>
X-Mailer: Apple Mail (2.1082)
X-Mailman-Approved-At: Fri, 21 Jan 2011 09:41:55 -0800
Cc: Phillip Hallam-Baker <hallam@gmail.com>, The 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: Fri, 21 Jan 2011 17:13:56 -0000

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

Greetings,

Sorry I'm late to the discussion, but I wanted to point out our actual =
policy regarding the Author's Address:

=46rom "RFC Document Style" =
(http://www.rfc-editor.org/rfc-style-guide/rfc-style)
4.9.  "Author's Address" Section

   This required section gives contact information for the author(s)
   listed in the first-page header, and perhaps those listed in a
   Contributors section.

   Contact information must include at least one, and ideally would
   include all, of a postal address, a telephone number and/or FAX
   number, and a long-lived email address.  The purpose of this section
   is to (1) unambiguously define author/contributor identity (e.g., the
   John Smith who works for FooBar Systems) and to (2) provide contact
   information for future readers who have questions or comments.  Note
   that some professional societies offer long-lived email addresses for
   their members.

Typically, we'll request an email address (at minimum) because we (RFC =
Production Center) need to be able to contact the authors via email and =
get author approval for the document. =20
Please let me know if you have any questions or if this causes any =
concern.

Thanks!
Sandy (for the RFC Production Center)


On Jan 14, 2011, at 7:06 AM, Marshall Eubanks wrote:

>=20
> On Jan 14, 2011, at 7:45 AM, Phillip Hallam-Baker wrote:
>=20
>> I believe that my personal security trumps any and all considerations =
that might be raised here.
>>=20
>> I do not give my home address out and do not intend to change. If the =
RFC editor were to insist that the fields are filled they are going to =
get a fake address.
>>=20
>>=20
>=20
> They should not insist on anything of the sort.=20
>=20
>> Corporate addresses are even less useful. Very few people in the IETF =
have the same employer for more than five years. And even those who have =
the same employer are unlikely to have the same office building very =
long.
>>=20
>>=20
>> On Fri, Jan 14, 2011 at 4:11 AM, t.petch <daedulus@btconnect.com> =
wrote:
>> ----- Original Message -----
>> From: "Doug Ewell" <doug@ewellic.org>
>> To: "The IETF" <ietf@ietf.org>
>> Sent: Friday, January 14, 2011 6:56 AM
>> Subject: Re: author's address (was: Re: Fwd: [OPS-DIR] OPS-DIR
>> Reviewofdraft-yevstifeyev-tn3270-uri-12)
>>=20
>>=20
>>> Peter Saint-Andre wrote:
>>>=20
>>>> For what it's worth, Section 10 of the informational RFC 2223
>>>> ("Instructions to RFC Authors") states:
>>>>=20
>>>> Each RFC must have at the very end a section giving the author's
>>>> address, including the name and postal address, the telephone =
number,
>>>> (optional: a FAX number) and the Internet email address.
>>>=20
>>> The Internet is not the type of chummy small-town environment where =
we
>>> can trust just anybody with our home address and phone number, or =
our
>>> bank account and credit card numbers, and where we can leave our =
front
>>> doors unlocked at night.
>>=20
>> As Joel pointed out, the Last Call issue is the contact details for =
change
>> control
>> in the registration of a widely used URI with IANA, details which =
consist
>> solely of a gmail address.  Is that enough to grant change control of =
this
>> URI (in which a number of people from a number of organisations have
>> expressed an ongoing interest)?
>>=20
>=20
> What, exactly, is the issue here ? How IANA authenticates someone with =
change control over some resource ?
> That, clearly, is a lot bigger than just this RFC. I would assume (and =
feel sure) that IANA is not just blindly going by
> email address, but by their judgement. I am also not sure what having =
an address will do to help with this. I doubt IANA
> will be sending inspectors to people's houses asking to see ID.
>=20
> If there seems to be of particular risk of such attacks for this URI, =
I would suggest adding=20
> text in the security section (or the IANA considerations).
>=20
> If impersonation attacks seem like a real threat in general, then =
someone who feels that way=20
> should write a draft specifying how IANA should authenticate people.
>=20
> Regards
> Marshall
>=20
>> RFC4395 appears to be silent.
>>=20
>> Tom Petch
>>=20
>>> I worked on two I-Ds in a WG where participant A once responded to
>>> participant B's support of an RFC 3683 P-R action against A by
>>> contacting B's employer, gleaned from his e-mail address, demanding =
that
>>> the employer take professional action against B.  In this type of
>>> hostile environment, I declined to state my employer's name or post =
to
>>> the WG list from my work address, much less divulge other personal
>>> information, and edited both RFC 4645 and 5646 as "Consultant."
>>>=20
>>> The argument that personal information is necessary to distinguish =
the
>>> author from other people with the same name probably carries some =
weight
>>> for authors named "John Smith" or "Bob Miller."  There are few =
enough
>>> people named "Doug Ewell" in the world that the risk of ambiguity of
>>> authorship seems much more remote than the risk to personal security =
if
>>> too much personal information is provided.  I suspect the same is =
true
>>> for people named "Mykyta Yevstifeyev."
>>>=20
>>> Having said that, I don't think there is any precedent for I-D =
authors
>>> or editors to claim their document was written by "IETF" or "IESG," =
and
>>> I doubt this will be permitted.
>>>=20
>>> --
>>> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
>>> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s=20
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>>=20
>> --=20
>> Website: http://hallambaker.com/
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20


--Apple-Mail-186--504579033
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>Greetings,</div><div><br></div><div>Sorry I'm late to the =
discussion, but I wanted to point out our actual policy regarding the =
Author's Address:</div><div><br></div><div>=46rom "<span =
class=3D"Apple-style-span" style=3D"white-space: pre; ">RFC Document =
Style" (</span><a =
href=3D"http://www.rfc-editor.org/rfc-style-guide/rfc-style">http://www.rf=
c-editor.org/rfc-style-guide/rfc-style</a>)</div><div><pre><font =
class=3D"Apple-style-span" face=3D"Courier" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 12px;">4.9.  "Author's =
Address" Section

   This required section gives contact information for the author(s)
   listed in the first-page header, and perhaps those listed in a
   Contributors section.

   Contact information must include at least one, and ideally would
   include all, of a postal address, a telephone number and/or FAX
   number, and a long-lived email address.  The purpose of this section
   is to (1) unambiguously define author/contributor identity (e.g., the
   John Smith who works for FooBar Systems) and to (2) provide contact
   information for future readers who have questions or comments.  Note
   that some professional societies offer long-lived email addresses for
   their members.</span></font></pre><pre><font class=3D"Apple-style-span"=
 face=3D"Courier" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 12px;"><br></span></font></pre><pre><font =
class=3D"Apple-style-span" face=3D"Courier" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 12px;">Typically, we'll =
request an email address (at minimum) because we (RFC Production Center) =
need to be able to contact the authors via email and get author approval =
for the document.  </span></font></pre><pre><font =
class=3D"Apple-style-span" face=3D"Courier" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: 12px;">Please let me know =
if you have any questions or if this causes any =
concern.</span></font></pre><pre><font class=3D"Apple-style-span" =
face=3D"Courier" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 12px;"><br></span></font></pre><pre><font =
class=3D"Apple-style-span" face=3D"Courier" size=3D"3"><span =
class=3D"Apple-style-span" style=3D"font-size: =
12px;">Thanks!</span></font></pre><pre><font class=3D"Apple-style-span" =
face=3D"Courier" size=3D"3"><span class=3D"Apple-style-span" =
style=3D"font-size: 12px;">Sandy (for the RFC Production =
Center)</span></font></pre></div><div><br></div><br><div><div>On Jan 14, =
2011, at 7:06 AM, Marshall Eubanks wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><br>On =
Jan 14, 2011, at 7:45 AM, Phillip Hallam-Baker wrote:<br><br><blockquote =
type=3D"cite">I believe that my personal security trumps any and all =
considerations that might be raised here.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">I do not give =
my home address out and do not intend to change. If the RFC editor were =
to insist that the fields are filled they are going to get a fake =
address.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>They should not insist on anything of =
the sort. <br><br><blockquote type=3D"cite">Corporate addresses are even =
less useful. Very few people in the IETF have the same employer for more =
than five years. And even those who have the same employer are unlikely =
to have the same office building very long.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">On Fri, Jan 14, =
2011 at 4:11 AM, t.petch &lt;<a =
href=3D"mailto:daedulus@btconnect.com">daedulus@btconnect.com</a>&gt; =
wrote:<br></blockquote><blockquote type=3D"cite">----- Original Message =
-----<br></blockquote><blockquote type=3D"cite">From: "Doug Ewell" =
&lt;<a =
href=3D"mailto:doug@ewellic.org">doug@ewellic.org</a>&gt;<br></blockquote>=
<blockquote type=3D"cite">To: "The IETF" &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br></blockquote><block=
quote type=3D"cite">Sent: Friday, January 14, 2011 6:56 =
AM<br></blockquote><blockquote type=3D"cite">Subject: Re: author's =
address (was: Re: Fwd: [OPS-DIR] OPS-DIR<br></blockquote><blockquote =
type=3D"cite">Reviewofdraft-yevstifeyev-tn3270-uri-12)<br></blockquote><bl=
ockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">Peter Saint-Andre =
wrote:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">For =
what it's worth, Section 10 of the informational RFC =
2223<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">("Instructions to RFC Authors") =
states:<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"><blockquote type=3D"cite">Each =
RFC must have at the very end a section giving the =
author's<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">address,=
 including the name and postal address, the telephone =
number,<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">(optional: a FAX number) and the Internet email =
address.<br></blockquote></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The Internet is not the type of =
chummy small-town environment where =
we<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">can trust just anybody with our home address and phone =
number, or our<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">bank account and credit card =
numbers, and where we can leave our =
front<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">doors unlocked at =
night.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">As Joel pointed =
out, the Last Call issue is the contact details for =
change<br></blockquote><blockquote =
type=3D"cite">control<br></blockquote><blockquote type=3D"cite">in the =
registration of a widely used URI with IANA, details which =
consist<br></blockquote><blockquote type=3D"cite">solely of a gmail =
address. &nbsp;Is that enough to grant change control of =
this<br></blockquote><blockquote type=3D"cite">URI (in which a number of =
people from a number of organisations have<br></blockquote><blockquote =
type=3D"cite">expressed an ongoing =
interest)?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><br>What, exactly, is the issue here ? =
How IANA authenticates someone with change control over some resource =
?<br>That, clearly, is a lot bigger than just this RFC. I would assume =
(and feel sure) that IANA is not just blindly going by<br>email address, =
but by their judgement. I am also not sure what having an address will =
do to help with this. I doubt IANA<br>will be sending inspectors to =
people's houses asking to see ID.<br><br>If there seems to be of =
particular risk of such attacks for this URI, I would suggest adding =
<br>text in the security section (or the IANA considerations).<br><br>If =
impersonation attacks seem like a real threat in general, then someone =
who feels that way <br>should write a draft specifying how IANA should =
authenticate people.<br><br>Regards<br>Marshall<br><br><blockquote =
type=3D"cite">RFC4395 appears to be silent.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Tom =
Petch<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">I worked on two I-Ds in a WG where participant A once =
responded to<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">participant B's support of an =
RFC 3683 P-R action against A =
by<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">contacting B's employer, gleaned from his e-mail address, =
demanding that<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">the employer take professional =
action against B. &nbsp;In this type =
of<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">hostile environment, I declined to state my employer's =
name or post to<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">the WG list from my work =
address, much less divulge other =
personal<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">information, and edited both RFC =
4645 and 5646 as "Consultant."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The argument that personal =
information is necessary to distinguish =
the<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">author from other people with the same name probably =
carries some weight<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">for authors named "John Smith" =
or "Bob Miller." &nbsp;There are few =
enough<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">people named "Doug Ewell" in the world that the risk of =
ambiguity of<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">authorship seems much more =
remote than the risk to personal security =
if<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite">too much personal information is provided. &nbsp;I suspect =
the same is true<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">for people named "Mykyta =
Yevstifeyev."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Having said that, I don't think =
there is any precedent for I-D =
authors<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote=
 type=3D"cite">or editors to claim their document was written by "IETF" =
or "IESG," and<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">I doubt this will be =
permitted.<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">--<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">Doug Ewell | Thornton, Colorado, =
USA | <a =
href=3D"http://www.ewellic.org">http://www.ewellic.org</a><br></blockquote=
></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">RFC =
5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =
<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite">Ietf =
mailing list<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/m=
ailman/listinfo/ietf</a><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">Ietf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br></blockquote><blockquot=
e type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/m=
ailman/listinfo/ietf</a><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">-- =
<br></blockquote><blockquote type=3D"cite">Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br></blockquo=
te><blockquote type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">_______________________________________________<br></blockqu=
ote><blockquote type=3D"cite">Ietf mailing =
list<br></blockquote><blockquote type=3D"cite"><a =
href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br></blockquote><blockquot=
e type=3D"cite"><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/m=
ailman/listinfo/ietf</a><br></blockquote><br></div></blockquote></div><br>=
</body></html>=

--Apple-Mail-186--504579033--

From hallam@gmail.com  Fri Jan 21 10:14: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 D108E3A6A76 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 10:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[AWL=0.131,  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 qaeRiJWwPffx for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 10:14:53 -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 BE2963A6A79 for <ietf@ietf.org>; Fri, 21 Jan 2011 10:14:53 -0800 (PST)
Received: by gxk27 with SMTP id 27so697249gxk.31 for <ietf@ietf.org>; Fri, 21 Jan 2011 10:17:40 -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=e01WzbGWC9a4hPXMGfAchEpZFZBbCysaEHVC/UsLN48=; b=Ils7iUymPooXwAmzBLgbq5a9zGV93I4+kxcDvx9D0WBO+vyObOI03o6sQY7DqgL9Sa bki5ELPahwEO4cmQTtVDMst71PiKMqfY+yN0E47xyVC21Y/W/6uLs3qnmKcvfAQqOPHA pr0rqOtTR0xPD29NMNxSUMyZeOkwpi9fliCzk=
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=A/473WIxh9FAGyOhHf1N9ostJgbw8Hnz1X43rFWpt1jOzrOh46ktr82FXZTg3vK/Id npup1zHc45woqdsQ9yTpq96Rszf2NljBZwSenN12OCt2GI8Mt4anim6SfWQovpCTDnua ylNGksCM8Z0Jhiy2qm0KDFbSOJUBvqLlzk/w8=
MIME-Version: 1.0
Received: by 10.100.34.1 with SMTP id h1mr703378anh.188.1295633859840; Fri, 21 Jan 2011 10:17:39 -0800 (PST)
Received: by 10.101.71.15 with HTTP; Fri, 21 Jan 2011 10:17:39 -0800 (PST)
In-Reply-To: <4D398CAF.5010906@krsek.cz>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTi=avJg560+OGARq8zi4bU-AF-=0iju7pZ_t4O-H@mail.gmail.com> <4D398CAF.5010906@krsek.cz>
Date: Fri, 21 Jan 2011 13:17:39 -0500
Message-ID: <AANLkTin7riGBsnWshkXQPCteMSSOhxGgpsHze1Zi8g7O@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Michal Krsek <michal@krsek.cz>
Content-Type: multipart/alternative; boundary=0016e6465220f98d46049a5f43a3
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, 21 Jan 2011 18:14:54 -0000

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

On Fri, Jan 21, 2011 at 8:39 AM, Michal Krsek <michal@krsek.cz> wrote:

>  Hi Phillip,
> as a person living in Prague I have to say that if you want to have western
> style services, you need to pay western (or higher) prices.
>

No, the opposite was true.

If you wanted a good meal you had to leave the hotel and buy at local
prices. It was the combination of Western prices and Communist food inside
the hotel that was the issue for me.



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

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

<br><br><div class=3D"gmail_quote">On Fri, Jan 21, 2011 at 8:39 AM, Michal =
Krsek <span dir=3D"ltr">&lt;<a href=3D"mailto:michal@krsek.cz">michal@krsek=
.cz</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">


 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#ffffff">
    Hi Phillip,<br>
    as a person living in Prague I have to say that if you want to have
    western style services, you need to pay western (or higher) prices.
    <br></div></blockquote><div><br></div><div>No, the opposite was true.</=
div><div><br></div><div>If you wanted a good meal you had to leave the hote=
l and buy at local prices. It was the combination of Western prices and Com=
munist food inside the hotel that was the issue for me.</div>
<div><br></div><div><br></div></div><br>-- <br>Website: <a href=3D"http://h=
allambaker.com/">http://hallambaker.com/</a><br><br>

--0016e6465220f98d46049a5f43a3--

From hallam@gmail.com  Fri Jan 21 10:19: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 C2D8528C133; Fri, 21 Jan 2011 10:19:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.468
X-Spam-Level: 
X-Spam-Status: No, score=-3.468 tagged_above=-999 required=5 tests=[AWL=0.130,  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 qix6lhtawYIE; Fri, 21 Jan 2011 10:19:39 -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 74F2D28C123; Fri, 21 Jan 2011 10:19:38 -0800 (PST)
Received: by ywk9 with SMTP id 9so699178ywk.31 for <multiple recipients>; Fri, 21 Jan 2011 10:22:24 -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=GdtxymgJqgS3dDy51w6KOCEpFlD10S9Qhp6DO+L6OnM=; b=k6omNLCgQ9ewfQ06wJgbnlkgC4T+rCWelzICUzoTzDNGrwgY+tnxiWEdTZmENSvFMl zOkcbSOB/eZCh/If5OSye2Um/t99b7t5SWZJpwF5AIL5cvKbTQWdujPk5rssycPXIJxk qQdNbN6V4pUavTxvitZjIDRaVovh+KGZvjtHU=
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=vmEAcAM1NPW10RmygB59wisZECuXXe1TUq7oE0pqHJRrSw18EwIb7S8sC5WB8DznId YTV/8IHWXjyh9UXQVs7iRuvAvugCeKToP4RaRRGDeiJ9HiFJLTRXlBlZnZJrA7D6TQtW W5PTlQJtJ14tPZAWUc5FyI8zQJjMn+DtHdoiM=
MIME-Version: 1.0
Received: by 10.100.44.17 with SMTP id r17mr684652anr.222.1295634144678; Fri, 21 Jan 2011 10:22:24 -0800 (PST)
Received: by 10.101.71.15 with HTTP; Fri, 21 Jan 2011 10:22:24 -0800 (PST)
In-Reply-To: <alpine.OSX.2.01.1101210808570.70222@macpro.local>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local>
Date: Fri, 21 Jan 2011 13:22:24 -0500
Message-ID: <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ole Jacobsen <ole@cisco.com>
Content-Type: multipart/alternative; boundary=0016e644bc76f3e142049a5f544e
Cc: iaoc@ietf.org, ietf@ietf.org, iab@iab.org, wgchairs@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, 21 Jan 2011 18:19:39 -0000

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

On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> wrote:

>
> Does anyone see the irony of us even discussing concerns about, of all
> things, FOOD when it comes to Paris?
>

What else is there to discuss in Paris?


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

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

On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:ole@cisco.com">ole@cisco.com</a>&gt;</span> wrote:<br><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Does anyone see the irony of us even discussing concerns about, of all<br>
things, FOOD when it comes to Paris?<br></blockquote><div><br></div><div>Wh=
at else is there to discuss in Paris?</div><div><br></div><div><br></div></=
div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br>
<br>

--0016e644bc76f3e142049a5f544e--

From tglassey@earthlink.net  Fri Jan 21 12:34:43 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 194CF3A67F5 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 12:34:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HOE5w0wnJHu0 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 12:34:42 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by core3.amsl.com (Postfix) with ESMTP id E072F3A67F8 for <ietf@ietf.org>; Fri, 21 Jan 2011 12:34:41 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Orl/uElrO6wpqYOXvS8wdSdi0qAS2JDU37pyYQPW5PACpNBJ9RdUxqwueRcriM9T; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Opacus-Archived:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [207.111.209.5] (helo=[192.168.1.101]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1PgNjb-0000DR-Ow for ietf@ietf.org; Fri, 21 Jan 2011 15:37:28 -0500
Message-ID: <4D39EE7B.6050507@earthlink.net>
Date: Fri, 21 Jan 2011 12:37:15 -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: IETF 83 Venue
References: <20110119213125.E3D2228C0F4@core3.amsl.com>	<201101210151.p0L1pqVe014924@sj-core-2.cisco.com>	<AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>	<alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com>
In-Reply-To: <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com>
X-Opacus-Archived: none
Content-Type: multipart/alternative; boundary="------------000305020805050301070302"
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7998bad1eeee2de0507d0be40108fc8cd4350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
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: Fri, 21 Jan 2011 20:34:43 -0000

This is a multi-part message in MIME format.
--------------000305020805050301070302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com 
> <mailto:ole@cisco.com>> wrote:
>
>
>     Does anyone see the irony of us even discussing concerns about, of all
>     things, FOOD when it comes to Paris?
>
>
> What else is there to discuss in Paris?
>
Making Paris the center of the world - ever look at French Navigation 
Charts - relative to Admiralty charts from any other nation?

Todd

>
>
> -- 
> Website: http://hallambaker.com/
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com>
> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: 01/21/11
>


--------------000305020805050301070302
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">
    On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
    <blockquote
      cite="mid:AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com"
      type="cite">On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <span
        dir="ltr">&lt;<a moz-do-not-send="true"
          href="mailto:ole@cisco.com">ole@cisco.com</a>&gt;</span>
      wrote:<br>
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          <br>
          Does anyone see the irony of us even discussing concerns
          about, of all<br>
          things, FOOD when it comes to Paris?<br>
        </blockquote>
        <div><br>
        </div>
        <div>What else is there to discuss in Paris?<br>
          <br>
        </div>
      </div>
    </blockquote>
    Making Paris the center of the world - ever look at French
    Navigation Charts - relative to Admiralty charts from any other
    nation? <br>
    <br>
    Todd<br>
    <br>
    <blockquote
      cite="mid:AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      -- <br>
      Website: <a moz-do-not-send="true" href="http://hallambaker.com/">http://hallambaker.com/</a><br>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Ietf mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ietf@ietf.org">Ietf@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <p class="avgcert" color="#000000" align="left">No virus found in
        this message.<br>
        Checked by AVG - <a moz-do-not-send="true"
          href="http://www.avg.com">www.avg.com</a><br>
        Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date:
        01/21/11</p>
    </blockquote>
    <br>
  </body>
</html>

--------------000305020805050301070302--

From clint.chaplin@gmail.com  Fri Jan 21 12:46:14 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 CAB363A6808 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 12:46:14 -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 ylt79ZynOk3g for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 12:46:13 -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 B64353A6807 for <ietf@ietf.org>; Fri, 21 Jan 2011 12:46:12 -0800 (PST)
Received: by bwz12 with SMTP id 12so2120026bwz.31 for <ietf@ietf.org>; Fri, 21 Jan 2011 12:48:58 -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=Bar/xcnOTWaZzGuuBRMyF96J1Bh00x8wcOSiwa2MqBI=; b=cVLhu+ZmQrvTRKhFEp3sTq00ehILXTugwi8zaPg85WfkLfB6uA+AdM913sdA/swP8M F7wqtoyt/GoBn4AUxQGwhNbrlYQFrRv1+ZPO8T/NiDWTLJGYatP2MzQORuFRATu4YY8/ FqbYS4RHg++v+wqz0JRYeTDXCSdmD9UZgFx+w=
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=OVyJVcTnS96aMWeKdG6BcneEaBdbDYM83EyrTXWNQEb6+/EnBrUkRH3dgN9RDBFaYn Blbqy78Ov4APbMJGQAblhHvXn0mOiYY0qUiZnjB33zy41Ss1kLzhCUc5GVSYyovAVMHl ewCVCOJjEmfTZqwdFHeDcahdyTv1EDSUFnB9w=
MIME-Version: 1.0
Received: by 10.103.165.16 with SMTP id s16mr778059muo.28.1295642938186; Fri, 21 Jan 2011 12:48:58 -0800 (PST)
Received: by 10.103.12.9 with HTTP; Fri, 21 Jan 2011 12:48:58 -0800 (PST)
In-Reply-To: <4D39EE7B.6050507@earthlink.net>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net>
Date: Fri, 21 Jan 2011 12:48:58 -0800
Message-ID: <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Clint Chaplin <clint.chaplin@gmail.com>
To: todd glassey <tglassey@earthlink.net>
Content-Type: multipart/alternative; boundary=001636b43151161af2049a61613e
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, 21 Jan 2011 20:46:14 -0000

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

Hey, Paris lobbied heavily to have the Prime Meridian be fixed in Paris.
 That would have really made them the center of the navigational world.

On Fri, Jan 21, 2011 at 12:37 PM, todd glassey <tglassey@earthlink.net>wrote:

>  On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
>
> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> wrote:
>
>>
>> Does anyone see the irony of us even discussing concerns about, of all
>> things, FOOD when it comes to Paris?
>>
>
>  What else is there to discuss in Paris?
>
>   Making Paris the center of the world - ever look at French Navigation
> Charts - relative to Admiralty charts from any other nation?
>
> Todd
>
>
>
>  --
> Website: http://hallambaker.com/
>
>
>
> _______________________________________________
> Ietf mailing listIetf@ietf.orghttps://www.ietf.org/mailman/listinfo/ietf
>
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: 01/21/11
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>


-- 
Clint (JOATMON) Chaplin
Principal Engineer
Corporate Standardization (US)
SISA

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

Hey, Paris lobbied heavily to have the Prime Meridian be fixed in Paris. =
=A0That would have really made them the center of the navigational world.<b=
r><br><div class=3D"gmail_quote">On Fri, Jan 21, 2011 at 12:37 PM, todd gla=
ssey <span dir=3D"ltr">&lt;<a href=3D"mailto:tglassey@earthlink.net">tglass=
ey@earthlink.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">

 =20
   =20
   =20
 =20
  <div bgcolor=3D"#ffffff" text=3D"#000000"><div class=3D"im">
    On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
    <blockquote type=3D"cite">On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobse=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:ole@cisco.com" target=3D"_blank">=
ole@cisco.com</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 rgb(204, 204, 204);padding-left:1ex">
          <br>
          Does anyone see the irony of us even discussing concerns
          about, of all<br>
          things, FOOD when it comes to Paris?<br>
        </blockquote>
        <div><br>
        </div>
        <div>What else is there to discuss in Paris?<br>
          <br>
        </div>
      </div>
    </blockquote></div>
    Making Paris the center of the world - ever look at French
    Navigation Charts - relative to Admiralty charts from any other
    nation? <br>
    <br>
    Todd<br>
    <br>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      -- <br>
      Website: <a href=3D"http://hallambaker.com/" target=3D"_blank">http:/=
/hallambaker.com/</a><div class=3D"im"><br>
      <br>
      <pre><fieldset></fieldset>
_______________________________________________
Ietf mailing list
<a href=3D"mailto:Ietf@ietf.org" target=3D"_blank">Ietf@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a>
</pre>
      <br>
      <fieldset></fieldset>
      <br>
      </div><p color=3D"#000000" align=3D"left">No virus found in
        this message.<br>
        Checked by AVG - <a href=3D"http://www.avg.com" target=3D"_blank">w=
ww.avg.com</a><br>
        Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date:
        01/21/11</p>
    </blockquote>
    <br>
  </div>

<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>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br>Clint (JOATMON) Cha=
plin<br>Principal Engineer<br>Corporate Standardization (US)<br>SISA<br>

--001636b43151161af2049a61613e--

From tme@americafree.tv  Fri Jan 21 12:53:57 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 D72F828C0E9 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 12:53:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.281
X-Spam-Level: 
X-Spam-Status: No, score=-102.281 tagged_above=-999 required=5 tests=[AWL=0.318, 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 v2j1851hxK7d for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 12:53:56 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id B31803A6A8B for <ietf@ietf.org>; Fri, 21 Jan 2011 12:53:56 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 7B2CB9B53ED9; Fri, 21 Jan 2011 15:56:43 -0500 (EST)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com>
Date: Fri, 21 Jan 2011 15:56:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com>
To: Clint Chaplin <clint.chaplin@gmail.com>
X-Mailer: Apple Mail (2.1081)
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, 21 Jan 2011 20:53:57 -0000

On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:

> Hey, Paris lobbied heavily to have the Prime Meridian be fixed in =
Paris.  That would have really made them the center of the navigational =
world.
>=20

Yes, and then they got the BIH, which got them the power to change GMT =
to UTC. (GMT no longer has any official existence.)=20

Marshall

> On Fri, Jan 21, 2011 at 12:37 PM, todd glassey =
<tglassey@earthlink.net> wrote:
> On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
>> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> wrote:
>>=20
>> Does anyone see the irony of us even discussing concerns about, of =
all
>> things, FOOD when it comes to Paris?
>>=20
>> What else is there to discuss in Paris?
>>=20
> Making Paris the center of the world - ever look at French Navigation =
Charts - relative to Admiralty charts from any other nation?=20
>=20
> Todd
>=20
>>=20
>>=20
>> --=20
>> Website: http://hallambaker.com/
>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>>=20
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: =
01/21/11
>>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20
>=20
>=20
> --=20
> Clint (JOATMON) Chaplin
> Principal Engineer
> Corporate Standardization (US)
> SISA
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From hallam@gmail.com  Fri Jan 21 14:03:03 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 DFFD63A67EC for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 14:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.469
X-Spam-Level: 
X-Spam-Status: No, score=-3.469 tagged_above=-999 required=5 tests=[AWL=0.129,  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 w7sOd53b+vsP for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 14:03:02 -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 6F6F83A6964 for <ietf@ietf.org>; Fri, 21 Jan 2011 14:03:02 -0800 (PST)
Received: by gyd12 with SMTP id 12so761754gyd.31 for <ietf@ietf.org>; Fri, 21 Jan 2011 14:05:49 -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=gIh8AZo9LU4lKfwLhwdzYhApwpMsC9Tzj1wbutfE+og=; b=Gi23zJitA7mlFTOcZijQrW8TM/E0d1Sw+Te2CMjct5btOVeJGKBhwOOz0VDlYayRbE jLHctT0pU/yAsj/nEe1wMNu2zPfdZsCECw8ZGnmrPzZ0ZSQOwds7bhDps40yE0wwmCZh BAHPelfmStkzkz2wZztpxIZYvffbNUnwymaXg=
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=nFQvr7igwyshwf1cgPGHnZVUQmbRC1lWJxW5xjjJFg7aABA9xup46EVoocoecZ2C6c 9IxCYHNl3z01f892kOQJbwpPZP0E/GB4NX84V6chjvJV9Hr9wx7Hb5kArwvWmYxL39j5 G+t7fr78iwyaMjGijYXpoyKWraaJiUEEdRMIk=
MIME-Version: 1.0
Received: by 10.100.4.11 with SMTP id 11mr885775and.52.1295647549081; Fri, 21 Jan 2011 14:05:49 -0800 (PST)
Received: by 10.101.71.15 with HTTP; Fri, 21 Jan 2011 14:05:49 -0800 (PST)
In-Reply-To: <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
Date: Fri, 21 Jan 2011 17:05:49 -0500
Message-ID: <AANLkTimdG3CckU50zynyfgXtwb6VtkOGtDgg8V_xZc_k@mail.gmail.com>
Subject: Re: IETF 83 Venue
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Marshall Eubanks <tme@americafree.tv>
Content-Type: multipart/alternative; boundary=0016e646526ceac816049a627324
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, 21 Jan 2011 22:03:04 -0000

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

GMT still exists as a legal construct and could well prove useful since it
is ultimately under control of HMG, quite possibly it can be modified by as
little as an order in council.

So if HMG would eliminate the inanity of leap seconds in GMT we could
probably move most computer systems back to GMT rather than UTC as a
reference point.


The idea that there is utility in leap seconds is ridiculous. Most
astronomers I have talked to tell me that UTC is useless for their purposes
anyway and the time of mid-day varies at Greenwich by 5 minutes over the
course of a year so what does it matter which two days are right?


On Fri, Jan 21, 2011 at 3:56 PM, Marshall Eubanks <tme@americafree.tv>wrote:

>
> On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:
>
> > Hey, Paris lobbied heavily to have the Prime Meridian be fixed in Paris.
>  That would have really made them the center of the navigational world.
> >
>
> Yes, and then they got the BIH, which got them the power to change GMT to
> UTC. (GMT no longer has any official existence.)
>
> Marshall
>
> > On Fri, Jan 21, 2011 at 12:37 PM, todd glassey <tglassey@earthlink.net>
> wrote:
> > On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
> >> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> wrote:
> >>
> >> Does anyone see the irony of us even discussing concerns about, of all
> >> things, FOOD when it comes to Paris?
> >>
> >> What else is there to discuss in Paris?
> >>
> > Making Paris the center of the world - ever look at French Navigation
> Charts - relative to Admiralty charts from any other nation?
> >
> > Todd
> >
> >>
> >>
> >> --
> >> Website: http://hallambaker.com/
> >>
> >>
> >>
> >> _______________________________________________
> >> Ietf mailing list
> >>
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >>
> >>
> >> No virus found in this message.
> >> Checked by AVG - www.avg.com
> >> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: 01/21/11
> >>
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
> >
> >
> >
> > --
> > Clint (JOATMON) Chaplin
> > Principal Engineer
> > Corporate Standardization (US)
> > SISA
> > _______________________________________________
> > 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
>



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

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

GMT still exists as a legal construct and could well prove useful since it =
is ultimately under control of HMG, quite possibly it can be modified by as=
 little as an order in council.<div><br></div><div>So if HMG would eliminat=
e the inanity of leap seconds in GMT we could probably move most computer s=
ystems back to GMT rather than UTC as a reference point.</div>
<div><br></div><div><br></div><div>The idea that there is utility in leap s=
econds is ridiculous. Most astronomers I have talked to tell me that UTC is=
 useless for their purposes anyway and the time of mid-day varies at Greenw=
ich by 5 minutes over the course of a year so what does it matter which two=
 days are right?<br>
<br></div><div><br><div class=3D"gmail_quote">On Fri, Jan 21, 2011 at 3:56 =
PM, Marshall Eubanks <span dir=3D"ltr">&lt;<a href=3D"mailto:tme@americafre=
e.tv">tme@americafree.tv</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex;">
<div class=3D"im"><br>
On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:<br>
<br>
&gt; Hey, Paris lobbied heavily to have the Prime Meridian be fixed in Pari=
s. =A0That would have really made them the center of the navigational world=
.<br>
&gt;<br>
<br>
</div>Yes, and then they got the BIH, which got them the power to change GM=
T to UTC. (GMT no longer has any official existence.)<br>
<font color=3D"#888888"><br>
Marshall<br>
</font><div><div></div><div class=3D"h5"><br>
&gt; On Fri, Jan 21, 2011 at 12:37 PM, todd glassey &lt;<a href=3D"mailto:t=
glassey@earthlink.net">tglassey@earthlink.net</a>&gt; wrote:<br>
&gt; On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:<br>
&gt;&gt; On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen &lt;<a href=3D"mail=
to:ole@cisco.com">ole@cisco.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Does anyone see the irony of us even discussing concerns about, of=
 all<br>
&gt;&gt; things, FOOD when it comes to Paris?<br>
&gt;&gt;<br>
&gt;&gt; What else is there to discuss in Paris?<br>
&gt;&gt;<br>
&gt; Making Paris the center of the world - ever look at French Navigation =
Charts - relative to Admiralty charts from any other nation?<br>
&gt;<br>
&gt; Todd<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Website: <a href=3D"http://hallambaker.com/" target=3D"_blank">htt=
p://hallambaker.com/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; Ietf mailing list<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_=
blank">https://www.ietf.org/mailman/listinfo/ietf</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; No virus found in this message.<br>
&gt;&gt; Checked by AVG - <a href=3D"http://www.avg.com" target=3D"_blank">=
www.avg.com</a><br>
&gt;&gt; Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: 01/=
21/11<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ietf</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Clint (JOATMON) Chaplin<br>
&gt; Principal Engineer<br>
&gt; Corporate Standardization (US)<br>
&gt; SISA<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ietf</a><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>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e646526ceac816049a627324--

From d3e3e3@gmail.com  Fri Jan 21 14:42:10 2011
Return-Path: <d3e3e3@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 680EA3A6849 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 14:42:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.404
X-Spam-Level: 
X-Spam-Status: No, score=-103.404 tagged_above=-999 required=5 tests=[AWL=0.195, 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 0KYo6HdhpNkJ for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 14:42:09 -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 E37D53A683D for <ietf@ietf.org>; Fri, 21 Jan 2011 14:42:08 -0800 (PST)
Received: by wyf23 with SMTP id 23so2419830wyf.31 for <ietf@ietf.org>; Fri, 21 Jan 2011 14:44: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:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=Iwkf8E5QjfeCt0x6r56jOlETR95UyxczPc+hijE/MQA=; b=Q+50ik31DUUPve95wQEoC6eYQ61O2TLiA4FFCikrKbacbXGkhRkb0H4bbU9T7vxcr6 XkDWAXC3n9VKoaIjWnUVgQpSEeKYSxz4tblLQI5JKTda8TzRyc00TDUNFq5MqZulhqYH 3jUgsc6ahG03LLDKQdFtnI9om+1PTcscWnk/Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=a8kUxea5HHwGmUyNJXXzV3WF9MZXndgK0ttqXnGBh9r8BkZuvvfkzfDRDK+UzslWOu tEOKz6D1nMv/ChbSDhdvDju2uqzvPMTA7CJHQgCn3nCVn4B20Z5Vl+njnn3vIRJWNEaz wzfqDCwVNxJNXAD6wOmnBOfm+Q7LA0LmYP5oQ=
Received: by 10.227.132.206 with SMTP id c14mr1454792wbt.124.1295649894584; Fri, 21 Jan 2011 14:44:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Fri, 21 Jan 2011 14:44:33 -0800 (PST)
In-Reply-To: <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 21 Jan 2011 17:44:33 -0500
Message-ID: <AANLkTi=koFq10iVUrmBtgEP-Z5hmnPqaHsJWqSRx-r=F@mail.gmail.com>
Subject: Re: IETF 83 Venue
To: Marshall Eubanks <tme@americafree.tv>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 21 Jan 2011 22:42:10 -0000

I had the impression that it was the International Earth Rotation
Service (www.iers.org), also headquartered in Paris, that was in
charge of leap seconds, as stated here
http://www.iers.org/nn_11252/IERS/EN/DataProducts/EarthOrientationData/bulC=
__MD.html

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com


On Fri, Jan 21, 2011 at 3:56 PM, Marshall Eubanks <tme@americafree.tv> wrot=
e:
>
> On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:
>
>> Hey, Paris lobbied heavily to have the Prime Meridian be fixed in Paris.=
 =A0That would have really made them the center of the navigational world.
>>
>
> Yes, and then they got the BIH, which got them the power to change GMT to=
 UTC. (GMT no longer has any official existence.)
>
> Marshall
>
>> On Fri, Jan 21, 2011 at 12:37 PM, todd glassey <tglassey@earthlink.net> =
wrote:
>> On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
>>> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> wrote:
>>>
>>> Does anyone see the irony of us even discussing concerns about, of all
>>> things, FOOD when it comes to Paris?
>>>
>>> What else is there to discuss in Paris?
>>>
>> Making Paris the center of the world - ever look at French Navigation Ch=
arts - relative to Admiralty charts from any other nation?
>>
>> Todd
>>
>>>
>>>
>>> --
>>> Website: http://hallambaker.com/
>>>
>>>
>>>
>>> _______________________________________________
>>> Ietf mailing list
>>>
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>
>>>
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: 01/21/11
>>>
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>>
>>
>>
>> --
>> Clint (JOATMON) Chaplin
>> Principal Engineer
>> Corporate Standardization (US)
>> SISA
>> _______________________________________________
>> 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 ted.ietf@gmail.com  Fri Jan 21 14:46:55 2011
Return-Path: <ted.ietf@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 A65F33A684B for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 14:46:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level: 
X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, J_CHICKENPOX_56=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 VDHT1JztsEQ8 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 14:46:54 -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 8ED953A683D for <ietf@ietf.org>; Fri, 21 Jan 2011 14:46:54 -0800 (PST)
Received: by qyj19 with SMTP id 19so2413535qyj.10 for <ietf@ietf.org>; Fri, 21 Jan 2011 14:49:41 -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=VBFCMnLc1TqAPpBkyLsO9moVxpbTVkXJCrc31NxVY28=; b=oM7ZarWWxUuzAcPi+97+ImoD0hzaOZss6RQ+XMwU/1z1kSG8XMQR/aEzR20IsXx74q k0aa8l70TGDdlLNz4iXSQSmIyj/FpknB15pqYFB6ipfeeRy7iQ8+RHqMMZIxp1WHcFOA 5CO/hBgi/s2RjLdroNFid3Xsz9zHyDNg8GxDo=
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=xAZbevzGLg1dFpDRi8DvqzbrdH+pFQMywuYQaGeFJ0TEUxQD5q6MX+c9bbLPp57Rft t7zEqKj06imN6F34m64ek0v5Ni1tSqRwieiEet1jRxHjHk42LaX/lBjxtZ03rL5Gbkwj /A5VH+cltGJl0hva3KfSg4a2t4l1JMLhDvAgw=
MIME-Version: 1.0
Received: by 10.229.215.9 with SMTP id hc9mr1031335qcb.117.1295650181276; Fri, 21 Jan 2011 14:49:41 -0800 (PST)
Received: by 10.229.230.138 with HTTP; Fri, 21 Jan 2011 14:49:41 -0800 (PST)
In-Reply-To: <4D39C46C.3020804@gmx.de>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net> <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com> <4D3943C8.5010206@gmx.de> <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com> <4D39C46C.3020804@gmx.de>
Date: Fri, 21 Jan 2011 14:49:41 -0800
Message-ID: <AANLkTik+T=vLMaG_WL5DLS-CPcaCW25ivF+xLcJBeugk@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Ted Hardie <ted.ietf@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 21 Jan 2011 22:46:55 -0000

Howdy,

Some further replies in-line.

On Fri, Jan 21, 2011 at 9:37 AM, Julian Reschke <julian.reschke@gmx.de> wro=
te:
> On 21.01.2011 17:57, Ted Hardie wrote:
>>
>> Howdy,
>> ...
>>>
>>> Reminder: the reason this was written down was so that
>>> "about:legacy-compat"
>>> can be specified as XML system identifier in HTML5
>>> (<http://dev.w3.org/html5/spec/Overview.html#the-doctype>).
>>>
>>
>> This rationale isn't in the draft, nor is the token legacy-compat.
>
> ...because HTML5 defines it... (I think)
>

But the question with this how you will get interoperability.  If there is =
a
token registry, then these should populate that registry pretty much
as soon as the registry opens, as these are entries for which conflict
has a bad result.  The whole point of a registry is to avoid collisions in
the token portion of the identifier space.

>> Having looked
>> at the section you reference, I see it also defines about:srcdoc as
>> reserved,
>> unresolvable URI. =A0It should be included in this doc, if it goes forwa=
rd.
>
> I don't think the goal of the registration document is to define all abou=
t
> URIs out there. (and I don't think it should).
>

It goes to significant lengths to define the behavior of about:blank,
and it mentions but does not define others.  That's a bit odd, in
IETF circles, especially when you are defining a protocol  to have
"reserved" and "unreserved" tokens.  This iis why the suggestion
of a registry is being made. That gives a place to look
for behavior definitions and confirm reserved vs. unreserved.

If that is not really wanted, this draft is  reserving a URI scheme on
what looks to me to be closer to provisional terms.

I have enough experience on the URI registration side to understand
that people mint schemes without registration pretty readily, and minting
tokens seems even easier.  If you don't  care at all about interoperability
in this behavior, a registry is not needed, but then I'm not sure why
a permanent URI registration is needed either.   The about: convention
has been around a while, and a provisional to note it seems enough.

>> That said, I note that HTML5 has a number of what it calls "willful
>> violations"
>> of the URI spec, in which it counsels the reading who actually knows wha=
t
>
> Sadly.
>
>> the spec says to pretend it was using a term other than URI. =A0(One of
>> these
>> is just past the fragment identifier used above). =A0Most uses of about
>> are outliers in the URI world by a long chalk. =A0Why not simply define
>> about
>> as a different identifier form that happens to have a colon in it
>> (which, broadly,
>> it is) and make its use as system identifier in HTML5 a "willful
>> violation" of
>> the XML spec? =A0That seems entirely consistent with the document's modu=
s
>> operandi
>> and save IANA the trouble of setting up a registry.
>> ...
>
> :-)
>
> Browsers use "about:" where URIs are entered. So no matter what we think,=
 it
> will be very hard to ever register a "about" URI scheme for something els=
e.
>

I agree, and a provisional to block its registration seems sensible.  But i=
f you
are not eventually trying to get interoperable behavior, having "reserved"
elements for this scheme seems, at best, confusing.

> Why not just accept it, and have a registration that at least enhances th=
e
> situation (as opposed to it not being registered)?
>
The last call invites advice from the community on how to improve the docum=
ent.
Why not just accept, and trust it enhances the situation?

> Also -- the spec doesn't define an IANA registry, so there won't be any
> trouble for them anyway.
>
> Best regards, Julian
>

best regards,

Ted

>
>

From tme@americafree.tv  Fri Jan 21 16:01:47 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 28E193A685C for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 16:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.282
X-Spam-Level: 
X-Spam-Status: No, score=-102.282 tagged_above=-999 required=5 tests=[AWL=0.317, 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 AkAlp2Ra-AHP for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 16:01:45 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id A119A3A6855 for <ietf@ietf.org>; Fri, 21 Jan 2011 16:01:45 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 6D3329B58289; Fri, 21 Jan 2011 19:04:32 -0500 (EST)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTi=koFq10iVUrmBtgEP-Z5hmnPqaHsJWqSRx-r=F@mail.gmail.com>
Date: Fri, 21 Jan 2011 19:04:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1465E091-72E5-4232-9DFE-A5C124259F75@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv> <AANLkTi=koFq10iVUrmBtgEP-Z5hmnPqaHsJWqSRx-r=F@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1081)
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, 22 Jan 2011 00:01:47 -0000

On Jan 21, 2011, at 5:44 PM, Donald Eastlake wrote:

> I had the impression that it was the International Earth Rotation
> Service (www.iers.org), also headquartered in Paris, that was in
> charge of leap seconds, as stated here
> =
http://www.iers.org/nn_11252/IERS/EN/DataProducts/EarthOrientationData/bul=
C__MD.html
>=20

It is now. However, it was the BIH (Bureau International de l'Heure) =
when the GMT was changed to UTC.

Regards
Marshall


> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street
>  Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
>=20
> On Fri, Jan 21, 2011 at 3:56 PM, Marshall Eubanks <tme@americafree.tv> =
wrote:
>>=20
>> On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:
>>=20
>>> Hey, Paris lobbied heavily to have the Prime Meridian be fixed in =
Paris.  That would have really made them the center of the navigational =
world.
>>>=20
>>=20
>> Yes, and then they got the BIH, which got them the power to change =
GMT to UTC. (GMT no longer has any official existence.)
>>=20
>> Marshall
>>=20
>>> On Fri, Jan 21, 2011 at 12:37 PM, todd glassey =
<tglassey@earthlink.net> wrote:
>>> On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
>>>> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> =
wrote:
>>>>=20
>>>> Does anyone see the irony of us even discussing concerns about, of =
all
>>>> things, FOOD when it comes to Paris?
>>>>=20
>>>> What else is there to discuss in Paris?
>>>>=20
>>> Making Paris the center of the world - ever look at French =
Navigation Charts - relative to Admiralty charts from any other nation?
>>>=20
>>> Todd
>>>=20
>>>>=20
>>>>=20
>>>> --
>>>> Website: http://hallambaker.com/
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> Ietf mailing list
>>>>=20
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>>=20
>>>>=20
>>>> No virus found in this message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: =
01/21/11
>>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>=20
>>>=20
>>>=20
>>>=20
>>> --
>>> Clint (JOATMON) Chaplin
>>> Principal Engineer
>>> Corporate Standardization (US)
>>> SISA
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20


From tme@americafree.tv  Fri Jan 21 16:12: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 D8DE63A6864 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 16:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.284
X-Spam-Level: 
X-Spam-Status: No, score=-102.284 tagged_above=-999 required=5 tests=[AWL=0.315, 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 LzMsGZaYzrQM for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 16:12:20 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 8D36C3A6863 for <ietf@ietf.org>; Fri, 21 Jan 2011 16:12:20 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 8C6A19B585EA; Fri, 21 Jan 2011 19:15:07 -0500 (EST)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <AANLkTimdG3CckU50zynyfgXtwb6VtkOGtDgg8V_xZc_k@mail.gmail.com>
Date: Fri, 21 Jan 2011 19:15:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B54E261E-FED3-464E-8536-0531DCD13C3C@americafree.tv>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv> <AANLkTimdG3CckU50zynyfgXtwb6VtkOGtDgg8V_xZc_k@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1081)
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, 22 Jan 2011 00:12:21 -0000

On Jan 21, 2011, at 5:05 PM, Phillip Hallam-Baker wrote:

> GMT still exists as a legal construct and could well prove useful =
since it is ultimately under control of HMG, quite possibly it can be =
modified by as little as an order in council.
>=20
> So if HMG would eliminate the inanity of leap seconds in GMT we could =
probably move most computer systems back to GMT rather than UTC as a =
reference point.
>=20
>=20
> The idea that there is utility in leap seconds is ridiculous. Most =
astronomers I have talked to tell me that UTC is useless for their =
purposes anyway and the time of mid-day varies at Greenwich by 5 minutes =
over the course of a year so what does it matter which two days are =
right?
>=20

UTC is kept close to UT1 for celestial navigation, not astronomy, and is =
indeed somewhat archaic. (The idea was that you could use UTC, i.e., =
civil time, as reported by a simple radio, and then do celestial =
navigation to get within about 1 km of your true location. You still =
can, but that is of
less and less utility as navigation moves to GPS and time keeping =
becomes ever better.)=20

The time of mid-day is solar time, which does vary in a periodic fashion =
during the year, driven by the Earth's orbital motion. These variations =
are not shared by mean solar time, which is now-a-days really an atomic =
time.=20

Regards
Marshall

>=20
> On Fri, Jan 21, 2011 at 3:56 PM, Marshall Eubanks <tme@americafree.tv> =
wrote:
>=20
> On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:
>=20
> > Hey, Paris lobbied heavily to have the Prime Meridian be fixed in =
Paris.  That would have really made them the center of the navigational =
world.
> >
>=20
> Yes, and then they got the BIH, which got them the power to change GMT =
to UTC. (GMT no longer has any official existence.)
>=20
> Marshall
>=20
> > On Fri, Jan 21, 2011 at 12:37 PM, todd glassey =
<tglassey@earthlink.net> wrote:
> > On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
> >> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> =
wrote:
> >>
> >> Does anyone see the irony of us even discussing concerns about, of =
all
> >> things, FOOD when it comes to Paris?
> >>
> >> What else is there to discuss in Paris?
> >>
> > Making Paris the center of the world - ever look at French =
Navigation Charts - relative to Admiralty charts from any other nation?
> >
> > Todd
> >
> >>
> >>
> >> --
> >> Website: http://hallambaker.com/
> >>
> >>
> >>
> >> _______________________________________________
> >> Ietf mailing list
> >>
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >>
> >>
> >> No virus found in this message.
> >> Checked by AVG - www.avg.com
> >> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: =
01/21/11
> >>
> >
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> >
> >
> >
> >
> > --
> > Clint (JOATMON) Chaplin
> > Principal Engineer
> > Corporate Standardization (US)
> > SISA
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
>=20
>=20
> --=20
> Website: http://hallambaker.com/
>=20


From julian.reschke@gmx.de  Sat Jan 22 01:44:58 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 DEFBA3A686B for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 01:44:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.303
X-Spam-Level: 
X-Spam-Status: No, score=-103.303 tagged_above=-999 required=5 tests=[AWL=-1.904, BAYES_00=-2.599, J_CHICKENPOX_55=0.6, J_CHICKENPOX_56=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 Z2ckKeQFYiue for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 01:44:57 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 5F1A73A683F for <ietf@ietf.org>; Sat, 22 Jan 2011 01:44:56 -0800 (PST)
Received: (qmail invoked by alias); 22 Jan 2011 09:47:43 -0000
Received: from p508FD23A.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.210.58] by mail.gmx.net (mp025) with SMTP; 22 Jan 2011 10:47:43 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/wxPpc6gXwvMqNMdj8j3wGAB7Ruq3tojWLZJ+USw ETbJgB6Qooj6mq
Message-ID: <4D3AA7AA.8090307@gmx.de>
Date: Sat, 22 Jan 2011 10:47:22 +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: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <20110114155632.17927.70550.idtracker@localhost>	<6.2.5.6.2.20110120110057.0d0f5228@resistor.net>	<AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>	<4D3943C8.5010206@gmx.de>	<AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com>	<4D39C46C.3020804@gmx.de> <AANLkTik+T=vLMaG_WL5DLS-CPcaCW25ivF+xLcJBeugk@mail.gmail.com>
In-Reply-To: <AANLkTik+T=vLMaG_WL5DLS-CPcaCW25ivF+xLcJBeugk@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, 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, 22 Jan 2011 09:44:59 -0000

Hi Ted,

On 21.01.2011 23:49, Ted Hardie wrote:
>>> This rationale isn't in the draft, nor is the token legacy-compat.
>>
>> ...because HTML5 defines it... (I think)
>>
>
> But the question with this how you will get interoperability.  If there is a
> token registry, then these should populate that registry pretty much
> as soon as the registry opens, as these are entries for which conflict
> has a bad result.  The whole point of a registry is to avoid collisions in
> the token portion of the identifier space.

I can't speak for the author, but I think the believe is that interop is 
only needed for a few specific values (and only realistic for those), 
and thus having them defined *somehwere* (HTML5 or about-URI-spec is 
sufficient).

I agree that it's a bit odd that the HTML5 spec defines some of those, 
but not about:blank.

Maybe all of them should live in the HTML5 spec.

>>> Having looked
>>> at the section you reference, I see it also defines about:srcdoc as
>>> reserved,
>>> unresolvable URI.  It should be included in this doc, if it goes forward.
>>
>> I don't think the goal of the registration document is to define all about
>> URIs out there. (and I don't think it should).
>>
>
> It goes to significant lengths to define the behavior of about:blank,
> and it mentions but does not define others.  That's a bit odd, in
> IETF circles, especially when you are defining a protocol  to have
> "reserved" and "unreserved" tokens.  This iis why the suggestion
> of a registry is being made. That gives a place to look
> for behavior definitions and confirm reserved vs. unreserved.
>
> If that is not really wanted, this draft is  reserving a URI scheme on
> what looks to me to be closer to provisional terms.

If you look at the document history, it started with "provisional". I 
think this was changed based on early feedback; this is not a 
placeholder registration but *really* all that can be said about "about".

> I have enough experience on the URI registration side to understand
> that people mint schemes without registration pretty readily, and minting
> tokens seems even easier.  If you don't  care at all about interoperability
> in this behavior, a registry is not needed, but then I'm not sure why
> a permanent URI registration is needed either.   The about: convention
> has been around a while, and a provisional to note it seems enough.

I believe "about" qualifies for permanent as per 
<http://tools.ietf.org/html/rfc4395#section-2>, if there's something 
essential missing, we should fix it.

>> Browsers use "about:" where URIs are entered. So no matter what we think, it
>> will be very hard to ever register a "about" URI scheme for something else.
>>
>
> I agree, and a provisional to block its registration seems sensible.  But if you
> are not eventually trying to get interoperable behavior, having "reserved"
> elements for this scheme seems, at best, confusing.

In particular,

    Other specifications MAY reserve "about" URIs.  Applications
    attempting to resolve reserved "about" URIs that are not defined to
    be resolvable, MAY treat such URIs as being unreserved.

reads odd.

>> Why not just accept it, and have a registration that at least enhances the
>> situation (as opposed to it not being registered)?
>>
> The last call invites advice from the community on how to improve the document.
> Why not just accept, and trust it enhances the situation?

Not arguing with that :-).

> ...

Best regards, Julian

From julian.reschke@gmx.de  Sat Jan 22 04:48:05 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 3AF463A6921 for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 04:48:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.878
X-Spam-Level: 
X-Spam-Status: No, score=-103.878 tagged_above=-999 required=5 tests=[AWL=-1.279, 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 VCGMWEXwr0rl for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 04:48:04 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 0EABA3A691D for <ietf@ietf.org>; Sat, 22 Jan 2011 04:48:03 -0800 (PST)
Received: (qmail invoked by alias); 22 Jan 2011 12:50:50 -0000
Received: from p508FD23A.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.210.58] by mail.gmx.net (mp063) with SMTP; 22 Jan 2011 13:50:50 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19RKX17EfJRUScsHYdSzb3xLJXURa1lBGNcKhDft6 tEoXDnPF3SVewN
Message-ID: <4D3AD292.5000701@gmx.de>
Date: Sat, 22 Jan 2011 13:50:26 +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: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
References: <20110114155632.17927.70550.idtracker@localhost>	<6.2.5.6.2.20110120110057.0d0f5228@resistor.net>	<AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com>	<4D3943C8.5010206@gmx.de> <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com> <4D39C46C.3020804@gmx.de>
In-Reply-To: <4D39C46C.3020804@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, 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, 22 Jan 2011 12:48:05 -0000

On 21.01.2011 18:37, Julian Reschke wrote:
> ...
>> That said, I note that HTML5 has a number of what it calls "willful
>> violations"
>> of the URI spec, in which it counsels the reading who actually knows what
>
> Sadly.
> ...

BTW: <http://www.w3.org/html/wg/tracker/issues/56>. We should try to 
improve this, maybe during Last Call.

See also: <http://www.w3.org/html/wg/#join>

Best regards, Julian

From mail@sabahattin-gucukoglu.com  Sat Jan 22 07:31:57 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 E54B33A6959 for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 07:31:57 -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 lU8S-KtRwjNW for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 07:31:57 -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 7EE973A695F for <ietf@ietf.org>; Sat, 22 Jan 2011 07:31:56 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:57567) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S27C34> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Sat, 22 Jan 2011 15:34:43 -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; Sat, 22 Jan 2011 15:34:42 +0000
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Just Thinking (About the Nightmare Transition Ahead)
Date: Sat, 22 Jan 2011 15:34:33 +0000
Message-Id: <A7DFC328-44B1-455D-9893-0EE8BF354894@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-1298302483.e6e7db@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: Sat, 22 Jan 2011 15:31:58 -0000

My thought right now is perhaps of an OS update that includes a =
background client which tries very hard to reduce the effect of breakage =
or delay caused by IPv6 routes that are dead, DNS queries that don't go =
anywhere, and delays caused by slow transition techniques.  It couldn't =
be comprehensive, but I think it'd go a long way at this point.  The =
software vendors could, for instance, provide the test sites that =
receive IPv6 probes and/or traffic, and respond to them.  Not scalable? =
...

Cheers,
Sabahattin

From brian.e.carpenter@gmail.com  Sat Jan 22 10:46:01 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 2CF703A69C4 for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 10:46:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.463
X-Spam-Level: 
X-Spam-Status: No, score=-103.463 tagged_above=-999 required=5 tests=[AWL=0.136, 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 kgJb-kebYNa6 for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 10:46:00 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 318FB3A698A for <ietf@ietf.org>; Sat, 22 Jan 2011 10:46:00 -0800 (PST)
Received: by qwi2 with SMTP id 2so2996973qwi.31 for <ietf@ietf.org>; Sat, 22 Jan 2011 10:48:49 -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=wtOt+KD3K7gMfPM1KEWoCYQG8tjU8IyGvJ98o8wGhNY=; b=HxTdyii7XpUUGMUdwL9L9g9FpGCVVvoi+egI0kF4VpEDy4DIkor9e/mgVnmlnC09/d 9R/A/eJLVCiR/oP0eTWYVcrDo5CQ2piScCFMrWLziir5xn6j2RMcJs8gaXUYre4Uh/zc iPK4XDibPv3vgwld33lYVkAkIESYhxLq4NcSE=
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=pQF6+zZUXiud2nAOC2bEpS5wU6hG+5W5ENfgxmaV3FpqfzJ0T4YKhIjqfSgV6oZ0RG 4dDmchvu5jKbvXMNQd6QJothWBoGIC3D6WDV4RLZy4BQ61+VsAm/VFqXMp2D97QNmhhG ZgMpj8h90lkwNXjjLASeM8lHZkBXfj7apiWQk=
Received: by 10.229.213.13 with SMTP id gu13mr1957897qcb.196.1295722129055; Sat, 22 Jan 2011 10:48:49 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id g28sm7720987qck.25.2011.01.22.10.48.46 (version=SSLv3 cipher=RC4-MD5); Sat, 22 Jan 2011 10:48:48 -0800 (PST)
Message-ID: <4D3B2688.8060902@gmail.com>
Date: Sun, 23 Jan 2011 07:48:40 +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: Sabahattin Gucukoglu <mail-dated-1298302483.e6e7db@sabahattin-gucukoglu.com>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
References: <A7DFC328-44B1-455D-9893-0EE8BF354894@sabahattin-gucukoglu.com>
In-Reply-To: <A7DFC328-44B1-455D-9893-0EE8BF354894@sabahattin-gucukoglu.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 22 Jan 2011 18:46:01 -0000

What nightmare? I find IPv6 dual stack works just fine.

However, see draft-wing-v6ops-happy-eyeballs-ipv6

Regards
   Brian Carpenter


On 2011-01-23 04:34, Sabahattin Gucukoglu wrote:
> My thought right now is perhaps of an OS update that includes a background client which tries very hard to reduce the effect of breakage or delay caused by IPv6 routes that are dead, DNS queries that don't go anywhere, and delays caused by slow transition techniques.  It couldn't be comprehensive, but I think it'd go a long way at this point.  The software vendors could, for instance, provide the test sites that receive IPv6 probes and/or traffic, and respond to them.  Not scalable? ...
> 
> Cheers,
> Sabahattin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From mail@sabahattin-gucukoglu.com  Sat Jan 22 12:43:22 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 744B13A67F2 for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 12:43:22 -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 bEPPh8x1dIfx for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 12:43:21 -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 0C86D3A67E5 for <ietf@ietf.org>; Sat, 22 Jan 2011 12:43:20 -0800 (PST)
Received: from Mintaka.sabahattin-gucukoglu.com ([::ffff:127.0.0.1]:38230) by Mintaka.sabahattin-gucukoglu.com with [XMail 1.27 ESMTP Server] id <S27C57> for <ietf@ietf.org> from <mail@sabahattin-gucukoglu.com>; Sat, 22 Jan 2011 20:46:09 -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; Sat, 22 Jan 2011 20:46:08 +0000
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4D3B2688.8060902@gmail.com>
Date: Sat, 22 Jan 2011 20:46:04 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <C274B223-91B3-4BFB-9869-FF79D3B8CCC4@sabahattin-gucukoglu.com>
References: <A7DFC328-44B1-455D-9893-0EE8BF354894@sabahattin-gucukoglu.com> <4D3B2688.8060902@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
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
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1298321169.dd6db7@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: Sat, 22 Jan 2011 20:43:22 -0000

On 22 Jan 2011, at 18:48, Brian E Carpenter wrote:
> What nightmare? I find IPv6 dual stack works just fine.

It does, when your connectivity is working.  Unfortunately, the 0.1% (or =
whatever it is) of users whose connectivity isn't working seem to be =
sufficient in number to prevent large sites from deploying, and a number =
of others to just turn IPv6 off.  Not news, except I'd hate for this to =
be justification in keeping dual-stack from happening (the effects of =
which must be considerably worse than just losing 0.1% of users), =
especially since the publicity about "World IPv6 Day" has brought the =
whole issue to light.

Of course, I'd also like Google to run IPv6 (on its main web servers) =
for longer than 24 hours at a time. :-)

> However, see draft-wing-v6ops-happy-eyeballs-ipv6

Yes.  I'd love there to be some sort of consensus on it, or something =
like it.  I'd focus more on testing connectivity, though, rather than =
optimal calculation of IPv6 reachability using one protocol/application =
to any given place at the time (i.e. rough and ready determination at OS =
boot whether we're on a broken network, EG).  It would not be foolproof, =
but it would not need to be in order to be useful in the short-term.  =
Perhaps Happy Eyeballs is the answer.

Cheers,
Sabahattin

From Roman.Arcea@orange.md  Sat Jan 22 22:04:11 2011
Return-Path: <Roman.Arcea@orange.md>
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 7B2B93A6BF1 for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 22:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.371
X-Spam-Level: 
X-Spam-Status: No, score=-1.371 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.097, MIME_HTML_ONLY=1.457]
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 vozZ9bgNfgEw for <ietf@core3.amsl.com>; Sat, 22 Jan 2011 22:04:10 -0800 (PST)
Received: from mailfilter.orange.md (mailfilter.orange.md [94.243.64.204]) by core3.amsl.com (Postfix) with ESMTP id 173393A6BC8 for <ietf@ietf.org>; Sat, 22 Jan 2011 22:04:09 -0800 (PST)
Received: from mailfilter.orange.md (antispam.orange.md [127.0.0.1]) by localhost (Postfix) with SMTP id 23D1DC0A25C; Sun, 23 Jan 2011 08:06:47 +0200 (EET)
Received: from postman.orange.md (unknown [172.16.1.6]) by mailfilter.orange.md (Postfix) with ESMTP id 10DF7C0A21B; Sun, 23 Jan 2011 08:06:47 +0200 (EET)
MIME-Version: 1.0
Importance: Normal
X-Priority: 3 (Normal)
In-Reply-To: <C274B223-91B3-4BFB-9869-FF79D3B8CCC4@sabahattin-gucukoglu.com>
References: <C274B223-91B3-4BFB-9869-FF79D3B8CCC4@sabahattin-gucukoglu.com>, <A7DFC328-44B1-455D-9893-0EE8BF354894@sabahattin-gucukoglu.com>	<4D3B2688.8060902@gmail.com>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
X-Disclaimed: 1
From: Roman.Arcea@orange.md
To: mail-dated-1298321169.dd6db7@sabahattin-gucukoglu.com
Message-ID: <OFAABD9883.F2568355-ONC2257821.002194AD-C2257821.002194B0@orange.md>
Date: Sun, 23 Jan 2011 08:06:47 +0200
X-Mailer: Lotus Domino Web Server Release 8.5.2 HF194 November 09, 2010
X-MIMETrack: Serialize by HTTP Server on postman/OrangeMD(Release 8.5.2 HF194|November 09, 2010) at 01/23/2011 08:06:47, Serialize complete at 01/23/2011 08:06:47, Itemize by HTTP Server on postman/OrangeMD(Release 8.5.2 HF194|November 09, 2010) at 01/23/2011 08:06:47, Serialize by Router on postman/OrangeMD(Release 8.5.2 HF194|November 09, 2010) at 01/23/2011 08:06:47
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Content-Type: text/html; charset=ISO-8859-1
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: Sun, 23 Jan 2011 06:04:11 -0000

<font face=3D"Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size=
=3D"2"> <span>Hi,<br><br>I agree with Brian. What nightmare? It only seems =
as a nightmare until you don't have it in place.<br><br>It is not about the=
 transition itself, rather about the conceptual fact. First off all, the co=
mmon belief is for 0.05% of brokenness (most of it coming from old version =
of Mac OS X, some from old versions of Opera etc.). Now, that was half a ye=
ar ago. Is it the same today? Have you noticed that no one has ever said th=
at the service WILL be broken, but rather MIGHT be broken. This is a very i=
mportant distinction. Also, do you know of any standardized method of measu=
ring it? Have you ever measured the brokenness in IPv4 due to MTU issues or=
 DNS problems? For instance I have quite often encountered issues with my h=
ome service provider, that had an overloaded DNS during the peak hours that=
 used to time out on various occasions, and the page would not display unti=
l you hit refresh. Is it brokenness?<br><br>So, really - I believe that to =
some extent the World IPv6 Day is a first step that proves QA departments a=
re starting being comfortable with the new realities.<br><br>What is a litt=
le hard, is the operations, where you need to watch now for two protocols i=
n the same time, while the feature parity is still an issue. But I would ha=
rdly call this a nightmare.<br><br>Best,<br>Roman<br></span><br><br><font c=
olor=3D"#990099">-----ietf-bounces@ietf.org wrote: -----</font><div><blockq=
uote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5px; bord=
er-left: 2px solid black; margin-right: 0px;">To: Brian E Carpenter &lt;bri=
an.e.carpenter@gmail.com&gt;<br>From: Sabahattin Gucukoglu <mail@sabahattin=
-gucukoglu.com><br>Sent by: ietf-bounces@ietf.org<br>Date: 01/22/2011 10:47=
PM<br>Cc: ietf@ietf.org<br>Subject: Re: Just Thinking (About the Nightmare =
Transition Ahead)<br><br><tt><font face=3D"Courier New,Courier,monospace" s=
ize=3D"2">On 22 Jan 2011, at 18:48, Brian E Carpenter wrote:<br></font></tt=
><tt><font face=3D"Courier New,Courier,monospace" size=3D"2">&gt;&nbsp;What=
 nightmare? I find IPv6 dual stack works just fine.<br></font></tt><br><tt>=
<font face=3D"Courier New,Courier,monospace" size=3D"2">It does, when your =
connectivity is working. &nbsp;Unfortunately, the 0.1% (or whatever it is) =
of users whose connectivity isn't working seem to be sufficient in number t=
o prevent large sites from deploying, and a number of others to just turn I=
Pv6 off. &nbsp;Not news, except I'd hate for this to be justification in ke=
eping dual-stack from happening (the effects of which must be considerably =
worse than just losing 0.1% of users), especially since the publicity about=
 "World IPv6 Day" has brought the whole issue to</font></tt><tt><font face=
=3D"Courier New,Courier,monospace" size=3D"2">&nbsp;light.<br></font></tt><=
br><tt><font face=3D"Courier New,Courier,monospace" size=3D"2">Of course, I=
'd also like Google to run IPv6 (on its main web servers) for longer than 2=
4 hours at a time. :-)<br></font></tt><br><tt><font face=3D"Courier New,Cou=
rier,monospace" size=3D"2">&gt;&nbsp;However, see draft-wing-v6ops-happy-ey=
eballs-ipv6<br></font></tt><br><tt><font face=3D"Courier New,Courier,monosp=
ace" size=3D"2">Yes. &nbsp;I'd love there to be some sort of consensus on i=
t, or something like it. &nbsp;I'd focus more on testing connectivity, thou=
gh, rather than optimal calculation of IPv6 reachability using one protocol=
/application to any given place at the time (i.e. rough and ready determina=
tion at OS boot whether we're on a broken network, EG). &nbsp;It would not =
be foolproof, but it would not need to be in order to be useful in the shor=
t-term. &nbsp;Perhaps Happy Eyeballs is the answer.<br></font></tt><br><tt>=
<font face=3D"Courier New,Courier,monospace" size=3D"2">Cheers,<br></font><=
/tt><tt><font face=3D"Courier New,Courier,monospace" size=3D"2">Sabahattin<=
br></font></tt><tt><font face=3D"Courier New,Courier,monospace" size=3D"2">=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br></fon=
t></tt><tt><font face=3D"Courier New,Courier,monospace" size=3D"2">Ietf mai=
ling list<br></font></tt><tt><font face=3D"Courier New,Courier,monospace" s=
ize=3D"2">Ietf@ietf.org<br></font></tt><tt><font face=3D"Courier New,Courie=
r,monospace" size=3D"2"><a href=3D"https://www.ietf.org/mailman/listinfo/ie=
tf">https://www.ietf.org/mailman/listinfo/ietf</a></font></tt></mail@sabaha=
ttin-gucukoglu.com></blockquote></div><div></div></font>=

From ron.even.tlv@gmail.com  Sun Jan 23 03:02:46 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 4E2343A6850; Sun, 23 Jan 2011 03:02:46 -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 w8Tv7+UTUT1W; Sun, 23 Jan 2011 03:02:43 -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 D63BB3A684E; Sun, 23 Jan 2011 03:02:42 -0800 (PST)
Received: by wwa36 with SMTP id 36so3957811wwa.13 for <multiple recipients>; Sun, 23 Jan 2011 03:05:33 -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=SSXAg+eIrUY8xAY1neY97AXGtf2NNyyZbH/k5mjyt4k=; b=V+H8scirsbuV7QMp4Bjv/6I0V+aQTw3Wb6AUoP2E9O8g9Ln65hBuCzaDNxTIexj086 0lNzoKrbZrLlLNggkCWT9sgbVq/099QiCCFB+NPjjRzjzQxC4uHXbxBO1Akg2W32eBvy CPdeo+TzSyNMsaBqH8mhDpl1MdErIxl0XRrsk=
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=gjM4fIWbtroxWTkdJg2wzgAa0Vz+f1Uv7recvoQ+af0GLz7dTruw4HCVUMaxk58eF/ +dolEZ5XpnD2KlKSvsHC6syqQx6APbIyPok32eS0nwJp1FZXLX9TwxlLNjPcb5HeN78L dODDlYh0bfZ5/98klGXaAGBZuqznn696gELRQ=
Received: by 10.216.39.196 with SMTP id d46mr2356106web.114.1295780731783; Sun, 23 Jan 2011 03:05:31 -0800 (PST)
Received: from windows8d787f9 (bzq-109-64-30-137.red.bezeqint.net [109.64.30.137]) by mx.google.com with ESMTPS id o33sm5937969wej.13.2011.01.23.03.05.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Jan 2011 03:05:30 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-turner-ekpct-algs-update.all@tools.ietf.org>, <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-turner-ekpct-algs-update-02
Date: Sun, 23 Jan 2011 13:01:40 +0200
Message-ID: <4d3c0b7a.2191d80a.21eb.2f56@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0400_01CBBAFD.AEC80F30"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acu67OVx5KWEA3lVRs+KGms81oooXA==
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, 23 Jan 2011 11:02:46 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0400_01CBBAFD.AEC80F30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

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-turner-ekpct-algs-update-02

Reviewer: Roni Even

Review Date:2011-1-23

IETF LC End Date: 2011-2-8

IESG Telechat date:

 

Summary: This draft is ready for publication as a Standard track RFC.

 

Major issues:

none

Minor issues:

None

Nits/editorial comments:

None


------=_NextPart_000_0400_01CBBAFD.AEC80F30
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><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><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Document: <span style=3D'font-family:"Courier =
New"'>draft-turner-ekpct-algs-update-02<o:p></o:p></span></p><p =
class=3DMsoPlainText>Reviewer: Roni Even<o:p></o:p></p><p =
class=3DMsoPlainText>Review Date:2011&#8211;1&#8211;23<o:p></o:p></p><p =
class=3DMsoPlainText>IETF LC End Date: =
2011&#8211;2&#8211;8<o:p></o:p></p><p class=3DMsoPlainText>IESG Telechat =
date:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Summary: This draft is ready for publication as a =
Standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText>none<o:p></o:p></p><p =
class=3DMsoPlainText>Minor issues:<o:p></o:p></p><p =
class=3DMsoPlainText>None<o:p></o:p></p><p =
class=3DMsoPlainText>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoNormal>None<o:p></o:p></p></div></body></html>
------=_NextPart_000_0400_01CBBAFD.AEC80F30--


From bob.hinden@gmail.com  Sun Jan 23 20:08:19 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 897733A6A40 for <ietf@core3.amsl.com>; Sun, 23 Jan 2011 20:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.461
X-Spam-Level: 
X-Spam-Status: No, score=-103.461 tagged_above=-999 required=5 tests=[AWL=0.138, 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 oNIkPL9WjBcj for <ietf@core3.amsl.com>; Sun, 23 Jan 2011 20:08:18 -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 358EE3A6A3A for <ietf@ietf.org>; Sun, 23 Jan 2011 20:08:18 -0800 (PST)
Received: by ywk9 with SMTP id 9so1338588ywk.31 for <ietf@ietf.org>; Sun, 23 Jan 2011 20:11:11 -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=LHBYFe8IosT3cuHFgZPNbt/XCJyxy8wFGN7rt1NqrO0=; b=VBbvE6LKgZ00wsGu1LNEopqO2xCivIrsVpQCqm0snOcFg1+LcuGLR8XASqOlTrke53 0oOHTBB5F9ROmXKdnj2RFW5c3va+vTWSf1Tl6hRFuUD5MCKauRNm1ghC0tls0UCopOG+ KKzz0J29GmkgX7PvHMoVJHIRvF7nU849UvdwY=
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=HrVyC4wTo4eacNgXP5jJgOhpkXOjkDUzy0P2WmmkCGxEgNR6eILKDZ/fdzJZb2tOIC ZkBSAgVA7E9g4+MXbOI7Y1JKbEjmSnYoP2n778R/P+eFl0jhN+bAIQvsQOYD6v5HIKd8 uiileLcPd7wO3sFPQ/zqKxu22Nd7rA0Z2e418=
Received: by 10.90.63.5 with SMTP id l5mr4270137aga.201.1295842271413; Sun, 23 Jan 2011 20:11:11 -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 17sm15608969anx.13.2011.01.23.20.11.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 Jan 2011 20:11:10 -0800 (PST)
Subject: Re: IETF 83 Venue
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: <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
Date: Sun, 23 Jan 2011 20:11:07 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>
To: Marshall Eubanks <tme@americafree.tv>
X-Mailer: Apple Mail (2.1082)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Discussion <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, 24 Jan 2011 04:08:19 -0000

On Jan 21, 2011, at 12:56 PM, Marshall Eubanks wrote:

>=20
> On Jan 21, 2011, at 3:48 PM, Clint Chaplin wrote:
>=20
>> Hey, Paris lobbied heavily to have the Prime Meridian be fixed in =
Paris.  That would have really made them the center of the navigational =
world.
>>=20
>=20
> Yes, and then they got the BIH, which got them the power to change GMT =
to UTC. (GMT no longer has any official existence.)=20

Wasn't the official definition of the meter also tied to Paris?

Bob


>=20
> Marshall
>=20
>> On Fri, Jan 21, 2011 at 12:37 PM, todd glassey =
<tglassey@earthlink.net> wrote:
>> On 1/21/2011 10:22 AM, Phillip Hallam-Baker wrote:
>>> On Fri, Jan 21, 2011 at 11:10 AM, Ole Jacobsen <ole@cisco.com> =
wrote:
>>>=20
>>> Does anyone see the irony of us even discussing concerns about, of =
all
>>> things, FOOD when it comes to Paris?
>>>=20
>>> What else is there to discuss in Paris?
>>>=20
>> Making Paris the center of the world - ever look at French Navigation =
Charts - relative to Admiralty charts from any other nation?=20
>>=20
>> Todd
>>=20
>>>=20
>>>=20
>>> --=20
>>> Website: http://hallambaker.com/
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>>=20
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>=20
>>>=20
>>> No virus found in this message.
>>> Checked by AVG - www.avg.com
>>> Version: 10.0.1191 / Virus Database: 1435/3394 - Release Date: =
01/21/11
>>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>>=20
>>=20
>> --=20
>> Clint (JOATMON) Chaplin
>> Principal Engineer
>> Corporate Standardization (US)
>> SISA
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From huitema@microsoft.com  Sun Jan 23 20:33:33 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 6BF193A6A26 for <ietf@core3.amsl.com>; Sun, 23 Jan 2011 20:33:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.441
X-Spam-Level: 
X-Spam-Status: No, score=-10.441 tagged_above=-999 required=5 tests=[AWL=0.158, 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 0kEiBoQGXP5f for <ietf@core3.amsl.com>; Sun, 23 Jan 2011 20:33:32 -0800 (PST)
Received: from smtp.microsoft.com (mailc.microsoft.com [131.107.115.214]) by core3.amsl.com (Postfix) with ESMTP id 976A63A67F4 for <ietf@ietf.org>; Sun, 23 Jan 2011 20:33:32 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E803.partners.extranet.microsoft.com (10.251.56.169) with Microsoft SMTP Server (TLS) id 8.2.176.0; Sun, 23 Jan 2011 20:36:26 -0800
Received: from TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com (157.54.71.39) by TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) with Microsoft SMTP Server (TLS) id 14.1.255.3; Sun, 23 Jan 2011 20:36:25 -0800
Received: from TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com ([169.254.1.204]) by TK5EX14MLTW651.wingroup.windeploy.ntdev.microsoft.com ([157.54.71.39]) with mapi; Sun, 23 Jan 2011 20:36:23 -0800
From: Christian Huitema <huitema@microsoft.com>
To: Bob Hinden <bob.hinden@gmail.com>, Marshall Eubanks <tme@americafree.tv>
Subject: RE: IETF 83 Venue
Thread-Topic: IETF 83 Venue
Thread-Index: AQHLuYT4GOW16wMre0Wtjc27234gyZPcHqEAgAAkvgCAACWtgIAAA0YAgAACKQCAA54KgP//fx9Q
Date: Mon, 24 Jan 2011 04:36:22 +0000
Message-ID: <CEBCE3CF81D2D441B14B84256C3C46810BD83A88@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv> <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com>
In-Reply-To: <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com>
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: IETF Discussion <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, 24 Jan 2011 04:33:33 -0000

> Wasn't the official definition of the meter also tied to Paris?

The invention of the meter is indeed tied to Paris. The value of the meter =
itself is not.

The meter was defined by scientists commissioned by the French revolutionar=
y assembly, but it is not exactly "tied to Paris." The original definition =
was 1/10,000,000 of a quarter of the Earth circumference, and the commissio=
n of scientists established the value by measuring an arc of the earth circ=
umference between North of France and North of Spain. The unit was then mat=
erialized by a big platinum ruler kept in a locker in Paris. It is now defi=
ned in relation to the speed of light, itself set as 299,792,458 meters per=
 second.

-- Christian Huitema




From mrex@sap.com  Mon Jan 24 03:12:40 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 4D63E3A6AC6 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 03:12:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.166
X-Spam-Level: 
X-Spam-Status: No, score=-10.166 tagged_above=-999 required=5 tests=[AWL=0.083, 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 6uulr+NeN7nX for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 03:12:39 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id 2EE623A6AC2 for <ietf@ietf.org>; Mon, 24 Jan 2011 03:12:38 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p0OBFQF4002105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Jan 2011 12:15:31 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
To: brian.e.carpenter@gmail.com (Brian E Carpenter)
Date: Mon, 24 Jan 2011 12:15:25 +0100 (MET)
In-Reply-To: <4D3B2688.8060902@gmail.com> from "Brian E Carpenter" at Jan 23, 11 07:48:40 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: mail-dated-1298302483.e6e7db@sabahattin-gucukoglu.com, 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: Mon, 24 Jan 2011 11:12:40 -0000

Brian E Carpenter wrote:
> 
> However, see draft-wing-v6ops-happy-eyeballs-ipv6

Yuk.  That approach appears to be from a completely different universe
that solutions to the IPv4->IPv6 migration issue.

Instead of solving the problem where it originates, at the network level,
it dumps the entire problem onto the application in the worst conceivable
fashion.  It makes IPv6 and IPv4 worlds appear like two completely
seperate and independent Internets, i.e. this proposal incurs on apps
the exact same effort as migrating a completely different network protocol
or completely different network.


If anyone had suggested that for a migration from PSTN to VoiP, then
everyone would have to use two phones these days, dial in parallel
and hang up on whichever call establishes second.

The problem that this draft tries to solve at the app-level really
ought to be solved at the network level.  Use IPv6 addresses that
embed the alternative IPv4 address and have the network figure out
whether the route is IPv6 clean and the connection can be established
as IPv6 or only IPv4. (IPv4-NATing the IPv4 part of such an
address along the way is probably "fun"...) ... for exactly those
network interfaces that _have_ dual IPv4+IPv6 addresses.

-Martin

From marka@isc.org  Mon Jan 24 04:00:18 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 DF05C3A6863 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 04:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.215
X-Spam-Level: 
X-Spam-Status: No, score=-2.215 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, J_CHICKENPOX_13=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 MLBjqFN4X7Hj for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 04:00:17 -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 4A0DF3A6845 for <ietf@ietf.org>; Mon, 24 Jan 2011 04:00:17 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 45C185F985D; Mon, 24 Jan 2011 12:02:54 +0000 (UTC) (envelope-from marka@isc.org)
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 farside.isc.org (Postfix) with ESMTP id 0BF1FE6030; Mon, 24 Jan 2011 12:02:52 +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 E2E3291F6FA; Mon, 24 Jan 2011 23:02:48 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
In-reply-to: Your message of "Mon, 24 Jan 2011 12:15:25 BST." <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp>
Date: Mon, 24 Jan 2011 23:02:48 +1100
Message-Id: <20110124120248.E2E3291F6FA@drugs.dv.isc.org>
Cc: mail-dated-1298302483.e6e7db@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: Mon, 24 Jan 2011 12:00:19 -0000

In message <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Brian E Carpenter wrote:
> > 
> > However, see draft-wing-v6ops-happy-eyeballs-ipv6
> 
> Yuk.  That approach appears to be from a completely different universe
> that solutions to the IPv4->IPv6 migration issue.
> 
> Instead of solving the problem where it originates, at the network level,
> it dumps the entire problem onto the application in the worst conceivable
> fashion.  It makes IPv6 and IPv4 worlds appear like two completely
> seperate and independent Internets, i.e. this proposal incurs on apps
> the exact same effort as migrating a completely different network protocol
> or completely different network.

The solution space is equally applicable to two IPv4 addresses or
two IPv6 addresses.  You start one, wait a short while to see if
it succeeds then start another, etc.  If the network is doing its
job you get a error back from it before you start the second and
you start it sooner.  If it isn't then you don't waste 30 seconds
for the connect to timeout.

If you have a abnormally long path then you get some embryonic
connections.  500ms is more than enough time to wait for a terrestrial
path to complete.  Sydney, Australia to Europe is high 3 hundreds
to low 4 hundreds of milliseconds.

% ~/a.out www.ripe.net
connect_to_host(www.ripe.net) -> 3 in 376 ms
% 

> If anyone had suggested that for a migration from PSTN to VoiP, then
> everyone would have to use two phones these days, dial in parallel
> and hang up on whichever call establishes second.

I've seen plenty of people pick up one phone dial then put the call
on speaker then pick up a second phone and dial a different number
and put it on speaker when trying to reach someone with two numbers
urgently.  They hang up which ever doesn't answer.

> The problem that this draft tries to solve at the app-level really
> ought to be solved at the network level.  Use IPv6 addresses that
> embed the alternative IPv4 address and have the network figure out
> whether the route is IPv6 clean and the connection can be established
> as IPv6 or only IPv4. (IPv4-NATing the IPv4 part of such an
> address along the way is probably "fun"...) ... for exactly those
> network interfaces that _have_ dual IPv4+IPv6 addresses.

Having good error recovery at the application layer hasn't been a
issue until now because 99.99% of sites were single homed.  This
is changing with almost a 100% of sites becoming multi-homed.  It's
time the applications learned how to work well in such a environment.

It might also mean that one might be able to stop having to deploy
DNS servers that track reachability just to get some robustness
that should have been there if clients wern't using naive connection
strategies.

B.T.W. the a.out above implements this sort of connection strategy
with a 500 ms wait before attempting the second connection.  The
wait for the 3rd connection is 250 ms, the 4th is 125 ms, the 5th
is 62 ms.  You get the pattern.  There are poll, select and thread
based versions.

Mark

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

From ron.even.tlv@gmail.com  Mon Jan 24 04:55:27 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 E7EA13A6873; Mon, 24 Jan 2011 04:55:27 -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 EvNOUUdyGxfz; Mon, 24 Jan 2011 04:55:26 -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 B10953A681B; Mon, 24 Jan 2011 04:55:25 -0800 (PST)
Received: by wwa36 with SMTP id 36so4863744wwa.13 for <multiple recipients>; Mon, 24 Jan 2011 04:58:19 -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=BLl+sqqhcU+WqzyleSwLwHMBOA18oqxAu7b7L/R3kuk=; b=gablu+JJ3NBsjIlhNDgCMK1w/g6Am3t6SirvxbY+f4m4hbpQqglW8bypn9DK3VwnMu 2yPUln7s+ymo7ePhH2Se+IbGGb1MBdDF8N6c4ovuA/xFHaq5+w4wNMQFUsbfcowSFXqy 1BxcqwlTzlzEpco0m5FsMbz1c5OA3zgGAUf34=
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=gW3jmH8ah/MGxdHFRKqss7b/4JGMzCnA5Pe1FuHZAj55krlv+c/fEELRr77y8Z1xsG cqIvlf0OjVieH5h7yHcn0i59Iu9r0xNxRVonJrqAToZdcgJjb75dp++v+vwJNnW+ELMU et7FWR8NGi0EMvWqoQfYw5BfDeOw8Qzo//ik4=
Received: by 10.216.185.199 with SMTP id u49mr4063405wem.45.1295873899527; Mon, 24 Jan 2011 04:58:19 -0800 (PST)
Received: from windows8d787f9 (bzq-109-64-30-137.red.bezeqint.net [109.64.30.137]) by mx.google.com with ESMTPS id b30sm6547564wen.1.2011.01.24.04.58.16 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 04:58:18 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-arkko-dual-stack-extra-lite.all@tools.ietf.org>, <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-arkko-dual-stack-extra-lite
Date: Mon, 24 Jan 2011 14:54:24 +0200
Message-ID: <4d3d776a.1ebdd80a.50b4.632e@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0479_01CBBBD6.9966FCD0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acu7xdFE2oElITEbTGWssnm/0IX5kg==
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: Mon, 24 Jan 2011 12:55:28 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0479_01CBBBD6.9966FCD0
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-arkko-dual-stack-extra-lite-03

Reviewer: Roni Even

Review Date:2011-1-24

IETF LC End Date: 2011-2-10

IESG Telechat date:

 

Summary: This draft is ready for publication.

 

Major issues:

 

 

Minor issues:

 

This document has a standard track intended status. It looks to me more of
informational type. 

 

 

Nits/editorial comments:

 


------=_NextPart_000_0479_01CBBBD6.9966FCD0
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Document: <span style=3D'font-family:"Courier =
New"'>draft-arkko-dual-stack-extra-lite-03<o:p></o:p></span></p><p =
class=3DMsoPlainText>Reviewer: Roni Even<o:p></o:p></p><p =
class=3DMsoPlainText>Review Date:2011&#8211;1&#8211;24<o:p></o:p></p><p =
class=3DMsoPlainText>IETF LC End Date: =
2011&#8211;2&#8211;10<o:p></o:p></p><p class=3DMsoPlainText>IESG =
Telechat date:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Summary: This draft is ready for =
publication.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>This document has a standard track intended status. =
It looks to me more of informational type. <o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0479_01CBBBD6.9966FCD0--


From hallam@gmail.com  Mon Jan 24 04:56:26 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 399573A684E for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 04:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.853
X-Spam-Level: 
X-Spam-Status: No, score=-2.853 tagged_above=-999 required=5 tests=[AWL=-0.488, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_FINCLOP=0.633]
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 8jCTpJpXElrc for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 04:56:24 -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 6D8FA3A687C for <ietf@ietf.org>; Mon, 24 Jan 2011 04:56:24 -0800 (PST)
Received: by yie19 with SMTP id 19so1480650yie.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 04:59:18 -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=umzwmS+K0hN5hLVjuXrZodzesO0DWdRr8rEJogoF2DY=; b=AVTOlYYzvvJpWrMpdpGXS2jz5bD7qSG9tnKKHQaCJZAU2HLqivZJM034HkRN1YTb1l qTpm598RMSzOYGcN5eXBYhzM8myaZ0oDYkPSHGqrHMVRLzxwaXrwDe2W/Mb9coD0bmT9 CkhYtnYtYPS/nOFVImozRCevEyoB0YIpe8qog=
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=BtLRWkUjzxYGTujTWp62NfSI1DOs0uMRkQdIgWvdN0+znhEXZZ8nDJKpH+ZjHX1a9T JX2dWVQtMFlVnFfiH0MfNq3te0lfOSm/UT2IQMlAJs2CGvEPAVkgEEjYy+Xkvs/R5yzC s2BSZc/WGiiHFazzt2yNn0RmVvG2IaatwigNA=
MIME-Version: 1.0
Received: by 10.100.8.9 with SMTP id 9mr2960253anh.120.1295873958267; Mon, 24 Jan 2011 04:59:18 -0800 (PST)
Received: by 10.100.109.16 with HTTP; Mon, 24 Jan 2011 04:59:18 -0800 (PST)
In-Reply-To: <20110124120248.E2E3291F6FA@drugs.dv.isc.org>
References: <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp> <20110124120248.E2E3291F6FA@drugs.dv.isc.org>
Date: Mon, 24 Jan 2011 07:59:18 -0500
Message-ID: <AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Mark Andrews <marka@isc.org>
Content-Type: multipart/alternative; boundary=0016e6441dd8f4cd0d049a972a98
Cc: mail-dated-1298302483.e6e7db@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: Mon, 24 Jan 2011 12:56:26 -0000

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

Sure people can do this, but what is the point?

Let us imagine that as a matter of national policy we are all to live in
smaller houses to save energy. In what respect would such a policy be
realized if everyone bought a second, smaller house and started occupying
both simultaneously?


The critical objective here is to create a situation where people can use
the Internet successfully without requiring a full IPv4 address.

It is not going to be the case that anyone can use pure IPv6 100% of the
time for several decades.

Getting people to use IPv6 is not an end in itself. If you have a full IPv4
address there is no point in using IPv6 in parallel.

Its like buying a Prius to show how ecological you are and towing it behind
your Hummer.


The case where this dual stack is going to make sense is where the user has
a shared IPv4 and clean IPv6 and there is a performance advantage to going
through the clean connection.

This is not something that I would want to have to code for as an
application programmer. I would want to have a call of the form 'get best
connection for (protocol, domain_name) and have the platform figure it out
using information that I would not want the application programmer to have
access to.

<eom>




On Mon, Jan 24, 2011 at 7:02 AM, Mark Andrews <marka@isc.org> wrote:

>
> In message <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp>, Martin Rex
> writes
> :
> > Brian E Carpenter wrote:
> > >
> > > However, see draft-wing-v6ops-happy-eyeballs-ipv6
> >
> > Yuk.  That approach appears to be from a completely different universe
> > that solutions to the IPv4->IPv6 migration issue.
> >
> > Instead of solving the problem where it originates, at the network level,
> > it dumps the entire problem onto the application in the worst conceivable
> > fashion.  It makes IPv6 and IPv4 worlds appear like two completely
> > seperate and independent Internets, i.e. this proposal incurs on apps
> > the exact same effort as migrating a completely different network
> protocol
> > or completely different network.
>
> The solution space is equally applicable to two IPv4 addresses or
> two IPv6 addresses.  You start one, wait a short while to see if
> it succeeds then start another, etc.  If the network is doing its
> job you get a error back from it before you start the second and
> you start it sooner.  If it isn't then you don't waste 30 seconds
> for the connect to timeout.
>
> If you have a abnormally long path then you get some embryonic
> connections.  500ms is more than enough time to wait for a terrestrial
> path to complete.  Sydney, Australia to Europe is high 3 hundreds
> to low 4 hundreds of milliseconds.
>
> % ~/a.out www.ripe.net
> connect_to_host(www.ripe.net) -> 3 in 376 ms
> %
>
> > If anyone had suggested that for a migration from PSTN to VoiP, then
> > everyone would have to use two phones these days, dial in parallel
> > and hang up on whichever call establishes second.
>
> I've seen plenty of people pick up one phone dial then put the call
> on speaker then pick up a second phone and dial a different number
> and put it on speaker when trying to reach someone with two numbers
> urgently.  They hang up which ever doesn't answer.
>
> > The problem that this draft tries to solve at the app-level really
> > ought to be solved at the network level.  Use IPv6 addresses that
> > embed the alternative IPv4 address and have the network figure out
> > whether the route is IPv6 clean and the connection can be established
> > as IPv6 or only IPv4. (IPv4-NATing the IPv4 part of such an
> > address along the way is probably "fun"...) ... for exactly those
> > network interfaces that _have_ dual IPv4+IPv6 addresses.
>
> Having good error recovery at the application layer hasn't been a
> issue until now because 99.99% of sites were single homed.  This
> is changing with almost a 100% of sites becoming multi-homed.  It's
> time the applications learned how to work well in such a environment.
>
> It might also mean that one might be able to stop having to deploy
> DNS servers that track reachability just to get some robustness
> that should have been there if clients wern't using naive connection
> strategies.
>
> B.T.W. the a.out above implements this sort of connection strategy
> with a 500 ms wait before attempting the second connection.  The
> wait for the 3rd connection is 250 ms, the 4th is 125 ms, the 5th
> is 62 ms.  You get the pattern.  There are poll, select and thread
> based versions.
>
> Mark
>
> > -Martin
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

Sure people can do this, but what is the point?<div><br></div><div>Let us i=
magine that as a matter of national policy we are all to live in smaller ho=
uses to save energy. In what respect would such a policy be realized if eve=
ryone bought a second, smaller house and started occupying both simultaneou=
sly?</div>
<div><br></div><div><br></div><div>The critical objective here is to create=
 a situation where people can use the Internet successfully without requiri=
ng a full IPv4 address.</div><div><br></div><div>It is not going to be the =
case that anyone can use pure IPv6 100% of the time for several decades.</d=
iv>
<div><br></div><div>Getting people to use IPv6 is not an end in itself. If =
you have a full IPv4 address there is no point in using IPv6 in parallel.=
=A0</div><div><br></div><div>Its like buying a Prius to show how ecological=
 you are and towing it behind your Hummer.</div>
<div><br></div><div><br></div><div>The case where this dual stack is going =
to make sense is where the user has a shared IPv4 and clean IPv6 and there =
is a performance advantage to going through the clean connection.</div>
<div><br></div><div>This is not something that I would want to have to code=
 for as an application programmer. I would want to have a call of the form =
&#39;get best connection for (protocol, domain_name) and have the platform =
figure it out using information that I would not want the application progr=
ammer to have access to.</div>
<div><br></div><div>&lt;eom&gt;</div><div><br></div><div><br></div><div><br=
></div><div><br></div><div><div class=3D"gmail_quote">On Mon, Jan 24, 2011 =
at 7:02 AM, Mark Andrews <span dir=3D"ltr">&lt;<a href=3D"mailto:marka@isc.=
org">marka@isc.org</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;"><br>
In message &lt;201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp&gt;, Martin =
Rex writes<br>
:<br>
<div class=3D"im">&gt; Brian E Carpenter wrote:<br>
&gt; &gt;<br>
&gt; &gt; However, see draft-wing-v6ops-happy-eyeballs-ipv6<br>
&gt;<br>
&gt; Yuk. =A0That approach appears to be from a completely different univer=
se<br>
&gt; that solutions to the IPv4-&gt;IPv6 migration issue.<br>
&gt;<br>
&gt; Instead of solving the problem where it originates, at the network lev=
el,<br>
&gt; it dumps the entire problem onto the application in the worst conceiva=
ble<br>
&gt; fashion. =A0It makes IPv6 and IPv4 worlds appear like two completely<b=
r>
&gt; seperate and independent Internets, i.e. this proposal incurs on apps<=
br>
&gt; the exact same effort as migrating a completely different network prot=
ocol<br>
&gt; or completely different network.<br>
<br>
</div>The solution space is equally applicable to two IPv4 addresses or<br>
two IPv6 addresses. =A0You start one, wait a short while to see if<br>
it succeeds then start another, etc. =A0If the network is doing its<br>
job you get a error back from it before you start the second and<br>
you start it sooner. =A0If it isn&#39;t then you don&#39;t waste 30 seconds=
<br>
for the connect to timeout.<br>
<br>
If you have a abnormally long path then you get some embryonic<br>
connections. =A0500ms is more than enough time to wait for a terrestrial<br=
>
path to complete. =A0Sydney, Australia to Europe is high 3 hundreds<br>
to low 4 hundreds of milliseconds.<br>
<br>
% ~/a.out <a href=3D"http://www.ripe.net" target=3D"_blank">www.ripe.net</a=
><br>
connect_to_host(<a href=3D"http://www.ripe.net" target=3D"_blank">www.ripe.=
net</a>) -&gt; 3 in 376 ms<br>
%<br>
<div class=3D"im"><br>
&gt; If anyone had suggested that for a migration from PSTN to VoiP, then<b=
r>
&gt; everyone would have to use two phones these days, dial in parallel<br>
&gt; and hang up on whichever call establishes second.<br>
<br>
</div>I&#39;ve seen plenty of people pick up one phone dial then put the ca=
ll<br>
on speaker then pick up a second phone and dial a different number<br>
and put it on speaker when trying to reach someone with two numbers<br>
urgently. =A0They hang up which ever doesn&#39;t answer.<br>
<div class=3D"im"><br>
&gt; The problem that this draft tries to solve at the app-level really<br>
&gt; ought to be solved at the network level. =A0Use IPv6 addresses that<br=
>
&gt; embed the alternative IPv4 address and have the network figure out<br>
&gt; whether the route is IPv6 clean and the connection can be established<=
br>
&gt; as IPv6 or only IPv4. (IPv4-NATing the IPv4 part of such an<br>
&gt; address along the way is probably &quot;fun&quot;...) ... for exactly =
those<br>
&gt; network interfaces that _have_ dual IPv4+IPv6 addresses.<br>
<br>
</div>Having good error recovery at the application layer hasn&#39;t been a=
<br>
issue until now because 99.99% of sites were single homed. =A0This<br>
is changing with almost a 100% of sites becoming multi-homed. =A0It&#39;s<b=
r>
time the applications learned how to work well in such a environment.<br>
<br>
It might also mean that one might be able to stop having to deploy<br>
DNS servers that track reachability just to get some robustness<br>
that should have been there if clients wern&#39;t using naive connection<br=
>
strategies.<br>
<br>
B.T.W. the a.out above implements this sort of connection strategy<br>
with a 500 ms wait before attempting the second connection. =A0The<br>
wait for the 3rd connection is 250 ms, the 4th is 125 ms, the 5th<br>
is 62 ms. =A0You get the pattern. =A0There are poll, select and thread<br>
based versions.<br>
<br>
Mark<br>
<div class=3D"im"><br>
&gt; -Martin<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; <a href=3D"mailto:Ietf@ietf.org">Ietf@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/ietf</a><br>
</div><font color=3D"#888888">--<br>
Mark Andrews, ISC<br>
1 Seymour St., Dundas Valley, NSW 2117, Australia<br>
PHONE: +61 2 9871 4742 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: <a href=3D=
"mailto:marka@isc.org">marka@isc.org</a><br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<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>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e6441dd8f4cd0d049a972a98--

From marka@isc.org  Mon Jan 24 05:32:52 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 F1CE53A6AC3 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 05:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.191
X-Spam-Level: 
X-Spam-Status: No, score=-2.191 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, SARE_FINCLOP=0.633]
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 2ojBDnmVI56g for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 05:32:51 -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 E28AF3A687A for <ietf@ietf.org>; Mon, 24 Jan 2011 05:32:50 -0800 (PST)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id C60B75F9861; Mon, 24 Jan 2011 13:35:30 +0000 (UTC) (envelope-from marka@isc.org)
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 farside.isc.org (Postfix) with ESMTP id ECADAE6030; Mon, 24 Jan 2011 13:35:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id DECCF91FD2E; Tue, 25 Jan 2011 00:35:24 +1100 (EST)
To: Phillip Hallam-Baker <hallam@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp> <20110124120248.E2E3291F6FA@drugs.dv.isc.org><AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
In-reply-to: Your message of "Mon, 24 Jan 2011 07:59:18 CDT." <AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com>
Date: Tue, 25 Jan 2011 00:35:24 +1100
Message-Id: <20110124133524.DECCF91FD2E@drugs.dv.isc.org>
Cc: mail-dated-1298302483.e6e7db@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: Mon, 24 Jan 2011 13:32:52 -0000

In message <AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com>, Phil
lip Hallam-Baker writes:
> 
> Sure people can do this, but what is the point?
> 
> Let us imagine that as a matter of national policy we are all to live in
> smaller houses to save energy. In what respect would such a policy be
> realized if everyone bought a second, smaller house and started occupying
> both simultaneously?
> 
> The critical objective here is to create a situation where people can use
> the Internet successfully without requiring a full IPv4 address.
> 
> It is not going to be the case that anyone can use pure IPv6 100% of the
> time for several decades.

Who is talking pure IPv6 yet?  I'm talking multi-homed.  Multiple
A's, A's and AAAA's or multiple AAAA's.  I don't care which.  The
path to one of those addresses is broken and the network is not
reporting it.  The question is how to make the application behave
well in such a enviorment and also not be a bad network citizen
when all the addresses are reachable.

> Getting people to use IPv6 is not an end in itself. If you have a full IPv4
> address there is no point in using IPv6 in parallel.

I will agree that when everything is working as expected it doesn't
matter if you use IPv4 or IPv6.  However we are not discussing this
senario.  We are discussing the senario where one of the paths is
broken and not returning error messages and you don't know it is
broken without trying it.

> The case where this dual stack is going to make sense is where the user has
> a shared IPv4 and clean IPv6 and there is a performance advantage to going
> through the clean connection.

That's one case but not the only one.

> This is not something that I would want to have to code for as an
> application programmer. I would want to have a call of the form 'get best
> connection for (protocol, domain_name) and have the platform figure it out
> using information that I would not want the application programmer to have
> access to.

Does it really matter if it in the application or a library.  The
problem is still the same.

Mark

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

From bzbarsky@mit.edu  Fri Jan 21 21:00:16 2011
Return-Path: <bzbarsky@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 46E0F3A6B09 for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 21:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_55=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 wxw0vwMauYwu for <ietf@core3.amsl.com>; Fri, 21 Jan 2011 21:00:15 -0800 (PST)
Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by core3.amsl.com (Postfix) with ESMTP id 454823A68AA for <ietf@ietf.org>; Fri, 21 Jan 2011 21:00:15 -0800 (PST)
X-AuditID: 12074423-b7bd0ae000000a00-0f-4d3a65067157
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-6.mit.edu (Symantec Brightmail Gateway) with SMTP id 3E.DD.02560.6056A3D4; Sat, 22 Jan 2011 00:03:02 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id p0M5320g021417 for <ietf@ietf.org>; Sat, 22 Jan 2011 00:03:02 -0500
Received: from Boris-Zbarskys-MacBook-Pro-2.local (pool-71-184-125-56.bstnma.fios.verizon.net [71.184.125.56]) (authenticated bits=0) (User authenticated as bzbarsky@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p0M52tp7003828 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sat, 22 Jan 2011 00:03:02 -0500 (EST)
Message-ID: <4D3A64FF.1020000@mit.edu>
Date: Sat, 22 Jan 2011 00:02:55 -0500
From: Boris Zbarsky <bzbarsky@MIT.EDU>
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: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
X-Mailman-Approved-At: Mon, 24 Jan 2011 08:06:44 -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, 22 Jan 2011 05:36:10 -0000

There seem to be two differences between what the draft specifies right 
now and what Gecko, at least, does:

1) Section 5.3 says:

    Applications SHOULD resolve unrecognized "about" URIs in the
    same way as "about:blank".

Gecko treats unknown about:* as unparseable URIs, and is not likely to 
change that behavior.  While that's allowed by the SHOULD, it's not 
clear to me why this is a SHOULD as opposed to a MAY, nor is it clear 
why this is present at all.  In particular, as specified this will cause 
situations where an empty resource is silently returned instead of a 
failure that the consumer can notice (e.g. in the DOM case via error 
event handlers and the like).

2)  Section 6 says:

   For example, "about:blank", "about:blan%6B" and "about:blan%6b"
   are equivalent

In Gecko they are not.  The string after ':' is treated as a literal 
string; when looking up a way to handle the URI the second and third 
URIs above are treated as unparseable by Gecko in its default 
configuration.  Changing this has some security implications that would 
require careful auditing of not only Gecko code but some specifications 
(e.g. HTML5 defines certain special-case security behavior for 
about:blank that's not obviously safe to apply to the other strings above).

The same section says:

   Similarly, "about:blank%3F" is not equivalent to "about:blank?".

which I think is trying to explain by example that only unreserved 
characters need to be unescaped.  But that assumes an implementation of 
RFC 3986 which may or may not be the case in web browsers (and is NOT 
the case in Gecko, for example, for various web-compatibility reasons). 
  Unless there are very strong reasons for it, I would recommend that no 
normalization is performed on about: URIs, period.

-Boris

From Even.roni@huawei.com  Sat Jan 22 23:18:22 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 398323A6BC8; Sat, 22 Jan 2011 23:18:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.495
X-Spam-Level: 
X-Spam-Status: No, score=-104.495 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 yrSU7FAwYJ0d; Sat, 22 Jan 2011 23:18:20 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 6D8063A68D0; Sat, 22 Jan 2011 23:18:19 -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 <0LFG007PXSEZ9M@szxga03-in.huawei.com>; Sun, 23 Jan 2011 15:21:00 +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 <0LFG00CR8SEZ7W@szxga03-in.huawei.com>; Sun, 23 Jan 2011 15:20:59 +0800 (CST)
Received: from windows8d787f9 (bzq-79-178-7-189.red.bezeqint.net [79.178.7.189]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LFG00ALLSEPFT@szxml01-in.huawei.com>; Sun, 23 Jan 2011 15:20:59 +0800 (CST)
Date: Sun, 23 Jan 2011 09:16:59 +0200
From: Roni Even <Even.roni@huawei.com>
Subject: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14
To: draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org, gen-art@ietf.org
Message-id: <03dc01cbbacd$8bff0880$a3fd1980$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_Cf6IZJkf8NxMXjTl8ZfJpQ)"
Content-language: en-us
Thread-index: Acu6zYUM9zrofD2DQv+vmHiCppfgbA==
X-Mailman-Approved-At: Mon, 24 Jan 2011 08:06:45 -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, 23 Jan 2011 07:18:22 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_Cf6IZJkf8NxMXjTl8ZfJpQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi,

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-pwe3-oam-msg-map-14

Reviewer: Roni Even

Review Date:2011-1-23

IETF LC End Date: 2011-1-24

IESG Telechat date:

 

Summary: This draft is ready for publication as a Standard track RFC.

 

Major issues:

 

 

Minor issues:

 

 

Nits/editorial comments:

 

1.  The document starts with Contributors and acknowledgments section. I
think that this is not the major reason for the document and suggest moving
these two sections to the end of the document.

2.  In the Abbreviations and Conventions section which includes the
terminology it may be good to reference the terminology from RFC3985.

3.  Towards the end of section 7 and in the beginning of section 11 you
RFC5087 not as a reference while in other places you have it as a reference.
I think it should be written as a reference.

 

 

 


--Boundary_(ID_Cf6IZJkf8NxMXjTl8ZfJpQ)
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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:304356142;
	mso-list-type:hybrid;
	mso-list-template-ids:-302068210 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;}
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>Hi,<o:p></o:p></p><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><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Document: <span style=3D'font-family:"Courier =
New"'>draft-ietf-pwe3-oam-msg-map-14<o:p></o:p></span></p><p =
class=3DMsoPlainText>Reviewer: Roni Even<o:p></o:p></p><p =
class=3DMsoPlainText>Review Date:2011&#8211;1&#8211;23<o:p></o:p></p><p =
class=3DMsoPlainText>IETF LC End Date: =
2011&#8211;1&#8211;24<o:p></o:p></p><p class=3DMsoPlainText>IESG =
Telechat date:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Summary: This draft is ready for publication as a =
Standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>The document starts with =
Contributors and acknowledgments section. I think that this is not the =
major reason for the document and suggest moving these two sections to =
the end of the document.<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>In the Abbreviations and =
Conventions section which includes the terminology it may be good to =
reference the terminology from RFC3985.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>Towards the end of =
section 7 and in the beginning of section 11 you RFC5087 not as a =
reference while in other places you have it as a reference. I think it =
should be written as a reference.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--Boundary_(ID_Cf6IZJkf8NxMXjTl8ZfJpQ)--

From housley@vigilsec.com  Mon Jan 24 09:34:16 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 AA71B3A6917 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 09:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, 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 bXO0JjoEMRWE for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 09:34:16 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by core3.amsl.com (Postfix) with ESMTP id EC31C3A6403 for <ietf@ietf.org>; Mon, 24 Jan 2011 09:34:15 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 2D4279A4783 for <ietf@ietf.org>; Mon, 24 Jan 2011 12:37:28 -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 Sls5nbhPbr4m for <ietf@ietf.org>; Mon, 24 Jan 2011 12:37:02 -0500 (EST)
Received: from new-host.home (pool-96-255-143-234.washdc.fios.verizon.net [96.255.143.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9B07A9A471B for <ietf@ietf.org>; Mon, 24 Jan 2011 12:37:27 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: draft-housley-two-maturity-levels
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20101027171037.GB3162@nsn.com>
Date: Mon, 24 Jan 2011 12:37:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com>
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com> <01NTJJR8423E000CVY@mauve.mrochek.com> <20101027171037.GB3162@nsn.com>
To: 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, 24 Jan 2011 17:34:16 -0000

draft-housley-two-maturity-levels-03 was just posted.  It reflects much =
of the discussion on this thread over the last few months.  In =
particular, it embraces the changes put forward in the recent proposal =
by Dave Crocker, Eric Burger, Peter Saint-Andre, and Spencer Dawkins.  =
Please take a look at the revised document, and provide your thoughts.

Russ=

From ted.ietf@gmail.com  Mon Jan 24 09:59:24 2011
Return-Path: <ted.ietf@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 ECDA73A6B15 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 09:59:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.258
X-Spam-Level: 
X-Spam-Status: No, score=-3.258 tagged_above=-999 required=5 tests=[AWL=0.341,  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 C5n-8-EaWsED for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 09:59:24 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 11FA03A6B0F for <ietf@ietf.org>; Mon, 24 Jan 2011 09:59:23 -0800 (PST)
Received: by qwi2 with SMTP id 2so4591923qwi.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 10:02:18 -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=7wxtmNhN9wI6aDF4c3g9QJYbN+kDeUViXc1MHrUp9hw=; b=rtQiLGhdnylEkbTIXHRkeCRVGcDDyBWD3ILmA4Xe205Ziv72oB9FoDZ/P9lPiWTq55 8/OBcNYWpDNMMzVya/zNQs4FeXO6R7X9V+AJMnIO9mBjQLjFwRPN4ocmS0io2XDQAxfn QXL/LFISPZVbyVzvsIf5/oT9WHFeI//DGqjp8=
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=Hv1ymZBwwB0CaUUI57n+/bVqMkb+R8q6ZpQGeXf9yky5mMZxcXSvWlGpLyLDk7Weor F7rxU2oe46eFHMY37K8t0zqFuVmiHXpK7OwSbipaUPjNy3Panrf2L/Pcys2Pk2Y2tiHL s530mpaYA2BPMWoWpHS3DfTJLrFI7hfepgIBs=
MIME-Version: 1.0
Received: by 10.229.109.213 with SMTP id k21mr4050804qcp.3.1295892138529; Mon, 24 Jan 2011 10:02:18 -0800 (PST)
Received: by 10.229.230.138 with HTTP; Mon, 24 Jan 2011 10:02:18 -0800 (PST)
In-Reply-To: <4D3AA7AA.8090307@gmx.de>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net> <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com> <4D3943C8.5010206@gmx.de> <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com> <4D39C46C.3020804@gmx.de> <AANLkTik+T=vLMaG_WL5DLS-CPcaCW25ivF+xLcJBeugk@mail.gmail.com> <4D3AA7AA.8090307@gmx.de>
Date: Mon, 24 Jan 2011 10:02:18 -0800
Message-ID: <AANLkTi=w1OJasn+STOQO8hHWDOqv2m4hERNocd0j1h4A@mail.gmail.com>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
From: Ted Hardie <ted.ietf@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, 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, 24 Jan 2011 17:59:25 -0000

On Sat, Jan 22, 2011 at 1:47 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> I believe "about" qualifies for permanent as per
> <http://tools.ietf.org/html/rfc4395#section-2>, if there's something
> essential missing, we should fix it.
>
Hi Julian,

I think the key question is whether this qualifies as well-defined
(section 2.3).
The draft declares some tokens/strings to be "reserved", and names one such
string.  It also declares that other strings may be reserved by other
specifications,
but it provides no way to discover them.  This leads someone who wishes to mint
a new "about" uri with no way of discovering whether a specification
has reserved
it.  To me, that means "reserved" is not currently well-defined.

I would not personally propose HTML5 be the canonical source for reserving these
strings, because I have some serious reservations about that spec's tendency to
fork other specs.  But the conversation thus far leads to believe that the two
probably ways forward are to

1) have a registry and populate it with blank and those
from the HTML5 spec as initial values

2)make HTML5 the only spec which can reserve these strings, an move
blank into it.

I hope this is clear.

best regards,

Ted Hardie

From dworley@avaya.com  Mon Jan 24 10:00:23 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 253E63A692D for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, 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 i4S6gVshH18H for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:00:22 -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 1BFE73A691E for <ietf@ietf.org>; Mon, 24 Jan 2011 10:00:21 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACtNPU2HCzI1/2dsb2JhbACkaHOidgKYdoVQBIRwiXA
X-IronPort-AV: E=Sophos;i="4.60,370,1291611600"; d="scan'208";a="55802332"
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; 24 Jan 2011 13:03:16 -0500
X-IronPort-AV: E=Sophos;i="4.60,370,1291611600"; d="scan'208";a="587705107"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 24 Jan 2011 13:02:41 -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; Mon, 24 Jan 2011 13:02:40 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Sabahattin Gucukoglu <mail-dated-1298302483.e6e7db@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 24 Jan 2011 13:02:40 -0500
Subject: RE: Just Thinking (About the Nightmare Transition Ahead)
Thread-Topic: Just Thinking (About the Nightmare Transition Ahead)
Thread-Index: Acu6Se05arcbVCrHTGy4LOAZ/c9q+wBpVxcT
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767D7@DC-US1MBEX4.global.avaya.com>
References: <A7DFC328-44B1-455D-9893-0EE8BF354894@sabahattin-gucukoglu.com>
In-Reply-To: <A7DFC328-44B1-455D-9893-0EE8BF354894@sabahattin-gucukoglu.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: Mon, 24 Jan 2011 18:00:23 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Sabahattin=
 Gucukoglu [mail@sabahattin-gucukoglu.com]

My thought right now is perhaps of an OS update that includes a background =
client which tries very hard to reduce the effect of breakage or delay caus=
ed by IPv6 routes that are dead, DNS queries that don't go anywhere, and de=
lays caused by slow transition techniques.  It couldn't be comprehensive, b=
ut I think it'd go a long way at this point.  The software vendors could, f=
or instance, provide the test sites that receive IPv6 probes and/or traffic=
, and respond to them.  Not scalable? ...
_______________________________________________

An interesting concept.  It resembles ideas we've discussed but not impleme=
nted in our SIP stack:  For any given SIP destination, there may be many SR=
V records that give various redundant servers for that SIP domain.  Instead=
 of obeying the SRV records as they are given, falling back from the one wi=
th highest priority to the next highest priority, etc., keep track of which=
 addresses have recently been responding and which have not.  Those that ha=
ve not been responding have their SRV priority artificially lowered for the=
 purposes of the address-selection algorithm.  For addresses that need prom=
pt response but are not accessed on a short cycle, a background process can=
 send probes to keep the responsiveness information up to date.

An interesting aspect of this that might allow it to be generalized (at lea=
st in regard to applications that search for SRV records before A records) =
is that this could be implemented in a shim between the DNS lookup interfac=
e that the SIP stack uses and the real DNS:  The SRV records that the appli=
cation sees can be modified to give the desired effect.  And for SIP domain=
 lookups that do not have SRV records, SRV records can be synthesized to gi=
ve the desired effect.

In particular, if a domain name has an A record and an AAAA record, instead=
 of letting the application see (and choose between) these records directly=
:

domain.example.com    A    xx.yy.zz.ww
domain.example.com    AAAA    pppp::qqqq

the shim could construct:

_sip._tcp.domain.example.com    SRV    prio=3D1 weight=3D1 name=3DAAAA.doma=
in.example.com port=3D5060
_sip._tcp.domain.example.com    SRV    prio=3D100 weight=3D1 name=3DA.domai=
n.example.com port=3D5060

_sip._udp.domain.example.com    SRV    prio=3D1 weight=3D1 name=3DAAAA.doma=
in.example.com port=3D5060
_sip._udp.domain.example.com    SRV    prio=3D100 weight=3D1 name=3DA.domai=
n.example.com port=3D5060

A.domain.example.com    A    xx.yy.zz.ww
AAAA.domain.example.com    AAAA    pppp::qqqq

Thus, the shim has directed the SIP stack to try the IPv6 address first -- =
without any application change!

Dale

From stpeter@stpeter.im  Mon Jan 24 10:27:49 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 AB2B33A6907 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, 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 3EZlNbliAZmp for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:27:48 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 7D91D3A6B23 for <ietf@ietf.org>; Mon, 24 Jan 2011 10:27:48 -0800 (PST)
Received: from dhcp-64-101-72-234.cisco.com (dhcp-64-101-72-234.cisco.com [64.101.72.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E2D88400F6; Mon, 24 Jan 2011 11:46:47 -0700 (MST)
Message-ID: <4D3DC552.30708@stpeter.im>
Date: Mon, 24 Jan 2011 11:30:42 -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: Russ Housley <housley@vigilsec.com>
Subject: Re: draft-housley-two-maturity-levels
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com>	<01NTJJR8423E000CVY@mauve.mrochek.com>	<20101027171037.GB3162@nsn.com> <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com>
In-Reply-To: <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.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="------------ms020008020502060608030102"
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, 24 Jan 2011 18:27:49 -0000

This is a cryptographically signed message in MIME format.

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

On 1/24/11 10:37 AM, Russ Housley wrote:
> draft-housley-two-maturity-levels-03 was just posted.  It reflects
> much of the discussion on this thread over the last few months.  In
> particular, it embraces the changes put forward in the recent
> proposal by Dave Crocker, Eric Burger, Peter Saint-Andre, and Spencer
> Dawkins.  Please take a look at the revised document, and provide
> your thoughts.

Thanks, Russ.

A few comments:

1. It's not clear to me if this is quite correct in the Introduction:

   Similarly, subsequent revisions to the
   documents ought to be easier to publish, whether the document is
   advancing on the maturity ladder or not.

As discussion later in the I-D reveals, we don't want to make it easy
for folks to publish subsequent revisions that are significant, we want
to make it easy to publish adjustments based on implementation and
deployment experience:

   Experience with a Proposed Standard often leads to revisions that
   clarify, modify, enhance, or remove features.

See also:

   A specification may be, and indeed, is likely to be, revised as it
   advances from Proposed Standard to Internet Standard.  When a revised
   specification is proposed for advancement to Internet Standard, the
   IESG shall determine the scope and significance of the changes to the
   specification, and, if necessary and appropriate, modify the
   recommended action.  Minor revisions and the removal of unused
   features are expected, but a significant revision may require that
   the specification accumulate more experience at Proposed Standard
   before progressing.

I suggest:

   Similarly, it ought to be easier to publish revisions that
   incorporate implementation and deployment experience, whether the
   document is advancing on the maturity ladder or not.

2. I found this statement to be strange:

   The intention of the two-tier maturity
   ladder is to restore the requirements for Proposed Standard from RFC
   2026.

Why "restore"? Have they been superseded or ignored? I suggest "retain".

3. I think there is a word missing here:

   The rules that make references to documents at
   lower maturity levels are a major cause of stagnation in the
   advancement of documents.

Perhaps "The rules prohibiting references..."?

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms020008020502060608030102
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
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEy
NDE4MzA0MlowIwYJKoZIhvcNAQkEMRYEFDL5M2WaYzz5BNPra+KHUEXl7r3pMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQCIkAkzJCP0LpuCBG0v6O4K+tbm6YRUok85ckSd+OQH4ACB8C8E5d8AVede
NSUaTLY60988UOGtzTt7wZDwasSsv8xun8AxXMqKX5qBE1hk4Hrznjvc+N/ksl0NQvE9bPsN
viT44v9OxXeb7lqhMl7znCAPnNVyYW14+3BiX4QBbhKBSFpnXuwTVv5FkA5ZBlBfBisntC2V
vbMnaaCoX/TeaTdCLK7O2H+hH0r9MtFoEWamPs4gfeAqEfFGHHV4Ds4LsWAB4e/GtT7RkyPZ
TFfDsDeyCxYmOB8lytx3YLAgQTViGRp92J0hW1BHOXRU6Si961mTK9uiQZ1FGfniBK3kAAAA
AAAA
--------------ms020008020502060608030102--

From jmh@joelhalpern.com  Mon Jan 24 10:36:37 2011
Return-Path: <jmh@joelhalpern.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 636543A6B0B for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[AWL=-0.002, 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 dsO08mbGElJo for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:36:35 -0800 (PST)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id E954F3A6B23 for <ietf@ietf.org>; Mon, 24 Jan 2011 10:36:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 8BC7032461ED for <ietf@ietf.org>; Mon, 24 Jan 2011 10:39:31 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [10.10.10.102] (pool-71-161-52-40.clppva.btas.verizon.net [71.161.52.40]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id 26844322C025 for <ietf@ietf.org>; Mon, 24 Jan 2011 10:39:31 -0800 (PST)
Message-ID: <4D3DC75E.9060804@joelhalpern.com>
Date: Mon, 24 Jan 2011 13:39:26 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: draft-housley-two-maturity-levels
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com>	<01NTJJR8423E000CVY@mauve.mrochek.com>	<20101027171037.GB3162@nsn.com>	<63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com> <4D3DC552.30708@stpeter.im>
In-Reply-To: <4D3DC552.30708@stpeter.im>
Content-Type: text/plain; charset=UTF-8; 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: Mon, 24 Jan 2011 18:36:37 -0000

It seems to me that this proposal strikes a good balance in making an 
effort to improve the situation regarding our document track.

Regarding the particular clause:

On 1/24/2011 1:30 PM, Peter Saint-Andre wrote:
...
> 2. I found this statement to be strange:
>
>     The intention of the two-tier maturity
>     ladder is to restore the requirements for Proposed Standard from RFC
>     2026.
>
> Why "restore"? Have they been superseded or ignored? I suggest "retain".

I think the use of the word "restore" is very important. Over the years, 
our informal requirements and our sense of what was needed for Proposed 
Standard have moved up noticeably.  This reflected a number of factors, 
all of them driven as best I can tell by good intentions.
Restoring the lower bar for PS is probably the most direct benefit this 
proposal can have on our work.

Separately, the replacement of the requirement for verified 
interoperability with the assumption of interoperability based on wide 
deployment is an understandable compromise.  I am not sure I like this 
change, but I can live with it, which is good enough.

I do like the more relaxed wording on the removal of unused features.

Yours,
Joel M. Halpern

From stpeter@stpeter.im  Mon Jan 24 10:41:42 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 6469F3A6B26 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:41:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 bArAJT5mbPBr for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:41:41 -0800 (PST)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 6D6963A6B24 for <ietf@ietf.org>; Mon, 24 Jan 2011 10:41:41 -0800 (PST)
Received: from dhcp-64-101-72-234.cisco.com (dhcp-64-101-72-234.cisco.com [64.101.72.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 39401400F6; Mon, 24 Jan 2011 12:00:41 -0700 (MST)
Message-ID: <4D3DC893.4090409@stpeter.im>
Date: Mon, 24 Jan 2011 11:44:35 -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: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: draft-housley-two-maturity-levels
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com>	<01NTJJR8423E000CVY@mauve.mrochek.com>	<20101027171037.GB3162@nsn.com>	<63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com>	<4D3DC552.30708@stpeter.im> <4D3DC75E.9060804@joelhalpern.com>
In-Reply-To: <4D3DC75E.9060804@joelhalpern.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="------------ms070904050007070705050001"
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, 24 Jan 2011 18:41:42 -0000

This is a cryptographically signed message in MIME format.

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

On 1/24/11 11:39 AM, Joel M. Halpern wrote:
> It seems to me that this proposal strikes a good balance in making an
> effort to improve the situation regarding our document track.
>=20
> Regarding the particular clause:
>=20
> On 1/24/2011 1:30 PM, Peter Saint-Andre wrote:
> ...
>> 2. I found this statement to be strange:
>>
>>     The intention of the two-tier maturity
>>     ladder is to restore the requirements for Proposed Standard from R=
FC
>>     2026.
>>
>> Why "restore"? Have they been superseded or ignored? I suggest "retain=
".
>=20
> I think the use of the word "restore" is very important. Over the years=
,
> our informal requirements and our sense of what was needed for Proposed=

> Standard have moved up noticeably.  This reflected a number of factors,=

> all of them driven as best I can tell by good intentions.
> Restoring the lower bar for PS is probably the most direct benefit this=

> proposal can have on our work.

Aha: so restore operationally. That makes sense.

Peter

--=20
Peter Saint-Andre
https://stpeter.im/




--------------ms070904050007070705050001
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
BQCgggIOMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEy
NDE4NDQzNVowIwYJKoZIhvcNAQkEMRYEFL76/LczI8VpAtplVNvEVjHVoSuwMF8GCSqGSIb3
DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBpAYJKwYBBAGCNxAEMYGWMIGT
MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2Vj
dXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xh
c3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgCLMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIAizANBgkqhkiG
9w0BAQEFAASCAQC0cx2gc7t4Bzo9/+vBCcmKdMm96kqgOjt5j8ewkZaMq0Aib8+c56SDDpU0
I/R2t1hIvYqs1glq585o+6tu+5BaKOmWNxwUkH600MFuPW0O4yZhasBFM1UF+ozsYy/jHRd1
x+VC2VzE38Qym43ZYYrTvc7q5iTjTR84GzLnX3ACytbvfC0LEDIrYbIYnCKnbEAGIpTPhnkF
G8SYVW+iVCP/Oiky/z0s47xi2O/90bns3ch5/dJqH8cGIjWUN7oOlE/bT+CBZI7zAh2mtTT1
kKfKG5iXO6R6mh8kLJq2tF7r/N5jfMHbNuPv3zsvMb7iGOUPL0QpLXC4ztH0L4+JkHnqAAAA
AAAA
--------------ms070904050007070705050001--

From hallam@gmail.com  Mon Jan 24 10:54:09 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 A70883A6A83 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.467
X-Spam-Level: 
X-Spam-Status: No, score=-3.467 tagged_above=-999 required=5 tests=[AWL=0.131,  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 22XH2jtkYFid for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 10:54:08 -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 677AD3A698F for <ietf@ietf.org>; Mon, 24 Jan 2011 10:54:08 -0800 (PST)
Received: by yxt33 with SMTP id 33so1637220yxt.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 10:57:03 -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=3WU081DD7t1e+0x/gqlqkKN/EC09mZu1t6K+8PfjE08=; b=HYJ2WD7bpWwwQ9fqi7lMIdU16l4McdWgBjvvNghhq8kMfOh0Cpc+yfnjM3MklLpuND dOigiiYJyrm0AhsGgqlHfqqsc/94TGRVakr5cK8xrXoXgTrkrJQJdzoNjKD7QUm43ny4 0jeAlfMhg3hOhTPZtU1EfcNjn55z0PxaIzz1g=
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=g6/EsjR15iWDb5rtXEqPh3JbfTzkilKonYCSDOHY26o0SQVSnT1H/qYB7euMUmjZRK Hi1K8A/GqGsHy3O92p0xRK3Aiy+9fqMCrdcqpwY4IShEBfXPYFtGhrqJm29LHwAqCQoR OOlbOcnxCDcCFHl+DyZYuEZ5BQnBmMLP1XI1k=
MIME-Version: 1.0
Received: by 10.100.6.7 with SMTP id 7mr3155556anf.256.1295895423357; Mon, 24 Jan 2011 10:57:03 -0800 (PST)
Received: by 10.100.109.16 with HTTP; Mon, 24 Jan 2011 10:57:03 -0800 (PST)
In-Reply-To: <4D3DC75E.9060804@joelhalpern.com>
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com> <01NTJJR8423E000CVY@mauve.mrochek.com> <20101027171037.GB3162@nsn.com> <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com> <4D3DC552.30708@stpeter.im> <4D3DC75E.9060804@joelhalpern.com>
Date: Mon, 24 Jan 2011 13:57:03 -0500
Message-ID: <AANLkTi=+utUoE_ZsWeHYiQJmWbM3JorJEmX3X1ywDPMN@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=0016e642d3ba6015ac049a9c2a32
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, 24 Jan 2011 18:54:09 -0000

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

On Mon, Jan 24, 2011 at 1:39 PM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> It seems to me that this proposal strikes a good balance in making an
> effort to improve the situation regarding our document track.
>
> Regarding the particular clause:
>
> On 1/24/2011 1:30 PM, Peter Saint-Andre wrote:
> ...
>
>  2. I found this statement to be strange:
>>
>>    The intention of the two-tier maturity
>>    ladder is to restore the requirements for Proposed Standard from RFC
>>    2026.
>>
>> Why "restore"? Have they been superseded or ignored? I suggest "retain".
>>
>
> I think the use of the word "restore" is very important. Over the years,
> our informal requirements and our sense of what was needed for Proposed
> Standard have moved up noticeably.  This reflected a number of factors, all
> of them driven as best I can tell by good intentions.
> Restoring the lower bar for PS is probably the most direct benefit this
> proposal can have on our work.
>

I would like that to be possible, but I would settle for just being able to
make Standard status feasible.

One of the side effects of most drafts deadlocking at Proposed is that
people don't want to let anything 'bad' go through and that often means
something that people 'feel uncomfortable with'.


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

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

<br><br><div class=3D"gmail_quote">On Mon, Jan 24, 2011 at 1:39 PM, Joel M.=
 Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com">jmh@j=
oelhalpern.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It seems to me that this proposal strikes a good balance in making an effor=
t to improve the situation regarding our document track.<br>
<br>
Regarding the particular clause:<br>
<br>
On 1/24/2011 1:30 PM, Peter Saint-Andre wrote:<br>
...<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
2. I found this statement to be strange:<br>
<br>
 =A0 =A0The intention of the two-tier maturity<br>
 =A0 =A0ladder is to restore the requirements for Proposed Standard from RF=
C<br>
 =A0 =A02026.<br>
<br>
Why &quot;restore&quot;? Have they been superseded or ignored? I suggest &q=
uot;retain&quot;.<br>
</blockquote>
<br></div>
I think the use of the word &quot;restore&quot; is very important. Over the=
 years, our informal requirements and our sense of what was needed for Prop=
osed Standard have moved up noticeably. =A0This reflected a number of facto=
rs, all of them driven as best I can tell by good intentions.<br>

Restoring the lower bar for PS is probably the most direct benefit this pro=
posal can have on our work.<br></blockquote><div><br></div><div>I would lik=
e that to be possible, but I would settle for just being able to make Stand=
ard status feasible.</div>
<div><br></div><div>One of the side effects of most drafts deadlocking at P=
roposed is that people don&#39;t want to let anything &#39;bad&#39; go thro=
ugh and that often means something that people &#39;feel uncomfortable with=
&#39;.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br><br>

--0016e642d3ba6015ac049a9c2a32--

From dworley@avaya.com  Mon Jan 24 11:13: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 3AFE63A6B2A for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 11:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 NK4RnBcGHbsC for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 11:13:05 -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 74CC33A6919 for <ietf@ietf.org>; Mon, 24 Jan 2011 11:13:05 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAL9ePU3GmAcF/2dsb2JhbACkaXOiZwKYdIVQBIRwiXCCXg
X-IronPort-AV: E=Sophos;i="4.60,371,1291611600"; d="scan'208";a="55814337"
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 Jan 2011 14:15:54 -0500
X-IronPort-AV: E=Sophos;i="4.60,371,1291611600"; d="scan'208";a="574312616"
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; 24 Jan 2011 14:15:53 -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; Mon, 24 Jan 2011 14:15:53 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Bob Hinden <bob.hinden@gmail.com>, Marshall Eubanks <tme@americafree.tv>
Date: Mon, 24 Jan 2011 14:13:15 -0500
Subject: RE: IETF 83 Venue
Thread-Topic: IETF 83 Venue
Thread-Index: Acu7fMMVooYpzLIIQOi5/8bhAuYDXgAffzwq
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B220A1767D8@DC-US1MBEX4.global.avaya.com>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>, <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com>
In-Reply-To: <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <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, 24 Jan 2011 19:13:06 -0000

________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Bob Hinden=
 [bob.hinden@gmail.com]

Wasn't the official definition of the meter also tied to Paris?
_______________________________________________

The original measurement was done on a meridian from Dunkirk to Barcelona, =
based on the assumption that the Earth is rotationally symmetric.  But like=
 all good projects, that measurement effort made clear that its fundamental=
 hypotheses were false (that the Earth is rotationally symmetric and that c=
areful measurements could be done essentially without error).

Dale

From rja.lists@gmail.com  Mon Jan 24 13:49:41 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 B13413A6967 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 13:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.385
X-Spam-Level: 
X-Spam-Status: No, score=-3.385 tagged_above=-999 required=5 tests=[AWL=0.214,  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 Pbo4LLCSyPrZ for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 13:49:39 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 129C83A68EE for <ietf@ietf.org>; Mon, 24 Jan 2011 13:49:38 -0800 (PST)
Received: by vws7 with SMTP id 7so2083608vws.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 13:52:34 -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=55g3CUcUURkekeo3aAxUJeI8vc+i/Ia/PwtWSSoev68=; b=fpVwLaLlV1eWRP7bUnraQXehFr8r313scDiN/Q2IOBPkhzckgy0ExyaxsRZd5SE6ce IuiZh1P0P9tDNHP07bzB+uVvoX2DBRBHBSDJzqEGssH/3wQe48tfDR20v74DeteTQR7s IQAX45osZaMJlmxaSwoqkBK4jztnPPiE+Qymc=
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=qq/WdbuNkpse3WQFz9aQjqdHYX72MUV77/CYNk+ZT6p2fI7jf4fOvVSF4Gtb+Lbw13 VX5Tx/SDYVpXKGz7yyC0Nf1QLxVgLC6D0OYZhvmra+w12ICmZnkLUzY7oEzzLBipVq6E wyby9siat5tXgEbERC6gUBd08fSBkHVZYrsAM=
Received: by 10.220.185.79 with SMTP id cn15mr1411362vcb.54.1295905954530; Mon, 24 Jan 2011 13:52:34 -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 j15sm4060539vcs.44.2011.01.24.13.52.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 13:52:33 -0800 (PST)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: draft-housley-two-maturity-levels
Date: Mon, 24 Jan 2011 16:52:32 -0500
Message-Id: <91153BB8-DA2D-468D-9F4B-BBCF6D3731E7@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: Mon, 24 Jan 2011 21:49:41 -0000

Earlier, Joel Halpern wrote:
> It seems to me that this proposal strikes a good balance in making an =
effort
> to improve the situation regarding our document track.
>=20
> Regarding the particular clause:
>=20
>> On 1/24/2011 1:30 PM, Peter Saint-Andre wrote:
>> ...
>>=20
>> 2. I found this statement to be strange:
>>=20
>>     The intention of the two-tier maturity
>>     ladder is to restore the requirements for Proposed Standard from =
RFC
>>     2026.
>>=20
>> Why "restore"? Have they been superseded or ignored? I suggest =
"retain".
>=20
> I think the use of the word "restore" is very important. Over the =
years,=20
> our informal requirements and our sense of what was needed for =
Proposed Standard
> have moved up noticeably. This reflected a number of factors, all of =
them
> driven as best I can tell by good intentions.  Restoring the lower bar =
for PS
> is probably the most direct benefit this proposal can have on our =
work.
>=20
> Separately, the replacement of the requirement for verified =
interoperability
> with the assumption of interoperability based on wide deployment
> is an understandable compromise. I am not sure I like this change,
> but I can live with it, which is good enough.
>=20
> I do like the more relaxed wording on the removal of unused features.

+1 to Joel's comments.



From sm@resistor.net  Mon Jan 24 15:16:52 2011
Return-Path: <sm@resistor.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 930C83A69B5 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 15:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.609
X-Spam-Level: 
X-Spam-Status: No, score=-103.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 hARsyc5Ros6v for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 15:16:51 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 502373A69A5 for <ietf@ietf.org>; Mon, 24 Jan 2011 15:16:51 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0ONJYHr028277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2011 15:19:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1295911183; x=1295997583; bh=Eo317YBvXqSvGImKQEsIGDS6tBkUKJ6gRBHnr66atnQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=efQPYWPjivD/+At/EjRuLkOx7xGMz8GpIo9BF00qjuyNwV/CEJkHBYJvjnma3t13v ILHV95eg0SG89zJtikkWXDnM5zrcBAgi6q+k6IKBUEwaMOCsgegqFA3Dv+5dJQge0J mr3HcJEX0yY4CEALkAuyXQRbi5neW0XFgUJNyotU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1295911183; x=1295997583; bh=Eo317YBvXqSvGImKQEsIGDS6tBkUKJ6gRBHnr66atnQ=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=HGdg8+J6U33UGh2JRhd0dVhod5W1GPg+3OBr1bD7Q/DdpuZykvHm/HrDRUG83cOU7 mOKy5XRurM+v5ABYwPhQtmv6PUQZc7+0uyLI+LUzXtyMlCv/LycjnWFtdN7s2VSTmY oUH0mBrVOCmqomGSN8d2EMOviGxLZVbraHrjOE7E=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=WqkAHcSZJVPoG7fsZdA0X90SPdsTaR8Y7iIkk+ERD4cXrp88wHNGTdBT8qv/50qts cJuXzNP50UhcozPtCKtlcU51KlxL7E6pJOqo6JIOLJ+A8TukqnpkD7mAHjP22BEtkcG Hv6OKGzn0IJnpbrtrjEnRV0g9AhhZK4Vg8tXABA=
Message-Id: <6.2.5.6.2.20110124145857.0823dd18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Jan 2011 15:16:48 -0800
To: Ted Hardie <ted.ietf@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-holsten-about-uri-scheme-06.txt> (The 'about' URI scheme) to Proposed Standard
In-Reply-To: <AANLkTi=w1OJasn+STOQO8hHWDOqv2m4hERNocd0j1h4A@mail.gmail.c om>
References: <20110114155632.17927.70550.idtracker@localhost> <6.2.5.6.2.20110120110057.0d0f5228@resistor.net> <AANLkTikm7TYddiVBrG0m221KKZsUeaW7TZj_N+UbZ99P@mail.gmail.com> <4D3943C8.5010206@gmx.de> <AANLkTim3AMcdmvDrj1FHfCPStz+jxcpq64o2J-_VnrhB@mail.gmail.com> <4D39C46C.3020804@gmx.de> <AANLkTik+T=vLMaG_WL5DLS-CPcaCW25ivF+xLcJBeugk@mail.gmail.com> <4D3AA7AA.8090307@gmx.de> <AANLkTi=w1OJasn+STOQO8hHWDOqv2m4hERNocd0j1h4A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 24 Jan 2011 23:16:52 -0000

Hi Ted,
At 10:02 24-01-11, Ted Hardie wrote:
>I think the key question is whether this qualifies as well-defined
>(section 2.3).
>The draft declares some tokens/strings to be "reserved", and names one such
>string.  It also declares that other strings may be reserved by other
>specifications,
>but it provides no way to discover them.  This leads someone who 
>wishes to mint
>a new "about" uri with no way of discovering whether a specification
>has reserved
>it.  To me, that means "reserved" is not currently well-defined.

Yes.

>I would not personally propose HTML5 be the canonical source for 
>reserving these
>strings, because I have some serious reservations about that spec's 
>tendency to
>fork other specs.  But the conversation thus far leads to believe that the two
>probably ways forward are to
>
>1) have a registry and populate it with blank and those
>from the HTML5 spec as initial values
>
>2)make HTML5 the only spec which can reserve these strings, an move
>blank into it.

Agreed.

Regards,
-sm 


From huubatwork@gmail.com  Mon Jan 24 15:25:48 2011
Return-Path: <huubatwork@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 22DAF3A69B5 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 15:25:48 -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=[BAYES_00=-2.599, DIET_1=0.083, 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 U38-xnrm9YaP for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 15:25:47 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 3C7B93A69B6 for <ietf@ietf.org>; Mon, 24 Jan 2011 15:25:47 -0800 (PST)
Received: by qwi2 with SMTP id 2so4921314qwi.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 15:28:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:disposition-notification-to:date :from:user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=fuNES9zmeUOfBeN5Rht1TGzWUCaTSMEGLaF98HW6XL4=; b=IwBAoUl4ppYpBsGu3PLslUj5yhTWW83HVaB/7ivkgrTQhoyOBmBAEz1wXI4rUse2jm Z/1y2++mW4DPV4yUZQBCvYvFpbhHIIZ0ORoUL0JL0OsbWnsuZTkl1+m6DGJfDZwanlFB eSLFJmHmeJbI1+FcR2qaq5H5d5XsIyYt+CFDg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; b=yDIWw4i9PWAp7AS4r4oCKCOkTxQ2sZSPCoD1Vz/hYZc8N3VurnpT0C/Q4zvRa7CNtx t5WsbWxX63+u/dl9htXbbwlf+h/d5lmjvQ4aCLEbyQeHpJxkcFV1q3svXrZOGburNEQz Y3aask7CSWHt8pCnwIVyAHD6ZU3Ew0uoaOEe0=
Received: by 10.224.37.80 with SMTP id w16mr4632127qad.186.1295911722587; Mon, 24 Jan 2011 15:28:42 -0800 (PST)
Received: from McAsterix.local ([116.6.21.148]) by mx.google.com with ESMTPS id g32sm9748250qck.10.2011.01.24.15.28.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 15:28:41 -0800 (PST)
Message-ID: <4D3E0B24.9050602@gmail.com>
Date: Tue, 25 Jan 2011 00:28:36 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 83 Venue
References: <20110119213125.E3D2228C0F4@core3.amsl.com>	<201101210151.p0L1pqVe014924@sj-core-2.cisco.com>	<AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com>	<alpine.OSX.2.01.1101210808570.70222@macpro.local>	<AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com>	<4D39EE7B.6050507@earthlink.net>	<AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com>	<5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv>, <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com> <CD5674C3CD99574EBA7432465FC13C1B220A1767D8@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220A1767D8@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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, 24 Jan 2011 23:25:48 -0000

Hi,

In adition to the meter, also the platinum kilogram is in Paris.
Although recently it was found that it has lost some weight
(compared to its brothers and sisters in other locations)...

> Wasn't the official definition of the meter also tied to Paris?
> _______________________________________________
>
> The original measurement was done on a meridian from Dunkirk to Barcelona, based on the assumption that the Earth is rotationally symmetric.  But like all good projects, that measurement effort made clear that its fundamental hypotheses were false (that the Earth is rotationally symmetric and that careful measurements could be done essentially without error).
>
> Dale

Regards, Huub.


-- 
*****************************************************************
                          我爱外点一七三一

From tony@att.com  Mon Jan 24 20:11:23 2011
Return-Path: <tony@att.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 AA7AA28B797 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 20:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.535
X-Spam-Level: 
X-Spam-Status: No, score=-107.535 tagged_above=-999 required=5 tests=[AWL=1.064, BAYES_00=-2.599, GB_I_LETTER=-2, 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 ZJZRRipmhBAI for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 20:11:15 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by core3.amsl.com (Postfix) with ESMTP id 9FFBA3A6B76 for <ietf@ietf.org>; Mon, 24 Jan 2011 20:11:13 -0800 (PST)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-13.tower-119.messagelabs.com!1295928848!3354854!1
X-StarScan-Version: 6.2.9; banners=-,-,-
X-Originating-IP: [144.160.20.145]
Received: (qmail 22625 invoked from network); 25 Jan 2011 04:14:09 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-13.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Jan 2011 04:14:09 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0P4EVlP021150 for <ietf@ietf.org>; Mon, 24 Jan 2011 23:14:31 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by mlpd192.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id p0P4EOC0021073 for <ietf@ietf.org>; Mon, 24 Jan 2011 23:14:24 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p0P4E19J004708 for <ietf@ietf.org>; Mon, 24 Jan 2011 23:14:01 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id p0P4DpXW003698 for <ietf@ietf.org>; Mon, 24 Jan 2011 23:13:52 -0500
Received: from [135.70.111.58] (vpn-135-70-111-58.vpn.swst.att.com[135.70.111.58]) by maillennium.att.com (mailgw1) with ESMTP id <20110125041349gw100e4l9ke> (Authid: tony); Tue, 25 Jan 2011 04:13:50 +0000
X-Originating-IP: [135.70.111.58]
Message-ID: <4D3E4DFD.4060906@att.com>
Date: Mon, 24 Jan 2011 23:13:49 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; 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: draft-housley-two-maturity-levels
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com>	<01NTJJR8423E000CVY@mauve.mrochek.com>	<20101027171037.GB3162@nsn.com> <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com>
In-Reply-To: <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Tue, 25 Jan 2011 04:11:23 -0000

On 1/24/2011 12:37 PM, Russ Housley wrote:
> draft-housley-two-maturity-levels-03 was just posted. ...

Overall I find this spec to be an improvement over the previous version. 
Here are a few areas where improvements can be made.

====

This phrase in Section 1:

     In addition,
     IETF working groups and IESG members providing much more scrutiny
     than is called for by RFC 2026 [1] prior to publication as Proposed
     Standard.

is not a sentence. Should it be "provide"? Should it be "have been 
providing"? Something else?

====

The sentence in Section 1

     One desired outcome is to provide an environment where the
     IETF community is able to publish Proposed Standards as soon
     as rough consensus is achieved.

and these sentences in Section 2.1:

     The intention of the two-tier maturity
     ladder is to restore the requirements for Proposed Standard from RFC
     2026. No new requirements are introduced; no existing published
     requirements are relaxed.

together lay out what is required for PS. Disregarding the other 
arguments over the word "restore", these sentences are otherwise fine 
and dandy.

But I think there needs to be further guidance provided to the IESG and 
Working Groups on how they should change their behavior. What is wrong 
with how the WGs and IESG are currently interpreting the rules of 2026 
for PS? What current behaviors differ or have gone beyond what 2026 
requires, and hence need to be changed to restore those requirements? 
Without such guidance, nothing changes.

====

One major section that has been removed from the previous version of 
this I-D is what to do with documents currently in the Draft Standard 
status. I know that there was significant disagreement with the 
"automatic reclassification to Internet Standard" proposed before, with 
good reason.

I'm going to letter the the rules in section 2.2 as follows. I'm also 
going to indicate how these sort of map into the old classifications:

     a) technical maturity (DS => FS)
     b) belief in significant benefit to Internet community (DS => FS)
     c) significant number of implementations with successful 
operational experience (DS => FS)
     d) no unresolved errata (PS => DS)
     e) no unused features that increases implementation complexity (PS 
=> DS)

Some people have argued that having a significant number of 
implementations (c) is sufficient to demonstrate both technical maturity 
(a) and the belief in benefit (b). The (d) and (e) requirements have 
already been demonstrated by virtue of those RFCs already being at DS 
status, although additional errata may have been filed against the DS.

So I'm going to suggest that the following be applied to documents that 
are currently in Draft Standard status:

     Any protocol or service that is currently in Draft Standard status, 
without
     significant unresolved errata, may be reclassified as an Internet 
Standard
     as soon as it can be demonstrated to have a significant number of
     implementations with successful operational experience.

     This reclassification may be accomplished by filing a request with 
the IESG,
     detailing the Implementation and Operational Experience. After 
review, the
     IESG will hold an IETF-wide Last Call on the reclassification. If 
there is consensus
     for the reclassification, the RFC will be reclassified without 
being reissued.

     Protocols and services that have significant unresolved errata will 
need to be
     re-issued to resolve the errata before the above criteria can be 
applied.

Of course, there is still an open question what it means to have a 
"significant number", which will remain as subjective as it was before 
with the 2026 rules.

     Tony Hansen
     tony@att.com

From evnikita2@gmail.com  Mon Jan 24 22:01:45 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 7DF233A6B76 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 22:01:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.219
X-Spam-Level: 
X-Spam-Status: No, score=-3.219 tagged_above=-999 required=5 tests=[AWL=0.379,  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 ePo3irfK65aL for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 22:01:44 -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 9F3533A6B75 for <ietf@ietf.org>; Mon, 24 Jan 2011 22:01:43 -0800 (PST)
Received: by fxm9 with SMTP id 9so5325986fxm.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 22:04:39 -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=nxD/eEdA2j2LZCTVwXlnU3CaNF5ukRzVC+shl5eo1NQ=; b=B0mlFDnwfA8Z6qx+O0uyVewWUI08AiApumFI3e9PNL3S0zCcFZ8Mp67j+cimBMBFpl 1YkSvfQVZTzcXqcZv6LenYqUs32Mq9vp0QtAUXHizuOfkR0H8FYTgcMEv/Pyn2ZiJys9 8hJy+ufGrNOI+/Yx1FP/aMgHf282pC9/YzIn8=
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=fuxedTT/skvPegFzL27YEM/K0oFT+wbUohQss0FM+ybSxw+IgWtHt6lL7HLeob6riQ 8QR7UdrqAFrZbG83R0t6xOxCxZuyAZX4siBZhtUo6yob/STKTyXrSpvo3Lb/PZaIF4oZ GAVRvCoP95fOP6RuH/sAsVNjGtFJZsXGyVQSE=
Received: by 10.223.83.197 with SMTP id g5mr4751623fal.5.1295935479744; Mon, 24 Jan 2011 22:04:39 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id e6sm4878114fav.32.2011.01.24.22.04.38 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 22:04:38 -0800 (PST)
Message-ID: <4D3E680C.9060609@gmail.com>
Date: Tue, 25 Jan 2011 08:05:00 +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>
Subject: draft-yevstifeyev-genarea-historic - Clarifying the Historic status
Content-Type: multipart/alternative; boundary="------------060908000402040907070708"
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, 25 Jan 2011 06:01:45 -0000

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

Hello all,

A few weeks ago, if you remember, we had a discussion on moving 
Experimental RFCs to Historic.  Among other, we spoke that the 
definition of Historic status is not right and needs to be corrected.  
I'm citing the corresponding message:

> Hi,
>
>> >  I think that the author of RFC2026 was wrong while writing the definition of Historic status. This document says that Historic should be assigned only to that documents that were standards and now are obsolete. But why do we need such narrow definition? Non-standards RFCs are not made Historic while obsoleting, according to 2026. Moreover, such status will just duplicate the obsoleted-by one. When there will be the attempt to revise RFC 2026, we should put there that Historic status is to be assigned to that documents that are considered to be deprecated. I fully share the opinion of Doug here.
> If you think RFC20206 is wrong, then propose changes to it and see if people agree with the changes.  Until it is changed, IMHO you should not propose actions based on what you as an individual think is incorrect.  There needs to be a community consensus that RFC2026 is wrong before any action should be taken.
>
> Bob
>
So now I's like to introduce the Internet-Draft I've just submitted on 
this topic.  You may find it here:

https://datatracker.ietf.org/doc/draft-yevstifeyev-genarea-historic/?include_text=1

This documents defined the criteria for Historic docs, mentions 
procedures for republication and reclassification of docs as Historic 
RFCs and discusses other issues connected with this status.

So any comments regarding it are welcome.

All the best,
Mykyta Yevstifeyev



--------------060908000402040907070708
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 all,<br>
        <br>
        A few weeks ago, if you remember, we had a discussion on moving
        Experimental RFCs to Historic.  Among other, we spoke that the
        definition of Historic status is not right and needs to be
        corrected.  I'm citing the corresponding message:<br>
        <br>
        <blockquote type="cite">
          <div class="moz-text-plain" wrap="true" style="font-family:
            -moz-fixed; font-size: 13px;" lang="x-western">
            <pre wrap="">Hi,

</pre>
            <blockquote type="cite" style="color: rgb(0, 0, 0);">
              <pre wrap=""><span class="moz-txt-citetags">&gt; </span>I think that the author of RFC2026 was wrong while writing the definition of Historic status. This document says that Historic should be assigned only to that documents that were standards and now are obsolete. But why do we need such narrow definition? Non-standards RFCs are not made Historic while obsoleting, according to 2026. Moreover, such status will just duplicate the obsoleted-by one. When there will be the attempt to revise RFC 2026, we should put there that Historic status is to be assigned to that documents that are considered to be deprecated. I fully share the opinion of Doug here.
</pre>
            </blockquote>
            <pre wrap="">If you think RFC20206 is wrong, then propose changes to it and see if people agree with the changes.  Until it is changed, IMHO you should not propose actions based on what you as an individual think is incorrect.  There needs to be a community consensus that RFC2026 is wrong before any action should be taken.

Bob

</pre>
          </div>
        </blockquote>
        So now I's like to introduce the Internet-Draft I've just
        submitted on this topic.  You may find it here:<br>
        <br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-yevstifeyev-genarea-historic/?include_text=1">https://datatracker.ietf.org/doc/draft-yevstifeyev-genarea-historic/?include_text=1</a><br>
        <br>
        This documents defined the criteria for Historic docs, mentions
        procedures for republication and reclassification of docs as
        Historic RFCs and discusses other issues connected with this
        status.<br>
        <br>
        So any comments regarding it are welcome.<br>
        <br>
        All the best,<br>
        Mykyta Yevstifeyev<br>
        <br>
        <br>
      </big></font>
  </body>
</html>

--------------060908000402040907070708--

From evnikita2@gmail.com  Mon Jan 24 22:16:39 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 20FAB3A6A6A for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 22:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.223
X-Spam-Level: 
X-Spam-Status: No, score=-4.223 tagged_above=-999 required=5 tests=[AWL=1.376,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 nXZFK2qRtyUo for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 22:16:38 -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 9C4F93A6A60 for <ietf@ietf.org>; Mon, 24 Jan 2011 22:16:37 -0800 (PST)
Received: by fxm9 with SMTP id 9so5335203fxm.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 22:19:33 -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=1dprHOSG51HzNMdHeptR/KJyZQyIepo/2PAwB2wBs3A=; b=kjsXPw2QFUrwvpN28yB2otS5DncgT1ysYZSrxEDl4aX+qqSzAh9ukOMsm+frp1B41m TqvsjRfe60zqoWhAGZ0Ksx856CzcUaB1W0hc2QFC1b6PrJAptz0pUi9VQKi8I5CBlL7i 7kEKd1akYJJC1laYBtKP3lOW7ELWFDdAHqZ8s=
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=OYDXQx1qVIEm/b5P0L9PAMgcMOHwE6cFQOJZc1sYKMeuu+YlDm+/PLsDsv1qZVBRzz lVxgLCvfrUU6dbArcKcCLoSZBozkQsb+QXcsR7CK9rNoR4Ny0UCkKBZGRPR2TOfXyznP qM/ghAwd5avG05ca+ja0Ccd8JiaXnU+DGKUAw=
Received: by 10.223.100.4 with SMTP id w4mr5342951fan.115.1295936373400; Mon, 24 Jan 2011 22:19:33 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id c11sm4881415fav.2.2011.01.24.22.19.28 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 22:19:29 -0800 (PST)
Message-ID: <4D3E6B87.5030700@gmail.com>
Date: Tue, 25 Jan 2011 08:19:51 +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: Tony Hansen <tony@att.com>
Subject: Re: draft-housley-two-maturity-levels
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com>	<01NTJJR8423E000CVY@mauve.mrochek.com>	<20101027171037.GB3162@nsn.com>	<63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com> <4D3E4DFD.4060906@att.com>
In-Reply-To: <4D3E4DFD.4060906@att.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Tue, 25 Jan 2011 06:16:39 -0000

25.01.2011 6:13, Tony Hansen wrote:
> On 1/24/2011 12:37 PM, Russ Housley wrote:
>> draft-housley-two-maturity-levels-03 was just posted. ...
>
> Overall I find this spec to be an improvement over the previous 
> version. Here are a few areas where improvements can be made.
>
> ====
> [. . . . .]
>
> ====
>
> One major section that has been removed from the previous version of 
> this I-D is what to do with documents currently in the Draft Standard 
> status. I know that there was significant disagreement with the 
> "automatic reclassification to Internet Standard" proposed before, 
> with good reason.
>
> I'm going to letter the the rules in section 2.2 as follows. I'm also 
> going to indicate how these sort of map into the old classifications:
>
>     a) technical maturity (DS => FS)
>     b) belief in significant benefit to Internet community (DS => FS)
>     c) significant number of implementations with successful 
> operational experience (DS => FS)
>     d) no unresolved errata (PS => DS)
>     e) no unused features that increases implementation complexity (PS 
> => DS)
>
> Some people have argued that having a significant number of 
> implementations (c) is sufficient to demonstrate both technical 
> maturity (a) and the belief in benefit (b). The (d) and (e) 
> requirements have already been demonstrated by virtue of those RFCs 
> already being at DS status, although additional errata may have been 
> filed against the DS.
>
> So I'm going to suggest that the following be applied to documents 
> that are currently in Draft Standard status:
>
>     Any protocol or service that is currently in Draft Standard 
> status, without
>     significant unresolved errata, may be reclassified as an Internet 
> Standard
>     as soon as it can be demonstrated to have a significant number of
>     implementations with successful operational experience.
>
>     This reclassification may be accomplished by filing a request with 
> the IESG,
>     detailing the Implementation and Operational Experience. After 
> review, the
>     IESG will hold an IETF-wide Last Call on the reclassification. If 
> there is consensus
>     for the reclassification, the RFC will be reclassified without 
> being reissued.
>
>     Protocols and services that have significant unresolved errata 
> will need to be
>     re-issued to resolve the errata before the above criteria can be 
> applied.
>
> Of course, there is still an open question what it means to have a 
> "significant number", which will remain as subjective as it was before 
> with the 2026 rules.
Russ, Tony, all,

I think that Section 5, regarding STD numbers, does not fully introduce 
the topic and is not acceptable.  So I'd like to propose the following 
solution: the STD numbers are splitted into two groups: STD P-xxx and 
STD F-xxx, for proposed and full standards and assigned to all 
Standards-Track document once they move to one of these levels.   The 
number must then be the same for P- and F- groups, with one of them 
reserved while the doc is in the other level.  I.e. the doc is PS - STD 
F-xxx is reserved and vice versa.

This, IMO, will resolve the problem with STD numbers.

As for the issue with Draft Standards, I find that Tony proposed 
acceptable.  But we should mention that if reclassification to FS did 
not gain the consensus, the spec. is reclassified to Proposed Standard.

All the best,
Mykyta Yevstifeyev
>
>     Tony Hansen
>     tony@att.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From evnikita2@gmail.com  Mon Jan 24 22:21:54 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 78C833A6A5D for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 22:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.232
X-Spam-Level: 
X-Spam-Status: No, score=-3.232 tagged_above=-999 required=5 tests=[AWL=0.366,  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 qtq-Vl5zgTlP for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 22:21:53 -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 329923A6A60 for <ietf@ietf.org>; Mon, 24 Jan 2011 22:21:53 -0800 (PST)
Received: by fxm9 with SMTP id 9so5338428fxm.31 for <ietf@ietf.org>; Mon, 24 Jan 2011 22:24:49 -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=FQe+J3Qp3LilLuixZgOYmNzX5P5r7gr0VYecAqh75jk=; b=aPVToQMloiiJ78E8c23kr6P4Tmtf0mtc9gQc4lEUPLqxAbyFSlnXjB+ztiInP/gGRA LCb7dtaIjPZCIlhW6Ea7i6t2Z9Jc2LPDWOi3JKVAgG8uVwtw9kfdDe50CU1yoKk995S1 HmP9Bxp2GoKeET9wp/3+5UeMJ1jTiYT44cvFw=
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=G0mrXh25CUTCXiC+2t+zEwvY8ElwSgj8icxKsXFLvMTUntKRzDbiwriJYTcN5Ki5K1 xuNIh1+1e7jC/9nIfhk2WWqft0t68VDmsIBWj0JolJbxOt0rIQ4ApZnSc/MY8X1X+vVd JNj8GD9DOhPF0Utk61Nyac31srYGHISOMG9/4=
Received: by 10.223.79.74 with SMTP id o10mr2051967fak.63.1295936689472; Mon, 24 Jan 2011 22:24:49 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n26sm4882282fam.13.2011.01.24.22.24.47 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Jan 2011 22:24:48 -0800 (PST)
Message-ID: <4D3E6CC7.9010209@gmail.com>
Date: Tue, 25 Jan 2011 08:25:11 +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>
Subject: Revising Some Standards?
Content-Type: multipart/alternative; boundary="------------020700080903090901090402"
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, 25 Jan 2011 06:21:54 -0000

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

Hello all,

There are a number of Full Standards (STD20-24), that, IMO, need 
revsising.  Firstly, all of these documents define the protocols only 
for TCP and UDP, and that might be useful to define them for such 
protocols, as DCCP or SCTP.  Moreover, in spite of being the Full 
Standards, it does not meet the current practices and view of Internet 
Standards.

So I'd like to ask whether making docs to obsolete these standards make 
any sense?  Or it would be OK just to update the corresponding documents 
for DCCP and SCTP?

All the best,
Mykyta Yevstifeyev


--------------020700080903090901090402
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">
    <big><big><font size="-1"><big>Hello all,<br>
            <br>
            There are a number of Full Standards (STD20-24), that, IMO,
            need revsising.  Firstly, all of these documents define the
            protocols only for TCP and UDP, and that might be useful to
            define them for such protocols, as DCCP or SCTP.  Moreover,
            in spite of being the Full Standards, it does not meet the
            current practices and view of Internet Standards.<br>
            <br>
            So I'd like to ask whether making docs to obsolete these
            standards make any sense?  Or it would be OK just to update
            the corresponding documents for DCCP and SCTP?<br>
            <br>
            All the best,<br>
            Mykyta Yevstifeyev<br>
            <br>
          </big></font></big></big>
  </body>
</html>

--------------020700080903090901090402--

From lars.eggert@nokia.com  Tue Jan 25 03:17:04 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 55A483A6A94; Tue, 25 Jan 2011 03:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.169
X-Spam-Level: 
X-Spam-Status: No, score=-103.169 tagged_above=-999 required=5 tests=[AWL=-1.170, BAYES_00=-2.599, J_CHICKENPOX_15=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 4Jwp+uUfyNp7; Tue, 25 Jan 2011 03:17:03 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 9F6733A6836; Tue, 25 Jan 2011 03:17:03 -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 p0PBJth7023256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jan 2011 13:19:56 +0200
Subject: Re: [port-srv-reg] 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
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-26--180392143; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4D39811D.6070208@ericsson.com>
Date: Tue, 25 Jan 2011 13:19:47 +0200
Message-Id: <F983EA1F-CF15-4D42-AB21-9AB200C4E061@nokia.com>
References: <4D36A12C.9010301@ericsson.com> <00ec01cbb960$6499ef80$4001a8c0@gateway.2wire.net> <4D39811D.6070208@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.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); Tue, 25 Jan 2011 13:19:52 +0200 (EET)
X-Nokia-AV: Clean
Cc: ietf <ietf@ietf.org>, "port-srv-reg@ietf.org" <port-srv-reg@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, 25 Jan 2011 11:17:04 -0000

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

I've made this change in our working copy.

On 2011-1-21, at 14:50, Magnus Westerlund wrote:

> t.petch skrev 2011-01-21 12:43:
>> I would like to see more clarity in 8.1
>> " For assignments done through IETF-published RFCs, the Contact will =
be the
>> IESG."
>> in that I am unclear what IETF-published RFCs are; presumably that is =
Standards
>> Track, BCP
>> and Individual Submissions, but not Independent Submissions  or IRTF =
RFC.
>>=20
>> I think that the terminology here should follow that of RFC4844 with =
a reference
>> thereto.
>>=20
>=20
> I guess we should use the "IETF Stream", and I do agree that a =
reference
> for the definition of that should be included.


--Apple-Mail-26--180392143
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEyNTExMTk0OFowIwYJKoZIhvcNAQkE
MRYEFHcEfduhzct/p4vi4PothaWBP4N9MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AHSi6f6H2aTf1gRGmGOlotQV5qP9sqqhJlBSoIoszYnEOsPJYh/4EsgHGOrn+spNmLehWiUG/XYB
+WLSHfr07qAetJeVITdsOObUNMk4j0RI8zFI8zRUgVj6qTEdfDkauZ5y9mxldo+iwH1fZi7jPiyy
pY4h8MTJRd28+3+u0aEAlLzY8auulS0Xl09dlRA7ZxTgiDLPlocc5LPreaLfUpVheIPuQA4jOfn0
D6NwmbgkA3h8NjJ9Dy6pXCKe4OMM879gQGNYQHgaMbDINKJXwsi9HjHcKpQZFhEXRbe3b0QaTbrE
DWBQh0/LHu93/Dph2J5lLL5otf89BBaFy/mriaQAAAAAAAA=

--Apple-Mail-26--180392143--

From olaf@NLnetLabs.nl  Tue Jan 25 05:06:21 2011
Return-Path: <olaf@NLnetLabs.nl>
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 C2E4B28C0E7 for <ietf@core3.amsl.com>; Tue, 25 Jan 2011 05:06:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level: 
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.122, 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 1jjxRpbXzG2X for <ietf@core3.amsl.com>; Tue, 25 Jan 2011 05:06:03 -0800 (PST)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by core3.amsl.com (Postfix) with ESMTP id A49D33A6858 for <ietf@ietf.org>; Tue, 25 Jan 2011 05:06:02 -0800 (PST)
Received: from dhcp-14.nlnetlabs.nl (dhcp-14.nlnetlabs.nl [213.154.224.80]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.4/8.14.4) with ESMTP id p0PD8sQ4054122 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 Jan 2011 14:08:55 +0100 (CET) (envelope-from olaf@NLnetLabs.nl)
Subject: Re: IETF 83 Venue
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/signed; boundary=Apple-Mail-47--173845496; protocol="application/pkcs7-signature"; micalg=sha1
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <CEBCE3CF81D2D441B14B84256C3C46810BD83A88@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
Date: Tue, 25 Jan 2011 14:08:54 +0100
Message-Id: <2FD224E1-F4F2-4E0C-9CBF-1BFB56F7DB30@NLnetLabs.nl>
References: <20110119213125.E3D2228C0F4@core3.amsl.com> <201101210151.p0L1pqVe014924@sj-core-2.cisco.com> <AANLkTim=RWM9RYw5oERf4w65weWE2hsg5nLfpsh3Q4nU@mail.gmail.com> <alpine.OSX.2.01.1101210808570.70222@macpro.local> <AANLkTimSYFKf0+WMAbk0fnvM7RO=Xsc69DRMkAh1E7p_@mail.gmail.com> <4D39EE7B.6050507@earthlink.net> <AANLkTinBPop5grGQGS-=auU8A-U579BxsZFrr5kDUTuz@mail.gmail.com> <5B1399B2-1D26-452C-A331-24390144B42A@americafree.tv> <0B40C8D8-5331-4905-8BD8-279B008A1CB0@gmail.com> <CEBCE3CF81D2D441B14B84256C3C46810BD83A88@TK5EX14MBXW651.wingroup.windeploy.ntdev.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (open.nlnetlabs.nl [213.154.224.1]); Tue, 25 Jan 2011 14:08:56 +0100 (CET)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Discussion <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, 25 Jan 2011 13:06:21 -0000

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



[More NOISE, skip reading if you want SIGNAL]

On Jan 24, 2011, at 5:36 AM, Christian Huitema wrote:

>> Wasn't the official definition of the meter also tied to Paris?
>=20
> The invention of the meter is indeed tied to Paris. The value of the =
meter itself is not.
>=20
> The meter was defined by scientists commissioned by the French =
revolutionary assembly, but it is not exactly "tied to Paris." The =
original definition was 1/10,000,000 of a quarter of the Earth =
circumference, and the commission of scientists established the value by =
measuring an arc of the earth circumference between North of France and =
North of Spain. The unit was then materialized by a big platinum ruler =
kept in a locker in Paris. It is now defined in relation to the speed of =
light, itself set as 299,792,458 meters per second.
>=20

Reminds me of an excellent story where Superdupont saved the world from =
misery when a bunch of International Terrorists (with British and German =
accents) saved replaced the standard meter by a non-standard.

http://en.wikipedia.org/wiki/Superdupont


Since we are exchanging pedantic wise cracks. Instead of Platinum, we =
now find Cesium to be at the hearth of the measurement of a meter: =
299,792,458 meters per 9,192,631,770 periods of the radiation =
corresponding to the transition between the two hyperfine levels of the =
ground state of the cesium 133 atom.


Earlier PhB wrote:

> The idea that there is utility in leap seconds is ridiculous. Most =
astronomers I have talked to tell me that UTC is useless for their =
purposes anyway and the time of mid-day varies at Greenwich by 5 minutes =
over the course of a year so what does it matter which two days are =
right?

Julian Date is the date mostly used in observation records etc. (at =
least when I did my observing runs as a graduate student). The =
convenience of the Julian date is that you just keep counting, the Unix =
time guys did the same, except that there NULL epoch was in 1970 instead =
of 4713 BC  and the unit of counting is seconds instead of days =
(roughly).


PhB also said:
> What else is there to discuss in Paris?


I vividly remember =
http://www.ietf.org/mail-archive/web/ietf/current/msg36670.html so those =
discussion may eventually contribute to more noise on the IETF list.

--Olaf







________________________________________________________=20

Olaf M. Kolkman                        NLnet Labs
                                       Science Park 140,=20
http://www.nlnetlabs.nl/               1098 XG Amsterdam


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

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFMTCCBS0w
ggMVoAMCAQICAwbqdTANBgkqhkiG9w0BAQUFADB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQL
ExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3Jp
dHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZzAeFw0wOTA1MjUwODQ4MTJaFw0x
MTA1MjUwODQ4MTJaMDkxFTATBgNVBAMTDE9sYWYgS29sa21hbjEgMB4GCSqGSIb3DQEJARYRb2xh
ZkBubG5ldGxhYnMubmwwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxtZNngmuLgcf
rto+Uax1WhonECqb5W8US2Z+ZPw/ASKsjKEF8Wa3Nnispys6Gj9Sl7C1X0/2pH//qauLpBqA+lHW
L9mgdGW1T9KU1Fb8Odqw0PBnIIhbLNQzecZL+BchEetcrubplQWzDOpROCJ00IwXksusBiKqhew4
u7X2QoraW+z32Knj5ogajIhdkAeBHUy1pwXsk/mDnV8cIEdz1MhaZWDSn7kJUQtRMVCpFBjVoiXh
ToXMJfiMvn0CKaeFxFm72dcdzvFsw906Ndafd2MOfdP7QSsTVP6sG9am790AOgkzxT5CM77IDPbD
zxZlQ8jTdhcp/WtUrFWIU4QBAgMBAAGjgf0wgfowDAYDVR0TAQH/BAIwADBWBglghkgBhvhCAQ0E
SRZHVG8gZ2V0IHlvdXIgb3duIGNlcnRpZmljYXRlIGZvciBGUkVFIGhlYWQgb3ZlciB0byBodHRw
Oi8vd3d3LkNBY2VydC5vcmcwQAYDVR0lBDkwNwYIKwYBBQUHAwQGCCsGAQUFBwMCBgorBgEEAYI3
CgMEBgorBgEEAYI3CgMDBglghkgBhvhCBAEwMgYIKwYBBQUHAQEEJjAkMCIGCCsGAQUFBzABhhZo
dHRwOi8vb2NzcC5jYWNlcnQub3JnMBwGA1UdEQQVMBOBEW9sYWZAbmxuZXRsYWJzLm5sMA0GCSqG
SIb3DQEBBQUAA4ICAQCLpawAoUQAxivf6blyMswVokRmDl2JGEbtmEu8j0h1BVOlGh6hlI8WaeWy
3x2jJ9uun3VK6oYnHy45ez+dUDjBLjOZdAgwFg225lm1OPdmisghDDVwCIiEogHPqmJtvKYMFoPF
3iFUambJDoQF8DeVeg8ctDvsxsaVGjA8OrMpo0K4I11vnNbCLv7mWCjnaZWt/6Y6TD8ErHQl5dmI
rpsHmEZx1/nsocdPkZGRA4QVf1omYHUNs79DtxpYdGKHoorpBNzlzIIjpceiqeOeykoDeYLTZX2G
c7Mh4Gdj2MHFqZucxV1cHibb8XKv8ebaGltMV5SrciqRn8yFXmiyTvmId6myNXLiOx+VJiGbLSS3
TltM/kf7UejXeEHulEKufU6Ya6EfH7W2/spTayYCauyLljOjE2Ey5A4oIoJV9eY64OCDuLF2nmGR
jOh3JB9nGkZIPhmTUwGZnMELLhzKz+eOZoulM4tXH6KEubed1shQEq1dkJ+tFtRS3Lm+vLCKWvVo
1iZScqPaQf9riPApAVrL+3Wat0p/jtCk5gLBF02uTiWvT2t4ZfSHMEBXR7CvVm58etRQuyZSMHyz
UQC4wkDvCeVawNRCZjq6wWdvx5hmr2JeDSkkRtSZ/Fa1WXf26b3BZugI75p5JXafbWdOTRpNc8M5
YMk7tx29ZG3u0qODgDGCAzMwggMvAgEBMIGAMHkxEDAOBgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsT
FWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0
eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3JnAgMG6nUwCQYFKw4DAhoFAKCCAYcw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTEwMTI1MTMwODU0WjAj
BgkqhkiG9w0BCQQxFgQUBdxsqGgSYMm/wK7VaPDmz2uWHRswgZEGCSsGAQQBgjcQBDGBgzCBgDB5
MRAwDgYDVQQKEwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNV
BAMTGUNBIENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2Fj
ZXJ0Lm9yZwIDBup1MIGTBgsqhkiG9w0BCRACCzGBg6CBgDB5MRAwDgYDVQQKEwdSb290IENBMR4w
HAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB
dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZwIDBup1MA0GCSqGSIb3
DQEBAQUABIIBAEmqsFU1lYP/5pdxfvMTl4ElU7XAEhegw/rQjmTae5sodDTalIFzIk6eyWSdQY6+
JHrAOdN6qtoaMMpGTKrG+V4oQCh1bNvXcKfDgBOqdyDWB4yz2fzBkuH+au1ux1lk+jo8otG9ZAKg
LGUJeAfOyMbRUMW8eozDqQyYceGT/2pj5CG46GnGEcprdy2NvG2w6flnuSaxQF7DSt99KzwvNX1F
qxulqutS40JKVTq6NAEMOqDzEo+4in0qBDEuxFTheJkUN8aGdRHyl7VPGwAsrb07rwctNJBhYMwz
r2P/59nCaVuMn0/TVSgPngCnngGFt5SZdeFTeJOl4P4lmwCBRikAAAAAAAA=

--Apple-Mail-47--173845496--

From danny.cohen@oracle.com  Mon Jan 24 18:05:18 2011
Return-Path: <danny.cohen@oracle.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 1E7843A6847 for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 18:05:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.965
X-Spam-Level: 
X-Spam-Status: No, score=-5.965 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_FINCLOP=0.633]
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 nSHTFPrBLrsj for <ietf@core3.amsl.com>; Mon, 24 Jan 2011 18:05:17 -0800 (PST)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id D05A23A6840 for <ietf@ietf.org>; Mon, 24 Jan 2011 18:05:16 -0800 (PST)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id p0P28Acw030036 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 25 Jan 2011 02:08:11 GMT
Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id p0P289lg032136; Tue, 25 Jan 2011 02:08:09 GMT
Received: from abhmt005.oracle.com by acsmt354.oracle.com with ESMTP id 988498071295921226; Mon, 24 Jan 2011 18:07:06 -0800
Received: from [129.146.72.34] (/129.146.72.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 24 Jan 2011 18:07:06 -0800
Message-ID: <4D3E2F90.1010902@oracle.com>
Date: Mon, 24 Jan 2011 18:04:00 -0800
From: Danny Cohen <danny.cohen@oracle.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090910)
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Just Thinking (About the Nightmare Transition Ahead)
References: <201101241115.p0OBFPmU016916@fs4113.wdf.sap.corp> <20110124120248.E2E3291F6FA@drugs.dv.isc.org> <AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com> <20110124133524.DECCF91FD2E@drugs.dv.isc.org>
In-Reply-To: <20110124133524.DECCF91FD2E@drugs.dv.isc.org>
Content-Type: multipart/alternative; boundary="------------090404050707050503010506"
X-Mailman-Approved-At: Tue, 25 Jan 2011 08:13:26 -0800
Cc: mail-dated-1298302483.e6e7db@sabahattin-gucukoglu.com, Phillip Hallam-Baker <hallam@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: danny.cohen@oracle.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, 25 Jan 2011 02:05:18 -0000

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

On 01/24/11 05:35, Mark Andrews wrote:
> In message <AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com>, Phil
> lip Hallam-Baker writes:
>   
>> Sure people can do this, but what is the point?
>>
>> Let us imagine that as a matter of national policy we are all to live in
>> smaller houses to save energy. In what respect would such a policy be
>> realized if everyone bought a second, smaller house and started occupying
>> both simultaneously?
>>
>> The critical objective here is to create a situation where people can use
>> the Internet successfully without requiring a full IPv4 address.
>>
>> It is not going to be the case that anyone can use pure IPv6 100% of the
>> time for several decades.
>>     
>
> Who is talking pure IPv6 yet?  I'm talking multi-homed.  Multiple
> A's, A's and AAAA's or multiple AAAA's.  I don't care which.  The
> path to one of those addresses is broken and the network is not
> reporting it.  The question is how to make the application behave
> well in such a enviorment and also not be a bad network citizen
> when all the addresses are reachable.
>
>   
>> Getting people to use IPv6 is not an end in itself. If you have a full IPv4
>> address there is no point in using IPv6 in parallel.
>>     
>
> I will agree that when everything is working as expected it doesn't
> matter if you use IPv4 or IPv6.  However we are not discussing this
> senario.  We are discussing the senario where one of the paths is
> broken and not returning error messages and you don't know it is
> broken without trying it.
>
>   
>> The case where this dual stack is going to make sense is where the user has
>> a shared IPv4 and clean IPv6 and there is a performance advantage to going
>> through the clean connection.
>>     
>
> That's one case but not the only one.
>
>   
>> This is not something that I would want to have to code for as an
>> application programmer. I would want to have a call of the form 'get best
>> connection for (protocol, domain_name) and have the platform figure it out
>> using information that I would not want the application programmer to have
>> access to.
>>     
>
> Does it really matter if it in the application or a library.  The
> problem is still the same.
>
> Mark
>
>   


--------------090404050707050503010506
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=us-ascii" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 01/24/11 05:35, Mark Andrews wrote:
<blockquote cite="mid:20110124133524.DECCF91FD2E@drugs.dv.isc.org"
 type="cite">
  <pre wrap="">In message <a class="moz-txt-link-rfc2396E" href="mailto:AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com">&lt;AANLkTim22fkSqt__6eFh0k3LDuUtV6orSBoeMFrUADPP@mail.gmail.com&gt;</a>, Phil
lip Hallam-Baker writes:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Sure people can do this, but what is the point?

Let us imagine that as a matter of national policy we are all to live in
smaller houses to save energy. In what respect would such a policy be
realized if everyone bought a second, smaller house and started occupying
both simultaneously?

The critical objective here is to create a situation where people can use
the Internet successfully without requiring a full IPv4 address.

It is not going to be the case that anyone can use pure IPv6 100% of the
time for several decades.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Who is talking pure IPv6 yet?  I'm talking multi-homed.  Multiple
A's, A's and AAAA's or multiple AAAA's.  I don't care which.  The
path to one of those addresses is broken and the network is not
reporting it.  The question is how to make the application behave
well in such a enviorment and also not be a bad network citizen
when all the addresses are reachable.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Getting people to use IPv6 is not an end in itself. If you have a full IPv4
address there is no point in using IPv6 in parallel.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I will agree that when everything is working as expected it doesn't
matter if you use IPv4 or IPv6.  However we are not discussing this
senario.  We are discussing the senario where one of the paths is
broken and not returning error messages and you don't know it is
broken without trying it.

  </pre>
  <blockquote type="cite">
    <pre wrap="">The case where this dual stack is going to make sense is where the user has
a shared IPv4 and clean IPv6 and there is a performance advantage to going
through the clean connection.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
That's one case but not the only one.

  </pre>
  <blockquote type="cite">
    <pre wrap="">This is not something that I would want to have to code for as an
application programmer. I would want to have a call of the form 'get best
connection for (protocol, domain_name) and have the platform figure it out
using information that I would not want the application programmer to have
access to.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Does it really matter if it in the application or a library.  The
problem is still the same.

Mark

  </pre>
</blockquote>
<br>
</body>
</html>

--------------090404050707050503010506--

From bertietf@bwijnen.net  Tue Jan 25 08:35:15 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 1FAF43A67F0; Tue, 25 Jan 2011 08:35:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 55iyCr24VqDW; Tue, 25 Jan 2011 08:35:13 -0800 (PST)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:610:240:11::c100:1342]) by core3.amsl.com (Postfix) with ESMTP id 013793A6800; Tue, 25 Jan 2011 08:35:12 -0800 (PST)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1Phlu9-0000AA-Kl; Tue, 25 Jan 2011 17:38:07 +0100
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1Phlu9-0003oo-F3; Tue, 25 Jan 2011 17:38:05 +0100
Message-ID: <4D3EFC6D.9030706@bwijnen.net>
Date: Tue, 25 Jan 2011 16:38:05 +0000
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: Jason_Livingood@cable.comcast.com, d.malas@cablelabs.com
Subject: opsdir review of draft-ietf-speermint-architecture-17.txt
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: 86ab03e524994f79ca2c75a176445dd4cd597e86f8fe435c2dbb7a44c5f52541
Cc: ops-dir@ietf.org, "ietf@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, 25 Jan 2011 16:35:15 -0000

I was appointed to review this document from an OPS-DIR point of
vie, i,e, to check for operational or management aspects.

This are is not my space of expertise, so don't rely too much on my
report.

I think that there might be some operational aspects in the sense that
sometimes secure/encrypted connections are needed and other times it may be
OK to use unencrypted connections if they are inside the same secure building.
So is there not something for an operator to configure in such cases?

typo:

Section 4, 4th bullet, 2nd sub bullet:

       *  LUF can communicator with SF and SBE

     s/cator/cate/

Section 5.1.1.2 2nd para:

    If an im: or pres: URI is chosen based on an "E2U+im" [RFC3861] or
    "E2U+pres" [RFC3953] enumserver, the SSP follows the procedures for
    resolving these URIs to URIs for specific protocols such a SIP or
    XMPP as described in the previous section.

    s/such a SIP/such as SIP/

Bert Wijnen



From evnikita2@gmail.com  Wed Jan 26 02:18:58 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 EA1BD3A697F; Wed, 26 Jan 2011 02:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.915, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, 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 eDoevuOJaeHj; Wed, 26 Jan 2011 02:18:57 -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 105003A6825; Wed, 26 Jan 2011 02:18:55 -0800 (PST)
Received: by fxm9 with SMTP id 9so824840fxm.31 for <multiple recipients>; Wed, 26 Jan 2011 02:21:52 -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:content-type; bh=zfUhmGCehru/y2x4Dc0y/iusKRYc8Lktub/cObhei3s=; b=CvN30GRK5TfOLGLLVfTaqvyXLioJXlvSfvlC51XrR0kQvHrV2CLABFpjmhAhyO9rDs OH6uNjORpJgE5iOg0xnMQXlRuY6L5+6eEQ/OfyDb0VWZRkWAa5xNdfp2ey8b0R3js0wy eu4fKbQWLFYKMcoJswyIIZ0oCDWqlO1NaIUh4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type; b=ok9NsSg+4jfbZsuR2tE0XMZuHnjEzMq43vC8uqsi7hstwpTJxAxafXW552FfP5riig llCHso9GEuV1g7RnKM4cdoSH+EylbmQ5cI/yrwnBedjyzXGhNzewDFZ0OpA+fY07vOlu bv4lOY9TDM53TQIC3VlJZdPrEZIAJQN2oe5BY=
Received: by 10.223.86.196 with SMTP id t4mr1423300fal.34.1296037312662; Wed, 26 Jan 2011 02:21:52 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id e6sm5425067fav.8.2011.01.26.02.21.49 (version=SSLv3 cipher=RC4-MD5); Wed, 26 Jan 2011 02:21:51 -0800 (PST)
Message-ID: <4D3FF5D4.2060900@gmail.com>
Date: Wed, 26 Jan 2011 12:22:12 +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>, iesg <iesg@ietf.org>,  "uri-review@ietf.org" <uri-review@ietf.org>
Subject: Last Call summary on draft-yevstifeyev-tn3270-uri
Content-Type: multipart/alternative; boundary="------------020407090604000606070509"
Cc: URI <uri@w3.org>, "apps-discuss@ietf.org" <apps-discuss@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, 26 Jan 2011 10:18:59 -0000

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

Hello all,

This message summarizes the Last Call on draft-yevstifeyev-tn3270-uri 
(http://tools.ietf.org/id/draft-yevstifeyev-tn3270-uri-13.txt).

Firstly, some statistical information.  The Last Call was requested by 
Peter Saint-Andre on 4 January, 2011 and was announced on 4 January, 
2011.  The Last Call ends on 1 February, 2011.  The LC announcement has 
been sent out to IETF Discussion, uri-review and URI@w3c.org mailing 
lists.  A number of comments have been received during the Last Call.  
The most current version - 13 - I have just uploaded is believed to 
resolve them.  Moreover, a number of improvements have been made to 
improve the document quality.

Secondly, here is the exhaustive list of differences between the 12 
version and 13 version.

/Intended status/ - did not change: Informational;

/Title/ - changed.  Was *The 'tn3270' Uniform Resource Identifier 
Scheme* and now is *The 'tn3270' Uniform Resource Identifier (URI) 
Scheme*.  I'm asking Peter to change the write0up in accordance to this.

/Abstract/ - did not change;

/Introduction/ - changed.  Added the RFC 2119 boilerplate (now used 
throughout the document); added the reference to IANA registry; 
clarified the purpose of the document; some other minor changes.

/Scheme definition/ - changed.  Splitted the designated service into 
Telnet 3270 and Telnet 3270 Enchanted, added the reference to IBM 
Publication GA23-0059, related to 3270 data stream; added the reference 
to RFC 3049, related to TN3270E; clarified the URI syntax, as follows.  Was:
> The 'tn3270' URI takes the following form (given in ABNF, as
>     described inRFC 5234  <http://tools.ietf.org/html/rfc5234>  [RFC5234  <http://tools.ietf.org/html/rfc5234>]):
>
>     tn3270uri = "tn3270:" "//" authority ["/"]
>
>     The 'authority' rule is defined inRFC 3986  <http://tools.ietf.org/html/rfc3986>  [RFC3986  <http://tools.ietf.org/html/rfc3986>]. The final
>     character "/" can be omitted.
>

Now:

>    The 'tn3270' URI takes the following form (given in ABNF, as
>     described inRFC 5234  <http://tools.ietf.org/html/rfc5234>  [RFC5234  <http://tools.ietf.org/html/rfc5234>]):
>
>     tn3270uri = "tn3270:" hier-part
>     hier-part = "//" authority ["/"]
>                 ;the URI takes the form
>                 ;tn3270://<user>:<password>@<host>:<port>/
>                 ;that is formally defined via the 'authority'
>
>     The 'authority' rule is specified inRFC 3986  <http://tools.ietf.org/html/rfc3986>  [RFC3986  <http://tools.ietf.org/html/rfc3986>].  If 'port'
>     (in the 'authority' part) is omitted, it SHALL default to 21.  The
>     final character "/" MAY be omitted.

/Security Considerations/ - changed.  Clarified why there are no other 
security considerations for 'tn3270' scheme other than the 'telnet' one has.

/IANA Considerations/ - changed.  added the reference to RFC 4395; 
changed the description of protocol, that uses the scheme in accordance 
with Section 2; changed the Contact and author to IESG and IETF, 
respectively.

/References/ - RFC 4395 is now Informative; added the references to RFC 
3049, IANA registry and IBM Publication GA23-0059.

/Acknowledgments/ - corrected the typographical mistake in the last name 
of Alfred Hoenes.

/Author's addresses/ - changed, clarified the address.

Lastly, during the LC the document was reviewed by IANA, GenART and 
OPS-DIR Review Team.  I'm citing their reviews.

IANA:
> IANA understands that, upon approval of this document, there is a single
> Action that IANA needs to complete.
>
> In the URI schemes registry located at:
>
> http://www.iana.org/assignments/uri-schemes.html
>
> in the Provisional URI Schemes section, the follow registration will be
> added:
>
> URI Scheme: tn3270
> Description: TN3270 Telnet Service
> Reference: [RFC-to-be]
>
> IANA understands that this is the only action required upon approval of
> this document. 

GenART:

> 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-yevstifeyev-tn3270-uri-12
> Reviewer: Vijay K. Gurbani
> Review Date: Jan-14-2011
> IETF LC End Date: Feb-02-2011
> IESG Telechat date: Unknown
>
> Summary: This draft is ready as an Informational RFC.
>
> Major issues: 0
> Minor issues: 0
> Nits/editorial comments: 0
>
> Thanks,
>
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/

OPS-DIR:

> -----Original Message-----
> From:ops-dir-bounces@ietf.org  [mailto:ops-dir-bounces@ietf.org] On
> Behalf Of ext Ersue, Mehmet (NSN - DE/Munich)
> Sent: Wednesday, January 12, 2011 1:07 PM
> To:ops-dir@ietf.org
> Cc:draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org
> Subject: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12
>
> I reviewed draft-yevstifeyev-tn3270-uri-12 for its operational impacts..
>
> Summary:
> The document gives a specification of syntax, semantics and use of
> 'tn3270' URI scheme.
>
> Obviously this is an individual submission without any document write-up
> and supporting AD.
> I would like to read a document write-up with the regular template even
> if it is written by the author.
>
> The main purpose of the document, namely to update the IANA registration
> of tn3270 URI scheme using the given registration template, should be
> added to the Introduction section. In general I would suggest to include
> in the Introduction section the purpose of the action and more
> importantly why existing IANA registrations are not sufficient and why
> the publication of this RFC is needed.
>
> Obviously the GEN-Area reviewer (Tom Petch) has an opposite opinion and
> does not see this IANA registration in the interest of IETF (see
> https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=55119&tid=129
> 4831574). The reviewer furthermore states, following the rules in
> RFC4395 the document should provide concrete contact information for the
> editor instead of an anonymous email address only.
>
> I don't see any additional operation impact other than above.
>
> Other issues:
>
> - The used language needs some polishing.
>
> - Following are draft nits suggesting correction:
>
> == The copyright year in the IETF Trust and authors Copyright Line does
> not
>     match the current year
>
> ->  Use new template or: s/2010/2011/
>
> -- Obsolete informational reference (is this intentional?): RFC 1738
>     (Obsoleted by RFC 4248, RFC 4266)
>
> ->  Use correct reference or clarify.
>
>
> Mehmet
>
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir
>
The most current version is believed to resolve all the comments received.

No changes are intended to be made up to the end of the LC.  This 
message is to allow the IESG to preliminarily review the doc.

Looking forward for the decision of IESG,
Mykyta Yevstifeyev

--------------020407090604000606070509
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">
    Hello all,<br>
    <br>
    This message summarizes the Last Call on
    draft-yevstifeyev-tn3270-uri
    (<a class="moz-txt-link-freetext" href="http://tools.ietf.org/id/draft-yevstifeyev-tn3270-uri-13.txt">http://tools.ietf.org/id/draft-yevstifeyev-tn3270-uri-13.txt</a>).  <br>
    <br>
    Firstly, some statistical information.  The Last Call was requested
    by Peter Saint-Andre on 4 January, 2011 and was announced on 4
    January, 2011.  The Last Call ends on 1 February, 2011.  The LC
    announcement has been sent out to IETF Discussion, uri-review and
    <a class="moz-txt-link-abbreviated" href="mailto:URI@w3c.org">URI@w3c.org</a> mailing lists.  A number of comments have been received
    during the Last Call.  The most current version - 13 - I have just
    uploaded is believed to resolve them.  Moreover, a number of
    improvements have been made to improve the document quality.<br>
    <br>
    Secondly, here is the exhaustive list of differences between the 12
    version and 13 version.<br>
    <br>
    <i>Intended status</i> - did not change: Informational;<br>
    <br>
    <i>Title</i> - changed.  Was <b>The 'tn3270' Uniform Resource
      Identifier Scheme</b> and now is <b>The 'tn3270' Uniform Resource
      Identifier <span class="insert">(URI)</span> Scheme</b>.  I'm
    asking Peter to change the write0up in accordance to this.<br>
    <br>
    <i>Abstract</i> - did not change;<br>
    <br>
    <i>Introduction</i> - changed.  Added the RFC 2119 boilerplate (now
    used throughout the document); added the reference to IANA registry;
    clarified the purpose of the document; some other minor changes.<br>
    <br>
    <i>Scheme definition</i> - changed.  Splitted the designated service
    into Telnet 3270 and Telnet 3270 Enchanted, added the reference to
    IBM Publication GA23-0059, related to 3270 data stream; added the
    reference to RFC 3049, related to TN3270E; clarified the URI syntax,
    as follows.  Was:<br>
    <blockquote type="cite">
      <pre class="newpage">The 'tn3270' URI takes the following form (given in ABNF, as
   described in <a href="http://tools.ietf.org/html/rfc5234">RFC 5234</a> [<a href="http://tools.ietf.org/html/rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>]):

   tn3270uri = "tn3270:" "//" authority ["/"]

   The 'authority' rule is defined in <a href="http://tools.ietf.org/html/rfc3986">RFC 3986</a> [<a href="http://tools.ietf.org/html/rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>]. The final
   character "/" can be omitted.

</pre>
    </blockquote>
    <br>
    Now:<br>
    <br>
    <blockquote type="cite">
      <pre class="newpage">  The 'tn3270' URI takes the following form (given in ABNF, as
   described in <a href="http://tools.ietf.org/html/rfc5234">RFC 5234</a> [<a href="http://tools.ietf.org/html/rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>]):

   tn3270uri = "tn3270:" hier-part
   hier-part = "//" authority ["/"]
               ;the URI takes the form
               ;<a class="moz-txt-link-freetext" href="tn3270://">tn3270://</a>&lt;user&gt;:&lt;password&gt;@&lt;host&gt;:&lt;port&gt;/
               ;that is formally defined via the 'authority'

   The 'authority' rule is specified in <a href="http://tools.ietf.org/html/rfc3986">RFC 3986</a> [<a href="http://tools.ietf.org/html/rfc3986" title="&quot;Uniform Resource Identifier (URI): Generic Syntax&quot;">RFC3986</a>].  If 'port'
   (in the 'authority' part) is omitted, it SHALL default to 21.  The
   final character "/" MAY be omitted.
</pre>
    </blockquote>
    <br>
    <i>Security Considerations</i> - changed.  Clarified why there are
    no other security considerations for 'tn3270' scheme other than the
    'telnet' one has.<br>
    <br>
    <i>IANA Considerations</i> - changed.  added the reference to RFC
    4395; changed the description of protocol, that uses the scheme in
    accordance with Section 2; changed the Contact and author to IESG
    and IETF, respectively.<br>
    <br>
    <i>References</i> - RFC 4395 is now Informative; added the
    references to RFC 3049, IANA registry and IBM Publication GA23-0059.<br>
    <br>
    <i>Acknowledgments</i> - corrected the typographical mistake in the
    last name of Alfred Hoenes.<br>
    <br>
    <i>Author's addresses</i> - changed, clarified the address.<br>
    <br>
    Lastly, during the LC the document was reviewed by IANA, GenART and
    OPS-DIR Review Team.  I'm citing their reviews.<br>
    <br>
    IANA:<br>
    <blockquote type="cite">IANA understands that, upon approval of this
      document, there is a single<br>
      Action that IANA needs to complete.<br>
      <br>
      In the URI schemes registry located at:<br>
      <br>
      <a href="http://www.iana.org/assignments/uri-schemes.html"
        rel="nofollow">http://www.iana.org/assignments/uri-schemes.html</a><br>
      <br>
      in the Provisional URI Schemes section, the follow registration
      will be<br>
      added:<br>
      <br>
      URI Scheme: tn3270<br>
      Description: TN3270 Telnet Service<br>
      Reference: [RFC-to-be]<br>
      <br>
      IANA understands that this is the only action required upon
      approval of<br>
      this document.
    </blockquote>
    <br>
    GenART:<br>
    <br>
    <blockquote type="cite">I am the assigned Gen-ART reviewer for this
      draft. For background on
      <br>
      Gen-ART, please see the FAQ at
      <br>
      <a class="moz-txt-link-rfc2396E"
        href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.
      <br>
      <br>
      Please resolve these comments along with any other Last Call
      comments
      <br>
      you may receive.
      <br>
      <br>
      Document: draft-yevstifeyev-tn3270-uri-12
      <br>
      Reviewer: Vijay K. Gurbani
      <br>
      Review Date: Jan-14-2011
      <br>
      IETF LC End Date: Feb-02-2011
      <br>
      IESG Telechat date: Unknown
      <br>
      <br>
      Summary: This draft is ready as an Informational RFC.
      <br>
      <br>
      Major issues: 0
      <br>
      Minor issues: 0
      <br>
      Nits/editorial comments: 0
      <br>
      <br>
      Thanks,
      <br>
      <br>
      - vijay
      <br>
      <span class="moz-txt-tag">-- <br>
      </span>Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
      <br>
      1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
      <br>
      Email: vkg@{bell-labs.com,acm.org} / <a
        class="moz-txt-link-abbreviated"
        href="mailto:vijay.gurbani@alcatel-lucent.com">vijay.gurbani@alcatel-lucent.com</a>
      <br>
      Web:   <a class="moz-txt-link-freetext"
        href="http://ect.bell-labs.com/who/vkg/">http://ect.bell-labs.com/who/vkg/</a>
      <br>
    </blockquote>
    <br>
    OPS-DIR:<br>
    <br>
    <blockquote type="cite">
      <div class="moz-text-plain" wrap="true" style="font-family:
        -moz-fixed; font-size: 13px;" lang="x-western">
        <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:ops-dir-bounces@ietf.org">ops-dir-bounces@ietf.org</a> [<a class="moz-txt-link-freetext" href="mailto:ops-dir-bounces@ietf.org">mailto:ops-dir-bounces@ietf.org</a>] On
Behalf Of ext Ersue, Mehmet (NSN - DE/Munich)
Sent: Wednesday, January 12, 2011 1:07 PM
To: <a class="moz-txt-link-abbreviated" href="mailto:ops-dir@ietf.org">ops-dir@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org">draft-yevstifeyev-tn3270-uri-authors@tools.ietf.org</a>
Subject: [OPS-DIR] OPS-DIR Review of draft-yevstifeyev-tn3270-uri-12

I reviewed draft-yevstifeyev-tn3270-uri-12 for its operational impacts..

Summary:
The document gives a specification of syntax, semantics and use of
'tn3270' URI scheme.

Obviously this is an individual submission without any document write-up
and supporting AD.
I would like to read a document write-up with the regular template even
if it is written by the author.

The main purpose of the document, namely to update the IANA registration
of tn3270 URI scheme using the given registration template, should be
added to the Introduction section. In general I would suggest to include
in the Introduction section the purpose of the action and more
importantly why existing IANA registrations are not sufficient and why
the publication of this RFC is needed.

Obviously the GEN-Area reviewer (Tom Petch) has an opposite opinion and
does not see this IANA registration in the interest of IETF (see
<a class="moz-txt-link-freetext" href="https://www.ietf.org/ibin/c5i?mid=6&amp;rid=49&amp;gid=0&amp;k1=933&amp;k2=55119&amp;tid=129">https://www.ietf.org/ibin/c5i?mid=6&amp;rid=49&amp;gid=0&amp;k1=933&amp;k2=55119&amp;tid=129</a>
4831574). The reviewer furthermore states, following the rules in
RFC4395 the document should provide concrete contact information for the
editor instead of an anonymous email address only.

I don't see any additional operation impact other than above.

Other issues:

- The used language needs some polishing.

- Following are draft nits suggesting correction:

== The copyright year in the IETF Trust and authors Copyright Line does
not
   match the current year

-&gt; Use new template or: s/2010/2011/

-- Obsolete informational reference (is this intentional?): RFC 1738
   (Obsoleted by RFC 4248, RFC 4266)

-&gt; Use correct reference or clarify.


Mehmet

_______________________________________________
OPS-DIR mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OPS-DIR@ietf.org">OPS-DIR@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ops-dir">https://www.ietf.org/mailman/listinfo/ops-dir</a>

</pre>
      </div>
    </blockquote>
    The most current version is believed to resolve all the comments
    received.<br>
    <br>
    No changes are intended to be made up to the end of the LC.  This
    message is to allow the IESG to preliminarily review the doc.<br>
    <br>
    Looking forward for the decision of IESG,<br>
    Mykyta Yevstifeyev<br>
  </body>
</html>

--------------020407090604000606070509--

From randy@psg.com  Tue Jan 25 13:47:46 2011
Return-Path: <randy@psg.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 D34353A68C0; Tue, 25 Jan 2011 13:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tb+oBhACSlPP; Tue, 25 Jan 2011 13:47:46 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id F0A0D3A68BC; Tue, 25 Jan 2011 13:47:45 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Phqme-000Huc-5o; Tue, 25 Jan 2011 21:50:40 +0000
Date: Wed, 26 Jan 2011 06:50:39 +0900
Message-ID: <m2vd1cr6ts.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina Tsou <tena@huawei.com>
Subject: Re: Review of draft-ymbk-aplusp-08
In-Reply-To: <01a201cbbcd7$197946c0$4c6bd440$@com>
References: <01a201cbbcd7$197946c0$4c6bd440$@com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Wed, 26 Jan 2011 08:45:15 -0800
Cc: ops-dir@ietf.org, ietf@ietf.org, iesg@ietf.org, draft-ymbk-aplusp@tools.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: Tue, 25 Jan 2011 21:47:47 -0000

> Operations directorate and Security directorate reviews are solicited
> primarily to help the area directors improve their efficiency, particularly
> when preparing for IESG telechats, and allowing them to focus on documents
> requiring their attention and spend less time on the trouble-free ones.

and which are you?  can't be ops, as you are a vendor.  so security?
but we already received the security review.

but thanks for the review anyway.

randy, a bit confused

From tena@huawei.com  Tue Jan 25 13:27:33 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 E9A543A68B1; Tue, 25 Jan 2011 13:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.237
X-Spam-Level: 
X-Spam-Status: No, score=-106.237 tagged_above=-999 required=5 tests=[AWL=0.362, 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 6s2su1Enpefb; Tue, 25 Jan 2011 13:27:32 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 8D3B43A68C6; Tue, 25 Jan 2011 13:27:32 -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 <0LFL00KLGL2UFA@usaga02-in.huawei.com>; Tue, 25 Jan 2011 13:30:31 -0800 (PST)
Received: from TingZousc1 ([10.212.245.166]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFL00CLMKYGRG@usaga02-in.huawei.com>; Tue, 25 Jan 2011 13:30:30 -0800 (PST)
Date: Tue, 25 Jan 2011 13:27:56 -0800
From: Tina Tsou <tena@huawei.com>
Subject: Review of draft-ymbk-aplusp-08
To: ops-dir@ietf.org, secdir@ietf.org
Message-id: <01a201cbbcd7$197946c0$4c6bd440$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=ISO-8859-1
Content-language: en-us
Content-transfer-encoding: quoted-printable
Thread-index: Acu81rPbyWvC8QjGT6iixeTbXkVESw==
x-cr-hashedpuzzle: Kb73 N1+x QaCS SRUO X9iC a/5H iiZT ohFD ooWx pZsn pgCe tH+x uHtg xbaB yRyF 8PCf; 5; ZAByAGEAZgB0AC0AeQBtAGIAawAtAGEAcABsAHUAcwBwAEAAdABvAG8AbABzAC4AaQBlAHQAZgAuAG8AcgBnADsAaQBlAHMAZwBAAGkAZQB0AGYALgBvAHIAZwA7AGkAZQB0AGYAQABpAGUAdABmAC4AbwByAGcAOwBvAHAAcwAtAGQAaQByAEAAaQBlAHQAZgAuAG8AcgBnADsAcwBlAGMAZABpAHIAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {94249E4E-AC6C-4722-8559-B0DA304CD2B0}; dABlAG4AYQBAAGgAdQBhAHcAZQBpAC4AYwBvAG0A; Tue, 25 Jan 2011 21:27:43 GMT; UgBlAHYAaQBlAHcAIABvAGYAIABkAHIAYQBmAHQALQB5AG0AYgBrAC0AYQBwAGwAdQBzAHAALQAwADgA
x-cr-puzzleid: {94249E4E-AC6C-4722-8559-B0DA304CD2B0}
X-Mailman-Approved-At: Wed, 26 Jan 2011 08:45:16 -0800
Cc: iesg@ietf.org, draft-ymbk-aplusp@tools.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, 25 Jan 2011 21:27:34 -0000

I reviewed the document draft-ymbk-aplusp-08 in general.
=20
Operations directorate and Security directorate reviews are solicited
primarily to help the area directors improve their efficiency, =
particularly
when preparing for IESG telechats, and allowing them to focus on =
documents
requiring their attention and spend less time on the trouble-free ones.

Improving the documents is important, 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/SecDir members do not in and of themselves cause the
IESG to raise issue with a document. The reviews may, however, convince
individual IESG members to raise concern over a particular document
requiring further discussion. The reviews, particularly those conducted =
in
last call and earlier, may also help the document editors improve their
documents.
=20
-----
This document is well written, though there may be some nits.

Comment #1:
In Abstract section this draft proposes an IPv4 address sharing scheme,
treating some of the port number bits as part of an extended IPv4 =
address.
A SOHO CPE (A+P) may provide with website service. When a host in =
external
network accesses this website, what information that DNS servers =
feedback to
host? If it is an IP address, it can't uniquely identify the CPE. If it =
is
IP + port range, how can host recognize this and process? If it is IP + =
some
a Port, how can DNS server know when port changed?=20
Some Operators identify services by five elements include UDP/TCP =
well-known
ports when CPE is an unreliable device. If well-known ports changed, =
service
can't be recognized.

Comment #2:
Abstract section,
"In the face of IPv4 address exhaustion, the need for addresses is =
stronger
than the need to be able to address thousands of applications on a =
single
host."
- This viewpoint is not always true. During the transition from IPv4 to
IPv6, some set of operators do not want the services are affected, which =
may
result some customers lost. A smoothly transition technology is more
favorable.

Comment #3:
Section 1.1 says: Another issue with CGN is the trade-off between =
session
state and network placement.
- If there are too many session state to keep, two CGN or more can be
placed. A distributed CGN may be a good choice. And single point of =
failure
can be resolved

Comment #4:
In section 3.3.1, it says: different port-ranges can have different
lifetimes, and the CPE is not entitled to use them after they expire =
what is
the appropriate lifetime for a port-rang?  When for P2P application, =
many
ports are used. In a short-term period, when for some fixed service =
(e.g.
site), a port may be used for many years. Will the server allocate port
according application? Or else there is some security problem or port
efficient allocation. For the more, port allocation will make more =
burdens
for server because of large number s of ports and high frequency
requisition.

Comment #5:
SMAP (stateless A+P Mapping) is proposed in section 4.1, IPv4 address =
and
port is embedded in the IPv6 address =96 which would be used to create a
tunnel.=20
- In section 5.2, =93Dynamic Allocation of Port Ranges=94 is proposed. =
What if
the allocated ports do not belong to a single IP address? The SMAP =
mechanism
may not work in this case.=20
- The IPv6 address would follow the format defined in
[I-D.ietf-behave-address-format], but port is not included in the =
address
formats defined by that draft. Any plan to define the address format?

Here is the format defined in [I-D.ietf-behave-address-format]:


    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |PL| 0-------------32--40--48--56--64--72--80--88--96--104---------|
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |32|     prefix    |v4(32)         | u | suffix                    |
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |40|     prefix        |v4(24)     | u |(8)| suffix                |
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |48|     prefix            |v4(16) | u | (16)  | suffix            |
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |56|     prefix                |(8)| u |  v4(24)   | suffix        |
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |64|     prefix                    | u |   v4(32)      | suffix    |
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
    |96|     prefix                                    |    v4(32)     |
    +--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
					=09
						Figure 1


Comment #6:
In section 5.1.2 A+P for Mobile Providers=20
- If=A0A+P is implemented in a terminal device, e.g. mobile phone and =
PC,
there might be some problems, e.g. ARP problem =96 terminal would not be =
able
to send packets to other terminals sharing the same IP address with =
itself.=20
- Any thoughts about the solution? A new NAT layer between the IP and
TCU/UDP layer in the stack?


Comment #7:
Section 5.2, it says: mechanism can allocate a port range from another =
IP
within the same subnet.
- For example, an internal host1 communicate with an external host2. At
first CPE allocates IP1 and a port for some a session. During the
communication, more sessions are built and there are no more ports in =
IP1.
If IP2 is used for session, the packet may be discarded by host2.
There may be some errors. Where does 198.51.100.3 come? I can't find it =
in
Figure 15.



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




From ned+ietf@mauve.mrochek.com  Wed Jan 26 14:10:20 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 1369F3A68D6 for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 14:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_LETTER=-2]
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 ireMdzY3iETC for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 14:10:18 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id CADBB3A68BB for <ietf@ietf.org>; Wed, 26 Jan 2011 14:10:18 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NX2YWC988G00IFXJ@mauve.mrochek.com> for ietf@ietf.org; Wed, 26 Jan 2011 14:13:19 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NWP1MZKQSW007FL5@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 26 Jan 2011 14:13:16 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NX2YWAT196007FL5@mauve.mrochek.com>
Date: Wed, 26 Jan 2011 14:11:25 -0800 (PST)
Subject: Re: draft-housley-two-maturity-levels
In-reply-to: "Your message dated Mon, 24 Jan 2011 23:13:49 -0500" <4D3E4DFD.4060906@att.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <4B803580-664C-42B3-92A7-712452F12BA3@gmail.com> <01NTJJR8423E000CVY@mauve.mrochek.com> <20101027171037.GB3162@nsn.com> <63DD35D1-1C25-401D-8C05-992A2D11E3DE@vigilsec.com> <4D3E4DFD.4060906@att.com>
To: Tony Hansen <tony@att.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1296076923; i=@mrochek.com; bh=mvpMjp4z1QZcj0HD4lFANv8aDbA7tqg65/2Vr+/01rs=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=liS2fKNdZjJGDdddBX4d39kjj4IJ94vQFyinZX5nuD3rE+QugeT3AnyW/VIANDlee zUJ6b4p3x3weX2AsKFtTe/GjgODJR26FNRSak+jfI5tmJhNlgIAVC6OJHN9gnZMFsR n8JS6x+f0YLl1vC5OgExj/jAOXfYrNKfvf82OrOM=
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, 26 Jan 2011 22:10:20 -0000

+1 to the proposed rules for reclassifying DS to IS. I think they offer a
reasonable balance between expediency and quality.

				Ned

> On 1/24/2011 12:37 PM, Russ Housley wrote:
> > draft-housley-two-maturity-levels-03 was just posted. ...

> Overall I find this spec to be an improvement over the previous version.
> Here are a few areas where improvements can be made.

> ====

> This phrase in Section 1:

>      In addition,
>      IETF working groups and IESG members providing much more scrutiny
>      than is called for by RFC 2026 [1] prior to publication as Proposed
>      Standard.

> is not a sentence. Should it be "provide"? Should it be "have been
> providing"? Something else?

> ====

> The sentence in Section 1

>      One desired outcome is to provide an environment where the
>      IETF community is able to publish Proposed Standards as soon
>      as rough consensus is achieved.

> and these sentences in Section 2.1:

>      The intention of the two-tier maturity
>      ladder is to restore the requirements for Proposed Standard from RFC
>      2026. No new requirements are introduced; no existing published
>      requirements are relaxed.

> together lay out what is required for PS. Disregarding the other
> arguments over the word "restore", these sentences are otherwise fine
> and dandy.

> But I think there needs to be further guidance provided to the IESG and
> Working Groups on how they should change their behavior. What is wrong
> with how the WGs and IESG are currently interpreting the rules of 2026
> for PS? What current behaviors differ or have gone beyond what 2026
> requires, and hence need to be changed to restore those requirements?
> Without such guidance, nothing changes.

> ====

> One major section that has been removed from the previous version of
> this I-D is what to do with documents currently in the Draft Standard
> status. I know that there was significant disagreement with the
> "automatic reclassification to Internet Standard" proposed before, with
> good reason.

> I'm going to letter the the rules in section 2.2 as follows. I'm also
> going to indicate how these sort of map into the old classifications:

>      a) technical maturity (DS => FS)
>      b) belief in significant benefit to Internet community (DS => FS)
>      c) significant number of implementations with successful
> operational experience (DS => FS)
>      d) no unresolved errata (PS => DS)
>      e) no unused features that increases implementation complexity (PS
> => DS)

> Some people have argued that having a significant number of
> implementations (c) is sufficient to demonstrate both technical maturity
> (a) and the belief in benefit (b). The (d) and (e) requirements have
> already been demonstrated by virtue of those RFCs already being at DS
> status, although additional errata may have been filed against the DS.

> So I'm going to suggest that the following be applied to documents that
> are currently in Draft Standard status:

>      Any protocol or service that is currently in Draft Standard status,
> without
>      significant unresolved errata, may be reclassified as an Internet
> Standard
>      as soon as it can be demonstrated to have a significant number of
>      implementations with successful operational experience.

>      This reclassification may be accomplished by filing a request with
> the IESG,
>      detailing the Implementation and Operational Experience. After
> review, the
>      IESG will hold an IETF-wide Last Call on the reclassification. If
> there is consensus
>      for the reclassification, the RFC will be reclassified without
> being reissued.

>      Protocols and services that have significant unresolved errata will
> need to be
>      re-issued to resolve the errata before the above criteria can be
> applied.

> Of course, there is still an open question what it means to have a
> "significant number", which will remain as subjective as it was before
> with the 2026 rules.

>      Tony Hansen
>      tony@att.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From fluffy@cisco.com  Wed Jan 26 16:09:44 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 EAE003A69FF; Wed, 26 Jan 2011 16:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.584
X-Spam-Level: 
X-Spam-Status: No, score=-110.584 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100, WEIRD_PORT=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 pr2NCZ+T8RRw; Wed, 26 Jan 2011 16:09:43 -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 4CD033A69F3; Wed, 26 Jan 2011 16:09:43 -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: AvsEAFtHQE2rRN+J/2dsb2JhbACke3OhAptJhU8EhReHEg
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-3.cisco.com with ESMTP; 27 Jan 2011 00:12:45 +0000
Received: from sjc-vpn5-670.cisco.com (sjc-vpn5-670.cisco.com [10.21.90.158]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p0R0Cj4r028934;  Thu, 27 Jan 2011 00:12:45 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: <20110118212603.5733.34489.idtracker@localhost>
Date: Wed, 26 Jan 2011 17:12:44 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1082)
Cc: 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: Thu, 27 Jan 2011 00:09:45 -0000

I'm really glad to see this draft in LC at long last and it is a great =
improvement to the current situation - thank you to all the people that =
put work into this. I have two significant problems with it that I think =
should be resolved before being published=20



Big Issues 1: I don't like mandating one port for secure and not secure =
versions of a protocol=20

I don't think this reflects IETF consensus given the number of protocols =
that deliberately choses to use two ports. I also don't think that it is =
a good idea in all cases. I believe the decision should be left to the =
people designing the protocol if they want one port or two. Let me give =
some examples

Imagine a client server protocol that runs over UDP and uses DTLS for =
security. The server will simultaneously serve requests over both DTLS =
and UDP. When the server receives a packet, it needs to be able to demux =
if it is a UDP packet or a DTLS packet. The obvious demux code point is =
the port. Yes, one might be able to reinvent a concept of a stream along =
with a 5 tuple and something like STARTTLS but this has many other =
problems. It means the client needs to use a different SRC port for each =
different "session" to the same server. This uses up NAT ports and =
complicates NAT traversal. It also adds additional latency to set up a =
small session. People just aren't going to do it. The other approach is =
demux based on the first byte inside the UDP packet. The CoAP protocol  =
being developed in the CORE WG has taken that approach. The CORE WG =
proposed to the TLS chairs that over half the remaining code space for =
the TLS code point in the first byte be assigned to CoAP. The TLS =
chairs, more or less told the CORE guys to get stuffed (politely of =
course). Two ports is the obvious answer.=20

Lets consider another example. As the draft mentions, firewalls help =
apply policy, and catch configuration errors. Take an organization (like =
my house) that has a policy of no email over unencrypted protocols. It's =
really easy to set up a firewall policy that allows the encrypted ports =
and blocks the non encrypted ports that are typically used for email and =
does not require the firewall to do DPI. No doubt my daughter could =
figure out to circumvent this and sent unencrypted email via an VPN =
tunneled over DNS or ICMP or something but thats not the point - the =
point is to catch accidental misconfiguration, like the type that happen =
during software upgrades. You can agree or disagree about using =
firewalls this way but the fact remains, lots of people do use firewalls =
this way.=20

I strongly urge this draft not to take on mandating one port - leave the =
decision with the designers of the protocol. If draft does mandate one =
port, you will end up with a port registered for protocol foo and a port =
for a proprietary protocol with no description called foo-secure.  As I =
mentioned before, I also do not believe there is IETF consensus for one =
port.=20



Big Issue #2: The draft has close to no review advice for the expert =
reviewer.=20

I have been involved with several port registrations and they all left =
me grumpy and irritated and very frustrated at the expert review =
process. I'm sure the expert reviewer involved felt the same way and I =
know others have had similar experiences. We need concrete actionable =
advice for when the review says yes or no.=20

This draft provides no guidance on what the expert review would approve =
or deny. If all they are doing is checking the requirements of this =
draft have been satisfied, then I am fine with that but the draft needs =
to say that something like any denial by an expert review should include =
which MUST in this draft was not complied with.=20

I would like the draft to say that when IANA sends a response from an =
expert review to the applicant, the name of the reviewer (and perhaps =
email address) should be included.=20

Lets take some specific points of never ending confusion about what is =
"good enough" to say yes.=20

The reference to the doc describing the protocol. Is this a one line =
description? Is it a overview of the high level way this works, deals =
with congestion, security etc? Is it a full protocol specification. I =
have no idea. I also have no idea on what grounds the expert reviews can =
say no based on this.=20

What protocols use Anycast. Does STUN? Does ping? what about DNS? Who =
knows - who cares. I  do not believe discussion of if a protocol uses =
anycast or not has much relevance to deciding to allocate a port.=20

Next lets talk about the whole topic of what is or is not appropriate =
for dynamic range. Let's take web browsing for example. You start with a =
URL like www.example.com but the protocol could have required a port =
like www.example.com:55123 in the URL and only used dynamic ports. Is =
http a protocol that should be forced into the dynamic range? Clearly =
the answer is no but if not http, then what protocol should? This draft =
offers no advice to the expert reviewer on what to do. Next lets =
consider a protocol like FTP data transport - first FTP does some =
signaling and it can pass the ports to be used for the data transport =
connection so you might think the dynamic range is fine for the =
transport part - but policy on firewalls has resulted in people wanting =
to have a well known port for that FTP uses for the data connection. =
Most FTP now supports PASV and things like that to meet this well known =
port requirement.  You need to do this to make NAT port forwarding work.=20=


I think this draft need specific actionable advice on what grounds the =
expert review can say No. Obviously violating any of the MUST in this =
draft is fine reason to say no - but beyond that it is just too vague.=20=


Next we come to the issue of if a new protocols is allowed or not. Cisco =
developed a new protocol - the retransmission and flow control part of =
it was stollen from another protocol that is an RFC. I viewed this as a =
good thing as it ensured that we did not reinvent something new that was =
broken. The IANA expert review felt that we should not make a new =
protocol and should instead extend the old one and would not approve the =
port. Eventually sanity prevailed and the port was allocated but it =
worth noting that when the port was approved, the product had already =
shipped and the port was fixed. Had IANA not allocated the port, Cisco =
would have just kept using the port anyways. I'll note most other =
vendors feel about the same way - if they need to build a product that =
needs a port, they will take a port, or more than one,  if one is not =
allocated. This does not make me happy but I think we need to be =
realistic about what our grounds are for saying no and the probable =
result of saying no.=20

Along these lines, I have no idea what review guidelines the expert =
would use to decide if something was OK to be in the System port range =
instead of User. What would be an appropriate argument for System =
instead of User?=20

Along these lines, I think the draft should contain an example =
registration for a protocol in the port range where the description of =
the protocol is not a reference to a document but is provided in this =
example - using an existing protocol such as HTTP might make it easier =
for everyone to read. Similarly be nice to have example for something in =
the System range.=20

Anyways, my meta point is the draft need to give enough advice to the =
expert review that they know what to do. Of course the expert applies =
human intelligence but the review and applicants have to be on the same =
page about what is expected here.=20



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.=20


On Jan 18, 2011, at 14:26 , The IESG wrote:

>=20
> The IESG has received a request from the Transport Area Working Group =
WG
> (tsvwg) to consider the following document:
> - 'Internet Assigned Numbers Authority (IANA) Procedures for the
>   Management of the Service Name and Transport Protocol Port Number
>   Registry'
>  <draft-ietf-tsvwg-iana-ports-09.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-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


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



From sob@harvard.edu  Wed Jan 26 19:26:23 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 9565A28C0F3 for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 19:26:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.18
X-Spam-Level: 
X-Spam-Status: No, score=-102.18 tagged_above=-999 required=5 tests=[AWL=0.419, 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 jHjV3d71OWKJ for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 19:26:22 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id A913E28C0F6 for <ietf@ietf.org>; Wed, 26 Jan 2011 19:26:22 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 2FE4480CCE8; Wed, 26 Jan 2011 22:29:24 -0500 (EST)
To: ietf@ietf.org
Subject: Re: draft-housley-two-maturity-levels
Message-Id: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
Date: Wed, 26 Jan 2011 22:29:24 -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: Thu, 27 Jan 2011 03:26:23 -0000

1/ I still do not think this (modified) proposal will have any real
   impact on the number of "Proposed Standard" documents that move
   to a (in this proposal, "the") higher level since I do not see
   how this makes any significant changes to the underlying reasons
   that documents have not progressed in the past - i.e., I see no
   reason to think that this proposal would change the world much
   (would not help, would not hurt)

2/ I think the proposal must specifically deal with the 2026 IPR licence
   requirement in section 4.1.2

      If patented or otherwise controlled technology
      is required for implementation, the separate implementations must
      also have resulted from separate exercise of the licensing process.

   The requirement can be dealt with by explicitly discarding 
   it or by including it. But not mentioning the requirement does
   not make the issue go away.  This requirement was, in theory, a
   way to keep the IETF/IESG out of the business of evaluating
   the fairness of licensing terms.  I can remember only
   one time it came up (in an appeal) so getting rid of it may
   be fine - but don't make it look like it was just forgotten.
 
3/ I think you also be quite specific as to how to decide that the
   conditions for advancement have been met - one of the big
   implementation issues with 2026 was knowing how to decide
   that a technology was ready to be advanced (did you need
   a spreadsheet listing all features and noting with ones
   had been multiply implemented (as was done at huge effort
   for HTTP 1.1) or is there someting simplier - clear rules 
   would help avoid this type of issue in the future

4/ as part of #3 - the rules should also specifically deal with
   the following pp from 2026

      The requirement for at least two independent and interoperable
      implementations applies to all of the options and features of the
      specification.  In cases in which one or more options or features
      have not been demonstrated in at least two interoperable
      implementations, the specification may advance to the Draft Standard
      level only if those options or features are removed.

   this requirement was included to try to remove cruft from protocols
   as they went forward - maybe this is no longer a desire but,
   like with the license issue, a specific mention of what has
   been decided would mean that people would not think that
   things were not just forgotton.

Scott




From john-ietf@jck.com  Wed Jan 26 23:26:01 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 CB11928C0E4 for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 23:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.027
X-Spam-Level: 
X-Spam-Status: No, score=-103.027 tagged_above=-999 required=5 tests=[AWL=-0.428, 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 RWCZXJroDY5b for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 23:25:59 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 957C23A6B11 for <ietf@ietf.org>; Wed, 26 Jan 2011 23:25:58 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiMHs-000Da4-Lt; Thu, 27 Jan 2011 02:29:00 -0500
Date: Thu, 27 Jan 2011 02:28:59 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Scott O. Bradner" <sob@harvard.edu>, ietf@ietf.org
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <C3BAE1E425FB4058C86138DD@PST.JCK.COM>
In-Reply-To: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
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, 27 Jan 2011 07:26:01 -0000

+1 on all points, especially the first one.

   john


--On Wednesday, January 26, 2011 22:29 -0500 "Scott O. Bradner"
<sob@harvard.edu> wrote:

> 
> 1/ I still do not think this (modified) proposal will have any
> real    impact on the number of "Proposed Standard" documents
> that move    to a (in this proposal, "the") higher level since
> I do not see    how this makes any significant changes to the
> underlying reasons    that documents have not progressed in
> the past - i.e., I see no    reason to think that this
> proposal would change the world much    (would not help, would
> not hurt)
> 
> 2/ I think the proposal must specifically deal with the 2026
> IPR licence    requirement in section 4.1.2
> 
>       If patented or otherwise controlled technology
>       is required for implementation, the separate
> implementations must       also have resulted from separate
> exercise of the licensing process.
> 
>    The requirement can be dealt with by explicitly discarding 
>    it or by including it. But not mentioning the requirement
> does    not make the issue go away.  This requirement was, in
> theory, a    way to keep the IETF/IESG out of the business of
> evaluating    the fairness of licensing terms.  I can remember
> only    one time it came up (in an appeal) so getting rid of
> it may    be fine - but don't make it look like it was just
> forgotten.  
> 3/ I think you also be quite specific as to how to decide that
> the    conditions for advancement have been met - one of the
> big    implementation issues with 2026 was knowing how to
> decide    that a technology was ready to be advanced (did you
> need    a spreadsheet listing all features and noting with ones
>    had been multiply implemented (as was done at huge effort
> for HTTP 1.1) or is there someting simplier - clear rules 
> would help avoid this type of issue in the future
> 
> 4/ as part of #3 - the rules should also specifically deal with
>    the following pp from 2026
> 
>       The requirement for at least two independent and
> interoperable       implementations applies to all of the
> options and features of the       specification.  In cases in
> which one or more options or features       have not been
> demonstrated in at least two interoperable
> implementations, the specification may advance to the Draft
> Standard       level only if those options or features are
> removed.
> 
>    this requirement was included to try to remove cruft from
> protocols    as they went forward - maybe this is no longer a
> desire but,    like with the license issue, a specific mention
> of what has    been decided would mean that people would not
> think that    things were not just forgotton.
> 
> Scott
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf





From gonzalo.camarillo@ericsson.com  Wed Jan 26 23:38:46 2011
Return-Path: <gonzalo.camarillo@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 E82D53A692F for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 23:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.632
X-Spam-Level: 
X-Spam-Status: No, score=-106.632 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IuQ80r4Nwk3f for <ietf@core3.amsl.com>; Wed, 26 Jan 2011 23:38:46 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id B8D163A6933 for <ietf@ietf.org>; Wed, 26 Jan 2011 23:38:45 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-cb-4d4121bb3422
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id DB.C8.23694.BB1214D4; Thu, 27 Jan 2011 08:41:47 +0100 (CET)
Received: from [131.160.126.208] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.2.234.1; Thu, 27 Jan 2011 08:41:46 +0100
Message-ID: <4D4121B9.2060407@ericsson.com>
Date: Thu, 27 Jan 2011 09:41:45 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
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: John C Klensin <john-ietf@jck.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <C3BAE1E425FB4058C86138DD@PST.JCK.COM>
In-Reply-To: <C3BAE1E425FB4058C86138DD@PST.JCK.COM>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Cc: "Scott O. Bradner" <sob@harvard.edu>, "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, 27 Jan 2011 07:38:47 -0000

Hi,

yes, I also agree the first one is the most important point and has not
been addressed so far. If we want a system that works (and is used), it
needs to include incentives to move from one level to the next one. I
have discussed this issue with quite a few people. Some people claim
that those incentives exist in some areas (e.g., public institutions
preferring or requiring full standards in their RFQs) but, at least in
the RAI area, the incentives are not there in the vast majority of cases.

Cheers,

Gonzalo


On 27/01/2011 9:28 AM, John C Klensin wrote:
> +1 on all points, especially the first one.
> 
>    john
> 
> 
> --On Wednesday, January 26, 2011 22:29 -0500 "Scott O. Bradner"
> <sob@harvard.edu> wrote:
> 
>>
>> 1/ I still do not think this (modified) proposal will have any
>> real    impact on the number of "Proposed Standard" documents
>> that move    to a (in this proposal, "the") higher level since
>> I do not see    how this makes any significant changes to the
>> underlying reasons    that documents have not progressed in
>> the past - i.e., I see no    reason to think that this
>> proposal would change the world much    (would not help, would
>> not hurt)
>>
>> 2/ I think the proposal must specifically deal with the 2026
>> IPR licence    requirement in section 4.1.2
>>
>>       If patented or otherwise controlled technology
>>       is required for implementation, the separate
>> implementations must       also have resulted from separate
>> exercise of the licensing process.
>>
>>    The requirement can be dealt with by explicitly discarding 
>>    it or by including it. But not mentioning the requirement
>> does    not make the issue go away.  This requirement was, in
>> theory, a    way to keep the IETF/IESG out of the business of
>> evaluating    the fairness of licensing terms.  I can remember
>> only    one time it came up (in an appeal) so getting rid of
>> it may    be fine - but don't make it look like it was just
>> forgotten.  
>> 3/ I think you also be quite specific as to how to decide that
>> the    conditions for advancement have been met - one of the
>> big    implementation issues with 2026 was knowing how to
>> decide    that a technology was ready to be advanced (did you
>> need    a spreadsheet listing all features and noting with ones
>>    had been multiply implemented (as was done at huge effort
>> for HTTP 1.1) or is there someting simplier - clear rules 
>> would help avoid this type of issue in the future
>>
>> 4/ as part of #3 - the rules should also specifically deal with
>>    the following pp from 2026
>>
>>       The requirement for at least two independent and
>> interoperable       implementations applies to all of the
>> options and features of the       specification.  In cases in
>> which one or more options or features       have not been
>> demonstrated in at least two interoperable
>> implementations, the specification may advance to the Draft
>> Standard       level only if those options or features are
>> removed.
>>
>>    this requirement was included to try to remove cruft from
>> protocols    as they went forward - maybe this is no longer a
>> desire but,    like with the license issue, a specific mention
>> of what has    been decided would mean that people would not
>> think that    things were not just forgotton.
>>
>> Scott
>>
>>
>>
>> _______________________________________________
>> 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 lars.eggert@nokia.com  Thu Jan 27 00:50:00 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 3BA7B3A6959; Thu, 27 Jan 2011 00:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.883
X-Spam-Level: 
X-Spam-Status: No, score=-103.883 tagged_above=-999 required=5 tests=[AWL=-0.284, 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 ZsID7qUB0wc4; Thu, 27 Jan 2011 00:49:59 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 442243A6939; Thu, 27 Jan 2011 00:49:59 -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 p0R8qx67016593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2011 10:53:00 +0200
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
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-15--16404008; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
Date: Thu, 27 Jan 2011 10:52:55 +0200
Message-Id: <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>
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, 27 Jan 2011 10:52:56 +0200 (EET)
X-Nokia-AV: Clean
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: Thu, 27 Jan 2011 08:50:00 -0000

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

Hi

On 2011-1-27, at 2:12, Cullen Jennings wrote:
> Big Issues 1: I don't like mandating one port for secure and not =
secure versions of a protocol
>=20
> I don't think this reflects IETF consensus given the number of =
protocols that deliberately choses to use two ports. I also don't think =
that it is a good idea in all cases. I believe the decision should be =
left to the people designing the protocol if they want one port or two. =
Let me give some examples

Paul Hoffman raised this issue as well (email from Nov 4 to this list.)

There was some discussion that lead to Paul suggesting specific edit to =
this document. (Which are not reflected in -09; us editors may have =
dropped the ball here). I'm attaching Paul's proposed changes below, =
could you check if you'd agree with them?

> Big Issue #2: The draft has close to no review advice for the expert =
reviewer.

Joe Touch (who leads the expert review team for ports) is working on a =
separate document (draft-touch-tsvwg-port-use). The first version of =
that draft was issued on the same day as the -09 version of iana-ports, =
which is why we don't refer to it.=20

Does draft-touch-tsvwg-port-use have the content you are looking for? If =
so, we should refer to it. (We should probably refer to it anyway, in a =
"you may also want to read this" kind-of way.)

> Small Issue #3: I object to anonymous review
>=20
> 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?

Lars

PS: Paul's proposed changes re item #1:

Begin forwarded message:
> From: Paul Hoffman <paul.hoffman@vpnc.org>
> Date: November 15, 2010 21:44:24 GMT+02:00
> To: <tsvwg@ietf.org>
> Subject: Proposed resolution for security issues with 	=
draft-ietf-tsvwg-iana-ports-08
>=20
> As this list and the TLS has seen, there is a wide variety of views on =
how to deal with fallback-to-insecure in protocols. I believe that the =
security community has no consensus on what this means, much less how to =
do it. My earlier proposal (continue to allow registration of two ports) =
was popular with some, unpopular with others; similarly, so was "force =
all protocols to use one port".
>=20
> Therefore, I retract my proposal to allow two-port registrations for =
fallback-to-insecure. However, I still recommend some changes to the =
text to reflect the view that STARTTLS is not the only way to have such =
a feature on one port.
>=20
> This will be an interesting IETF Last Call discussion.
>=20
> I propose the following changes to draft-ietf-tsvwg-iana-ports:
>=20
> Section 7.2 current:
> o  IANA will allocate only one assigned port number for all versions
>   of a service (e.g., running the service with or without a security
>   mechanism, or for updated variants of a service)
>=20
> Section 7.2 current:
[in the line above s/current/proposed/, I think]
> o  IANA will normally allocate only one assigned port number for all =
versions
>   of a service (e.g., running the service with or without a security
>   mechanism, or for updated variants of a service). This policy can
>   be overridden by the expert reviewer.
>=20
> Section 7.2 current:
>   Further,
>   previous separation of protocol variants based on security
>   capabilities (e.g., HTTP on TCP port 80 vs. HTTPS on TCP port 443) =
is
>   not recommended for new protocols, because all new protocols should
>   be security-capable and capable of negotiating the use of security
>   in-band.
>=20
> Section 7.2 proposed:
>   Further,
>   previous separation of protocol variants based on security
>   capabilities (e.g., HTTP on TCP port 80 vs. HTTPS on TCP port 443) =
is
>   not recommended for new protocols, because all new protocols should
>   be security-capable.
>=20
> --Paul Hoffman, Director
> --VPN Consortium

--Apple-Mail-15--16404008
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEyNzA4NTI1NlowIwYJKoZIhvcNAQkE
MRYEFM/N0pkgulvbzfI8SVXLC8wn1bZyMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AEc6AzQhlzIgVfkf5rZKPPP2NfI1YxivUkkh+OxY+3ppysvemDH6ozG3Qqi4+raG4Kmb5JEAW6y9
8Vv5zBI5CyPAsc56LqZose8sSQh6+goi9m6SxrT9r3zyn94TuTCeQCrlnmXopBa6MFaLThAvb96/
1sAF49RTqCMMLYcoEPn/P0P6DOHwiy1x9Se0hZg9htYHfy13Ks4kqv+9KGI7L5h0w0AMFKSrmSzL
LkVBY2fEt7vbG+wKgVD2Uz4dLufHw2tJz5tzo8hbwAGuvvO6RcucgmPoxI78WGhxbxEMVZvjiPoh
m3EfwzBDS1gg3IIzxhk/amFeS2S6pZDATXZt2OsAAAAAAAA=

--Apple-Mail-15--16404008--

From john-ietf@jck.com  Thu Jan 27 01:07:22 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 160113A6974 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 01:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.014
X-Spam-Level: 
X-Spam-Status: No, score=-103.014 tagged_above=-999 required=5 tests=[AWL=-0.415, 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 TRP3CXNhWMt6 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 01:07:21 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 1DAE13A6951 for <ietf@ietf.org>; Thu, 27 Jan 2011 01:07:21 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PiNry-000Gdq-Ot; Thu, 27 Jan 2011 04:10:22 -0500
Date: Thu, 27 Jan 2011 04:10:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <A4324E60B4E050068AC29A5E@PST.JCK.COM>
In-Reply-To: <4D4121B9.2060407@ericsson.com>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <C3BAE1E425FB4058C86138DD@PST.JCK.COM> <4D4121B9.2060407@ericsson.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: "Scott O. Bradner" <sob@harvard.edu>, 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, 27 Jan 2011 09:07:22 -0000

--On Thursday, January 27, 2011 09:41 +0200 Gonzalo Camarillo
<Gonzalo.Camarillo@ericsson.com> wrote:

> Hi,
> 
> yes, I also agree the first one is the most important point
> and has not been addressed so far. If we want a system that
> works (and is used), it needs to include incentives to move
> from one level to the next one. I have discussed this issue
> with quite a few people. Some people claim that those
> incentives exist in some areas (e.g., public institutions
> preferring or requiring full standards in their RFQs) but, at
> least in the RAI area, the incentives are not there in the
> vast majority of cases.

Gonzalo,

Suppose we were to succeed in returning Proposed Standard to its
intended purpose --  more or less a good rough sketch of a
protocol, suitable for implementation and testing with the
support of mailing list discussions -- and being completely
clear about what that meant.   I think the incentives to advance
to a more complete specification that represented community
consensus about its being implementable and probably useful
would then be clear.

That change clearly requires our being very clear internally
that Proposed Standard is a lightweight spec with a lightweight
approval process: if we can't get away from the mentality of
"you made me review this, so I have to find at least something
to comment on and ask for changes" in the various review teams
and the IESG, I think it is pretty much hopeless and that
draft-housley-two-maturity-levels will turn out to accomplish
exactly nothing other than to eliminate whatever further
specification refinement occurs in the few documents that now to
to Full Standard.

As long as we apply a very high bar to entry for Proposed
Standard and insist that specifications at that level are
perfectly good standards, there will rarely be an incentive to
move to the second level, no matter what we call it and whether
or not there is a third level.

I think the change, and the incentives, might be reinforced by
renaming "Proposed" to "Rough Preliminary Specification" or
something else without "Standard" in its name, but that is a
separate matter.

best,
    john






From magnus.westerlund@ericsson.com  Thu Jan 27 01:14:26 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 AA67828C10E; Thu, 27 Jan 2011 01:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.494
X-Spam-Level: 
X-Spam-Status: No, score=-106.494 tagged_above=-999 required=5 tests=[AWL=0.105, 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 YE748kOMQvr5; Thu, 27 Jan 2011 01:14:25 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 4261528C0D6; Thu, 27 Jan 2011 01:14:25 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-a1-4d413827ae71
Received: from esessmw0191.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id E7.62.13987.728314D4; Thu, 27 Jan 2011 10:17:27 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0191.eemea.ericsson.se (153.88.115.85) with Microsoft SMTP Server id 8.2.234.1; Thu, 27 Jan 2011 10:17:26 +0100
Message-ID: <4D413827.7040407@ericsson.com>
Date: Thu, 27 Jan 2011 10:17:27 +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>
In-Reply-To: <B88A8A82-9C4A-40AC-89AF-F177260760F7@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: Thu, 27 Jan 2011 09:14:26 -0000

Cullen Jennings skrev 2011-01-27 01:12:
>
> I'm really glad to see this draft in LC at long last and it is a great
improvement to the current situation - thank you to all the people that
put work into this. I have two significant problems with it that I think
should be resolved before being published
>
>
>
> Big Issues 1: I don't like mandating one port for secure and not
secure versions of a protocol
>
> I don't think this reflects IETF consensus given the number of
protocols that deliberately choses to use two ports. I also don't think
that it is a good idea in all cases. I believe the decision should be
left to the people designing the protocol if they want one port or two.
Let me give some examples
>


We have extensive discussion on this in the WG last call. There was no
consensus for having two ports. At the same time we did also have no
consensus on mandating one port for any future protocol. Thus we
adjusted the text to say in Section 7.2:

IANA strives to assign only one assigned port number per service or
application

To my knowledge "strive" is not a binding RFC2119 term. I also think it
is a good trade-off with the intention of preserving the space as well
as possible with only assigning one port, and still allow for more than
one if it really is needed.

Is it the above text that triggered your comment or some other text?

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 cabo@tzi.org  Thu Jan 27 01:17:10 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 757CF28C123; Thu, 27 Jan 2011 01:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.307
X-Spam-Level: 
X-Spam-Status: No, score=-106.307 tagged_above=-999 required=5 tests=[AWL=-0.058, 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 bUpGDrwDF7FN; Thu, 27 Jan 2011 01:17:09 -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 89A0E28C10E; Thu, 27 Jan 2011 01:17:08 -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 p0R9K1IM005984; Thu, 27 Jan 2011 10:20:01 +0100 (CET)
Received: from [192.168.10.52] (christoph.dagstuhl.de [192.76.146.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F37BE40E; Thu, 27 Jan 2011 10:19:59 +0100 (CET)
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: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>
Date: Thu, 27 Jan 2011 10:20:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D75A1EB1-B142-41D4-A270-FCA8DD81CB23@tzi.org>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.1082)
Cc: Cullen Jennings <fluffy@cisco.com>, 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: Thu, 27 Jan 2011 09:17:10 -0000

On Jan 27, 2011, at 09:52, Lars Eggert wrote:

>> all new protocols should
>>  be security-capable

Sure.

How is this relevant?

In some protocols, there is value to use them without communication =
security (think TLS) for some applications, and with communication =
security for others.
We used to distinguish these two cases using two ports, now we use a =
single port plus per-connection negotiation like STARTLS.
I think the draft is trying to encourage this conversion, and I agree =
with this, at least where latency is less relevant.

With UDP-based protocols, it is harder to do this.
Please look at section 7.3 of

	=
http://tools.ietf.org/html/draft-ietf-core-coap-04.html#section-7.3

and tell us whether this is how you would like this to be handled for =
UDP-based protocols in the future.
If not, we may want to add to the guidance in the (tsvwg) draft.

Gruesse, Carsten


From lars.eggert@nokia.com  Thu Jan 27 01:23:21 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 BFA2528C119; Thu, 27 Jan 2011 01:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.38
X-Spam-Level: 
X-Spam-Status: No, score=-103.38 tagged_above=-999 required=5 tests=[AWL=-0.781, 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 ceESe2PqaKYo; Thu, 27 Jan 2011 01:23:20 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 75B0428C10D; Thu, 27 Jan 2011 01:23:20 -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 p0R9QJcC000941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2011 11:26:21 +0200
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
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-19--14408218; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <D75A1EB1-B142-41D4-A270-FCA8DD81CB23@tzi.org>
Date: Thu, 27 Jan 2011 11:26:11 +0200
Message-Id: <A44FD9FC-6017-4139-A1E1-81C59D5792DD@nokia.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <D75A1EB1-B142-41D4-A270-FCA8DD81CB23@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
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, 27 Jan 2011 11:26:16 +0200 (EET)
X-Nokia-AV: Clean
Cc: Cullen Jennings <fluffy@cisco.com>, 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: Thu, 27 Jan 2011 09:23:21 -0000

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

On 2011-1-27, at 11:20, Carsten Bormann wrote:
> With UDP-based protocols, it is harder to do this.
> Please look at section 7.3 of
>=20
> 	=
http://tools.ietf.org/html/draft-ietf-core-coap-04.html#section-7.3
>=20
> and tell us whether this is how you would like this to be handled for =
UDP-based protocols in the future.
> If not, we may want to add to the guidance in the (tsvwg) draft.

This looks like a totally reasonable way to to this in-band using a =
single port.

Lars=

--Apple-Mail-19--14408218
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEyNzA5MjYxMlowIwYJKoZIhvcNAQkE
MRYEFCPoCX0jwUP+ShAaM9wCn8If3RIYMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AHnlY3oYbhRIBZA5XWOANs3VsVb/7avJN2U+mVjgmpjmMYNGRfKgYptsHPPrCWO3DL/5RXn1PEUU
oO9CrsC4GmLeHmuaofDVl3F7GbhnWxyvWzYdRt7DNyr+wnsH34KXlqVmEc7WgHdf7VVrV/hU+FpL
17n5iPEICQbSAPaFw2pjRX/VTpOLff/Bw1kcFFWNiANigPoNIBAgDDLY7ZVnsINSNygR1Pjf1mYQ
cJfmH0r2D9S63JzmrxSCYEFrtElRQmrX2QM7/qnOxEbSMKjYslXvJwpoapmNVX8k38hlCnF4sSXs
v5KtbP+JkoysBamZe065nfZioLwEfjbTFLiXv+AAAAAAAAA=

--Apple-Mail-19--14408218--

From yaakov_s@rad.com  Thu Jan 27 07:44:31 2011
Return-Path: <yaakov_s@rad.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 282573A67ED; Thu, 27 Jan 2011 07:44:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.49
X-Spam-Level: 
X-Spam-Status: No, score=-102.49 tagged_above=-999 required=5 tests=[AWL=0.108, 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 VJi6SNIQT5w8; Thu, 27 Jan 2011 07:44:27 -0800 (PST)
Received: from antivir1.rad.co.il (antivir1.rad.co.il [62.0.23.193]) by core3.amsl.com (Postfix) with ESMTP id BF23F3A67B8; Thu, 27 Jan 2011 07:44:23 -0800 (PST)
Received: from exrad5.ad.rad.co.il ([192.114.24.28]) by antivir1.rad.co.il with ESMTP; 27 Jan 2011 17:47:26 +0200
Received: from EXUS4-DRP.ad.rad.co.il (192.114.24.119) by EXRAD5.ad.rad.co.il (192.114.24.28) with Microsoft SMTP Server (TLS) id 14.1.218.12; Thu, 27 Jan 2011 17:47:25 +0200
Received: from EXRAD5.ad.rad.co.il ([fe80::ec3e:feb5:8bef:e3ba]) by exus4-drp.ad.rad.co.il ([fe80::5d6f:c2cb:2468:ee2%16]) with mapi id 14.01.0270.001; Thu, 27 Jan 2011 17:47:25 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: Roni Even <Even.roni@huawei.com>, "draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org" <draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14
Thread-Topic: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14
Thread-Index: Acu6zYUM9zrofD2DQv+vmHiCppfgbADaoU9w
Date: Thu, 27 Jan 2011 15:47:24 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC903CD9AA6@EXRAD5.ad.rad.co.il>
References: <03dc01cbbacd$8bff0880$a3fd1980$%roni@huawei.com>
In-Reply-To: <03dc01cbbacd$8bff0880$a3fd1980$%roni@huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.17.170.37]
Content-Type: multipart/alternative; boundary="_000_07F7D7DED63154409F13298786A2ADC903CD9AA6EXRAD5adradcoil_"
MIME-Version: 1.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: Thu, 27 Jan 2011 15:44:31 -0000

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

Roni

Thanks for the nit-catching.

I assume  you RFC5087 not as a reference means you quote RFC5087 not as a r=
eference.

Due to Adrian's DISCUSS we are going to have to respin after the LC;
I will fix all the nits you mention (and Russ' nit as well) at that time.

Y(J)S

From: Roni Even [mailto:Even.roni@huawei.com]
Sent: Sunday, January 23, 2011 09:17
To: draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org; gen-art@ietf.org
Cc: 'IETF-Discussion list'
Subject: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14

Hi,
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-pwe3-oam-msg-map-14

Reviewer: Roni Even

Review Date:2011-1-23

IETF LC End Date: 2011-1-24

IESG Telechat date:



Summary: This draft is ready for publication as a Standard track RFC.



Major issues:





Minor issues:





Nits/editorial comments:



1.  The document starts with Contributors and acknowledgments section. I th=
ink that this is not the major reason for the document and suggest moving t=
hese two sections to the end of the document.

2.  In the Abbreviations and Conventions section which includes the termino=
logy it may be good to reference the terminology from RFC3985.

3.  Towards the end of section 7 and in the beginning of section 11 you RFC=
5087 not as a reference while in other places you have it as a reference. I=
 think it should be written as a reference.






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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:0cm;
	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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:304356142;
	mso-list-type:hybrid;
	mso-list-template-ids:-302068210 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D">Roni<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D">Thanks for the nit-catching.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D">I assume&nbsp; </span>you RFC5087 not as a re=
ference <span style=3D"color:#1F497D">
means </span>you quote RFC5087 not as a reference<span style=3D"color:#1F49=
7D">.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D">Due to Adrian's DISCUSS we are going to have =
to respin after the LC;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D">I will fix all the nits you mention (and Russ=
' nit as well) at that time.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<span style=3D"color:#1F497D">Y(J)S<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:
normal">
<b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;">From:</span></b><span style=3D"font-size:10.0pt;font-family:=
&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Roni Even [mailto:Even.roni@hua=
wei.com]
<br>
<b>Sent:</b> Sunday, January 23, 2011 09:17<br>
<b>To:</b> draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org; gen-art@ietf.org=
<br>
<b>Cc:</b> 'IETF-Discussion list'<br>
<b>Subject:</b> Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14<o:p></o=
:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. F=
or 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=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: <span style=3D"font-family:&quot;Courie=
r New&quot;">draft-ietf-pwe3-oam-msg-map-14<o:p></o:p></span></p>
<p class=3D"MsoPlainText">Reviewer: Roni Even<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date:2011&#8211;1&#8211;23<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2011&#8211;1&#8211;24<o:p></o:p=
></p>
<p class=3D"MsoPlainText">IESG Telechat date:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary: This draft is ready for publication as a=
 Standard track RFC.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:18.0pt"><o:p>&nbsp;</o:p></p=
>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:
l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>The document starts with C=
ontributors and acknowledgments section. I think that this is not the major=
 reason for the document and suggest moving these two sections to the end o=
f the document.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:
l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>In the Abbreviations and C=
onventions section which includes the terminology it may be good to referen=
ce the terminology from RFC3985.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:
l0 level1 lfo2">
<![if !supportLists]><span style=3D"mso-list:Ignore">3.<span style=3D"font:=
7.0pt &quot;Times New Roman&quot;">&nbsp;
</span></span><![endif]><span dir=3D"LTR"></span>Towards the end of section=
 7 and in the beginning of section 11 you RFC5087 not as a reference while =
in other places you have it as a reference. I think it should be written as=
 a reference.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_07F7D7DED63154409F13298786A2ADC903CD9AA6EXRAD5adradcoil_--

From iesg@ietf.org  Thu Jan 27 08:09:36 2011
Return-Path: <iesg@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 50CDE3A67ED; Thu, 27 Jan 2011 08:09:36 -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 aLFE2cTEtCDU; Thu, 27 Jan 2011 08:09:35 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.20]) by core3.amsl.com (Postfix) with ESMTP id 2FF823A682A; Thu, 27 Jan 2011 08:09:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c1a.amsl.com (Postfix) with ESMTP id 4D43FE086B; Thu, 27 Jan 2011 08:12:39 -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 eCXyyJwRhwHa; Thu, 27 Jan 2011 08:12:39 -0800 (PST)
Received: from [192.168.2.100] (pool-96-255-13-194.washdc.fios.verizon.net [96.255.13.194]) by c1a.amsl.com (Postfix) with ESMTPSA id AFE65E0809; Thu, 27 Jan 2011 08:12:38 -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: IETF Chair <iesg@ietf.org>
In-Reply-To: <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
Date: Thu, 27 Jan 2011 11:12:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <37255E32-37F1-4907-8A5A-6AB7B590562F@ietf.org>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
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: Thu, 27 Jan 2011 16:09:36 -0000

Cullen:

> Big Issues 1: I don't like mandating one port for secure and not =
secure versions of a protocol=20
>=20
> I don't think this reflects IETF consensus given the number of =
protocols that deliberately choses to use two ports. I also don't think =
that it is a good idea in all cases. I believe the decision should be =
left to the people designing the protocol if they want one port or two. =
Let me give some examples
>=20
> Imagine a client server protocol that runs over UDP and uses DTLS for =
security. The server will simultaneously serve requests over both DTLS =
and UDP. When the server receives a packet, it needs to be able to demux =
if it is a UDP packet or a DTLS packet. The obvious demux code point is =
the port. Yes, one might be able to reinvent a concept of a stream along =
with a 5 tuple and something like STARTTLS but this has many other =
problems. It means the client needs to use a different SRC port for each =
different "session" to the same server. This uses up NAT ports and =
complicates NAT traversal. It also adds additional latency to set up a =
small session. People just aren't going to do it. The other approach is =
demux based on the first byte inside the UDP packet. The CoAP protocol  =
being developed in the CORE WG has taken that approach. The CORE WG =
proposed to the TLS chairs that over half the remaining code space for =
the TLS code point in the first byte be assigned to CoAP. The TLS =
chairs, more or less told the CORE guys to get stuffed (politely of =
course). Two ports is the obvious answer.=20
>=20
> Lets consider another example. As the draft mentions, firewalls help =
apply policy, and catch configuration errors. Take an organization (like =
my house) that has a policy of no email over unencrypted protocols. It's =
really easy to set up a firewall policy that allows the encrypted ports =
and blocks the non encrypted ports that are typically used for email and =
does not require the firewall to do DPI. No doubt my daughter could =
figure out to circumvent this and sent unencrypted email via an VPN =
tunneled over DNS or ICMP or something but thats not the point - the =
point is to catch accidental misconfiguration, like the type that happen =
during software upgrades. You can agree or disagree about using =
firewalls this way but the fact remains, lots of people do use firewalls =
this way.=20
>=20
> I strongly urge this draft not to take on mandating one port - leave =
the decision with the designers of the protocol. If draft does mandate =
one port, you will end up with a port registered for protocol foo and a =
port for a proprietary protocol with no description called foo-secure.  =
As I mentioned before, I also do not believe there is IETF consensus for =
one port.=20

Originally, two ports were assigned for plain and over-TLS, which for =
HTTP mapped to two different URL schemes: http and https.

Many people thought that this was a waste of a port, and the STARTTLS =
approach was developed.  You say that it does not work in some cases, =
and you seem to be suggesting that we go back to the original way.

Maybe it works in some cases and not others.  Can we say which is which?

Russ


From paul.hoffman@vpnc.org  Thu Jan 27 08:38:16 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 42C473A690E for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 08:38:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.742
X-Spam-Level: 
X-Spam-Status: No, score=-101.742 tagged_above=-999 required=5 tests=[AWL=0.304, 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 Mvf2a255w6O7 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 08:38:15 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 801773A690F for <ietf@ietf.org>; Thu, 27 Jan 2011 08:38:15 -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 p0RGfIw8063145 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 27 Jan 2011 09:41:19 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D41A02E.7070701@vpnc.org>
Date: Thu, 27 Jan 2011 08:41:18 -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: 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> <37255E32-37F1-4907-8A5A-6AB7B590562F@ietf.org>
In-Reply-To: <37255E32-37F1-4907-8A5A-6AB7B590562F@ietf.org>
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, 27 Jan 2011 16:38:16 -0000

On 1/27/11 8:12 AM, IETF Chair wrote:
> Originally, two ports were assigned for plain and over-TLS, which for HTTP mapped to two different URL schemes: http and https.
>
> Many people thought that this was a waste of a port, and the STARTTLS approach was developed.  You say that it does not work in some cases, and you seem to be suggesting that we go back to the original way.
>
> Maybe it works in some cases and not others.  Can we say which is which?

In a word: no. We have very little operational experience, and where we 
do, it gives conflicting results. Some mail client developers say that 
POP and IMAP STARTTLS works fine, some say that it is unreliable and so 
they just use the alternate ports.

Note that Cullen's example for where it almost certainly would not work 
is for non-stream UDP. Making UDP developers have to come up with a 
stream-like capability to do a STARTTLS-style single port solution 
defeats the purpose of using UDP. The benefit of "we saved another 
port!" over "we forced someone to make UDP more like TCP!" seems like a 
false one.

From joelja@bogus.com  Thu Jan 27 09:30:30 2011
Return-Path: <joelja@bogus.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 C4B6A3A6975 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 09:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.011
X-Spam-Level: 
X-Spam-Status: No, score=-96.011 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FB_WORD1_END_DOLLAR=3.294, FB_WORD2_END_DOLLAR=3.294, 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 d0ZBvtdfrRSj for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 09:30:29 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 1D9D23A698D for <ietf@ietf.org>; Thu, 27 Jan 2011 09:30:28 -0800 (PST)
Received: from joelja-mac.local (adsl-99-173-15-226.dsl.pltn13.sbcglobal.net [99.173.15.226]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id p0RHXUhP055484 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 27 Jan 2011 17:33:31 GMT (envelope-from joelja@bogus.com)
Message-ID: <4D41AC6A.40605@bogus.com>
Date: Thu, 27 Jan 2011 09:33:30 -0800
From: Joel Jaeggli <joelja@bogus.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: 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>	<37255E32-37F1-4907-8A5A-6AB7B590562F@ietf.org> <4D41A02E.7070701@vpnc.org>
In-Reply-To: <4D41A02E.7070701@vpnc.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 27 Jan 2011 17:30:30 -0000

On 1/27/11 8:41 AM, Paul Hoffman wrote:
> On 1/27/11 8:12 AM, IETF Chair wrote:
>> Originally, two ports were assigned for plain and over-TLS, which for
>> HTTP mapped to two different URL schemes: http and https.
>>
>> Many people thought that this was a waste of a port, and the STARTTLS
>> approach was developed.  You say that it does not work in some cases,
>> and you seem to be suggesting that we go back to the original way.
>>
>> Maybe it works in some cases and not others.  Can we say which is which?
> 
> In a word: no. We have very little operational experience, and where we
> do, it gives conflicting results. Some mail client developers say that
> POP and IMAP STARTTLS works fine, some say that it is unreliable and so
> they just use the alternate ports.

So I can say that having provided a large scale mail-service in a former
life that we made it work for our customers.

On the SMTP side on the virtually everyone has this working except those
people that use 465, because the service you're talking to on 587 is
fundamentaly the same one that's on 25.

joelja-mac:tmp joelja$ telnet nagasaki.bogus.com 25
Trying 147.28.0.81...
Connected to nagasaki.bogus.com.
Escape character is '^]'.
220 nagasaki.bogus.com ESMTP Sendmail 8.14.4/8.14.4; Thu, 27 Jan 2011
17:28:24 GMT
ehlo jaeggli
250-nagasaki.bogus.com Hello adsl-99-173-15-226.dsl.pltn13.sbcglobal.net
[99.173.15.226], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN
250-STARTTLS
250-DELIVERBY
250 HELP

> Note that Cullen's example for where it almost certainly would not work
> is for non-stream UDP. Making UDP developers have to come up with a
> stream-like capability to do a STARTTLS-style single port solution
> defeats the purpose of using UDP. The benefit of "we saved another
> port!" over "we forced someone to make UDP more like TCP!" seems like a
> false one.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 


From daedulus@btconnect.com  Thu Jan 27 09:59:36 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 AE46A3A684C; Thu, 27 Jan 2011 09:59:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 kuprjlyINNLU; Thu, 27 Jan 2011 09:59:31 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by core3.amsl.com (Postfix) with ESMTP id 1AEF73A67CF; Thu, 27 Jan 2011 09:59:30 -0800 (PST)
Received: from host86-134-204-119.range86-134.btcentralplus.com (HELO pc6) ([86.134.204.119]) by c2beaomr07.btconnect.com with SMTP id BOB92254; Thu, 27 Jan 2011 18:02:28 +0000 (GMT)
Message-ID: <00a401cbbe43$76e693e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Lars Eggert" <lars.eggert@nokia.com>, "Cullen Jennings" <fluffy@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost><B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.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: Thu, 27 Jan 2011 17:58:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4D41B334.00A8, actions=tag
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4D41B335.0037,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: Thu, 27 Jan 2011 17:59:36 -0000

And what happens when we have ProtocolX over SSH and ProtocolX over TLS?

Must they share a port, with ProtocolX, which has been quietly using its
assigned port for
20 years?

Tom Petch


----- Original Message -----
From: "Lars Eggert" <lars.eggert@nokia.com>
To: "Cullen Jennings" <fluffy@cisco.com>; "Paul Hoffman" <paul.hoffman@vpnc.org>
Cc: "IESG IESG" <iesg@ietf.org>; "IETF discussion list" <ietf@ietf.org>;
<tsvwg@ietf.org>
Sent: Thursday, January 27, 2011 9:52 AM
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


On 2011-1-27, at 2:12, Cullen Jennings wrote:
> Big Issues 1: I don't like mandating one port for secure and not secure
versions of a protocol
>
> I don't think this reflects IETF consensus given the number of protocols that
deliberately choses to use two ports. I also don't think that it is a good idea
in all cases. I believe the decision should be left to the people designing the
protocol if they want one port or two. Let me give some examples

Paul Hoffman raised this issue as well (email from Nov 4 to this list.)

There was some discussion that lead to Paul suggesting specific edit to this
document. (Which are not reflected in -09; us editors may have dropped the ball
here). I'm attaching Paul's proposed changes below, could you check if you'd
agree with them?

> Big Issue #2: The draft has close to no review advice for the expert reviewer.

Joe Touch (who leads the expert review team for ports) is working on a separate
document (draft-touch-tsvwg-port-use). The first version of that draft was
issued on the same day as the -09 version of iana-ports, which is why we don't
refer to it.

Does draft-touch-tsvwg-port-use have the content you are looking for? If so, we
should refer to it. (We should probably refer to it anyway, in a "you may also
want to read this" kind-of way.)

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

Lars

PS: Paul's proposed changes re item #1:

Begin forwarded message:
> From: Paul Hoffman <paul.hoffman@vpnc.org>
> Date: November 15, 2010 21:44:24 GMT+02:00
> To: <tsvwg@ietf.org>
> Subject: Proposed resolution for security issues with
draft-ietf-tsvwg-iana-ports-08
>
> As this list and the TLS has seen, there is a wide variety of views on how to
deal with fallback-to-insecure in protocols. I believe that the security
community has no consensus on what this means, much less how to do it. My
earlier proposal (continue to allow registration of two ports) was popular with
some, unpopular with others; similarly, so was "force all protocols to use one
port".
>
> Therefore, I retract my proposal to allow two-port registrations for
fallback-to-insecure. However, I still recommend some changes to the text to
reflect the view that STARTTLS is not the only way to have such a feature on one
port.
>
> This will be an interesting IETF Last Call discussion.
>
> I propose the following changes to draft-ietf-tsvwg-iana-ports:
>
> Section 7.2 current:
> o  IANA will allocate only one assigned port number for all versions
>   of a service (e.g., running the service with or without a security
>   mechanism, or for updated variants of a service)
>
> Section 7.2 current:
[in the line above s/current/proposed/, I think]
> o  IANA will normally allocate only one assigned port number for all versions
>   of a service (e.g., running the service with or without a security
>   mechanism, or for updated variants of a service). This policy can
>   be overridden by the expert reviewer.
>
> Section 7.2 current:
>   Further,
>   previous separation of protocol variants based on security
>   capabilities (e.g., HTTP on TCP port 80 vs. HTTPS on TCP port 443) is
>   not recommended for new protocols, because all new protocols should
>   be security-capable and capable of negotiating the use of security
>   in-band.
>
> Section 7.2 proposed:
>   Further,
>   previous separation of protocol variants based on security
>   capabilities (e.g., HTTP on TCP port 80 vs. HTTPS on TCP port 443) is
>   not recommended for new protocols, because all new protocols should
>   be security-capable.
>
> --Paul Hoffman, Director
> --VPN Consortium


From lars.eggert@nokia.com  Thu Jan 27 10:08:35 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 1E39028C151; Thu, 27 Jan 2011 10:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.063
X-Spam-Level: 
X-Spam-Status: No, score=-103.063 tagged_above=-999 required=5 tests=[AWL=-1.064, BAYES_00=-2.599, J_CHICKENPOX_15=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 f4Y29xzfe0hv; Thu, 27 Jan 2011 10:08:34 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id 62C2428C14D; Thu, 27 Jan 2011 10:08:34 -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 p0RIBYwY012260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2011 20:11:36 +0200
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
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-2-17107338; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <00a401cbbe43$76e693e0$4001a8c0@gateway.2wire.net>
Date: Thu, 27 Jan 2011 20:11:27 +0200
Message-Id: <D8AE8A20-B6E6-4159-BBF0-20EC4A939623@nokia.com>
References: <20110118212603.5733.34489.idtracker@localhost><B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <00a401cbbe43$76e693e0$4001a8c0@gateway.2wire.net>
To: "t.petch" <daedulus@btconnect.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, 27 Jan 2011 20:11:32 +0200 (EET)
X-Nokia-AV: Clean
Cc: Cullen Jennings <fluffy@cisco.com>, 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: Thu, 27 Jan 2011 18:08:35 -0000

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

On 2011-1-27, at 18:58, t.petch wrote:
> And what happens when we have ProtocolX over SSH and ProtocolX over =
TLS?
>=20
> Must they share a port, with ProtocolX, which has been quietly using =
its
> assigned port for
> 20 years?

No. The expert reviewer can obviously assign a second port in that case =
(if ProtocolX doesn't have a feature negotiation capability built in so =
that the port could be shared.)

But we don't want to allocate multiple ports for the different security =
flavors of *new* protocols. At least we want this to be the exception.

The expert team is (from what I hear) seeing frequent applications that =
look like "Hi, we're company X and our foo protocol runs on TCP. We'd =
like a port for that, and one for when we run foo over TLS."

Lars=

--Apple-Mail-2-17107338
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEyNzE4MTEyN1owIwYJKoZIhvcNAQkE
MRYEFEfsQJ/bQKhcXSnnynH1ox0ZYPD0MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AE4ci1Rc8ywo4RkMi4SKd/MBsg7OEYgiP30PALUODnlU0TDAVK7387Q2YO/Acvhlj8n5HJA+0V69
k145lyw2bJPCeFl7oxXoPCilY5e6cdbrav2mCQuGXEsQC7DEPpyEvQWCpw12s6M6nUc8TA1UT9Zk
fzEmf0RLWheQrd9/dOTWunmHv9nTOgR8v79A9SxQRDcCPRyToDFx37CIuO4bEaUK5SN1/iUjVvq/
N8/pG0OXQOdtSyaUT+IO1t2GslOKN7S9eSktlX31KPS2lWFxDRVUFLuGVWBkODunq5MnhIkNoUl+
hRGK7SjLEzJs4Y6wdw3YVHZCilq4nrzYd3a5/h0AAAAAAAA=

--Apple-Mail-2-17107338--

From dhc2@dcrocker.net  Thu Jan 27 12:32:21 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 10E7B3A696B for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 12:32:21 -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 QOwCuFQbZvnV for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 12:32:19 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id AA61F3A6A5B for <ietf@ietf.org>; Thu, 27 Jan 2011 12:32:19 -0800 (PST)
Received: from [192.168.1.3] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0RKZEjm003394 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2011 12:35:22 -0800
Message-ID: <4D41D6F8.5050205@dcrocker.net>
Date: Thu, 27 Jan 2011 12:35:04 -0800
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: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
In-Reply-To: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 27 Jan 2011 12:35:22 -0800 (PST)
Cc: 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: Thu, 27 Jan 2011 20:32:21 -0000

On 1/26/2011 7:29 PM, Scott O. Bradner wrote:
> 2/ I think the proposal must specifically deal with the 2026 IPR licence
>     requirement in section 4.1.2
>
>        If patented or otherwise controlled technology
>        is required for implementation, the separate implementations must
>        also have resulted from separate exercise of the licensing process.
>
>     The requirement can be dealt with by explicitly discarding
>     it or by including it. But not mentioning the requirement does
>     not make the issue go away.  This requirement was, in theory, a
>     way to keep the IETF/IESG out of the business of evaluating
>     the fairness of licensing terms.  I can remember only
>     one time it came up (in an appeal) so getting rid of it may
>     be fine - but don't make it look like it was just forgotten.


Please note that this reply is only about Scott's friendly amendment for one 
added sentence to cover "interoperability" about IPR:

+1

It's terse, relevant and seems pragmatic.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From dougb@dougbarton.us  Thu Jan 27 13:48:03 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 4F26F3A69D7 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 13:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  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 MiM+upvjgRFd for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 13:48:02 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by core3.amsl.com (Postfix) with ESMTP id 7AE383A69D4 for <ietf@ietf.org>; Thu, 27 Jan 2011 13:47:54 -0800 (PST)
Received: (qmail 14399 invoked by uid 399); 27 Jan 2011 21:50:54 -0000
Received: from localhost (HELO doug-optiplex.ka9q.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 27 Jan 2011 21:50:54 -0000
X-Originating-IP: 127.0.0.1
X-Sender: dougb@dougbarton.us
Message-ID: <4D41E8AE.1020009@dougbarton.us>
Date: Thu, 27 Jan 2011 13:50:38 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101212 Thunderbird/3.1.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>	<C3BAE1E425FB4058C86138DD@PST.JCK.COM>	<4D4121B9.2060407@ericsson.com> <A4324E60B4E050068AC29A5E@PST.JCK.COM>
In-Reply-To: <A4324E60B4E050068AC29A5E@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: ietf@ietf.org, "Scott O. Bradner" <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: Thu, 27 Jan 2011 21:48:03 -0000

On 01/27/2011 01:10, John C Klensin wrote:
>
>
> --On Thursday, January 27, 2011 09:41 +0200 Gonzalo Camarillo
> <Gonzalo.Camarillo@ericsson.com>  wrote:
>
>> Hi,
>>
>> yes, I also agree the first one is the most important point
>> and has not been addressed so far. If we want a system that
>> works (and is used), it needs to include incentives to move
>> from one level to the next one. I have discussed this issue
>> with quite a few people. Some people claim that those
>> incentives exist in some areas (e.g., public institutions
>> preferring or requiring full standards in their RFQs) but, at
>> least in the RAI area, the incentives are not there in the
>> vast majority of cases.
>
> Gonzalo,
>
> Suppose we were to succeed in returning Proposed Standard to its
> intended purpose --  more or less a good rough sketch of a
> protocol, suitable for implementation and testing with the
> support of mailing list discussions -- and being completely
> clear about what that meant.   I think the incentives to advance
> to a more complete specification that represented community
> consensus about its being implementable and probably useful
> would then be clear.
>
> That change clearly requires our being very clear internally
> that Proposed Standard is a lightweight spec with a lightweight
> approval process: if we can't get away from the mentality of
> "you made me review this, so I have to find at least something
> to comment on and ask for changes" in the various review teams
> and the IESG, I think it is pretty much hopeless and that
> draft-housley-two-maturity-levels will turn out to accomplish
> exactly nothing other than to eliminate whatever further
> specification refinement occurs in the few documents that now to
> to Full Standard.
>
> As long as we apply a very high bar to entry for Proposed
> Standard and insist that specifications at that level are
> perfectly good standards, there will rarely be an incentive to
> move to the second level, no matter what we call it and whether
> or not there is a third level.
>
> I think the change, and the incentives, might be reinforced by
> renaming "Proposed" to "Rough Preliminary Specification" or
> something else without "Standard" in its name, but that is a
> separate matter.

I've made this statement before, so I'll only touch on it briefly. The 
world outside the IETF does not understand the difference between our 
various flavors of "RFC" now. There is absolutely no hope of refining 
that understanding EXternally when we can't even follow it consistently 
INternally.

To some extent I think Russ' draft accurately reflects the status quo, 
namely that drafts are the new proposed, and that proposed is the new 
deployed. I'm hesitant to provide full-throated support for the draft 
for a few reasons:

1. To the extent that anyone still cares that I once managed the IANA I 
don't want to appear to be trying to influence the IETF's processes.
2. As an IETF participant I haven't fully thought through all the 
ramifications of the draft.
3. As both an IETF participant and as a consumer of the standards we 
create I still believe (as I've said previously) that what we need is 
not an evolution, but a revolution; with different names for things that 
more accurately reflect their status and intended use. However, it's 
pretty obvious at this point that there is no broad support for this 
position, so I won't waste more time on it.


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 touch@isi.edu  Thu Jan 27 17:08:01 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 924693A6A38; Thu, 27 Jan 2011 17:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 ddb6J4L32OqN; Thu, 27 Jan 2011 17:08:00 -0800 (PST)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 946223A6A0D; Thu, 27 Jan 2011 17:08:00 -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 p0S1AjEM007742 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Thu, 27 Jan 2011 17:10:45 -0800 (PST)
Message-ID: <4D421795.70505@isi.edu>
Date: Thu, 27 Jan 2011 17:10:45 -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: Lars Eggert <lars.eggert@nokia.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>
In-Reply-To: <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: p0S1AjEM007742
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Cullen Jennings <fluffy@cisco.com>, 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: Fri, 28 Jan 2011 01:08:01 -0000

On 1/27/2011 12:52 AM, Lars Eggert wrote:
...
>> 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?

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.e., we are advisors to IANA.

Further, many requests are handled my multiple reviewers.

Many of us do have specific conversations with applicants, and identify 
ourselves when that happens, but it doesn't seem important to codify 
that in this doc.

Again, this doc is about the unification of the registries. It is NOT 
about all the other policies that govern them. The info that's there is 
advisory ONLY (it is not binding to IANA).

Joe

From michelle.cotton@icann.org  Thu Jan 27 17:26:34 2011
Return-Path: <michelle.cotton@icann.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 BF8C83A68FC; Thu, 27 Jan 2011 17:26:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.461
X-Spam-Level: 
X-Spam-Status: No, score=-106.461 tagged_above=-999 required=5 tests=[AWL=0.138, 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 ApVSkWZSX-7L; Thu, 27 Jan 2011 17:26:32 -0800 (PST)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by core3.amsl.com (Postfix) with ESMTP id 986173A6B47; Thu, 27 Jan 2011 17:26:31 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Thu, 27 Jan 2011 17:29:36 -0800
From: Michelle Cotton <michelle.cotton@icann.org>
To: Joe Touch <touch@isi.edu>, Lars Eggert <lars.eggert@nokia.com>
Date: Thu, 27 Jan 2011 17:29:34 -0800
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: Acu+iEzAJ7ZkWDlMTVmmf9FwyJMukAAAoTBe
Message-ID: <C9675BFE.2B995%michelle.cotton@icann.org>
In-Reply-To: <4D421795.70505@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Cullen Jennings <fluffy@cisco.com>, Paul Hoffman <paul.hoffman@vpnc.org>, The 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: Fri, 28 Jan 2011 01:26:34 -0000

We are changing that process right now.  We have begun to report the
reviewer (with the review) in the email to the requester.

We just need to make sure this small change is communicated to those expert=
s
that are part of review "teams" as their individual names are not published
on the main list of registries.

I don't think it needs to go in this document as this is already in
progress.

Let me know if you have any questions.

--Michelle



On 1/27/11 5:10 PM, "Joe Touch" <touch@isi.edu> wrote:

>=20
>=20
> On 1/27/2011 12:52 AM, Lars Eggert wrote:
> ...
>>> Small Issue #3: I object to anonymous review
>>>=20
>>> 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 i=
t
>>> encourages really bad behavior. I have several emails with an expert
>>> reviewer relayed via IANA where the conversation was going no where - o=
nce 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 thes=
e
>>> emails to the list as that would just not be kind to anyone but I am ha=
ppy
>>> to forward them to the IESG if they think looking at them is really
>>> critical.
>>=20
>> I can see your point, and I personally have no problem with disclosing t=
he
>> reviewer identity. What do others think?
>=20
> 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.
>=20
> I.e., we are advisors to IANA.
>=20
> Further, many requests are handled my multiple reviewers.
>=20
> Many of us do have specific conversations with applicants, and identify
> ourselves when that happens, but it doesn't seem important to codify
> that in this doc.
>=20
> Again, this doc is about the unification of the registries. It is NOT
> about all the other policies that govern them. The info that's there is
> advisory ONLY (it is not binding to IANA).
>=20
> Joe


From sm@resistor.net  Thu Jan 27 17:34:16 2011
Return-Path: <sm@resistor.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 83E2F3A6B53 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 17:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.609
X-Spam-Level: 
X-Spam-Status: No, score=-103.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 S0T-fHe8KYBX for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 17:34:13 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id C22553A6B52 for <ietf@ietf.org>; Thu, 27 Jan 2011 17:34:13 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0S1b8Or004765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 27 Jan 2011 17:37:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1296178637; x=1296265037; bh=EOlmyHPcvHFV2Nod0hKBvQyUMvV2ai5XI86v5gRfgFg=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=Dik5KytcNOU57KaMELYTXcl3okVT6OVC2gd/zauO72IOIv+ecxvHDO9hshC1fqzAs JXksHC8xu3ZKMAV0kl50CYfCQg/2xN1N/fY2HKXjawkENRVXomf9j4HFjIdJxJC6UF l0bIyHdac6Wi66+iwHUORo+WjXt2Ko8TuBIyha/8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1296178637; x=1296265037; bh=EOlmyHPcvHFV2Nod0hKBvQyUMvV2ai5XI86v5gRfgFg=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=rF21guCdY/3VyBKO8AboAt+CoWH6WcAG+U7nUJhLlfd6eDR8LyPDKlvhUu6gywEK3 Kg0epXZzZS3YSUtCBcIBYNmUCnHtJBM/eieEiAa40yTDsmDDf4zEVLSJwcith5yrBt jQc+upyZLyp3cMFleutqRzH79ac56URCFNg41/xo=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=HiT2+MMyQv8pVY3ZrrcfLPbMUJOQWmrN6QhW/hPVXY7WlIycgAmbCajNagY1e+4v7 OPn7kGp2zS0hw59U+YioZZAaMyuSWYgt3yM2/8WgiZJrZ5S+Ym8cb2QcNSSUi0QEzFE 4DAm95BRppCongiPJ3lA4CcktoB/vEYSyxwrE9o=
Message-Id: <6.2.5.6.2.20110127151321.0e5ac3d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jan 2011 17:36:26 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: draft-housley-two-maturity-levels
In-Reply-To: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 28 Jan 2011 01:34:16 -0000

At 19:29 26-01-11, Scott O. Bradner wrote:
>1/ I still do not think this (modified) proposal will have any real
>    impact on the number of "Proposed Standard" documents that move
>    to a (in this proposal, "the") higher level since I do not see
>    how this makes any significant changes to the underlying reasons
>    that documents have not progressed in the past - i.e., I see no
>    reason to think that this proposal would change the world much
>    (would not help, would not hurt)

If this draft is published, there may be more documents moving to the 
next level.  There has been some comments about stated requirements 
for Proposed Standard being restored.  It requires more than a BCP 
for that to happen.

In Section 2:

  "Reconsideration of the portions that were previously approved for
   publication as a Proposed Standard requires evidence that the
   unchanged features are causing harm to the Internet."

I gather that there won't be any requirement for interoperability.

That draft does not say which sections of RFC 2026 are being 
updated.  As I do not have any IETF experience, I'll defer to what 
the elders of the IETF have to say about BCP 9 if it ever becomes 
subject to interpretation. :-)

At 01:10 27-01-11, John C Klensin wrote:
>I think the change, and the incentives, might be reinforced by
>renaming "Proposed" to "Rough Preliminary Specification" or
>something else without "Standard" in its name, but that is a
>separate matter.

The constituency has a lot of authors of documents which are at 
"Proposed Standard".  A name change will face strong resistance 
unless it is at least at par with the current gold standard.

At 13:50 27-01-11, Doug Barton wrote:
>I've made this statement before, so I'll only touch on it briefly. 
>The world outside the IETF does not understand the difference 
>between our various flavors of "RFC" now. There

As it is probably the consensus of the IETF that the world inside the 
IETF understands the difference, it is not worth arguing about.

>3. As both an IETF participant and as a consumer of the standards we 
>create I still believe (as I've said previously) that what we need 
>is not an evolution, but a revolution; with different names for 
>things that more accurately reflect their status and intended use. 
>However, it's pretty obvious at this point that there is no broad 
>support for this position, so I won't waste more time on it.

A revolution is only possible if the world runs out of IPv4 addresses 
or if there is support from business constituency, whichever happens later.

Regards,
-sm 


From ned+ietf@mauve.mrochek.com  Thu Jan 27 18:00:57 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 99A523A6B6E for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 18:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=-0.250, 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 K75C8wLnaIMe for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 18:00:56 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id F39163A6B65 for <ietf@ietf.org>; Thu, 27 Jan 2011 18:00:55 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NX4L8O4CLC00GKUB@mauve.mrochek.com> for ietf@ietf.org; Thu, 27 Jan 2011 18:03:59 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NWP1MZKQSW007FL5@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 27 Jan 2011 18:03:55 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01NX4L8MKNFI007FL5@mauve.mrochek.com>
Date: Thu, 27 Jan 2011 17:43:16 -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 Wed, 26 Jan 2011 17:12:44 -0700" <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>
To: Cullen Jennings <fluffy@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1296177160; i=@mrochek.com; bh=2UvZsLUE4WQwheIgZQeu/cFZZsl3RnTbF9QyBalfjFc=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=SC45io/wkTL6SiJ2QSdpnjnr/7JIvnu9+olMmx1gSdOx+qxLZo+CcKgsHV/RAR5Yz AFvaEk7Hkj1Dl/dxMsMY+jR50l1Kc4s50W7vButIUzCMjWsoWAQU6xIi5hP85spyZf Nb92xseAsylZaORhBWx0BOvXJ4DUQn4Ff4PfOn20=
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: Fri, 28 Jan 2011 02:00:57 -0000

> Big Issues 1: I don't like mandating one port for secure and not secure
> versions of a protocol

I don't either, so it's good that the document doesn't do that. It says:

   Services are expected to include support for security, either as
   default or dynamically negotiated in-band.  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.

"is to be avoided" != "forbidden". There are legitimate use-cases for
two port approaches - not many, but some - so they should be avoided but not
banned. And the main reason for this isn't to encourage optional use of
negotiated in-band security, but rather because deployment of insecure
service variants no matter what the protocol details are bad idea.

> I don't think this reflects IETF consensus given the number of protocols that
> deliberately choses to use two ports. I also don't think that it is a good idea
> in all cases. I believe the decision should be left to the people designing the
> protocol if they want one port or two. Let me give some examples


> Imagine a client server protocol that runs over UDP and uses DTLS for
> security. The server will simultaneously serve requests over both DTLS and UDP.
> When the server receives a packet, it needs to be able to demux if it is a UDP
> packet or a DTLS packet. The obvious demux code point is the port. Yes, one
> might be able to reinvent a concept of a stream along with a 5 tuple and
> something like STARTTLS but this has many other problems. It means the client
> needs to use a different SRC port for each different "session" to the same
> server. This uses up NAT ports and complicates NAT traversal. It also adds
> additional latency to set up a small session. People just aren't going to do
> it. The other approach is demux based on the first byte inside the UDP packet.


> The CoAP protocol  being developed in the CORE WG has taken that approach. The
> CORE WG proposed to the TLS chairs that over half the remaining code space for
> the TLS code point in the first byte be assigned to CoAP. The TLS chairs,
> more or less told the CORE guys to get stuffed (politely of course). Two
> ports is the obvious answer.

And nothing in this document would prevent such an assignment from being
made as long as there are compelling reasons to do so.

> Lets consider another example. As the draft mentions, firewalls help apply
> policy, and catch configuration errors. Take an organization (like my house)
> that has a policy of no email over unencrypted protocols.

I have to say that that policy must be pretty tricky to implement given
the widespread lack of encryption support in SMTP relay scenarios.

> It's really easy to set up a firewall policy that allows the encrypted ports
> and blocks the non encrypted ports that are typically used for email and does
> not require the firewall to do DPI.

But this doesn't address the bad configuration problem at all - all it does is
change the location where the problem would have to be, from the mail server
configuration (which, if it was compliant with the relevant email standards,
should have been fairly secure by default) to the firewall (which doesn't 
really have a means of being secure by default without DPI). Now, perhaps
you'll argue that firewalls configs are less likely to be grinched than those
of an email server. If so, all I can say is that doesn't jibe with my
experience.

> No doubt my daughter could figure out to circumvent this and sent unencrypted
> email via an VPN tunneled over DNS or ICMP or something but thats not the point
> - the point is to catch accidental misconfiguration, like the type that happen
> during software upgrades. You can agree or disagree about using firewalls this
> way but the fact remains, lots of people do use firewalls this way.

And lots of people screw up their firewall configurations in the process. 

> I strongly urge this draft not to take on mandating one port - leave the
> decision with the designers of the protocol. If draft does mandate one port,
> you will end up with a port registered for protocol foo and a port for a
> proprietary protocol with no description called foo-secure.  As I mentioned
> before, I also do not believe there is IETF consensus for one port.

Actually, I suspect there is rough consensus on the one port approach, in the
TCP space at least. A few exceptions don't invalidate that.

As for two registrations versus one, I would not object for there to be some
cleaner mechanism for two port assignments. But any such mechanism needs to
jibe with the reality that the best solution for production services is not to
have an insecure variant at all, either on a separate port or negotiated
in-band.

				Ned

From mrex@sap.com  Thu Jan 27 18:27:56 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 616BD3A68B8 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 18:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.152
X-Spam-Level: 
X-Spam-Status: No, score=-10.152 tagged_above=-999 required=5 tests=[AWL=0.097, 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 2wxZolHq8dLn for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 18:27:43 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id 2E48E3A6B6F for <ietf@ietf.org>; Thu, 27 Jan 2011 18:27:41 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p0S2Uiwp007240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 28 Jan 2011 03:30:44 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201101280230.p0S2UhrM006665@fs4113.wdf.sap.corp>
Subject: Re: draft-housley-two-maturity-levels
To: sob@harvard.edu (Scott O. Bradner)
Date: Fri, 28 Jan 2011 03:30:43 +0100 (MET)
In-Reply-To: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> from "Scott O. Bradner" at Jan 26, 11 10:29:24 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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: Fri, 28 Jan 2011 02:27:56 -0000

Scott O. Bradner wrote:
> 
> 1/ I still do not think this (modified) proposal will have any real
>    impact on the number of "Proposed Standard" documents that move
>    to a (in this proposal, "the") higher level since I do not see
>    how this makes any significant changes to the underlying reasons
>    that documents have not progressed in the past - i.e., I see no
>    reason to think that this proposal would change the world much
>    (would not help, would not hurt)

The reason why so many documents are at proposed is that they're
often collections of bloat (limited-use features with an aggresive
requirements level) from various interest groups that is
not strictly necessary for a protocol to be useful, and sometimes
used only by a minority.

Normally, for progression from Proposed to Draft,

   - some of the MUSTs would have to be changed to SHOULDs,
   - some of the SHOULDs would have to be changed to MAYs,
   - some parts might better be moved to seperate, optional
     extensions documents

But the particular interest groups would rather have the document
remain at Proposed than seeing any of the requirements level of
those particular features they're interested in, to come out lowered,
or see features removed from the base protocol and into a
seperate extensions document.


This is one of the reasons why there is a constant stream of new
authentication protocols.


-Martin


From narten@us.ibm.com  Thu Jan 27 21:50:18 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 43E073A6BB1 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 21:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.055
X-Spam-Level: 
X-Spam-Status: No, score=-106.055 tagged_above=-999 required=5 tests=[AWL=0.544, 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 sSgmRTNMebMB for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 21:50: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 CFDB33A6BAE for <ietf@ietf.org>; Thu, 27 Jan 2011 21:50:09 -0800 (PST)
Received: from d01dlp01.pok.ibm.com (d01dlp01.pok.ibm.com [9.56.224.56]) by e4.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p0S5YpUv022762 for <ietf@ietf.org>; Fri, 28 Jan 2011 00:34:51 -0500
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id E66AB728042 for <ietf@ietf.org>; Fri, 28 Jan 2011 00:53:07 -0500 (EST)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p0S5r7vh298558 for <ietf@ietf.org>; Fri, 28 Jan 2011 00:53:07 -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 p0S5r7vV018598 for <ietf@ietf.org>; Fri, 28 Jan 2011 00:53:07 -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 p0S5r3dS018268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 28 Jan 2011 00:53:04 -0500
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 p0S5r21E022348 for <ietf@ietf.org>; Fri, 28 Jan 2011 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id p0S5r2rw022334 for ietf@ietf.org; Fri, 28 Jan 2011 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201101280553.p0S5r2rw022334@rotala.raleigh.ibm.com>
Date: Fri, 28 Jan 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-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, 28 Jan 2011 05:50:18 -0000

Total of 87 messages in the last 7 days.
 
script run at: Fri Jan 28 00:53:02 EST 2011
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.90% |    6 |  8.09% |    57034 | hallam@gmail.com
  5.75% |    5 |  7.75% |    54689 | evnikita2@gmail.com
  4.60% |    4 |  6.95% |    49016 | lars.eggert@nokia.com
  5.75% |    5 |  4.02% |    28367 | tme@americafree.tv
  4.60% |    4 |  3.26% |    22998 | julian.reschke@gmx.de
  3.45% |    3 |  3.05% |    21503 | daedulus@btconnect.com
  3.45% |    3 |  3.04% |    21426 | ted.ietf@gmail.com
  2.30% |    2 |  4.15% |    29237 | stpeter@stpeter.im
  2.30% |    2 |  3.47% |    24465 | ron.even.tlv@gmail.com
  2.30% |    2 |  2.50% |    17626 | ned+ietf@mauve.mrochek.com
  1.15% |    1 |  3.49% |    24586 | sginoza@amsl.com
  2.30% |    2 |  1.99% |    14010 | marka@isc.org
  2.30% |    2 |  1.94% |    13661 | magnus.westerlund@ericsson.com
  2.30% |    2 |  1.91% |    13449 | sm@resistor.net
  2.30% |    2 |  1.78% |    12550 | dworley@avaya.com
  2.30% |    2 |  1.70% |    12008 | john-ietf@jck.com
  1.15% |    1 |  2.60% |    18370 | yaakov_s@rad.com
  2.30% |    2 |  1.40% |     9876 | mail@sabahattin-gucukoglu.com
  2.30% |    2 |  1.37% |     9666 | mrex@sap.com
  1.15% |    1 |  2.11% |    14914 | even.roni@huawei.com
  1.15% |    1 |  1.84% |    12963 | fluffy@cisco.com
  1.15% |    1 |  1.59% |    11238 | michal@krsek.cz
  1.15% |    1 |  1.50% |    10569 | olaf@nlnetlabs.nl
  1.15% |    1 |  1.45% |    10257 | danny.cohen@oracle.com
  1.15% |    1 |  1.43% |    10063 | tena@huawei.com
  1.15% |    1 |  1.32% |     9282 | roman.arcea@orange.md
  1.15% |    1 |  1.30% |     9162 | clint.chaplin@gmail.com
  1.15% |    1 |  1.25% |     8791 | tony@att.com
  1.15% |    1 |  1.17% |     8222 | tglassey@earthlink.net
  1.15% |    1 |  1.11% |     7829 | mary.ietf.barnes@gmail.com
  1.15% |    1 |  1.08% |     7602 | gonzalo.camarillo@ericsson.com
  1.15% |    1 |  1.06% |     7470 | dougb@dougbarton.us
  1.15% |    1 |  1.05% |     7395 | narten@us.ibm.com
  1.15% |    1 |  1.01% |     7131 | iesg@ietf.org
  1.15% |    1 |  1.01% |     7127 | d3e3e3@gmail.com
  1.15% |    1 |  0.98% |     6947 | bob.hinden@gmail.com
  1.15% |    1 |  0.87% |     6105 | joelja@bogus.com
  1.15% |    1 |  0.86% |     6094 | michelle.cotton@icann.org
  1.15% |    1 |  0.85% |     6029 | huubatwork@gmail.com
  1.15% |    1 |  0.84% |     5954 | bzbarsky@mit.edu
  1.15% |    1 |  0.81% |     5701 | sob@harvard.edu
  1.15% |    1 |  0.80% |     5664 | rja.lists@gmail.com
  1.15% |    1 |  0.79% |     5549 | brian.e.carpenter@gmail.com
  1.15% |    1 |  0.78% |     5501 | touch@isi.edu
  1.15% |    1 |  0.76% |     5336 | huitema@microsoft.com
  1.15% |    1 |  0.74% |     5243 | jmh@joelhalpern.com
  1.15% |    1 |  0.73% |     5141 | cabo@tzi.org
  1.15% |    1 |  0.72% |     5050 | bertietf@bwijnen.net
  1.15% |    1 |  0.71% |     5035 | paul.hoffman@vpnc.org
  1.15% |    1 |  0.70% |     4916 | dhc2@dcrocker.net
  1.15% |    1 |  0.62% |     4402 | housley@vigilsec.com
  1.15% |    1 |  0.59% |     4136 | ole@cisco.com
  1.15% |    1 |  0.57% |     4026 | randy@psg.com
  1.15% |    1 |  0.56% |     3929 | joao@bondis.org
--------+------+--------+----------+------------------------
100.00% |   87 |100.00% |   705310 | Total

From mra@pobox.com  Thu Jan 27 23:12:23 2011
Return-Path: <mra@pobox.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 596F83A6AF2 for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 23:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 fK-BD2AQSL6S for <ietf@core3.amsl.com>; Thu, 27 Jan 2011 23:12:12 -0800 (PST)
Received: from sasl.smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by core3.amsl.com (Postfix) with ESMTP id 35A1B3A6AEA for <ietf@ietf.org>; Thu, 27 Jan 2011 23:12:08 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 62E4717A8 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:15:13 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; s=sasl; bh=RKmpVXjTAYiQ UtENrZ9Ijp2rk48=; b=FWlITFalg0vqqBS7qCDBM873t2uu/QVQPxVYu8/4QWT6 G4LLUGvU7PeTSQWM9wF+sHd85C70eUnE7V9qItLIcIFXINiOu0SIYS/GHHKnT3kH 8Akt3oHX6EDm7HeJUhQt9uY7XcfKHp/t4yrpd1CRSVyoLrflPRd3hr/ukGt87PM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; q=dns; s=sasl; b=Bw5B5L iIDRTyKBtUThjlY3KXro58wiadYfXGLb7hCH7iDx+X1WAfdcswnn9x1gEeaL38TE 70Hv0nLSkmePXUB56JnJ/d2AHb+dbTa479q/nnLDqjaBaZPyHBBUChL81m4+fC9C o4H0SHp0dEaYPySA7QEVItJGzht7NWCMXGI14=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 5FA1317A7 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:15:13 -0500 (EST)
Received: from mail-yx0-f172.google.com (unknown [209.85.213.172]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by b-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 2D0A317A6 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:15:13 -0500 (EST)
Received: by yxt33 with SMTP id 33so1074060yxt.31 for <ietf@ietf.org>; Thu, 27 Jan 2011 23:15:12 -0800 (PST)
Received: by 10.236.102.179 with SMTP id d39mr4347154yhg.48.1296198895665; Thu, 27 Jan 2011 23:14:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.147.168.3 with HTTP; Thu, 27 Jan 2011 23:14:35 -0800 (PST)
In-Reply-To: <201101280230.p0S2UhrM006665@fs4113.wdf.sap.corp>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <201101280230.p0S2UhrM006665@fs4113.wdf.sap.corp>
From: Mark Atwood <mra@pobox.com>
Date: Thu, 27 Jan 2011 23:14:35 -0800
Message-ID: <AANLkTi=aBt=e6SzQNOXa_+J18_qM-MEkD-TjrfdXFW6N@mail.gmail.com>
Subject: Re: draft-housley-two-maturity-levels
To: mrex@sap.com, "Scott O. Bradner" <sob@harvard.edu>, ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Pobox-Relay-ID: 5960E94C-2AAE-11E0-918C-D3BDF791CF9A-82717895!b-pb-sasl-quonix.pobox.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: Fri, 28 Jan 2011 07:12:23 -0000

This post would be much less confusing if you would name names, cite
examples, and point fingers.

> The reason why so many documents are at proposed is that they're
> often collections of bloat (limited-use features with an aggresive
> requirements level) from various interest groups that is
> not strictly necessary for a protocol to be useful, and sometimes
> used only by a minority.
>
> Normally, for progression from Proposed to Draft,
>
> =C2=A0 - some of the MUSTs would have to be changed to SHOULDs,
> =C2=A0 - some of the SHOULDs would have to be changed to MAYs,
> =C2=A0 - some parts might better be moved to seperate, optional
> =C2=A0 =C2=A0 extensions documents
>
> But the particular interest groups would rather have the document
> remain at Proposed than seeing any of the requirements level of
> those particular features they're interested in, to come out lowered,
> or see features removed from the base protocol and into a
> seperate extensions document.
>
>
> This is one of the reasons why there is a constant stream of new
> authentication protocols.
>
>
> -Martin
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From john@jlc.net  Fri Jan 28 01:07:57 2011
Return-Path: <john@jlc.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 122223A6B00 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 01:07:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.379
X-Spam-Level: 
X-Spam-Status: No, score=-106.379 tagged_above=-999 required=5 tests=[AWL=0.220, 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 tNBA5AC2txIo for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 01:07:55 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by core3.amsl.com (Postfix) with ESMTP id B23AA3A6959 for <ietf@ietf.org>; Fri, 28 Jan 2011 01:07:55 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id AEC1233C6C; Fri, 28 Jan 2011 04:11:00 -0500 (EST)
Date: Fri, 28 Jan 2011 04:11:00 -0500
From: John Leslie <john@jlc.net>
To: Mark Atwood <mra@pobox.com>
Subject: Re: draft-housley-two-maturity-levels
Message-ID: <20110128091100.GD68297@verdi>
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <201101280230.p0S2UhrM006665@fs4113.wdf.sap.corp> <AANLkTi=aBt=e6SzQNOXa_+J18_qM-MEkD-TjrfdXFW6N@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTi=aBt=e6SzQNOXa_+J18_qM-MEkD-TjrfdXFW6N@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Cc: "Scott O. Bradner" <sob@harvard.edu>, 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, 28 Jan 2011 09:07:57 -0000

Mark Atwood <mra@pobox.com> wrote:
> 
> This post would be much less confusing if you would name names, cite
> examples, and point fingers.

   No, it wouldn't.

   We don't need a flame-war over which features of which protocols
would have to go away under a strict reading of RFC 2026 in order to
advance.

   The point is clear enough: that features that find their way into
Proposed Standards have constituencies, and that pulling them out is
too painful for most WGs to tackle.

> [Martin Rex <mrex@sap.com> wrote:] 
>
>> The reason why so many documents are at proposed is that they're
>> often collections of bloat (limited-use features with an aggresive
>> requirements level) from various interest groups that is
>> not strictly necessary for a protocol to be useful, and sometimes
>> used only by a minority.

   Thank you, Martin!

   This brings us closer to the actual problem.

>> Normally, for progression from Proposed to Draft,
>>
>> - some of the MUSTs would have to be changed to SHOULDs,
>> - some of the SHOULDs would have to be changed to MAYs,
>> - some parts might better be moved to seperate, optional
>>   extensions documents

   I've been there, done that, got the T-shirt. Some pretty dreadful
MUSTs remain because of constituencies. "Consensus" is reached only
by exhaustion.

   Often we end up leaving stuff which can reasonably be called "bloat"
(though that's not how I would describe it) because we can't reach
agreement that we can patch-in a better way without "recycling at
Proposed".

   The whole process is exhausting. More often than not, folks give up.

>> But the particular interest groups would rather have the document
>> remain at Proposed than seeing any of the requirements level of
>> those particular features they're interested in, to come out lowered,
>> or see features removed from the base protocol and into a
>> seperate extensions document.

   Remaining at Proposed just doesn't seem that bad after you've been
through the wringer a few times. (It's not that people start out
wanting to prevent progression; it's that consensus on needed changes
is too hard to reach.)

   Add to this that chartering a WG to advance from Proposed to Draft
never seems to happen (what AD would volunteer to endure this _again_?)
and we have the wrangling which should be contained in a WG arising
during IETF LastCall: few document authors will persist long enough.

   I refuse to argue how many levels there should be -- though I'd
be happy to work within the old consensus for three. What needs work
(assuming we aim for more than one) is how to get there from here!
I have some ideas; but the time just doesn't seem ripe to discuss them.

--
John Leslie <john@jlc.net>

From evnikita2@gmail.com  Fri Jan 28 02:30:40 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 AB7CB3A63D2 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 02:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.238
X-Spam-Level: 
X-Spam-Status: No, score=-2.238 tagged_above=-999 required=5 tests=[AWL=-0.600, 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 M5Au1DX-F9vX for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 02:30:39 -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 6E56B3A6359 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:30:39 -0800 (PST)
Received: by fxm9 with SMTP id 9so3464392fxm.31 for <ietf@ietf.org>; Fri, 28 Jan 2011 02:33:44 -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:content-type; bh=bjDc4CVsfzTShSfD8CHqCatjIO3GdsG5C7pd3OrWrSU=; b=ZOxH3iAgBa5NcQD1v7T7YO9Lm6z1WLA8pJ2U0FvCj1LhuR1Waq3QG97DaE3NuD+Jz9 hw278+lSnV0UETkD9huvlU+p7MDiBx0nAD3Wh2F+wRWoJak72ddYvSG055s81O0cJHTq BK9GHF1l1RIUWAR42cWVIDpSDVXKyXpFDZo9o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :content-type; b=k6EasmtK3Rv+gBLWRhace3HZ4IsJczxHmbB55h/DOMzZitDBCFvB7CotwyZL8UJ4Mw W+iZrimv9CJJQeI0hJnFMI25r7XJvDdkmevPRWd2rbQGKElDyQq7d5ilDV9qg6TwBMTx daOFEp6QXozTmkQ65KBeTEJiLdbz8VftqSbeM=
Received: by 10.223.85.204 with SMTP id p12mr2140501fal.146.1296210824851; Fri, 28 Jan 2011 02:33:44 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id y1sm6355713fak.15.2011.01.28.02.33.43 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Jan 2011 02:33:44 -0800 (PST)
Message-ID: <4D429B9F.5010009@gmail.com>
Date: Fri, 28 Jan 2011 12:34:07 +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>
Subject: Request for Review - draft-yevstifeyev-genarea-historic-01
Content-Type: multipart/alternative; boundary="------------020105020606000701060309"
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, 28 Jan 2011 10:30:40 -0000

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

Hello all,

I'm writing to request the review of 
draft-yevstifeyev-genarea-historic-01, that could be found here: 
http://www.ietf.org/id/draft-yevstifeyev-genarea-historic-01.txt

The purpose of this document is to clarify the use of Historic status, 
mention procedures for reclassification and republication of RFCs to 
this status and discuss other issues connected with historic RFCs, such 
as references to Historic documents, etc.

This message is sent to IETF Discussion list since there are no other 
appropriate mailing list to discuss this draft.

Please be careful while looking the HTMLized version of the document, 
the may refer to -00 version of the draft.  I am asking for comments on 
-01 version of the document.

Thank you for your time,
Mykyta Yevstifeyev

--------------020105020606000701060309
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 all,<br>
        <br>
        I'm writing to request the review of
        draft-yevstifeyev-genarea-historic-01, that could be found here:
        <a class="moz-txt-link-freetext" href="http://www.ietf.org/id/draft-yevstifeyev-genarea-historic-01.txt">http://www.ietf.org/id/draft-yevstifeyev-genarea-historic-01.txt</a><br>
        <br>
        The purpose of this document is to clarify the use of Historic
        status, mention procedures for reclassification and
        republication of RFCs to this status and discuss other issues
        connected with historic RFCs, such as references to Historic
        documents, etc.<br>
        <br>
        This message is sent to IETF Discussion list since there are no
        other appropriate mailing list to discuss this draft.<br>
        <br>
        Please be careful while looking the HTMLized version of the
        document, the may refer to -00 version of the draft.  I am
        asking for comments on -01 version of the document.<br>
        <br>
        Thank you for your time, <br>
        Mykyta Yevstifeyev<br>
      </big></font>
  </body>
</html>

--------------020105020606000701060309--

From magnus.westerlund@ericsson.com  Fri Jan 28 05:14:11 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 236393A67F5; Fri, 28 Jan 2011 05:14:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.481
X-Spam-Level: 
X-Spam-Status: No, score=-106.481 tagged_above=-999 required=5 tests=[AWL=0.118, 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 9wVMJgr8QOwz; Fri, 28 Jan 2011 05:14:10 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id D0E5F3A67F1; Fri, 28 Jan 2011 05:14:09 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-41-4d42c1dbf57f
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 98.B6.23694.BD1C24D4; Fri, 28 Jan 2011 14:17:15 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.2.234.1; Fri, 28 Jan 2011 14:17:06 +0100
Message-ID: <4D42C1D2.8080406@ericsson.com>
Date: Fri, 28 Jan 2011 14:17:06 +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: ietf <ietf@ietf.org>, Stuart Cheshire <cheshire@apple.com>,  marc@apple.com, TSV Dir <tsv-dir@ietf.org>
Subject: Re: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
References: <20110117230048.26192.84056.idtracker@localhost>
In-Reply-To: <20110117230048.26192.84056.idtracker@localhost>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
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: Fri, 28 Jan 2011 13:14:11 -0000

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.

My comments on the document are:

1. Section 3. I wonder if "Standards Action" is the most appropriate
rule here. My concern with this is that any other body must perform the
work in the IETF and give IETF full change control over this proposal.
This might intended, but I wonder if it is the most appropriate policy.
My suggestion would be to allow IESG approval as a policy also to give
some freedom in the strange cases. I do think an IETF standards RFC is
the preferred way for doing this, but it might be overly restrictive.

2. Section 6.
Why doesn't this document populate this registry with some initial
values. The document it self already lists some of these. So why not
include the ones and a note that they are legacy and does not come with
the new required consideration section?

Best Regards

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 doug@ewellic.org  Fri Jan 28 06:54:50 2011
Return-Path: <doug@ewellic.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 3C5E93A687B for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 06:54:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzlWsa4XgbZ3 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 06:54:49 -0800 (PST)
Received: from smtpoutwbe09.prod.mesa1.secureserver.net (smtpoutwbe09.prod.mesa1.secureserver.net [208.109.78.21]) by core3.amsl.com (Postfix) with SMTP id 249813A6856 for <ietf@ietf.org>; Fri, 28 Jan 2011 06:54:48 -0800 (PST)
Received: (qmail 16442 invoked from network); 28 Jan 2011 14:57:54 -0000
Received: from unknown (HELO localhost) (72.167.218.130) by smtpoutwbe09.prod.mesa1.secureserver.net with SMTP; 28 Jan 2011 14:57:53 -0000
Received: (qmail 581 invoked by uid 99); 28 Jan 2011 14:57:53 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.190
User-Agent: Web-Based Email 5.3.08
Message-Id: <20110128075753.665a7a7059d7ee80bb4d670165c8327d.30b3acba39.wbe@email03.secureserver.net>
From: "Doug Ewell" <doug@ewellic.org>
To: ietf@ietf.org
Subject: Re: Request for Review - draft-yevstifeyev-genarea-historic-01
Date: Fri, 28 Jan 2011 07:57:53 -0700
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, 28 Jan 2011 14:54:50 -0000

Mykyta Yevstifeyev <evnikita2 at gmail dot com> wrote:

> I'm writing to request the review of
> draft-yevstifeyev-genarea-historic-01, that could be found here:
> http://www.ietf.org/id/draft-yevstifeyev-genarea-historic-01.txt

The document says:

2.1. Criteria for Historic RFCs

   If the RFC is replaced by another one, it SHALL be considered to be
   superseded.

   The RFC SHALL be considered to be obsolete if it meets the following
   criteria:

     a. It has been publicly available for at least 7 years;

     b. During this period of time the technology, described in this RFC
     has not been seen used in the Internet; or

     c. The technology defined in this RFC is not possible or is not
     advised to be used in the Internet because of its security issues,
     impact on its performance or any other reason.

I'd like to see some kind of guideline that the RFC should not be
considered obsolete solely because of security or performance concerns
in some particular, specific context.  For example, the fact that
vanilla FTP is not sufficiently secure for use in some applications
where high security is paramount is not a rationale for deprecating FTP
in all applications.

The phrase "or any other reason" seems unnecessarily open-ended, and may
invite abuse.

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =C2=AD



From tena@huawei.com  Wed Jan 26 14:47:21 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 88D563A69EB; Wed, 26 Jan 2011 14:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.251
X-Spam-Level: 
X-Spam-Status: No, score=-106.251 tagged_above=-999 required=5 tests=[AWL=0.348, 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 0MdE4+9WBvCZ; Wed, 26 Jan 2011 14:47:20 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 7F6803A69DD; Wed, 26 Jan 2011 14:47:20 -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 <0LFN00J8EJFXKY@usaga02-in.huawei.com>; Wed, 26 Jan 2011 14:50:21 -0800 (PST)
Received: from TingZousc1 ([10.212.246.230]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFN00M4CJFQNG@usaga02-in.huawei.com>; Wed, 26 Jan 2011 14:50:21 -0800 (PST)
Date: Wed, 26 Jan 2011 14:50:18 -0800
From: Tina Tsou <tena@huawei.com>
Subject: RE: Review of draft-ymbk-aplusp-08
In-reply-to: <m2vd1cr6ts.wl%randy@psg.com>
To: 'Randy Bush' <randy@psg.com>
Message-id: <001701cbbdab$6b3ce000$41b6a000$@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: Acu82qXBYG9862qhTTOT3oPTAW8HiQA0AorA
References: <01a201cbbcd7$197946c0$4c6bd440$@com> <m2vd1cr6ts.wl%randy@psg.com>
X-Mailman-Approved-At: Fri, 28 Jan 2011 07:44:23 -0800
Cc: ops-dir@ietf.org, ietf@ietf.org, iesg@ietf.org, draft-ymbk-aplusp@tools.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: Wed, 26 Jan 2011 22:47:21 -0000

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


-----Original Message-----
From: Randy Bush [mailto:randy@psg.com] 
Sent: Tuesday, January 25, 2011 1:51 PM
To: Tina Tsou
Cc: ops-dir@ietf.org; secdir@ietf.org; draft-ymbk-aplusp@tools.ietf.org;
iesg@ietf.org; ietf@ietf.org
Subject: Re: Review of draft-ymbk-aplusp-08

> Operations directorate and Security directorate reviews are solicited
> primarily to help the area directors improve their efficiency,
particularly
> when preparing for IESG telechats, and allowing them to focus on documents
> requiring their attention and spend less time on the trouble-free ones.

and which are you?  can't be ops, as you are a vendor.  so security?
but we already received the security review.
[Tina:
I know the author is my friend Randy, so I have to be very careful ;-)

I'm a member and also the secretary of Operations directorate.
Here is the wiki page for the Operations directorate.
http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates
You can see many of us do not have the affiliation of operators.
I did the additional review besides the allocated member's review.

I'm also a member of Security directorate.
I did the additional review besides the allocated member's review.

Hope it clarifies.
]

but thanks for the review anyway.

randy, a bit confused


From tena@huawei.com  Wed Jan 26 15:12:42 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 554F83A6A00; Wed, 26 Jan 2011 15:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.264
X-Spam-Level: 
X-Spam-Status: No, score=-106.264 tagged_above=-999 required=5 tests=[AWL=0.335, 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 nvU+R-ATS0gl; Wed, 26 Jan 2011 15:12:41 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 657373A69FD; Wed, 26 Jan 2011 15:12:41 -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 <0LFN00JJIKM6KY@usaga02-in.huawei.com>; Wed, 26 Jan 2011 15:15:43 -0800 (PST)
Received: from TingZousc1 ([10.212.246.230]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFN00MXCKM1NG@usaga02-in.huawei.com>; Wed, 26 Jan 2011 15:15:42 -0800 (PST)
Date: Wed, 26 Jan 2011 15:15:41 -0800
From: Tina Tsou <tena@huawei.com>
Subject: Review of draft-arkko-dual-stack-extra-lite-03
To: ops-dir@ietf.org
Message-id: <004401cbbdae$f6bf1c30$e43d5490$@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: Acu9rvMrHjHQeojPR8u1Zv294pvWgg==
X-Mailman-Approved-At: Fri, 28 Jan 2011 07:44:23 -0800
Cc: 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: Wed, 26 Jan 2011 23:12:42 -0000

Hi,
I reviewed draft-arkko-dual-stack-extra-lite-03.
This document proposed using layer 2 identifier to make address translation.
Is this application scenario compatible with the existing technologies,
e.g., DS-Lite, GI DS-Lite and 6RD? 
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. 
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?   


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




From randy@psg.com  Wed Jan 26 15:31:05 2011
Return-Path: <randy@psg.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 E41013A69FB; Wed, 26 Jan 2011 15:31:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGu5zEWhrbXs; Wed, 26 Jan 2011 15:31:05 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id C4A963A69FA; Wed, 26 Jan 2011 15:31:04 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PiEsD-000LkQ-Ow; Wed, 26 Jan 2011 23:34:01 +0000
Date: Thu, 27 Jan 2011 08:34:06 +0900
Message-ID: <m24o8vp7dd.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina Tsou <tena@huawei.com>
Subject: Re: Review of draft-ymbk-aplusp-08
In-Reply-To: <001701cbbdab$6b3ce000$41b6a000$@com>
References: <01a201cbbcd7$197946c0$4c6bd440$@com> <m2vd1cr6ts.wl%randy@psg.com> <001701cbbdab$6b3ce000$41b6a000$@com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Fri, 28 Jan 2011 07:44:23 -0800
Cc: ops-dir@ietf.org, ietf@ietf.org, iesg@ietf.org, draft-ymbk-aplusp@tools.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: Wed, 26 Jan 2011 23:31:06 -0000

> I'm a member and also the secretary of Operations directorate.

the ops dir is a joke.  does reviews for an area director who does not
do his/her own?

there is an ops cabal that meets at ietf and has ML etc.  all actual ops
except for one guest, the actual ops director, ron.

> http://trac.tools.ietf.org/area/ops/trac/wiki/Directorates
> You can see many of us do not have the affiliation of operators.

welcome to the ietf

> I'm also a member of Security directorate.

must be fun.

randy

From sm@resistor.net  Fri Jan 28 07:55:27 2011
Return-Path: <sm@resistor.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 8EA5E3A6872 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 07:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.608
X-Spam-Level: 
X-Spam-Status: No, score=-103.608 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 AMLzZzNAoDZW for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 07:55:24 -0800 (PST)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id AA13F3A67A8 for <ietf@ietf.org>; Fri, 28 Jan 2011 07:55:24 -0800 (PST)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id p0SFvTN4025131 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 28 Jan 2011 07:58:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1296230309; x=1296316709; bh=dxW17FYWCXMItu0cgNMlFSZr/maraSR7Et7VEUh6jwA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=x0BCy0J0l9mONd+4i3pyHsRZGvIecLZrPt1eYyAr/JhplLrf6XWs0viq+ExD5coQM p9b+wCmmFt9auv0laDkXdqwFpcM5cwkvVx4uwILkzNBNPJ3Vdb1yldqqid+lXLEu3R TaSOBYyumxuCmrZZe/S2Lq9RLh0Rrzq4CVTwH8O8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1296230309; x=1296316709; bh=dxW17FYWCXMItu0cgNMlFSZr/maraSR7Et7VEUh6jwA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=o5ubKs+BayqhOZaa+qS4axLQS0xzE4kBiloqNUVyzm4nK+ZVXik8ApCVe1DLPC/yx DzZA9UcF6nes1FCvKJq3NzyEeC0Nf9vPjcnA8HEBNAUe5KlvjZWIWwnrP3fnHg0lCF fjoFMNRF8IslVsCRy49tkAD7D4o/+aMMZCd5inrA=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=Kil9QCZpMv3uhFhF88le1lE9buSyLLg1u6hVocbxnSI6htU8jai+BhzrrD4NhRq6V ZJIDfMNxeIVuEmFqX7yl3jitpx4ptae3ONZpTv8UHFd7E80hPcRiV2GSuNvbd2fx9vl 64MaHPERkVMOAPhELKbIA8a4ZVG9QJM1ySlMHq0=
Message-Id: <6.2.5.6.2.20110128055818.0d12bb18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 28 Jan 2011 07:15:50 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
In-Reply-To: <20110117230048.26192.84056.idtracker@localhost>
References: <20110117230048.26192.84056.idtracker@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 28 Jan 2011 15:55:27 -0000

At 15:00 17-01-11, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Special-Use Domain Names'
>   <draft-cheshire-dnsext-special-names-01.txt> as a Proposed Standard
>
>    Abstract
>
>    This document describes what it means to say that a DNS name is
>    reserved for special use, when reserving such a name is appropriate,
>    and the procedure for doing so.
>
>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

The intended status of draft-cheshire-dnsext-special-names-01 is 
Standards Track.  BCP would have been a better fit is the aim of this 
draft is to create a registry and a procedure for reserved DNS names.

In Section 1:

   'For example, IPv4 addresses 224.0.0.0 to 239.255.255.255 are
    multicast addresses [RFC2606], with 224.0.0.1 being the "all hosts"'

I suggest dropping that reference as example refers to IPv4 addresses 
discussed in RFC 5735; RFC 2606 is about Reserved Top Level DNS Names.

 From Section 2:

   "Similarly, if a domain name has special properties that affect the
    way hardware and software implementations handle the name, which
    apply universally regardless of what network the implementation may
    be connected to, then that may be a candidate for having the IETF
    declare the name to be a Special-Use Domain Name and specify what
    special treatment implementations should give to that name."

That sounds like a good argument for the IETF declare a domain name 
as "Special Use".  Does ".local" qualify for registration 
(draft-cheshire-dnsext-multicastdns-13)?

Are domain names as defined under this proposal to be considered as 
Internet protocol parameters?

 From Section 3:

   "If it is determined that special handling of a name is required in
    order to implement some desired new functionality, then an IETF
    "Standards Action" RFC [RFC5226] needs to be published describing the
    new functionality ..."

In other words, if an author can get a Proposed Standard through the 
IETF process, he or she can get a registration for a Special-Use Domain Name.

In Section 7:

   'How should DNS Registrars treat requests to register this reserved
    domain name? Should such requests be denied? Should such requests
    be allowed, but only to a specially-designated entity? (For
    example, the name "www.example.org" is reserved for documentation
    examples and is not available for registration; however, the name
    is in fact registered; and there is even a web site at that name,
    which states circularly that the name is reserved for use in
    documentation and cannot be registered!)'

That would be:

    Domain Name: EXAMPLE.COM
    Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
    Whois Server: whois.iana.org
    Referral URL: http://res-dom.iana.org
    Name Server: A.IANA-SERVERS.NET
    Name Server: B.IANA-SERVERS.NET
    Status: clientDeleteProhibited
    Status: clientTransferProhibited
    Status: clientUpdateProhibited
    Updated Date: 26-mar-2004
    Creation Date: 14-aug-1995
    Expiration Date: 13-aug-2011

By the way, res-dom.iana.org is not responding on port 80.

In the IANA Considerations Section, 
draft-cheshire-dnsext-special-names creates a registry of Special-Use 
Domain Names.  It is customary to populate a new registry with legacy 
entries such as the domain names mentioned in RFC 2606.

Regards,
-sm 


From daedulus@btconnect.com  Fri Jan 28 08:03:52 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 2C9FE3A68F7; Fri, 28 Jan 2011 08:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_15=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 Wr2e8LbqkbU5; Fri, 28 Jan 2011 08:03:51 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr07.btconnect.com [213.123.20.125]) by core3.amsl.com (Postfix) with ESMTP id D338E3A68CC; Fri, 28 Jan 2011 08:03:50 -0800 (PST)
Received: from host86-134-204-119.range86-134.btcentralplus.com (HELO pc6) ([86.134.204.119]) by c2bthomr07.btconnect.com with SMTP id BSZ42142; Fri, 28 Jan 2011 16:06:52 +0000 (GMT)
Message-ID: <007501cbbefc$7a858d80$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Lars Eggert" <lars.eggert@nokia.com>
References: <20110118212603.5733.34489.idtracker@localhost><B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <00a401cbbe43$76e693e0$4001a8c0@gateway.2wire.net> <D8AE8A20-B6E6-4159-BBF0-20EC4A939623@nokia.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: Fri, 28 Jan 2011 16:02:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4D42E98E.01B1, actions=TAG
X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4D42E99D.004E,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>, 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: Fri, 28 Jan 2011 16:03:52 -0000

----- Original Message -----
From: "Lars Eggert" <lars.eggert@nokia.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "Cullen Jennings" <fluffy@cisco.com>; "IESG IESG" <iesg@ietf.org>; "IETF
discussion list" <ietf@ietf.org>
Sent: Thursday, January 27, 2011 7:11 PM

On 2011-1-27, at 18:58, t.petch wrote:
> And what happens when we have ProtocolX over SSH and ProtocolX over TLS?
>
> Must they share a port, with ProtocolX, which has been quietly using its
> assigned port for
> 20 years?

No. The expert reviewer can obviously assign a second port in that case (if
ProtocolX doesn't have a feature negotiation capability built in so that the
port could be shared.)

But we don't want to allocate multiple ports for the different security flavors
of *new* protocols. At least we want this to be the exception.

The expert team is (from what I hear) seeing frequent applications that look
like "Hi, we're company X and our foo protocol runs on TCP. We'd like a port for
that, and one for when we run foo over TLS."

</tp>
Right.  What I had not noticed, although I have read several versions of this
I-D, is that it says
a lot about new applications, and not much - if anything - about old.  I have
never been involved in
a new application, only with retrofitting security to old, TLS or SSH, and so my
views are coloured by
that.  The expectation of WGs seems to be to expect a new port when adding
either TLS or SSH
to something that has been happily chugging along for decades without it, and I
expect in future,
the same to apply when adding SSH or TLS support to a protocol with TLS or SSH
support
respectively, and would not want this I-D to make that much more difficult.

Is there any text about this, old protocol, situation, for I cannot see any?  Or
are we at the mercy
of the expert reviewer?

Tom Petch
</tp>

Lars=


From jabley@hopcount.ca  Fri Jan 28 08:53:43 2011
Return-Path: <jabley@hopcount.ca>
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 2DA293A67F4 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 08:53:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 2jaZ1KNbB3E7 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 08:53:42 -0800 (PST)
Received: from monster.hopcount.ca (monster.hopcount.ca [216.235.14.38]) by core3.amsl.com (Postfix) with ESMTP id 0A20C3A68D2 for <ietf@ietf.org>; Fri, 28 Jan 2011 08:53:42 -0800 (PST)
Received: from [199.212.90.21] (helo=dh21.r2.owls.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1Pirh1-000KXY-JN; Fri, 28 Jan 2011 17:01:04 +0000
Subject: Re: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6.2.5.6.2.20110128055818.0d12bb18@resistor.net>
Date: Fri, 28 Jan 2011 11:56:44 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <A157B368-6B06-4C92-8F7C-B0F303EFE34F@hopcount.ca>
References: <20110117230048.26192.84056.idtracker@localhost> <6.2.5.6.2.20110128055818.0d12bb18@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1082)
X-SA-Exim-Connect-IP: 199.212.90.21
X-SA-Exim-Mail-From: jabley@hopcount.ca
X-SA-Exim-Scanned: No (on monster.hopcount.ca); SAEximRunCond expanded to false
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, 28 Jan 2011 16:53:43 -0000

On 2011-01-28, at 10:15, SM wrote:

>   Domain Name: EXAMPLE.COM
>   Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
>   Whois Server: whois.iana.org
>   Referral URL: http://res-dom.iana.org
>   Name Server: A.IANA-SERVERS.NET
>   Name Server: B.IANA-SERVERS.NET
>   Status: clientDeleteProhibited
>   Status: clientTransferProhibited
>   Status: clientUpdateProhibited
>   Updated Date: 26-mar-2004
>   Creation Date: 14-aug-1995
>   Expiration Date: 13-aug-2011
> 
> By the way, res-dom.iana.org is not responding on port 80.

I will let the appropriate people know. Thanks for picking that up.


Joe

From fluffy@cisco.com  Fri Jan 28 09:43:37 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 610AA3A68D2; Fri, 28 Jan 2011 09:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.581
X-Spam-Level: 
X-Spam-Status: No, score=-110.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 jnV7lPa44ivD; Fri, 28 Jan 2011 09:43:36 -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 9285F3A68F8; Fri, 28 Jan 2011 09:43:36 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKePQk2rR7Hu/2dsb2JhbAClAHOfY5tVhU8EhRiHDw
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 28 Jan 2011 17:46:43 +0000
Received: from sjc-vpn5-2007.cisco.com (sjc-vpn5-2007.cisco.com [10.21.95.215]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0SHkgUr002935; Fri, 28 Jan 2011 17:46:42 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: <A44FD9FC-6017-4139-A1E1-81C59D5792DD@nokia.com>
Date: Fri, 28 Jan 2011 09:46:42 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F78C5467-8762-415C-A8B1-17F6D83108FC@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com> <D75A1EB1-B142-41D4-A270-FCA8DD81CB23@tzi.org> <A44FD9FC-6017-4139-A1E1-81C59D5792DD@nokia.com>
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.1082)
Cc: Carsten Bormann <cabo@tzi.org>, IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.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: Fri, 28 Jan 2011 17:43:37 -0000

On Jan 27, 2011, at 1:26 , Lars Eggert wrote:

> On 2011-1-27, at 11:20, Carsten Bormann wrote:
>> With UDP-based protocols, it is harder to do this.
>> Please look at section 7.3 of
>>=20
>> 	=
http://tools.ietf.org/html/draft-ietf-core-coap-04.html#section-7.3
>>=20
>> and tell us whether this is how you would like this to be handled for =
UDP-based protocols in the future.
>> If not, we may want to add to the guidance in the (tsvwg) draft.
>=20
> This looks like a totally reasonable way to to this in-band using a =
single port.

How is the COAP working stepping on top of TLS code points any different =
that the ITU-T stepping on MPLS code points?


From touch@isi.edu  Fri Jan 28 10:43:43 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 AA4073A67ED; Fri, 28 Jan 2011 10:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.215
X-Spam-Level: 
X-Spam-Status: No, score=-102.215 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, J_CHICKENPOX_15=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 EfBi1p+tycvF; Fri, 28 Jan 2011 10:43:43 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 0B1203A67D1; Fri, 28 Jan 2011 10:43:43 -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 p0SIkFta023471 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Fri, 28 Jan 2011 10:46:18 -0800 (PST)
Message-ID: <4D430EF7.9040700@isi.edu>
Date: Fri, 28 Jan 2011 10:46: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: "t.petch" <daedulus@btconnect.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
References: <20110118212603.5733.34489.idtracker@localhost><B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com>	<ECA80A72-4E72-44D2-B40E-C90D7197E8C5@nokia.com>	<00a401cbbe43$76e693e0$4001a8c0@gateway.2wire.net>	<D8AE8A20-B6E6-4159-BBF0-20EC4A939623@nokia.com> <007501cbbefc$7a858d80$4001a8c0@gateway.2wire.net>
In-Reply-To: <007501cbbefc$7a858d80$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>, 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: Fri, 28 Jan 2011 18:43:43 -0000

Hi, Tom,

On 1/28/2011 7:02 AM, t.petch wrote:
> Is there any text about this, old protocol, situation, for I cannot see any?  Or
> are we at the mercy
> of the expert reviewer?
>
> Tom Petch

See Sec 7.2:

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

and

    ...In particular, the principles form a goal that IANA strives
    to achieve for new applications (with exceptions as deemed
    appropriate, especially as for extensions to legacy services) as
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    follows:

Joe

From evnikita2@gmail.com  Fri Jan 28 11:33:39 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 9240B3A695D for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 11:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.938
X-Spam-Level: 
X-Spam-Status: No, score=-3.938 tagged_above=-999 required=5 tests=[AWL=-0.340, 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 fvneU1iQ8efz for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 11:33:38 -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 2B39B3A695C for <ietf@ietf.org>; Fri, 28 Jan 2011 11:33:38 -0800 (PST)
Received: by yie19 with SMTP id 19so1351114yie.31 for <ietf@ietf.org>; Fri, 28 Jan 2011 11:36:45 -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=Bu9W0W2rhb1dFqwvIkb5M0+hdM2syI9PURwSvEk0hGI=; b=kFmBcmqwQC4tMvaxl0S6w/b2hx7LEyJk8K8KQuOA9A6B+MPylqmAMT+8t1xdnqJviQ QArtbNgRZaXWJHUJFKKCJBbLGLOJPzRpzXgdh8anRaPaCEijy5kom7OX1X2IRb8t+FT6 PHvSWoRbI5/cbVF+4j3pA6xb9C3ga84NKwdTM=
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=AyM1/InzLgYjOAnMtXQbK/5pckpUcH5iHkKu2oXac8OhkY4gmcD0GvSWtF20kD4RJB 3Z87hk+of5f27HOETbqqcy0ryaI7xgV8WRIrRKnZuqvJUN32WVTYTOgVP6tSd2Oxvtq/ BfASYW/64twCab+6LZLg5aY1m8AciT4wShyoQ=
MIME-Version: 1.0
Received: by 10.150.91.17 with SMTP id o17mr1992792ybb.41.1296243404266; Fri, 28 Jan 2011 11:36:44 -0800 (PST)
Received: by 10.150.140.1 with HTTP; Fri, 28 Jan 2011 11:36:44 -0800 (PST)
In-Reply-To: <20110128075753.665a7a7059d7ee80bb4d670165c8327d.30b3acba39.wbe@email03.secureserver.net>
References: <20110128075753.665a7a7059d7ee80bb4d670165c8327d.30b3acba39.wbe@email03.secureserver.net>
Date: Fri, 28 Jan 2011 21:36:44 +0200
Message-ID: <AANLkTi=w1B1Op9Qbua=zFnQj3refWc_ZX1=aXr=gZUKP@mail.gmail.com>
Subject: Re: Request for Review - draft-yevstifeyev-genarea-historic-01
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Doug Ewell <doug@ewellic.org>
Content-Type: multipart/alternative; boundary=000e0cd47d2ea75c5c049aed2fa8
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, 28 Jan 2011 19:33:39 -0000

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

Doug,

2011/1/28 Doug Ewell <doug@ewellic.org>

> Mykyta Yevstifeyev <evnikita2 at gmail dot com> wrote:
>
> > I'm writing to request the review of
> > draft-yevstifeyev-genarea-historic-01, that could be found here:
> > http://www.ietf.org/id/draft-yevstifeyev-genarea-historic-01.txt
>
> The document says:
>
> 2.1. Criteria for Historic RFCs
>
>   If the RFC is replaced by another one, it SHALL be considered to be
>   superseded.
>
>   The RFC SHALL be considered to be obsolete if it meets the following
>   criteria:
>
>     a. It has been publicly available for at least 7 years;
>
>     b. During this period of time the technology, described in this RFC
>     has not been seen used in the Internet; or
>
>     c. The technology defined in this RFC is not possible or is not
>     advised to be used in the Internet because of its security issues,
>     impact on its performance or any other reason.
>
> I'd like to see some kind of guideline that the RFC should not be
> considered obsolete solely because of security or performance concerns
> in some particular, specific context.  For example, the fact that
> vanilla FTP is not sufficiently secure for use in some applications
> where high security is paramount is not a rationale for deprecating FTP
> in all applications.
>
In the case I mentioned as c the key words are 'is not possible or is not
advised to be used in the Internet' but not what you mentioned.  The phrase
'or any other reason' is put because there is no possibility to put the
exhaustive list of such purposes.   Anyway, what would you like to propose
here?

Mykyta Yevstifeyev

>
> The phrase "or any other reason" seems unnecessarily open-ended, and may
> invite abuse.
>
> --
> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Doug,<br><br><div class=3D"gmail_quote">2011/1/28 Doug Ewell <span dir=3D"l=
tr">&lt;<a href=3D"mailto:doug@ewellic.org">doug@ewellic.org</a>&gt;</span>=
<br><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; b=
order-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Mykyta Yevstifeyev &lt;evnikita2 at gmail dot com&gt; wrote:<br>
<br>
&gt; I&#39;m writing to request the review of<br>
&gt; draft-yevstifeyev-genarea-historic-01, that could be found here:<br>
&gt; <a href=3D"http://www.ietf.org/id/draft-yevstifeyev-genarea-historic-0=
1.txt" target=3D"_blank">http://www.ietf.org/id/draft-yevstifeyev-genarea-h=
istoric-01.txt</a><br>
<br>
The document says:<br>
<br>
2.1. Criteria for Historic RFCs<br>
<br>
 =A0 If the RFC is replaced by another one, it SHALL be considered to be<br=
>
 =A0 superseded.<br>
<br>
 =A0 The RFC SHALL be considered to be obsolete if it meets the following<b=
r>
 =A0 criteria:<br>
<br>
 =A0 =A0 a. It has been publicly available for at least 7 years;<br>
<br>
 =A0 =A0 b. During this period of time the technology, described in this RF=
C<br>
 =A0 =A0 has not been seen used in the Internet; or<br>
<br>
 =A0 =A0 c. The technology defined in this RFC is not possible or is not<br=
>
 =A0 =A0 advised to be used in the Internet because of its security issues,=
<br>
 =A0 =A0 impact on its performance or any other reason.<br>
<br>
I&#39;d like to see some kind of guideline that the RFC should not be<br>
considered obsolete solely because of security or performance concerns<br>
in some particular, specific context. =A0For example, the fact that<br>
vanilla FTP is not sufficiently secure for use in some applications<br>
where high security is paramount is not a rationale for deprecating FTP<br>
in all applications.<br></blockquote><div>In the case I mentioned as c the =
key words are &#39;is not possible or is not advised to be used in the Inte=
rnet&#39; but not what you mentioned.=A0 The phrase &#39;or any other reaso=
n&#39; is put because there is no possibility to put the exhaustive list of=
 such purposes.=A0=A0 Anyway, what would you like to propose here?<br>
<br>Mykyta Yevstifeyev<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); paddi=
ng-left: 1ex;">
<br>
The phrase &quot;or any other reason&quot; seems unnecessarily open-ended, =
and may<br>
invite abuse.<br>
<br>
--<br>
Doug Ewell | Thornton, Colorado, USA | <a href=3D"http://www.ewellic.org" t=
arget=3D"_blank">http://www.ewellic.org</a><br>
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =AD<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>

--000e0cd47d2ea75c5c049aed2fa8--

From evnikita2@gmail.com  Fri Jan 28 11:41:23 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 8503A3A68BD; Fri, 28 Jan 2011 11:41:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.929
X-Spam-Level: 
X-Spam-Status: No, score=-3.929 tagged_above=-999 required=5 tests=[AWL=-0.331, 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 mRufBe1xbG0G; Fri, 28 Jan 2011 11:41:22 -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 3D3EA3A680F; Fri, 28 Jan 2011 11:41:22 -0800 (PST)
Received: by yxt33 with SMTP id 33so1357647yxt.31 for <multiple recipients>; Fri, 28 Jan 2011 11:44: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=DCI8V9OHEy4kSKvEKulBlXsgD001Wxte66lgAUIObGA=; b=NvCcNGamODeH20JyC29feFIGjNX7KginBMuSyD1ovGxnUL1gHJAdnKzFxBwy2NYPLv E58cQtWEdN0OHpDgy+ksEiShC9b7FTBN6FvY77F+jYHY+kah472XVSuQFR66ZaLxa6iA V9ISVx0yh9UOLm3Bb7lokaVVqwlmGprsuFuBU=
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=EaVgvHIBs/xcmlLfnXKe2vWEOwu70vkQlCSzF8oue9i0utRK7IU0DLeZbO80qMTEZF 7A0QqSfhZeJ/AcN75v6AdGuSOJjMGVHxr2/nXvNLO+FjZ0fCmUgzlw+4/XX14yMHI0x/ olIohyXLa/SpsN9X6wmJnI8B79bx3beLENub8=
MIME-Version: 1.0
Received: by 10.150.91.10 with SMTP id o10mr4615206ybb.440.1296243868882; Fri, 28 Jan 2011 11:44:28 -0800 (PST)
Received: by 10.150.140.1 with HTTP; Fri, 28 Jan 2011 11:44:28 -0800 (PST)
In-Reply-To: <4D42C1D2.8080406@ericsson.com>
References: <20110117230048.26192.84056.idtracker@localhost> <4D42C1D2.8080406@ericsson.com>
Date: Fri, 28 Jan 2011 21:44:28 +0200
Message-ID: <AANLkTim_Bgft2wowxn35csHsTN3jJU17gE4rKqUKkt-P@mail.gmail.com>
Subject: Re: Last Call: <draft-cheshire-dnsext-special-names-01.txt> (Special-Use Domain Names) to Proposed Standard
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=000e0cd47d0658ecb0049aed4b65
Cc: Stuart Cheshire <cheshire@apple.com>, ietf <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: Fri, 28 Jan 2011 19:41:23 -0000

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

Hello all,

2011/1/28 Magnus Westerlund <magnus.westerlund@ericsson.com>

> 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.
>
> My comments on the document are:
>
> 1. Section 3. I wonder if "Standards Action" is the most appropriate
> rule here. My concern with this is that any other body must perform the
> work in the IETF and give IETF full change control over this proposal.
> This might intended, but I wonder if it is the most appropriate policy.
> My suggestion would be to allow IESG approval as a policy also to give
> some freedom in the strange cases. I do think an IETF standards RFC is
> the preferred way for doing this, but it might be overly restrictive.
>

Therefore, I'd like to propose the 'IETF Consensus' or 'IESG Approval' as
the first the most preferable.

>
> 2. Section 6.
> Why doesn't this document populate this registry with some initial
> values. The document it self already lists some of these. So why not
> include the ones and a note that they are legacy and does not come with
> the new required consideration section?
>

I also commented this section saying the registry, created by this document
is underspecified and does not contain clear guidelines for IANA per RFC
5226.

Finally I really do not know why this document has the intended status
'Standrds Track'.  It is rather the candidate for BCP.

All the best,
Mykyta Yevstifeyev

>
> Best Regards
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> 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
> ----------------------------------------------------------------------
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Hello all,<br><br><div class=3D"gmail_quote">2011/1/28 Magnus Westerlund <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:magnus.westerlund@ericsson.com">magnu=
s.westerlund@ericsson.com</a>&gt;</span><br><blockquote class=3D"gmail_quot=
e" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204,=
 204); padding-left: 1ex;">
I&#39;ve reviewed this document as part of the transport area directorate&#=
39;s<br>
ongoing effort to review key IETF documents. These comments were written<br=
>
primarily for the transport area directors, but are copied to the<br>
document&#39;s authors for their information and to allow them to address<b=
r>
any issues raised. The authors should consider this review together with<br=
>
any other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-dir@ietf.org">tsv-dir@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
My comments on the document are:<br>
<br>
1. Section 3. I wonder if &quot;Standards Action&quot; is the most appropri=
ate<br>
rule here. My concern with this is that any other body must perform the<br>
work in the IETF and give IETF full change control over this proposal.<br>
This might intended, but I wonder if it is the most appropriate policy.<br>
My suggestion would be to allow IESG approval as a policy also to give<br>
some freedom in the strange cases. I do think an IETF standards RFC is<br>
the preferred way for doing this, but it might be overly restrictive.<br></=
blockquote><div><br>Therefore, I&#39;d like to propose the &#39;IETF Consen=
sus&#39; or &#39;IESG Approval&#39; as the first the most preferable. <br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
 border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
2. Section 6.<br>
Why doesn&#39;t this document populate this registry with some initial<br>
values. The document it self already lists some of these. So why not<br>
include the ones and a note that they are legacy and does not come with<br>
the new required consideration section?<br></blockquote><div><br>I also com=
mented this section saying the registry, created by this document is unders=
pecified and does not contain clear guidelines for IANA per RFC 5226.<br>
<br>Finally I really do not know why this document has the intended status =
&#39;Standrds Track&#39;.=A0 It is rather the candidate for BCP.<br><br>All=
 the best,<br>Mykyta Yevstifeyev<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 2=
04); padding-left: 1ex;">

<br>
Best Regards<br>
<br>
Magnus Westerlund<br>
<br>
----------------------------------------------------------------------<br>
Multimedia Technologies, Ericsson Research EAB/TVM<br>
----------------------------------------------------------------------<br>
Ericsson AB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Phone =A0+46 10 7148287<br>
F=E4r=F6gatan 6 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| Mobile +46 73 0949079<br>
SE-164 80 Stockholm, Sweden| mailto: <a href=3D"mailto:magnus.westerlund@er=
icsson.com">magnus.westerlund@ericsson.com</a><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>

--000e0cd47d0658ecb0049aed4b65--

From evnikita2@gmail.com  Fri Jan 28 22:05:43 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 1746F3A68FD for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 22:05:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.23
X-Spam-Level: 
X-Spam-Status: No, score=-2.23 tagged_above=-999 required=5 tests=[AWL=-0.591,  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 JaXVJxebBtJ2 for <ietf@core3.amsl.com>; Fri, 28 Jan 2011 22:05:41 -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 EE53D3A68C8 for <ietf@ietf.org>; Fri, 28 Jan 2011 22:05:40 -0800 (PST)
Received: by fxm9 with SMTP id 9so4417212fxm.31 for <ietf@ietf.org>; Fri, 28 Jan 2011 22:08: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:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6riJ3j+htYLEsqj+cjjpGIH1JS8AvZ7w/+SaAIWBME8=; b=qnG9FYkJLW+SLcep13DpBHGwpatXfp+Slp+7EgV+kUkWL5f6nCKpvCa8KrcVwNPJRN bejieP9/9wFZU6HhBscOnNbXYgXuLNvjmdF2Z4rUMC5FxSyPQ2iuTCSTRjYophfw4WKz sajp0zf9BpmuFsnOSK8Y8uvrUpdgQX50xRnm0=
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=kZ2VuFYNJ4CU4l8QPiMADQTa/r+4HVAj7NnkRhZqzoQPe3prexCYiQICUQAoA06uQV 8KvUUKFRjycWVb3zwx+slPwYfBzN/65GUlvRWiSy9PrGp2h/rMCheXOrSKlvzJM/AN30 ljWsiQZCxTLBvKiO5zHdH0TT15qzetnBlTMN0=
Received: by 10.223.54.132 with SMTP id q4mr3293815fag.117.1296281326829; Fri, 28 Jan 2011 22:08:46 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id k6sm6697310faa.30.2011.01.28.22.08.45 (version=SSLv3 cipher=RC4-MD5); Fri, 28 Jan 2011 22:08:45 -0800 (PST)
Message-ID: <4D43AF04.6050903@gmail.com>
Date: Sat, 29 Jan 2011 08:09:08 +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: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-cheshire-dnsext-special-names-01.txt>	(Special-Use Domain Names) to Proposed Standard
References: <20110117230048.26192.84056.idtracker@localhost> <6.2.5.6.2.20110128055818.0d12bb18@resistor.net>
In-Reply-To: <6.2.5.6.2.20110128055818.0d12bb18@resistor.net>
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: Sat, 29 Jan 2011 06:05:43 -0000

28.01.2011 17:15, SM wrote:
> At 15:00 17-01-11, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Special-Use Domain Names'
>> <draft-cheshire-dnsext-special-names-01.txt> as a Proposed Standard
>>
>>    Abstract
>>
>>    This document describes what it means to say that a DNS name is
>>    reserved for special use, when reserving such a name is appropriate,
>>    and the procedure for doing so.
>>
>> 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
>
> The intended status of draft-cheshire-dnsext-special-names-01 is 
> Standards Track.  BCP would have been a better fit is the aim of this 
> draft is to create a registry and a procedure for reserved DNS names.
I recommended the authors the same in my previous message.
>
> In Section 1:
>
>   'For example, IPv4 addresses 224.0.0.0 to 239.255.255.255 are
>    multicast addresses [RFC2606], with 224.0.0.1 being the "all hosts"'
>
> I suggest dropping that reference as example refers to IPv4 addresses 
> discussed in RFC 5735; RFC 2606 is about Reserved Top Level DNS Names.
While reading the document I really got confused seeing such beginning 
of Introduction.  That would be better to drop all such confusing 
phrases about IPv4 addresses.

Another issue I'd like to raise is references.  Do the authors consider 
making all references Informative as appropriate?  Personally I think 
the following docs. should be referenced normatively: RFC 1034 and RFC 
5226.  Moreover, shouldn't the document update RFC 2606?

Finally, I'd like to propose to create the sub-registry in th cerated 
registry connected with 'Reserved Top Level Domains' for tracking these 
issues along with other special-use domain names.

All the best,
Mykyta Yevstifeyev
>
> From Section 2:
>
>   "Similarly, if a domain name has special properties that affect the
>    way hardware and software implementations handle the name, which
>    apply universally regardless of what network the implementation may
>    be connected to, then that may be a candidate for having the IETF
>    declare the name to be a Special-Use Domain Name and specify what
>    special treatment implementations should give to that name."
>
> That sounds like a good argument for the IETF declare a domain name as 
> "Special Use".  Does ".local" qualify for registration 
> (draft-cheshire-dnsext-multicastdns-13)?
>
> Are domain names as defined under this proposal to be considered as 
> Internet protocol parameters?
>
> From Section 3:
>
>   "If it is determined that special handling of a name is required in
>    order to implement some desired new functionality, then an IETF
>    "Standards Action" RFC [RFC5226] needs to be published describing the
>    new functionality ..."
>
> In other words, if an author can get a Proposed Standard through the 
> IETF process, he or she can get a registration for a Special-Use 
> Domain Name.
>
> In Section 7:
>
>   'How should DNS Registrars treat requests to register this reserved
>    domain name? Should such requests be denied? Should such requests
>    be allowed, but only to a specially-designated entity? (For
>    example, the name "www.example.org" is reserved for documentation
>    examples and is not available for registration; however, the name
>    is in fact registered; and there is even a web site at that name,
>    which states circularly that the name is reserved for use in
>    documentation and cannot be registered!)'
>
> That would be:
>
>    Domain Name: EXAMPLE.COM
>    Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
>    Whois Server: whois.iana.org
>    Referral URL: http://res-dom.iana.org
>    Name Server: A.IANA-SERVERS.NET
>    Name Server: B.IANA-SERVERS.NET
>    Status: clientDeleteProhibited
>    Status: clientTransferProhibited
>    Status: clientUpdateProhibited
>    Updated Date: 26-mar-2004
>    Creation Date: 14-aug-1995
>    Expiration Date: 13-aug-2011
>
> By the way, res-dom.iana.org is not responding on port 80.
>
> In the IANA Considerations Section, 
> draft-cheshire-dnsext-special-names creates a registry of Special-Use 
> Domain Names.  It is customary to populate a new registry with legacy 
> entries such as the domain names mentioned in RFC 2606.
>
> Regards,
> -sm
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From brian.e.carpenter@gmail.com  Sat Jan 29 12:07:00 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 AF3753A6858 for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 12:07:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.469
X-Spam-Level: 
X-Spam-Status: No, score=-103.469 tagged_above=-999 required=5 tests=[AWL=0.130, 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 Don+NaSMqAQU for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 12:06:59 -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 9F0553A681C for <ietf@ietf.org>; Sat, 29 Jan 2011 12:06:59 -0800 (PST)
Received: by gxk27 with SMTP id 27so1739024gxk.31 for <ietf@ietf.org>; Sat, 29 Jan 2011 12:10:09 -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=eiy8gu5KT22xSaLh6sLI5Of/nvUii9vDr0Ur7LgyFV8=; b=Z2hqJxmZQaBb7TBGWs8L0739sKj4h8jGP7bC0DdDLuZrcfAV8peBjOK8NtUnpBn3sm 1eud2zEhPHYb6kjfsdZA8ZuXKx+ua4tYKYy+qAYMARLjniDD3SZJrfXIwvjXvYlRO5iY WY5A9LHZjZGILhf98BjkCgxtZ+HZLSL+4S3FQ=
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=WD52PU2EDL1m+/aM9VgtOtwAz+kQU3vEJ64gP/ko35xZ1vd4L0DaIR7RmMRchmIV3Q jAvuPchcSlvpNe94Il+jtHxT9hisCIuVtxO1QduoCLTuYin5joZbY8nR4qkAzG/SfM4/ e0uL+q9IWredR5EZBjj8oBKLLw9bxld2Xx/SU=
Received: by 10.236.95.17 with SMTP id o17mr8709411yhf.35.1296331809087; Sat, 29 Jan 2011 12:10:09 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id v8sm3468854yhg.40.2011.01.29.12.10.05 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 12:10:07 -0800 (PST)
Message-ID: <4D44741A.9070108@gmail.com>
Date: Sun, 30 Jan 2011 09:10:02 +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: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
In-Reply-To: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 29 Jan 2011 20:07:00 -0000

On 2011-01-27 16:29, Scott O. Bradner wrote:
> 1/ I still do not think this (modified) proposal will have any real
>    impact on the number of "Proposed Standard" documents that move
>    to a (in this proposal, "the") higher level since I do not see
>    how this makes any significant changes to the underlying reasons
>    that documents have not progressed in the past - i.e., I see no
>    reason to think that this proposal would change the world much
>    (would not help, would not hurt)

I tend to be more optimistic. I think that having only one step
ahead to reach final status is *much* less of a psychological
barrier, and the name "Internet Standard" is a *much* more appealing
target than "Draft Standard". Therefore, I believe this change will
be a significant step forward.

> 2/ I think the proposal must specifically deal with the 2026 IPR licence
>    requirement in section 4.1.2
> 
>       If patented or otherwise controlled technology
>       is required for implementation, the separate implementations must
>       also have resulted from separate exercise of the licensing process.

I strongly agree. This exact sentence should be carried forward.

> 
>    The requirement can be dealt with by explicitly discarding 
>    it or by including it. But not mentioning the requirement does
>    not make the issue go away.  This requirement was, in theory, a
>    way to keep the IETF/IESG out of the business of evaluating
>    the fairness of licensing terms.  I can remember only
>    one time it came up (in an appeal) so getting rid of it may
>    be fine - but don't make it look like it was just forgotten.
>  
> 3/ I think you also be quite specific as to how to decide that the
>    conditions for advancement have been met - one of the big
>    implementation issues with 2026 was knowing how to decide
>    that a technology was ready to be advanced (did you need
>    a spreadsheet listing all features and noting with ones
>    had been multiply implemented (as was done at huge effort
>    for HTTP 1.1) or is there someting simplier - clear rules 
>    would help avoid this type of issue in the future

Whike I agree with Scott, I suggest solving this outside the BCP itself.
It's quite a complex issue.

> 
> 4/ as part of #3 - the rules should also specifically deal with
>    the following pp from 2026
> 
>       The requirement for at least two independent and interoperable
>       implementations applies to all of the options and features of the
>       specification.  In cases in which one or more options or features
>       have not been demonstrated in at least two interoperable
>       implementations, the specification may advance to the Draft Standard
>       level only if those options or features are removed.
> 
>    this requirement was included to try to remove cruft from protocols
>    as they went forward - maybe this is no longer a desire but,
>    like with the license issue, a specific mention of what has
>    been decided would mean that people would not think that
>    things were not just forgotton.

Actually the draft does not appear to require interoperability testing
at all:

     "* There are a significant number of implementations with
        successful operational experience."

Is that intentional? I thought interop was generally regarded as
fundamental. So I think the text needs to be explicit about which
bits of section 4.1.2 of RFC 2026 still apply. Or expand the
sentence by adding ", including interoperation between different
implementations when meaningful."

(It's "when meaningful" because some standards such as MIB modules
don't interoperate as such, see RFC 2438.)

On another point:

"5.  Open Question Regarding STD Numbers"

IMHO the easiest solution is still what I suggested some years
ago: retain STD numbers, but assign them at the PS stage. That
removes the confusion about a PS that updates a numbered Standard.

   Brian


From dhc2@dcrocker.net  Sat Jan 29 12:49:24 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 DD0CE3A6880 for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 12:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.583
X-Spam-Level: 
X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016,  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 5bBvIwpjdMtE for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 12:49:22 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id E0D4B3A686D for <ietf@ietf.org>; Sat, 29 Jan 2011 12:49:22 -0800 (PST)
Received: from [192.168.1.4] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0TKqQKk006838 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sat, 29 Jan 2011 12:52:31 -0800
Message-ID: <4D447DF8.7040800@dcrocker.net>
Date: Sat, 29 Jan 2011 12:52:08 -0800
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: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <4D44741A.9070108@gmail.com>
In-Reply-To: <4D44741A.9070108@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 29 Jan 2011 12:52:32 -0800 (PST)
Cc: 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: Sat, 29 Jan 2011 20:49:24 -0000

On 1/29/2011 12:10 PM, Brian E Carpenter wrote:
> On 2011-01-27 16:29, Scott O. Bradner wrote:
>> 4/ as part of #3 - the rules should also specifically deal with
>>     the following pp from 2026
>>
>>        The requirement for at least two independent and interoperable
>>        implementations applies to all of the options and features of the
...
> Actually the draft does not appear to require interoperability testing
> at all:
>
>       "* There are a significant number of implementations with
>          successful operational experience."
>
> Is that intentional? I thought interop was generally regarded as


People are confusing testing with use. Those are two different kinds of 
"interoperability", with the latter being far more stringent.

The new draft specifies the latter.  And it quite intentionally does not specify 
the former.

While "testing" is extremely important for when doing development, there is no 
reason that the IETF should be required to include that very intermediary 
activity within our standards process.

So the new proposal has two phases:

    1) Specification

    2) Use

That there are intermediate real-world phases, such as development, testing and 
deployment is essential, of course.  But there is nothing essential in having 
the IETF mark completion of any of those intermediate phases.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From brian.e.carpenter@gmail.com  Sat Jan 29 14:05:36 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 CEBF93A687F for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 14:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.47
X-Spam-Level: 
X-Spam-Status: No, score=-103.47 tagged_above=-999 required=5 tests=[AWL=0.129, 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 8f9qu-521WQe for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 14:05: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 C50BA3A680E for <ietf@ietf.org>; Sat, 29 Jan 2011 14:05:35 -0800 (PST)
Received: by yie19 with SMTP id 19so1735180yie.31 for <ietf@ietf.org>; Sat, 29 Jan 2011 14:08:45 -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=3iPLl4PXF+wUZWc72V0STwNybWd+VqIla9Eu+R447nI=; b=DOW+JjTOzC9NfQyFDWbXqzCXj2GXHm61l5ibgxMe0kzbnaqp0U0mul3a8d501BBU1R Xk0QQlKbc2KYp7x7TrmD7RYwlOhr9y8vYDvzpn4PJmiWs1nc4VrSOpHmuu62XUv9qwuj ZtWofdj3UZYOytDoVqkKj/9ZGSTan5YlnlPFc=
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=PuvRUGvLYbNMhEYStUicdCVp0trs8Bb3V0Me5SY8KE4j443l1oorpjttf0YZlPFQgn oxYFIzDJceqn7HSyPzGVxGqYD8CI5DYgdXHdQ3f9WoFGCie/X5ZYS2BGbd460SWHsLXk mETUstGBcHRHkwHr1EPb6MNZPbtbDGP2gF5Ls=
Received: by 10.90.28.17 with SMTP id b17mr6853987agb.128.1296338925428; Sat, 29 Jan 2011 14:08:45 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id w6sm3795928anf.26.2011.01.29.14.08.43 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 14:08:44 -0800 (PST)
Message-ID: <4D448FE7.60704@gmail.com>
Date: Sun, 30 Jan 2011 11:08:39 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: draft-housley-two-maturity-levels
References: <20110127032924.2FE4480CCE8@newdev.eecs.harvard.edu> <4D44741A.9070108@gmail.com> <4D447DF8.7040800@dcrocker.net>
In-Reply-To: <4D447DF8.7040800@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 29 Jan 2011 22:05:36 -0000

On 2011-01-30 09:52, Dave CROCKER wrote:
> 
> 
> On 1/29/2011 12:10 PM, Brian E Carpenter wrote:
>> On 2011-01-27 16:29, Scott O. Bradner wrote:
>>> 4/ as part of #3 - the rules should also specifically deal with
>>>     the following pp from 2026
>>>
>>>        The requirement for at least two independent and interoperable
>>>        implementations applies to all of the options and features of the
> ...
>> Actually the draft does not appear to require interoperability testing
>> at all:
>>
>>       "* There are a significant number of implementations with
>>          successful operational experience."
>>
>> Is that intentional? I thought interop was generally regarded as
> 
> 
> People are confusing testing with use. Those are two different kinds of
> "interoperability", with the latter being far more stringent.
> 
> The new draft specifies the latter.  And it quite intentionally does not
> specify the former.

Please point to the text that requires *any* kind of interoperability
being demonstrated by running code. "successful operational experience"
does not state or imply interoperation between independent implementations.

This is a big change in principle from 2026, which is not what is advertised
on the box as "primarily a reduction from three IETF standards track
maturity levels to two."

I want a two stage process, but I don't want to lose interoperability as
an explicit criterion. To me, that's always been the meaning of the
"running code" slogan.

     Brian

> 
> While "testing" is extremely important for when doing development, there
> is no reason that the IETF should be required to include that very
> intermediary activity within our standards process.
> 
> So the new proposal has two phases:
> 
>    1) Specification
> 
>    2) Use
> 
> That there are intermediate real-world phases, such as development,
> testing and deployment is essential, of course.  But there is nothing
> essential in having the IETF mark completion of any of those
> intermediate phases.
> 
> d/

From sob@harvard.edu  Sat Jan 29 14:35:52 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 A708F3A68A3 for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 14:35:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.202
X-Spam-Level: 
X-Spam-Status: No, score=-102.202 tagged_above=-999 required=5 tests=[AWL=0.397, 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 0mw3x9DQLU6C for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 14:35:51 -0800 (PST)
Received: from newdev.eecs.harvard.edu (newdev.eecs.harvard.edu [140.247.60.212]) by core3.amsl.com (Postfix) with ESMTP id 382F53A689C for <ietf@ietf.org>; Sat, 29 Jan 2011 14:35:51 -0800 (PST)
Received: by newdev.eecs.harvard.edu (Postfix, from userid 501) id 60C00817786; Sat, 29 Jan 2011 17:39:00 -0500 (EST)
To: ietf@ietf.org
Subject: prerequisite for change (was Re: draft-housley-two-maturity-levels)
Message-Id: <20110129223900.60C00817786@newdev.eecs.harvard.edu>
Date: Sat, 29 Jan 2011 17:39:00 -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: Sat, 29 Jan 2011 22:35:52 -0000

I've previously expressed my opinion that proposals to muck with the
number of steps in teh IETF standards process will no do anything
useful (i.e., will not be effective) - JOhn and I have just posted
what, to us, would be a prerequisite for amy process mucking proposal
to succeed

Scott

-----
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-bradner-restore-proposed-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Restoring Proposed Standard to Its Intended Use
	Author(s)       : J. Klensin, S. Bradner
	Filename        : draft-bradner-restore-proposed-00.txt
	Pages           : 6
	Date            : 2011-01-29

Restore the very low bar for Proposed Standard described in RFC 2026
(BCP 9)

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-bradner-restore-proposed-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From brian.e.carpenter@gmail.com  Sat Jan 29 15:58:45 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 D7F343A690F for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 15:58:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.472
X-Spam-Level: 
X-Spam-Status: No, score=-103.472 tagged_above=-999 required=5 tests=[AWL=0.127, 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 7vwCAs852mR7 for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 15:58:45 -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 CF24E3A6903 for <ietf@ietf.org>; Sat, 29 Jan 2011 15:58:44 -0800 (PST)
Received: by ywk9 with SMTP id 9so1763296ywk.31 for <ietf@ietf.org>; Sat, 29 Jan 2011 16:01:54 -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=0efDdumPAypC2i3d+bXKR8BA7rQe8M538eYa8TC8rM8=; b=S1i10NM5zPE5nVpTKRu10QVdnLplhQ/BYbhcvqj4CT5TtB/WmEti897eaGyrhuJWvL wK33sdVqFwB6OT3k3cO0t/y0iDR+yT38e11lQ32t1wVe0+pPUR4nTfqJ2PUNO0om7uF9 xNyR7HzFmffkWX8kXWM2z+u6p4MW4epwpzn5M=
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=HWb6xqHjEOu6GHEjN2CI+6RKAvMS2vSBkKFDLuSrcWRSsgiuiseHWZPuzwZpNr6LAQ 3Hc0ub0vd3ngH0iJfgdxVHo6ZfAC/BQ6Xkvu9k9e+sf2fJepttvqJZYIIpejxq7gteoH ta/ORikka/Xrc2sh6lA764hGs8g9gGI6nNxFM=
Received: by 10.150.105.40 with SMTP id d40mr6022944ybc.431.1296345713597; Sat, 29 Jan 2011 16:01:53 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id v8sm12567468ybe.13.2011.01.29.16.01.51 (version=SSLv3 cipher=RC4-MD5); Sat, 29 Jan 2011 16:01:53 -0800 (PST)
Message-ID: <4D44AA6C.8060003@gmail.com>
Date: Sun, 30 Jan 2011 13:01:48 +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: "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu>
In-Reply-To: <20110129223900.60C00817786@newdev.eecs.harvard.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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, 29 Jan 2011 23:58:46 -0000

Hi Scott and John,

I don't see this as inconsistent with the current 2-stage proposal,
if the latter's omission of a requirement for independent interoperable
implementations for stage 2 is corrected.

I don't, however, believe that the problems are separable.
The bar for PS has crept up, IMHO, precisely because the bar
for DS/STD has appeared too high to be readily attainable.

So I see two ways forward that hang together:

1. draft-bradner-restore-proposed +
(draft-housley-two-maturity-levels + independent interoperable implementations)

2. draft-loughney-newtrk-one-size-fits-all-01 (i.e. simply abolish
the second and third stages, and make interoperability reports optional)

I prefer #1.

Regards
   Brian

On 2011-01-30 11:39, Scott O. Bradner wrote:
> I've previously expressed my opinion that proposals to muck with the
> number of steps in teh IETF standards process will no do anything
> useful (i.e., will not be effective) - JOhn and I have just posted
> what, to us, would be a prerequisite for amy process mucking proposal
> to succeed
> 
> Scott
> 
> -----
> From: Internet-Drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-bradner-restore-proposed-00.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 	Title           : Restoring Proposed Standard to Its Intended Use
> 	Author(s)       : J. Klensin, S. Bradner
> 	Filename        : draft-bradner-restore-proposed-00.txt
> 	Pages           : 6
> 	Date            : 2011-01-29
> 
> Restore the very low bar for Proposed Standard described in RFC 2026
> (BCP 9)
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-bradner-restore-proposed-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 

From fluffy@cisco.com  Sat Jan 29 20:50:49 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 0B49B3A6AE3; Sat, 29 Jan 2011 20:50:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.581
X-Spam-Level: 
X-Spam-Status: No, score=-110.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 q07txgfZ4Tbc; Sat, 29 Jan 2011 20:50:46 -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 6C9F33A6A6B; Sat, 29 Jan 2011 20:50:46 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAD59RE2rR7Ht/2dsb2JhbACkenOgapoehU4EhROHDoNF
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 30 Jan 2011 04:53:57 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0U4rUUN015483; Sun, 30 Jan 2011 04:53:55 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: <C9675BFE.2B995%michelle.cotton@icann.org>
Date: Sat, 29 Jan 2011 20:53:55 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C43339C1-88B4-41E9-9CA1-3591338AC6C0@cisco.com>
References: <C9675BFE.2B995%michelle.cotton@icann.org>
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.1082)
Cc: IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, The 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: Sun, 30 Jan 2011 04:50:49 -0000

On Jan 27, 2011, at 17:29 , Michelle Cotton wrote:

> We are changing that process right now.  We have begun to report the
> reviewer (with the review) in the email to the requester.
>=20
> We just need to make sure this small change is communicated to those =
experts
> that are part of review "teams" as their individual names are not =
published
> on the main list of registries.
>=20
> I don't think it needs to go in this document as this is already in
> progress.
>=20
> Let me know if you have any questions.

As long as we agree that is the process, it's not a big deal to me if it =
is in or out of the document but I don't see any reason not to put it =
into the document.=20


From fluffy@cisco.com  Sat Jan 29 20:51:26 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 CC1563A6AA9; Sat, 29 Jan 2011 20:51:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 EX8RjcEeuyof; Sat, 29 Jan 2011 20:51:26 -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 D7D3A3A6A6C; Sat, 29 Jan 2011 20:51:25 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGt+RE2rR7Ht/2dsb2JhbACkeXOgbZoegniCVgSFE4cOg0WITA
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 30 Jan 2011 04:54:21 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0U4rUUO015483; Sun, 30 Jan 2011 04:54:20 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: <4D421795.70505@isi.edu>
Date: Sat, 29 Jan 2011 20:54:19 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFADE5D0-BB33-4418-B743-DFEC11B12740@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>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1082)
Cc: 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: Sun, 30 Jan 2011 04:51:27 -0000

On Jan 27, 2011, at 17:10 , Joe Touch wrote:

> On 1/27/2011 12:52 AM, Lars Eggert wrote:
> ...
> >> 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?
>=20
> 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.=20


From fluffy@cisco.com  Sat Jan 29 20:52:28 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 02F8D3A6A6C; Sat, 29 Jan 2011 20:52:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 f71hJYJ5X5Nz; Sat, 29 Jan 2011 20:52:27 -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 253AD3A6A6B; Sat, 29 Jan 2011 20:52:27 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGt+RE2rR7Ht/2dsb2JhbACkeXOgbZoehU4EhROHDoNF
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 30 Jan 2011 04:55:37 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0U4ta2q016095; Sun, 30 Jan 2011 04:55:37 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: <37255E32-37F1-4907-8A5A-6AB7B590562F@ietf.org>
Date: Sat, 29 Jan 2011 20:55:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF423613-0BB5-4B53-AE3B-4DE696A3C512@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <37255E32-37F1-4907-8A5A-6AB7B590562F@ietf.org>
To: IETF Chair <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: Sun, 30 Jan 2011 04:52:28 -0000

On Jan 27, 2011, at 8:12 , IETF Chair wrote:

>=20
> Originally, two ports were assigned for plain and over-TLS, which for =
HTTP mapped to two different URL schemes: http and https.
>=20
> Many people thought that this was a waste of a port, and the STARTTLS =
approach was developed.  You say that it does not work in some cases, =
and you seem to be suggesting that we go back to the original way.
>=20
> Maybe it works in some cases and not others.  Can we say which is =
which?

I did misread the draft as saying that 2 ports were not allowed when =
clearly that was not what people meant but ...

I'm mostly concerned about cases where latency or bandwidth are an issue =
- basically protocols for real time protocols for internet of things. =
For things like email I'm less concerned. However, I think we can make =
some observation about which works best. Consider some of the most =
successful protocols on the internet

http, 2 ports

email, pop, imap, and smtp, -  more use on multi ports than STARTLS =
though many deployment support both=20

sip, 2 ports=20





From fluffy@cisco.com  Sat Jan 29 20:53:01 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 33B543A6B0B; Sat, 29 Jan 2011 20:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 KWT64mZnkPwc; Sat, 29 Jan 2011 20:52:59 -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 6046B3A6B07; Sat, 29 Jan 2011 20:52:59 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGt+RE2rR7Ht/2dsb2JhbACkeXOgbZoehU4EhROHDoNF
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 30 Jan 2011 04:56:10 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0U4ta2r016095; Sun, 30 Jan 2011 04:56:08 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: <4D413827.7040407@ericsson.com>
Date: Sat, 29 Jan 2011 20:56:07 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4F0B107-4D84-43A5-A091-B6877D24C23B@cisco.com>
References: <20110118212603.5733.34489.idtracker@localhost> <B88A8A82-9C4A-40AC-89AF-F177260760F7@cisco.com> <4D413827.7040407@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: Sun, 30 Jan 2011 04:53:01 -0000

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.=20

We probably need to adjust text like=20

o  IANA strives to encourage the deployment of secure protocols, and
     so strives to avoid separate assignments for non-secure variants

and=20

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

 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


On Jan 27, 2011, at 1:17 , Magnus Westerlund wrote:

>=20
> We have extensive discussion on this in the WG last call. There was no
> consensus for having two ports. At the same time we did also have no
> consensus on mandating one port for any future protocol. Thus we
> adjusted the text to say in Section 7.2:
>=20
> IANA strives to assign only one assigned port number per service or
> application
>=20
> To my knowledge "strive" is not a binding RFC2119 term. I also think =
it
> is a good trade-off with the intention of preserving the space as well
> as possible with only assigning one port, and still allow for more =
than
> one if it really is needed.
>=20
> Is it the above text that triggered your comment or some other text?
>=20
> Cheers
>=20
> Magnus Westerlund


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



From touch@isi.edu  Sat Jan 29 21:28: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 229163A6B06; Sat, 29 Jan 2011 21:28:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, 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 OcJGS-75Ki95; Sat, 29 Jan 2011 21:28:35 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2CF263A6B05; Sat, 29 Jan 2011 21:28:35 -0800 (PST)
Received: from [128.9.176.217] (c2-vpn05.isi.edu [128.9.176.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0U5VDtA000211 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sat, 29 Jan 2011 21:31:14 -0800 (PST)
Message-ID: <4D44F7A1.9090608@isi.edu>
Date: Sat, 29 Jan 2011 21:31:13 -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: <C9675BFE.2B995%michelle.cotton@icann.org> <C43339C1-88B4-41E9-9CA1-3591338AC6C0@cisco.com>
In-Reply-To: <C43339C1-88B4-41E9-9CA1-3591338AC6C0@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: tsvwg@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>, The 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: Sun, 30 Jan 2011 05:28:36 -0000

On 1/29/2011 8:53 PM, Cullen Jennings wrote:
>
> On Jan 27, 2011, at 17:29 , Michelle Cotton wrote:
>
>> We are changing that process right now.  We have begun to report the
>> reviewer (with the review) in the email to the requester.
>>
>> We just need to make sure this small change is communicated to those experts
>> that are part of review "teams" as their individual names are not published
>> on the main list of registries.
>>
>> I don't think it needs to go in this document as this is already in
>> progress.
>>
>> Let me know if you have any questions.
>
> As long as we agree that is the process, it's not a big deal to me if
> it is in or out of the document but I don't see any reason not to put
> it into the document.

The reason is that this document isn't about the IANA process for 
reviewing ports; it's about unifying the port registries.

RFC2780 specifies Expert Review as *one* of the viable means by which 
IANA can decide on transport protocol port assignments:

    Both the Source and Destination Port fields use the same namespace.
    Values in this namespace are assigned following a Specification
    Required, Expert Review, IESG Approval, IETF Consensus, or Standards
    Action process.

The term "Expert Review" is defined in RFC 2434. Neither document 
mandates that IANA either act on the advice such a review, nor that the 
reviewer identity be disclosed as part of that process.

Further, the list of such experts is known by IANA and the IESG:

    Designated experts are appointed by the relevant Area Director of the
    IESG. They are typically named at the time a document that creates a
    new numbering space is published as an RFC, but as experts originally
    appointed may later become unavailable, the relevant Area Director
    will appoint replacements if necessary.

If you want to codify this process further, you would need to revise 
RFC2434 - e.g., to require the disclosure of the expert reviewer. 
However, that is not in the scope of this document.

Joe

From touch@isi.edu  Sat Jan 29 21:31:54 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 0D6683A6876; Sat, 29 Jan 2011 21:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.515
X-Spam-Level: 
X-Spam-Status: No, score=-102.515 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 Q5Hxk0lhYFlN; Sat, 29 Jan 2011 21:31:47 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 1ADB53A6B06; Sat, 29 Jan 2011 21:31:47 -0800 (PST)
Received: from [128.9.176.217] (c2-vpn05.isi.edu [128.9.176.217]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0U5YLrh000739 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sat, 29 Jan 2011 21:34:21 -0800 (PST)
Message-ID: <4D44F85D.5030407@isi.edu>
Date: Sat, 29 Jan 2011 21:34: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: 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>
In-Reply-To: <EFADE5D0-BB33-4418-B743-DFEC11B12740@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: 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: Sun, 30 Jan 2011 05:31:55 -0000

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

Joe


From john-ietf@jck.com  Sat Jan 29 23:06:11 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 B8FDD3A6999 for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 23:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-0.378, 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 1kdoO3tneYRp for <ietf@core3.amsl.com>; Sat, 29 Jan 2011 23:06:10 -0800 (PST)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 6C71A3A6973 for <ietf@ietf.org>; Sat, 29 Jan 2011 23:06:10 -0800 (PST)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1PjRPT-0006fS-IE; Sun, 30 Jan 2011 02:09:19 -0500
X-Vipre-Scanned: 067647F8001DEB06764945-TDI
Date: Sun, 30 Jan 2011 02:09:18 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Scott O. Bradner" <sob@harvard.edu>
Subject: Re: prerequisite for change (was Re:	draft-housley-two-maturity-levels)
Message-ID: <B1775B3EED89C7E2859B9CB8@[192.168.1.128]>
In-Reply-To: <4D44AA6C.8060003@gmail.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <4D44AA6C.8060003@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: 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, 30 Jan 2011 07:06:11 -0000

--On Sunday, January 30, 2011 1:01 PM +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Hi Scott and John,
> 
> I don't see this as inconsistent with the current 2-stage
> proposal, if the latter's omission of a requirement for
> independent interoperable implementations for stage 2 is
> corrected.

I won't try to speak for Scott, but I agree.

> I don't, however, believe that the problems are separable.
> The bar for PS has crept up, IMHO, precisely because the bar
> for DS/STD has appeared too high to be readily attainable.

I think one can read the symptoms, and cause-effect
relationships, in different ways.  However, I think it is safe
to say that --

	* as the bar for PS creeps up, there is less energy,
	inclination, and motivation to move toward DS/STD
	
	* as the percentage of documents --out of those that
	represent specifications of protocols anyone cares about
	-- that are actually advanced to DS/STD goes down, the
	incentives to raise the bar for PS increase.

In other words, regardless of what one believes about cause and
effect, there is a positive feedback loop operating here.

Collapsing STD onto DS is unlikely to affect that loop.  There
has been no evidence offered that such a collapse will increase
the number of documents that advance to that level.   Indeed, by
_adding_ requirements to a combined DS/STD level, it is at least
as likely to raise the perceived threshold for getting to DS/STD
without significantly increasing the motivation to push
documents into that level.

On the other hand, reverting the definition of PS both makes
that level faster and increases the motivation to move a
document to DS/STD because that second level become the first
one at which a reader can really expect a complete and
comprehensive spec.

That is why we used used the term "prerequisite".

> So I see two ways forward that hang together:
> 
> 1. draft-bradner-restore-proposed +
> (draft-housley-two-maturity-levels + independent interoperable
> implementations)
> 
> 2. draft-loughney-newtrk-one-size-fits-all-01 (i.e. simply
> abolish the second and third stages, and make interoperability
> reports optional)

> I prefer #1.

So do I.  But we agree that, absent the commitment to
interoperability testing as a critical part of the standards
process -- the one thing we claimed for years was what made IETF
work almost unique and almost uniquely successful among SDO--
there is little value in having a multiple-step process.

regards,
      john


From gwz@net-zen.net  Sun Jan 30 04:01:39 2011
Return-Path: <gwz@net-zen.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 564B63A6959 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 04:01:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.636
X-Spam-Level: 
X-Spam-Status: No, score=-103.636 tagged_above=-999 required=5 tests=[AWL=0.963, BAYES_00=-2.599, GB_I_LETTER=-2, 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 IvUUx8t7oX1O for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 04:01:39 -0800 (PST)
Received: from smtpauth20.prod.mesa1.secureserver.net (smtpauth20.prod.mesa1.secureserver.net [64.202.165.36]) by core3.amsl.com (Postfix) with SMTP id 248CF3A693B for <ietf@ietf.org>; Sun, 30 Jan 2011 04:01:39 -0800 (PST)
Received: (qmail 9082 invoked from network); 30 Jan 2011 11:58:10 -0000
Received: from unknown (124.122.190.93) by smtpauth20.prod.mesa1.secureserver.net (64.202.165.36) with ESMTP; 30 Jan 2011 11:58:08 -0000
From: "Glen Zorn" <gwz@net-zen.net>
To: <secdir@ietf.org>, <Michael.Groves@cesg.gsi.gov.uk>, <iesg@ietf.org>, <ietf@ietf.org>
Subject: secdir review of draft-groves-mikey-sakke-00
Date: Sun, 30 Jan 2011 18:57:44 +0700
Organization: Network Zen
Message-ID: <000001cbc074$eb1b10f0$c15132d0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcvAdODyYgmg4dzFQJWjFf21rT3diA==
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: Sun, 30 Jan 2011 12:01:39 -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.

EDITORIAL COMMENTS

In the Abstract, the acronym IDPKC doesn't match the capitalized letters in
its expansion.  Suggestion: s/Identifier-based Public Key
Cryptography/Identifier-Based Public Key Cryptography/

In section 1, paragraph 2, s/legislation/legislations/.

Why is the word "identifier" (and variants) persistently capitalized?  It
doesn't appear to be being used as a proper noun.

In the title of section 2, s/Mode;/Mode:/.

In section 2.1, paragraph 1, the acronym "TGK" is not expanded on first use.

There is no IANA Considerations section, FULL STOP.




From hallam@gmail.com  Sun Jan 30 06:24:08 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 58A213A67D2 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 06:24:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.475
X-Spam-Level: 
X-Spam-Status: No, score=-3.475 tagged_above=-999 required=5 tests=[AWL=0.123,  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 WD18OvkC9dZg for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 06:24:07 -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 E1A573A6767 for <ietf@ietf.org>; Sun, 30 Jan 2011 06:24:06 -0800 (PST)
Received: by ywk9 with SMTP id 9so1902979ywk.31 for <ietf@ietf.org>; Sun, 30 Jan 2011 06:27:18 -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=5adL0CsZHqZCkita6BJtiP2Nk9gaH3eA5tN48mKsqLo=; b=w8kEQWPzKAgbZlZrGBo1NPj0TaUOIWeYNWuuN1j+jzJ+GhZiQNpxaj7KC4gxAI+cji d05Zg6hsFS+nTsluQ194+9JlQh6kk2W3+SyyYww1awwp60VtEpCmyXlz5N2DebOTmPlX JwP4Xb6zKontRqQQOyBZ/0cy4IkyxQHO3G4r8=
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=FJksyXRs6jAKV/szclfUdWAWeftQLseD0iHfvtSbRyJjeE008/OJ7bI5pUSONDV89o Ii5HCCltt4WRYzH1oQkmK4iPMb+1hsDB4/osq+yCP+wo5HtPORZ8OUxynaBfOc243VD5 AQ4L1hilDAgbA3qWK7xuyq5vJPq2Zd31aCgjM=
MIME-Version: 1.0
Received: by 10.100.8.9 with SMTP id 9mr3136746anh.120.1296397638023; Sun, 30 Jan 2011 06:27:18 -0800 (PST)
Received: by 10.100.109.16 with HTTP; Sun, 30 Jan 2011 06:27:17 -0800 (PST)
In-Reply-To: <20110129223900.60C00817786@newdev.eecs.harvard.edu>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu>
Date: Sun, 30 Jan 2011 09:27:17 -0500
Message-ID: <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com>
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Scott O. Bradner" <sob@harvard.edu>
Content-Type: multipart/alternative; boundary=0016e6441dd8b3b982049b11185c
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: Sun, 30 Jan 2011 14:24:08 -0000

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

I believe this proposal to be dangerous and undesirable.

The fact is that the three stage process has never worked. As in not ever.
If you take a look at the current Internet standards over half of the total
are grandfathered from before the IETF was started.

You cannot return to a state that never existed.


The raising of the bar for proposed standard has a very simple reason: it is
now almost impossible to change specifications once deployed. There is no
point in conducting a security review after the RFC has issued, it is too
late. Similarly there is no point in checking to see if the Gen Art criteria
are met.

Another factor here is that many specifications coming to IETF have already
had significant work done.



On Sat, Jan 29, 2011 at 5:39 PM, Scott O. Bradner <sob@harvard.edu> wrote:

>
> I've previously expressed my opinion that proposals to muck with the
> number of steps in teh IETF standards process will no do anything
> useful (i.e., will not be effective) - JOhn and I have just posted
> what, to us, would be a prerequisite for amy process mucking proposal
> to succeed
>
> Scott
>
> -----
> From: Internet-Drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D Action:draft-bradner-restore-proposed-00.txt
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>        Title           : Restoring Proposed Standard to Its Intended Use
>        Author(s)       : J. Klensin, S. Bradner
>        Filename        : draft-bradner-restore-proposed-00.txt
>        Pages           : 6
>        Date            : 2011-01-29
>
> Restore the very low bar for Proposed Standard described in RFC 2026
> (BCP 9)
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-bradner-restore-proposed-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>



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

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

I believe this proposal to be dangerous and undesirable.<div><br></div><div=
>The fact is that the three stage process has never worked. As in not ever.=
 If you take a look at the current Internet standards over half of the tota=
l are grandfathered from before the IETF was started.</div>
<div><br></div><div>You cannot return to a state that never existed.</div><=
div><br></div><div><br></div><div>The raising of the bar for proposed stand=
ard has a very simple reason: it is now almost impossible to change specifi=
cations once deployed. There is no point in conducting a security review af=
ter the RFC has issued, it is too late. Similarly there is no point in chec=
king to see if the Gen Art criteria are met.</div>
<div><br></div><div>Another factor here is that many specifications coming =
to IETF have already had significant work done.=A0</div><div><br></div><div=
><br><br><div class=3D"gmail_quote">On Sat, Jan 29, 2011 at 5:39 PM, Scott =
O. Bradner <span dir=3D"ltr">&lt;<a href=3D"mailto:sob@harvard.edu">sob@har=
vard.edu</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;"><br>
I&#39;ve previously expressed my opinion that proposals to muck with the<br=
>
number of steps in teh IETF standards process will no do anything<br>
useful (i.e., will not be effective) - JOhn and I have just posted<br>
what, to us, would be a prerequisite for amy process mucking proposal<br>
to succeed<br>
<br>
Scott<br>
<br>
-----<br>
From: <a href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org<=
/a><br>
To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>
Subject: I-D Action:draft-bradner-restore-proposed-00.txt<br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : Restoring Proposed Standard to =
Its Intended Use<br>
 =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : J. Klensin, S. Bradner<br>
 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-bradner-restore-proposed-00=
.txt<br>
 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 6<br>
 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-01-29<br>
<br>
Restore the very low bar for Proposed Standard described in RFC 2026<br>
(BCP 9)<br>
<br>
A URL for this Internet-Draft is:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-bradner-restore-propos=
ed-00.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-brad=
ner-restore-proposed-00.txt</a><br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><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>Website: <a href=3D"htt=
p://hallambaker.com/">http://hallambaker.com/</a><br><br>
</div>

--0016e6441dd8b3b982049b11185c--

From ajs@shinkuro.com  Sun Jan 30 06:55:07 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 050103A6827 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 06:55:07 -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, 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 PY7tFrif2Yaz for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 06:55:05 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 55D7A3A67B7 for <ietf@ietf.org>; Sun, 30 Jan 2011 06:55:05 -0800 (PST)
Received: from crankycanuck.ca (external.shinkuro.com [66.92.164.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 5545E1ECB42D for <ietf@ietf.org>; Sun, 30 Jan 2011 14:58:16 +0000 (UTC)
Date: Sun, 30 Jan 2011 09:58:14 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
Message-ID: <20110130145814.GA39423@shinkuro.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.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: Sun, 30 Jan 2011 14:55:07 -0000

On Sun, Jan 30, 2011 at 09:27:17AM -0500, Phillip Hallam-Baker wrote:

> The raising of the bar for proposed standard has a very simple reason: it is
> now almost impossible to change specifications once deployed.

That's an argument for _no_ maturity levels, then, not for two.   

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From paul.hoffman@vpnc.org  Sun Jan 30 07:09:15 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 8B3F23A699E; Sun, 30 Jan 2011 07:09:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.75
X-Spam-Level: 
X-Spam-Status: No, score=-101.75 tagged_above=-999 required=5 tests=[AWL=0.296, 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 lzelg3HlWQRr; Sun, 30 Jan 2011 07:09:14 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id B14723A67B4; Sun, 30 Jan 2011 07:09:14 -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 p0UFCOd5016644 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 30 Jan 2011 08:12:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D457FD9.5030905@vpnc.org>
Date: Sun, 30 Jan 2011 07:12:25 -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: 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>	<EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com> <4D44F85D.5030407@isi.edu>
In-Reply-To: <4D44F85D.5030407@isi.edu>
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: Sun, 30 Jan 2011 15:09:15 -0000

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.

From moore@network-heretics.com  Sun Jan 30 07:11:54 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 726D03A67D4 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:11:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.650,  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 kjfxvX-HjjDF for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:11:53 -0800 (PST)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 602AD3A6959 for <ietf@ietf.org>; Sun, 30 Jan 2011 07:11:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 8C5A420581; Sun, 30 Jan 2011 10:15:04 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Sun, 30 Jan 2011 10:15:04 -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=IYxmzvP+/NohTT3f0vfe3iI6GDs=; b=HWh2eyOwE7kXXTxvSADPlEc3DgZqLJFCUQyeb+H5BrIwY6zlOkmArcpeUGNFACbweW+MPiZWXSKxdBnCQ9DD5WN3l6OHCyTC1GdSTQvDekd1Vt7kcZ+Llj4Rb+QyYejc2RvA14vvDk0670vsoeiJNuvntTkvMQfs34K5PzRUrgU=
X-Sasl-enc: EVwEwmTT9N39JrrJTPcqqBbo4Sr2xIeNXsuNiKoFTNl9 1296400504
Received: from 99-205-242-51.pools.spcsdns.net (99-205-242-51.pools.spcsdns.net [99.205.242.51]) by mail.messagingengine.com (Postfix) with ESMTPA id A4B68441C64; Sun, 30 Jan 2011 10:15:03 -0500 (EST)
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
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: <20110130145814.GA39423@shinkuro.com>
Date: Sun, 30 Jan 2011 10:15:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com> <20110130145814.GA39423@shinkuro.com>
To: Andrew Sullivan <ajs@shinkuro.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: Sun, 30 Jan 2011 15:11:54 -0000

On Jan 30, 2011, at 9:58 AM, Andrew Sullivan wrote:

> On Sun, Jan 30, 2011 at 09:27:17AM -0500, Phillip Hallam-Baker wrote:
>=20
>> The raising of the bar for proposed standard has a very simple =
reason: it is
>> now almost impossible to change specifications once deployed.
>=20
> That's an argument for _no_ maturity levels, then, not for two.  =20

Is there an implicit assumption here that more standards (presumably of =
poorer quality) is a good thing?


From ajs@shinkuro.com  Sun Jan 30 07:32:44 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 78E153A67B6 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.326
X-Spam-Level: 
X-Spam-Status: No, score=-102.326 tagged_above=-999 required=5 tests=[AWL=0.273, 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 kU3X3auAEP5Q for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:32:43 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id A61633A699E for <ietf@ietf.org>; Sun, 30 Jan 2011 07:32:43 -0800 (PST)
Received: from crankycanuck.ca (external.shinkuro.com [66.92.164.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 446331ECB42D; Sun, 30 Jan 2011 15:35:55 +0000 (UTC)
Date: Sun, 30 Jan 2011 10:35:51 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
Message-ID: <20110130153551.GB39423@shinkuro.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com> <20110130145814.GA39423@shinkuro.com> <F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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: Sun, 30 Jan 2011 15:32:44 -0000

On Sun, Jan 30, 2011 at 10:15:01AM -0500, Keith Moore wrote:
> > 
> > That's an argument for _no_ maturity levels, then, not for two.   
> 
> Is there an implicit assumption here that more standards (presumably of poorer quality) is a good thing?

Not on my part.  I'm merely observing that, if the claim is that you
can't alter deployed protocols, then there's no reason to say that we
need two maturity levels, because in fact nothing will advance past
the first stage anyway.

Phillip's description of the state of affairs is consistent with what
we actually see today in a three-maturity-level system: nothing moves
past the first level.  But if the problem is that you can't alter a
deployed spec, then no matter how many levels we pare off past the
first, nothing will move to those higher levels, because it's only the
first level that counts.

I'm not happy about this, note.  I'm just making an observation about
what is entailed by Phillip's description.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From moore@network-heretics.com  Sun Jan 30 07:39:16 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 8BBB73A699E for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.274
X-Spam-Level: 
X-Spam-Status: No, score=-3.274 tagged_above=-999 required=5 tests=[AWL=0.325,  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 PoJai4yfibEo for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:39:15 -0800 (PST)
Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by core3.amsl.com (Postfix) with ESMTP id 9042D3A6407 for <ietf@ietf.org>; Sun, 30 Jan 2011 07:39:15 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id 64F302051D; Sun, 30 Jan 2011 10:42:27 -0500 (EST)
Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Sun, 30 Jan 2011 10:42:27 -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=HFdxmZuFV7NrAJgnLifRFtG65xk=; b=ab79GrmhyqCk41vmUS6LNlH/Ytv37cY7tGHihXAe0FPWkRIUJd0Kgk1m+M1kOWzMvwkyovGfj5UWJr9ZP4/B7/OTU3wkeI1nomMQoGJewpy/1H7egnwadrmMhS9lIl1G29sAB3SNsbNJ2ACw0RnNc82tCO4C4c0PuAB0VVV/3sM=
X-Sasl-enc: Z4cmTsz5rO/5OOQu1ma7KIzEKifFWSAC1qbQvAxI/h+5 1296402145
Received: from 99-205-242-51.pools.spcsdns.net (99-205-242-51.pools.spcsdns.net [99.205.242.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 2E2A24493B7; Sun, 30 Jan 2011 10:42:22 -0500 (EST)
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
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: <20110130153551.GB39423@shinkuro.com>
Date: Sun, 30 Jan 2011 10:42:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <12212A10-9793-4E48-8280-06B412B1A3E9@network-heretics.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com> <20110130145814.GA39423@shinkuro.com> <F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com> <20110130153551.GB39423@shinkuro.com>
To: Andrew Sullivan <ajs@shinkuro.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: Sun, 30 Jan 2011 15:39:16 -0000

On Jan 30, 2011, at 10:35 AM, Andrew Sullivan wrote:

> On Sun, Jan 30, 2011 at 10:15:01AM -0500, Keith Moore wrote:
>>>=20
>>> That's an argument for _no_ maturity levels, then, not for two.  =20
>>=20
>> Is there an implicit assumption here that more standards (presumably =
of poorer quality) is a good thing?
>=20
> Not on my part. =20

Sorry, I didn't mean to imply that it was your assumption.  I do wonder =
if it's an assumption held by many in the discussion.

> I'm merely observing that, if the claim is that you
> can't alter deployed protocols, then there's no reason to say that we
> need two maturity levels, because in fact nothing will advance past
> the first stage anyway.

As far as I can tell, the principal reason any specifications move =
beyond Proposed is that they are widely deployed and their limitations =
become apparent.  So I think you can alter deployed protocols, but only =
if the protocols or their implementations are seen to be sufficiently =
broken.

(Which could lead one to conclude, from a perverse point-of-view, that =
some flaws should be left in at Proposed Standards so that they'll have =
to be fixed later, so that we can get more Draft and Full Standards =
published.)

Keith



From dhc2@dcrocker.net  Sun Jan 30 07:46: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 3BC863A67EB for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.589
X-Spam-Level: 
X-Spam-Status: No, score=-6.589 tagged_above=-999 required=5 tests=[AWL=0.010,  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 N8snUJVd1yco for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 07:46:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 2A8BB3A67D4 for <ietf@ietf.org>; Sun, 30 Jan 2011 07:46:58 -0800 (PST)
Received: from [192.168.1.5] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0UFo4uo005852 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 30 Jan 2011 07:50:09 -0800
Message-ID: <4D458898.8090008@dcrocker.net>
Date: Sun, 30 Jan 2011 07:49:44 -0800
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: Andrew Sullivan <ajs@shinkuro.com>
Subject: Re: prerequisite for change (was Re:	draft-housley-two-maturity-levels)
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu>	<AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com>	<20110130145814.GA39423@shinkuro.com>	<F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com> <20110130153551.GB39423@shinkuro.com>
In-Reply-To: <20110130153551.GB39423@shinkuro.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]); Sun, 30 Jan 2011 07:50:10 -0800 (PST)
Cc: 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: Sun, 30 Jan 2011 15:46:59 -0000

On 1/30/2011 7:35 AM, Andrew Sullivan wrote:
>> Is there an implicit assumption here that more standards (presumably of
>> poorer quality) is a good thing?
>
> Not on my part.  I'm merely observing that, if the claim is that you can't
> alter deployed protocols, then there's no reason to say that we need two
> maturity levels, because in fact nothing will advance past the first stage
> anyway.

The current proposal specifies a second maturity level that does not permit 
changing the technical specification.


> But if the problem is that you can't alter a deployed spec, then no matter
> how many levels we pare off past the first, nothing will move to those higher
> levels, because it's only the first level that counts.

The rationale for the second level concerns assessment of success, not changes
to the protocol.

So the basis upon which the second level will succeed or fail has nothing to do
with the criterion you are citing.

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ajs@shinkuro.com  Sun Jan 30 08:03:19 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 439403A699E for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 08:03:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.349
X-Spam-Level: 
X-Spam-Status: No, score=-102.349 tagged_above=-999 required=5 tests=[AWL=0.250, 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 2EhTjxQ6VJUC for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 08:03:18 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 757D03A696E for <ietf@ietf.org>; Sun, 30 Jan 2011 08:03:18 -0800 (PST)
Received: from crankycanuck.ca (external.shinkuro.com [66.92.164.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 9D6691ECB42D; Sun, 30 Jan 2011 16:06:29 +0000 (UTC)
Date: Sun, 30 Jan 2011 11:06:28 -0500
From: Andrew Sullivan <ajs@shinkuro.com>
To: dcrocker@bbiw.net
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
Message-ID: <20110130160628.GD39423@shinkuro.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com> <20110130145814.GA39423@shinkuro.com> <F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com> <20110130153551.GB39423@shinkuro.com> <4D458898.8090008@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D458898.8090008@dcrocker.net>
User-Agent: Mutt/1.5.18 (2008-05-17)
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: Sun, 30 Jan 2011 16:03:19 -0000

On Sun, Jan 30, 2011 at 07:49:44AM -0800, Dave CROCKER wrote:
>> Not on my part.  I'm merely observing that, if the claim is that you can't
>> alter deployed protocols, then there's no reason to say that we need two
>> maturity levels, because in fact nothing will advance past the first stage
>> anyway.
>
> The current proposal specifies a second maturity level that does not 
> permit changing the technical specification.

Yes, I know.  I fail completely to see why anyone would ever do the
work for such movement of maturity level.  The proposal seems to me to
be something along the lines of giving gold stars to protocols with
people who are willing to do the busywork.  I don't have any special
objection to the proposal, and I don't really have strong feelings
about whether it goes anywhere.  But I don't believe it will change
things very much, and it feels to me more like a bureaucratic
improvement than something that helps IETF participants and consumers
of IETF protocols.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.

From hallam@gmail.com  Sun Jan 30 08:54:08 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 304823A6802 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 08:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.475
X-Spam-Level: 
X-Spam-Status: No, score=-3.475 tagged_above=-999 required=5 tests=[AWL=0.123,  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 3PFeFIdmxwsR for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 08:54:06 -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 2B6D63A697A for <ietf@ietf.org>; Sun, 30 Jan 2011 08:54:06 -0800 (PST)
Received: by yie19 with SMTP id 19so1931308yie.31 for <ietf@ietf.org>; Sun, 30 Jan 2011 08:57:18 -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=QmpFU5ogmXVQDfNk7vEkl7wp9vL2JHIWAx5RE7wZxPU=; b=PTD7yEJZfpfP8Tt+T+q/eqSEf00DPhK4pdJw14MPH0PRvwVJnp7eLdjJFIzZ+k618Y xxa8IxJkQiSdDigGz9/3PHSwZmWr26h85jzwzx+iWcTEZqGfEOdRPHZA9U6NZFvJ6IkB KK+vRvtxpmuOJOkCO8W9AmdgKWPGLfQuykxtk=
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=g30FSxrkhInd0kB9TaUvBCkX2PpLhGrZ7ro2kbEQ8BELFW6LWpmoEIlIGrFqlzxzA2 TIJQxUpTCkK+G0ZTXH8I7Z+GFU18N2h7VNotTa6J5FMv7Mej4eEuuWDSjiG/ZGb6Wkzy zTnZQl9MS67GM6y181Jl28isd/0iMQy25dAiQ=
MIME-Version: 1.0
Received: by 10.100.6.7 with SMTP id 7mr3180567anf.256.1296406637678; Sun, 30 Jan 2011 08:57:17 -0800 (PST)
Received: by 10.100.109.16 with HTTP; Sun, 30 Jan 2011 08:57:17 -0800 (PST)
In-Reply-To: <20110130145814.GA39423@shinkuro.com>
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com> <20110130145814.GA39423@shinkuro.com>
Date: Sun, 30 Jan 2011 11:57:17 -0500
Message-ID: <AANLkTikQgpGHw-r9VWP6DykmBPQSw_11QBhOhxjYh8me@mail.gmail.com>
Subject: Re: prerequisite for change (was Re: draft-housley-two-maturity-levels)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Andrew Sullivan <ajs@shinkuro.com>
Content-Type: multipart/alternative; boundary=0016e642d3ba1f9344049b133169
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: Sun, 30 Jan 2011 16:54:08 -0000

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

On Sun, Jan 30, 2011 at 9:58 AM, Andrew Sullivan <ajs@shinkuro.com> wrote:

> On Sun, Jan 30, 2011 at 09:27:17AM -0500, Phillip Hallam-Baker wrote:
>
> > The raising of the bar for proposed standard has a very simple reason: it
> is
> > now almost impossible to change specifications once deployed.
>
> That's an argument for _no_ maturity levels, then, not for two.
>

Not at all, many protocols are never successfully deployed.

In the case that a protocol is successfully deployed, the final protocol has
frequently required major modification. Documenting those changes has value.


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

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

On Sun, Jan 30, 2011 at 9:58 AM, Andrew Sullivan <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:ajs@shinkuro.com">ajs@shinkuro.com</a>&gt;</span> wrote:<br><=
div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Sun, Jan 30, 2011 at 09:27:17AM -0500, Phillip Hallam-=
Baker wrote:<br>
<br>
&gt; The raising of the bar for proposed standard has a very simple reason:=
 it is<br>
&gt; now almost impossible to change specifications once deployed.<br>
<br>
</div>That&#39;s an argument for _no_ maturity levels, then, not for two.<b=
r></blockquote><div><br></div><div>Not at all, many protocols are never suc=
cessfully deployed.</div><div><br></div><div>In the case that a protocol is=
 successfully deployed, the final protocol has frequently required major mo=
dification. Documenting those changes has value.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br><br>

--0016e642d3ba1f9344049b133169--

From touch@isi.edu  Sun Jan 30 09:31: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 863DA3A6AF1; Sun, 30 Jan 2011 09:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.502
X-Spam-Level: 
X-Spam-Status: No, score=-102.502 tagged_above=-999 required=5 tests=[AWL=0.097, 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 LK2u4Kuh5rO6; Sun, 30 Jan 2011 09:31:14 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 23BBF3A6ABD; Sun, 30 Jan 2011 09:31:14 -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 vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p0UHY2IY008760 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Sun, 30 Jan 2011 09:34:13 -0800 (PST)
Message-ID: <4D45A105.1020102@isi.edu>
Date: Sun, 30 Jan 2011 09:33:57 -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>
In-Reply-To: <4D457FD9.5030905@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>, 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: Sun, 30 Jan 2011 17:31:15 -0000

Paul (et al.),

See below.

Note that IANA can't just make its own decisions either and ignore IETF 
process *AND* expert review.

I wasn't trying to imply that, but it appears to have been inferred from 
my claim that "neither document binds IANA to the advice of a reviewer". 
IANA is bound by the "OR" of basic IETF process and Expert Review. The 
former can override the latter (or vice versa), but there is an appeal 
process - through the IETF - as well.

If you have issue with these processes, then RFC 2434 and RFC 2780 are 
your targets, not this doc.

Joe

On 1/30/2011 7:12 AM, Paul Hoffman wrote:
> On 1/29/11 9:34 PM, Joe Touch wrote:
...
>> 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.

Repeating myself:

a) this document is NOT proscribing IANA processes for expert review of 
port requests

b) RFC 2790 describes MANY ways IANA decides how to allocate ports:

    Values in this namespace are assigned following a Specification
    Required, Expert Review, IESG Approval, IETF Consensus, or Standards
    Action.

Note the word *OR* above. Expert review doesn't override IETF process here.

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

The above section already allows for that.

> This makes it the responsibility
> of the IETF consensus process to follow the guidelines in this
> document.

This document says, quite clearly, at the front of Section 7.2:

    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.

It never says that this is a process that the IESG or IETF is required 
to follow. The language of the section has wiggle words throughout, and 
does not use RFC 2119 language. Thus nobody anywhere is bound by it.

c) RFC 2434 notes how expert reviewers are selected:

    Designated experts are appointed by the relevant Area Director of the
    IESG. They are typically named at the time a document that creates a
    new numbering space is published as an RFC, but as experts originally
    appointed may later become unavailable, the relevant Area Director
    will appoint replacements if necessary.

d) there is already a process to appeal decisions that are based on 
Expert Review:

    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]. Since the designated experts are appointed by the IESG,
    they may be removed by the IESG.

------

From doug@ewellic.org  Sun Jan 30 10:47:57 2011
Return-Path: <doug@ewellic.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 5BB9E3A684E for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 10:47:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.004
X-Spam-Level: 
X-Spam-Status: No, score=-1.004 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_05=-1.11, 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 iNMYmEHg3aDf for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 10:47:56 -0800 (PST)
Received: from p3plsmtpa01-09.prod.phx3.secureserver.net (p3plsmtpa01-09.prod.phx3.secureserver.net [72.167.82.89]) by core3.amsl.com (Postfix) with SMTP id 2B0903A67EB for <ietf@ietf.org>; Sun, 30 Jan 2011 10:47:55 -0800 (PST)
Received: (qmail 15410 invoked from network); 30 Jan 2011 18:51:07 -0000
Received: from unknown (24.8.55.39) by p3plsmtpa01-09.prod.phx3.secureserver.net (72.167.82.89) with ESMTP; 30 Jan 2011 18:51:07 -0000
Message-ID: <CD7CBA8E03324FD1B6D06B7B6221D9D1@DougEwell>
From: "Doug Ewell" <doug@ewellic.org>
To: "Mykyta Yevstifeyev" <evnikita2@gmail.com>
References: <20110128075753.665a7a7059d7ee80bb4d670165c8327d.30b3acba39.wbe@email03.secureserver.net> <AANLkTi=w1B1Op9Qbua=zFnQj3refWc_ZX1=aXr=gZUKP@mail.gmail.com>
In-Reply-To: <AANLkTi=w1B1Op9Qbua=zFnQj3refWc_ZX1=aXr=gZUKP@mail.gmail.com>
Subject: Re: Request for Review - draft-yevstifeyev-genarea-historic-01
Date: Sun, 30 Jan 2011 11:51:06 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A1_01CBC073.FA31F0A0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 15.4.3502.922
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3502.922
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: Sun, 30 Jan 2011 18:47:57 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_00A1_01CBC073.FA31F0A0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Mykyta Yevstifeyev wrote:

>> I'd like to see some kind of guideline that the RFC should not be =
considered obsolete solely because of security or performance concerns =
in some particular, specific context.  For example, the fact that =
vanilla FTP is not sufficiently secure for use in some applications =
where high security is paramount is not a rationale for deprecating FTP =
in all applications.
>
> In the case I mentioned as c the key words are 'is not possible or is =
not advised to be used in the Internet' but not what you mentioned.

The document says =E2=80=9Cis not advised to be used in the Internet =
because of its security issues, impact on its performance or any other =
reason.=E2=80=9D  (Do you agree that the document says that?)  My point =
is that, because security or performance issues in one context do not =
necessarily imply security or performance issues in all contexts, they =
should not by themselves (or together with the 7-year criterion) be =
sufficient to trigger deprecation.

> The phrase 'or any other reason' is put because there is no =
possibility to put the exhaustive list of such purposes.   Anyway, what =
would you like to propose here?

I don=E2=80=99t have exact replacement wording.  =E2=80=9CAny other =
reason=E2=80=9D could permit me to propose deprecation or =
=E2=80=9Chistoricization=E2=80=9D of a protocol because I don=E2=80=99t =
like the guy who created it, or because my company is promoting a rival =
protocol.

--
Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s =C2=AD
------=_NextPart_000_00A1_01CBC073.FA31F0A0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-FAMILY: 'Calibri'; COLOR: #000000; FONT-SIZE: 12pt">
<DIV>Mykyta Yevstifeyev wrote:</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;&gt; I'd like to see some kind of guideline that the RFC should =
not be=20
considered obsolete solely because of security or performance concerns =
in some=20
particular, specific context.&nbsp; For example, the fact that vanilla =
FTP is=20
not sufficiently secure for use in some applications where high security =
is=20
paramount is not a rationale for deprecating FTP in all =
applications.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt; In the case I mentioned as c the key words are 'is not =
possible or is=20
not advised to be used in the Internet' but not what you =
mentioned.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The document says =E2=80=9Cis not advised to be used in the =
Internet because of its=20
security issues, impact on its performance or any other =
reason.=E2=80=9D&nbsp; (Do you=20
agree that the document says that?)&nbsp; My point is that, because =
security or=20
performance issues in one context do not necessarily imply security or=20
performance issues in all contexts, they should not by themselves (or =
together=20
with the 7-year criterion) be sufficient to trigger deprecation.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt; The phrase 'or any other reason' is put because there is no=20
possibility to put the exhaustive list of such purposes.&nbsp;&nbsp; =
Anyway,=20
what would you like to propose here?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I don=E2=80=99t have exact replacement wording.&nbsp; =E2=80=9CAny =
other reason=E2=80=9D could=20
permit me to propose deprecation or =E2=80=9Chistoricization=E2=80=9D of =
a protocol because I=20
don=E2=80=99t like the guy who created it, or because my company is =
promoting a rival=20
protocol.</DIV>
<DIV>&nbsp;</DIV>
<DIV>--</DIV>
<DIV>Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org</DIV>
<DIV>RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s=20
&shy;</DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_00A1_01CBC073.FA31F0A0--


From drc@virtualized.org  Sun Jan 30 10:49:05 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 C24F83A6AD2; Sun, 30 Jan 2011 10:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=0.160,  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 IxhCxWIgUzfT; Sun, 30 Jan 2011 10:49:04 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id CAD513A684E; Sun, 30 Jan 2011 10:49:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 328B3106F259; Sun, 30 Jan 2011 10:52:17 -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 4cDctRJsvFv0; Sun, 30 Jan 2011 10:52:15 -0800 (PST)
Received: from [10.0.1.9] (c-24-130-212-17.hsd1.ca.comcast.net [24.130.212.17]) by virtualized.org (Postfix) with ESMTP id 1D212106F24B; Sun, 30 Jan 2011 10:52:15 -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: David Conrad <drc@virtualized.org>
In-Reply-To: <EFADE5D0-BB33-4418-B743-DFEC11B12740@cisco.com>
Date: Sun, 30 Jan 2011 10:52:13 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E96E191-26AD-41CA-A0BA-099276312814@virtualized.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>
To: Cullen Jennings <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1082)
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: Sun, 30 Jan 2011 18:49:05 -0000

Cullen,

On Jan 29, 2011, at 8:54 PM, Cullen Jennings 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.
>=20
> 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.=20


Joe is closer. =20

In general, IANA staff are not technical experts in any of the wide =
variety of areas for which they are asked to provide registry services.  =
As such, they rely on technical experts to provide =
input/advice/recommendations.  In the past, there were some very rare =
cases in which the advice provided by the technical experts was deemed =
insufficient and IANA staff looked to the ADs or the IESG for additional =
input.  However, at least historically, IANA staff viewed the =
maintenance of the registries as their responsibility (at the direction =
of the IESG), not the technical experts' responsibility. I would be =
surprised if this had changed.

Regards,
-drc


From michelle.cotton@icann.org  Sun Jan 30 11:07:16 2011
Return-Path: <michelle.cotton@icann.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 3E4963A6851; Sun, 30 Jan 2011 11:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.465
X-Spam-Level: 
X-Spam-Status: No, score=-106.465 tagged_above=-999 required=5 tests=[AWL=0.135, 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 Tid-NTBZefCg; Sun, 30 Jan 2011 11:06:45 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 762D43A6849; Sun, 30 Jan 2011 11:06:45 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Sun, 30 Jan 2011 11:09:57 -0800
From: Michelle Cotton <michelle.cotton@icann.org>
To: David Conrad <drc@virtualized.org>, Cullen Jennings <fluffy@cisco.com>
Date: Sun, 30 Jan 2011 11:09:54 -0800
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: AcvAruKab6Aanz9fQse61B69W+wxdgAAmQ2x
Message-ID: <C96AF782.2BAD0%michelle.cotton@icann.org>
In-Reply-To: <2E96E191-26AD-41CA-A0BA-099276312814@virtualized.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF, "tsvwg@ietf.org" <tsvwg@ietf.org>, discussion list <ietf@ietf.org>, The 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: Sun, 30 Jan 2011 19:07:16 -0000

David has said this well.  Thank you.

Please let me know if there are any other questions.

--Michelle



On 1/30/11 10:52 AM, "David Conrad" <drc@virtualized.org> wrote:

> Cullen,
>=20
> On Jan 29, 2011, at 8:54 PM, Cullen Jennings 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.
>>=20
>> I think you are pretty misrepresenting the situation. My impression of t=
he
>> 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 the=
y
>> pretty much do whatever the expert says.
>=20
>=20
> Joe is closer. =20
>=20
> In general, IANA staff are not technical experts in any of the wide varie=
ty of
> areas for which they are asked to provide registry services.  As such, th=
ey
> rely on technical experts to provide input/advice/recommendations.  In th=
e
> past, there were some very rare cases in which the advice provided by the
> technical experts was deemed insufficient and IANA staff looked to the AD=
s or
> the IESG for additional input.  However, at least historically, IANA staf=
f
> viewed the maintenance of the registries as their responsibility (at the
> direction of the IESG), not the technical experts' responsibility. I woul=
d be
> surprised if this had changed.
>=20
> Regards,
> -drc
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From evnikita2@gmail.com  Sun Jan 30 22:10:34 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 F3B203A6B95 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 22:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.193
X-Spam-Level: 
X-Spam-Status: No, score=-3.193 tagged_above=-999 required=5 tests=[AWL=0.405,  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 BjRW2e2DsPj6 for <ietf@core3.amsl.com>; Sun, 30 Jan 2011 22:10:32 -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 96B513A6B90 for <ietf@ietf.org>; Sun, 30 Jan 2011 22:10:31 -0800 (PST)
Received: by fxm9 with SMTP id 9so5745412fxm.31 for <ietf@ietf.org>; Sun, 30 Jan 2011 22:13:44 -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=fPA7hz14QGRDd+BGrt6vfGV8xEt4RM7eZkmq7wIG+oU=; b=f7p+MxrHsdPH8DXEbYllcZZCehg3LY9ZKO0klbQ6gj3mmdiCSUU+RapFKFOsAgozkc OhVwgiX+MQzzTNQhUiV19G23ors0GRA3Jsb3AgPxqwmXBBQRfUEG6pM94ENVrmuPO9Az G3+/oJHsZkURcsgra1k6ATFz9vBud4EybeHhM=
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=GdH+fiT46zGb7APT+Ys86sIb+rI+whjUihPhJWGlfgIrNRx0Pal7RyXlyI77LT2QLI Np95ETLyxmklIqWsRpsbvQ3zxI+Nun39ZCV3VCXt8bHjuziKyXgmZeFs4ucZ+2fpA6aO pQHcjCdbDMFhT9gc4NAcaRYhBMTbQTLacbXt0=
Received: by 10.223.96.73 with SMTP id g9mr5627636fan.24.1296454424358; Sun, 30 Jan 2011 22:13:44 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id n15sm7191358fam.12.2011.01.30.22.13.42 (version=SSLv3 cipher=RC4-MD5); Sun, 30 Jan 2011 22:13:43 -0800 (PST)
Message-ID: <4D46532E.7080308@gmail.com>
Date: Mon, 31 Jan 2011 08:14:06 +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: Doug Ewell <doug@ewellic.org>
Subject: Re: Request for Review - draft-yevstifeyev-genarea-historic-01
References: <20110128075753.665a7a7059d7ee80bb4d670165c8327d.30b3acba39.wbe@email03.secureserver.net> <AANLkTi=w1B1Op9Qbua=zFnQj3refWc_ZX1=aXr=gZUKP@mail.gmail.com> <CD7CBA8E03324FD1B6D06B7B6221D9D1@DougEwell>
In-Reply-To: <CD7CBA8E03324FD1B6D06B7B6221D9D1@DougEwell>
Content-Type: multipart/alternative; boundary="------------040200090000010800040005"
Cc: rfc-interest@rfc-editor.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, 31 Jan 2011 06:10:34 -0000

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

Doug, all,

30.01.2011 20:51, Doug Ewell wrote:
> Mykyta Yevstifeyev wrote:
> >> I'd like to see some kind of guideline that the RFC should not be 
> considered obsolete solely because of security or performance concerns 
> in some particular, specific context.  For example, the fact that 
> vanilla FTP is not sufficiently secure for use in some applications 
> where high security is paramount is not a rationale for deprecating 
> FTP in all applications.
> >
> > In the case I mentioned as c the key words are 'is not possible or 
> is not advised to be used in the Internet' but not what you mentioned.
> The document says “is not advised to be used in the Internet because 
> of its security issues, impact on its performance or any other 
> reason.”  (Do you agree that the document says that?)  My point is 
> that, because security or performance issues in one context do not 
> necessarily imply security or performance issues in all contexts, they 
> should not by themselves (or together with the 7-year criterion) be 
> sufficient to trigger deprecation.
I've recently thought on how to formulate this criterion.  My most 
current thoughts are the following:

c. The RFC describes the technology that is not possible to be used
      in the current Internet because of its technical characteristics or
      possible problems with its implementation.

However this is not a final variant - any other proposals are welcome.
> > The phrase 'or any other reason' is put because there is no 
> possibility to put the exhaustive list of such purposes.   Anyway, 
> what would you like to propose here?
> I don’t have exact replacement wording.  “Any other reason” could 
> permit me to propose deprecation or “historicization” of a protocol 
> because I don’t like the guy who created it, or because my company is 
> promoting a rival protocol.
Agreed here.  See what I think below.

---------

And now a few questions for discussion:

1)  Should historicizing Informational RFCs be allowed?

My proposal is to allow this only if they describe the protocol (see 
Section 4.2.2 of RFC 2026) with the authors' approval REQUIRED.

2)  Definition of obsolete RFCs are still unclear.  The most recent what 
I have is:

The RFC SHALL be considered to be obsolete if it meets the following
    criteria:

      a. It has been publicly available for at least 7 years;

      b. During this period of time the technology, described in this RFC
      has not been seen used in the Internet; or

      c. The RFC describes the technology that is not possible to be used
      in the current Internet because of its technical characteristics or
      possible problems with its implementation.

Any proposals on this?

3)  Procedures on Experimental RFCs to Historic.

What I have in my working version is different from what is in -01 
version.  See below:

3.2.3. Experimental RFCs

    Procedures for historicizing Experimental RFCs depend on their origin
    and the way it is being historicized with.

3.2.3.1. Separate Historicizing Document

    The procedures described in this section apply to the case, mentioned
    as 'b' at the beginning of Section 3.2 (separate historicizing
    document).

    If the Experimental RFCs has been processed on IETF stream [RFC4844],
    'IETF Consensus' [RFC5226] is REQUIRED to historicize it.

    If the Experimental RFCs has been processed on IAB stream [RFC4844],
    'IETF Consensus' [RFC5226] and IAB Chair approval is REQUIRED to
    historicize it.

    If the Experimental RFCs has been processed on IRTF stream [RFC4844],
    'IETF Consensus' [RFC5226] and IRTF Chair approval is REQUIRED to
    historicize it.

    If the Experimental RFCs has been processed on Independent
    Submissions stream [RFC4844], 'IETF Consensus' [RFC5226] and authors'
    approval is REQUIRED to historicize it.  In essential cases the
    approval of the director of the area the historicized document is
    considered to be related to MAY be used instead the authors' one.

    In the cases described above IESG is responsible for recording their
    approval.

3.2.3.2. Superseding Document Historicizes the Superseded One

    The procedures described in this section apply to the case, mentioned
    as 'a' at the beginning of Section 3.2 (superseding document
    historicizes the superseded one).

    The superseding document that is being processed on the same stream
    [RFC4844] as the superseded one MAY move it to Historic without any
    special procedures; a simple mention of such action is therefore
    REQUIRED in superseding document.

    If the superseding document is being processed on the stream,
    different from that of superseded one, the approval of corresponding
    party is REQUIRED.  Section 3.2.3.1 describes some cases that apply
    this one as well (for IAB-, IETF-, and Independent Submissions
    streams [RFC4844]).  Historicizing IETF-stream documents by non-IETF-
    stream ones SHALL be made following usual procedures for RFCs of such
    stream with IETF Chair approval REQUIRED.

4)  Are there any thoughts on other consideration connected with 
historic docs.?

Except referencing, there might be appropriate to discuss what should be 
done with IANA registries defined by Historic RFCs.  Anything else?

All the best,
Mykyta Yevstifeyev
> --
> Doug Ewell | Thornton, Colorado, USA | http://www.ewellic.org
> RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd slash 2kf0s ­


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Doug, all,<br>
    <br>
    30.01.2011 20:51, Doug Ewell wrote:
    <blockquote cite="mid:CD7CBA8E03324FD1B6D06B7B6221D9D1@DougEwell"
      type="cite">
      <div dir="ltr">
        <div style="font-family: 'Calibri'; color: rgb(0, 0, 0);
          font-size: 12pt;">
          <div>Mykyta Yevstifeyev wrote:</div>
          <div> </div>
          <div>&gt;&gt; I'd like to see some kind of guideline that the
            RFC should not be considered obsolete solely because of
            security or performance concerns in some particular,
            specific context.  For example, the fact that vanilla FTP is
            not sufficiently secure for use in some applications where
            high security is paramount is not a rationale for
            deprecating FTP in all applications.</div>
          <div>&gt;</div>
          <div>&gt; In the case I mentioned as c the key words are 'is
            not possible or is not advised to be used in the Internet'
            but not what you mentioned.</div>
          <div> </div>
          <div>The document says “is not advised to be used in the
            Internet because of its security issues, impact on its
            performance or any other reason.”  (Do you agree that the
            document says that?)  My point is that, because security or
            performance issues in one context do not necessarily imply
            security or performance issues in all contexts, they should
            not by themselves (or together with the 7-year criterion) be
            sufficient to trigger deprecation.</div>
        </div>
      </div>
    </blockquote>
    I've recently thought on how to formulate this criterion.  My most
    current thoughts are the following:<br>
    <br>
    <small>c. The RFC describes the technology that is not possible to
      be used<br>
           in the current Internet because of its technical
      characteristics or<br>
           possible problems with its implementation.</small><br>
    <br>
    However this is not a final variant - any other proposals are
    welcome.<br>
    <blockquote cite="mid:CD7CBA8E03324FD1B6D06B7B6221D9D1@DougEwell"
      type="cite">
      <div dir="ltr">
        <div style="font-family: 'Calibri'; color: rgb(0, 0, 0);
          font-size: 12pt;">
          <div> </div>
          <div>&gt; The phrase 'or any other reason' is put because
            there is no possibility to put the exhaustive list of such
            purposes.   Anyway, what would you like to propose here?</div>
          <div> </div>
          <div>I don’t have exact replacement wording.  “Any other
            reason” could permit me to propose deprecation or
            “historicization” of a protocol because I don’t like the guy
            who created it, or because my company is promoting a rival
            protocol.</div>
        </div>
      </div>
    </blockquote>
    Agreed here.  See what I think below.<br>
    <br>
    ---------<br>
    <br>
    And now a few questions for discussion:<br>
    <br>
    1)  Should historicizing Informational RFCs be allowed?<br>
    <br>
    My proposal is to allow this only if they describe the protocol (see
    Section 4.2.2 of RFC 2026) with the authors' approval REQUIRED.<br>
    <br>
    2)  Definition of obsolete RFCs are still unclear.  The most recent
    what I have is:<br>
    <br>
    <small>The RFC SHALL be considered to be obsolete if it meets the
      following<br>
         criteria:<br>
      <br>
           a. It has been publicly available for at least 7 years; <br>
      <br>
           b. During this period of time the technology, described in
      this RFC<br>
           has not been seen used in the Internet; or<br>
      <br>
           c. The RFC describes the technology that is not possible to
      be used<br>
           in the current Internet because of its technical
      characteristics or<br>
           possible problems with its implementation.</small><br>
    <br>
    Any proposals on this?<br>
    <br>
    3)  Procedures on Experimental RFCs to Historic.<br>
    <br>
    What I have in my working version is different from what is in -01
    version.  See below:<br>
    <br>
    <small>3.2.3. Experimental RFCs<br>
      <br>
         Procedures for historicizing Experimental RFCs depend on their
      origin<br>
         and the way it is being historicized with.<br>
      <br>
      3.2.3.1. Separate Historicizing Document<br>
      <br>
         The procedures described in this section apply to the case,
      mentioned<br>
         as 'b' at the beginning of Section 3.2 (separate historicizing<br>
         document).<br>
      <br>
         If the Experimental RFCs has been processed on IETF stream
      [RFC4844],<br>
         'IETF Consensus' [RFC5226] is REQUIRED to historicize it.<br>
      <br>
         If the Experimental RFCs has been processed on IAB stream
      [RFC4844],<br>
         'IETF Consensus' [RFC5226] and IAB Chair approval is REQUIRED
      to<br>
         historicize it.<br>
      <br>
         If the Experimental RFCs has been processed on IRTF stream
      [RFC4844],<br>
         'IETF Consensus' [RFC5226] and IRTF Chair approval is REQUIRED
      to<br>
         historicize it.<br>
      <br>
         If the Experimental RFCs has been processed on Independent<br>
         Submissions stream [RFC4844], 'IETF Consensus' [RFC5226] and
      authors'<br>
         approval is REQUIRED to historicize it.  In essential cases the<br>
         approval of the director of the area the historicized document
      is<br>
         considered to be related to MAY be used instead the authors'
      one.<br>
      <br>
         In the cases described above IESG is responsible for recording
      their <br>
         approval.<br>
      <br>
      3.2.3.2. Superseding Document Historicizes the Superseded One<br>
      <br>
         The procedures described in this section apply to the case,
      mentioned<br>
         as 'a' at the beginning of Section 3.2 (superseding document<br>
         historicizes the superseded one).<br>
      <br>
         The superseding document that is being processed on the same
      stream<br>
         [RFC4844] as the superseded one MAY move it to Historic without
      any<br>
         special procedures; a simple mention of such action is
      therefore<br>
         REQUIRED in superseding document.<br>
      <br>
         If the superseding document is being processed on the stream,<br>
         different from that of superseded one, the approval of
      corresponding<br>
         party is REQUIRED.  Section 3.2.3.1 describes some cases that
      apply<br>
         this one as well (for IAB-, IETF-, and Independent Submissions<br>
         streams [RFC4844]).  Historicizing IETF-stream documents by
      non-IETF-<br>
         stream ones SHALL be made following usual procedures for RFCs
      of such<br>
         stream with IETF Chair approval REQUIRED.</small><br>
    <br>
    4)  Are there any thoughts on other consideration connected with
    historic docs.?<br>
    <br>
    Except referencing, there might be appropriate to discuss what
    should be done with IANA registries defined by Historic RFCs. 
    Anything else?<br>
    <br>
    All the best,<br>
    Mykyta Yevstifeyev<br>
    <blockquote cite="mid:CD7CBA8E03324FD1B6D06B7B6221D9D1@DougEwell"
      type="cite">
      <div dir="ltr">
        <div style="font-family: 'Calibri'; color: rgb(0, 0, 0);
          font-size: 12pt;">
          <div> </div>
          <div>--</div>
          <div>Doug Ewell | Thornton, Colorado, USA |
            <a class="moz-txt-link-freetext" href="http://www.ewellic.org">http://www.ewellic.org</a></div>
          <div>RFC 5645, 4645, UTN #14 | ietf-languages @ is dot gd
            slash 2kf0s ­</div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040200090000010800040005--

From lars.eggert@nokia.com  Mon Jan 31 00:20:46 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 DFC4C3A6BB1; Mon, 31 Jan 2011 00:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.796
X-Spam-Level: 
X-Spam-Status: No, score=-103.796 tagged_above=-999 required=5 tests=[AWL=-0.197, 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 xP14HQYMOJzK; Mon, 31 Jan 2011 00:20:46 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id DB3093A6BB9; Mon, 31 Jan 2011 00:20:45 -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 p0V8NuQ1012118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 10:23:57 +0200
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
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-14-327443728; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4D457FD9.5030905@vpnc.org>
Date: Mon, 31 Jan 2011 10:23:43 +0200
Message-Id: <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.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>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Mon, 31 Jan 2011 10:23:48 +0200 (EET)
X-Nokia-AV: Clean
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, IETF discussion list <ietf@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: Mon, 31 Jan 2011 08:20:47 -0000

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

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. And I've never witnessed IANA rejecting requests =
coming through the IETF. But even if they did, there is an appeals =
procedure.

Lars=20=

--Apple-Mail-14-327443728
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEzMTA4MjM0M1owIwYJKoZIhvcNAQkE
MRYEFKCf303LMvmzDao+W1UcPtMq7sZRMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
ABiqSyROzEOw5SRI713JGRYAsMc4G2NALek56P185xuS7Y1CNPT9WBc5cfiqhbGl+Mkynwhp6ou7
XJibylFC4hcZaAU0+8HnxMn+2ieruqFf449Suqa7K9jIb7Yn9sLmgJSjsAodhadtBa4XsLEicPhQ
xUBVkK4PfWkcfFFNaQqNvxJ+d8UFdK5HjGLARmzCZ7tu4OeGDjQkJUCeT2vW+LHlCFGcqo4TVYL7
e4vwTLoaaHxQBzE2g6gk/koNBg4kgm0p/aTtlz0Sd557zHxtRycboSjZnnexa5S/Ihh7+14Lq3Xp
mZ7lj1utAEEvrVm/DgXr3DVRCUm3Nncxw714uDMAAAAAAAA=

--Apple-Mail-14-327443728--

From magnus.westerlund@ericsson.com  Mon Jan 31 05:02:50 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 799573A694A; Mon, 31 Jan 2011 05:02:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.485
X-Spam-Level: 
X-Spam-Status: No, score=-106.485 tagged_above=-999 required=5 tests=[AWL=0.114, 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 VEKf-Fcv7j44; Mon, 31 Jan 2011 05:02:49 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id D08B33A6BEC; Mon, 31 Jan 2011 05:02:48 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-93-4d46b3baadd5
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 77.AC.23694.AB3B64D4; Mon, 31 Jan 2011 14:06:02 +0100 (CET)
Received: from [147.214.183.170] (153.88.115.8) by esessmw0237.eemea.ericsson.se (153.88.115.91) with Microsoft SMTP Server id 8.2.234.1; Mon, 31 Jan 2011 14:06:01 +0100
Message-ID: <4D46B3B9.4050804@ericsson.com>
Date: Mon, 31 Jan 2011 14:06:01 +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>
In-Reply-To: <B4F0B107-4D84-43A5-A091-B6877D24C23B@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: Mon, 31 Jan 2011 13:02:50 -0000

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

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.

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?

We clearly can't, this will be up to human judgment.

I also think it is important that we separate the basic registry rules
from the review guidelines, as they will change. Thus this is a separate
document. One that we should make clear is going to exist.

And as pointed out in other parts of this discussion there are several
ways of challenging the reviewers recommendation resulting in an IANA
decision. First of all is the appeal process. Secondly, is to take it
through the IETF approval process where IETF makes the decision, not IANA.

As I see it, we either leave these high level goals in this document, or
we remove the completely and put everything in a separate document.

I rather leave them in, because I don't seem them changing. Only be
acted up in varying ways over the coming years.

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 paul.hoffman@vpnc.org  Mon Jan 31 06:48:01 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 6F8073A6BFF; Mon, 31 Jan 2011 06:48:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.754
X-Spam-Level: 
X-Spam-Status: No, score=-101.754 tagged_above=-999 required=5 tests=[AWL=0.292, 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 dkn6KIkn7r4Y; Mon, 31 Jan 2011 06:48:00 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id AD2353A67F9; Mon, 31 Jan 2011 06:48:00 -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 p0VEpCcl065541 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 07:51:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D46CC62.1040006@vpnc.org>
Date: Mon, 31 Jan 2011 06:51:14 -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: Lars Eggert <lars.eggert@nokia.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>
In-Reply-To: <B1E38EDF-E78E-47E2-B9A9-D7320A908217@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, IETF discussion list <ietf@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: Mon, 31 Jan 2011 14:48:01 -0000

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

> And I've never witnessed IANA rejecting requests coming through the
> IETF.

This document is about new restrictions for the future, not what has 
happened in the past.

> But even if they did, there is an appeals procedure.

That is slim comfort to a WG that has designed a protocol that has good 
design reasons for needing two ports and, at the last minute is told 
that they either have to re-design from scratch or go through an appeals 
process to justify their design to IANA. It's fine that they have to 
justify it to the IESG (well, fine to me; other greybeards seem to not 
like that so much these days), but there should be no way that IANA can 
say "you cannot get ports assigned because this new RFC says that you 
designed your protocol wrong". If what you say above about "Assignments 
through IETF-stream documents do not go through expert review." is true, 
it should be plainly stated in the introduction to the document.

From lars.eggert@nokia.com  Mon Jan 31 07:03:21 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 86CFE3A6C0C; Mon, 31 Jan 2011 07:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.768
X-Spam-Level: 
X-Spam-Status: No, score=-103.768 tagged_above=-999 required=5 tests=[AWL=-0.169, 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 J3HHYGNYih1W; Mon, 31 Jan 2011 07:03:20 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 684753A6C07; Mon, 31 Jan 2011 07:03:20 -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 p0VF6VWf028591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 17:06:33 +0200
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
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-18-351603736; protocol="application/pkcs7-signature"; micalg=sha1
From: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <4D46CC62.1040006@vpnc.org>
Date: Mon, 31 Jan 2011 17:06:23 +0200
Message-Id: <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.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>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.1082)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mail.fit.nokia.com); Mon, 31 Jan 2011 17:06:28 +0200 (EET)
X-Nokia-AV: Clean
Cc: Cullen Jennings <fluffy@cisco.com>, tsvwg@ietf.org, IETF discussion list <ietf@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: Mon, 31 Jan 2011 15:03:21 -0000

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

Hi,

On 2011-1-31, at 16:51, 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.
>>=20
>> I don't follow. Assignments through IETF-stream documents do not go
>> through expert review.
>=20
> Then this should be made *much* clearer in the document. In fact, the =
document says:
>=20
>   A key element of the procedural streamlining specified in this
>   document is to establish identical assignment procedures for all =
IETF
>   transport protocols.
>=20
> I assumed that "all" meant "all", not "all except those through =
IETF-stream documents"; others might have read it the same way I did.

The sentence you quote isn't related to the issue we're discussing. It =
is intended to say "a goal is that the procedures to get ports and =
service names are the same for UDP, TCP, DCCP and SCTP." (Maybe it would =
be clearer by explicitly naming these protocols in the document.)

But I see the point you're raising. The document should somewhere say =
that "Expert Review" is the procedure used for assignment requests made =
directly to IANA, whereas for documents on the IETF Stream, "IETF =
Consensus" is sufficient to make the assignment. In other words, no =
expert review doesn't really need to happen for those, since IETF Review =
and IESG Approval are at least equivalent.

Did I get that right?

>> But even if they did, there is an appeals procedure.
>=20
> That is slim comfort to a WG that has designed a protocol that has =
good design reasons for needing two ports and, at the last minute is =
told that they either have to re-design from scratch or go through an =
appeals process to justify their design to IANA. It's fine that they =
have to justify it to the IESG (well, fine to me; other greybeards seem =
to not like that so much these days), but there should be no way that =
IANA can say "you cannot get ports assigned because this new RFC says =
that you designed your protocol wrong". If what you say above about =
"Assignments through IETF-stream documents do not go through expert =
review." is true, it should be plainly stated in the introduction to the =
document.

Right. I think the change I outlined above would address this.

Thanks!

Lars=

--Apple-Mail-18-351603736
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
AzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMDEzMTE1MDYyM1owIwYJKoZIhvcNAQkE
MRYEFOhp46BHP6QFd08yJ/ZKjcTrVErZMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQG
EwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5l
dHdvcmsxOzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhIChjKTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlT
aWduIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEGxdPUZzCwUJ8KBiJwH+
bYgwggEFBgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlT
aWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJt
cyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMV
UGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1
YWwgU3Vic2NyaWJlciBDQSAtIEczAhBsXT1GcwsFCfCgYicB/m2IMA0GCSqGSIb3DQEBAQUABIIB
AAAG/Y2RNHh1DdpBUp4+okYG7AwzBGQmN1+do76U0jdwqlgMfMyB/RwpYTO+3zQh79uR2uLtuOOX
htPWKE3mKBduR0WhPSueV+y3aYu+19NWD+YoKg8VAIbbFVop7ZcSX+JDpksGFBICK9OpzUE7y6rG
X9+10FrUtekb/4g+L9eSgR+riCrEJXMwSYm3/RmrO98VG7s0dHq6LP3zsBCxDkIBnNL19KEID4bq
NKuggsKKPdOmEcYWmp5PyY1XDkmfKC2kGcg9uK0+huIGg/TbXuyA9et5KjLyH5PdYV83lP365noA
fNcbzaGWBDUZwem7Bf4ww+2lS7xrsVY22TSHFycAAAAAAAA=

--Apple-Mail-18-351603736--

From paul.hoffman@vpnc.org  Mon Jan 31 07:11:19 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 0E75B3A6B32; Mon, 31 Jan 2011 07:11:16 -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 MKwMntZxMrzm; Mon, 31 Jan 2011 07:11:13 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 1EF243A6AC9; Mon, 31 Jan 2011 07:11:13 -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 p0VFEQ3e066616 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 08:14:26 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D46D1D3.10701@vpnc.org>
Date: Mon, 31 Jan 2011 07:14:27 -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: Lars Eggert <lars.eggert@nokia.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>
In-Reply-To: <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.com>
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: Mon, 31 Jan 2011 15:11:21 -0000

On 1/31/11 7:06 AM, Lars Eggert wrote:
> But I see the point you're raising. The document should somewhere say
> that "Expert Review" is the procedure used for assignment requests
> made directly to IANA, whereas for documents on the IETF Stream,
> "IETF Consensus" is sufficient to make the assignment. In other
> words, no expert review doesn't really need to happen for those,
> since IETF Review and IESG Approval are at least equivalent.
>
> Did I get that right?

Yes, that would greatly reduce the concern about where and when (and how 
often!) the review would happen.

From Even.roni@huawei.com  Sat Jan 29 00:15:47 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 0A2E03A6A44; Sat, 29 Jan 2011 00:15:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.271
X-Spam-Level: 
X-Spam-Status: No, score=-103.271 tagged_above=-999 required=5 tests=[AWL=1.223, 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 a7Ftf-67erRa; Sat, 29 Jan 2011 00:15:42 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id B90C03A6A67; Sat, 29 Jan 2011 00:15:41 -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 <0LFR00FD4Z33FA@szxga03-in.huawei.com>; Sat, 29 Jan 2011 16:18:39 +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 <0LFR00MPGZ337J@szxga03-in.huawei.com>; Sat, 29 Jan 2011 16:18:39 +0800 (CST)
Received: from windows8d787f9 ([109.64.19.90]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LFR0067JZ2UFQ@szxml01-in.huawei.com>; Sat, 29 Jan 2011 16:18:39 +0800 (CST)
Date: Sat, 29 Jan 2011 10:14:16 +0200
From: Roni Even <Even.roni@huawei.com>
Subject: RE: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14
In-reply-to: <07F7D7DED63154409F13298786A2ADC903CD9AA6@EXRAD5.ad.rad.co.il>
To: 'Yaakov Stein' <yaakov_s@rad.com>, draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org, gen-art@ietf.org
Message-id: <08ef01cbbf8c$8a6347c0$9f29d740$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_uXWz0xXwjKpPPgE4dKsxBw)"
Content-language: en-us
Thread-index: Acu6zYUM9zrofD2DQv+vmHiCppfgbADaoU9wAFUUTnA=
References: <03dc01cbbacd$8bff0880$a3fd1980$%roni@huawei.com> <07F7D7DED63154409F13298786A2ADC903CD9AA6@EXRAD5.ad.rad.co.il>
X-Mailman-Approved-At: Mon, 31 Jan 2011 07:49:29 -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: Sat, 29 Jan 2011 08:15:47 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_uXWz0xXwjKpPPgE4dKsxBw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Yaakov,

Yes this is what I mean

Roni

 

From: Yaakov Stein [mailto:yaakov_s@rad.com] 
Sent: Thursday, January 27, 2011 5:47 PM
To: Roni Even; draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org;
gen-art@ietf.org
Cc: 'IETF-Discussion list'
Subject: RE: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14

 

Roni

 

Thanks for the nit-catching.

 

I assume  you RFC5087 not as a reference means you quote RFC5087 not as a
reference.

 

Due to Adrian's DISCUSS we are going to have to respin after the LC;

I will fix all the nits you mention (and Russ' nit as well) at that time.

 

Y(J)S

 

From: Roni Even [mailto:Even.roni@huawei.com] 
Sent: Sunday, January 23, 2011 09:17
To: draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org; gen-art@ietf.org
Cc: 'IETF-Discussion list'
Subject: Gen-ART LC review of draft-ietf-pwe3-oam-msg-map-14

 

Hi,

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-pwe3-oam-msg-map-14

Reviewer: Roni Even

Review Date:2011-1-23

IETF LC End Date: 2011-1-24

IESG Telechat date:

 

Summary: This draft is ready for publication as a Standard track RFC.

 

Major issues:

 

 

Minor issues:

 

 

Nits/editorial comments:

 

1.  The document starts with Contributors and acknowledgments section. I
think that this is not the major reason for the document and suggest moving
these two sections to the end of the document.

2.  In the Abbreviations and Conventions section which includes the
terminology it may be good to reference the terminology from RFC3985.

3.  Towards the end of section 7 and in the beginning of section 11 you
RFC5087 not as a reference while in other places you have it as a reference.
I think it should be written as a reference.

 

 

 


--Boundary_(ID_uXWz0xXwjKpPPgE4dKsxBw)
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:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" 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:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-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;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:304356142;
	mso-list-type:hybrid;
	mso-list-template-ids:-302068210 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;}
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><span =
style=3D'color:#1F497D'>Yaakov,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>Yes this is what I =
mean<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Yaakov Stein [mailto:yaakov_s@rad.com] <br><b>Sent:</b> Thursday, =
January 27, 2011 5:47 PM<br><b>To:</b> Roni Even; =
draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org; =
gen-art@ietf.org<br><b>Cc:</b> 'IETF-Discussion list'<br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-pwe3-oam-msg-map-14<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>Thanks for the =
nit-catching.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>I assume&nbsp; </span>you RFC5087 not as a =
reference <span style=3D'color:#1F497D'>means </span>you quote RFC5087 =
not as a reference<span =
style=3D'color:#1F497D'>.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>Due to Adrian's DISCUSS we are going to have =
to respin after the LC;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>I will fix all the nits you mention (and Russ' =
nit as well) at that time.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'color:#1F497D'>Y(J)S<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Roni Even [mailto:Even.roni@huawei.com] <br><b>Sent:</b> Sunday, January =
23, 2011 09:17<br><b>To:</b> =
draft-ietf-pwe3-oam-msg-map.all@tools.ietf.org; =
gen-art@ietf.org<br><b>Cc:</b> 'IETF-Discussion list'<br><b>Subject:</b> =
Gen-ART LC review of =
draft-ietf-pwe3-oam-msg-map-14<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><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><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Document: <span style=3D'font-family:"Courier =
New"'>draft-ietf-pwe3-oam-msg-map-14<o:p></o:p></span></p><p =
class=3DMsoPlainText>Reviewer: Roni Even<o:p></o:p></p><p =
class=3DMsoPlainText>Review Date:2011&#8211;1&#8211;23<o:p></o:p></p><p =
class=3DMsoPlainText>IETF LC End Date: =
2011&#8211;1&#8211;24<o:p></o:p></p><p class=3DMsoPlainText>IESG =
Telechat date:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Summary: This draft is ready for publication as a =
Standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.25in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Nits/editorial comments:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>The document starts with =
Contributors and acknowledgments section. I think that this is not the =
major reason for the document and suggest moving these two sections to =
the end of the document.<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>In the Abbreviations and =
Conventions section which includes the terminology it may be good to =
reference the terminology from RFC3985.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>Towards the end of =
section 7 and in the beginning of section 11 you RFC5087 not as a =
reference while in other places you have it as a reference. I think it =
should be written as a reference.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>=

--Boundary_(ID_uXWz0xXwjKpPPgE4dKsxBw)--

From fluffy@cisco.com  Mon Jan 31 08:10:53 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 C17D33A6C3F; Mon, 31 Jan 2011 08:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.582
X-Spam-Level: 
X-Spam-Status: No, score=-110.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 Op4uPkcF4THd; Mon, 31 Jan 2011 08:10:45 -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 554D83A6C39; Mon, 31 Jan 2011 08:10:45 -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: AvsEAFtuRk2rR7Ht/2dsb2JhbACkeXOiNJp7hU4EhROHDoNF
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-2.cisco.com with ESMTP; 31 Jan 2011 16:14:00 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0VGDwuU011891; Mon, 31 Jan 2011 16:13:58 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
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: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <4D46D1D3.10701@vpnc.org>
Date: Mon, 31 Jan 2011 09:13:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2152494-8C79-4A0F-951F-B3DB1D274A61@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>
To: Paul Hoffman <paul.hoffman@vpnc.org>, Lars Eggert <lars.eggert@nokia.com>,  tsvwg@ietf.org, IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@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, 31 Jan 2011 16:10:53 -0000

On Jan 31, 2011, at 8:14 , Paul Hoffman wrote:

> On 1/31/11 7:06 AM, Lars Eggert wrote:
> > But I see the point you're raising. The document should somewhere =
say
> > that "Expert Review" is the procedure used for assignment requests
> > made directly to IANA, whereas for documents on the IETF Stream,
> > "IETF Consensus" is sufficient to make the assignment. In other
> > words, no expert review doesn't really need to happen for those,
> > since IETF Review and IESG Approval are at least equivalent.
> >
> > Did I get that right?
>=20
> Yes, that would greatly reduce the concern about where and when (and =
how
> often!) the review would happen.
>=20

Hmm ... I don't agree that solves the issue.=20

Well lets say the request was coming from 3GPP for a protocol they =
designed - why should IANA be able to tell them no but IETF yes.=20

I think the policy issue here is fairly clear. We do not have consensus =
that in all cases that one should not have a second port for security =
(I'm basing this assertion on Magnus read of WG consensus and my read of =
IETF LC consensus). Therefore that should not be a ground for the expert =
reviewer (or IANA) to reject the registration. The document needs to be =
updated to make that clear or it does not reflect consensus. If the =
authors of the draft want to propose text for conditions when it would =
be ok to reject a second port for security purposes and see if they can =
get consensus for that text, that seems perfectly reasonable.=20

I'm sure that some people believe the draft, by using the word =
"strives", actually means that this is not a grounds for rejection but =
given the push back from Lars and Joe, I believe that "strives" means =
that the decision is up to Joe. Given things could be read either ways, =
I think it's fair to ask for the draft to clarify this.=20






From lear@cisco.com  Mon Jan 31 08:24:42 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 6628A3A6827; Mon, 31 Jan 2011 08:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.22
X-Spam-Level: 
X-Spam-Status: No, score=-110.22 tagged_above=-999 required=5 tests=[AWL=0.379, 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 aym9kKrf6bTe; Mon, 31 Jan 2011 08:24:41 -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 E29003A67B6; Mon, 31 Jan 2011 08:24:40 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 31 Jan 2011 16:27:55 +0000
Received: from dhcp-10-61-100-10.cisco.com (dhcp-10-61-100-10.cisco.com [10.61.100.10]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p0VGRsC0015449; Mon, 31 Jan 2011 16:27:54 GMT
Message-ID: <4D46E2FF.7010203@cisco.com>
Date: Mon, 31 Jan 2011 17:27:43 +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: 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>
In-Reply-To: <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Mon, 31 Jan 2011 16:24:42 -0000

On 1/31/11 5:13 PM, Cullen Jennings wrote:
> Hmm ... I don't agree that solves the issue. 
>
> Well lets say the request was coming from 3GPP for a protocol they designed - why should IANA be able to tell them no but IETF yes. 

Who, ultimately, is the steward of this precious resource?  If it is not
the IANA and it is not the IETF, then who?  To say that it is everyone's
responsibility is to avoid responsibility entirely.  Who gets to say
which standards organizations are stewards and which are not?

> I think the policy issue here is fairly clear. We do not have consensus that in all cases that one should not have a second port for security (I'm basing this assertion on Magnus read of WG consensus and my read of IETF LC consensus). Therefore that should not be a ground for the expert reviewer (or IANA) to reject the registration. The document needs to be updated to make that clear or it does not reflect consensus. If the authors of the draft want to propose text for conditions when it would be ok to reject a second port for security purposes and see if they can get consensus for that text, that seems perfectly reasonable. 

This is a VERY VERY dangerous approach you propose, Cullen.  It is akin
to saying, "you can think about security later, because we'll have to
give you a port for it later."  We don't want to be saying that.


From fluffy@cisco.com  Mon Jan 31 08:30:05 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 50FE63A6C3E; Mon, 31 Jan 2011 08:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.583
X-Spam-Level: 
X-Spam-Status: No, score=-110.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 h4UTNZ+BFXKH; Mon, 31 Jan 2011 08:30:03 -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 DCC863A6C21; Mon, 31 Jan 2011 08:30:02 -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: AvsEAAtzRk2rR7Hu/2dsb2JhbACkeXOiOpsBhU4EhROHDoNF
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-2.cisco.com with ESMTP; 31 Jan 2011 16:33:17 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0VGXFgj000531; Mon, 31 Jan 2011 16:33: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=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <C96AF782.2BAD0%michelle.cotton@icann.org>
Date: Mon, 31 Jan 2011 09:33:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEF9689B-E426-45E1-8F72-BDAB80F62538@cisco.com>
References: <C96AF782.2BAD0%michelle.cotton@icann.org>
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.1082)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, The 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, 31 Jan 2011 16:30:05 -0000

So IANA has a huge amount of technical expertise and takes maintaing the =
registries very seriously. I've seen them catch technical mistakes that =
made all the way through WG and IESG review. I've got huge respect for =
technical competence of IANA and in particular Michelle. So I'm not =
questions that but  I don't recall seeing them override an expert on a =
technical issue. I'd be happy to hear of examples but lets consider the =
example I am actually concerned about here.=20
=20
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.=20

So Michelle, in that case, would you be willing to override Joe? I'm =
sure you would be willing to help facilitate any conversations, bring in =
other people such as ADs that can help etc. I was sort of working on the =
assumption that you would not override Joe in this case and the the only =
path forward would be an appeal to Lars but perhaps that is just a bad =
assumption on my part. Appeals are really the worst way possible to =
resolve things. I have a hard time imagining that IANA would want to =
engage in a technical discussion to resolve this and instead relies on =
the expert reviewer. I'll note that the expert review may report to IANA =
but they are selected by and replaced by the IESG.=20

The important point here is that I really don't care if it is Joe or =
IANA that is saying no - I think this document should be clear that this =
BCP can not be used as grounds for rejecting the request for a second =
port for security.=20



On Jan 30, 2011, at 12:09 , Michelle Cotton wrote:

> David has said this well.  Thank you.
>=20
> Please let me know if there are any other questions.
>=20
> --Michelle
>=20
>=20
>=20
> On 1/30/11 10:52 AM, "David Conrad" <drc@virtualized.org> wrote:
>=20
>> Cullen,
>>=20
>> On Jan 29, 2011, at 8:54 PM, Cullen Jennings 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.
>>>=20
>>> 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.
>>=20
>>=20
>> Joe is closer. =20
>>=20
>> In general, IANA staff are not technical experts in any of the wide =
variety of
>> areas for which they are asked to provide registry services.  As =
such, they
>> rely on technical experts to provide input/advice/recommendations.  =
In the
>> past, there were some very rare cases in which the advice provided by =
the
>> technical experts was deemed insufficient and IANA staff looked to =
the ADs or
>> the IESG for additional input.  However, at least historically, IANA =
staff
>> viewed the maintenance of the registries as their responsibility (at =
the
>> direction of the IESG), not the technical experts' responsibility. I =
would be
>> surprised if this had changed.
>>=20
>> Regards,
>> -drc
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20


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



From paul.hoffman@vpnc.org  Mon Jan 31 08:37:38 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 4D7E33A67F0; Mon, 31 Jan 2011 08:37:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.755
X-Spam-Level: 
X-Spam-Status: No, score=-101.755 tagged_above=-999 required=5 tests=[AWL=0.291, 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 xbU4jGvOtuT4; Mon, 31 Jan 2011 08:37:37 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 096123A67B4; Mon, 31 Jan 2011 08:37:37 -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 p0VGeTlB070327 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 09:40:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D46E5FF.5040706@vpnc.org>
Date: Mon, 31 Jan 2011 08:40:31 -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>	<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>
In-Reply-To: <F2152494-8C79-4A0F-951F-B3DB1D274A61@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 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: Mon, 31 Jan 2011 16:37:38 -0000

On 1/31/11 8:13 AM, Cullen Jennings wrote:
> Hmm ... I don't agree that solves the issue.
>
> Well lets say the request was coming from 3GPP for a protocol they
> designed - why should IANA be able to tell them no but IETF yes.

Because IANA is responsible for maintaining the usefulness of the 
registry. Part of that is "don't hand out ports unnecessarily", and part 
of that is "hand out ports without hassle to those who are trusted to 
ask for them wisely". If 3GPP can show it belongs in the latter 
category, great. Until then, the only body that is there is "IETF 
consensus" plus maybe "IESG pressure".

> I think the policy issue here is fairly clear. We do not have
> consensus that in all cases that one should not have a second port
> for security (I'm basing this assertion on Magnus read of WG
> consensus and my read of IETF LC consensus). Therefore that should
> not be a ground for the expert reviewer (or IANA) to reject the
> registration. The document needs to be updated to make that clear or
> it does not reflect consensus. If the authors of the draft want to
> propose text for conditions when it would be ok to reject a second
> port for security purposes and see if they can get consensus for that
> text, that seems perfectly reasonable.
>
> I'm sure that some people believe the draft, by using the word
> "strives", actually means that this is not a grounds for rejection
> but given the push back from Lars and Joe, I believe that "strives"
> means that the decision is up to Joe. Given things could be read
> either ways, I think it's fair to ask for the draft to clarify this.

Fully agree.

From magnus.westerlund@ericsson.com  Mon Jan 31 08:37:55 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 98D873A6C40; Mon, 31 Jan 2011 08:37:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.487
X-Spam-Level: 
X-Spam-Status: No, score=-106.487 tagged_above=-999 required=5 tests=[AWL=0.112, 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 9LTpZ94nDruT; Mon, 31 Jan 2011 08:37:54 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 05A883A6C43; Mon, 31 Jan 2011 08:37:53 -0800 (PST)
X-AuditID: c1b4fb39-b7cfbae000005c8e-42-4d46e623e149
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id A1.49.23694.326E64D4; Mon, 31 Jan 2011 17:41:08 +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; Mon, 31 Jan 2011 17:41:07 +0100
Message-ID: <4D46E623.3080602@ericsson.com>
Date: Mon, 31 Jan 2011 17:41:07 +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>
In-Reply-To: <F2152494-8C79-4A0F-951F-B3DB1D274A61@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: Mon, 31 Jan 2011 16:37:55 -0000

Cullen Jennings skrev 2011-01-31 17:13:

> Well lets say the request was coming from 3GPP for a protocol they designed - why should IANA be able to tell them no but IETF yes. 

I am not certain I understand what your issue is here. Is it that they
can come to different conclusions, and that IETF can decided to override
the expert review team? I think that is the logical conclusion, as the
IETF's decision will have gone through a consensus process. One which
the expert can provide their view into this.

> 
> I think the policy issue here is fairly clear. We do not have consensus that in all cases that one should not have a second port for security (I'm basing this assertion on Magnus read of WG consensus and my read of IETF LC consensus). Therefore that should not be a ground for the expert reviewer (or IANA) to reject the registration. The document needs to be updated to make that clear or it does not reflect consensus. If the authors of the draft want to propose text for conditions when it would be ok to reject a second port for security purposes and see if they can get consensus for that text, that seems perfectly reasonable. 


My reading of the WG last call consensus is that nobody is disagreeing
with the goal of trying minimize the port consumption. My interpretation
is that we do need to state that goal in the document. And the only way
of achieving this is to try to minimize the consumption by each protocol
that requires a registration. That includes trying to get all
multiplexing into that single socket, or at least use it for agreeing on
dynamic range port for this protocol.

> 
> I'm sure that some people believe the draft, by using the word "strives", actually means that this is not a grounds for rejection but given the push back from Lars and Joe, I believe that "strives" means that the decision is up to Joe. Given things could be read either ways, I think it's fair to ask for the draft to clarify this. 

It is a high level goal to minimize the port space consumption. I do
believe there is strong consensus for this. And I believe that the only
way of ensuring that this goal is meet is to take a pretty hard stance
against frivolous use of ports.

Thus, I still think there is clear grounds for rejecting requests for
multiple ports based on not sufficiently motivating why it is impossible
to not use one port. I do agree that these guidelines should be
documented, and that is the plans as far as I know.

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 michelle.cotton@icann.org  Mon Jan 31 08:52:47 2011
Return-Path: <michelle.cotton@icann.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 5F4453A6C48; Mon, 31 Jan 2011 08:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.468
X-Spam-Level: 
X-Spam-Status: No, score=-106.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 GVc7bqBDTW-P; Mon, 31 Jan 2011 08:52:42 -0800 (PST)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by core3.amsl.com (Postfix) with ESMTP id 261133A67B4; Mon, 31 Jan 2011 08:52:42 -0800 (PST)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Mon, 31 Jan 2011 08:55:56 -0800
From: Michelle Cotton <michelle.cotton@icann.org>
To: Cullen Jennings <fluffy@cisco.com>
Date: Mon, 31 Jan 2011 08:55:53 -0800
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: AcvBZJ9mWsU96xX0SG+vL8gbuhiBkgAAxkG5
Message-ID: <C96C2999.2BB2C%michelle.cotton@icann.org>
In-Reply-To: <BEF9689B-E426-45E1-8F72-BDAB80F62538@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.8.0.101117
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, The 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, 31 Jan 2011 16:52:47 -0000

Cullen,

We do have some technical expertise within the IANA staff, however our
expertise is more aligned with the process of creating and maintaining
registries.  Part of that includes relying on the experts that the IESG
designates to make the decisions for requests that utilize the "Expert
Review" policy in RFC 5226.

In the past, if there is strong disagreement from an expert and the
requester disagrees, we have brought the Transport Area Directors into the
communications to see if all parties can come to an agreement.  In almost
all cases, this is where a final decision is made.  If that set of folks ca=
n
not come to a conclusion, we then would default to going to the IESG.  With
all requests, if there is any uncertainty as to what decision should be
made, we go to the IESG for guidance.

We do rely on the technical expertise of the appointed experts for all
registries, but we ALWAYS have the possibility to seek guidance form the
IESG.

I don't believe we have ever had an official appeals with ports (Knocking o=
n
wood really hard!).

Does that help?

--Michelle



On 1/31/11 8:33 AM, "Cullen Jennings" <fluffy@cisco.com> wrote:

>=20
> So IANA has a huge amount of technical expertise and takes maintaing the
> registries very seriously. I've seen them catch technical mistakes that m=
ade
> all the way through WG and IESG review. I've got huge respect for technic=
al
> competence of IANA and in particular Michelle. So I'm not questions that =
but
> I don't recall seeing them override an expert on a technical issue. I'd b=
e
> happy to hear of examples but lets consider the example I am actually
> concerned about here.
> =20
> I put in a request for a latency sensitive protocol that uses DTLS and re=
quest
> a different port for the secure version. Joe as expert review says we sho=
uld
> 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 o=
f the
> protocol. Joe does not agree.
>=20
> So Michelle, in that case, would you be willing to override Joe? I'm sure=
 you
> would be willing to help facilitate any conversations, bring in other peo=
ple
> such as ADs that can help etc. I was sort of working on the assumption th=
at
> you would not override Joe in this case and the the only path forward wou=
ld be
> an appeal to Lars but perhaps that is just a bad assumption on my part.
> Appeals are really the worst way possible to resolve things. I have a har=
d
> time imagining that IANA would want to engage in a technical discussion t=
o
> resolve this and instead relies on the expert reviewer. I'll note that th=
e
> expert review may report to IANA but they are selected by and replaced by=
 the
> IESG.=20
>=20
> The important point here is that I really don't care if it is Joe or IANA=
 that
> is saying no - I think this document should be clear that this BCP can no=
t be
> used as grounds for rejecting the request for a second port for security.
>=20
>=20
>=20
> On Jan 30, 2011, at 12:09 , Michelle Cotton wrote:
>=20
>> David has said this well.  Thank you.
>>=20
>> Please let me know if there are any other questions.
>>=20
>> --Michelle
>>=20
>>=20
>>=20
>> On 1/30/11 10:52 AM, "David Conrad" <drc@virtualized.org> wrote:
>>=20
>>> Cullen,
>>>=20
>>> On Jan 29, 2011, at 8:54 PM, Cullen Jennings 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.
>>>>=20
>>>> 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 o=
f the
>>>> expert reviewer, they might ask the AD to override but short of that t=
hey
>>>> pretty much do whatever the expert says.
>>>=20
>>>=20
>>> Joe is closer.=20
>>>=20
>>> In general, IANA staff are not technical experts in any of the wide var=
iety
>>> of
>>> areas for which they are asked to provide registry services.  As such, =
they
>>> rely on technical experts to provide input/advice/recommendations.  In =
the
>>> past, there were some very rare cases in which the advice provided by t=
he
>>> technical experts was deemed insufficient and IANA staff looked to the =
ADs
>>> or
>>> the IESG for additional input.  However, at least historically, IANA st=
aff
>>> viewed the maintenance of the registries as their responsibility (at th=
e
>>> direction of the IESG), not the technical experts' responsibility. I wo=
uld
>>> be
>>> surprised if this had changed.
>>>=20
>>> Regards,
>>> -drc
>>>=20
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>=20
>=20
> Cullen Jennings
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20


From touch@isi.edu  Mon Jan 31 09:15:00 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 B9A623A67B7; Mon, 31 Jan 2011 09:15:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, 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 W5xxmejejXri; Mon, 31 Jan 2011 09:15:00 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id EEC0A3A67B4; Mon, 31 Jan 2011 09:14:59 -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 vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p0VHGmQX014839 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 31 Jan 2011 09:16:58 -0800 (PST)
Message-ID: <4D46EE80.8090906@isi.edu>
Date: Mon, 31 Jan 2011 09:16:48 -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: Lars Eggert <lars.eggert@nokia.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>
In-Reply-To: <3EEDEA1C-C34B-4F39-8E6E-AEDE50C1E504@nokia.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>, 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: Mon, 31 Jan 2011 17:15:00 -0000

Lars,

On 1/31/2011 7:06 AM, Lars Eggert wrote:
> Hi,
>
> On 2011-1-31, at 16:51, 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. 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.
>
> The sentence you quote isn't related to the issue we're discussing. It is intended to say "a goal is that the procedures to get ports and service names are the same for UDP, TCP, DCCP and SCTP." (Maybe it would be clearer by explicitly naming these protocols in the document.)
>
> But I see the point you're raising. The document should somewhere say that "Expert Review" is the procedure used for assignment requests made directly to IANA, whereas for documents on the IETF Stream, "IETF Consensus" is sufficient to make the assignment. In other words, no expert review doesn't really need to happen for those, since IETF Review and IESG Approval are at least equivalent.

RFC2434 already gives IANA these options.

Perhaps - at best - we should include a ref to that.

However, this document is not focused at changing what RFC2434 says, and 
the above statement, IMO, does.

That's another can of worms, and should be reserved for a different 
document.

Joe


From touch@isi.edu  Mon Jan 31 09:16:14 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 B4EDD3A69A9; Mon, 31 Jan 2011 09:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 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 z1hV47zPBtZW; Mon, 31 Jan 2011 09:16:13 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id E167C3A6844; Mon, 31 Jan 2011 09:16:13 -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 vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p0VHIkLs015329 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 31 Jan 2011 09:18:56 -0800 (PST)
Message-ID: <4D46EEF6.9010209@isi.edu>
Date: Mon, 31 Jan 2011 09:18:46 -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>
In-Reply-To: <4D46CC62.1040006@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>, 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: Mon, 31 Jan 2011 17:16:14 -0000

The procedures that are specified - for ALL assignments - are the 
PROCEDURES - the word itself is used specifically in the heading of 
section 8.

That does not refer to the "principles" - again for which there are more 
than sufficient wiggle words, and which already cite existing RFCs that 
have provisions that already limit the role of Expert Review and allow 
for appeals.

Again - this document is NOT focused on those principles. IANA - and 
more specifically its review team - is NOT required to publish any such 
principles (as per RFC 5226). If they continue to be a source of 
contention, then section 7 should be removed.

Joe

On 1/31/2011 6:51 AM, 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. 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.
>
>> And I've never witnessed IANA rejecting requests coming through the
>> IETF.
>
> This document is about new restrictions for the future, not what has
> happened in the past.
>
>> But even if they did, there is an appeals procedure.
>
> That is slim comfort to a WG that has designed a protocol that has good
> design reasons for needing two ports and, at the last minute is told
> that they either have to re-design from scratch or go through an appeals
> process to justify their design to IANA. It's fine that they have to
> justify it to the IESG (well, fine to me; other greybeards seem to not
> like that so much these days), but there should be no way that IANA can
> say "you cannot get ports assigned because this new RFC says that you
> designed your protocol wrong". If what you say above about "Assignments
> through IETF-stream documents do not go through expert review." is true,
> it should be plainly stated in the introduction to the document.

From touch@isi.edu  Mon Jan 31 09:23: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 81ED03A67F0; Mon, 31 Jan 2011 09:23:11 -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 68YUQNe9SPOR; Mon, 31 Jan 2011 09:23:09 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id D8CCD3A699E; Mon, 31 Jan 2011 09:23:09 -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 vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p0VHPNh1016357 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 31 Jan 2011 09:25:33 -0800 (PST)
Message-ID: <4D46F083.9090500@isi.edu>
Date: Mon, 31 Jan 2011 09:25:23 -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: Lars Eggert <lars.eggert@nokia.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> <4D46EE80.8090906@isi.edu>
In-Reply-To: <4D46EE80.8090906@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Cullen Jennings <fluffy@cisco.com>, 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: Mon, 31 Jan 2011 17:23:11 -0000

On 1/31/2011 9:16 AM, Joe Touch wrote:
> Lars,
>
> On 1/31/2011 7:06 AM, Lars Eggert wrote:
>> Hi,
>>
>> On 2011-1-31, at 16:51, 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. 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.
>>
>> The sentence you quote isn't related to the issue we're discussing. It
>> is intended to say "a goal is that the procedures to get ports and
>> service names are the same for UDP, TCP, DCCP and SCTP." (Maybe it
>> would be clearer by explicitly naming these protocols in the document.)
>>
>> But I see the point you're raising. The document should somewhere say
>> that "Expert Review" is the procedure used for assignment requests
>> made directly to IANA, whereas for documents on the IETF Stream, "IETF
>> Consensus" is sufficient to make the assignment. In other words, no
>> expert review doesn't really need to happen for those, since IETF
>> Review and IESG Approval are at least equivalent.
>
> RFC2434 already gives IANA these options.

As does RFC 5226 - its update (there is no substantive change between 
the two in this regard, FWIW).

> Perhaps - at best - we should include a ref to that.

And 5226 is already clearly cited.

No further action should be required.

Joe

> However, this document is not focused at changing what RFC2434 says, and
> the above statement, IMO, does.
>
> That's another can of worms, and should be reserved for a different
> document.
>
> Joe

From fluffy@cisco.com  Mon Jan 31 09:36:51 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 03D193A6977; Mon, 31 Jan 2011 09:36:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.583
X-Spam-Level: 
X-Spam-Status: No, score=-110.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 E+HgLik5gDUG; Mon, 31 Jan 2011 09:36:49 -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 256033A67B6; Mon, 31 Jan 2011 09:36:49 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADeDRk2rR7H+/2dsb2JhbACkeXOiOpsQhU4EhROHDoNF
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 31 Jan 2011 17:39:50 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0VHdmgZ020743; Mon, 31 Jan 2011 17:39:49 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: <C96C2999.2BB2C%michelle.cotton@icann.org>
Date: Mon, 31 Jan 2011 10:39:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DF650F5-A5DA-4AB6-9553-40FE38CE6175@cisco.com>
References: <C96C2999.2BB2C%michelle.cotton@icann.org>
To: Michelle Cotton <michelle.cotton@icann.org>
X-Mailer: Apple Mail (2.1082)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF discussion list <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, The 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, 31 Jan 2011 17:36:51 -0000

Thanks - yes that makes it clear and I like the way IANA handles all of =
this.

On Jan 31, 2011, at 9:55 , Michelle Cotton wrote:

> Cullen,
>=20
> We do have some technical expertise within the IANA staff, however our
> expertise is more aligned with the process of creating and maintaining
> registries.  Part of that includes relying on the experts that the =
IESG
> designates to make the decisions for requests that utilize the "Expert
> Review" policy in RFC 5226.
>=20
> In the past, if there is strong disagreement from an expert and the
> requester disagrees, we have brought the Transport Area Directors into =
the
> communications to see if all parties can come to an agreement.  In =
almost
> all cases, this is where a final decision is made.  If that set of =
folks can
> not come to a conclusion, we then would default to going to the IESG.  =
With
> all requests, if there is any uncertainty as to what decision should =
be
> made, we go to the IESG for guidance.
>=20
> We do rely on the technical expertise of the appointed experts for all
> registries, but we ALWAYS have the possibility to seek guidance form =
the
> IESG.
>=20
> I don't believe we have ever had an official appeals with ports =
(Knocking on
> wood really hard!).
>=20
> Does that help?
>=20
> --Michelle
>=20
>=20
>=20
> On 1/31/11 8:33 AM, "Cullen Jennings" <fluffy@cisco.com> wrote:
>=20
>>=20
>> So IANA has a huge amount of technical expertise and takes maintaing =
the
>> registries very seriously. I've seen them catch technical mistakes =
that made
>> all the way through WG and IESG review. I've got huge respect for =
technical
>> competence of IANA and in particular Michelle. So I'm not questions =
that but
>> I don't recall seeing them override an expert on a technical issue. =
I'd be
>> happy to hear of examples but lets consider the example I am actually
>> concerned about here.
>>=20
>> 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.
>>=20
>> So Michelle, in that case, would you be willing to override Joe? I'm =
sure you
>> would be willing to help facilitate any conversations, bring in other =
people
>> such as ADs that can help etc. I was sort of working on the =
assumption that
>> you would not override Joe in this case and the the only path forward =
would be
>> an appeal to Lars but perhaps that is just a bad assumption on my =
part.
>> Appeals are really the worst way possible to resolve things. I have a =
hard
>> time imagining that IANA would want to engage in a technical =
discussion to
>> resolve this and instead relies on the expert reviewer. I'll note =
that the
>> expert review may report to IANA but they are selected by and =
replaced by the
>> IESG.=20
>>=20
>> The important point here is that I really don't care if it is Joe or =
IANA that
>> is saying no - I think this document should be clear that this BCP =
can not be
>> used as grounds for rejecting the request for a second port for =
security.
>>=20
>>=20
>>=20
>> On Jan 30, 2011, at 12:09 , Michelle Cotton wrote:
>>=20
>>> David has said this well.  Thank you.
>>>=20
>>> Please let me know if there are any other questions.
>>>=20
>>> --Michelle
>>>=20
>>>=20
>>>=20
>>> On 1/30/11 10:52 AM, "David Conrad" <drc@virtualized.org> wrote:
>>>=20
>>>> Cullen,
>>>>=20
>>>> On Jan 29, 2011, at 8:54 PM, Cullen Jennings 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.
>>>>>=20
>>>>> 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.
>>>>=20
>>>>=20
>>>> Joe is closer.=20
>>>>=20
>>>> In general, IANA staff are not technical experts in any of the wide =
variety
>>>> of
>>>> areas for which they are asked to provide registry services.  As =
such, they
>>>> rely on technical experts to provide input/advice/recommendations.  =
In the
>>>> past, there were some very rare cases in which the advice provided =
by the
>>>> technical experts was deemed insufficient and IANA staff looked to =
the ADs
>>>> or
>>>> the IESG for additional input.  However, at least historically, =
IANA staff
>>>> viewed the maintenance of the registries as their responsibility =
(at the
>>>> direction of the IESG), not the technical experts' responsibility. =
I would
>>>> be
>>>> surprised if this had changed.
>>>>=20
>>>> Regards,
>>>> -drc
>>>>=20
>>>> _______________________________________________
>>>> Ietf mailing list
>>>> Ietf@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf
>>>=20
>>=20
>>=20
>> Cullen Jennings
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>=20
>>=20
>=20


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



From fluffy@cisco.com  Mon Jan 31 09:41: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 90C213A6977; Mon, 31 Jan 2011 09:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.583
X-Spam-Level: 
X-Spam-Status: No, score=-110.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 2yJszrRVSqii; Mon, 31 Jan 2011 09:41:15 -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 BDFA33A6807; Mon, 31 Jan 2011 09:41:15 -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: AvsEAISDRk2rR7Hu/2dsb2JhbACkeXOiPJsQhU4EhROHDoNF
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 31 Jan 2011 17:44:30 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0VHiSJH013208; Mon, 31 Jan 2011 17:44:29 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: <4D46E623.3080602@ericsson.com>
Date: Mon, 31 Jan 2011 10:44:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E89C43A-EB2A-4DAB-9B12-A740612783E8@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>
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" <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, 31 Jan 2011 17:41:16 -0000

On Jan 31, 2011, at 9:41 , Magnus Westerlund wrote:

> Cullen Jennings skrev 2011-01-31 17:13:
>=20
>> Well lets say the request was coming from 3GPP for a protocol they =
designed - why should IANA be able to tell them no but IETF yes.=20
>=20
> I am not certain I understand what your issue is here. Is it that they
> can come to different conclusions, and that IETF can decided to =
override
> the expert review team? I think that is the logical conclusion, as the
> IETF's decision will have gone through a consensus process. One which
> the expert can provide their view into this.
>=20
>>=20
>> I think the policy issue here is fairly clear. We do not have =
consensus that in all cases that one should not have a second port for =
security (I'm basing this assertion on Magnus read of WG consensus and =
my read of IETF LC consensus). Therefore that should not be a ground for =
the expert reviewer (or IANA) to reject the registration. The document =
needs to be updated to make that clear or it does not reflect consensus. =
If the authors of the draft want to propose text for conditions when it =
would be ok to reject a second port for security purposes and see if =
they can get consensus for that text, that seems perfectly reasonable.=20=

>=20
>=20
> My reading of the WG last call consensus is that nobody is disagreeing
> with the goal of trying minimize the port consumption. My =
interpretation
> is that we do need to state that goal in the document. And the only =
way
> of achieving this is to try to minimize the consumption by each =
protocol
> that requires a registration. That includes trying to get all
> multiplexing into that single socket, or at least use it for agreeing =
on
> dynamic range port for this protocol.
>=20
>>=20
>> I'm sure that some people believe the draft, by using the word =
"strives", actually means that this is not a grounds for rejection but =
given the push back from Lars and Joe, I believe that "strives" means =
that the decision is up to Joe. Given things could be read either ways, =
I think it's fair to ask for the draft to clarify this.=20
>=20
> It is a high level goal to minimize the port space consumption. I do
> believe there is strong consensus for this. And I believe that the =
only
> way of ensuring that this goal is meet is to take a pretty hard stance
> against frivolous use of ports.
>=20
> Thus, I still think there is clear grounds for rejecting requests for
> multiple ports based on not sufficiently motivating why it is =
impossible
> to not use one port. I do agree that these guidelines should be
> documented, and that is the plans as far as I know.

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




From fluffy@cisco.com  Mon Jan 31 09:48:39 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 5D3F03A6ADF; Mon, 31 Jan 2011 09:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.583
X-Spam-Level: 
X-Spam-Status: No, score=-110.583 tagged_above=-999 required=5 tests=[AWL=0.016, 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 mqZjDtSro0qH; Mon, 31 Jan 2011 09:48:38 -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 450043A6844; Mon, 31 Jan 2011 09:48:38 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-2.cisco.com with ESMTP; 31 Jan 2011 17:51:53 +0000
Received: from [192.168.4.3] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0VHppL7003932; Mon, 31 Jan 2011 17:51:52 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: <4D46E2FF.7010203@cisco.com>
Date: Mon, 31 Jan 2011 10:51:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <768DE9F6-FC0B-49B0-8244-0D97CD7BD2DA@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> <4D46E2FF.7010203@cisco.com>
To: Eliot Lear <lear@cisco.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: Mon, 31 Jan 2011 17:48:39 -0000

So first, we already have a BCP that says  more or less all protocols =
must implement a secure version but deployment is optional. This is a =
good BCP, and it comes from the right area to say that - security. It's =
probably impacts design work in working groups more than any other BCP. =
It has IETF consensus. The IESG holds protocols to this.=20

Now - I am at loss to see why forcing people to use one port will make =
it more likely to have secure protocols. This seems crazy.  Please do =
enlighten me.

And on the topic, I'm still looking forward to an explanation of how the =
current CoAP design stomping all over the TLS code points would be an =
acceptable design.=20


On Jan 31, 2011, at 9:27 , Eliot Lear wrote:

>=20
>=20
> On 1/31/11 5:13 PM, Cullen Jennings wrote:
>> Hmm ... I don't agree that solves the issue.=20
>>=20
>> Well lets say the request was coming from 3GPP for a protocol they =
designed - why should IANA be able to tell them no but IETF yes.=20
>=20
> Who, ultimately, is the steward of this precious resource?  If it is =
not
> the IANA and it is not the IETF, then who?  To say that it is =
everyone's
> responsibility is to avoid responsibility entirely.  Who gets to say
> which standards organizations are stewards and which are not?
>=20
>> I think the policy issue here is fairly clear. We do not have =
consensus that in all cases that one should not have a second port for =
security (I'm basing this assertion on Magnus read of WG consensus and =
my read of IETF LC consensus). Therefore that should not be a ground for =
the expert reviewer (or IANA) to reject the registration. The document =
needs to be updated to make that clear or it does not reflect consensus. =
If the authors of the draft want to propose text for conditions when it =
would be ok to reject a second port for security purposes and see if =
they can get consensus for that text, that seems perfectly reasonable.=20=

>=20
> This is a VERY VERY dangerous approach you propose, Cullen.  It is =
akin
> to saying, "you can think about security later, because we'll have to
> give you a port for it later."  We don't want to be saying that.
>=20


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



From lear@cisco.com  Mon Jan 31 09:53:50 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 70FCB3A69A9; Mon, 31 Jan 2011 09:53:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.226
X-Spam-Level: 
X-Spam-Status: No, score=-110.226 tagged_above=-999 required=5 tests=[AWL=0.373, 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 31HQryoJ+70J; Mon, 31 Jan 2011 09:53:48 -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 14F993A6844; Mon, 31 Jan 2011 09:53:46 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 31 Jan 2011 17:57:01 +0000
Received: from dhcp-10-61-100-10.cisco.com (dhcp-10-61-100-10.cisco.com [10.61.100.10]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p0VHv0of006773; Mon, 31 Jan 2011 17:57:00 GMT
Message-ID: <4D46F7E1.8040601@cisco.com>
Date: Mon, 31 Jan 2011 18:56:49 +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: 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> <4D46E2FF.7010203@cisco.com> <768DE9F6-FC0B-49B0-8244-0D97CD7BD2DA@cisco.com>
In-Reply-To: <768DE9F6-FC0B-49B0-8244-0D97CD7BD2DA@cisco.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Mon, 31 Jan 2011 17:53:50 -0000

On 1/31/11 6:51 PM, Cullen Jennings wrote:
> So first, we already have a BCP that says  more or less all protocols must implement a secure version but deployment is optional. This is a good BCP, and it comes from the right area to say that - security. It's probably impacts design work in working groups more than any other BCP. It has IETF consensus. The IESG holds protocols to this. 

But this isn't only about IETF process.  You just asked about why the
IETF is special and why 3GPP shouldn't be treated on equal footing. 
Well, then what about ITU, ISO, W3C, and Joe's Standards Body?

> Now - I am at loss to see why forcing people to use one port will make it more likely to have secure protocols. This seems crazy.  Please do enlighten me.

The vast majority of the requests I see have 0 security built in until I
ask the question.  A few come back with a plan.  Take away that lever
and I don't even get to ask the question.
> And on the topic, I'm still looking forward to an explanation of how the current CoAP design stomping all over the TLS code points would be an acceptable design. 

I missed a step there?  CoAP?



From twalsh@juniper.net  Mon Jan 31 10:24:43 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 17DEF3A6A7A for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 10:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.475
X-Spam-Level: 
X-Spam-Status: No, score=-106.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 88mmCkvd4SOE for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 10:24:42 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by core3.amsl.com (Postfix) with ESMTP id 0BDC53A6A6F for <ietf@ietf.org>; Mon, 31 Jan 2011 10:24:41 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTUb/LIqV45KDYDuGNuX2Wvq/TuLukas9@postini.com; Mon, 31 Jan 2011 10:27:57 PST
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 31 Jan 2011 10:19:38 -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; Mon, 31 Jan 2011 13:19:37 -0500
From: Thomas Walsh <twalsh@juniper.net>
To: IETF discussion list <ietf@ietf.org>
Date: Mon, 31 Jan 2011 13:19:36 -0500
Subject: FW: NomCom 2010-2011: IESG Appointments 
Thread-Topic: NomCom 2010-2011: IESG Appointments 
Thread-Index: AcvBcsfTKhnqwdI+S4uAPB8E7dQLTAAAI7lw
Message-ID: <A4C6A166C36F5F40A5767E6F66358FC092E06081E5@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: Mon, 31 Jan 2011 18:24:43 -0000

-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org=
] On Behalf Of NomCom Chair
Sent: Monday, January 31, 2011 1:11 PM
To: IETF Announcement list
Subject: NomCom 2010-2011: IESG Appointments=20

Hi Folks,

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

The following have been selected to serve as ADs by the nominating=20
committee for the open IESG positions and confirmed by the IAB in their=20
role as confirming body:=20

GEN/IETF Chair: Russ Housley=20
Applications: Pete Resnick=20
Internet: Ralph Droms=20
Operations and Management: Ron Bonica=20
Real-time Applications and Infrastructure: Robert Sparks=20
Routing: Adrian Farrel=20
Security: Stephen Farrell=20
Transport: Wesley Eddy=20

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 IESG.=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 touch@isi.edu  Mon Jan 31 10:39: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 45F313A6B01; Mon, 31 Jan 2011 10:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.815
X-Spam-Level: 
X-Spam-Status: No, score=-101.815 tagged_above=-999 required=5 tests=[AWL=-0.612, BAYES_00=-2.599, 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 W9B+Oj9YXroE; Mon, 31 Jan 2011 10:39:14 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 791933A6ABC; Mon, 31 Jan 2011 10:39:14 -0800 (PST)
Received: from [192.168.1.91] (pool-71-105-81-169.lsanca.dsl-w.verizon.net [71.105.81.169]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id p0VIfjQj000932 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 31 Jan 2011 10:41:55 -0800 (PST)
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> <4D46EE80.8090906@isi.edu> <4D46F083.9090500@isi.edu>
In-Reply-To: <4D46F083.9090500@isi.edu>
Mime-Version: 1.0 (iPad Mail 8C148)
Content-Type: text/plain; charset=us-ascii
Message-Id: <86B08EA1-476E-487A-BDB3-655A60680254@isi.edu>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (8C148)
From: 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
Date: Mon, 31 Jan 2011 10:42:03 -0800
To: Joe Touch <touch@isi.edu>
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" <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: Mon, 31 Jan 2011 18:39:15 -0000

Fwiw please see sec 8.1 of our doc which states which procedures of RFC 5226=
 are specified for each range, and already allows IESG approval as a path fo=
r user ports.=20

Joe

On Jan 31, 2011, at 9:25 AM, Joe Touch <touch@isi.edu> wrote:

>=20
>=20
> On 1/31/2011 9:16 AM, Joe Touch wrote:
>> Lars,
>>=20
>> On 1/31/2011 7:06 AM, Lars Eggert wrote:
>>> Hi,
>>>=20
>>> On 2011-1-31, at 16:51, 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.
>>>>>=20
>>>>> I don't follow. Assignments through IETF-stream documents do not go
>>>>> through expert review.
>>>>=20
>>>> Then this should be made *much* clearer in the document. In fact, the
>>>> document says:
>>>>=20
>>>> A key element of the procedural streamlining specified in this
>>>> document is to establish identical assignment procedures for all IETF
>>>> transport protocols.
>>>>=20
>>>> I assumed that "all" meant "all", not "all except those through
>>>> IETF-stream documents"; others might have read it the same way I did.
>>>=20
>>> The sentence you quote isn't related to the issue we're discussing. It
>>> is intended to say "a goal is that the procedures to get ports and
>>> service names are the same for UDP, TCP, DCCP and SCTP." (Maybe it
>>> would be clearer by explicitly naming these protocols in the document.)
>>>=20
>>> But I see the point you're raising. The document should somewhere say
>>> that "Expert Review" is the procedure used for assignment requests
>>> made directly to IANA, whereas for documents on the IETF Stream, "IETF
>>> Consensus" is sufficient to make the assignment. In other words, no
>>> expert review doesn't really need to happen for those, since IETF
>>> Review and IESG Approval are at least equivalent.
>>=20
>> RFC2434 already gives IANA these options.
>=20
> As does RFC 5226 - its update (there is no substantive change between the t=
wo in this regard, FWIW).
>=20
>> Perhaps - at best - we should include a ref to that.
>=20
> And 5226 is already clearly cited.
>=20
> No further action should be required.
>=20
> Joe
>=20
>> However, this document is not focused at changing what RFC2434 says, and
>> the above statement, IMO, does.
>>=20
>> That's another can of worms, and should be reserved for a different
>> document.
>>=20
>> Joe

From dhc2@dcrocker.net  Mon Jan 31 11:14:50 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 536583A6C40 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 11:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.591
X-Spam-Level: 
X-Spam-Status: No, score=-6.591 tagged_above=-999 required=5 tests=[AWL=0.008,  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 I427H7EB4K9j for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 11:14:48 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 227F63A6A7A for <ietf@ietf.org>; Mon, 31 Jan 2011 11:14:48 -0800 (PST)
Received: from [192.168.1.7] (adsl-68-122-35-253.dsl.pltn13.pacbell.net [68.122.35.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p0VJHveV011041 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 31 Jan 2011 11:18:02 -0800
Message-ID: <4D470AD1.80400@dcrocker.net>
Date: Mon, 31 Jan 2011 11:17:37 -0800
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: Andrew Sullivan <ajs@shinkuro.com>
Subject: Re: prerequisite for change (was Re:	draft-housley-two-maturity-levels)
References: <20110129223900.60C00817786@newdev.eecs.harvard.edu> <AANLkTinLzBs7P2Fw-U2pNVOTqdG-nOOpYNNTMU40QK+2@mail.gmail.com> <20110130145814.GA39423@shinkuro.com> <F3C3FE2A-3DCD-46B2-8E4D-B557AD22A2DC@network-heretics.com> <20110130153551.GB39423@shinkuro.com> <4D458898.8090008@dcrocker.net> <20110130160628.GD39423@shinkuro.com>
In-Reply-To: <20110130160628.GD39423@shinkuro.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 31 Jan 2011 11:18:03 -0800 (PST)
Cc: 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: Mon, 31 Jan 2011 19:14:50 -0000

On 1/30/2011 8:06 AM, Andrew Sullivan wrote:
> On Sun, Jan 30, 2011 at 07:49:44AM -0800, Dave CROCKER wrote:
>> The current proposal specifies a second maturity level that does not
>> permit changing the technical specification.
>
> Yes, I know.  I fail completely to see why anyone would ever do the
> work for such movement of maturity level.  The proposal seems to me to
> be something along the lines of giving gold stars to protocols with
> people who are willing to do the busywork.


One of the challenges in the discussion of this topic on the IETF list is some 
very different models of the role of a standards label.  Given the frequent view 
that only technical details matter, one would think that we are composed only of 
engineers who give little thought to organizational, social and psychological 
factors that might also affect adoption decisions...

One curiosity about this is that our documentation style for specifications 
permits far more tutorial and explanatory content than most other standards 
group, which one might take to indicate that we actually worry a bit about those 
who will adopt our work and that we actually want to help them.  Yet our 
organization mode tends to consider 'publication' the end of our concern.

As folks in the communications game, the IETF tends to have a curious lack of 
interest in the 'feedback' portion of a Shannon-Weaver model[1], when it comes 
to protocol adoption.  It's as if we stopped reading after the first Shannon 
paper.[2]

In any event, I thought the value proposition of the proposal's second label had 
been discussed at some length:

    For significant portions of industry, the decision whether to adopt new 
technology relies heavily on an assessment of its stability and likely success. 
  Some specs are nascent and fluid.  Some are failed.  Others are successful. As 
of now, it can be difficult for such folk to distinguish the real maturity of 
IETF proposals, since most are at Proposed.

    So the proposal defines a second stage that serves the purpose of making an 
official statement of stability and success, by virtue of noting significant 
deployment.  That can be helpful during the "market expansion" phase of adoption.

d/


[1] <http://en.wikipedia.org/wiki/Shannon%E2%80%93Weaver_model>

[2] <http://plan9.bell-labs.com/cm/ms/what/shannonday/shannon1948.pdf>
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ekr@rtfm.com  Mon Jan 31 11:49:47 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 D367D3A6C64 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 11:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.705
X-Spam-Level: 
X-Spam-Status: No, score=-102.705 tagged_above=-999 required=5 tests=[AWL=0.272, 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 Ols8rC3UBEXq for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 11:49:46 -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 4ADE03A6C57 for <ietf@ietf.org>; Mon, 31 Jan 2011 11:49:46 -0800 (PST)
Received: by gxk27 with SMTP id 27so2488031gxk.31 for <ietf@ietf.org>; Mon, 31 Jan 2011 11:53:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.20.6 with SMTP id 6mr9134238agt.200.1296503580841; Mon, 31 Jan 2011 11:53:00 -0800 (PST)
Received: by 10.90.116.7 with HTTP; Mon, 31 Jan 2011 11:53:00 -0800 (PST)
In-Reply-To: <DFEB1164-0F63-4FCF-A68D-EF7B2F807649@skype.net>
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> <4D46E2FF.7010203@cisco.com> <DFEB1164-0F63-4FCF-A68D-EF7B2F807649@skype.net>
Date: Mon, 31 Jan 2011 11:53:00 -0800
Message-ID: <AANLkTimkvJOdaBSp4r_Lqv5Q=zf1pH1rvhQB+Qf0BpLH@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: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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 19:49:47 -0000

On Mon, Jan 31, 2011 at 11:41 AM, Eric Rescorla <ekr@skype.net> wrote:
> So first, we already have a BCP that says =A0more or less all protocols m=
ust implement a secure version but deployment is optional. This is a good B=
CP, and it comes from the right area to say that - security. It's probably =
impacts design work in working groups more than any other BCP. It has IETF =
consensus. The IESG holds protocols to this.
>
> Now - I am at loss to see why forcing people to use one port will make it=
 more likely to have secure protocols. This seems crazy. =A0Please do enlig=
hten me.

I don't think it does.

At a high level, there are three ways in which insecure and secure
versions (by which I mostly mean channel security mechanisms such as
TLS) of the same protocol can coexist:

1. They can operate on totally different transport parameters (e.g., ports)
2. They can be demuxable by some indicator that's simply sent by one
side and accepted or rejected by the other side. (E.g., "If the first
byte is 20 this is TLS, else it's not)
3. It can be negotiated as in STARTTLS

In the first two of these, the client knows which version it wants
(secure or insecure) and there is no chance for the server to indicate
otherwise other than failing the connection. In the third, the sides
negotiate. So, I think the first question is which general design you
wish to have. Each of these have their merits: negotiation designs are
more complicated but allow for opportunistic security. Unfortunately,
they also allow for downgrade attack, as the experience with STARTTLS
for SMTP shows. By contrast, non-negotiation designs are easier to
implement and provide for referential integrity but not for
opportunistic security. IMO there is a place for both, though I
generally tend towards non-negotiated designs, in part out of a
feeling that the world would be better if people used encryption all
the time.

Clearly, if you're going to do a negotiation design you want a single port.
If you're going to do a non-negotiated design, then I don't see a huge
amount of value in using a single port. It's true that there is a port
consumption issue, but OTOH ports are there for protocol demuxing and
this is clearly another protocol. It's simply a lot easier to have
your TLS stack just start its thing rather than try to autodetect
whether you have TLS or some other protocol. So I would generally push
back on the claim that non-negotiated designs should have to have
demuxing in information in the dataflow rather than use the port.


> And on the topic, I'm still looking forward to an explanation of how the =
current CoAP design stomping all over the TLS code points would be an accep=
table design.

I don't consider this an acceptable design and I've already told the
CoAP authors and chairs so. Speaking as chair, if the CoAP
authors/chairs wish to pursue this avenue they should bring it to the
TLS WG, which AFAIK they have not done.

-Ekr



>
> On Jan 31, 2011, at 9:27 , Eliot Lear wrote:
>
>>
>>
>> On 1/31/11 5:13 PM, Cullen Jennings wrote:
>>> Hmm ... I don't agree that solves the issue.
>>>
>>> Well lets say the request was coming from 3GPP for a protocol they desi=
gned - why should IANA be able to tell them no but IETF yes.
>>
>> Who, ultimately, is the steward of this precious resource? =A0If it is n=
ot
>> the IANA and it is not the IETF, then who? =A0To say that it is everyone=
's
>> responsibility is to avoid responsibility entirely. =A0Who gets to say
>> which standards organizations are stewards and which are not?
>>
>>> I think the policy issue here is fairly clear. We do not have consensus=
 that in all cases that one should not have a second port for security (I'm=
 basing this assertion on Magnus read of WG consensus and my read of IETF L=
C consensus). Therefore that should not be a ground for the expert reviewer=
 (or IANA) to reject the registration. The document needs to be updated to =
make that clear or it does not reflect consensus. If the authors of the dra=
ft want to propose text for conditions when it would be ok to reject a seco=
nd port for security purposes and see if they can get consensus for that te=
xt, that seems perfectly reasonable.
>>
>> This is a VERY VERY dangerous approach you propose, Cullen. =A0It is aki=
n
>> to saying, "you can think about security later, because we'll have to
>> give you a port for it later." =A0We don't want to be saying that.
>>
>
>
> Cullen Jennings
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
>
>

From stig@venaas.com  Mon Jan 31 12:34:39 2011
Return-Path: <stig@venaas.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 AE6033A6C87 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 12:34:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.37
X-Spam-Level: 
X-Spam-Status: No, score=-102.37 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9SN2BV-Qx27y for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 12:34:39 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by core3.amsl.com (Postfix) with ESMTP id C583B3A6C6E for <ietf@ietf.org>; Mon, 31 Jan 2011 12:34:38 -0800 (PST)
Received: from [IPv6:2001:420:4:ea0c:954b:5606:be1f:6b0c] (unknown [IPv6:2001:420:4:ea0c:954b:5606:be1f:6b0c]) by ufisa.uninett.no (Postfix) with ESMTPSA id 5FD917FE6 for <ietf@ietf.org>; Mon, 31 Jan 2011 21:37:52 +0100 (CET)
Message-ID: <4D471DAA.5080402@venaas.com>
Date: Mon, 31 Jan 2011 12:38:02 -0800
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: The IETF <ietf@ietf.org>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
In-Reply-To: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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 20:34:39 -0000

I have now submitted version 04 which I believe addresses the last
call comments. The changes are as follows:

Added the sentence:
The message type is a 4-bit integer with possible values from 0 to 15.

Listing 11-14 as Unassigned.

The references are now all Informational (there was a down reference
to experimental).

There was a comment about expanding the term PIM. PIM has now been
added to the list of well-known abbreviations that don't need to be
expanded. Hence I chose not to expand it.

Stig

From lear@cisco.com  Mon Jan 31 14:08:13 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 88BC13A6B2B for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 14:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.231
X-Spam-Level: 
X-Spam-Status: No, score=-110.231 tagged_above=-999 required=5 tests=[AWL=0.368, 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 rMHtKMRlARZf for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 14:08:08 -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 3CE773A6885 for <ietf@ietf.org>; Mon, 31 Jan 2011 14:08:08 -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: ApkEALvCRk2Q/khLgWdsb2JhbACEFaBmFQEBFiIkohWKYpBGgSOBZ4FQdASMIQ
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 31 Jan 2011 22:11:22 +0000
Received: from dhcp-10-61-100-10.cisco.com (dhcp-10-61-100-10.cisco.com [10.61.100.10]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p0VMBM5O009538; Mon, 31 Jan 2011 22:11:22 GMT
Message-ID: <4D47337E.1070300@cisco.com>
Date: Mon, 31 Jan 2011 23: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: 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>	<4D46E2FF.7010203@cisco.com>	<DFEB1164-0F63-4FCF-A68D-EF7B2F807649@skype.net> <AANLkTimkvJOdaBSp4r_Lqv5Q=zf1pH1rvhQB+Qf0BpLH@mail.gmail.com>
In-Reply-To: <AANLkTimkvJOdaBSp4r_Lqv5Q=zf1pH1rvhQB+Qf0BpLH@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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:08:13 -0000

Eric,
> Clearly, if you're going to do a negotiation design you want a single port.
> If you're going to do a non-negotiated design, then I don't see a huge
> amount of value in using a single port. It's true that there is a port
> consumption issue, but OTOH ports are there for protocol demuxing and
> this is clearly another protocol.

Another way to look at this is that it's the same protocol running atop
a security layer.  Same protocol engine, perhaps in a slightly different
security context in terms of what is authorized.  And there's good
reason to look at it this way.  Aside from the leverage it gives
reviewers as I discussed previously, there's also the minor matter of
port consumption, which won't be so minor if we run short.  And don't
think that can't happen.  Additional ports are being approved for
reasons that are clearly architecture limitations.  I'm not even sure
this is an acceptable excuse.

For one, if we look at some of the examples that have been mooted, I
doubt that an additional port would have solved the downgrade problem. 
The case I have in mind is indeed SMTP.  The conditions that allow for
the downgrade attack have more to do with the realities of certificate
management than STARTTLS.

As I wrote in a different context there is also the draft that Paul has
written for HASTLS, which allows a server to express a policy without
having to require a port.  While some of us have some questions about
some of the choices Paul made in the design, on the whole I think
everyone agrees it's a good idea.  It may not, however, solve the entire
problem, because we now are forced to answer the question as to how host
policy should be conveyed.

>  It's simply a lot easier to have
> your TLS stack just start its thing rather than try to autodetect
> whether you have TLS or some other protocol.

Maybe so (wasn't so hard for me), but there now is a whole lot of free
code out there that does just this.



>  So I would generally push
> back on the claim that non-negotiated designs should have to have
> demuxing in information in the dataflow rather than use the port.

There is a cost that extends beyond the protocol.  That has to be taken
into account.

Eliot

From ekr@rtfm.com  Mon Jan 31 14:18:02 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 7BB5D3A69B8 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 14:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.707
X-Spam-Level: 
X-Spam-Status: No, score=-102.707 tagged_above=-999 required=5 tests=[AWL=0.270, 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 QKMVD+w12R54 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 14:18:01 -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 614573A67F7 for <ietf@ietf.org>; Mon, 31 Jan 2011 14:18:01 -0800 (PST)
Received: by ywk9 with SMTP id 9so2530078ywk.31 for <ietf@ietf.org>; Mon, 31 Jan 2011 14:21:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.104.18 with SMTP id b18mr9544701agc.81.1296512476240; Mon, 31 Jan 2011 14:21:16 -0800 (PST)
Received: by 10.90.116.7 with HTTP; Mon, 31 Jan 2011 14:21:16 -0800 (PST)
In-Reply-To: <4D47337E.1070300@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> <4D46E2FF.7010203@cisco.com> <DFEB1164-0F63-4FCF-A68D-EF7B2F807649@skype.net> <AANLkTimkvJOdaBSp4r_Lqv5Q=zf1pH1rvhQB+Qf0BpLH@mail.gmail.com> <4D47337E.1070300@cisco.com>
Date: Mon, 31 Jan 2011 14:21:16 -0800
Message-ID: <AANLkTik81tYo3UtpPiyrWH5RD1YNy65A1dQWm-DkKETb@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: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.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:18:02 -0000

On Mon, Jan 31, 2011 at 2:11 PM, Eliot Lear <lear@cisco.com> wrote:
> Eric,
>> Clearly, if you're going to do a negotiation design you want a single po=
rt.
>> If you're going to do a non-negotiated design, then I don't see a huge
>> amount of value in using a single port. It's true that there is a port
>> consumption issue, but OTOH ports are there for protocol demuxing and
>> this is clearly another protocol.
>
> Another way to look at this is that it's the same protocol running atop
> a security layer. =A0Same protocol engine, perhaps in a slightly differen=
t
> security context in terms of what is authorized. =A0And there's good
> reason to look at it this way. =A0Aside from the leverage it gives
> reviewers as I discussed previously, there's also the minor matter of
> port consumption, which won't be so minor if we run short. =A0And don't
> think that can't happen. =A0Additional ports are being approved for
> reasons that are clearly architecture limitations. =A0I'm not even sure
> this is an acceptable excuse.

Really? What fraction of the port space has been consumed?


> For one, if we look at some of the examples that have been mooted, I
> doubt that an additional port would have solved the downgrade problem.
> The case I have in mind is indeed SMTP. =A0The conditions that allow for
> the downgrade attack have more to do with the realities of certificate
> management than STARTTLS.

I didn't say it did, if you reread my message. What I said was that
not negotiating
addresses downgrade.


> As I wrote in a different context there is also the draft that Paul has
> written for HASTLS, which allows a server to express a policy without
> having to require a port. =A0While some of us have some questions about
> some of the choices Paul made in the design, on the whole I think
> everyone agrees it's a good idea.

Well, I'm not sure I see the relevance of this. The question is how
the server supports
both secure and insecure variants at once.




>> =A0It's simply a lot easier to have
>> your TLS stack just start its thing rather than try to autodetect
>> whether you have TLS or some other protocol.
>
> Maybe so (wasn't so hard for me),

Well, I have no idea what protocol you're thinking of, but all of the
upward negotiation
protocols have a significantly more complicated state machine than does HTT=
PS.


>but there now is a whole lot of free
> code out there that does just this.

And it's generally all protocol specific, so we have this problem with
every new protocol.


>> =A0So I would generally push
>> back on the claim that non-negotiated designs should have to have
>> demuxing in information in the dataflow rather than use the port.
>
> There is a cost that extends beyond the protocol. =A0That has to be taken
> into account.

Of course. Which is why I'm not saying that you should ALWAYS do a
separate port.
But I don't agree there is consensus that it's bad either.

From Adrian.Farrel@huawei.com  Mon Jan 31 14:41:06 2011
Return-Path: <Adrian.Farrel@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 55E8F3A6AF1; Mon, 31 Jan 2011 14:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.39
X-Spam-Level: 
X-Spam-Status: No, score=-103.39 tagged_above=-999 required=5 tests=[AWL=-0.791, 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 SKwSzer54fIw; Mon, 31 Jan 2011 14:41:04 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id D098B3A67F7; Mon, 31 Jan 2011 14:41:04 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFW00NBPSHV4C@usaga01-in.huawei.com>; Mon, 31 Jan 2011 14:44:20 -0800 (PST)
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LFW00IE4SHTDT@usaga01-in.huawei.com>; Mon, 31 Jan 2011 14:44:19 -0800 (PST)
Date: Mon, 31 Jan 2011 22:44:17 +0000
From: Adrian Farrel <Adrian.Farrel@huawei.com>
Subject: RE: Gen-ART LC Review of draft-ietf-ccamp-mpls-tp-cp-framework-05
In-reply-to: <CFD03B48-6D22-4B6B-A843-B52DF114A101@nostrum.com>
To: 'Ben Campbell' <ben@nostrum.com>, draft-ietf-ccamp-mpls-tp-cp-framework.all@tools.ietf.org, 'General Area Review Team' <gen-art@ietf.org>
Message-id: <067101cbc198$668eb790$33ac26b0$@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: en-gb
Content-transfer-encoding: 7BIT
Thread-index: AQC4hxCfQ9qdcjMyJmrhMDJEGg8QCpYSIPEw
References: <CFD03B48-6D22-4B6B-A843-B52DF114A101@nostrum.com>
Cc: 'The IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian.Farrel@huawei.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, 31 Jan 2011 22:41:06 -0000

Thanks for the review and these minor points.

Russ, I'm going to capture Ben's review in a Comment attached to my Yes ballot,
and the authors can come back and pick them up after the IESG review complete.

Cheers,
Adrian

> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: 31 January 2011 22:25
> To: draft-ietf-ccamp-mpls-tp-cp-framework.all@tools.ietf.org; General Area
> Review Team
> Cc: The IETF
> Subject: Gen-ART LC Review of draft-ietf-ccamp-mpls-tp-cp-framework-05
> 
> 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:
> 
> 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 rbarnes@bbn.com  Mon Jan 31 18:08:24 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 715583A6CB7 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 18:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.208
X-Spam-Level: 
X-Spam-Status: No, score=-102.208 tagged_above=-999 required=5 tests=[AWL=-0.209, BAYES_00=-2.599, J_CHICKENPOX_28=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 HnYBB0e4cSZO for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 18:08:23 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 73EDF3A6CAA for <ietf@ietf.org>; Mon, 31 Jan 2011 18:08:23 -0800 (PST)
Received: from [128.89.254.147] (port=49282 helo=[192.168.0.196]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.71 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Pk5iU-00007p-N1 for ietf@ietf.org; Mon, 31 Jan 2011 21:11:38 -0500
From: "Richard L. Barnes" <rbarnes@bbn.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: IANA IPv4 depletion
Date: Mon, 31 Jan 2011 21:11:35 -0500
Message-Id: <9C2FDB62-A996-45B8-A675-F1A6DCEB5A89@bbn.com>
To: "ietf@ietf.org IETF" <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 02:08:24 -0000

Since it doesn't seem to have hit this list yet:

<http://www.apnic.net/publications/news/2011/delegation>

Dear Colleagues

The information in this announcement is to enable the Internet community =
to update network configurations, such as routing filters, where =
required.

APNIC received the following IPv4 address blocks from IANA in February =
2011 and will be making allocations from these ranges in the near =
future:
 =95 39/8
 =95 106/8
Reachability and routability testing of the new prefixes will commence =
soon. The daily report will be published on the RIPE NCC Routing =
Information Service.

Please be aware, this will be the final allocation made by IANA under =
the current framework and will trigger the final distribution of five /8 =
blocks, one to each RIR under the agreed "Global policy for the =
allocation of the remaining IPv4 address space".

After these final allocations, each RIR will continue to make =
allocations according to their own established policies.

APNIC expects normal allocations to continue for a further three to six =
months. After this time, APNIC will continue to make small allocations =
from the last /8 block, guided by section 9.10 in"Policies for IPv4 =
address space management in the Asia Pacific region". This policy =
ensures that IPv4 address space is available for IPv6 transition.

It is expected that these allocations will continue for at least another =
five years.

APNIC reiterates that IPv6 is the only means available for the sustained =
ongoing growth of the Internet, and urges all Members of the Internet =
industry to move quickly towards its deployment.=

From evnikita2@gmail.com  Mon Jan 31 22:13:24 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 04A683A692C for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 22:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.206
X-Spam-Level: 
X-Spam-Status: No, score=-3.206 tagged_above=-999 required=5 tests=[AWL=0.393,  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 phfOAEMy-iM9 for <ietf@core3.amsl.com>; Mon, 31 Jan 2011 22:13:22 -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 2345F3A687B for <ietf@ietf.org>; Mon, 31 Jan 2011 22:13:21 -0800 (PST)
Received: by fxm9 with SMTP id 9so7037940fxm.31 for <ietf@ietf.org>; Mon, 31 Jan 2011 22:16:37 -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=lgmjaXqlPwjKAvze7cA7MtAos9+LBOXordASsWJbQyA=; b=KPJyajsKQTjCU726t+1CjX7vp0VpgCIn55QyYpESkO7jIYNSlR/GJ+eDWyrKfrfgVG BZuUxcuhNKmWt3t6Jfy9VTnl0WgewD+2xbuXVg9SBuPfuLCdsl9f/MgWp82J8k68yRay abIvSJNWt4lEUXYKTic+PcXLnxUuOjhYf9i54=
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=EvCaM1x/qOmfe65zeX51PyuZIZd1jDBAiA8Ab+SsiKWcguWTIHGq1UMXKF2nGOuyZt 6RqW8LbHbVR/rfDWqXvEeaq3URAy2ZZrGVqAj1q1NNruPMgd2dqzsxDuRFo8N/hAD+rS 9tYlc/byOfrBAsCWmZjbWsOHe7CRFGwG2/CBs=
Received: by 10.223.74.206 with SMTP id v14mr775167faj.66.1296540997718; Mon, 31 Jan 2011 22:16:37 -0800 (PST)
Received: from [127.0.0.1] ([195.191.104.134]) by mx.google.com with ESMTPS id a2sm7679105faw.22.2011.01.31.22.16.35 (version=SSLv3 cipher=RC4-MD5); Mon, 31 Jan 2011 22:16:36 -0800 (PST)
Message-ID: <4D47A55B.3030200@gmail.com>
Date: Tue, 01 Feb 2011 08:16:59 +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: Stig Venaas <stig@venaas.com>
Subject: Re: Last Call on draft-ietf-pim-registry-03.txt
References: <AANLkTin+wxG6oSrvux6DuqZNA1hLGALmozfxzhhGxT3+@mail.gmail.com> <4D471DAA.5080402@venaas.com>
In-Reply-To: <4D471DAA.5080402@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Tue, 01 Feb 2011 06:13:24 -0000

31.01.2011 22:38, Stig Venaas wrote:
> I have now submitted version 04 which I believe addresses the last
> call comments. The changes are as follows:
>
> Added the sentence:
> The message type is a 4-bit integer with possible values from 0 to 15.
>
> Listing 11-14 as Unassigned.
Stig,

Thank you very much for your changes.  Now the registry definition seems 
to be clear.

>
> The references are now all Informational (there was a down reference
> to experimental).
Maybe RFC 5226 should be referenced normatively, as well as some docs. 
connected to PIMv2.  Moreover, the reference to IANA registry should read:

Internet Assigned Numbers Authority (IANA) Registry, "IGMP Type 
Numbers", per RFC 3228, as for <registry update date, for this - 
November 2010>

All the best,
Mykyta Yevstifeyev
>
> There was a comment about expanding the term PIM. PIM has now been
> added to the list of well-known abbreviations that don't need to be
> expanded. Hence I chose not to expand it.
>
> Stig
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

